Datasets:

param-bharat

/

ragbench-context-relevance-filtered

like 1

[ "WTX security bulletin transformation extender POODLE SSL 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 WebSphere Transformation Extender. \n\nVULNERABILITY DETAILS\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\nProducts:\n* WebSphere Transformation Extender with Command Server\n* WebSphere Transformation Extender with Launcher\n* WebSphere Transformation Extender for Application Programming\n* WebSphere Transformation Extender for Integration Servers\n* WebSphere Transformation Extender Design Studio \n\nVersions:\n* 8.3.0.0 - 8.3.0.6\n* 8.4.0.0 - 8.4.0.5\n* 8.4.1.0 - 8.4.1.2\n\nREMEDIATION/FIXES\nDownload and install the interim fix for APAR PI31732 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Transformation+Extender&release=All&platform=All&function=aparId&apars=PI31732] from IBM Fix Central.\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.\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 22 December 2014: 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 WTX", " SECURITY BULLETIN\n\nSUMMARY\n The RC4 “Bar Mitzvah” Attack for SSL/TLS affects IBM Integration Designer and WebSphere Integration Developer. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-2808 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2808]\nDESCRIPTION: The RC4 algorithm, as used in the TLS protocol and SSL protocol, could allow a remote attacker to obtain sensitive information. An attacker could exploit this vulnerability to remotely expose account credentials without requiring an active man-in-the-middle session. Successful exploitation could allow an attacker to retrieve credit card data or other sensitive information. This vulnerability is commonly referred to as \"Bar Mitzvah Attack\".\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/101851 [https://exchange.xforce.ibmcloud.com/vulnerabilities/101851] 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\nThis vulnerability affects IBM Integration Designer and WebSphere Integration Developer.\n\nREMEDIATION/FIXES\nTo fully mitigate these vulnerabilities, an additional fix (JR53201) is required for the following product versions: \n\n * WebSphere Integration Developer V7.0.0.5 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FWebSphere+Integration+Developer&fixids=7.0.0.5-WS-IID-IFJR53201&source=SAR] \n * IBM Integration Designer V7.5.1.2 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Integration+Designer&fixids=7.5.1.2-WS-IID-IFJR53201&source=SAR] \n * IBM Integration Designer V8.0.1.3 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Integration+Designer&fixids=8.0.1.3-WS-IID-IFJR53201&source=SAR] \n * IBM Integration Designer V8.5.0.1 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Integration+Designer&fixids=8.5.0.1-WS-IID-IFJR53201] \n * IBM Integration Designer V8.5.5.0 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Integration+Designer&fixids=8.5.5.0-WS-IID-IFJR53201] \n * IBM Integration Designer V8.5.6.0 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Integration+Designer&fixids=8.5.6.0-WS-IID-IFJR53201]\n\nWORKAROUNDS AND MITIGATIONS\nIf you are using any of the following products: \n\n * IBM Integration Designer V8.5.0.1 \n * IBM Integration Designer V8.5.5.0 \n * IBM Integration Designer V8.5.6.0\n\n\nthen the following steps can be used to remove RC4 from the list of available algorithms: \n\nPrerequisite: Before removing RC4 from the list of available algorithms, you must first install the FREAK: Factoring Attack on RSA-EXPORT keys fix. See this document [http://www.ibm.com/support/docview.wss?uid=swg21700896] for more information. \n\n1. Ensure that the product is not running. \n\n2. Locate the java.security file used by the product from the following location: \ninstall folder/jdk/jre/lib/security/java.security \n\n3. Edit the java.security file with a text editor and locate the line: \njdk.tls.disabledAlgorithms=SSLv3 \n\n4. Add RC4 to the list of disabled algorithms, for example: \njdk.tls.disabledAlgorithms=SSLv3, RC4 \n\n5. Save the file and restart the product. \n\nYou should verify applying this configuration change does not cause any compatibility issues. Not disabling the RC4 stream cipher 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 RC4 stream cipher and take appropriate mitigation 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\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 1 May 2015: original document published\n19 May 2015: document republished \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 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 \nPRODUCT ALIAS/SYNONYM\n IID\nWID", "security; vulnerability; psirt; CVE-2014-3566; sslv3; poodle SECURITY BULLETIN\n\nSUMMARY\n SSLv3 contains a vulnerability that has been referred to as the Padding Oracle On Downgraded Legacy Encryption (POODLE) attack. \n\nVULNERABILITY DETAILS\n \n\nSubscribe to My Notifications to be notified of important product support alerts like this. * Follow this link [https://www.ibm.com/systems/support/myview/subscription/css.wss/subscriptions?methodName=startSearchToSubscribe&uctug_rational_dcfsbblurb_2013-11-05_myn_adoption_promo] for more information (requires login with your IBM ID)\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) AFFECTED PRODUCTS AND VERSIONS\nRational Lifecycle Integration Adapter Tasktop Edition 1.0 through 1.1.3.0.\n\nREMEDIATION/FIXES\nNone\n\nWORKAROUNDS AND MITIGATIONS\nUpgrade to one of the following releases: \n\n * Rational Lifecycle Integration Adapters Tasktop Edition Interim Fix 5 for 1.1.2.4 [http://www.ibm.com/support/docview.wss?uid=swg24038803] \n * Rational Lifecycle Integration Adapters Tasktop Edition Interim Fix 2 for 1.1.3 [http://www.ibm.com/support/docview.wss?uid=swg24038819]\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] \nSubscribe to Security Bulletins [http://www.ibm.com/support/mynotifications/] \nACKNOWLEDGEMENT\nNone \n\nCHANGE HISTORY\n * 12 December 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.", " 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", " 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 WebSphere Dynamic Process Edition. \n\nVULNERABILITY DETAILS\nCVE-ID: CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566]\n\nDESCRIPTION: WebSphere Dynamic Process Edition 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 WebSphere Dynamic Process Edition.\n\nREMEDIATION/FIXES\nWebSphere Dynamic Process Edition completely relies on WebSphere Application Server to provide HTTPS capabilities. \n\n\nIBM recommends that customers install an interim fix for the IBM JDK to disable SSLv3. For information on the required fix, refer to the the Remediation/Fixes section in the following bulletins: \n\n * Security Bulletin: Vulnerability in SSLv3 affects IBM Integration Designer (CVE-2014-3566) [http://www.ibm.com/support/docview.wss?uid=swg21689914] \n * Security Bulletin: Vulnerability in SSLv3 affects WebSphere Business Services Fabric (CVE-2014-3566) [http://www.ibm.com/support/docview.wss?uid=swg21689152] \n * Security Bulletin: Vulnerability in SSLv3 affects WebSphere Process Server, WebSphere Business Compass, and WebSphere Business Modeler Publishing Server (CVE-2014-3566) [http://www.ibm.com/support/docview.wss?uid=swg21689918]\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. \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. WORKAROUNDS 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 the \"Workarounds and Mitigations\" section in the above bulletins.\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 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." ]

[ [ "3a", " SECURITY BULLETIN SUMMARY" ], [ "3b", " SSLv3 contains a vulnerability that has been referred to as the Padding Oracle On Downgraded Legacy Encryption (POODLE) attack." ], [ "3c", "SSLv3 is enabled in IBM Integration Designer and WebSphere Integration Developer. VULNERABILITY DETAILS" ], [ "3d", "CVE-ID: CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566]" ], [ "3e", "DESCRIPTION: 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." ], [ "3f", "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." ], [ "3g", "CVSS Base Score: 4.3" ], [ "3h", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/97013 [https://exchange.xforce.ibmcloud.com/vulnerabilities/97013] for the current score" ], [ "3i", "CVSS Environmental Score*: Undefined" ], [ "3j", "CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)" ], [ "3k", "AFFECTED PRODUCTS AND VERSIONS" ], [ "3l", "This vulnerability affects some versions and releases of IBM Integration Designer and WebSphere Integration Developer. REMEDIATION/FIXES" ], [ "3m", "IBM recommends that you review your entire environment to identify areas that enable the SSLv3 protocol and take appropriate mitigation and remediation actions." ], [ "3n", "The most immediate mitigation action that can be taken is disabling SSLv3." ], [ "3o", "You should verify disabling SSLv3 does not cause any compatibility issues." ], [ "3p", "Note that other related products are also affected by this vulnerability." ], [ "3q", "In the context of applying fixes, you will also want to update Installation Manager to version 1.8 or later." ], [ "3r", "To fully mitigate the POODLE vulnerability for server side components, an additional fix for IBM Integration Designer and WebSphere Integration Developer is required (JR51720):" ], [ "3s", " * 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]" ], [ "3t", " * 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]" ], [ "3u", " * 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]" ], [ "3v", "WORKAROUNDS AND MITIGATIONS" ], [ "3w", "Customers 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]" ], [ "3x", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS" ], [ "3y", " Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. REFERENCES" ], [ "3z", "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]" ], [ "3aa", "On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]" ], [ "3ab", "Security Bulletin: Vulnerability in SSLv3 affects IBM WebSphere Application Server (CVE-2014-3566) [http://www.ibm.com/support/docview.wss?uid=swg21687173] RELATED INFORMATION" ], [ "3ac", "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]" ], [ "3ad", "IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] CHANGE HISTORY" ], [ "3ae", " 2014-11-14- Original Version Published" ], [ "3af", "*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score." ], [ "3ag", "Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. DISCLAIMER" ], [ "3ah", "According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\"" ], [ "3ai", "IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE." ], [ "3aj", "CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY." ], [ "3ak", "Cross 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" ] ]

[ "3a", "3b", "3c", "3d", "3e", "3f", "3g", "3h", "3i", "3j", "3k", "3l", "3m", "3n", "3o", "3p", "3q", "3r", "3s", "3t", "3u", "3v", "3w", "3x", "3y", "3z", "3aa", "3ab", "3ac", "3ad", "3ae", "3af", "3ag", "3ah", "3ai", "3aj", "3ak" ]

[ " SECURITY BULLETIN\n\nSUMMARY\n There is a vulnerability in IBM® SDK Java™ Technology Edition,Version 6.0, 7.0 that is used by IBM Tivoli Composite Application Manager for Transactions. This vulnerability, commonly referred to as “SLOTH”, was disclosed as part of the IBM Java SDK updates in January 2016. \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. This vulnerability is commonly referred to as “SLOTH”. \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/UI:U/C:H/I:L/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Tivoli Composite Application Manager (ITCAM) for Transactions : Versions 7.3.x.x to 7.4.x.x are affected.\n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation/First Fix IBM Tivoli Composite Application Manager for Transaction 7.4\n7.3 IV81569 FixCentral link [http://www-01.ibm.com/support/docview.wss?rs=0&uid=isg400002530] WORKAROUNDS 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· Add MD5 to the jdk.certpath.disabledAlgorithms property - e.g. jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024, MD5 \n\n· Add MD5withRSA to the jdk.tls.disabledAlgorithms property - e.g. 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 JDK 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\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=swg21974193] \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-7575 was reported to IBM by Karthikeyan Bhargavan at INRIA in Paris, France \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.", "java.security; securerandom RELEASE NOTES\n\nABSTRACT\n WebSphere Application Server java.security file may need manual updates \n\nCONTENT\nThe java.security file shipped with WebSphere Application Server is a customizable file. WebSphere Application Server does not update this file when fix packs or i-fixes are applied, to avoid overwriting customizations. \n\nWebSphere Application Server Liberty using the Installation Manager (IM) install method, and the WebSphere Application Server Classic may be affected.\n\nThe java.security file may need manual updates to comply with both security and performance upgrades.\n\nSee the following, organized by Java major version, to determine if your java.security file needs to be manually updated.\n\nJava 8\n\n\n\nJava 8 release start point Description CVE Common name java.security property Java 8 GA Vulnerability in SSLv3 CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566] POODLE jdk.tls.disabledAlgorithms=SSLv3 Java 8 SR1 Vulnerability in RC4 CVE-2015-2808 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2808] Bar Mitzvah jdk.tls.disabledAlgorithms=SSLv3, RC4 Java 8 SR1 FP1 Vulnerability with Diffie-Hellman ciphers CVE-2015-4000 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000] Logjam jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize <768 Java 8 SR2 Performance degradation due to secure random source n/a n/a securerandom.source=file:/dev/urandom Java 8 SR2 FP10 Vulnerability in MD5 CVE-2015-7575 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575] SLOTH jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 1024\n-and-\njdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize <768, MD5withRSA \n\n\nJava 7 and 7.1 \n\nJava 7/7.1 release start point Description CVE Common name java.security property Java 7.1 SR2\n----\nJava 7 SR8 FP10 Vulnerability in SSLv3 CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566] POODLE jdk.tls.disabledAlgorithms=SSLv3 Java 7.1 SR 3\n-----\nJava 7 SR9 Vulnerability in RC4 CVE-2015-2808 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2808] Bar Mitzvah jdk.tls.disabledAlgorithms=SSLv3, RC4 Java 7.1 SR3 FP10\n-----\nJava 7 SR9 FP10 Vulnerability with Diffie-Hellman ciphers CVE-2015-4000 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000] Logjam jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize <768 Java 7.1 SR3 FP30\n-----\nJava 7 SR9 FP30\nVulnerability in MD5 CVE-2015-7575 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575] SLOTH jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 1024\n-and-\njdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize <768, MD5withRSA \n\nJava 6 and 6.1 \n\n\nMinimum Java 6/6.1 Description CVE Common name java.security property Java 6.1 SR8 FP2\n-----\nJava 6 SR16 FP3 Vulnerability in SSLv3 CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566] POODLE jdk.tls.disabledAlgorithms=SSLv3 Java 6.1 SR8 FP7\n-----\nJava 6 SR16 FP7 Vulnerability in RC4 CVE-2015-2808 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2808] Bar Mitzvah jdk.tls.disabledAlgorithms=SSLv3, RC4 Java 6.1 SR8 FP5\n-----\nJava 6 SR16 FP5 Vulnerability with Diffie-Hellman ciphers CVE-2015-4000 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000] Logjam jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize <768 Java 6.1 SR8 FP20\n-----\nJava 6 SR16 FP20 Vulnerability in MD5 CVE-2015-7575 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575] SLOTH jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 1024\n-and-\njdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize <768, MD5withRSA \n\n\nRELATED INFORMATION\n WebSphere Java Versions [http://www-01.ibm.com/support/docview.wss?rs=404&uid=swg27005002]\nWebSphere Java Non-serviceable files [http://www-01.ibm.com/support/docview.wss?uid=swg27046880]\nIBM SDK Java Technology Edition Version 8 fixes [http://www.ibm.com/developerworks/java/jdk/fixes/8/]\nIBM SDK Java Technology Edition Version 7 Release 1 fix [http://www.ibm.com/developerworks/java/jdk/fixes/71/]\nIBM SDK Java Technology Edition Version 7 fixes [http://www.ibm.com/developerworks/java/jdk/fixes/7/]\nIBM SDK for Java 6 with an IBM J9 2.6 virtual machine f [http://www.ibm.com/developerworks/java/jdk/fixes/601/]\nIBM SDK Java Technology Edition Version 6 fixes [http://www.ibm.com/developerworks/java/jdk/fixes/6/]", "z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Using the CPSM API to issue a PERFORM OBJECT(DSNAME) command\n with action=QUIESCE with an invalid LENGTH specified, a\n RESPONSE=FAILED AND REASON=EXCEPTION is returned.\n When a PERFORM OBJECT is issued, CPSM performs a GET to build\n the result set to apply the action against. EYU0XDP3 allocates\n 1024 bytes for the GET command descriptor. However, if it is\n larger, CSPM incorrectly fails the request with RESPONSE=FAILED\n and REASON=EXCEPTION.\n Additional Symptom(s) Search Keyword(s):\n KIXREVRJS\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All CICSPlex SM V3R2M0 Users *\n ****************************************************************\n * PROBLEM DESCRIPTION: Users may receive RESPONSE=FAILED, *\n * REASON=EXCEPTION when issuing an API *\n * PERFORM OBJECT command, if a CRITERIA *\n * and/or PARM is specified in the command *\n * and the combined LENGTH and/or PARMLEN *\n * specified is greater than 736. *\n ****************************************************************\n * RECOMMENDATION: After applying the PTF that resolves this *\n * APAR, all CMASes must be restarted. Note *\n * that the restarts do not need to occur at *\n * the same time. *\n ****************************************************************\n When a PERFORM OBJECT command is issued, method EYU0XDP3 (XDP3)\n creates a GET command descriptor to pass to method EYU0XDP1\n (XDP1) to build the result set of records to change for the\n PERFORM OBJECT action. XDP3 reserves 1024 bytes of working\n storage for the GET command descriptor. The fixed portion of\n the GET command descriptor is 288 bytes. If CRITERIA is\n specified in the PERFORM OBJECT command, this is also included\n in the GET command descriptor. If PARM is specified in the\n PERFORM OBJECT command, this may also be included in the GET\n command descriptor. If the LENGTH of the CRITERIA is greater\n than 736 or if the PARM is included in the GET command\n descriptor and the combined value of LENGTH and PARMLEN is\n greater than 736, then this plus the fixed portion would exceed\n the 1024 bytes allocated by XDP3 for the GET command descriptor,\n resulting in FAILED/EXCEPTION being returned to the user.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * XDP3 has been updated to check if the size required for the GET\n command descriptor will exceed the 1024 bytes allocated in its\n working storage. If it does, XDP3 will getmain and use an area\n large enough to hold the GET command descriptor and will free\n the area on exit.\n \n \n \n \n \n\nTEMPORARY FIX\n * FIX AVAILABLE BY PTF ONLY\n \n \n \n \n \n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PK73810\n \n \n * REPORTED COMPONENT NAME\n CICSTS V3 Z/OS\n \n \n * REPORTED COMPONENT ID\n 5655M1500\n \n \n * REPORTED RELEASE\n 50M\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 2008-10-14\n \n \n * CLOSED DATE\n 2008-10-17\n \n \n * LAST MODIFIED DATE\n 2008-11-03\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 UK40816\n \n \n\nMODULES/MACROS\n * EYU0XDP3\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n CICSTS V3 Z/OS\n \n \n * FIXED COMPONENT ID\n 5655M1500\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R50M PSY UK40816 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK40816]\n UP08/10/18 P F810\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.", "z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * If a CICS region is configured to use SSL and the default\n certificate in the keyring used by the CICS region has a private\n key length greater than 1024 then CICS display message\n \n DFHXS0002 xxxxxxxxx A severe error (code X'0109') has occurred\n in module DFHXSDM.\n \n and then abend U1800.\n \n \n \n \n \n\nLOCAL FIX\n * Create the default certificate to be used by the CICS/SSL\n connection to have a private key length of 1024 or less.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All CICS users. *\n ****************************************************************\n * PROBLEM DESCRIPTION: DFHXS0002 A severe error *\n * (code X'0109') has occurred in module *\n * DFHXSDM. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n A keyring was created where the default certificate had a\n private key size greater than 1024 bytes, this was then\n specified as the KEYRING parameter in the CICS System\n Initialisation Table (the SIT). During CICS initialisation\n msgDFHXS0002 was issued and CICS abended with U1800.\n This is because DFHXSIS does not supply a large enough\n buffer on the IRRSDL00 call to RACF which is used to obtain\n the certificate and the private key.\n The same problem will occur if a TCPIPSERVICE or a\n CORBASERVER is defined specifying a certificate with a private\n key greater than 1024 bytes in length. In that case DFHXSCT\n does not supply a large enough buffer. When the resource is\n installed, this results in msgDFHXS0002 being issued.\n \n Additional keywords: msgDFHXS0002 XS0002 U1800 SSL 0109\n GET-PARMS-FAILED 0B08 IRRSDL00_ERROR INQUIRE_CERTIFICATE\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * DFHXSIS and DFHXSCT have been changed to pass a buffer of\n length 4096 on the IRRSDL00 call.\n \n \n \n \n \n\nTEMPORARY FIX\n * *********\n * HIPER *\n *********\n FIX AVAILABLE BY PTF ONLY\n \n \n \n \n \n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PK89833\n \n \n * REPORTED COMPONENT NAME\n CICS TS Z/OS V4\n \n \n * REPORTED COMPONENT ID\n 5655S9700\n \n \n * REPORTED RELEASE\n 600\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n YesHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2009-06-25\n \n \n * CLOSED DATE\n 2009-07-27\n \n \n * LAST MODIFIED DATE\n 2009-08-03\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n PK87785 [http://www-01.ibm.com/support/docview.wss?uid=swg1PK87785]\n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n UK48716\n \n \n\nMODULES/MACROS\n * DESXSCT DESXSIS DFHXSCT DFHXSIS\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n CICS TS Z/OS V4\n \n \n * FIXED COMPONENT ID\n 5655S9700\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R600 PSY UK48716 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK48716]\n UP09/07/29 P F907\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.", " TECHNOTE (FAQ)\n\nQUESTION\n How to find and list large files in IFS \n\nCAUSE\nThis tip can be helpful when your system is running out of storage and you are trying to identify large files in IFS that could potentially be taking up room, like ISO image files etc. \n\nANSWER\nFind based on size\n\n\nYou can use the \"find\" command to search a filesystem to find large files. I especially like the \"-xdev\" flag which tells find to not traverse in to directories that are not part of the filesystem you are searching on. This is especially useful when your \"/\" (root) filesystem fills up because if you do a \"find\" on \"/\" without -xdev it will search every filesystem on the system since they are mounted under \"/\". But with \"-xdev\" it will only search what is actually in the \"/\" filesystem and skip everything else. \n\nThese commands need to run in PASE shell. \n\nYou can launch PASE shell from OS/400 commandline by using CALL QP2TERM. \n\nFind all files larger than 1 MB: \n\nfind /tmp -xdev -size +`echo 1024*1024 | bc`c -ls \n\nSample output:\n\n44178 7954 -rwxrwxrwx 1 qbrms 0 8144071 Dec 3 10:19 /tmp/brms/flightrec \n71392 276152 -rwxrwxrwx 1 qbrms 0 282779391 Dec 19 10:54 /tmp/brms/qbrms \n4096 2689 -rwxrwxrwx 1 kentb 0 2752708 Feb 10 2014 /tmp/Lionel.pdf\n\n\nFind all files larger than 40 MB: \n\nfind /tmp -xdev -size +`echo 1024*1024*40 | bc`c -ls \n\nFind all files larger than 1 GB: \n\nfind /tmp -xdev -size +`echo 1024*1024*1024 | bc`c -ls \n\nYou can replace /tmp with the directory of your own interest i.e /home/* or /QIBM/UserData/* etc \n\nNote that I'm just doing simple math with \"bc\" to calculate the byte size. For example, if you wanted 500 MB it would be 1024*1024*500. If you wanted 50 GB it would be 1024*1024*1024*50.\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Operating System IBM i 7.2 Operating System IBM i 7.1 Operating System IBM i 6.1" ]

[ [ "3a", "z/os A FIX IS AVAILABLE" ], [ "3b", "Obtain the fix for this APAR. SUBSCRIBE" ], [ "3c", "You can track all active APARs for this component. APAR STATUS" ], [ "3d", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "3e", " * If a CICS region is configured to use SSL and the default" ], [ "3f", " certificate in the keyring used by the CICS region has a private" ], [ "3g", " key length greater than 1024 then CICS display message" ], [ "3h", " DFHXS0002 xxxxxxxxx A severe error (code X'0109') has occurred" ], [ "3i", " in module DFHXSDM." ], [ "3j", " and then abend U1800. LOCAL FIX" ], [ "3k", " * Create the default certificate to be used by the CICS/SSL" ], [ "3l", " connection to have a private key length of 1024 or less. PROBLEM SUMMARY" ], [ "3m", " * ****************************************************************" ], [ "3n", " * USERS AFFECTED: All CICS users. *" ], [ "3o", " ****************************************************************" ], [ "3p", " * PROBLEM DESCRIPTION: DFHXS0002 A severe error *" ], [ "3q", " * (code X'0109') has occurred in module *" ], [ "3r", " * DFHXSDM. *" ], [ "3s", " ****************************************************************" ], [ "3t", " * RECOMMENDATION: *" ], [ "3u", " ****************************************************************" ], [ "3v", " A keyring was created where the default certificate had a" ], [ "3w", " private key size greater than 1024 bytes, this was then" ], [ "3x", " specified as the KEYRING parameter in the CICS System" ], [ "3y", " Initialisation Table (the SIT)." ], [ "3z", "During CICS initialisation" ], [ "3aa", " msgDFHXS0002 was issued and CICS abended with U1800." ], [ "3ab", " This is because DFHXSIS does not supply a large enough" ], [ "3ac", " buffer on the IRRSDL00 call to RACF which is used to obtain" ], [ "3ad", " the certificate and the private key." ], [ "3ae", " The same problem will occur if a TCPIPSERVICE or a" ], [ "3af", " CORBASERVER is defined specifying a certificate with a private" ], [ "3ag", " key greater than 1024 bytes in length." ], [ "3ah", "In that case DFHXSCT" ], [ "3ai", " does not supply a large enough buffer." ], [ "3aj", "When the resource is" ], [ "3ak", " installed, this results in msgDFHXS0002 being issued." ], [ "3al", " Additional keywords: msgDFHXS0002 XS0002 U1800 SSL 0109" ], [ "3am", " GET-PARMS-FAILED 0B08 IRRSDL00_ERROR INQUIRE_CERTIFICATE PROBLEM CONCLUSION" ], [ "3an", " * DFHXSIS and DFHXSCT have been changed to pass a buffer of" ], [ "3ao", " length 4096 on the IRRSDL00 call. TEMPORARY FIX" ], [ "3ap", " * *********" ], [ "3aq", " * HIPER *" ], [ "3ar", " *********" ], [ "3as", " FIX AVAILABLE BY PTF ONLY COMMENTS APAR INFORMATION" ], [ "3at", " * APAR NUMBER" ], [ "3au", " PK89833" ], [ "3av", " * REPORTED COMPONENT NAME" ], [ "3aw", " CICS TS Z/OS V4" ], [ "3ax", " * REPORTED COMPONENT ID" ], [ "3ay", " 5655S9700" ], [ "3az", " * REPORTED RELEASE" ], [ "3ba", " 600" ], [ "3bb", " * STATUS" ], [ "3bc", " CLOSED PER" ], [ "3bd", " * PE" ], [ "3be", " NoPE" ], [ "3bf", " * HIPER" ], [ "3bg", " YesHIPER" ], [ "3bh", " * SPECIAL ATTENTION" ], [ "3bi", " NoSpecatt" ], [ "3bj", " * SUBMITTED DATE" ], [ "3bk", " 2009-06-25" ], [ "3bl", " * CLOSED DATE" ], [ "3bm", " 2009-07-27" ], [ "3bn", " * LAST MODIFIED DATE" ], [ "3bo", " 2009-08-03" ], [ "3bp", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "3bq", " PK87785 [http://www-01.ibm.com/support/docview.wss?uid=swg1PK87785]" ], [ "3br", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:" ], [ "3bs", " UK48716 MODULES/MACROS" ], [ "3bt", " * DESXSCT DESXSIS DFHXSCT DFHXSIS FIX INFORMATION" ], [ "3bu", " * FIXED COMPONENT NAME" ], [ "3bv", " CICS TS Z/OS V4" ], [ "3bw", " * FIXED COMPONENT ID" ], [ "3bx", " 5655S9700" ], [ "3by", "APPLICABLE COMPONENT LEVELS" ], [ "3bz", " * R600 PSY UK48716 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK48716]" ], [ "3ca", " UP09/07/29 P F907" ], [ "3cb", "FIX IS AVAILABLE" ], [ "3cc", " * SELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL." ], [ "3cd", "YOU WILL BE REQUIRED TO SIGN IN." ], [ "3ce", "DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES." ] ]

[ "3d", "3e", "3f", "3g", "3h", "3i", "3k", "3l", "3v", "3w", "3x", "3z", "3aa" ]

[ " 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", "z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * SET CHLAUTH command used with ADDRESS (' ')\n leads to abend 5C5 with RC 00D400A6 in CSQMSCA\n (set CHLAUTH processor).\n \n Qmgr trace shows in CEXIT for rsxSetChlAuthMap\n return code 20009231.\n \n This return code means rrcE_INVALID_PARAMETER\n \n The parameter ADDRESS(' ') is causing this return code that\n results in this abend.\n \n \n \n \n \n\nLOCAL FIX\n * add a value for the ADDRESS parameter\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *\n * Release 0 Modification 0. *\n ****************************************************************\n * PROBLEM DESCRIPTION: SET CHLAUTH('xx') TYPE(ADDRESSMAP) with *\n * keyword ADDRESS(' ') generates error *\n * message CSQ9017E and abend 5C6-00D400A6 *\n * in CSQMSCA. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n When command SET CHLAUTH('xx') TYPE(ADDRESSMAP) ADDRESS(' ') is\n used to add or remove channel authentication records generates\n abend 5C6-00D400A6 in CSQMSCA to report that ADDRESS(' ')\n parameter is invalid.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * SET CHLAUTH('xx') TYPE(ADDRESSMAP) has been changed to issue\n error messages CSQM192I and CSQ9023E to report that parameter\n ADDRESS(' ') is invalid and that the command has terminated\n abnormally. No abends are generated.\n 000Y\n CSQMSCA\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI62545\n \n \n * REPORTED COMPONENT NAME\n WMQ Z/OS 8\n \n \n * REPORTED COMPONENT ID\n 5655W9700\n \n \n * REPORTED RELEASE\n 000\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 2016-05-17\n \n \n * CLOSED DATE\n 2016-05-31\n \n \n * LAST MODIFIED DATE\n 2016-08-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 UI38279\n \n \n\nMODULES/MACROS\n * CSQMSCA\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WMQ Z/OS 8\n \n \n * FIXED COMPONENT ID\n 5655W9700\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R000 PSY UI38279 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI38279]\n UP16/07/06 P F607\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.", "z/os SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DOCUMENTATION ERROR.\n \n \n \n\nERROR DESCRIPTION\n * The purpose of this DOC APAR is to update the PCF\n documentation for Channel Authentication Records\n to include a syntax diagram similar to that in\n the MQSC reference.\n .\n The syntax diagram for the MQSC command in the\n following link shows that WARN should not be\n used together with USERSRC(CHANNEL) or\n USERSRC(MAP).\n .\n http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/\n topic/com.ibm.mq.doc/sc14440_.htm [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.doc/sc14440_.htm]\n .\n And\n .\n PCF description of command MQCMD_SET_CHLAUTH_REC\n .\n http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/\n topic/com.ibm.mq.doc/pc20640_.htm [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.doc/pc20640_.htm]\n .\n The new Channel Authentication Record objects\n are much more complex, with a combination of\n primary attributes and secondary attributes where\n the validity of the secondary attribute (e.g. WARN)\n depends on the value Of a primary attribute\n (e.g. USERSRC).\n .\n Capturing all the valid and invalid combinations\n in a text description is extremely difficult.\n .\n A DOC APAR is the best solution to update\n the PCF documentation for Channel Authentication\n Records to include a syntax diagram similar\n to that in the MQSC reference.\n \n \n \n \n \n\nLOCAL FIX\n * n/a\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of WebSphere MQ Version 7 Release *\n * 1 Modification 0. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n Syntax of PCF command MQCMD_SET_CHLAUTH_REC is complex and\n description in V710 infocenter does not show clearly the uses\n and restrictions of the parameters and values for the different\n types of channel authentication records.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * === Documentation update to MQ V7.1 Infocenter ======\n Refer to MQ V7.1 infocenter link:\n http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/\n topic/com.ibm.mq.doc/pc20640_.htm [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.doc/pc20640_.htm]\n \n The MQ V7.1.0 Infocenter will be updated with a syntax diagram\n for the PCF command Set Channel Authentication Record:\n >WebSphere MQ\n ->Reference\n -->Administration reference\n --->Programable command formats reference\n ---->Definitions of PCFs\n ----->Set Channel Authentication Record\n The description of the PCF command Set Channel\n Authentication Record (MQCMD_SET_CHLAUTH_REC)\n will be updated with a syntax diagram similar\n to the diagram for the MQSC commmand\n SET CHLAUTH found in the following infocenter link:\n http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/ [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/]\n topic/com.ibm.mq.doc/sc14440_.htm#sc14440___S1\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM65186\n \n \n * REPORTED COMPONENT NAME\n WMQ Z/OS V7\n \n \n * REPORTED COMPONENT ID\n 5655R3600\n \n \n * REPORTED RELEASE\n 100\n \n \n * STATUS\n CLOSED DOC\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-05-22\n \n \n * CLOSED DATE\n 2012-06-07\n \n \n * LAST MODIFIED DATE\n 2012-06-07\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\nAPPLICABLE COMPONENT LEVELS", "z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Various problems found during final test cycle.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n * All users of IBM MQ for z/OS Version 9 Release 0 *\n * Modification 0. *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * Various problems found during the final test cycle. *\n ****************************************************************\n * RECOMMENDATION: *\n * N/A *\n ****************************************************************\n Various queue-manager and channel initiator problems found\n during the final test cycle.\n \n For example,\n CHIN ABEND S0C4-00000038 in CSQXRCTL when DIAG traps are\n enabled.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The following APAR fixes are included in this APAR:\n \n PI40486 - INTEGRITY PROBLEM\n PI41923 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI41923] - WMQ ABENDA78 ABEND0C4 DURING EXECUTION OF SVRCONN\n CHANNEL EXIT\n PI50176 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI50176] - RECEIVE CSQX205E WHEN TRYING TO START A LISTENER WITH\n IPADDR SPECIFYING A DOTTED-DECIMAL ADDRESS\n PI54598 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI54598] - WMQ Z/OS V800: PREVENT THE MESSAGES FROM BEING\n GENERATED OUT-OF-ORDER FOR QUEUE SERVICE INTERVAL EVENT\n PI55997 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI55997] - CSQX218E MQ LISTENER FAILS TO RESTART USING IP ADDRESS\n 0.0.0.0\n PI56364 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI56364] - MESSAGES STUCK ON SYSTEM.QSG.TRANSMIT.QUEUE AFTER\n CSQM065E (MQRC=2124 FOLLOWED BY ABEND 5C6-00D40050\n PI56916 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI56916] - MQ ABEND S5C6 ABN=5C6-00F20042 MQCLOSE ERROR\n M=CSQGFRCV,LOC=CSQ2IEPL.CSQ2QCP0+0000455C - PI38007 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI38007] APPLIED\n PI59408 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI59408] - WMQ WHEN USING SDEFS TO CREATE QMODEL DEFINITIONS THIS\n FAILS WITH CSQN103I CSQM148I CSQ9023E\n PI59706 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI59706] - WMQ V8 - CSQX479E RECEIVED FOR A SHARED RECEIVER\n CHANNEL WHEN IT IS STARTED ON A DIFFERENT QMGR IN THE QSG.\n PI60014 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI60014] - WMQ ABENDS0C4 ABN=0C4-00000004\n BUFF-CSQP3GET,M=CSQGFRCV,LOC=CSQPLPLM.CSQP3GET ABEND S0C4 0C4\n BUFFER POOLS ABOVE THE BAR\n PI60172 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI60172] - STORAGE LEAK CAUSING HIGH CPU IN CHIN ASID DUE TO\n FRAGEMENTION.\n PI60242 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI60242] - WMQ CSQN212E COMMAND SERVER ERROR PUTTING TO REPLY TO\n QUEUE MQRC 2052\n PI60424 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI60424] - MQ MSTR ADDRESS SPACE RECEIVED\n ABEND=S026,REASON=08118001 WITH REASON=00C510AB\n PI60478 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI60478] - MQ MQINQ FOR MQCA_CUSTOM ATTRIBUTE FAILS WITH\n MQRC_SELECTOR_ERROR ERROR RC2067 ( 0813 ) ( 2067 )\n PI61141 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI61141] - WMQ JAVA THREADS FOR MQGET HANG AFTER WEBSPHERE MQ JMS\n MAINTENANCE IS APPLIED 16/05/04 PTF PECHANGE\n PI61291 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI61291] - WMQ Z/OS V8: CSQ2004E WITH MQRC=2013\n (MQRC_EXPIRY_ERROR) AFTER CSQ2005I WITH FEEDBACK=292\n (MQFB_NOT_AUTHO 16/04/28 PTF PECHANGE\n PI61741 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI61741] - WMQ V8:ABEND 5C6 RSN00F30230 WHEN STOP QMGR\n MODE(FORCE)\n PI61954 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI61954] - DURING FORWARD MIGRATION FROM V6 TO V800, THE PROPCTL\n ATTRIBUTE SHOULD BE SET TO V6COMPAT, AFTER BACKWARDS MIGRATION\n PI62545 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI62545] - WMQ V8: ABEND 5C6-00D400A6 AFTER SET CHLAUTH COMMAND\n PI63137 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI63137] - WMQ: CONTENTS OF SMDS DO NOT MATCH WITH CONTENTS OF CF\n FOR MESSAGE BEING READ DUE TO ERROR IN RECOVER CFSTRUCT\n PROCESSING\n PI63883 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI63883] - WMQ Z/OS V800:SET CHLAUTH CLNTUSER PARAMETER IS 12\n CHARACTERS WHICH CAUSES CSQY337E\n PI64205 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI64205] - WMQ V800 ABEND5C6 WITH REASON CODE 00C51059 AT\n BROADCAST LAST CLOSE OF SHARED QUEUE TO ACTIVE QUEUE MANAGERS IN\n QSG.\n PI64235 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI64235] - ABEND 0C4 OCCURS IN CSQJL002.CSQJOFF1 DURING QUEUE\n MANAGER SHUTDOWN\n PI64687 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI64687] - CSQUTIL TRIED TO FORMAT PAGES BEYOND THE 64 GB LIMIT.\n PI64757 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI64757] - MQMSTR HIGH CPU CONSUMPTION AND FLOOD OF MESSAGES\n IGD103I IGD104I RELATED TO BSDS AND LOG OF A STOPPED MEMBER OF\n QSG\n PI66686 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI66686] - WMQ: SHUTDOWN HANGS FOR AN MQ APPLICATION AND THEN THE\n QUEUE MANAGER AFTER Z/OS MAINTENANCE IS APPLIED.\n \n The following new messages are introduced by this APAR:\n \n CSQY344E\n csect-name&#160;Loading of channel authentication rules failed,\n profile&#160;rule-name&#160;is restricted\n \n Severity\n 8\n \n Explanation\n During initialization the queue manager was unable to load the\n channel authentication rules because profile&#160;rule-name&#160;uses\n function that is disabled by the queue manager mode of operation\n (OPMODE).\n \n For example, the channel authentication profile has been defined\n with a hostname but the queue manager mode of operation is\n OPMODE(COMPAT,800), so version 8 new functions are not\n available. Only the first profile found is reported so other\n restricted profiles might also exist.\n \n System action\n Queue manager initialization continues, but inbound channels are\n not permitted to start.\n \n System programmer response\n Ensure the queue manager mode of operation is correctly\n configured. If the configuration is correct, remove channel\n authentication profiles that use restricted function, then\n restart the queue manager.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI65369\n \n \n * REPORTED COMPONENT NAME\n MQ Z/OS V9\n \n \n * REPORTED COMPONENT ID\n 5655MQ900\n \n \n * REPORTED RELEASE\n 000\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 2016-07-07\n \n \n * CLOSED DATE\n 2016-08-12\n \n \n * LAST MODIFIED DATE\n 2016-10-03\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 UI40085 UI40086 UI40087 UI40088 UI40089 UI40090\n \n \n\nMODULES/MACROS\n * CSQFMDIF CSQFMTXF CSQFSTXF CSQFXTXF CSQFYDIF\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n MQ Z/OS V9\n \n \n * FIXED COMPONENT ID\n 5655MQ900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R000 PSY UI40085 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI40085]\n UP16/09/20 P F609\n \n \n * R001 PSY UI40086 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI40086]\n UP16/09/20 P F609\n \n \n * R002 PSY UI40087 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI40087]\n UP16/09/20 P F609\n \n \n * R003 PSY UI40088 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI40088]\n UP16/09/20 P F609\n \n \n * R004 PSY UI40089 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI40089]\n UP16/09/20 P F609\n \n \n * R005 PSY UI40090 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI40090]\n UP16/09/20 P F609\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.", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * For either BLOCKADDR or BLOCKUSER in a CHLAUTH rule you can\n provide a list of addresses or users.\n .\n For each of these fields the type is listed in the MQ Knowledge\n Center as:\n .\n AddrList (MQCFSL)\n A list of up to 100 IP address patterns which are banned from\n accessing this queue manager on any channel\n (parameter identifier: MQCACH_CONNECTION_NAME_LIST).\n .\n UserList (MQCFSL)\n A list of up to 100 user IDs which are banned from use of this\n channel or set of channels\n (parameter identifier: MQCACH_MCA_USER_ID_LIST).\n .\n It was discovered that, if the command server's response from\n the MQCMD_INQUIRE_CHLAUTH_RECS command contained multiple IP\n addresses or user IDs, the PCF message conformed to that listed\n in the MQ Knowledge Center. That is, the field type was MQCFSL.\n However, if the response contained a single IP address or a\n single user ID, the field type was MQCFST.\n .\n In MQ Java, when you inquire the PCF message fields\n MQCACH_CONNECTION_NAME_LIST and MQCACH_MCA_USER_ID_LIST you\n have to use the getStringParameterValue method when there is\n only 1 user or address and the getStringListParameterValue\n method when there are multiple addresses or users.\n .\n The exception triggered when using the\n getStringListParameterValue when only one address or user is\n blocked is:\n .\n Exception:\n java.lang.ClassCastException: java.lang.String cannot be cast\n to java.lang.String\n .\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n This affects users of PCF applications, which query channel\n authentication (CHLAUTH) records of type BLOCKUSER or BLOCKADDR.\n \n \n Platforms affected:\n MultiPlatform\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n When responding to an inquire chlauth request\n (MQCMD_INQUIRE_CHLAUTH_RECS) for BLOCKUSER or BLOCKADDR records,\n the MQ queue manager's command server incorrectly returned the\n MQCACH_MCA_USER_ID_LIST and MQCACH_CONNECTION_NAME_LIST fields\n as string type (MQCFST) instead of string list (MQCFSL) if there\n was only one item the list.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The MQ queue manager's command server logic has been updated to\n always return MQCACH_CONNECTION_NAME_LIST and\n MQCACH_MCA_USER_ID_LIST as a string list type (MQCFSL) in its\n response to the MQCMD_INQUIRE_CHLAUTH_RECS command.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v8.0 8.0.0.8\n v9.0 CD 9.0.4\n v9.0 LTS 9.0.0.3\n \n The latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n \n If the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT18341\n \n \n * REPORTED COMPONENT NAME\n WMQ BASE MULTIP\n \n \n * REPORTED COMPONENT ID\n 5724H7251\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 2016-12-09\n \n \n * CLOSED DATE\n 2017-08-14\n \n \n * LAST MODIFIED DATE\n 2017-08-14\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 WMQ BASE MULTIP\n \n \n * FIXED COMPONENT ID\n 5724H7251\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R800 PSY\n UP" ]

[ [ "0a", " TECHNOTE (FAQ) QUESTION" ], [ "0b", " You have added a channel authentication record into a WebSphere MQ 7.1 or later queue manager:" ], [ "0c", "SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) USERSRC(CHANNEL) ACTION(ADD)" ], [ "0d", "AMQ8877: WebSphere MQ channel authentication record set." ], [ "0e", "Then you display it:" ], [ "0f", "DISPLAY CHLAUTH(*) TYPE(USERMAP)" ], [ "0g", "1 : DISPLAY CHLAUTH(*) TYPE(USERMAP)" ], [ "0h", "AMQ8878: Display channel authentication record details. CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) USERSRC(CHANNEL)" ], [ "0i", "Now you want to remove it and you try executing the following runmqsc command which you constructed using copy and paste from the above output:" ], [ "0j", "DELETE CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) USERSRC(CHANNEL)" ], [ "0k", "3 : DELETE CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) USERSRC(CHANNEL)" ], [ "0l", "You get the following error:" ], [ "0m", "AMQ8405: Syntax error detected at or near end of command segment below:- DELETE CHLAUTH" ], [ "0n", "The 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)." ], [ "0o", "You try now:" ], [ "0p", "SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) ACTION(REMOVE)" ], [ "0q", "19 : SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) ACTION(REMOVE)" ], [ "0r", "But you get the following error:" ], [ "0s", "AMQ8884: Channel authentication record not found." ], [ "0t", "You specified the attribute CLNTUSER(testuser) as it was shown in the output of the DISPLAY CHLAUTH(*), thus, you think the record should be found." ], [ "0u", "You want to know what is the problem? CAUSE" ], [ "0v", "See the following section of the MQ 7.1 documentation:" ], [ "0w", "WebSphere MQ > Administering > Administering local WebSphere MQ objects > Performing local administration tasks using MQSC commands" ], [ "0x", "WebSphere MQ object names [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/fa11060_.htm]" ], [ "0y", "+ Case-sensitivity in MQSC commands" ], [ "0z", "MQSC commands, including their attributes, can be written in upper-case or lower-case." ], [ "0aa", "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." ], [ "0ab", "If quotation marks are not used, the object is processed with a name in upper-case." ], [ "0ac", "When 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: CLNTUSER(TESTUSER)" ], [ "0ad", "And in this case, there is no record for the user TESTUSER (the record is for 'testuser'). ANSWER" ], [ "0ae", "NOTICE that the userid mentioned in the CLNTUSER field of the output of the DISPLAY CHLAUTH command is NOT surrounded by single quotes." ], [ "0af", "However, you MUST include the single quotes when specifying the value during an ACTION(REMOVE):" ], [ "0ag", "SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER('testuser') ACTION(REMOVE)" ], [ "0ah", "1 : set CHLAUTH(*) TYPE(USERMAP) CLNTUSER('testuser') ACTION(REMOVE)" ], [ "0ai", "AMQ8877: WebSphere MQ channel authentication record set." ], [ "0aj", "++ Example of record with more attributes" ], [ "0ak", "Let's examine the case when a record has more attributes, such as:" ], [ "0al", "SET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('client_1') USERSRC(MAP) MCAUSER('user_1') ADDRESS('*') ACTION(ADD)" ], [ "0am", "AMQ8877: WebSphere MQ channel authentication record set. display CHLAUTH(MY.CHANNEL)" ], [ "0an", "9 : display CHLAUTH(MY.CHANNEL)" ], [ "0ao", "AMQ8878: Display channel authentication record details. CHLAUTH(MY.CHANNEL) TYPE(USERMAP)" ], [ "0ap", "DESCR( ) CUSTOM( ) ADDRESS(*) CLNTUSER(client_1) MCAUSER(user_1) USERSRC(MAP)" ], [ "0aq", "You want to delete the record and you try the following command which is based on the command that worked well for a simpler case." ], [ "0ar", "But this time, it fails:" ], [ "0as", "SET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('client_1') ACTION(REMOVE)" ], [ "0at", "AMQ8884: Channel authentication record not found." ], [ "0au", "You try the original command that created the record, but changing the action to REMOVE:" ], [ "0av", "SET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('client_1') USERSRC(MAP) MCAUSER('user_1') ADDRESS('*') ACTION(REMOVE)" ], [ "0aw", "AMQ8885: Parameter not allowed for this action on a channel authentication record." ], [ "0ax", "The attribute USERSRC is not a valid parameter for the REMOVE action (see table below)." ], [ "0ay", "Therefore, by removing this attribute, then the following command worked successfully to remove the record:" ], [ "0az", "SET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('mengano') ADDRESS('*') ACTION(REMOVE)" ], [ "0ba", "AMQ8877: WebSphere MQ channel authentication record set. See:" ], [ "0bb", "WebSphere MQ 8.0.0 > IBM MQ > Reference > Administration reference > MQSC reference > The MQSC commands >" ], [ "0bc", "SET CHLAUTH [http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ref.adm.doc/q086630_.htm] ." ], [ "0bd", "+ begin excerpt . Usage notes" ], [ "0be", "The following table shows which parameters are valid for each value of ACTION: . Action" ], [ "0bf", "Parameter ADD or REMOVE REMOVEALL REPLACE" ], [ "0bg", "CHLAUTH X X X" ], [ "0bh", "TYPE X X X" ], [ "0bi", "CMDSCOPE X X X" ], [ "0bj", "ACTION X X X" ], [ "0bk", "ADDRESS X X" ], [ "0bl", "ADDRLIST X X CHCKCLNT X" ], [ "0bm", "CLNTUSER X X MCAUSER X" ], [ "0bn", "QMNAME X X" ], [ "0bo", "SSLCERTI X X" ], [ "0bp", "SSLPEER X X" ], [ "0bq", "USERLIST X X USERSRC X WARN X DESCR X ." ], [ "0br", "+ end excerpt" ], [ "0bs", "Additional Search Words: uppercase lowercase upper lower case PRODUCT ALIAS/SYNONYM" ], [ "0bt", " WMQ MQ MQSeries" ] ]

[ "0ac", "0ad", "0af", "0ag" ]

[ "FastDoc Capture TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Why am I receiving error \"Studio: application error! Root element missing\" when trying to run FastDoc Capture? \n\nCAUSE\nThis error may be an indication that \\Datacap\\BatchExplorer\\BatchProfiles.xml is corrupt\n\nRESOLVING THE PROBLEM\nReplace the following file with a working copy of \\Datacap\\BatchExplorer\\BatchProfiles.xml", "Datacap Navigator Desktop TECHNOTE (FAQ)\n\nQUESTION\n Why using Datacap Navigator desktop fail to logon Datacap when service account was used for Datacap wTM? \n\nCAUSE\nThe root cause for the issue is related with service account settings.\nFollowing reasons may cause the request to wTM fail to response:\n1) Not using dckey to export/import the encryption key for service account.\n2) On IIS configuration, please ensure the application pool's identity is using\nservice account and load user profile is true.\n\n\nANSWER\nTherefore, please ensure you do the following for the service account setting of Datacap wTM. \n\n1) ensure the service account can access/write datacap installation folder; \n\n2) logon as service account to system, and run dcskey -e -i \n\n3) on IIS application pool for wTM, make sure the following settings are made correctly \n\n a) the identity is set to service account \n\n b) load user profile is set to true", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\n DIRECT LINK TO FIX\nIBM Datacap 9.0.1 Fix Pack 2 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FDatacap+Taskmaster+Capture&fixids=9.0.1.2-Datacap-WIN-FP002&source=SAR]\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * The PDFDocumentToImage action intermittently fails with an Out\n of Memory error, aborting the batch and causing all subsequent\n batches to fail until Rulerunner is restarted. In testing, I\n found that this could be replicated in Datacap Studio and\n appears to be a conflict with the ConvertGrayToBW action. When\n both commands exist in the task and the task is run repeatedly\n against multiple batches, the PDFDocumentToImage action will\n eventually start failing. Monitoring CPU memory shows that\n there is no increase in actual memory usage.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n * windows users *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * See Error Description *\n ****************************************************************\n * RECOMMENDATION: *\n * apply Datacap 9.0.1 FP 2 *\n ****************************************************************\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Updated Datacap.Libraries.Convert.dll - Fixed issue creating\n grayscale TIF from PDF using VeryPDF\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IO24703\n \n \n * REPORTED COMPONENT NAME\n DATACAP TASKMST\n \n \n * REPORTED COMPONENT ID\n 5725C1500\n \n \n * REPORTED RELEASE\n 900\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 2016-07-11\n \n \n * CLOSED DATE\n 2016-09-08\n \n \n * LAST MODIFIED DATE\n 2016-09-08\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 DATACAP TASKMST\n \n \n * FIXED COMPONENT ID\n 5725C1500\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R901 PSY\n UP", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The issue is seen when Rulerunner running the vscan task is processing a large number of documents, typically single page TIF files.\n\nThe documents are renamed with a \".tmp\" file extension during processing but then either the .tmp or .tif file required by Rulerunner can be \"locked\" at a time when access is required. If this error condition occurs, the batch will fail with an \"Error #:70 Decription: Permission denied\" file IO error in the Rulerunner logs.\n\n\nSYMPTOM\n \n\nThe batch never completes and one of the following errors is seen in the log files:\n\n11:05:54.540 File 'C:\\Datacap\\APT\\Images\\Input\\APT001.tif'\nis locked and will be ignored. Error #:70 Decription: Permission denied\n10:44:43.255 (0) t:1CE8 p:293F908 Failed to Move Temp file\n'\\\\server\\APT\\20160801\\APT001.tmp' to\n'\\\\server\\APT\\20160801\\APT.tif '. Error #:70 Decription: Permission denied An error like this is also seen in the Windows Event logs:\n\n[/support/docview.wss?uid=swg21988830&aid=1] [/support/docview.wss?uid=swg21988830&aid=1]\n\n\n\nCAUSE\nUnder load, the vscan task can end up in a hung state when it tries to perform standard file IO processes on a \"locked\" file. The issue is intermittent and can occur at any time since its occurrence relies on the specific timing of the file IO actions being carried out at the time.\n\n\nDIAGNOSING THE PROBLEM\nReview the Rulerunner logs from a batch where the issue is seen and search for text:\n\nError #:70 Decription \n\n(Note: the incorrect spelling of \"Description\" above is not a typographical error in this article but what is displayed in the log file. The text is a direct extraction from a log file where the problem occurred and therefore is the exact error syntax which will be seen in the logs.)\n\n\n\n\nRESOLVING THE PROBLEM\n \n\nUse mvscan actions instead of the vscan actions to create batches from large numbers of files stored on local disk like this.\n\nThe mvscan actions are much better suited to handling large numbers of files stored in the input folder and the associated IO file handling that is required to process them all through the batch. RELATED INFORMATION\n mvscan actions summary [https://www.ibm.com/support/knowledgecenter/SSZRWV_9.0.0/com.ibm.dc.develop.doc/dcadg811.htm]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Datacap Enterprise Content Management Datacap Taskmaster Capture", "Desktop; 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]" ]

[ [ "4a", "Desktop; No data; Scan; VScan TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "4b", " Receiving the following error message when attempting to launch up Scan task from Datacap Desktop:" ], [ "4c", "\"This batch has no data to process. Aborting.\"" ], [ "4d", "Then followed by this error:" ], [ "4e", "\"Unable to run queue.\"" ], [ "4f", "DIAGNOSING THE PROBLEM" ], [ "4g", "The panel for TravelDocs contained a value with all upper-case letter [eg." ], [ "4h", "TRAVELDOCS], which caused the error to occur when attempting to launch the Scan task from Datacap Desktop" ], [ "4i", "RESOLVING THE PROBLEM" ], [ "4j", "The \"Bind DCO type to panel\" for Datacap Desktop is case-sensitive." ], [ "4k", "Be sure the DCO name matches as it appears in Datacap Studio (both the spelling and case-sensitivity)." ], [ "4l", "Logon to TMWeb client." ], [ "4m", "Go to Administrator tab" ], [ "4n", "Select the VScan task from the Workflow." ], [ "4o", "Click Setup under Program." ], [ "4p", "Then change the value of the Panel to match what is in Datacap Studio." ], [ "4q", "For example \"TRAVELDOCS\" to \"TravelDocs\" Click Save [/support/docview.wss?uid=swg21967312&aid=1] [/support/docview.wss?uid=swg21967312&aid=1] [/support/docview.wss?uid=swg21967312&aid=2] [/support/docview.wss?uid=swg21967312&aid=2] [/support/docview.wss?uid=swg21967312&aid=3] [/support/docview.wss?uid=swg21967312&aid=3]" ] ]

[ "4b", "4c", "4d", "4e", "4j", "4p" ]

[ " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n WAS 8.5.5 may come with Java 1.6 enabled by default, depending on WAS version deployed. Sterling Order Management 9.4 is compiled against java 1.7. So when deploying the EAR a 'bad major version' or 'java major minor version mismatch' error may be thrown. \n\nSYMPTOM\nAt time of deployment a java.lang.UnsupportedClassVersionError error can be seen in installation logs.\n\n\nCAUSE\nFeatures of java 7 against which Sterling Order Management 9.4 is compiled against, may not be available on java 6.\n\nENVIRONMENT\nSterling Order management 9.4 deployment.\n\nDIAGNOSING THE PROBLEM\nDeployment fails with java.lang.UnsupportedClassVersionError.\n\nRESOLVING THE PROBLEM\nThere is a command in Websphere 8.5.x that allows selection of SDK, see links below. Use this to force WAS to use java 7\n\n\n\n\nList available sdk's with:\n./IBM/WebSphere/AppServer/bin/managesdk.sh\n-listAvailable\n\nChange WAS SDK with, for example:\n./IBM/WebSphere/AppServer/bin/managesdk.sh -enableProfile -profileName\nAppSrv01 -sdkname 1.7_64 -enableServers\n\n\n\nRELATED INFORMATION\n Manage WAS SDK [http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.iseries.doc/ae/rxml_managesdk.html]", "Websphere; startup; FileSystemPreferences; user prefs; prefs; Could not lock User prefs TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Warning message issued during the non-root or root startup of WebSphere stating that it can not lock the user or system preferences. \n\nSYMPTOM\nThe following message can be seen in the systemout.log: \n\n[9/11/11 18:03:19:921 EDT] 00000001 prefs W java.util.prefs.FileSystemPreferences syncWorld Couldn't flush user prefs: java.util.prefs.BackingStoreException: Couldn't get file lock.\n[9/11/11 18:03:49:929 EDT] 00000001 prefs W java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode Could not lock User prefs. Unix error code 2.\n\n\nCAUSE\nThe non-root ID that is being used to start WebSphere Application Server does not have a user_home directory. Therefore this non-root ID is unable to access the root user's \"/etc/.java/.systemPrefs\". This produces the aforementioned warning messages every 30 seconds in the profile_root/logs/server_name/systemout.log.\n\nThe root ID used to start Websphere Application Server can not find the Java system pref file. \n\n\nDIAGNOSING THE PROBLEM\nFor non-root, you can confirm this issue by trying to start WebSphere using the \"root\" ID. Review the Websphere_Home/profiles/<profile_name>/logs/<failing server_name/systemout.log to verify that you no longer see the warning messages. \n\n\nFor root, verify if the /etc/.java/.systemPrefs exists\n\n\nRESOLVING THE PROBLEM\nFor non-root : \n\nCreate a User_Home directory for this non-root user and restart WebSphere Application Server. If this does not resolve the issue use the following 2 suggestions below : \n\nNOTE : The \"dot\" in front of the directories below represent that these are \"hidden\" directories. So the \"dot\" must be in front of the directory name to go into the directory or to access them. \n\n1. Try giving 755 permission for /home/wasadmin/.java/.userPrefs \n\n2. Add \"-Djava.util.prefs.userRoot=/home/wasadmin/preps\" as a SDK generic jvm argument \n\n\nTo set the argument on the SDK: \n\n 1. In the administrative console, click Servers > Server Types > WebSphere application servers , and select the server that you want to add the generic argument to.. \n 2. Then, in the Server Infrastructure section, click Java and process management > Process definition > Java virtual machine. \n 3. Specify -Djava.util.prefs.userRoot=/home/wasadmin/preps for the Generic JVM Arguments property, and click OK . \n 4. Click Save to save your changes. \n 5. Restart the application server.\n\n\nFor root : 1. Create a Java system pref directory\n sudo mkdir -p /etc/.java/.systemPrefs \n 2. Restart the application server.", "DEL2INST No valid hosting environment TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Installation of Netcool Omnibus/Webgui fails with below error:\n\n<className>com.ibm.ac.si.cli.HostingEnvironmentException</className>\n<message>ACUCLI0001E No valid hosting environment was found for the target of the root IU.</message> \n\nSYMPTOM\nCheck the IA log and see if following error is present.\n\n \n2014-04-25 16:23:48.557-04:00 : FINE : processReq stdout: <?xml \nversion=\"1.0\" encoding=\"UTF-8\" ?> \n<output:processReqOutput schemaVersion=\"1.3\" implVersion=\"1.4.0.23\" xmlns:output=\"http://www.ibm.com/namespaces/autonomic/solutioninstall/d eProcessReqOutput\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" \nxsi:schemaLocation=\"http://www.ibm.com/namespaces/autonomic/solutioninst all/deProcessReqOutput deProcessReqOutput.xsd\"> \n<exceptions> \n<exception> \n<className>com.ibm.ac.si.cli.HostingEnvironmentException</className> \n<message>ACUCLI0001E No valid hosting environment was found for \nthe target of the root IU.</message> \n\n\n\nRESOLVING THE PROBLEM\nThis error can happen if you deleted the target installation directory and removed the Deployment Engine (DE) related files, but the DE related files were not completely removed.\n\n \nPlease follow steps in below technote to remove DE and the target installation dir. Also, please make sure you have enough free disk space in /tmp and the target installation directory. \nCAUTION: Removing DE related files as described in below technote will completely remove the DE repository. This procedure should only be used if you are installing a base product from scratch and there is no other product installed (under same user id) which shares this DE repository. If you are not sure then do not perform these steps. \n\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21679379 [http://www-01.ibm.com/support/docview.wss?uid=swg21679379] \n\nAfter above step try the install again. If it fails for any reason then please provide complete set of logs as described in below technote. \n\nhttps://www-304.ibm.com/support/docview.wss?uid=swg21500633 [https://www-304.ibm.com/support/docview.wss?uid=swg21500633]", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When creating a WebSphere Commerce instance, the following warning messages are displayed in the SystemErr.log:\n\nMar 22, 2006 2:11:35 PM java.util.prefs.FileSystemPreferences$3 run\nWARNING: Could not create system preferences directory. System preferences are unusable.\nMar 22, 2006 2:11:49 PM java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode\nWARNING: Could not lock System prefs. Unix error code 273859672.\nMar 22, 2006 2:12:19 PM java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode\nWARNING: Could not lock System prefs. Unix error code 268911000.\nMar 22, 2006 2:12:49 PM java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode\nWARNING: Could not lock System prefs. Unix error code 273676720. \n\nCAUSE\nThe warning messages are caused by SUN JDK Bug# 4666397: \n\nhttp://developer.java.sun.com/developer/bugParade/bugs/4666397.html [http://developer.java.sun.com/developer/bugParade/bugs/4666397.html]\n\n\nRESOLVING THE PROBLEM\nYou can safely ignore the warning messages. The creation of a WebSphere Commerce instance will not be affected by these warning messages.", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When running a DataStage job that uses the hierarchichal stage, the warning:\n\n\"<stageName>,0: Couldn't flush user prefs: java.util.prefs.BackingStoreException: Couldn't get file lock.\"\n\nis generated randomly in the log file. \n\nCAUSE\nJAVA_HOME environment variable is not set correctly.\n\nRESOLVING THE PROBLEM\nBe sure that the JAVA_HOME environment variable is set to the jdk directory of the Information Server install directory. For example:\nJAVA_HOME=/opt/IBM/InformationServer/jdk \n\nThe JAVA_HOME environment variable can be set in the $DSHOME/dsenv file for simplicity. Once this is set, restart the DataStage engine. \n\n \n\nIf this does not correct the issue, please see the following WebSphere document: \n\nhttp://www.ibm.com/support/docview.wss?uid=swg21515420 [http://www.ibm.com/support/docview.wss?uid=swg21515420]" ]

[ [ "1a", "Websphere; startup; FileSystemPreferences; user prefs; prefs; Could not lock User prefs TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "1b", " Warning message issued during the non-root or root startup of WebSphere stating that it can not lock the user or system preferences. SYMPTOM" ], [ "1c", "The following message can be seen in the systemout.log:" ], [ "1d", "[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." ], [ "1e", "[9/11/11 18:03:49:929 EDT] 00000001 prefs W java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode Could not lock User prefs." ], [ "1f", "Unix error code 2. CAUSE" ], [ "1g", "The non-root ID that is being used to start WebSphere Application Server does not have a user_home directory." ], [ "1h", "Therefore this non-root ID is unable to access the root user's \"/etc/.java/.systemPrefs\"." ], [ "1i", "This produces the aforementioned warning messages every 30 seconds in the profile_root/logs/server_name/systemout.log." ], [ "1j", "The root ID used to start Websphere Application Server can not find the Java system pref file." ], [ "1k", "DIAGNOSING THE PROBLEM" ], [ "1l", "For non-root, you can confirm this issue by trying to start WebSphere using the \"root\" ID." ], [ "1m", "Review the Websphere_Home/profiles/<profile_name>/logs/<failing server_name/systemout.log to verify that you no longer see the warning messages." ], [ "1n", "For root, verify if the /etc/.java/.systemPrefs exists" ], [ "1o", "RESOLVING THE PROBLEM" ], [ "1p", "For non-root :" ], [ "1q", "Create a User_Home directory for this non-root user and restart WebSphere Application Server." ], [ "1r", "If this does not resolve the issue use the following 2 suggestions below :" ], [ "1s", "NOTE : The \"dot\" in front of the directories below represent that these are \"hidden\" directories." ], [ "1t", "So the \"dot\" must be in front of the directory name to go into the directory or to access them. 1." ], [ "1u", "Try giving 755 permission for /home/wasadmin/.java/.userPrefs 2." ], [ "1v", "Add \"-Djava.util.prefs.userRoot=/home/wasadmin/preps\" as a SDK generic jvm argument" ], [ "1w", "To set the argument on the SDK: 1." ], [ "1x", "In the administrative console, click Servers > Server Types > WebSphere application servers , and select the server that you want to add the generic argument to.. 2." ], [ "1y", "Then, in the Server Infrastructure section, click Java and process management > Process definition > Java virtual machine. 3." ], [ "1z", "Specify -Djava.util.prefs.userRoot=/home/wasadmin/preps for the Generic JVM Arguments property, and click OK . 4." ], [ "1aa", "Click Save to save your changes. 5." ], [ "1ab", "Restart the application server." ], [ "1ac", "For root : 1." ], [ "1ad", "Create a Java system pref directory" ], [ "1ae", " sudo mkdir -p /etc/.java/.systemPrefs 2." ], [ "1af", "Restart the application server." ] ]

[ "1c", "1d", "1e", "1f", "1g", "1h", "1i", "1j", "1l", "1m", "1n", "1p", "1q", "1r", "1s", "1u", "1v", "1x", "1y", "1z", "1aa", "1ad", "1ae", "1af", "3f", "3g", "3h" ]

[ " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n WAS 8.5.5 may come with Java 1.6 enabled by default, depending on WAS version deployed. Sterling Order Management 9.4 is compiled against java 1.7. So when deploying the EAR a 'bad major version' or 'java major minor version mismatch' error may be thrown. \n\nSYMPTOM\nAt time of deployment a java.lang.UnsupportedClassVersionError error can be seen in installation logs.\n\n\nCAUSE\nFeatures of java 7 against which Sterling Order Management 9.4 is compiled against, may not be available on java 6.\n\nENVIRONMENT\nSterling Order management 9.4 deployment.\n\nDIAGNOSING THE PROBLEM\nDeployment fails with java.lang.UnsupportedClassVersionError.\n\nRESOLVING THE PROBLEM\nThere is a command in Websphere 8.5.x that allows selection of SDK, see links below. Use this to force WAS to use java 7\n\n\n\n\nList available sdk's with:\n./IBM/WebSphere/AppServer/bin/managesdk.sh\n-listAvailable\n\nChange WAS SDK with, for example:\n./IBM/WebSphere/AppServer/bin/managesdk.sh -enableProfile -profileName\nAppSrv01 -sdkname 1.7_64 -enableServers\n\n\n\nRELATED INFORMATION\n Manage WAS SDK [http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.iseries.doc/ae/rxml_managesdk.html]", "Websphere; startup; FileSystemPreferences; user prefs; prefs; Could not lock User prefs TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Warning message issued during the non-root or root startup of WebSphere stating that it can not lock the user or system preferences. \n\nSYMPTOM\nThe following message can be seen in the systemout.log: \n\n[9/11/11 18:03:19:921 EDT] 00000001 prefs W java.util.prefs.FileSystemPreferences syncWorld Couldn't flush user prefs: java.util.prefs.BackingStoreException: Couldn't get file lock.\n[9/11/11 18:03:49:929 EDT] 00000001 prefs W java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode Could not lock User prefs. Unix error code 2.\n\n\nCAUSE\nThe non-root ID that is being used to start WebSphere Application Server does not have a user_home directory. Therefore this non-root ID is unable to access the root user's \"/etc/.java/.systemPrefs\". This produces the aforementioned warning messages every 30 seconds in the profile_root/logs/server_name/systemout.log.\n\nThe root ID used to start Websphere Application Server can not find the Java system pref file. \n\n\nDIAGNOSING THE PROBLEM\nFor non-root, you can confirm this issue by trying to start WebSphere using the \"root\" ID. Review the Websphere_Home/profiles/<profile_name>/logs/<failing server_name/systemout.log to verify that you no longer see the warning messages. \n\n\nFor root, verify if the /etc/.java/.systemPrefs exists\n\n\nRESOLVING THE PROBLEM\nFor non-root : \n\nCreate a User_Home directory for this non-root user and restart WebSphere Application Server. If this does not resolve the issue use the following 2 suggestions below : \n\nNOTE : The \"dot\" in front of the directories below represent that these are \"hidden\" directories. So the \"dot\" must be in front of the directory name to go into the directory or to access them. \n\n1. Try giving 755 permission for /home/wasadmin/.java/.userPrefs \n\n2. Add \"-Djava.util.prefs.userRoot=/home/wasadmin/preps\" as a SDK generic jvm argument \n\n\nTo set the argument on the SDK: \n\n 1. In the administrative console, click Servers > Server Types > WebSphere application servers , and select the server that you want to add the generic argument to.. \n 2. Then, in the Server Infrastructure section, click Java and process management > Process definition > Java virtual machine. \n 3. Specify -Djava.util.prefs.userRoot=/home/wasadmin/preps for the Generic JVM Arguments property, and click OK . \n 4. Click Save to save your changes. \n 5. Restart the application server.\n\n\nFor root : 1. Create a Java system pref directory\n sudo mkdir -p /etc/.java/.systemPrefs \n 2. Restart the application server.", "DEL2INST No valid hosting environment TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Installation of Netcool Omnibus/Webgui fails with below error:\n\n<className>com.ibm.ac.si.cli.HostingEnvironmentException</className>\n<message>ACUCLI0001E No valid hosting environment was found for the target of the root IU.</message> \n\nSYMPTOM\nCheck the IA log and see if following error is present.\n\n \n2014-04-25 16:23:48.557-04:00 : FINE : processReq stdout: <?xml \nversion=\"1.0\" encoding=\"UTF-8\" ?> \n<output:processReqOutput schemaVersion=\"1.3\" implVersion=\"1.4.0.23\" xmlns:output=\"http://www.ibm.com/namespaces/autonomic/solutioninstall/d eProcessReqOutput\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" \nxsi:schemaLocation=\"http://www.ibm.com/namespaces/autonomic/solutioninst all/deProcessReqOutput deProcessReqOutput.xsd\"> \n<exceptions> \n<exception> \n<className>com.ibm.ac.si.cli.HostingEnvironmentException</className> \n<message>ACUCLI0001E No valid hosting environment was found for \nthe target of the root IU.</message> \n\n\n\nRESOLVING THE PROBLEM\nThis error can happen if you deleted the target installation directory and removed the Deployment Engine (DE) related files, but the DE related files were not completely removed.\n\n \nPlease follow steps in below technote to remove DE and the target installation dir. Also, please make sure you have enough free disk space in /tmp and the target installation directory. \nCAUTION: Removing DE related files as described in below technote will completely remove the DE repository. This procedure should only be used if you are installing a base product from scratch and there is no other product installed (under same user id) which shares this DE repository. If you are not sure then do not perform these steps. \n\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21679379 [http://www-01.ibm.com/support/docview.wss?uid=swg21679379] \n\nAfter above step try the install again. If it fails for any reason then please provide complete set of logs as described in below technote. \n\nhttps://www-304.ibm.com/support/docview.wss?uid=swg21500633 [https://www-304.ibm.com/support/docview.wss?uid=swg21500633]", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When creating a WebSphere Commerce instance, the following warning messages are displayed in the SystemErr.log:\n\nMar 22, 2006 2:11:35 PM java.util.prefs.FileSystemPreferences$3 run\nWARNING: Could not create system preferences directory. System preferences are unusable.\nMar 22, 2006 2:11:49 PM java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode\nWARNING: Could not lock System prefs. Unix error code 273859672.\nMar 22, 2006 2:12:19 PM java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode\nWARNING: Could not lock System prefs. Unix error code 268911000.\nMar 22, 2006 2:12:49 PM java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode\nWARNING: Could not lock System prefs. Unix error code 273676720. \n\nCAUSE\nThe warning messages are caused by SUN JDK Bug# 4666397: \n\nhttp://developer.java.sun.com/developer/bugParade/bugs/4666397.html [http://developer.java.sun.com/developer/bugParade/bugs/4666397.html]\n\n\nRESOLVING THE PROBLEM\nYou can safely ignore the warning messages. The creation of a WebSphere Commerce instance will not be affected by these warning messages.", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When running a DataStage job that uses the hierarchichal stage, the warning:\n\n\"<stageName>,0: Couldn't flush user prefs: java.util.prefs.BackingStoreException: Couldn't get file lock.\"\n\nis generated randomly in the log file. \n\nCAUSE\nJAVA_HOME environment variable is not set correctly.\n\nRESOLVING THE PROBLEM\nBe sure that the JAVA_HOME environment variable is set to the jdk directory of the Information Server install directory. For example:\nJAVA_HOME=/opt/IBM/InformationServer/jdk \n\nThe JAVA_HOME environment variable can be set in the $DSHOME/dsenv file for simplicity. Once this is set, restart the DataStage engine. \n\n \n\nIf this does not correct the issue, please see the following WebSphere document: \n\nhttp://www.ibm.com/support/docview.wss?uid=swg21515420 [http://www.ibm.com/support/docview.wss?uid=swg21515420]" ]

[ [ "3a", " TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "3b", " When creating a WebSphere Commerce instance, the following warning messages are displayed in the SystemErr.log:" ], [ "3c", "Mar 22, 2006 2:11:35 PM java.util.prefs.FileSystemPreferences$3 run" ], [ "3d", "WARNING: Could not create system preferences directory." ], [ "3e", "System preferences are unusable." ], [ "3f", "Mar 22, 2006 2:11:49 PM java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode" ], [ "3g", "WARNING: Could not lock System prefs." ], [ "3h", "Unix error code 273859672." ], [ "3i", "Mar 22, 2006 2:12:19 PM java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode" ], [ "3j", "WARNING: Could not lock System prefs." ], [ "3k", "Unix error code 268911000." ], [ "3l", "Mar 22, 2006 2:12:49 PM java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode" ], [ "3m", "WARNING: Could not lock System prefs." ], [ "3n", "Unix error code 273676720. CAUSE" ], [ "3o", "The warning messages are caused by SUN JDK Bug# 4666397: http://developer.java.sun.com/developer/bugParade/bugs/4666397.html [http://developer.java.sun.com/developer/bugParade/bugs/4666397.html]" ], [ "3p", "RESOLVING THE PROBLEM" ], [ "3q", "You can safely ignore the warning messages." ], [ "3r", "The creation of a WebSphere Commerce instance will not be affected by these warning messages." ] ]

[ "1c", "1d", "1e", "1f", "1g", "1h", "1i", "1j", "1l", "1m", "1n", "1p", "1q", "1r", "1s", "1u", "1v", "1x", "1y", "1z", "1aa", "1ad", "1ae", "1af", "3f", "3g", "3h" ]

[ "vmm; administration; wpsadmin; wpsadmins; mutliple; LDAP; database; repository; federated TECHNOTE (FAQ)\n\nQUESTION\n IBM WebSphere Portal has been configured to use the federated repositories configuration with multiple user repositories (for example, multiple LDAP servers). One repository contains the primary Portal administrative user and the primary Portal administative group. You would like to add additional Portal administrative users from the second repository. This document will detail how to configure the Portal to allow administators to exist in multiple repositories. \n\nANSWER\nWebSphere Portal has a default configuration which allows a single superuser administrator for the system (e.g. wpsadmin) and a single administrator group for the system (e.g. wpsadmins). There are two configuration options which can allow multiple Portal administrators in this scenario: \n\nOption #1: Manually duplicate Portal permissions\nAdvantage: Quickest option to implement\nDisadvantage: Most difficult to maintain. New permission assignments must be manually duplicated\n\n\nOption #2: Utilize application groups \nAdvantage: Greatest flexibility, scalability, and robustness\nDisadvantage: Most time-consuming initial configuration \n\n\n\n\nOption #1: Manually duplicate Portal permissions \n\nLet's suppose we have the following group from LDAP server A as our Portal administrators group: \n\ncn=wpsadminsA,ou=groups,dc=websphere,dc=com \n\n \n\nWe are looking to add a second LDAP group to the Portal server configuration from LDAP server B: \n\ncn=wpsadminsB,ou=groups,dc=lotus,dc=com \n\n \n\nThe following steps will allow the second LDAP group to administer most of the Portal: \n\n1) Login to the Portal server as an administrator from LDAP serverA \n\n2) Navigate to the Administration Area, and click on the Users and Groups link. \n\n3) In the Manage Users and Groups portlet, search for the second group you wish to make an administration group, e.g. wpsadminsB. \n\n4) Click on the third icon for \"Duplicate Role Assignments\"\n[/support/docview.wss?uid=swg21599046&aid=1] [/support/docview.wss?uid=swg21599046&aid=1]\n\n5) Search for the wpsadminsA group group. Select it, and click OK.\n6) The second group in LDAP server B now will now be able to administer the Portal server.\n\nThe following steps are required if you have Web Content Management (WCM) installed with your Portal server. If you do not have WCM installed, skip the following steps:\n\n7) Still in the Administration Area, click on the \"Web Content Libraries\" \n8) Click the button for \"Set Access on Root\"\n[/support/docview.wss?uid=swg21599046&aid=2] [/support/docview.wss?uid=swg21599046&aid=2]\n\n9) Click \"Edit Role\" for the \"Administrator\" Role.\n10) Verify the \"wpsadminsB\" group appears at this screen.\n\n[/support/docview.wss?uid=swg21599046&amp;aid=3].\n\n\nNote: The \"Duplicate Role Assignments\" operation only duplicates the permissions at the time the icon is clicked. It will not automatically duplicate new role assignments from the first administration group to the second administration group. Therefore, If you manually assign the wpsadminsA group to a page, portlet, etc., you will also need to manually assign the wpsadminsB group as well with the same permissions, OR, click the \"Duplicate Role Assignments\" icon once more to ensure the wpsadminsB group matches the wpsadminsA group permissions.\n\n\nOption #2: Utilize application groups\nPer the Portal Infocenter [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Enabling_application_groups_wp7]:\n\"Application groups is a concept that allows you to define user groups within the database user registry with members (users or groups) contained in the federated LDAP user registry you configured. The benefit of application groups is that you can create Groups that are only used in IBM® WebSphere® Portal.\"\n\n\nIn this specific case, we will create a new application group: \n\ncn=wpsadminsDB,o=dbrepo\n\n\nAnd add the two LDAP groups as members of the application group: \n\ncn=wpsadminsA,ou=groups,dc=websphere,dc=com \n\ncn=wpsadminsB,ou=groups,dc=lotus,dc=com \n\n \n\nAnd configure Portal to use the application group (cn=wpsadminsDB,o=repo) as the administrators group in its configuration. As a result, any users who are members of the wpsadminsA group from LDAP server #1, or, any users who are members of the wpsadminsB group from LDAP server #2 will now be Portal administrators. \n\n \n\nThe primary administrator we will assume to remain in LDAP server A, e.g. uid=wpsadminA,ou=users,dc=websphere,dc=com \n\n \n\nTo setup application groups in this configuration: \n\n1) Create a new database [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Linux_Adding_a_database_user_registry_wp7] to store the application groups per step #2 in the Portal Infocenter. \n\n2) Run the configuration task wp-create-db [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Linux_Adding_a_database_user_registry_wp7] to configure Portal to use the database per step #8 in the Portal Infocenter. Restart the servers after running this configuration task. \n\n3) Update the location where new users and new groups are created to be the database by running the configuration task wp-set-entitytypes [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Linux_Adding_a_database_user_registry_wp7] per step #10 in the Portal Infocenter. Restart the servers after running this configuration task. \n\n4) Run the configuration task wp-update-group-repository-relationship [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Enabling_application_groups_wp7] to allow users from LDAP server A to be added as members in the application groups per step #1 in the Portal Infocenter. Restart the servers after running this configuration task. \n\n5) Run the configuration task wp-update-group-repository-relationship [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Enabling_application_groups_wp7] to allow users from LDAP server B to be added as members in the application groups per step #1 in the Portal Infocenter. Restart the servers after running this configuration task. \n\n6) Using the WebSphere Portal Manage Users & Groups portlet, create a new group named \"wpsadminsDB\". \n\n7) Using the WebSphere Portal Manage Users & Groups portlet, add the \"wpsadminsA\" group from LDAP server A to the wpsadminsDB group. \n\n8) Using the WebSphere Portal Manage Users & Groups portlet, add the \"wpsadminsB\" group from LDAP server B to the wpsadminsDB group. \n\n9) Run the configuration task wp-change-portal-admin-user [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Replacing_the_WebSphere_Portal_administrator_user_ID_wp7] per step #2 in the Portal Infocenter with the following conditions:\n-DnewAdminId=uid=wpsadminA,ou=users,dc=websphere,dc=com\n-DnewAdminGroupId=cn=wpsadminsDB,o=dbrepo\n\n\nRestart the servers after running this configuration task.\n\nNote: This step is updating only the administrator group to be the newly created application group. We do not wish to change the primary Portal administrator at this time, however, the configuration task requires the -DnewAdminId parameter be specified. Therefore, specify the -DnewAdminId parameter to be the fullDN of the current Portal administrator in LDAP server A.\n\n10) Verify users in the wpsadminsA group in LDAP server A and wpsadminsB in LDAP server B are able to login to the Portal and access the Administration area successfully.\n\n11) Optional: Create a new user in the database to be the primary Portal administrator. \ni. Verify steps #1-#10 complete successfully, otherwise, the Portal may not start executing this optional step.\nii. Using the WebSphere Portal Manage Users & Groups portlet, create a new user named \"wpsadminDB\".\niii. Run the configuration task wp-change-portal-admin-user [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Replacing_the_WebSphere_Portal_administrator_user_ID_wp7] per step #2 in the Portal Infocenter with the following conditions:\n-DnewAdminId=uid=wpsadminDB,o=dbrepo\n-DnewAdminGroupId=cn=wpsadminsDB,o=dbrepo\n\niv. Restart the servers. \n\nNote: This option requires the most time up-front for configuration, but also offers the greatest flexibility for Portal administrators spread across multiple user repositories. In our example of multiple LDAP servers, each LDAP server can independently maintain their respective wpsadmins group, adding / removing LDAP users to each group as needed. If optional step #11 was executed, should LDAP server A become unavailable, the Portal server would remain operable with the primary administrative user stored in a database, rather than LDAP server A. \n\n\n\n\nRELATED INFORMATION\n Adding a database user registry [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Linux_Adding_a_database_user_registry_wp7]\nEnabling application groups [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Enabling_application_groups_wp7]\nChanging the Portal admin ID or admin group ID [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Replacing_the_WebSphere_Portal_administrator_user_ID_wp7]\n\n\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", "Mobile Portlets are not displayed on the page; when a portlet project is deployed from the Rational SDP (RAD/RSA) workspace using ‘Run on Server’ Option. TECHNOTE (FAQ)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n English \n\nQUESTION\n Mobile Portlets are not displayed on the page, when a portlet project is deployed from the Rational SDP (RAD/RSA) workspace using ‘Run on Server’ Option.\n\n\nCAUSE\nIn general when a portlet is deployed from the RSA/RAD workspace, the portlet application gets deployed to the portal server and the portlet is added to a page under \"Rational Portlets\". The particular page inherits the Style Theme from the Node 'Context Root'. \nIn the Portal 6.1.5, the default theme set to the content root is \"Tab Menu - Page Builder\" which is being inherited by \"Rational Portlets\". But for Mobile portlets to be rendered, the theme of the Rational Portlets page should be ‘Portal’ theme.\n\n\nANSWER\nAfter deploying a mobile portlet project from Rational SDP Workspace, accessing the Mobile Portal Site using Firefox Useragent switcher or any simulator doesn’t render the mobile portlets deployed. \n\n\nAny one of the following two methods can be used to resolve this problem.\n\nMETHOD-1: After the WebSphere Portal 6.1.5 installation is performed for the pre-requisite softwares for MPTK.\n1. Start the Portal Server\n2. Login to the Portal Administration console using portal Admin access.\n3. Go to administration menu; select the ‘Manage Pages’. \n4. Select the ‘Context Root’ node and Navigate to the node which represents the ‘Home’ page.\n5. Click the Edit properties of the page and set the theme of the ‘Home’ Node to \"Portal\".\n\nMETHOD-2: After installing the MPTK on WebSphere Portal 6.1.5\n1. Start the Portal Server\n2. Login to the Portal Administration console using portal Admin access\n3. Go to administration menu; select the ‘Mobile Manage Pages’. \n4. Select the ‘Context Root’ and Navigate to the node which represents the ‘Home’ page.\n5. Click the Edit properties of the page and set the theme of the ‘Home’ Node to \"Portal\".\n\n[/support/docview.wss?uid=swg21424383&amp;aid=1]", " FIXES ARE AVAILABLE\n6.1.0.1 Download: WebSphere Portal and Web Content Management V6.1, fix pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24020387]\n6.1.0.2 Download: WebSphere Portal and Web Content Management V6.1, fix pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24022898]\n6.1.0.3 Download: WebSphere Portal and WCM V6.1 fix pack 3, 6.1.5 feature pack [http://www-01.ibm.com/support/docview.wss?uid=swg24025054]\n6.1.0.4 Download: WebSphere Portal and WCM V6.1.0 fix pack 4 & 6.1.5 fix pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24026394]\n6.1.0.5 Download: WebSphere Portal and WCM V6.1.0 fix pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24027475]\n6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24030970]\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * In some instances, restarting a Websphere Content Manager\n (WCM) workflow may result in an exception. The stack trace will\n be similar to:\n Restart workflow fails with IWKMU1062X: Message: Could not save\n object in repository., Cause: javax.jcr.ItemNotFoundException\n 7/8/08 17:22:27:886 CD 00000109 WorkflowServi W IWKMU1062X:\n Message: Could not save object in repository., Cause:\n javax.jcr.ItemNotFoundException: A node does not exist with\n UUID: <id here> 7/8/08 17:22:27:938 CDT 00000109 CommandUtils W\n <Null Message>\n com.ibm.workplace.wcm.services.repository.RepositoryException:\n IWKMU1062X: Message: Instance of workspace ROOTWORKSPACE has\n been marked invalid and should be discarded., Cause:\n com.ibm.icm.jcr.InvalidWorkspaceException: Instance of\n workspace ROOTWORKSPACE has been marked invalid and should be\n discarded. at\n com.ibm.workplace.wcm.services.workflow.WorkflowServiceImpl.upda\n tePublis hedToDraft(WorkflowServiceImpl.java:2029) at\n com.ibm.workplace.wcm.services.workflow.WorkflowServiceImpl.inte\n rnalUpdate(WorkflowServiceImpl.java:1949)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * RESTART WORKFLOW FAILS WITH IWKMU1062X: MESSAGE: COULD NOT SAVE\n OBJECT IN REPOSITORY., CAUSE: JAVAX.JCR.ITEMNOTFOUNDEXCEPTION\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Cause was a JCR version was removed by some non-wcm process,\n causing the lookup for the version to fail. When the lookup\n failed, workspace marked invalid. This APAR re-retrieves a new\n workspace to continue\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PK69777\n \n \n * REPORTED COMPONENT NAME\n LOTUS WEB CONT\n \n \n * REPORTED COMPONENT ID\n 5724I2900\n \n \n * REPORTED RELEASE\n 60F\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 2008-07-29\n \n \n * CLOSED DATE\n 2008-07-30\n \n \n * LAST MODIFIED DATE\n 2008-08-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 LOTUS WEB CONT\n \n \n * FIXED COMPONENT ID\n 5724I2900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R60F PSY\n UP", "hidden; wcm; web content management; base; full; virtual portal; vp; InitAdminVirtualPortal.xml; InitVirtualContentPortal.xm; Edit Shared Setting; Web Content Viewer; jsr 286; Edit; loop; library; content; VirtualPortal.zip TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nIn Portal 7.0.0.1, when configuring the content that a page should show (via Web Content Viewer portlet), after clicking on \"Edit\" the pop-up window that appears is the same \"Edit Shared Setting\" of the Web Content Viewer portlet, instead of the correct \"Select Content Item\" window that allows user to select library content .\n\nSYMPTOM\n The \"Edit Shared Setting\" appears to go into a loop.\n[/support/docview.wss?uid=swg21495688&aid=1] [/support/docview.wss?uid=swg21495688&aid=1]\n\n\nCAUSE\nThe hidden page \"Web Content Management\" is missing in the virtual portal. \n\n This issue only occurs in a \"Base\" installation. It does not occur in a \"Full\" installation. \n\n The hidden page \"Web Content Management\" only exists in the \"InitVirtualContentPortal.xml\" initialization script, which in turn only exists in the VirtualPortal.zip of a \"Full\" installation. \n\n (The default initialization script in a \"Base\" installation is \"InitAdminVirtualPortal.xml\".)\n\n\nENVIRONMENT\nIBM WebSphere Portal 7.0.0.1 - \"Base\" installation\n\n\n\nDIAGNOSING THE PROBLEM\nFrom the Portal UI of the base Portal, go to \"Manage Pages\", under \"Content Root\", click on the \"Hidden Pages\" link, you should be able to find the hidden page \"Web Content Management\" (its default unique name is \"com.ibm.wps.hiddenpage.wcm.Authoring_Portlet\"). \n\n\n[/support/docview.wss?uid=swg21495688&aid=2] [/support/docview.wss?uid=swg21495688&aid=2]\n\nIn the problematic virtual portal, this hidden page is missing.\n\n\nRESOLVING THE PROBLEM\nExport the hidden page \"Web Content Management\" from the base Portal and and import it into the problematic virtual portal. \n\n\n1) From the Portal UI - Manage Pages, navigate to the hidden page \"Web Content Management\".\n\n2) Click on the icon on the right hand side to do a page export. \n\n3) Select to export the page hierarchy and save the file to a temp directory. \n\n4) Log in to the problematic virtual portal. Go to Portal Settings >> Import XML and import the page created in step 3 to this virtual portal.\n\n(No restart is required.)", "RT0002E; JDBC; database; driver; RepositoryException; PLS; EJPAS0017E TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nYou attempt to create a new page via the Manage Pages portlet or add a portlet to a page via the Edit Layout portlet and encounter an error.\n\nSYMPTOM\nSystemOut.log contains:\n... DefaultTransa E Message: Could not save object in repository., \nCause: javax.jcr.RepositoryException: RT0002E: Error while calling a function createItems of PLS data manager\ncom.ibm.workplace.wcm.services.repository.RepositoryException: \nMessage: Could not save object in repository., Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a function createItems of PLS data manager\n...\nCaused by: com.ibm.icm.da.DBAccessException:\njava.sql.SQLFeatureNotSupportedException:DSRA1300E: Feature is not implemented: PreparedStatement.setBinaryStream\nat com.ibm.icm.da.portable.data.WideTableData.changeItems(WideTableData.java:857) \n\n \n\nThe client browser displays: \n\n\nEJPAS0017E ... Message: Could not save object in repository.,\nCause: javax.jcr.RepositoryException: RT0002E: Error while calling a\nfunction createItems of PLS data ...\n\nor:\n\nEJPAE0015E: Failed to add new portlets.\n...\nEJPEC0002E: The transaction has been set to rollback state...\n\n\nCAUSE\nThe JDBC driver does not meet WebSphere Portal v8's prerequisites.\n\n\nDIAGNOSING THE PROBLEM\nCheck SystemOut.log for the database server version and JDBC driver version: \n\n\nDSRA8204I: Database product version : ...\nInternalGener I DSRA8205I: JDBC driver name : ...\nInternalGener I DSRA8206I: JDBC driver version : ...\n\nCompare these to WebSphere Portal v8's prerequisites. Refer to the WebSphere Portal V8.0 detailed system requirements link below.\n\n\nRESOLVING THE PROBLEM\nIf the database server and/or JDBC driver do not meet WebSphere Portal v8's prerequisites, upgrade or downgrade the component(s) to the appropriate supported level(s) and restart the Portal server(s). \n\n \n\nIf upgrading the JDBC driver requires replacing the .jar with another differently named .jar, other components in the system that referenced the older .jar may be affected. Pay special consideration to: \n\n\nWAS Integrated Solutions Console > Environment > WebSphere Variables\nVMM_JDBC_CLASSPATH\nORACLE_JDBC_DRIVER_PATH\n\nThese are stored in: <profile>/config/cells/<cell name>/variables.xml\n\nOther WebSphere variables may also reference the older .jar, or these same variables may be set in different scopes, so check other variables and variables.xml files as well, such as: <profile>/config/cells/<cell name>/nodes/<node name>/variables.xml\n\nRELATED INFORMATION\n WebSphere Portal V8.0 detailed system requirements [http://www-01.ibm.com/support/docview.wss?uid=swg27007791]" ]

[ [ "4a", "RT0002E; JDBC; database; driver; RepositoryException; PLS; EJPAS0017E TECHNOTE (TROUBLESHOOTING) PROBLEM" ], [ "4b", "You attempt to create a new page via the Manage Pages portlet or add a portlet to a page via the Edit Layout portlet and encounter an error. SYMPTOM SystemOut.log contains:" ], [ "4c", "... DefaultTransa E Message: Could not save object in repository.," ], [ "4d", "Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a function createItems of PLS data manager com.ibm.workplace.wcm.services.repository.RepositoryException:" ], [ "4e", "Message: Could not save object in repository., Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a function createItems of PLS data manager ..." ], [ "4f", "Caused by: com.ibm.icm.da.DBAccessException:" ], [ "4g", "java.sql.SQLFeatureNotSupportedException:DSRA1300E: Feature is not implemented: PreparedStatement.setBinaryStream at com.ibm.icm.da.portable.data.WideTableData.changeItems(WideTableData.java:857)" ], [ "4h", "The client browser displays: EJPAS0017E ..." ], [ "4i", "Message: Could not save object in repository.," ], [ "4j", "Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a" ], [ "4k", "function createItems of PLS data ... or:" ], [ "4l", "EJPAE0015E: Failed to add new portlets. ..." ], [ "4m", "EJPEC0002E: The transaction has been set to rollback state... CAUSE" ], [ "4n", "The JDBC driver does not meet WebSphere Portal v8's prerequisites." ], [ "4o", "DIAGNOSING THE PROBLEM" ], [ "4p", "Check SystemOut.log for the database server version and JDBC driver version:" ], [ "4q", "DSRA8204I: Database product version : ..." ], [ "4r", "InternalGener I DSRA8205I: JDBC driver name : ..." ], [ "4s", "InternalGener I DSRA8206I: JDBC driver version : ..." ], [ "4t", "Compare these to WebSphere Portal v8's prerequisites." ], [ "4u", "Refer to the WebSphere Portal V8.0 detailed system requirements link below." ], [ "4v", "RESOLVING THE PROBLEM" ], [ "4w", "If the database server and/or JDBC driver do not meet WebSphere Portal v8's prerequisites, upgrade or downgrade the component(s) to the appropriate supported level(s) and restart the Portal server(s)." ], [ "4x", "If upgrading the JDBC driver requires replacing the .jar with another differently named .jar, other components in the system that referenced the older .jar may be affected." ], [ "4y", "Pay special consideration to:" ], [ "4z", "WAS Integrated Solutions Console > Environment > WebSphere Variables VMM_JDBC_CLASSPATH ORACLE_JDBC_DRIVER_PATH" ], [ "4aa", "These are stored in: <profile>/config/cells/<cell name>/variables.xml" ], [ "4ab", "Other WebSphere variables may also reference the older .jar, or these same variables may be set in different scopes, so check other variables and variables.xml files as well, such as: <profile>/config/cells/<cell name>/nodes/<node name>/variables.xml RELATED INFORMATION" ], [ "4ac", " WebSphere Portal V8.0 detailed system requirements [http://www-01.ibm.com/support/docview.wss?uid=swg27007791]" ] ]

[ "4b", "4c", "4d", "4f", "4n", "4o", "4p", "4q", "4r", "4s", "4t", "4u", "4v", "4w", "4x", "4y", "4z", "4aa", "4ab" ]

[ " SECURITY BULLETIN\n\nSUMMARY\n Vulnerability in Apache commons-fileupload affects IBM Algo One Algo Risk Application (ARA) \nCVE-2016-1000031 \n\nVULNERABILITY DETAILS\n\nCVEID: CVE-2016-1000031 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031]\nDESCRIPTION: Apache Commons FileUpload, as used in Novell NetIQ Sentinel and other 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\nIBM Algo One Algo Risk Application (ARA) v5.1, 5.0\n\nREMEDIATION/FIXES\n \n\nProduct Name iFix Name Remediation/First Fix IBM Algo One - ARA 5.1.0.3-2 Fix Central Download [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~Information+Management&product=ibm/Information+Management/Algo+One&release=All&platform=All&function=fixId&fixids=5.1.0.3-2-Algo-One-ARA-if0346:0&includeSupersedes=0&source=fc&login=true] IBM Algo One - ARA 5.0.0.6-23 Fix Central Download [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~Information+Management&product=ibm/Information+Management/Algo+One&release=All&platform=All&function=fixId&fixids=5.0.0.6-23-Algo-One-ARA-if0400:0&includeSupersedes=0&source=fc&login=true] 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\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.", " SECURITY BULLETIN\n\nSUMMARY\n A security vulnerability exists in the open source library Apache Commons FileUpload that is shipped with and used by IBM WebSphere Lombardi Edition. \n\nVULNERABILITY DETAILS\nBy sending a specially crafted request, an attacker might exploit this vulnerability to cause the application to enter into an infinite loop.\nCVE-2014-0050 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0050] \nCVSS Base Score: 5.0\nCVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/90987 [https://exchange.xforce.ibmcloud.com/vulnerabilities/90987] \nCVSS Environmental Score*: Undefined \nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)\n\nAFFECTED PRODUCTS AND VERSIONS\nWebSphere Lombardi Edition 7.1.0, 7.2.0\n\nREMEDIATION/FIXES\nInstall APAR IC99466 [http://www-933.ibm.com/support/fixcentral/swg/quickorder?product=ibm/WebSphere/WebSphere+Lombardi+Edition&release=All&platform=All&function=aparId&apars=IC99466&source=fc] as appropriate for your current version of IBM WebSphere Lombardi Edition.\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] \nApache Commons FileUpload change report [http://commons.apache.org/proper/commons-fileupload/changes-report.html#a1.3.1] \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.", " SECURITY BULLETIN\n\nSUMMARY\n Jazz for Service Management (JazzSM) is affected by an Apache Commons FileUpload vulnerability. JazzSM has addressed this vulnerability \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-1000031 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031]\nDESCRIPTION: JazzSM could allow a remote attacker to execute arbitrary code on the system, caused by deserialization of untrusted data in DiskFileItem class of FileUpload library. A 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\nJazz for Service Management version 1.1.3\n\nREMEDIATION/FIXES\n \n\nPrincipal Product and Version(s) Cumulative Patch Level Jazz for Service Management version 1.1.3 Apache Commons FileUpload Vulnerability addressed with JazzSM 1.1.3 Cumulative Patch level 5\n1.1.3.0-TIV-JazzSM-DASH-Cumulative-Patch-0005 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7ETivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=1.1&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\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 05-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.", " 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.", " SECURITY BULLETIN\n\nSUMMARY\n A security vulnerability relating to remote code execution CVE-2016-1000031 has been reported against Apache Commons FileUpload DiskFileItem File Manipulation, which IBM Spectrum Conductor with Spark 2.2.0 uses as a framework for some services. Commons FileUpload 1.3.3 addresses this vulnerability and can be applied through the manual steps detailed in the Remediation section. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2016-1000031\nDESCRIPTION:A vulnerability in IBM Spectrum Conductor with Spark 2.2.0 could allow a remote attacker to execute arbitrary code on the system, caused by deserialization of untrusted data in DiskFileItem class of FileUpload library. A attacker could exploit this vulnerability to execute arbitrary code under the context of the current process.\nCVSS V3 Base Score:7.5 HIGH\nCVSS V3 Vector:CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H [https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?name=CVE-2016-1000031&vector=AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H](legend [https://nvd.nist.gov/vuln-metrics/cvss])\nCVSS V3 Impact Score: 5.9\nCVSS V3 Exploitability Score: 3.9\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Spectrum Conductor with Spark 2.2.0. All architectures. The remediation steps are provided in this document.\n\nREMEDIATION/FIXES\nNone\n\nWORKAROUNDS AND MITIGATIONS\n1.1 Log on to each management host in the cluster and download the commons-fileupload-1.3.3-bin.tar.gz package from the following location:\n\nhttp://archive.apache.org/dist/commons/fileupload/binaries/commons-fileupload-1.3.3-bin.tar.gz [http://archive.apache.org/dist/commons/fileupload/binaries/commons-fileupload-1.3.3-bin.tar.gz]\n\n1.2 Stop the following services:\n\n> egosh service stop WEBGUI REST ascd plc purger\n\n1.3 For backup purposes, move the following files, which will be replaced by new files:\n\n> mkdir -p /tmp/cf121backup/\n\n> mkdir -p /tmp/cf131backup/\n\nMake note of the file owner, group, and permissions for the following files:\n>ls -la $EGO_TOP/gui/3.5/lib/commons-fileupload-*.jar\n>ls -la $EGO_TOP/perf/3.5/lib/commons-fileupload-*.jar\n>ls -la $EGO_TOP/ascd/2.2.0/lib/commons-fileupload-*.jar\n>ls -la $EGO_TOP/wlp/usr/servers/rest/apps/3.5/deploymentrest/WEB-INF/lib/commons-fileupload-*.jar\n\n> mv $EGO_TOP/gui/3.5/lib/commons-fileupload-*.jar /tmp/cf131backup\n\n> mv $EGO_TOP/perf/3.5/lib/commons-fileupload-*.jar /tmp/cf121backup/\n\n> rm $EGO_TOP/ascd/2.2.0/lib/commons-fileupload-*.jar\n\n> rm $EGO_TOP/wlp/usr/servers/rest/apps/3.5/deploymentrest/WEB-INF/lib/commons-fileupload-*.jar\n\n1.4 On each management host, decompress the commons-fileupload-1.3.3-bin.tar.gz package and copy the following files to your cluster directory:\n\n> tar zxf commons-fileupload-1.3.3-bin.tar.gz\n\n> cp commons-fileupload-1.3.3-bin/commons-fileupload-1.3.3.jar $EGO_TOP/gui/3.5/lib/\n\n> cp commons-fileupload-1.3.3-bin/commons-fileupload-1.3.3.jar $EGO_TOP/perf/3.5/lib/\n\n> cp commons-fileupload-1.3.3-bin/commons-fileupload-1.3.3.jar $EGO_TOP/ascd/2.2.0/lib/\n\n> cp commons-fileupload-1.3.3-bin/commons-fileupload-1.3.3.jar $EGO_TOP/wlp/usr/servers/rest/apps/3.5/deploymentrest/WEB-INF/lib/\n\nIf needed, restore the original file permissions with:\n> chmod ### [file]\n\nIf needed, restore the original file owner and group with:\n> chown [user]:[group] [file]\n\n1.5 On each management host, clean up the GUI work directories:\n\n> rm -rf $EGO_TOP/gui/work/*\n\n> rm -rf $EGO_TOP/gui/workarea/*\n\nNOTE: If you configured theWLP_OUTPUT_DIRparameter andAPPEND_HOSTNAME_TO_WLP_OUTPUT_DIRis set to true in the $EGO_CONFDIR/wlp.conf file, you must clean up the $WLP_OUTPUT_DIR/webgui_hostname/gui/workarea/ directory.\n\n1.6 Launch a web browser and clear your browser cache.\n\n1.7 Start the following services:\n\n> egosh service start WEBGUI REST ascd plc purger\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." ]

[ [ "3a", " SECURITY BULLETIN SUMMARY" ], [ "3b", " The DiskFileItem class in Apache Commons Fileupload before version 1.3.3, used in IBM WebSphere MQ File Transfer Edition, specifically the Web Gateway component, could allow remote attackers to execute arbitrary code under the context of the current process, causing an undefined behavior. VULNERABILITY DETAILS CVEID:CVE-2016-1000031 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031]" ], [ "3c", "DESCRIPTION:Apache Commons FileUpload, used in IBM WebSphere MQ File Transfer Edition, could allow deserialization of untrusted data in the DiskFileItem class of the FileUpload library." ], [ "3d", "A remote attacker could exploit this vulnerability to execute arbitrary code under the context of the current process." ], [ "3e", "CVSS Base Score: 9.8" ], [ "3f", "CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/117957 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117957]for the current score" ], [ "3g", "CVSS Environmental Score*: Undefined" ], [ "3h", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)" ], [ "3i", "AFFECTED PRODUCTS AND VERSIONS" ], [ "3j", "IBM WebSphere MQ File Transfer Edition v7.0.0" ], [ "3k", "IBM WebSphere MQ File Transfer Edition v7.0.1" ], [ "3l", "IBM WebSphere MQ File Transfer Edition v7.0.2" ], [ "3m", "IBM WebSphere MQ File Transfer Edition v7.0.3" ], [ "3n", "IBM WebSphere MQ File Transfer Edition v7.0.4 REMEDIATION/FIXES" ], [ "3o", "All affected product versions are already End of Support." ], [ "3p", "Customers must contact IBM to obtain a fix for the affected release." ], [ "3q", "WORKAROUNDS AND MITIGATIONS None" ], [ "3r", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS" ], [ "3s", " Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. REFERENCES" ], [ "3t", "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]" ], [ "3u", "On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION" ], [ "3v", "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]" ], [ "3w", "IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] CHANGE HISTORY" ], [ "3x", " 22 Dec 2017 Original Version" ], [ "3y", "*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score." ], [ "3z", "Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. DISCLAIMER" ], [ "3aa", "According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\"" ], [ "3ab", "IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE." ], [ "3ac", "CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY." ] ]

[ "3a", "3b", "3c", "3d", "3e", "3f", "3g", "3h", "3i", "3j", "3k", "3l", "3m", "3n", "3o", "3p", "3q" ]

[ " A FIX IS AVAILABLE\nWebSphere Message Broker V7.0 - Fix Pack 7.0.0.8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041187]\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 * When the HTTPRequest node is used with a HTTP proxy location\n set and \"Follow HTTP(S) redirection\" enabled redirects are not\n followed if the initial remote server is ssl enabled.\n \n \n \n \n \n \n \n \n Additional Symptom(s) Search Keyword(s): SSL HTTPRequest\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of WebSphere Message Broker V7.0 or higher and IBM\n Integration Bus V9.0 using HTTPS proxy servers with the\n HTTPRequest or SOAP Request Nodes.\n \n \n Platforms affected:\n z/OS, MultiPlatform\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n When the HTTPRequest or SOAPRequest nodes are used with a HTTP\n proxy location\n set and \"Follow HTTP(S) redirection\" enabled redirects are not\n followed if the initial remote server is ssl enabled.\n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The HTTPRequest and SOAPRequest Nodes have been updated so the\n redirects are followed when using a HTTP proxy and SSL.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v7.0 7.0.0.8\n v8.0 8.0.0.6\n v9.0 9.0.0.3\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available, information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT01504\n \n \n * REPORTED COMPONENT NAME\n WEB MESSAGE BRO\n \n \n * REPORTED COMPONENT ID\n 5724J0510\n \n \n * REPORTED RELEASE\n 700\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-05-02\n \n \n * CLOSED DATE\n 2014-07-31\n \n \n * LAST MODIFIED DATE\n 2014-07-31\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 WEB MESSAGE BRO\n \n \n * FIXED COMPONENT ID\n 5724J0510\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R700 PSY\n UP", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * The percentage character of a percentage-encoded part is getting\n encoded again by the HTTPRequest/SOAPrequest nodes\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of IBM integration Bus V9.0 and V10.0 using the\n HTTPRequest node or the SOAPRequest node.\n \n \n Platforms affected:\n z/OS, MultiPlatform\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n If a percentage character(%) appears in a percentage-encoded\n part of a request URI it is incorrectly getting re-encoded by\n HTTPRequest and SOAPrequest nodes.\n \n \n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The product no longer double encodes percent characters if they\n appear in an encoded part of a request URI.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v10.0 10.0.0.6\n v9.0 9.0.0.7\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available,information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT15787\n \n \n * REPORTED COMPONENT NAME\n INTEGRATION BUS\n \n \n * REPORTED COMPONENT ID\n 5724J0530\n \n \n * REPORTED RELEASE\n 900\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 2016-06-20\n \n \n * CLOSED DATE\n 2016-08-17\n \n \n * LAST MODIFIED DATE\n 2016-08-17\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 INTEGRATION BUS\n \n \n * FIXED COMPONENT ID\n 5724J0530\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R900 PSY\n UP", " SUBSCRIBE\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 * On AIX only, memory corruption can occur after an exception\n condition, such as a timeout, in the HTTPRequest node.\n \n This then causes a coredump and a restart of the integration\n server. The stack in the coredump can vary, but is most likely\n to show a segfault following a native throw:\n \n ImbWSRequestNode.ImbBufferedStringBase\n char,std::char_traits,unsigned\n short,24,128>::__dftdt()(??) at 0x900000016273b40\n invokedtr.__Invoke__Destructor() at 0x9000000006ef9e4\n __DoThrowV6() at 0x9000000006f2dcc\n ImbRecoverableException::throwThis()(??) at 0x900000000f026d0\n ImbWSRequestNode::evaluate(const ImbMessageAssembly&,const\n ImbDataFlowTerminal*)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of IBM Integration Bus V9.0 on AIX, who use the\n HTTPRequest node.\n \n \n Platforms affected:\n AIX\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n On AIX only, memory corruption can occur after an exception\n condition, such as a timeout, in the HTTPRequest node.\n \n This then causes a coredump and a restart of the integration\n server. The stack in the coredump can vary, but is most likely\n to show a segfault following a native throw:\n \n ImbWSRequestNode.ImbBufferedStringBase\n char,std::char_traits,unsigned\n short,24,128>::__dftdt()(??) at 0x900000016273b40\n invokedtr.__Invoke__Destructor() at 0x9000000006ef9e4\n __DoThrowV6() at 0x9000000006f2dcc\n ImbRecoverableException::throwThis()(??) at 0x900000000f026d0\n ImbWSRequestNode::evaluate(const ImbMessageAssembly&,const\n ImbDataFlowTerminal*)\n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The product no longer encounters memory corruption following an\n exception in the HTTPRequest node.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v9.0 9.0.0.3\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available, information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT00989\n \n \n * REPORTED COMPONENT NAME\n INTEGRATION BUS\n \n \n * REPORTED COMPONENT ID\n 5724J0530\n \n \n * REPORTED RELEASE\n 900\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 2014-04-11\n \n \n * CLOSED DATE\n 2014-07-31\n \n \n * LAST MODIFIED DATE\n 2014-07-31\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 INTEGRATION BUS\n \n \n * FIXED COMPONENT ID\n 5724J0530\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R900 PSY\n UP", " SUBSCRIBE\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 * HTTPINPUT/REQUEST NODES SHOULD ALLOW TWO CONNECTION HEADERS\n WHENCLOSE IS SPECIFIED (BACKPORT IC59901 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC59901])\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of WebSphere Message Broker who *\n * use the HTTPRequest node. *\n ****************************************************************\n * PROBLEM DESCRIPTION: WebSphere Message Broker issues a *\n * BIP3157 message when it receives two *\n * 'connection' headers in the response *\n * to a request from a HTTPRequest node. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n WebSphere Message Broker issues a BIP3157 message when it\n receives two 'connection' headers in the response to a\n request from a HTTPRequest node.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * WebSphere Message Broker has been modified so that it allows\n two or more connection headers in the response to requests\n from the HTTPRequest node.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IZ55783\n \n \n * REPORTED COMPONENT NAME\n MSSG BROKER AIX\n \n \n * REPORTED COMPONENT ID\n 5724J0501\n \n \n * REPORTED RELEASE\n 100\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 2009-07-22\n \n \n * CLOSED DATE\n 2009-07-30\n \n \n * LAST MODIFIED DATE\n 2009-07-30\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 MSSG BROKER AIX\n \n \n * FIXED COMPONENT ID\n 5724J0501\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R100 PSY\n UP", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You are experiencing High CPU and Performance problems in IBM Integration Bus (IIB) or WebSphere Message Broker (WMB). You would like to know what documentation you must collect (MustGather) so that the IBM Integration Bus / WebSphere Message Broker 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\nRESOLVING THE PROBLEM\n\n\n\nSTEP 1: SELF-GUIDED TROUBLESHOOTING\n\n 1. Message flow accounting and statistics [http://www.ibm.com/developerworks/websphere/library/techarticles/0710_piatek/0710_piatek.html] can be started and viewed in IBM Integration Explorer to monitor the message flows processing messages when such a problem is experienced. Also check the following example in the Knowledge Center. [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac19050_.htm] \n By reviewing the data, you can isolate the problem down to a specific message flow node where the problem may be occurring. For example: average elapsed time (in milliseconds), average CPU time and the number of times a node is invoked can help you identify a particular node that may be a bottleneck. \n 2. \n 3. Check for known issues:\n IIB diagnostic tools guide [http://www.ibm.com/support/knowledgecenter/en/SSKM8N/pdguides/clientDiagnostics.html?sc=_latest]\n How to use the flow analysis to find further performance problems [https://developer.ibm.com/integration/blog/2014/03/20/how-to-use-the-flow-analysis-to-find-further-performance-problems/]\n IIB and WMB FAQ for memory [http://www.ibm.com/support/docview.wss?uid=swg21665926&acss=dakc]\n Dynamic guide to help troubleshooting Message Broker [https://developer.ibm.com/integration/docs/ibm-integration-bus/troubleshooting/dynamic-problem-determination-guides/]\n Troubleshooting performance problems [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bj28660_.htm?lang=en]\n Message splitter pattern [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.pattern.mbi.doc/mbi/ms/overview.htm?lang=en]\n [http://www.ibm.com/software/htp/cics/tserver/support/]IBM Integration Bus support site [https://www-947.ibm.com/support/entry/myportal/product/websphere/ibm_integration_bus?productContext=-1766202334]\n \n\n\n\nSTEP 2: COLLECT DATA\n\n 1. mqsidc\n See: mqsidc usage instructions [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bu46012_.htm]\n * This command line tool is only available for WMB 7.0.0.5+, WMB 8.0.0.1+, IIB 9.0.0.0+, and IIB 10.0.0.0+.\n * When running the tool, select the option for 'Broker Collector', when prompted.\n \n \n 2. \n 3. \n 4. Message flow accounting and statistics\n See: Procedure for collecting accounting and statistics data as XML messages [http://www.ibm.com/support/docview.wss?uid=swg21678313] [http://www.ibm.com/support/docview.wss?uid=swg21678312] \n 5. \n 6. \n 7. Stack dump In hang situations, collect 4-5 stack dumps of the threads running in the DataFlowEngine with a gap of about 10 seconds each.\n Use these commands, where <PID> is the process ID of the DataFlowEngine:\n \n \n * procstack <PID> (On AIX)\n * pstack <PID> (On Linux, Solaris)\n \n \n \n \n 8. \n 9. \n 10. Project Interchange files for the problematic flow/set/ESQL/model\n * You can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.\n See: Exporting files from the Workbench [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ax20230_.htm?cp=SSMKHH_9.0.0%2F1-2-4] \n \n \n 11. \n 12. \n 13. Traces If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321] can be used to gain a better understanding of the problem. * A service level trace [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321#2] is intended to be provided to IBM Support to assist in the diagnosis of your issue. Please run the service level trace independently and not while the above other items are being collected\n \n \n 14. \n 15. \n 16. General Broker information\n If the mqsidc tool was not run, then capture this information manually * Record the IBM Integration Bus or WebSphere Message Broker version, release, and maintenance level.\n This can be captured using the command 'mqsiservice -v'..\n * Record the operating system version, release, and maintenance level.\n * Record the version, release, and maintenance level of any related products and components for the problematic application.\n * Collect the local error log. On UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.\n See: Configuring the syslog daemon [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/an04230_.htm]\n * Collect the Standard Output/Error logs.\n WMB writes information to both STDOUT and STDERR. These files are located under the Message Broker workpath.\n See: Standard System Logs [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/au14165_.htm]\n \n \n 17. \n 18. \n 19. Additional information * Output of command: mqsilist -r -d2 \n \n \n\n\n\nATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!\nWhen sending data to IBM, be sure to update your PMR or send a note with the following information:\n\n * Tell us what errors you saw, where you saw them, and what time they happened Let us know if you made any changes to WebSphere Message Broker or the system before the problem Share any other observations which you think will help us to better understand the problem \n\n\n\nSTEP 3: SUBMIT DATA TO IBM\n\n * Use IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM.\n * Send your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis.\n\n\n\n\n\nPlease see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support.\n\n\n\nBack to top\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Performance AIX, HP-UX, Linux, Solaris, Windows 8.0 All Editions" ]

[ [ "0a", " A FIX IS AVAILABLE" ], [ "0b", "WebSphere Message Broker V7.0 - Fix Pack 7.0.0.8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041187] SUBSCRIBE" ], [ "0c", "You can track all active APARs for this component. APAR STATUS" ], [ "0d", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "0e", " * When the HTTPRequest node is used with a HTTP proxy location" ], [ "0f", " set and \"Follow HTTP(S) redirection\" enabled redirects are not" ], [ "0g", " followed if the initial remote server is ssl enabled." ], [ "0h", " Additional Symptom(s) Search Keyword(s): SSL HTTPRequest LOCAL FIX PROBLEM SUMMARY" ], [ "0i", " * ****************************************************************" ], [ "0j", " USERS AFFECTED:" ], [ "0k", " All users of WebSphere Message Broker V7.0 or higher and IBM" ], [ "0l", " Integration Bus V9.0 using HTTPS proxy servers with the" ], [ "0m", " HTTPRequest or SOAP Request Nodes." ], [ "0n", " Platforms affected:" ], [ "0o", " z/OS, MultiPlatform" ], [ "0p", " ****************************************************************" ], [ "0q", " PROBLEM DESCRIPTION:" ], [ "0r", " When the HTTPRequest or SOAPRequest nodes are used with a HTTP" ], [ "0s", " proxy location" ], [ "0t", " set and \"Follow HTTP(S) redirection\" enabled redirects are not" ], [ "0u", " followed if the initial remote server is ssl enabled." ], [ "0v", " There are a number of resource name changes between WebSphere" ], [ "0w", " Message Broker and IBM Integration Bus Version 9.0. For details" ], [ "0x", " visit" ], [ "0y", " http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e" ], [ "0z", " tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm] PROBLEM CONCLUSION" ], [ "0aa", " * The HTTPRequest and SOAPRequest Nodes have been updated so the" ], [ "0ab", " redirects are followed when using a HTTP proxy and SSL." ], [ "0ac", " ---------------------------------------------------------------" ], [ "0ad", " The fix is targeted for delivery in the following PTFs:" ], [ "0ae", " Version Maintenance Level" ], [ "0af", " v7.0 7.0.0.8" ], [ "0ag", " v8.0 8.0.0.6" ], [ "0ah", " v9.0 9.0.0.3" ], [ "0ai", " The latest available maintenance can be obtained from:" ], [ "0aj", " http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]" ], [ "0ak", " If the maintenance level is not yet available, information on" ], [ "0al", " its planned availability can be found on:" ], [ "0am", " http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]" ], [ "0an", " --------------------------------------------------------------- TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "0ao", " * APAR NUMBER" ], [ "0ap", " IT01504" ], [ "0aq", " * REPORTED COMPONENT NAME" ], [ "0ar", " WEB MESSAGE BRO" ], [ "0as", " * REPORTED COMPONENT ID" ], [ "0at", " 5724J0510" ], [ "0au", " * REPORTED RELEASE" ], [ "0av", " 700" ], [ "0aw", " * STATUS" ], [ "0ax", " CLOSED PER" ], [ "0ay", " * PE" ], [ "0az", " NoPE" ], [ "0ba", " * HIPER" ], [ "0bb", " NoHIPER" ], [ "0bc", " * SPECIAL ATTENTION" ], [ "0bd", " NoSpecatt" ], [ "0be", " * SUBMITTED DATE" ], [ "0bf", " 2014-05-02" ], [ "0bg", " * CLOSED DATE" ], [ "0bh", " 2014-07-31" ], [ "0bi", " * LAST MODIFIED DATE" ], [ "0bj", " 2014-07-31" ], [ "0bk", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "0bl", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "0bm", " * FIXED COMPONENT NAME" ], [ "0bn", " WEB MESSAGE BRO" ], [ "0bo", " * FIXED COMPONENT ID" ], [ "0bp", " 5724J0510" ], [ "0bq", "APPLICABLE COMPONENT LEVELS" ], [ "0br", " * R700 PSY" ], [ "0bs", " UP" ] ]

[ "0e", "0g", "0n", "0q", "0t", "0u", "1e", "1g", "1p", "1q", "1s", "1y", "2b", "2c", "2d", "2x", "2y", "2z", "3e", "3i", "3m", "3p", "3s", "4f", "4g", "4h", "4i", "4p", "4s", "4t", "4u" ]

[ " A FIX IS AVAILABLE\nWebSphere Message Broker V7.0 - Fix Pack 7.0.0.8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041187]\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 * When the HTTPRequest node is used with a HTTP proxy location\n set and \"Follow HTTP(S) redirection\" enabled redirects are not\n followed if the initial remote server is ssl enabled.\n \n \n \n \n \n \n \n \n Additional Symptom(s) Search Keyword(s): SSL HTTPRequest\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of WebSphere Message Broker V7.0 or higher and IBM\n Integration Bus V9.0 using HTTPS proxy servers with the\n HTTPRequest or SOAP Request Nodes.\n \n \n Platforms affected:\n z/OS, MultiPlatform\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n When the HTTPRequest or SOAPRequest nodes are used with a HTTP\n proxy location\n set and \"Follow HTTP(S) redirection\" enabled redirects are not\n followed if the initial remote server is ssl enabled.\n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The HTTPRequest and SOAPRequest Nodes have been updated so the\n redirects are followed when using a HTTP proxy and SSL.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v7.0 7.0.0.8\n v8.0 8.0.0.6\n v9.0 9.0.0.3\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available, information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT01504\n \n \n * REPORTED COMPONENT NAME\n WEB MESSAGE BRO\n \n \n * REPORTED COMPONENT ID\n 5724J0510\n \n \n * REPORTED RELEASE\n 700\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-05-02\n \n \n * CLOSED DATE\n 2014-07-31\n \n \n * LAST MODIFIED DATE\n 2014-07-31\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 WEB MESSAGE BRO\n \n \n * FIXED COMPONENT ID\n 5724J0510\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R700 PSY\n UP", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * The percentage character of a percentage-encoded part is getting\n encoded again by the HTTPRequest/SOAPrequest nodes\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of IBM integration Bus V9.0 and V10.0 using the\n HTTPRequest node or the SOAPRequest node.\n \n \n Platforms affected:\n z/OS, MultiPlatform\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n If a percentage character(%) appears in a percentage-encoded\n part of a request URI it is incorrectly getting re-encoded by\n HTTPRequest and SOAPrequest nodes.\n \n \n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The product no longer double encodes percent characters if they\n appear in an encoded part of a request URI.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v10.0 10.0.0.6\n v9.0 9.0.0.7\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available,information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT15787\n \n \n * REPORTED COMPONENT NAME\n INTEGRATION BUS\n \n \n * REPORTED COMPONENT ID\n 5724J0530\n \n \n * REPORTED RELEASE\n 900\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 2016-06-20\n \n \n * CLOSED DATE\n 2016-08-17\n \n \n * LAST MODIFIED DATE\n 2016-08-17\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 INTEGRATION BUS\n \n \n * FIXED COMPONENT ID\n 5724J0530\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R900 PSY\n UP", " SUBSCRIBE\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 * On AIX only, memory corruption can occur after an exception\n condition, such as a timeout, in the HTTPRequest node.\n \n This then causes a coredump and a restart of the integration\n server. The stack in the coredump can vary, but is most likely\n to show a segfault following a native throw:\n \n ImbWSRequestNode.ImbBufferedStringBase\n char,std::char_traits,unsigned\n short,24,128>::__dftdt()(??) at 0x900000016273b40\n invokedtr.__Invoke__Destructor() at 0x9000000006ef9e4\n __DoThrowV6() at 0x9000000006f2dcc\n ImbRecoverableException::throwThis()(??) at 0x900000000f026d0\n ImbWSRequestNode::evaluate(const ImbMessageAssembly&,const\n ImbDataFlowTerminal*)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of IBM Integration Bus V9.0 on AIX, who use the\n HTTPRequest node.\n \n \n Platforms affected:\n AIX\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n On AIX only, memory corruption can occur after an exception\n condition, such as a timeout, in the HTTPRequest node.\n \n This then causes a coredump and a restart of the integration\n server. The stack in the coredump can vary, but is most likely\n to show a segfault following a native throw:\n \n ImbWSRequestNode.ImbBufferedStringBase\n char,std::char_traits,unsigned\n short,24,128>::__dftdt()(??) at 0x900000016273b40\n invokedtr.__Invoke__Destructor() at 0x9000000006ef9e4\n __DoThrowV6() at 0x9000000006f2dcc\n ImbRecoverableException::throwThis()(??) at 0x900000000f026d0\n ImbWSRequestNode::evaluate(const ImbMessageAssembly&,const\n ImbDataFlowTerminal*)\n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The product no longer encounters memory corruption following an\n exception in the HTTPRequest node.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v9.0 9.0.0.3\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available, information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT00989\n \n \n * REPORTED COMPONENT NAME\n INTEGRATION BUS\n \n \n * REPORTED COMPONENT ID\n 5724J0530\n \n \n * REPORTED RELEASE\n 900\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 2014-04-11\n \n \n * CLOSED DATE\n 2014-07-31\n \n \n * LAST MODIFIED DATE\n 2014-07-31\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 INTEGRATION BUS\n \n \n * FIXED COMPONENT ID\n 5724J0530\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R900 PSY\n UP", " SUBSCRIBE\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 * HTTPINPUT/REQUEST NODES SHOULD ALLOW TWO CONNECTION HEADERS\n WHENCLOSE IS SPECIFIED (BACKPORT IC59901 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC59901])\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of WebSphere Message Broker who *\n * use the HTTPRequest node. *\n ****************************************************************\n * PROBLEM DESCRIPTION: WebSphere Message Broker issues a *\n * BIP3157 message when it receives two *\n * 'connection' headers in the response *\n * to a request from a HTTPRequest node. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n WebSphere Message Broker issues a BIP3157 message when it\n receives two 'connection' headers in the response to a\n request from a HTTPRequest node.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * WebSphere Message Broker has been modified so that it allows\n two or more connection headers in the response to requests\n from the HTTPRequest node.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IZ55783\n \n \n * REPORTED COMPONENT NAME\n MSSG BROKER AIX\n \n \n * REPORTED COMPONENT ID\n 5724J0501\n \n \n * REPORTED RELEASE\n 100\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 2009-07-22\n \n \n * CLOSED DATE\n 2009-07-30\n \n \n * LAST MODIFIED DATE\n 2009-07-30\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 MSSG BROKER AIX\n \n \n * FIXED COMPONENT ID\n 5724J0501\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R100 PSY\n UP", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You are experiencing High CPU and Performance problems in IBM Integration Bus (IIB) or WebSphere Message Broker (WMB). You would like to know what documentation you must collect (MustGather) so that the IBM Integration Bus / WebSphere Message Broker 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\nRESOLVING THE PROBLEM\n\n\n\nSTEP 1: SELF-GUIDED TROUBLESHOOTING\n\n 1. Message flow accounting and statistics [http://www.ibm.com/developerworks/websphere/library/techarticles/0710_piatek/0710_piatek.html] can be started and viewed in IBM Integration Explorer to monitor the message flows processing messages when such a problem is experienced. Also check the following example in the Knowledge Center. [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac19050_.htm] \n By reviewing the data, you can isolate the problem down to a specific message flow node where the problem may be occurring. For example: average elapsed time (in milliseconds), average CPU time and the number of times a node is invoked can help you identify a particular node that may be a bottleneck. \n 2. \n 3. Check for known issues:\n IIB diagnostic tools guide [http://www.ibm.com/support/knowledgecenter/en/SSKM8N/pdguides/clientDiagnostics.html?sc=_latest]\n How to use the flow analysis to find further performance problems [https://developer.ibm.com/integration/blog/2014/03/20/how-to-use-the-flow-analysis-to-find-further-performance-problems/]\n IIB and WMB FAQ for memory [http://www.ibm.com/support/docview.wss?uid=swg21665926&acss=dakc]\n Dynamic guide to help troubleshooting Message Broker [https://developer.ibm.com/integration/docs/ibm-integration-bus/troubleshooting/dynamic-problem-determination-guides/]\n Troubleshooting performance problems [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bj28660_.htm?lang=en]\n Message splitter pattern [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.pattern.mbi.doc/mbi/ms/overview.htm?lang=en]\n [http://www.ibm.com/software/htp/cics/tserver/support/]IBM Integration Bus support site [https://www-947.ibm.com/support/entry/myportal/product/websphere/ibm_integration_bus?productContext=-1766202334]\n \n\n\n\nSTEP 2: COLLECT DATA\n\n 1. mqsidc\n See: mqsidc usage instructions [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bu46012_.htm]\n * This command line tool is only available for WMB 7.0.0.5+, WMB 8.0.0.1+, IIB 9.0.0.0+, and IIB 10.0.0.0+.\n * When running the tool, select the option for 'Broker Collector', when prompted.\n \n \n 2. \n 3. \n 4. Message flow accounting and statistics\n See: Procedure for collecting accounting and statistics data as XML messages [http://www.ibm.com/support/docview.wss?uid=swg21678313] [http://www.ibm.com/support/docview.wss?uid=swg21678312] \n 5. \n 6. \n 7. Stack dump In hang situations, collect 4-5 stack dumps of the threads running in the DataFlowEngine with a gap of about 10 seconds each.\n Use these commands, where <PID> is the process ID of the DataFlowEngine:\n \n \n * procstack <PID> (On AIX)\n * pstack <PID> (On Linux, Solaris)\n \n \n \n \n 8. \n 9. \n 10. Project Interchange files for the problematic flow/set/ESQL/model\n * You can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.\n See: Exporting files from the Workbench [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ax20230_.htm?cp=SSMKHH_9.0.0%2F1-2-4] \n \n \n 11. \n 12. \n 13. Traces If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321] can be used to gain a better understanding of the problem. * A service level trace [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321#2] is intended to be provided to IBM Support to assist in the diagnosis of your issue. Please run the service level trace independently and not while the above other items are being collected\n \n \n 14. \n 15. \n 16. General Broker information\n If the mqsidc tool was not run, then capture this information manually * Record the IBM Integration Bus or WebSphere Message Broker version, release, and maintenance level.\n This can be captured using the command 'mqsiservice -v'..\n * Record the operating system version, release, and maintenance level.\n * Record the version, release, and maintenance level of any related products and components for the problematic application.\n * Collect the local error log. On UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.\n See: Configuring the syslog daemon [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/an04230_.htm]\n * Collect the Standard Output/Error logs.\n WMB writes information to both STDOUT and STDERR. These files are located under the Message Broker workpath.\n See: Standard System Logs [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/au14165_.htm]\n \n \n 17. \n 18. \n 19. Additional information * Output of command: mqsilist -r -d2 \n \n \n\n\n\nATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!\nWhen sending data to IBM, be sure to update your PMR or send a note with the following information:\n\n * Tell us what errors you saw, where you saw them, and what time they happened Let us know if you made any changes to WebSphere Message Broker or the system before the problem Share any other observations which you think will help us to better understand the problem \n\n\n\nSTEP 3: SUBMIT DATA TO IBM\n\n * Use IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM.\n * Send your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis.\n\n\n\n\n\nPlease see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support.\n\n\n\nBack to top\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Performance AIX, HP-UX, Linux, Solaris, Windows 8.0 All Editions" ]

[ [ "1a", " SUBSCRIBE TO THIS APAR" ], [ "1b", "By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available." ], [ "1c", "You can track this item individually or track all items by product." ], [ "1d", "Notify me when this APAR changes." ], [ "1e", "Notify me when an APAR for this component changes. APAR STATUS" ], [ "1f", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "1g", " * The percentage character of a percentage-encoded part is getting" ], [ "1h", " encoded again by the HTTPRequest/SOAPrequest nodes LOCAL FIX PROBLEM SUMMARY" ], [ "1i", " * ****************************************************************" ], [ "1j", " USERS AFFECTED:" ], [ "1k", " All users of IBM integration Bus V9.0 and V10.0 using the" ], [ "1l", " HTTPRequest node or the SOAPRequest node." ], [ "1m", " Platforms affected:" ], [ "1n", " z/OS, MultiPlatform" ], [ "1o", " ****************************************************************" ], [ "1p", " PROBLEM DESCRIPTION:" ], [ "1q", " If a percentage character(%) appears in a percentage-encoded" ], [ "1r", " part of a request URI it is incorrectly getting re-encoded by" ], [ "1s", " HTTPRequest and SOAPrequest nodes." ], [ "1t", " There are a number of resource name changes between WebSphere" ], [ "1u", " Message Broker and IBM Integration Bus Version 9.0. For details" ], [ "1v", " visit" ], [ "1w", " http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e" ], [ "1x", " tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm] PROBLEM CONCLUSION" ], [ "1y", " * The product no longer double encodes percent characters if they" ], [ "1z", " appear in an encoded part of a request URI." ], [ "1aa", " ---------------------------------------------------------------" ], [ "1ab", " The fix is targeted for delivery in the following PTFs:" ], [ "1ac", " Version Maintenance Level" ], [ "1ad", " v10.0 10.0.0.6" ], [ "1ae", " v9.0 9.0.0.7" ], [ "1af", " The latest available maintenance can be obtained from:" ], [ "1ag", " http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]" ], [ "1ah", " If the maintenance level is not yet available,information on" ], [ "1ai", " its planned availability can be found on:" ], [ "1aj", " http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]" ], [ "1ak", " --------------------------------------------------------------- TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "1al", " * APAR NUMBER" ], [ "1am", " IT15787" ], [ "1an", " * REPORTED COMPONENT NAME" ], [ "1ao", " INTEGRATION BUS" ], [ "1ap", " * REPORTED COMPONENT ID" ], [ "1aq", " 5724J0530" ], [ "1ar", " * REPORTED RELEASE" ], [ "1as", " 900" ], [ "1at", " * STATUS" ], [ "1au", " CLOSED PER" ], [ "1av", " * PE" ], [ "1aw", " NoPE" ], [ "1ax", " * HIPER" ], [ "1ay", " NoHIPER" ], [ "1az", " * SPECIAL ATTENTION" ], [ "1ba", " NoSpecatt / Xsystem" ], [ "1bb", " * SUBMITTED DATE" ], [ "1bc", " 2016-06-20" ], [ "1bd", " * CLOSED DATE" ], [ "1be", " 2016-08-17" ], [ "1bf", " * LAST MODIFIED DATE" ], [ "1bg", " 2016-08-17" ], [ "1bh", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "1bi", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "1bj", " * FIXED COMPONENT NAME" ], [ "1bk", " INTEGRATION BUS" ], [ "1bl", " * FIXED COMPONENT ID" ], [ "1bm", " 5724J0530" ], [ "1bn", "APPLICABLE COMPONENT LEVELS" ], [ "1bo", " * R900 PSY" ], [ "1bp", " UP" ] ]

[ "0e", "0g", "0n", "0q", "0t", "0u", "1e", "1g", "1p", "1q", "1s", "1y", "2b", "2c", "2d", "2x", "2y", "2z", "3e", "3i", "3m", "3p", "3s", "4f", "4g", "4h", "4i", "4p", "4s", "4t", "4u" ]

[ " A FIX IS AVAILABLE\nWebSphere Message Broker V7.0 - Fix Pack 7.0.0.8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041187]\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 * When the HTTPRequest node is used with a HTTP proxy location\n set and \"Follow HTTP(S) redirection\" enabled redirects are not\n followed if the initial remote server is ssl enabled.\n \n \n \n \n \n \n \n \n Additional Symptom(s) Search Keyword(s): SSL HTTPRequest\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of WebSphere Message Broker V7.0 or higher and IBM\n Integration Bus V9.0 using HTTPS proxy servers with the\n HTTPRequest or SOAP Request Nodes.\n \n \n Platforms affected:\n z/OS, MultiPlatform\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n When the HTTPRequest or SOAPRequest nodes are used with a HTTP\n proxy location\n set and \"Follow HTTP(S) redirection\" enabled redirects are not\n followed if the initial remote server is ssl enabled.\n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The HTTPRequest and SOAPRequest Nodes have been updated so the\n redirects are followed when using a HTTP proxy and SSL.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v7.0 7.0.0.8\n v8.0 8.0.0.6\n v9.0 9.0.0.3\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available, information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT01504\n \n \n * REPORTED COMPONENT NAME\n WEB MESSAGE BRO\n \n \n * REPORTED COMPONENT ID\n 5724J0510\n \n \n * REPORTED RELEASE\n 700\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-05-02\n \n \n * CLOSED DATE\n 2014-07-31\n \n \n * LAST MODIFIED DATE\n 2014-07-31\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 WEB MESSAGE BRO\n \n \n * FIXED COMPONENT ID\n 5724J0510\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R700 PSY\n UP", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * The percentage character of a percentage-encoded part is getting\n encoded again by the HTTPRequest/SOAPrequest nodes\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of IBM integration Bus V9.0 and V10.0 using the\n HTTPRequest node or the SOAPRequest node.\n \n \n Platforms affected:\n z/OS, MultiPlatform\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n If a percentage character(%) appears in a percentage-encoded\n part of a request URI it is incorrectly getting re-encoded by\n HTTPRequest and SOAPrequest nodes.\n \n \n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The product no longer double encodes percent characters if they\n appear in an encoded part of a request URI.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v10.0 10.0.0.6\n v9.0 9.0.0.7\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available,information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT15787\n \n \n * REPORTED COMPONENT NAME\n INTEGRATION BUS\n \n \n * REPORTED COMPONENT ID\n 5724J0530\n \n \n * REPORTED RELEASE\n 900\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 2016-06-20\n \n \n * CLOSED DATE\n 2016-08-17\n \n \n * LAST MODIFIED DATE\n 2016-08-17\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 INTEGRATION BUS\n \n \n * FIXED COMPONENT ID\n 5724J0530\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R900 PSY\n UP", " SUBSCRIBE\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 * On AIX only, memory corruption can occur after an exception\n condition, such as a timeout, in the HTTPRequest node.\n \n This then causes a coredump and a restart of the integration\n server. The stack in the coredump can vary, but is most likely\n to show a segfault following a native throw:\n \n ImbWSRequestNode.ImbBufferedStringBase\n char,std::char_traits,unsigned\n short,24,128>::__dftdt()(??) at 0x900000016273b40\n invokedtr.__Invoke__Destructor() at 0x9000000006ef9e4\n __DoThrowV6() at 0x9000000006f2dcc\n ImbRecoverableException::throwThis()(??) at 0x900000000f026d0\n ImbWSRequestNode::evaluate(const ImbMessageAssembly&,const\n ImbDataFlowTerminal*)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of IBM Integration Bus V9.0 on AIX, who use the\n HTTPRequest node.\n \n \n Platforms affected:\n AIX\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n On AIX only, memory corruption can occur after an exception\n condition, such as a timeout, in the HTTPRequest node.\n \n This then causes a coredump and a restart of the integration\n server. The stack in the coredump can vary, but is most likely\n to show a segfault following a native throw:\n \n ImbWSRequestNode.ImbBufferedStringBase\n char,std::char_traits,unsigned\n short,24,128>::__dftdt()(??) at 0x900000016273b40\n invokedtr.__Invoke__Destructor() at 0x9000000006ef9e4\n __DoThrowV6() at 0x9000000006f2dcc\n ImbRecoverableException::throwThis()(??) at 0x900000000f026d0\n ImbWSRequestNode::evaluate(const ImbMessageAssembly&,const\n ImbDataFlowTerminal*)\n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The product no longer encounters memory corruption following an\n exception in the HTTPRequest node.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v9.0 9.0.0.3\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available, information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT00989\n \n \n * REPORTED COMPONENT NAME\n INTEGRATION BUS\n \n \n * REPORTED COMPONENT ID\n 5724J0530\n \n \n * REPORTED RELEASE\n 900\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 2014-04-11\n \n \n * CLOSED DATE\n 2014-07-31\n \n \n * LAST MODIFIED DATE\n 2014-07-31\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 INTEGRATION BUS\n \n \n * FIXED COMPONENT ID\n 5724J0530\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R900 PSY\n UP", " SUBSCRIBE\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 * HTTPINPUT/REQUEST NODES SHOULD ALLOW TWO CONNECTION HEADERS\n WHENCLOSE IS SPECIFIED (BACKPORT IC59901 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC59901])\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of WebSphere Message Broker who *\n * use the HTTPRequest node. *\n ****************************************************************\n * PROBLEM DESCRIPTION: WebSphere Message Broker issues a *\n * BIP3157 message when it receives two *\n * 'connection' headers in the response *\n * to a request from a HTTPRequest node. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n WebSphere Message Broker issues a BIP3157 message when it\n receives two 'connection' headers in the response to a\n request from a HTTPRequest node.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * WebSphere Message Broker has been modified so that it allows\n two or more connection headers in the response to requests\n from the HTTPRequest node.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IZ55783\n \n \n * REPORTED COMPONENT NAME\n MSSG BROKER AIX\n \n \n * REPORTED COMPONENT ID\n 5724J0501\n \n \n * REPORTED RELEASE\n 100\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 2009-07-22\n \n \n * CLOSED DATE\n 2009-07-30\n \n \n * LAST MODIFIED DATE\n 2009-07-30\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 MSSG BROKER AIX\n \n \n * FIXED COMPONENT ID\n 5724J0501\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R100 PSY\n UP", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You are experiencing High CPU and Performance problems in IBM Integration Bus (IIB) or WebSphere Message Broker (WMB). You would like to know what documentation you must collect (MustGather) so that the IBM Integration Bus / WebSphere Message Broker 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\nRESOLVING THE PROBLEM\n\n\n\nSTEP 1: SELF-GUIDED TROUBLESHOOTING\n\n 1. Message flow accounting and statistics [http://www.ibm.com/developerworks/websphere/library/techarticles/0710_piatek/0710_piatek.html] can be started and viewed in IBM Integration Explorer to monitor the message flows processing messages when such a problem is experienced. Also check the following example in the Knowledge Center. [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac19050_.htm] \n By reviewing the data, you can isolate the problem down to a specific message flow node where the problem may be occurring. For example: average elapsed time (in milliseconds), average CPU time and the number of times a node is invoked can help you identify a particular node that may be a bottleneck. \n 2. \n 3. Check for known issues:\n IIB diagnostic tools guide [http://www.ibm.com/support/knowledgecenter/en/SSKM8N/pdguides/clientDiagnostics.html?sc=_latest]\n How to use the flow analysis to find further performance problems [https://developer.ibm.com/integration/blog/2014/03/20/how-to-use-the-flow-analysis-to-find-further-performance-problems/]\n IIB and WMB FAQ for memory [http://www.ibm.com/support/docview.wss?uid=swg21665926&acss=dakc]\n Dynamic guide to help troubleshooting Message Broker [https://developer.ibm.com/integration/docs/ibm-integration-bus/troubleshooting/dynamic-problem-determination-guides/]\n Troubleshooting performance problems [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bj28660_.htm?lang=en]\n Message splitter pattern [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.pattern.mbi.doc/mbi/ms/overview.htm?lang=en]\n [http://www.ibm.com/software/htp/cics/tserver/support/]IBM Integration Bus support site [https://www-947.ibm.com/support/entry/myportal/product/websphere/ibm_integration_bus?productContext=-1766202334]\n \n\n\n\nSTEP 2: COLLECT DATA\n\n 1. mqsidc\n See: mqsidc usage instructions [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bu46012_.htm]\n * This command line tool is only available for WMB 7.0.0.5+, WMB 8.0.0.1+, IIB 9.0.0.0+, and IIB 10.0.0.0+.\n * When running the tool, select the option for 'Broker Collector', when prompted.\n \n \n 2. \n 3. \n 4. Message flow accounting and statistics\n See: Procedure for collecting accounting and statistics data as XML messages [http://www.ibm.com/support/docview.wss?uid=swg21678313] [http://www.ibm.com/support/docview.wss?uid=swg21678312] \n 5. \n 6. \n 7. Stack dump In hang situations, collect 4-5 stack dumps of the threads running in the DataFlowEngine with a gap of about 10 seconds each.\n Use these commands, where <PID> is the process ID of the DataFlowEngine:\n \n \n * procstack <PID> (On AIX)\n * pstack <PID> (On Linux, Solaris)\n \n \n \n \n 8. \n 9. \n 10. Project Interchange files for the problematic flow/set/ESQL/model\n * You can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.\n See: Exporting files from the Workbench [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ax20230_.htm?cp=SSMKHH_9.0.0%2F1-2-4] \n \n \n 11. \n 12. \n 13. Traces If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321] can be used to gain a better understanding of the problem. * A service level trace [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321#2] is intended to be provided to IBM Support to assist in the diagnosis of your issue. Please run the service level trace independently and not while the above other items are being collected\n \n \n 14. \n 15. \n 16. General Broker information\n If the mqsidc tool was not run, then capture this information manually * Record the IBM Integration Bus or WebSphere Message Broker version, release, and maintenance level.\n This can be captured using the command 'mqsiservice -v'..\n * Record the operating system version, release, and maintenance level.\n * Record the version, release, and maintenance level of any related products and components for the problematic application.\n * Collect the local error log. On UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.\n See: Configuring the syslog daemon [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/an04230_.htm]\n * Collect the Standard Output/Error logs.\n WMB writes information to both STDOUT and STDERR. These files are located under the Message Broker workpath.\n See: Standard System Logs [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/au14165_.htm]\n \n \n 17. \n 18. \n 19. Additional information * Output of command: mqsilist -r -d2 \n \n \n\n\n\nATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!\nWhen sending data to IBM, be sure to update your PMR or send a note with the following information:\n\n * Tell us what errors you saw, where you saw them, and what time they happened Let us know if you made any changes to WebSphere Message Broker or the system before the problem Share any other observations which you think will help us to better understand the problem \n\n\n\nSTEP 3: SUBMIT DATA TO IBM\n\n * Use IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM.\n * Send your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis.\n\n\n\n\n\nPlease see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support.\n\n\n\nBack to top\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Performance AIX, HP-UX, Linux, Solaris, Windows 8.0 All Editions" ]

[ [ "2a", " SUBSCRIBE You can track all active APARs for this component. APAR STATUS" ], [ "2b", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "2c", " * On AIX only, memory corruption can occur after an exception" ], [ "2d", " condition, such as a timeout, in the HTTPRequest node." ], [ "2e", " This then causes a coredump and a restart of the integration" ], [ "2f", " server." ], [ "2g", "The stack in the coredump can vary, but is most likely" ], [ "2h", " to show a segfault following a native throw:" ], [ "2i", " ImbWSRequestNode.ImbBufferedStringBase" ], [ "2j", " char,std::char_traits,unsigned" ], [ "2k", " short,24,128>::__dftdt()(??) at 0x900000016273b40" ], [ "2l", " invokedtr.__Invoke__Destructor() at 0x9000000006ef9e4" ], [ "2m", " __DoThrowV6() at 0x9000000006f2dcc" ], [ "2n", " ImbRecoverableException::throwThis()(??) at 0x900000000f026d0" ], [ "2o", " ImbWSRequestNode::evaluate(const ImbMessageAssembly&,const" ], [ "2p", " ImbDataFlowTerminal*) LOCAL FIX PROBLEM SUMMARY" ], [ "2q", " * ****************************************************************" ], [ "2r", " USERS AFFECTED:" ], [ "2s", " All users of IBM Integration Bus V9.0 on AIX, who use the" ], [ "2t", " HTTPRequest node." ], [ "2u", " Platforms affected:" ], [ "2v", " AIX" ], [ "2w", " ****************************************************************" ], [ "2x", " PROBLEM DESCRIPTION:" ], [ "2y", " On AIX only, memory corruption can occur after an exception" ], [ "2z", " condition, such as a timeout, in the HTTPRequest node." ], [ "2aa", " This then causes a coredump and a restart of the integration" ], [ "2ab", " server." ], [ "2ac", "The stack in the coredump can vary, but is most likely" ], [ "2ad", " to show a segfault following a native throw:" ], [ "2ae", " ImbWSRequestNode.ImbBufferedStringBase" ], [ "2af", " char,std::char_traits,unsigned" ], [ "2ag", " short,24,128>::__dftdt()(??) at 0x900000016273b40" ], [ "2ah", " invokedtr.__Invoke__Destructor() at 0x9000000006ef9e4" ], [ "2ai", " __DoThrowV6() at 0x9000000006f2dcc" ], [ "2aj", " ImbRecoverableException::throwThis()(??) at 0x900000000f026d0" ], [ "2ak", " ImbWSRequestNode::evaluate(const ImbMessageAssembly&,const" ], [ "2al", " ImbDataFlowTerminal*)" ], [ "2am", " There are a number of resource name changes between WebSphere" ], [ "2an", " Message Broker and IBM Integration Bus Version 9.0. For details" ], [ "2ao", " visit" ], [ "2ap", " http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e" ], [ "2aq", " tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm] PROBLEM CONCLUSION" ], [ "2ar", " * The product no longer encounters memory corruption following an" ], [ "2as", " exception in the HTTPRequest node." ], [ "2at", " ---------------------------------------------------------------" ], [ "2au", " The fix is targeted for delivery in the following PTFs:" ], [ "2av", " Version Maintenance Level" ], [ "2aw", " v9.0 9.0.0.3" ], [ "2ax", " The latest available maintenance can be obtained from:" ], [ "2ay", " http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]" ], [ "2az", " If the maintenance level is not yet available, information on" ], [ "2ba", " its planned availability can be found on:" ], [ "2bb", " http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]" ], [ "2bc", " --------------------------------------------------------------- TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "2bd", " * APAR NUMBER" ], [ "2be", " IT00989" ], [ "2bf", " * REPORTED COMPONENT NAME" ], [ "2bg", " INTEGRATION BUS" ], [ "2bh", " * REPORTED COMPONENT ID" ], [ "2bi", " 5724J0530" ], [ "2bj", " * REPORTED RELEASE" ], [ "2bk", " 900" ], [ "2bl", " * STATUS" ], [ "2bm", " CLOSED PER" ], [ "2bn", " * PE" ], [ "2bo", " NoPE" ], [ "2bp", " * HIPER" ], [ "2bq", " NoHIPER" ], [ "2br", " * SPECIAL ATTENTION" ], [ "2bs", " NoSpecatt / Xsystem" ], [ "2bt", " * SUBMITTED DATE" ], [ "2bu", " 2014-04-11" ], [ "2bv", " * CLOSED DATE" ], [ "2bw", " 2014-07-31" ], [ "2bx", " * LAST MODIFIED DATE" ], [ "2by", " 2014-07-31" ], [ "2bz", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "2ca", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "2cb", " * FIXED COMPONENT NAME" ], [ "2cc", " INTEGRATION BUS" ], [ "2cd", " * FIXED COMPONENT ID" ], [ "2ce", " 5724J0530" ], [ "2cf", "APPLICABLE COMPONENT LEVELS" ], [ "2cg", " * R900 PSY" ], [ "2ch", " UP" ] ]

[ "0e", "0g", "0n", "0q", "0t", "0u", "1e", "1g", "1p", "1q", "1s", "1y", "2b", "2c", "2d", "2x", "2y", "2z", "3e", "3i", "3m", "3p", "3s", "4f", "4g", "4h", "4i", "4p", "4s", "4t", "4u" ]

[ " A FIX IS AVAILABLE\nWebSphere Message Broker V7.0 - Fix Pack 7.0.0.8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041187]\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 * When the HTTPRequest node is used with a HTTP proxy location\n set and \"Follow HTTP(S) redirection\" enabled redirects are not\n followed if the initial remote server is ssl enabled.\n \n \n \n \n \n \n \n \n Additional Symptom(s) Search Keyword(s): SSL HTTPRequest\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of WebSphere Message Broker V7.0 or higher and IBM\n Integration Bus V9.0 using HTTPS proxy servers with the\n HTTPRequest or SOAP Request Nodes.\n \n \n Platforms affected:\n z/OS, MultiPlatform\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n When the HTTPRequest or SOAPRequest nodes are used with a HTTP\n proxy location\n set and \"Follow HTTP(S) redirection\" enabled redirects are not\n followed if the initial remote server is ssl enabled.\n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The HTTPRequest and SOAPRequest Nodes have been updated so the\n redirects are followed when using a HTTP proxy and SSL.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v7.0 7.0.0.8\n v8.0 8.0.0.6\n v9.0 9.0.0.3\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available, information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT01504\n \n \n * REPORTED COMPONENT NAME\n WEB MESSAGE BRO\n \n \n * REPORTED COMPONENT ID\n 5724J0510\n \n \n * REPORTED RELEASE\n 700\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-05-02\n \n \n * CLOSED DATE\n 2014-07-31\n \n \n * LAST MODIFIED DATE\n 2014-07-31\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 WEB MESSAGE BRO\n \n \n * FIXED COMPONENT ID\n 5724J0510\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R700 PSY\n UP", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * The percentage character of a percentage-encoded part is getting\n encoded again by the HTTPRequest/SOAPrequest nodes\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of IBM integration Bus V9.0 and V10.0 using the\n HTTPRequest node or the SOAPRequest node.\n \n \n Platforms affected:\n z/OS, MultiPlatform\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n If a percentage character(%) appears in a percentage-encoded\n part of a request URI it is incorrectly getting re-encoded by\n HTTPRequest and SOAPrequest nodes.\n \n \n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The product no longer double encodes percent characters if they\n appear in an encoded part of a request URI.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v10.0 10.0.0.6\n v9.0 9.0.0.7\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available,information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT15787\n \n \n * REPORTED COMPONENT NAME\n INTEGRATION BUS\n \n \n * REPORTED COMPONENT ID\n 5724J0530\n \n \n * REPORTED RELEASE\n 900\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 2016-06-20\n \n \n * CLOSED DATE\n 2016-08-17\n \n \n * LAST MODIFIED DATE\n 2016-08-17\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 INTEGRATION BUS\n \n \n * FIXED COMPONENT ID\n 5724J0530\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R900 PSY\n UP", " SUBSCRIBE\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 * On AIX only, memory corruption can occur after an exception\n condition, such as a timeout, in the HTTPRequest node.\n \n This then causes a coredump and a restart of the integration\n server. The stack in the coredump can vary, but is most likely\n to show a segfault following a native throw:\n \n ImbWSRequestNode.ImbBufferedStringBase\n char,std::char_traits,unsigned\n short,24,128>::__dftdt()(??) at 0x900000016273b40\n invokedtr.__Invoke__Destructor() at 0x9000000006ef9e4\n __DoThrowV6() at 0x9000000006f2dcc\n ImbRecoverableException::throwThis()(??) at 0x900000000f026d0\n ImbWSRequestNode::evaluate(const ImbMessageAssembly&,const\n ImbDataFlowTerminal*)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of IBM Integration Bus V9.0 on AIX, who use the\n HTTPRequest node.\n \n \n Platforms affected:\n AIX\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n On AIX only, memory corruption can occur after an exception\n condition, such as a timeout, in the HTTPRequest node.\n \n This then causes a coredump and a restart of the integration\n server. The stack in the coredump can vary, but is most likely\n to show a segfault following a native throw:\n \n ImbWSRequestNode.ImbBufferedStringBase\n char,std::char_traits,unsigned\n short,24,128>::__dftdt()(??) at 0x900000016273b40\n invokedtr.__Invoke__Destructor() at 0x9000000006ef9e4\n __DoThrowV6() at 0x9000000006f2dcc\n ImbRecoverableException::throwThis()(??) at 0x900000000f026d0\n ImbWSRequestNode::evaluate(const ImbMessageAssembly&,const\n ImbDataFlowTerminal*)\n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The product no longer encounters memory corruption following an\n exception in the HTTPRequest node.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v9.0 9.0.0.3\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available, information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT00989\n \n \n * REPORTED COMPONENT NAME\n INTEGRATION BUS\n \n \n * REPORTED COMPONENT ID\n 5724J0530\n \n \n * REPORTED RELEASE\n 900\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 2014-04-11\n \n \n * CLOSED DATE\n 2014-07-31\n \n \n * LAST MODIFIED DATE\n 2014-07-31\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 INTEGRATION BUS\n \n \n * FIXED COMPONENT ID\n 5724J0530\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R900 PSY\n UP", " SUBSCRIBE\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 * HTTPINPUT/REQUEST NODES SHOULD ALLOW TWO CONNECTION HEADERS\n WHENCLOSE IS SPECIFIED (BACKPORT IC59901 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC59901])\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of WebSphere Message Broker who *\n * use the HTTPRequest node. *\n ****************************************************************\n * PROBLEM DESCRIPTION: WebSphere Message Broker issues a *\n * BIP3157 message when it receives two *\n * 'connection' headers in the response *\n * to a request from a HTTPRequest node. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n WebSphere Message Broker issues a BIP3157 message when it\n receives two 'connection' headers in the response to a\n request from a HTTPRequest node.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * WebSphere Message Broker has been modified so that it allows\n two or more connection headers in the response to requests\n from the HTTPRequest node.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IZ55783\n \n \n * REPORTED COMPONENT NAME\n MSSG BROKER AIX\n \n \n * REPORTED COMPONENT ID\n 5724J0501\n \n \n * REPORTED RELEASE\n 100\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 2009-07-22\n \n \n * CLOSED DATE\n 2009-07-30\n \n \n * LAST MODIFIED DATE\n 2009-07-30\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 MSSG BROKER AIX\n \n \n * FIXED COMPONENT ID\n 5724J0501\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R100 PSY\n UP", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You are experiencing High CPU and Performance problems in IBM Integration Bus (IIB) or WebSphere Message Broker (WMB). You would like to know what documentation you must collect (MustGather) so that the IBM Integration Bus / WebSphere Message Broker 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\nRESOLVING THE PROBLEM\n\n\n\nSTEP 1: SELF-GUIDED TROUBLESHOOTING\n\n 1. Message flow accounting and statistics [http://www.ibm.com/developerworks/websphere/library/techarticles/0710_piatek/0710_piatek.html] can be started and viewed in IBM Integration Explorer to monitor the message flows processing messages when such a problem is experienced. Also check the following example in the Knowledge Center. [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac19050_.htm] \n By reviewing the data, you can isolate the problem down to a specific message flow node where the problem may be occurring. For example: average elapsed time (in milliseconds), average CPU time and the number of times a node is invoked can help you identify a particular node that may be a bottleneck. \n 2. \n 3. Check for known issues:\n IIB diagnostic tools guide [http://www.ibm.com/support/knowledgecenter/en/SSKM8N/pdguides/clientDiagnostics.html?sc=_latest]\n How to use the flow analysis to find further performance problems [https://developer.ibm.com/integration/blog/2014/03/20/how-to-use-the-flow-analysis-to-find-further-performance-problems/]\n IIB and WMB FAQ for memory [http://www.ibm.com/support/docview.wss?uid=swg21665926&acss=dakc]\n Dynamic guide to help troubleshooting Message Broker [https://developer.ibm.com/integration/docs/ibm-integration-bus/troubleshooting/dynamic-problem-determination-guides/]\n Troubleshooting performance problems [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bj28660_.htm?lang=en]\n Message splitter pattern [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.pattern.mbi.doc/mbi/ms/overview.htm?lang=en]\n [http://www.ibm.com/software/htp/cics/tserver/support/]IBM Integration Bus support site [https://www-947.ibm.com/support/entry/myportal/product/websphere/ibm_integration_bus?productContext=-1766202334]\n \n\n\n\nSTEP 2: COLLECT DATA\n\n 1. mqsidc\n See: mqsidc usage instructions [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bu46012_.htm]\n * This command line tool is only available for WMB 7.0.0.5+, WMB 8.0.0.1+, IIB 9.0.0.0+, and IIB 10.0.0.0+.\n * When running the tool, select the option for 'Broker Collector', when prompted.\n \n \n 2. \n 3. \n 4. Message flow accounting and statistics\n See: Procedure for collecting accounting and statistics data as XML messages [http://www.ibm.com/support/docview.wss?uid=swg21678313] [http://www.ibm.com/support/docview.wss?uid=swg21678312] \n 5. \n 6. \n 7. Stack dump In hang situations, collect 4-5 stack dumps of the threads running in the DataFlowEngine with a gap of about 10 seconds each.\n Use these commands, where <PID> is the process ID of the DataFlowEngine:\n \n \n * procstack <PID> (On AIX)\n * pstack <PID> (On Linux, Solaris)\n \n \n \n \n 8. \n 9. \n 10. Project Interchange files for the problematic flow/set/ESQL/model\n * You can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.\n See: Exporting files from the Workbench [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ax20230_.htm?cp=SSMKHH_9.0.0%2F1-2-4] \n \n \n 11. \n 12. \n 13. Traces If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321] can be used to gain a better understanding of the problem. * A service level trace [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321#2] is intended to be provided to IBM Support to assist in the diagnosis of your issue. Please run the service level trace independently and not while the above other items are being collected\n \n \n 14. \n 15. \n 16. General Broker information\n If the mqsidc tool was not run, then capture this information manually * Record the IBM Integration Bus or WebSphere Message Broker version, release, and maintenance level.\n This can be captured using the command 'mqsiservice -v'..\n * Record the operating system version, release, and maintenance level.\n * Record the version, release, and maintenance level of any related products and components for the problematic application.\n * Collect the local error log. On UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.\n See: Configuring the syslog daemon [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/an04230_.htm]\n * Collect the Standard Output/Error logs.\n WMB writes information to both STDOUT and STDERR. These files are located under the Message Broker workpath.\n See: Standard System Logs [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/au14165_.htm]\n \n \n 17. \n 18. \n 19. Additional information * Output of command: mqsilist -r -d2 \n \n \n\n\n\nATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!\nWhen sending data to IBM, be sure to update your PMR or send a note with the following information:\n\n * Tell us what errors you saw, where you saw them, and what time they happened Let us know if you made any changes to WebSphere Message Broker or the system before the problem Share any other observations which you think will help us to better understand the problem \n\n\n\nSTEP 3: SUBMIT DATA TO IBM\n\n * Use IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM.\n * Send your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis.\n\n\n\n\n\nPlease see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support.\n\n\n\nBack to top\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Performance AIX, HP-UX, Linux, Solaris, Windows 8.0 All Editions" ]

[ [ "3a", " SUBSCRIBE You can track all active APARs for this component. APAR STATUS" ], [ "3b", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "3c", " * HTTPINPUT/REQUEST NODES SHOULD ALLOW TWO CONNECTION HEADERS" ], [ "3d", " WHENCLOSE IS SPECIFIED (BACKPORT IC59901 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC59901]) LOCAL FIX PROBLEM SUMMARY" ], [ "3e", " * ****************************************************************" ], [ "3f", " * USERS AFFECTED: All users of WebSphere Message Broker who *" ], [ "3g", " * use the HTTPRequest node. *" ], [ "3h", " ****************************************************************" ], [ "3i", " * PROBLEM DESCRIPTION: WebSphere Message Broker issues a *" ], [ "3j", " * BIP3157 message when it receives two *" ], [ "3k", " * 'connection' headers in the response *" ], [ "3l", " * to a request from a HTTPRequest node. *" ], [ "3m", " ****************************************************************" ], [ "3n", " * RECOMMENDATION: *" ], [ "3o", " ****************************************************************" ], [ "3p", " WebSphere Message Broker issues a BIP3157 message when it" ], [ "3q", " receives two 'connection' headers in the response to a" ], [ "3r", " request from a HTTPRequest node. PROBLEM CONCLUSION" ], [ "3s", " * WebSphere Message Broker has been modified so that it allows" ], [ "3t", " two or more connection headers in the response to requests" ], [ "3u", " from the HTTPRequest node. TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "3v", " * APAR NUMBER" ], [ "3w", " IZ55783" ], [ "3x", " * REPORTED COMPONENT NAME" ], [ "3y", " MSSG BROKER AIX" ], [ "3z", " * REPORTED COMPONENT ID" ], [ "3aa", " 5724J0501" ], [ "3ab", " * REPORTED RELEASE" ], [ "3ac", " 100" ], [ "3ad", " * STATUS" ], [ "3ae", " CLOSED PER" ], [ "3af", " * PE" ], [ "3ag", " NoPE" ], [ "3ah", " * HIPER" ], [ "3ai", " NoHIPER" ], [ "3aj", " * SPECIAL ATTENTION" ], [ "3ak", " NoSpecatt" ], [ "3al", " * SUBMITTED DATE" ], [ "3am", " 2009-07-22" ], [ "3an", " * CLOSED DATE" ], [ "3ao", " 2009-07-30" ], [ "3ap", " * LAST MODIFIED DATE" ], [ "3aq", " 2009-07-30" ], [ "3ar", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "3as", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "3at", " * FIXED COMPONENT NAME" ], [ "3au", " MSSG BROKER AIX" ], [ "3av", " * FIXED COMPONENT ID" ], [ "3aw", " 5724J0501" ], [ "3ax", "APPLICABLE COMPONENT LEVELS" ], [ "3ay", " * R100 PSY" ], [ "3az", " UP" ] ]

[ "0e", "0g", "0n", "0q", "0t", "0u", "1e", "1g", "1p", "1q", "1s", "1y", "2b", "2c", "2d", "2x", "2y", "2z", "3e", "3i", "3m", "3p", "3s", "4f", "4g", "4h", "4i", "4p", "4s", "4t", "4u" ]

[ " A FIX IS AVAILABLE\nWebSphere Message Broker V7.0 - Fix Pack 7.0.0.8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041187]\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 * When the HTTPRequest node is used with a HTTP proxy location\n set and \"Follow HTTP(S) redirection\" enabled redirects are not\n followed if the initial remote server is ssl enabled.\n \n \n \n \n \n \n \n \n Additional Symptom(s) Search Keyword(s): SSL HTTPRequest\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of WebSphere Message Broker V7.0 or higher and IBM\n Integration Bus V9.0 using HTTPS proxy servers with the\n HTTPRequest or SOAP Request Nodes.\n \n \n Platforms affected:\n z/OS, MultiPlatform\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n When the HTTPRequest or SOAPRequest nodes are used with a HTTP\n proxy location\n set and \"Follow HTTP(S) redirection\" enabled redirects are not\n followed if the initial remote server is ssl enabled.\n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The HTTPRequest and SOAPRequest Nodes have been updated so the\n redirects are followed when using a HTTP proxy and SSL.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v7.0 7.0.0.8\n v8.0 8.0.0.6\n v9.0 9.0.0.3\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available, information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT01504\n \n \n * REPORTED COMPONENT NAME\n WEB MESSAGE BRO\n \n \n * REPORTED COMPONENT ID\n 5724J0510\n \n \n * REPORTED RELEASE\n 700\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-05-02\n \n \n * CLOSED DATE\n 2014-07-31\n \n \n * LAST MODIFIED DATE\n 2014-07-31\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 WEB MESSAGE BRO\n \n \n * FIXED COMPONENT ID\n 5724J0510\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R700 PSY\n UP", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * The percentage character of a percentage-encoded part is getting\n encoded again by the HTTPRequest/SOAPrequest nodes\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of IBM integration Bus V9.0 and V10.0 using the\n HTTPRequest node or the SOAPRequest node.\n \n \n Platforms affected:\n z/OS, MultiPlatform\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n If a percentage character(%) appears in a percentage-encoded\n part of a request URI it is incorrectly getting re-encoded by\n HTTPRequest and SOAPrequest nodes.\n \n \n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The product no longer double encodes percent characters if they\n appear in an encoded part of a request URI.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v10.0 10.0.0.6\n v9.0 9.0.0.7\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available,information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT15787\n \n \n * REPORTED COMPONENT NAME\n INTEGRATION BUS\n \n \n * REPORTED COMPONENT ID\n 5724J0530\n \n \n * REPORTED RELEASE\n 900\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 2016-06-20\n \n \n * CLOSED DATE\n 2016-08-17\n \n \n * LAST MODIFIED DATE\n 2016-08-17\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 INTEGRATION BUS\n \n \n * FIXED COMPONENT ID\n 5724J0530\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R900 PSY\n UP", " SUBSCRIBE\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 * On AIX only, memory corruption can occur after an exception\n condition, such as a timeout, in the HTTPRequest node.\n \n This then causes a coredump and a restart of the integration\n server. The stack in the coredump can vary, but is most likely\n to show a segfault following a native throw:\n \n ImbWSRequestNode.ImbBufferedStringBase\n char,std::char_traits,unsigned\n short,24,128>::__dftdt()(??) at 0x900000016273b40\n invokedtr.__Invoke__Destructor() at 0x9000000006ef9e4\n __DoThrowV6() at 0x9000000006f2dcc\n ImbRecoverableException::throwThis()(??) at 0x900000000f026d0\n ImbWSRequestNode::evaluate(const ImbMessageAssembly&,const\n ImbDataFlowTerminal*)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of IBM Integration Bus V9.0 on AIX, who use the\n HTTPRequest node.\n \n \n Platforms affected:\n AIX\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n On AIX only, memory corruption can occur after an exception\n condition, such as a timeout, in the HTTPRequest node.\n \n This then causes a coredump and a restart of the integration\n server. The stack in the coredump can vary, but is most likely\n to show a segfault following a native throw:\n \n ImbWSRequestNode.ImbBufferedStringBase\n char,std::char_traits,unsigned\n short,24,128>::__dftdt()(??) at 0x900000016273b40\n invokedtr.__Invoke__Destructor() at 0x9000000006ef9e4\n __DoThrowV6() at 0x9000000006f2dcc\n ImbRecoverableException::throwThis()(??) at 0x900000000f026d0\n ImbWSRequestNode::evaluate(const ImbMessageAssembly&,const\n ImbDataFlowTerminal*)\n \n There are a number of resource name changes between WebSphere\n Message Broker and IBM Integration Bus Version 9.0. For details\n visit\n http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e\n tools.mft.doc/bb23814_.htm [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/bb23814_.htm]\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The product no longer encounters memory corruption following an\n exception in the HTTPRequest node.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v9.0 9.0.0.3\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available, information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT00989\n \n \n * REPORTED COMPONENT NAME\n INTEGRATION BUS\n \n \n * REPORTED COMPONENT ID\n 5724J0530\n \n \n * REPORTED RELEASE\n 900\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 2014-04-11\n \n \n * CLOSED DATE\n 2014-07-31\n \n \n * LAST MODIFIED DATE\n 2014-07-31\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 INTEGRATION BUS\n \n \n * FIXED COMPONENT ID\n 5724J0530\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R900 PSY\n UP", " SUBSCRIBE\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 * HTTPINPUT/REQUEST NODES SHOULD ALLOW TWO CONNECTION HEADERS\n WHENCLOSE IS SPECIFIED (BACKPORT IC59901 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC59901])\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of WebSphere Message Broker who *\n * use the HTTPRequest node. *\n ****************************************************************\n * PROBLEM DESCRIPTION: WebSphere Message Broker issues a *\n * BIP3157 message when it receives two *\n * 'connection' headers in the response *\n * to a request from a HTTPRequest node. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n WebSphere Message Broker issues a BIP3157 message when it\n receives two 'connection' headers in the response to a\n request from a HTTPRequest node.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * WebSphere Message Broker has been modified so that it allows\n two or more connection headers in the response to requests\n from the HTTPRequest node.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IZ55783\n \n \n * REPORTED COMPONENT NAME\n MSSG BROKER AIX\n \n \n * REPORTED COMPONENT ID\n 5724J0501\n \n \n * REPORTED RELEASE\n 100\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 2009-07-22\n \n \n * CLOSED DATE\n 2009-07-30\n \n \n * LAST MODIFIED DATE\n 2009-07-30\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 MSSG BROKER AIX\n \n \n * FIXED COMPONENT ID\n 5724J0501\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R100 PSY\n UP", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You are experiencing High CPU and Performance problems in IBM Integration Bus (IIB) or WebSphere Message Broker (WMB). You would like to know what documentation you must collect (MustGather) so that the IBM Integration Bus / WebSphere Message Broker 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\nRESOLVING THE PROBLEM\n\n\n\nSTEP 1: SELF-GUIDED TROUBLESHOOTING\n\n 1. Message flow accounting and statistics [http://www.ibm.com/developerworks/websphere/library/techarticles/0710_piatek/0710_piatek.html] can be started and viewed in IBM Integration Explorer to monitor the message flows processing messages when such a problem is experienced. Also check the following example in the Knowledge Center. [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac19050_.htm] \n By reviewing the data, you can isolate the problem down to a specific message flow node where the problem may be occurring. For example: average elapsed time (in milliseconds), average CPU time and the number of times a node is invoked can help you identify a particular node that may be a bottleneck. \n 2. \n 3. Check for known issues:\n IIB diagnostic tools guide [http://www.ibm.com/support/knowledgecenter/en/SSKM8N/pdguides/clientDiagnostics.html?sc=_latest]\n How to use the flow analysis to find further performance problems [https://developer.ibm.com/integration/blog/2014/03/20/how-to-use-the-flow-analysis-to-find-further-performance-problems/]\n IIB and WMB FAQ for memory [http://www.ibm.com/support/docview.wss?uid=swg21665926&acss=dakc]\n Dynamic guide to help troubleshooting Message Broker [https://developer.ibm.com/integration/docs/ibm-integration-bus/troubleshooting/dynamic-problem-determination-guides/]\n Troubleshooting performance problems [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bj28660_.htm?lang=en]\n Message splitter pattern [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.pattern.mbi.doc/mbi/ms/overview.htm?lang=en]\n [http://www.ibm.com/software/htp/cics/tserver/support/]IBM Integration Bus support site [https://www-947.ibm.com/support/entry/myportal/product/websphere/ibm_integration_bus?productContext=-1766202334]\n \n\n\n\nSTEP 2: COLLECT DATA\n\n 1. mqsidc\n See: mqsidc usage instructions [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bu46012_.htm]\n * This command line tool is only available for WMB 7.0.0.5+, WMB 8.0.0.1+, IIB 9.0.0.0+, and IIB 10.0.0.0+.\n * When running the tool, select the option for 'Broker Collector', when prompted.\n \n \n 2. \n 3. \n 4. Message flow accounting and statistics\n See: Procedure for collecting accounting and statistics data as XML messages [http://www.ibm.com/support/docview.wss?uid=swg21678313] [http://www.ibm.com/support/docview.wss?uid=swg21678312] \n 5. \n 6. \n 7. Stack dump In hang situations, collect 4-5 stack dumps of the threads running in the DataFlowEngine with a gap of about 10 seconds each.\n Use these commands, where <PID> is the process ID of the DataFlowEngine:\n \n \n * procstack <PID> (On AIX)\n * pstack <PID> (On Linux, Solaris)\n \n \n \n \n 8. \n 9. \n 10. Project Interchange files for the problematic flow/set/ESQL/model\n * You can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.\n See: Exporting files from the Workbench [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ax20230_.htm?cp=SSMKHH_9.0.0%2F1-2-4] \n \n \n 11. \n 12. \n 13. Traces If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321] can be used to gain a better understanding of the problem. * A service level trace [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321#2] is intended to be provided to IBM Support to assist in the diagnosis of your issue. Please run the service level trace independently and not while the above other items are being collected\n \n \n 14. \n 15. \n 16. General Broker information\n If the mqsidc tool was not run, then capture this information manually * Record the IBM Integration Bus or WebSphere Message Broker version, release, and maintenance level.\n This can be captured using the command 'mqsiservice -v'..\n * Record the operating system version, release, and maintenance level.\n * Record the version, release, and maintenance level of any related products and components for the problematic application.\n * Collect the local error log. On UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.\n See: Configuring the syslog daemon [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/an04230_.htm]\n * Collect the Standard Output/Error logs.\n WMB writes information to both STDOUT and STDERR. These files are located under the Message Broker workpath.\n See: Standard System Logs [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/au14165_.htm]\n \n \n 17. \n 18. \n 19. Additional information * Output of command: mqsilist -r -d2 \n \n \n\n\n\nATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!\nWhen sending data to IBM, be sure to update your PMR or send a note with the following information:\n\n * Tell us what errors you saw, where you saw them, and what time they happened Let us know if you made any changes to WebSphere Message Broker or the system before the problem Share any other observations which you think will help us to better understand the problem \n\n\n\nSTEP 3: SUBMIT DATA TO IBM\n\n * Use IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM.\n * Send your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis.\n\n\n\n\n\nPlease see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support.\n\n\n\nBack to top\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Performance AIX, HP-UX, Linux, Solaris, Windows 8.0 All Editions" ]

[ [ "4a", " TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "4b", " You are experiencing High CPU and Performance problems in IBM Integration Bus (IIB) or WebSphere Message Broker (WMB)." ], [ "4c", "You would like to know what documentation you must collect (MustGather) so that the IBM Integration Bus / WebSphere Message Broker Support team can diagnose your problem." ], [ "4d", "If you gather this documentation before contacting support it will expedite the troubleshooting process, and save you time." ], [ "4e", "RESOLVING THE PROBLEM" ], [ "4f", "STEP 1: SELF-GUIDED TROUBLESHOOTING 1." ], [ "4g", "Message flow accounting and statistics [http://www.ibm.com/developerworks/websphere/library/techarticles/0710_piatek/0710_piatek.html] can be started and viewed in IBM Integration Explorer to monitor the message flows processing messages when such a problem is experienced." ], [ "4h", "Also check the following example in the Knowledge Center. [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac19050_.htm]" ], [ "4i", " By reviewing the data, you can isolate the problem down to a specific message flow node where the problem may be occurring." ], [ "4j", "For example: average elapsed time (in milliseconds), average CPU time and the number of times a node is invoked can help you identify a particular node that may be a bottleneck. 2. 3." ], [ "4k", "Check for known issues:" ], [ "4l", " IIB diagnostic tools guide [http://www.ibm.com/support/knowledgecenter/en/SSKM8N/pdguides/clientDiagnostics.html?sc=_latest]" ], [ "4m", " How to use the flow analysis to find further performance problems [https://developer.ibm.com/integration/blog/2014/03/20/how-to-use-the-flow-analysis-to-find-further-performance-problems/]" ], [ "4n", " IIB and WMB FAQ for memory [http://www.ibm.com/support/docview.wss?uid=swg21665926&acss=dakc]" ], [ "4o", " Dynamic guide to help troubleshooting Message Broker [https://developer.ibm.com/integration/docs/ibm-integration-bus/troubleshooting/dynamic-problem-determination-guides/]" ], [ "4p", " Troubleshooting performance problems [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bj28660_.htm?lang=en]" ], [ "4q", " Message splitter pattern [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.pattern.mbi.doc/mbi/ms/overview.htm?lang=en]" ], [ "4r", " [http://www.ibm.com/software/htp/cics/tserver/support/]IBM Integration Bus support site [https://www-947.ibm.com/support/entry/myportal/product/websphere/ibm_integration_bus?productContext=-1766202334]" ], [ "4s", "STEP 2: COLLECT DATA" ], [ "4t", " 1. mqsidc" ], [ "4u", " See: mqsidc usage instructions [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bu46012_.htm]" ], [ "4v", " * This command line tool is only available for WMB 7.0.0.5+, WMB 8.0.0.1+, IIB 9.0.0.0+, and IIB 10.0.0.0+." ], [ "4w", " * When running the tool, select the option for 'Broker Collector', when prompted. 2. 3. 4." ], [ "4x", "Message flow accounting and statistics" ], [ "4y", " See: Procedure for collecting accounting and statistics data as XML messages [http://www.ibm.com/support/docview.wss?uid=swg21678313] [http://www.ibm.com/support/docview.wss?uid=swg21678312] 5. 6. 7." ], [ "4z", "Stack dump In hang situations, collect 4-5 stack dumps of the threads running in the DataFlowEngine with a gap of about 10 seconds each." ], [ "4aa", " Use these commands, where <PID> is the process ID of the DataFlowEngine:" ], [ "4ab", " * procstack <PID> (On AIX)" ], [ "4ac", " * pstack <PID> (On Linux, Solaris) 8. 9. 10." ], [ "4ad", "Project Interchange files for the problematic flow/set/ESQL/model" ], [ "4ae", " * You can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support." ], [ "4af", " See: Exporting files from the Workbench [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ax20230_.htm?cp=SSMKHH_9.0.0%2F1-2-4] 11. 12. 13." ], [ "4ag", "Traces If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321] can be used to gain a better understanding of the problem." ], [ "4ah", "* A service level trace [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321#2] is intended to be provided to IBM Support to assist in the diagnosis of your issue." ], [ "4ai", "Please run the service level trace independently and not while the above other items are being collected 14. 15. 16." ], [ "4aj", "General Broker information" ], [ "4ak", " If the mqsidc tool was not run, then capture this information manually * Record the IBM Integration Bus or WebSphere Message Broker version, release, and maintenance level." ], [ "4al", " This can be captured using the command 'mqsiservice -v'.." ], [ "4am", " * Record the operating system version, release, and maintenance level." ], [ "4an", " * Record the version, release, and maintenance level of any related products and components for the problematic application." ], [ "4ao", " * Collect the local error log." ], [ "4ap", "On UNIX and Linux systems, the local error log is the syslog." ], [ "4aq", "The location of your syslog is configured in the syslog daemon." ], [ "4ar", " See: Configuring the syslog daemon [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/an04230_.htm]" ], [ "4as", " * Collect the Standard Output/Error logs." ], [ "4at", " WMB writes information to both STDOUT and STDERR." ], [ "4au", "These files are located under the Message Broker workpath." ], [ "4av", " See: Standard System Logs [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/au14165_.htm] 17. 18. 19." ], [ "4aw", "Additional information * Output of command: mqsilist -r -d2" ], [ "4ax", "ATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!" ], [ "4ay", "When sending data to IBM, be sure to update your PMR or send a note with the following information:" ], [ "4az", " * Tell us what errors you saw, where you saw them, and what time they happened Let us know if you made any changes to WebSphere Message Broker or the system before the problem Share any other observations which you think will help us to better understand the problem" ], [ "4ba", "STEP 3: SUBMIT DATA TO IBM" ], [ "4bb", " * Use IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM." ], [ "4bc", " * Send your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis." ], [ "4bd", "Please see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support." ], [ "4be", "Back to top" ], [ "4bf", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Performance AIX, HP-UX, Linux, Solaris, Windows 8.0 All Editions" ] ]

[ "0e", "0g", "0n", "0q", "0t", "0u", "1e", "1g", "1p", "1q", "1s", "1y", "2b", "2c", "2d", "2x", "2y", "2z", "3e", "3i", "3m", "3p", "3s", "4f", "4g", "4h", "4i", "4p", "4s", "4t", "4u" ]

[ "silent; custom; install; This is not a supported operating system; not supported; operating system; Please check the system requirements; XWindows; RHEL; OUNCE_CONFIG_FILE; custom_install.properties; setup.bin; Installer User Interface Mode Not Supported; silently; installing; installation; AppScan Source; Listening for transport dt_socket at address; 5005; dt_socket TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to silently install IBM Rational AppScan Source Edition on a supported Red Hat Enterprise Linux (RHEL) machine results in error \"This is not a supported operating system. Please check the system requirements and try installing IBM Rational AppScan Source Edition on a supported platform.\" \n\nSYMPTOM\nThe following error occurs when you try to silently install the product:\n\n\n> ./setup.bin -i Silent\nListening for transport dt_socket at address: 5005\nThis is not a supported operating system. Please check the\nsystem requirements and try installing IBM Rational AppScan\nSource Edition on a supported platform.\n\n\n\nCAUSE\nThe \"-i Silent\" option is not a supported. \n\n\n\nENVIRONMENT\nThis installation issue occurs on a supported Red Hat Enterprise Linux machine. \n\nAs of version 8.0.0.2, AppScan Source supports the following RHEL versions: \n\n\nRed Hat Enterprise Linux Version 4 (workstation and server)\nRed Hat Enterprise Linux Version 5 (workstation and server) 32-bit or 64-bit\n\nNote: On 64-bit Linux, Rational AppScan Source Edition runs in 32-bit mode.\n\n\nRESOLVING THE PROBLEM\nTo install AppScan Source for Core on a RHEL machine, you need to have XWindows installed and then run setup.bin to initiate the installation Wizard. \n\n\nIf you do not have XWindows installed and you try to install via the command line by executing \"setup.bin\", you will get an error that states, \"Installer User Interface Mode Not Supported\"; this essentially indicates that XWindows is required to run setup.bin.\n\nTo install any of the other AppScan Source components other than Core, you may use the silent install without XWindows pre-installed. \n\nTo achieve this, create a custom_install.properties file on a Microsoft Windows machine, then distribute that file to as many Linux machines as you want to perform the silent install on. \n\nHere are the installation steps in detail:\n\n\n 1. On a Windows machine, create a new user variable: OUNCE_CONFIG_FILE (Click Start > Control Panel > System > Advanced tab > Environment Variables) and set the value to: \n \n C:\\custom_install.properties\n \n Note: When setting OUNCE_CONFIG_FILE, do not put quotes around the value even if the value contains spaces\n \n \n 2. Next, run setup.exe\n \n When you run the setup.exe, you should get a choice to select whether you want to do a silent install.\n \n You will also be able to select which components will be included in the install. \n \n The only ones available are: \n 3. * Automation \n * Security \n * Command Line Client \n * Dev Plug-in for VS 2003 \n * Dev Plug-in for VS 2005 \n * Dev Plug-in for VS 2008 \n * Dev Plug-in for VS 2010 (version 8.0.0.2 and above) \n * Dev Plug-in for Eclipse and RAD\n \n Upon completion, the custom_install.properties file is created\n \n \n \n \n 4. Distribute the custom_install.properties file to the RHEL machine where you want to install the AppScan Source component. \n \n \n 5. Execute the following command on the RHEL machine to run the silent install: \n \n > setup.bin -f <path_to_file>/custom_install.properties", "ITCAM 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", "TSA; TSAMP; setup.bin; console TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Trying to install TSAMP Operations Console and getting an error message:\n\"Installer User Interface Mode Not Supported\nThe installer cannot run in this UI mode.\" \n\nENVIRONMENT\n# setup.bin -i console\nPreparing to install...\nExtracting the JRE from the installer archive...\nUnpacking the JRE...\nExtracting the installation resources from the installer archive...\nConfiguring the installer for this system's environment...\n\nLaunching installer...\n\nPreparing CONSOLE Mode Installation...\n\n\n\nRESOLVING THE PROBLEM\nThere are only two supported methods for installing the Operations Console (OC): \n\n - You can use a graphical installation program, the so-called installation wizard.\n- You can install the operations console in silent mode, using a response file you generated in a previous wizard-driven installation.\n\nThe Installation Guide includes X Windows as a prerequisite for the OC on Linux and AIX systems.", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PERMANENT RESTRICTION.\n \n \n \n\nERROR DESCRIPTION\n * installation hangs:\n \n Start up GUI (VNCSERVER) and run the setuplinux4zos.bin, and\n InstallShield Wizard hangs at this point:\n \n Finalizing the Vital Product Data Registry. Please wait...\n Progress bar shows 100%, but never appears to complete.\n \n \n \n \n \n\nLOCAL FIX\n * use command line install w/ the -console flag as workaround if\n GUI hangs.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * OM XE for Messaging 6.0 Installer hangs on Red Hat Enterprise\n Linux AS release 4 (Nahant Update 3) Kernel 2.6.9-34.EL on S390\n in GUI mode\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * This is an Installshield defect. Please use console mode by\n using the -console parm w/ the install script.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IY99643\n \n \n * REPORTED COMPONENT NAME\n OMG XE MSG DIST\n \n \n * REPORTED COMPONENT ID\n 5724N1300\n \n \n * REPORTED RELEASE\n 600\n \n \n * STATUS\n CLOSED PRS\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 2007-06-05\n \n \n * CLOSED DATE\n 2007-06-26\n \n \n * LAST MODIFIED DATE\n 2007-06-26\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\nAPPLICABLE COMPONENT LEVELS", "CPIT; Linux; idsldif2db TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When 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>========================================== \nOUTPUT>Setting Directories... \nOUTPUT>Mon Aug 11 08:20:00 SGT 2014 \nOUTPUT>/opt/IBM/cpit/decompressed/TDS/tdsV6.3/tds \nERROR>./install_tds.bin: line 1956: warning: here-document at line 1956 delimited by end-of-file (wanted `/dev/null') \nOUTPUT>ERROR: /opt/IBM/ldap/V6.3/sbin/idsldif2db not found. TDS installation failed. \nProcess completed with exit code: 1 \nERROR in InvokeScripts-function - Terminate the remaining scripts. ***Aborting InvokeScripts-Install function. \n\nDIAGNOSING THE PROBLEM\nFrom the error, it seems like a file is missing from the package (see\"/opt/IBM/ldap/V6.3/sbin/idsldif2db not found. TDS installation failed.\"). \nIf review the installTDS63.sh shell script, the script uses the following method to install ITDS: \n\n====================================================\ncd \"$DirToDecompressTo/$TDSDirName/tdsV6.3/tds\" \npwd \nInstallerName=install_tds.bin \nif [ -e $InstallerName ] ;then \n./$InstallerName -is:silent -options installTDS63.txt -is:log \n$ScriptsDir/log/installtds63.txt\n====================================================\n\nIt is a ITDS 6.3 silent install and encounter the problem.\n\n\nRESOLVING THE PROBLEM\nThe issue is caused by ITDS 6.3 doesn't support ISMP/GUI install on RHEL 6. \n\n\n1. ITDS does not support ISMP/GUI install on RHEL 6 - since RHEL 6 is released after ITDS 6.3. Refer to the link below:\n\nInstalling IBM Tivoli Directory Server Version 6.3 on RHEL 6 operating system [http://www-01.ibm.com/support/docview.wss?uid=swg21599258]\n\n2. ITDS does not support silent install using install_tds.bin (ISMP/GUI installer). Refer to the link below:\n\nInstalling and uninstalling silently on Windows systems [http://www-01.ibm.com/support/knowledgecenter/SSVJJU_6.3.0/com.ibm.IBMDS.doc/install95.htm%23silent]\n\nTo silently install and uninstall on AIX®, Linux, Solaris, and HP-UX (Itanium) systems, use the operating system utilities. \n\nTo fix this issue, please use RHEL 5 since ITDS 6.3 supports ISMP/GUI install on RHEL 5." ]

[ [ "1a", "ITCAM compat-libstdc++ libstdc++ libraries silent_MS_linux.bin launchpad.sh errors TECHNOTE (TROUBLESHOOTING)" ], [ "1b", "THIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):" ], [ "1c", " US English PROBLEM(ABSTRACT)" ], [ "1d", " Using the DC or MS 'launchpad.sh' script results in the following error message:" ], [ "1e", "./setup_MS_lin.bin: line 1926: warning: here-document at line 1926" ], [ "1f", "delimited by end-of-file (wanted `/dev/null') SYMPTOM" ], [ "1g", "The following error is seen running when doing either 'launchpad.sh' or 'silent_MS_linux.bin':" ], [ "1h", " Initializing InstallShield Wizard........" ], [ "1i", "Launching InstallShield Wizard........" ], [ "1j", "./setup_MS_lin.bin: line 1926: warning: here-document at line 1926" ], [ "1k", "delimited by end-of-file (wanted `/dev/null')" ], [ "1l", "The installer is unable to run in graphical mode." ], [ "1m", "Try running the" ], [ "1n", "installer with the -console for -silent flag. CAUSE" ], [ "1o", "Missing Linux system libraries. ENVIRONMENT" ], [ "1p", "Linux - RHEL6.x and RHEL7.x 64-bit versions." ], [ "1q", "RESOLVING THE PROBLEM" ], [ "1r", "This error messag is seen because of some missing Linux libraries." ], [ "1s", "Usually what's missing are the compat-libstdc++ or libstdc++ libraries." ], [ "1t", "Usually the 32-bit version is missing." ], [ "1u", "Use the commands shown below to verify you have them installed, otherwise contact your Linux system administrator and installt these required libraries. [/support/docview.wss?uid=swg21985630&aid=1] [/support/docview.wss?uid=swg21985630&aid=1] [/support/docview.wss?uid=swg21985630&aid=2] [/support/docview.wss?uid=swg21985630&aid=2] PRODUCT ALIAS/SYNONYM" ], [ "1v", " ITCAM4AD ITCAMfAD ITCAM for App Diagnostics" ] ]

[ "1d", "1e", "1f", "1g", "1h", "1l", "1n", "1o", "1s", "1t", "1u" ]

[ "approval workflow; workflow refinement TECHNOTE (FAQ)\n\nQUESTION\n How can I refine a simple workflow for StoredIQ for Legal with branches and buttons? \n\nANSWER\n\n\nPART 2: APPROVAL TASKS AND BUTTONS\nOVERVIEW\nThis recipe is the second part of a series explaining how workflows are designed for StoredIQ for Legal. It shows how to create a simple approval workflow and introduces buttons.\n\nINGREDIENTS\n\n\n * Eclipse [https://eclipse.org/downloads/] with installed Activiti plug-in\n * StoredIQ for Legal\n * The review process definition created in part 1 [http://www.ibm.com/support/docview.wss?uid=swg22001296] of this series\n\nINTRODUCTION\nThis document focuses on workflows in the context of StoredIQ for Legal. For details about workflows in general and Activiti [https://www.activiti.org/], the workflow engine used by StoredIQ for Legal, refer to the Activiti User Guide [http://www.activiti.org/userguide/index.html].\n\nWe start with the workflow process definition generated in the first part [http://www.ibm.com/support/docview.wss?uid=swg22001296] of this series. If you followed that recipe, you can reuse the workflow you created. Alternatively, you can use the definition attached to this document. [https://github.ibm.com/LBREMER/SIQ4L/blob/master/SIQ4L-Workflow-Examples/1%20Review%20Process.bpmn]This definition consists of only one review task for matter closures that can be completed by an attorney. After the attorney completes the review task, the matter is closed by the workflow engine. \n\n[/support/docview.wss?uid=swg22001297&amp;aid=1]\n\nIn this recipe, we will transform the review task into an approval task. In such a task, the attorney has the option to either approve closing the matter or to reject the operation. The matter will only be closed if the attorney approves.\n\nThe recipe continues with the following steps:\n\n * Configuring the process\n * Configuring the approval task\n * Deploying and testing the workflow definition\n\nIf you don't want to generate the process definition yourself and simply want to see how the approval task looks in StoredIQ for Legal, you can download the sample workflow definition attached to this document. With that .bpmn file, you can skip the configuration steps and start directly with the deployment of the workflow definition.\n\nSTEP-BY-STEP\n 1. Configure the ProcessOpen the workflow definition in the Activiti Designer. Click anywhere in the white canvas and select Process in the Properties view. Change the settings as follows:\n \n * Id: approval\n * Name:Approval Process\n * Namespace: Approval\n \n [/support/docview.wss?uid=swg22001297&amp;aid=2] After the namespace is set to Approval, the action that triggers the workflow (matter close, in this example) is only executed when a predefined variable status is set to approved at the time the workflow finishes. If the variable has a different value, the action is not executed. In our example, the matter would stay open.\n \n Process variables are introduced in more detail in a different recipe. For now, it is sufficient to know that each active workflow process contains a set of variables. One of these variables is called status.\n \n \n 2. Configure the TaskTo configure the approval task, we first change the name and ID of the review task. To do this, click the user task and, on the General tab in the Properties view, change the ID and the name of the task to attorney-approval and Matter Close Approval, respectively. Then, switch to the Documentation tab and change the description to Please approve the following action: Matter Close.[/support/docview.wss?uid=swg22001297&amp;aid=3]\n \n As mentioned before, the approval workflow only executes the trigger action when the status variable is set to approved. There are multiple ways to modify variables. Here, we will use a button. Buttons are shown in user tasks and allow the user to complete the task. By default, each task contains a Complete button. However, it is possible to configure custom buttons. The default button is no longer shown when custom buttons are present. For the approval task, we want to create two buttons. One to approve and one to decline the request.\n \n Custom buttons are well-defined form properties of a task. To configure a button, go to the Properties view of the task, click Form, and select New to create a new form property. Set the ID to buttons and the type to enum. Now, you can create one or more buttons in the Form Values section. Each button must have an ID and a name. The ID is the value that is set for the status variable, the name is the display name that is shown on the button.\n \n The order of the buttons in the Activiti Designer determines their order in the user interface. The first button will be highlighted. Create the configuration as shown in the following screen capture.\n \n \n \n \n \n \n [/support/docview.wss?uid=swg22001297&aid=4] [/support/docview.wss?uid=swg22001297&aid=4]\n \n \n 3. Test the workflowDeploy the new workflow definition in StoredIQ for Legal and activate it. Map Matter - Close as starting action. Note that a starting action can be mapped to only one workflow definition at a time. If you completed part one of this series, you probably still have the matter-close starting action mapped to the review workflow. In that case, you need to remove it from the review process before you can assign it to the approval process definition.\n \n To test the workflow, try to close a matter. As a user with the Attorney role, navigate to the approval task. After you assigned the task to yourself, you will see the two buttons. Depending on which button you click, the matter is closed, or not. \n \n [/support/docview.wss?uid=swg22001297&aid=5] [/support/docview.wss?uid=swg22001297&aid=5]\n \n \n \n 4. \n 5. Conclusion and next steps\n 6. In this recipe, we modified the review workflow of the first recipe [http://www.ibm.com/support/docview.wss?uid=swg22001296] and transformed it into an approval workflow. To do so, we configured the namespace property of the process to be Approval. Furthermore, we introduced buttons. These can be used to set the status variable, which defines whether the action that triggered the workflow is executed or not.\n 7. In the third recipe [http://www.ibm.com/support/docview.wss?uid=swg22001298], we will refine the approval workflow and convert it into a workflow requiring multiple approvals. We will use this use case to introduce process variables.\n\nStoredIQ_for_Legal_Review_Process.bpmn [/support/docview.wss?uid=swg22001297&aid=7]StoredIQ_for_Legal_Review_Process.bpmn [/support/docview.wss?uid=swg22001297&aid=6] \n\n[/support/docview.wss?uid=swg22001297&aid=9]StoredIQ_for_Legal_Approval_Process.bpmn [/support/docview.wss?uid=swg22001297&aid=8]", " 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.", "brocade smi agent cim connect switch cimom problem TECHNOTE (FAQ)\n\nQUESTION\n What should I do if the Brocade SMI Agent for FOS is not connecting to the switches I want to monitor? \n\nANSWER\nThe Tivoli Storage Productivity Center CIMOM Agent can be configured to connect to the Brocade SMI Agent for FOS as a data source for switch and fabric data collection and management. If the Brocade SMI Agent is not connected to the switches, then no information about them will be reported back to Tivoli Storage Productivity Center. Listed below are common reasons why the switches may not connect to the Brocade SMI Agent and suggestion to help resolve them.\n\n1.) Firmware Version supported\n\nCheck if the firmware version of the switch added is supported by the SMI Agent version being used. The best document to check that is the Release Notes document shipped with each version of the Brocade SMI Agent. Look for the section \"Supported as proxy connection\". \n\n2.) User and Password problems \n\na) Telnet to the switch from the host where Brocade SMI Agent is running with same password. Telnet must be enabled on the switch.\n\nb) Log onto the switch with this userid and run userconfig. Make sure the user has role of admin and membership of AD 0-255: \n\nadmin> userconfig --show\nAccount name: admin\nRole: admin\nDescription: Administrator\nEnabled: Yes\nPassword Last Change Date: Unknow\nPassword Expiration Date: Not Applicable\nLocked: No\nAD membership: 0-255\nHome AD: 0\n\n3.) Multiple IP addresses on the SMI Agent Host:\n\na) If the host has multiple IP addresses, make sure that SMIAgentConfig.xml is set correct. Run \"ipconfig\" command on the SMIS Agent host.\n\nChange line: \n\n * \n * \n\nto: * \n * \n\nwhere xxx is replaced by the IP address of the active ethernet port. \nb) Telnet to the switch and make sure that the IP address you configured in SMIAgentConfig.xml is pingable from the switch. \n\n4.) Firewall between SMI Agent host and switches \n\nVenting and ARR ports required by the Brocade SMI Agent are not configured. As a result, the ports chosen by the operating system are likely blocked by the firewall: \n\na) Follow this procedure to configure dedicated ports for ARR & Eventing: \n 1. Launch the Brocade SMI Agent Configuration Tool. \n 2. Click ARR & Eventing in the menu tree. The content pane displays the current ARR and eventing ports. \n 3. To change the settings, type new values in the fields. The value must be between 0 and 65535, inclusive. If the value is 0, the SMI Agent dynamically allocates a port during server startup. \n 4. Click Apply. The changes take effect when you restart the server. Click Start Server to restart the server.\n \n\n[/support/docview.wss?uid=swg21426285&amp;aid=1] \n\nBe aware that if there is a firewall between SMIS Agents and Switches you have to define ARR & Eventing Ports. You cannot use the default configuration (0) in this case. \n\n5.) Check RPCD on the switch \n\nThe daemon RPCD must be up and running on the proxy switch. Verify this by logging on to the switch as user “root” and executing the following commands and reviewing the output. \n\na) chkconfig | grep rpcd \nrpcd on \n\nb) ps -eaf | grep rpcd \nroot 938 781 0 Sep27 ? 00:00:04 /fabos/libexec/rpcd -S fcsw -s 0 \n\nc) netstat -an | grep 897 | grep ESTABLISHED \n\nMake sure that there are not more than 19 established connections for this port. If there are, then there are too many other Management Application, such as Brocade Element Manager, connected to the switch. The SMIS Agent needs at least 1 free RPC handle and the overall amount is limited to 20. \n\n6,) Check EVMD on the switch \n\nThe daemon EVMD must be up and running on the proxy switch. Verify this by logging on to the switch as user “root” and executing the following commands and its output: \n\na) chkconfig | grep evmd \nevmd on \n\nb) ps -eaf | grep evmd \nroot 938 781 0 Sep27 ? 00:00:04 /fabos/libexec/evmd -S fcsw -s 0 \n\n\n7.) Check CALD on the switch \n\nThe daemon CALD must be up and running on the proxy switch. Verify this by logging on to the switch as user “root” and executing the following commands and its output: \n\na) chkconfig | grep clad \ncald on \n\nb) ps -eaf | grep cald \nroot 938 781 0 Sep27 ? 00:00:04 /fabos/libexec/clad -S fcsw -s 0 \n\n8.) Log files are needed for investigation if all of these checks are successful. \n\nDeeper analysis is necessary. Brocade support should be engaged to help debug. \n\na) Configure the SMI Agent for additional logging. 1. Launch the Brocade SMI Agent Configuration Tool. \n 2. Click Debugging and Logging in the menu tree. Change the settings according to this picture:\n \n\n[/support/docview.wss?uid=swg21426285&amp;aid=2] \n * \n\n\nb) Zip the following directories and provide to Brocade support. \n\n\\SMIAgent\\agent\\server\\jserver\\logr \n\\SMIAgent\\agent\\server\\jserver\\bin \n\n\n\nCross reference information Segment Product Component Platform Version Edition Storage Management Tivoli Storage Productivity Center AIX, Linux, Windows 5.1, 5.1.1", "AIX FIXES ARE AVAILABLE\nIBM Tivoli Storage Manager (TSM) Client 5.5.4 Downloads and READMEs [http://www-01.ibm.com/support/docview.wss?uid=swg24032025]\nIBM Tivoli Storage Manager (TSM) Client 6.1.5 Downloads and READMEs [http://www-01.ibm.com/support/docview.wss?uid=swg24031696]\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 * When using the backup-archive client to back up a Microsoft\n Windows system, a message similar to the following might be\n issued:\n \n ANS1688I Sparse attributes for 'C:\\somedir\\somefile' cannot be\n backed up correctly because the volume from which the file is\n backed up does not support sparse files.\n \n Although this message should be issued only if the drive does\n not support sparse files, the Windows \"fsutil\" utility reports\n that the drive does support sparse files:\n \n C:\\>fsutil fsinfo volumeinfo c:\n Volume Name :\n Volume Serial Number : 0xf882e3f5\n Max Component Length : 255\n File System Name : NTFS\n Supports Case-sensitive filenames\n Preserves Case of filenames\n Supports Unicode in filenames\n Preserves & Enforces ACL's\n Supports file-based Compression\n Supports Disk Quotas\n Supports Sparse files\n ...\n \n The problem described by this APAR can occur when all of the\n following conditions apply:\n \n - The file is sparse\n - The file cannot be accessed. Possible reasons include, but are\n not necessarily limited to:\n . The file is used exclusively by another application\n (Windows return code 32)\n . Windows security prevents access to the file\n (Windows return code 5)\n \n Under these conditions, even if an EXCLUDE statement is used to\n exclude the file from backup, the client will still examine the\n file, issue this message, then skip the file because it is\n excluded.\n \n Tivoli Storage Manager Versions Affected:\n Windows client 5.5.3 , 6.1.4 , 6.2.2\n The message is erroneously issued with these client\n levels due to the fix for IC68197 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC68197] that was included\n in these levels.\n \n The following extract from a SERVICE trace shows the signature\n for this problem in a \"file in use\" situation :\n \n : cacheobj.cpp ( 977): dbQueryEntry(): DB Query Entry\n Operation - Elapsed time < 1 ms\n : cacheobj.cpp (1002): dbQueryEntry(): Key not found in db.\n : cacheobj.cpp (1015): dbQueryEntry(): exit., result code=104 .\n : ntfileio.cpp (9220): GetFileSecurityInfo(): Get security\n descriptors in new format for 'C:\\somedir\\somefile'\n : ntfileio.cpp (9386): GetFileSecurityInfo(): size of the SDs\n is 168.\n : ntfileio.cpp (5294): fioScanDirEntry(): Obtained NTFS\n File Security Info.\n : ntrc.cpp ( 895): TransWin32RC(): Translated Win32\n RC 32 (0x00000020) from QueryAllocatedRanges(): CreateFile to\n TSM RC 933\n : ntrc.cpp ( 967): TransWin32RC(): SnapshotErrMode = 0;\n dwWin32RC = 32\n \n Initial Impact: Medium\n \n Additional Keywords:\n zz61 zz62\n \n \n \n \n \n\nLOCAL FIX\n * If an ANS1688I message reports a file that resides on a volume\n that supports sparse files, then the message can be safely\n ignored. The message has no impact on whether the file is backed\n up. If the file should be backed up, then correct the condition\n that causes the file to be skipped. For example:\n \n - If a file is skipped because it is open for exclusive use by\n another application, ensure that the application closes the file\n before backing it up. You can also use Open File Support to back\n up the volume on which the files reside.\n \n - If a file is skipped because of an \"access denied\" error, make\n sure the backup runs with an account that has sufficient\n privilege to back up the file.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: Version 5.5.3, 6.1.4, 6.2.2 and 6.2.3 *\n * backup-archive clients running on Microsoft *\n * Windows *\n ****************************************************************\n * PROBLEM DESCRIPTION: See ERROR DESCRIPTION *\n ****************************************************************\n * RECOMMENDATION: Apply fixing level when available. This *\n * problem is currently projected to be fixed *\n * in levels 5.5.4, 6.1.5 and 6.2.4. Note that *\n * until the fixing levels are available, this *\n * information is subject to change at the *\n * discretion of IBM. *\n ****************************************************************\n The ANS1688I message, introduced by the fix for APAR IC68197 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC68197],\n is intended to be displayed when an attempt is made to back\n up a file whose sparse attribute is set, but exists on a file\n system that does not support sparse files. It is triggered if\n the backup-archive client is unable to query the sparse file's\n allocated ranges.\n \n However the backup-archive client might not be able to query a\n sparse file's allocated ranges for reasons other than the file\n system not supporting sparse files. For example, if the file is\n opened for exclusive use by another application so that the\n backup-archive client cannot read it, then the allocated ranges\n cannot be queried.\n \n An error in the backup-archive client code causes ANS1688I to\n be issued without regard for why the allocated ranges cannot be\n queried.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The backup-archive client has been fixed so that the ANS1688I\n message is displayed only if the attempt to query a sparse\n file's allocated ranges is unsuccessful because the file system\n does not support sparse files. If the file cannot be backed up\n for other reasons, such as the file being used exclusively by\n another application, then another message will be issued to\n indicate why the file cannot be backed up.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IC74758\n \n \n * REPORTED COMPONENT NAME\n TSM CLIENT\n \n \n * REPORTED COMPONENT ID\n 5698ISMCL\n \n \n * REPORTED RELEASE\n 55F\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 2011-03-01\n \n \n * CLOSED DATE\n 2011-03-31\n \n \n * LAST MODIFIED DATE\n 2011-03-31\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\nMODULES/MACROS\n * DSMC\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n TSM CLIENT\n \n \n * FIXED COMPONENT ID\n 5698ISMCL\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R55D PSY\n UP\n \n \n * R55F PSY\n UP\n \n \n * R55W PSY\n UP\n \n \n * R61D PSY\n UP\n \n \n * R61F PSY\n UP\n \n \n * R61W PSY\n UP\n \n \n * R62W PSY\n UP", "FileNet domain configuration; firewall; port; timed out; time out; API_UNABLE_TO_USE_CONNECTION; FNRCA0031E TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When setting up a StoredIQ volume for use with FileNet P8 Content Engine Platform it is necessary to enter configuration details of the FileNet Content Engine server and port into forms. When done on the Appstack all required properties are defined in a single form. On the Data Server it is necessary to initially define a FileNet domain configuration and then it is possible to create a volume to use with the FileNet Content Engine.\n\nA connection timed out error may display if the environment is not properly configured. \n\nSYMPTOM\nAfter selecting the OK or Apply button on the configuration page there will be a short delay and then an error message will display. \n\nThe following error message will display in the Appstack volume setup configuration form or on the Dataserver Data sources -> Specify servers -> FileNet domain configurations setup page:\n\n[False, 'java.lang.String', 'fn_listPossibleEDMObjStores] 1664773366 error: java.lang.Exception: com.filenet.api.exception.EngineRuntimeException: FNRCA0031E: API_UNABLE_TO_USE_CONNECTION: The URI for server communication cannot be determined from the connection object <FileNet Content Engine Servername:9080/wsi/FNCEWS40MTOM. Message was: Connection timed out']\n\nThe following error will be reported in the /deepfs/confing/siqsmb0.out file on the Dataserver:\n\nCEConnection][WARNING] CEConnection.validateURI: com.filenet.api.exception.EngineRuntimeException: FNRCA0031E: API_UNABLE_TO_USE_CONNECTION: The URI for server communication cannot be determined from the connection object :9080/wsi/FNCEWS40MTOM. Message was: Connection timed out \n\n\nCAUSE\nThe default port of 9080 for the FileNet Content Engine is closed by default on the firewall of the FileNet P8 Content Engine Platform server.\n\nENVIRONMENT\nDataserver and Appstack\n\nDIAGNOSING THE PROBLEM\nUse the following URL to access the Administration Console for Content Platform Engine using a browser on a platform that is not the same as the FileNet Content Engine server. :9080\\acce This URL should open a browser session to permit logging into the FileNet Content Engine for administrative purposes. If the URL is not found the 9080 port may be closed on the FileNet Content Engine server firewall preventing access. \n\nRESOLVING THE PROBLEM\nCreate an Inbound Rule to open the required port of 9080 to allow the creation of the StoredIQ volume definition. If https access to the FileNet Content Engine server is configured then the Inbound Rule for the firewall should open port 9443.\n\nRELATED INFORMATION\n [FileNet P8 ports [http://pic.dhe.ibm.com/infocenter/iconf/v5r2m0/index.jsp?topic=%2Fcom.ibm.p8.planprepare.doc%2Fp8pap057.htm]\nContent Platform Engine ports [http://www-01.ibm.com/support/knowledgecenter/SSNW2F_5.2.1/com.ibm.p8.planprepare.doc/p8pap058.htm]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management eDiscovery Identification and Collection StoredIQ Platform Platform Independent 7.5.1 Enterprise Content Management Policy Assessment and Compliance StoredIQ Platform Platform Independent 7.5.1 Enterprise Content Management Unstructured Data Identification and Mgmt Not Applicable Platform Independent 7.5.1" ]

[ [ "1a", " TECHNOTE (FAQ) QUESTION" ], [ "1b", " How do I turn on sparse data object processing ANSWER" ], [ "1c", "After harvesting a volume, the audit may show \"skipped - cannot" ], [ "1d", "access data object\", with a sparse data object message recorded in the details section." ], [ "1e", "To correct this problem, ensure that no jobs are running." ], [ "1f", "SSH into the Data Server(s) and enter the following command at the prompt;" ], [ "1g", "psql -U dfuser dfdata -c \"insert into adminknobs (name,value,description,valuetype,use) VALUES ('read_sparse_files','1','Read sprase data objects','int','1')\"" ], [ "1h", "It should return the following;" ], [ "1i", "INSERT 0 1" ], [ "1j", "if so, enter the following command and wait for the UI to come back up;" ], [ "1k", "service siqinit restart" ], [ "1l", "You can now run harvests as normal and sparse data objects will be processed." ], [ "1m", "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." ], [ "1n", "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." ] ]

[ "1c", "1d", "1e", "1f", "1g", "1h", "1i", "1j", "1k", "1l" ]

[ "BPMConfig; profile; path; directory TECHNOTE (FAQ)\n\nQUESTION\n How do you specify the profile path in the configuration properties file for IBM Business Process Manager so you can use it with the BPMConfig command? \n\nANSWER\nNote: The information that is contained in this document has been moved to dW Answers at this location [https://developer.ibm.com/answers/questions/171346/how-do-you-specify-the-profile-path-with-bpmconfig.html]. The new format will allow you to ask questions of the community to better understand the information. This technote will be archived in 60 days. Please bookmark the new location.\n\nYou can use the following property names: \n\n * For a Deployment Manager profile: bpm.dmgr.profilePath \n * For a Custom profile: bpm.de.node.#.profilePath\n\n\nFor example: \nbpm.dmgr.profilePath=/usr/IBM/bpm85/profiles/DmgrProfile \nbpm.de.node.1.profilePath=c:\\\\Program Files\\\\WebSphere\\\\profiles\\\\MyCustomProfile1 \n\nFor Microsoft Windows, you can use double backslashes or forward slashes. For example: \n\nbpm.de.node.1.profilePath=c:/Program Files/WebSphere/profiles/MyCustomProfile1 \n\n \n\nNote: If you are creating the profile makes sure a profilePath value does not exist. The parent directory of the profile path should exist and the user should have write privileges to create a new directory. \n\n\nFor example, if you want to create a profile under the /usr/BPM850profiles/myProfile directory. Create the/usr/BPM850profiles directory, but do not create the /usr/BPM850profiles/myProfile directory.\n\nRELATED INFORMATION\n BPMConfig command: sample configuration properties file [http://www.ibm.com/support/knowledgecenter/SSFTDH_8.5.0/com.ibm.wbpm.imuc.doc/topics/samplecfgprops.html]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Advanced Installation / Configuration AIX, Linux, Linux zSeries, Solaris, Windows 8.5 \nPRODUCT ALIAS/SYNONYM\n BPM", " SUBSCRIBE\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 * Augmenting a dmgr profile with the parameter -profilePath will\n fail with a Exception in thread \"main\"\n java.lang.IllegalArgumentException: can't parse argument\n number wsadmin.output\n at java.text.MessageFormat.makeFormat(MessageFormat.java:1350)\n at java.text.MessageFormat.applyPattern(MessageFormat.java:470)\n at java.text.MessageFormat.<init>(MessageFormat.java:365)\n at java.text.MessageFormat.format(MessageFormat.java:823)\n at com.ibm.ws.install.configmanager.utils.MessageFormatUtils.\n formatMessage(MessageFormatUtils.java:66)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: Users of the Feature Pack for EJB 3.0 for *\n * IBM WebSphere Application Server version *\n * 6.1. *\n ****************************************************************\n * PROBLEM DESCRIPTION: A java.lang.IllegalArgumentException *\n * is caused when you attempt to *\n * augment a profile when specifying the *\n * parameter -profilePath <path>. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n A java.lang.IllegalArgumentException is caused when the user\n attempts to augment a profile when specifying the\n parameter -profilePath <path>. The underlying code should be\n creating a file that is then read and parsed for further\n information. In the case where the -profilePath parameter is\n specified the file is not being created and thus the reading\n and parsing fails.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * With this fix, the code which caused the creation of the file\n to not happen will be removed. The file will now always be\n generated.\n \n The fix for this APAR is currently targeted for inclusion in\n fix pack for 6.1.0.15 of the Feature Pack for EJB 3.0.\n Please refer to the recommended updates page for delivery\n 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 PK60043\n \n \n * REPORTED COMPONENT NAME\n WAS EJB3 FEATUR\n \n \n * REPORTED COMPONENT ID\n 5724J0851\n \n \n * REPORTED RELEASE\n 610\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 2008-01-28\n \n \n * CLOSED DATE\n 2008-01-30\n \n \n * LAST MODIFIED DATE\n 2008-01-30\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 WAS EJB3 FEATUR\n \n \n * FIXED COMPONENT ID\n 5724J0851\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R610 PSY\n UP", "profile management TECHNOTE (FAQ)\n\nQUESTION\n What are the recommended procedures to prevent the most common profile-related problems and ensure a successful installation of the Business Space powered by WebSphere product as a part of an IBM Case Manager installation? \n\nANSWER\nThe IBM Case Manager (ICM) installation procedure installs Business Space powered by WebSphere (Business Space), which is an underlying component to ICM. The installation of Business Space requires a profile defined in the WebSphere Application Server (WebSphere) product. Before Business Space is installed, the WebSphere profile is augmented to include Business Space configuration information. During an ICM installation procedure, that profile augmentation takes place when the Configure Business Space task is run in the Case Manager Administration Client. \n\nThe following procedures are recommended to fix and prevent problems due to WebSphere profile corruption: \n\n * Back up and restore profiles. Check if a WebSphere profile has been augmented previously. Augment profiles correctly. \n\nSeveral steps in the procedures below use the WebSphere manageprofiles command. The manageprofiles command has to run at the command prompt in the <was_root>\\AppServer\\bin directory. A detailed reference of the manageprofiles command can be found in the WebSphere InfoCenter documentation. For example: \n\n \n\n * WebSphere Network Deployment Version 7.0, manageprofiles command\n\n\n1. Back up and Restore Profiles \n\nOn each server where you will run the Configure Business Space task in CMAC, back up the WebSphere profiles using the WebSphere manageprofiles command before you start installing ICM. For example, to back up a profile called AppSrv01 on Windows: \n\n * \n * \n\n\nIn case there are symptoms of a corrupted WebSphere profile during the ICM installation procedure, you can restore the original profile and go back to running the Configure Business Space task in CMAC again. For example, to restore the profile backup generated above on Windows: * \n * \n\n\nThese are the steps of restoring a profile based on the WebSphere InfoCenter documentation: * Stop the server and the running processes for the profile that you want to restore. Manually delete the directory for the profile from the file system. Run the -validateAndUpdateRegistry option of the manageprofiles command. Restore the profile by using the -restoreProfile option of the manageprofiles command. \n\n\nPlease note: In order to recover corrupted WebSphere profiles, we recommend restoring a good backup of the profile. We do not recommend unagmenting the profile with the manageprofiles command, as it may give unexpected results in rare cases. \n\n2. Check if a WebSphere Profile has been Augmented Previously \n\nIf you want CMAC to install Business Space, then it is best to use a WebSphere profile that has not been augmented yet. Check if the WebSphere profile configured in CMAC had been augmented previously before running the Configure Business Space task in CMAC. \n\nTo check which WebSphere profile is configured in CMAC: \n\n * In CMAC, open your CMAC profile. In the CMAC File menu, choose the Edit Profile Properties command. Check the value of the Application server profile directory parameter. \n * \n\n\nTo check if a WebSphere profile has been augmented: Method 1: \n\n * manageprofiles -listAugments -profileName \"<profile name>\" In the output, check if a Business Space profile is listed under Registered Augment Templates \n\nMethod 2: \n * Open the <was_root>\\AppServer\\properties\\profileRegistry.xml file in a text editor. Find the <profile> tag with the name=\"<profile name>\" parameter, where <profile name> is the WebSphere profile you will use for the ICM installation. Check if there is another xml tag called <augmentor> is within the <profile> tag. If yes, then this profile is augmented. The path in the template parameter of the augmentor tag shows what template was used for the augmentation. \n\n3. Augment Profiles Correctly \n\nWebSphere profiles are created based on profile templates supplied with WebSphere. There are different types of WebSphere profile templates, such as: \n\n * Deployment manager Application server Custom profile Administrative agent Job manager Cell Secure proxy \n\nThe Websphere profile templates are located in the following directory: * \n * \n\nThe type of profile templates that exist in the directory above depends on the type of WebSphere installation. For example, the following profile templates may be there: * default dmgr management \n\n\nWebSphere profiles are augmented for Business Space based on profile templates supplied with Business Space. Business Space supports the following types of profiles: * Deployment manager Application server Custom profile \n\nThe Business Space profile templates are located in the following directory: * \n * \n\nThe folder above has the following profile templates: * default.bspace dmgr.bspace managed.bspace manageddefault.bspace \n\n\nIMPORTANT RULE: When augmenting a WebSphere profile for Business Space, the type of Business Space profile template must be compatible with the type of WebSphere profile template that was used to create the WebSphere profile. \n\nTo look up the type of WebSphere profile template that was used to create the WebSphere profile: \n\nMethod 1: \n * Open the <was_root>\\AppServer\\properties\\profileRegistry.xml file in a text editor. Find the <profile> tag with the name=\"<profile name>\" parameter, where <profile name> is the WebSphere profile you will use for the ICM installation. In the same xml tag, find the template parameter. It shows the path to the WebSphere profile template that was used to create the WebSphere profile. \n\n\nMethod 2: \n * Open the <was_root>\\AppServer\\logs\\manageprofiles\\<profile name>_create.log file in a text editor. Find the <record> tag that has a <message> tag inside with the following text: * \"Incoming command line is:\" OR \n * \"Current command line is:\"\n \n In the same <message> tag, find the parameter \"-templatePath\". The next parameter after that is the path to the WebSphere profile template that was used to create the WebSphere profile. \n\n\nWebSphere and Business Space Profile Template Compatibility * WebSphere Profile Business Space Profile default default.bspace\n manageddefault.bspace dmgr dmgr.bspace management managed.bspace \n \n\nWhen running the Configure Business Space task in CMAC, make sure that the WebSphere profile configured in the CMAC profile properties is augmented using a compatible Business Space profile template. \n\nUsing the Correct Business Space Profile Template in CMAC \n\nWith the instructions above, you can do the following: \n\n * In the CMAC profile properties, look up the WebSphere profile used for the ICM installation. In the WebSphere profileRegistry.xml file or the <profile name>_create.log file, look up what WebSphere profile template was used to create the WebSphere profile. In the profile template compatibility table above, check the compatible Business Space profile templates. \n\nNow you have to make sure to use a compatible Business Space profile template in the Configure Business Space task in CMAC. This is controlled by the Environment parameter. * \n * \n * 2. Make sure the value of the Environment property maps to a compatible Business Space profile template type. \n * \n\nCMAC Environment and Business Space Profile Template Mapping * CMAC Environment Business Space Profile Type Stand-alone Profile default.bspace\n manageddefault.bspace Deployment Manager Profile dmgr.bspace Managed Profile managed.bspace \n\n\nMessages in the CMAC log files: \n\nThe CMAC log files are located in the <ICM install location>\\logs directory. For example, on Windows: \n * \n * \n * \n * Scenario CMAC log message Augmenting a WebSphere profile with an incompatible Business Space Profile template in the Configure Business Space task in CMAC java.lang.RuntimeException: The Business Space template type for the selected environment, deployment type, and managed node type is incompatible with the selected profile. Please either select a different profile to augment, or verify that you have selected the appropriate environment, deployment type, and managed node types for your profile and try again Augmenting a profile that has already been augmented The specified profile has already been augmented with the Business Space Template. You do not need to run this task. Profile augmentation fails (UNIX example) Profile augmentation failed. For more information, consult /opt/IBM/WebSphere7/AppServer/logs/manageprofiles/<profile_name>_augment.log.", "INSTCONFFAILED profileRegistry.xml_LOCK FileLockerException TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When you attempt to create a profile for WebSphere Enterprise Service, you might encounter a \" INSTCONFFAILED: The profile could not be created.\" error. \n\nSYMPTOM\nThe following text shows the complete error: \n\nProfile creation is failing with this error: \n\nINSTCONFFAILED: The profile could not be created. For more information, consult the <path>\\ESB\\logs\\manageprofiles\\ESBAppSrv01_create.log file. \n\n\nWhen you examine the <path>\\ESB\\logs\\manageprofiles\\ESBAppSrv01_create.log file, it says: \n\n<message>com.ibm.wsspi.profile.WSProfileException: Another profile_nameprocess is running or a lock file exists. \n\nwhere profile_name represents the specific profile in question.\n\n\nRESOLVING THE PROBLEM\nTo resolve this issue, complete the following steps: \n\n 1. If a process is not running, delete the profileRegistry.xml_LOCK file as specified in the com.ibm.wsspi.profile.WSProfileException message.\n \n \n 2. If the complete path to the lock file does not exist, create it. The path to the lock file is stated in the message. For example, the message might say:\n If no process is running, delete the following file: \n F:\\IBM\\WebSphere\\content\\config\\ESB\\properties\\profileRegistry.xml_LOCK\n \n \n Ensure that the full path to the properties directory exists so that the lock file can be written.\n \n \n 3. Recreate the profile.\n\n \n\nPRODUCT ALIAS/SYNONYM\n WESB", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DOCUMENTATION ERROR.\n \n \n \n\nERROR DESCRIPTION\n * If the password are encrypted at the custoemr environemnt\n BPMConfig -upgrade command will fail with the following\n exception\n \n ./BPMConfig.sh -upgrade -profile $DMGR\n \n \n 2016-02-12 14:39.17.025\n com.ibm.bpm.config.util.ConfigHelper.getCommandMgr(): RETURN\n com.ibm.ws.management.cmdframework.impl.LocalCommandMgr@1dad4687\n 2016-02-12 14:39.17.025\n com.ibm.bpm.config.util.ConfigHelper.invokeAdminCommand(): ENTRY\n anonymous1455305664063\n com.ibm.ws.management.cmdframework.impl.LocalCommandMgr@1dad4687\n createKeyStore {keyStoreReadOnly=false,\n keyStoreName=IBMBPMKeyStore-De1,\n keyStorePasswordVerify=********,\n keyStoreLocation=${CONFIG_ROOT}/cells/PSCell1/ibmbpmks-De1.jceks\n ,\n keyStoreDescription=IBM BPM key store for De1,\n keyStoreType=JCEKS,\n keyStorePassword=********, keyStoreUsage=KeySetKeys,\n scopeName=(cell):PSCell1} null null\n \n [2/12/16 14:39:17:222 EST] FFDC\n Exception:com.ibm.bpm.config.util.ConfigException\n SourceId:com.ibm.bpm.config.BPMConfig.main ProbeId:163\n Reporter:java.lang.Class@59426a1a\n com.ibm.bpm.config.util.ConfigException: CWMCB0046E: The\n 'createKeyStore' command failed: Both password and verify\n password were\n not supplied.\n at\n com.ibm.bpm.config.util.ConfigHelper.invokeAdminCommand(ConfigHe\n lper.jav\n a:2468)\n at\n \n com.ibm.bpm.config.util.ConfigHelper.invokeAdminCommand(ConfigHe\n lper.jav\n a:1998)\n at\n com.ibm.bpm.config.capability.standard.ComponentProcessServer.ad\n dKeyStor\n eForBpm(ComponentProcessServer.java:3059)\n at\n com.ibm.bpm.config.capability.standard.ComponentProcessServer.up\n gradeDep\n loymentTarget(ComponentProcessServer.java:613)\n at\n com.ibm.bpm.config.capability.Capability.upgrade(Capability.java\n :511)\n at\n com.ibm.bpm.config.capability.ProvisionDe.upgradeDeploymentEnvir\n onment(P\n rovisionDe.java:1052)\n at\n com.ibm.bpm.config.BPMConfig.upgradeProfile(BPMConfig.java:1266)\n at\n com.ibm.bpm.config.BPMConfig.access$1100(BPMConfig.java:150)\n ==============\n \n All upgrade documents need to be updated with a note to edit\n the file\n \n http://www-01.ibm.com/support/docview.wss?uid=swg27047000 [http://www-01.ibm.com/support/docview.wss?uid=swg27047000]\n \n Step X : optional\n * DBUpgrade script modification already listed\n * BPMConfig script modification\n - Find the comment block \"Enabling custom password encryption\"\n - Modify the value of the CUSTOMPWDPROPS property based on your\n custom encryption class name and add any required variables\n - Add CLASSPATH=$CLASSPATH: <full file path of your custom\n password encryption jar file>\n \n \n \n \n \n\nLOCAL FIX\n * DOC improvment\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: IBM Business Process Manager (BPM) *\n * Advanced *\n * IBM Business Process Manager (BPM) *\n * Standard *\n * IBM Business Process Manager (BPM) Express *\n ****************************************************************\n * PROBLEM DESCRIPTION: In *\n * http://www- *\n * 01.ibm.com/support/docview.w *\n * ss?uid=swg27047000 before step 15 \" *\n * Start the deployment manager server.\" *\n * and before step 11 \"For each *\n * stand-alone profile in the IBM BPM *\n * Express installation\" add the same *\n * following new step (4 times in total): *\n * Optional: If you enabled custom *\n * password encryption in your IBM BPM *\n * environment to protect passwords that *\n * are contained in your WebSphere *\n * Application Server configuration, you *\n * must enable the BPMConfig script to *\n * support custom encryption. From *\n * install_root/bin, open the script or *\n * batch file for the BPMConfig command. *\n * - Find the comment block \"Enabling *\n * custom password encryption.\" Read the *\n * comments and then uncomment the *\n * properties. *\n * - Modify the value of the *\n * CUSTOMPWDPROPS property based on your *\n * custom encryption class name. Also *\n * add any additional system properties *\n * that your custom encryption class *\n * needs. *\n * - Modify the value of the CLASSPATH *\n * property and replace it with the full *\n * file path of your custom password *\n * encryption jar file. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n In http://www-01.ibm.com/support/docview.wss?uid=swg27047000 [http://www-01.ibm.com/support/docview.wss?uid=swg27047000]\n before step 15 \"\n Start the deployment manager server.\" and before step 11 \"For\n each stand-alone profile in the IBM BPM Express installation\"\n add the same following new step (4 times in total):\n Optional: If you enabled custom password encryption in your\n IBM BPM environment to protect passwords that are contained in\n your WebSphere Application Server configuration, you must\n enable the BPMConfig script to support custom encryption. From\n install_root/bin, open the script or batch file for the\n BPMConfig command.\n - Find the comment block \"Enabling custom password\n encryption.\" Read the comments and then uncomment the\n properties.\n - Modify the value of the CUSTOMPWDPROPS property based on\n your custom encryption class name. Also add any additional\n system properties that your custom encryption class needs.\n - Modify the value of the CLASSPATH property and replace it\n with the full file path of your custom password encryption jar\n file.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * This will be updated in next refresh\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n JR55335\n \n \n * REPORTED COMPONENT NAME\n BPM STANDARD\n \n \n * REPORTED COMPONENT ID\n 5725C9500\n \n \n * REPORTED RELEASE\n 856\n \n \n * STATUS\n CLOSED DOC\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 2016-02-16\n \n \n * CLOSED DATE\n 2016-03-28\n \n \n * LAST MODIFIED DATE\n 2016-03-28\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\nAPPLICABLE COMPONENT LEVELS" ]

[ [ "0a", "BPMConfig; profile; path; directory TECHNOTE (FAQ) QUESTION" ], [ "0b", " How do you specify the profile path in the configuration properties file for IBM Business Process Manager so you can use it with the BPMConfig command? ANSWER" ], [ "0c", "Note: The information that is contained in this document has been moved to dW Answers at this location [https://developer.ibm.com/answers/questions/171346/how-do-you-specify-the-profile-path-with-bpmconfig.html]." ], [ "0d", "The new format will allow you to ask questions of the community to better understand the information." ], [ "0e", "This technote will be archived in 60 days." ], [ "0f", "Please bookmark the new location." ], [ "0g", "You can use the following property names:" ], [ "0h", " * For a Deployment Manager profile: bpm.dmgr.profilePath" ], [ "0i", " * For a Custom profile: bpm.de.node.#.profilePath For example: bpm.dmgr.profilePath=/usr/IBM/bpm85/profiles/DmgrProfile bpm.de.node.1.profilePath=c:\\\\Program Files\\\\WebSphere\\\\profiles\\\\MyCustomProfile1" ], [ "0j", "For Microsoft Windows, you can use double backslashes or forward slashes. For example: bpm.de.node.1.profilePath=c:/Program Files/WebSphere/profiles/MyCustomProfile1" ], [ "0k", "Note: If you are creating the profile makes sure a profilePath value does not exist." ], [ "0l", "The parent directory of the profile path should exist and the user should have write privileges to create a new directory." ], [ "0m", "For example, if you want to create a profile under the /usr/BPM850profiles/myProfile directory." ], [ "0n", "Create the/usr/BPM850profiles directory, but do not create the /usr/BPM850profiles/myProfile directory. RELATED INFORMATION" ], [ "0o", " BPMConfig command: sample configuration properties file [http://www.ibm.com/support/knowledgecenter/SSFTDH_8.5.0/com.ibm.wbpm.imuc.doc/topics/samplecfgprops.html]" ], [ "0p", "Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Advanced Installation / Configuration AIX, Linux, Linux zSeries, Solaris, Windows 8.5 PRODUCT ALIAS/SYNONYM BPM" ] ]

[ "0k", "0l", "0m", "0n" ]

[ "ClearCase; Cleartool; AIX; HP-UX; Linux; Solaris; 7.0.0.1; 7.0.1; RATLC01052117; PK61010; 1287218 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote explains why the error vobrpc_server(9622): Error: Unable to open /tmp/myvob.vbs/.hostname: No such file or directory might appear in the logs when using IBM® Rational® ClearCase® on Linux® and UNIX®. \n\nSYMPTOM\n \n\nAfter upgrading ClearCase the following are reported in the vobrpc_server_log. \n\n2007-11-07T14:35:42-08 vobrpc_server(21703): Error: Unable to open \n/tmp/vob2.vbs/.hostname: No such file or directory\n\nThese errors appear after applying the following updates: \n\n7.0 \n\n7.0.0.1-IFIX04\n7.0.1-IFIX01 \n\n \n\n2003.06.00 \n\nclearcase_p2003.06.00-48\nclearcase_p2003.06.00-49\nmultisite_p2003.06.00-19 \n\n \n\nNote: This error may be repeated for different VOBs.\n\nYou may also see the following errors when running the multitool mkreplica command:\n\nmyhost% multitool mkreplica -export -workdir /tmp/ms_workdir -fship host1:vob_2\nEnabling replication in VOB.\nGenerating replica creation packet /opt/rational/clearcase/shipping/ms_ship/outgoing/repl_original_08-Nov-07.17.13.19_10088_1\n- shipping order file is /opt/rational/clearcase/shipping/ms_ship/outgoing/sh_o_repl_original_08-Nov-07.17.13.19_10088_1\nDumping database...\ndb_dumper.54: Error: Unable to open /tmp/vob2.vbs/db/../.hostname: No such \n\nfile or directory \n\n0 hyperlinks dumped.\n1 oplog entries dumped.\n59 events dumped.\n1 locks dumped.\nDumper done.\nStarting to copy dumped db files to replica creation packet.\nSize: 1 (megabytes, rounded up), File: /tmp/ms_workdir/pass1_dump_file.\nSize: 1 (megabytes, rounded up), File: /tmp/ms_workdir/pass2_dump_file.\nSize: 1 (megabytes, rounded up), File: /tmp/ms_workdir/string_dump_file.\nFinished copying db files.\nStarting to copy pool files.\nFinished copying pool files.\nAttempting to forward/deliver generated packets...\n-- Forwarded/delivered packet /opt/rational/clearcase/shipping/ms_ship/outgoing/repl_original_08-Nov-07.17.13.19_10088_1\n=====\n\nAdditional errors reported in the vobrpc log:\n\n2007-11-07T18:22:13-05 vobrpc_server(9622): Error: Unable to open /tmp/vob2.vbs/.hostname: No such file or directory\n2007-11-07T18:22:13-05 vobrpc_server(9622): Error: Unable to open /tmp/vob2.vbs/db/../.hostname: No such file or directory\n\n\n\nCAUSE\n \n\nThis is caused by a missing file in the VOB storage directory called .hostname which is referenced when the vobrpc_server process is first started for that VOB. The error may be repeated in the logs for each VOB that is missing this file.\n\nThe error is reported as a result of defect APAR PK61010 Upon upgrading ClearCase errors appear in the vobrpc_server log\n\nNOTE: This is not a critical error and will not prevent the vobrpc_server process from accessing the VOB storage or database. \n\n\nRESOLVING THE PROBLEM\n \n\n [http://www-1.ibm.com/support/docview.wss?rs=984&uid=swg1PK61010]\nAPAR PK61010 [http://www-1.ibm.com/support/docview.wss?rs=984&uid=swg1PK61010]has been closed as there are no plans to change this behavior. \n\n\nWORKAROUNDS:\n\nEither of the following workarounds can be used to resolve the errors.\n\n\n * Unregister and re-register the VOBs that are reporting the errors. This will create a new .hostname file in the VOB storage directory. \n \n For each of the VOBs reporting the errors, perform the following steps: 1. Unregister [http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m1/index.jsp?topic=/com.ibm.rational.clearcase.cc_ref.doc/topics/ct_unregister.htm]the VOB\n Example:\n cleartool unregister –vob /vobstore/vob2.vbs \n \n \n 2. Register [http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m1/index.jsp?topic=/com.ibm.rational.clearcase.cc_ref.doc/topics/ct_register.htm]the VOB\n Example:\n cleartool register –vob /vobstore/vob2.vbs \n \n \n \n \n * Manually create a .hostname file in the VOB storage directory for any VOB that is reporting the errors in the logs.\n\n * Note: \n * \n * \n * \n * \n * myhost\n * \n * \n * myhost% cleartool lsvob\n * /tmp/vob2 /tmp/vob2.vbs private\n \n myhost% pwd\n /tmp/vob2.vbs\n \n * \n * \n * \n \n # ls -ali\n total 192\n 117413622 drwxr-xr-x 8 jdoe user 805 Nov 12 18:32 .\n 1474127 drwxrwxrwt 18 root sys 3097 Nov 12 17:55 ..\n 117286737 drwx------ 2 jdoe user 305 Nov 12 04:30 .identity\n 117413314 -rw-r--r-- 1 jdoe user 6 Nov 6 16:06 .pid\n 4903559 drwxr--r-- 4 jdoe user 248 Nov 12 04:30 admin\n 117413202 drwxr-xr-x 3 jdoe user 178 Nov 6 16:06 c\n 117413230 drwxr-xr-x 3 jdoe user 178 Nov 6 16:06 d\n 117413174 drwxr-xr-x 3 jdoe user 1062 Nov 12 04:30 db\n 4903391 -rw-r--r-- 1 root root 0 Nov 12 18:31 echo\n 117413734 -r--r--r-- 1 jdoe user 41 Nov 6 16:06 replica_uuid\n 117413258 drwxr-xr-x 3 jdoe user 178 Nov 6 16:06 s\n 117413454 -r--r--r-- 1 jdoe user 41 Nov 6 16:06 vob_oid\n 117413286 -rw-r--r-- 1 jdoe user 625 Nov 6 16:06 vob_server.conf\n \n # touch .hostname\n \n # echo myhost >> .hostname\n \n # ls -ali\n total 208\n 117413622 drwxr-xr-x 8 jdoe user 871 Nov 12 18:32 .\n 1474127 drwxrwxrwt 18 root sys 3097 Nov 12 17:55 ..\n \n * 4902971 -rw-r--r-- 1 root root 6 Nov 12 18:32 .hostname\n \n * 117286737 drwx------ 2 jdoe user 305 Nov 12 04:30 .identity\n 117413314 -rw-r--r-- 1 jdoe user 6 Nov 6 16:06 .pid\n 4903559 drwxr--r-- 4 jdoe user 248 Nov 12 04:30 admin\n 117413202 drwxr-xr-x 3 jdoe user 178 Nov 6 16:06 c\n 117413230 drwxr-xr-x 3 jdoe user 178 Nov 6 16:06 d\n 117413174 drwxr-xr-x 3 jdoe user 1062 Nov 12 04:30 db\n 4903391 -rw-r--r-- 1 root root 0 Nov 12 18:31 echo\n 117413734 -r--r--r-- 1 jdoe user 41 Nov 6 16:06 replica_uuid\n 117413258 drwxr-xr-x 3 jdoe user 178 Nov 6 16:06 s\n 117413454 -r--r--r-- 1 jdoe user 41 Nov 6 16:06 vob_oid\n 117413286 -rw-r--r-- 1 jdoe user 625 Nov 6 16:06 vob_server.conf\n \n # cat .hostname\n myhost\n\n\nRELATED INFORMATION\n#Failed to record hostname [http://www.ibm.com/support/docview.wss?uid=swg21234135]", "missing 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.", " SUBSCRIBE\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 * Duplicated of BR10000105521\n Customer has found a major issue which is impacting\n production.\n When using the SWI option ?Open from SmarTeam? which we were\n told is the only supported ST/SW Integration option, the\n ?Destination directory? defaults to\n previous user?s destination location, and not obeying the\n Default Work Directory defined in STFE.\n The issue is not reproducible if we use the function ?Find\n Object? which we were told by DS is not a supported use for\n SWI. See below:\n If we continue using the ?Open from SmarTeam? option, users\n have to always remember to manually change the location of\n the file(s) which will be Checked-Out or the file(s) will be\n Checked-Out to a location that does not exist.\n If the file is checked to a non-existing location, the file\n is not accessible as the location gets created as phantom and\n the user does not have access to the location.\n I found BR10000105521 on DS? KB which appears to be the same\n issue as we are seeing.\n We cannot use the ?Find object? since DS told us that any\n option used under the SmarTeam menu in SW other than the\n ?Open from SmarTeam? is unsupported part of the integration.\n And using the ?Find Object? option produces the ?Read Only?\n error with files marked at Checked-Out.\n The only workaround we can use for now, is for each user to\n manually set the directory with every checkout.\n I would like to have this issue elevated and have DS/Artizone\n immediately provide us with the proper course of action from\n here, as we have no options to move forward in a ?Supported?\n fashion.\n Customer's Environment\n SmarTeam R20 SP 5 (HF 76)\n SolidWorks 2011 SP3.0\n Windows 7 x64\n Description of BE reproduction of BR10000105521 (for which\n this SR/BR is Duplicated) :\n Windows 7 x64 - V5R20 SP5 - SWI x64 - SW2011 SP2 x64 - PLMDB\n from V5R20 SP5\n No any default setting changed.\n Default setting included set in SMARTEAM System Configuration\n Editor for Default used\n I have reproduced the reported problem using next scenario:\n 1. Launch SWI with admin\n 2. Default SmarTeam Work directory is My\n Documents\\SmarTeam\\Work\n 3. Create DifferentFolder in My Documents\n 4. Create SW Part, Save it by SolidWorks Save As under\n DifferentFolder\n 5. Do SmarTeam Save and Check In - succeeded\n 6. Open from SmarTeam\n 7. Search for the Part\n 8. Check (mark) Edit check box in SmarTeam Open Dialog -\n Check Out window appears\n 9. Check the destination directory\n Expected result: SmarTeam Work directory as My\n Documents\\SmarTeam\\Work should appear and the file should be\n copied into it\n Current result: the defect - My Documents\\DifferentFolder\n appears (that was folder were the Part was saved previously\n in SW and in ST)\n Besides, if we are not using SmarTeam Open dialog (Open from\n SmarTeam, but any Search and doing Open for Edit/Check Out\n from Search SmarTeam Editor, there is the right destination\n folder appear\n \n \n \n \n \n\nLOCAL FIX\n * empty\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Duplicated of BR10000105521\n Customer has found a major issue which is impacting\n production.\n When using the SWI option ?Open from SmarTeam? which we were\n told is the only supported ST/SW Integration option, the\n ?Destination directory? defaults to\n previous user?s destination location, and not obeying the\n Default Work Directory defined in STFE.\n The issue is not reproducible if we use the function ?Find\n Object? which we were told by DS is not a supported use for\n SWI. See below:\n If we continue using the ?Open from SmarTeam? option, users\n have to always remember to manually change the location of\n the file(s) which will be Checked-Out or the file(s) will be\n Checked-Out to a location that does not exist.\n If the file is checked to a non-existing location, the file\n is not accessible as the location gets created as phantom and\n the user does not have access to the location.\n I found BR10000105521 on DS? KB which appears to be the same\n issue as we are seeing.\n We cannot use the ?Find object? since DS told us that any\n option used under the SmarTeam menu in SW other than the\n ?Open from SmarTeam? is unsupported part of the integration.\n And using the ind Object? option produces the ?Read Only?\n error with files marked at Checked-Out.\n The only workaround we can use for now, is for each user to\n manually set the directory with every checkout.\n I would like to have this issue elevated and have DS/Artizone\n immediately provide us with the proper course of action from\n here, as we have no options to move forward in a ?Supported?\n fashion.\n Customer's Environment\n SmarTeam R20 SP 5 (HF 76)\n SolidWorks 2011 SP3.0\n Windows 7 x64\n Description of BE reproduction of BR10000105521 (for which\n this SR/BR is Duplicated) :\n Windows 7 x64 - V5R20 SP5 - SWI x64 - SW2011 SP2 x64 - PLMDB\n from V5R20 SP5\n No any default setting changed.\n Default setting included set in SMARTEAM System Configuration\n Editor for Default used\n I have reproduced the reported problem using next scenario:\n 1. Launch SWI with admin\n 2. Default SmarTeam Work directory is My\n Documents\\SmarTeam\\Work\n 3. Create DifferentFolder in My Documents\n 4. Create SW Part, Save it by SolidWorks Save As under\n DifferentFolder\n 5. Do SmarTeam Save and Check In - succeeded\n 6. Open from SmarTeam\n 7. Search for the Part\n 8. Check (mark) Edit check box in SmarTeam Open Dialog -\n Check Out window appears\n 9. Check the destination directory\n Expected result: SmarTeam Work directory as My\n Documents\\SmarTeam\\Work should appear and the file should be\n copied into it\n Current result: the defect - My Documents\\DifferentFolder\n appears (that was folder were the Part was saved previously\n in SW and in ST)\n Besides, if we are not using SmarTeam Open dialog (Open from\n SmarTeam, but any Search and doing Open for Edit/Check Out\n from Search SmarTeam Editor, there is the right destination\n folder appear\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * NOTE THAT THIS PROBLEM WILL ALSO BE FIXED ON V5R20 SP7.\n NOTE THAT THIS PROBLEM WILL ALSO BE FIXED ON V5R21 SP1.\n Additional Closure Information:\n -\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n HE07243\n \n \n * REPORTED COMPONENT NAME\n SMARTEAM NT>XP\n \n \n * REPORTED COMPONENT ID\n 569199970\n \n \n * REPORTED RELEASE\n 520\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 2011-05-24\n \n \n * CLOSED DATE\n 2011-06-17\n \n \n * LAST MODIFIED DATE\n 2011-06-17\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 SMARTEAM NT>XP\n \n \n * FIXED COMPONENT ID\n 569199970\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R520 PSN\n UP", "purge; object; performance TECHNOTE (FAQ)\n\nQUESTION\n How do you purge one or all IBM Rational DOORS Objects? \n\nCAUSE\nPurging the deleted objects will free-up database space hence the IBM Rational DOORS performance will be optimized.\n\nANSWER\nTo purge a Rational DOORS Object, apply the following steps: \n\n 1. Open the Rational DOORS Module in exclusive edit\n \n \n 2. Click View > Show > Deletions\n \n \n 3. Select the deleted object you want to purge\n \n \n 4. Click Edit > Object > Purge...\n \n \n 5. A message is displayed asking if you really want to purge the selected deleted item; Click Confirm\n \n \n 6. Click File > Save to save the change\n\n\nThe object and all objects in the tree below it are permanently removed from the module. \n\nNote: You cannot delete or purge objects that have descendants if sorting is turned on. Leaf objects can be deleted when sorting is on. \n\n\n\n Back to top \n\n\n\nTo purge all the Rational DOORS Objects, apply the following steps: \n 1. Open the Rational DOORS Module in exclusive edit\n \n \n 2. Click Edit > Purge All\n \n \n 3. A message is displayed showing the number of objects marked for deletion, Click Yes\n \n \n 4. Deleted objects are purged even if they are not being displayed\n \n \n 5. Click File > Save\n\nRELATED INFORMATION\n#How to purge a Rational DOORS Module: [https://www.ibm.com/support/docview.wss?rs=0&uid=swg21498577]", "http 409; RQM ; test plan; Validates link; unable to load TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to save a test plan or a test case with a 'Validates' link to a requirement or module view in IBM Rational DOORS fails with: \"An error occurred while saving links from requirements provider\". The link to DOORS is created in Quality Manager but no link back to Quality Manager is created in DOORS. \n\nSYMPTOM\nThe full error message is as follows - note the status:409:\n\nAn error occurred while saving links from requirements provider\nUnable to load /qm/proxy?uri=http%3A%2F%2Fclm%3A8080%2Fdwa%2Frm%2Furn%3Arational%3A%3A1-504dd9b9029f2803-M-00000080 status:409\n\n\nAnother variant, with a different cause - note the status:500: \n\n\nAn error occurred while saving links from requirements provider\nUnable to load /qm/proxy?uri=http%3A%2F%2Fclm%3A8080%2Fdwa%2Frm%2Furn%3Arational%3A%3A1-504dd9b9029f2803-M-00000080 status:500\n\n\n\n\n\n\nCAUSE\n \n\n * The 409 error is seen where the DOORS module is open in exclusive edit mode or a section of the module which needs to be updated has been locked in shared edit mode. Or the user does not have write access to the module in DOORS.\n\n\n * The 500 error can occur when there a mismatch in the dwaHost registered with DOORS and that set in the published.url.prefix parameter in IBM Rational DOORS Web Access (DWA) To verify if this is the issue, open the properties of a DOORS module and note its exact URL. \n \n For example: \n http ://tennyson:9999/dwa/rm/urn:rational::1-4f9819536c985f97-M-00000541\n \n \n Edit the <DWA Install folder>\\server\\festival\\config\\festival.xml file \n \n Note the value for the parameter published.url.prefix. \n \n The hostname there must match exactly the hostname in the module's properties. \n \n For example: <f:property name=\"published.url.prefix\" value=\"http ://tennyson.ibm.com:8080/doors/redirector/\"/> \n \n This does not match. In DOORS, it is tennyson; In DWA it is tennyson.ibm.com.\n \n \n\n\n\nRESOLVING THE PROBLEM\nTo resolve the issue: \n\n * For the 409 error, close the module in DOORS and try to save the test plan again.\n\n\n * For the 500 error, if the value in the festival.xml is incorrect, correct it and restart DWA. If the value in the module is incorrect, it is necessary to run the dbadmin command and restart the DOORS database server. \n \n Run the command: dbadmin -data <port@host> -dwaHost <correct hostname> \n \n \n \n Verify you see a response like: \n \n I- DBADMIN: DWA host has been set \n \n \n \n For example: dbadmin -data 36677@localhost -dwaHost tennyson.ibm.com \n \n -I- DBADMIN: DWA host has been set \n \n \n \n Restart the DOORS database server and check in the module properties that it is now correct.\n \n \n\n\nRELATED INFORMATION\n#Http 500 error trying to associate a DOORS module with [http://www.ibm.com/support/docview.wss?uid=swg21615699]" ]

[ [ "1a", "missing session file; file not found; can not open module; open module exclusive edit fails; PM50525 TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "1b", " Attempts to open a module exclusive edit in IBM Rational DOORS result in the error \"DOORS report" ], [ "1c", "Unable to open module '/A Project/Requirements' No such file or directory\". SYMPTOM" ], [ "1d", "A module with a large number of sections is used mostly in shareable edit mode." ], [ "1e", "You can open the module Read-only , or Shareable-Edit; but not in exclusive edit." ], [ "1f", "Steps to reproduce: 1." ], [ "1g", "Login to DOORS 2." ], [ "1h", "Click the Project, or folder, icon that contains the module 3." ], [ "1i", "Click the module icon in the DOORS Explorer window 4." ], [ "1j", "Click File > Open> Exclusive Edit (Ctrl + E)" ], [ "1k", "Expected result: The module should open in Exclusive edit mode." ], [ "1l", "Actual result: The module will not open in exclusive edit module; however it will open in read only mode, or shareable edit mode." ], [ "1m", "If you attempt to check the database integrity for issue the module is not flagged for any problems." ], [ "1n", "The full error message is as follows: DOORS report" ], [ "1o", "Unable to open module '/A Project/Requirements' No such file or directory\"" ], [ "1p", "C:\\Program Files (x86)\\IBM\\Rational\\DOORS\\9.5\\data\\v6data\\20\\m00000021.mod\\current.ver\\s1000005.dtc image [/support/docview.wss?uid=swg21511831&aid=1] [/support/docview.wss?uid=swg21511831&aid=1] CAUSE" ], [ "1q", " This issue has been identified as a product defect under APAR PM50525 [http://ibm.com/support/docview.wss?uid=swg1PM31236]." ], [ "1r", "RESOLVING THE PROBLEM" ], [ "1s", "This error indicates that a user session file is corrupted on the database server." ], [ "1t", "This defect is resolved in IBM Rational DOORS Version 9.4.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27036720#9401] WORKAROUND:" ], [ "1u", "the following options can be used to correct this problem:" ], [ "1v", " * Retrieve the missing file from system backup and insert it into the module current.ver directory" ], [ "1w", " The advantage of inserting the missing session file is you do not need to restart the database server." ], [ "1x", "Warning these two option should only be performed by Rational Support." ], [ "1y", "Modifications to the files in your DOORS database could result is data corruption and jeapordize your DOORS database." ], [ "1z", "Send the session.ixc file to support for repair" ], [ "1aa", "From the module directory listed in the error message provide support the file session.ixc" ], [ "1ab", "Choosing to have support repair the session index file requires you to have all users log out" ], [ "1ac", "and shut down the DOORS database server until the repaired file is returned and inserted" ], [ "1ad", "to replace the existing data file for the module." ], [ "1ae", "Create a replacement session file" ], [ "1af", "From the module directory listed in the error message provide support the file session.ixc" ], [ "1ag", "Adjacent session files will be required in order to to create the replacement." ], [ "1ah", "Your support engineer will identify these files from the session index file." ], [ "1ai", "No work can be performed in the effected module until the replacement session file is restored" ], [ "1aj", "for the effected module." ], [ "1ak", "Note: Generally the repair is only required for one user session file." ], [ "1al", "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." ], [ "1am", "For this situation you may need to perform a successive repair to the index file." ] ]

[ "1b", "1c", "1e", "1n", "1o", "1q", "1r", "1s", "1t", "1u" ]

[ " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nPresentation and Q&A session for IBM Open Mic on \"Best Practices & Troubleshooting for Lotus Domino Policies\", March 28, 2012\n\nRESOLVING THE PROBLEM\nIBM hosted an Open Mic session on topic \"Best Practices & Troubleshooting for Lotus Domino Policies\", March 28, 2012. In this Open Mic, the presenter walked through a 45 minute presentation followed by Q&A session. Below are the Q&A's happened during the session. Presentation is attached at the end. \n\nQ. Can we use policy to restrict users from sending emails with specific size of attachments? \n\nA. No This requirement cannot be achieved using policy. You may use server rule to achieve this requirement. \n\n************************************************************************************************************************** \n\nQ. Is it possible that an administrator receive an alert when the policy is assigned to the user? \n\nA. No. It is not possible to send an alert to administrator when a policy is assigned to the user. An Administrator can use Policy Synopsis tool to check which are the different policies assigned to the user. \n\n************************************************************************************************************************** \n\nQ. Can I have multiple auto archiving criteria on server? \n\nA. You can have one criteria at a time that can be applied to the user and user will able to see only one Archive criteria at a time. \n\n************************************************************************************************************************** \n\nQ. Can we put control on archive database size on server when archiving policy is used? \n\nA. There's no way that you can set a size for an archive database on server. You may create a new criteria after a certain period of time so that you will have a new archive database. For example you can have new archive database each year. Better option is to store archive database on local. \n\n************************************************************************************************************************** \n\nQ. Is there any way that user's archive will be automatically deleted from server if user lefts the organization? \n\nA. No there's no way to delete archive automatically in this situation. \n\n************************************************************************************************************************** \n\nQ. What all fields can be controlled from dynamic and explicit policies? Is there any document that explain about implementing different settings with best options? Any recommended settings from IBM? \n\nA. You can control all the available fields in settings document using dynamic and explicit policies. As such there's no any document which states that customers should put some specific settings as best practices. It depends on an organizational needs and every organization has different needs/requirements. Hence there's no any recommendation from IBM suggesting to implement specific settings as best practices. \n\n************************************************************************************************************************** \n\nQ. What is the console command to forcefully update policies from server? \n\nYou can give load updall -t (\"$Policies\") names.nsf -R to forcefully update policies from server. You don't need to use quotes if your domino server is on AIX/Linux/Solaris platform. \n\nTo refresh mail policy, you can give tell adminp process mailpolicy command. \n\n************************************************************************************************************************** \n\nQ. Can you please brief on \"Prohibit private archiving criteria\" setting? \n\nA. Using this setting, you can prohibit users from creating local archive criteria at their own. Users have to use the one you created, they can't make their own criteria. \n\n************************************************************************************************************************** \n\nQ. How can I sync my Notes, Internet and Active Directory Password? \n\nA. Using Security settings/policy, you can sync Notes Password with Internet. There's no way to sync Active Directory password using policy. \n\nTo Sync Active Directory password with internet password, you can use Windows SSO for Web Client or SPNEGO feature and using Notes Shared Login, you can sync Notes Password with Active Directory password. \n\n************************************************************************************************************************** \n\nQ. For a user \"Don't let administrator set domino web/internet password to match Notes password\" option is checked and greyed out under Files -> Security->User Security. How can an Administrator Synchronize this user's Notes Password with Internet password? \n\nA. With this setting, user has disabled the administrator's ability to synchronize user's notes password with Domino web/internet password. \n\nIf this setting is greyed out then the user is assigned a security settings/policy in which \"Update Internet Password When Notes Client Password Changes\" option is set to No. \n\n \n\nPresentation in PDF format is attached below.\n\nIBM Open Mic_Best Practices & Troubleshooting for Lotus Domino Policies.pdf [/support/docview.wss?uid=swg21589912&aid=2]IBM Open Mic_Best Practices & Troubleshooting for Lotus Domino Policies.pdf [/support/docview.wss?uid=swg21589912&aid=1]", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DOCUMENTATION ERROR.\n \n \n \n\nERROR DESCRIPTION\n * The ConfigDms.sh script fails when the DB2 Password contains\n a \"$\" preventing the configuration of the SDMS and/or TCORE DD.\n \n \n \n \n \n\nLOCAL FIX\n * Remove the $ from password.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * $ sign is not allowed to be used in passwords.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * To be resolved by doc change.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IV14274\n \n \n * REPORTED COMPONENT NAME\n ITCAM FOR SOA-D\n \n \n * REPORTED COMPONENT ID\n 5724SOA00\n \n \n * REPORTED RELEASE\n 711\n \n \n * STATUS\n CLOSED DOC\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-01-27\n \n \n * CLOSED DATE\n 2013-04-12\n \n \n * LAST MODIFIED DATE\n 2013-04-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 ITCAM FOR SOA-D\n \n \n * FIXED COMPONENT ID\n 5724SOA00\n \n \n\nAPPLICABLE COMPONENT LEVELS", "CAMSOAALL CAMSOADB CAMSOAPERF REQMETRICS RESPMETRICS kd4TrimDB2db TECHNOTE (FAQ)\n\nQUESTION\n As the KD4SDMS grows unbounded, is there a way to regularly prune it? \n\nANSWER\nRegarding the older release ITCAM for SOA 7.1.1, there is no a mechanism to automatically regularly prune the KD4SDMS database. The following Wiki page has been published on the topic:\nhttps://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Composite+Application+Manager/page/Pruning+SDMS+Relationship+Metrics+Tables [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Composite+Application+Manager/page/Pruning+SDMS+Relationship+Metrics+Tables]\n\nTo keep only the latest 24 hours every day (regular pruning), you can schedule a daily job to run the kd4TrimDB2db utility provided above. \n\nAs for the newer ITCAM for SOA 7.2, there is a cleanup task that runs on the TEPS host where SDMS database is installed. It deletes REQMETRICS and RESPMETRICS table rows where SRTTIME (start of period) is more than 24 hours ago. So these two tables, which are responsible for most of KD4SDMS storage occupation, should not grow unbounded anymore.\n\nNOTE: ITCAM for SOA 7.1.1 is Out-Of-Support since 2015 April 30.", "CAMSOAALL CAMSOACD \"collecting Data\" MustGather ITCAM SOA ITCAMfSOA ITCAM4SOA 7.1.1 7.1 7.2 Log logs trace traces d4 TECHNOTE (FAQ)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n US English \n\nQUESTION\n What ITCAM for SOA logs are required for Problem Determination ? \n\nANSWER\n\nInformation/document required for SOA problem determination\n\n\nPlease provide the following information from the environment having the problem: \n\n 1. All platforms (operating systems) related to the issue. \n 2. Version of ITCAM for SOA. \n 3. Name and Version of the App Server (ex: WebSphere 6.1) \n 4. Result of the following command from all the platforms listed in 1 above From \"<ITM_HOME>/bin\" directory, \n **Windows : \"kincinfo -i\" \n **Unix : \"cinfo -i\" \n 5. Helpful snapshot if appropriate \n 6. Logs : Send DC and TEMA logs. \n\n * \n\n\nAbbreviations and Definitions: [/support/docview.wss?uid=swg21407069&amp;aid=1] [/support/docview.wss?uid=swg21407069&amp;aid=1] DC Data Collector TEMA Tivoli Enterprise Monitoring Agent (ITCAM for SOA Agent) TEP\nTEMS\nTCOR\nSDMS\nDP\nITM Tivoli Enterprise Portal\nTivoli Enterprise Monitoring Server\nTivoli Common Object Repository\nSOA Domain Management Server\nData Power\nIBM Tivoli Monitoring \nProblem Occurring : Collect Doc for : SDMS and Topology View * DC log and the Description of what you expect the view to show \n * If \"performance summary\" NOT working, send TEMA logs using following link -\n\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21422604&collections=technotes:hpmrs [http://www-01.ibm.com/support/docview.wss?uid=swg21422604&collections=technotes:hpmrs] (for TEMA logs)\n * If \"operational flow\" NOT working, send SDMS and related TEPS logs using following link - \n\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21422496&collections=technotes:hpmrs [http://www-01.ibm.com/support/docview.wss?uid=swg21422496&collections=technotes:hpmrs] (for SDMS logs)\n\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21422652&collections=technotes:hpmrs [http://www-01.ibm.com/support/docview.wss?uid=swg21422652&collections=technotes:hpmrs] (for related TEPS logs) History Data not available * TEMA log \n * TEPS log \n * Warehouse Proxy Agent log \n * TEMS log,\n\nIf SOA is not directly connected to a HUB, then send Remote TEMS log DLA \n(Discovery Library Adapter) * DC log and TEMA log \n * SDMS log and TCORE log\n\nITM (TEMS, TEPS) * TEMA log \n * TEPS and TEMS log\n\nData Power Appliance * Send the requested logs described in following link -http://www.ibm.com/support/docview.wss?&uid=swg21305909 [http://www.ibm.com/support/docview.wss?&uid=swg21305909]\n\n\n\nCollecting Data Collector (DC) Data Note : \n1. Please turn on UpdateTracing_610 takeAction to collect DC trace, if possible. \nClick this for the UpdateTracing_610 takeAction instruction => \nhttp://www.ibm.com/support/docview.wss?uid=swg21408921 [http://www.ibm.com/support/docview.wss?uid=swg21408921] \n\n2. Zip/Tar up following directory from SOA installed machine of your specific platform. \n\n** Windows Location <ITM_HOME>\\TMAITM6\\KD4\\logs and all its subdirectories\n<ITM_HOME>\\TMAITM6\\ KD4\\config \n** UNIX, Linux and z/OS Location <ITM_HOME>/<os>/d4/KD4/logs and all its subdirectories \n<ITM_HOME>/<os>/d4/KD4/config \n\nCollecting Monitoring Agents (TEMA) Data \nNote : Zip/Tar up following directory from SOA installed machine of your specific platform. \n\n** Both Windows and Unix Location <ITM_HOME>\\logs\\<hostname>_d4_<timestamp>*.log files \n\nCollecting ITM TEMS and TEPS Data \nNote : Use following provided link to get the data for your specific ITM component error case. \n\nAll ITM V6 Components http://www.ibm.com/support/docview.wss?&uid=swg21266383 [http://www.ibm.com/support/docview.wss?&uid=swg21266383] TEMS ** Windows, Linux, Unix, z/OS \nhttp://www.ibm.com/support/docview.wss?&uid=swg21269622 [http://www.ibm.com/support/docview.wss?&uid=swg21269622] TEPS ** Windows, Linux, Unix \nhttp://www.ibm.com/support/docview.wss?uid=swg21297524 [http://www.ibm.com/support/docview.wss?uid=swg21297524] TEP ** Windows : <ITM_HOME>\\CNP\\logs\n** Linux/UNIX : <ITM_HOME>/<os>/cj/logs \n\nCollecting TCORE and SDMS Data \nNote : Zip/Tar up following directory from TEPS installed machine of your specific platform. \n\n** Windows Location <ITM_HOME>\\CNPSJ\\profiles\\ITMProfiles|logs\\ITMServer\\SystemOut.log and SystemErr.log \n** UNIX, Linux Location <ITM_HOME>/<platform>/iw/profiles/ITMProfile/logs/ITMServer/SystemOut.log and SystemErr.log \n\nCollecting for ITCAM for SOA and WebSphere DataPower Problem Determination \nData Power http://www.ibm.com/support/docview.wss?&uid=swg21305909 [http://www.ibm.com/support/docview.wss?&uid=swg21305909] \n\nPRODUCT ALIAS/SYNONYM\n ITCAM for SOA", " A README IS AVAILABLE\nIBM Tivoli Composite Application Manager for SOA 7.2 Interim Fix 12 README 7.2.0.1-TIV-ITCAMSOA-IF0012 [http://www-01.ibm.com/support/docview.wss?uid=isg400003852]\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 * Problem Description :\n \n If the user in the Operation Flow view selects a node to View\n Interaction Detail, the Interaction Detail view shows an error\n (KD4UI0003E) instead of an interaction topology. The TEPS eWAS\n SystemOut.log shows the following exceptions.\n \n [3/28/16 11:02:43:182 EDT] 0000982c SDMSUIAccessI E\n com.ibm.management.soa.dms.query.impl.SDMSUIAccessImpl\n getOperationDetailsForGUID An error was encountered while\n creating the graph.\n \n com.ibm.management.soa.dms.exceptions.DMSDataFormatException:\n com.ibm.management.soa.dms.exceptions.DMSDataFormatException\n KD4DM0023E The SDMS command failed due to errors accessing the\n SDMS database.: com.ibm.db2.jcc.am.SqlDataException: DB2 SQL\n Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null,\n DRIVER=3.64.96\n at\n com.ibm.management.soa.dms.access.dao.BaseInstanceView.setOperat\n ionsInstanceFocaleNodeToGraph(BaseInstanceView.java:3326)\n at\n com.ibm.management.soa.dms.access.dao.BaseInstanceView.findInsta\n nceRelationships(BaseInstanceView.java:309)\n at\n com.ibm.management.soa.dms.access.factory.impl.PersistenceFactor\n yImpl.findInstanceRelationships(PersistenceFactoryImpl.java:366)\n at\n com.ibm.management.soa.dms.query.impl.SDMSUIAccessImpl.getOperat\n ionDetailsForGUID(SDMSUIAccessImpl.java:1246)\n at\n com.ibm.management.soa.dms.ejb.access.AccessManagerBean.getOpera\n tionDetailsForGUID(AccessManagerBean.java:589)\n at\n com.ibm.management.soa.dms.ejb.access.EJSLocalStatelessAccessMan\n ager_c8a58271.getOperationDetailsForGUID(Unknown Source)\n at\n com.ibm.management.soa.dms.ejb.facade.SDMSFacadeBean.invokeAcces\n sBeanMethods(SDMSFacadeBean.java:586)\n at\n com.ibm.management.soa.dms.ejb.facade.SDMSFacadeBean.invokeQuery\n (SDMSFacadeBean.java:225)\n at\n com.ibm.management.soa.dms.ejb.facade.EJSRemoteStatelessSDMSFaca\n de_7c3bc5ed.invokeQuery(Unknown Source)\n ....\n \n caused by\n \n com.ibm.db2.jcc.am.SqlDataException: DB2 SQL Error:\n SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=3.64.96\n ....\n at\n com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeQuery(W\n SJdbcPreparedStatement.java:712)\n at\n com.ibm.management.soa.dms.access.dao.JDBCHelper.executeQuery(JD\n BCHelper.java:283)\n at\n com.ibm.management.soa.dms.access.dao.StandardBPDDescription.get\n BPDDescriptionByProcessApplicationVersion(StandardBPDDescription\n .java:561)\n at\n com.ibm.management.soa.dms.access.dao.BaseInstanceView.setOperat\n ionsInstanceFocaleNodeToGraph(BaseInstanceView.java:3307)\n at\n com.ibm.management.soa.dms.access.dao.BaseInstanceView.findInsta\n nceRelationships(BaseInstanceView.java:309)\n at\n com.ibm.management.soa.dms.access.factory.impl.PersistenceFactor\n yImpl.findInstanceRelationships(PersistenceFactoryImpl.java:366)\n at\n com.ibm.management.soa.dms.query.impl.SDMSUIAccessImpl.getOperat\n ionDetailsForGUID(SDMSUIAccessImpl.java:1246)\n at\n com.ibm.management.soa.dms.ejb.access.AccessManagerBean.getOpera\n tionDetailsForGUID(AccessManagerBean.java:589)\n at\n com.ibm.management.soa.dms.ejb.access.EJSLocalStatelessAccessMan\n ager_c8a58271.getOperationDetailsForGUID(Unknown Source)\n at\n com.ibm.management.soa.dms.ejb.facade.SDMSFacadeBean.invokeAcces\n sBeanMethods(SDMSFacadeBean.java:586)\n at\n com.ibm.management.soa.dms.ejb.facade.SDMSFacadeBean.invokeQuery\n (SDMSFacadeBean.java:225)\n at\n com.ibm.management.soa.dms.ejb.facade.EJSRemoteStatelessSDMSFaca\n de_7c3bc5ed.invokeQuery(Unknown Source\n \n Approver :\n L3 - BG\n L2 - IS\n \n LOCAL FIX:\n none\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: ITCAM for SOA Interaction Detail topology *\n * users on all platforms. *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * If a service port namespace is longer than 64 characters the *\n * BPM code attempts to insert the full length string into a *\n * smaller buffer and this throws an exception. *\n * *\n * The fix limits the length of a namespace query that was *\n * causing database errors and preventing users from viewing *\n * certain interaction detail topologies. *\n ****************************************************************\n * RECOMMENDATION: Apply fix when it is available. *\n ****************************************************************\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Apply the IFix when it is available.\n \n The fix for this APAR is contained in the following maintenance\n packages:\n | interim fix | 7.2.0.1-TIV-ITCAMSOA-IF0010\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IV83741\n \n \n * REPORTED COMPONENT NAME\n ITCAM FOR SOA-D\n \n \n * REPORTED COMPONENT ID\n 5724SOA00\n \n \n * REPORTED RELEASE\n 720\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 2016-04-14\n \n \n * CLOSED DATE\n 2016-08-04\n \n \n * LAST MODIFIED DATE\n 2016-08-04\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 ITCAM FOR SOA-D\n \n \n * FIXED COMPONENT ID\n 5724SOA00\n \n \n\nAPPLICABLE COMPONENT LEVELS" ]

[ [ "2a", "CAMSOAALL CAMSOADB CAMSOAPERF REQMETRICS RESPMETRICS kd4TrimDB2db TECHNOTE (FAQ) QUESTION" ], [ "2b", " As the KD4SDMS grows unbounded, is there a way to regularly prune it? ANSWER" ], [ "2c", "Regarding the older release ITCAM for SOA 7.1.1, there is no a mechanism to automatically regularly prune the KD4SDMS database." ], [ "2d", "The following Wiki page has been published on the topic: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Composite+Application+Manager/page/Pruning+SDMS+Relationship+Metrics+Tables [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Composite+Application+Manager/page/Pruning+SDMS+Relationship+Metrics+Tables]" ], [ "2e", "To keep only the latest 24 hours every day (regular pruning), you can schedule a daily job to run the kd4TrimDB2db utility provided above." ], [ "2f", "As for the newer ITCAM for SOA 7.2, there is a cleanup task that runs on the TEPS host where SDMS database is installed." ], [ "2g", "It deletes REQMETRICS and RESPMETRICS table rows where SRTTIME (start of period) is more than 24 hours ago." ], [ "2h", "So these two tables, which are responsible for most of KD4SDMS storage occupation, should not grow unbounded anymore." ], [ "2i", "NOTE: ITCAM for SOA 7.1.1 is Out-Of-Support since 2015 April 30." ] ]

[ "2c", "2e", "2f", "2g" ]

[ "st14willkc PRODUCT DOCUMENTATION\n\nABSTRACT\n This document contains the statement of support for the IBM MQ resource adapter provided with IBM MQ V8.0 \n\nCONTENT\nThe resource adapter that comes with IBM MQ Version 8.0 uses JMS 2.0, and can only be deployed into an application server that is Java™ EE 7 compliant and therefore supports JMS 2.0. \n\n\n\nDeployment within WebSphere Application Server - Liberty profile\nWebSphere Application Server Liberty Profile 8.5.5.6 and later can be configured to use either an IBM MQ V8.0 or a WebSphere MQ V7.5 resource adapter. WebSphere Application Server Liberty Profile 8.5.5.6 became a Java™ EE 7 certified application sever so the IBM MQ V8 resource adapter can be used. \n\nThe WebSphere Application Server Liberty Profile contains both wmqJmsClient-1.1 and wmqJmsClient-2.0 features to permit working with both JMS 1.1 and JMS 2.0 resource adapters respectively. \n\nInformation on this configuration is in the Scenario Connecting WebSphere Application Server Liberty Profile to WebSphere MQ [http://www-01.ibm.com/support/knowledgecenter/prodconn_1.0.0/com.ibm.prodconn.doc/infocenter_homepage/mqwasliberty_home.htm?cp=SSFKSJ_7.5.0%2F8&lang=en]. \n\nDeployment within WebSphere Application Server\nThe IBM MQ V8.0 resource adapter cannot be deployed in WebSphere Application Server.\n\nWebSphere Application Server is supplied with a WebSphere MQ resource adapter already installed. This resource adapter can connect to Version 8 queue managers. For more information, please see the section called \"Connectivity IBM MQ V8 queue managers\"\n\n\nUsing the resource adapter with other application servers\nFor all other Java™ EE 7 compliant application servers, problems following successful completion of the IBM MQ resource adapter Installation Verification Test (IVT) can be reported to IBM for the investigation of IBM MQ product trace and other IBM MQ diagnostic information. If the IBM MQ resource adapter IVT cannot be run successfully, problems encountered are likely to be caused by incorrect deployment or incorrect resource definitions which are application server specific and the problems should be investigated using application server documentation and / or the support organization for that application server.\n\nIBM has tested the resource adapter IVT on the application servers listed below \n\n * Glassfish V4 \n * Wildfly V8\n\n\nJava Runtime \nThe Java Runtime (JRE) that is used to run the application server must be one that is supported with the MQ Client V8. These are listed in the IBM System Requirements for IBM MQ v8 [http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Miscellaneous_569814401AEF11E38F7D228059AF1569#sw-2]. (Follow the 'Java' link listed under the Supported Software tab). \n\nConnectivity to IBM MQ V8 queue managers \nThe full range of JMS 2.0 functionality is available when connecting to a Version 8 queue manager using the Version 8 resource adapter that has been deployed into a Java EE 7 application server. \n\nIf you are using an application server which is not Java EE 7 compliant and does not support JMS 2.0 (for WebSphere Application Server this is currently Versions 7.0 to 8.5.5), you can still connect to IBM MQ V8 queue managers using an older version of the WebSphere MQ resource adapter. With this configuration it is not possible to make use of the new JMS 2.0 functionality provided by IBM MQ V8, however existing JMS 1.1, and earlier, functionality will be preserved. \n\nConnectivity to WebSphere MQ V7.5 queue managers and earlier \nIt is supported to deploy the IBM MQ V8 resource adapter into a Java EE 7 compliant application server that supports JMS 2,0, and connect that resource adapter to a queue manger running WebSphere MQ V7.5 or earlier. The functionality that will be available will be limited by the capabilities of the queue manager. \n\nThis is supported for both the BINDINGS and CLIENT transport. When using the BINDINGS transport, ensure that the java.library.path is set to: \n * MQ_INSTALLATION_PATH\\java\\lib if the application server is running with a 32-bit Java runtime environment. \n * MQ_INSTALLATION_PATH\\java\\lib64 if the application server is running with a 64-bit Java runtime environment.\n\n\nwhere MQ_INSTALLATION_PATH is the location where WebSphere MQ has been installed. If there are multiple WebSphere MQ installations on the same system, MQ_INSTALLATION_PATH should be the location where the latest version of WebSphere MQ has been installed. \n\nGeneral issues \n\nSession interleaving is not supported: \nSome application servers provide a capability called session interleaving, where the same JMS session can be used in multiple transactions, although it is only enlisted in one at a time. This is not supported by the WebSphere MQ resource adapter, and can lead to the issues shown below: \n * An attempt to put a message to a WebSphere MQ queue fails with reason code 2072 (MQRC_SYNCPOINT_NOT_AVAILABLE). \n * Calls to xa_close() fail with reason code -3 (XAER_PROTO), and an FDC with probe ID AT040010 is generated on the WebSphere MQ queue manager being accessed from the application server.\n\n\nPlease see your application server documentation for how to disable this capability. \n\nJava™ Transaction API (JTA) Specification of how XA resources are recovered for XA transaction recovery: \nSection 3.4.8 of the JTA specification does not define a specific mechanism by which XA resources are recreated to perform XA transactional recovery. As such, it is up to each individual transaction manager (and therefore application server) how XA resources involved in an XA transaction are recovered. It is possible that, for some application servers, the WebSphere MQ resource adapter does not implement the application server specific mechanism utilized to perform XA transactional recovery.", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n A JMS application works as expected when using the WebSphere MQ V6 Classes for JMS.\nWhen the application is migrated to the WebSphere MQ V7 Classes for JMS, the application appears to suffer performance degradation. \n\nSYMPTOM\nAnalysis from the Queue Manager perspective when the application is running shows a large number of connections being created and closed.\n\n\nCAUSE\nThe internal JMS connection pooling functionality has been removed from the WebSphere MQ V7 classes for JMS. \n\n \nThe connection pooling functionality provided by the WebSphere MQ V6 classes for JMS allowed connection handles (Hconns) to WebSphere MQ to be stored in a pool where they were available for reuse. This functionality was implemented using the WebSphere MQ classes for Java. This was possible because the WebSphere MQ V6 classes for JMS were implemented as a layer of code on top of the WebSphere MQ V6 classes for Java. In WebSphere MQ V7 the implementation of WebSphere MQ classes for JMS is no longer dependent on WebSphere MQ classes for Java. This means that the WebSphere MQ classes for JMS can no longer access features of the WebSphere MQ classes for Java.\n\nWhen using the WebSphere MQ V6 classes for JMS inside of a Java EE application server, two levels of pooling were provided: \n\n\n * Java EE application servers provided JMS Connection Pools and JMS Session Pools for applications to use.\n\n * When the application server was configured to use the WebSphere MQ V6 classes for JMS, these JMS Connection and JMS Session Pools sat on top of the connection handle pooling provided by the WebSphere MQ classes for JMS. \n\n\nThis led to some confusion about how the JMS Connection and Session Pools provided by application servers worked. It might have looked like there were still open connections from the application servers to WebSphere MQ, even though the JMS Connection and JMS Session Pools were empty. This was because the connection handles associated with the JMS Connections and JMS Sessions that had been removed from the application server Connection and Session Pools were now in the underlying WebSphere MQ classes for JMS connection handle pool. \n\nWhen the WebSphere MQ V7 classes for JMS are used in JEE Application Server environments, JMS Connection and JMS Session Pools are provided as follows: \n * For Inbound Communications, the JMS Connection Pools and JMS Session Pools are implemented by the WebSphere MQ JCA resource adapter. \n * For Outbound Communications, the JMS Connection Pools and JMS Session Pools are implemented by the JEE Application Server. \n\nRESOLVING THE PROBLEM\nStand-alone applications using the WebSphere MQ V7 classes for JMS that require the use of JMS Connection and JMS Session pooling need to be modified to implement their own pooling logic.", "com.sun.jndi.fscontext.RefFSContextFactory; security exit mqminfo TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You are not using LDAP. You must pass a userid and password pair from a JMS client using JNDI to be validated by WebSphere MQ. \n\n\n\nSYMPTOM\nThe process for writing the server-side security exit [http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.dev.doc/q028010_.htm]is well documented in the online documentation for WebSphere MQ.. Unfortunately, there was less documentation available which shows how to write a security exit in Java in previous levels of WebSphere MQ. The more recent versions of the WebSphere MQ online documentation contain information on Creating a channel exit in WebSphere MQ classes for Java [http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.dev.doc/q031040_.htm]. The steps below were documented here for the versions of WebSphere MQ, previous to V7.0, to elaborate on the process of writing a security exit in Java. The steps below remain valid, but the new method is preferred for improved functionality and performance. Since it is still valid for current versions, this document can be used as an additional reference point. However, please refer to Creating a channel exit in WebSphere MQ classes for Java [http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.dev.doc/q031040_.htm] for the more up to date and preferred instructions. \n\n\nRESOLVING THE PROBLEM\nUse a security exit program on both the client (QCF and TCF) and the server (SVRCONN) definitions. You will need two exits: \n\n * A server-side security exit, written in C, which is associated with the SVRCONN channel used by the JMS application to talk to the MQ Server. \n * A client-side security exit, written in Java™, which is associated with the Connection Factory used by the JMS application.\n \n\n\nReminder: The steps below remain valid, but the new method is preferred for improved functionality and performance . Please refer to Creating a channel exit in WebSphere MQ classes for Java [http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.dev.doc/q031040_.htm] for the more up to date and preferred instructions. \n\nOld method for writing a security exit in Java: \n\nFirst, write a class which implements the MQSecurityExit interface. This class must implement a constructor (which takes a string as a parameter) and the securityExit method, which takes three parameters:\n\n\n * MQChannelExit securityExit - this contains information about the context in which the method is being invoked. \n * MQChannelDefinition channelDefinition - details of the channel used to communicate with the queue manager. \n * byte[] agentBuffer - this buffer holds the data which has been received from the server-side security exit. \n \n \n\n\n\nThe first thing the method should do is to check the value of the exitReason variable in the securityExit object, which indicates why the security exit was called. If the exitReason is set to MQXR_INIT the security exit should copy the user name and password to the agentBuffer, and set the exitResponse variable to MQXCC_SEND_SEC_MESSAGE. This will direct MQ to forward the data in the buffer to the WebSphere MQ server. * \n\n\nThe server-side security exit should now validate the username password it has received, and can take two actions: * Allow the client to continue by setting exitResponse to MQXCC_OK. \n * Prevent the JMS application from connecting by setting exitResponse to MQXCC_SUPPRESS_FUNCTION. \n \n\n\nRegardless of the value of the exitResponse set by the server-side exit, the client-side security exit will now be called with the exitReason set to MQXR_TERM. The security exit should now perform any necessary shut-down processing. It does not need to worry about closing the connection with the queue manager as the WebSphere MQ server will do this if necessary. When it is finished cleaning up, the security exit should set the exitResponse variable to MQXCC_OK to indicate the security checks are finished. \n\nIn order to use the security exit, the Connection Factory used by your JMS client must have: \n\n * \n * \n\n\nIf you wish to pass a string to the security exit constructor, be sure to set: \n\n * \n * \n * \n\n\nFor further information refer to the WebSphere MQ Using Java manual [http://publibfp.boulder.ibm.com/epubs/pdf/csqzaw12.pdf] Chapter 5. Using the MQ JMS administration tool -> Administering JMS objects->Properties and specify a security exit built on both the client (sending) and the Server (receiving) channels. \n\n\nThe samples attached to this item demonstrate the old method of using JMS with JNDI. \n\nsvrauth.c [/support/docview.wss?uid=swg21175189&aid=2] [/support/docview.wss?uid=swg21175189&aid=1]MyMQExits.java [/support/docview.wss?uid=swg21175189&aid=4] [/support/docview.wss?uid=swg21175189&aid=3]JMSPutExitDriver.java [/support/docview.wss?uid=swg21175189&aid=6] [/support/docview.wss?uid=swg21175189&aid=5]\n\nDISCLAIMER\nAll 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. \n\nPRODUCT ALIAS/SYNONYM\n WMQ MQ", "develop Developing testing MDB RAD 7.5 WebSphere Application Server V7 MQ V7 JMS Provider WHITE PAPER\n\nABSTRACT\n Demonstrate the steps to develop and test a Message Driven Bean (MDB) using Rational Application Developer (RAD) 7.5 and WebSphere Application Server V7, while using WebSphere MQ V7 as Java ™ Messaging Service (JMS) Provider. \n\nCONTENT\nThe document is provided in the attached file: Developing_and_testing_MDB_on_RAD7.pdf\n\n\nThis demonstrates the steps required to develop and test a Message Driven Bean (MDB) using Rational Application Developer (RAD) 7.5 and WebSphere Application Server V7, while using WebSphere MQ V7 as the Java Messaging Service (JMS) Provider.\n\nThe testing scenario shows how the Listener Port for WebSphere Application Server gets a message from an MQ Queue (Point to Point) and passes it to the MDB, which displays the contents of the text message. This MDB is a simple but functional application.\n\nThe following file (available with this techdoc) includes the MDB as it was developed, tested and exported as described in this document:\nEAR file with MDB: SampleMDBEJB.ear \n\nThe document is provided in the attached file: Developing_and_testing_MDB_on_RAD7.doc\nThis document shows all the screen shots needed for beginners.\nThis document has the following chapters:\n1: RAD 7.5 development of the MDB\n2: RAD 7.5 testing of the MDB using WebSphere Application Server 7\n\n\nRelated techdoc \nIt is necessary to configure MQ and WebSphere Application Server with the objects that are used in this scenario. Consult the following techdoc for details:\n\nUsing WebSphere MQ V7 as JMS Provider for WebSphere Application Server V7, V8.0 and V8.5 [http://www.ibm.com/support/docview.wss?rs=171&uid=swg27016505]\nChapter 1: MQ V7 configuration: queue and topic\nChapter 2: WebSphere Application Server V7 configuration: JNDI objects\n\nRequisite software\nThe following software was used: \n\n * SUSE Linux Enterprise Server (SLES) 9: \n * Rational Application Developer 7.5 \n * WebSphere Application Server 7.0.0.5 \n * WebSphere MQ 7.0.0.2 \n * Firefox (also known as Mozilla)\n\n\nDownloadable files \nThe following files are included as attachments to this techdoc: * Developing_and_testing_MDB_on_RAD7.pdf \n * EAR file with MDB: SampleMDBEJB.ear \n * Text file with code excerpt: onMessage.txt\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. \n\n\nDeveloping_and_testing_MDB_on_RAD7.pdf [/support/docview.wss?uid=swg27016507&aid=2] [/support/docview.wss?uid=swg27016507&aid=1]\nFile name: Developing_and_testing_MDB_on_RAD7.pdf\nFile size: 2 MB\n\nSampleMDBEJB.ear [/support/docview.wss?uid=swg27016507&aid=4] [/support/docview.wss?uid=swg27016507&aid=3]\nFile name: SampleMDBEJB.ear\nFile size: 4 KB \n\nonMessage.txt [/support/docview.wss?uid=swg27016507&aid=6] [/support/docview.wss?uid=swg27016507&aid=5]\nFile name: onMessage.txt\nFile size: 1 KB\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Java Message Service (JMS) AIX, HP-UX, Linux, Solaris 7.0 Software Development Rational Application Developer for WebSphere Software Application Deployment Windows, Linux 7.0 PRODUCT ALIAS/SYNONYM\n WebSphere MQ WMQ WebSphere Application Server WAS WSAS Rational Application Developer RAD", " TECHNOTE (FAQ)\n\nQUESTION\n How do I use a subscription manually predefined in the queue manager with a WebSphere MQ classes for JMS client application, running in either JEE or J2SE environments? \n\nANSWER\nA WebSphere MQ V7 subscription has two different ways of defining the message destination: Managed or Provided. In the managed destination mode, the queue manager manages the queue used to store messages for the subscriber, automatically removing the queue when it is no longer required, and removing unconsumed messages as necessary. In provided destination mode, an unmanaged queue is provided by the administrator, and messages for the subscriber are placed upon that queue. If a subscription is deregistered, and the queue and messages are no longer required, the administrator needs to remove the queue from the queue manager. \n\nThe WebSphere MQ classes for JMS use the managed destination mode when creating a subscription, and do not provide a way to use a predefined subscription, or allow the application to specify the subscription destination to use. \n\n \n\nTo use predefined subscriptions with WebSphere MQ classes for JMS, so that the location of the published messages for the subscriber is known and does not change, a combination of JMS point-to-point messaging, and a WebSphere MQ subscription to a provided queue can be used. This requires a subscription in the queue manager to be defined that places messages onto a provided queue, and then the WebSphere MQ classes for JMS to be configured to directly read messages from that queue in point-to-point mode, using a JMS queue destination. From a JMS application perspective, it is not consuming a message published to a topic, but reading messages from a JMS queue. \n\n \n\nExample steps could include: \n\n \n\n 1. Define an MQ queue to store the messages on, for example \"MySUBQ\" \n 2. Create a subscription to the required topic that uses a Destination class of PROVIDED, and specify the queue name of \"MySUBQ\" \n 3. Configure the JMS application to read messages from a WebSphere MQ classes for JMS Queue object with the Queue field set to \"MySUBQ\", defined using a tool such as JMSAdmin. Note that the JMS application should not use the JMS Publish/Subscribe features, and only use the JMS Point-to-Point interfaces.\n\n\nWhen messages are published to the required topic, the queue manager places a message for the subscription on the destination queue \"MySUBQ\", and the JMS application reads it from that queue.\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Java Message Service (JMS) AIX, HP-UX, i5/OS, IBM i, Linux, Solaris, Windows, z/OS 8.5, 8.0, 7.0 \nPRODUCT ALIAS/SYNONYM\n WebSphere MQ WMQ WebSphere Application Server WAS" ]

[ [ "4a", " TECHNOTE (FAQ) QUESTION" ], [ "4b", " How do I use a subscription manually predefined in the queue manager with a WebSphere MQ classes for JMS client application, running in either JEE or J2SE environments? ANSWER" ], [ "4c", "A WebSphere MQ V7 subscription has two different ways of defining the message destination: Managed or Provided." ], [ "4d", "In the managed destination mode, the queue manager manages the queue used to store messages for the subscriber, automatically removing the queue when it is no longer required, and removing unconsumed messages as necessary." ], [ "4e", "In provided destination mode, an unmanaged queue is provided by the administrator, and messages for the subscriber are placed upon that queue." ], [ "4f", "If a subscription is deregistered, and the queue and messages are no longer required, the administrator needs to remove the queue from the queue manager." ], [ "4g", "The WebSphere MQ classes for JMS use the managed destination mode when creating a subscription, and do not provide a way to use a predefined subscription, or allow the application to specify the subscription destination to use." ], [ "4h", "To use predefined subscriptions with WebSphere MQ classes for JMS, so that the location of the published messages for the subscriber is known and does not change, a combination of JMS point-to-point messaging, and a WebSphere MQ subscription to a provided queue can be used." ], [ "4i", "This requires a subscription in the queue manager to be defined that places messages onto a provided queue, and then the WebSphere MQ classes for JMS to be configured to directly read messages from that queue in point-to-point mode, using a JMS queue destination." ], [ "4j", "From a JMS application perspective, it is not consuming a message published to a topic, but reading messages from a JMS queue." ], [ "4k", "Example steps could include: 1." ], [ "4l", "Define an MQ queue to store the messages on, for example \"MySUBQ\" 2." ], [ "4m", "Create a subscription to the required topic that uses a Destination class of PROVIDED, and specify the queue name of \"MySUBQ\" 3." ], [ "4n", "Configure the JMS application to read messages from a WebSphere MQ classes for JMS Queue object with the Queue field set to \"MySUBQ\", defined using a tool such as JMSAdmin." ], [ "4o", "Note that the JMS application should not use the JMS Publish/Subscribe features, and only use the JMS Point-to-Point interfaces." ], [ "4p", "When messages are published to the required topic, the queue manager places a message for the subscription on the destination queue \"MySUBQ\", and the JMS application reads it from that queue." ], [ "4q", "Cross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Java Message Service (JMS) AIX, HP-UX, i5/OS, IBM i, Linux, Solaris, Windows, z/OS 8.5, 8.0, 7.0 PRODUCT ALIAS/SYNONYM" ], [ "4r", " WebSphere MQ WMQ WebSphere Application Server WAS" ] ]

[ "4b", "4c", "4d", "4e", "4f", "4g", "4h", "4i", "4j", "4k", "4l", "4m", "4n", "4o", "4p" ]

[ "Endpoint-open-mic; ilmt-open-mic; STEwebcastDocument; ISS_OPEN_MIC WEBCAST\n\nABSTRACT\n The Support team talked about how to install or upgrade to the newly released IBM License Metric Tool (ILMT) version 9.2.8. Attendees were given an opportunity to ask questions of the panel of experts. \n\nCONTENT\nFor this open mic session, Silviu Gligore and his teammates provided a collection of resources so you can install the latest ILMT/BFI update successfully.\n\n\n * Topic: Install or upgrade IBM License Metric Tool and BigFix Inventory to version 9.2.8 \n * Date: Wednesday, 19 July Month 2017 \n * Time: 10:00 AM EDT (14:00 UTC/GMT, UTC-4 hours) \n\nHow to ask questions on the topic To ask a question, please use the \" Community questions and discussion\" option near the bottom of this page. \n\n\nPresentation OpenMic-Install-or-upgrade-ILMTBFI-to-V9.2.8post-event.pdf [/support/docview.wss?uid=swg27050061&aid=2]OpenMic-Install-or-upgrade-ILMTBFI-to-V9.2.8post-event.pdf [/support/docview.wss?uid=swg27050061&aid=1] \n\n\nAudio Replay The recording of the session is available on the IBM Security Support YouTube channel [https://www.youtube.com/IBMSecuritySupport] at https://youtu.be/--HXvs41Fao [https://youtu.be/--HXvs41Fao] \n\n\nAbout Open Mic Webcasts This Open Mic session was the sixth webcast provided by ILMT Technical Support in 2017. Our goal is to provide insight on how the License Metric Tool works and to teach on-going sessions that help users and administrators understand, maintain, troubleshoot, and resolve issues with their their software license monitoring. \nIBM Security Support wants to help you take full advantage of your products. Join us for our Open Mic Webcast series as technical experts share their knowledge and answer your questions. These webcasts are designed to address specific topics and provide an in-depth and focused technical exchange in a convenient online webcast format. \nVisit the Support technical exchanges for IBM Security [https://support.podc.sl.edst.ibm.com/support/home/exchanges-listing/K527788Q35237V48/IBM_Security_support_(general)/product] page to see lists of all scheduled and past Open Mic events. \n[https://www-947.ibm.com/support/entry/myportal/scheduled_tech_exchanges/security_systems/security_systems_support_%28general%29?productContext=-1089885148] \nTo be on the mailing list that gets notified about Security Support's Open Mic webcasts, send an e-mail to [email protected] [[email protected]?subject=ste%20subscribe%20Endpoint%20And%20Mobility%20Management] with the subject line: \nste subscribe Endpoint And Mobility Management \n\nWe welcome you to follow us on Twitter [http://bit.ly/1jZ80d3] @AskIBMSecurity [http://bit.ly/1jZ80d3]. \nWe welcome you to like us on Facebook [https://www.facebook.com/IBMSecuritySupport]. \n\nRELATED INFORMATION\n BigFix Inventory - What's new in v9.2.8 [https://youtu.be/HMThvxfunks]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Security IBM BigFix Inventory", " SECURITY BULLETIN\n\nSUMMARY\n Vulnerability in REST API present in IBM License Metric Tool and IBM Endpoint Manager for Software Use Analysis allows for extraction of information. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-4929 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4929]\nDESCRIPTION: IBM License Metric Tool could allow an authenticated attacker to extract sensitive information due to incorrect handling of REST API requests.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/104097 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104097] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:S/C:P/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM License Metric Tool v9 \n\nIBM Endpoint Manager for Software Use Analysis v9\n\nREMEDIATION/FIXES\nUpgrade to version 9.2.1.0 or later: \n\n * In IBM Endpoint Manager console, expand IBM License Reporting or IBM BigFix Inventory node under Sites node in the tree panel. \n * Click Fixlets and Tasks node. Fixlets and Tasks panel will be displayed on the right. \n * In the Fixlets and Tasks panel locate Upgrade to the newest version of License Metric Tool 9.x or Upgrade to the newest version of IBM BigFix Inventory 9.x fixlet and run it against the computer that hosts your IBM License Metric Tool or IBM Endpoint Manager for Software Use Analysis server.\n\n\nNote: In an airgapped environment, you have to run BESAirgapTool and BESDownloadCacher first in order to update your site. 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\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 Security IBM BigFix Inventory", " SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere Application Server is shipped with IBM License Metric Tool 7.5 and IBM Tivoli Asset Discovery for Distributed 7.5.\nInformation about a security vulnerability affecting WebSphere Application Server has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nRefer to the security bulletin(s) listed in the Remediation/Fixes section.\n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nProduct and Version(s) IBM License Metric Tool 7.5\nIBM Tivoli Asset Discovery for Distributed 7.5 REMEDIATION/FIXES\nRefer to the following security bulletins for vulnerability details and information about fixes addressed by IBM WebSphere Application Server which is shipped with IBM License Metric Tool 7.5 and IBM Tivoli Asset Discovery for Distributed 7.5.\n\n\n\nPrincipal Product and Version(s) Affected Supporting Product and Version Affected Supporting Product Security Bulletin IBM License Metric Tool 7.5\n\nIBM Tivoli Asset Discovery for Distributed 7.5 WebSphere Application Server 7.0 Security Bulletin: Multiple vulnerabilities in IBM® Java SDK affects WebSphere Application Server July 2016 CPU (CVE-2016-3485) [http://www-01.ibm.com/support/docview.wss?uid=swg21988339] WORKAROUNDS AND MITIGATIONS\nN/A\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] *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 Security Tivoli Asset Discovery for Distributed AIX, Windows, HP-UX, Linux, Solaris 7.5", " NEWS\n\nABSTRACT\n IBM Security Support announced in October, 2017, that changes to your online IBM License Metric Tool (ILMT) Support experience were coming. See below for the text of the mailing to that was sent to Support customers. \n\nCONTENT\n\nDear IBM License Metric Tool Customer,\n\nIn addition to the recently announced LMT forum process [http://ibm.biz/ILMTforumAnnounce], we are excited to announce that we are launching a new online Support experience. Most IBM Security products, including IBM License Metric Tool, will go live with this new technology at the end of October, 2017. \n\nThe move to this new online Support experience should be seamless for you. \n\n\n * As announced earlier this year, IBM dW Answers [https://developer.ibm.com/answers/index.html] should still be your first avenue to Support. \n * The e-mail and phone support channels offered to you today will remain unchanged. \n * Your bookmarks and existing access methods will automatically connect to the new online Support experience once you’ve selected your IBM Security product or you can use a new URL to reach the new online Support experience directly: https://www.ibm.com/mysupport [https://www.ibm.com/mysupport]. \n * Any existing PMRs will be automatically converted to “Cases” in the new experience. Simply choose “cases” from the Security product support landing page to see status or make updates. \n\n\nIf you are experiencing a problem with the portal (such as a login issue, etc.), we are here to help. You can submit your issue via our Support page [https://www.ibm.com/mysupport/s/] by clicking “Email IBM Support”, or by emailing [email protected]. \n\nShould you have any questions, please send email to [email protected] [[email protected]?subject=Changes%20to%20your%20IBM%20Support%20experience]. [/support/docview.wss?uid=swg22009938&amp;aid=1] IBM Security Support Team \n\nPRODUCT ALIAS/SYNONYM\n LMT", "self help; newsletter; troubleshooting; FAQs; administration; problem solving; documentation; install; configuration; BFI NEWSLETTER\n\nABSTRACT\n Client self assist - Technical Support information for ILMT, BFI (and TAD4D) administrators and users.\nMail date was October 31, 2017. \n\nCONTENT\n\n\nThis edition contains links to technical support documents and information. It is intended to help you be proactive in the support and administration of your software. \nNew for you\n * \n * New online Support experience for IBM Security is now live!\n * \n * \n * \n * http://ibm.biz/ILMTforumAnnounce\n * \n * www.ibm.com/mysupport\n * \n * Video 1 - Introducing the IBM Support Community: Search [https://mediacenter.ibm.com/media/t/1_hjcvgybl?acss=danl_4792_email] \n Video 2 - IBM Support Community: Open and manage cases [https://mediacenter.ibm.com/media/t/1_47uqs38j?acss=danl_4792_email] \n \n * \n * BigFix 9.5 Patch 7 is now available\n * \n * \n * \n * https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Endpoint%20Manager/page/IBM%20BigFix%209.5.7%20Release%20Notes\n * \n * \n * \n * BigFix 9.2 Patch 12 is now available\n * \n * \n * \n * https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Endpoint%20Manager/page/IBM%20BigFix%209.2.12%20Release%20Notes\n * \n * \n * \n * BigFix WebUI update for all WebUI applications\n * \n * \n * \n * \n * \n * \n * Availability of BigFix Compliance Analytics version 1.9 Patch 3\n * \n * \n * \n * https://ibm.co/2qePzKY2\n * \n * \n * \n * BigFixInventory Update v9.2.9\n * \n * \n * \n * \n * \n * \n * License Metric Tool Update v9.2.9\n * \n * \n * \n * \n * \n * \n * Security Bulletin: The BigFix Platform has vulnerabilities that have been addressed in patch releases\n * \n * \n * \n * \n * \n * \n * Tool Updated: AIX Download Plug-in v4.0.0.1 published 2017-10-10\n * \n * \n * \n * \n * \n * \n * BigFix Protection End of Life and Migration\n * \n * \n * \n * \n * \n * \n * Unable to get site content\n * \n * \n * \n * \n * \n * \n * Duplicate Applicability Fixlets and Check Fixlets might cause import errors in BigFix Compliance (BFC Analytics, previously SCA)\n * \n * \n * \n\n\nLearn more\n * \n * The IBM Security Learning Academy\n * \n * \n * \n * Video series: Installing BigFix on a Linux Environment [https://www.securitylearningacademy.com/course/view.php?id=1891] \n \n * \n * How to Migrate the IBM BigFix Server (Windows/MS-SQL)\n * \n * \n * \n * \n * \n * \n * Nov 15: Live online training: LMT and BFI Administration and Maintenance\n * \n * \n * \n * \n * \n * \n * Nov.16 Open Mic: Resolving an ILMT Catalog upload failure\n * \n * \n * \n * \n * \n * \n * Dec. 6 Open Mic: The ILMT and BFI Targeting Exception fixlet\n * \n * \n * \n * \n * \n * \n * BigFix and License Metric Tool Open Mic replays\n * \n * \n * \n\n\n\n\n\n[/support/docview.wss?uid=swg27050689&amp;aid=1] Stay connected with support\n * \n * Subscribe to My Notifications\n * \n * \n * \n * \n * \n * \n * Follow these tags in the dW Answers forum: BIGFIX-INVENTORY, ILMT\n * \n * \n * \n\n\n\n[/support/docview.wss?uid=swg27050689&aid=2] [https://www.facebook.com/pages/IBM-Security-Support/221766828033861] [/support/docview.wss?uid=swg27050689&aid=3] [https://twitter.com/AskIBMSecurity] [/support/docview.wss?uid=swg27050689&aid=4] [https://www.youtube.com/user/IBMSecuritySupport] \n\n\n\nTo be on the mailing list that gets newsletters, as well as invitations to Security Support's Open Mic webcasts, send an e-mail to [email protected] [[email protected]?subject=snl%20subscribe%20Endpoint%20And%20Mobility%20Management] with the exact subject line: \nsnl subscribe ILMT2017\n\n\n\n\n\nORIGINAL PUBLICATION DATE\n 2017/10/31 \n\n\n\nCross reference information Segment Product Component Platform Version Edition Security Tivoli Asset Discovery for Distributed Security IBM Endpoint Manager for Software Use Analysis Security IBM BigFix Inventory PRODUCT ALIAS/SYNONYM\n IBM BigFix Inventory\nIBM License Metric Tool\nLMT\nILMT\nSUA\nTAD4D\nTAD4zOS" ]

[ [ "3a", " NEWS ABSTRACT" ], [ "3b", " IBM Security Support announced in October, 2017, that changes to your online IBM License Metric Tool (ILMT) Support experience were coming." ], [ "3c", "See below for the text of the mailing to that was sent to Support customers. CONTENT" ], [ "3d", "Dear IBM License Metric Tool Customer," ], [ "3e", "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." ], [ "3f", "Most IBM Security products, including IBM License Metric Tool, will go live with this new technology at the end of October, 2017." ], [ "3g", "The move to this new online Support experience should be seamless for you." ], [ "3h", " * As announced earlier this year, IBM dW Answers [https://developer.ibm.com/answers/index.html] should still be your first avenue to Support." ], [ "3i", " * The e-mail and phone support channels offered to you today will remain unchanged." ], [ "3j", " * Your bookmarks and existing access methods will automatically connect to the new online Support experience once you’ve selected your IBM Security product or you can use a new URL to reach the new online Support experience directly: https://www.ibm.com/mysupport [https://www.ibm.com/mysupport]." ], [ "3k", " * Any existing PMRs will be automatically converted to “Cases” in the new experience." ], [ "3l", "Simply choose “cases” from the Security product support landing page to see status or make updates." ], [ "3m", "If you are experiencing a problem with the portal (such as a login issue, etc. ), we are here to help." ], [ "3n", "You can submit your issue via our Support page [https://www.ibm.com/mysupport/s/] by clicking “Email IBM Support”, or by emailing [email protected]." ], [ "3o", "Should you have any questions, please send email to [email protected] [[email protected]?subject=Changes%20to%20your%20IBM%20Support%20experience]." ], [ "3p", "[/support/docview.wss?uid=swg22009938&amp;aid=1] IBM Security Support Team PRODUCT ALIAS/SYNONYM LMT" ] ]

[ "3b", "3d", "3f", "3g", "3h", "3i", "3j", "3k", "3l", "3m", "3n" ]

[ " TECHNOTE (FAQ)\n\nQUESTION\n Error #2072 'There was an unanticipated problem with the license for this product.' When running IBM SPSS Statistics or Modeler. \n\nCAUSE\nWhen starting IBM SPSS Statistics or Modeler, a license check is performed by the system. That check is failing. There are several possible causes:\n· The license is valid, but for a different product or version.\n· The license is valid, but for a different machine.\n· The license is valid, but does not have the proper settings for your installation.\n· The license if for a desktop install, but was used on a License Manager or visa versa.\n\nThe specific symptom number will help determine which possible cause will resolve your issue.\n\n\n\n\n\n\nSpecific Symptom #4 locally licensed Specific Symptom #4 on a License Manager Specific Symptom #4 Mac with Thunderbolt Technology Specific Symptom #4 Statistics 20 broken after Upgrade to Mountain Lion Specific Symptom #6 Specific Symptom #15 Specific Symptom #25 Specific Symptom #62 on a Redundant License Manager Specific Symptom #133 Specific Symptom #188 How to contact Support \n\nANSWER\n Specific Symptom #4 locally licensed \n\nYour license can be generated with the incorrect settings. Determining whether an incorrectly generated license is the issue, use the #SuuportHow to contact Support Support Request information to contact IBM SPSS Technical Support, who review the license and make corrections if necessary. You must apply the license after the corrections are made in order for them to take effect. \n\nSpecific Symptom #4 on a License Manager \n\nA license check is performed from the client machine (users computer) to the server hosting the license manager when an IBM SPSS Statistics or Modeler installation is licensed by a license Manager, If the licenses for IBM products are not valid, your license check fails. The most likely cause of the problem is the hardware on the server that is hosting the license manager changed. If you encounter this scenario, contact your company's IT department and ask them to check the code. The IT Team can contact IBM to determine what steps are required to correct the license issue. \n\nBack to top\nSpecific Symptom #4 - Mac with Thunderbolt Technology \n\nTo correct the error (2072/4) you need to change the Statistics application's tethering locking code from using a NIC Card tether (10) to using a hard disk drive tether (4), which is less likely to change. \n\nYou need to know the path of where IBM SPSS Statistics is installed. Depending on the version of Statistics you installed the paths vary. NOTE: Steps 1 through 6 can vary should the softwares default path was not used. Modify accordingly.\n\nHere are some of versions of Statistics and their default paths.\n\n[Defaults paths]\nStatistics 21.0: /Applications/IBM/SPSS/Statistics/21/SPSSStatistics.app/Contents/bin \nStatistics 22.0: /Applications/IBM/SPSS/Statistics/22/SPSSStatistics.app/Contents/bin \nStatistics 23.0: /Applications/IBM/SPSS/Statistics/23/SPSSStatistics.app/Contents/bin \n\n============================================ \n1) Open up FINDER\n2) Open up the APPLICATIONS folder\n3) Open up the IBM folder\n4) Open up the SPSS folder\n5) Open up the Statistics folder\n6) Open up the version of Statistics xx.x (21, 22, 23, xx, depending on the installed version of Statistics)\n7) Locate the \"SPSSStatistics.app\" (application bundle) right click and choose \"Show Package Contents\".\n8) Open up the \"Contents\" folder\n9) Open up the \"bin\" folder\n10) Locate and Control Click echoid.dat and choose Open With, and then choose \nTextEdit.app \n11) Change the 0x010 to 0x004 \n12) Save the echoid.dat file \n13) Delete the current lservrc file in this directory (if one exists, if not continue)\n14) Run the License Authorization Wizard \n15) Re-launch Statistics. The software should now launch without error.\n\n\nBack to top\nSpecific Symptom #4 - Statistics 20 broken after Upgrade to Mountain Lion \n\nThe error is due to a lock code change after the Operating System upgrade. NOTE: IBM SPSS Statistics 20.0 is not formally supported on MAC OSX 10.8 (Mountain Lion). We suggest upgrading to version 21.0, which was fully tested and is supported. Any issues that you might encounter using version 20 on Mountain Lion will be addressed in future releases or FixPacks for 21. That said, we don't anticipate any significant problems with using version 20 on Mountain Lion, and are providing this installation information as a courtesy. To resolve the licensing problem on version 20, rerun the license Authorization Wizard (LAW) and enter the Authorization Code to activate the IBM SPSS Statistics product. IBM cannot guarantee the performance of any versions earlier than 20 on Mountain Lion and can suggest that you install those versions only on formally supported operating systems. \n\nSpecific Symptom #6 \n\nThis error indicates license code that is generated by the IBM SPSS license Authorization Wizard failed to use the complete lock code when it was created. To correct the problem, run the IBM SPSS license Authorization Wizard again. You can also use the Support Request information to check or correct your code. \n\nSpecific Symptom #15 \n\nThe Specific Symptom #15 error message is caused by the license Manager administrator, creating a reserved license, which excludes your workstation from using the license manager. Check with the administrator as the configuration can be intentional. The license manager reservation file that is created can be edited to include the affected machines, if necessary. Review the topic \"Setting Group Reservations\" in the Sentinel RMS license Manager help for more information. \n\nBack to top\nSpecific Symptom #25 \n\nThere are two common causes for Error 2072 Specific Symptom #25:\n\n(1) If the desktop product exhibiting symptom 25 uses a License Manager for licensing, the likely cause is an incompatibility between the version of the licensing technology of the License Manager and the desktop product (client). For details see TechNote 2015199 [http://www.ibm.com/support/docview.wss?uid=swg22015199]. \n\n(2) A user's account has three consecutive exclamation points in its name. You can correct the problem by renaming the account. To do so, follow these steps:\n\n1. If you aren't already, please login with Administrator privileges to the machine\n2. Right click \"My Computer' and select \"Manage\" from the context menu \n3. On the left side, expand System Tools->Local Users and Groups->Users\n4. On the right side, locate your account, right-click the account name and choose \"Rename\"\n5. Rename the account and press Enter \n\nSpecific Symptom #62 on a Redundant License Manager \n\nThe error is caused by incorrect codes, most likely the lock codes for the redundant license Manager host computer does not match the lock code that was encrypted into the license string. Open a Support Request to IBM. To resolve the problem, Support requires that you check the lock codes for the three workstations in the redundancy. Support will then create new codes. \n\nBack to top\nSpecific Symptom #133 \n\nSpecific Symptom #133 is caused by an internet security program (for example, 'personal firewall', 'anti-spyware') preventing SPSS Statistic from recognizing that it is licensed. To restore SPSS Statistics functions, the internet security program on the computer with this error must allow the SPSS Statistics program files 'spss.com' and 'spss.exe' to run without interference. This process is sometimes referred to as 'whitelisting'. See your internet security programs documentation -- or contact the vendor -- for information on how to perform this configuration task \n\nSpecific Symptom #188 \n\nMost likely there's a problem with your computer's system date. Check it, correct it if necessary, and then relaunch SPSS Statistics. It might be necessary to rerun the license authorization wizard to regenerate your license with the correct system date and time. \n\nHow to contact Support \n\nThere are multiple ways to contact support. Your support contact depends on the Support Contract you chose at time of purchase.\n\n\n· Customers with current support contracts can open a Support Request on Support Portal [https://www-947.ibm.com/support/entry/myportal/support]. \n\n· Everyone can use the Predictive Analytics Community Licensing Forums [https://developer.ibm.com/answers/topics/spsslicensing.html] to do the same. \n\n· Students can use the Predictive Analytics Community Student Forums [https://developer.ibm.com/answers/topics/spssstudent.html] [https://developer.ibm.com/answers/topics/spssstudent.html]. \n\nBack to top", " TECHNOTE (FAQ)\n\nQUESTION\n You work with IBM SPSS Client application which requires to be licensed. You would like to set up a redundant license environment at your site.\nYou open the Network License Administrator Guide.pdf for release 21 or 22 and go to chapter \"Administering the Network License -> Setting up Redundant License Servers\"\nand see the following sentence:\n\n'You will need a special authorization code to enable the redundancy feature. The authorization\ncode shipped with the software will not enable redundancy.'\n\nHowever, you think this is confusing as only a special license code will enable redundant features, not the authorization code. Therefore you would like to have the sentence change to:\n\n'You will need a special LICENSE code to enable the redundancy feature. The authorization\ncode shipped with the software will not enable redundancy as you need a LICENSE code.'\n\nYou think it should also be mentioned on this page that there is a difference between authorization code and license code. \n\nANSWER\nAn Enhanecment Request was submitted to IBM SPSS documentation (Reference ID: ECM00196220)\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]", " TECHNOTE (FAQ)\n\nQUESTION\n I have questions or a problem with acquiring IBM SPSS software and licensing IBM SPSS products? Where can I go for more information? \n\nANSWER\nWhere and how do I download and start using my IBM SPSS Software? [http://www.ibm.com/software/analytics/spss/support/get_spss.html]\nHow can I access my SPSS software downloads through IBM Passport Advantage online? [http://www.ibm.com/software/passportadvantage/PassportAdvantageOnlinevideos.html]\n\nHow do I get assistance with my software download problem? [http://www.ibm.com/support/docview.wss?uid=swg21981178]\n\nHow do I get my activation key (authorization code)? \n\n\n * \n * \n * \n * \n * \n * I do not have access to the License Key Center. [http://www.ibm.com/support/docview.wss?uid=swg21980071] \n \n I do have access to the License Key Center. [http://www.ibm.com/support/docview.wss?uid=swg21980065] \n\n\nI need additional information about using the License Key Center: \n * Self-help tutorials \n\n * Self-help video instruction\n\n\nFrequently Asked General Questions about IBM SPSS product licensing \n * How do I transfer software and license from one machine to another?\n * \n * \n * How do I create an SPSS authorization code as stand-alone versus an add-on module?\n * \n * \n * What is the difference between an authorization code and a license code?\n * \n * \n * What is a 'lock code' and where can I find it?\n * \n * \n * How do I change the Primary and/or the Technical Contact?\n * \n * \n * Is my authorization code good for any operating system?\n\n\nI have a question/issue with applying/using an authorization or license code \n\nHow do I activate my desktop SPSS Statistics product? [http://www.ibm.com/support/docview.wss?uid=swg21991408] \n\nHow do I install an additional IBM SPSS Statistics module or function to an existing Statistics product installation? [http://www.ibm.com/support/docview.wss?uid=swg21985980] \n\nWhat are the steps to add an authorization code to License Manager on Linux, Solaris or AIX operating systems? [http://www.ibm.com/support/docview.wss?uid=swg21702183] \n\nWhat can I do to fix a message with 'authorization failed' and 'you are not allowed to generate any more new licenses'? [http://www.ibm.com/support/docview.wss?uid=swg21480566] \n\nWhat can I do about a message with 'authorization failed' and 'authorization code entered is not for this product/version'? [http://www.ibm.com/support/docview.wss?uid=swg21486143] \n\nWhy am I receiving a message 'You do not have the correct administrator privileges to license this product' when I try to license my SPSS Statistics product? [http://www.ibm.com/support/docview.wss?uid=swg21966637] \n\nWhy am I receiving a message with 'Error Code 201' and ' License generation failed'? [http://www.ibm.com/support/docview.wss?uid=swg21486099] \n\nWhy am I receiving 'Authorization failed the server was unable to establish communication with the data base'? [http://www.ibm.com/support/docview.wss?uid=swg21482869] \n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Modeler Not Applicable Business Analytics SPSS SamplePower Not Applicable Business Analytics SPSS Text Analytics for Surveys Not Applicable Business Analytics SPSS AnswerTree Not Applicable Business Analytics SPSS Visualization Designer Not Applicable", "SPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http://www.hearne.software/Software/SPSS-Grad-Packs-for-Students-by-IBM/FAQ] \n * On the Hub [http://onthehub.com/] \n * StudentDiscounts.com [http://studentdiscounts.com/contact-us.aspx] \n * JourneyEd [https://www.journeyed.com/contact] \n * thinkEDU [https://thinkedu.desk.com/] \n * Studica [http://www.studica.com/technical-support]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version", " TECHNOTE (FAQ)\n\nQUESTION\n I would like to perform a network install with my IBM SPSS Software. \nThe install documents provided on the CD do not provide a set of step by step instructions. How do I perform a network installation? \n\nANSWER\n\nGiven you have a network authorization code please follow the instructions below to assist in Network install of IBM SPSS software.\n\nREM : IBM SPSS Statistics has been used as example in below procedure. \n\n1) Decide on a machine that you wish to be the host server (Sentinel RMS LM) to which other machines will connect for license verification. Generally, you will want this machine to be a high-availability machine 24x7. The software does not require heavy processing.\n\n2) Install Sentinel RMS License manager as a separate program apart from the application (IBM SPSS Statistics, IBM SPSS Modeler,...). \n1. Open and explore the DVD and browse to the directory Windows\\Administration\\Licensing\\NetworkLicenseManager.\n2. Run the Setup executable (setup.exe).\n3. After Sentinel RMS is installed you may add the Authorization/License code \nvia Network License Manager Licensing:\n- Select one of the following :\no License my product now\no Enable for temporary usage\nvia a DOS CMD shell :\nwith the command 'spssactivator' or 'licenseactivator' [authorizationcode or licensecode].\nThis command should be executed in the WinNT subdirectory of the Sentinel RMS LM installation directory.\n\nOnce the Sentinel RMS LM is successfully installed, licensed and running (it is a windows service) you may now install the clients. Please note that it is a requirement to restart the Sentinel License Manager service whenever changes (either addition or removal of licenses) are made. Otherwise, these changes will not be displayed within the Sentinel RMS Administration tool.\nTo install the clients, please follow the steps below:\n1. When prompted for install options choose \"Network\"\n2. Use the IP address or Name of the Host Machine containing the Sentinel LM installation.\n\nYour clients should now have IBM SPSS Statistics/Modeler installed and connected to the License host.\n\n\n\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]\n\n\n \n\nHISTORICAL NUMBER\n 60852" ]

[ [ "2a", " TECHNOTE (FAQ) QUESTION" ], [ "2b", " I have questions or a problem with acquiring IBM SPSS software and licensing IBM SPSS products?" ], [ "2c", "Where can I go for more information? ANSWER" ], [ "2d", "Where and how do I download and start using my IBM SPSS Software? [http://www.ibm.com/software/analytics/spss/support/get_spss.html]" ], [ "2e", "How can I access my SPSS software downloads through IBM Passport Advantage online? [http://www.ibm.com/software/passportadvantage/PassportAdvantageOnlinevideos.html]" ], [ "2f", "How do I get assistance with my software download problem? [http://www.ibm.com/support/docview.wss?uid=swg21981178]" ], [ "2g", "How do I get my activation key (authorization code)? * * * * *" ], [ "2h", " * I do not have access to the License Key Center. [http://www.ibm.com/support/docview.wss?uid=swg21980071]" ], [ "2i", " I do have access to the License Key Center. [http://www.ibm.com/support/docview.wss?uid=swg21980065]" ], [ "2j", "I need additional information about using the License Key Center:" ], [ "2k", " * Self-help tutorials" ], [ "2l", " * Self-help video instruction" ], [ "2m", "Frequently Asked General Questions about IBM SPSS product licensing" ], [ "2n", " * How do I transfer software and license from one machine to another? * *" ], [ "2o", " * How do I create an SPSS authorization code as stand-alone versus an add-on module? * *" ], [ "2p", " * What is the difference between an authorization code and a license code? * *" ], [ "2q", " * What is a 'lock code' and where can I find it? * *" ], [ "2r", " * How do I change the Primary and/or the Technical Contact? * *" ], [ "2s", " * Is my authorization code good for any operating system?" ], [ "2t", "I have a question/issue with applying/using an authorization or license code" ], [ "2u", "How do I activate my desktop SPSS Statistics product? [http://www.ibm.com/support/docview.wss?uid=swg21991408]" ], [ "2v", "How do I install an additional IBM SPSS Statistics module or function to an existing Statistics product installation? [http://www.ibm.com/support/docview.wss?uid=swg21985980]" ], [ "2w", "What are the steps to add an authorization code to License Manager on Linux, Solaris or AIX operating systems? [http://www.ibm.com/support/docview.wss?uid=swg21702183]" ], [ "2x", "What can I do to fix a message with 'authorization failed' and 'you are not allowed to generate any more new licenses'? [http://www.ibm.com/support/docview.wss?uid=swg21480566]" ], [ "2y", "What can I do about a message with 'authorization failed' and 'authorization code entered is not for this product/version'? [http://www.ibm.com/support/docview.wss?uid=swg21486143]" ], [ "2z", "Why am I receiving a message 'You do not have the correct administrator privileges to license this product' when I try to license my SPSS Statistics product? [http://www.ibm.com/support/docview.wss?uid=swg21966637]" ], [ "2aa", "Why am I receiving a message with 'Error Code 201' and ' License generation failed'? [http://www.ibm.com/support/docview.wss?uid=swg21486099]" ], [ "2ab", "Why am I receiving 'Authorization failed the server was unable to establish communication with the data base'? [http://www.ibm.com/support/docview.wss?uid=swg21482869]" ], [ "2ac", "Cross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Modeler Not Applicable Business Analytics SPSS SamplePower Not Applicable Business Analytics SPSS Text Analytics for Surveys Not Applicable Business Analytics SPSS AnswerTree Not Applicable Business Analytics SPSS Visualization Designer Not Applicable" ] ]

[ "2g", "2h", "2i", "2m", "2n", "2t", "2x", "2y" ]

[ "DFSMSdss; DFSMShsm; DFSMS; DUMP; COPY; RESTORE; dataset; vsam; sphere; log; logger; logging; logstream; logstreamid; frlog; 5655H9101 R330 5655-H91 5655H91 FMID HCCV330 5655-P30 5655P30 5655P3000 5655Y24 5655-Y24 5655Y2400 R510 HCCV510 HCCV410 HCCV420 HCCV430 TECHNOTE (FAQ)\n\nQUESTION\n You are using the DFSMSdss utility program ADRDSSU to RESTORE a VSAM sphere to a target dataset defined with FRLOG ALL, UNDO, or REDO. You would like to know: Does an ADRDSSU RESTORE to the CICS VSAM Recovery for z/OS (CICSVR) recoverable dataset result in MVS logger activity to the logstream associated with the target VSAM sphere? \n\nANSWER\nThe DFSMSdss ADRDSSU RESTORE command for a VSAM dataset defined in the catalog with the FRLOG(ALL), FRLOG(UNDO), or FRLOG(REDO), will not result in logging activity by CICSVR.\n\nThe determination to bypass logging occurs in DFSMS VSAM module(s) IDA0192A (VSAM OPEN string) and IDA019R4 (VSAM Keyed/Addressed Access) by checking the VSAM ACB field ACBNOCVR.\n\nCICSVR can invoke IBM restore utilities as part of the recovery, for example DFSMSdss, DFSMShsm, or ABARS. The DFSMSdss VSAM IO module ADRIOWVS is invoked for all VSAM OPEN, CLOSE, and I/O requests, and sets the ACBNOCVR bit when the ACB is opened to inform VSAM not to invoke CICSVR for logging. DFSMShsm and ABARS use DFSMSdss, so the RESTORE will not call CICSVR for logging. \n\nAny other utility that uses VSAM macros to perform the restore, will be subject to VSAM checking to see if it needs to invoke CICSVR batch logging. Following are the only other methods to stop logging, other than altering the catalog entry to remove the FRLOG recoverable attributes for the dataset to be restored: \n\n * Set the ACBNOCVR flag in the VSAM ACB during OPEN ACB processing.\n \n * Allocate the NEWSPHERE DD in your RESTORE JCL, and specify no logging in the AMP DD FRLOG=NONE subparamter. For example: \n \n //DS1 DD DSNAME=RESTDSN,AMP=('FRLOG=NONE')\n \n\n\nIf your RESTORE utility only allows for internal dynamic allocation and if you have access to an OPEN exit routine for your RESTORE utility, you can set the ACBNOCVR bit and VSAM will not call CICSVR for logging. RELATED INFORMATION\n#Restore commands for DFSMSdss [http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.adru000/restorec.htm]\nAggregate Backup and Recovery Support (ABARS) [http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.arcf000/abarsp.htm]\nIDCAMS DEFINE CLUSTER - FRLOG() operand [http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.idat300/defclu.htm]\nMVS JCL AMP subparameter options including FRLOG [http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.ieab600/iea3b6_Subparameter_definition1.htm]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Storage Software DFSMS DFSMSdss Storage Software DFSMS DFSMShsm Storage Software DFSMS CICSVR \nPRODUCT ALIAS/SYNONYM\n CICSVR CICS VR", "z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * The target and source IIDR for VSAM server LPARs were IPLed\n at different times. After this, the following message is seen:\n CECW0025I When replicating subscription PACXVUG1 from source\n PACXVUG1, a record update was not performed. A record with key\n 40C5E2F3F7F4F1F5E3 in file TTES20 , data set\n PGYU.V35A.VR.TTES20\n does not match the before image. The log stream timestamp is\n 2017-09-24-07.38.49.175031.\n So one of our files is out of sync.\n \n \n \n \n \n\nLOCAL FIX\n * N/A\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: InfoSphere Classic Change Data Capture for *\n * z/OS for VSAM *\n * InfoSphere Data Replication for VSAM for *\n * z/OS *\n ****************************************************************\n * PROBLEM DESCRIPTION: The target and source side LPARs were *\n * IPL'ed at different times. After this, *\n * message CECW0025I was seen. One of *\n * the VSAM files is out of sync. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n CICS VR changes were replicated out of order.\n Connex was moved from one LPAR to another and the last block\n of changes was replicated out of order. A file close was\n missed and got the count of open files such that it was\n non-zero. This prevented the non-recoverable commit from being\n generated until later when it was done for other reasons\n (e.g. LEOL or number of blocks read). However, by the time the\n block is sent, it is out of order and some keys are out of\n synch.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Classic code is changed to generate a commit if the job has\n any outstanding updates. This will be done for any file close\n for the job. To avoid sending changes out of order, use any\n file close to flush buffered changes for the job.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI88275\n \n \n * REPORTED COMPONENT NAME\n CLASSIC FED & E\n \n \n * REPORTED COMPONENT ID\n 5697I8200\n \n \n * REPORTED RELEASE\n B3J\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 2017-10-04\n \n \n * CLOSED DATE\n 2017-10-10\n \n \n * LAST MODIFIED DATE\n 2017-11-01\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 UI50972\n \n \n\nMODULES/MACROS\n * CECCLRVR\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n CLASSIC FED & E\n \n \n * FIXED COMPONENT ID\n 5697I8200\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * RB30 PSY UI50972 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI50972]\n UP17/10/11 P F710\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.", "z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * In InfoSphere Data Replication for VSAM 11.3.0, when attempting\n to run a batch performance test using CICSVR and IIDR, the\n target server log is swamped with 1000s of CECW0027I, CECW0029I\n and CECW0030I messages.\n \n \n \n \n \n\nLOCAL FIX\n * NA\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: Data Replication for VSAM *\n ****************************************************************\n * PROBLEM DESCRIPTION: Customer has 8 batch jobs running on *\n * 6 LPARs. If a block is being read *\n * from one LPAR and VSAM LRI finds that *\n * a job from a second LPAR *\n * needs a commit, the log reader sends *\n * a log block header and a manufactured *\n * commit for the second LPAR and sets *\n * a flag saying the log block header *\n * was sent. This causes the block *\n * header from the first LPAR to not be *\n * sent and changes in the block are *\n * incorrectly associated with the *\n * second LPAR. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n When a CICS VR log block is read, a check is made to see to\n see if any tracked jobs need to be committed. The commit\n is generated if 50 blocks have been read since the last\n non-recoverable commit for the stream was done. Also, 2\n seconds must have passed since the last non-recoverable commit\n for the job and the time in the current log block header, and\n that job must also have changes sent to the capture service\n that haven't been committed. If a block is being read\n from one LPAR and VSAM LRI finds that a job from a second\n LPAR needs a commit, the log reader sends a log block header\n and a manufactured commit for the second LPAR and sets\n a flag saying the log block header was sent. This causes the\n block header from the first LPAR to not be sent and changes\n in the block are incorrectly associated with the second LPAR.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Classic code will be changed to reset a flag after the\n generated commit processing to ensure the current log block\n header being read is sent to the capture service. This will\n allow the changes in the block to be associated with the\n correct LPAR.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI76063\n \n \n * REPORTED COMPONENT NAME\n CLASSIC FED & E\n \n \n * REPORTED COMPONENT ID\n 5697I8200\n \n \n * REPORTED RELEASE\n B3J\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 2017-02-06\n \n \n * CLOSED DATE\n 2017-03-08\n \n \n * LAST MODIFIED DATE\n 2017-04-03\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 UI45392\n \n \n\nMODULES/MACROS\n * CECCLRVR\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n CLASSIC FED & E\n \n \n * FIXED COMPONENT ID\n 5697I8200\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * RB30 PSY UI45392 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI45392]\n UP17/03/10 P F703\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.", "cics expedite edir edis vsam datasets cr0040 expderr TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When the EDIS transaction is invoked from a blank CICS screen, we receive the following error:-\n\nContinuous Receive request unsuccessful, message CR0040 was logged.\n\nError messages in the WDI Event Log:\n\nVN1019*08*A Timeout error occurred while DataInterchange was waiting for Expedite/CICS to complete a continuous receive termination request. Mailbox (Requestor Profile) ID = <mailbox>, Network Account = <account>, Network Userid = <userid>. ****\n\nCR0040*08*Error occurred during the invocation of communications support. Communications support return code = 8. Communications support extended return code = 1019. **** \n\nDIAGNOSING THE PROBLEM\nAfter user has ran the Recovering Continuous Receive steps in the WDI 3.3.0 Programmer's Reference Guide on page 244 the user still experienced the same problem. \n\nWe checked the Expedite/CICS settings via LGO1 using the SYSTEM DEFAULT for the particular account and userid for the associated C.R. session and found the following settings were different between the working and non-working Region:\n\nForce user to logon... < Y > Y - yes N - no\nAuto create user...... < N > Y - yes N - no\n\nWe had customer to reverse those two values to the following:\nForce user to logon... < N > Y - yes N - no\nAuto create user...... < Y > Y - yes N - no\nNote: This is the default setting \n\nWe went through the process again and got the same results. While the C.R. was finally stopped as per a check using LGO1, it seems that this occurred right after EDIS timed-out. This implies that there may be a deadlock on an ENQ resource between EDIS and an Expedite/CICS transaction; such as from recovery being defined on the Expedite/CICS VSAM files, hence causing Expedite/CICS to have to wait for EDIS to end/timeout before it can update the file to mark it as stopped.\n\nThe Expedite/CICS Program Directory says:\n\n7.1.5 EXPEDITE/CICS DATA SET CONSIDERATIONS\n\nExpedite/CICS requires that its data sets not be defined as recoverable. Expedite/CICS handles its own recovery between itself and IE by the use of the recovery levels IE offers, and would be severely impacted if the files were defined as recoverable. For example, it is very possible and likely that deadly embraces and deadlocks, and loss of data occur when the Expedite/CICS data sets are defined as recoverable. This is due to the way that file recoverability works with regards with the locking up of records when certain file actions are taken, and when they are released.\n\nUse \"CEDA VIEW FILE(EXP*) GR(*)\" to check all of your VSAM file definitions for Expedite/CICS to ensure they are defined as follows:\n\nRECOVERY PARAMETERS\nRECOVery : None None | Backoutonly | All\nFwdrecovlog : No No | 1-99\nBAckuptype : Static Static | Dynamic\n\nIt was found that the only one of the VSAM files that was marked as Recoverable.\n\n\nRESOLVING THE PROBLEM\nUser changed the EXPDERR dataset to None for RECOVery and that resolved the problem. Also be sure these other Expedite/CICS VSAM files are defined with RECOVery = None: \n\nEXPDTST\nEXPDSRC\nEXPDPTF\nEXPHPHP\nEXPRDAT\nEXPSDAT\nEXPDLKP\nEXPDKEY\n\nAfter changing the recovery parameters accordingly, clear out the previous C.R. via these quick steps: \n- EDIZ\n- EDIW to execute WDI command: PERFORM CLOSE MAILBOX WHERE REQID(<mailbox>)\n- and then use LGO1 (SYSTEM DEFAULT id) to delete the associated C.R. userid.", "RFE ; RFEs ; CICS request for enhancements ; CICS requirements ; delivered ; answered ; implemented ; provided CICSCM 5.2 ; CICS Configuration Manager ; 5697CIC00 5697CIC01 R520 R52E R52K 5697-CIC 5697CIC FMID HCCK520 JCCK52E JCCK52K CICSDA 5.2 ; CICS Deployment Assistant ; 5655Y2900 5655Y2901 R520 R52C R52E R52K 5655-Y29 5655Y29 FMID HGEM520 CICSIA 5.2 ; CICS Interdependency Analyzer ; 5655Y2200 5655Y2201 R520 R52E R52K 5655-Y22 5655Y22 FMID H274520 J27452E J27452K CICSPA 5.2 ; CICS Performance Analyzer ; 5655Y2300 5655Y2301 R520 R52C R52E R52K R52S 5655-Y23 5655Y23 FMID H24D520 J24D52E J24D52K J24D52C J24D52S CICSVR 5.2 ; CICS VSAM Recovery ; 5655Y2400 R520 R52E R52K 5655-Y24 ; 5655Y24 FMID HCCV520 JCCV52E JCCV52K retention52 PRODUCT DOCUMENTATION\n\nABSTRACT\n This document lists the customer requirements or requests for enhancements (RFEs) that have been delivered in version 5.2 of the IBM CICS Tools products. \n\nCONTENT\nFor more information about each customer requirement that was delivered in V5.2 of the CICS Tools, click on the headline text in the following tables. This will display the corresponding entry in the IBM Request For Enhancement (RFE) Community [http://www.ibm.com/developerworks/rfe/]*.\n\n\n\n * CICS Configuration Manager for z/OS V5.2 (CICS CM)\n * CICS Deployment Assistant V5.2 (CICS DA)\n * CICS Interdependency Analyzer for z/OS V5.2 (CICS IA)\n * CICS Performance Analyzer for z/OS V5.2 (CICS PA) \n * CICS VSAM Recovery for z/OS V5.2 (CICS VR) \n\n* requires (free) IBM developerWorks registration [https://www.ibm.com/developerworks/dwwi/jsp/Register.jsp].\n\nFor information about how to use RFE to give feedback and ideas for changes and improvements to CICS Tools, see this blog: How to let the team know what you want in CICS - use RFE! [https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/how_to_let_the_team_know_what_you_want_in_cics_use_rfe?maxresults=15&lang=en]\n\n\n\n\n\n\n\n\n\n\nIBM CICS Configuration Manager for z/OS V5.2 (CICS CM) RFE ID Headline 38122 CICS CM - Provide string compare function on Standards Enforcement exit [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=38122] 40335 CICS CM - Migrate of WLM specifications between two CICSPlex SM data repositories [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=40335] \nBack to top\n\n\n\n\n\n\n\nIBM CICS Deployment Assistant for z/OS V5.2 (CICS DA) RFE ID Headline 15353 CICS Deployment Assistant: To provide cloning function for non-CICSPLEX environment [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=15353] \nBack to top\n\n\n\n\n\n\n\nIBM CICS Interdependency Analyzer for z/OS V5.2 (CICS IA) RFE ID Headline 72144 \"CICS IA Command Flow Options\". The ability to run generic searches to tasks without a UserID or TermID, such as an asynchronous task. [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=72144] 76146 Command Flow Run limited to one user ID in V5.1 (no wildcard allowed any more) [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=76146] 76282 Add CODESET and TERRITORY to CICS IA CIUCNFG1 customization clist for CIUUDBC CREATE DATABASE on UDB [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=76282] 82357 Full tab names should appear when hovering over a tab in the left middle window [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=82357] \nBack to top\n\n\n\n\n\n\n\nIBM CICS Performance Analyzer for z/OS V5.2 (CICS PA) RFE ID Headline 15431 CICS PA Batch reporting of CICS TS and CICS TG statistics [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=15431] 15603 CICS PA LISTX report for TRANFLAG abnormal termination bit [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=15603] 31395 CICS PA Find command when viewing CICS TS and CICS TG statistics data using the ISPF dialogues [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=31395] 36016 CICS PA plug-in - Allow date modification when plugging data into MS Excel [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=36016] \nBack to top\n\n\n\n\n\n\n\nIBM CICS VSAM Recovery for z/OS V5.2 (CICS VR) RFE ID Headline 15328 Inability to delete records from the RCDS without recalling migrated LOGS [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=15328] 15329 CICS VR Recovered Data set Statistics Report needs to report on backout record counts and actions [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=15329] 15330 Reset BWO bit by BATCH utility [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=15330] 20952 CICS VR needs to be re-architected to allow only 1 unique module for DWW1SCSR and DWW1VS00 [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=20952] 32974 CICS VR support of old CDS until run conversion program [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=32974] 32975 Implement and backout CICS VR without an IPL [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=32975] 34181 Currently CICS VR supports only 1 DSCB Format. Need extended volume format of DSCB8 DCSB9form [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=34181] 34183 CICS VR generated JCL customization [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=34183] 39781 Allow user specification of CICS VR trans IDs [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=39781] 42974 CICS VR 5.1 needs to coexist with prior versions [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=42974] \nBack to top\n\nRELATED INFORMATION\n Announcement Letters for CICS Products [http://www.ibm.com/support/docview.wss?uid=swg21227090]\nCustomer requirements answered in CICS TS 5.2 [http://www.ibm.com/support/docview.wss?uid=swg27041548]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Host Transaction Processing CICS Configuration Manager for z/OS Availability z/OS 5.2 Host Transaction Processing CICS Deployment Assistant for z/OS Availability z/OS 5.2 Host Transaction Processing CICS Interdependency Analyzer for z/OS Availability z/OS 5.2 Host Transaction Processing CICS Performance Analyzer for z/OS Availability z/OS 5.2 Host Transaction Processing CICS VSAM Recovery for z/OS Availability z/OS 5.2 PRODUCT ALIAS/SYNONYM\n CICSCM CICS CM CICSDA CICS DA CICSIA CICS IA CICSPA CICS PA CICSVR CICS VR" ]

[ [ "0a", "DFSMSdss; DFSMShsm; DFSMS; DUMP; COPY; RESTORE; dataset; vsam; sphere; log; logger; logging; logstream; logstreamid; frlog; 5655H9101 R330 5655-H91 5655H91 FMID HCCV330 5655-P30 5655P30 5655P3000 5655Y24 5655-Y24 5655Y2400 R510 HCCV510 HCCV410 HCCV420 HCCV430 TECHNOTE (FAQ) QUESTION" ], [ "0b", " You are using the DFSMSdss utility program ADRDSSU to RESTORE a VSAM sphere to a target dataset defined with FRLOG ALL, UNDO, or REDO." ], [ "0c", "You would like to know: Does an ADRDSSU RESTORE to the CICS VSAM Recovery for z/OS (CICSVR) recoverable dataset result in MVS logger activity to the logstream associated with the target VSAM sphere? ANSWER" ], [ "0d", "The DFSMSdss ADRDSSU RESTORE command for a VSAM dataset defined in the catalog with the FRLOG(ALL), FRLOG(UNDO), or FRLOG(REDO), will not result in logging activity by CICSVR." ], [ "0e", "The determination to bypass logging occurs in DFSMS VSAM module(s) IDA0192A (VSAM OPEN string) and IDA019R4 (VSAM Keyed/Addressed Access) by checking the VSAM ACB field ACBNOCVR." ], [ "0f", "CICSVR can invoke IBM restore utilities as part of the recovery, for example DFSMSdss, DFSMShsm, or ABARS." ], [ "0g", "The DFSMSdss VSAM IO module ADRIOWVS is invoked for all VSAM OPEN, CLOSE, and I/O requests, and sets the ACBNOCVR bit when the ACB is opened to inform VSAM not to invoke CICSVR for logging." ], [ "0h", "DFSMShsm and ABARS use DFSMSdss, so the RESTORE will not call CICSVR for logging." ], [ "0i", "Any other utility that uses VSAM macros to perform the restore, will be subject to VSAM checking to see if it needs to invoke CICSVR batch logging." ], [ "0j", "Following are the only other methods to stop logging, other than altering the catalog entry to remove the FRLOG recoverable attributes for the dataset to be restored:" ], [ "0k", " * Set the ACBNOCVR flag in the VSAM ACB during OPEN ACB processing." ], [ "0l", " * Allocate the NEWSPHERE DD in your RESTORE JCL, and specify no logging in the AMP DD FRLOG=NONE subparamter. For example:" ], [ "0m", " //DS1 DD DSNAME=RESTDSN,AMP=('FRLOG=NONE')" ], [ "0n", "If your RESTORE utility only allows for internal dynamic allocation and if you have access to an OPEN exit routine for your RESTORE utility, you can set the ACBNOCVR bit and VSAM will not call CICSVR for logging. RELATED INFORMATION" ], [ "0o", "#Restore commands for DFSMSdss [http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.adru000/restorec.htm]" ], [ "0p", "Aggregate Backup and Recovery Support (ABARS) [http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.arcf000/abarsp.htm]" ], [ "0q", "IDCAMS DEFINE CLUSTER - FRLOG() operand [http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.idat300/defclu.htm]" ], [ "0r", "MVS JCL AMP subparameter options including FRLOG [http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.ieab600/iea3b6_Subparameter_definition1.htm]" ], [ "0s", "Cross reference information Segment Product Component Platform Version Edition Storage Software DFSMS DFSMSdss Storage Software DFSMS DFSMShsm Storage Software DFSMS CICSVR PRODUCT ALIAS/SYNONYM" ], [ "0t", " CICSVR CICS VR" ] ]

[ "0b", "0d", "0e", "0f", "0g", "0h", "0i", "0j", "0k", "0l", "0m", "0n" ]

[ " FIXES ARE AVAILABLE\nTivoli Netcool/OMNIbus 7.2.0 InterimFix 4, 7.2.0-TIV-NCOMNIbus-IF0004 [http://www-01.ibm.com/support/docview.wss?uid=swg24024892]\nTivoli Netcool/OMNIbus 7.2.1 Fix Pack 7, 7.2.1-TIV-NCOMNIbus-FP0007 [http://www-01.ibm.com/support/docview.wss?uid=swg24025507]\nTivoli Netcool/OMNIbus 7.2.1 Fix Pack 15, 7.2.1-TIV-NCOMNIbus-FP0015 [http://www-01.ibm.com/support/docview.wss?uid=swg24036693]\nTivoli Netcool/OMNIbus 7.2.1 Fix Pack 13, 7.2.1-TIV-NCOMNIbus-FP0013 [http://www-01.ibm.com/support/docview.wss?uid=swg24031554]\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 * Environment: Linux\n \n OMNIbus version: 7.2.1 FP3\n Probe version: syslog probe 5.0.4066\n \n Current behaviour/symptoms/Problem description:\n \n store and forward file not getting deleted if probe goes to\n store and forward mode, then straight be shuted down, even\n though all the events have been forwarded to ObjectServer. This\n results in duplicated events forwarded to ObjectServer.\n \n Steps to re-create:\n \n 1. start ObjectServer \"NCOMS\"\n 2. start syslog probe by CleanStart : 1 and ReplayFile :0 to\n make sure probe ignores the recovery file and starts reading\n events from the log file created after the probe started.\n 3. shutdown ObjectServer\n 4. generate syslog message with logger :\n # logger -p debug test_alarm_1\n test_alarm_1 is stored in\n $NCHOME/omnibus/var/syslog.store.NCOMS file\n 5. shutdown syslog probe (note: this step is crucial, the issue\n only happens when probe is shutdown after probe goes to store\n and forward mode)\n 6. start objectserver\n 7. start syslog probe. test_alarm_1 is forwarded to\n ObjectServer with Tally=1.However syslog.store.NCOMS file is not\n deleted.\n 8. restart syslog probe\n 9. test_alarm_1 is forwarded to ObjectServer again. Now\n test_alarm_1 become Tally=2. However syslog.store.NCOMS file is\n not deleted.\n \n Expected behaviour:\n \n store and forward file is deleted after all the events have been\n forwarded to ObjectServer no matter probe is shutdown or not.\n \n \n \n \n \n\nLOCAL FIX\n * Manually delete store and forward file after all events have\n been forwarded to ObjectServer\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n Users of probes where the store-and-forward file is used.\n ****************************************************************\n PROBLEM DESCRIPTION:\n The store-and-forward file of a probe was not being deleted if\n the file contents were forwarded by the probe after the probe\n was restarted. The failure to delete the file caused duplicate\n events to be sent each time the probe was restarted.\n ****************************************************************\n RECOMMENDATION:\n Apply one of the listed maintenance packages as appropriate for\n the version of OMNIbus you have installed.\n ****************************************************************\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * This problem has been fixed, and the store-and-forward file is\n now deleted as expected.\n \n The fix for this APAR is contained in the following maintenance\n packages:\n | fix pack | 7.2.0-TIV-NCOMNIbus-FP0007\n | fix pack | 7.2.1-TIV-NCOMNIbus-FP0005\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IZ52966\n \n \n * REPORTED COMPONENT NAME\n NETCOOL/OMNIBUS\n \n \n * REPORTED COMPONENT ID\n 5724O4800\n \n \n * REPORTED RELEASE\n 720\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 2009-06-10\n \n \n * CLOSED DATE\n 2009-07-29\n \n \n * LAST MODIFIED DATE\n 2009-07-29\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\nMODULES/MACROS\n * LIBOPL\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n NETCOOL/OMNIBUS\n \n \n * FIXED COMPONENT ID\n 5724O4800\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R720 PSN\n UP", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\n DIRECT LINKS TO FIXES\n7.1.0-TIV-NCI-SOLARIS-FP0013 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-SOLARIS-FP0013&source=SAR]\n7.1.0-TIV-NCI-WINDOWS-FP0013 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-WINDOWS-FP0013&source=SAR]\n7.1.0-TIV-NCI-ZLINUX-FP0013 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-ZLINUX-FP0013&source=SAR]\n7.1.0-TIV-NCI-LINUX-FP0013 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-LINUX-FP0013&source=SAR]\n7.1.0-TIV-NCI-AIX-FP0013 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-AIX-FP0013&source=SAR]\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * A DASH widget which receives a JSON string containing an\n escaped quotation mark and is instructed to forward the string\n to an Impact policy will automatically send the string with the\n escape character. Impact is handling this incorrectly by\n stripping out the escape character. The Impact policy is then\n unable to successfully parse the JSON string and returns no\n data to DASH.\n \n \n \n \n \n\nLOCAL FIX\n * Only pre-existing workarounds are not very satisfactory: avoid\n the use of quotes inside strings in OMNIbus events (this limits\n OMNIbus functionality, which otherwise supports this), or, have\n Impact obtain the object server data directly from OMNIbus\n rather than via DASH (which removes the capability of wiring an\n Event Viewer directly to a DASH widget)\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n * All Impact Users *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * When passing a string value from a Dashboard widget to an *\n * Impact policy dataset, the escape character for quotation *\n * marks may be discarded by the policy. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n When embedding a quotation mark inside of another quoted string,\n the quotation mark must normally be escaped e.g. \"One \\\"Two\\\"\n Three\". However, the escape character is lost by the policy when\n it parses the incoming string parameters. This issue can\n normally be worked around by double escaping the quotation mark.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * In cases where double escaping is unsuitable, you can configure\n the policy parser to automatically escape and preserve embedded\n quotation marks. This can be done by setting the new property,\n impact.policy.escapestrings=true in the\n <servername>_server.props file.\n \n The fix for this APAR is contained in the following maintenance\n packages:\n |Fix Pack | 7.1.0-TIV-NCI-FP0013\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IV99283\n \n \n * REPORTED COMPONENT NAME\n NETCOOL/IMPACT\n \n \n * REPORTED COMPONENT ID\n 5724O59IS\n \n \n * REPORTED RELEASE\n 710\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 2017-08-24\n \n \n * CLOSED DATE\n 2018-01-26\n \n \n * LAST MODIFIED DATE\n 2018-01-26\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\nMODULES/MACROS\n * UNKNOWN\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n NETCOOL/IMPACT\n \n \n * FIXED COMPONENT ID\n 5724O59IS\n \n \n\nAPPLICABLE COMPONENT LEVELS", " SUBSCRIBE\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 * Customer install IF-00001 for Impact 4.0.2 and he was not able\n to connect to object servers and on the gui display only 4\n services show up. The problem is that selfmonitoring has this\n two properties set to true:\n \n impact.selfmonitoring.queuestatus.enable=true\n impact.selfmonitoring.autostartup=true\n \n \n \n \n \n\nLOCAL FIX\n * L3 has provided the following work around:\n \n 1) If you have the patch install and currently experience the\n issue. Do the following:\n - Turn OFF impact server by doing $NCHOME/bin/wasce stop\n - cd $NCHOME/impact/etc/vi\n <Your_servername>_selfmonitoring.props\n - set the following option to false:\n \n impact.selfmonitoring.queuestatus.enable=false\n impact.selfmonitoring.autostartup=false\n \n - Turn ON impact server by doing $NCOME/bin/wasce start\n \n 2) If you don't have the patch install, then do the following\n before install this patch:\n -- Turn OFF impact server by doing $NCHOME/bin/wasce stop\n - cd $NCHOME/impact/etc/vi\n <Your_servername>_selfmonitoring.props\n - set the following option to false:\n \n \n impact.selfmonitoring.autostartup=false\n \n - Turn ON impact server make sure everything is OK\n - Then apply the patch\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: all Netcool/Impact 4.0.2 users *\n ****************************************************************\n * PROBLEM DESCRIPTION: Customer install IF-00001 for Impact *\n * 4.0.2 and he was not able to connect *\n * to object servers and on the gui *\n * display only 4 services show up. *\n ****************************************************************\n * RECOMMENDATION: *\n * *\n ****************************************************************\n Steps to replicate: 1) Start Impact 2) Configure Impact\n SelfMonitoring Service to: a) Monitor Queue b) To AutoStartup\n when server starts 3) Restart Impact 4) Impact will not fully\n start, when you go the gui you will see only 3 Services in the\n Services list. Note the exception in the log file\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * 4.0.2.-TIV-NCI-IF0002\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IZ22413\n \n \n * REPORTED COMPONENT NAME\n NETCOOL/IMPACT\n \n \n * REPORTED COMPONENT ID\n 5724O59IS\n \n \n * REPORTED RELEASE\n 400\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 2008-05-15\n \n \n * CLOSED DATE\n 2008-07-14\n \n \n * LAST MODIFIED DATE\n 2008-07-14\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\nMODULES/MACROS\n * NETCOOL\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n NETCOOL/IMPACT\n \n \n * FIXED COMPONENT ID\n 5724O59IS\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R400 PSY\n UP", "netcool; 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]", "ObjectServer; Object Server; Serial; ServerSerial; bi-directional; uni-directional; odbc gateway; reporter gateway; oracle gateway; audit gateway; gateway; nco_g_oracle; nco_g_odbc; nco_g_jdbc TECHNOTE (FAQ)\n\nQUESTION\n ObjectServer Serial maximum value for 32-bit Object Servers \n\nCAUSE\n32-bit limitations\n\nANSWER\nThe Serial field is defined using the INCR data type. \n\nFor Netcool/OMNIbus v7.3;\nINCR is a 32-bit unsigned auto-incrementing INTEGER that can only be updated by the system\nINTEGER: is a 32-bit signed integer\n\nThe range of integer values that can be stored in 32 bits are 0 through to 4294967295 or -2,147,483,648 through 2147483647 using two's complement encoding. \n\nTherefore:-\n1 day = 60*60*24 = 86,400 seconds\nThe maximum number of days is therefore, given one event a second;\n4294967295 / 86,400 seconds = 49,710 days => 49,710 / 365 = 136 years\n\nHowever INCR has a maximum value of 2147483647, which implies the following for a system with an event rate of one event a second;\n2147483647 / 86,400 seconds = 24,855 days\n24,855 / 365 = 68 years\n\nThe conclusion is that for the ObjectServer Serial to wrap in a year the event rate needs to be 68 events a second.\n\nThe impact of the ObjectServer Serial wrapping does not affect the ObjectServer itself, provided events are cleared within the period before the ObjectServer Serial wraps. In large multi-tiered systems, the risk of this occurring increases, since the event rate increases, the more events are handled at the Aggregation layer.\n\nThe other impact is on gates and historical databases, which use the Serial, or more precisely the ServerSerial to store data. Therefore it is important to understand the transient real-time nature of the ObjectServer data, and to archive and manage the historical and ObjectServer data accordingly.\n\nA 64-bit Object Server will last 4 billion times longer than a 32-bit Object Server, before Serial wraps." ]

[ [ "3a", "netcool; 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) PROBLEM(ABSTRACT)" ], [ "3b", " All SelfMonitoring Service problem (Service stopped) events are cleared by GenericClear if any single resolution (Service started) event is created SYMPTOM" ], [ "3c", "A Service is stopped and a SelfMonitoring (problem) event is sent to the ObjectServer." ], [ "3d", "Another Service is stopped and that too creates a SelfMonitoring (problem) event in the ObjectServer." ], [ "3e", "The 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. CAUSE" ], [ "3f", "SelfMonitoring 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." ], [ "3g", "DIAGNOSING THE PROBLEM" ], [ "3h", "SelfMonitoring Service events for known stopped Services are vanishing when they shouldn't." ], [ "3i", "RESOLVING THE PROBLEM" ], [ "3j", "The easy solution at this time is to upgrade to Fix Pack 1 or higher." ], [ "3k", "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." ], [ "3l", "This problem is recorded by APAR IV13297 \"ALERTKEY VALUE FOR SELFMONITORING (SERVICE) EVENTS DOES NOT INCLUDE SERVICE DETAILS, SO GENERICCLEAR CLEARS ALL SUCH EVENTS.\"" ], [ "3m", "[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. RELATED INFORMATION" ], [ "3n", " APAR IV13297 [http://www-01.ibm.com/support/docview.wss?uid=swg1IV13297] 6.1.0-TIV-NCI-FP0001 [http://www-01.ibm.com/support/docview.wss?uid=swg24031658]" ] ]

[ "3b", "3c", "3d", "3e", "3f", "3g", "3i", "3j", "3k", "3l", "3m" ]

[ "adjust; 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.", " TECHNOTE (FAQ)\n\nQUESTION\n Will Leap Second have any impact on Process Engine (PE) \n\nCAUSE\nTechnology authorities have released an upcoming issue with Leap\nSecond.\nWhat is Leap Second?\nDefined: \" To ensure the correct alignment of astronomical and atomic time, \nthe International Earth Rotation & Reference Systems Service has called for an extra second to be added to Coordinated Universal Time\n(UTC) at 23:59:59 on June 30, 2015.\n\nANSWER\nProcess Engine does not build timestamps, PE gets its timestamps from the system OS and/or Java for the current time, which gives us the number of seconds since 1970. \nWe use that internally as an integer (or big int ), so all time calculations are done on that.\nIf Process Engine needs to display the value, java converts the integer time (which is actually UTC, not in the local time zone) to display the value and then puts it in the requested time zone.\n\nLeap seconds will not be an issue for the PE. We have had 25 Leap seconds over the past 10 years or so.", " SUBSCRIBE\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 * Specific Binary: NCOEvent.exe\n Last Modified By:\n Version: 3.6\n Component:\n Product Group: Desktop\n Product: Netcool/OMNIBUS\n Prority: Med\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: Users of the Windows EventList. *\n ****************************************************************\n * PROBLEM DESCRIPTION: 1) click on subevent list to open a *\n * filter.. 2) modify the filter, then *\n * click apply. and then close , it will *\n * close the gui as normal 3)repeat the *\n * test for the second instance - , Then *\n * modify the filter, and click close. - *\n * 4) The save dialog Pops up. Press save *\n * *\n * The save dialog box does not close *\n * *\n ****************************************************************\n * RECOMMENDATION: *\n * *\n ****************************************************************\n 1) click on subevent list to open a filter.. 2) modify the\n filter, then click apply. and then close , it will close the\n gui as normal 3)repeat the test for the second instance - ,\n Then modify the filter, and click close. - 4) The save dialog\n Pops up. Press save\n \n The save dialog box does not close\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The Save dialog box closes after pressing save button.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IY90579\n \n \n * REPORTED COMPONENT NAME\n NETCOOL/OMNIBUS\n \n \n * REPORTED COMPONENT ID\n 5724O4800\n \n \n * REPORTED RELEASE\n 350\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 2006-10-12\n \n \n * CLOSED DATE\n 2006-11-06\n \n \n * LAST MODIFIED DATE\n 2006-11-06\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\nMODULES/MACROS\n * NETCOOL\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n NETCOOL/OMNIBUS\n \n \n * FIXED COMPONENT ID\n 5724O4800\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R701 PSY\n UP", "LEAP SECOND TECHNOTE (FAQ)\n\nQUESTION\n Is LEAP SECONDS / LEAP SECOND have any negative effect on TKLM / SKLM? \n\nANSWER\nThe \"Leap Second\" / \"Leap Seconds\" will not affect TKLM/SKLM. \nNo negative impact if the leap second is not added. \n\nSKLM is not a time keeper. \nTKLM / SKLM takes the 'time' from the host system - System level or NTP Server level. \n\nLEAP SECONDS has been added on June 30. \nAdditional links that refer to LEAP SECONDS which cover IBM \nStorage products environment: \n\" \nIBM SONAS / Storwize V7000 Unified Machines might be affected by LEAP SECONDS \n../support/docview.wss?uid=ssg1S1005265 \n\nLEAP SECONDS Information for SAN Volume Controller and Storwize Family Systems \n../support/docview.wss?uid=ssg1S1005279 \n\nLEAP SECONDS Information for DS8000 \n../support/docview.wss?uid=ssg1S1005244 \n\nLEAP SECONDS and IBM ProtecTIER \n../support/docview.wss?uid=ssg1S1005270 \n\nThere were some security bulletins on the XIV, Flashsystems and IBM N series (Netapp ..kb.netapp.com/support/index?page=content&id=3011978&locale=en_US)", "z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * When formatting a dump using the CICSPlex SM Verbexit\n keyword TRC=A for an abbreviated trace format, the local\n time may be computed incorrectly resulting in the local\n time being off by the time zone adjustment which could\n also affect the date.\n .\n For example...\n .\n Local time formats as: 09:08:17.97470\n and GMT time formats : 05:08:17.97470\n .\n This should be:\n .\n Local time formats as: 01:08:17.97470\n and GMT time formats : 05:08:17.97470\n .\n Additional Symptom(s) Search Keyword(s): KIXREVWJB\n verbx eyu0dvaf adjust_stck\n DVAF_STCK_ADD\n DVAF_STCK_SUB\n DVAF_STCK_FLAG\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All CICSPlex SM V4R1M0 and V4R2M0 Users *\n ****************************************************************\n * PROBLEM DESCRIPTION: When the CPSM IPCS VERBEXIT is used to *\n * format CPSM trace records in a dump, *\n * the local time displayed may be *\n * incorrect. *\n ****************************************************************\n * RECOMMENDATION: After applying the PTF that resolves this *\n * APAR, rerun the CPSM IPCS VERBEXIT, ensuring *\n * that IPCS is accessing the version of the *\n * VERBEXIT updated by the PTF. *\n ****************************************************************\n When method EYU0DVAF (DVAF) is called to format CPSM trace\n records in a dump, it may have to alter the GMT time stamp in\n the trace record to apply the leap second adjustment to produce\n the correct GMT time, and to apply the time zone offset to\n produce the correct local time.\n \n If a leap second adjustment is provided in the record, a\n subroutine is called to modify the provided GMT clock by\n subtracting the leap second adjustment. If a time zone offset\n is provided in the record, the subroutine is called again to add\n the time zone offset to current setting of the GMT clock to\n provide the local time.\n \n Before calling the subroutine, a flag is set indicating whether\n a subtract (leap second adjustment) or add (time zone offset)\n should be performed. Since the flag is not initialized properly\n on entry to DVAF, if there is no leap second adjustment to be\n applied, but there is a time zone offset, residual data in the\n flag may cause the subroutine to subtract the time zone offset\n instead of adding it. This will result in the local time being\n invalid.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * EYU0DVAF has been updated to correctly initialize the clock\n adjustment flag on entry.\n \n \n \n \n \n\nTEMPORARY FIX\n * FIX AVAILABLE BY PTF ONLY\n \n \n \n \n \n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM41654\n \n \n * REPORTED COMPONENT NAME\n CICS TS Z/OS V4\n \n \n * REPORTED COMPONENT ID\n 5655S9700\n \n \n * REPORTED RELEASE\n 60M\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 2011-06-16\n \n \n * CLOSED DATE\n 2011-07-11\n \n \n * LAST MODIFIED DATE\n 2011-08-01\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n PM41866 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM41866]\n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n UK69526 UK69527\n \n \n\nMODULES/MACROS\n * EYU0DVAF\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n CICS TS Z/OS V4\n \n \n * FIXED COMPONENT ID\n 5655S9700\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R60M PSY UK69526 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK69526]\n UP11/07/13 P F107\n \n \n * R70M PSY UK69527 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK69527]\n UP11/07/13 P F107\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." ]

[ [ "0a", "adjust; timezone; tz TECHNOTE (FAQ) QUESTION" ], [ "0b", " What is the impact of the addition of Leap Second on WebGUI? CAUSE" ], [ "0c", "Every 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. ANSWER" ], [ "0d", "The addition of Leap Second has no impact to WebGUI functionality." ], [ "0e", "Therefore, preventive maintenance is not necessary." ] ]

[ "0c", "0d" ]

[ "toolkit; portal; cloud; SOA; eclipse; CRIMA1062E TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to install Rational Desktop Connection Toolkit for Cloud Environments (Cloud Toolkit) with IBM Rational Application Developer for WebSphere Software (RAD) or Rational Software Architect (RSA) results in the error \"CRIMA1062E: Installing IBM Rational Desktop Connection Toolkit for Cloud Environments 2.0 is not allowed\". \n\nSYMPTOM\nInstalling Cloud Toolkit with Rational Application Developer for WebSphere Software, following error message is shown in install log:\n\nNote: When installing Cloud Toolkit with Rational Software Architect, the same error message will be shown as well. \n\nError determining install and download size for {0}.\nCRIMA1062E: Installing IBM® Rational® Desktop Connection Toolkit for Cloud Environments 2.0 is not allowed; it is not compatible with IBM® Rational® Application Developer for WebSphere® Software 9.0.\n\nIn installation context \"com.ibm.sdp.eclipse.ide\":\n\nSoftware being installed: SE.2.com.ibm.rational.cloud.toolkit.main 2.0.0.CTKO20-I20130529_1623\n\nMissing requirement: Cloud 1.0.2.v20130211_2155 (com.ibm.etools.portal.server.cloud.v7 1.0.2.v20130211_2155) requires 'bundle com.ibm.etools.portal.server.tools.common.core [8.0.0,9.0.0)' but it could not be found\n\nCannot satisfy dependency:\n\nFrom: SE.2.com.ibm.etools.portal.server.cloud.feature 1.1.0.v20130527_2141\n\nTo: com.ibm.etools.portal.server.cloud.feature.feature.group [1.1.0.v20130409_1952]\n\nCannot satisfy dependency:\n\nFrom: SE.2.com.ibm.rational.cloud.toolkit.main 2.0.0.CTKO20-I20130529_1623\n\nTo: SE.2.com.ibm.etools.portal.server.cloud.feature [1.1.0,2.0.0)\n\nCannot satisfy dependency:\n\nFrom: Portal Server Cloud Support 1.1.0.v20130409_1952 (com.ibm.etools.portal.server.cloud.feature.feature.group 1.1.0.v20130409_1952)\n\nTo: com.ibm.etools.portal.server.cloud.v7 [1.0.2.v20130211_2155]\n\nCAUSE\nWhen installing Rational Desktop Connection Toolkit for Cloud Environments (Cloud Toolkit) with RAD or RSA, some of the features in RAD or RSA must be selected when the \"Portal Tools Extension for the Cloud\" or \"Deployment Modeling Extension for the Cloud\" feature is selected in the Cloud Toolkit. \n\n\n\nRESOLVING THE PROBLEM\nEnsure following features are selected: \n\nIf installing with Rational Application Developer, ensure one of the following feature is selected: \n\n * Server tools -> WebSphere Application Server 8.5 -> Development tools \n * Server tools -> WebSphere Application Server 8.0 -> Development tools \n * Server tools -> WebSphere Application Server 7.0 -> Development tools \n * Server tools -> WebSphere Portal Server 8.0 -> Development tools \n * Server tools -> WebSphere Portal Server 7.0 -> Development tools\n\nIf installing with Rational Software Architect, ensure one of the following feature is selected: \n\n * Extension for SOA and web applications -> Server tools -> WebSphere Application Server 8.5 - Development tools \n * Extension for SOA and web applications -> Server tools -> WebSphere Application Server 8.0 - Development tools \n * Extension for SOA and web applications -> Server tools -> WebSphere Application Server 7.0 - Development tools \n * Extension for Deployment Planning -> Deployment modeling \n * Extension for Deployment Planning -> Rational Asset Manager integration for deployment architecture\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Software Development Rational Software Architect Not Applicable", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DOCUMENTATION ERROR.\n \n \n \n\nERROR DESCRIPTION\n * The following WP v6.1 IC pages:\n Adding a database user registry on i5/OS\n Migrating the security configuration\n Adding a database user registry on i5/OS\n Adding a database user registry on HP-UX\n Adding a database user registry on AIX\n Adding a database user registry on Solaris\n Adding a database user registry on HP-UX\n Adding a database user registry on Windows\n Adding a database user registry on Linux\n Adding a database user registry on Solaris\n Configuring a property extension database on i5/OS\n Adding a database user registry on Linux\n Adding a database user registry on Windows\n Adding a database user registry on AIX\n Configuring a property extension database on Linux\n Configuring a property extension database on Solaris\n Configuring a property extension database on Windows\n Configuring a property extension database on HP-UX\n Configuring a property extension database on AIX\n \n \n Have this step:\n If the WebSphere Application Server installed PK66195 and you\n installed WebSphere Portal version 6.1.0, perform the following\n steps:\n \n ...\n \n If the WebSphere Application Server did not install PK66195,\n copy the above library files into the appserver/lib directory\n prior to starting the server.\n \n That needs the following corrected as follows:\n If the WebSphere Application Server did not install PK66195,\n copy the above library files into the appserver/lib directory.\n Then stop and restart server1 and WebSphere_Portal servers to\n load the library files.\n \n Because failure to load the library files will cause subsequent\n tasks to complete incorrectly.\n \n \n \n \n \n\nLOCAL FIX\n * n/a\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ERROR DESCRIPTION:\n The following WP v6.1 IC pages:\n Adding a database user registry on i5/OS\n Migrating the security configuration\n Adding a database user registry on i5/OS\n Adding a database user registry on HP-UX\n Adding a database user registry on AIX\n Adding a database user registry on Solaris\n Adding a database user registry on HP-UX\n Adding a database user registry on Windows\n Adding a database user registry on Linux\n Adding a database user registry on Solaris\n Configuring a property extension database on i5/OS\n Adding a database user registry on Linux\n Adding a database user registry on Windows\n Adding a database user registry on AIX\n Configuring a property extension database on Linux\n Configuring a property extension database on Solaris\n Configuring a property extension database on Windows\n Configuring a property extension database on HP-UX\n Configuring a property extension database on AIX\n \n \n Have this step:\n If the WebSphere Application Server installed PK66195 and y\n installed WebSphere Portal version 6.1.0, perform the follo\n steps:\n \n ...\n \n If the WebSphere Application Server did not install PK66195\n copy the above library files into the appserver/lib directo\n prior to starting the server.\n \n That needs the following corrected as follows:\n If the WebSphere Application Server did not install PK66195\n copy the above library files into the appserver/lib directo\n Then stop and restart server1 and WebSphere_Portal servers\n load the library files.\n \n Because failure to load the library files will cause subseq\n tasks to complete incorrectly.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * IC updated as required\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PK74171\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE PORTA\n \n \n * REPORTED COMPONENT ID\n 5724E7600\n \n \n * REPORTED RELEASE\n 610\n \n \n * STATUS\n CLOSED DOC\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 2008-10-21\n \n \n * CLOSED DATE\n 2008-11-12\n \n \n * LAST MODIFIED DATE\n 2008-11-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\nAPPLICABLE COMPONENT LEVELS", "CRIMA1076E; setupCmdLine.sh; setupCmdLine.bat; installProfileTemplates.sh; installProfileTemplates.bat TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nWhen installing WebSphere Portal v8 silently, the installation fails when executing the installProfileTemplates script. \n\nSYMPTOM\nIn the IBM Installation Manager logs, you see the following error:\n\n==========================\nERROR CRIMA1076E 04:27.03 Error executing the /opt/IBM/WebSphere/PortalServer/profileTemplates/installPortalTemplates.sh command: status=99. For more information, see the agent log file: /var/ibm/InstallationManager/logs/native/20121211_0935a.log The installation operation failed due to an error executing the exec command.An issue has occurred with the package that cannot be resolved by Installation Manager. Identify the package that has the issue. Contact IBM Support.\n==========================\n\nIn the native log referenced in the error (in this case, /var/ibm/InstallationManager/logs/native/20121211_0935a.log), we find the root cause:\n\n=====================\nThe appserver directory at /opt/IBM/WebSphere/AppServer exists.\n/opt/IBM/WebSphere/AppServer/bin/setupCmdLine.sh not found\n=====================\n\n\nCAUSE\nIn this case, a previous Portal installation attempt failed after it successfully installed WebSphere Application Server. \n\nThe user then deleted the AppServer directory but did not uninstall it from IBM Installation Manager. On the next Portal installation attempt, IBM Installation Manager skipped the WAS installation since it was still registered within Installation Manager. \n\nRESOLVING THE PROBLEM\nTo resolve the problem, you can attempt to uninstall the WebSphere Application Server from IBM Installation Manager. If the installation fails because the AppServer directory is missing or incomplete, you can reinstall IBM Installation Manager to completely clean its registry.\n\nNOTE: If you have other products installed by the same IBM Installation Manager, do not reinstall IIM without first consulting with IBM support. Reinstalling IBM Installation Manager can break products that have previously been installed.", " 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", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After deploying an OSGi extension, ClassCastException gets thrown \ninconsistently. \n\nSYMPTOM\nClassCastException sometimes occurs after deployment of OSGi extension. \n\n\n[15/08/16 14:39:58:985 EDT] 00000166 NativeLoader I \ncom.ibm.mdm.mds.jni.NativeLoader <clinit> Loading native libraries \n\n[15/08/16 14:39:58:986 EDT] 00000166 NativeLoader I \ncom.ibm.mdm.mds.jni.NativeLoader loadLibrary Trying to load native \nlibrary 'mad'... \n\n[15/08/16 14:39:59:795 EDT] 00000166 NativeLoader I \ncom.ibm.mdm.mds.jni.NativeLoader loadLibrary Trying to load native \nlibrary 'mad'...failed (library is loaded by another defunct \nclassloader), retrying (60s remaining) \n... ... \n\nDWLExceptionU E java.lang.ClassCastException: \nca.gg.ccc.commercial.extensions.entityObject.EObjIdXReference \nincompatible with \nca.gg.ccc.commercial.extensions.entityObject.EObjIdXReference \n... ...\n\n\n\nRESOLVING THE PROBLEM\nRestarting server will resolve the issue. It is part of the deployment. See more details in the following Knowledge center link: \nhttp://www.ibm.com/support/knowledgecenter/en/SSWSR9_11.3.0/com.ibm.mdmhs.wb.tools.models.doc/c_Addition_and_Extension_Deployment_in_OSGi_Framework.html [http://www.ibm.com/support/knowledgecenter/en/SSWSR9_11.3.0/com.ibm.mdmhs.wb.tools.models.doc/c_Addition_and_Extension_Deployment_in_OSGi_Framework.html] \n\nAlso you can restart servers one by one in cluster." ]

[ [ "3a", " A FIX IS AVAILABLE" ], [ "3b", "Fixes integrated in WebSphere Portal 8.5.0.0 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24037786] SUBSCRIBE" ], [ "3c", "You can track all active APARs for this component. APAR STATUS" ], [ "3d", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "3e", " * During Portal Start-Up following error is shown:" ], [ "3f", " --------------------" ], [ "3g", " 0000005e MBeanStarter E com.ibm.wps." ], [ "3h", " scripting.server.MBeanStarter loadExtensions failed to load" ], [ "3i", " extension:" ], [ "3j", " key: ServerExt.applications / value:" ], [ "3k", " com.ibm.wps.scripting.server." ], [ "3l", " ApplicationServerExtensions LOCAL FIX" ], [ "3m", " * 1) open the WAS admin console" ], [ "3n", " 2) navigate to Resources > Resource environment providers > WP" ], [ "3o", " ScriptingService > Custom properties" ], [ "3p", " 3) you should see an entry with the name" ], [ "3q", " \"ServerExt.applications\" and value" ], [ "3r", " \"com.ibm.wps.scripting.server.ApplicationServerExtensions\"" ], [ "3s", " 4) delete this entry, save and restart the server. PROBLEM SUMMARY" ], [ "3t", " * A code fix for this issue is integrated into the WebSphere" ], [ "3u", " Portal & WCM Combined Cumulative Fix 05 (PI31198 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI31198]) for Portal" ], [ "3v", " 8.5.0.0 available from Fix Central:" ], [ "3w", " http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent" ], [ "3x", " =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]" ], [ "3y", " l&platform=All&function=aparId&apars=PI31198 PROBLEM CONCLUSION" ], [ "3z", " * Added a task to remove the outdate resource environment" ], [ "3aa", " provider entry. TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "3ab", " * APAR NUMBER" ], [ "3ac", " PI34677" ], [ "3ad", " * REPORTED COMPONENT NAME" ], [ "3ae", " WEBSPHERE PORTA" ], [ "3af", " * REPORTED COMPONENT ID" ], [ "3ag", " 5724E7600" ], [ "3ah", " * REPORTED RELEASE" ], [ "3ai", " 850" ], [ "3aj", " * STATUS" ], [ "3ak", " CLOSED PER" ], [ "3al", " * PE" ], [ "3am", " NoPE" ], [ "3an", " * HIPER" ], [ "3ao", " NoHIPER" ], [ "3ap", " * SPECIAL ATTENTION" ], [ "3aq", " NoSpecatt" ], [ "3ar", " * SUBMITTED DATE" ], [ "3as", " 2015-02-10" ], [ "3at", " * CLOSED DATE" ], [ "3au", " 2015-03-10" ], [ "3av", " * LAST MODIFIED DATE" ], [ "3aw", " 2015-03-10" ], [ "3ax", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "3ay", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "3az", " * FIXED COMPONENT NAME" ], [ "3ba", " WEBSPHERE PORTA" ], [ "3bb", " * FIXED COMPONENT ID" ], [ "3bc", " 5724E7600" ], [ "3bd", "APPLICABLE COMPONENT LEVELS" ], [ "3be", " * R850 PSY" ], [ "3bf", " UP" ] ]

[ "3e", "3m", "3n", "3o", "3p", "3q", "3r", "3s" ]

[ " SECURITY BULLETIN\n\nSUMMARY\n IBM OpenPages GRC Platform has addressed potential security exposure due to multiple vulnerabilities in Apache Tomcat. \n\nVULNERABILITY DETAILS\n\nCVE-ID: CVE-2018-1323 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1323]\nDescription: Apache Tomcat JK ISAPI Connector could allow a remote attacker to obtain sensitive information, caused by the improper handling of HTTP request paths in jk_isapi_plugin.c. An attacker could exploit this vulnerability using the reverse proxy to expose application resources.\nCVSS Base Score: 7.5\nCVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/140213 [https://exchange.xforce.ibmcloud.com/vulnerabilities/140213] for more information\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\nCVE-ID: CVE-2018-1305 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1305]\nDescription: Apache Tomcat could allow a remote attacker to bypass security restrictions, caused by the failure to properly enforce security constraints that are defined by annotations of Servlets in certain cases. An attacker could exploit this vulnerability to bypass security constraints to access restricted resources.\nCVSS Base Score: 7.5\nCVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/139475 [https://exchange.xforce.ibmcloud.com/vulnerabilities/139475] for more information\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\nCVE-ID: CVE-2018-1304 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1304]\nDescription: Apache Tomcat could allow a remote attacker to bypass security restrictions, caused by the failure to properly enforce security constraint definitions that contain a URL pattern of \"\" (the empty string) that exactly maps to the context root. An attacker could exploit this vulnerability to bypass security constraints to access restricted resources.\nCVSS Base Score: 7.5\nCVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/139476 [https://exchange.xforce.ibmcloud.com/vulnerabilities/139476] for more information\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\nCVE-ID: CVE-2017-15706 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15706]\nDescription: Apache Tomcat could provide weaker than expected security, caused by the incorrect documentation of the CGI search algorithm used by the CGI Servlet to identify which script to execute. The error resulted in the failure of some scripts to execute as expected and other scripts may have been executed unexpectedly.\nCVSS Base Score: 5.3\nCVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/138486 [https://exchange.xforce.ibmcloud.com/vulnerabilities/138486] for more information\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)\n\nCVEID: CVE-2017-12617 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12617]\nDESCRIPTION: Apache Tomcat could allow a remote attacker to execute arbitrary code on the system, caused by an incomplete fix related to an error when running on Windows with HTTP PUTs enabled. By sending a specially crafted request, an attacker could exploit this vulnerability to upload a JSP file and execute arbitrary code on the system.\nCVSS Base Score: 8.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/132484 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132484] 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\nCVEID: CVE-2017-12616 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12616]\nDESCRIPTION: Apache Tomcat could allow a remote attacker to obtain sensitive information, caused by an error when using VirtualDirContext. By sending a specially crafted request, an attacker could exploit this vulnerability to bypass security constraints and view the source code of JSPs for resources.\nCVSS Base Score: 6.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/132276 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132276] 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:L/A:N) \n\nCVEID: CVE-2017-12615 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12615]\nDESCRIPTION: Apache Tomcat could allow a remote attacker to execute arbitrary code on the system, caused by an error when running on Windows with HTTP PUTs enabled. By sending a specially crafted request, an attacker could exploit this vulnerability to upload a JSP file and execute arbitrary code on the system.\nCVSS Base Score: 8.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/132277 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132277] 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\nAFFECTED PRODUCTS AND VERSIONS\nIBM OpenPages GRC Platform version 7.1\n\nREMEDIATION/FIXES\nA fix has been created for each affected version of the named product. Download and install the fix as soon as possible. Fixes and installation instructions are provided at the URLs listed below:\n\n\n\nFix Download URL For OpenPages GRC Platform 7.1.0.4\n- Apply 7.1.0.4 Interim Fix 1 or later http://www.ibm.com/support/docview.wss?uid=swg24044731 [http://www-01.ibm.com/support/docview.wss?uid=swg24044731] \nFor OpenPages GRC Platform v7.0.x customers, IBM recommends upgrading to a fixed, supported version/release/platform of the product. \n\nWORKAROUNDS AND MITIGATIONS\nNone known, apply 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 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 April 2018: 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.", " SECURITY BULLETIN\n\nSUMMARY\n There are vulnerabilities in Apache Tomcat to which the IBM® FlashSystem™ 840 and FlashSystem™ 900 are susceptible. An exploit of this vulnerability (CVE-2017-5647) could make the system susceptible to an attack which could allow an attacker to obtain sensitive information. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-5647 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5647]\nDESCRIPTION: Apache Tomcat could allow a remote attacker to obtain sensitive information, caused by an error in the processing of pipelined requests in send file. An attacker could exploit this vulnerability to obtain sensitive information from the wrong response.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/124400 [https://exchange.xforce.ibmcloud.com/vulnerabilities/124400] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S\n\nAFFECTED PRODUCTS AND VERSIONS\nFlashSystem 840 machine type and models (MTMs) affected include 9840-AE1 and 9843-AE1. \n\nFlashSystem 900 MTMs affected include 9840-AE2 and 9843-AE2.\n\nSupported code versions which are affected\n· VRMFs prior to 1.3.0.9 \n· VRMFs prior to 1.4.7.0\n\nREMEDIATION/FIXES\n\n\nMTMs VRMF APAR Remediation/First Fix FlashSystem 840 MTM: \n9840-AE1 &\n9843-AE1\n\nFlashSystem 900 MTMs:\n9840-AE2 &\n9843-AE2 Code fixes are now available, the minimum VRMF containing the fix depends on the code stream:\n\nFixed Code VRMF \n1.4 stream: 1.4.7.0 \n1.3 stream: 1.3.0.9 N/A FlashSystem 840 fixes [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=Flash%2Bhigh%2Bavailability%2Bsystems&product=ibm/StorageSoftware/IBM+FlashSystem+840&release=All&platform=All&function=all] and FlashSystem 900 fixes [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=Flash%2Bhigh%2Bavailability%2Bsystems&product=ibm/StorageSoftware/IBM+FlashSystem+900&release=All&platform=All&function=all] are available @ IBM’s Fix Central 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\nACKNOWLEDGEMENT\nNone \n\nCHANGE HISTORY\n 22 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. \n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Flash Storage IBM FlashSystem 900 Security Bulletin Platform Independent Version Independent", "CVE-2017-6056; JRS SECURITY BULLETIN\n\nSUMMARY\n Jazz Team Server is shipped as a component of Jazz Reporting Service (JRS). Information about a security vulnerability affecting Jazz Team Server and Jazz-based products has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2017-6056 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-6056]\nDESCRIPTION:Apache Tomcat is vulnerable to a denial of service, caused by a programming error in the servlet and JSP engine. A remote attacker could exploit this vulnerability to cause the server to enter into an infinite loop.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/122312 [https://exchange.xforce.ibmcloud.com/vulnerabilities/122312]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\nPrincipal Product and Version(s) Affected Supporting Product(s) and Version(s) JRS 5.0, 5.0.1, 5.0.2 Jazz Foundation 5.0, 5.0.1, 5.0.2 JRS 6.0, 6.0.1, 6.0.2, 6.0.3 Jazz Foundation 6.0, 6.0.1, 6.0.2, 6.0.3 * Both JRS and Jazz Foundation are part of Rational Collaborative Lifecycle Management. REMEDIATION/FIXES\nConsult the security bulletin Security Bulletin: Security vulnerabilities in Apache Tomcat affect multiple IBM Rational products based on IBM's Jazz technology [http://www-01.ibm.com/support/docview.wss?uid=swg21999760] for vulnerability details and information about fixes.\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 11 July 2017: Initial Publication \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.", " SECURITY BULLETIN\n\nSUMMARY\n Apache Tomcat vulnerability affects IBM Storwize V7000 Unified. \n\nVULNERABILITY DETAILS\nThis bulletin relates to vulnerabilities in the Apache Tomcat component which is used to provide the product’s management GUI. The CLI interface is unaffected.\nCVEID: CVE-2016-6816 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6816]\nDESCRIPTION: Apache Tomcat is vulnerable to HTTP response splitting attacks, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability to inject arbitrary HTTP headers and cause the server to return a split response, once the URL is clicked. This would allow the attacker to perform further attacks, such as Web cache poisoning or cross-site scripting, and possibly obtain sensitive information.\nCVSS Base Score: 6.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/119158 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119158] 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:N) \n\nCVEID: CVE-2016-6817 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6817]\nDESCRIPTION: Apache Tomcat is vulnerable to a denial of service. By sending a specially crafted HTTP/2 header, a remote attacker could exploit this vulnerability to cause the application to enter into an infinite loop.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/119156 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119156] 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\nCVEID: CVE-2016-8735 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8735]\nDESCRIPTION: Apache Tomcat could allow a remote attacker to execute arbitrary code on the system, caused by an error in the JmxRemoteLifecycleListener. By sending specially crafted data to a JMX port, an attacker could exploit this vulnerability to execute arbitrary code on the system with elevated privileges.\nCVSS Base Score: 7.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/119157 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119157] 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:L/A:L)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Storwize V7000 Unified \n\nThe product is affected when running code releases 1.5.0.0 to 1.5.2.5 and 1.6.0.0 to 1.6.2.0\n\nREMEDIATION/FIXES\nA fix for these issues is in version 1.5.2.6 and 1.6.2.1 of IBM Storwize V7000 Unified. Customers running an affected version of IBM Storwize V7000 Unified should upgrade to 1.5.2.6 or 1.6.2.1 or a later version, so that the fix gets applied.\n\nLatest Storwize V7000 Unified Software [http://www-01.ibm.com/support/docview.wss?uid=ssg1S1003918&myns=s028&mynp=OCST5Q4U&mync=E] \n\nPlease contact IBM support for assistance in upgrading your system.\n\nWORKAROUNDS AND MITIGATIONS\nWorkaround(s) : None.\n\nMitigation(s) : Although IBM recommends that you install a level of code with a fix for this vulnerability, you can mitigate, although not eliminate, your risk until you have done so by ensuring that all users who have access to the system are authenticated by another security system such as a firewall.\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 31 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.", "CVE-2017-15706; http; security; Apache SECURITY BULLETIN\n\nSUMMARY\n There is a potential security vulnerability in the Apache Tomcat used by Rational Build Forge. \n\nVULNERABILITY DETAILS\n\nCVEID: CVE-2017-15706 [http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15706]\nDESCRIPTION: Apache Tomcat could provide weaker than expected security, caused by the incorrect documentation of the CGI search algorithm used by the CGI Servlet to identify which script to execute. The error resulted in the failure of some scripts to execute as expected and other scripts may have been executed unexpectedly.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/138486 [https://exchange.xforce.ibmcloud.com/vulnerabilities/138486] 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:L/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Rational Build Forge from 8.0.0.6.\n\nREMEDIATION/FIXES\nYou must download the Fix pack specified in the following table and apply it.\n\n\n * Affected Version\n\n * Fix\n\n * \n\n * \n * Download\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 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\nNone \n\nCHANGE HISTORY\n * 22 MARCH 2018: 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." ]

[ [ "0a", " SECURITY BULLETIN SUMMARY" ], [ "0b", " IBM OpenPages GRC Platform has addressed potential security exposure due to multiple vulnerabilities in Apache Tomcat. VULNERABILITY DETAILS" ], [ "0c", "CVE-ID: CVE-2018-1323 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1323]" ], [ "0d", "Description: Apache Tomcat JK ISAPI Connector could allow a remote attacker to obtain sensitive information, caused by the improper handling of HTTP request paths in jk_isapi_plugin.c." ], [ "0e", "An attacker could exploit this vulnerability using the reverse proxy to expose application resources." ], [ "0f", "CVSS Base Score: 7.5" ], [ "0g", "CVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/140213 [https://exchange.xforce.ibmcloud.com/vulnerabilities/140213] for more information" ], [ "0h", "CVSS Environmental Score*: Undefined" ], [ "0i", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)" ], [ "0j", "CVE-ID: CVE-2018-1305 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1305]" ], [ "0k", "Description: Apache Tomcat could allow a remote attacker to bypass security restrictions, caused by the failure to properly enforce security constraints that are defined by annotations of Servlets in certain cases." ], [ "0l", "An attacker could exploit this vulnerability to bypass security constraints to access restricted resources." ], [ "0m", "CVSS Base Score: 7.5" ], [ "0n", "CVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/139475 [https://exchange.xforce.ibmcloud.com/vulnerabilities/139475] for more information" ], [ "0o", "CVSS Environmental Score*: Undefined" ], [ "0p", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N)" ], [ "0q", "CVE-ID: CVE-2018-1304 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1304]" ], [ "0r", "Description: Apache Tomcat could allow a remote attacker to bypass security restrictions, caused by the failure to properly enforce security constraint definitions that contain a URL pattern of \"\" (the empty string) that exactly maps to the context root." ], [ "0s", "An attacker could exploit this vulnerability to bypass security constraints to access restricted resources." ], [ "0t", "CVSS Base Score: 7.5" ], [ "0u", "CVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/139476 [https://exchange.xforce.ibmcloud.com/vulnerabilities/139476] for more information" ], [ "0v", "CVSS Environmental Score*: Undefined" ], [ "0w", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N)" ], [ "0x", "CVE-ID: CVE-2017-15706 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15706]" ], [ "0y", "Description: Apache Tomcat could provide weaker than expected security, caused by the incorrect documentation of the CGI search algorithm used by the CGI Servlet to identify which script to execute." ], [ "0z", "The error resulted in the failure of some scripts to execute as expected and other scripts may have been executed unexpectedly." ], [ "0aa", "CVSS Base Score: 5.3" ], [ "0ab", "CVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/138486 [https://exchange.xforce.ibmcloud.com/vulnerabilities/138486] for more information" ], [ "0ac", "CVSS Environmental Score*: Undefined" ], [ "0ad", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)" ], [ "0ae", "CVEID: CVE-2017-12617 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12617]" ], [ "0af", "DESCRIPTION: Apache Tomcat could allow a remote attacker to execute arbitrary code on the system, caused by an incomplete fix related to an error when running on Windows with HTTP PUTs enabled." ], [ "0ag", "By sending a specially crafted request, an attacker could exploit this vulnerability to upload a JSP file and execute arbitrary code on the system." ], [ "0ah", "CVSS Base Score: 8.1" ], [ "0ai", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/132484 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132484] for the current score" ], [ "0aj", "CVSS Environmental Score*: Undefined" ], [ "0ak", "CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)" ], [ "0al", "CVEID: CVE-2017-12616 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12616]" ], [ "0am", "DESCRIPTION: Apache Tomcat could allow a remote attacker to obtain sensitive information, caused by an error when using VirtualDirContext." ], [ "0an", "By sending a specially crafted request, an attacker could exploit this vulnerability to bypass security constraints and view the source code of JSPs for resources." ], [ "0ao", "CVSS Base Score: 6.5" ], [ "0ap", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/132276 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132276] for the current score" ], [ "0aq", "CVSS Environmental Score*: Undefined" ], [ "0ar", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N)" ], [ "0as", "CVEID: CVE-2017-12615 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12615]" ], [ "0at", "DESCRIPTION: Apache Tomcat could allow a remote attacker to execute arbitrary code on the system, caused by an error when running on Windows with HTTP PUTs enabled." ], [ "0au", "By sending a specially crafted request, an attacker could exploit this vulnerability to upload a JSP file and execute arbitrary code on the system." ], [ "0av", "CVSS Base Score: 8.1" ], [ "0aw", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/132277 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132277] for the current score" ], [ "0ax", "CVSS Environmental Score*: Undefined" ], [ "0ay", "CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)" ], [ "0az", "AFFECTED PRODUCTS AND VERSIONS" ], [ "0ba", "IBM OpenPages GRC Platform version 7.1 REMEDIATION/FIXES" ], [ "0bb", "A fix has been created for each affected version of the named product." ], [ "0bc", "Download and install the fix as soon as possible." ], [ "0bd", "Fixes and installation instructions are provided at the URLs listed below:" ], [ "0be", "Fix Download URL For OpenPages GRC Platform 7.1.0.4" ], [ "0bf", "- Apply 7.1.0.4 Interim Fix 1 or later http://www.ibm.com/support/docview.wss?uid=swg24044731 [http://www-01.ibm.com/support/docview.wss?uid=swg24044731]" ], [ "0bg", "For OpenPages GRC Platform v7.0.x customers, IBM recommends upgrading to a fixed, supported version/release/platform of the product." ], [ "0bh", "WORKAROUNDS AND MITIGATIONS" ], [ "0bi", "None known, apply fixes." ], [ "0bj", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS" ], [ "0bk", " Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. REFERENCES" ], [ "0bl", "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]" ], [ "0bm", "On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION" ], [ "0bn", "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]" ], [ "0bo", "IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] CHANGE HISTORY" ], [ "0bp", " 30 April 2018: Original version published" ], [ "0bq", "*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score." ], [ "0br", "Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. DISCLAIMER" ], [ "0bs", "According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\"" ], [ "0bt", "IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE." ], [ "0bu", "CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY." ] ]

[ "0ae", "0af", "0ag", "0ah", "0ai", "0aj", "0ak", "0al", "0am", "0an", "0ao", "0ap", "0aq", "0ar", "0as", "0at", "0au" ]

[ "SPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http://www.hearne.software/Software/SPSS-Grad-Packs-for-Students-by-IBM/FAQ] \n * On the Hub [http://onthehub.com/] \n * StudentDiscounts.com [http://studentdiscounts.com/contact-us.aspx] \n * JourneyEd [https://www.journeyed.com/contact] \n * thinkEDU [https://thinkedu.desk.com/] \n * Studica [http://www.studica.com/technical-support]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n I have SPSS Base licensed with a Sentinel RMS License Manager and purchased an additional module.\nDo I need to re-install all my SPSS clients to be able to use the additional module? \n\nRESOLVING THE PROBLEM\nNo, once the license for the new module is in the license file the application will launch with the additional module.\nThis applies to standalone client licenses as well\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 31923", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Questions regarding the IBM SPSS (Sentinel RMS) Concurrent License Manager. \n\nRESOLVING THE PROBLEM\nHow do I add a new license to the SPSS (Sentinel RMS) License Manager? [http://www.ibm.com/support/docview.wss?uid=swg21989508] \n\nHow do I migrate my SPSS (Sentinel RMS) License Manager client(s) to a new host? [http://www.ibm.com/support/docview.wss?uid=swg21987631]\n\nHow do I move/migrate my License Manager to a new host? [http://www.ibm.com/support/docview.wss?uid=swg21489714]\n\nInstalling and licensing the SPSS Concurrent License Manager in a virtual environment. [http://www.ibm.com/support/docview.wss?uid=swg21677004]\n\nHow do I perform a version upgrade on a solo (non-redundant) License Manager installed on a Windows host? [http://www.ibm.com/support/docview.wss?uid=swg21989211]\n\nHow do I analyze a License Manager usage log file? [http://www.ibm.com/support/docview.wss?uid=swg21986875]\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Business Analytics SPSS Modeler Business Analytics SPSS Statistics Business Analytics SPSS Text Analytics for Surveys", " TECHNOTE (FAQ)\n\nQUESTION\n How To Generate an Authorization and / or license Key for your SPSS add-on module \n\nCAUSE\nWhen licensing an installation of SPSS additional modules are not listed in the License Authorization Wizard\n\nANSWER\nHow to create an Authorization Code or license key to activate the installation of SPSS add-on modules? \n\n\nTo generate an authorization code or license key for your SPSS product, access the \"License Key Center\". If you do not have access, refer to the Accessing the \"License Key Center\" documentation (#1968941) [http://www.ibm.com/support/docview.wss?uid=swg21968941] \n\nGenerating an Authorization code: \n\nLog in to the \"License Key Center\" click the product and version you want to generate an authorization code for \n\n1 - Quantity Purchased and Quantity Available are displayed. \n\n2 - If there is no Quantity available, the code was generated, click the \"view codes\" link to see your code. \n\n3 - If there is Quantity Available click Generate \n\n4 - Choose your quantity. \n\n5 - click Create Multiple codes or One code, click Next \n\n6 - Confirm Quantity, click Next \n\n7 - click Add a Feature (See Examples above your choice), click Next \n\n8 - Confirm installation type Selection, click Next \n\n9 - Select Dongle option (do not check), click Next \n\n10 - Choose expiration date or leave blank for default, click Next \n\n11 - Add comments (not needed, only used for internal tracking) \n\n12 - click Create Authorization code \n\nGenerating a license code from your Authorization code: \n\nSome installations require a license key rather than an authorization code. Such situations are; \n\n- your system does not have internet access \n\n- your companies security protocols do not allow your system to connect to the internet to generate a license key for your software. In this case, you must generate a license key for your software. \n\nWith the Authorization code generated: \n\n1 - click the code \n\n2 - Enter in the Lock code of the users system (the lock code is found by drilling down into the installation files and double-clicking the echoid.exe file) \n\n3 - click Activate \n\n- Paste into the license Authorization Wizard to license the software.\n\nRELATED INFORMATION\n How to Access the IBM License Key Center for your SPSS [http://www-01.ibm.com/support/docview.wss?uid=swg21968941]\nSPSS Help & Support [https://www.ibm.com/analytics/us/en/spss/spss-support/]", "silent install msi TECHNOTE (FAQ)\n\nQUESTION\n How to do a silent install of IBM SPSS Modeler 17? \n\nCAUSE\nThis has been identified as a product defect under APAR PI47109\n\nANSWER\nThe following text shows an example of the MSI command: \n\nC:>msiexec.exe /i ModelerClient64.msi /qn /l*v \nc:\\temp\\Modeler_Silent_Install.log INSTALLDIR=\"C:\\Program \nFiles\\IBM\\SPSS\\Modeler\\17\" DISABLE_COMMUTE=1 LICENSETYPE=\"Network\" \nLSHOST=\"netlicense.mylocation.mycompany.com\" \n\nNote: The above command will restart the machine automatically. \nEnsure you save and close all applications before executing the above command. \n\nIf you are using a single license for the Modeler Client installation then remove the LICENSETYPE parameter and modify LSHOST to =\"no-net\". Once the installation is completed ensure you run the License\nAuthorization Wizard application to license the Modeler Client. \n\ne.g: \n\nC:>msiexec.exe /i ModelerClient64.msi /qn /l*v \nc:\\temp\\Modeler_Silent_Install.log INSTALLDIR=\"C:\\Program \nFiles\\IBM\\SPSS\\Modeler\\17\" DISABLE_COMMUTE=1 LSHOST=\"no-net\" \n\nThis means you can push the install, but you still have to run the License Authorization Wizard because every client would have its own authorization code. \n\nFor a Modeler Server Windows silent install: \n\nChange the parameters \n\nFrom: \n\nc:\\>msiexec.exe /i ModelerServer64.msi /qn /l*v \nc:\\temp\\Modeler_Silent_Install.log INSTALLDIR=\"C:\\Program \nFiles\\IBM\\SPSS\\Modeler\\17\" DISABLE_COMMUTE=1 LICENSETYPE=\"Network\" \nLSHOST=\"netlicense.mylocation.mycompany.com\" \n\nTo: \n\nc:\\>msiexec.exe /i ModelerServer64.msi /qn /l*v \nc:\\temp\\Modeler_Silent_Install.log INSTALLDIR=\"C:\\Program \nFiles\\IBM\\SPSS\\ModelerServer\\17\" DISABLE_COMMUTE=1 SERVERMOD=1 \n\nWhere the value for SERVERMOD depends on the type of installation you \nhave. You can choose from the following values: \n\n0 - Non-Production Mode. If you purchased a separate non-production installation, enter this option. This installation cannot be employed for production use. \n1 - Production Mode. A production installation is a standard installation of SPSS Modeler Server. It is appropriate for production use. \n\n\nRELATED INFORMATION\n Need more help? Our Modeler forum is Live! [https://developer.ibm.com/answers/topics/modeler/?smartspace=predictive-analytics]" ]

[ [ "3a", " TECHNOTE (FAQ) QUESTION" ], [ "3b", " How To Generate an Authorization and / or license Key for your SPSS add-on module CAUSE" ], [ "3c", "When licensing an installation of SPSS additional modules are not listed in the License Authorization Wizard ANSWER" ], [ "3d", "How to create an Authorization Code or license key to activate the installation of SPSS add-on modules?" ], [ "3e", "To generate an authorization code or license key for your SPSS product, access the \"License Key Center\"." ], [ "3f", "If you do not have access, refer to the Accessing the \"License Key Center\" documentation (#1968941) [http://www.ibm.com/support/docview.wss?uid=swg21968941]" ], [ "3g", "Generating an Authorization code:" ], [ "3h", "Log in to the \"License Key Center\" click the product and version you want to generate an authorization code for" ], [ "3i", "1 - Quantity Purchased and Quantity Available are displayed." ], [ "3j", "2 - If there is no Quantity available, the code was generated, click the \"view codes\" link to see your code." ], [ "3k", "3 - If there is Quantity Available click Generate" ], [ "3l", "4 - Choose your quantity." ], [ "3m", "5 - click Create Multiple codes or One code, click Next" ], [ "3n", "6 - Confirm Quantity, click Next" ], [ "3o", "7 - click Add a Feature (See Examples above your choice), click Next" ], [ "3p", "8 - Confirm installation type Selection, click Next" ], [ "3q", "9 - Select Dongle option (do not check), click Next" ], [ "3r", "10 - Choose expiration date or leave blank for default, click Next" ], [ "3s", "11 - Add comments (not needed, only used for internal tracking)" ], [ "3t", "12 - click Create Authorization code" ], [ "3u", "Generating a license code from your Authorization code:" ], [ "3v", "Some installations require a license key rather than an authorization code." ], [ "3w", "Such situations are;" ], [ "3x", "- your system does not have internet access" ], [ "3y", "- your companies security protocols do not allow your system to connect to the internet to generate a license key for your software." ], [ "3z", "In this case, you must generate a license key for your software." ], [ "3aa", "With the Authorization code generated:" ], [ "3ab", "1 - click the code" ], [ "3ac", "2 - Enter in the Lock code of the users system (the lock code is found by drilling down into the installation files and double-clicking the echoid.exe file)" ], [ "3ad", "3 - click Activate" ], [ "3ae", "- Paste into the license Authorization Wizard to license the software. RELATED INFORMATION" ], [ "3af", " How to Access the IBM License Key Center for your SPSS [http://www-01.ibm.com/support/docview.wss?uid=swg21968941]" ], [ "3ag", "SPSS Help & Support [https://www.ibm.com/analytics/us/en/spss/spss-support/]" ] ]

[ "3b", "3c", "3d", "3e", "3f", "3g", "3h", "3i", "3j", "3k", "3l", "3m", "3n", "3o", "3p", "3q", "3r", "3s", "3t", "3u", "3v", "3w", "3x", "3y", "3z", "3aa", "3ab", "3ac", "3ad", "3ae" ]

[ "5697wsz01 OPC TWSZOS ITWSZ CPEXTEND EQQDNTOP TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n There are two different formats for the SYSIN data for the EQQDNTOP step. \n\nRESOLVING THE PROBLEM\nOne format extends the plan by a set number of hours and minutes (for example, 24 hours)\nand one extends the plan to a specific time of day. Using the wrong format can make\nit appear that the EQQDNTOP job is extending the plan to the wrong time. \n\nThe time that the current plan is extended to is shown in the 6.6 panel (EQQSGCPP), as \"planning period end\" for example: \n\n\nEQQSGCPP --------- BROWSING GENERAL CURRENT PLAN INFORMATION\n\nCurrent plan created : 05/04/05 10.01 \nPlanning period end : 05/04/06 12.00\n\nIn this case, if the current plan were extended by 24 hours, using\nthis format of the SYSIN:\n\n----+----1----+----2----+----3\n//SYSIN DD * \n02400 11111111\n\nthe new \"planning period end\" date would be 12.00 (noon) on the\nfollowing day.\n\nNote that regardless of whether the EQQDNTOP job is run at noon,\nor 4 p.m. or 6 a.m., the CP will be extended until noon the\nfollowing day.\n\nSometimes this is not desirable, and it is preferred to have\nthe current plan extended to a set time of day, for example\n6 a.m.\n\nTo accomplish this, the second format of the EQQDNTOP SYSIN can\nbe used, which uses the plan end date (in YYMMDD format) and time\n(in hhmm format), for example:\n\n----+----1----+----2----+----3-\n//SYSIN DD *\n050407060011111111 \n\nThis would cause the planning period end to be set to 06:00 on 04/07/2005.\n\nTo have a consistent plan end time without having to modify\nthe date in the SYSIN date, variable substitution can be\nused in the EQQDNTOP job.\n\nFor example:\n\n//*%OPC SCAN \n//*%OPC SETVAR TDPX=(CYYMMDD+1WD)\n\nIf this is inserted after the job card, variable TDPX will be\nset to one workday more than the current date.\n\nThe SYSIN can then be coded as:\n\n//SYSIN DD *\n&TDPX.060011111111 \n\nThis will extend the current plan to 06:00 on the NEXT work day, regardless of when the CP EXTEND job is executed.", "TCR - 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]", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n User runs a standard report (also known as a 'system report'), such as 'Reconcile - Between Accounts/Opening Balances'. User receives error message. \n\nSYMPTOM\nReconcile - Between Accounts/Opening Balances (Preview) \n\nCognos 8\nAn error has occurred\nDPR-ERR-2079 Firewall Security Rejection. Your request was rejected by the security Firewall.\nCAF rejection details are available in the log. Please contact your administrator.\n\n\n\nCAUSE\nThere are several potential causes for this error message. However, they broadly fall into two catagories: \n\n * Scenario #1 - System was working OK for many weeks/months. Problem appeared one morning (for example, first thing on Monday morning after the weekend). * In this scenario, it is possible that a change was made to at least one of the servers * for example a Microsoft patch was applied to the database server \n * or there was a period of temporary network connection failure (for example DNS changes were made etc. \n \n \n * This would have caused the 'Report Server' (which is typically the same as the Controller application server, for small to medium systems) to lose connectivity to the database ('ContentStore') where it stores its configuration settings \n * This would lead to instability with the Report Server ('IBM Cognos 8 BI') service, which is involved with user logons and running 'standard reports' for Controller. \n \n \n * Scenario #2 - Reports have never worked successfully in the past * Cognos Configuration has been incorrectly configured.\n \n \n\nRESOLVING THE PROBLEM\nScenario #1 \n\nObtain a short period of downtime, and restart the Cognos 8 BI (report) Windows service \n\nSteps: \n\n 1. Ensure no users using the system \n 2. Logon to the Controller application server (or dedicated Cognos 8 BI Report Server, as appropriate) as an administrator \n 3. Launch 'Cognos Configuration' from the Start Menu \n 4. Click the 'Restart Service' icon (at the top left corner). TIP: This will take approx 1 or 2 minutes to complete. \n 5. Test.\n\n\nScenario #2 \nEnsure that the Cognos Configuration (for example, the URI names / DNS names etc.) are correct. \n\nSteps: \nSee separate IBM Technotes (such as those listed below) and follow their advice. \nRELATED INFORMATION\n#1384521 - Getting DPR-ERR-2079 when hit import or disp [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21384521]\n1343027 - Error modifying pacakges in Framework Manager [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21343027]\n\n\n\n\nHISTORICAL NUMBER\n 1040891", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Some queries run faster when bind variables are used in filters and others show better performance without them.\n\nIs it possible to control if Bind Variables are used in Cognos generated SQL? \n\nRESOLVING THE PROBLEM\nIBM Cognos will sometimes use bind variables in the SQL it generates and sometimes it will use parameter markers particularly in the cases of master-detail relationships, reports with prompts, and some model elements such as join or filter expressions that contain prompts. Also, in some of these cases, a parameter value is used rather than the parameter marker itself. Cognos will use whatever it believes will result in the fastest, correct results.\nThere is no setting to control when bind variables are used and when they aren't. The usage of bind variables is controlled by Cognos internal logic algorithm and there is no way for users to exercise any control over that.\n\nIf bind variables are absolutely required or shouldn't be used for any particular queries and Cognos is or isn't using them in the SQL it generates on its own, then custom Pass-Through SQL or a stored procedure can be used by the reports that need it.", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Error \n\nError number: -40 . \n\nSYMPTOM\nIWR raised ObjectStore TIX exception: \nFile Name: S:\\Imp60\\IWR\\ReportManager\\Service\\reportentry.cpp; Line#:3033;\nDesc.:Unknown internal error in Report Manager. (iwr_raised_tix) \n\nwhen attempting to run a IWR report in the browser.\n\n\nOR\n\nThe Application Event Logs could be filled with the following information:\n\nSWID=20001011060000822WEBREPORTS - WEBREPORTS, 429(1cb), 2000/10/11 06:00:00.912; \nRequested job completion could not be performed because the job has already been \nremoved from the queue. The probable cause is that Report Process Dispatcher did not \nrespond for an extended period of time. \n\n\nOR \n\n(D:\\Cognos\\cer1\\bin\\\\IWIRSDisp.exe) has terminated unexpectedly. An attempt will be made to start it again.; BackTrace Info: 1. File Name: S:\\Imp60\\IWR\\Watchdog\\WDRegisteredProcess.cpp; Line#:524; Desc.:; \n\nUnable to start report server. Reason Address space is full <err-0025-0583>Some segment could be referencing a large number of segment address ranges. (err_address_space_full) .; BackTrace Info:\n\n\nRESOLVING THE PROBLEM\nThis could be due to a corrupted scheduling database, the following may resolve the \nissue:\n\n1. Stop all IWR services\n2. Browse to X:\\Program Files\\Cognos\\cer1\\Databases\\IWRJOB.DB\n3. Rename the iwrjob.db file\n4. Start the Object Store services\n5. Launch a DOS session\n6. Change directories to the IWR bin directory\n7. Run the command line: iwcreatedb -job Ensure you use the -job switch, if not all five databases will be recreated.\n8. run the command line iwirsdisp -register \n9. Start the services and you will then be able to schedule and run reports\n\n \n\nHISTORICAL NUMBER\n 91975" ]

[ [ "4a", " TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT) Error" ], [ "4b", "Error number: -40 . SYMPTOM" ], [ "4c", "IWR raised ObjectStore TIX exception:" ], [ "4d", "File Name: S:\\Imp60\\IWR\\ReportManager\\Service\\reportentry.cpp; Line#:3033; Desc." ], [ "4e", ":Unknown internal error in Report Manager. (iwr_raised_tix)" ], [ "4f", "when attempting to run a IWR report in the browser. OR" ], [ "4g", "The Application Event Logs could be filled with the following information:" ], [ "4h", "SWID=20001011060000822WEBREPORTS - WEBREPORTS, 429(1cb), 2000/10/11 06:00:00.912;" ], [ "4i", "Requested job completion could not be performed because the job has already been" ], [ "4j", "removed from the queue." ], [ "4k", "The probable cause is that Report Process Dispatcher did not" ], [ "4l", "respond for an extended period of time. OR" ], [ "4m", "(D:\\Cognos\\cer1\\bin\\\\IWIRSDisp.exe) has terminated unexpectedly." ], [ "4n", "An attempt will be made to start it again." ], [ "4o", "; BackTrace Info: 1." ], [ "4p", "File Name: S:\\Imp60\\IWR\\Watchdog\\WDRegisteredProcess.cpp; Line#:524; Desc. :;" ], [ "4q", "Unable to start report server." ], [ "4r", "Reason Address space is full <err-0025-0583>Some segment could be referencing a large number of segment address ranges. (err_address_space_full) ." ], [ "4s", "; BackTrace Info:" ], [ "4t", "RESOLVING THE PROBLEM" ], [ "4u", "This could be due to a corrupted scheduling database, the following may resolve the issue: 1." ], [ "4v", "Stop all IWR services 2." ], [ "4w", "Browse to X:\\Program Files\\Cognos\\cer1\\Databases\\IWRJOB.DB 3." ], [ "4x", "Rename the iwrjob.db file 4." ], [ "4y", "Start the Object Store services 5." ], [ "4z", "Launch a DOS session 6." ], [ "4aa", "Change directories to the IWR bin directory 7." ], [ "4ab", "Run the command line: iwcreatedb -job Ensure you use the -job switch, if not all five databases will be recreated." ], [ "4ac", "8. run the command line iwirsdisp -register 9." ], [ "4ad", "Start the services and you will then be able to schedule and run reports HISTORICAL NUMBER 91975" ] ]

[ "4c", "4f", "4k", "4m", "4o", "4p", "4q", "4r", "4s", "4t", "4u", "4v", "4w", "4x", "4y", "4z", "4aa", "4ab", "4ac", "4ad" ]

[ "SPSS mac macintosh Apple Macintosh statistics OS supported version compatibility matrix leopard Snow Leopard Lion Mountain Lion 10.8 Mavericks 10.9 22 Yosemite 10.10 (Yosemite) el capitan 10.11 spss 24 Sierra 10.12 High Sierra 10.13 TECHNOTE (FAQ)\n\nQUESTION\n I would like to know what are the supported Macintosh Operating system versions for IBM SPSS Statistics versions? \n\nANSWER\nPlease see the list below. It is strongly recommended to review the platform information on IBM Software Product Compatibility Reports [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.jsp]. The installation of IBM SPSS Statistics software on Apple Macintosh OSX operating systems requires an Intel processor. \n\nA) Apple Macintosh MacOS High Sierra (10.13) \n\nSupport for IBM SPSS Statistics 25 only. Please note that no other SPSS release will be officially supported on High Sierra, but older versions like SPSS Statistics 24 may run as well on High Sierra. \n\nNOTE: There's a known issue with some of the earlier release of Mac High Sierra system (13.0 and 13.1 beta version). \nThe top menu of SPSS 25 may disappear if the Mac OS system is set to Non-English. \nThe official MacOSX 10.13.1 version do not have this issue. So, if you encountert this issue you need to update your Mac OS version to latest official 10.13.1 build from Apple. \n\n \n\nB) Apple Macintosh MacOS Sierra (10.12) \n\nSupport for IBM SPSS Statistics 25 and IBM SPSS Statistics 24 only. For release 24 It is also recommended to install the latest FixPack 2 for release 24 on Mac [http://www-01.ibm.com/support/docview.wss?uid=swg24043574]. [http://www-01.ibm.com/support/docview.wss?uid=swg24042675] \n\nNo older SPSS Statistics releases are supported on Sierra. \n\n \n\nC) Apple Macintosh OSX El Capitan (10.11) \n\nSupport for IBM SPSS Statistics 24. Please see the Release notes - IBM SPSS Statistics 24.0 [http://www-01.ibm.com/support/docview.wss?uid=swg27047057] for known issues on Macintosh. \n\nFull documentation including installation material provided in different languages and manuals for release 24 can be found on IBM SPSS Statistics 24 Documentation [http://www-01.ibm.com/support/docview.wss?uid=swg27047033] webpage. \n\n \n\nAlso, Support for IBM SPSS Statistics 23. Note: if you want to install on El Capitan, please refer to technote 1970391 [http://www-01.ibm.com/support/docview.wss?uid=swg21970391] \n\n \n\nD) Apple Macintosh OSX Yosemite (10.10) \n\nSupport for IBM SPSS Statistics 24, IBM SPSS Statistics 23 and IBM SPSS Statistics 22 \n\n \n\nNote: Mac OSX 10.10 (Yosemite) was released on Thursday, October 16th 2014 by Apple after Statistics 22 was released. If you like to use Statistics 22 on Yosemite you need to install Statistics 22 Fixpack 2 as well. Statistics 22 FixPack 2 and release Statistics 23 are fully tested on Yosemite OSX 10.10. So if you like to run Statistics 22 on Yosemite please install Statistics 22 FixPack 2 and also read the section below: \n\n**** \n\nIn some instances it can be necessary to re-install the legacy Apple Java 6 on 10.10 for the use of Statistics 22 FixPack 2 on this platform\n\nDownload and re-install Apple Java 6 \n\n- After you upgraded your Apple Mac OSX from a previous release to 10.10, Apple Java 6 may no longer exists on your upgraded system. If you then launch Statistics 22 which is an application that relies on Java 6, it can happen, the Mac OS pops up a dialog box stating Java 6 was requested, but none is present.\n- The Java dialog has a \"More Info\" button, which when clicked opens a browser to an Apple Tech Support page for Apple Java 2014-001. A download link is provided:\nhttp://support.apple.com/kb/dl1572 [http://support.apple.com/kb/dl1572]\n- Click on the download link and a DMG containing the Java 6 installer is downloaded.\n- Then you open the Java DMG, double click on the Java installer, follow the prompts and complete the installation of Java 6.\n\n******* \n\n \n\nE) Apple Macintosh OSC Mavericks (10.9) \n\nSupport for IBM SPSS Statistics 23 and IBM SPSS Statistics 22 \n\n*** \n\nNote: IBM SPSS Statistics 22 was developed and released prior to Apple's release of OS X 10.9 (Mavericks). However, Statistics 22 can be installed on Mac OSX 10.9 if you install Apple Java SE 6 (1.6.0_65) on OS X 10.9 first before you install Statistics 22. Please see http://support.apple.com/kb/dl1572 [http://support.apple.com/kb/dl1572] for download. \n\n**** \n\nF) Apple Macintosh OSX Mountain Lion (10.8) \n\nSupport for IBM SPSS Statistics 22 and IBM SPSS Statistics 21 \n\n**** \n\nG) Apple Macintosh OSX Lion (10.7) \n\nSupport for IBM SPSS Statistics 21 \n\n \n\nH) Apple Macintosh OSX Snow Leopard (10.6) \n\nSupport for IBM SPSS Statistics 21 \n\n \n\nOlder SPSS Statistics releases 18 and 19 and 20: \n\nPlease note that SPSS Statistics releases 18, 19 and 20 are no longer supported by IBM. Please contact IBM Sales department to renew your contracts.\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n I am trying to install SPSS for Windows and get the following error:\n\n\"Error 1311 Source file not found basutl.cab\" \n\nand cannot continue with installation. How can I install SPSS? \n\nRESOLVING THE PROBLEM\nThis error message is due to the security policy of Windows which may not let your computer autoplay the SPSS CD-ROM or allow you to double click on the CD in order to run the installer. \n\nThis can be worked around by either editing a registry key or running the setup file off of your desktop.\n\nTo edit the AllocateCDRoms key:\nGo to Start->Run and type 'Regedit' in the Open field. In the registry, go to HKEY_LOCAL_MACHINE\\Software\\Microsoft\\WindowsNT\\CurrentVersion\\WinLogon\\AllocateCDRoms. If the value for AllocateCDRoms is set to \"1\", change it to \"0\", reboot the machine and try again. \n\nWarning: These instructions involve modifying the Windows registry. Modifications to the Windows registry, if not done correctly, can cause serious problems to a Windows system. Consider backing up any registry keys you modify to a .reg file.\n\nTo run setup off the desktop:\nCopy the SPSS folder from the CD-ROM to your Hard Drive (If running Windows NT 4.0/2000, you may skip this step.):\nGo to Start->Programs->Windows Explorer\nRight-click the SPSS CD-ROM and select Open to access the contents\nDrag the entire SPSS directory to directory on your hard drive, e.g. c:\\windows\\temp.\nThis will take a few minutes, but when it is complete, close the Windows Explorer.\n\nLog in with Administrative privileges (For Windows NT 4.0/2000 only).\nGo to Start->Run and Browse to the SPSS directory on the hard drive.\nWithin that directory, navigate to Setup.exe and select Open and Press OK to begin installation.\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 39355", " TECHNOTE (FAQ)\n\nQUESTION\n \nHow to find and download a FixPack for IBM SPSS Statistics software?\n\n\n\n\n\n\n\nANSWER\nDuring a product version lifecycle IBM SPSS development creates a so called FixPack which is a bunch of defect fixes reported by Customers for a product version and release.\nTypically a FixPack is available twice per year and product release cycle.\n\nFor SPSS Statistics 24 the last available FixPack for example is FixPack 2,\nsee also availability notification: SPSS Statistics 24.0 Fix Pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24043574]\nUsually, on availability notification technotes, if you scroll down, you see the link to where you can fownload the FixPack for a particular platform for example for Apple Macintosh OSX.\n\nAnother option is to go to IBM Fixcentral directly\nhttps://www-945.ibm.com/support/fixcentral [https://www-945.ibm.com/support/fixcentral] \n\nFirst, click on \"Find Product\" and enter SPSS or SPSS Statistics. \n\nIf you enter SPSS a list of products will be listed on a dropdown. \n\n\n[/support/docview.wss?uid=swg22003897&aid=1] [/support/docview.wss?uid=swg22003897&aid=1]\n\n\nAs Product select IBM SPSS Statistics. As installed select for example 24.0.0.0 if you have never installed a Fixpack for this release so far or you can select 24.0.0.1 when you have installed FixOack 1 before. \n\nPlease note : if you never installed a fixpack before it is NOT necessary to first install FixPack 1 and then FixPack 2. You can directly install the latest one (FixPack 2) as FixPacks are always cumulative and the latest one include all Fixes that were published in prior FixPacks. \n\nFinally, select the operating system platform where you have installed SPSS Statistics, on example below Mac OXS is used. Click on Cointinue. \n\n\n[/support/docview.wss?uid=swg22003897&aid=2] [/support/docview.wss?uid=swg22003897&aid=2] \n\n \n\nOn the next page select \"Browse for Fixes\" and click Continue. \n\n\n[/support/docview.wss?uid=swg22003897&aid=3] [/support/docview.wss?uid=swg22003897&aid=3] \n\nIf you like to download the interactive installer for Macintosh platform you would select 24.0-IM-S24STATC-Mac-FP002. The silent installer is necessary when you like to perform a silent distribution of the FixPack to multiple Mac computer. \n\n[/support/docview.wss?uid=swg22003897&aid=4] [/support/docview.wss?uid=swg22003897&aid=4] \n\n \n\nOn next page you need to login with your IBM Web ID. Ff you have none you can just register with your e-mail address and a self selected password when you use \"Create an IBMid\". after that you can download the FixPack. To register for an ID is only needed once.\n[/support/docview.wss?uid=swg22003897&aid=5] [/support/docview.wss?uid=swg22003897&aid=5]\n\n[/support/docview.wss?uid=swg22003897&aid=6] [/support/docview.wss?uid=swg22003897&aid=6]", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n I have received a license string that was created from an authorization code. How do I add a license string to SPSS Statistics through the License Authorization Wizard? \n\nRESOLVING THE PROBLEM\n1. Start the IBM SPSS License Authorization Wizard: \n\nWindows \n\n * In the Start menu, select All Programs. \n * In your list of programs, you will see a folder called either SPSS or IBM SPSS Statistics. Open that folder. \n * In that folder, you will see a program called either SPSS License Authorization Wizard or IBM SPSS Statistics License Authorization Wizard. \n * Right-click the License Authorization Wizard icon, and select Run As Administrator. \n * Log in to a Windows user account with full Administrator access rights. (If you do not have a Windows user account with full Administrator rights, please see your local system administrator or technical support provider.) \n * The License Authorization Wizard should then launch. \n * Mac OS X: \n * In your Applications folder, you should see either an IBM folder or an SPSS folder. Open that folder. \n * Inside that folder should be a folder called either SPSS 21, 22, 23, 24 or 25 (depending on your specific version). Open that folder. \n * You should see an application called License Authorization Wizard. Double-click that program. \n * The License Authorization Wizard should then launch. \n\n2. The wizard should display the License Status window, which shows the authorization status for all detected SPSS components. Click Next. \n\n3. On the Product Authorization window, select the button next to License my product now. Click Next. \n\n4. Enter the license string you received in your SPSS order confirmation, then click Next. \n\n5. If successful, the installer should report \"Successfully processed all codes.\" Click Next. \n\n6. Click Finish. You have now completed the installation and license the authorization of your \nnew SPSS software. A note about older versions of SPSS: IBM no longer supports versions of SPSS earlier than version 21, and is not releasing product codes for them. If you are using an older version of SPSS, you must upgrade to version 21 or later.", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS FIXED IF NEXT.\n \n \n \n\nERROR DESCRIPTION\n * You downloaded the Silent Installer file for the installation of\n IBM SPSS Statistics 24 on Macintosh.\n The version you downloaded was the refreshed media posted on\n passport Advantage on 23. June 2016, part number CND2FML:\n IBM SPSS Statistics Client 24.0 Mac OS Silent Multilingual\n (CND2FML)\n Size 1,457MB, Date posted: 23 June 2016\n As a prerequisite you need to have a working License Manager\n 8.6.1 (Concurrent licensing Tools 9.6) installation on any host\n the Mac Client can connect to.\n The file you will download is SPSS_Statistics_24_mac_silent.dmg\n You put the file on a Mac desktop and extract the contents\n The files you have after extraction are\n SPSS_Statistics_Installer.bin and installer.properties\n You create a new folder on desktop and copy both files into the\n new folder.\n On this folder open installer.properties file in TextEdit.app\n and change LSHOST name to the IP address of the host where you\n have installed the license manager\n For example LSHOST=10.142.201.199\n You do not change any of the other properties in\n installer.properties file (only LSHOST) and save the file with\n same name\n Next, open Terminal.app and change directory to the folder where\n you put SPSS_Statistics_Installer.bin and installer.properties\n file\n Start the silent installation from this folder with command\n below\n Sudo ./SPSS_Statistics_Installer.bin -f installer.properties\n When prompted enter your password\n Wait until installer is ready.\n Then open Finder and go to release 24 installation directory on\n this Mac. The content looks good.\n Right click on SPSSStatistics and select Show package content.\n Then go to Contents - Bin folder and open lservrc. The file is\n empty which is correct.\n Then, open file spssprod.inf file in a text Editor and look for\n the DaemonHost value.\n Current behavior:\n On file spssprod.inf you see DaemonHost=no-net which is not\n correct.\n Instead there should be the LSHOST=IP address (or host name) of\n the Sentinel license manager host you entered on\n installer.properties file\n Consequently, when you now launch SPSS 24 on this Mac it says\n IBM SPSS Statistics has expired and will stop functioning. On\n Output Viewer you see license error 7001 - symptom 18 \"There is\n no license for SPSS Statistics\".\n \n \n \n \n \n\nLOCAL FIX\n * As a workaround please enter the daemonhost value in\n spssprod.inf manually to reflect the Sentinel LM host name and\n save the file with the same name.\n Then SPSS 24 will launch properly and get a license token from\n the License manager.\n This issue will be addressed in a future release of IBM SPSS\n Statistics.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n * This affects all users of IBM SPSS Statistics 24 on a Mac *\n * osX platform. *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * SILENT / UNATTENDED / PUSH INSTALLATION OF STATISTICS 24 *\n * (REFRESHED MEDIA) ON MAC NOT WORKING - SPSSPROD.INF NOT *\n * UPDATED *\n ****************************************************************\n * RECOMMENDATION: *\n * Please upgrade to IBM SPSS Statistics 25.0 to resolve this *\n * issue. *\n ****************************************************************\n \n \n \n \n \n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI66924\n \n \n * REPORTED COMPONENT NAME\n SPSS STATISTICS\n \n \n * REPORTED COMPONENT ID\n 5725A54ST\n \n \n * REPORTED RELEASE\n O00\n \n \n * STATUS\n CLOSED FIN\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 2016-08-03\n \n \n * CLOSED DATE\n 2017-08-09\n \n \n * LAST MODIFIED DATE\n 2017-08-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\nAPPLICABLE COMPONENT LEVELS\n * RO00 PSY\n UP" ]

[ [ "0a", "SPSS mac macintosh Apple Macintosh statistics OS supported version compatibility matrix leopard Snow Leopard Lion Mountain Lion 10.8 Mavericks 10.9 22 Yosemite 10.10 (Yosemite) el capitan 10.11 spss 24 Sierra 10.12 High Sierra 10.13 TECHNOTE (FAQ) QUESTION" ], [ "0b", " I would like to know what are the supported Macintosh Operating system versions for IBM SPSS Statistics versions? ANSWER" ], [ "0c", "Please see the list below." ], [ "0d", "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]." ], [ "0e", "The installation of IBM SPSS Statistics software on Apple Macintosh OSX operating systems requires an Intel processor." ], [ "0f", "A) Apple Macintosh MacOS High Sierra (10.13)" ], [ "0g", "Support for IBM SPSS Statistics 25 only." ], [ "0h", "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." ], [ "0i", "NOTE: There's a known issue with some of the earlier release of Mac High Sierra system (13.0 and 13.1 beta version)." ], [ "0j", "The top menu of SPSS 25 may disappear if the Mac OS system is set to Non-English." ], [ "0k", "The official MacOSX 10.13.1 version do not have this issue." ], [ "0l", "So, if you encountert this issue you need to update your Mac OS version to latest official 10.13.1 build from Apple." ], [ "0m", "B) Apple Macintosh MacOS Sierra (10.12)" ], [ "0n", "Support for IBM SPSS Statistics 25 and IBM SPSS Statistics 24 only." ], [ "0o", "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]" ], [ "0p", "No older SPSS Statistics releases are supported on Sierra." ], [ "0q", "C) Apple Macintosh OSX El Capitan (10.11)" ], [ "0r", "Support for IBM SPSS Statistics 24." ], [ "0s", "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." ], [ "0t", "Full 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." ], [ "0u", "Also, Support for IBM SPSS Statistics 23." ], [ "0v", "Note: if you want to install on El Capitan, please refer to technote 1970391 [http://www-01.ibm.com/support/docview.wss?uid=swg21970391]" ], [ "0w", "D) Apple Macintosh OSX Yosemite (10.10)" ], [ "0x", "Support for IBM SPSS Statistics 24, IBM SPSS Statistics 23 and IBM SPSS Statistics 22" ], [ "0y", "Note: Mac OSX 10.10 (Yosemite) was released on Thursday, October 16th 2014 by Apple after Statistics 22 was released." ], [ "0z", "If you like to use Statistics 22 on Yosemite you need to install Statistics 22 Fixpack 2 as well." ], [ "0aa", "Statistics 22 FixPack 2 and release Statistics 23 are fully tested on Yosemite OSX 10.10." ], [ "0ab", "So if you like to run Statistics 22 on Yosemite please install Statistics 22 FixPack 2 and also read the section below: ****" ], [ "0ac", "In 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" ], [ "0ad", "Download and re-install Apple Java 6" ], [ "0ae", "- 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." ], [ "0af", "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." ], [ "0ag", "- 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." ], [ "0ah", "A download link is provided: http://support.apple.com/kb/dl1572 [http://support.apple.com/kb/dl1572]" ], [ "0ai", "- Click on the download link and a DMG containing the Java 6 installer is downloaded." ], [ "0aj", "- Then you open the Java DMG, double click on the Java installer, follow the prompts and complete the installation of Java 6. *******" ], [ "0ak", "E) Apple Macintosh OSC Mavericks (10.9)" ], [ "0al", "Support for IBM SPSS Statistics 23 and IBM SPSS Statistics 22 ***" ], [ "0am", "Note: IBM SPSS Statistics 22 was developed and released prior to Apple's release of OS X 10.9 (Mavericks)." ], [ "0an", "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." ], [ "0ao", "Please see http://support.apple.com/kb/dl1572 [http://support.apple.com/kb/dl1572] for download. ****" ], [ "0ap", "F) Apple Macintosh OSX Mountain Lion (10.8)" ], [ "0aq", "Support for IBM SPSS Statistics 22 and IBM SPSS Statistics 21 ****" ], [ "0ar", "G) Apple Macintosh OSX Lion (10.7)" ], [ "0as", "Support for IBM SPSS Statistics 21" ], [ "0at", "H) Apple Macintosh OSX Snow Leopard (10.6)" ], [ "0au", "Support for IBM SPSS Statistics 21" ], [ "0av", "Older SPSS Statistics releases 18 and 19 and 20:" ], [ "0aw", "Please note that SPSS Statistics releases 18, 19 and 20 are no longer supported by IBM." ], [ "0ax", "Please contact IBM Sales department to renew your contracts. RELATED INFORMATION" ], [ "0ay", " Need more help?" ], [ "0az", "Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]" ] ]

[ "0a", "0ak", "0al" ]

[ "security; vulnerability; psirt; CVE-2014-0230 SECURITY BULLETIN\n\nSUMMARY\n Apache Tomcat is vulnerable to a denial of service and is supplied with specific versions of Rational Lifecycle Integration Adapter for HP ALM. \n\nVULNERABILITY DETAILS\nCVE Information: \n\nCVEID: CVE-2014-0230 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0230]\nDESCRIPTION: Apache Tomcat is vulnerable to a denial of service, caused by an error when uploading files. An attacker could exploit this vulnerability to consume all available memory resources.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/102131 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/102131] 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 Rational Lifecycle Integration Adapter for HP ALM 1.1.2 and 1.1.2.1\n\nREMEDIATION/FIXES\nThe IBM Rational Lifecycle Integration Adapter can be updated with a corrected Tomcat by following the instructions below. This is only applicable to products deployed on Apache Tomcat. Be sure to upgrade all the components that your deployment uses.\n\nNote: Rational Lifecycle Integration Adapter 1.1.x product modification may contain updated Tomcats, however 1.1.x iFixes typically do not update Tomcat. \n\nNOTE: Apache Tomcat is only included by IBM Rational Lifecycle Integration Adapter version 1.1.2 and 1.1.2.1 Previous versions oft he RLIA SE HP Adapter were released as WAR files only.\n\nTo obtain the latest Apache Tomcat, please visit the Apache Tomcat website [https://tomcat.apache.org/download-60.cgi] and download versions 6.0.44 or higher version (in 6.0 stream). Once the Tomcat is obtained, follow the instructions below to replace the existing Tomcat:\n\nUpgrading Tomcat installation \n\n 1. Stop the Rational Lifecycle Integration Adapter server.\n\nNote: The applications may be running in different application server instances or using a delegated converter. \n\n 2. Navigate to the original install directory and rename the JRE folder\n\n<InstallDir>/server/tomcat\n\nto\n\n<InstallDir>/server/tomcat-Original\n\nThis will ensure that the original Tomcat is kept as a backup in the event a restore is required.\n\nExample (Linux):\nmv <InstallDir>/server/tomcat <InstallDir>/server/tomcat-Original \n\n 3. Unzip the new Tomcat file provided by support to the Installation directory. \n\nExample (Linux): unzip <newInsallZip> -d <InstallDir>/server/tomcat/ \n\n 4. Delete the following directories from the exploded archive:\n\n<InstallDir>/server/tomcat/webapps/docs\n<InstallDir>/server/tomcat/webapps/examples\n<InstallDir>/server/tomcat/webapps/host-manager\n<InstallDir>/server/tomcat/webapps/manager \n\n 5. Copy the Apache Tomcat SSL Keystore from the backup:\n\n<InstallDir>/server/tomcat-Original/ibm-team-ssl.keystore\n\nto\n\n<InstallDir>/server/tomcat/ibm-team-ssl.keystore \n\n 6. Copy the Apache Tomcat Server configuration from the backup:\n\n<InstallDir>/server/tomcat-Original/conf/server.xml\n\nto\n\n<InstallDir>/server/tomcat/conf/server.xml \n\n 7. Copy the HP Adapter WAR file from the backup:\n\n<InstallDir>/server/tomcat-Original/webapps/hpqm.war\n\nto\n\n<InstallDir>/server/tomcat/webapps/hpqm.war \n\n 8. Restart the Rational Lifecycle Integration Adapter server\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] [https://www-304.ibm.com/support/docview.wss?uid=swg21496117&wv=1] 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\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.", " SECURITY BULLETIN\n\nSUMMARY\n Multiple vulnerabilities in Open Source Apache Tomcat reported by The Apache Software Foundation affect IBM Tivoli Application Dependency Discovery Manager \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-0762 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0762]\nDESCRIPTION: Apache Tomcat could allow a remote attacker to obtain sensitive information, caused by the failure to process the user supplied password if the specified user name does not exist by the Realm implementation. An attacker could exploit this vulnerability to conduct a timing attack and determine valid usernames on the system.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118407 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118407] 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\nCVEID: CVE-2016-5018 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5018]\nDESCRIPTION: Apache Tomcat could allow a local attacker to bypass security restrictions. An attacker could exploit this vulnerability using a Tomcat utility method to bypass a configured SecurityManager.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118406 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118406] 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\nCVEID: CVE-2016-6794 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6794]\nDESCRIPTION: Apache Tomcat could allow a local attacker to obtain sensitive information, caused by an error in the system property replacement feature. An attacker could exploit this vulnerability to bypass the SecurityManager and read system properties.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118405 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118405] 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\nCVEID: CVE-2016-6796 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6796]\nDESCRIPTION: Apache Tomcat could allow a local attacker to bypass security restrictions. By modifying configuration parameters for the JSP Servlet, an attacker could exploit this vulnerability to bypass a configured SecurityManager.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118404 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118404] 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\nCVEID: CVE-2016-6797 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6797]\nDESCRIPTION: Apache Tomcat could allow a local attacker to gain unauthorized access to the system, caused by an error in the ResourceLinkFactory. An attacker could exploit this vulnerability to gain access to arbitrary global JNDI resources.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118403 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118403] 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\nCVEID: CVE-2016-6816 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6816]\nDESCRIPTION: Apache Tomcat is vulnerable to HTTP response splitting attacks, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability to inject arbitrary HTTP headers and cause the server to return a split response, once the URL is clicked. This would allow the attacker to perform further attacks, such as Web cache poisoning or cross-site scripting, and possibly obtain sensitive information.\nCVSS Base Score: 6.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/119158 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119158] 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:N) \n\nCVEID: CVE-2016-8745 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8745]\nDESCRIPTION: Apache Tomcat could allow a remote attacker to obtain sensitive information, caused by the improper handling of the send file code for the NIO HTTP connector when the Connector code for Tomcat 8.5.x is refactored. An attacker could exploit this vulnerability to obtain the session ID and the response body.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/119642 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119642] 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\nTADDM 7.2.2.0 - 7.2.2.5\nTADDM 7.3.0.0 (TADDM 7.3.0.1-3 - not affected - using WebSphere Liberty Profile) \n\nREMEDIATION/FIXES\nThere are eFixes prepared on top of the latest released FixPack for each stream: \n\n \n\nFix VRMF APAR How to acquire fix efix_TADDM73_tomcat7077_201411291020_1.zip 7.3.0.0 None Download eFix [ftp://ftp.ecurep.ibm.com/fromibm/tivoli/efix_TADDM73_tomcat7077_201411291020_1.zip] efix_TADDM722_tomcat7077_FP520160209.zip 7.2.2.5\nNone Download eFix [ftp://ftp.ecurep.ibm.com/fromibm/tivoli/efix_TADDM722_tomcat7077_FP520160209.zip] \nPlease get familiar with eFix readme in etc/<efix_name>_readme.txt \nNote that the eFix requires manual deletion of the external/apache-tomcat directory. WORKAROUNDS AND MITIGATIONS\nThe solution is to upgrade TADDM to use Tomcat version 7.0.77\n\neFixes are prepared on top of the latest FixPack release, but if there were any custom changes made in a previous version of Apache Tomcat, please reapply them after the upgrade is finished.\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] \nApache Tomcat 7.x vulnerabilities [https://tomcat.apache.org/security-7.html] \nCHANGE HISTORY\n 05 May 2017: Updated file name and efix link.\n02 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.", "WMB IIB SECURITY BULLETIN\n\nSUMMARY\n WebSphere Message Broker and IBM Integration Bus are affected by Open Source Apache Tomcat vulnerability \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-6816 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6816]\nDESCRIPTION: Apache Tomcat is vulnerable to HTTP response splitting attacks, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability to inject arbitrary HTTP headers and cause the server to return a split response, once the URL is clicked. This would allow the attacker to perform further attacks, such as Web cache poisoning or cross-site scripting, and possibly obtain sensitive information.\nCVSS Base Score: 6.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/119158 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119158] 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:N) \n\nAFFECTED PRODUCTS AND VERSIONS\n IBM 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\nProduct VRMF APAR Remediation/Fix IBM Integration Bus V10.0.0.0- 10.0.0.8 IT19472 The APAR is available in fix pack 10.0.0.9 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 IT19472 The APAR is available in fix pack 9.0.0.8 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 IT19472 The APAR is available in fix pack 8.0.0.9 https://www.ibm.com/support/docview.wss?uid=swg24043806 [https://www.ibm.com/support/docview.wss?uid=swg24043806]\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?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] \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 30 Jun 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\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", "CVE-2017-7674; Insight SECURITY BULLETIN\n\nSUMMARY\n Jazz Reporting Service is shipped as a component of Rational Insight. Information about a security vulnerability affecting Jazz Reporting Service has been published in a security bulletin.\n\n\nVULNERABILITY DETAILS\n\nCVEID:CVE-2017-7674 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7674]\nDESCRIPTION:Apache Tomcat could provide weaker than expected security, caused by the failure to add an HTTP Vary header indicating that the response varies depending on Origin by the CORS Filter. A remote attacker could exploit this vulnerability to conduct client and server side cache poisoning.\nCVSS Base Score: 7.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/130248 [https://exchange.xforce.ibmcloud.com/vulnerabilities/130248]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:L/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nPrincipal Product and Version(s) Affected Supporting Product(s) and Version(s) Rational Insight 1.1.1.4, 1.1.1.5 and 1.1.1.6 Jazz Reporting Service 5.0, 5.0.1 and 5.0.2 Rational Insight 1.1.1.7 Jazz Reporting Service 6.0 REMEDIATION/FIXES\n\nConsult the security bulletin Security Bulletin: Security vulnerability has been identified in Jazz Team Server shipped with Jazz Reporting Service (CVE-2017-7674) [http://www-01.ibm.com/support/docview.wss?uid=swg22008257] for vulnerability details and information about fixes.\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 18 January 2018: Initial Publication \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.", " SECURITY BULLETIN\n\nSUMMARY\n \nMultiple vulnerabilities in Open Source Apache Tomcat reported by The Apache Software Foundation affect IBM Tivoli Application Dependency Discovery Manager\n\n\nVULNERABILITY DETAILS\n\nCVE-ID: CVE-2017-5664 [https://exchange.xforce.ibmcloud.com/vulnerabilities/126962]\nDESCRIPTION: Apache Tomcat could allow a remote attacker to bypass security restrictions, caused by the improper handling of specific HTTP request methods for static error pages by the Default Servlet error page mechanism. By sending a specially crafted GET request, an attacker could exploit this vulnerability to bypass HTTP method restrictions and cause the deletion or replacement of the target error page.\nCVSS Base Score: 6.5\nCVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/126962 [https://exchange.xforce.ibmcloud.com/vulnerabilities/126962] for more information\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L)\n\nCVE-ID: CVE-2017-7674 [https://exchange.xforce.ibmcloud.com/vulnerabilities/130248]\nDESCRIPTION: Apache Tomcat could provide weaker than expected security, caused by the failure to add an HTTP Vary header indicating that the response varies depending on Origin by the CORS Filter. A remote attacker could exploit this vulnerability to conduct client and server side cache poisoning.\nCVSS Base Score: 7.3\nCVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/130248 [https://exchange.xforce.ibmcloud.com/vulnerabilities/130248] for more information\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L)\n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nTADDM 7.2.2.0 - 7.2.2.5\nTADDM 7.3.0.0 (TADDM 7.3.0.1-3 - not affected - using WebSphere Liberty Profile)\n\nREMEDIATION/FIXES\n \n\nThere are eFixes prepared on top of the latest released FixPack for each stream: \n\n \n\nFix VRMF APAR How to acquire fix efix_taddm73_tomcat7081_201411291020.zip 7.3.0.0 None Download eFix [ftp://ftp.ecurep.ibm.com/fromibm/tivoli/efix_taddm73_tomcat7081_201411291020.zip] efix_TADDM722_tomcat7081_FP520160209.zip 7.2.2.5\nNone Download eFix [ftp://ftp.ecurep.ibm.com/fromibm/tivoli/efix_TADDM722_tomcat7081_FP520160209.zip] \nPlease get familiar with eFix readme in etc/<efix_name>_readme.txt \nNote that the eFix requires manual deletion of the external/apache-tomcat directory. WORKAROUNDS AND MITIGATIONS\n\nThe only solution is to apply eFix prepared to specific TADDM version (7.2.2.5 or 7.3.0.0). \nIf you need eFix for other TADDM versions, please contact IBM Support.\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 \n21-Sep-17 - Orignal 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." ]

[ [ "3a", "CVE-2017-7674; Insight SECURITY BULLETIN SUMMARY" ], [ "3b", " Jazz Reporting Service is shipped as a component of Rational Insight." ], [ "3c", "Information about a security vulnerability affecting Jazz Reporting Service has been published in a security bulletin. VULNERABILITY DETAILS CVEID:CVE-2017-7674 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7674]" ], [ "3d", "DESCRIPTION:Apache Tomcat could provide weaker than expected security, caused by the failure to add an HTTP Vary header indicating that the response varies depending on Origin by the CORS Filter." ], [ "3e", "A remote attacker could exploit this vulnerability to conduct client and server side cache poisoning." ], [ "3f", "CVSS Base Score: 7.3" ], [ "3g", "CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/130248 [https://exchange.xforce.ibmcloud.com/vulnerabilities/130248]for the current score" ], [ "3h", "CVSS Environmental Score*: Undefined" ], [ "3i", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L)" ], [ "3j", "AFFECTED PRODUCTS AND VERSIONS" ], [ "3k", "Principal Product and Version(s) Affected Supporting Product(s) and Version(s) Rational Insight 1.1.1.4, 1.1.1.5 and 1.1.1.6 Jazz Reporting Service 5.0, 5.0.1 and 5.0.2 Rational Insight 1.1.1.7 Jazz Reporting Service 6.0 REMEDIATION/FIXES" ], [ "3l", "Consult the security bulletin Security Bulletin: Security vulnerability has been identified in Jazz Team Server shipped with Jazz Reporting Service (CVE-2017-7674) [http://www-01.ibm.com/support/docview.wss?uid=swg22008257] for vulnerability details and information about fixes." ], [ "3m", "WORKAROUNDS AND MITIGATIONS None" ], [ "3n", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS" ], [ "3o", " Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. REFERENCES" ], [ "3p", "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]" ], [ "3q", "On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION" ], [ "3r", "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]" ], [ "3s", "IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] CHANGE HISTORY" ], [ "3t", " 18 January 2018: Initial Publication" ], [ "3u", "*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score." ], [ "3v", "Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. DISCLAIMER" ], [ "3w", "According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\"" ], [ "3x", "IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE." ], [ "3y", "CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY." ] ]

[ "3c", "3d", "3e", "3f", "3g", "3h", "3i", "3j", "3k", "3l", "4j", "4k", "4l", "4m", "4n", "4o", "4p" ]

[ "security; vulnerability; psirt; CVE-2014-0230 SECURITY BULLETIN\n\nSUMMARY\n Apache Tomcat is vulnerable to a denial of service and is supplied with specific versions of Rational Lifecycle Integration Adapter for HP ALM. \n\nVULNERABILITY DETAILS\nCVE Information: \n\nCVEID: CVE-2014-0230 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0230]\nDESCRIPTION: Apache Tomcat is vulnerable to a denial of service, caused by an error when uploading files. An attacker could exploit this vulnerability to consume all available memory resources.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/102131 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/102131] 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 Rational Lifecycle Integration Adapter for HP ALM 1.1.2 and 1.1.2.1\n\nREMEDIATION/FIXES\nThe IBM Rational Lifecycle Integration Adapter can be updated with a corrected Tomcat by following the instructions below. This is only applicable to products deployed on Apache Tomcat. Be sure to upgrade all the components that your deployment uses.\n\nNote: Rational Lifecycle Integration Adapter 1.1.x product modification may contain updated Tomcats, however 1.1.x iFixes typically do not update Tomcat. \n\nNOTE: Apache Tomcat is only included by IBM Rational Lifecycle Integration Adapter version 1.1.2 and 1.1.2.1 Previous versions oft he RLIA SE HP Adapter were released as WAR files only.\n\nTo obtain the latest Apache Tomcat, please visit the Apache Tomcat website [https://tomcat.apache.org/download-60.cgi] and download versions 6.0.44 or higher version (in 6.0 stream). Once the Tomcat is obtained, follow the instructions below to replace the existing Tomcat:\n\nUpgrading Tomcat installation \n\n 1. Stop the Rational Lifecycle Integration Adapter server.\n\nNote: The applications may be running in different application server instances or using a delegated converter. \n\n 2. Navigate to the original install directory and rename the JRE folder\n\n<InstallDir>/server/tomcat\n\nto\n\n<InstallDir>/server/tomcat-Original\n\nThis will ensure that the original Tomcat is kept as a backup in the event a restore is required.\n\nExample (Linux):\nmv <InstallDir>/server/tomcat <InstallDir>/server/tomcat-Original \n\n 3. Unzip the new Tomcat file provided by support to the Installation directory. \n\nExample (Linux): unzip <newInsallZip> -d <InstallDir>/server/tomcat/ \n\n 4. Delete the following directories from the exploded archive:\n\n<InstallDir>/server/tomcat/webapps/docs\n<InstallDir>/server/tomcat/webapps/examples\n<InstallDir>/server/tomcat/webapps/host-manager\n<InstallDir>/server/tomcat/webapps/manager \n\n 5. Copy the Apache Tomcat SSL Keystore from the backup:\n\n<InstallDir>/server/tomcat-Original/ibm-team-ssl.keystore\n\nto\n\n<InstallDir>/server/tomcat/ibm-team-ssl.keystore \n\n 6. Copy the Apache Tomcat Server configuration from the backup:\n\n<InstallDir>/server/tomcat-Original/conf/server.xml\n\nto\n\n<InstallDir>/server/tomcat/conf/server.xml \n\n 7. Copy the HP Adapter WAR file from the backup:\n\n<InstallDir>/server/tomcat-Original/webapps/hpqm.war\n\nto\n\n<InstallDir>/server/tomcat/webapps/hpqm.war \n\n 8. Restart the Rational Lifecycle Integration Adapter server\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] [https://www-304.ibm.com/support/docview.wss?uid=swg21496117&wv=1] 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\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.", " SECURITY BULLETIN\n\nSUMMARY\n Multiple vulnerabilities in Open Source Apache Tomcat reported by The Apache Software Foundation affect IBM Tivoli Application Dependency Discovery Manager \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-0762 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0762]\nDESCRIPTION: Apache Tomcat could allow a remote attacker to obtain sensitive information, caused by the failure to process the user supplied password if the specified user name does not exist by the Realm implementation. An attacker could exploit this vulnerability to conduct a timing attack and determine valid usernames on the system.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118407 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118407] 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\nCVEID: CVE-2016-5018 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5018]\nDESCRIPTION: Apache Tomcat could allow a local attacker to bypass security restrictions. An attacker could exploit this vulnerability using a Tomcat utility method to bypass a configured SecurityManager.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118406 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118406] 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\nCVEID: CVE-2016-6794 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6794]\nDESCRIPTION: Apache Tomcat could allow a local attacker to obtain sensitive information, caused by an error in the system property replacement feature. An attacker could exploit this vulnerability to bypass the SecurityManager and read system properties.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118405 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118405] 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\nCVEID: CVE-2016-6796 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6796]\nDESCRIPTION: Apache Tomcat could allow a local attacker to bypass security restrictions. By modifying configuration parameters for the JSP Servlet, an attacker could exploit this vulnerability to bypass a configured SecurityManager.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118404 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118404] 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\nCVEID: CVE-2016-6797 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6797]\nDESCRIPTION: Apache Tomcat could allow a local attacker to gain unauthorized access to the system, caused by an error in the ResourceLinkFactory. An attacker could exploit this vulnerability to gain access to arbitrary global JNDI resources.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118403 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118403] 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\nCVEID: CVE-2016-6816 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6816]\nDESCRIPTION: Apache Tomcat is vulnerable to HTTP response splitting attacks, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability to inject arbitrary HTTP headers and cause the server to return a split response, once the URL is clicked. This would allow the attacker to perform further attacks, such as Web cache poisoning or cross-site scripting, and possibly obtain sensitive information.\nCVSS Base Score: 6.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/119158 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119158] 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:N) \n\nCVEID: CVE-2016-8745 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8745]\nDESCRIPTION: Apache Tomcat could allow a remote attacker to obtain sensitive information, caused by the improper handling of the send file code for the NIO HTTP connector when the Connector code for Tomcat 8.5.x is refactored. An attacker could exploit this vulnerability to obtain the session ID and the response body.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/119642 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119642] 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\nTADDM 7.2.2.0 - 7.2.2.5\nTADDM 7.3.0.0 (TADDM 7.3.0.1-3 - not affected - using WebSphere Liberty Profile) \n\nREMEDIATION/FIXES\nThere are eFixes prepared on top of the latest released FixPack for each stream: \n\n \n\nFix VRMF APAR How to acquire fix efix_TADDM73_tomcat7077_201411291020_1.zip 7.3.0.0 None Download eFix [ftp://ftp.ecurep.ibm.com/fromibm/tivoli/efix_TADDM73_tomcat7077_201411291020_1.zip] efix_TADDM722_tomcat7077_FP520160209.zip 7.2.2.5\nNone Download eFix [ftp://ftp.ecurep.ibm.com/fromibm/tivoli/efix_TADDM722_tomcat7077_FP520160209.zip] \nPlease get familiar with eFix readme in etc/<efix_name>_readme.txt \nNote that the eFix requires manual deletion of the external/apache-tomcat directory. WORKAROUNDS AND MITIGATIONS\nThe solution is to upgrade TADDM to use Tomcat version 7.0.77\n\neFixes are prepared on top of the latest FixPack release, but if there were any custom changes made in a previous version of Apache Tomcat, please reapply them after the upgrade is finished.\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] \nApache Tomcat 7.x vulnerabilities [https://tomcat.apache.org/security-7.html] \nCHANGE HISTORY\n 05 May 2017: Updated file name and efix link.\n02 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.", "WMB IIB SECURITY BULLETIN\n\nSUMMARY\n WebSphere Message Broker and IBM Integration Bus are affected by Open Source Apache Tomcat vulnerability \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-6816 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6816]\nDESCRIPTION: Apache Tomcat is vulnerable to HTTP response splitting attacks, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability to inject arbitrary HTTP headers and cause the server to return a split response, once the URL is clicked. This would allow the attacker to perform further attacks, such as Web cache poisoning or cross-site scripting, and possibly obtain sensitive information.\nCVSS Base Score: 6.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/119158 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119158] 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:N) \n\nAFFECTED PRODUCTS AND VERSIONS\n IBM 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\nProduct VRMF APAR Remediation/Fix IBM Integration Bus V10.0.0.0- 10.0.0.8 IT19472 The APAR is available in fix pack 10.0.0.9 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 IT19472 The APAR is available in fix pack 9.0.0.8 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 IT19472 The APAR is available in fix pack 8.0.0.9 https://www.ibm.com/support/docview.wss?uid=swg24043806 [https://www.ibm.com/support/docview.wss?uid=swg24043806]\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?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] \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 30 Jun 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\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", "CVE-2017-7674; Insight SECURITY BULLETIN\n\nSUMMARY\n Jazz Reporting Service is shipped as a component of Rational Insight. Information about a security vulnerability affecting Jazz Reporting Service has been published in a security bulletin.\n\n\nVULNERABILITY DETAILS\n\nCVEID:CVE-2017-7674 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7674]\nDESCRIPTION:Apache Tomcat could provide weaker than expected security, caused by the failure to add an HTTP Vary header indicating that the response varies depending on Origin by the CORS Filter. A remote attacker could exploit this vulnerability to conduct client and server side cache poisoning.\nCVSS Base Score: 7.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/130248 [https://exchange.xforce.ibmcloud.com/vulnerabilities/130248]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:L/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nPrincipal Product and Version(s) Affected Supporting Product(s) and Version(s) Rational Insight 1.1.1.4, 1.1.1.5 and 1.1.1.6 Jazz Reporting Service 5.0, 5.0.1 and 5.0.2 Rational Insight 1.1.1.7 Jazz Reporting Service 6.0 REMEDIATION/FIXES\n\nConsult the security bulletin Security Bulletin: Security vulnerability has been identified in Jazz Team Server shipped with Jazz Reporting Service (CVE-2017-7674) [http://www-01.ibm.com/support/docview.wss?uid=swg22008257] for vulnerability details and information about fixes.\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 18 January 2018: Initial Publication \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.", " SECURITY BULLETIN\n\nSUMMARY\n \nMultiple vulnerabilities in Open Source Apache Tomcat reported by The Apache Software Foundation affect IBM Tivoli Application Dependency Discovery Manager\n\n\nVULNERABILITY DETAILS\n\nCVE-ID: CVE-2017-5664 [https://exchange.xforce.ibmcloud.com/vulnerabilities/126962]\nDESCRIPTION: Apache Tomcat could allow a remote attacker to bypass security restrictions, caused by the improper handling of specific HTTP request methods for static error pages by the Default Servlet error page mechanism. By sending a specially crafted GET request, an attacker could exploit this vulnerability to bypass HTTP method restrictions and cause the deletion or replacement of the target error page.\nCVSS Base Score: 6.5\nCVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/126962 [https://exchange.xforce.ibmcloud.com/vulnerabilities/126962] for more information\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L)\n\nCVE-ID: CVE-2017-7674 [https://exchange.xforce.ibmcloud.com/vulnerabilities/130248]\nDESCRIPTION: Apache Tomcat could provide weaker than expected security, caused by the failure to add an HTTP Vary header indicating that the response varies depending on Origin by the CORS Filter. A remote attacker could exploit this vulnerability to conduct client and server side cache poisoning.\nCVSS Base Score: 7.3\nCVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/130248 [https://exchange.xforce.ibmcloud.com/vulnerabilities/130248] for more information\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L)\n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nTADDM 7.2.2.0 - 7.2.2.5\nTADDM 7.3.0.0 (TADDM 7.3.0.1-3 - not affected - using WebSphere Liberty Profile)\n\nREMEDIATION/FIXES\n \n\nThere are eFixes prepared on top of the latest released FixPack for each stream: \n\n \n\nFix VRMF APAR How to acquire fix efix_taddm73_tomcat7081_201411291020.zip 7.3.0.0 None Download eFix [ftp://ftp.ecurep.ibm.com/fromibm/tivoli/efix_taddm73_tomcat7081_201411291020.zip] efix_TADDM722_tomcat7081_FP520160209.zip 7.2.2.5\nNone Download eFix [ftp://ftp.ecurep.ibm.com/fromibm/tivoli/efix_TADDM722_tomcat7081_FP520160209.zip] \nPlease get familiar with eFix readme in etc/<efix_name>_readme.txt \nNote that the eFix requires manual deletion of the external/apache-tomcat directory. WORKAROUNDS AND MITIGATIONS\n\nThe only solution is to apply eFix prepared to specific TADDM version (7.2.2.5 or 7.3.0.0). \nIf you need eFix for other TADDM versions, please contact IBM Support.\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 \n21-Sep-17 - Orignal 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." ]

[ [ "4a", " SECURITY BULLETIN SUMMARY" ], [ "4b", "Multiple vulnerabilities in Open Source Apache Tomcat reported by The Apache Software Foundation affect IBM Tivoli Application Dependency Discovery Manager VULNERABILITY DETAILS" ], [ "4c", "CVE-ID: CVE-2017-5664 [https://exchange.xforce.ibmcloud.com/vulnerabilities/126962]" ], [ "4d", "DESCRIPTION: Apache Tomcat could allow a remote attacker to bypass security restrictions, caused by the improper handling of specific HTTP request methods for static error pages by the Default Servlet error page mechanism." ], [ "4e", "By sending a specially crafted GET request, an attacker could exploit this vulnerability to bypass HTTP method restrictions and cause the deletion or replacement of the target error page." ], [ "4f", "CVSS Base Score: 6.5" ], [ "4g", "CVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/126962 [https://exchange.xforce.ibmcloud.com/vulnerabilities/126962] for more information" ], [ "4h", "CVSS Environmental Score*: Undefined" ], [ "4i", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L)" ], [ "4j", "CVE-ID: CVE-2017-7674 [https://exchange.xforce.ibmcloud.com/vulnerabilities/130248]" ], [ "4k", "DESCRIPTION: Apache Tomcat could provide weaker than expected security, caused by the failure to add an HTTP Vary header indicating that the response varies depending on Origin by the CORS Filter." ], [ "4l", "A remote attacker could exploit this vulnerability to conduct client and server side cache poisoning." ], [ "4m", "CVSS Base Score: 7.3" ], [ "4n", "CVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/130248 [https://exchange.xforce.ibmcloud.com/vulnerabilities/130248] for more information" ], [ "4o", "CVSS Environmental Score*: Undefined" ], [ "4p", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L)" ], [ "4q", "AFFECTED PRODUCTS AND VERSIONS" ], [ "4r", "TADDM 7.2.2.0 - 7.2.2.5" ], [ "4s", "TADDM 7.3.0.0 (TADDM 7.3.0.1-3 - not affected - using WebSphere Liberty Profile) REMEDIATION/FIXES" ], [ "4t", "There are eFixes prepared on top of the latest released FixPack for each stream:" ], [ "4u", "Fix VRMF APAR How to acquire fix efix_taddm73_tomcat7081_201411291020.zip 7.3.0.0 None Download eFix [ftp://ftp.ecurep.ibm.com/fromibm/tivoli/efix_taddm73_tomcat7081_201411291020.zip] efix_TADDM722_tomcat7081_FP520160209.zip 7.2.2.5" ], [ "4v", "None Download eFix [ftp://ftp.ecurep.ibm.com/fromibm/tivoli/efix_TADDM722_tomcat7081_FP520160209.zip]" ], [ "4w", "Please get familiar with eFix readme in etc/<efix_name>_readme.txt" ], [ "4x", "Note that the eFix requires manual deletion of the external/apache-tomcat directory." ], [ "4y", "WORKAROUNDS AND MITIGATIONS" ], [ "4z", "The only solution is to apply eFix prepared to specific TADDM version (7.2.2.5 or 7.3.0.0)." ], [ "4aa", "If you need eFix for other TADDM versions, please contact IBM Support." ], [ "4ab", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS" ], [ "4ac", " Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. REFERENCES" ], [ "4ad", "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]" ], [ "4ae", "On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION" ], [ "4af", "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]" ], [ "4ag", "IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] CHANGE HISTORY" ], [ "4ah", "21-Sep-17 - Orignal version published" ], [ "4ai", "*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score." ], [ "4aj", "Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. DISCLAIMER" ], [ "4ak", "According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\"" ], [ "4al", "IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE." ], [ "4am", "CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY." ] ]

[ "3c", "3d", "3e", "3f", "3g", "3h", "3i", "3j", "3k", "3l", "4j", "4k", "4l", "4m", "4n", "4o", "4p" ]

[ "cecdataprovider aixdataprovider hmcdataprovider system p data provider shared memory emsvcsctrl harmad overflow allocation malloc TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Shared memory is exhausted when harmad daemon is running \n\nSYMPTOM\nData provider not starting and no data in the Tivoli Enterprise Portal for CEC/HMC/VIOS/AIX system P agent\n\n\nCAUSE\nThe harmad daemon is running and taking all shared memory\n\nENVIRONMENT\nSystems running the Event Management subsystem and the CEC Base, HMC Base, AIX Premium or VIOS Premium ITM agents\n\nDIAGNOSING THE PROBLEM\nThe system P agent data provider is exiting with errors like:\nERROR: Spmi: Shared Memory OverFlow.. STBase=70000000, SHigh=70000570\nor:\nERROR: Spmi: Unable to malloc\n\nRESOLVING THE PROBLEM\nThe harmad daemon is the resource monitor for AIX operating system resources and is part of the AIX Event Management subsystem. It also uses shared memory and is known to take a lot of shared memory.\n\n\n\n\nThe harmad daemon can be stopped running the following command:\nemsvcsctrl -k\n\nAfter that, it is recommended to run the following procedure:\n1. genld -ld | grep -p Spmi | grep Proc\n# List all Spmi consumers running\n2. Stop/kill all Spmi consumer process listed in step 1. above:\na) stop the CEC agent\nb) for the other processes, stop them in a clean way, or use\nkill <pid> (do not use kill -9 <pid> )\n3. slibclean\n4. genld -ld | grep -p Spmi | grep Proc\n# Should not list anything as we stopped all Spmi consumer\n5. ipcs -m | grep 0x78 \n# Should not list anything. If at least an entry is listed then shared memory clean-up steps are required.\n\nShared memory cleanup steps: -\n6. ipcrm -m <ID> # For all entries in output of 5. above\n7. slibclean\n\nNow, try to start the system P agent.\n\nIn case you want to start harmad and other Spmi consumers, run the commands in the following order:\n1. start xmwlm\n2. emsvcsctrl -s # Kindly do this if you really want to run harmad.\n3. start any other Spmi consumer process which you want to run.\n\n\nRegarding the harmad daemon, there's an APAR stating that it is in fact no longer required:\nIBM IZ86786: PREVENT EMAIXOS (HARMAD) FROM RUNNING IN HACMP ON AIX 5.3\n\nIn case you no longer need the harmad daemon, it is recommended that you delete the daemon and the associated subsystem using the following command:\nemsvcsctrl -d\n\nFor more info about emsvcsctrl:\nhttp://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds2/emsvcsctrl.htm [http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cmds/doc/aixcmds2/emsvcsctrl.htm]", " FIXES ARE AVAILABLE\nIBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008) [http://www-01.ibm.com/support/docview.wss?uid=swg24031354]\nIBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009) [http://www-01.ibm.com/support/docview.wss?uid=swg24032067]\nIBM Tivoli Monitoring 6.2.2 Fix Pack 6 (6.2.2-TIV-ITM-FP0006) [http://www-01.ibm.com/support/docview.wss?uid=swg24030135]\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 * Severity: 1\n Approver:BEH\n Compid: 5724K1000 Tivoli Universal Agent\n Abstract:UA during startup may enter infinite loop and leak\n memory\n \n Environment:\n 6.2.1, 6.2.2\n \n Problem Description:\n Universal Agent ate up memory to over 2GB immediately after UA\n starting up.\n \n Detailed Recreation Procedure:\n The detailed recreation procedure is unknown for now.\n A lot of recycling UA can cause the problem infrequently.\n \n Related Files and Output:\n When the problem occurs, the following line is outputted\n infinitely under KBB_RAS1=ERROR METRICS (UNIT:kumdcw ALL)\n (UNIT:kumdchsv DET METRICS STATE ERROR) (UNIT:kumpldsf DET)\n =======\n (4B863BE9.00C5-3:kumdchsv.cpp,5498,\"DCHserver::dp_getApplNameLis\n t\") Comparing DCH_dc_waitForApplNameList 2048 srcName[ASFS]\n against waiterType[2070] source[NULL]\n =======\n \n \n \n \n \n\nLOCAL FIX\n * N/A\n \n \n \n \n \n\nPROBLEM SUMMARY\n * There is an exposure in startup processing of UA. If the UA\n thread timing occurs in a particular sequence, an infinite loop\n condition is triggered and 8 bytes of memory is allocated\n repeatedly until system's heap memory space is exhausted. UA is\n effectively disabled and cannot monitor.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * A statement missing from inside the loop logic was added to\n reset a flag, thereby eliminating the possible infinite loop and\n the subsequent memory leak.\n \n The fix for this APAR is included in the following maintenance\n vehicle:\n | fix pack | 6.2.1.0-TIV-ITM-FP0003\n \n Note: Search the IBM Technical support web site for maintenance\n package availability\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IZ71021\n \n \n * REPORTED COMPONENT NAME\n UNIVERSAL AGENT\n \n \n * REPORTED COMPONENT ID\n 5724K1000\n \n \n * REPORTED RELEASE\n 621\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 2010-03-01\n \n \n * CLOSED DATE\n 2010-03-22\n \n \n * LAST MODIFIED DATE\n 2010-07-22\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 UNIVERSAL AGENT\n \n \n * FIXED COMPONENT ID\n 5724K1000\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R621 PSY\n UP", "Netcool; Omnibus; Agent; ITM; TEPS; TEMS; silent TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n \nHow can you configure the Netcool Omnibus ITM Agent silently? \n\nSYMPTOM\n \n\nThere is no response file to silently install the Netcool/Omnibus ITM Agent\n\n\nRESOLVING THE PROBLEM\n\nThe response file is in /opt/IBM/ITM/samples or equivalent directory \n\nThe silent_config.txt file is the generic response file for an agent. Configure the ITM parameters that are desired. Also add these 2 parameters for the agent-specific configuration. For example: \n# Location of the metrics log files for the OMNIbus agent \nKNO_LOG_DIR=/opt/IBM/netcool/omnibus/log \n\n# Name of the ObjectServer to monitor \nKNO_OBJSRV_NAME=NCOMS \n\nThen run this command to do the silent config: \n\nitmcmd config -p <absolute_path_to_response_file> -A no \n\nIf the files do not exist in the samples directory then you need to do the following:\n\n$CANDLEHOME/bin/itmcmd manage & \n\n[/support/docview.wss?uid=swg21438008&aid=1] [/support/docview.wss?uid=swg21438008&aid=1]\n\nThe agent will supply the silent_install.txt file, but you must generate the silent_config.txt parameter file using an installed agent. This file can then be used as a template. To create the silent config response file, open the Manage Tivoli Enterprise Monitoring Services (MTEMS) window, right-click selected agent and choose \"Advanced/Utilities/Generate Response Files\" menu option. Be aware that in created file, all passwords/encryption keys need to be provided manually. This file can then be modified and used as the parameter to configure other instances of that agent.", " 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", "Spmi.lock tmp TEP Portal spmi consumers system P CEC Base HMC Premium AIX VIOS root non-root permissions shared memory data provider aixdataprovider cecdataprovider hmcdataprovider TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Starting the system P agent as a non-root user, the data provider does not start, but instead spawns a defunct process. \n\nSYMPTOM\nNo data for the system P agent in the Tivoli Enterprise Portal.\n\n\nCAUSE\nAIX APAR IZ89719 describes a problem where the file /tmp/Spmi.lock is being created with wrong permissions: \n\nhttps://www-304.ibm.com/support/docview.wss?uid=isg1IZ89719 [https://www-304.ibm.com/support/docview.wss?uid=isg1IZ89719]\n\nThis usually occurs when the agent has been started in the past with root user, leading to permissions where only the root user is able to access this file. This file is created when a SPMI consumer (like the system P agent) is started.\n\n\nENVIRONMENT\nSystem P agents (CEC Base, AIX Premium, VIOS Premium, HMC Base) running as non-root\n\n\n\nDIAGNOSING THE PROBLEM\nThere are no meaningful messages or errors in the agent logs and traces. \n\nPermissions should be -rwSr--r-- , and owned by the user running the agents.\nIn case permissions are like this, and/or the file is owned by root, the agent user (non-root) will not be able to access the file.\n\n\nRESOLVING THE PROBLEM\nYou can try changing the permissions for /tmp/Spmi.lock, so they match the above recommendation. \n\nBest would be to delete this file, since it will be recreated next time the agent restarts, with correct permissions.\nThere can be cases that this issue causes shared memory locks, so you should clear the shared memory as well, by following this procedure:\n\n1° Run:\ngenld -l | grep -p spmi | grep Proc_pid\n=> command output will list all the processes using SPMI\n\n2° Stop all the processes returned above, and also others which might use the SPMI shared library (topasrec, xmtopas, xmtopasagg, xmservd,filtd, xmperf, 3dmon, ptxrlog, harmd, topas, any PSSP process, ITM System P agents) if they are currently running on your system.\n\n3° Check if there are any defunct processes still running:\nps -ef | grep defunct\nand kill each of them.\n\n4° SU to root, run \"ipcs -m\" command and check for any segment \"KEY\" that begins with '0x78', as listed below:\nT ID KEY\nm 0 0xc76283cc\nm 1 0x78002323\n\nIf there are any such segments, make sure the process which uses those shared segments is stopped:\nipcrm -m <ID #>\n=> will clear up those shared memory segments.\n\n5° Check whether there are still processes using SPMI:\ngenld -l | grep -p Spmi | grep Proc | awk '{ print $2 }' | xargs kill\n=> will kill them\n\n6° Run \"slibclean\"\n\n7° Change the ownership of /tmp/Spmi.lock to your non-root user, and set permissions to -rwSr--r--.\nYou can use these commands, supposing that your user is tivadmin, belonging to the staff group:\nchown tivadmin:staff /tmp/Spmi.lock\nchmod u+r /tmp/Spmi.lock\n\nPermissions should look like:\n-rwSr--r-- 1 tivadmin staff 0 Jan 05 10:16 Spmi.lock\n\n8° As your agent user, start the system P agent again" ]

[ [ "3a", " DOWNLOADABLE FILES ABSTRACT" ], [ "3b", " This fix resolves the APARs listed in the APAR Number(s) section below, and adds enhancement feature 215857 to add hardware events. DOWNLOAD DESCRIPTION" ], [ "3c", "Copyright International Business Machines Corporation 2015." ], [ "3d", "All rights reserved." ], [ "3e", "Component: IBM(R) Tivoli(R) Monitoring: HMC Base Agent, Version 6.2.2.3" ], [ "3f", "Component ID: 5724C04HB" ], [ "3g", "Interim Fix 0004, 6.2.2.3-TIV-ITM_HMC_BASE-IF0004" ], [ "3h", "Date: October 20, 2015 Contents:" ], [ "3i", "1.0 General description" ], [ "3j", "2.0 Problems fixed" ], [ "3k", "3.0 Architecture and prerequisites" ], [ "3l", "4.0 Image directory contents" ], [ "3m", "5.0 Installation instructions" ], [ "3n", "6.0 Additional installation information" ], [ "3o", "7.0 Known problems and workarounds" ], [ "3p", "8.0 Additional product information" ], [ "3q", "9.0 Copyright and trademark information 10.0 Notices" ], [ "3r", "1.0 General description ===============" ], [ "3s", "This fix resolves the APARs and defects listed in the \"Problems Fixed\" section below." ], [ "3t", "2.0 Problems fixed ============" ], [ "3u", "The following problems are addressed by this fix. 2.1 APARs --------------- APAR: IV67769" ], [ "3v", "Abstract: APPLICATION SUPPORT MISMATCH WARNING MESSAGE" ], [ "3w", "Additional information: After installing interim fix" ], [ "3x", "6.2.2.3-TIV-ITM_HMC_BASE-IF0003, the Tivoli Enterprise" ], [ "3y", "Portal might display a warning indicator that states" ], [ "3z", "Application Support Mismatch and shows HMC Base Servers" ], [ "3aa", "with Client Version 06220302 and Server Version 06220303. 2.3 Enhancements ------------------ Feature: 215857" ], [ "3ab", "Abstract: New Hardware Events Attribute Group" ], [ "3ac", "Additional information: Add a new attribute group to collect" ], [ "3ad", "hardware events from the Hardware Management Console (HMC)." ], [ "3ae", "Attribute group name: Hardware Events" ], [ "3af", "Table name : KPHHDWEVNTS" ], [ "3ag", "Warehouse table name: KPH_HARDWARE_EVENTS or KPHHDWEVNTS Attribute descriptions:" ], [ "3ah", "Problem_No - The problem number of the event." ], [ "3ai", "Reference_Code - The reference code for the event." ], [ "3aj", "First_Report_Time - The first time when the event was reported." ], [ "3ak", "PMH_No - The IBM hardware support PMR number that" ], [ "3al", "was created if the call home was successful." ], [ "3am", "Firmware_Fix - The Firmware Fix for the event." ], [ "3an", "Service_Event_Text - The description of the service event." ], [ "3ao", "Approval_State - The event approval state, either approved or unapproved." ], [ "3ap", "Duplicated_Count - The number of times the event has occurred." ], [ "3aq", "Severity - The event severity." ], [ "3ar", "System_MTMS - The machine type/model of the server" ], [ "3as", "reporting the event." ], [ "3at", "Enclosure_MTMS - The machine type/model of the enclosure" ], [ "3au", "system reporting the event." ], [ "3av", "Created_Time - The time the event was created." ], [ "3aw", "Event_Time - The time the event was reported." ], [ "3ax", "Call_Home_Intended - Defines if call home was intended for this" ], [ "3ay", "event, either true or false." ], [ "3az", "Analyzing_MTMS - The machine type/model of the analyzing system." ], [ "3ba", "Reference_Code_Extent - The extent of reference code." ], [ "3bb", "System_Ref_code - The system reference code." ], [ "3bc", "2.4 Superseded fixes --------------------- 6.2.2.3-TIV-ITM_HMC_BASE-IF0003 6.2.2.3-TIV-ITM_HMC_BASE-IF0002 6.2.2.3-TIV-ITM_HMC_BASE-IF0001" ], [ "3bd", "2.5 APARs and defects included from superseded fixes --------------------------------------------------------------- 6.2.2.3-TIV-ITM_HMC_BASE-IF0003 --------------------------------- APAR: IV60709" ], [ "3be", "Abstract: NO CPU DATA WHEN HMC TIME ZONE IS SET TO BST" ], [ "3bf", "Additional information: If the Hardware Management Console (HMC)" ], [ "3bg", "time zone is set to BST, data might not be collected." ], [ "3bh", "The data provider might use the incorrect time zone" ], [ "3bi", "because BST can represent more than one time zone, for" ], [ "3bj", "example, British Summer Time and Bangladesh Standard Time." ], [ "3bk", "When the data provider sends the commands to the" ], [ "3bl", "HMC to collect the CPU data, the start and stop times of" ], [ "3bm", "the commands might not be correct and might not receive any data." ], [ "3bn", "Also, data might be collected, but for the" ], [ "3bo", "wrong time frame. 6.2.2.3-TIV-ITM_HMC_BASE-IF0002 --------------------------------- Feature: 208626" ], [ "3bp", "Abstract: LPAR Memory Attributes" ], [ "3bq", "Additional information: The following new attributes are added in" ], [ "3br", "the Server LPARs attribute group:" ], [ "3bs", "Current_Memory - The current amount of memory, in megabytes," ], [ "3bt", "configured for the LPAR." ], [ "3bu", "Warehouse name: CM0" ], [ "3bv", "Running_Memory - The amount of memory, in megabytes, varied on-line" ], [ "3bw", "by the LPAR." ], [ "3bx", "Warehouse name: RM" ], [ "3by", "In order to display these new attributes in the Tivoli Enterprise" ], [ "3bz", "Portal, use the Query Editor and select Server LPARs_V9 under" ], [ "3ca", "KPH SERVER LPARS. 6.2.2.3-TIV-ITM_HMC_BASE-IF0001 --------------------------------- APAR: IV47101" ], [ "3cb", "Abstract: NO CPU DATA DUE TO TIME OUTS ON HMC SSH CALLS" ], [ "3cc", "Additional information: In large environments, where there are more" ], [ "3cd", "than 150 LPARs on a server, the CPU Units used and CPU" ], [ "3ce", "Used Pct might display \"Not Collected.\" The" ], [ "3cf", "kph_data_provider_<instance>_0.log displays the following message: --" ], [ "3cg", "SEVERE: SSHCommandExecutor.call: Timed out while waiting" ], [ "3ch", "for `lslparutil -m \"<server>\" -r \"lpar\" -s s -F 'lpar_id|time|time_cycles | entitled_cycles|capped_cycles|uncapped_cycles| idle_cycles' -- APAR: IV50134" ], [ "3ci", "Abstract: NO CPU DATA WHEN HMC TIME SET TO GMT FORMAT" ], [ "3cj", "Additional information: If the HMC time zone is set to a GMT format," ], [ "3ck", "for example, GMT-08:00, CPU data might not be collected" ], [ "3cl", "because the data provider does not recognize the GMT" ], [ "3cm", "format and will default to using the local time zone." ], [ "3cn", "When the data provider sends the commands to the HMC to" ], [ "3co", "collect the CPU data, the start and stop times of the" ], [ "3cp", "commands might not be correct and might not receive any data." ], [ "3cq", "It is also possible that data will be collected," ], [ "3cr", "but for the wrong time frame. APAR: IV50135" ], [ "3cs", "Abstract: NO DATA IN MEMORY AND PAGING SPACE VIEW" ], [ "3ct", "Additional information: The System workspace might not display any" ], [ "3cu", "data in the Memory and Paging Space views. This can" ], [ "3cv", "happen when the HMC commands: ---" ], [ "3cw", "monhmc -r swap -n 0" ], [ "3cx", "monhmc -r mem -n 0 ---" ], [ "3cy", "return data in M bytes instead of k bytes: ---" ], [ "3cz", "Swap: 1992M total, 0M used, 1992M free, 2853M cached" ], [ "3da", "Mem: 24336M total, 4534M used, 19801M free, 480M buffers --- APAR: IV50686" ], [ "3db", "Abstract: NO CPU DATA IN NON-ENGLISH LOCALE" ], [ "3dc", "Additional information: When the agent runs in a non-English locale," ], [ "3dd", "attributes \"CPU Units Used\" and \"CPU Used Pct\" might" ], [ "3de", "display as \"Not Collected\" due to a Java problem. The" ], [ "3df", "kph_data_provider_0.log will have a message similar to this: --- WARNING: ManagementConsoleInventoryItemBuilder$BasicDataCommand." ], [ "3dg", "processResult: An error occurred while parsing the N2 date" ], [ "3dh", "field \"Fri Sep 27 11:35:31 JST 2013\". Continuing. --- 2.2 Defects --------------- Defect: 207939" ], [ "3di", "Abstract: Java CPCI - deadlock due to bad lock usage in some versions" ], [ "3dj", "of Java runtime" ], [ "3dk", "Additional information: Classloading and resource loading might get" ], [ "3dl", "locks in the wrong order, due to Java APAR IZ96933," ], [ "3dm", "causing the data provider to stop collecting data. This" ], [ "3dn", "fix prevents the problem no matter what version of Java is running. Defect: 208541" ], [ "3do", "Abstract: Add log messages to show data sent to kphagent" ], [ "3dp", "Additional information: At log level of FINEST, show the contents of" ], [ "3dq", "the rows of data sent from the data provider to the kphagent process." ], [ "3dr", "3.0 Architecture and prerequisites ======================" ], [ "3ds", "This fix is supported on all operating systems listed in the" ], [ "3dt", "IBM Tivoli Monitoring: HMC Base Agent User's Guide, version 6.2.2.3." ], [ "3du", "Please refer to the IBM Software Product Compatability Reports (SPCR)" ], [ "3dv", "for the latest operating system certification information: http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]" ], [ "3dw", "3.1 Prerequisites for this fix --------------------------------" ], [ "3dx", "The prerequisite level for this fix is as follows:" ], [ "3dy", "IBM Tivoli Monitoring: HMC Base Agent, Version 6.2.2 Interim" ], [ "3dz", "Feature 3, which is available from PassPort Advantage under the following eAssembly:" ], [ "3ea", "IBM Tivoli Monitoring for System p V6.2.2 Interim Feature 3, English" ], [ "3eb", "(CIH93EN) (Both agent and support files are included in this one package)" ], [ "3ec", "IBM Tivoli Monitoring for System p V6.2.2 Interim Feature 3, Language" ], [ "3ed", "Support, Multiplatform, Multilingual (CIH94ML)" ], [ "3ee", "For details, see the Troubleshooting Wiki: https://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]" ], [ "3ef", "As this fix is cumulative, it can be installed on any fix level for" ], [ "3eg", "this version, release, and mod level above the prerequisite." ], [ "3eh", "4.0 Image directory contents ===================" ], [ "3ei", "This fix image contains the following files:" ], [ "3ej", "- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004.README - This README file" ], [ "3ek", "- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004.tar - Fix archive .tar format" ], [ "3el", "- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004.zip - Fix archive .zip format." ], [ "3em", "Note: The .tar and .zip files are identical in content." ], [ "3en", "Use the .tar" ], [ "3eo", "file if you are working in a UNIX(R) environment; use the .zip file if" ], [ "3ep", "you are working in a Windows(R) environment." ], [ "3eq", "The fix archive file contains the following files: - 6.2.2.3-TIV-ITM_HMC_BASE-IF0004/kphaix526.dsc - 6.2.2.3-TIV-ITM_HMC_BASE-IF0004/kph_aix526_tema_if0004.tar - 6.2.2.3-TIV-ITM_HMC_BASE-IF0004/ph_dd.properties - 6.2.2.3-TIV-ITM_HMC_BASE-IF0004/ph_dd_062203004.xml - 6.2.2.2-TIV-ITM_HMC_BASE-IF0004/kpk_tems_teps_tepd_if0004.tar - 6.2.2.2-TIV-ITM_HMC_BASE-IF0004/kpk_tems_teps_tepd_if0004.zip" ], [ "3er", "5.0 Installation instructions ==================" ], [ "3es", "This fix can only be installed over an existing installation. Use" ], [ "3et", "the following steps to install this fix." ], [ "3eu", "5.1 Before installing the fix ------------------------------" ], [ "3ev", "- The prerequisites listed under section 3.1 entitled 'Prerequisites" ], [ "3ew", "for this fix' must be installed before this fix can be installed." ], [ "3ex", "- For the purpose of this README, the symbol <CANDLEHOME> is the" ], [ "3ey", "IBM Tivoli Monitoring installation directory." ], [ "3ez", "The default value" ], [ "3fa", "for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\\IBM\\ITM'" ], [ "3fb", "on Windows systems." ], [ "3fc", "Before installing this fix on UNIX systems, set the environment" ], [ "3fd", "variable CANDLEHOME to the IBM Tivoli Monitoring installation directory. For example: > CANDLEHOME=/opt/IBM/ITM" ], [ "3fe", "> export CANDLEHOME" ], [ "3ff", "- Because there is no uninstall utility for this fix, make sure to" ], [ "3fg", "perform a backup of your environment before installing this fix." ], [ "3fh", "5.2 Local agent update -------------------------- 1." ], [ "3fi", "Transfer the appropriate archive file" ], [ "3fj", "(6.2.2.3-TIV-ITM_HMC_BASE-IF0004.tar or .zip) to a temporary" ], [ "3fk", "directory on the system that contains the agent code to be updated." ], [ "3fl", "For the purpose of this README, the symbol <TEMP>" ], [ "3fm", "represents the fully qualified path to this directory. Note: On" ], [ "3fn", "Windows systems, this path includes the drive letter. 2." ], [ "3fo", "Expand the archive file using the \"tar\" command on UNIX systems or" ], [ "3fp", "an extract utility on Windows systems." ], [ "3fq", "This step creates a" ], [ "3fr", "directory structure that contains fixes for all of the supported platforms. 3." ], [ "3fs", "Use the \"itmpatch\" command to install the fix for the operating" ], [ "3ft", "system for that agent." ], [ "3fu", "For more information on the \"itmpatch\"" ], [ "3fv", "command, see section 6.2." ], [ "3fw", "On UNIX systems, if the fix was expanded to" ], [ "3fx", "<TEMP>/6.2.2.3-TIV-ITM_HMC_BASE-IF0004, the install command is:" ], [ "3fy", "> itmpatch -h <CANDLEHOME> -i <TEMP>/6.2.2.3-TIV-ITM_HMC_BASE-IF0004/kph_aix526_tema_if0004.tar" ], [ "3fz", "5.3 Remote agent update ---------------------------- 1." ], [ "3ga", "Transfer the appropriate archive file" ], [ "3gb", "(6.2.2.3-TIV-ITM_HMC_BASE-IF0004.tar or .zip) to a temporary" ], [ "3gc", "directory on the IBM Tivoli Enterprise Monitoring Server system." ], [ "3gd", "For the purpose of this README, the symbol <TEMP> represents the" ], [ "3ge", "fully qualified path to this directory." ], [ "3gf", "Note: On Windows systems," ], [ "3gg", "this path includes the drive letter. 2." ], [ "3gh", "Expand the archive file using the \"tar\" command on UNIX systems or" ], [ "3gi", "an extract utility on Windows systems." ], [ "3gj", "This step creates a" ], [ "3gk", "directory structure that contains fixes for all of the supported platforms. 3." ], [ "3gl", "To add the agent fix bundles into the remote deploy depot, use the" ], [ "3gm", "\"tacmd addBundles\" command found in $CANDLEHOME/bin on UNIX systems" ], [ "3gn", "or in %CANDLE_HOME%\\bin on Windows systems." ], [ "3go", "For more information" ], [ "3gp", "on the \"tacmd addBundles\" command, see the IBM Tivoli Monitoring Administrator's Guide." ], [ "3gq", "On UNIX systems," ], [ "3gr", "if the fix was expanded to <TEMP>/6.2.2.3-TIV-ITM_HMC_BASE-IF0004:" ], [ "3gs", "> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.2.3-TIV-ITM_HMC_BASE-IF0004" ], [ "3gt", "On Windows systems," ], [ "3gu", "if the fix was expanded to <TEMP>\\6.2.2.3-TIV-ITM_HMC_BASE-IF0004:" ], [ "3gv", "> %CANDLE_HOME%\\bin\\tacmd addBundles -n -i <TEMP>\\6.2.2.3-TIV-ITM_HMC_BASE-IF0004 where:" ], [ "3gw", "-n indicates that prerequisite bundles are not automatically added." ], [ "3gx", "The -n parameter must be used because the fix" ], [ "3gy", "directory does not contain any prerequisites that the fix might require." ], [ "3gz", "Please see Section 3.1 for the prerequisites" ], [ "3ha", "for this fix." ], [ "3hb", "-i is the directory that contains the deployment bundles to be" ], [ "3hc", "added to the depot. 4." ], [ "3hd", "To log in to the Tivoli Enterprise Monitoring server, and deploy" ], [ "3he", "the fix to the appropriate nodes where the agent is running, use" ], [ "3hf", "the following \"tacmd\" commands." ], [ "3hg", "For more information on the" ], [ "3hh", "\"tacmd login\" and \"tacmd updateAgent\" commands, see the IBM Tivoli" ], [ "3hi", "Monitoring Administrator's Guide." ], [ "3hj", "On UNIX systems:" ], [ "3hk", "> $CANDLEHOME/bin/tacmd login -s <server> -u <itmuser> -p <password>" ], [ "3hl", "> $CANDLEHOME/bin/tacmd listSystems" ], [ "3hm", "The output shows the Managed System Name for the OS agent on the" ], [ "3hn", "remote system to be updated." ], [ "3ho", "Use this value as the target of the" ], [ "3hp", "\"tacmd updateAgent\" command." ], [ "3hq", "> $CANDLEHOME/bin/tacmd updateAgent -t ph" ], [ "3hr", "-n <Managed system name> -v 062203004" ], [ "3hs", "On Windows systems:" ], [ "3ht", "> %CANDLE_HOME%\\bin\\tacmd login -s <server> -u <itmuser> -p <password>" ], [ "3hu", "> %CANDLE_HOME%\\bin\\tacmd listSystems" ], [ "3hv", "The output shows the Managed System Name for the OS agent on the" ], [ "3hw", "remote system to be updated." ], [ "3hx", "Use this value as the target of the" ], [ "3hy", "\"tacmd updateAgent\" command." ], [ "3hz", "> %CANDLE_HOME%\\bin\\tacmd updateAgent -t PH" ], [ "3ia", "-n <Managed system name> -v 062203004 Note:" ], [ "3ib", "- The component (-t) for the \"tacmd updateAgent\" command is" ], [ "3ic", "specified as two characters (PH), not three characters (KPH)." ], [ "3id", "- The node (-n) for the \"tacmd updateAgent\" command is the managed" ], [ "3ie", "system name of the operating system (OS) agent to be updated." ], [ "3if", "The target node for the \"tacmd updateAgent\" command is always" ], [ "3ig", "an OS agent." ], [ "3ih", "5.4 Agent support update ------------------------------" ], [ "3ii", "This fix 6.2.2.2-TIV-ITM_HMC_BASE-IF0004 includes changes to the agent" ], [ "3ij", "support files which need to be installed." ], [ "3ik", "Use the following steps to" ], [ "3il", "update the Tivoli Enterprise Monitoring Server, Tivoli Enterprise" ], [ "3im", "Portal Server, or Tivoli Enterprise Portal Desktop. 1." ], [ "3in", "Transfer the appropriate archive file" ], [ "3io", "(6.2.2.2-TIV-ITM_HMC_BASE-IF0004.tar or .zip) to the Tivoli" ], [ "3ip", "Enterprise Monitoring Servers, Tivoli Enterprise Portal Servers," ], [ "3iq", "or Tivoli Enterprise Portal Desktops. 2." ], [ "3ir", "Expand the archive file using the \"tar\" command on UNIX systems" ], [ "3is", "or an extract utility on Windows systems." ], [ "3it", "This step creates a" ], [ "3iu", "directory structure that contains fixes for all of the supported platforms. 3." ], [ "3iv", "Expand the archive file (kph_tems_teps_tepd_if0004.tar or .zip)" ], [ "3iw", "that contains the updates for Tivoli Enterprise Monitoring Server," ], [ "3ix", "Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal" ], [ "3iy", "Desktop using the \"tar\" command on UNIX systems or an extract" ], [ "3iz", "utility on Windows systems." ], [ "3ja", "This step creates a directory" ], [ "3jb", "structure that includes a subdirectory called CD-ROM, with the necessary updates. 4." ], [ "3jc", "Use the Application Support Installer(ASI) GUI or the silent" ], [ "3jd", "installation method to install the application support files." ], [ "3je", "Note: For IBM Tivoli Monitoring Version 6.3 or above, one" ], [ "3jf", "of the following additional steps must be performed. 1." ], [ "3jg", "Acquire a platform-specific pre-packaged JRE version" ], [ "3jh", "of the Application Support Installer (ASI). See IBM" ], [ "3ji", "Tivoli Monitoring Application Support Installer, 6.2-tiv-itm_asi-if0003 at http://www.ibm.com/support/docview.wss?uid=swg24034924 [http://www.ibm.com/support/docview.wss?uid=swg24034924]" ], [ "3jj", "for download and installation instructions." ], [ "3jk", "-- OR -- 2." ], [ "3jl", "Specify the '-j javahome' parameter with the path to" ], [ "3jm", "a Java(r) 1.5 or java 1.6 installation when running" ], [ "3jn", "the itmasi.sh or itmasi.bat script described below." ], [ "3jo", "GUI installation option ------------------------" ], [ "3jp", "The GUI can be started by using one of the following commands" ], [ "3jq", "from within the CD-ROM directory where setup.jar is located." ], [ "3jr", "On UNIX systems:" ], [ "3js", "> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]" ], [ "3jt", "On Windows systems:" ], [ "3ju", "> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]" ], [ "3jv", "When prompted by the Application Support Installer for the" ], [ "3jw", "installable media directory, select the CD-ROM directory, not the component directory." ], [ "3jx", "The installer can install updates for" ], [ "3jy", "multiple components at the same time." ], [ "3jz", "Silent installation option --------------------------" ], [ "3ka", "To use the silent installation option, use one of the following" ], [ "3kb", "commands from within the CD-ROM directory where setup.jar is located." ], [ "3kc", "Note: Using the silent installation option for Linux and zLinux" ], [ "3kd", "operating systems requires the following files contained in" ], [ "3ke", "interim fix 6.2-TIV-ITM_ASI-IF0001:" ], [ "3kf", "- Linux: setupLinux.bin" ], [ "3kg", "- zLinux: setupLinux390.bin" ], [ "3kh", "Follow the installation instructions contained in the \"6.2-TIV-ITM_ASI-IF0001.README\"." ], [ "3ki", "On UNIX systems:" ], [ "3kj", "> ./itmasi.sh -h <CANDLEHOME>[-silent]" ], [ "3kk", "[-r <response file>] [-j <JAVAHOME>]" ], [ "3kl", "On Windows systems:" ], [ "3km", "> itmasi -h <CANDLEHOME> [-silent]" ], [ "3kn", "[-r <response file>] [-j <JAVAHOME>] where:" ], [ "3ko", "-h <CANDLEHOME> - Required." ], [ "3kp", "The path to the IBM Tivoli" ], [ "3kq", "Monitoring installation directory." ], [ "3kr", "-r <response file> - Optional." ], [ "3ks", "Customized response file name." ], [ "3kt", "The default response file \"response.txt\" in" ], [ "3ku", "the CD-ROM directory can be copied and modified" ], [ "3kv", "for your environment." ], [ "3kw", "Do not update \"response.txt\"." ], [ "3kx", "-j <JAVAHOME> - Optional." ], [ "3ky", "The fully-qualified path to the \"bin\"" ], [ "3kz", "directory where Java(R) is installed. The" ], [ "3la", "location of Java on your system might vary. 5." ], [ "3lb", "The next panel presented by the Application Support Installer asks" ], [ "3lc", "for the selection of which Tivoli Monitoring components you want" ], [ "3ld", "to add application support to." ], [ "3le", "For this fix, check or clear the" ], [ "3lf", "check boxes as follows:" ], [ "3lg", "checked - Tivoli Enterprise Monitoring Server (TEMS)" ], [ "3lh", "checked - Tivoli Enterprise Portal Server (TEPS)" ], [ "3li", "checked - Tivoli Enterprise Desktop Client (TEPD)" ], [ "3lj", "Continue through the remaining GUI panels selecting the HMC Base" ], [ "3lk", "06.22.03.04 support to complete the installation. 6." ], [ "3ll", "If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal" ], [ "3lm", "Browser was running when the update was installed, it must be restarted." ], [ "3ln", "6.0 Additional installation information ========================" ], [ "3lo", "For additional troubleshooting installation information, see the" ], [ "3lp", "itmpatch.log in the patchlogs directory in <CANDLEHOME>." ], [ "3lq", "6.1 Installation instructions for agent baroc file -----------------------------------------------------" ], [ "3lr", "This fix 6.2.2.2-TIV-ITM_HMC_BASE-IF0004 includes changes to the" ], [ "3ls", "agent baroc files that must be installed." ], [ "3lt", "Refer to IBM Tivoli" ], [ "3lu", "Monitoring Installation and Setup Guide under \"Installing monitoring" ], [ "3lv", "agent baroc files on the event server\" in \"Installing the IBM Tivoli" ], [ "3lw", "Enterprise Console Event Synchronization\" section for more information." ], [ "3lx", "6.2 Additional information on using \"itmpatch\" command --------------------------------------------------------------" ], [ "3ly", "The \"itmpatch\" command has the following syntax:" ], [ "3lz", "Usage: itmpatch -h <installation home> [OPTIONS]" ], [ "3ma", "itmpatch -h <installation home>" ], [ "3mb", "-t { <patch_file_directory> | <patch_file> }" ], [ "3mc", "itmpatch -h <installation home>" ], [ "3md", "-i { <patch_file_directory> | <patch_file> } where:" ], [ "3me", "-h Specifies the IBM Tivoli Monitoring installation directory" ], [ "3mf", "-i Specifies the path to the directory or patch file to be installed" ], [ "3mg", "-t Generates a report of the actions to be taken by the patch" ], [ "3mh", "For example, on UNIX systems:" ], [ "3mi", "- To preview the fix installation, use the \"-t\" option:" ], [ "3mj", "> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>" ], [ "3mk", "- To install the fix, use the \"-i\" option:" ], [ "3ml", "> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP> where:" ], [ "3mm", "<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring installation directory." ], [ "3mn", "On Windows systems, this path must include" ], [ "3mo", "the drive letter." ], [ "3mp", "<TEMP> represents the fully qualified directory specification where" ], [ "3mq", "the fix is located." ], [ "3mr", "On Windows systems, this must include the drive letter." ], [ "3ms", "6.3 Verifying the update ---------------------------- 1." ], [ "3mt", "To verify the agent was updated correctly, use the \"tacmd\" command" ], [ "3mu", "to view the agent's current version after the agent is restarted." ], [ "3mv", "You are required to log in to a Tivoli Enterprise Monitoring" ], [ "3mw", "Server prior to viewing the agent version. For example:" ], [ "3mx", "On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring" ], [ "3my", "installation directory, the default location is '/opt/IBM/ITM'." ], [ "3mz", "> $CANDLEHOME/bin/tacmd login -s <server> -u <itmuser> -p <password>" ], [ "3na", "> $CANDLEHOME/bin/tacmd listSystems -t PH" ], [ "3nb", "On Windows systems, where %CANDLE_HOME% is the IBM Tivoli" ], [ "3nc", "Monitoring installation directory, the default location is 'C:\\IBM\\ITM'." ], [ "3nd", "> %CANDLE_HOME%\\bin\\tacmd login -s <server> -u <itmuser> -p <password>" ], [ "3ne", "> %CANDLE_HOME%\\bin\\tacmd listSystems -t PH" ], [ "3nf", "Note: The component (-t) for the \"tacmd listSystems\" command is" ], [ "3ng", "specified as two characters (PH), not three characters (KPH)." ], [ "3nh", "When the agent update is successful, the agent version is: 06.22.03.04. 2." ], [ "3ni", "To verify the agent support files were updated correctly, use the" ], [ "3nj", "\"kincinfo\" command on Windows systems or the \"cinfo\" command on" ], [ "3nk", "Linux or UNIX systems." ], [ "3nl", "The sample output below shows the versions" ], [ "3nm", "of the Tivoli Enterprise Portal Server, Tivoli Enterprise" ], [ "3nn", "Monitoring Server, or Tivoli Enterprise Portal Desktop systems" ], [ "3no", "after this fix has been successfully applied." ], [ "3np", "Note: The displayed date of the build might not be accurate. This" ], [ "3nq", "is a known problem." ], [ "3nr", "On UNIX or Linux systems: -------------------------" ], [ "3ns", "To validate that all components have been installed, run the following command: ./cinfo -i" ], [ "3nt", "*********** Thu Oct 7 13:57:24 CST 2015 ******************" ], [ "3nu", "User: root Groups: system bin sys security cron audit lp" ], [ "3nv", "Host name : <hostname> Installer Lvl:06.30.02.00 CandleHome: /opt/IBM/ITM *********************************************************** ...Product inventory . . ." ], [ "3nw", "ph Monitoring Agent for HMC Base" ], [ "3nx", "tms Version: 06.22.03.04" ], [ "3ny", "tps Version: 06.22.03.04" ], [ "3nz", "tpw Version: 06.22.03.00 . . ." ], [ "3oa", "On Windows systems: ---------------------" ], [ "3ob", "To validate that all components have been installed, run the following command: For example:" ], [ "3oc", "> %CANDLE_HOME%\\InstallITM\\kincinfo -i" ], [ "3od", "{Add your sample output here}" ], [ "3oe", "*********** Thu Oct 7 16:03:55 Eastern Standard Time 2015 **********" ], [ "3of", "User : Administrator Group : NA" ], [ "3og", "Host Name : <hostname> Installer: Ver: 062204000 CandleHome: C:\\IBM\\ITM Installitm: C:\\IBM\\ITM\\InstallITM ********************************************************************* . . ." ], [ "3oh", "PH Monitoring Agent for HMC Base Support" ], [ "3oi", "WINNT Version: 06.22.03.04 Build: 201510070000" ], [ "3oj", "PH Monitoring Agent for HMC Base Support" ], [ "3ok", "WINNT Version: 06.22.03.04 Build: 201510070000" ], [ "3ol", "PH Monitoring Agent for HMC Base Support" ], [ "3om", "WINNT Version: 06.22.03.04 Build: 201510070000 . . ." ], [ "3on", "7.0 Known problems and workarounds ========================= None." ], [ "3oo", "8.0 Additional product information ====================== None." ], [ "3op", "9.0 Copyright and trademark information ==================================" ], [ "3oq", "A current list of IBM trademarks is available on the Web at \"Copyright" ], [ "3or", "and trademark information\" at www.ibm.com/legal/copytrade.shtml. 10.0 Notices =======" ], [ "3os", "INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION" ], [ "3ot", "\"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED," ], [ "3ou", "INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF" ], [ "3ov", "NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." ], [ "3ow", "Some jurisdictions do not allow disclaimer of express or implied" ], [ "3ox", "warranties in certain transactions, therefore, this statement may not" ], [ "3oy", "apply to you." ], [ "3oz", "This information could include technical inaccuracies or typographical errors." ], [ "3pa", "Changes are periodically made to the information herein; these" ], [ "3pb", "changes will be incorporated in new editions of the publication. IBM" ], [ "3pc", "may make improvements and/or changes in the product(s) and/or the" ], [ "3pd", "program(s) described in this publication at any time without notice." ], [ "3pe", "Microsoft, Windows, and Windows Server are trademarks of Microsoft" ], [ "3pf", "Corporation in the United States, other countries, or both." ], [ "3pg", "Java and all Java-based trademarks are trademarks of Sun Microsystems," ], [ "3ph", "Inc. in the United States, other countries, or both." ], [ "3pi", "UNIX is a registered trademark of The Open Group in the United States" ], [ "3pj", "and other countries." ], [ "3pk", "Other company, product, or service names may be trademarks or service" ], [ "3pl", "marks of others." ], [ "3pm", "Third-Party License Terms and Conditions, Notices and Information -----------------------------------------------------------------" ], [ "3pn", "The license agreement for this product refers you to this file for" ], [ "3po", "details concerning terms and conditions applicable to third party" ], [ "3pp", "software code included in this product, and for certain notices and" ], [ "3pq", "other information IBM must provide to you under its license to" ], [ "3pr", "certain software code." ], [ "3ps", "The relevant terms and conditions, notices and" ], [ "3pt", "other information are provided or referenced below." ], [ "3pu", "Please note that" ], [ "3pv", "any non-English version of the licenses below is unofficial and is" ], [ "3pw", "provided to you for your convenience only." ], [ "3px", "The English version of the" ], [ "3py", "licenses below, provided as part of the English version of this file," ], [ "3pz", "is the official version." ], [ "3qa", "Notwithstanding the terms and conditions of any other agreement you" ], [ "3qb", "may have with IBM or any of its related or affiliated entities" ], [ "3qc", "(collectively \"IBM\"), the third party software code identified below" ], [ "3qd", "are \"Excluded Components\" and are subject to the following terms and conditions:" ], [ "3qe", "- the Excluded Components are provided on an \"AS IS\" basis" ], [ "3qf", "- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND" ], [ "3qg", "CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT" ], [ "3qh", "NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE" ], [ "3qi", "AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND" ], [ "3qj", "FITNESS FOR A PARTICULAR PURPOSE" ], [ "3qk", "- IBM will not be liable to you or indemnify you for any claims" ], [ "3ql", "related to the Excluded Components" ], [ "3qm", "- IBM will not be liable for any direct, indirect, incidental," ], [ "3qn", "special, exemplary, punitive or consequential damages with respect" ], [ "3qo", "to the Excluded Components. PREREQUISITES" ], [ "3qp", "IBM Tivoli Monitoring: HMC Base Agent, Version 6.2.2 Interim Feature 3 INSTALLATION INSTRUCTIONS" ], [ "3qq", "Please refer to the README contained in the Description section above for general installation instructions. DOWNLOAD PACKAGE" ], [ "3qr", "Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options" ], [ "3qs", "What is Fix Central(FC)?" ], [ "3qt", "[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] [ ] PRODUCT ALIAS/SYNONYM" ], [ "3qu", " HMC Agent" ], [ "3qv", "Monitoring Agent for System P" ], [ "3qw", "System P Agent" ], [ "3qx", " [/support/docview.wss?uid=swg24042283&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24042283&aid=2]Problems (APARS) fixed" ], [ "3qy", "IV47101, IV50134, IV50135, IV50686, IV60709, IV67769" ] ]

[ "3br", "3bs", "3bt", "3bu", "3bv", "3bw", "3bx" ]

[ "SIB SIBus SIBDestHandler DOWNLOADABLE FILES\n\nABSTRACT\n A tool to view, move, copy, delete, save and restore messages in the default messaging provider for IBM WebSphere Application Server version 6.0 and later. \n\nDOWNLOAD DESCRIPTION\nThe IBM Service Integration Bus Destination Handler tool provides a flexible interface to perform a range of different actions on messages, which would otherwise require custom coding, or a number of separate and time consuming manual steps. \n\nActions can be run once to perform an individual task, or the tool can be deployed as a WebSphere Application Server scheduler task to regularly check the contents of an exception destination and provide appropriate handling of messages based on the set of rules configured.\n\nA graphical user interface (GUI) is provided to perform actions interactively and create configuration files. The GUI also provides facilities to send test messages to queues or topics. Screenshot below.\nIBM Service Integration Bus Destination Handler GUI screenshot [/support/docview.wss?uid=swg24021439&aid=1] [/support/docview.wss?uid=swg24021439&aid=1]\n\nThe actions which can be performed upon a message by the tool include:\n- Printing out the properties and body of messages in a readable form\n- Moving messages to a different queue point\n- Copying messages to a another destination\n- Deleting messages from a queue point or subscription\n- Resubmitting messages from an exception destination back to the exception problem destination\n- Saving binary copies of messages to files\n- Restoring messages from files to destinations\n- Sending e-mails to administrators containing details of messages\n\nThe actions can be performed on all messages on a particular destination, or on a subset of those messages. Messages can be selected based on JMS headers. Messages containing text can be selected based on their contents, including XPath selection for messages containing XML formatted data.\n\nPossible uses\n- Gathering a snapshot of the contents of a queue to send to an application developer, or IBM customer support for investigation\n- Searching the contents of a queue for an individual message or group of messages\n- Examining the contents of a message which cannot be processed by an application\n- Handling a case where a message has been sent to the wrong queue point\n- Moving messages from a queue point where no application is available to consume them\n- Moving messages to a different bus\n- Moving messages that can never be processed from an exception destination to a permanent failure destination\n- Resubmitting messages from an exception destination after restarting a database or other system required to process them\n- Copying messages from a production bus to a test bus for investigation\n- Creating a copy of a set of JMS messages sent by an application to use multiple times in testing\n- Loading a set of JMS messages from disk onto a destination as the input for a test\n- Configuring an exception destination handler to inform an administrator when certain conditions occur\n\ndeveloperWorks forum\n\nThe following forum topic on developerWorks exists as a place to discuss the tool:\nIBM Service Integration Bus Destination Handler - Q&A [https://www.ibm.com/developerworks/community/forums/html/topic?id=6a8691d9-d72f-4aaa-bf52-a670ee1fe8b2]\n\nSkill level required\nExperience of using the default messaging provider for WebSphere Application Server.\n\nThis includes use for JMS messaging within applications, or as part of the runtime of another product such as IBM WebSphere Process Server or IBM WebSphere Business Monitor.\n\nNew in this release\nVersion 1.1.6:\n- Browsing messages larger than 1024b via a JMXConnection\nVersion 1.1.5:\n- Viewing messages queued for delivery on Service Integration Bus links\n- Body-based selection of messages for administrative (JMX) connections\n- Setting of property types on send message dialog\n- Minor bug fixes\nVersion 1.1.4:\n- Minor bug fixes\nVersion 1.1.3:\n- Bug fix: RawDumpAction created empty files for bytes messages\nVersion 1.1.2:\n- Graphical user interface\n- Matching of messages containing text data, including using XPath expressions\n- Viewing messages on remote queue and publication points\n- Masking passwords in configuration files\n- Limiting of the number messages a rule will match per run\n- A number of other minor improvements\nVersion 1.0.2:\n- Initial release\n\nDetails\nReleased: 23Dec08\nLast updated: 25Apr13\nCurrent Version: 1.1.5\n\nNote: The version number shown in the right-hand pane is the version of WebSphere Application Server this tool applies to. The date is the last web page refresh.\n\nINSTALLATION INSTRUCTIONS\nDownload and unzip the binary package. Follow the instructions contained in readme.html within the package.\n\nDOWNLOAD PACKAGE\n\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is DD? [http://www6.software.ibm.com/dldirector/doc/DDfaq_en.html] sib.desthandler.1.1.6.zip 25 Apr 2013 English 2055517 FTP [ftp://public.dhe.ibm.com/software/websphere/appserv/support/tools/sibdesthandler/sib.desthandler.1.1.6.zip] DD \nTECHNICAL SUPPORT\n This tool is 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 from IBM product service channels.\n\nYou can submit a question using the 'rate this page' below, or preferably by using the developerWorks forum listed in the description section above. A response is not guaranteed when using either route to submit your question.\n\nRead the license information contained within the zip file to determine if you want to use it. \n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Process Server SupportPac AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS 7.0, 6.1, 6.0.2 Business Integration WebSphere Business Monitor AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows, z/OS 7.5.1, 7.5, 7.0, 6.2, 6.1, 6.0.2 Application Servers WebSphere Application Server for z/OS z/OS 8.5, 8.0, 7.0, 6.1, 6.0 Business Integration WebSphere Enterprise Service Bus AIX, HP-UX, Linux, Linux zSeries, Windows, z/OS 7.5.1, 7.5, 7.0, 6.2 Business Integration IBM Business Process Manager Advanced AIX, Linux, Linux zSeries, Solaris, Windows, z/OS 8.5, 8.0, 7.5.1, 7.5", "wsst DOWNLOADABLE FILES\n\nABSTRACT\n This command-line Java™ tool checks for potential security vulnerabilities that are caused by improper or incorrect IBM WebSphere Application Server security configuration \n\nDOWNLOAD DESCRIPTION\nThe tool scans static security configuration files for WebSphere Application Server, WebSphere Application Server Express, and WebSphere Application Server Network Deployment Versions 7.0, 6.1, 6.0, 5.1 and 5.0 to look for potential vulnerabilities. This tool is not available for Version 8.0 and beyond.\n\nThe tool produces an HTML report that contains the following information: \n\n * The security configuration checks that were performed\n \n \n * The status of each check\n \n \n * A corrective action, if necessary\n \n \n * A link to the information center task that is related to the corrective action\n\n\nThe IBM WebSphere Developer Technical Journal article entitled, WebSphere Application Server V5.0 Advanced Security and System Hardening [http://www.ibm.com/developerworks/websphere/techjournal/0406_botzum/0406_botzum.html], identifies many of the security checks that are performed and explains why the checks are important. Although the article refers to WebSphere Application Server Version 5.0 and V5.1, the information applies to V6.0 as well. \n\nThe article entitled, WebSphere Application Server V6.1: What's new in security? [http://www.ibm.com/developerworks/websphere/library/techarticles/0606_botzum/0606_botzum.html], discusses the security features that are introduced and how security hardening has been addressed in V6.1. \n\nWhat the tool does not do: * Does not check for runtime penetration vulnerabilities\n \n \n * Is not a general purpose configuration diagnostic tool for WebSphere Application Server that is intended to aid in problem determination for configuration problems\n \n \n * Is not a fail safe guarantee that the system is totally secure\n \n \n * Does not do network, host, physical, or operating system security vulnerability analysis\n\n\nImportant note: This tool only can point out WebSphere Application Server configuration items which, if corrective action is taken, might improve the overall security of the WebSphere Application server. IBM does not make a claim or guarantee that the tool detects all of the possible security configuration issues. IBM also does not make a claim or guarantee that, if corrective action is taken for the items it does detect, the WebSphere Application Server system is completely secure from any or all possible threats. Consider network security, operating system security, and physical security in addition to WebSphere Application Server security. \n\nRelated information: \nUse the ACert tool [http://www.ibm.com/support/docview.wss?rs=180&uid=swg24006797] to check for out-of-date Secure Sockets Layer (SSL) certificates that are used by WebSphere Application Server. PREREQUISITES\nThe tool runs on the same system that is used to install WebSphere Application Server for versions 7.0, 6.1, 6.0, 5.1 and 5.0 only.\n\nINSTALLATION INSTRUCTIONS\nComplete the following steps to install the tool: \n\n 1. Place the wsst.zip file for WebSphere Application Server Version 5.x. and 6.0.x,wsst61.zip file for Version 6.1 or wsst70.zip file for Version 7.0 in any directory on the machine that has the WebSphere Application Server installation to be scanned. For example, you might create a security_scanner directory under the /usr/IBM/WebSphere/AppServer or C:\\Program Files\\WebSphere\\AppServer directory and place the compressed file in the directory. \n \n \n 2. Extract the wsst.zip, wsst61.zip, or wsst70.zip file. After extracting the file, a wsst, wsst61, or wsst70 directory is created.\n \n \n 3. Change the current directory to the wsst, wsst61, or wsst70 directory that is created after extracting the respective compressed file. \n \n \n 4. Edit the appropriate script file to replace the WAS_HOME variable with the path to your WebSphere Application Server installation. For example, you might change this variable to the C:\\WebSphere\\AppServer or /usr/IBM/WebSphere/AppServer directory on the same machine. \n \n The following list provides the script file names to run the tool on WebSphere Application Server Version 5.x and 6.0.x on different operating systems: * The Microsoft® Windows® operating systems: wsst.bat \n * The AIX, HP-UX, Linux®, Solaris, and z/OS operating systems: wsst.sh \n * The OS/400 operating system: wsstxx.qsh\n \n \n\n * \n * \n * The Microsoft Windows operating systems: wsst61.bat The AIX, HP-UX, Linux, Solaris, and z/OS operating systems: wsst61.sh The i5/OS operating system: wsst61.qsh \n * \n * \n * The Microsoft Windows operating system: wsst70.bat The AIX, HP-UX, Linux and Solaris operating systems: wsst70.sh The z/OS operating system: wsst70z.sh The IBM i operating system: wsst70.qsh \n\n\nNotes: * The following different scripts are provided for the i5/OS operating system in the wsst.zip file: * wsst50.qsh \n * wsst.51.qsh \n * wsst60.qsh\n \n \n The numbers in the script file names refer to the version number of WebSphere Application Server against which you are running the tool. For example, on the OS/400 operating system, edit the wsst50.qsh file to change the WAS_HOME variable to point to the /QIBM/ProdData/WebAS5/Base directory and run the tool against a WebSphere Application Server Version 5.0 installation.\n \n \n * On the z/OS operating system, you might have to convert the wsst.sh file from the ASCII format to the EBCDIC format and change the permission bits of the wsst.sh file to 755 to run the tool. \n \n \n * On the AIX, HP-UX, Linux, and Solaris operating systems after unzipping wsst.zip, run the chmod +x command to grant execute permission to the wsst.sh file.\n \n\nUse the tool \nFor WebSphere Application Server Versions 5.x and 6.0.x, run the appropriate script file on the command line from the same wsst directory that was created when you extracted the wsst.zip file. \n\nFor WebSphere Application Server version 6.1.x, run the appropriate script file on the command line from the same wsst61 directory that was created when you extracted the wsst61.zip file. \n\nFor WebSphere Application Server version 7.0.x, run the appropriate script file on the command line from the same wsst70 directory that was created when you extracted the wsst70.zip file. \n\nOn all operating systems, except on the OS/400 and i5/OS operating systems for WebSphere Application Server 5.x and 6.x respectively, the tool prompts for the WebSphere Application Server installation that you want to scan. Press Enter to scan the WebSphere Application Server installation that is referenced by the script or enter the path to another WebSphere Application Server installation on the same machine that you want to scan. \n\nMonitor and view the result \nThe tool displays the name of the WebSphere Application Server installation for V5.x or the WebSphere Application Server profile name for V6.x and V7.0.x that is scanned. The tool also displays the name of each security check that is running along with its status. For V5.x on the OS/400 operating system, the tool displays the WebSphere Application Server instance name. \n\nWhen the scans are completed, the tool generates a report in the host_name_ report_ date_ time.html format. Open the report in a browser window to view the result of the scan. DOWNLOAD PACKAGE\n\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is DD? [http://www6.software.ibm.com/dldirector/doc/DDfaq_en.html] Scan tool for WAS v5.x.x and v6.0.x 6/29/2005 US English 152830 FTP [ftp://public.dhe.ibm.com/software/websphere/appserv/support/tools/SecurityScanner/wsst.zip] DD Scan tool for WAS v6.1.x 8/29/2006 US English 158087 FTP [ftp://public.dhe.ibm.com/software/websphere/appserv/support/tools/SecurityScanner/wsst61.zip] DD Scan tool for WAS V7.0.x 6/30/2009 US English 1299420 FTP [ftp://public.dhe.ibm.com/software/websphere/appserv/support/tools/SecurityScanner/wsst70.zip] DD \nTECHNICAL SUPPORT\n This tool is provided \"as-is\". However, if you have questions about any WebSphere Application Server issues identified by this tool, you can contact IBM Support at 1-800-IBM-SERV (US calls only). \n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server for z/OS Security z/OS 7.0, 6.1, 6.0, 5.1 Application Servers Runtimes for Java Technology Java SDK Application Servers WebSphere Application Server - Express Security", "mustgatherdocument; IBM Forms; IBM Forms API; IBM Forms Server; troubleshooting; mustgather; support; documentation; wpf; wpf.pel; pel file; logs; log files; problem management record; PMR TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\n This document will aid in problem determination and save time resolving Problem Management Records (PMRs) for IBM Forms products. \n\nCollecting this data early, even before opening a PMR, helps IBM Support determine: \n\n * If symptoms match known problems (rediscovery) \n * If there is a non-defect problem that can be identified and resolved \n * The root cause, which can accelerate the development of a code fix\n\nRESOLVING THE PROBLEM\n\nA. Gather general information\nWhen working with IBM Support, every problem must have a corresponding problem management record (PMR) opened for it. There are several potential problem areas that will need to be investigated. The following is a list of products for which the Support Engineers will require specific version information.\n\n\n * WebSphere Application Server \n * WebSphere Portal Server \n * IBM Forms: \n * Viewer \n * Designer \n * Webform Server \n * API \n * Services Platform \n * Java version \n * Operating System and patch levels \n * Server \n * Client\n\n\nInclude the following general information: \n 1. Provide all software being used including all service packs. Note: If you do not know how to collect the version information for one of the products listed above, please refer to our collecting data technote titled. How to determine version information for IBM Forms [http://www.ibm.com/support/docview.wss?uid=swg21457001].\n \n 2. Provide hardware specifics (i.e. CPU, available hard dive space, memory, and so on)\n \n 3. Describe the problem in detail giving step by step instructions and screen shots to duplicate the issue. What is the error? How is it manifested (i.e. popups, server crash, and so on)\n \n 4. How often does the problem occur?\n \n 5. How many people are affected?\n \n 6. Provide the form and servlet/portlet application code experiencing the issue. Note: If a simplified application that is able to duplicate the issue and can be deployed without requiring outside resources is provided, this will cut down on investigation times.\n \n 7. What is the business impact that the issue is causing? What are your current time lines? When do you absolutely need this issue resolved by?\n \n 8. Provide an architectural overview of the server. Helpful when clustering and multiple servers are involved.\n \n 9. Additional contact information - phone number and e-mail address\n \n 10. Log files (see Step C)\n\n\nCOLLECTING DATA USING IBM SUPPORT ASSISTANT\n 1. Download ISA Lite [https://www-304.ibm.com/support/docview.wss?uid=swg24029414] and extract it to your WAS_HOME directory.\n \n \n 2. Start ISA Lite by running runISALite.[sh|bat].\n \n \n 3. Select the following collector: IBM Forms General Data Collection\n \n \n 4. Follow the prompts to automatically submit the collected data to IBM Support.\n 5. \n\nNote: Due to limited functionality of tool, ISA Lite will only collect logs for runtime issues. This tool currently is not able to collect logs generated by wpf.pel file or install specific issues. Please review section B and C of the 'Collecting data manually' section for further information. This functionality will be added in a later iteration of the tool.\n\nCOLLECTING DATA MANUALLY\nB. Gather debug information \n\n\nTo help IBM Support with its troubleshooting, take the following steps to create debug information:\n\nOn a Windows® system, create an empty text file in the C: directory or the user profile directory named wpf.pel. \n\nYou can confirm the user profile directory path by running the 'set USERPROFILE' command on the command line. \n\nMake sure the extension is .pel rather than .pel.txt. Re-run your application when this file exists. Note: We look for the pel file in the user profile directory first. \n\nIBM Forms generates log files first on the C: drive else the user profiles temp directory. \n\nYou can confirm the temp directory's location by running the 'set temp' command on the command line.\n\nWhen working with Viewer, a masqform.log will be generated. When working with Webform Server or the API, a java.log will be created. \n\nOn a Unix system, create an empty text file in the /etc directory or in the current working directory (Translator or custom application using Forms API). When this file exists, IBM Forms Server products will generate a debug.log in the current working directory.\n\nFor debugging signature issues, open the pel file in a text editor and add the word 'signmessage'. This will create signmessage-java-x.xml files in the same location as the pel file.\n\nFor debugging Webform Server issues, you can increase the debug log level to finest under Websphere's Admin Console;Troubleshooting -> Logs and trace -> TranslatorServer -> Change log detail levels and modify com.ibm.form.*. *=info is default log level.\n\nie. *=info: com.ibm.form.*=finest\n\nNote: For SharedFileCache issues (database out of sync, Cache locking), you may want to refine your tracing to:\n\n*=info: com.ibm.form.webform.logging.facility.fom.*=FINE: \n\ncom.ibm.form.webform.logging.facility.fom.FormInstances=FINEST\n\nNote: For debugging issues where you need to log all activity between your front end application that extends our framework and the translator, you may want to refine your tracing under the server you have deployed your application (ie. server1) to:\n\n*=info: com.ibm.form.webform.framework.*=FINEST\n\nC. Gather log files \n\nViewer \n\n1. See section B \n\nDesigner \n\n1. .log file under C:\\Documents and Settings\\Administrator\\workspace\\.metadata if a runtime error is encountered. \n\n2. Core and javacore files in C:\\Program Files\\IBM\\Lotus Forms\\Designer\\4.0\\platform\\eclipse if Designer experiences a crash. \n\nWebform Server \n\nInstall issues \n\nWhen running into an install/uninstall issue, please provide the following logs \n\nIf the install does not let you select the finish button in the install process, please provide the following logs: \n\nWindows: \nC:\\Documents and Settings\\ <user>\\Local Settings\\Temp\\FormsServerInstall-xx.log \nC:\\Documents and Settings\\ <user>\\Local Settings\\Temp\\FormsServerUninstall-xx.log \n\nUnix: \n<System Temp dir>/FormsServerInstall-xx.log \n<System Temp dir>/FormsServerUninstall-xx.log \n\nIf the install/uninstall finishes with serious errors, please provide the following zip file: \n\n<IBM Forms Install Dir>\\Server\\4.0\\logs.zip \n\nRuntime issues \n\nSee section B \n\nZip the WebSphere Application Server logs folder \n\n<WebSphere Install Dir>\\AppServer\\profiles\\ <profileName>\\logs \n\nWebSphere Portal logs \n\n<WebSphere Install Dir>\\PortalServer\\log \n<WebSphere Install Dir>\\AppServer\\profiles\\ <profileName>\\logs\\ffdc \n<WebSphere Install Dir>\\AppServer\\logs \n\n<IBM Forms Install Dir>\\Translator\\translator.properties \n\nAPI \n\nSee section B \n\nZip the WebSphere Application Server logs folder \n\n<WebSphere Install Dir>\\AppServer\\profiles\\ <profileName>\\logs \nEXCHANGING DATA WITH IBM SUPPORT\nFollow the instructions to send diagnostic information to IBM support, and be sure to provide all information captured above. This step requires that a PMR be opened if not already: \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?rs=180&uid=swg21153852]\n\nRELATED INFORMATION\n IBM Forms Wiki [http://www.lotus.com/ldd/lfwiki.nsf]", "wasservice; was service; wasservice command; websphere windows service; wasservice cmd; versiongap TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n WASServiceCmd.exe is a front end for WASService.exe, which is shipped with WebSphere Application Server. WASService.exe is required in its default directory for adding, updating, and removing WebSphere Services in Windows.\n\nNotice: In WebSphere Application Server v8 and later, this utility is shipped with the product under the name of WASServiceHelper.bat in the bin directory.\nReference:\nUsing the WASServiceHelper utility to create Windows services for application servers\nhttps://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tins_wasservicecmd.html [https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tins_wasservicecmd.html]\n\nSee DeveloperWorks article for detailed information: (Link at the bottom of this document) \n\nSYMPTOM\nCreating and removing a WebSphere service in Windows is confusing and error prone.\n\n\nCAUSE\nThis application takes several parameters which can be confusing to the user along with several long path strings leaving opportunities to setup incorrectly.\n\nENVIRONMENT\nWindows\n\nRESOLVING THE PROBLEM\n\n\n\n 1. Place the WASServiceCmd.exe utility in the following directory:\n \n install_root\\bin \n \n 2. Launch the command from the command line. \n \n \n 3. The WASServiceCmd utility prompts you to select specific options and settings from a list and then calls the WASService.exe command passing all selected parameters. This greatly reduces the time it takes to create a Windows service for WebSphere Application Server and reduces the opportunity for user errors.\n\n\n[/support/docview.wss?uid=swg21397335&amp;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.", "wsad; wte; enable security; server; configuration; security; WebSphere Application Server; WAS Base V5 Server; WAS V4 AEs Server; 1107407; local OS; Act as part of the operating system; NT; XP; 2000; Windows; WSAD; RAD; LDAP TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Enabling security for the WebSphere® Test Environment (WTE) v5.x server configuration of WebSphere Studio Application Developer (WSAD) v5.x and Rational® Application Developer (RAD) v6.0 and v7.0. \n\nRESOLVING THE PROBLEM\nThe following instructions assume that there is a server configured in the WebSphere Test Environment. To enable security for the WebSphere Test Environment, do the following steps: \n\n \n\n 1. Open the Server perspective. \n 2. Open the server configuration in the Server Configuration view. \n 3. Select the Security tab. \n 4. Check the Enable Security box. \n 5. Enter the user name and password for the administrator or any user that is part of the administrator group in Microsoft® Windows® in the Local OS Authentication section. \n 6. Enter the password again for verification. \n 7. Press Ctrl + S to save the changes.\n \n\nFor Linux® users: \n\nStart the server in the WebSphere Test Environment. Find the Security enabled true log entry in the console, which indicates that security is enabled. The console log at the end of this page shows an example. You might receive an exception in the console log that indicates that you do not possess sufficient permissions to start the server. Please consult your system administrator to obtain sufficient access levels to start the server. \n\nFor Windows users: \n\nThe specified user must have the following permissions in Windows: \n * Log on as service \n * Act as part of the operating system\n\n\nTo grant these permissions, follow these steps: \n * For Windows 2000:\n * \n * Click Start > Control Panel Double-click Administrative Tools Double-click Local Security Policy. Expand Local Policies. Double-click User Rights Assignment. Double-click Log on as service from the right side of the window. Click Add. Select the user name. Click Add. Click OK. Click OK. Repeat for Act as part of the operating system. Press Ctrl + S to save the changes. Log off and back on to the operating system for the permission to take effect. \n * \n * For Windows NT:\n * \n * Select Programs > Administrative Tools > User Manager > Policies Menu > User Rights. Check Show Advanced User Rights. Select Log on as service from the drop down list. Click Add. Click Show Users. Select the user name in the Names field. Click Add. Click OK. Repeat step two for Act as part of the operating system. Click OK. Press Ctrl + S to save the changes. Log off and back on to the operating system for the permission to take effect. \n * \n * For Windows XP:\n * \n * Click Start > Control Panel. Double-click Administrative Tools. Double-click Local Security Policy. \n Expand Local Policies Double-click User Rights Assignment. Double-click Log on as service from the right side of the window. Select Add User or Group. Type in the username in the Enter the object names to select field, and click Check Names. The user name in use and machine name appear in the Enter the object names to select field. Click OK. Click OK. Repeat steps two and three for Act as part of the operating system. Press Ctrl + S to save the changes. Log off and back on to the operating system for the permission to take effect. \n * \n * \n\n\nThe following console log shows an example for WebSphere Studio v5.x on Windows NT: \n\nSecurityCompo I SECJ0240I: Security service initialization completed successfully \nSASRas A JSAS0001I: Security configuration initialized. \nSASRas A JSAS0002I: Authentication protocol: CSIV2/IBM \nSASRas A JSAS0003I: Authentication mechanism: SWAM \nSASRas A JSAS0004I: Principal name: localhost/localuser \nSASRas A JSAS0005I: SecurityCurrent registered. \nSASRas A JSAS0006I: Security connection interceptor initialized. \nSASRas A JSAS0007I: Client request interceptor registered. \nSASRas A JSAS0008I: Server request interceptor registered. \nSASRas A JSAS0009I: IOR interceptor registered. \nCacheServiceI I DYNA0048I: WebSphere Dynamic Cache initialized successfully. \nUserRegistryI A SECJ0136I: Custom Registry:com.ibm.ws.security.registry.nt.NTLocalDomainRegistryImpl has been initialized \nJMXSoapAdapte A ADMC0013I: SOAP connector available at port 8880 \nSecurityCompo I SECJ0243I: Security service started successfully \nSecurityCompo I SECJ0210I: Security enabled true \n... \nWsServer A WSVR0001I: Server server1 open for e-business \n\n\nNote: For WTE/WAS v5.x only Local OS security is supported in WSAD v5.x and RAD v6.0/v7.0 as per this technote in the Related Information section: Integrated WebSphere Test Environment v5.x server support for the Administrative Console or non Local OS security. \nLDAP security is not supported. \n\n\n\nRELATED INFORMATION\n#Integrated WTE v5.x server support for the Admin Consol [http://www.ibm.com/support/docview.wss?uid=swg21199888]\n\n\n\n\n\n\nCross Reference information Segment Product Component Platform Version Edition Business Integration WebSphere Studio Application Developer Integration Edition Server Windows, Linux 4.1, 4.1.1, 5.0, 5.0.1 All Editions Business Integration WebSphere Studio Application Developer Server Linux, Windows 4.0, 4.02, 4.03, 5.0, 5.0.1 All Editions Business Integration WebSphere Development Studio Client for iSeries Server Multi-Platform 4.0, 5.0 All Editions Business Integration WebSphere Studio Enterprise Developer Server Linux/390, Windows 5.0, 5.0.1 All Editions Software Development Rational Application Developer for WebSphere Software Server Tooling Windows, Linux 6.0, 6.0.0.1, 6.0.1, 6.0.1.1, 6.0.1.2, 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4 Software Development Rational Software Architect Server Tooling Linux, Windows 6.0, 6.0.0.1, 6.0.1, 6.0.1.1, 6.0.1.2, 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4" ]

[ [ "3a", "wasservice; was service; wasservice command; websphere windows service; wasservice cmd; versiongap TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "3b", " WASServiceCmd.exe is a front end for WASService.exe, which is shipped with WebSphere Application Server." ], [ "3c", "WASService.exe is required in its default directory for adding, updating, and removing WebSphere Services in Windows." ], [ "3d", "Notice: In WebSphere Application Server v8 and later, this utility is shipped with the product under the name of WASServiceHelper.bat in the bin directory. Reference:" ], [ "3e", "Using the WASServiceHelper utility to create Windows services for application servers https://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]" ], [ "3f", "See DeveloperWorks article for detailed information: (Link at the bottom of this document) SYMPTOM" ], [ "3g", "Creating and removing a WebSphere service in Windows is confusing and error prone. CAUSE" ], [ "3h", "This application takes several parameters which can be confusing to the user along with several long path strings leaving opportunities to setup incorrectly. ENVIRONMENT Windows" ], [ "3i", "RESOLVING THE PROBLEM 1." ], [ "3j", "Place the WASServiceCmd.exe utility in the following directory:" ], [ "3k", " install_root\\bin 2." ], [ "3l", "Launch the command from the command line. 3." ], [ "3m", "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." ], [ "3n", "This greatly reduces the time it takes to create a Windows service for WebSphere Application Server and reduces the opportunity for user errors." ], [ "3o", "[/support/docview.wss?uid=swg21397335&amp;aid=1] Flash demonstration [http://public.dhe.ibm.com/software/websphere/appserv/support/tutorials/wasservicecmd.swf]" ], [ "3p", "Note: 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." ], [ "3q", "Example of a log entry:" ], [ "3r", "[Fri Aug 14 12:22:01 -0500 2009] WASService.exe -add \"Deployment Mgr01\" -serverName \"dmgr\"" ], [ "3s", "-profilePath \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\"" ], [ "3t", "-logRoot \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\\logs\\dmgr\"" ], [ "3u", "-logFile \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\\logs\\dmgr\\WS_startdmgr.log\" -encodeParams -stopArgs \"-username vanno -password ****** \" -startType manual" ], [ "3v", "-restart false WASServicecmd.zip [/support/docview.wss?uid=swg21397335&aid=3] [/support/docview.wss?uid=swg21397335&aid=2]" ], [ "3w", "Notice: Some browsers are having trouble downloading this file and getting docview.wss instead." ], [ "3x", "Download this file, then rename the file with a \".zip\" extension (for example, docview.zip or WASServiceCmd.zip)." ], [ "3y", "You can now access the utility." ], [ "3z", "See DeveloperWorks article for more information:" ], [ "3aa", "The 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]" ], [ "3ab", "See 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." ] ]

[ "3a", "3b", "3c", "3d", "3e", "3g", "3j", "3k", "3l", "3m", "3n", "3o", "3p", "3v", "3y", "3aa", "3ab" ]

[ " \nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * \"PathNotFoundException while syndicating a deleted item\"\n \n \n \n \n \n\nLOCAL FIX\n * NA\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Detailed Problem Description:\n \n The following scenario exhibits the problem:\n Create a new library and create items in the library\n Create a syndicator / subscriber pair and rebuild the syndicator\n Stop portal on both machines\n From <wps>/config on both the syndicator and subscriber run:\n WPSconfig[.sh|.bat] wcm-reset-event-log\n Start portal on both machines\n Rebuild the syndicator\n Update items on the first library and create a second library\n with some items that reference into first library. For example,\n create contents in the second library using authoring templates\n from the first.\n Edit the syndicator to add the new library\n Update the syndicator. The syndication is successful, but the\n following exception appears in the log:\n [6/8/07 3:57:11:797 PDT] 0000003a VersioningSer E\n /7d7c070045a25314879defddc740cc36/0/jcr:versionedNode\n \n javax.jcr.PathNotFoundException:\n /7d7c070045a25314879defddc740cc36/0/jcr:versionedNode\n at com.ibm.icm.jcr.NodeImpl.getNode(NodeImpl.java:1013)\n at com.ibm.icm.jcr.NodeImpl.getNode(NodeImpl.java:926)\n at\n com.ibm.icm.jcr.service.version.VersionServiceImpl.restoreToRela\n tivePath(VersionServiceImpl.java:1226)\n at\n com.ibm.icm.jcr.service.version.VersionImpl.restoreToAbsolutePat\n h(VersionImpl.java:680)\n at\n com.ibm.workplace.wcm.services.versioning.VersioningServiceImpl.\n restoreToAbsolutePath(VersioningServiceImpl.java:2891)\n at\n com.ibm.workplace.wcm.services.versioning.VersioningServiceImpl.\n getDeletedVersionAsControllable(VersioningServiceImpl.java:6226)\n at\n com.ibm.workplace.wcm.services.versioning.VersioningServiceImpl.\n getDeleted(VersioningServiceImpl.java:4883)\n at\n com.ibm.workplace.wcm.services.versioning.VersioningServiceImpl.\n getDeleted(VersioningServiceImpl.java:4773)\n at\n com.ibm.workplace.wcm.services.versioning.VersioningServiceUtils\n .getDeletedForSyndication(VersioningServiceUtils.java:887)\n at\n com.aptrix.deployment.syndicator.ItemDispatcher.fetchItemVersion\n (ItemDispatcher.java:363)\n at\n com.aptrix.deployment.syndicator.ItemDispatcher.fetchItem(ItemDi\n spatcher.java:643)\n at\n com.aptrix.deployment.syndicator.ItemDispatcher.dispatchItem(Ite\n mDispatcher.java:261)\n at\n com.aptrix.deployment.syndicator.ItemDispatcher.process(ItemDisp\n atcher.java:209)\n at\n com.presence.connect.business.module.ModuleManager.launchBusines\n s(ModuleManager.java:121)\n at\n com.presence.connect.business.module.ModuleManager.launchBusines\n s(ModuleManager.java:384)\n at\n com.presence.connect.RequestExecutable.execute(RequestExecutable\n .java:84)\n at com.presence.connect.dispatcher.Task.run(Task.java:151)\n at\n com.presence.connect.ConnectClient.processSynchronous(ConnectCli\n ent.java:167)\n at\n com.presence.connect.ConnectServlet.process(ConnectServlet.java:\n 298)\n at\n com.presence.connect.ConnectServlet.doGet(ConnectServlet.java:12\n 0)\n at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)\n at\n javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled\n Code))\n at\n com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr\n apper.java(Compiled Code))\n at\n com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser\n vletWrapper.java(Compiled Code))\n at\n com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleReques\n t(CacheServletWrapper.java(Compiled Code))\n at\n com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.\n java(Compiled Code))\n at\n com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLin\n k.java(Compiled Code))\n at\n com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscr\n imination(HttpInboundLink.java(Compiled Code))\n at\n com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewIn\n formation(HttpInboundLink.java(Compiled Code))\n at\n com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complet\n e(HttpICLReadCallback.java(Compiled Code))\n at\n com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(Wor\n kQueueManager.java(Compiled Code))\n at\n com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueue\n Manager.java(Compiled Code))\n at\n com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueue\n Manager.java(Compiled Code))\n at\n com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueu\n eManager.java(Compiled Code))\n at\n com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled\n Code))\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Problem Analysis:\n \n Sometimes the base version in the JCR has the same timestamp as\n the first real version. If this is true, the base version will\n be returned when retrieving a version by date. The base version\n is not usable for retrieving the actual versions of WCM items\n and trying to use it in that manner causes the exception.\n \n Failing Module: WCM - Web Content Management (General)\n \n Problem Solution:\n \n If a retrieved version is the base version, the succeeding\n versions are retrieved until one with the same timestamp is\n retrieved.\n \n \n Affected Users: All Users\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PK46689\n \n \n * REPORTED COMPONENT NAME\n WRKPLC WEB CON\n \n \n * REPORTED COMPONENT ID\n 5724I2900\n \n \n * REPORTED RELEASE\n 60A\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 2007-06-07\n \n \n * CLOSED DATE\n 2007-08-30\n \n \n * LAST MODIFIED DATE\n 2007-08-30\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 WRKPLC WEB CON\n \n \n * FIXED COMPONENT ID\n 5724I2900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R601 PSY\n UP\n \n \n * R60C PSY\n UP", " FLASH (ALERT)\n\nABSTRACT\n There are two known issues related to WCM with the CF4 installation for WebSphere Portal v8.0.0.1. \n\n1.The CF4 installation fails if the Portal URI has been changed. \n2. If you have disabled automatic syndication, it is re-enabled after CF4 installation completes. \n\nCONTENT\nIssue #1 - The CF4 installation fails during the post-install-configure step \"CONFIG-WP-PTF-CF\" if you have changed the Portal URI to something other than the default /wps. The failure occurs during the sub-script 'run-wcm-admin-task' here:\n========================\nrun-wcm-admin-task:\n[echo] VirtualPortalContext = , VirtualPortalHost = \n[echo] Initialized: host my.portal.com vpContext \n[echo] To call ConfigModuleClient: host my.portal.com vpContext \n[ConfigModuleClient] Connecting to login address: customp://my.portal.com:10039/custom/wcm/login\n[ConfigModuleClient] Connecting to task address: customp://my.portal.com:10039/custom/wcm/myconnect?MOD=data&processLibraries=false&taskType=import&input.dir=%2Fopt%2FIBM%2FWebSphere%2Fwp_profile%2FConfigEngine%2Fconfig%2Fwork%2Fct_import%2Fweb+content+templates&importLibrary=%24%7Bimport.library%7D with user name: uid=wpsadmin,o=defaultWIMFileBasedRealm\n[ConfigModuleClient] No output will be shown while this task is running. Check the SystemOut.log for progress information.\n--- Exception Thrown ---\n/opt/IBM/WebSphere/PortalServer/wcm/prereq.wcm/config/includes/prereq.wcm_cfg.xml:3829: An exception occurred while executing the task: Header field 'Set-Cookie' is null. The login failed. Can not continue.\n=========================\n\nSolution - This is addressed in WCM APAR PM84880.\n\n\n\nIssue #2 - If you have set the WCMConfigService property 'connect.moduleconfig.syndication.inittasks' to 'false' in order to disable automatic syndication, this property will be reset to 'true' after the CF4 installation completes. \n\nNote: You can disable syndication by doing to each syndicator and disabling it there as opposed to setting this property\n\nSolution - This is addressed in WCM APAR PM85264. \n\n\n\nBoth PM84880 and PM85264 have been packaged into a single download. You must apply it in conjunction with CF4 to avoid both of these issues:\n\n- Add both CF4 and \"8.0.0.1-WCM-IFPM84880-PM85264-CF04.zip\" as repositories to IBM Installation Manager\n- When prompted, select both for installation", " A FIX IS AVAILABLE\nFixes integrated in WebSphere Portal 7.0.0.1 & 7.0.0.2 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24029452]\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * The error message displayed when attempting to create a 8001 ->\n 7002 syndication pair does not clearly indicate that this is\n because backward syndication is not supported.\n \n Reproduction Steps\n 1. Create a library \"Test Library\" on a 7002 XVS enabled server\n 2. On a 8001 server, subscriber to the 7002 server and click\n \"Next\"\n 3. Select the library \"Test Library\" and finish\n \n Expected: A clear error message indicating backward syndication\n is not supported on the first page of the wizard (where the\n syndicator details are entered)\n Actual: A generic error message saying \"Could not create\n subscriber. Please check the subscriber logs for more\n information\" appears on the second page of the wizard (where the\n libraries are selected)\n Opened for release 7002\n \n \n \n \n \n\nLOCAL FIX\n * When syndicating with higher version of WCM, a error code will\n returned. Get this error code and display a clearer error\n message in the UI.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * The error message displayed when attempting to create a 8001 ->\n 7002 syndication pair does not clearly indicate that this is\n because backward syndication is not supported.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * When syndicating with higher version of WCM, a error code will\n returned. Get this error code and display a clearer error\n message in the UI.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI05098\n \n \n * REPORTED COMPONENT NAME\n LOTUS WEB CONT\n \n \n * REPORTED COMPONENT ID\n 5724I2900\n \n \n * REPORTED RELEASE\n 700\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 2013-10-29\n \n \n * CLOSED DATE\n 2013-11-12\n \n \n * LAST MODIFIED DATE\n 2013-11-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 LOTUS WEB CONT\n \n \n * FIXED COMPONENT ID\n 5724I2900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R700 PSY\n UP", "JDBC 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]", "My notifications; notifications; subscribe; APAR; software updates; fix pack release TECHNOTE (FAQ)\n\nQUESTION\n How can you receive an e-mail either weekly or daily with important technical news about the IBM products that you select? \n\n\nANSWER\n1) Go to https://www.ibm.com/support/mynotifications [https://www.ibm.com/support/mynotifications] to learn more about the features of the My Notifications service, change your subscription, or to become a new subscriber. \n2) For a detailed PDF, Click on Help in the left navigation panel and click on the anchor entitled: \"Detailed documentation for using the My notifications tool\". \n\n3) You will then be taken to the section with the following link \"Support Notifications for IBM Products using the My notifications tool\". \n\n4) Click the link for a PDF document that provides (1) An overview and instructions & (2) How to subscribe and manage subscriptions. \n\n5) I have attached the PDF for your reference, but as this PDF could become out of date, it is always a good idea follow the above steps for the most current version of the PDF.\n\n[Topics under the 'Help' menu, located in the left navigation panel]\nHow do I create and organize subscriptions?\nHow am I notified about my subscriptions?\nHow do I specify frequency of e-mail notifications?\nHow can I change the e-mail address where my notifications are delivered?\nHow can I include machine translated content for emails, syndication feeds and web folders?\nWhat are syndication feeds (RSS,Atom) and how do I use them?\nHow do I enable folder messages or syndication links?\nHow can I subscribe to APARs?\nHow do I find APARs?\nCan I subscribe to specific topics per product?\nCan I define my own default folder name and notification options?\nCan I update the notification options for all of my subscriptions at one time?\nHow do I unsubscribe?\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\nSupport Notifications for IBM Products.pdf [/support/docview.wss?uid=swg21619629&aid=2]Support Notifications for IBM Products.pdf [/support/docview.wss?uid=swg21619629&aid=1]" ]

[ [ "3a", "JDBC JCC SSL SSLKeyException .InvalidKeyException TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "3b", " My java application using the Data Server Driver for JDBC (JCC) is failing to establish SSL connection with following error:" ], [ "3c", "SSLKeyException: RSA premaster secret error." ], [ "3d", "Caused by: java.security.InvalidKeyException: Illegal key size or default parameters. SYMPTOM" ], [ "3e", "javax.net.ssl.SSLKeyException: RSA premaster secret error." ], [ "3f", "Caused by: java.security.InvalidKeyException: Illegal key size or default parameters CAUSE" ], [ "3g", "The default restricted policy file has a 2048 key size limit." ], [ "3h", "If the RSA key size exceeds this limit then this error is expected." ], [ "3i", "RESOLVING THE PROBLEM" ], [ "3j", "This issue can be resolved by upgrading to the unrestricted policy files, replacing the security policy files with the IBM unlimited cryptography files." ], [ "3k", "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]" ] ]

[ "3b", "3c", "3d", "3g", "3h", "3i", "3j", "3k" ]

[ "isLicenseValidatedWithServerLicenseProc; checkForLicenseRestrictions; hang; jdbc; java; license; connect TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Java application hang during license check \n\nSYMPTOM\nJavacore file will show the function stack below: \n\nat sun/nio/ch/FileChannelImpl.lock0\nat sun/nio/ch/FileChannelImpl.lock(FileChannelImpl.java:882)\nat java/nio/channels/FileChannel.lock(FileChannel.java:871)\nat com/ibm/db2/jcc/am/hp.a(hp.java:629)\nat com/ibm/db2/jcc/am/gp.a(gp.java:403)\nat com/ibm/db2/jcc/am/gp.a(gp.java:475)\nat com/ibm/db2/jcc/am/Connection.isLicenseValidatedWithServerLicenseProc\nat com/ibm/db2/jcc/am/Connection.checkForLicenseRestrictions\nat com/ibm/db2/jcc/am/Connection.completeConnect\n...\n\n\nRESOLVING THE PROBLEM\n \n\nTwo possible causes: \n\n(a) Known defect with JDBC driver first fixed in db2jcc4.jar v4.16.53 (build date 2013-05-23)\n$ java -cp ./db2jcc4.jar:. com.ibm.db2.jcc.DB2Jcc -version\n\nDB2 JDBC Driver Versions and Downloads\nhttp://www-01.ibm.com/support/docview.wss?rs=71&uid=swg21363866 [http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg21363866]\n\nIf using db2jcc.jar, use a recent driver or newest one.\n\n(b) DB2Driver class being loaded multiple times into a single JVM. This behaviour is unsupported and would also cause a hang with function stack seen in Symptom section.", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n User can not create P8 domain with the following exception:\n\nERROR GCDinit: Error occurred checking/creating table: FNGCD, No statement. com.filenet.api.exception.EngineRuntimeException: FNRCD0009E: DB_ERROR: The database access failed with the following error: ErrorCode -4,203, Message '[jcc][t4][2041][11392][4.17.29] Error executing XAResource.start(). Server returned XAER_PROTO. ERRORCODE=-4203, SQLSTATE=null' SQL: \"\"SELECT 1 FROM FNGCD for update with RS\"\" \n\nDIAGNOSING THE PROBLEM\nI found the following tech note that describes this issue: \n\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21963886 [http://www-01.ibm.com/support/docview.wss?uid=swg21963886]\n\nFrom the above tech note, we can see the DB2 JDBC driver version 4.17.28 are not supported with DB2 10.5 FP2, but in this environment, it's using DB2 10.5 FP3 and the JDBC driver version is 4.17.29 and still encounter the same error.\n\nWhat I think is: The driver version with 4.17.29 from DB2 10.5 FP3 has the exact same issue as driver version 4.17.28 from DB2 10.5 FP2. We'd better add it to compatibility report.\n\n\nRESOLVING THE PROBLEM\nAfter user downloads the JDBC driver with version 4.16.53 and put to DB2 JDBC Driver Path, then perform a recycle on CPE WAS JVM, they can create the domain successfully.", "z/os FIXES ARE AVAILABLE\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX [http://www-01.ibm.com/support/docview.wss?uid=swg24028875]\n7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24028881]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX [http://www-01.ibm.com/support/docview.wss?uid=swg24029071]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i [http://www-01.ibm.com/support/docview.wss?uid=swg24029072]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux [http://www-01.ibm.com/support/docview.wss?uid=swg24029073]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris [http://www-01.ibm.com/support/docview.wss?uid=swg24029074]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24029075]\n7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17 [http://www-01.ibm.com/support/docview.wss?uid=swg24029634]\n7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24029894]\n7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19 [http://www-01.ibm.com/support/docview.wss?uid=swg24030660]\n7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21 [http://www-01.ibm.com/support/docview.wss?uid=swg24031366]\n7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23 [http://www-01.ibm.com/support/docview.wss?uid=swg24032493]\n7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25 [http://www-01.ibm.com/support/docview.wss?uid=swg24033267]\n7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27 [http://www-01.ibm.com/support/docview.wss?uid=swg24033882]\n7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29 [http://www-01.ibm.com/support/docview.wss?uid=swg24034966]\n7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31 [http://www-01.ibm.com/support/docview.wss?uid=swg24036768]\n7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24035324]\n7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33 [http://www-01.ibm.com/support/docview.wss?uid=swg24037573]\n7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35 [http://www-01.ibm.com/support/docview.wss?uid=swg24038310]\n7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37 [http://www-01.ibm.com/support/docview.wss?uid=swg24039338]\n7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39 [http://www-01.ibm.com/support/docview.wss?uid=swg24041013]\n7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41 [http://www-01.ibm.com/support/docview.wss?uid=swg24041931]\n7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43 [http://www-01.ibm.com/support/docview.wss?uid=swg24043400]\n7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45 [http://www-01.ibm.com/support/docview.wss?uid=swg24044551]\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 * It is possible that the schema name indicated by the\n CurrentSQLID property is not honored. One consequence is that\n customers may encounter the following error due to an incorrect\n schema name:\n \n Exception data: com.ibm.ejs.container.CreateFailureException: ;\n nested exception is:\n .com.ibm.events.datastore.DataStoreException: CEIDS0058E\n Database table cei_t_properties does not exist for schema\n WPJMSU. The defau lt data store is unable to start.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server V7.0 users that configures Common *\n * Event Infrastructure with DB2 z/OS database *\n * using IBM Data Server Driver. *\n ****************************************************************\n * PROBLEM DESCRIPTION: The automatic configuration process *\n * of Common Event Infrastructure with *\n * DB2 z/OS database does not support *\n * specifying a different schema from *\n * the CURRENTSQLID when the data source *\n * uses IBM Data Server. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n The automatic configuration process of Common Event\n Infrastructure with a DB2 z/OS database creates the WebSphere\n Application Server data source based on the DB2 Universal JDBC\n Driver Provider (XA) driver version (the case of remote DB2\n z/OS database) or DB2 Universal JDBC Driver Provider (the case\n of local DB2 z/OS database). These are the scenarios when JDBC\n driver v3.0 is used and in this case the user can specify a\n different schema where the tables are stored on. At runtime\n the tables will be qualified with the correct schema. In case\n of a data source that is based on the IBM Data Server driver\n the tables are not correctly qualified. The user that is\n specified for the connection is used instead.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The runtime code used when the initial database access is\n performed was augmented in order to consider a different\n schema if this is specified. This can be achieved by providing\n a value tot the CURRENTSQLID custom parameter.\n In order to support this also at the configuration level, the\n automatic configuration process with DB2 z/OS database has been\n changed by adding to the configEventServiceDB2ZOSDB\n configuration Admin Task a new optional parameter\n -jdbcDriverVersion that will accept the following\n possible/acceptable values 3.0 / 4.0\n By using the '3.0' value it will configure the JDBC provider\n to use DB2 Universal JDBC Driver Provider (XA) or DB2\n Universal JDBC Driver Provider. The usage of '4.0' value will\n determine the configuration of the JDBC provider to be based\n on the DB2 Using IBM JCC Driver (XA) or on the DB2 Using IBM\n JCC Driver version (depending on the database location &#162;&#226;&#130;&#172;&#226;€&#156;\n remote or local).\n The introduced behavior is:\n a. -jdbcDriverVersion not specified in the AdminTask - The\n configuration will be performed using 'DB2 Universal JDBC\n Driver Provider (XA)' or DB2 &#162;&#226;&#130;&#172; &#156;Universal JDBC Driver Provid\n therefore the 3.0 driver version.\n b. -jdbcDriverVersion specified but no value supplied - Will\n raise an exception as -jdbcDriverVersion needs a parameter,\n then if the user goes so far as to use the parameter but does\n NOT supply a value, we give an error stating like in the\n following example \"CEIIN0739E No value was specified for the\n jdbcDriverVersion parameter\".\n c. -jdbcDriverVersion specified with the '3.0' value supplied\n - The configuration will be performed using 'DB2 Universal\n JDBC Driver Provider (XA)' or DB2 'Universal JDBC Driver\n Provider'.\n d. -jdbcDriverVersion specified with the '4.0' value supplied\n - The configuration will be performed using 'DB2 Using IBM JCC\n Driver (XA)' or 'DB2 Using IBM JCC Driver', therefore based\n on the provider that supports JDBC 4.0 specification using the\n IBM Data Server Driver.\n e. -jdbcDriverVersion specified with a value OTHER than 3.0 or\n 4.0 - Will raise an exception like in the following example:\n \"CEIIN0701E The parameter jdbcDriverVersion contains the value\n <wrong_value>, which is not valid. Valid values are: 3.0, 4.0.\"\n \n APAR PM22017 is currently targeted for inclusion in Service\n Level (Fix Pack) 7.0.0.15 of WebSphere Application Server V7.0.\n \n Please refer to URL:\n //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970\n for Fix Pack availability.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM22017\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE FOR Z\n \n \n * REPORTED COMPONENT ID\n 5655I3500\n \n \n * REPORTED RELEASE\n 700\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 2010-09-07\n \n \n * CLOSED DATE\n 2010-11-29\n \n \n * LAST MODIFIED DATE\n 2011-04-04\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 FOR Z\n \n \n * FIXED COMPONENT ID\n 5655I3500\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R700 PSY UK65060 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK65060]\n UP11/03/04 P F103\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.", "wps; commonDB; can't detect DB; WSVR0501E; DDT; deployment manager; JCC; common database; database provider; v70rnotes TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n If you use the DB2 JDBC JCC driver as the provider for the Common database when configuring your deployment environment, WebSphere Process Server might not recognize the database type and deployment manager startup might fail. \n\nSYMPTOM\nThe following exception can occur when starting the deployment environment or using other administrative operations to manage the deployment environment. \n\n[10/1/10 3:44:01:828 EDT] 00000000 ContainerHelp E WSVR0501E: Error creating component com.ibm.wbiserver.security.auth.startup.SecurityComponentImpl@6c806c80\ncom.ibm.ws.exception.RuntimeWarning: An error occurred while starting system roles component to populate BPM admin roles.\nat com.ibm.wbiserver.security.auth.startup.SecurityComponentImpl.start(SecurityComponentImpl.java:75)\nat com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:538)\nat com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:627)\nat com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:618)\n..\nCaused by: java.lang.IllegalStateException: Can't detect DB\nat com.webify.wsf.support.spring.dbversion.DbUtils.doDetection(DbUtils.java:136)\nat com.webify.wsf.support.spring.dbversion.DbUtils.detectDatabaseType(DbUtils.java:92)\nat com.ibm.tyto.jdbc.database.DatabaseFactoryImpl.selectAdapter(DatabaseFactoryImpl.java:37)\nat com.ibm.tyto.jdbc.database.DatabaseFactoryImpl.getDatabase(DatabaseFactoryImpl.java:31)\nat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\nat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)\nat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)\nat java.lang.reflect.Method.invoke(Method.java:600)\nat org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:115)\n... 118 more\n\n\nCAUSE\nThe Database Design Tool offers two provider options when you are configuring and generating the generating the wps.nd.topology.dbDesign file:\n\n\n * DB2 Universal JDBC Driver Provider # XA data source # DB2 Universal JDBC Driver Provider (XA) \n * DB2 Using IBM JCC Driver # XA data source # DB2 Using IBM JCC Driver (XA)\n\n\n\nIf you choose the JCC driver and then use the design file to create the deployment manager, some WebSphere Process Server components do not recognize the database type. \nRESOLVING THE PROBLEM\nIf you are using the wps.nd.topology.dbDesign file to create the deployment manager, generate a new DbDesign file using that uses the DB2 Universal JDBC Driver Provider (XA). Create a new deployment manager using this new dbDesign file.\n\nRELATED INFORMATION\n Creating the database design file using the DDT [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wps.doc/doc/tcfg_ddl_generator.html]", "OutOfMemoryException; Universal; JDBC; leak; memory TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n A memory leak in DB2 Universal JDBC driver might cause an OutOfMemoryException exception for DB2 Content Manager client applications. \n\nRESOLVING THE PROBLEM\nA memory leak in the DB2 Universal JDBC driver causes DB2 Content Manager Information Integrator for Content API applications to become unresponsive. In some cases, WebSphere Application Server applications that use the DB2 Content Manager Information Integrator for Content API report an OutOfMemoryException in the WebSphere Application Server error log files.\nThis problem is caused by defects in the DB2 Universal JDBC driver that are tracked with the following APARs:\n\nAPAR= JR30534\nMEMORY LEAK IN VECTOR FIELD OF COM.IBM.DB2.JCC.AM.CONFIGURATION,SUBCLASS OF COM.IBM.JCC.DB2BASEDATASOURCE.\n\nAPAR= IZ36247\nJCC NOT CLEANING LOGWRITERS IN CASE OF CONNECTION FAILURE.\n\nUser Response:\nDB2 Content Manager Information Integrator for Content Version 8.4 API users should download IBM Data Server Driver for JDBC and SQLJ Version 9.5 Fix Pack 4 (or later). The link to Version 9.5 Fix Pack 4 is in the Related information section. When you get to that Web page, scroll down to the row for IBM Data Server Driver for JDBC and SQLJ, download the compressed deliverable, then extract the db2jcc.jar file.\n\nRELATED INFORMATION\n DB2 UDB Version 9.5 fix pack 4 downloads [http://www-01.ibm.com/support/docview.wss?uid=swg24023213]" ]

[ [ "0a", "isLicenseValidatedWithServerLicenseProc; checkForLicenseRestrictions; hang; jdbc; java; license; connect TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "0b", " Java application hang during license check SYMPTOM" ], [ "0c", "Javacore file will show the function stack below: at sun/nio/ch/FileChannelImpl.lock0 at sun/nio/ch/FileChannelImpl.lock(FileChannelImpl.java:882) at java/nio/channels/FileChannel.lock(FileChannel.java:871) at com/ibm/db2/jcc/am/hp.a(hp.java:629) at com/ibm/db2/jcc/am/gp.a(gp.java:403) at com/ibm/db2/jcc/am/gp.a(gp.java:475) at com/ibm/db2/jcc/am/Connection.isLicenseValidatedWithServerLicenseProc at com/ibm/db2/jcc/am/Connection.checkForLicenseRestrictions at com/ibm/db2/jcc/am/Connection.completeConnect ..." ], [ "0d", "RESOLVING THE PROBLEM" ], [ "0e", "Two possible causes:" ], [ "0f", "(a) Known defect with JDBC driver first fixed in db2jcc4.jar v4.16.53 (build date 2013-05-23)" ], [ "0g", "$ java -cp ./db2jcc4.jar:. com.ibm.db2.jcc.DB2Jcc -version" ], [ "0h", "DB2 JDBC Driver Versions and Downloads http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg21363866 [http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg21363866]" ], [ "0i", "If using db2jcc.jar, use a recent driver or newest one." ], [ "0j", "(b) DB2Driver class being loaded multiple times into a single JVM." ], [ "0k", "This behaviour is unsupported and would also cause a hang with function stack seen in Symptom section." ] ]

[ "0a", "0b", "0c", "0d", "0e", "0f", "0g", "0h", "0i", "0j", "0k", "3a", "3b", "3c", "3d", "3e", "3f", "3i", "3j", "3k", "3m" ]

[ "isLicenseValidatedWithServerLicenseProc; checkForLicenseRestrictions; hang; jdbc; java; license; connect TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Java application hang during license check \n\nSYMPTOM\nJavacore file will show the function stack below: \n\nat sun/nio/ch/FileChannelImpl.lock0\nat sun/nio/ch/FileChannelImpl.lock(FileChannelImpl.java:882)\nat java/nio/channels/FileChannel.lock(FileChannel.java:871)\nat com/ibm/db2/jcc/am/hp.a(hp.java:629)\nat com/ibm/db2/jcc/am/gp.a(gp.java:403)\nat com/ibm/db2/jcc/am/gp.a(gp.java:475)\nat com/ibm/db2/jcc/am/Connection.isLicenseValidatedWithServerLicenseProc\nat com/ibm/db2/jcc/am/Connection.checkForLicenseRestrictions\nat com/ibm/db2/jcc/am/Connection.completeConnect\n...\n\n\nRESOLVING THE PROBLEM\n \n\nTwo possible causes: \n\n(a) Known defect with JDBC driver first fixed in db2jcc4.jar v4.16.53 (build date 2013-05-23)\n$ java -cp ./db2jcc4.jar:. com.ibm.db2.jcc.DB2Jcc -version\n\nDB2 JDBC Driver Versions and Downloads\nhttp://www-01.ibm.com/support/docview.wss?rs=71&uid=swg21363866 [http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg21363866]\n\nIf using db2jcc.jar, use a recent driver or newest one.\n\n(b) DB2Driver class being loaded multiple times into a single JVM. This behaviour is unsupported and would also cause a hang with function stack seen in Symptom section.", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n User can not create P8 domain with the following exception:\n\nERROR GCDinit: Error occurred checking/creating table: FNGCD, No statement. com.filenet.api.exception.EngineRuntimeException: FNRCD0009E: DB_ERROR: The database access failed with the following error: ErrorCode -4,203, Message '[jcc][t4][2041][11392][4.17.29] Error executing XAResource.start(). Server returned XAER_PROTO. ERRORCODE=-4203, SQLSTATE=null' SQL: \"\"SELECT 1 FROM FNGCD for update with RS\"\" \n\nDIAGNOSING THE PROBLEM\nI found the following tech note that describes this issue: \n\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21963886 [http://www-01.ibm.com/support/docview.wss?uid=swg21963886]\n\nFrom the above tech note, we can see the DB2 JDBC driver version 4.17.28 are not supported with DB2 10.5 FP2, but in this environment, it's using DB2 10.5 FP3 and the JDBC driver version is 4.17.29 and still encounter the same error.\n\nWhat I think is: The driver version with 4.17.29 from DB2 10.5 FP3 has the exact same issue as driver version 4.17.28 from DB2 10.5 FP2. We'd better add it to compatibility report.\n\n\nRESOLVING THE PROBLEM\nAfter user downloads the JDBC driver with version 4.16.53 and put to DB2 JDBC Driver Path, then perform a recycle on CPE WAS JVM, they can create the domain successfully.", "z/os FIXES ARE AVAILABLE\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX [http://www-01.ibm.com/support/docview.wss?uid=swg24028875]\n7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24028881]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX [http://www-01.ibm.com/support/docview.wss?uid=swg24029071]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i [http://www-01.ibm.com/support/docview.wss?uid=swg24029072]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux [http://www-01.ibm.com/support/docview.wss?uid=swg24029073]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris [http://www-01.ibm.com/support/docview.wss?uid=swg24029074]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24029075]\n7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17 [http://www-01.ibm.com/support/docview.wss?uid=swg24029634]\n7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24029894]\n7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19 [http://www-01.ibm.com/support/docview.wss?uid=swg24030660]\n7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21 [http://www-01.ibm.com/support/docview.wss?uid=swg24031366]\n7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23 [http://www-01.ibm.com/support/docview.wss?uid=swg24032493]\n7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25 [http://www-01.ibm.com/support/docview.wss?uid=swg24033267]\n7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27 [http://www-01.ibm.com/support/docview.wss?uid=swg24033882]\n7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29 [http://www-01.ibm.com/support/docview.wss?uid=swg24034966]\n7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31 [http://www-01.ibm.com/support/docview.wss?uid=swg24036768]\n7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24035324]\n7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33 [http://www-01.ibm.com/support/docview.wss?uid=swg24037573]\n7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35 [http://www-01.ibm.com/support/docview.wss?uid=swg24038310]\n7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37 [http://www-01.ibm.com/support/docview.wss?uid=swg24039338]\n7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39 [http://www-01.ibm.com/support/docview.wss?uid=swg24041013]\n7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41 [http://www-01.ibm.com/support/docview.wss?uid=swg24041931]\n7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43 [http://www-01.ibm.com/support/docview.wss?uid=swg24043400]\n7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45 [http://www-01.ibm.com/support/docview.wss?uid=swg24044551]\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 * It is possible that the schema name indicated by the\n CurrentSQLID property is not honored. One consequence is that\n customers may encounter the following error due to an incorrect\n schema name:\n \n Exception data: com.ibm.ejs.container.CreateFailureException: ;\n nested exception is:\n .com.ibm.events.datastore.DataStoreException: CEIDS0058E\n Database table cei_t_properties does not exist for schema\n WPJMSU. The defau lt data store is unable to start.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server V7.0 users that configures Common *\n * Event Infrastructure with DB2 z/OS database *\n * using IBM Data Server Driver. *\n ****************************************************************\n * PROBLEM DESCRIPTION: The automatic configuration process *\n * of Common Event Infrastructure with *\n * DB2 z/OS database does not support *\n * specifying a different schema from *\n * the CURRENTSQLID when the data source *\n * uses IBM Data Server. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n The automatic configuration process of Common Event\n Infrastructure with a DB2 z/OS database creates the WebSphere\n Application Server data source based on the DB2 Universal JDBC\n Driver Provider (XA) driver version (the case of remote DB2\n z/OS database) or DB2 Universal JDBC Driver Provider (the case\n of local DB2 z/OS database). These are the scenarios when JDBC\n driver v3.0 is used and in this case the user can specify a\n different schema where the tables are stored on. At runtime\n the tables will be qualified with the correct schema. In case\n of a data source that is based on the IBM Data Server driver\n the tables are not correctly qualified. The user that is\n specified for the connection is used instead.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The runtime code used when the initial database access is\n performed was augmented in order to consider a different\n schema if this is specified. This can be achieved by providing\n a value tot the CURRENTSQLID custom parameter.\n In order to support this also at the configuration level, the\n automatic configuration process with DB2 z/OS database has been\n changed by adding to the configEventServiceDB2ZOSDB\n configuration Admin Task a new optional parameter\n -jdbcDriverVersion that will accept the following\n possible/acceptable values 3.0 / 4.0\n By using the '3.0' value it will configure the JDBC provider\n to use DB2 Universal JDBC Driver Provider (XA) or DB2\n Universal JDBC Driver Provider. The usage of '4.0' value will\n determine the configuration of the JDBC provider to be based\n on the DB2 Using IBM JCC Driver (XA) or on the DB2 Using IBM\n JCC Driver version (depending on the database location &#162;&#226;&#130;&#172;&#226;€&#156;\n remote or local).\n The introduced behavior is:\n a. -jdbcDriverVersion not specified in the AdminTask - The\n configuration will be performed using 'DB2 Universal JDBC\n Driver Provider (XA)' or DB2 &#162;&#226;&#130;&#172; &#156;Universal JDBC Driver Provid\n therefore the 3.0 driver version.\n b. -jdbcDriverVersion specified but no value supplied - Will\n raise an exception as -jdbcDriverVersion needs a parameter,\n then if the user goes so far as to use the parameter but does\n NOT supply a value, we give an error stating like in the\n following example \"CEIIN0739E No value was specified for the\n jdbcDriverVersion parameter\".\n c. -jdbcDriverVersion specified with the '3.0' value supplied\n - The configuration will be performed using 'DB2 Universal\n JDBC Driver Provider (XA)' or DB2 'Universal JDBC Driver\n Provider'.\n d. -jdbcDriverVersion specified with the '4.0' value supplied\n - The configuration will be performed using 'DB2 Using IBM JCC\n Driver (XA)' or 'DB2 Using IBM JCC Driver', therefore based\n on the provider that supports JDBC 4.0 specification using the\n IBM Data Server Driver.\n e. -jdbcDriverVersion specified with a value OTHER than 3.0 or\n 4.0 - Will raise an exception like in the following example:\n \"CEIIN0701E The parameter jdbcDriverVersion contains the value\n <wrong_value>, which is not valid. Valid values are: 3.0, 4.0.\"\n \n APAR PM22017 is currently targeted for inclusion in Service\n Level (Fix Pack) 7.0.0.15 of WebSphere Application Server V7.0.\n \n Please refer to URL:\n //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970\n for Fix Pack availability.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM22017\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE FOR Z\n \n \n * REPORTED COMPONENT ID\n 5655I3500\n \n \n * REPORTED RELEASE\n 700\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 2010-09-07\n \n \n * CLOSED DATE\n 2010-11-29\n \n \n * LAST MODIFIED DATE\n 2011-04-04\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 FOR Z\n \n \n * FIXED COMPONENT ID\n 5655I3500\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R700 PSY UK65060 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK65060]\n UP11/03/04 P F103\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.", "wps; commonDB; can't detect DB; WSVR0501E; DDT; deployment manager; JCC; common database; database provider; v70rnotes TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n If you use the DB2 JDBC JCC driver as the provider for the Common database when configuring your deployment environment, WebSphere Process Server might not recognize the database type and deployment manager startup might fail. \n\nSYMPTOM\nThe following exception can occur when starting the deployment environment or using other administrative operations to manage the deployment environment. \n\n[10/1/10 3:44:01:828 EDT] 00000000 ContainerHelp E WSVR0501E: Error creating component com.ibm.wbiserver.security.auth.startup.SecurityComponentImpl@6c806c80\ncom.ibm.ws.exception.RuntimeWarning: An error occurred while starting system roles component to populate BPM admin roles.\nat com.ibm.wbiserver.security.auth.startup.SecurityComponentImpl.start(SecurityComponentImpl.java:75)\nat com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:538)\nat com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:627)\nat com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:618)\n..\nCaused by: java.lang.IllegalStateException: Can't detect DB\nat com.webify.wsf.support.spring.dbversion.DbUtils.doDetection(DbUtils.java:136)\nat com.webify.wsf.support.spring.dbversion.DbUtils.detectDatabaseType(DbUtils.java:92)\nat com.ibm.tyto.jdbc.database.DatabaseFactoryImpl.selectAdapter(DatabaseFactoryImpl.java:37)\nat com.ibm.tyto.jdbc.database.DatabaseFactoryImpl.getDatabase(DatabaseFactoryImpl.java:31)\nat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\nat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)\nat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)\nat java.lang.reflect.Method.invoke(Method.java:600)\nat org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:115)\n... 118 more\n\n\nCAUSE\nThe Database Design Tool offers two provider options when you are configuring and generating the generating the wps.nd.topology.dbDesign file:\n\n\n * DB2 Universal JDBC Driver Provider # XA data source # DB2 Universal JDBC Driver Provider (XA) \n * DB2 Using IBM JCC Driver # XA data source # DB2 Using IBM JCC Driver (XA)\n\n\n\nIf you choose the JCC driver and then use the design file to create the deployment manager, some WebSphere Process Server components do not recognize the database type. \nRESOLVING THE PROBLEM\nIf you are using the wps.nd.topology.dbDesign file to create the deployment manager, generate a new DbDesign file using that uses the DB2 Universal JDBC Driver Provider (XA). Create a new deployment manager using this new dbDesign file.\n\nRELATED INFORMATION\n Creating the database design file using the DDT [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wps.doc/doc/tcfg_ddl_generator.html]", "OutOfMemoryException; Universal; JDBC; leak; memory TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n A memory leak in DB2 Universal JDBC driver might cause an OutOfMemoryException exception for DB2 Content Manager client applications. \n\nRESOLVING THE PROBLEM\nA memory leak in the DB2 Universal JDBC driver causes DB2 Content Manager Information Integrator for Content API applications to become unresponsive. In some cases, WebSphere Application Server applications that use the DB2 Content Manager Information Integrator for Content API report an OutOfMemoryException in the WebSphere Application Server error log files.\nThis problem is caused by defects in the DB2 Universal JDBC driver that are tracked with the following APARs:\n\nAPAR= JR30534\nMEMORY LEAK IN VECTOR FIELD OF COM.IBM.DB2.JCC.AM.CONFIGURATION,SUBCLASS OF COM.IBM.JCC.DB2BASEDATASOURCE.\n\nAPAR= IZ36247\nJCC NOT CLEANING LOGWRITERS IN CASE OF CONNECTION FAILURE.\n\nUser Response:\nDB2 Content Manager Information Integrator for Content Version 8.4 API users should download IBM Data Server Driver for JDBC and SQLJ Version 9.5 Fix Pack 4 (or later). The link to Version 9.5 Fix Pack 4 is in the Related information section. When you get to that Web page, scroll down to the row for IBM Data Server Driver for JDBC and SQLJ, download the compressed deliverable, then extract the db2jcc.jar file.\n\nRELATED INFORMATION\n DB2 UDB Version 9.5 fix pack 4 downloads [http://www-01.ibm.com/support/docview.wss?uid=swg24023213]" ]

[ [ "3a", "wps; commonDB; can't detect DB; WSVR0501E; DDT; deployment manager; JCC; common database; database provider; v70rnotes TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "3b", " If you use the DB2 JDBC JCC driver as the provider for the Common database when configuring your deployment environment, WebSphere Process Server might not recognize the database type and deployment manager startup might fail. SYMPTOM" ], [ "3c", "The following exception can occur when starting the deployment environment or using other administrative operations to manage the deployment environment." ], [ "3d", "[10/1/10 3:44:01:828 EDT] 00000000 ContainerHelp E WSVR0501E: Error creating component com.ibm.wbiserver.security.auth.startup.SecurityComponentImpl@6c806c80" ], [ "3e", "com.ibm.ws.exception.RuntimeWarning: An error occurred while starting system roles component to populate BPM admin roles. at com.ibm.wbiserver.security.auth.startup.SecurityComponentImpl.start(SecurityComponentImpl.java:75) at com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:538) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:627) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:618) .." ], [ "3f", "Caused by: java.lang.IllegalStateException: Can't detect DB at com.webify.wsf.support.spring.dbversion.DbUtils.doDetection(DbUtils.java:136) at com.webify.wsf.support.spring.dbversion.DbUtils.detectDatabaseType(DbUtils.java:92) at com.ibm.tyto.jdbc.database.DatabaseFactoryImpl.selectAdapter(DatabaseFactoryImpl.java:37) at com.ibm.tyto.jdbc.database.DatabaseFactoryImpl.getDatabase(DatabaseFactoryImpl.java:31)" ], [ "3g", "at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:600) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:115)" ], [ "3h", "... 118 more CAUSE" ], [ "3i", "The Database Design Tool offers two provider options when you are configuring and generating the generating the wps.nd.topology.dbDesign file:" ], [ "3j", " * DB2 Universal JDBC Driver Provider # XA data source # DB2 Universal JDBC Driver Provider (XA)" ], [ "3k", " * DB2 Using IBM JCC Driver # XA data source # DB2 Using IBM JCC Driver (XA)" ], [ "3l", "If you choose the JCC driver and then use the design file to create the deployment manager, some WebSphere Process Server components do not recognize the database type." ], [ "3m", "RESOLVING THE PROBLEM" ], [ "3n", "If you are using the wps.nd.topology.dbDesign file to create the deployment manager, generate a new DbDesign file using that uses the DB2 Universal JDBC Driver Provider (XA)." ], [ "3o", "Create a new deployment manager using this new dbDesign file. RELATED INFORMATION" ], [ "3p", " Creating the database design file using the DDT [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wps.doc/doc/tcfg_ddl_generator.html]" ] ]

[ "0a", "0b", "0c", "0d", "0e", "0f", "0g", "0h", "0i", "0j", "0k", "3a", "3b", "3c", "3d", "3e", "3f", "3i", "3j", "3k", "3m" ]

[ "bpm751; typical install; launchpad; hang; 41% TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The Launchpad hangs at 41% when you install an IBM Business Process Manager product using the typical installation method in some Microsoft Windows environments. \n\nSYMPTOM\nThe following screen capture shows the Launchpad has stopped at 41% complete: \n\n\n\n[/support/docview.wss?uid=swg21588515&aid=1] [/support/docview.wss?uid=swg21588515&aid=1]\n\n\n\nIn the Launchpad log files, you find the following lines as the last entry:\n\n1322802963546 I: Running install step 4 of 7 1322802963562 I: Running imcl install 1322802963625 I: id: 7.5.1.0-WS-ATLAS-IFJR41201 7.5.1.0-WS-ATLAS-IFJR41203 7.5.1.0-WS-BPM-IFJR41195 7.5.1.0-WS-BPMPC-IFJR41200 7.0.0.19-WS-WAS-IFPM37925 7.0.0.19-WS-WAS-IFPM43353 7.0.0.19-WS-WAS-IFPM43364 7.0.0.19-WS-WAS-IFPM43561 7.0.0.19-WS-WAS-IFPM45697 7.0.0.19-WS-WAS-IFPM47956 7.0.0.19-WS-WAS-IFPM48489 7.0.0.19-WS-WAS-IFPM49205 7.0.0.19-WS-WAS-IFPM49452 7.0.0.19-WS-WAS-IFPM50399 7.0.0.19-WS-WAS-IFPM51383 7.0.0.19-WS-WAS-IFPM51899 7.0.0.19-WS-WAS-IFPM52125 7.0.0.19-WS-WASND-IFPM50455 1.0.0.9-WS-WASXML-IFPM51341 1322802963625 I: location: C:\\IBM\\BPM\\v7.5 1322802963625 I: repository: http://public.dhe.ibm.com/software/websphere/bpm/repositories/server/bspace/751/updates/fixes/atlas/./atlas.7.5.1.0.fixes/./7.5.1.0-WS-ATLAS-IFJR41201,http://public.dhe.ibm.com/software/websphere/bpm/repositories/server/bspace/751/updates/fixes/atlas/./atlas.7.5.1.0.fixes/./7.5.1.0-WS-ATLAS-IFJR41203,http://public.dhe.ibm.com/software/websphere/bpm/repositories/server/bpmadv/751/updates/fixes/bpm/./bpm.7.5.1.0.fixes/./7.5.1.0-WS-BPM-IFJR41195,http://public.dhe.ibm.com/software/websphere/bpm/reposito...\n\n\n\nNote: The Launchpad log file path is specific to your environment. For example: <WindowsTEMP_DIR>/Temp/1/IBM_LaunchPad_BPM_1322801669906/typical_install.log \n\n\nCAUSE\nA typical installation using LaunchPad completes the following tasks:. \n\n * Installs the product \n * Installs the recommended interim fixes from the external product repository. \n * Creates a profile \n\n\nAfter completing the product installation, Lauchpad invokes Installation Manager to download the recommended interim fixes from the external product repository. In some Windows environments, the Installation Manger never gets invoked and the Launchpad keeps waiting for the Installation Manager to complete the operation. \n\nThis issue has been identified as a product defect under APAR JR42324\n\n\nRESOLVING THE PROBLEM\nTo resolve this issue, see the following sections: \n\nResolving the problem if you see it hang \n\nAvoiding the problem in a new Windows environment \n\n \n\nResolving the problem if you see it hang \n\nTo resolve the problem you stop the Launchpad, complete the interim fix installation, and create a profile manually using the following steps. \n\n 1. Check the version information using the <BPMinstall>/bin/versioninfo command and make sure the product installation has been completed. You should see that the following packages are installed based on the versioninfo output: * WebSphere Application Server Version 7.0.0 Fix Pack 19 \n * WebSphere Application Server Feature Pack for XML \n * WebSphere Application Server Feature Pack for SCA (for IBM Business Process Manager Advanced only) \n * IBM Business Process Manager Version 7.5.1 product pack \n \n \n \n \n 2. Click Cancel on the Launchpad panel. If the Launchpad does not respond after few minutes, kill the process using Windows Task Manager.\n \n \n 3. Start the Installation Manger and install all the recommended interim fixes [http://www.ibm.com/support/docview.wss?uid=swg27023411].\n \n \n 4. Use the Profile Management tool (PMT) or the manageprofiles command to create the desired profile [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/index.jsp?topic=/com.ibm.wbpm.imuc.sbpm.doc/topics/ccnfg_profiles_create_aug.html] \n\n\nAvoiding the problem in new Windows environment \n\n \n\nThis problem is seen only for certain windows environments with external access to the Internet. You can use a custom installation [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/index.jsp?topic=/com.ibm.wbpm.imuc.sbpm.doc/topics/tins_custom_standard.html] where the product is installed using the Installation Manger interface and you will not encounter this problem. \n\n \n\nYou can avoid the problem by installing the patch for the launchpad defect JR42324. Use the instructions documented for the defect JR42324: Launchpad hangs at 41%. [http://www.ibm.com/support/docview.wss?uid=swg24032300]\n\nRELATED INFORMATION\n#Recommended fixes: IBM Business Process Manager 7.5.1 [http://www.ibm.com/support/docview.wss?uid=swg27023411]\nCustom installation: IBM Business Process Manager 7.5.1 [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/index.jsp?topic=/com.ibm.wbpm.imuc.sbpm.doc/topics/tins_custom_standard.html]\nCreating and augmenting profiles [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/index.jsp?topic=/com.ibm.wbpm.imuc.sbpm.doc/topics/ccnfg_profiles_create_aug.html]\nLauchpad patch JR42324 for 41% hang defect [http://www.ibm.com/support/docview.wss?uid=swg24032300]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Advanced Installation / Configuration 7.5.1 Business Integration IBM Business Process Manager Express Installation / Configuration Windows 7.5.1", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM Business Process Manager installation on AIX 6.1 with POWER 8 might fail to start if certain GUI libraries are not present. \n\nSYMPTOM\nIBM Business Process Manager Installation fails to start on AIX 6.1 with POWER 8, with the following error:\n\nJVMDUMP006I Processing dump event \"gpf\", detail \"\" - please wait.\nJVMDUMP032I JVM requested System dump using '/opt/hanminw/IM/core.20140424.011426.5308606.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/hanminw/IM/core.20140424.011426.5308606.0001.dmp\nJVMDUMP032I JVM requested Java dump using '/opt/hanminw/IM/javacore.20140424.011426.5308606.0002.txt' in response to an event\nJVMDUMP010I Java dump written to /opt/hanminw/IM/javacore.20140424.011426.5308606.0002.txt\nJVMDUMP032I JVM requested Snap dump using '/opt/hanminw/IM/Snap.20140424.011426.5308606.0003.trc' in response to an event\nJVMDUMP010I Snap dump written to /opt/hanminw/IM/Snap.20140424.011426.5308606.0003.trc\nJVMDUMP013I Processed dump event \"gpf\", detail \"\".\nSegmentation fault(coredump)\n\n\nCAUSE\nIBM Installation Manager requires GTK libraries to support the graphical user interface. If the environment does not have required library, or the library version is higher or lower than the requirement, Installation Manager fails when it is starting. \n\nRESOLVING THE PROBLEM\nInstall the required GTK libraries according to the Required gtk libraries for Installation Manager on AIX [http://www.ibm.com/support/docview.wss?uid=swg21631478] document.\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Installation / Configuration AIX 8.5.6, 8.5.5 \nPRODUCT ALIAS/SYNONYM\n BPM", " DOWNLOADABLE FILES\n\nABSTRACT\n Interim fixes, including fixes for IBM WebSphere Application Server, are required for several business process management products. \n\nDOWNLOAD DESCRIPTION\n\n\nTAB NAVIGATION\n * Installing the fix pack [http://www.ibm.com/support/docview.wss?uid=swg27046472]\n * Upgrading profiles [http://www.ibm.com/support/docview.wss?uid=swg27046471]\n * Recommended fixes [http://www.ibm.com/support/docview.wss?uid=swg24041216]- selected tab,\n * Post-installation tasks [http://www.ibm.com/support/docview.wss?uid=swg27047034]\n\n\nRecommended Interim Fixes\nThis document provides you with links to the interim fixes that are recommended for V8.5.0 Fix Pack 2 for the following products,: \n\n * IBM Business Process Manager Express \n * IBM Business Process Manager Standard \n * IBM Business Process Manager Advanced \n * IBM Business Process Manager Advanced – Process Server \n\nNote: You need to clear the Show recommended only option in Installation Manager to see the recommended WebSphere Application Server fixes. \n\n\nRecommended Interim fixes for IBM Business Process Manager Express V8.5.0.2 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Express&release=8.5.0.2&platform=All&function=recommended]\n\n\n\nRecommended Interim fixes for IBM Business Process Manager Standard V8.5.0.2 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Standard&release=8.5.0.2&platform=All&function=recommended]\n\n\n\nRecommended Interim fixes for IBM Business Process Manager Advanced V8.5.0.2 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Advanced&release=8.5.0.2&platform=All&function=recommended]\n\n\n\nRecommended Interim fixes for IBM Business Process Manager Advanced - Process Server V8.5.0.2 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Advanced&release=8.5.0.2&platform=All&function=recommended]\n\nINSTALLATION INSTRUCTIONS\nThe following links contain the download, installation, profile upgrade and optional post-installation instructions for the fix pack. You are strongly encouraged to read these documents prior to installing the fix pack and the interim fixes.\n\nURL LANGUAGE SIZE(Bytes) Fix pack download information [http://www.ibm.com/support/docview.wss?uid=swg24040683] English 9999 Install instructions [http://www.ibm.com/support/docview.wss?uid=swg27046472] English 9999 Profile upgrade instructions [http://www.ibm.com/support/docview.wss?uid=swg27046471] English 9999 Post-installation tasks [http://www.ibm.com/support/docview.wss?uid=swg27047034] English 9999 \n\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.0.2 Business Integration IBM Business Process Manager Express Installation / Configuration Linux, Windows 8.5.0.2 \nPRODUCT ALIAS/SYNONYM\n BPM", "wps; installation; proxy; installation manager; internet; hang; freeze TECHNOTE (FAQ)\n\nQUESTION\n How can I install WebSphere Process Server with IBM Installation Manager if I do not have an Internet connection or if my server uses a proxy? \n\nANSWER\nIBM Installation Manager generally requires connectivity to the Internet to be able to connect to the live repositories and retrieve information regarding the current features/fixes available for a particular product installation.\nIn cases where there is no internet connectivity, Installation Manager hangs during start up trying to access the http://public.dhe.ibm.com/software/websphere/repositories/ [http://public.dhe.ibm.com/software/websphere/repositories/] URL. This behavior includes cases when the server where installation is being attempted is behind a firewall and requires proxy server information to access the Internet. \n\nUsing IBM Installation Manager without an Internet connection \n\nUsing IBM Installation Manager when your Internet connection uses a proxy \n\n \n\n\n\nUSING IBM INSTALLATION MANAGER WITHOUT AN INTERNET CONNECTION\nIf you do not have an active Internet connection, complete one of the following tasks, depending on whether IBM Installation Manager is already installed. \n\nImportant: \n\n * If you are not logged in as root or if you do not have administrator privileges on the machine, you must use the userinst command in the steps instead of the install command.\n \n \n * After installing WebSphere Process Server using one of the procedures that follows, you might experience problems if you try to update, modify, or uninstall the software. These problems occur because the WebSphere Application Server, Service Component Architecture (SCA) and XML repository checks are not available as they require an active Internet connection. You can work around this problem by modifying Installation Manager preferences to include install_image/repository/repository.config, where install_image is either the mount point for the DVD or the directory in which you downloaded the installation images.\n \n \n * To prevent always needing the Installation image, you can instead download the following repositories:\n \n http://public.dhe.ibm.com/software/websphere/downloads/xml/import/xml.1.0.import.zip [http://public.dhe.ibm.com/software/websphere/downloads/xml/import/xml.1.0.import.zip]\n \n http://public.dhe.ibm.com/software/websphere/downloads/sca/import/sca.1.0.import.zip [http://public.dhe.ibm.com/software/websphere/downloads/sca/import/sca.1.0.import.zip]\n \n http://public.dhe.ibm.com/software/websphere/downloads/was/import/was.7.0.import.zip [http://public.dhe.ibm.com/software/websphere/downloads/was/import/was.7.0.import.zip]\n \n \n\n\n\nIBM Installation Manager is not installed and you have a downloaded installation package 1. Install IBM Installation Manager, as follows: 1. Change to the install_image/IM directory.\n \n \n 2. Remove the following entry from the install.xml and post-install.xml files:\n <repository location='http://public.dhe.ibm.com/software/websphere/repositories/'/>\n \n \n \n \n 2. Install IBM Installation Manager with the following command, where 'location' specifies the directory containing the install.xml file: \n install_image/IM/install -input location/install.xml\n \n \n 3. Install the product with the following command, where 'location' specifies the directory containing the post-install.xml file: \n install_image/IM/install -input location/post-install.xml \n \n \n\n\nIBM Installation Manager is not installed and you have the installation DVD 1. Copy the install.xml and post-install.xml files from the DVD to your local file system.\n \n \n 2. Remove the following entry from both files: \n <repository location='http://public.dhe.ibm.com/software/websphere/repositories/'/\n \n \n 3. Install IBM Installation Manager with the following command, where 'location' specifies the directory containing the install.xml file: \n iso_mount/IM/install -input location/install.xml\n \n \n 4. Install the product with the following command, where 'location' specifies the directory containing the post-install.xml file: \n iso_mount/IM/install -input location/post-install.xml\n \n \n\n\nIBM Installation Manager is installed 1. Start IBM Installation Manager with the IBMIM command. \n \n \n 2. Modify the Installation Manager repository, as follows: 1. Click File > Preferences > Repositories.\n \n \n 2. Clear the http://public.dhe.ibm.com/software/websphere/repositories [http://public.dhe.ibm.com/software/websphere/repositories] repository option.\n \n \n 3. Add the install_image/repository/repository.config repository and ensure that it is selected.\n \n \n \n \n 3. Install WebSphere Process Server.\n \n \n\nBack to top\n\n\nUSING IBM INSTALLATION MANAGER WITH A PROXY\n\nIf your Internet connection is configured to use a proxy, complete the following steps to use IBM Installation Manager: \n\nUsing the Installation Manager GUI \n\n 1. If IBM Installation Manager is not yet installed on your machine, install it and start it using one of the methods described in the \"Using Installation Manager without an Internet connection\" section of this document.\n \n \n 2. From within Installation Manager, click File > Preferences > Internet > HTTP Proxy.\n \n \n 3. Click Enable proxy server.\n \n \n 4. Enter the proxy server details for your particular environment.\n \n \n 5. Install WebSphere Process Server.\n \n \n\n\nUsing the silent installation mode 1. Change to the Agent data location directory (appDataLocation) for IBM Installation Manager. By default, this directory is located in C:\\Documents and Settings\\All Users\\Application Data\\ibm\\Installation Manager for Windows systems and in /var/ibm/InstallationManager/or /home/<user>/var/ibm/InstallationManager for Linux systems.\n \n \n 2. Make a back up copy of the com.ibm.cic.agent.core.prefs file in the appDataLocation/settings directory. \n \n \n 3. Set the proxy host preferences according to the Silent Installation Preferences Internet Keys [http://publib.boulder.ibm.com/infocenter/install/v1r2/topic/com.ibm.silentinstall12.doc/topics/r_silent_prefs.html#r_silent_prefs__internetKey] section. [http://publib.boulder.ibm.com/infocenter/install/v1r2/topic/com.ibm.silentinstall12.doc/topics/r_silent_prefs.html#r_silent_prefs__internetKey]The example illustrates the typical values for a proxy server named proxy.host.com using port 8080. Substitute the values particular to your proxy server and port. com.ibm.cic.common.core.preferences.http.proxyEnabled=true com.ibm.cic.common.core.preferences.http.proxyHost=proxy.host.com com.ibm.cic.common.core.preferences.http.proxyPort=8080 \n 4. Save the com.ibm.cic.agent.core.prefs file.\n \n \n 5. Use the documented procedure to silently install WebSphere Process Server.\n \n \n\nBack to top\n\n\nAdditional References: \n * Installation process for WebSphere Process Server v7.0 by a non-root user using the silent install method [http://www.ibm.com/support/docview.wss?uid=swg21417628] \n * Instructions for installing an interim fix for WebSphere Process Server (WPS) and IBM Business Process Manager (BPM) using the IBM Installation Manager [http://www.ibm.com/support/docview.wss?uid=swg21417656] \n * Installation Manager graphical environment issues on Solaris, Linux, AIX [http://www.ibm.com/support/docview.wss?uid=swg21330190]\n\nBack to top\n\n \n\nPRODUCT ALIAS/SYNONYM\n WPS", "upgrade; process portal; JR41549 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After you upgrade the database from IBM Business Process Manager Version 7.5.0.x to 7.5.1, you might find some messages that are similar to \"messge for key: [scoreboard.MyPerf.name] is not found\" in the left panel of Process Portal Console under the\"My ScoreBoards\" tab. \n\nSYMPTOM\nYou see the following problem in the Process Portal Console after you upgrade the database to Version 7.5.1: \n\n[/support/docview.wss?uid=swg21577551&amp;aid=1]\n\n\nENVIRONMENT\nThis problem does not occur in a new Version 7.5.1 installation or in a database that is created for new profiles.\n\n\n\nRESOLVING THE PROBLEM\nSee the following options that resolve this issue: \n\n \n\nThis problem is addressed in IBM Business Process Manager V7.5.1 Fix Pack 1. If you upgrade your environment from IBM Business Process Manager Version 7.5.0.x to 7.5.1 Fix Pack 1, you do not need to install JR41549, which is referenced in the other resolutions within this document. \n\nYou can use the IBM Business Process Manager 7.5.1 Fix Pack 1 [http://www.ibm.com/support/docview.wss?uid=swg24033036] images to upgrade from IBM Business Process Manager Version 7.5.0,x. Continue to follow instructions in the Upgrading from IBM Business Process Manager V7.5 [http://pic.dhe.ibm.com/infocenter/dmndhelp/v7r5m1/index.jsp?topic=/com.ibm.wbpm.imuc.doc/topics/tmig_upgrading_bpm.html] document within the product documentation to complete the profile, clusters, and database upgrade.\n\n\n\n\n\n\n\n\nIf you have installed Version 7.5.1 using either IBM Installation Manager or the silent installation method, but you have not run the upgrade_7x.bat or upgrade_7x.sh script to upgrade the Process Server database, complete the following steps: \n\n 1. Install Interim Fix JR41549. * IBM Business Process Manager Standard [http://www-933.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Standard&release=7.5.1.0&platform=All&function=fixId&fixids=7.5.1.0-WS-BPM-MultiOS-IFJR41549-STD&includeSupersedes=0&source=fc] \n * IBM Business Process Manager Express [http://www-933.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Express&release=7.5.1.0&platform=All&function=fixId&fixids=7.5.1.0-WS-BPM-MultiOS-IFJR41549-EXP&includeSupersedes=0&source=fc] \n * IBM Business Process Manager Advanced [http://www-933.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Advanced&release=7.5.1.0&platform=All&function=fixId&fixids=7.5.1.0-WS-BPM-MultiOS-IFJR41549-ADV&includeSupersedes=0&source=fc]\n \n \n \n \n 2. Upgrade the database using the upgrade_7x.bat or upgrade_7x.sh scripts. You can find the upgrade instructions in the Upgrading from IBM Business Process Manager V7.5 to IBM Business Process Manager V7.5.1 [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/index.jsp?topic=/com.ibm.wbpm.imuc.doc/topics/tmig_upgrading_bpm.html] topic in the product documentation.\n\n\n\n\n\n\n\nIf you already installed binary to 7.5.1 and upgraded the database and see the problem in the Process Portal Console, complete the following steps: \n\n 1. Stop the server.\n \n \n 2. Install the Interim Fix JR41549. * IBM Business Process Manager Standard [http://www-933.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Standard&release=7.5.1.0&platform=All&function=fixId&fixids=7.5.1.0-WS-BPM-MultiOS-IFJR41549-STD&includeSupersedes=0&source=fc] \n * IBM Business Process Manager Express [http://www-933.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Express&release=7.5.1.0&platform=All&function=fixId&fixids=7.5.1.0-WS-BPM-MultiOS-IFJR41549-EXP&includeSupersedes=0&source=fc] \n * IBM Business Process Manager Advanced [http://www-933.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Advanced&release=7.5.1.0&platform=All&function=fixId&fixids=7.5.1.0-WS-BPM-MultiOS-IFJR41549-ADV&includeSupersedes=0&source=fc]\n \n \n \n \n 3. Backup the ${server_root}/BPM/base/profile/actions/bootstrapData.ant file.\n \n \n 4. In the bootstrapData.ant file, find the \"main\" target, and comment out the following ant calls: \"importSystemToolkit\", \"importProcessPortal\", \"importSamples\"\n \n For example:\n \n <target name=\"main\" depends=\"init.config\">\n <bootstrap>\n <!--\n <antcall target=\"importSystemToolkit\"/>\n <antcall target=\"importProcessPortal\"/>\n -->\n <antcall target=\"importRBGs\"/>\n <!--\n <antcall target=\"importSamples\"/>\n -->\n </bootstrap>\n </target>\n \n \n 5. Run the BootstrapProcessServerData command. For more information on this command, see the Loading the database with system information [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/index.jsp?topic=/com.ibm.wbpm.imuc.ebpm.doc/topics/tcnfg_bootstrap.html] topic in the product documentation.\n \n \n 6. Start the server.\n \n \n 7. Confirm that the problem has been resolved.\n \n \n 8. Restore the backup of the bootstrapData.ant file that you saved in step 3 .\n\n\nNote: The bootstrapData.ant file is used while loading the system data into the database. It is very important that you restore the original bootstrapData.ant file. If you do not restore this file, you will see a failure next time you create a new profile or when you run the bootstrapProcessServerData command to load the system data. \n\nRELATED INFORMATION\n V7.5.1 Profile upgrade instructions [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/index.jsp?topic=/com.ibm.wbpm.imuc.doc/topics/tmig_upgrading_bpm.html]\nbootstrapProcessServerData.sh command help [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/index.jsp?topic=/com.ibm.wbpm.imuc.ebpm.doc/topics/tcnfg_bootstrap.html]\nInterim Fix JR41549 [http://www.ibm.com/support/docview.wss?uid=swg1JR41549]\n\n\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 7.5.1 Business Integration IBM Business Process Manager Express Installation / Configuration Linux, Windows 7.5.1" ]

[ [ "3a", "wps; installation; proxy; installation manager; internet; hang; freeze TECHNOTE (FAQ) QUESTION" ], [ "3b", " How can I install WebSphere Process Server with IBM Installation Manager if I do not have an Internet connection or if my server uses a proxy? ANSWER" ], [ "3c", "IBM Installation Manager generally requires connectivity to the Internet to be able to connect to the live repositories and retrieve information regarding the current features/fixes available for a particular product installation." ], [ "3d", "In cases where there is no internet connectivity, Installation Manager hangs during start up trying to access the http://public.dhe.ibm.com/software/websphere/repositories/ [http://public.dhe.ibm.com/software/websphere/repositories/] URL." ], [ "3e", "This behavior includes cases when the server where installation is being attempted is behind a firewall and requires proxy server information to access the Internet." ], [ "3f", "Using IBM Installation Manager without an Internet connection" ], [ "3g", "Using IBM Installation Manager when your Internet connection uses a proxy" ], [ "3h", "USING IBM INSTALLATION MANAGER WITHOUT AN INTERNET CONNECTION" ], [ "3i", "If you do not have an active Internet connection, complete one of the following tasks, depending on whether IBM Installation Manager is already installed. Important:" ], [ "3j", " * If you are not logged in as root or if you do not have administrator privileges on the machine, you must use the userinst command in the steps instead of the install command." ], [ "3k", " * After installing WebSphere Process Server using one of the procedures that follows, you might experience problems if you try to update, modify, or uninstall the software." ], [ "3l", "These problems occur because the WebSphere Application Server, Service Component Architecture (SCA) and XML repository checks are not available as they require an active Internet connection." ], [ "3m", "You can work around this problem by modifying Installation Manager preferences to include install_image/repository/repository.config, where install_image is either the mount point for the DVD or the directory in which you downloaded the installation images." ], [ "3n", " * To prevent always needing the Installation image, you can instead download the following repositories:" ], [ "3o", " http://public.dhe.ibm.com/software/websphere/downloads/xml/import/xml.1.0.import.zip [http://public.dhe.ibm.com/software/websphere/downloads/xml/import/xml.1.0.import.zip]" ], [ "3p", " http://public.dhe.ibm.com/software/websphere/downloads/sca/import/sca.1.0.import.zip [http://public.dhe.ibm.com/software/websphere/downloads/sca/import/sca.1.0.import.zip]" ], [ "3q", " http://public.dhe.ibm.com/software/websphere/downloads/was/import/was.7.0.import.zip [http://public.dhe.ibm.com/software/websphere/downloads/was/import/was.7.0.import.zip]" ], [ "3r", "IBM Installation Manager is not installed and you have a downloaded installation package 1." ], [ "3s", "Install IBM Installation Manager, as follows: 1." ], [ "3t", "Change to the install_image/IM directory." ], [ "3u", " 2." ], [ "3v", "Remove the following entry from the install.xml and post-install.xml files:" ], [ "3w", " <repository location='http://public.dhe.ibm.com/software/websphere/repositories/'/> 2." ], [ "3x", "Install IBM Installation Manager with the following command, where 'location' specifies the directory containing the install.xml file:" ], [ "3y", " install_image/IM/install -input location/install.xml 3." ], [ "3z", "Install the product with the following command, where 'location' specifies the directory containing the post-install.xml file:" ], [ "3aa", " install_image/IM/install -input location/post-install.xml" ], [ "3ab", "IBM Installation Manager is not installed and you have the installation DVD 1." ], [ "3ac", "Copy the install.xml and post-install.xml files from the DVD to your local file system. 2." ], [ "3ad", "Remove the following entry from both files:" ], [ "3ae", " <repository location='http://public.dhe.ibm.com/software/websphere/repositories/'/ 3." ], [ "3af", "Install IBM Installation Manager with the following command, where 'location' specifies the directory containing the install.xml file:" ], [ "3ag", " iso_mount/IM/install -input location/install.xml 4." ], [ "3ah", "Install the product with the following command, where 'location' specifies the directory containing the post-install.xml file:" ], [ "3ai", " iso_mount/IM/install -input location/post-install.xml" ], [ "3aj", "IBM Installation Manager is installed 1." ], [ "3ak", "Start IBM Installation Manager with the IBMIM command. 2." ], [ "3al", "Modify the Installation Manager repository, as follows: 1." ], [ "3am", "Click File > Preferences > Repositories." ], [ "3an", " 2." ], [ "3ao", "Clear the http://public.dhe.ibm.com/software/websphere/repositories [http://public.dhe.ibm.com/software/websphere/repositories] repository option." ], [ "3ap", " 3." ], [ "3aq", "Add the install_image/repository/repository.config repository and ensure that it is selected. 3." ], [ "3ar", "Install WebSphere Process Server." ], [ "3as", "Back to top" ], [ "3at", "USING IBM INSTALLATION MANAGER WITH A PROXY" ], [ "3au", "If your Internet connection is configured to use a proxy, complete the following steps to use IBM Installation Manager:" ], [ "3av", "Using the Installation Manager GUI 1." ], [ "3aw", "If IBM Installation Manager is not yet installed on your machine, install it and start it using one of the methods described in the \"Using Installation Manager without an Internet connection\" section of this document. 2." ], [ "3ax", "From within Installation Manager, click File > Preferences > Internet > HTTP Proxy. 3." ], [ "3ay", "Click Enable proxy server. 4." ], [ "3az", "Enter the proxy server details for your particular environment. 5." ], [ "3ba", "Install WebSphere Process Server." ], [ "3bb", "Using the silent installation mode 1." ], [ "3bc", "Change to the Agent data location directory (appDataLocation) for IBM Installation Manager." ], [ "3bd", "By default, this directory is located in C:\\Documents and Settings\\All Users\\Application Data\\ibm\\Installation Manager for Windows systems and in /var/ibm/InstallationManager/or /home/<user>/var/ibm/InstallationManager for Linux systems. 2." ], [ "3be", "Make a back up copy of the com.ibm.cic.agent.core.prefs file in the appDataLocation/settings directory. 3." ], [ "3bf", "Set the proxy host preferences according to the Silent Installation Preferences Internet Keys [http://publib.boulder.ibm.com/infocenter/install/v1r2/topic/com.ibm.silentinstall12.doc/topics/r_silent_prefs.html#r_silent_prefs__internetKey] section." ], [ "3bg", "[http://publib.boulder.ibm.com/infocenter/install/v1r2/topic/com.ibm.silentinstall12.doc/topics/r_silent_prefs.html#r_silent_prefs__internetKey]The example illustrates the typical values for a proxy server named proxy.host.com using port 8080." ], [ "3bh", "Substitute the values particular to your proxy server and port." ], [ "3bi", "com.ibm.cic.common.core.preferences.http.proxyEnabled=true com.ibm.cic.common.core.preferences.http.proxyHost=proxy.host.com com.ibm.cic.common.core.preferences.http.proxyPort=8080 4." ], [ "3bj", "Save the com.ibm.cic.agent.core.prefs file. 5." ], [ "3bk", "Use the documented procedure to silently install WebSphere Process Server." ], [ "3bl", "Back to top Additional References:" ], [ "3bm", " * Installation process for WebSphere Process Server v7.0 by a non-root user using the silent install method [http://www.ibm.com/support/docview.wss?uid=swg21417628]" ], [ "3bn", " * Instructions for installing an interim fix for WebSphere Process Server (WPS) and IBM Business Process Manager (BPM) using the IBM Installation Manager [http://www.ibm.com/support/docview.wss?uid=swg21417656]" ], [ "3bo", " * Installation Manager graphical environment issues on Solaris, Linux, AIX [http://www.ibm.com/support/docview.wss?uid=swg21330190]" ], [ "3bp", "Back to top PRODUCT ALIAS/SYNONYM WPS" ] ]

[ "3ak", "3al", "3am" ]

[ " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The command line returns a deployment failure message- \"The application deployment failed\" -even though messages from the admininstration tool interface state that the EAR file deployed correctly for WebSphere Appliation Server 8.5.5. \n\nSYMPTOM\nThis issue occurs while running the Configuration Manager deploy application task in silent mode, for example, by using the following command:\n./configmgr_cl execute -task deployapplication -profile <cmuiprofile> \n\nThe task shows the following failure message even though the administration tool interface messages state that the deployment completed successfully.\n\nThe application deployment failed.\nWASX7209I: Connected to process \"server1\" on node node1 using SOAP connector; The type of process is: UnManagedProcess\nTurn off RMI/IIOP SSL\nconfigure server transaction time out\nADMA5016I: Installation of FileNetEngine started.\nADMA5058I: Application and module versions are validated with versions of deployment targets.\nADMA5018I: The EJBDeploy program is running on file /tmp/app4972436744907325454.ear.\nStarting workbench.\nEJB Deploy configuration directory: /opt/IBM/WebSphere/AppServer/profiles/default/ejbdeploy/configuration/\nframework search path: /opt/IBM/WebSphere/AppServer/deploytool/itp/plugins\nbuild:RAD851-I20121103_1921\nCreating the project.\nDeploying jar Engine-ejb-ws\nGenerating deployment code\nDeploying jar peengine-ejb\nInvoking RMIC.\nokToInvokeInJVM true\nWriting output file\nShutting down workbench.\nEJBDeploy complete.\n0 Errors, 0 Warnings, 0 Informational Messages\nADMA5007I: The EJBDeploy program completed on file /tmp/app4972436744907325454.ear\nADMA5005I: The application FileNetEngine is configured in the WebSphere Application Server repository.\nADMA5005I: The application FileNetEngine is configured in the WebSphere Application Server repository.\nADMA5081I: The bootstrap address for client module is configured in the WebSphere Application Server repository.\nADMA5053I: The library references for the installed optional package are created.\nADMA5005I: The application FileNetEngine is configured in the WebSphere Application Server repository.\nADMA5001I: The application binaries are saved in /opt/IBM/WebSphere/AppServer/profiles/default/wstemp/Script15b3ab9b6b1/workspace/cells/cell1/applications/FileNetEngine.ear/FileNetEngine.ear\nADMA5005I: The application FileNetEngine is configured in the WebSphere Application Server repository.\nSECJ0400I: Successfully updated the application FileNetEngine with the appContextIDForSecurity information.\nADMA5005I: The application FileNetEngine is configured in the WebSphere Application Server repository.\nADMA5005I: The application FileNetEngine is configured in the WebSphere Application Server repository.\nADMA5113I: Activation plan created successfully.\nADMA5011I: The cleanup of the temp directory for application FileNetEngine is complete.\nADMA5013I: Application FileNetEngine installed successfully.\nDeployment completed\n\n\nCAUSE\nThis error message is seen when the ApplicationServerVersion property value in the applicationserver.xml file is set to 8.5.5 instead of the correct value 8.5. The WebSphere Application Server version value should include only the first two numbers. \n\n\n\nRESOLVING THE PROBLEM\nTo avoid the misleading error message, edit the applicationserver.xml file to set the ApplicationServerVersion property value to 8.5 instead of 8.5.5: \n\n\n<property name=\"ApplicationServerVersion\">\n<value>8.5</value>\n<description>Enter one of the following WebSphere Application Server version values: 7.0, 8.0, 8.5, 9.0</description>\n<displayName>Application server version</displayName>\n</property>\n\nTo ensure that the deployment was successful, rerun the deployment task after you correct the property value in the applicationserver.xml file.", "searchbases; searchfilter; wp-change-portal-admin-user; group; ConfigEngine; change admin group TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n \nWhen you run the wp-change-portal-admin-user task in IBM WebSphere Portal, the task fails with a message that the group does not exist. \n\nSYMPTOM\n \n\nThe ConfigTrace.log contains the following:\n\n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * [echo] Validating if group 'cn=groupname,ou=orgunit1,dc=yourcompany,dc=com' exists. \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * Given user group 'cn=groupname,ou=orgunit1,dc=yourcompany,dc=com' does not exist.\n\n\nCAUSE\nThe Virtual Member Manager (VMM) is not correctly configured to find the new administrative group. This can occur if the LDAP structure changes between when you set up the WebSphere Portal security configuration and when you run wp-change-portal-admin-user.\n\nRESOLVING THE PROBLEM\n \n\nVerify the VMM configuration. Specifically, confirm that the newAdminGroupId can be found given the searchFilter and searchBases in the wimconfig.xml file (<wp_profile>/config/cells/<cellname>/wim/config/):\n\n\n * \n * <config:objectClasses>groupOfUniqueNames</config:objectClasses> \n * \n * \n * \n\n\nLDAPsearch can be used to validate these settings as follows: \n * \n * password\n * \n * LDAP port\n * \n * yourcompany\n * \n * groupOfUniqueNames\n * \n * \n * \n * \n\nFor the task to run successfully, the newAdminGroupId should be contained in the LDAPsearch results. If it is not, your LDAP administrator should advise you on determining the correct settings for searchFilter and searchBases. \n\nIn this example, the searchBases do not allow VMM to find the group and must be corrected. To change these settings: \n * \n * \n * \n * searchFilter\n * \n * searchBases\n * \n * \n * \n * \n * \n * \n * \n * standalone.ldap.et.group.searchFilter / standalone.ldap.et.group.searchBases \n - o r- \n federated.ldap.et.group.searchFilter / federated.ldap.et.group.searchBases \n * If you later run a task that updates the security configuration, the changes you made in Step 2 above will not be overwritten.", " FIXES ARE AVAILABLE\nRational Application Developer for WebSphere Software 8.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24032855]\nRational Software Architect Interim Fix 1 for 8.0.4.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24036852]\nRational Software Architect for WebSphere Software Interim Fix 1 for 8.0.4.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24036853]\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 * Abstract:\n \n Attempts to validate a project result in error: 'EJB reference\n or EJB local reference with name 'EJB/mybean' not found'\n \n Problem:\n \n Using IBM Rational Application Developer v8.0.4 and IBM\n WebSphere Application server v7.0.0.19:\n \n 1. Create an EJB 3.0 project called MyEJB with client project\n MyEJBClient, associated with the EAR 5 project called MyEJBEAR\n 2. Add a Stateless session EJB with code similar to the\n following:\n \n package com;\n import javax.ejb.Stateless;\n @Stateless(name='EJB/mybean')\n public class Bean implements BeanRemote {\n public Bean() {\n }\n }\n and the required remote interface com.BeanRemote.\n \n 3. Create a Dynamic Web project 2.5 called MyWeb, associated\n with a separate EAR 5 project called MyWebEAR\n 4. Add the project MyEJBClient as a Utility Module to MyWebEAR\n 5. Configure MyEJBClient in the Deployment Assembly page of\n MyWeb\n 6. Add a Servlet Filter to MyWeb. The source file of the Servlet\n Filter should be placed in MyEJBClient, and the code should\n reference the EJB by dependency injection as follows:\n \n package com;\n import java.io.IOException;\n import javax.ejb.EJB;\n import javax.servlet.*\n public class Test1 implements Filter{\n @EJB(name='EJB/mybean') BeanRemote myRemote;\n @Override\n public void destroy() {}\n @Override\n public void doFilter(ServletRequest arg0, ServletResponse\n arg1,FilterChain arg2) throws IOException, ServletException {}\n @Override\n public void init(FilterConfig arg0) throws ServletException\n {System.out.println('Servlet Filter\n init:'+myRemote.toString());}}\n 7. Right click on project MyWeb,and select:\n Java EE?Generate WebSphere Bindings Deployment Descriptor\n 8. In the file ibm-web-bnd.xml add the line that specifies the\n binding to the Remote EJB located in a separate EAR:\n ?ejb-ref name='EJB/mybean'\n binding-name='ejb/MyEJBEAR/MyEJB.jar/EJB/mybean#com.BeanRemote'\n /?\n \n The resulting web bindings validator will report the following\n error:\n \n EJB reference or EJB local reference with name 'EJB/mybean' not\n found on the file: /MyWeb/WebContent/WEB-INF/ibm-web-bnd.xml\n \n The application cannot be published to WebSphere Application\n Server because of this validation error.\n \n Local fix:\n \n 1. Navigate to Windows ? Preferences ? Validator\n 2. Disable the WebSphere Web bindings Validator\n \n The validation error will disappear and the application will\n publish correctly.\n \n Note that when the target of the reference is in a separate\n Enterprise Archive then the binding is required. If the binding\n is missing you will get the following error from the server:\n \n [3/14/12 15:32:50:533 CET] 00000019 annotation E\n com.ibm.ws.webcontainer.annotation.WASAnnotationHelper inject\n exception while injecting resource --? [InjectionTargetField=\n com.BeanRemote com.Test1.myRemote]\n \n com.ibm.wsspi.injectionengine.InjectionException: The\n com.ibm.ws.ejbcontainer.injection.factory.EJBLinkObjectFactory\n factory encountered a problem getting the object instance for\n the Reference:com.BeanRemote binding object.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n Validation error (EJB reference not found) prevents\n publishing to a WebSphere Application Server\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * This APAR is fixed in Rational Application Developer\n v8.0.4.1.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM60400\n \n \n * REPORTED COMPONENT NAME\n RATL APP DEV WI\n \n \n * REPORTED COMPONENT ID\n 5724J1901\n \n \n * REPORTED RELEASE\n 804\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-03-14\n \n \n * CLOSED DATE\n 2012-05-15\n \n \n * LAST MODIFIED DATE\n 2012-05-15\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 RATL APP DEV WI\n \n \n * FIXED COMPONENT ID\n 5724J1901\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R804 PSN\n UP", " DIRECT LINK TO FIX\n8.5.0.0-WCM-IFPI57013-CF09 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FLotus%2FWorkplace+Web+Content+Management&fixids=8.5.0.0-WCM-IFPI57013-CF09&source=SAR]\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * IBM WebSphere Portal and IBM Web Content Manager V8.5.0.0 CF08\n and CF09 applyCF command may fail when executed on clustered\n environments. This issue may also occur on CF05, CF06 and CF07\n when the equivalent APPLY-FIX ConfigEngine task is being\n executed in order to complete the CF installation.\n \n The following error can be seen in the ConfigTrace.log file when\n the applyCF command or APPLY-FIX task fails:\n Target started: wcm-run-ejb-task:\n ....\n [java] java.rmi.NoSuchObjectException: CORBA OBJECT_NOT_EXIST\n 0x0 No; nested exception is:\n [java] org.omg.CORBA.OBJECT_NOT_EXIST:\n ....\n [java] >> org.omg.CORBA.OBJECT_NOT_EXIST:\n java.rmi.NoSuchObjectException:\n Stateful bean BeanId(wcm-remote-admin-ejb#wcm-remote-admin-ejb\n .jar#MigrationService, .... was removed or timed out.\n \n or\n \n Target started: wcm-run-ejb-task:\n ....\n [java] java.rmi.MarshalException: CORBA MARSHAL 0x4942f89a No;\n nested exception is:\n [java] org.omg.CORBA.MARSHAL: Unable to read value from\n underlying bridge : Mismatched serialization UIDs : Source\n (RepId RMI:com.ibm.workplace.wcm.app.migration.ejb\n .MigrationResult .... whereas Target (RepId\n RMI:com.ibm.workplace.wcm.app.migration.ejb.MigrationResult ....\n [java] Caused by: org.omg.CORBA.MARSHAL: Unable to read value\n from underlying bridge : Mismatched serialization UIDs : Source\n (RepId RMI:com.ibm.workplace.wcm.app.migration.ejb\n .MigrationResult ...\n [java] Caused by: org.omg.CORBA.MARSHAL: Unable to read value\n from underlying bridge : Mismatched serialization UIDs ...\n [java] Caused by: java.io.IOException: Mismatched serialization\n UIDs : Source (RepId RMI:com.ibm.workplace.wcm.app.migration.ejb\n .MigrationResult ....\n \n \n \n \n \n\nLOCAL FIX\n * Stop WebSphere Portal on all remaining cluster node members and\n then attempt to re-run the applyCF command again on the failing\n node.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * IBM WebSphere Portal and IBM Web Content Manager V8.5.0.0 CF08\n and CF09 applyCF command may fail when executed on clustered\n environments. This issue may also occur on CF05, CF06 and CF07\n when the equivalent APPLY-FIX ConfigEngine task is being\n executed in order to complete the CF installation.\n \n The following error can be seen in the ConfigTrace.log file when\n the applyCF command or APPLY-FIX task fails:\n Target started: wcm-run-ejb-task:\n ....\n [java] java.rmi.NoSuchObjectException: CORBA OBJECT_NOT_EXIST\n 0x0 No; nested exception is:\n [java] org.omg.CORBA.OBJECT_NOT_EXIST:\n ....\n [java] >> org.omg.CORBA.OBJECT_NOT_EXIST:\n java.rmi.NoSuchObjectException:\n Stateful bean BeanId(wcm-remote-admin-ejb#wcm-remote-admin-ejb\n .jar#MigrationService, .... was removed or timed out.\n \n or\n \n Target started: wcm-run-ejb-task:\n ....\n [java] java.rmi.MarshalException: CORBA MARSHAL 0x4942f89a No;\n nested exception is:\n [java] org.omg.CORBA.MARSHAL: Unable to read value from\n underlying bridge : Mismatched serialization UIDs : Source\n (RepId RMI:com.ibm.workplace.wcm.app.migration.ejb\n .MigrationResult .... whereas Target (RepId\n RMI:com.ibm.workplace.wcm.app.migration.ejb.MigrationResult ....\n [java] Caused by: org.omg.CORBA.MARSHAL: Unable to read value\n from underlying bridge : Mismatched serialization UIDs : Source\n (RepId RMI:com.ibm.workplace.wcm.app.migration.ejb\n .MigrationResult ...\n [java] Caused by: org.omg.CORBA.MARSHAL: Unable to read value\n from underlying bridge : Mismatched serialization UIDs ...\n [java] Caused by: java.io.IOException: Mismatched serialization\n UIDs : Source (RepId RMI:com.ibm.workplace.wcm.app.migration.ejb\n .MigrationResult ....\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * If the current node of the cluster that is being updated does\n not hold the lease to WPSTaskScheduler (wps/Scheduler), then all\n remote EBJ tasks from WCM when issued will get executed on a\n different node member.\n \n And if the none member where the WCM EJB tasks is being executed\n on is at different CF level, then the wcm-run-ejb-task will fail\n with the error messages listed above.\n \n To overcome this, all usages of the wcm-run-ejb-task target\n within the applyCF has been replaced with alternative mechanism\n that no longer relies upon EJB tasks.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI57013\n \n \n * REPORTED COMPONENT NAME\n LOTUS WEB CONT\n \n \n * REPORTED COMPONENT ID\n 5724I2900\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 2016-02-10\n \n \n * CLOSED DATE\n 2016-02-18\n \n \n * LAST MODIFIED DATE\n 2016-02-18\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 LOTUS WEB CONT\n \n \n * FIXED COMPONENT ID\n 5724I2900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R850 PSY\n UP", " 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:<host name>:<port number>\". \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 name>:host=<host name>,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 <node name> using SOAP connector; The type of process is: DeploymentManager \n [wsadmin] 'dmgr(cells/<cell name>/nodes/<node name>/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 * <serverEntries serverDisplayName=\"dmgr\" serverName=\"dmgr\" serverType=\"DEPLOYMENT_MANAGER\" xmi:id=\"ServerEntry_1\"> \n * <deployedApplications>\n * \n * ...\n * (contains no references to WIMSYSTEM.ear) \n \n * \n * <serverEntries serverName=\"WebSphere_Portal\" serverType=\"APPLICATION_SERVER\" \n * ...\n * \n * <deployedApplications>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]" ]

[ [ "4a", " TECHNOTE (TROUBLESHOOTING) PROBLEM" ], [ "4b", "The ConfigEngine wp-add-property fails with the following error:" ], [ "4c", "Cannot find EJB: ejb/com/ibm/websphere/wim/ejb/WIMServiceHome" ], [ "4d", "[wplc-add-property] javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: \"corbaloc:iiop:<host name>:<port number>\". CAUSE" ], [ "4e", "In a cluster, the .ear file must be installed on the Deployment Manager (DMGR)." ], [ "4f", "For more information, refer to Document #1358381 [http://www.ibm.com/support/docview.wss?rs=899&uid=swg21358381]." ], [ "4g", "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. ENVIRONMENT" ], [ "4h", "Clustered WebSphere Portal" ], [ "4i", "DIAGNOSING THE PROBLEM" ], [ "4j", "-- Confirm that any bootstrap address information in the URL is correct and that the target name server is running." ], [ "4k", "A bootstrap address with no port specification defaults to port 2809." ], [ "4l", "Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration." ], [ "4m", "[Root exception is org.omg.CORBA.TRANSIENT: java.net.UnknownHostException: <host name>:host=<host name>,port=9809 vmcid: IBM minor code: E02 completed: No]" ], [ "4n", "-- Check the results of the wp-la-install-ear file in the ConfigTrace.log to determine if the .ear file was already installed:" ], [ "4o", " * Command line arguments: ... wp-la-install-ear *" ], [ "4p", " * ... *" ], [ "4q", " * Target started: wp-la-install-ear * *" ], [ "4r", " * wp-la-install-ear: *" ], [ "4s", " * ... *" ], [ "4t", " * [wplc-create-ear] *" ], [ "4u", " * earfile=\"/prod/sys/Portal61/WebSphere/AppServer/systemApps/wim.ear/wimejb.jar\" *" ], [ "4v", " * [wplc-create-ear] null" ], [ "4w", " * [wsadmin] WASX7209I: Connected to process \"dmgr\" on node <node name> using SOAP connector; The type of process is: DeploymentManager" ], [ "4x", " [wsadmin] 'dmgr(cells/<cell name>/nodes/<node name>/servers/dmgr|server.xml#Server_1)'" ], [ "4y", " [wsadmin] Enterprise application WIMSYSTEM already exists." ], [ "4z", " ..." ], [ "4aa", " * BUILD SUCCESSFUL" ], [ "4ab", "-- Inspect the serverindex.xml files to confirm that the .ear file is installed on a non-DMGR node in the cluster: *" ], [ "4ac", " * <serverEntries serverDisplayName=\"dmgr\" serverName=\"dmgr\" serverType=\"DEPLOYMENT_MANAGER\" xmi:id=\"ServerEntry_1\">" ], [ "4ad", " * <deployedApplications> *" ], [ "4ae", " * ..." ], [ "4af", " * (contains no references to WIMSYSTEM.ear) *" ], [ "4ag", " * <serverEntries serverName=\"WebSphere_Portal\" serverType=\"APPLICATION_SERVER\"" ], [ "4ah", " * ... *" ], [ "4ai", " * <deployedApplications>WIMSYSTEM.ear/deployments/WIMSYSTEM</deployedApplcations>" ], [ "4aj", "RESOLVING THE PROBLEM" ], [ "4ak", "You must first uninstall the WIMSYSTEM enterprise application from the WebSphere_Portal server (using the WebSphere Administrative console)." ], [ "4al", "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. RELATED INFORMATION" ], [ "4am", " Incorrect providerURL causes wp-add-property failure [http://www.ibm.com/support/docview.wss?uid=swg21358381]" ] ]

[ "4a", "4d", "4e", "4g", "4h", "4j", "4m", "4o", "4q", "4w", "4x", "4y", "4ab", "4ak", "4al" ]

[ " FLASH (ALERT)\n\nABSTRACT\n IBM Mobile Connect is not vulnerable to the Bash vulnerabilities that have been referred to as “Bash Bug” or “Shellshock” and the two memory corruption vulnerabilities. \n\nCONTENT\nIBM Mobile Connect 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).\nIBM recommends that you review your entire environment to identify vulnerable releases of Bash including your Operating Systems and take appropriate mitigation and remediation actions. Please contact your Operating System provider for more information.\n\n\n\n\n\n\nChange History: November 6, 2014 - original version published.", "CVE-2014-6271 CVE-2014-7169 DataPower Bash FLASH (ALERT)\n\nABSTRACT\n DataPower is not vulnerable to the Bash vulnerabilities that have been referred to as “Bash Bug” or “Shellshock” and the two memory corruption vulnerabilities. \n\nCONTENT\nDataPower does not use Bash anywhere. Hence it is not impacted by any of the Bash vulnerabilities. \n\nIn particular, DataPower in all editions and all platforms is NOT vulnerable to the Bash vulnerabilities: CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277, and CVE-2014-6278. \n\nIBM recommends that you review your entire environment to identify vulnerable releases of Bash and take appropriate mitigation and remediation actions.", " SECURITY BULLETIN\n\nSUMMARY\n Six Bash vulnerabilities were disclosed in September 2014. This bulletin addresses the vulnerabilities that have been referred to as “Bash Bug” or “Shellshock” and two memory corruption vulnerabilities. Bash is used by IBM PureData™ System for Transactions. \n\nVULNERABILITY DETAILS\nCVE-ID: CVE-2014-6271 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6271]\n\nDESCRIPTION: GNU Bash could allow a remote attacker to execute arbitrary commands on the system, caused by an error when evaluating specially-crafted environment variables passed to it by the bash functionality. An attacker could exploit this vulnerability to write to files and execute arbitrary commands on the system.\n\nCVSS Base Score: 10.0\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/96153 [https://exchange.xforce.ibmcloud.com/vulnerabilities/96153] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:C/I:C/A:C)\n\n\nCVE-ID: CVE-2014-7169 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-7169]\n\nDESCRIPTION: GNU Bash could allow a remote attacker to execute arbitrary commands on the system, caused by an incomplete fix related to malformed function definitions in the values of environment variables. An attacker could exploit this vulnerability using attack vectors involving the ForceCommand feature in OpenSSH sshd, the mod_cgi and mod_cgid modules in the Apache HTTP Server to write to files and execute arbitrary commands on the system.\n\nCVSS Base Score: 10.0\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/96209 [https://exchange.xforce.ibmcloud.com/vulnerabilities/96209] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:C/I:C/A:C)\n\n\nCVE-ID: CVE-2014-7186 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-7186]\n\nDESCRIPTION: GNU Bash could allow a local attacker to execute arbitrary code on the system, caused by an out-of-bounds memory access while handling redir_stack. An attacker could exploit this vulnerability to execute arbitrary code on the system or cause a denial of service.\n\nCVSS Base Score: 4.6\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/96237 [https://exchange.xforce.ibmcloud.com/vulnerabilities/96237] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:L/AC:L/Au:N/C:P/I:P/A:P)\n\n\nCVE-ID: CVE-2014-7187 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-7187]\n\nDESCRIPTION: GNU Bash could allow a local attacker to execute arbitrary code on the system, caused by an off-by-one-error when handling deeply nested flow control constructs. An attacker could exploit this vulnerability to execute arbitrary code on the system or cause a denial of service.\n\nCVSS Base Score: 4.6\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/96238 [https://exchange.xforce.ibmcloud.com/vulnerabilities/96238] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:L/AC:L/Au:N/C:P/I:P/A:P)\n\n\nCVE-ID: CVE-2014-6277 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6277]\n\nDESCRIPTION: GNU Bash could allow a remote attacker to execute arbitrary code on the system, caused by an incomplete fix related to the failure to properly parse function definitions in the values of environment variables. An attacker could exploit this vulnerability using attack vectors involving the ForceCommand feature in OpenSSH sshd, the mod_cgi and mod_cgid modules in the Apache HTTP Server to execute arbitrary code on the system or cause a denial of service.\n\nCVSS Base Score: 10.0\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/96686 [https://exchange.xforce.ibmcloud.com/vulnerabilities/96686] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:C/I:C/A:C)\n\n\nCVE-ID: CVE-2014-6278 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6278]\n\nDESCRIPTION: GNU Bash could allow a remote attacker to execute arbitrary code on the system, caused by an incomplete fix related to the parsing of user scripts. An attacker could exploit this vulnerability to execute arbitrary code on the system or cause a denial of service.\n\nCVSS Base Score: 10.0\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/96687 [https://exchange.xforce.ibmcloud.com/vulnerabilities/96687] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:C/I:C/A:C)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM PureData System for Transactions: V1.0\n\nREMEDIATION/FIXES\nTo obtain a fix for these vulnerabilities, contact IBM Support.\n\nIn the United States and Canada dial 1-800-IBM-SERV \nView the support contacts for other countries [http://www.ibm.com/planetwide/] outside of the United States. \nElectronically open a Service Request [http://www.ibm.com/software/data/db2/support/db2_9/probsub.html] with IBM Support.\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 12 October 2014: 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.", " SECURITY BULLETIN\n\nSUMMARY\n Multiple Vulnerabilities in Sametime Classic Meeting Server (File upload - CVE-2014-3088, Cross Site Scripting - CVE-2014-4747 and Meeting Password Disclosure - CVE-2014-4748) \n\nVULNERABILITY DETAILS\nCVE ID: CVE-2014-3088 [http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3088]\n\nDESCRIPTION: \n\nIBM Sametime Classic Meeting Server could allow a remote attacker to upload arbitrary files. By sending a specially crafted HTTP request, a remote attacker could exploit this vulnerability to upload a malicious file to the meeting. Other users may download and execute the file on their system. \n\nCVSS: \n\nCVSS Base Score: 6.8\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/94113 [https://exchange.xforce.ibmcloud.com/vulnerabilities/94113] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:P/A:P)\n\n\n======================================== \n\n\nCVE-ID: CVE-2014-4747 [http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-4747]\n\nDESCRIPTION: \n\nIBM Sametime Classic Meeting Server allows a user that has access to the same machine and browser of a user that is allowed to a meeting, to obtain the meeting password hash from the HTML source. \n\nCVSS: \n\nCVSS Base Score: 2.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/94349 [https://exchange.xforce.ibmcloud.com/vulnerabilities/94349] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:L/AC:L/Au:N/C:P/I:N/A:N)\n\n\n======================================== \n\n\nCVE-ID: CVE-2014-4748 [http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-4748]\n\nDESCRIPTION: \n\nIBM Sametime Classic Meeting Server is vulnerable to reflected 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 a 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\nCVSS: \n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/94350 [https://exchange.xforce.ibmcloud.com/vulnerabilities/94350] 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 Sametime Classic Meeting Server versions 8.0.x and 8.5.x\n\nREMEDIATION/FIXES\nInstall the following fixes based on the version that you are using. \n\nPlease follow the instructions in IBM technote #1679454 \"Security fixes for Sametime Classic Meetings Server [http://www.ibm.com/support/docview.wss?uid=swg21679454].\"\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\nThe vulnerabilities of CVE-2014-3088, CVE-2014-4747 and CVE-2014-4748 were reported to IBM by Adriano Marcio Monteiro.\n\n\nCHANGE HISTORY\n 18 July 2014 - 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.", "heart bleed; JFBA9HZ686; Memory Leak Vulnerability; CVE-2014-0160 FLASH (ALERT)\n\nABSTRACT\n Information is circulating describing a method called \"Heartbleed,\" which exploits a vulnerability caused by a design error in OpenSSL. This technote provides confirmation that IBM Notes and Domino are not susceptible to the Heartbleed attack. \n\nCONTENT\nIBM Notes and Domino are not vulnerable to the Heartbleed bug because they do not use OpenSSL as the basis of the SSL stack in the products. Note that this includes both the Domino SSL stack as well as the TLS implementation supported by the IBM HTTP Server in 9.0. Notes Traveler is also not affected. \n\nFor more information on the Heartbleed bug, including a Q&A, go to http://www.heartbleed.com [http://www.heartbleed.com/]. \n\nRELATED INFORMATION\n CVE-2014-0160 [http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-0160]\nOpenSSL vulnerabilities do not apply to IHS [http://www.ibm.com/support/docview.wss?uid=swg21383959]\nA simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21669880]\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Messaging Applications IBM Notes 9.0, 8.5, 8.0 Messaging Applications IBM Traveler 9.0, 8.5, 8.0.1" ]

[ [ "1a", "CVE-2014-6271 CVE-2014-7169 DataPower Bash FLASH (ALERT) ABSTRACT" ], [ "1b", " DataPower is not vulnerable to the Bash vulnerabilities that have been referred to as “Bash Bug” or “Shellshock” and the two memory corruption vulnerabilities. CONTENT" ], [ "1c", "DataPower does not use Bash anywhere." ], [ "1d", "Hence it is not impacted by any of the Bash vulnerabilities." ], [ "1e", "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." ], [ "1f", "IBM recommends that you review your entire environment to identify vulnerable releases of Bash and take appropriate mitigation and remediation actions." ] ]

[ "1b", "1c", "1d", "1e" ]

[ " FIXES ARE AVAILABLE\nITCAM Agent for SAP Applications, 7.1.1-TIV-ITM_SAP-IF0001 [http://www-01.ibm.com/support/docview.wss?uid=swg24036988]\nITCAM Agent for SAP Applications, 7.1.1-TIV-ITM_SAP-FP0003 [http://www-01.ibm.com/support/docview.wss?uid=swg24043404]\nITCAM Agent for SAP Applications, 7.1.1.3-TIV-ITM_SAP-IF0001 [http://www-01.ibm.com/support/docview.wss?uid=swg24043820]\nITCAM Agent for SAP Applications,7.1.1-TIV-ITM_SAP-FP0004 [http://www-01.ibm.com/support/docview.wss?uid=swg24044289]\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 * Environemnt:\n SAP version: 731\n SAP Agent: 711\n \n Steps to reproduce:\n &#65530; Import the transport ITM711_00098U\n &#65530; Check the transport log\n \n \n \n \n \n\nLOCAL FIX\n * N/A\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ERROR DESCRIPTION:\n Environemnt:\n SAP version: 731\n SAP Agent: 711\n \n Steps to reproduce:\n &#250; Import the transport ITM711_00098U\n &#250; Check the transport log\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * 711 Version:\n The formal fix for this APAR is contained in the following\n package:\n IBM(R) Tivoli(R) Composite Application Manager Agent for SAP\n Applications,\n Version 7.1.1\n Component ID: 5724B97SO\n \n Interim Pack: 0001, 7.1.1-TIV-ITM_SAP-IF0001\n \n Date: Feb, 2014\n \n \n \n \n \n\nTEMPORARY FIX\n * TempFix Provided and got positive results.\n \n \n \n \n \n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IV53685\n \n \n * REPORTED COMPONENT NAME\n ITMF APPL - SAP\n \n \n * REPORTED COMPONENT ID\n 5724B97SO\n \n \n * REPORTED RELEASE\n 710\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-01-06\n \n \n * CLOSED DATE\n 2014-01-20\n \n \n * LAST MODIFIED DATE\n 2014-01-20\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 ITMF APPL - SAP\n \n \n * FIXED COMPONENT ID\n 5724B97SO\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R710 PSY\n UP", "ITCAM; J2EE; uplift; Refresh Pack; prerequisites; CAMJ2ALL; CAMJ2INST TECHNOTE (FAQ)\n\nQUESTION\n When trying to install 7.1.1-TIV-ITCAM_J2EE-Windows-RP001 on a Windows 2008 R2 64-bit, the installation returns the following error popup message:\nThe Agent Compatibility Package in version 06230400 is required but unavailable.\nHow can I solve this? \n\nCAUSE\nThe Agent Compatibility Package is not bundled with ITCAM for J2EE 7.1.1.\nThe Agent Compatibility Package is not installed on the involved server, or it is of a version older than the one required.\nITM 6.2.3 FP4 is the minimum prerequisite ITM version supported with ITCAM for J2EE agent v7.1.1.\n\nE.g. if you have ITM 6.2.3 FP1 components installed, you will have this component installed:\n\nAC 32/64 Bit Agent Compatibility Package\nWIX64 Version: 06.23.01.00 Build: 201202220943\n\nbesides other Windows 64-bit ITM components, and you will get this error message.\n\n\nANSWER\nThe AC component can be found on the Agents DVD. \n\n\nComplete the following steps on the 64-bit Windows system where a 64-bit agent is installed: \n1. Locate the installation media for IBM Tivoli Monitoring V6.2.3 FP4 (or later). \n\n2. From the WINDOWS subdirectory of the Tivoli Monitoring installation media, run setup.exe. The installation wizard starts. \n\n3. On the Select Features page, leave all of the existing check boxes selected. The following two components are selected by default: \n\n \n\n * 32/64 Bit Agent Compatibility Package (x86-64 only) \n * Tivoli Enterprise Monitoring Agent Framework (x86-64 only)\n\n\nIBM recommends you install the AC component at the same version as the Windows OS agent (component code NT). \n\n4. Follow the instructions on the Tivoli Monitoring installation wizard to complete the installation of the agent compatibility package. \n\n5. Run the ITCAM for J2EE 7.1.1 installation wizard to complete the installation of ITCAM for J2EE. \n\nImportant: You can install the agent compatibility package from any media where it is bundled, but the version that is installed must be equal to or greater than V6.2.3 Fix Pack 4. \n\nYou can also refer to the following documentation link for further details: \nhttp://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/install/acpinstall.htm?cp=SSTFXA_6.3.0&lang=en [http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/install/acpinstall.htm?cp=SSTFXA_6.3.0&lang=en]", " FIXES ARE AVAILABLE\nITCAM Agent for SAP Applications, 7.1.1-TIV-ITM_SAP-FP0001 [http://www-01.ibm.com/support/docview.wss?uid=swg24037991]\nITCAM Agent for SAP Applications, 7.1.1-TIV-ITM_SAP-FP0003 [http://www-01.ibm.com/support/docview.wss?uid=swg24043404]\nITCAM Agent for SAP Applications, 7.1.1.3-TIV-ITM_SAP-IF0001 [http://www-01.ibm.com/support/docview.wss?uid=swg24043820]\nITCAM Agent for SAP Applications,7.1.1-TIV-ITM_SAP-FP0004 [http://www-01.ibm.com/support/docview.wss?uid=swg24044289]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DOCUMENTATION ERROR.\n \n \n \n\nERROR DESCRIPTION\n * ITM SAP agent 7.11 not collecting alerts from solution\n manager\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * This is DOC APAR and needs to put proper steps to configure\n Thred Party adapter OS command adapter. Put steps to enable mail\n notification. Steps to verify MAI alerts in database table ,\n verify BADI transport.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * 711 Version:\n The formal fix for this APAR is contained in the following\n package:\n IBM(R) Tivoli(R) Composite Application Manager Agent for SAP\n Applications,\n Version 7.1.1\n Component ID: 5724B97SO\n \n \n Fixpack: 0001, 7.1.1-TIV-ITM_SAP-FP0001\n \n OR TEcnote with required steps to configure.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IV59319\n \n \n * REPORTED COMPONENT NAME\n ITMF APPL - SAP\n \n \n * REPORTED COMPONENT ID\n 5724B97SO\n \n \n * REPORTED RELEASE\n 711\n \n \n * STATUS\n CLOSED DOC\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-04-16\n \n \n * CLOSED DATE\n 2014-05-19\n \n \n * LAST MODIFIED DATE\n 2014-05-19\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 ITMF APPL - SAP\n \n \n * FIXED COMPONENT ID\n 5724B97SO\n \n \n\nAPPLICABLE COMPONENT LEVELS", " SUBSCRIBE\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 * After SAP Agent is reconfigured or restarted, the SAP user is\n locked.\n \n The password is corruptted when the SAP Agent Reconfigure or\n restart, so SAP locks the SAP Agent user.\n \n This problem is shown in Japanese environment only.\n \n \n \n \n \n\nLOCAL FIX\n * Using the password file in SAP agent Reconfigure.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * After mySAP agent is reconfigured, the agent can no longer\n connect to the mySAP system due to a corrupt password. This\n problem occurs only on mySAP agents running on Windows systems\n in a multi-byte language environment such as Japenese.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * This APAR has been fixed and delivered in a limited availability\n fix 6.1.0-TIV-ITM_SAP-LA0009. This maintenance delivery vehicle\n is a limited availability patch and therefore is in a \"hidden\n directory.\" Level 2 Support can provide down load instructions\n to you. Contact level 2 support at:\n \n http://www.ibm.com/software/sysmgmt/products/support/Contact_L2\n Support.html [http://www.ibm.com/software/sysmgmt/products/support/Contact_L2Support.html]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IZ08143\n \n \n * REPORTED COMPONENT NAME\n ITMF APPL - SAP\n \n \n * REPORTED COMPONENT ID\n 5724B97SO\n \n \n * REPORTED RELEASE\n 610\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 2007-11-06\n \n \n * CLOSED DATE\n 2008-01-17\n \n \n * LAST MODIFIED DATE\n 2008-01-17\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 ITMF APPL - SAP\n \n \n * FIXED COMPONENT ID\n 5724B97SO\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R610 PSY\n UP", " SUBSCRIBE\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 * Title: SAP CUA adapter 4.65.1009 does not cause the PASSCODE to\n be\n generated on a password change transaction as occurs during an\n add\n provisioning operation.\n \n Problem description:\n \n Customer states:\n \n \"On a password change request, a new password isn't getting\n properly\n sent\n down to the child systems. With SAP version 7, there is both a\n BCODE and\n PASSCODE field on the user accounts. BCODE is there for backward\n compatability with\n pre-version 7 systems. In our environment, that means uppercase\n and 8\n characters. the PASSCODE is the \"new\" field and will accept up\n to a 40\n character password, in mixed case. It's this\n passcode that's not being replicated down to the child systems,\n and our\n SAP person believes he has found why in the BAPI that is called\n on a\n change (/TIVSECTY/TIM_USER_USR02_620). He sees where it copies\n the BCODE\n value down but not the PASSCODE.\"\n \n IF agrees with the customer's assessment and has asked to have\n an apar\n raised.\n \n Steps to duplicate:\n \n IF has duplicated per customer description of problem.\n \n \n Customer Recreate:\n \n Yes.\n \n \n Desired behavior:\n \n PASSCODE to be propagated to child systems on password\n change operation as it is on add operation.\n \n \n =================================================\n \n \n \n \n \n\nLOCAL FIX\n * n/a\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Modified SAP transport to replace passcode\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Fix will ship in SAP Adapter v4.6.6 in 1Q208\n \n \n \n \n \n\nTEMPORARY FIX\n * Install updated transport.\n \n \n \n \n \n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IZ05147\n \n \n * REPORTED COMPONENT NAME\n ITIM AGENTS\n \n \n * REPORTED COMPONENT ID\n 5724C34AG\n \n \n * REPORTED RELEASE\n 460\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 2007-09-21\n \n \n * CLOSED DATE\n 2007-10-31\n \n \n * LAST MODIFIED DATE\n 2010-01-26\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\nMODULES/MACROS\n * AGENT\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n ITIM AGENTS\n \n \n * FIXED COMPONENT ID\n 5724C34AG\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R460 PSY\n UP" ]

[ [ "3a", " SUBSCRIBE You can track all active APARs for this component. APAR STATUS" ], [ "3b", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "3c", " * After SAP Agent is reconfigured or restarted, the SAP user is" ], [ "3d", " locked." ], [ "3e", " The password is corruptted when the SAP Agent Reconfigure or" ], [ "3f", " restart, so SAP locks the SAP Agent user." ], [ "3g", " This problem is shown in Japanese environment only. LOCAL FIX" ], [ "3h", " * Using the password file in SAP agent Reconfigure. PROBLEM SUMMARY" ], [ "3i", " * After mySAP agent is reconfigured, the agent can no longer" ], [ "3j", " connect to the mySAP system due to a corrupt password. This" ], [ "3k", " problem occurs only on mySAP agents running on Windows systems" ], [ "3l", " in a multi-byte language environment such as Japenese. PROBLEM CONCLUSION" ], [ "3m", " * This APAR has been fixed and delivered in a limited availability" ], [ "3n", " fix 6.1.0-TIV-ITM_SAP-LA0009." ], [ "3o", "This maintenance delivery vehicle" ], [ "3p", " is a limited availability patch and therefore is in a \"hidden" ], [ "3q", " directory.\"" ], [ "3r", "Level 2 Support can provide down load instructions" ], [ "3s", " to you." ], [ "3t", "Contact level 2 support at:" ], [ "3u", " http://www.ibm.com/software/sysmgmt/products/support/Contact_L2" ], [ "3v", " Support.html [http://www.ibm.com/software/sysmgmt/products/support/Contact_L2Support.html] TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "3w", " * APAR NUMBER" ], [ "3x", " IZ08143" ], [ "3y", " * REPORTED COMPONENT NAME" ], [ "3z", " ITMF APPL - SAP" ], [ "3aa", " * REPORTED COMPONENT ID" ], [ "3ab", " 5724B97SO" ], [ "3ac", " * REPORTED RELEASE" ], [ "3ad", " 610" ], [ "3ae", " * STATUS" ], [ "3af", " CLOSED PER" ], [ "3ag", " * PE" ], [ "3ah", " NoPE" ], [ "3ai", " * HIPER" ], [ "3aj", " NoHIPER" ], [ "3ak", " * SPECIAL ATTENTION" ], [ "3al", " NoSpecatt" ], [ "3am", " * SUBMITTED DATE" ], [ "3an", " 2007-11-06" ], [ "3ao", " * CLOSED DATE" ], [ "3ap", " 2008-01-17" ], [ "3aq", " * LAST MODIFIED DATE" ], [ "3ar", " 2008-01-17" ], [ "3as", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "3at", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "3au", " * FIXED COMPONENT NAME" ], [ "3av", " ITMF APPL - SAP" ], [ "3aw", " * FIXED COMPONENT ID" ], [ "3ax", " 5724B97SO" ], [ "3ay", "APPLICABLE COMPONENT LEVELS" ], [ "3az", " * R610 PSY" ], [ "3ba", " UP" ] ]

[ "3b", "3c", "3d", "3e", "3f", "3g", "3h", "3i", "3j", "3k", "3l", "3m" ]

[ "sha-2; sha256; sha2; sha-256; SB2B; sterling integrator TECHNOTE (FAQ)\n\nQUESTION\n In What Version(s) of IBM Sterling B2B Integrator is SHA-256 Supported? \n\nANSWER\nBeginning with IBM Sterling B2B Integrator (SI) 5.2.4.2 support for FIPS 140-2 Level 1 is certified with using the Certicom Government Service Edition (GSE) cryptographic module that is distributed within SB2Bi.\nWhile previous product releases allowed you to check-in or even generate a SHA256 RSA certificate, the underlying support to utilize that hash level was not present. To be fully compliant at a SHA256 level you must be running version 5.2.4.2 or higher.\n\nSHA256 is the same as SHA2 or SHA-2", "z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Development fixes.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of the IBM Communications Server *\n * for z/OS Version 1 Release 12 IP *\n ****************************************************************\n * PROBLEM DESCRIPTION: Development fixes *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n D151337\n The RFCs for AES-GCM and AES-GMAC state that the initialization\n vector (IV) generated for packets sent over these tunnels must\n be unique. FIPS 140 requires that the IV used by these\n algorithms be generated within the cryptographic boundary when\n FIPS 140 is enabled. ICSF is the cryptographic boundary used\n by the stack. Therefore, TCP/IP requests ICSF to generate the IV\n when FIPS 140 is enabled. Otherwise the stack generates the IV.\n Since ICSF is not always used to generate the IV, it is not\n possible to guarantee that the generated IV is unique.\n \n KEYWORD: SWPSP/K\n +-------------------------------------------------------------+\n + Please check our Communications Server for OS/390 homepages +\n + for common networking tips and fixes. The URL for these +\n + homepages can be found in Informational APAR II11334 [http://www-01.ibm.com/support/docview.wss?uid=isg1II11334]. +\n +-------------------------------------------------------------+\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * D151337\n Logic was added to always request ICSF to generate the IV.\n \n \n * Cross Reference between External and Internal Names\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM17826\n \n \n * REPORTED COMPONENT NAME\n TCP/IP V3 MVS\n \n \n * REPORTED COMPONENT ID\n 5655HAL00\n \n \n * REPORTED RELEASE\n 1C0\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 2010-07-02\n \n \n * CLOSED DATE\n 2010-08-06\n \n \n * LAST MODIFIED DATE\n 2010-09-01\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 UK59508 UK59509\n \n \n\nMODULES/MACROS\n * EZBISAGM EZBISGMA EZBISXGM EZBXFMSG EZBXFSWS\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n TCP/IP V3 MVS\n \n \n * FIXED COMPONENT ID\n 5655HAL00\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R1CK PSY UK59509 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK59509]\n UP10/08/11 P F008\n \n \n * R1C0 PSY UK59508 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK59508]\n UP10/08/11 P F008\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.", " TECHNOTE (FAQ)\n\nQUESTION\n Why can I no longer create a 1024-bit RSA key on the HSM (hardware security module) after a DataPower appliance upgrade to 7.0.0.14, 7.1.0.11, 7.2.0.8, 7.5.0.2 or 7.5.1.2? \n\nANSWER\nDataPower Type 2426, 7198, 7199, or 8436 appliances with the HSM automatically have their HSM firmware upgraded from version 1.2 to version 2.2 after an upgrade to 7.0.0.14, 7.1.0.11, 7.2.0.8, 7.5.0.2 or 7.5.1.2 (or later). This HSM firmware upgrade is required to maintain the NIST FIPS-140-2 certificate. After the HSM firmware upgrade, you can no longer create 1024-bit keys on the HSM but existing 1024-bit keys continue to function. \n\nNIST made obsolete the ANSI X9.31 RNG (Random Number Generator) algorithm and will no longer certify products that use this algorithm as compliant with FIPS-140-2. The DataPower HSM version 1.2 firmware has this algorithm, so the HSM firmware must be updated to retain compliance with FIPS-140-2. The new HSM version 2.2 firmware provides only the CTR_DRBG RNG (Counter mode Deterministic Random Byte Generator) algorithm. Although the HSM version 1.2 firmware has no associated vulnerability, the certificate will be removed from the NIST validation list. \n\nBeginning 2011, NIST recommended the use of RSA keys of at least 2048 bits. The HSM version 2.2 firmware enforces this recommendation and does not allow you to create new 1024-bit RSA keys on the HSM. Although existing 1024-bit keys continue to function, you should replace 1024-bit keys with new 2048-bit or 4096-bit keys. To replace keys that are stored on the HSM, back them up to another HSM with the Export Crypto Object utility or the crypto-export command, \n\nThe HSM firmware is updated only when the HSM was initialized with the hsm-reinit command. If you install the fix pack but the HSM is not initialized, the HSM firmware update is delayed until the first restart after you initialize the HSM. \n\nNote: If you want to downgrade to the previous HSM version after you installed the DataPower fix pack, you can obtain the following tools from IBM Fix Central. Search for text string HSM. \n\n * Use the idg-hsm_downgrade tool to downgrade the HSM to version 1.2 and keep it at version 1.2 across fix pack installations until you enable the HSM upgrade with the idg-hsm_enable_update tool. \n * Use the idg-hsm_enable_update tool to allow the installation of a fix pack to upgrade the HSM component firmware to the latest version. After you run this tool, you must install a firmware version.\n\nTo determine whether your appliances has the HSM, use the show crypto-engine command. When the accelerator type is hsm2, the appliance has the HSM. This status provider also provides the status, which informs you whether the HSM is initialized. \n\nTo determine the HSM firmware version, use the service show component-firmware command. \n\n * Before the upgrade, the version is CN16XX-NFBE-FW-1.2-101022. \n * After the upgrade, the version is CN16XX-NFBE-FW-2.2-130013.\n\n\nAttention: If you switch to the secondary image ( boot switch) after you install the fix pack with the component firmware upgrade or install an earlier fix pack, the HSM will not function. After the firmware downgrade, the show crypto-engine command reports the accelerator type is uncertifiedHSMFirmwareDetected. To prevent this situation, downgrade the HSM before you downgrade the firmware. If you get into the situation where you already downgraded your firmware, you must complete the following procedure and use a tool from IBM Fix Central. 1. Switch back to the previously installed, secondary image (boot switch) or install a fix pack with the upgraded HSM component firmware. \n 2. Downgrade the HSM component firmware by using the tool from IBM Fix Central. Make sure the downgrade process succeeds and the HSM version is back to CN16XX-NFBE-FW-1.2-101022 with the service show component-firmware command. \n 3. Switch back to the primary image (boot switch) or install the wanted fix pack without the upgraded HSM component firmware.\n\n\nFor more information about the HSM, see the DataPower version-specific documentation in IBM Knowledge Center [http://www.ibm.com/support/knowledgecenter/SS9H2Y].", " 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® for performing encryption. As of DB2® Universal Database™ (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]", "162556; AppScan; AppScan Source; FIPS; Federal Information Processing; 140-2; OS X; NSS; Mozilla; Network Security Services; compliance; validation; validated TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n On OS X platforms that are supported by IBM Security AppScan Source, manual steps are needed to operate in Federal Information Processing Standard (FIPS) 140-2 mode. These steps are described in this document. In addition, the document covers enabling and disabling FIPS 140-2 mode - and how to determine if AppScan Source is running in FIPS 140-2 mode. \n\nRESOLVING THE PROBLEM\nThe OS X Java Development Kit (JDK) requires an external FIPS 140-2 validated cryptographic module in order to correctly enable FIPS compliance for AppScan Source. This document provides example steps for using the open source Mozilla Network Security Services (NSS) as that external cryptographic module. \n\nPrerequisites: \n\n * Ensure that Xcode and its command line tools are installed.\n Note: AppScan Source supports Xcode Versions 4.4 through 4.6. \n * Ensure that MacPorts (available at http://www.macports.org/ [http://www.macports.org/]) is installed. \n * After installing MacPorts, install NSS by issuing these commands:\n sudo port install sqlite3\n sudo port install nss \n * Configure NSS by following these steps: 1. Create a folder and, inside that folder, create a configuration file with a .config or .cfg extension (for example, nss-client.config). \n 2. Open the configuration file in an editor and enter only these contents in it:\n name = nss-client\n nssLibraryDirectory = /opt/local/lib/nss\n nssDbMode=noDb \n 3. Save the configuration file.\n Note: The file must not be saved as rich text format.\n \n \n\nEnable FIPS 140-2 mode in AppScan Source: \n\n 1. Ensure that AppScan Source is not running. \n 2. Open <data_dir>/config/ounce.ozsettings (where <data_dir> is the location of your AppScan Source program data) and locate the fips_mode setting. By default, the setting looks like this:\n <Setting\n description_id=\"\"\n name=\"fips_mode\"\n read_only=\"false\"\n default_value=\"1\"\n value=\"1\"\n description=\"FIPS Mode\"\n type=\"text\"\n display_name=\"FIPS Mode\"\n display_name_id=\"\"\n available_values=\"\"\n hidden=\"false\"\n force_upgrade=\"false\"\n /> \n 3. In the setting, ensure that the value attribute is set to value=\"1\". This attribute setting indicates that FIPS is enabled. \n 4. In a Terminal window, change directory to <install_dir>/jre/lib/security (where <install_dir> is the location of your AppScan Source installation) and then create a backup of the java.security and java.security.fips files (for example, to back up java.security, \n issue a cp java.security java.security.bkp command). \n 5. Delete the java.security file and then rename java.security.fips to java.security. \n 6. Edit java.security (the file that was previously named java.security.fips) and locate this line:\n security.provider.2=sun.security.pkcs11.SunPKCS11 /Users/Shared/NSS/nss-client.cfg\n Note that this line refers to an NSS configuration file. Edit this line so that it refers to the NSS configuration file (including its path) that you created in the Prerequisites section above.\n\n\nTo disable FIPS 140-2 mode, change the fips_mode setting so that value=\"0\" - and restore the java.security and java.security.fips files to their initial state. \n\n \n\nConfigure certificates for publishing to AppScan Enterprise Console: \n\nUsing a self-signed root certificate for your AppScan Enterprise Server will not allow you to publish assessments to the AppScan Enterprise Console. To be able to publish assessments to the AppScan Enterprise Console, you must manually save the AppScan Enterprise Server certificate to your Java KeyStore. \n\n 1. Enter the URL for your AppScan Enterprise Server instance (for example, https://my_server:9443/asc/) in Safari. \n 2. When prompted to verify the identity of the web site, choose the Always trust option. \n 3. Open the OS X Keychain Access utility and locate the certificate that was added for your AppScan Enterprise Server instance. \n 4. Right-click the certificate and select the Export option, making note of the location and file name that the certificate is exported to. \n 5. In a Terminal window, set your environment by issuing these commands:\n export JAVA_HOME=/Applications/AppScanSource.app/jre\n export PATH=$JAVA_HOME/bin: $PATH \n 6. In a Terminal window, change directory to the location that the certificate was exported to in Step 4 - and then save the AppScan Enterprise Server certificate to your Java KeyStore by issuing this command:\n keytool -importcert -trustcacerts -file <certificate> -alias appscan -keystore <data_dir>/config/cacertspersonal -storepass changeit\n where: * <certificate> is the file name of the exported certificate created in Step 4. \n * <data_dir> is the location of your AppScan Source program data. By default, the location on OS X is /Users/Shared/AppScanSource.\n \n \n\nHow to determine if AppScan Source is operating in FIPS 140-2 mode: \n\n 1. Open <data_dir>/config/ounce.ozsettings (where <data_dir> is the location of your AppScan Source program data) and modify the log_level setting so that its value is 3 (Info). By default, the setting looks like this:\n <Setting\n name=\"log_level\"\n default_value=\"5\"\n description=\"Error log level\"\n type=\"list\"\n value=\"5\"\n display_name=\"Log level\"\n available_values=\"1:Trace,2:Debug,3:Info,4:Warn,5:Error,6:Fatal\"\n />\n Modify the setting so that value=\"3\". \n 2. Launch AppScan Source and run a scan. \n 3. Open <data_dir>/logs/scanner_exceptions.log, where you will notice these log entries, which are indicators that AppScan Source is operating in FIPS 140-2 mode:\n 02/01/13 11:10:57 Info(30082) from PlService.cpp(276)\n Current FIPS Mode: 1\n \n ....\n \n 02/01/13 11:12:05 Info(60015) from AppScanServerClient.cpp(91)\n FIPS initialiazed correctly for client\n \n 02/01/13 11:12:05 Info(30082) from AppScanServerClient.cpp(94)\n Current FIPS Mode from Client: 1 \n 4. Open <data_dir>/logs/osa.log. Entries marked as Java FIPS are indicators that AppScan Source is operating in FPS 140-2 mode. For example:\n Java FIPS: com.ibm.jsse2.usefupsprovider: null\n Java FIPS: SSL Context does not exists\n Java FIPS: SecureRandom provider: SunPKCS11-nss-client version 1.7\n\nRELATED INFORMATION\n Operating in FIPS 140-2 mode on Windows and Linux [http://www.ibm.com/support/docview.wss?uid=swg21626684]\nBackground information [http://www.ibm.com/support/docview.wss?uid=swg21626701]" ]

[ [ "3a", " TECHNOTE (FAQ) QUESTION" ], [ "3b", " Is DB2 v8, v10.5 compliant to FIPS 140-2 ?. ANSWER" ], [ "3c", "Is DB2 v10.5 compliant with FIPS 140-2?" ], [ "3d", "Q: Is DB2 vulnerable to the problem described below?" ], [ "3e", "V-58165 DBMS main in the middle attack [https://www.stigviewer.com/stig/database_security_requirements_guide/2015-06-23/finding/V-58165]" ], [ "3f", "\"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." ], [ "3g", "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." ], [ "3h", "However, it is recognized that available DBMS products do not all implement the preferred technique yet may have other protections against session hijacking." ], [ "3i", "Therefore, other techniques are acceptable, provided they are demonstrated to be effective. \"" ], [ "3j", "A: No because DB2 does not use session ids for authentication and thus not vulnerable to the attack described above." ], [ "3k", "DB2 uses encryption modules which are FIPS 140-2 certified." ], [ "3l", "DB2 v8.x compliancy to FIPS 140-2" ], [ "3m", "DB2 v8.x went out of support in April 2009." ], [ "3n", "What is ICC?" ], [ "3o", "ICC (IBM Crypto for C) is a set of libraries from Tivoli® for performing encryption." ], [ "3p", "As of DB2® Universal Database™ (DB2 UDB) Version 8 fixpak 7 (equivalent to DB2 UDB Version 8.2), DB2 is using ICC on most platforms." ], [ "3q", "Customers 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." ], [ "3r", "Following is a list of platforms on which DB2 is using ICC for encryption of data flowing between clients and servers:" ], [ "3s", "DB2 V8 Fixpak 7 through DB2 Fixpak 11:" ], [ "3t", "ICC Version 1.2.2 on platforms:" ], [ "3u", "AIX 32 bit" ], [ "3v", "HP-UX PA-RISC 32 bit" ], [ "3w", "ICC Version 1.2.1 on platforms:" ], [ "3x", "AIX 64 bit" ], [ "3y", "HP-UX PA-RISC 64 bit HP-UX IA64" ], [ "3z", "Linux x86, Linux x86-64, Linux IA64" ], [ "3aa", "Linux for zSeries" ], [ "3ab", "Linux for POWER" ], [ "3ac", "Windows x86 and IA64" ], [ "3ad", "Solaris SPARC 64 bit" ], [ "3ae", "ICC Version 1.3.9 on platforms:" ], [ "3af", "Solaris x86-64 (DB2 V8.2 GA)" ], [ "3ag", "DB2 V8 Fixpak 12 and later:" ], [ "3ah", "ICC Version 1.4.1 on platforms AIX HP-UX PA-RISC" ], [ "3ai", "Linux x86 and x86-64" ], [ "3aj", "Linux for zSeries" ], [ "3ak", "Linux for POWER" ], [ "3al", "Windows x86 and x86-64 Solaris SPARC" ], [ "3am", "ICC Version 1.3.9 on platforms HP-UX IA64 Linux IA64 Windows IA64" ], [ "3an", "Summary of known problems encountered in ICC 1.2.1/1.2.2:" ], [ "3ao", "There are a number of issues with DB2 and the ICC encryption libraries at levels prior to 1.3.9." ], [ "3ap", "The known problems are: 1." ], [ "3aq", "Severe performance problems where processes seem to hang, or take several minutes to run. 2." ], [ "3ar", "A bug in ICC code causes it to communicate with the OpenSSL EGD (Entropy Gathering Daemon) which under certain circumstances could hang 3." ], [ "3as", "ICC symbols have not been namespaced and DB2 can end up with symbol collisions with OpenSSL code." ], [ "3at", "This can also happen when multiple versions of ICC are used within the same process." ], [ "3au", "DB2 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." ], [ "3av", "Note: 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] RELATED INFORMATION" ], [ "3aw", " FIPS PUB 140-2 [http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf]" ] ]

[ "3c", "3g", "3k", "3p", "3q" ]

[ " 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-2017-12418, CVE-2017-12427, CVE-2017-12428, CVE-2017-12429, CVE-2017-12430, CVE-2017-12431, CVE-2017-12432, CVE-2017-12433, CVE-2017-12434, CVE-2017-12435, CVE-2017-12563, CVE-2017-12564, CVE-2017-12565, CVE-2017-12566, CVE-2017-12587, CVE-2017-12640, CVE-2017-12641, CVE-2017-12642, CVE-2017-12643, CVE-2017-12644, CVE-2017-12654, CVE-2017-12662 CVE-2017-12663 CVE-2017-12664 CVE-2017-12665 CVE-2017-12666 CVE-2017-12667 CVE-2017-12668 CVE-2017-12669 CVE-2017-12670 CVE-2017-12671 CVE-2017-12672 CVE-2017-12673 CVE-2017-12674 CVE-2017-12675 CVE-2017-12676 CVE-2017-12983 CVE-2017-13058 CVE-2017-13059 CVE-2017-13060 CVE-2017-13061 and CVE-2017-13062 \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", " 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. \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-3706, CVE-2016-4429, CVE-2016-5195, and CVE-2016-7799\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", "IIB WMB FLASH (ALERT)\n\nABSTRACT\n IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux \n\nCONTENT\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with version Red Hat Enterprise Linux (RHEL) Server 6.2 which is vulnerable to\nCVE-2018-5247 CVE-2018-5246 CVE-2018-5248 CVE-2017-1000476 CVE-2017-18008 CVE-2017-17914 CVE-2017-17934 CVE-2017-18022 CVE-2017-17882 CVE-2017-17884 CVE-2017-17887 CVE-2017-17886 CVE-2017-17880 CVE-2017-17883 CVE-2017-17885 CVE-2017-17879 CVE-2017-17881 CVE-2017-17499 CVE-2017-17504 \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", " フラッシュ(ALERTS)\n\n概要\n IBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0 V7.0, IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0で提供されている Red Hat Enterprise Linux (RHEL) の GNU C library (glibc) に脆弱性が存在します。(CVE-2015-1472 & CVE-2013-7423)\n\n\n\n本文\nIBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Editions V8.0, V7.0, IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 で提供されている Red Hat Enterprise Linux (RHEL) Server の GNU C library (glibc) に脆弱性が存在します。(CVE-2013-7423, CVE-2015-1472 and CVE-2013-7424 )\n.\n\n【対象ソフトウェア】\n･IBM Integration Bus Hypervisor Edition V9.0 \n･WebSphere Message Broker Hypervisor Editions V8.0, V7.0 \n･IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0\n\nIBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0, IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 は、Red Hat Enterprise Linux (RHEL) Server 6.2を同梱しています。\nWebSphere Message Broker Hypervisor Edition V7.0は、Red Hat Enterprise Linux (RHEL) Server 5.5を同梱しています。\n\n* Hypervisor Edition ではなく、IBM Integration Bus もしくは、WebSphere Message Broker を使用されている場合、この脆弱性は該当いたしません。\n\n\n【対応策/軽減策】\nRed Hat Enterprise Linux (RHEL)の修正を入手し、導入してください。\n\n\n修正をRed Hatから入手できない場合、GNU web site [http://www.gnu.org] からダウンロードし、glibc リリース2.21以降を導入してください。\n\n\n【参考情報】\nRed Hat vulnerabilities by CVE name [https://access.redhat.com/security/cve/]\n\nRed Hat(CVE-2013-7423) [https://access.redhat.com/security/cve/CVE-2013-7423]\nRed Hat(CVE-2015-1472) [https://access.redhat.com/security/cve/CVE-2015-1472]\nRed Hat(CVE-2013-7424) [https://access.redhat.com/security/cve/CVE-2013-7424]\n\n\n[IBMサイト]\nこの文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。\nAction required for IBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0, V7.0 and IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 for the GNU C library (glibc) vulnerabilities. [http://www.ibm.com/support/docview.wss?uid=swg21697721]\n\n[CVSS情報]\n独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html]\nJVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html]\nglibc の脆弱性対策について(CVE-2015-0235)：IPA 独立行政法人 情報処理推進機構 [http://www.ipa.go.jp/security/announce/20150129-glibc.html]\n\n\n【お問合せ先】\n技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。\nIBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html]\n\n\n関連情報\n An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21697721]", "IIB WMB FLASH (ALERT)\n\nABSTRACT\n IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux \n\nCONTENT\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2 which is vulnerable to: \n\nCVE-2017-5715\nCVE-2017-5753\nCVE-2017-5754\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" ]

[ [ "0a", " FLASH (ALERT) ABSTRACT" ], [ "0b", " IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux CONTENT" ], [ "0c", "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2017-12418, CVE-2017-12427, CVE-2017-12428, CVE-2017-12429, CVE-2017-12430, CVE-2017-12431, CVE-2017-12432, CVE-2017-12433, CVE-2017-12434, CVE-2017-12435, CVE-2017-12563, CVE-2017-12564, CVE-2017-12565, CVE-2017-12566, CVE-2017-12587, CVE-2017-12640, CVE-2017-12641, CVE-2017-12642, CVE-2017-12643, CVE-2017-12644, CVE-2017-12654, CVE-2017-12662 CVE-2017-12663 CVE-2017-12664 CVE-2017-12665 CVE-2017-12666 CVE-2017-12667 CVE-2017-12668 CVE-2017-12669 CVE-2017-12670 CVE-2017-12671 CVE-2017-12672 CVE-2017-12673 CVE-2017-12674 CVE-2017-12675 CVE-2017-12676 CVE-2017-12983 CVE-2017-13058 CVE-2017-13059 CVE-2017-13060 CVE-2017-13061 and CVE-2017-13062 Remediation:" ], [ "0d", "IBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable" ], [ "0e", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0 PRODUCT ALIAS/SYNONYM" ], [ "0f", " WMB HVE IIB HVE" ] ]

[ "0b", "0c", "0d", "1b", "1c", "1d", "1e", "2b", "2c", "2d", "2e", "4b", "4c", "4d" ]

[ " 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-2017-12418, CVE-2017-12427, CVE-2017-12428, CVE-2017-12429, CVE-2017-12430, CVE-2017-12431, CVE-2017-12432, CVE-2017-12433, CVE-2017-12434, CVE-2017-12435, CVE-2017-12563, CVE-2017-12564, CVE-2017-12565, CVE-2017-12566, CVE-2017-12587, CVE-2017-12640, CVE-2017-12641, CVE-2017-12642, CVE-2017-12643, CVE-2017-12644, CVE-2017-12654, CVE-2017-12662 CVE-2017-12663 CVE-2017-12664 CVE-2017-12665 CVE-2017-12666 CVE-2017-12667 CVE-2017-12668 CVE-2017-12669 CVE-2017-12670 CVE-2017-12671 CVE-2017-12672 CVE-2017-12673 CVE-2017-12674 CVE-2017-12675 CVE-2017-12676 CVE-2017-12983 CVE-2017-13058 CVE-2017-13059 CVE-2017-13060 CVE-2017-13061 and CVE-2017-13062 \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", " 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. \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-3706, CVE-2016-4429, CVE-2016-5195, and CVE-2016-7799\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", "IIB WMB FLASH (ALERT)\n\nABSTRACT\n IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux \n\nCONTENT\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with version Red Hat Enterprise Linux (RHEL) Server 6.2 which is vulnerable to\nCVE-2018-5247 CVE-2018-5246 CVE-2018-5248 CVE-2017-1000476 CVE-2017-18008 CVE-2017-17914 CVE-2017-17934 CVE-2017-18022 CVE-2017-17882 CVE-2017-17884 CVE-2017-17887 CVE-2017-17886 CVE-2017-17880 CVE-2017-17883 CVE-2017-17885 CVE-2017-17879 CVE-2017-17881 CVE-2017-17499 CVE-2017-17504 \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", " フラッシュ(ALERTS)\n\n概要\n IBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0 V7.0, IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0で提供されている Red Hat Enterprise Linux (RHEL) の GNU C library (glibc) に脆弱性が存在します。(CVE-2015-1472 & CVE-2013-7423)\n\n\n\n本文\nIBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Editions V8.0, V7.0, IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 で提供されている Red Hat Enterprise Linux (RHEL) Server の GNU C library (glibc) に脆弱性が存在します。(CVE-2013-7423, CVE-2015-1472 and CVE-2013-7424 )\n.\n\n【対象ソフトウェア】\n･IBM Integration Bus Hypervisor Edition V9.0 \n･WebSphere Message Broker Hypervisor Editions V8.0, V7.0 \n･IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0\n\nIBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0, IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 は、Red Hat Enterprise Linux (RHEL) Server 6.2を同梱しています。\nWebSphere Message Broker Hypervisor Edition V7.0は、Red Hat Enterprise Linux (RHEL) Server 5.5を同梱しています。\n\n* Hypervisor Edition ではなく、IBM Integration Bus もしくは、WebSphere Message Broker を使用されている場合、この脆弱性は該当いたしません。\n\n\n【対応策/軽減策】\nRed Hat Enterprise Linux (RHEL)の修正を入手し、導入してください。\n\n\n修正をRed Hatから入手できない場合、GNU web site [http://www.gnu.org] からダウンロードし、glibc リリース2.21以降を導入してください。\n\n\n【参考情報】\nRed Hat vulnerabilities by CVE name [https://access.redhat.com/security/cve/]\n\nRed Hat(CVE-2013-7423) [https://access.redhat.com/security/cve/CVE-2013-7423]\nRed Hat(CVE-2015-1472) [https://access.redhat.com/security/cve/CVE-2015-1472]\nRed Hat(CVE-2013-7424) [https://access.redhat.com/security/cve/CVE-2013-7424]\n\n\n[IBMサイト]\nこの文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。\nAction required for IBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0, V7.0 and IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 for the GNU C library (glibc) vulnerabilities. [http://www.ibm.com/support/docview.wss?uid=swg21697721]\n\n[CVSS情報]\n独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html]\nJVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html]\nglibc の脆弱性対策について(CVE-2015-0235)：IPA 独立行政法人 情報処理推進機構 [http://www.ipa.go.jp/security/announce/20150129-glibc.html]\n\n\n【お問合せ先】\n技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。\nIBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html]\n\n\n関連情報\n An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21697721]", "IIB WMB FLASH (ALERT)\n\nABSTRACT\n IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux \n\nCONTENT\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2 which is vulnerable to: \n\nCVE-2017-5715\nCVE-2017-5753\nCVE-2017-5754\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" ]

[ [ "1a", " FLASH (ALERT) ABSTRACT" ], [ "1b", " IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat. CONTENT" ], [ "1c", "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-3706, CVE-2016-4429, CVE-2016-5195, and CVE-2016-7799" ], [ "1d", "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2. Remediation:" ], [ "1e", "IBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable." ], [ "1f", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0 PRODUCT ALIAS/SYNONYM" ], [ "1g", " WMB HVE IIB HVE" ] ]

[ "0b", "0c", "0d", "1b", "1c", "1d", "1e", "2b", "2c", "2d", "2e", "4b", "4c", "4d" ]

[ " 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-2017-12418, CVE-2017-12427, CVE-2017-12428, CVE-2017-12429, CVE-2017-12430, CVE-2017-12431, CVE-2017-12432, CVE-2017-12433, CVE-2017-12434, CVE-2017-12435, CVE-2017-12563, CVE-2017-12564, CVE-2017-12565, CVE-2017-12566, CVE-2017-12587, CVE-2017-12640, CVE-2017-12641, CVE-2017-12642, CVE-2017-12643, CVE-2017-12644, CVE-2017-12654, CVE-2017-12662 CVE-2017-12663 CVE-2017-12664 CVE-2017-12665 CVE-2017-12666 CVE-2017-12667 CVE-2017-12668 CVE-2017-12669 CVE-2017-12670 CVE-2017-12671 CVE-2017-12672 CVE-2017-12673 CVE-2017-12674 CVE-2017-12675 CVE-2017-12676 CVE-2017-12983 CVE-2017-13058 CVE-2017-13059 CVE-2017-13060 CVE-2017-13061 and CVE-2017-13062 \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", " 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. \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-3706, CVE-2016-4429, CVE-2016-5195, and CVE-2016-7799\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", "IIB WMB FLASH (ALERT)\n\nABSTRACT\n IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux \n\nCONTENT\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with version Red Hat Enterprise Linux (RHEL) Server 6.2 which is vulnerable to\nCVE-2018-5247 CVE-2018-5246 CVE-2018-5248 CVE-2017-1000476 CVE-2017-18008 CVE-2017-17914 CVE-2017-17934 CVE-2017-18022 CVE-2017-17882 CVE-2017-17884 CVE-2017-17887 CVE-2017-17886 CVE-2017-17880 CVE-2017-17883 CVE-2017-17885 CVE-2017-17879 CVE-2017-17881 CVE-2017-17499 CVE-2017-17504 \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", " フラッシュ(ALERTS)\n\n概要\n IBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0 V7.0, IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0で提供されている Red Hat Enterprise Linux (RHEL) の GNU C library (glibc) に脆弱性が存在します。(CVE-2015-1472 & CVE-2013-7423)\n\n\n\n本文\nIBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Editions V8.0, V7.0, IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 で提供されている Red Hat Enterprise Linux (RHEL) Server の GNU C library (glibc) に脆弱性が存在します。(CVE-2013-7423, CVE-2015-1472 and CVE-2013-7424 )\n.\n\n【対象ソフトウェア】\n･IBM Integration Bus Hypervisor Edition V9.0 \n･WebSphere Message Broker Hypervisor Editions V8.0, V7.0 \n･IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0\n\nIBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0, IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 は、Red Hat Enterprise Linux (RHEL) Server 6.2を同梱しています。\nWebSphere Message Broker Hypervisor Edition V7.0は、Red Hat Enterprise Linux (RHEL) Server 5.5を同梱しています。\n\n* Hypervisor Edition ではなく、IBM Integration Bus もしくは、WebSphere Message Broker を使用されている場合、この脆弱性は該当いたしません。\n\n\n【対応策/軽減策】\nRed Hat Enterprise Linux (RHEL)の修正を入手し、導入してください。\n\n\n修正をRed Hatから入手できない場合、GNU web site [http://www.gnu.org] からダウンロードし、glibc リリース2.21以降を導入してください。\n\n\n【参考情報】\nRed Hat vulnerabilities by CVE name [https://access.redhat.com/security/cve/]\n\nRed Hat(CVE-2013-7423) [https://access.redhat.com/security/cve/CVE-2013-7423]\nRed Hat(CVE-2015-1472) [https://access.redhat.com/security/cve/CVE-2015-1472]\nRed Hat(CVE-2013-7424) [https://access.redhat.com/security/cve/CVE-2013-7424]\n\n\n[IBMサイト]\nこの文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。\nAction required for IBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0, V7.0 and IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 for the GNU C library (glibc) vulnerabilities. [http://www.ibm.com/support/docview.wss?uid=swg21697721]\n\n[CVSS情報]\n独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html]\nJVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html]\nglibc の脆弱性対策について(CVE-2015-0235)：IPA 独立行政法人 情報処理推進機構 [http://www.ipa.go.jp/security/announce/20150129-glibc.html]\n\n\n【お問合せ先】\n技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。\nIBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html]\n\n\n関連情報\n An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21697721]", "IIB WMB FLASH (ALERT)\n\nABSTRACT\n IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux \n\nCONTENT\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2 which is vulnerable to: \n\nCVE-2017-5715\nCVE-2017-5753\nCVE-2017-5754\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" ]

[ [ "2a", "IIB WMB FLASH (ALERT) ABSTRACT" ], [ "2b", " IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux CONTENT" ], [ "2c", "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with version Red Hat Enterprise Linux (RHEL) Server 6.2 which is vulnerable to" ], [ "2d", "CVE-2018-5247 CVE-2018-5246 CVE-2018-5248 CVE-2017-1000476 CVE-2017-18008 CVE-2017-17914 CVE-2017-17934 CVE-2017-18022 CVE-2017-17882 CVE-2017-17884 CVE-2017-17887 CVE-2017-17886 CVE-2017-17880 CVE-2017-17883 CVE-2017-17885 CVE-2017-17879 CVE-2017-17881 CVE-2017-17499 CVE-2017-17504 Remediation:" ], [ "2e", "IBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable." ], [ "2f", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0" ] ]

[ "0b", "0c", "0d", "1b", "1c", "1d", "1e", "2b", "2c", "2d", "2e", "4b", "4c", "4d" ]

[ " 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-2017-12418, CVE-2017-12427, CVE-2017-12428, CVE-2017-12429, CVE-2017-12430, CVE-2017-12431, CVE-2017-12432, CVE-2017-12433, CVE-2017-12434, CVE-2017-12435, CVE-2017-12563, CVE-2017-12564, CVE-2017-12565, CVE-2017-12566, CVE-2017-12587, CVE-2017-12640, CVE-2017-12641, CVE-2017-12642, CVE-2017-12643, CVE-2017-12644, CVE-2017-12654, CVE-2017-12662 CVE-2017-12663 CVE-2017-12664 CVE-2017-12665 CVE-2017-12666 CVE-2017-12667 CVE-2017-12668 CVE-2017-12669 CVE-2017-12670 CVE-2017-12671 CVE-2017-12672 CVE-2017-12673 CVE-2017-12674 CVE-2017-12675 CVE-2017-12676 CVE-2017-12983 CVE-2017-13058 CVE-2017-13059 CVE-2017-13060 CVE-2017-13061 and CVE-2017-13062 \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", " 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. \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-3706, CVE-2016-4429, CVE-2016-5195, and CVE-2016-7799\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", "IIB WMB FLASH (ALERT)\n\nABSTRACT\n IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux \n\nCONTENT\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with version Red Hat Enterprise Linux (RHEL) Server 6.2 which is vulnerable to\nCVE-2018-5247 CVE-2018-5246 CVE-2018-5248 CVE-2017-1000476 CVE-2017-18008 CVE-2017-17914 CVE-2017-17934 CVE-2017-18022 CVE-2017-17882 CVE-2017-17884 CVE-2017-17887 CVE-2017-17886 CVE-2017-17880 CVE-2017-17883 CVE-2017-17885 CVE-2017-17879 CVE-2017-17881 CVE-2017-17499 CVE-2017-17504 \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", " フラッシュ(ALERTS)\n\n概要\n IBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0 V7.0, IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0で提供されている Red Hat Enterprise Linux (RHEL) の GNU C library (glibc) に脆弱性が存在します。(CVE-2015-1472 & CVE-2013-7423)\n\n\n\n本文\nIBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Editions V8.0, V7.0, IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 で提供されている Red Hat Enterprise Linux (RHEL) Server の GNU C library (glibc) に脆弱性が存在します。(CVE-2013-7423, CVE-2015-1472 and CVE-2013-7424 )\n.\n\n【対象ソフトウェア】\n･IBM Integration Bus Hypervisor Edition V9.0 \n･WebSphere Message Broker Hypervisor Editions V8.0, V7.0 \n･IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0\n\nIBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0, IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 は、Red Hat Enterprise Linux (RHEL) Server 6.2を同梱しています。\nWebSphere Message Broker Hypervisor Edition V7.0は、Red Hat Enterprise Linux (RHEL) Server 5.5を同梱しています。\n\n* Hypervisor Edition ではなく、IBM Integration Bus もしくは、WebSphere Message Broker を使用されている場合、この脆弱性は該当いたしません。\n\n\n【対応策/軽減策】\nRed Hat Enterprise Linux (RHEL)の修正を入手し、導入してください。\n\n\n修正をRed Hatから入手できない場合、GNU web site [http://www.gnu.org] からダウンロードし、glibc リリース2.21以降を導入してください。\n\n\n【参考情報】\nRed Hat vulnerabilities by CVE name [https://access.redhat.com/security/cve/]\n\nRed Hat(CVE-2013-7423) [https://access.redhat.com/security/cve/CVE-2013-7423]\nRed Hat(CVE-2015-1472) [https://access.redhat.com/security/cve/CVE-2015-1472]\nRed Hat(CVE-2013-7424) [https://access.redhat.com/security/cve/CVE-2013-7424]\n\n\n[IBMサイト]\nこの文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。\nAction required for IBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0, V7.0 and IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 for the GNU C library (glibc) vulnerabilities. [http://www.ibm.com/support/docview.wss?uid=swg21697721]\n\n[CVSS情報]\n独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html]\nJVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html]\nglibc の脆弱性対策について(CVE-2015-0235)：IPA 独立行政法人 情報処理推進機構 [http://www.ipa.go.jp/security/announce/20150129-glibc.html]\n\n\n【お問合せ先】\n技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。\nIBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html]\n\n\n関連情報\n An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21697721]", "IIB WMB FLASH (ALERT)\n\nABSTRACT\n IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux \n\nCONTENT\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2 which is vulnerable to: \n\nCVE-2017-5715\nCVE-2017-5753\nCVE-2017-5754\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" ]

[ [ "4a", "IIB WMB FLASH (ALERT) ABSTRACT" ], [ "4b", " IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux CONTENT" ], [ "4c", "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2 which is vulnerable to: CVE-2017-5715 CVE-2017-5753 CVE-2017-5754 Remediation:" ], [ "4d", "IBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable." ], [ "4e", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0" ] ]

[ "0b", "0c", "0d", "1b", "1c", "1d", "1e", "2b", "2c", "2d", "2e", "4b", "4c", "4d" ]

[ " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM WebSphere Application Server that shipped with WebSphere Enterprise Service Bus for z/OS \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: Seehttps://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\nREMEDIATION/FIXES\nThese security vulnerabilities are all fixed with available interim fixes and are targeted for specific WebSphere Application Server fix pack levels. For more information on these fixes, including workarounds and mitigations please see Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [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 25th of June: 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.", " SECURITY BULLETIN\n\nSUMMARY\n Diffie-Hellman (DH) 暗号を使用した TLSプロトコルに脆弱性が発見されました。(通称 Logjam)\nTLS接続を行うIBM WebSphere MQ Internet Pass-Thru (MQIPT) に影響があります。\nTLS 接続を使用する場合、中間者攻撃により TLS 接続が暗号強度の低い輸出グレードの 512 ビット暗号に格下げされる問題があります。その結果、通信内容の盗聴や改ざんをされる可能性があります。\n\n\nVULNERABILITY DETAILS\n脆弱性の詳細\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\n影響のある製品・バージョン： \n\n次の製品に影響があります。 \n\n・IBM WebSphere MQ Internet Pass-Thru (MQIPT) : SupportPac MS81 \n\n2.1.0.2 以前のIBM WebSphere MQ Internet Pass-Thru (MQIPT) のすべてのバージョンで影響のある暗号スイートが使用されています。\n\nREMEDIATION/FIXES\n修正策： \n\n\nIBM WebSphere MQ Internet Pass-Thru 2.1.0.2 [http://www.ibm.com/support/docview.wss?uid=swg24006386] 以降のリリースにアップグレードしてください。\n\nWORKAROUNDS AND MITIGATIONS\n回避策/軽減策： \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参照情報： \n\n[IBMサイト] \nこの文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。 \nSecurity Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) [http://www.ibm.com/support/docview.wss?uid=swg21959745] \n\n公開済みのフィックスパックについては、以下のサイトよりご利用いただけます。 \nRecommended fixes for WebSphere MQ [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006037] \n\nフィックス・パックの公開予定については、以下のサイトよりご確認いただけます。 \nWebSphere MQ planned maintenance release dates [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006309] \n\n[CVSS情報] \n独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html] \nJVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html] 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] . \n関連情報： \n. \n[お問合せ先] \n技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。 \nIBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html] *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 An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21959745]", " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM WebSphere Application Server that shipped with WebSphere Enterprise Service Bus Registry Edition. \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: Seehttps://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\nREMEDIATION/FIXES\nThese security vulnerabilities are all fixed with available interim fixes and are targeted for specific WebSphere Application Server fix pack levels. For more information on these fixes, including workarounds and mitigations please see Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [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] \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 25th of June: 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.", "CVE-2015-4000 SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere Application Server is shipped as components of IBM Service Delivery Manager. Information about a security vulnerability affecting WebSphere Application Server has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nReview security bulletin Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [http://www-01.ibm.com/support/docview.wss?uid=swg21957980] for vulnerability details and information about fixes.\n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nPrincipal Product and Versions Affected Supporting Product and Version IBM Service Delivery Manager V7.2.4 WebSphere Application Server V6.1.0.37 IBM Service Delivery Manager V7.2.2 WebSphere Application Server V6.1.0.29 IBM Service Delivery Manager V7.2.1 WebSphere Application Server V6.1.0.23 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] ACKNOWLEDGEMENT\n* 16 July 2015: 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.", " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect IBM Tivoli Provisioning Manager and IBM WebSphere Application Server shipped as a component of IBM Tivoli Provisioning Manager. \n\nVULNERABILITY DETAILS\n CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]\n\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\".\n\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\n \n\nPrincipal Product and Version(s) Affected Supporting Product and Version Tivoli Provisioning Manager version 7.1, 7.2 WebSphere Application Server 6.1, 7 REMEDIATION/FIXES\nFor vulnerability details and information about fixes, consult the security bulletin Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [http://www.ibm.com/support/docview.wss?uid=swg21957980]\n\nWORKAROUNDS AND MITIGATIONS\n [http://www.ibm.com/support/docview.wss?uid=swg21957980]The affected ciphersuites can be disabled in Tivoli Provisioning Manager server by restricting the ciphersuites that are used by the Java runtime. Please refer to How to disable Diffie-Hellman ciphers in IBM Tivoli Provisioning Manager server [http://www.ibm.com/support/docview.wss?uid=swg21959162]\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 18 June 2015: Original Version Published\n06 July 2015: Remediation fix 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." ]

[ [ "0a", " SECURITY BULLETIN SUMMARY" ], [ "0b", " The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM WebSphere Application Server that shipped with WebSphere Enterprise Service Bus for z/OS VULNERABILITY DETAILS CVEID:CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]" ], [ "0c", "DESCRIPTION:The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice." ], [ "0d", "An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher." ], [ "0e", "Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic." ], [ "0f", "This vulnerability is commonly referred to as \"Logjam\"." ], [ "0g", "CVSS Base Score: 4.3" ], [ "0h", "CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294]for the current score" ], [ "0i", "CVSS Environmental Score*: Undefined" ], [ "0j", "CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N) REMEDIATION/FIXES" ], [ "0k", "These security vulnerabilities are all fixed with available interim fixes and are targeted for specific WebSphere Application Server fix pack levels." ], [ "0l", "For more information on these fixes, including workarounds and mitigations please see Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [http://www-01.ibm.com/support/docview.wss?uid=swg21957980]" ], [ "0m", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS" ], [ "0n", " Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. REFERENCES" ], [ "0o", "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]" ], [ "0p", "On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] RELATED INFORMATION" ], [ "0q", "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]" ], [ "0r", "IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] ACKNOWLEDGEMENT" ], [ "0s", "Reported to IBM by The WeakDH team at https://weakdh.org [https://weakdh.org] CHANGE HISTORY" ], [ "0t", " 25th of June: Original Version Published" ], [ "0u", "*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score." ], [ "0v", "Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. DISCLAIMER" ], [ "0w", "According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\"" ], [ "0x", "IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE." ], [ "0y", "CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY." ] ]

[ "0b", "0c", "0d", "0e", "0f", "0k", "0l", "1b", "1c", "1d", "1e", "1f", "1g", "1h", "1i", "1p", "1q", "2b", "2c", "2d", "2e", "2f", "2k", "2l", "3c", "3d", "4b", "4c", "4d", "4e", "4f", "4g", "4n", "4o" ]

[ " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM WebSphere Application Server that shipped with WebSphere Enterprise Service Bus for z/OS \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: Seehttps://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\nREMEDIATION/FIXES\nThese security vulnerabilities are all fixed with available interim fixes and are targeted for specific WebSphere Application Server fix pack levels. For more information on these fixes, including workarounds and mitigations please see Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [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 25th of June: 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.", " SECURITY BULLETIN\n\nSUMMARY\n Diffie-Hellman (DH) 暗号を使用した TLSプロトコルに脆弱性が発見されました。(通称 Logjam)\nTLS接続を行うIBM WebSphere MQ Internet Pass-Thru (MQIPT) に影響があります。\nTLS 接続を使用する場合、中間者攻撃により TLS 接続が暗号強度の低い輸出グレードの 512 ビット暗号に格下げされる問題があります。その結果、通信内容の盗聴や改ざんをされる可能性があります。\n\n\nVULNERABILITY DETAILS\n脆弱性の詳細\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\n影響のある製品・バージョン： \n\n次の製品に影響があります。 \n\n・IBM WebSphere MQ Internet Pass-Thru (MQIPT) : SupportPac MS81 \n\n2.1.0.2 以前のIBM WebSphere MQ Internet Pass-Thru (MQIPT) のすべてのバージョンで影響のある暗号スイートが使用されています。\n\nREMEDIATION/FIXES\n修正策： \n\n\nIBM WebSphere MQ Internet Pass-Thru 2.1.0.2 [http://www.ibm.com/support/docview.wss?uid=swg24006386] 以降のリリースにアップグレードしてください。\n\nWORKAROUNDS AND MITIGATIONS\n回避策/軽減策： \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参照情報： \n\n[IBMサイト] \nこの文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。 \nSecurity Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) [http://www.ibm.com/support/docview.wss?uid=swg21959745] \n\n公開済みのフィックスパックについては、以下のサイトよりご利用いただけます。 \nRecommended fixes for WebSphere MQ [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006037] \n\nフィックス・パックの公開予定については、以下のサイトよりご確認いただけます。 \nWebSphere MQ planned maintenance release dates [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006309] \n\n[CVSS情報] \n独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html] \nJVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html] 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] . \n関連情報： \n. \n[お問合せ先] \n技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。 \nIBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html] *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 An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21959745]", " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM WebSphere Application Server that shipped with WebSphere Enterprise Service Bus Registry Edition. \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: Seehttps://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\nREMEDIATION/FIXES\nThese security vulnerabilities are all fixed with available interim fixes and are targeted for specific WebSphere Application Server fix pack levels. For more information on these fixes, including workarounds and mitigations please see Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [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] \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 25th of June: 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.", "CVE-2015-4000 SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere Application Server is shipped as components of IBM Service Delivery Manager. Information about a security vulnerability affecting WebSphere Application Server has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nReview security bulletin Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [http://www-01.ibm.com/support/docview.wss?uid=swg21957980] for vulnerability details and information about fixes.\n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nPrincipal Product and Versions Affected Supporting Product and Version IBM Service Delivery Manager V7.2.4 WebSphere Application Server V6.1.0.37 IBM Service Delivery Manager V7.2.2 WebSphere Application Server V6.1.0.29 IBM Service Delivery Manager V7.2.1 WebSphere Application Server V6.1.0.23 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] ACKNOWLEDGEMENT\n* 16 July 2015: 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.", " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect IBM Tivoli Provisioning Manager and IBM WebSphere Application Server shipped as a component of IBM Tivoli Provisioning Manager. \n\nVULNERABILITY DETAILS\n CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]\n\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\".\n\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\n \n\nPrincipal Product and Version(s) Affected Supporting Product and Version Tivoli Provisioning Manager version 7.1, 7.2 WebSphere Application Server 6.1, 7 REMEDIATION/FIXES\nFor vulnerability details and information about fixes, consult the security bulletin Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [http://www.ibm.com/support/docview.wss?uid=swg21957980]\n\nWORKAROUNDS AND MITIGATIONS\n [http://www.ibm.com/support/docview.wss?uid=swg21957980]The affected ciphersuites can be disabled in Tivoli Provisioning Manager server by restricting the ciphersuites that are used by the Java runtime. Please refer to How to disable Diffie-Hellman ciphers in IBM Tivoli Provisioning Manager server [http://www.ibm.com/support/docview.wss?uid=swg21959162]\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 18 June 2015: Original Version Published\n06 July 2015: Remediation fix 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." ]

[ [ "1a", " SECURITY BULLETIN SUMMARY" ], [ "1b", " Diffie-Hellman (DH) 暗号を使用した TLSプロトコルに脆弱性が発見されました。(通称 Logjam)" ], [ "1c", "TLS接続を行うIBM WebSphere MQ Internet Pass-Thru (MQIPT) に影響があります。" ], [ "1d", "TLS 接続を使用する場合、中間者攻撃により TLS 接続が暗号強度の低い輸出グレードの 512 ビット暗号に格下げされる問題があります。その結果、通信内容の盗聴や改ざんをされる可能性があります。 VULNERABILITY DETAILS 脆弱性の詳細" ], [ "1e", "CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]" ], [ "1f", "DESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice." ], [ "1g", "An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher." ], [ "1h", "Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic." ], [ "1i", "This vulnerability is commonly referred to as \"Logjam\"." ], [ "1j", "CVSS Base Score: 4.3" ], [ "1k", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score" ], [ "1l", "CVSS Environmental Score*: Undefined" ], [ "1m", "CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)" ], [ "1n", "AFFECTED PRODUCTS AND VERSIONS 影響のある製品・バージョン： 次の製品に影響があります。" ], [ "1o", "・IBM WebSphere MQ Internet Pass-Thru (MQIPT) : SupportPac MS81" ], [ "1p", "2.1.0.2 以前のIBM WebSphere MQ Internet Pass-Thru (MQIPT) のすべてのバージョンで影響のある暗号スイートが使用されています。 REMEDIATION/FIXES 修正策：" ], [ "1q", "IBM WebSphere MQ Internet Pass-Thru 2.1.0.2 [http://www.ibm.com/support/docview.wss?uid=swg24006386] 以降のリリースにアップグレードしてください。" ], [ "1r", "WORKAROUNDS AND MITIGATIONS 回避策/軽減策： なし" ], [ "1s", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS" ], [ "1t", " Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. REFERENCES" ], [ "1u", "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]" ], [ "1v", "On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] 参照情報： [IBMサイト]" ], [ "1w", "この文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。" ], [ "1x", "Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) [http://www.ibm.com/support/docview.wss?uid=swg21959745] 公開済みのフィックスパックについては、以下のサイトよりご利用いただけます。" ], [ "1y", "Recommended fixes for WebSphere MQ [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006037] フィックス・パックの公開予定については、以下のサイトよりご確認いただけます。" ], [ "1z", "WebSphere MQ planned maintenance release dates [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006309] [CVSS情報]" ], [ "1aa", "独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html]" ], [ "1ab", "JVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html] RELATED INFORMATION" ], [ "1ac", "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]" ], [ "1ad", "IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] . 関連情報： . [お問合せ先] 技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。" ], [ "1ae", "IBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html] *The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score." ], [ "1af", "Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. DISCLAIMER" ], [ "1ag", "According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\"" ], [ "1ah", "IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE." ], [ "1ai", "CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. 関連情報" ], [ "1aj", " An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21959745]" ] ]

[ "0b", "0c", "0d", "0e", "0f", "0k", "0l", "1b", "1c", "1d", "1e", "1f", "1g", "1h", "1i", "1p", "1q", "2b", "2c", "2d", "2e", "2f", "2k", "2l", "3c", "3d", "4b", "4c", "4d", "4e", "4f", "4g", "4n", "4o" ]

[ " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM WebSphere Application Server that shipped with WebSphere Enterprise Service Bus for z/OS \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: Seehttps://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\nREMEDIATION/FIXES\nThese security vulnerabilities are all fixed with available interim fixes and are targeted for specific WebSphere Application Server fix pack levels. For more information on these fixes, including workarounds and mitigations please see Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [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 25th of June: 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.", " SECURITY BULLETIN\n\nSUMMARY\n Diffie-Hellman (DH) 暗号を使用した TLSプロトコルに脆弱性が発見されました。(通称 Logjam)\nTLS接続を行うIBM WebSphere MQ Internet Pass-Thru (MQIPT) に影響があります。\nTLS 接続を使用する場合、中間者攻撃により TLS 接続が暗号強度の低い輸出グレードの 512 ビット暗号に格下げされる問題があります。その結果、通信内容の盗聴や改ざんをされる可能性があります。\n\n\nVULNERABILITY DETAILS\n脆弱性の詳細\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\n影響のある製品・バージョン： \n\n次の製品に影響があります。 \n\n・IBM WebSphere MQ Internet Pass-Thru (MQIPT) : SupportPac MS81 \n\n2.1.0.2 以前のIBM WebSphere MQ Internet Pass-Thru (MQIPT) のすべてのバージョンで影響のある暗号スイートが使用されています。\n\nREMEDIATION/FIXES\n修正策： \n\n\nIBM WebSphere MQ Internet Pass-Thru 2.1.0.2 [http://www.ibm.com/support/docview.wss?uid=swg24006386] 以降のリリースにアップグレードしてください。\n\nWORKAROUNDS AND MITIGATIONS\n回避策/軽減策： \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参照情報： \n\n[IBMサイト] \nこの文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。 \nSecurity Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) [http://www.ibm.com/support/docview.wss?uid=swg21959745] \n\n公開済みのフィックスパックについては、以下のサイトよりご利用いただけます。 \nRecommended fixes for WebSphere MQ [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006037] \n\nフィックス・パックの公開予定については、以下のサイトよりご確認いただけます。 \nWebSphere MQ planned maintenance release dates [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006309] \n\n[CVSS情報] \n独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html] \nJVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html] 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] . \n関連情報： \n. \n[お問合せ先] \n技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。 \nIBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html] *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 An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21959745]", " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM WebSphere Application Server that shipped with WebSphere Enterprise Service Bus Registry Edition. \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: Seehttps://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\nREMEDIATION/FIXES\nThese security vulnerabilities are all fixed with available interim fixes and are targeted for specific WebSphere Application Server fix pack levels. For more information on these fixes, including workarounds and mitigations please see Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [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] \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 25th of June: 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.", "CVE-2015-4000 SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere Application Server is shipped as components of IBM Service Delivery Manager. Information about a security vulnerability affecting WebSphere Application Server has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nReview security bulletin Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [http://www-01.ibm.com/support/docview.wss?uid=swg21957980] for vulnerability details and information about fixes.\n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nPrincipal Product and Versions Affected Supporting Product and Version IBM Service Delivery Manager V7.2.4 WebSphere Application Server V6.1.0.37 IBM Service Delivery Manager V7.2.2 WebSphere Application Server V6.1.0.29 IBM Service Delivery Manager V7.2.1 WebSphere Application Server V6.1.0.23 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] ACKNOWLEDGEMENT\n* 16 July 2015: 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.", " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect IBM Tivoli Provisioning Manager and IBM WebSphere Application Server shipped as a component of IBM Tivoli Provisioning Manager. \n\nVULNERABILITY DETAILS\n CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]\n\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\".\n\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\n \n\nPrincipal Product and Version(s) Affected Supporting Product and Version Tivoli Provisioning Manager version 7.1, 7.2 WebSphere Application Server 6.1, 7 REMEDIATION/FIXES\nFor vulnerability details and information about fixes, consult the security bulletin Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [http://www.ibm.com/support/docview.wss?uid=swg21957980]\n\nWORKAROUNDS AND MITIGATIONS\n [http://www.ibm.com/support/docview.wss?uid=swg21957980]The affected ciphersuites can be disabled in Tivoli Provisioning Manager server by restricting the ciphersuites that are used by the Java runtime. Please refer to How to disable Diffie-Hellman ciphers in IBM Tivoli Provisioning Manager server [http://www.ibm.com/support/docview.wss?uid=swg21959162]\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 18 June 2015: Original Version Published\n06 July 2015: Remediation fix 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." ]

[ [ "2a", " SECURITY BULLETIN SUMMARY" ], [ "2b", " The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM WebSphere Application Server that shipped with WebSphere Enterprise Service Bus Registry Edition. VULNERABILITY DETAILS CVEID:CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]" ], [ "2c", "DESCRIPTION:The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice." ], [ "2d", "An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher." ], [ "2e", "Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic." ], [ "2f", "This vulnerability is commonly referred to as \"Logjam\"." ], [ "2g", "CVSS Base Score: 4.3" ], [ "2h", "CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294]for the current score" ], [ "2i", "CVSS Environmental Score*: Undefined" ], [ "2j", "CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N) REMEDIATION/FIXES" ], [ "2k", "These security vulnerabilities are all fixed with available interim fixes and are targeted for specific WebSphere Application Server fix pack levels." ], [ "2l", "For more information on these fixes, including workarounds and mitigations please see Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [http://www-01.ibm.com/support/docview.wss?uid=swg21957980]" ], [ "2m", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS" ], [ "2n", " Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. REFERENCES" ], [ "2o", "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]" ], [ "2p", "On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] RELATED INFORMATION" ], [ "2q", "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]" ], [ "2r", "IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT" ], [ "2s", "Reported to IBM by The WeakDH team at https://weakdh.org [https://weakdh.org] CHANGE HISTORY" ], [ "2t", " 25th of June: Original Version Published" ], [ "2u", "*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score." ], [ "2v", "Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. DISCLAIMER" ], [ "2w", "According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\"" ], [ "2x", "IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE." ], [ "2y", "CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY." ] ]

[ "0b", "0c", "0d", "0e", "0f", "0k", "0l", "1b", "1c", "1d", "1e", "1f", "1g", "1h", "1i", "1p", "1q", "2b", "2c", "2d", "2e", "2f", "2k", "2l", "3c", "3d", "4b", "4c", "4d", "4e", "4f", "4g", "4n", "4o" ]

[ " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM WebSphere Application Server that shipped with WebSphere Enterprise Service Bus for z/OS \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: Seehttps://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\nREMEDIATION/FIXES\nThese security vulnerabilities are all fixed with available interim fixes and are targeted for specific WebSphere Application Server fix pack levels. For more information on these fixes, including workarounds and mitigations please see Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [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 25th of June: 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.", " SECURITY BULLETIN\n\nSUMMARY\n Diffie-Hellman (DH) 暗号を使用した TLSプロトコルに脆弱性が発見されました。(通称 Logjam)\nTLS接続を行うIBM WebSphere MQ Internet Pass-Thru (MQIPT) に影響があります。\nTLS 接続を使用する場合、中間者攻撃により TLS 接続が暗号強度の低い輸出グレードの 512 ビット暗号に格下げされる問題があります。その結果、通信内容の盗聴や改ざんをされる可能性があります。\n\n\nVULNERABILITY DETAILS\n脆弱性の詳細\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\n影響のある製品・バージョン： \n\n次の製品に影響があります。 \n\n・IBM WebSphere MQ Internet Pass-Thru (MQIPT) : SupportPac MS81 \n\n2.1.0.2 以前のIBM WebSphere MQ Internet Pass-Thru (MQIPT) のすべてのバージョンで影響のある暗号スイートが使用されています。\n\nREMEDIATION/FIXES\n修正策： \n\n\nIBM WebSphere MQ Internet Pass-Thru 2.1.0.2 [http://www.ibm.com/support/docview.wss?uid=swg24006386] 以降のリリースにアップグレードしてください。\n\nWORKAROUNDS AND MITIGATIONS\n回避策/軽減策： \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参照情報： \n\n[IBMサイト] \nこの文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。 \nSecurity Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) [http://www.ibm.com/support/docview.wss?uid=swg21959745] \n\n公開済みのフィックスパックについては、以下のサイトよりご利用いただけます。 \nRecommended fixes for WebSphere MQ [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006037] \n\nフィックス・パックの公開予定については、以下のサイトよりご確認いただけます。 \nWebSphere MQ planned maintenance release dates [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006309] \n\n[CVSS情報] \n独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html] \nJVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html] 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] . \n関連情報： \n. \n[お問合せ先] \n技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。 \nIBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html] *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 An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21959745]", " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM WebSphere Application Server that shipped with WebSphere Enterprise Service Bus Registry Edition. \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: Seehttps://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\nREMEDIATION/FIXES\nThese security vulnerabilities are all fixed with available interim fixes and are targeted for specific WebSphere Application Server fix pack levels. For more information on these fixes, including workarounds and mitigations please see Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [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] \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 25th of June: 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.", "CVE-2015-4000 SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere Application Server is shipped as components of IBM Service Delivery Manager. Information about a security vulnerability affecting WebSphere Application Server has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nReview security bulletin Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [http://www-01.ibm.com/support/docview.wss?uid=swg21957980] for vulnerability details and information about fixes.\n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nPrincipal Product and Versions Affected Supporting Product and Version IBM Service Delivery Manager V7.2.4 WebSphere Application Server V6.1.0.37 IBM Service Delivery Manager V7.2.2 WebSphere Application Server V6.1.0.29 IBM Service Delivery Manager V7.2.1 WebSphere Application Server V6.1.0.23 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] ACKNOWLEDGEMENT\n* 16 July 2015: 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.", " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect IBM Tivoli Provisioning Manager and IBM WebSphere Application Server shipped as a component of IBM Tivoli Provisioning Manager. \n\nVULNERABILITY DETAILS\n CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]\n\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\".\n\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\n \n\nPrincipal Product and Version(s) Affected Supporting Product and Version Tivoli Provisioning Manager version 7.1, 7.2 WebSphere Application Server 6.1, 7 REMEDIATION/FIXES\nFor vulnerability details and information about fixes, consult the security bulletin Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [http://www.ibm.com/support/docview.wss?uid=swg21957980]\n\nWORKAROUNDS AND MITIGATIONS\n [http://www.ibm.com/support/docview.wss?uid=swg21957980]The affected ciphersuites can be disabled in Tivoli Provisioning Manager server by restricting the ciphersuites that are used by the Java runtime. Please refer to How to disable Diffie-Hellman ciphers in IBM Tivoli Provisioning Manager server [http://www.ibm.com/support/docview.wss?uid=swg21959162]\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 18 June 2015: Original Version Published\n06 July 2015: Remediation fix 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." ]

[ [ "3a", "CVE-2015-4000 SECURITY BULLETIN SUMMARY" ], [ "3b", " IBM WebSphere Application Server is shipped as components of IBM Service Delivery Manager." ], [ "3c", "Information about a security vulnerability affecting WebSphere Application Server has been published in a security bulletin. VULNERABILITY DETAILS" ], [ "3d", "Review security bulletin Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [http://www-01.ibm.com/support/docview.wss?uid=swg21957980] for vulnerability details and information about fixes." ], [ "3e", "AFFECTED PRODUCTS AND VERSIONS" ], [ "3f", "Principal Product and Versions Affected Supporting Product and Version IBM Service Delivery Manager V7.2.4 WebSphere Application Server V6.1.0.37 IBM Service Delivery Manager V7.2.2 WebSphere Application Server V6.1.0.29 IBM Service Delivery Manager V7.2.1 WebSphere Application Server V6.1.0.23 GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS" ], [ "3g", " Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. REFERENCES" ], [ "3h", "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]" ], [ "3i", "On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] RELATED INFORMATION" ], [ "3j", "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]" ], [ "3k", "IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT" ], [ "3l", "* 16 July 2015: Original copy published" ], [ "3m", "*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score." ], [ "3n", "Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. DISCLAIMER" ], [ "3o", "According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\"" ], [ "3p", "IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE." ], [ "3q", "CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY." ] ]

[ "0b", "0c", "0d", "0e", "0f", "0k", "0l", "1b", "1c", "1d", "1e", "1f", "1g", "1h", "1i", "1p", "1q", "2b", "2c", "2d", "2e", "2f", "2k", "2l", "3c", "3d", "4b", "4c", "4d", "4e", "4f", "4g", "4n", "4o" ]

[ " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM WebSphere Application Server that shipped with WebSphere Enterprise Service Bus for z/OS \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: Seehttps://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\nREMEDIATION/FIXES\nThese security vulnerabilities are all fixed with available interim fixes and are targeted for specific WebSphere Application Server fix pack levels. For more information on these fixes, including workarounds and mitigations please see Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [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 25th of June: 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.", " SECURITY BULLETIN\n\nSUMMARY\n Diffie-Hellman (DH) 暗号を使用した TLSプロトコルに脆弱性が発見されました。(通称 Logjam)\nTLS接続を行うIBM WebSphere MQ Internet Pass-Thru (MQIPT) に影響があります。\nTLS 接続を使用する場合、中間者攻撃により TLS 接続が暗号強度の低い輸出グレードの 512 ビット暗号に格下げされる問題があります。その結果、通信内容の盗聴や改ざんをされる可能性があります。\n\n\nVULNERABILITY DETAILS\n脆弱性の詳細\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\n影響のある製品・バージョン： \n\n次の製品に影響があります。 \n\n・IBM WebSphere MQ Internet Pass-Thru (MQIPT) : SupportPac MS81 \n\n2.1.0.2 以前のIBM WebSphere MQ Internet Pass-Thru (MQIPT) のすべてのバージョンで影響のある暗号スイートが使用されています。\n\nREMEDIATION/FIXES\n修正策： \n\n\nIBM WebSphere MQ Internet Pass-Thru 2.1.0.2 [http://www.ibm.com/support/docview.wss?uid=swg24006386] 以降のリリースにアップグレードしてください。\n\nWORKAROUNDS AND MITIGATIONS\n回避策/軽減策： \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参照情報： \n\n[IBMサイト] \nこの文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。 \nSecurity Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) [http://www.ibm.com/support/docview.wss?uid=swg21959745] \n\n公開済みのフィックスパックについては、以下のサイトよりご利用いただけます。 \nRecommended fixes for WebSphere MQ [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006037] \n\nフィックス・パックの公開予定については、以下のサイトよりご確認いただけます。 \nWebSphere MQ planned maintenance release dates [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006309] \n\n[CVSS情報] \n独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html] \nJVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html] 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] . \n関連情報： \n. \n[お問合せ先] \n技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。 \nIBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html] *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 An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21959745]", " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM WebSphere Application Server that shipped with WebSphere Enterprise Service Bus Registry Edition. \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: Seehttps://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\nREMEDIATION/FIXES\nThese security vulnerabilities are all fixed with available interim fixes and are targeted for specific WebSphere Application Server fix pack levels. For more information on these fixes, including workarounds and mitigations please see Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [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] \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 25th of June: 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.", "CVE-2015-4000 SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere Application Server is shipped as components of IBM Service Delivery Manager. Information about a security vulnerability affecting WebSphere Application Server has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nReview security bulletin Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [http://www-01.ibm.com/support/docview.wss?uid=swg21957980] for vulnerability details and information about fixes.\n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nPrincipal Product and Versions Affected Supporting Product and Version IBM Service Delivery Manager V7.2.4 WebSphere Application Server V6.1.0.37 IBM Service Delivery Manager V7.2.2 WebSphere Application Server V6.1.0.29 IBM Service Delivery Manager V7.2.1 WebSphere Application Server V6.1.0.23 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] ACKNOWLEDGEMENT\n* 16 July 2015: 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.", " SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect IBM Tivoli Provisioning Manager and IBM WebSphere Application Server shipped as a component of IBM Tivoli Provisioning Manager. \n\nVULNERABILITY DETAILS\n CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]\n\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\".\n\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\n \n\nPrincipal Product and Version(s) Affected Supporting Product and Version Tivoli Provisioning Manager version 7.1, 7.2 WebSphere Application Server 6.1, 7 REMEDIATION/FIXES\nFor vulnerability details and information about fixes, consult the security bulletin Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [http://www.ibm.com/support/docview.wss?uid=swg21957980]\n\nWORKAROUNDS AND MITIGATIONS\n [http://www.ibm.com/support/docview.wss?uid=swg21957980]The affected ciphersuites can be disabled in Tivoli Provisioning Manager server by restricting the ciphersuites that are used by the Java runtime. Please refer to How to disable Diffie-Hellman ciphers in IBM Tivoli Provisioning Manager server [http://www.ibm.com/support/docview.wss?uid=swg21959162]\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 18 June 2015: Original Version Published\n06 July 2015: Remediation fix 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." ]

[ [ "4a", " SECURITY BULLETIN SUMMARY" ], [ "4b", " The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect IBM Tivoli Provisioning Manager and IBM WebSphere Application Server shipped as a component of IBM Tivoli Provisioning Manager. VULNERABILITY DETAILS" ], [ "4c", " CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]" ], [ "4d", "DESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice." ], [ "4e", "An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher." ], [ "4f", "Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic." ], [ "4g", "This vulnerability is commonly referred to as \"Logjam\"." ], [ "4h", "CVSS Base Score: 4.3" ], [ "4i", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score" ], [ "4j", "CVSS Environmental Score*: Undefined" ], [ "4k", "CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)" ], [ "4l", "AFFECTED PRODUCTS AND VERSIONS" ], [ "4m", "Principal Product and Version(s) Affected Supporting Product and Version Tivoli Provisioning Manager version 7.1, 7.2 WebSphere Application Server 6.1, 7 REMEDIATION/FIXES" ], [ "4n", "For vulnerability details and information about fixes, consult the security bulletin Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server (CVE-2015-4000) [http://www.ibm.com/support/docview.wss?uid=swg21957980]" ], [ "4o", "WORKAROUNDS AND MITIGATIONS" ], [ "4p", " [http://www.ibm.com/support/docview.wss?uid=swg21957980]The affected ciphersuites can be disabled in Tivoli Provisioning Manager server by restricting the ciphersuites that are used by the Java runtime." ], [ "4q", "Please refer to How to disable Diffie-Hellman ciphers in IBM Tivoli Provisioning Manager server [http://www.ibm.com/support/docview.wss?uid=swg21959162]" ], [ "4r", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS" ], [ "4s", " Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. REFERENCES" ], [ "4t", "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]" ], [ "4u", "On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] RELATED INFORMATION" ], [ "4v", "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]" ], [ "4w", "IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] ACKNOWLEDGEMENT" ], [ "4x", "Reported to IBM by The WeakDH team at https://weakdh.org [https://weakdh.org] CHANGE HISTORY" ], [ "4y", " 18 June 2015: Original Version Published" ], [ "4z", "06 July 2015: Remediation fix added" ], [ "4aa", "*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score." ], [ "4ab", "Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. DISCLAIMER" ], [ "4ac", "According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\"" ], [ "4ad", "IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE." ], [ "4ae", "CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY." ] ]

[ "0b", "0c", "0d", "0e", "0f", "0k", "0l", "1b", "1c", "1d", "1e", "1f", "1g", "1h", "1i", "1p", "1q", "2b", "2c", "2d", "2e", "2f", "2k", "2l", "3c", "3d", "4b", "4c", "4d", "4e", "4f", "4g", "4n", "4o" ]

[ " FLASH (ALERT)\n\nABSTRACT\n IBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0 V7.0 and IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 require customer action for the GNU C library (glibc) vulnerabilities. \n\nCONTENT\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Editions V8.0, V7.0 and IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to the GNU C library (glibc) vulnerabilities (CVE-2013-7423, CVE-2015-1472 and CVE-2013-7424 ). \n\n * \n * \n * \n * \n * \n\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 or Red Hat Enterprise Linux (RHEL) Server 5.5, as applicable \n\nIf fixes are not available from Red Hat then users can download and apply glibc release 2.21 or later directly from the GNU web site [http://www.gnu.org/software/libc/download.html] RELATED INFORMATION\n Red Hat(CVE-2013-7423) [https://access.redhat.com/security/cve/CVE-2013-7423]\nRed Hat(CVE-2015-1472) [https://access.redhat.com/security/cve/CVE-2015-1472]\nRed Hat(CVE-2013-7424) [https://access.redhat.com/security/cve/CVE-2013-7424]\nA Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21903157]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0, 7.0 \nPRODUCT ALIAS/SYNONYM\n WebSphere Message Broker WMB IBM Integration Bus IIB", " フラッシュ(ALERTS)\n\n概要\n IIBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0 and WebSphere Message Broker Hypervisor Edition V7.0 で提供されている Red Hat Enterprise Linux (RHEL) の GNU C library (glibc) に脆弱性が存在します。(CVE-2015-0235).\n\n\n本文\nIIBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0 and WebSphere Message Broker Hypervisor Edition V7.0 で提供されている Red Hat Enterprise Linux (RHEL) の GNU C library (glibc) に脆弱性が存在します。(CVE-2015-0235).\nGNU C Library (glibc)の__nss_hostname_digits_dots() 関数にバッファオーバフローの脆弱性が発見されました。(GHOSTと呼ばれます)\nこれにより、遠隔の第三者による任意のコード実行が可能になる場合があります。\n\n【対象ソフトウェア】 \n\n・IBM Integration Bus Hypervisor Edition V9.0 \n\n・WebSphere Message Broker Hypervisor Edition V7.0/8.0 \n\n\nIBM Integration Bus Hypervisor Edition V9.0 と WebSphere Message Broker Hypervisor Edition V8.0 は、Red Hat Enterprise Linux (RHEL) Server 6.2を同梱しています。\nWebSphere Message Broker Hypervisor Edition V7.0は、 Red Hat Enterprise Linux (RHEL) Server 5.5を同梱しています。\n\n* Hypervisor Edition ではなく、IBM Integration BusもしくWebSphere Message Brokerを使用されている場合、該当いたしません。\n\n\n【対応策/軽減策】\nRed Hat Enterprise Linux (RHEL)の修正を入手し、導入してください。\n\n\n【参考情報】\nRed Hat Customer Portal - GHOST vulnerability [https://access.redhat.com/articles/1332213]\n\n[IBMサイト]\nこの文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。\nAction required for IBM WebSphere MQ Hypervisor Edition for Red Hat Enterprise Linux Server for the GNU C library (glibc) vulnerability (CVE-2015-0235) [http://www.ibm.com/support/docview.wss?uid=swg21695676]\n\n[CVSS情報]\n独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html]\nJVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html]\nglibc の脆弱性対策について(CVE-2015-0235)：IPA 独立行政法人 情報処理推進機構 [http://www.ipa.go.jp/security/announce/20150129-glibc.html]\n\n\n【お問合せ先】\n技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。\nIBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html]\n\n関連情報\n An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21695798 ]", " 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 (CVE-2016-0800, CVE-2016-0703, CVE-2016-0704,CVE-2016-1234) \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 \n\n * - Cross-protocol attack on TLS using SSLv2 (DROWN)(CVE-2016-0800) \n - Divide-and-conquer session key recovery in SSLv2 (CVE-2016-0703) \n - Bleichenbacher oracle in SSLv2 (CVE-2016-0704) \n - Denial of service in glibc (CVE-2016-1234 ) \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 provider to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2 as applicable RELATED INFORMATION\n Redhat [https://access.redhat.com/security/vulnerabilities/drown]\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 WebSphere Message Broker WMB IBM Integration Bus IIB", " DOWNLOADABLE FILES\n\nABSTRACT\n This document describes how to download IBM WebSphere Message Broker Hypervisor Edition V8.0 eAssembly images from the Passport Advantage website. \n\nDOWNLOAD DESCRIPTION\nThis document was created during November 2011 for V8.0 and updated during September 2012.\n\nTerminology\n\nWebSphere Message Broker Hypervisor Edition V8.0 is supplied in two eAssemblies: refer to the table below to identify the appropriate eAssembly image for your environment. \n\nRelated product documentation\n\nWebSphere Message Broker Hypervisor Edition contains WebSphere Message Broker and WebSphere MQ. The most up-to-date information about WebSphere Message Broker can be found in the US English WebSphere Message Broker V8.0 readme file at http://www.ibm.com/support/docview.wss?&uid=swg27006913 [http://www.ibm.com/support/docview.wss?&uid=swg27006913] [http://www-01.ibm.com/support/docview.wss?&uid=swg27006913]. Translated versions of the WebSphere Message Broker V8.0 readme file are available at: ftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/V8.0/ [ftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/V8.0/]. For specific documentation about Websphere Message Broker Hypervisor Edition V8.0, refer to the User's Guide and Reference (which is available for download in several languages). It can be accessed via the IBM Publications Center as follows: 1. Go to the IBM Publications Center [http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss] home page. \n 2. Select \"country/region/language to begin\" and click Go.\n 3. Click on \"Search for publications\" on the Navigation panel.\n 4. Type \"message broker hypervisor\" into the Search on field and click Go.\n 5. Click on the required language publication number or Online button to display the Download screen.\n\n\n\nDownloading the relevant eAssembly images from the Passport Advantage website\n\n 1. From the eAssemblies table below, decide which of the eAssemblies you want to download.\n 2. Go to the Download package table below and follow the link to the Passport Advantage website.\n 3. Sign in to download all of the images that you need.\n 4. Unpack each of the images onto your system. Documentation is included in every image except for the Quick Start Guide.\n\neAssemblies table \n\neAssembly or eImage part number eAssembly or eImage Description CI9F5ML WebSphere Message Broker Hypervisor Edition V8.0.0.1 Quickstart Guide CRGY4ML WebSphere Message Broker Hypervisor Edition V8.0 Red Hat Enterprise Linux Server for x86 Multilingual eAssembly\n\nThis Assembly contains the following eImages:​​ CI7TXML WebSphere Message Broker Hypervisor Edition V8.0.0.1 Red Hat Enterprise Linux Server for x86 VMWare Multilingual CI7TYML WebSphere Message Broker Hypervisor Edition V8.0.0.1 Red Hat Enterprise Linux Server for x86 IBM Workload Deployer and IBM Pure Application System Multilingual [/support/docview.wss?uid=swg24031059&amp;aid=1] [/support/docview.wss?uid=swg24031059&amp;aid=1] CRGY5ML WebSphere Message Broker Hypervisor Edition V8.0 for AIX Multilingual eAssembly\n\nThis Assembly contains the following eImages:​​ CI7TKML WebSphere Message Broker Hypervisor Edition V8.0.0.1 for AIX IBM Workload Deployer Multilingual - AIX License Required CI7TMML WebSphere Message Broker Hypervisor Edition V8.0.0.1 for AIX mksysb Multilingual - AIX License required \n\nDOWNLOAD PACKAGE\n\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central (FC)? [http://www-304.ibm.com/systems/support/fixes/en/fixcentral/help/faq_sw.html] IBM Passport Advantage Online 09 Dec 2011 English 1 FC [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm] [ ] \nPRODUCT ALIAS/SYNONYM\n WMB MB Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI", " 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" ]

[ [ "2a", " FLASH (ALERT) ABSTRACT" ], [ "2b", " IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat (CVE-2016-0800, CVE-2016-0703, CVE-2016-0704,CVE-2016-1234) CONTENT" ], [ "2c", "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" ], [ "2d", " * - Cross-protocol attack on TLS using SSLv2 (DROWN)(CVE-2016-0800)" ], [ "2e", " - Divide-and-conquer session key recovery in SSLv2 (CVE-2016-0703)" ], [ "2f", " - Bleichenbacher oracle in SSLv2 (CVE-2016-0704)" ], [ "2g", " - Denial of service in glibc (CVE-2016-1234 )" ], [ "2h", "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2. Remediation:" ], [ "2i", "IBM strongly recommends that you contact Red Hat provider to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2 as applicable RELATED INFORMATION" ], [ "2j", " Redhat [https://access.redhat.com/security/vulnerabilities/drown]" ], [ "2k", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0 PRODUCT ALIAS/SYNONYM" ], [ "2l", " WebSphere Message Broker WMB IBM Integration Bus IIB" ] ]

[ "2b", "2c", "2d", "2e", "2f", "2g", "2h", "2i", "2j", "4b", "4c", "4d", "4e" ]

[ " FLASH (ALERT)\n\nABSTRACT\n IBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0 V7.0 and IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 require customer action for the GNU C library (glibc) vulnerabilities. \n\nCONTENT\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Editions V8.0, V7.0 and IBM SOA Policy Pattern for Red Hat Enterprise Linux Server 2.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to the GNU C library (glibc) vulnerabilities (CVE-2013-7423, CVE-2015-1472 and CVE-2013-7424 ). \n\n * \n * \n * \n * \n * \n\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 or Red Hat Enterprise Linux (RHEL) Server 5.5, as applicable \n\nIf fixes are not available from Red Hat then users can download and apply glibc release 2.21 or later directly from the GNU web site [http://www.gnu.org/software/libc/download.html] RELATED INFORMATION\n Red Hat(CVE-2013-7423) [https://access.redhat.com/security/cve/CVE-2013-7423]\nRed Hat(CVE-2015-1472) [https://access.redhat.com/security/cve/CVE-2015-1472]\nRed Hat(CVE-2013-7424) [https://access.redhat.com/security/cve/CVE-2013-7424]\nA Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21903157]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0, 7.0 \nPRODUCT ALIAS/SYNONYM\n WebSphere Message Broker WMB IBM Integration Bus IIB", " フラッシュ(ALERTS)\n\n概要\n IIBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0 and WebSphere Message Broker Hypervisor Edition V7.0 で提供されている Red Hat Enterprise Linux (RHEL) の GNU C library (glibc) に脆弱性が存在します。(CVE-2015-0235).\n\n\n本文\nIIBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0 and WebSphere Message Broker Hypervisor Edition V7.0 で提供されている Red Hat Enterprise Linux (RHEL) の GNU C library (glibc) に脆弱性が存在します。(CVE-2015-0235).\nGNU C Library (glibc)の__nss_hostname_digits_dots() 関数にバッファオーバフローの脆弱性が発見されました。(GHOSTと呼ばれます)\nこれにより、遠隔の第三者による任意のコード実行が可能になる場合があります。\n\n【対象ソフトウェア】 \n\n・IBM Integration Bus Hypervisor Edition V9.0 \n\n・WebSphere Message Broker Hypervisor Edition V7.0/8.0 \n\n\nIBM Integration Bus Hypervisor Edition V9.0 と WebSphere Message Broker Hypervisor Edition V8.0 は、Red Hat Enterprise Linux (RHEL) Server 6.2を同梱しています。\nWebSphere Message Broker Hypervisor Edition V7.0は、 Red Hat Enterprise Linux (RHEL) Server 5.5を同梱しています。\n\n* Hypervisor Edition ではなく、IBM Integration BusもしくWebSphere Message Brokerを使用されている場合、該当いたしません。\n\n\n【対応策/軽減策】\nRed Hat Enterprise Linux (RHEL)の修正を入手し、導入してください。\n\n\n【参考情報】\nRed Hat Customer Portal - GHOST vulnerability [https://access.redhat.com/articles/1332213]\n\n[IBMサイト]\nこの文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。\nAction required for IBM WebSphere MQ Hypervisor Edition for Red Hat Enterprise Linux Server for the GNU C library (glibc) vulnerability (CVE-2015-0235) [http://www.ibm.com/support/docview.wss?uid=swg21695676]\n\n[CVSS情報]\n独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html]\nJVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html]\nglibc の脆弱性対策について(CVE-2015-0235)：IPA 独立行政法人 情報処理推進機構 [http://www.ipa.go.jp/security/announce/20150129-glibc.html]\n\n\n【お問合せ先】\n技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。\nIBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html]\n\n関連情報\n An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21695798 ]", " 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 (CVE-2016-0800, CVE-2016-0703, CVE-2016-0704,CVE-2016-1234) \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 \n\n * - Cross-protocol attack on TLS using SSLv2 (DROWN)(CVE-2016-0800) \n - Divide-and-conquer session key recovery in SSLv2 (CVE-2016-0703) \n - Bleichenbacher oracle in SSLv2 (CVE-2016-0704) \n - Denial of service in glibc (CVE-2016-1234 ) \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 provider to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2 as applicable RELATED INFORMATION\n Redhat [https://access.redhat.com/security/vulnerabilities/drown]\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 WebSphere Message Broker WMB IBM Integration Bus IIB", " DOWNLOADABLE FILES\n\nABSTRACT\n This document describes how to download IBM WebSphere Message Broker Hypervisor Edition V8.0 eAssembly images from the Passport Advantage website. \n\nDOWNLOAD DESCRIPTION\nThis document was created during November 2011 for V8.0 and updated during September 2012.\n\nTerminology\n\nWebSphere Message Broker Hypervisor Edition V8.0 is supplied in two eAssemblies: refer to the table below to identify the appropriate eAssembly image for your environment. \n\nRelated product documentation\n\nWebSphere Message Broker Hypervisor Edition contains WebSphere Message Broker and WebSphere MQ. The most up-to-date information about WebSphere Message Broker can be found in the US English WebSphere Message Broker V8.0 readme file at http://www.ibm.com/support/docview.wss?&uid=swg27006913 [http://www.ibm.com/support/docview.wss?&uid=swg27006913] [http://www-01.ibm.com/support/docview.wss?&uid=swg27006913]. Translated versions of the WebSphere Message Broker V8.0 readme file are available at: ftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/V8.0/ [ftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/V8.0/]. For specific documentation about Websphere Message Broker Hypervisor Edition V8.0, refer to the User's Guide and Reference (which is available for download in several languages). It can be accessed via the IBM Publications Center as follows: 1. Go to the IBM Publications Center [http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss] home page. \n 2. Select \"country/region/language to begin\" and click Go.\n 3. Click on \"Search for publications\" on the Navigation panel.\n 4. Type \"message broker hypervisor\" into the Search on field and click Go.\n 5. Click on the required language publication number or Online button to display the Download screen.\n\n\n\nDownloading the relevant eAssembly images from the Passport Advantage website\n\n 1. From the eAssemblies table below, decide which of the eAssemblies you want to download.\n 2. Go to the Download package table below and follow the link to the Passport Advantage website.\n 3. Sign in to download all of the images that you need.\n 4. Unpack each of the images onto your system. Documentation is included in every image except for the Quick Start Guide.\n\neAssemblies table \n\neAssembly or eImage part number eAssembly or eImage Description CI9F5ML WebSphere Message Broker Hypervisor Edition V8.0.0.1 Quickstart Guide CRGY4ML WebSphere Message Broker Hypervisor Edition V8.0 Red Hat Enterprise Linux Server for x86 Multilingual eAssembly\n\nThis Assembly contains the following eImages:​​ CI7TXML WebSphere Message Broker Hypervisor Edition V8.0.0.1 Red Hat Enterprise Linux Server for x86 VMWare Multilingual CI7TYML WebSphere Message Broker Hypervisor Edition V8.0.0.1 Red Hat Enterprise Linux Server for x86 IBM Workload Deployer and IBM Pure Application System Multilingual [/support/docview.wss?uid=swg24031059&amp;aid=1] [/support/docview.wss?uid=swg24031059&amp;aid=1] CRGY5ML WebSphere Message Broker Hypervisor Edition V8.0 for AIX Multilingual eAssembly\n\nThis Assembly contains the following eImages:​​ CI7TKML WebSphere Message Broker Hypervisor Edition V8.0.0.1 for AIX IBM Workload Deployer Multilingual - AIX License Required CI7TMML WebSphere Message Broker Hypervisor Edition V8.0.0.1 for AIX mksysb Multilingual - AIX License required \n\nDOWNLOAD PACKAGE\n\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central (FC)? [http://www-304.ibm.com/systems/support/fixes/en/fixcentral/help/faq_sw.html] IBM Passport Advantage Online 09 Dec 2011 English 1 FC [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm] [ ] \nPRODUCT ALIAS/SYNONYM\n WMB MB Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI", " 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" ]

[ [ "4a", " FLASH (ALERT) ABSTRACT" ], [ "4b", " IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux. CONTENT" ], [ "4c", "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2016-2126, CVE-2016-2125, CVE-2016-2123, CVE-2016-8866, CVE-2016-9556, CVE-2016-9559, and CVE-2016-9773." ], [ "4d", "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2. Remediation:" ], [ "4e", "IBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable." ], [ "4f", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0 PRODUCT ALIAS/SYNONYM" ], [ "4g", " WMB HVE IIB HVE" ] ]

[ "2b", "2c", "2d", "2e", "2f", "2g", "2h", "2i", "2j", "4b", "4c", "4d", "4e" ]

[ " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * A number of Java InputStream objects for files are acquired by\n the MQ JCA resource adapter (MQ-RA) when it is first initialised\n that are not explicitly closed programmatically. As a result,\n when the MQ-RA is running within GlassFish application server\n and the server is shutdown, the following warning message is\n logged:\n \n [WARNING]\n [javax.enterprise.resource.resourceadapter.com.sun.enterprise.co\n nnectors.service]\n [tld: _ThreadID21_ThreadName=RunLevelControllerThread-xxxx]\n \n Java call stack:\n -----------------\n java.lang.Throwable\n com.sun.enterprise.loader.ASURLClassLoader$sentinelInputStream.<\n init>\n com.sun.enterprise.loader.ASURLClassLoader$InternalJarUrlConnect\n ion.getInputStream\n java.net.URL.openStream\n com.ibm.msg.client.commonservices.componentmanager.ComponentMana\n ger.locateComponents\n .....\n com.ibm.mq.connector.ResourceAdapteronfiguration.<clinit>\n .....\n java.lang.Class.newInstance\n com.sun.enterprise.connectors.ActiveRAFactory.createActiveResour\n ceAdapter\n .....\n org.Jvnet.hk2.internal.ServiceHandleImpl.getService\n org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunne\n r.oneJob\n org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunne\n r.run\n ....\n java.util.concurrent.ThreadPoolExecutor$Worker.run\n java.lang.Thread.run\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n This issue affects users of the:\n \n - MQ classes for JMS\n - MQ classes for Java\n - MQ JCA resource adapter\n \n \n Platforms affected:\n MultiPlatform\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n A component known as \"CommonServices\" is initialised when the MQ\n classes for JMS or classes for Java are first used by an\n application, or the MQ JCA resource adapter is initialised by an\n application server. The CommonServices component attempts to\n discover all of the individual client components that are\n available within the environment. For example, the classes for\n Java API, classes for JMS API and Java MQI are all components\n within the MQ Java client.\n \n In order to discover the components, one mechanism used by the\n CommonServices component is to search for files named\n \"compinfo.properties\" within the META-INF directory of the MQ\n Java client component jar files.\n \n The CommonServices component opened an InputStream to the found\n compinfo.properties files to read the data. The InputStream was\n not explicitly closed. This resulted in a warning log message\n when the MQ resource adapter was running within a Glassfish\n application server environment and the server was shutdown.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The CommonServices component has been updated to explicitly call\n the close() method on InputStreams that are opened when reading\n compinfo.properties files included within the MQ Java client jar\n files.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v9.0 LTS 9.0.0.4\n \n The latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n \n If the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT24135\n \n \n * REPORTED COMPONENT NAME\n IBM MQ BASE M/P\n \n \n * REPORTED COMPONENT ID\n 5724H7261\n \n \n * REPORTED RELEASE\n 900\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 2018-02-20\n \n \n * CLOSED DATE\n 2018-03-06\n \n \n * LAST MODIFIED DATE\n 2018-03-06\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 IBM MQ BASE M/P\n \n \n * FIXED COMPONENT ID\n 5724H7261\n \n \n\nAPPLICABLE COMPONENT LEVELS", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n What WebSphere MQ 7.5 jar files are needed in Sterling B2B Integrator for them to communicate? \n\nSYMPTOM\nUnable to successfully connect from SBI to WebSphere MQ 7.5 Server.\n\n\nCAUSE\nSBI dynamicclasspath.cfg file contains both MQ 7.0.1.x jar files entries and MQ 7.5 jars files. It should contain only 1 version of WebSphere MQ jar files. There should not be duplicate jars in the dynamicclasspath.cfg\n\nRESOLVING THE PROBLEM\nPlease be aware that the SBI 5.2.4.2 installation comes with the below MQ 7.0.1.x jar files/entries (and maybe some others) already present in the dynamicclasspath.cfg file for SBI, for example:\nVENDOR_JAR={SI_install_dir}/jar/mqseries/7_0_1_6/com.ibm.mq.commonservic\nes.jar\nVENDOR_JAR={SI_install_dir}/jar/mqseries/7_0_1_6/com.ibm.mq.headers.jar\nVENDOR_JAR={SI_install_dir}/jar/mqseries/7_0_1_6/com.ibm.mq.jar\nVENDOR_JAR={SI_install_dir}/jar/mqseries/7_0_1_6/com.ibm.mq.jmqi.jar\nVENDOR_JAR={SI_install_dir}/jar/mqseries/7_0_1_6/com.ibm.mq.pcf.jar\nVENDOR_JAR={SI_install_dir}/jar/mqseries/7_0_1_6/com.ibm.mqjms.jar\n\nThese jar file works well when connecting to WebSphere MQ 7.0.1.\nBut if you want to connect to a higher version of WebSphere MQ Server (e.g. v7.5), currently you MUST first manually remove all of these older existing MQ 7.0.1.x jar files from the dynamicclasspath.cfg file.\n\n\nNext you need to install all of the new client jar files from the WebSphere MQ 7.5 Server library into SBI using the install3rdParty script which is under the SBI /bin dir. You should be able to install all of the new MQ 7.5 jars in one execution just by using an asterisk for the jar file names, or you can install each of the new jars one at a time. \n\n\nNext, restart SBI and configure the WebSphere adapter correctly in SBI to communicate with WebSphere MQ 7.5 Server.\n\nAgain, if you forget to uninstall any of the older existing 7_0_1_6 jars from SBI, and then install the new WebSphere MQ (e.g. v7.5) jars, then there will be duplicate jars in the dynamicclasspath.cfg and this can cause issues as well.", "WebSphere MQ WMQ TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When Java™ 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​:\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&amp;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", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n A JMS application works as expected when using the WebSphere MQ V6 Classes for JMS.\nWhen the application is migrated to the WebSphere MQ V7 Classes for JMS, the application appears to suffer performance degradation. \n\nSYMPTOM\nAnalysis from the Queue Manager perspective when the application is running shows a large number of connections being created and closed.\n\n\nCAUSE\nThe internal JMS connection pooling functionality has been removed from the WebSphere MQ V7 classes for JMS. \n\n \nThe connection pooling functionality provided by the WebSphere MQ V6 classes for JMS allowed connection handles (Hconns) to WebSphere MQ to be stored in a pool where they were available for reuse. This functionality was implemented using the WebSphere MQ classes for Java. This was possible because the WebSphere MQ V6 classes for JMS were implemented as a layer of code on top of the WebSphere MQ V6 classes for Java. In WebSphere MQ V7 the implementation of WebSphere MQ classes for JMS is no longer dependent on WebSphere MQ classes for Java. This means that the WebSphere MQ classes for JMS can no longer access features of the WebSphere MQ classes for Java.\n\nWhen using the WebSphere MQ V6 classes for JMS inside of a Java EE application server, two levels of pooling were provided: \n\n\n * Java EE application servers provided JMS Connection Pools and JMS Session Pools for applications to use.\n\n * When the application server was configured to use the WebSphere MQ V6 classes for JMS, these JMS Connection and JMS Session Pools sat on top of the connection handle pooling provided by the WebSphere MQ classes for JMS. \n\n\nThis led to some confusion about how the JMS Connection and Session Pools provided by application servers worked. It might have looked like there were still open connections from the application servers to WebSphere MQ, even though the JMS Connection and JMS Session Pools were empty. This was because the connection handles associated with the JMS Connections and JMS Sessions that had been removed from the application server Connection and Session Pools were now in the underlying WebSphere MQ classes for JMS connection handle pool. \n\nWhen the WebSphere MQ V7 classes for JMS are used in JEE Application Server environments, JMS Connection and JMS Session Pools are provided as follows: \n * For Inbound Communications, the JMS Connection Pools and JMS Session Pools are implemented by the WebSphere MQ JCA resource adapter. \n * For Outbound Communications, the JMS Connection Pools and JMS Session Pools are implemented by the JEE Application Server. \n\nRESOLVING THE PROBLEM\nStand-alone applications using the WebSphere MQ V7 classes for JMS that require the use of JMS Connection and JMS Session pooling need to be modified to implement their own pooling logic.", "mqminfo permissions sec auth TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You are running WebSphere MQ and your MQ JMS application fails with security authentication errors. \n\nSYMPTOM\nMQRC 2035 MQRC_NOT_AUTHORIZED \n\nMQRC 2063 MQRC_SECURITY_ERROR \n\nMQ V6:\nMQJMS2013: invalid security authentication supplied for MQQueueManager. \n\nMQ V7 and later:\nJMSWMQ2013: The security authentication was not valid that was supplied for QueueManager 'x' with connection mode 'Client' (or 'Bindings') and host name 'y.com'. Please check if the supplied username and password are correct on the QueueManager you are connecting to.\n\n\nCAUSE\nThe MQJMS2013 exception shown in the WebSphere Application Server logs is generated due to a return code 2035 from the MQ queue manager: MQRC_NOT_AUTHORIZED\n\nThis return code is generated because of these possible conditions:\n\na) The userid that is used to start the JVM (WebSphere Application Server) has not been defined in the host where the MQ queue manager is located.\n... or ...\n\nb) The userid is defined, but it does not have the proper authority to work with the queue manager.\n... or ...\n\nc) MQ 7.1 or later: Channel authentication records: the user has been defined and:\nc.1) is a member of the MQ Administration group, but the default channel authentication records do not allow an MQ Administrator to do a remote login.\nc.2) There are no channel authentication records that allow the non-administrator user to access the queue manager.\n... or ...\n\nd) MQ V8: user did not specify password, and queue manager error log shows \nAMQ5540: Application 'Sphere MQ\\bin64\\amqsputc.exe' did not supply a user ID\nand password\nAMQ5541: The failed authentication check was caused by the queue manager\nCONNAUTH CHCKCLNT(REQDADM) configuration.\n\n\n\n\nRESOLVING THE PROBLEM\n+++ If you notice this problem when migrating from WAS 7.0 or 8.0, to WAS 8.5: \n\n\nThe following technote explains a change of behavior regarding security that affects WAS 8.5 (which includes MQ JMS 7.1) with respect to WAS 7.0 and 8.0 (which include MQ JMS 7.0).\n.\nChanges in the default user identifier between WebSphere MQ V7.0.1 classes for JMS and WebSphere MQ V7.1 classes for JMS [http://www.ibm.com/support/docview.wss?uid=swg21662193] \n. \n+ begin quote \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.\n+ end quote \n\n\n \n\n+++ Specifically when using MQ 7.1 or later queue managers: \n\nConsult the following technote:\n\nWMQ 7.1 or later queue manager - RC 2035 MQRC_NOT_AUTHORIZED when using client connection as an MQ Administrator [http://www.ibm.com/support/docview.wss?uid=swg21577137]\n\n+++ Specifically when using MQ 8.0 or later queue managers:\n\nMQ 8.0: errors AMQ5540 and AMQ5541, application did not supply a user ID and password, 2035 MQRC_NOT_AUTHORIZED [http://www.ibm.com/support/docview.wss?uid=swg21680930] \n\n\n+++ General \n\nDetermine the user ID the application is being run under, and then ensure that the user ID is in a group that has sufficient authority on the server where the MQ queue manager is running. \n\nAfter adding the userid into the group that has sufficient authority, issue the runmqsc command: \n\nREFRESH SECURITY(*) \n\n\nWebSphere Application Server JMS Trace (trace.log)\nSome possible return codes in the WebSphere Application Server stack trace could include the following MQ return codes:\n\nMQJE001: An MQException occurred: Completion Code 2, Reason 2035\nThe return code 2035 means \"MQRC_NOT_AUTHORIZED\"\n\nMQJE001: An MQException occurred: Completion Code 2, Reason 2063\nThe return code 2063 means \"MQRC_SECURITY_ERROR\"\n\nIf it is not obvious which user ID is being used to authenticate with the Queue Manager, then you will need to enable the tracing both for the JMS client (and WebSphere Application Server, if you are using it) and the MQ server. See section 'Related URLs'.\n\nFor example, the trace.log for the JMS client could have strings such as these:\ncom.ibm.mq.jms.MQQueueConnectionFactory connecting as user: JohnDoe\ncom.ibm.mq.jms.MQQueueConnection Setting username = JohnDoe\ncom.ibm.mq.MQv6InternalCommunications userID = 'JohnDoe '\ncom.ibm.mq.MQv6InternalCommunications UID :JOHNDOE\n\nMQ server trace:\nIt is very likely that one of the MQ trace files (*.FMT) will have the following string indicating that the value (username) is not a user ID in the system.\n\nUnknownPrincipal(johndoe)\n\nAlso, in case that the userid does exist, another possible cause is that the user does not have all the proper authorizations, thus, check for the following phrase in the trace:\n\nThe following requested permissions are unauthorized: xxx\n\nRelated technotes for problem determination:\n\nBy default, the userid that causes this reason code 2035 (MQRC_NOT_AUTHORIZED) is not shown in the MQ Queue Manager error logs or in the FDC files. The reason is that a rogue application could try to connect thousands of times, and there would be thousands of entries in the logs and thousands of FDC files.\n\nThere are 2 environment variables that can be used with the MQ queue manager in order to show in the MQ Queue Manager error logs and in the FDCs the userid that is causing the reason code 2035. You will need to setup one or both environment variables and then restart the queue managers (these variables are only read during a startup).\n\nFor additional information see the following technotes and APAR:\nMQS_REPORT_NOAUTH environment variable can be used to better diagnose return code 2035 (MQRC_NOT_AUTHORIZED) [http://www.ibm.com/support/docview.wss?uid=swg21299319]\n\nUsing MQSAUTHERRORS to generate FDC files related to RC 2035 (MQRC_NOT_AUTHORIZED) [http://www.ibm.com/support/docview.wss?uid=swg21377578]\n\nIZ49302: THE WEBSPHERE MQ JAVA MESSAGE SERVICE CLIENT MUST TREAT \"\" FOR A USERID THE SAME AS NULL WHEN CREATING CONNECTIONS [http://www.ibm.com/support/docview.wss?uid=swg1IZ49302]\n\n\nRELATED INFORMATION\n MustGather - MQ Getting Traces [http://www.ibm.com/support/docview.wss?&uid=swg21174924]\nEnabling Application Server trace [http://www.ibm.com/support/docview.wss?&uid=swg21199176]\nA Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21651526]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Java Message Service (JMS) 8.5, 8.0, 7.0 \nPRODUCT ALIAS/SYNONYM\n WMQ MQ" ]

[ [ "2a", "WebSphere MQ WMQ TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "2b", " When Java™ 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." ], [ "2c", "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." ], [ "2d", "This error can occur if the application server finds an earlier version of the WebSphere MQ classes for JMS in the class path." ], [ "2e", "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.\" ENVIRONMENT" ], [ "2f", "The mqjavalist.sh script runs on Linux and UNIX systems and can identify Java archives and classes from MQ V5.3 and later versions." ], [ "2g", "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." ], [ "2h", "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." ], [ "2i", "Make sure that either the unzip command or the Java jar command is available in your PATH before running mqjavalist.sh. For example: 1." ], [ "2j", "Preparing to run mqjavalist.sh 2." ], [ "2k", " 3. sh> chmod +x mqjavalist.sh" ], [ "2l", " sh> PATH=$PATH:/opt/java7/bin" ], [ "2m", "DIAGNOSING THE PROBLEM" ], [ "2n", "IBM MQ ships a number of Java archives (jar files) that applications use to connect to MQ and work with messages." ], [ "2o", "For Java EE environments, MQ provides a Resource Adapter called wmq.jmsra.rar which contains the jar files required by JMS applications." ], [ "2p", "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." ], [ "2q", "It 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)." ], [ "2r", "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." ], [ "2s", " * Syntax" ], [ "2t", " * Examples" ], [ "2u", " * WebSphere Application Server" ], [ "2v", " * Sample output" ], [ "2w", " * Resolving problems" ], [ "2x", " * Download SYNTAX" ], [ "2y", " 1. mqjavalist.sh -? | -h 2." ], [ "2z", " 3. mqjavalist.sh [-v] [-r] [-f File] -d Directory ... 4. 5. 6. 7. -? : 8. 9. 10. -h: 11. 12. 13. -v: 14. 15. 16. -r: 17. 18. 19. -f File​: 20. 21. 22. -d Directory: 23. 24. 25. 26. 27. 28." ], [ "2aa", "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." ], [ "2ab", "While running, the script regularly prints its status and the percentage of work completed." ], [ "2ac", "Back to top EXAMPLES 1." ], [ "2ad", "Search for MQ files under /usr/IBM/WebSphere and save the results to the file mqlist.txt:" ], [ "2ae", " mqjavalist.sh -f mqlist.txt -d /usr/IBM/WebSphere 2. 3. 4." ], [ "2af", "Perform a recursive search of archives under /opt/IBM:" ], [ "2ag", " mqjavalist.sh -r -d /opt/IBM 5. 6. 7." ], [ "2ah", "Recursively search archive files under the /opt/IBM/IIB and /opt/mqm directories and enable verbose output to ~/output.txt:" ], [ "2ai", " mqjavalist.sh -vrf ~/output.txt -d /opt/IBM/IIB -d /opt/mqm 8." ], [ "2aj", "Back to top" ], [ "2ak", "WEBSPHERE APPLICATION SERVER" ], [ "2al", "WebSphere Application Server and other IBM products built on WebSphere Application Server normally show the MQ jar files in more than one location." ], [ "2am", "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]." ], [ "2an", "Any copies of the MQ jar files other than those listed below might represent a problem: 1." ], [ "2ao", "WebSphere Application Server V8.5.5, V8.5 and V8.0 2. 3. 1." ], [ "2ap", "WebSphere Application Server V7.0 2. 3. 4. 5. 6." ], [ "2aq", "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]." ], [ "2ar", "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. 1." ], [ "2as", "WebSphere Application Server V6.1 2. 3." ], [ "2at", "Back to top SAMPLE OUTPUT" ], [ "2au", " 1. sh> 2." ], [ "2av", "./mqjavalist.sh -r -f mqlist.txt -d /opt/IBM/WebSphere/AppServer 3. 4." ], [ "2aw", "Running mqjavalist.sh V1.4 on SUSE Linux Enterprise Server 10 (ppc) with arguments: -r -f mqlist.txt -d /opt/IBM/WebSphere/AppServer" ], [ "2ax", " mqjavalist.sh: Searching directory /opt/IBM/WebSphere/AppServer" ], [ "2ay", " mqjavalist.sh: 2180 possible Java archives found" ], [ "2az", " 1." ], [ "2ba", "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:" ], [ "2bb", " root root 145600 2014-07-16 13:56 /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/aemtux1Cell01/applications/WMQHTTP_war.ear/WMQHTTP_war.ear" ], [ "2bc", " 2." ], [ "2bd", "Found 80 MQ classes in /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/aemtux1Cell01/WMQHTTP_war.ear/WMQHTTP.war/WEB-INF/lib/classes.jar:" ], [ "2be", " 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" ], [ "2bf", " 3." ], [ "2bg", "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:" ], [ "2bh", " root root 145600 2014-07-16 13:57 /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/aemtux1Cell01/applications/WMQHTTP_war.ear/WMQHTTP_war.ear" ], [ "2bi", " 4." ], [ "2bj", "Found com.ibm.mq.commonservices.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:" ], [ "2bk", " root root 7885592 2012-10-15 12:56 wmq.jmsra.rar" ], [ "2bl", " Implementation-Title: WebSphere MQ Common Service" ], [ "2bm", " Implementation-Version: ${version.number} - ${build.level}" ], [ "2bn", " Implementation-Vendor: IBM Corporation" ], [ "2bo", " 5." ], [ "2bp", "Found com.ibm.mq.connector.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:" ], [ "2bq", " root root 7885592 2012-10-15 12:56 wmq.jmsra.rar" ], [ "2br", " Implementation-Title: WebSphere MQ J2EE Connector Architecture" ], [ "2bs", " Implementation-Version: 7.1.0.0-k000-L111005.1" ], [ "2bt", " Implementation-Vendor: IBM Corporation" ], [ "2bu", " 6." ], [ "2bv", "Found com.ibm.mq.headers.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:" ], [ "2bw", " root root 7885592 2012-10-15 12:56 /wmq.jmsra.rar" ], [ "2bx", " Implementation-Title: WebSphere MQ classes for Java" ], [ "2by", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2bz", " Implementation-Vendor: IBM Corporation" ], [ "2ca", " 7." ], [ "2cb", "Found com.ibm.mq.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:" ], [ "2cc", " root root 7885592 2012-10-15 12:56 wmq.jmsra.rar" ], [ "2cd", " Implementation-Title: WebSphere MQ classes for Java" ], [ "2ce", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2cf", " Implementation-Vendor: IBM Corporation" ], [ "2cg", " 8." ], [ "2ch", "Found com.ibm.mq.jmqi.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:" ], [ "2ci", " root root 7885592 2012-10-15 12:56 wmq.jmsra.rar" ], [ "2cj", " Implementation-Title: WebSphere MQ classes for Java" ], [ "2ck", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2cl", " Implementation-Vendor: IBM Corporation" ], [ "2cm", " 9." ], [ "2cn", "Found com.ibm.mq.jmqi.local.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:" ], [ "2co", " root root 7885592 2012-10-15 12:56 wmq.jmsra.rar" ], [ "2cp", " Implementation-Title: WebSphere MQ classes for Java" ], [ "2cq", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2cr", " Implementation-Vendor: IBM Corporation" ], [ "2cs", " 10." ], [ "2ct", "Found com.ibm.mq.jmqi.remote.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:" ], [ "2cu", " root root 7885592 2012-10-15 12:56 wmq.jmsra.rar" ], [ "2cv", " Implementation-Title: WebSphere MQ classes for Java" ], [ "2cw", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2cx", " Implementation-Vendor: IBM Corporation" ], [ "2cy", " 11." ], [ "2cz", "Found com.ibm.mq.jmqi.system.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:" ], [ "2da", " root root 7885592 2012-10-15 12:56 wmq.jmsra.rar" ], [ "2db", " Implementation-Title: WebSphere MQ classes for Java" ], [ "2dc", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2dd", " Implementation-Vendor: IBM Corporation" ], [ "2de", " 12." ], [ "2df", "Found com.ibm.mq.jms.admin.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:" ], [ "2dg", " root root 7885592 2012-10-15 12:56 wmq.jmsra.rar" ], [ "2dh", " Implementation-Title: JMS Common Client API/SPI" ], [ "2di", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2dj", " Implementation-Vendor: IBM Corporation" ], [ "2dk", " 13." ], [ "2dl", "Found com.ibm.mq.pcf.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:" ], [ "2dm", " root root 7885592 2012-10-15 12:56 wmq.jmsra.rar" ], [ "2dn", " Implementation-Title: WebSphere MQ classes for Java" ], [ "2do", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2dp", " Implementation-Vendor: IBM Corporation" ], [ "2dq", " 14." ], [ "2dr", "Found com.ibm.mqjms.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:" ], [ "2ds", " root root 7885592 2012-10-15 12:56 wmq.jmsra.rar" ], [ "2dt", " Implementation-Title: JMS Client Common Facade" ], [ "2du", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2dv", " Implementation-Vendor: IBM Corporation" ], [ "2dw", " 15." ], [ "2dx", "Found dhbcore.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:" ], [ "2dy", " root root 7885592 2012-10-15 12:56 wmq.jmsra.rar" ], [ "2dz", " Implementation-Version: \"DH610-GOLD\"" ], [ "2ea", " Implementation-Title: \"Webscale Distribution Hub Core\"" ], [ "2eb", " Implementation-Vendor: \"IBM Corporation\"" ], [ "2ec", " 16. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.jar:" ], [ "2ed", " root root 1115668 2012-10-15 12:56 com.ibm.mq.jmqi.jar" ], [ "2ee", " Implementation-Title: WebSphere MQ classes for Java" ], [ "2ef", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2eg", " Implementation-Vendor: IBM Corporation" ], [ "2eh", " 17. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.commonservices.jar:" ], [ "2ei", " root root 728387 2012-10-15 12:56 com.ibm.mq.commonservices.jar" ], [ "2ej", " Implementation-Title: WebSphere MQ Common Service" ], [ "2ek", " Implementation-Version: ${version.number} - ${build.level}" ], [ "2el", " Implementation-Vendor: IBM Corporation" ], [ "2em", " 18. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.remote.jar:" ], [ "2en", " root root 546407 2012-10-15 12:56 com.ibm.mq.jmqi.remote.jar" ], [ "2eo", " Implementation-Title: WebSphere MQ classes for Java" ], [ "2ep", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2eq", " Implementation-Vendor: IBM Corporation" ], [ "2er", " 19. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jar:" ], [ "2es", " root root 448745 2012-10-15 12:56 com.ibm.mq.jar" ], [ "2et", " Implementation-Title: WebSphere MQ classes for Java" ], [ "2eu", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2ev", " Implementation-Vendor: IBM Corporation" ], [ "2ew", " 20. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jms.admin.jar:" ], [ "2ex", " root root 358016 2012-10-15 12:56 com.ibm.mq.jms.admin.jar" ], [ "2ey", " Implementation-Title: JMS Common Client API/SPI" ], [ "2ez", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2fa", " Implementation-Vendor: IBM Corporation" ], [ "2fb", " 21. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mqjms.jar:" ], [ "2fc", " root root 352254 Aug 01 11:49 com.ibm.mqjms.jar" ], [ "2fd", " Implementation-Title: JMS Common Client facade" ], [ "2fe", " Implementation-Version: 7.0.1.5 - k701-105-110419" ], [ "2ff", " Implementation-Vendor: IBM Corporation" ], [ "2fg", " 22. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.connector.jar:" ], [ "2fh", " root root 339396 2012-10-15 12:56 com.ibm.mq.connector.jar" ], [ "2fi", " Implementation-Title: WebSphere MQ J2EE Connector Architecture" ], [ "2fj", " Implementation-Version: 7.1.0.0-k000-L111005.1" ], [ "2fk", " Implementation-Vendor: IBM Corporation" ], [ "2fl", " 23. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.headers.jar:" ], [ "2fm", " root root 338572 2012-10-15 12:56 com.ibm.mq.headers.jar" ], [ "2fn", " Implementation-Title: WebSphere MQ classes for Java" ], [ "2fo", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2fp", " Implementation-Vendor: IBM Corporation" ], [ "2fq", " 24. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.local.jar:" ], [ "2fr", " root root 224747 2012-10-15 12:56 com.ibm.mq.jmqi.local.jar" ], [ "2fs", " Implementation-Title: WebSphere MQ classes for Java" ], [ "2ft", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2fu", " Implementation-Vendor: IBM Corporation" ], [ "2fv", " 25. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.system.jar:" ], [ "2fw", " root root 209738 2012-10-15 12:56 com.ibm.mq.jmqi.system.jar" ], [ "2fx", " Implementation-Title: WebSphere MQ classes for Java" ], [ "2fy", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2fz", " Implementation-Vendor: IBM Corporation" ], [ "2ga", " 26. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.pcf.jar:" ], [ "2gb", " root root 125200 2012-10-15 12:56 com.ibm.mq.pcf.jar" ], [ "2gc", " Implementation-Title: WebSphere MQ classes for Java" ], [ "2gd", " Implementation-Version: 7.1.0.0 - k000-L111005.1" ], [ "2ge", " Implementation-Vendor: IBM Corporation" ], [ "2gf", " 27. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/dhbcore.jar:" ], [ "2gg", " root root 2011835 2012-10-15 12:56 dhbcore.jar" ], [ "2gh", " Implementation-Version: \"DH610-GOLD\"" ], [ "2gi", " Implementation-Title: \"Webscale Distribution Hub Core\"" ], [ "2gj", " Implementation-Vendor: \"IBM Corporation\"" ], [ "2gk", " mqjavalist.sh: 27 jar files with MQ code found in /opt/IBM/WebSphere/AppServer" ], [ "2gl", " mqjavalist.sh: 27 total jar files with MQ code found" ], [ "2gm", " mqjavalist.sh: Results saved to mqlist.txt 5. 6." ], [ "2gn", "Back to top" ], [ "2go", "RESOLVING THE PROBLEM" ], [ "2gp", "Review the output from mqjavalist.sh to determine where copies of the MQ jar files have been found." ], [ "2gq", "Not all duplicates represent a problem, unless they are being loaded by your Java SE application or Java EE application server at runtime." ], [ "2gr", "If the com.ibm.mq.commonservices.jar file shows an implementation version of ${version.number} - ${build.level} just ignore it." ], [ "2gs", "In the sample output above, entries #16 through #27 represent the jar files for the installed MQ Resource Adapter." ], [ "2gt", "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." ], [ "2gu", "Because the jar file versions are not in sync, MQ JMS will not function as expected." ], [ "2gv", "In cases like this, the wmq.jmsra.rar file should contain a copy of the MQ jar at the right level for the application server." ], [ "2gw", "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." ], [ "2gx", "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." ], [ "2gy", "Use chown and chmod to ensure the permissions on the file are correct." ], [ "2gz", "In 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." ], [ "2ha", "Eliminating unnecessary classpath entries can resolve the problem." ], [ "2hb", "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." ], [ "2hc", "Back to top Additional Keywords:" ], [ "2hd", "troubleshoot troubleshooting trouble shoot classloader classpath configuration scripts DOWNLOAD 1." ], [ "2he", " 2. mqjavalist.sh [/support/docview.wss?uid=swg21681142&amp;aid=2]mqjavalist.sh" ], [ "2hf", "DISCLAIMER: All source code and/or binaries attached to this document are referred to here as \"the Program\"." ], [ "2hg", "IBM is not providing program services of any kind for the Program." ], [ "2hh", "IBM is providing the Program on an \"AS IS\" basis without warranty of any kind." ], [ "2hi", "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." ], [ "2hj", "Back to top" ] ]

[ "2b", "2d", "2g", "2p", "2q", "2r", "2v", "2x", "2aa", "2gp", "2gr", "2gu", "2gv", "2gz", "2ha" ]

[ " A FIX IS AVAILABLE\nFixes integrated in WebSphere Portal 8.0.0.1 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24034497]\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Hung BackgroundCache thread reported by WAS during pre-rendering\n of a large site.\n \n Example messages in the system log:\n ThreadMonitor W ﾠ ﾠ WSVR0605W: Thread\n \"WorkManager.wpsDefaultWorkManager : 2\" (0000006f) has been\n active for 719719 milliseconds and may be hung. ﾠ There is/are 4\n thread(s) in total in the server that may be hung.\n at java.lang.Thread.sleep(Native Method)\n at java.lang.Thread.sleep(Thread.java:896)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:303)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:347)\n at com.aptrix.cacher.Cacher.storePreRenderedContent(Cacher)\n at com.aptrix.cacher.Cacher.cache(Cacher.java:213)\n ...\n \n \n \n \n \n\nLOCAL FIX\n * None available\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Hung BackgroundCache thread reported by WAS during pre-rendering\n of a large site.\n \n Example messages in the system log:\n ThreadMonitor W  WSVR0605W: Thread\n \"WorkManager.wpsDefaultWorkManager : 2\" (0000006f) has been\n active for 719719 milliseconds and may be hung.  There is/are 4\n thread(s) in total in the server that may be hung.\n at java.lang.Thread.sleep(Native Method)\n at java.lang.Thread.sleep(Thread.java:896)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:303)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:347)\n at com.aptrix.cacher.Cacher.storePreRenderedContent(Cacher)\n at com.aptrix.cacher.Cacher.cache(Cacher.java:213)\n ...\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Code was modified to prevent the hung threads from occurring\n during the pre-rendering of large sites.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM95353\n \n \n * REPORTED COMPONENT NAME\n LOTUS WEB CONT\n \n \n * REPORTED COMPONENT ID\n 5724I2900\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 2013-08-19\n \n \n * CLOSED DATE\n 2013-09-08\n \n \n * LAST MODIFIED DATE\n 2013-09-08\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 LOTUS WEB CONT\n \n \n * FIXED COMPONENT ID\n 5724I2900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R800 PSY\n UP", " FIXES ARE AVAILABLE\n6.1.0.5 Download: WebSphere Portal and WCM V6.1.0 fix pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24027475]\n6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24030970]\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 * Under some rare conditions a hang can be seen when Portlet\n actions are executed. These conditions are that the same action\n ID is submitted more than one time by a Portlet and garbage\n collection occours between the 2 actions.\n \n In the logs a NullPointerException can be seen:\n \n [6/9/10 9:13:07:007 CDT] 0000006a Servlet E\n com.ibm.wps.engine.Servlet handleException EJPEJ0070E: An\n exception occurred while processing the request.\n java.lang.NullPointerException\n at com.ibm.wps.engine.phases.WPActionPhase$LockManager$Data\n .access$200(WPActionPhase.java:3462)\n at com.ibm.wps.engine.phases.WPActionPhase$LockManager\n .lockReleased(WPActionPhase.java:3453)\n at com.ibm.wps.engine.phases.WPActionPhase\n .processPortlets(WPActionPhase.java:2762)\n at com.ibm.wps.engine.phases.WPActionPhase\n .execute(WPActionPhase.java:668)\n at com.ibm.wps.state.phases.AbstractActionPhase\n .next(AbstractActionPhase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888)\n ...\n \n Some minutes later the Application Server will report hang\n threads:\n \n [6/9/10 9:22:41:135 CDT] 00000025 ThreadMonitor W WSVR0605W:\n Thread \"WebContainer : 31\" (00000088) has been active for\n 602945\n milliseconds and may be hung. There is/are 1 thread(s) in\n total\n in the server that may be hung.\n at sun.misc.Unsafe.park(Native Method)\n at java.util.concurrent.locks.LockSupport.park(LockSupport\n .java:158)\n at java.util.concurrent.locks.AbstractQueuedSynchronizer\n .parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:747)\n at java.util.concurrent.locks.AbstractQueuedSynchronizer\n .acquireQueued(AbstractQueuedSynchronizer.java:778)\n at java.util.concurrent.locks.AbstractQueuedSynchronizer\n .acquire(AbstractQueuedSynchronizer.java:1114)\n at java.util.concurrent.locks.ReentrantLock$FairSync\n .lock(ReentrantLock.java:201)\n at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock\n .java:262)\n at com.ibm.wps.engine.phases.WPActionPhase\n .processPortlets(WPActionPhase.java:2463)\n at com.ibm.wps.engine.phases.WPActionPhase\n .execute(WPActionPhase.java:668)\n at com.ibm.wps.state.phases.AbstractActionPhase\n .next(AbstractActionPhase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888)\n ...\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * Under some rare conditions a hang can be seen when Portlet\n actions are executed. These conditions are that the same action\n ID is submitted more than one time by a Portlet and garbage\n collection occurs between the 2 actions. In the logs a\n NullPointerException can be seen:\n \n [6/9/10 9:13:07:007 CDT] 0000006a Servlet E\n com.ibm.wps.engine.Servlet handleException EJPEJ0070E: An\n exception occurred while processing the request.\n java.lang.NullPointerException at\n com.ibm.wps.engine.phases.WPActionPhase$LockManager$Data.access$\n 200(WPActionPhase.java:3462)\n at\n com.ibm.wps.engine.phases.WPActionPhase$LockManager.lockReleased\n (WPActionPhase.java:3453)\n at\n com.ibm.wps.engine.phases.WPActionPhase.processPortlets(WPAction\n Phase.java:2762)\n at\n com.ibm.wps.engine.phases.WPActionPhase.execute(WPActionPhase.ja\n va:668)\n at\n com.ibm.wps.state.phases.AbstractActionPhase.next(AbstractAction\n Phase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888) ...\n S\n \n Some minutes later the Application Server will report hang\n threads:\n \n [6/9/10 9:22:41:135 CDT] 00000025 ThreadMonitor W\n WSVR0605W: Thread \"WebContainer : 31\" (00000088) has been active\n for 602945 milliseconds and may be hung. There is/are 1\n thread(s) in total in the server that may be hung.\n at sun.misc.Unsafe.park(Native Method) at\n java.util.concurrent.locks.LockSupport.park(LockSupport.java:158\n )\n at\n java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndChe\n ckInterrupt(AbstractQueuedSynchronizer.java:747)\n at\n java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQue\n ued(AbstractQueuedSynchronizer.java:778)\n at\n java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(Ab\n stractQueuedSynchronizer.java:1114)\n at\n java.util.concurrent.locks.ReentrantLock$FairSync.lock(Reentrant\n Lock.java:201)\n at\n java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java\n :262)\n at\n com.ibm.wps.engine.phases.WPActionPhase.processPortlets(WPAction\n Phase.java:2463)\n at\n com.ibm.wps.engine.phases.WPActionPhase.execute(WPActionPhase.ja\n va:668)\n at\n com.ibm.wps.state.phases.AbstractActionPhase.next(AbstractAction\n Phase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888) ...\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Fixed action ID synchronization.\n \n Failing Module(s):\n Engine: State handling\n \n Affected Users:\n All Users\n \n Version Information:\n Portal Version(s): 6.1.0.3\n Pre-Requisite(s): ---\n Co-Requisite(s): ---\n \n Manuel Steps:\n None\n \n Platform Specific:\n This fix applies to all platforms.\n \n \n PM16223 is part of Cumulative Fix 06 for Portal 6.1.0.3/6.1.5.0.\n \n The fix is available from Fix Central:\n \n http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde\n r?apar=PM14900&productid=WebSphere%20Portal&brandid=5 [http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorder?apar=PM14900&productid=WebSphere%20Portal&brandid=5]\n \n You may need to type or paste the complete address into your Web\n browser.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM16223\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE PORTA\n \n \n * REPORTED COMPONENT ID\n 5724E7600\n \n \n * REPORTED RELEASE\n 61C\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 2010-06-10\n \n \n * CLOSED DATE\n 2010-07-20\n \n \n * LAST MODIFIED DATE\n 2010-07-20\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 * R61C PSY\n UP", " A FIX IS AVAILABLE\nVersion 8.5 Refresh Pack 7 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24041575]\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Hung threads are observed in the SystemOut.log with a stack\n similar to the following:\n \n [2/19/15 11:04:27:790 CST] 00000036 ThreadMonitor W WSVR0605W:\n Thread \"server.startup : 0\" (0000008a) has been active for\n 632013 milliseconds and may be hung. There is/are 8 thread(s)\n in total in the server that may be hung.\n at java.util.zip.ZipFile.open(Native Method)\n at java.util.zip.ZipFile.(ZipFile.java:140)\n at java.util.jar.JarFile.(JarFile.java:140)\n at java.util.jar.JarFile.(JarFile.java:77)\n at sun.net.www.protocol.jar.URLJarFile.(URLJarFile.java:84)\n at\n sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:6\n 0)\n at\n sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:\n 92)\n at\n sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnecti\n on.java:119)\n at\n sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLC\n onnection.java:147)\n at\n com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe\n r$1.run(FileLoaderHelper.java:69)\n at\n com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe\n r$1.run(FileLoaderHelper.java:64)\n at\n java.security.AccessController.doPrivileged(AccessController.jav\n a:327)\n at\n com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe\n r.openJarStream(FileLoaderHelper.java:64)\n at\n com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe\n r.openStream(FileLoaderHelper.java:53)\n at\n com.ibm.ws.sibx.scax.mediation.model.xml.loader.XMLMedflowModelL\n oaderUtil.initialiseMedflowInputStream(XMLMedflowModelLoaderUtil\n .java:431)\n at\n com.ibm.ws.sibx.scax.mediation.model.xml.loader.XMLMedflowModelL\n oaderUtil.isReadableFormat(XMLMedflowModelLoaderUtil.java:230)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n Users of Business Process Manager v8.5 who have human readable\n mediation flows and are making use of the preload WebSphere\n environment variable to load the flows at application startup.\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n During preload a large amount of processing time was spent\n reading the mediation flow file (mfc) to determine if the flow\n was in a human readable format. This increased the time required\n to start the application server.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * A new WebSphere environment variable has been added to bypass\n the code that determines if the flow is in a human readable\n format, this reduces the time taken to start the server.\n \n The variable applies to the whole server and should only be set\n if all of the mediation flows for all applications are in a\n human readable format. This property should not be used if any\n of the mediation flows are in the old EMF (non-human readable)\n format.\n \n The variable is defined using the Integrated Solutions Console,\n located under:\n Environment -> WebSphere Variables.\n \n name: WESB_HUMAN_READABLE_VALUE\n value: true\n \n The variable should be set at the server scope and the server\n must be restarted before it will take affect.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT07543\n \n \n * REPORTED COMPONENT NAME\n WESB IN BPM\n \n \n * REPORTED COMPONENT ID\n AIMCMFC00\n \n \n * REPORTED RELEASE\n 855\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-03-06\n \n \n * CLOSED DATE\n 2015-03-25\n \n \n * LAST MODIFIED DATE\n 2015-03-25\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 WESB IN BPM\n \n \n * FIXED COMPONENT ID\n AIMCMFC00\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R855 PSY\n UP", "ITNCM; Server; startup; start up; events; timeout; Thread \"server.startup : TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Scenario where an existing ITNCM DB was migrated to a new server, and a new presentation/worker server was installed. After all steps completed, the server would not start successfully. \n\nSYMPTOM\nCustomer will see the following when trying to start ITNCM:\n\n\nIBM Tivoli Netcool Configuration Manager\n----------------------------------------\nStarting Worker Server\nWorker Server = RUNNING\n\n\nStarting Compliance Server\nCompliance Server = RUNNING\n\nStarting GUI Server\nGUI Server = NOT RUNNING <- GUI is not starting\n\n**************************************************************** \n\n\n\nCAUSE\nThe customer did not have \"housekeeping\" configured and running. This resulted in a lot of 'events' in the EVENTS table of the DB. When the server attempted to startup, it was trying to process all of these 'events', but would timeout before completing. Thus, it would not start up successfully.\n\nDIAGNOSING THE PROBLEM\nThe customer may see the following error in the systemout log file:\n\n[5/11/15 6:16:00:262 GMT+00:00] 00000023 ThreadMonitor W WSVR0605W: Thread \"server.startup : 1\" (0000001d) has been active for 779275 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.\nat com.ibm.tivoli.ncm.events.DatabasePoller.addConsumer(DatabasePoller.java:69)\nat com.ibm.tivoli.nsm.work.NSMEventConsumer.register(NSMEventConsumer.java:33)\nat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\n\n\n\nRESOLVING THE PROBLEM\nThe customer will need to manually clear out the 'events' in the EVENTS table using the following SQL command:\n\n\nDELETE FROM EVENTS WHERE UNIQUEKEY NOT IN (SELECT DISTINCT(LASTEVENTKEY) FROM EVENTPOLLERINSTANCES);\n\n\nDepending on the volume of EVENTS records, this may take a long time to execute. If the customer wishes, they can break it down into chunks of deletions using the SQL below:\n\nDELETE FROM EVENTS WHERE CREATEDTIME&lt;? AND ROWNUM&lt;=10000\nAND UNIQUEKEY NOT IN (SELECT DISTINCT(LASTEVENTKEY) FROM EVENTPOLLERINSTANCES);\n\n\nNote: It is important that the customer delete using this method rather than just emptying the table, as there are some events that ITNCM requires. \n\n\n\nTo prevent this from happening in the future, the customer should configure and enable internal housekeeping on their server. In case of a mutil server-deployment, internal housekeeping should only be enabled on one of the servers. To enable and configure Internal Housekeeping, follow the directions found on the following links:\n\nhttp://www-01.ibm.com/support/knowledgecenter/SS7UH9_6.4.1/ncm/wip/confg/task/ncm_config_internalhousekeeping.dita?lang=en [http://www-01.ibm.com/support/knowledgecenter/SS7UH9_6.4.1/ncm/wip/confg/task/ncm_config_internalhousekeeping.dita?lang=en]\n\n\nhttp://www-01.ibm.com/support/knowledgecenter/SS7UH9_6.4.1/ncm/wip/adm/concept/ncm_adm_housekeeping.dita?cp=SS7UH9_6.4.1%2F13-5&lang=en [http://www-01.ibm.com/support/knowledgecenter/SS7UH9_6.4.1/ncm/wip/adm/concept/ncm_adm_housekeeping.dita?cp=SS7UH9_6.4.1%2F13-5&lang=en]", " FIXES ARE AVAILABLE\n8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24037574]\n8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24038133]\n8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24038539]\n8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24039242]\n8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24039425]\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 * Hung thread, CPU issue:\n \n ThreadMonitor W WSVR0605W: Thread \"WebContainer : 0\" (0000005b)\n has been active for 694749 milliseconds and may be hung. There\n is/are 1 thread(s) in total in the server that may be hung.\n \n atcom.ibm.xml.xci.dp.cache.dom.CacheNodeSequence.appendSequence\n (CacheNodeSequence.java:678)\n \n atcom.ibm.xml.xci.dp.cache.dom.CacheNodeSequence.sequenceConcat\n (CacheNodeSequence.java:403)\n \n atcom.ibm.xltxe.rnm1.xtq.xslt.runtime.v2.BasisLibrary2.\n xpathStep(BasisLibrary2.java:4907)\n \n \n \n \n \n\nLOCAL FIX\n * n/a\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 *\n ****************************************************************\n * PROBLEM DESCRIPTION: Hung thread in CacheNodeSequence due to *\n * frequent array expansion *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n The algorithm to expand the array in\n com.ibm.xml.xci.dp.cache.dom.CacheNodeSequence consumes a lot of\n resources when iterating over an extremely large Cursor set that\n contains thousands of nodes. The following hung thread message\n could be seen :\n Thread \"WebContainer : 5\" (00000dab) has been active for 669268\n milliseconds and may be hung. There is/are 1 thread(s) in total\n in the server that may be hung.\n at\n com.ibm.xml.xci.dp.cache.dom.CacheNodeSequence.appendSequence(Ca\n cheNodeSequence.java:678)\n at\n com.ibm.xml.xci.dp.cache.dom.CacheNodeSequence.sequenceConcat(Ca\n cheNodeSequence.java:403)\n at\n com.ibm.xltxe.rnm1.xtq.xslt.runtime.v2.BasisLibrary2.xpathStep(B\n asisLibrary2.java:4907)\n .....\n .....\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The new algorithm expands the array more efficiently and does\n not exhaust the system which prevents the thread from being\n hung.\n \n The fix for this APAR is currently targeted for inclusion in\n fix packs 8.0.0.9 and 8.5.5.3. 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 PI15317\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 700\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-04-04\n \n \n * CLOSED DATE\n 2014-05-02\n \n \n * LAST MODIFIED DATE\n 2014-05-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 PI15529 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI15529]\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" ]

[ [ "0a", " A FIX IS AVAILABLE" ], [ "0b", "Fixes integrated in WebSphere Portal 8.0.0.1 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24034497] APAR STATUS" ], [ "0c", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "0d", " * Hung BackgroundCache thread reported by WAS during pre-rendering" ], [ "0e", " of a large site." ], [ "0f", " Example messages in the system log:" ], [ "0g", " ThreadMonitor W ﾠ ﾠ WSVR0605W: Thread" ], [ "0h", " \"WorkManager.wpsDefaultWorkManager : 2\" (0000006f) has been" ], [ "0i", " active for 719719 milliseconds and may be hung." ], [ "0j", "ﾠ There is/are 4" ], [ "0k", " thread(s) in total in the server that may be hung." ], [ "0l", " at java.lang.Thread.sleep(Native Method)" ], [ "0m", " at java.lang.Thread.sleep(Thread.java:896)" ], [ "0n", " at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:303)" ], [ "0o", " at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:347)" ], [ "0p", " at com.aptrix.cacher.Cacher.storePreRenderedContent(Cacher)" ], [ "0q", " at com.aptrix.cacher.Cacher.cache(Cacher.java:213)" ], [ "0r", " ... LOCAL FIX" ], [ "0s", " * None available PROBLEM SUMMARY" ], [ "0t", " * Hung BackgroundCache thread reported by WAS during pre-rendering" ], [ "0u", " of a large site." ], [ "0v", " Example messages in the system log:" ], [ "0w", " ThreadMonitor W  WSVR0605W: Thread" ], [ "0x", " \"WorkManager.wpsDefaultWorkManager : 2\" (0000006f) has been" ], [ "0y", " active for 719719 milliseconds and may be hung." ], [ "0z", "There is/are 4" ], [ "0aa", " thread(s) in total in the server that may be hung." ], [ "0ab", " at java.lang.Thread.sleep(Native Method)" ], [ "0ac", " at java.lang.Thread.sleep(Thread.java:896)" ], [ "0ad", " at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:303)" ], [ "0ae", " at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:347)" ], [ "0af", " at com.aptrix.cacher.Cacher.storePreRenderedContent(Cacher)" ], [ "0ag", " at com.aptrix.cacher.Cacher.cache(Cacher.java:213)" ], [ "0ah", " ... PROBLEM CONCLUSION" ], [ "0ai", " * Code was modified to prevent the hung threads from occurring" ], [ "0aj", " during the pre-rendering of large sites. TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "0ak", " * APAR NUMBER" ], [ "0al", " PM95353" ], [ "0am", " * REPORTED COMPONENT NAME" ], [ "0an", " LOTUS WEB CONT" ], [ "0ao", " * REPORTED COMPONENT ID" ], [ "0ap", " 5724I2900" ], [ "0aq", " * REPORTED RELEASE" ], [ "0ar", " 800" ], [ "0as", " * STATUS" ], [ "0at", " CLOSED PER" ], [ "0au", " * PE" ], [ "0av", " NoPE" ], [ "0aw", " * HIPER" ], [ "0ax", " NoHIPER" ], [ "0ay", " * SPECIAL ATTENTION" ], [ "0az", " NoSpecatt" ], [ "0ba", " * SUBMITTED DATE" ], [ "0bb", " 2013-08-19" ], [ "0bc", " * CLOSED DATE" ], [ "0bd", " 2013-09-08" ], [ "0be", " * LAST MODIFIED DATE" ], [ "0bf", " 2013-09-08" ], [ "0bg", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "0bh", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "0bi", " * FIXED COMPONENT NAME" ], [ "0bj", " LOTUS WEB CONT" ], [ "0bk", " * FIXED COMPONENT ID" ], [ "0bl", " 5724I2900" ], [ "0bm", "APPLICABLE COMPONENT LEVELS" ], [ "0bn", " * R800 PSY" ], [ "0bo", " UP" ] ]

[ "0d", "0h", "0t", "0x", "0ai", "1f", "1g", "1dx", "2d", "2q", "2ae", "2bj" ]

[ " A FIX IS AVAILABLE\nFixes integrated in WebSphere Portal 8.0.0.1 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24034497]\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Hung BackgroundCache thread reported by WAS during pre-rendering\n of a large site.\n \n Example messages in the system log:\n ThreadMonitor W ﾠ ﾠ WSVR0605W: Thread\n \"WorkManager.wpsDefaultWorkManager : 2\" (0000006f) has been\n active for 719719 milliseconds and may be hung. ﾠ There is/are 4\n thread(s) in total in the server that may be hung.\n at java.lang.Thread.sleep(Native Method)\n at java.lang.Thread.sleep(Thread.java:896)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:303)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:347)\n at com.aptrix.cacher.Cacher.storePreRenderedContent(Cacher)\n at com.aptrix.cacher.Cacher.cache(Cacher.java:213)\n ...\n \n \n \n \n \n\nLOCAL FIX\n * None available\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Hung BackgroundCache thread reported by WAS during pre-rendering\n of a large site.\n \n Example messages in the system log:\n ThreadMonitor W  WSVR0605W: Thread\n \"WorkManager.wpsDefaultWorkManager : 2\" (0000006f) has been\n active for 719719 milliseconds and may be hung.  There is/are 4\n thread(s) in total in the server that may be hung.\n at java.lang.Thread.sleep(Native Method)\n at java.lang.Thread.sleep(Thread.java:896)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:303)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:347)\n at com.aptrix.cacher.Cacher.storePreRenderedContent(Cacher)\n at com.aptrix.cacher.Cacher.cache(Cacher.java:213)\n ...\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Code was modified to prevent the hung threads from occurring\n during the pre-rendering of large sites.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM95353\n \n \n * REPORTED COMPONENT NAME\n LOTUS WEB CONT\n \n \n * REPORTED COMPONENT ID\n 5724I2900\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 2013-08-19\n \n \n * CLOSED DATE\n 2013-09-08\n \n \n * LAST MODIFIED DATE\n 2013-09-08\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 LOTUS WEB CONT\n \n \n * FIXED COMPONENT ID\n 5724I2900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R800 PSY\n UP", " FIXES ARE AVAILABLE\n6.1.0.5 Download: WebSphere Portal and WCM V6.1.0 fix pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24027475]\n6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24030970]\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 * Under some rare conditions a hang can be seen when Portlet\n actions are executed. These conditions are that the same action\n ID is submitted more than one time by a Portlet and garbage\n collection occours between the 2 actions.\n \n In the logs a NullPointerException can be seen:\n \n [6/9/10 9:13:07:007 CDT] 0000006a Servlet E\n com.ibm.wps.engine.Servlet handleException EJPEJ0070E: An\n exception occurred while processing the request.\n java.lang.NullPointerException\n at com.ibm.wps.engine.phases.WPActionPhase$LockManager$Data\n .access$200(WPActionPhase.java:3462)\n at com.ibm.wps.engine.phases.WPActionPhase$LockManager\n .lockReleased(WPActionPhase.java:3453)\n at com.ibm.wps.engine.phases.WPActionPhase\n .processPortlets(WPActionPhase.java:2762)\n at com.ibm.wps.engine.phases.WPActionPhase\n .execute(WPActionPhase.java:668)\n at com.ibm.wps.state.phases.AbstractActionPhase\n .next(AbstractActionPhase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888)\n ...\n \n Some minutes later the Application Server will report hang\n threads:\n \n [6/9/10 9:22:41:135 CDT] 00000025 ThreadMonitor W WSVR0605W:\n Thread \"WebContainer : 31\" (00000088) has been active for\n 602945\n milliseconds and may be hung. There is/are 1 thread(s) in\n total\n in the server that may be hung.\n at sun.misc.Unsafe.park(Native Method)\n at java.util.concurrent.locks.LockSupport.park(LockSupport\n .java:158)\n at java.util.concurrent.locks.AbstractQueuedSynchronizer\n .parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:747)\n at java.util.concurrent.locks.AbstractQueuedSynchronizer\n .acquireQueued(AbstractQueuedSynchronizer.java:778)\n at java.util.concurrent.locks.AbstractQueuedSynchronizer\n .acquire(AbstractQueuedSynchronizer.java:1114)\n at java.util.concurrent.locks.ReentrantLock$FairSync\n .lock(ReentrantLock.java:201)\n at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock\n .java:262)\n at com.ibm.wps.engine.phases.WPActionPhase\n .processPortlets(WPActionPhase.java:2463)\n at com.ibm.wps.engine.phases.WPActionPhase\n .execute(WPActionPhase.java:668)\n at com.ibm.wps.state.phases.AbstractActionPhase\n .next(AbstractActionPhase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888)\n ...\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * Under some rare conditions a hang can be seen when Portlet\n actions are executed. These conditions are that the same action\n ID is submitted more than one time by a Portlet and garbage\n collection occurs between the 2 actions. In the logs a\n NullPointerException can be seen:\n \n [6/9/10 9:13:07:007 CDT] 0000006a Servlet E\n com.ibm.wps.engine.Servlet handleException EJPEJ0070E: An\n exception occurred while processing the request.\n java.lang.NullPointerException at\n com.ibm.wps.engine.phases.WPActionPhase$LockManager$Data.access$\n 200(WPActionPhase.java:3462)\n at\n com.ibm.wps.engine.phases.WPActionPhase$LockManager.lockReleased\n (WPActionPhase.java:3453)\n at\n com.ibm.wps.engine.phases.WPActionPhase.processPortlets(WPAction\n Phase.java:2762)\n at\n com.ibm.wps.engine.phases.WPActionPhase.execute(WPActionPhase.ja\n va:668)\n at\n com.ibm.wps.state.phases.AbstractActionPhase.next(AbstractAction\n Phase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888) ...\n S\n \n Some minutes later the Application Server will report hang\n threads:\n \n [6/9/10 9:22:41:135 CDT] 00000025 ThreadMonitor W\n WSVR0605W: Thread \"WebContainer : 31\" (00000088) has been active\n for 602945 milliseconds and may be hung. There is/are 1\n thread(s) in total in the server that may be hung.\n at sun.misc.Unsafe.park(Native Method) at\n java.util.concurrent.locks.LockSupport.park(LockSupport.java:158\n )\n at\n java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndChe\n ckInterrupt(AbstractQueuedSynchronizer.java:747)\n at\n java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQue\n ued(AbstractQueuedSynchronizer.java:778)\n at\n java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(Ab\n stractQueuedSynchronizer.java:1114)\n at\n java.util.concurrent.locks.ReentrantLock$FairSync.lock(Reentrant\n Lock.java:201)\n at\n java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java\n :262)\n at\n com.ibm.wps.engine.phases.WPActionPhase.processPortlets(WPAction\n Phase.java:2463)\n at\n com.ibm.wps.engine.phases.WPActionPhase.execute(WPActionPhase.ja\n va:668)\n at\n com.ibm.wps.state.phases.AbstractActionPhase.next(AbstractAction\n Phase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888) ...\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Fixed action ID synchronization.\n \n Failing Module(s):\n Engine: State handling\n \n Affected Users:\n All Users\n \n Version Information:\n Portal Version(s): 6.1.0.3\n Pre-Requisite(s): ---\n Co-Requisite(s): ---\n \n Manuel Steps:\n None\n \n Platform Specific:\n This fix applies to all platforms.\n \n \n PM16223 is part of Cumulative Fix 06 for Portal 6.1.0.3/6.1.5.0.\n \n The fix is available from Fix Central:\n \n http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde\n r?apar=PM14900&productid=WebSphere%20Portal&brandid=5 [http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorder?apar=PM14900&productid=WebSphere%20Portal&brandid=5]\n \n You may need to type or paste the complete address into your Web\n browser.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM16223\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE PORTA\n \n \n * REPORTED COMPONENT ID\n 5724E7600\n \n \n * REPORTED RELEASE\n 61C\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 2010-06-10\n \n \n * CLOSED DATE\n 2010-07-20\n \n \n * LAST MODIFIED DATE\n 2010-07-20\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 * R61C PSY\n UP", " A FIX IS AVAILABLE\nVersion 8.5 Refresh Pack 7 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24041575]\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Hung threads are observed in the SystemOut.log with a stack\n similar to the following:\n \n [2/19/15 11:04:27:790 CST] 00000036 ThreadMonitor W WSVR0605W:\n Thread \"server.startup : 0\" (0000008a) has been active for\n 632013 milliseconds and may be hung. There is/are 8 thread(s)\n in total in the server that may be hung.\n at java.util.zip.ZipFile.open(Native Method)\n at java.util.zip.ZipFile.(ZipFile.java:140)\n at java.util.jar.JarFile.(JarFile.java:140)\n at java.util.jar.JarFile.(JarFile.java:77)\n at sun.net.www.protocol.jar.URLJarFile.(URLJarFile.java:84)\n at\n sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:6\n 0)\n at\n sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:\n 92)\n at\n sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnecti\n on.java:119)\n at\n sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLC\n onnection.java:147)\n at\n com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe\n r$1.run(FileLoaderHelper.java:69)\n at\n com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe\n r$1.run(FileLoaderHelper.java:64)\n at\n java.security.AccessController.doPrivileged(AccessController.jav\n a:327)\n at\n com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe\n r.openJarStream(FileLoaderHelper.java:64)\n at\n com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe\n r.openStream(FileLoaderHelper.java:53)\n at\n com.ibm.ws.sibx.scax.mediation.model.xml.loader.XMLMedflowModelL\n oaderUtil.initialiseMedflowInputStream(XMLMedflowModelLoaderUtil\n .java:431)\n at\n com.ibm.ws.sibx.scax.mediation.model.xml.loader.XMLMedflowModelL\n oaderUtil.isReadableFormat(XMLMedflowModelLoaderUtil.java:230)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n Users of Business Process Manager v8.5 who have human readable\n mediation flows and are making use of the preload WebSphere\n environment variable to load the flows at application startup.\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n During preload a large amount of processing time was spent\n reading the mediation flow file (mfc) to determine if the flow\n was in a human readable format. This increased the time required\n to start the application server.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * A new WebSphere environment variable has been added to bypass\n the code that determines if the flow is in a human readable\n format, this reduces the time taken to start the server.\n \n The variable applies to the whole server and should only be set\n if all of the mediation flows for all applications are in a\n human readable format. This property should not be used if any\n of the mediation flows are in the old EMF (non-human readable)\n format.\n \n The variable is defined using the Integrated Solutions Console,\n located under:\n Environment -> WebSphere Variables.\n \n name: WESB_HUMAN_READABLE_VALUE\n value: true\n \n The variable should be set at the server scope and the server\n must be restarted before it will take affect.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT07543\n \n \n * REPORTED COMPONENT NAME\n WESB IN BPM\n \n \n * REPORTED COMPONENT ID\n AIMCMFC00\n \n \n * REPORTED RELEASE\n 855\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-03-06\n \n \n * CLOSED DATE\n 2015-03-25\n \n \n * LAST MODIFIED DATE\n 2015-03-25\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 WESB IN BPM\n \n \n * FIXED COMPONENT ID\n AIMCMFC00\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R855 PSY\n UP", "ITNCM; Server; startup; start up; events; timeout; Thread \"server.startup : TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Scenario where an existing ITNCM DB was migrated to a new server, and a new presentation/worker server was installed. After all steps completed, the server would not start successfully. \n\nSYMPTOM\nCustomer will see the following when trying to start ITNCM:\n\n\nIBM Tivoli Netcool Configuration Manager\n----------------------------------------\nStarting Worker Server\nWorker Server = RUNNING\n\n\nStarting Compliance Server\nCompliance Server = RUNNING\n\nStarting GUI Server\nGUI Server = NOT RUNNING <- GUI is not starting\n\n**************************************************************** \n\n\n\nCAUSE\nThe customer did not have \"housekeeping\" configured and running. This resulted in a lot of 'events' in the EVENTS table of the DB. When the server attempted to startup, it was trying to process all of these 'events', but would timeout before completing. Thus, it would not start up successfully.\n\nDIAGNOSING THE PROBLEM\nThe customer may see the following error in the systemout log file:\n\n[5/11/15 6:16:00:262 GMT+00:00] 00000023 ThreadMonitor W WSVR0605W: Thread \"server.startup : 1\" (0000001d) has been active for 779275 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.\nat com.ibm.tivoli.ncm.events.DatabasePoller.addConsumer(DatabasePoller.java:69)\nat com.ibm.tivoli.nsm.work.NSMEventConsumer.register(NSMEventConsumer.java:33)\nat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\n\n\n\nRESOLVING THE PROBLEM\nThe customer will need to manually clear out the 'events' in the EVENTS table using the following SQL command:\n\n\nDELETE FROM EVENTS WHERE UNIQUEKEY NOT IN (SELECT DISTINCT(LASTEVENTKEY) FROM EVENTPOLLERINSTANCES);\n\n\nDepending on the volume of EVENTS records, this may take a long time to execute. If the customer wishes, they can break it down into chunks of deletions using the SQL below:\n\nDELETE FROM EVENTS WHERE CREATEDTIME&lt;? AND ROWNUM&lt;=10000\nAND UNIQUEKEY NOT IN (SELECT DISTINCT(LASTEVENTKEY) FROM EVENTPOLLERINSTANCES);\n\n\nNote: It is important that the customer delete using this method rather than just emptying the table, as there are some events that ITNCM requires. \n\n\n\nTo prevent this from happening in the future, the customer should configure and enable internal housekeeping on their server. In case of a mutil server-deployment, internal housekeeping should only be enabled on one of the servers. To enable and configure Internal Housekeeping, follow the directions found on the following links:\n\nhttp://www-01.ibm.com/support/knowledgecenter/SS7UH9_6.4.1/ncm/wip/confg/task/ncm_config_internalhousekeeping.dita?lang=en [http://www-01.ibm.com/support/knowledgecenter/SS7UH9_6.4.1/ncm/wip/confg/task/ncm_config_internalhousekeeping.dita?lang=en]\n\n\nhttp://www-01.ibm.com/support/knowledgecenter/SS7UH9_6.4.1/ncm/wip/adm/concept/ncm_adm_housekeeping.dita?cp=SS7UH9_6.4.1%2F13-5&lang=en [http://www-01.ibm.com/support/knowledgecenter/SS7UH9_6.4.1/ncm/wip/adm/concept/ncm_adm_housekeeping.dita?cp=SS7UH9_6.4.1%2F13-5&lang=en]", " FIXES ARE AVAILABLE\n8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24037574]\n8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24038133]\n8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24038539]\n8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24039242]\n8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24039425]\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 * Hung thread, CPU issue:\n \n ThreadMonitor W WSVR0605W: Thread \"WebContainer : 0\" (0000005b)\n has been active for 694749 milliseconds and may be hung. There\n is/are 1 thread(s) in total in the server that may be hung.\n \n atcom.ibm.xml.xci.dp.cache.dom.CacheNodeSequence.appendSequence\n (CacheNodeSequence.java:678)\n \n atcom.ibm.xml.xci.dp.cache.dom.CacheNodeSequence.sequenceConcat\n (CacheNodeSequence.java:403)\n \n atcom.ibm.xltxe.rnm1.xtq.xslt.runtime.v2.BasisLibrary2.\n xpathStep(BasisLibrary2.java:4907)\n \n \n \n \n \n\nLOCAL FIX\n * n/a\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 *\n ****************************************************************\n * PROBLEM DESCRIPTION: Hung thread in CacheNodeSequence due to *\n * frequent array expansion *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n The algorithm to expand the array in\n com.ibm.xml.xci.dp.cache.dom.CacheNodeSequence consumes a lot of\n resources when iterating over an extremely large Cursor set that\n contains thousands of nodes. The following hung thread message\n could be seen :\n Thread \"WebContainer : 5\" (00000dab) has been active for 669268\n milliseconds and may be hung. There is/are 1 thread(s) in total\n in the server that may be hung.\n at\n com.ibm.xml.xci.dp.cache.dom.CacheNodeSequence.appendSequence(Ca\n cheNodeSequence.java:678)\n at\n com.ibm.xml.xci.dp.cache.dom.CacheNodeSequence.sequenceConcat(Ca\n cheNodeSequence.java:403)\n at\n com.ibm.xltxe.rnm1.xtq.xslt.runtime.v2.BasisLibrary2.xpathStep(B\n asisLibrary2.java:4907)\n .....\n .....\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The new algorithm expands the array more efficiently and does\n not exhaust the system which prevents the thread from being\n hung.\n \n The fix for this APAR is currently targeted for inclusion in\n fix packs 8.0.0.9 and 8.5.5.3. 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 PI15317\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 700\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-04-04\n \n \n * CLOSED DATE\n 2014-05-02\n \n \n * LAST MODIFIED DATE\n 2014-05-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 PI15529 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI15529]\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" ]

[ [ "1a", " FIXES ARE AVAILABLE" ], [ "1b", "6.1.0.5 Download: WebSphere Portal and WCM V6.1.0 fix pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24027475]" ], [ "1c", "6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24030970] SUBSCRIBE" ], [ "1d", "You can track all active APARs for this component. APAR STATUS" ], [ "1e", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "1f", " * Under some rare conditions a hang can be seen when Portlet" ], [ "1g", " actions are executed." ], [ "1h", "These conditions are that the same action" ], [ "1i", " ID is submitted more than one time by a Portlet and garbage" ], [ "1j", " collection occours between the 2 actions." ], [ "1k", " In the logs a NullPointerException can be seen:" ], [ "1l", " [6/9/10 9:13:07:007 CDT] 0000006a Servlet E" ], [ "1m", " com.ibm.wps.engine.Servlet handleException EJPEJ0070E: An" ], [ "1n", " exception occurred while processing the request." ], [ "1o", " java.lang.NullPointerException" ], [ "1p", " at com.ibm.wps.engine.phases.WPActionPhase$LockManager$Data" ], [ "1q", " .access$200(WPActionPhase.java:3462)" ], [ "1r", " at com.ibm.wps.engine.phases.WPActionPhase$LockManager" ], [ "1s", " .lockReleased(WPActionPhase.java:3453)" ], [ "1t", " at com.ibm.wps.engine.phases.WPActionPhase" ], [ "1u", " .processPortlets(WPActionPhase.java:2762)" ], [ "1v", " at com.ibm.wps.engine.phases.WPActionPhase" ], [ "1w", " .execute(WPActionPhase.java:668)" ], [ "1x", " at com.ibm.wps.state.phases.AbstractActionPhase" ], [ "1y", " .next(AbstractActionPhase.java:130)" ], [ "1z", " at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)" ], [ "1aa", " at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)" ], [ "1ab", " at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888)" ], [ "1ac", " ..." ], [ "1ad", " Some minutes later the Application Server will report hang" ], [ "1ae", " threads:" ], [ "1af", " [6/9/10 9:22:41:135 CDT] 00000025 ThreadMonitor W WSVR0605W:" ], [ "1ag", " Thread \"WebContainer : 31\" (00000088) has been active for" ], [ "1ah", " 602945" ], [ "1ai", " milliseconds and may be hung." ], [ "1aj", "There is/are 1 thread(s) in" ], [ "1ak", " total" ], [ "1al", " in the server that may be hung." ], [ "1am", " at sun.misc.Unsafe.park(Native Method)" ], [ "1an", " at java.util.concurrent.locks.LockSupport.park(LockSupport" ], [ "1ao", " .java:158)" ], [ "1ap", " at java.util.concurrent.locks.AbstractQueuedSynchronizer" ], [ "1aq", " .parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:747)" ], [ "1ar", " at java.util.concurrent.locks.AbstractQueuedSynchronizer" ], [ "1as", " .acquireQueued(AbstractQueuedSynchronizer.java:778)" ], [ "1at", " at java.util.concurrent.locks.AbstractQueuedSynchronizer" ], [ "1au", " .acquire(AbstractQueuedSynchronizer.java:1114)" ], [ "1av", " at java.util.concurrent.locks.ReentrantLock$FairSync" ], [ "1aw", " .lock(ReentrantLock.java:201)" ], [ "1ax", " at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock" ], [ "1ay", " .java:262)" ], [ "1az", " at com.ibm.wps.engine.phases.WPActionPhase" ], [ "1ba", " .processPortlets(WPActionPhase.java:2463)" ], [ "1bb", " at com.ibm.wps.engine.phases.WPActionPhase" ], [ "1bc", " .execute(WPActionPhase.java:668)" ], [ "1bd", " at com.ibm.wps.state.phases.AbstractActionPhase" ], [ "1be", " .next(AbstractActionPhase.java:130)" ], [ "1bf", " at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)" ], [ "1bg", " at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)" ], [ "1bh", " at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888)" ], [ "1bi", " ... LOCAL FIX PROBLEM SUMMARY" ], [ "1bj", " * Under some rare conditions a hang can be seen when Portlet" ], [ "1bk", " actions are executed." ], [ "1bl", "These conditions are that the same action" ], [ "1bm", " ID is submitted more than one time by a Portlet and garbage" ], [ "1bn", " collection occurs between the 2 actions." ], [ "1bo", "In the logs a" ], [ "1bp", " NullPointerException can be seen:" ], [ "1bq", " [6/9/10 9:13:07:007 CDT] 0000006a Servlet E" ], [ "1br", " com.ibm.wps.engine.Servlet handleException EJPEJ0070E: An" ], [ "1bs", " exception occurred while processing the request." ], [ "1bt", " java.lang.NullPointerException at" ], [ "1bu", " com.ibm.wps.engine.phases.WPActionPhase$LockManager$Data.access$" ], [ "1bv", " 200(WPActionPhase.java:3462)" ], [ "1bw", " at" ], [ "1bx", " com.ibm.wps.engine.phases.WPActionPhase$LockManager.lockReleased" ], [ "1by", " (WPActionPhase.java:3453)" ], [ "1bz", " at" ], [ "1ca", " com.ibm.wps.engine.phases.WPActionPhase.processPortlets(WPAction" ], [ "1cb", " Phase.java:2762)" ], [ "1cc", " at" ], [ "1cd", " com.ibm.wps.engine.phases.WPActionPhase.execute(WPActionPhase.ja" ], [ "1ce", " va:668)" ], [ "1cf", " at" ], [ "1cg", " com.ibm.wps.state.phases.AbstractActionPhase.next(AbstractAction" ], [ "1ch", " Phase.java:130)" ], [ "1ci", " at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)" ], [ "1cj", " at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)" ], [ "1ck", " at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888) ..." ], [ "1cl", " S" ], [ "1cm", " Some minutes later the Application Server will report hang" ], [ "1cn", " threads:" ], [ "1co", " [6/9/10 9:22:41:135 CDT] 00000025 ThreadMonitor W" ], [ "1cp", " WSVR0605W: Thread \"WebContainer : 31\" (00000088) has been active" ], [ "1cq", " for 602945 milliseconds and may be hung." ], [ "1cr", "There is/are 1" ], [ "1cs", " thread(s) in total in the server that may be hung." ], [ "1ct", " at sun.misc.Unsafe.park(Native Method) at" ], [ "1cu", " java.util.concurrent.locks.LockSupport.park(LockSupport.java:158" ], [ "1cv", " )" ], [ "1cw", " at" ], [ "1cx", " java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndChe" ], [ "1cy", " ckInterrupt(AbstractQueuedSynchronizer.java:747)" ], [ "1cz", " at" ], [ "1da", " java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQue" ], [ "1db", " ued(AbstractQueuedSynchronizer.java:778)" ], [ "1dc", " at" ], [ "1dd", " java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(Ab" ], [ "1de", " stractQueuedSynchronizer.java:1114)" ], [ "1df", " at" ], [ "1dg", " java.util.concurrent.locks.ReentrantLock$FairSync.lock(Reentrant" ], [ "1dh", " Lock.java:201)" ], [ "1di", " at" ], [ "1dj", " java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java" ], [ "1dk", " :262)" ], [ "1dl", " at" ], [ "1dm", " com.ibm.wps.engine.phases.WPActionPhase.processPortlets(WPAction" ], [ "1dn", " Phase.java:2463)" ], [ "1do", " at" ], [ "1dp", " com.ibm.wps.engine.phases.WPActionPhase.execute(WPActionPhase.ja" ], [ "1dq", " va:668)" ], [ "1dr", " at" ], [ "1ds", " com.ibm.wps.state.phases.AbstractActionPhase.next(AbstractAction" ], [ "1dt", " Phase.java:130)" ], [ "1du", " at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)" ], [ "1dv", " at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)" ], [ "1dw", " at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888) ... PROBLEM CONCLUSION" ], [ "1dx", " * Fixed action ID synchronization." ], [ "1dy", " Failing Module(s):" ], [ "1dz", " Engine: State handling" ], [ "1ea", " Affected Users:" ], [ "1eb", " All Users" ], [ "1ec", " Version Information:" ], [ "1ed", " Portal Version(s): 6.1.0.3" ], [ "1ee", " Pre-Requisite(s): ---" ], [ "1ef", " Co-Requisite(s): ---" ], [ "1eg", " Manuel Steps:" ], [ "1eh", " None" ], [ "1ei", " Platform Specific:" ], [ "1ej", " This fix applies to all platforms." ], [ "1ek", " PM16223 is part of Cumulative Fix 06 for Portal 6.1.0.3/6.1.5.0." ], [ "1el", " The fix is available from Fix Central:" ], [ "1em", " http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde" ], [ "1en", " r?apar=PM14900&productid=WebSphere%20Portal&brandid=5 [http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorder?apar=PM14900&productid=WebSphere%20Portal&brandid=5]" ], [ "1eo", " You may need to type or paste the complete address into your Web" ], [ "1ep", " browser. TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "1eq", " * APAR NUMBER" ], [ "1er", " PM16223" ], [ "1es", " * REPORTED COMPONENT NAME" ], [ "1et", " WEBSPHERE PORTA" ], [ "1eu", " * REPORTED COMPONENT ID" ], [ "1ev", " 5724E7600" ], [ "1ew", " * REPORTED RELEASE" ], [ "1ex", " 61C" ], [ "1ey", " * STATUS" ], [ "1ez", " CLOSED PER" ], [ "1fa", " * PE" ], [ "1fb", " NoPE" ], [ "1fc", " * HIPER" ], [ "1fd", " NoHIPER" ], [ "1fe", " * SPECIAL ATTENTION" ], [ "1ff", " NoSpecatt" ], [ "1fg", " * SUBMITTED DATE" ], [ "1fh", " 2010-06-10" ], [ "1fi", " * CLOSED DATE" ], [ "1fj", " 2010-07-20" ], [ "1fk", " * LAST MODIFIED DATE" ], [ "1fl", " 2010-07-20" ], [ "1fm", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "1fn", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "1fo", " * FIXED COMPONENT NAME" ], [ "1fp", " WEBSPHERE PORTA" ], [ "1fq", " * FIXED COMPONENT ID" ], [ "1fr", " 5724E7600" ], [ "1fs", "APPLICABLE COMPONENT LEVELS" ], [ "1ft", " * R61C PSY" ], [ "1fu", " UP" ] ]

[ "0d", "0h", "0t", "0x", "0ai", "1f", "1g", "1dx", "2d", "2q", "2ae", "2bj" ]

[ " A FIX IS AVAILABLE\nFixes integrated in WebSphere Portal 8.0.0.1 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24034497]\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Hung BackgroundCache thread reported by WAS during pre-rendering\n of a large site.\n \n Example messages in the system log:\n ThreadMonitor W ﾠ ﾠ WSVR0605W: Thread\n \"WorkManager.wpsDefaultWorkManager : 2\" (0000006f) has been\n active for 719719 milliseconds and may be hung. ﾠ There is/are 4\n thread(s) in total in the server that may be hung.\n at java.lang.Thread.sleep(Native Method)\n at java.lang.Thread.sleep(Thread.java:896)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:303)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:347)\n at com.aptrix.cacher.Cacher.storePreRenderedContent(Cacher)\n at com.aptrix.cacher.Cacher.cache(Cacher.java:213)\n ...\n \n \n \n \n \n\nLOCAL FIX\n * None available\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Hung BackgroundCache thread reported by WAS during pre-rendering\n of a large site.\n \n Example messages in the system log:\n ThreadMonitor W  WSVR0605W: Thread\n \"WorkManager.wpsDefaultWorkManager : 2\" (0000006f) has been\n active for 719719 milliseconds and may be hung.  There is/are 4\n thread(s) in total in the server that may be hung.\n at java.lang.Thread.sleep(Native Method)\n at java.lang.Thread.sleep(Thread.java:896)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:303)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:347)\n at com.aptrix.cacher.Cacher.storePreRenderedContent(Cacher)\n at com.aptrix.cacher.Cacher.cache(Cacher.java:213)\n ...\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Code was modified to prevent the hung threads from occurring\n during the pre-rendering of large sites.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM95353\n \n \n * REPORTED COMPONENT NAME\n LOTUS WEB CONT\n \n \n * REPORTED COMPONENT ID\n 5724I2900\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 2013-08-19\n \n \n * CLOSED DATE\n 2013-09-08\n \n \n * LAST MODIFIED DATE\n 2013-09-08\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 LOTUS WEB CONT\n \n \n * FIXED COMPONENT ID\n 5724I2900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R800 PSY\n UP", " FIXES ARE AVAILABLE\n6.1.0.5 Download: WebSphere Portal and WCM V6.1.0 fix pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24027475]\n6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24030970]\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 * Under some rare conditions a hang can be seen when Portlet\n actions are executed. These conditions are that the same action\n ID is submitted more than one time by a Portlet and garbage\n collection occours between the 2 actions.\n \n In the logs a NullPointerException can be seen:\n \n [6/9/10 9:13:07:007 CDT] 0000006a Servlet E\n com.ibm.wps.engine.Servlet handleException EJPEJ0070E: An\n exception occurred while processing the request.\n java.lang.NullPointerException\n at com.ibm.wps.engine.phases.WPActionPhase$LockManager$Data\n .access$200(WPActionPhase.java:3462)\n at com.ibm.wps.engine.phases.WPActionPhase$LockManager\n .lockReleased(WPActionPhase.java:3453)\n at com.ibm.wps.engine.phases.WPActionPhase\n .processPortlets(WPActionPhase.java:2762)\n at com.ibm.wps.engine.phases.WPActionPhase\n .execute(WPActionPhase.java:668)\n at com.ibm.wps.state.phases.AbstractActionPhase\n .next(AbstractActionPhase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888)\n ...\n \n Some minutes later the Application Server will report hang\n threads:\n \n [6/9/10 9:22:41:135 CDT] 00000025 ThreadMonitor W WSVR0605W:\n Thread \"WebContainer : 31\" (00000088) has been active for\n 602945\n milliseconds and may be hung. There is/are 1 thread(s) in\n total\n in the server that may be hung.\n at sun.misc.Unsafe.park(Native Method)\n at java.util.concurrent.locks.LockSupport.park(LockSupport\n .java:158)\n at java.util.concurrent.locks.AbstractQueuedSynchronizer\n .parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:747)\n at java.util.concurrent.locks.AbstractQueuedSynchronizer\n .acquireQueued(AbstractQueuedSynchronizer.java:778)\n at java.util.concurrent.locks.AbstractQueuedSynchronizer\n .acquire(AbstractQueuedSynchronizer.java:1114)\n at java.util.concurrent.locks.ReentrantLock$FairSync\n .lock(ReentrantLock.java:201)\n at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock\n .java:262)\n at com.ibm.wps.engine.phases.WPActionPhase\n .processPortlets(WPActionPhase.java:2463)\n at com.ibm.wps.engine.phases.WPActionPhase\n .execute(WPActionPhase.java:668)\n at com.ibm.wps.state.phases.AbstractActionPhase\n .next(AbstractActionPhase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888)\n ...\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * Under some rare conditions a hang can be seen when Portlet\n actions are executed. These conditions are that the same action\n ID is submitted more than one time by a Portlet and garbage\n collection occurs between the 2 actions. In the logs a\n NullPointerException can be seen:\n \n [6/9/10 9:13:07:007 CDT] 0000006a Servlet E\n com.ibm.wps.engine.Servlet handleException EJPEJ0070E: An\n exception occurred while processing the request.\n java.lang.NullPointerException at\n com.ibm.wps.engine.phases.WPActionPhase$LockManager$Data.access$\n 200(WPActionPhase.java:3462)\n at\n com.ibm.wps.engine.phases.WPActionPhase$LockManager.lockReleased\n (WPActionPhase.java:3453)\n at\n com.ibm.wps.engine.phases.WPActionPhase.processPortlets(WPAction\n Phase.java:2762)\n at\n com.ibm.wps.engine.phases.WPActionPhase.execute(WPActionPhase.ja\n va:668)\n at\n com.ibm.wps.state.phases.AbstractActionPhase.next(AbstractAction\n Phase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888) ...\n S\n \n Some minutes later the Application Server will report hang\n threads:\n \n [6/9/10 9:22:41:135 CDT] 00000025 ThreadMonitor W\n WSVR0605W: Thread \"WebContainer : 31\" (00000088) has been active\n for 602945 milliseconds and may be hung. There is/are 1\n thread(s) in total in the server that may be hung.\n at sun.misc.Unsafe.park(Native Method) at\n java.util.concurrent.locks.LockSupport.park(LockSupport.java:158\n )\n at\n java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndChe\n ckInterrupt(AbstractQueuedSynchronizer.java:747)\n at\n java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQue\n ued(AbstractQueuedSynchronizer.java:778)\n at\n java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(Ab\n stractQueuedSynchronizer.java:1114)\n at\n java.util.concurrent.locks.ReentrantLock$FairSync.lock(Reentrant\n Lock.java:201)\n at\n java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java\n :262)\n at\n com.ibm.wps.engine.phases.WPActionPhase.processPortlets(WPAction\n Phase.java:2463)\n at\n com.ibm.wps.engine.phases.WPActionPhase.execute(WPActionPhase.ja\n va:668)\n at\n com.ibm.wps.state.phases.AbstractActionPhase.next(AbstractAction\n Phase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888) ...\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Fixed action ID synchronization.\n \n Failing Module(s):\n Engine: State handling\n \n Affected Users:\n All Users\n \n Version Information:\n Portal Version(s): 6.1.0.3\n Pre-Requisite(s): ---\n Co-Requisite(s): ---\n \n Manuel Steps:\n None\n \n Platform Specific:\n This fix applies to all platforms.\n \n \n PM16223 is part of Cumulative Fix 06 for Portal 6.1.0.3/6.1.5.0.\n \n The fix is available from Fix Central:\n \n http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde\n r?apar=PM14900&productid=WebSphere%20Portal&brandid=5 [http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorder?apar=PM14900&productid=WebSphere%20Portal&brandid=5]\n \n You may need to type or paste the complete address into your Web\n browser.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM16223\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE PORTA\n \n \n * REPORTED COMPONENT ID\n 5724E7600\n \n \n * REPORTED RELEASE\n 61C\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 2010-06-10\n \n \n * CLOSED DATE\n 2010-07-20\n \n \n * LAST MODIFIED DATE\n 2010-07-20\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 * R61C PSY\n UP", " A FIX IS AVAILABLE\nVersion 8.5 Refresh Pack 7 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24041575]\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Hung threads are observed in the SystemOut.log with a stack\n similar to the following:\n \n [2/19/15 11:04:27:790 CST] 00000036 ThreadMonitor W WSVR0605W:\n Thread \"server.startup : 0\" (0000008a) has been active for\n 632013 milliseconds and may be hung. There is/are 8 thread(s)\n in total in the server that may be hung.\n at java.util.zip.ZipFile.open(Native Method)\n at java.util.zip.ZipFile.(ZipFile.java:140)\n at java.util.jar.JarFile.(JarFile.java:140)\n at java.util.jar.JarFile.(JarFile.java:77)\n at sun.net.www.protocol.jar.URLJarFile.(URLJarFile.java:84)\n at\n sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:6\n 0)\n at\n sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:\n 92)\n at\n sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnecti\n on.java:119)\n at\n sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLC\n onnection.java:147)\n at\n com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe\n r$1.run(FileLoaderHelper.java:69)\n at\n com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe\n r$1.run(FileLoaderHelper.java:64)\n at\n java.security.AccessController.doPrivileged(AccessController.jav\n a:327)\n at\n com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe\n r.openJarStream(FileLoaderHelper.java:64)\n at\n com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe\n r.openStream(FileLoaderHelper.java:53)\n at\n com.ibm.ws.sibx.scax.mediation.model.xml.loader.XMLMedflowModelL\n oaderUtil.initialiseMedflowInputStream(XMLMedflowModelLoaderUtil\n .java:431)\n at\n com.ibm.ws.sibx.scax.mediation.model.xml.loader.XMLMedflowModelL\n oaderUtil.isReadableFormat(XMLMedflowModelLoaderUtil.java:230)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n Users of Business Process Manager v8.5 who have human readable\n mediation flows and are making use of the preload WebSphere\n environment variable to load the flows at application startup.\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n During preload a large amount of processing time was spent\n reading the mediation flow file (mfc) to determine if the flow\n was in a human readable format. This increased the time required\n to start the application server.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * A new WebSphere environment variable has been added to bypass\n the code that determines if the flow is in a human readable\n format, this reduces the time taken to start the server.\n \n The variable applies to the whole server and should only be set\n if all of the mediation flows for all applications are in a\n human readable format. This property should not be used if any\n of the mediation flows are in the old EMF (non-human readable)\n format.\n \n The variable is defined using the Integrated Solutions Console,\n located under:\n Environment -> WebSphere Variables.\n \n name: WESB_HUMAN_READABLE_VALUE\n value: true\n \n The variable should be set at the server scope and the server\n must be restarted before it will take affect.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT07543\n \n \n * REPORTED COMPONENT NAME\n WESB IN BPM\n \n \n * REPORTED COMPONENT ID\n AIMCMFC00\n \n \n * REPORTED RELEASE\n 855\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-03-06\n \n \n * CLOSED DATE\n 2015-03-25\n \n \n * LAST MODIFIED DATE\n 2015-03-25\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 WESB IN BPM\n \n \n * FIXED COMPONENT ID\n AIMCMFC00\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R855 PSY\n UP", "ITNCM; Server; startup; start up; events; timeout; Thread \"server.startup : TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Scenario where an existing ITNCM DB was migrated to a new server, and a new presentation/worker server was installed. After all steps completed, the server would not start successfully. \n\nSYMPTOM\nCustomer will see the following when trying to start ITNCM:\n\n\nIBM Tivoli Netcool Configuration Manager\n----------------------------------------\nStarting Worker Server\nWorker Server = RUNNING\n\n\nStarting Compliance Server\nCompliance Server = RUNNING\n\nStarting GUI Server\nGUI Server = NOT RUNNING <- GUI is not starting\n\n**************************************************************** \n\n\n\nCAUSE\nThe customer did not have \"housekeeping\" configured and running. This resulted in a lot of 'events' in the EVENTS table of the DB. When the server attempted to startup, it was trying to process all of these 'events', but would timeout before completing. Thus, it would not start up successfully.\n\nDIAGNOSING THE PROBLEM\nThe customer may see the following error in the systemout log file:\n\n[5/11/15 6:16:00:262 GMT+00:00] 00000023 ThreadMonitor W WSVR0605W: Thread \"server.startup : 1\" (0000001d) has been active for 779275 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.\nat com.ibm.tivoli.ncm.events.DatabasePoller.addConsumer(DatabasePoller.java:69)\nat com.ibm.tivoli.nsm.work.NSMEventConsumer.register(NSMEventConsumer.java:33)\nat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\n\n\n\nRESOLVING THE PROBLEM\nThe customer will need to manually clear out the 'events' in the EVENTS table using the following SQL command:\n\n\nDELETE FROM EVENTS WHERE UNIQUEKEY NOT IN (SELECT DISTINCT(LASTEVENTKEY) FROM EVENTPOLLERINSTANCES);\n\n\nDepending on the volume of EVENTS records, this may take a long time to execute. If the customer wishes, they can break it down into chunks of deletions using the SQL below:\n\nDELETE FROM EVENTS WHERE CREATEDTIME&lt;? AND ROWNUM&lt;=10000\nAND UNIQUEKEY NOT IN (SELECT DISTINCT(LASTEVENTKEY) FROM EVENTPOLLERINSTANCES);\n\n\nNote: It is important that the customer delete using this method rather than just emptying the table, as there are some events that ITNCM requires. \n\n\n\nTo prevent this from happening in the future, the customer should configure and enable internal housekeeping on their server. In case of a mutil server-deployment, internal housekeeping should only be enabled on one of the servers. To enable and configure Internal Housekeeping, follow the directions found on the following links:\n\nhttp://www-01.ibm.com/support/knowledgecenter/SS7UH9_6.4.1/ncm/wip/confg/task/ncm_config_internalhousekeeping.dita?lang=en [http://www-01.ibm.com/support/knowledgecenter/SS7UH9_6.4.1/ncm/wip/confg/task/ncm_config_internalhousekeeping.dita?lang=en]\n\n\nhttp://www-01.ibm.com/support/knowledgecenter/SS7UH9_6.4.1/ncm/wip/adm/concept/ncm_adm_housekeeping.dita?cp=SS7UH9_6.4.1%2F13-5&lang=en [http://www-01.ibm.com/support/knowledgecenter/SS7UH9_6.4.1/ncm/wip/adm/concept/ncm_adm_housekeeping.dita?cp=SS7UH9_6.4.1%2F13-5&lang=en]", " FIXES ARE AVAILABLE\n8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24037574]\n8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24038133]\n8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24038539]\n8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24039242]\n8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24039425]\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 * Hung thread, CPU issue:\n \n ThreadMonitor W WSVR0605W: Thread \"WebContainer : 0\" (0000005b)\n has been active for 694749 milliseconds and may be hung. There\n is/are 1 thread(s) in total in the server that may be hung.\n \n atcom.ibm.xml.xci.dp.cache.dom.CacheNodeSequence.appendSequence\n (CacheNodeSequence.java:678)\n \n atcom.ibm.xml.xci.dp.cache.dom.CacheNodeSequence.sequenceConcat\n (CacheNodeSequence.java:403)\n \n atcom.ibm.xltxe.rnm1.xtq.xslt.runtime.v2.BasisLibrary2.\n xpathStep(BasisLibrary2.java:4907)\n \n \n \n \n \n\nLOCAL FIX\n * n/a\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 *\n ****************************************************************\n * PROBLEM DESCRIPTION: Hung thread in CacheNodeSequence due to *\n * frequent array expansion *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n The algorithm to expand the array in\n com.ibm.xml.xci.dp.cache.dom.CacheNodeSequence consumes a lot of\n resources when iterating over an extremely large Cursor set that\n contains thousands of nodes. The following hung thread message\n could be seen :\n Thread \"WebContainer : 5\" (00000dab) has been active for 669268\n milliseconds and may be hung. There is/are 1 thread(s) in total\n in the server that may be hung.\n at\n com.ibm.xml.xci.dp.cache.dom.CacheNodeSequence.appendSequence(Ca\n cheNodeSequence.java:678)\n at\n com.ibm.xml.xci.dp.cache.dom.CacheNodeSequence.sequenceConcat(Ca\n cheNodeSequence.java:403)\n at\n com.ibm.xltxe.rnm1.xtq.xslt.runtime.v2.BasisLibrary2.xpathStep(B\n asisLibrary2.java:4907)\n .....\n .....\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The new algorithm expands the array more efficiently and does\n not exhaust the system which prevents the thread from being\n hung.\n \n The fix for this APAR is currently targeted for inclusion in\n fix packs 8.0.0.9 and 8.5.5.3. 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 PI15317\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 700\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-04-04\n \n \n * CLOSED DATE\n 2014-05-02\n \n \n * LAST MODIFIED DATE\n 2014-05-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 PI15529 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI15529]\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" ]

[ [ "2a", " A FIX IS AVAILABLE" ], [ "2b", "Version 8.5 Refresh Pack 7 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24041575] APAR STATUS" ], [ "2c", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "2d", " * Hung threads are observed in the SystemOut.log with a stack" ], [ "2e", " similar to the following:" ], [ "2f", " [2/19/15 11:04:27:790 CST] 00000036 ThreadMonitor W WSVR0605W:" ], [ "2g", " Thread \"server.startup : 0\" (0000008a) has been active for" ], [ "2h", " 632013 milliseconds and may be hung." ], [ "2i", "There is/are 8 thread(s)" ], [ "2j", " in total in the server that may be hung." ], [ "2k", " at java.util.zip.ZipFile.open(Native Method)" ], [ "2l", " at java.util.zip.ZipFile. (ZipFile.java:140)" ], [ "2m", " at java.util.jar.JarFile. (JarFile.java:140)" ], [ "2n", " at java.util.jar.JarFile. (JarFile.java:77)" ], [ "2o", " at sun.net.www.protocol.jar.URLJarFile. (URLJarFile.java:84)" ], [ "2p", " at" ], [ "2q", " sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:6" ], [ "2r", " 0)" ], [ "2s", " at" ], [ "2t", " sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:" ], [ "2u", " 92)" ], [ "2v", " at" ], [ "2w", " sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnecti" ], [ "2x", " on.java:119)" ], [ "2y", " at" ], [ "2z", " sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLC" ], [ "2aa", " onnection.java:147)" ], [ "2ab", " at" ], [ "2ac", " com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe" ], [ "2ad", " r$1.run(FileLoaderHelper.java:69)" ], [ "2ae", " at" ], [ "2af", " com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe" ], [ "2ag", " r$1.run(FileLoaderHelper.java:64)" ], [ "2ah", " at" ], [ "2ai", " java.security.AccessController.doPrivileged(AccessController.jav" ], [ "2aj", " a:327)" ], [ "2ak", " at" ], [ "2al", " com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe" ], [ "2am", " r.openJarStream(FileLoaderHelper.java:64)" ], [ "2an", " at" ], [ "2ao", " com.ibm.ws.sibx.scax.mediation.model.readablexml.FileLoaderHelpe" ], [ "2ap", " r.openStream(FileLoaderHelper.java:53)" ], [ "2aq", " at" ], [ "2ar", " com.ibm.ws.sibx.scax.mediation.model.xml.loader.XMLMedflowModelL" ], [ "2as", " oaderUtil.initialiseMedflowInputStream(XMLMedflowModelLoaderUtil" ], [ "2at", " .java:431)" ], [ "2au", " at" ], [ "2av", " com.ibm.ws.sibx.scax.mediation.model.xml.loader.XMLMedflowModelL" ], [ "2aw", " oaderUtil.isReadableFormat(XMLMedflowModelLoaderUtil.java:230) LOCAL FIX PROBLEM SUMMARY" ], [ "2ax", " * ****************************************************************" ], [ "2ay", " USERS AFFECTED:" ], [ "2az", " Users of Business Process Manager v8.5 who have human readable" ], [ "2ba", " mediation flows and are making use of the preload WebSphere" ], [ "2bb", " environment variable to load the flows at application startup." ], [ "2bc", " ****************************************************************" ], [ "2bd", " PROBLEM DESCRIPTION:" ], [ "2be", " During preload a large amount of processing time was spent" ], [ "2bf", " reading the mediation flow file (mfc) to determine if the flow" ], [ "2bg", " was in a human readable format." ], [ "2bh", "This increased the time required" ], [ "2bi", " to start the application server. PROBLEM CONCLUSION" ], [ "2bj", " * A new WebSphere environment variable has been added to bypass" ], [ "2bk", " the code that determines if the flow is in a human readable" ], [ "2bl", " format, this reduces the time taken to start the server." ], [ "2bm", " The variable applies to the whole server and should only be set" ], [ "2bn", " if all of the mediation flows for all applications are in a" ], [ "2bo", " human readable format." ], [ "2bp", "This property should not be used if any" ], [ "2bq", " of the mediation flows are in the old EMF (non-human readable)" ], [ "2br", " format." ], [ "2bs", " The variable is defined using the Integrated Solutions Console," ], [ "2bt", " located under:" ], [ "2bu", " Environment -> WebSphere Variables." ], [ "2bv", " name: WESB_HUMAN_READABLE_VALUE" ], [ "2bw", " value: true" ], [ "2bx", " The variable should be set at the server scope and the server" ], [ "2by", " must be restarted before it will take affect. TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "2bz", " * APAR NUMBER" ], [ "2ca", " IT07543" ], [ "2cb", " * REPORTED COMPONENT NAME" ], [ "2cc", " WESB IN BPM" ], [ "2cd", " * REPORTED COMPONENT ID" ], [ "2ce", " AIMCMFC00" ], [ "2cf", " * REPORTED RELEASE" ], [ "2cg", " 855" ], [ "2ch", " * STATUS" ], [ "2ci", " CLOSED PER" ], [ "2cj", " * PE" ], [ "2ck", " NoPE" ], [ "2cl", " * HIPER" ], [ "2cm", " NoHIPER" ], [ "2cn", " * SPECIAL ATTENTION" ], [ "2co", " NoSpecatt" ], [ "2cp", " * SUBMITTED DATE" ], [ "2cq", " 2015-03-06" ], [ "2cr", " * CLOSED DATE" ], [ "2cs", " 2015-03-25" ], [ "2ct", " * LAST MODIFIED DATE" ], [ "2cu", " 2015-03-25" ], [ "2cv", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "2cw", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "2cx", " * FIXED COMPONENT NAME" ], [ "2cy", " WESB IN BPM" ], [ "2cz", " * FIXED COMPONENT ID" ], [ "2da", " AIMCMFC00" ], [ "2db", "APPLICABLE COMPONENT LEVELS" ], [ "2dc", " * R855 PSY" ], [ "2dd", " UP" ] ]

[ "0d", "0h", "0t", "0x", "0ai", "1f", "1g", "1dx", "2d", "2q", "2ae", "2bj" ]

[ " SUBSCRIBE\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 * See Problem Summary\n \n \n \n \n \n\nLOCAL FIX\n * na\n \n \n \n \n \n\nPROBLEM SUMMARY\n * APAR NUMBER: PJ42140\n PRODUCT: z/TPF\n FUNCTIONAL AREA: Cryptography\n SHIPPED IN PUT: 11\n \n ABSTRACT:\n With PJ31336 [http://www-01.ibm.com/support/docview.wss?uid=swg1PJ31336] or PJ31807 [http://www-01.ibm.com/support/docview.wss?uid=swg1PJ31807] applied, the Secure Hash Algorithm\n (SHA) user APIs yield incorrect results that cause\n inter-operability problems with other platforms.\n \n PACKAGE CONTENTS:\n Source Segments:\n (C) base/exp/CTAL.exp\n (C) base/include/tpf/tpfapi.h\n (C) base/openssl/tpfssl/cryu.c\n (C) base/rt/crypt.c\n \n Object Only Binaries:\n None.\n \n Configuration Independent Binaries:\n (C) base/openssl/lib/libCRYU.so\n (C) base/openssl/load/CRYU.so\n (C) base/openssl/obj/cryu.o\n \n Support Files:\n base/openssl/lst/CRYU.map\n base/openssl/lst/cryu.lst\n \n OTHER BINARIES TO BUILD: YES\n (C) <sys>/obj/crypt.o\n (C) <sys>/stdlib/libCTAL.so\n (C) <sys>/stdload/CTAL.so\n COMMENTS:\n Creating hash values on z/TPF using the tpf_SHA1_Digest,\n tpf_SHA1_Init, tpf_SHA1_Update, tpf_SHA1_Final,\n tpf_SHA256_Digest, tpf_SHA256_Init, tpf_SHA256_Update or\n tpf_SHA256_Final APIs will result in an incorrect hash being\n returned because the parameters passed to CRYK from CRYU to\n perform the operation within the CPACF hardware are not set up\n correctly. This causes problems if z/TPF creates a SHA hash and\n sends that hash to another platform that then attempts to\n verify the hash value, or if another platform creates a SHA\n hash and sends that hash to z/TPF that then attempts to verify\n the hash value. The incorrect hash problem exists only when the\n z/TPF SHA APIs are used - other code in z/TPF such as SSL that\n creates/verifies SHA hash values does so correctly.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * SOLUTION:\n Some z/TPF customers are using the existing set of SHA APIs and\n persist those hash values along with data, then verify the hash\n values whenever the persisted data is read back into memory.\n For this reason, the behavior of the existing set of SHA1 and\n SHA256 APIs cannot be changed. This APAR introduces a new set\n of SHA APIs (tpf_SHA1_Digest_new, tpf_SHA1_Init_new,\n tpf_SHA1_Update_new, tpf_SHA1_Final_new, tpf_SHA256_Digest_new,\n tpf_SHA256_Init_new, tpf_SHA256_Update_new, and\n tpf_SHA256_Final_new) that has the same user interface as the\n existing set of APIs, but returns the correct hash value.\n If you have user code in z/TPF that created and saved SHA hash\n values using the existing SHA APIs, then that code should\n continue to use the existing SHA APIs to verify those saved\n hash values. However, if you are creating a SHA hash of new\n data or verifying SHA hashes created by other platforms, you\n should use the new set of SHA APIs.\n \n COREQS: NO\n None.\n \n MIGRATION CONSIDERATIONS: YES\n Application programming interface (API) changes:\n tpf_SHA1_Init_new()\n tpf_SHA1_Update_new()\n tpf_SHA1_Final_new()\n tpf_SHA1_Digest_new()\n tpf_SHA256_Init_new()\n tpf_SHA256_Update_new()\n tpf_SHA256_Final_new()\n tpf_SHA256_Digest_new()\n \n BUILD COMMANDS AND INSTRUCTIONS: YES\n #maketpf commands for linux\n maketpf -f CTAL crypt.o\n maketpf -f CRYU cryu.o\n maketpf CTAL link TPF_VERIFY_LINK_REFS=NO\n maketpf CRYU link\n maketpf CTAL link\n \n UPDATED INFORMATION UNITS: YES\n z/TPF C/C++ Language Support User's Guide\n \n See your IBM representative if you need additional information.\n \n DOWNLOAD INSTRUCTIONS:\n http://www.ibm.com/software/htp/tpf/maint/maintztpf.html [http://www.ibm.com/software/htp/tpf/maint/maintztpf.html]\n \n APAR URL:\n http://www.ibm.com/software/htp/tpf/ztpfmaint/put11/PJ42140.htm [http://www.ibm.com/software/htp/tpf/ztpfmaint/put11/PJ42140.htm]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PJ42140\n \n \n * REPORTED COMPONENT NAME\n Z/TPF\n \n \n * REPORTED COMPONENT ID\n 5748T1501\n \n \n * REPORTED RELEASE\n 110\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 2014-03-20\n \n \n * CLOSED DATE\n 2014-05-30\n \n \n * LAST MODIFIED DATE\n 2014-05-30\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\nPublications Referenced SK2T8062 FIX INFORMATION\n * FIXED COMPONENT NAME\n Z/TPF\n \n \n * FIXED COMPONENT ID\n 5748T1501\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R110 PSY\n UP", "COGIPF_SESSIONID; SESSION_ID; Session ID; COGIPF_USERLOGON; COGIPF_RUNREPORT; digest algorithm; SHA-256; SHA-1 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n SESSION_ID column values in the COGIPF_USERLOGON and COGIPF_RUNREPORT do not match in a multi-tier environment. In prior releases, the sample Audit package would correctly show Report Usage, however, after upgrading, no data is returned. \n\nSYMPTOM\nWhen reports are executed against the dispatcher which is installed with the Content Manager, the Session IDs match; however, for reports executed against other two other dispatchers, the Session IDs generated in the COGIPF_RUNREPORT do not have corresponding entries in the COGIPF_USERLOGON table. This prevents the join between COGIPF_RUNREPORT and COGIPF_USERLOGON from returning results\n\n\nCAUSE\nOne of the Dispatchers is using a SHA-256 digest Algorithm, whereas the other Dispatcher is using a SHA-1. \n\nIn releases previous to IBM Cognos 10.2.1, the default was SHA-1. In 10.2.1, the default is SHA-256. If a configuration was upgraded from prior release, it would keep the value SHA-1, whereas new configuration (or configuration from scratch) will default to SHA-256\n\n\nDIAGNOSING THE PROBLEM\nIn a session/time frame, select data from the COGIPF_USERLOGON and COGIPF_RUNREPORT tables and determine if all Session IDs in COGIPF_RUNREPORT have corresponding values in COGIPF_USERLOGON table. Alternatively, with no load on the system, review the cogserver.log and find a UserLogon then run a report and see if the Session ID is different string length. \n\nSHA-1 will produce a 40 byte string, whereas SHA-256 will produce a 64 byte string. \n\n\nRESOLVING THE PROBLEM\nSet all digest algorithm values to the same value. This can be done in IBM Cognos Configuration--> Security---> Cryptography---> Digest Algorithm: Set value to SHA-256 in all dispatchers or SHA-1, or another value as long as they are consistent across each dispatcher within the environment", " SUBSCRIBE\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 * Attempts to run an application or component process that\n contains \"Download Artifacts\" step using uDeploy version 4.8.5\n result in \"Blob not found for hash SHA-xxxxxxxxxxxxx\"\n Downloading file '<file_location>'\n Error Trying to download files : Blob not found for hash SHA-256\n {xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\n x}\n Caught: java.io.IOException: Blob not found for hash SHA-256\n {xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\n x}\n java.io.IOException: Blob not found for hash SHA-256\n {xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\n x}\n at\n com.urbancode.vfs.client.Client.copyFileFromDownload(Client.java\n : 1282)\n at com.urbancode.vfs.client.Client.access$200(Client.java:61)\n at\n com.urbancode.vfs.client.Client$DirectDownloadHandler.download\n (Client.java:1259)\n at\n com.urbancode.vfs.client.Client.downloadFiles(Client.java:1185)\n at\n com.urbancode.vfs.client.Client.transferFiles(Client.java:1091)\n at\n com.urbancode.vfs.client.Client.downloadFilesInternalRemovingPat\n hPrefix(Client.java:1017)\n at\n com.urbancode.vfs.client.Client.downloadChangeSetDeltaRemovingPa\n thPrefix(Client.java:973)\n at\n com.urbancode.vfs.client.Client$downloadChangeSetDeltaRemovingPa\n thPrefix.call(Unknown Source)\n at downloadByLabel.run(downloadByLabel.groovy:501)\n \n We think this is related to version cleanup, when hash files are\n deleted but the server still believes the version still exists.\n This may happen when using uDeploy V4.8.4 or onwards, and think\n this is a different issue from a known version cleanup issue\n identified by APAR PI05165 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI05165].\n \n \n \n \n \n\nLOCAL FIX\n * Import the missing files again as new component versions and use\n that for deployments.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n * Any users with version cleanup enabled *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * Attempts to run an application or component process that *\n * contains \"Download Artifacts\" step using uDeploy version *\n * 4.8.5 *\n * result in \"Blob not found for hash SHA-xxxxxxxxxxxxx\" *\n * Downloading file '<file_location>' *\n * Error Trying to download files : Blob not found for hash *\n * SHA-256 *\n * {xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx *\n * xxxx *\n * x} *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Fixed in IBM UrbanCode Deploy 6.0.1.4\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI09616\n \n \n * REPORTED COMPONENT NAME\n UDEPLOY\n \n \n * REPORTED COMPONENT ID\n 5725M7700\n \n \n * REPORTED RELEASE\n 500\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-01-15\n \n \n * CLOSED DATE\n 2014-03-24\n \n \n * LAST MODIFIED DATE\n 2014-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 UDEPLOY\n \n \n * FIXED COMPONENT ID\n 5725M7700\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R500 PSN\n UP\n \n \n * R500 PSY\n UP", "sha1; secure; hash; algorithm; deduplication TECHNOTE (FAQ)\n\nQUESTION\n According to media reports, an engineered collision was demonstrated for the Secure Hash Algorithm 1 (SHA-1). A collision occurs when two distinct pieces of data hash to the same digest. Does this collision affect data that is deduplicated by using IBM Spectrum Protect? \n\nANSWER\nIBM Spectrum Protect uses SHA-1 for data deduplication. \n\nSHA-1 is a cryptographic hash algorithm that produces a message digest of 160 bits or 20 bytes. IBM Spectrum Protect uses SHA-1 message digests for data deduplication, a function that can be performed on the client side or server side. (For details about SHA-1, see the many sources of information on the internet and elsewhere. Those sources also provide details about message digests, cryptography, and related topics.) \n\nWithin IBM Spectrum Protect, SHA-1 is suitable for producing a message digest that describes data in a data deduplication system. IBM Spectrum Protect does not use SHA-1 for security purposes, such as for authentication to the product. IBM Spectrum Protect uses several data attributes to determine the uniqueness of a data extent (sometimes referred to as a chunk) when data is deduplicated. \n\nExample \n\nConsider a file that is named mydata.abc. Assume that the file is 760,000 bytes in size. When IBM Spectrum Protect deduplicates the file, the file is initially analyzed and extents are determined. An extent is determined by using a fingerprint algorithm that analyzes patterns in the data to determine where one extent ends and the next one begins. The fingerprint algorithm that IBM Spectrum Protect uses is variable block, meaning that extents are not fixed and uniform in size. One extent might be determined to be 56,000 bytes, while another extent from an analyzed file might be 120,000 bytes. After the extent is identified by the fingerprint algorithm, an SHA-1 message digest is generated to uniquely identify the extent. Finally, IBM Spectrum Protect generates an end-to-end MD5 message digest for the entire file. The digest is stored and used during file retrieval to ensure that the reassembly is correct. \n\nFor purposes of this example, assume that the sample file mydata.abc results in the following extents: \n\nExtent Start position of extent in file (offset from beginning of file) Length of extent SHA-1 message digest for extent (displayed as a hex value) 1 0 100,000 x'0D6DC1019BF40D8BF3B2408C4C7BD6C104230B77' 2 100,000 73,000 x'19B222AF5EB625E945ED138AC71F268BCE59129F' 3 173,000 119,000 x'8314A1F73053A2B87FA98612C4985EB0A6D036EB' 4 292,000 88,000 x'D5B5012C9777BC4CF8E838953164431320D1BD46' 5 380,000 150,000 x'E7FE4356FBCE1634D4D9B36A64134695D618E0E4' 6 530,000 109,000 x'6082B153F4FAFBF1FF0A7DFA228ED2CFAB51C3B6' 7 639,000 121,000 x'39ECACBE658DE2B1A1F6B7C5CC5400C2F131CCA0' \nA key consideration for the IBM Spectrum Protect data deduplication system is that a given data extent is identified by more than the SHA-1 message digest that is generated for a given extent. In the example, each data extent is addressed or referenced by both the SHA-1 message digest along with the length of the extent. In the table, extent 3 would be uniquely identified by the SHA-1 message digest that was calculated for it along with the length of the extent: x'8314A1F73053A2B87FA98612C4985EB0A6D036EB'\nand\n119,000 \n\nThe normal behavior for IBM Spectrum Protect is to use the SHA-1 message digest along with the extent length to determine duplication of data and subsequently to process deduplication and reference handling. Also note that the deduplication analysis of this file created seven extents with the extents varying in size based on the fingerprint algorithm.\n\nIBM Spectrum Protect also has the ability to detect if the deduplication system incorrectly \"links\" an extent from one file to another where the attributes (extent length and SHA-1 message digest) match but in fact the data is different. To detect this, IBM Spectrum Protect generates an end-to-end MD5 message digest for the entire file when the file is ingested and the deduplication is performed. Upon reassembly of the data, such as when it is read back by a client, the original MD5 digest is compared to a newly generated one for the data read. If the MD5 digests do not match, there was an issue with one or more of the data extents used to assemble that file. Today, a failure of the MD5 digest reported by IBM Spectrum Protect is typically indicative of a storage failure such as an unrecoverable disk failure. With regards to the SHA-1 collision discussed here, the MD5 end-to-end digest would detect this as well. When data is read by a client (restore, retrieve, or recall), IBM Spectrum Protect generates an end-to-end MD5 digest across the deduplicated extents that are being read from storage and sent to the client. This calculated MD5 digest is compared to the one that was generated and stored at the time that the file was originally stored to the server. If the MD5 digest that is calculated at the time of read does not match the one that is created when the data was stored, the issue will be surfaced as an error message and the IBM Spectrum Protect administrator will have visibility to this issue. In the case of the SHA-1 collision, this would result in the MD5 validation during read to fail. \n\nDoes the SHA-1 collision affect IBM Spectrum Protect data deduplication? \n\nHow does IBM Spectrum Protect use of SHA-1 message digests to support data deduplication relate to the SHA-1 collision as reported in the media? To summarize a few key data points from the announcement of the SHA-1 collision \n(Announcing the first SHA1 collision [https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html]), consider the following: \n\n * The SHA-1 collision was demonstrated for the message digest calculated for an entire file. \n * To generate that collision, researchers expended quintillions of SHA-1 calculations requiring thousands of years of computation time (CPU and follow-on GPU).\n\n\nTo impact the data deduplication that is performed by IBM Spectrum Protect and to create a collision, the steps and actions outlined in the SHA-1 collision mentioned above are required. The SHA-1 collision would require significant additional engineering to result in the following issues: * Cause a collision for a deduplicated extent. IBM Spectrum Protect uses SHA-1 for deduplicated extents. The SHA-1 collision demonstrated is at the level or scope of an entire file. The SHA-1 collision would have to be engineered with knowledge of deduplicated extent boundaries in order to operate at the level of granularity where IBM Spectrum Protect uses the SHA-1 hash. \n * Generate targeted SHA-1 collisions for normally occurring data being stored to IBM Spectrum Protect as deduplicated extents where the colliding data will both generate the same SHA-1 and have the same size. \n\n\nWhile the reported SHA-1 collision is significant, and seems to have moved from being theoretical to actual, the chance of the collision occurring is quite small and requires significant effort. In this case, the effort to create the collision for a file is complex and resource intensive. Additional effort is needed to move beyond the file-level collision to something that achieves collisions for deduplicated extents for a given file while also compromising the end-to-end MD5 digest in addition to the SHA-1 hash.", "Datapower DP valcred SHA2 SHA-2 SHA-256 certificate trust CA TECHNOTE (FAQ)\n\nQUESTION\n When a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), can IBM Websphere DataPower SOA Appliance validate the certificate and trust chain? \n\nANSWER\n Yes, if a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate CA's signature on the certificate while building trust chain from the DataPower ValCred.\n\n\n \n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower SOA Appliances General Firmware 3.8.1, 3.8, 3.7.3, 3.7.2" ]

[ [ "4a", "Datapower DP valcred SHA2 SHA-2 SHA-256 certificate trust CA TECHNOTE (FAQ) QUESTION" ], [ "4b", " When a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), can IBM Websphere DataPower SOA Appliance validate the certificate and trust chain? ANSWER" ], [ "4c", " 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." ], [ "4d", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower SOA Appliances General Firmware 3.8.1, 3.8, 3.7.3, 3.7.2" ] ]

[ "4a", "4b", "4c" ]

[ "datapower; 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", " A FIX IS AVAILABLE\nWebSphere MQ V7.5 Fix Pack 7.5.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24038252]\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 dmpmqcfg utility program is being used to dump definitions\n on a remote queue manager.\n \n The user supplies the -c parameter to pass the client channel\n and connection information to connect to the remote queue\n manager.\n \n The program connects successfully with non-SSL channels but\n fails using SSL channels with \"AMQ9518: File\n '/var/mqm/AMQCLCHL.TAB' not found.\"\n \n The AMQCLCHL.TAB file should not be required since the user\n did not want any Certificate Revocation checking to be\n performed, and the client channel information was supplied\n with the \"mqsc -c\" parameter.\n \n \n \n \n \n\nLOCAL FIX\n * If the user wants no certificate revocation checks, copy a blank\n CCDT to /var/mqm on the client.\n \n If the user wants certificate revocation checks, ensure the CCDT\n is correctly populated with the information needed, and make\n it available in /var/mqm.\n \n Remember that alternative locations for the CCDT can be given\n via MQCHLLIB and MQCHLTAB environment variables.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n Users of dmpmqcfg via an SSL client channel, but who want no\n Certificate Revocation checking to be done, and do not want to\n supply a Client Channel Definition Table to the client to\n configure this.\n \n \n Platforms affected:\n MultiPlatform\n \n ****************************************************************\n PROBLEM SUMMARY:\n The client connection code running in the WebSphere MQ library\n code in the client application was initializing, and as part\n of this it was trying to initialize its certificate revocation\n checking component. Because the CLNTCONN definition supplied\n by the program did not include any certificate revocation\n information, the WebSphere MQ code tried to load the Client\n Channel Definition Table (CCDT) file to check for that\n information. The file did not exist. The initialization\n therefore failed, and the connection attempt to the queue\n manager was abandoned.\n \n However, the user did not want certificate revocation checking\n to be performed for this application. There was no easy way\n for them to assert this to the WebSphere MQ code, though.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * A new parameter has been added to the mqclient.ini file, to\n enable a user to opt out of the certificate revocation\n initialization, if that is what they want to do:\n \n SSL stanza:\n \n ClientRevocationChecks\n \n Description: this setting determines if, and how, the\n WebSphere MQ client attempts to configure certificate revocation\n checking in the event of client connect call which uses an\n SSL/TLS channel:\n Acceptable values:\n - REQUIRED (this is the default): attempt to load certificate\n revocation configuration from the CCDT. The MQCONN fails if\n WebSphere MQ cannot open the CCDT.\n - DISABLED: do not configure certificate revocation checking\n at all\n - OPTIONAL: attempt to load certificate revocation configuration\n from the CCDT, but no error is reported if WebSphere MQ fails to\n open the CCDT - for example, if there is no CCDT file.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v7.5 7.5.0.4\n \n The latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n \n If the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IC98041\n \n \n * REPORTED COMPONENT NAME\n WMQ BASE MULTIP\n \n \n * REPORTED COMPONENT ID\n 5724H7241\n \n \n * REPORTED RELEASE\n 750\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 2013-12-02\n \n \n * CLOSED DATE\n 2014-01-23\n \n \n * LAST MODIFIED DATE\n 2014-01-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 WMQ BASE MULTIP\n \n \n * FIXED COMPONENT ID\n 5724H7241\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R750 PSY\n UP", " SUBSCRIBE\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 * DataPower change to prevent SSL TLS Man-in-the-Middle attack.\n The SSLM MitM attack is also known as CVE-2009-3555.\n This change is to prevent SSL renegotiations from occurring.\n \n \n \n \n \n\nLOCAL FIX\n * Use mutual or client authentication until the new firmware can\n be installed.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * *******************************************************\n * USERS AFFECTED: All IBM WebSphere DataPower SOA Appliance\n * Users.\n ******************************************************\n * PROBLEM DESCRIPTION:\n *****************************************************\n * RECOMMENDATION: Apply fixpacks 3.7.1.12, 3.7.2.8, 3.7.3.7,\n * 3.8.0.1 or superceding fix packs.\n ******************************************************\n A recently discovered vulnerability in the renegotiation feature\n of the SSL and TLS protocols allows an attacker to inject an\n arbitrary string into the SSL session. This vulnerability is\n commonly referred to as the SSL Man-in-the-Middle (MITM) attack\n or CVE-2009-3555.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The DataPower SSL server implementation is not vulnerable to\n either form of attack when using SSL client authentication,\n because the implementation requires immediate client\n authentication in the first SSL handshake (unlike vulnerable SSL\n server implementations that only require client authentication\n in a renegotiation handshake after seeing the request URL).\n \n However, the DataPower SSL server implementation is vulnerable\n to the weaker form of attack when client authentication is not\n used. This weaker form of attack is limited, because it can only\n steal HTTP headers from the initial HTTP request of the attacked\n client. Most HTTP clients do not send authentication credentials\n in the initial HTTP request headers. Most HTTP clients wait\n until seeing certain HTTP status codes from the HTTP server\n before sending authentication credentials, and HTTP clients like\n these would not be vulnerable to this weaker form of attack.\n \n To confirm if your appliance uses SSL client authentication,\n look at the reverse/server Crypto Profile of the SSL Proxy\n Profile in question. If it contain a Validation Credentials,\n client authentication is in use.\n \n See this technote:\n http://www.ibm.com/support/docview.wss?uid=swg21410851 for more\n information.\n \n \n \n \n \n\nTEMPORARY FIX\n * Use mutual or client authentication until new firmware is\n installed.\n \n \n \n \n \n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IC64790\n \n \n * REPORTED COMPONENT NAME\n DATAPOWER\n \n \n * REPORTED COMPONENT ID\n DP1234567\n \n \n * REPORTED RELEASE\n 373\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 2009-11-24\n \n \n * CLOSED DATE\n 2009-12-18\n \n \n * LAST MODIFIED DATE\n 2010-01-11\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 DATAPOWER\n \n \n * FIXED COMPONENT ID\n DP1234567\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R371 PSY\n UP\n \n \n * R372 PSY\n UP\n \n \n * R373 PSY\n UP\n \n \n * R380 PSY\n UP", "communications WAS JMS client WMQ server SSL repertoires secure connection TECHNOTE (FAQ)\n\nQUESTION\n How do I secure communications between a WebSphere Application Server JMS client and a WebSphere MQ server, using SSL repertoires? \n\nCAUSE\nPrior to the release of 6.0.2.15 the only way to enable secure communications between the WebSphere Application Server JMS client and the WebSphere MQ server was to use JVM properties set in the WebSphere Application Server console to specify a keystore and truststore which would be used for every connection. \nSince the release of versions 6.0.2.15 and 6.1.0.2 WebSphere Application Server now has the ability to use a different keystore and truststore - and so different certificates - for every connection that is created between the application server's JMS client and the WebSphere MQ server. This is done by setting a custom property on the connection factory. This article explains how an existing connection can be modified to enable secure communications. \n\nThe custom property which is used to enable SSL communication is valid for use with queue, topic and unified connection factories, however this example shows how to modify a queue connection factory. \n\nA queue connection factory, queue destination and message listener need to be set up and running before proceeding with the setup. Note that the transport type of the connection factory must be CLIENT. \n\n\n\nANSWER\nCreate key databases \n\nKey databases must be created to contain the certificates. For this example, only two are needed: one for the WebSphere MQ server and one for the WebSphere Application Server connection factory. To secure more connection factories, the same key database - and so the same certificates - can be used, or more key databases can be created if a different set of certificates are to be used for the additional connections. \n\nTo create the databases, use iKeyman. This certificate management tool is supplied with WebSphere MQ. To start it, type strmqikm at a command line. \n\nTo create key database for WebSphere MQ: \n\n * Key Database File > New \n * Key database type > CMS \n * File name > key.kdb \n * Location > C:\\Program Files\\IBM\\WebSphere MQ\\qmgrs\\qmgrname\\ssl (where qmgrname is the name of the WebSphere MQ server queue manager) \n * Next step > enter password, ensure 'stash password to a file' is selected \n * To create jks keystore(s) for WebSphere Application Server connection (for this example, only one need be created): \n * Key Database File > New \n * Key database type > JKS \n * Filename > key.jks \n * Location > C:\\WASclient (any location can be specified) \n * Next step > enter password \n\n\nCreate certificates \n\nIn order to utilize server and client authentication a CA signer certificate and a signed personal certificate for each connection you wish to secure must be created, as well as a CA signer certificate and signed personal certificate for the WebSphere MQ server. \n\nEach of the CA signer certs created for the WebSphere Application Server key databases will need to be added to the WebSphere MQ server's key database along with the server's CA signer certificate and its signed personal certificate. \n\nEach WebSphere Application Server connection factory's keystore will need the WebSphere MQ server's CA signer certificate, its own CA signer certificate, and its own signed personal certificate: \n\n\nWMQ WAS1 WAS2\n\nserverCA serverCA serverCA\nWAS_CA1 WAS_CA1\nWAS_CA2 WAS_CA2\nserversigned WASsigned1 WASsigned2 \n\nFor this example two CA signer certificates will need to be created, and each of these will need to be used to sign a personal certificate. \n\n \n\nAdd certificates to key databases \n\nFor this example each key database will need to contain both of the CA signer certificates generated, and its own signed personal certificate. \n\nUse ikeyman to add certs. \n\nThese steps need to be followed for each key database: \n\nTo add CA certs: \n\n * Open the database \n * Signer certs tab > click Add \n * Select location, enter label - the label given to CA certificates is not important \n * Do this for each CA cert. \n * To add signed (personal) certs: \n * Open the database \n * Select personal certificates tab > Import \n * Select key file type PKCS12 \n * Select cert, enter password, alter label (ensure that the WebSphere MQ server's signed cert has label 'ibmwebspheremqqmgrname', for the WebSphere Application Server connection factory's signed cert this label is not important) \n\n\nCreate SSL repertoire(s) \n\nAn SSL repertoire must be created for each key database. This is used to specify the location, password and other details of the key database inside WebSphere Application Server. \n\nTo create the SSL repertoire: \n\n * In the WebSphere admin console go to Security > SSL > New JSSE Repertoire \n * Alias 'JMSClient' (the alias entered here can be anything) \n * Select 'client auth' \n * Security level 'high' \n * Select all cipher suites and click 'add' \n * Enter key and trust store locations and passwords (note: in this example, these are the same file) \n * Save \n\n\nAlter connection factory details \n\nThe next step is to alter the connection factory to add the cipher spec and the custom property 'ssl.repertoire' \n\nIn the WebSphere admin console: \n\n * Go to Resources > JMS Providers > Websphere MQ \n * Then select the connection factory to be secured \n * In 'SSL cipher suite' enter a valid cipher suite (eg SSL_RSA_WITH_3DES_EDE_CBC_SHA) \n * Select 'Custom properties' \n * Select 'New' \n * Enter name 'ssl.repertoire' \n * Enter the Alias - this is the alias which was specified for the repertoire created earlier, prepended by the name of the node in which it was created - for this example: 'nodename/JMSClient' \n * Save all \n\n\nAlter queue manager details \n\nNext, alter the WebSphere MQ channel definition. \n\nOn a command line: \n\n * runmqsc qmgrname \n * alter chl(SYSTEM.DEF.SVRCONN) chltype(svrconn) sslciph(TRIPLE_DES_SHA_US) \n * The cipher spec must match that specified in the connection factory. There is a list of valid cipher spec combinations in the Websphere MQ Using Java manual, Appendix D \n\n\nEnable global security \n\nTo turn on global security: \n\n * On the WebSphere Admin Console: go to Security > Global Security \n * Select a user registry to contain signon information - for this example go to 'local OS'. \n * Enter user name and password here \n * Save \n * Go back to Security > Global Security \n * Select 'enable global security' \n * Ensure that active user registry is 'local OS' \n * Save \n * Restart WebSphere Application Server and WebSphere MQ (ensure WebSphere MQ listener is running after the restart) \n\n\nNote: Once Global Security has been enabled WebSphere Application Server must be stopped using the stopServer script, specify the username and password from the local OS user registry. When WebSphere Application Server is restarted, the message listener using the altered connection factory should be running with its communications secured. \n\n \n\nHISTORICAL NUMBER\n 77482442000 \n\nPRODUCT ALIAS/SYNONYM\n WMQ\nWebSphere MQ\nMQSeries", "ibm http server ihs key sslclientauth key.kdb; mutual authentication TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When setting up 'SSLClientAuth required' directive, it is required that the IHS key.kdb have the signer certificates for the clients personal certificate. \n\nThe list of signer certificates will be passed to the client on the Server Hello.\n\nThis is required for the client to pass it's personal certificate during the SSL handshake. \n\nMost sites do not require client authentication. To require client authentication, use the 'SSLClientAuth required' directive. \n\nSYMPTOM\nMutual SSL hand shake fails with the following:\n\nSSL0271I: SSL Handshake Failed, client closed connection without sending any data\n\n\nCAUSE\nClients signer certificates are not passed on the 'Server Hello'\n\nRESOLVING THE PROBLEM\nPopulate the IHS key.kdb with the signer certificates for the client's personal certificate. This can be accomplished by using the iKeyman utility provided with the IHS installation. See the following reference. \n\nManaging keys with the IKEYMAN graphical interface [http://www-01.ibm.com/support/knowledgecenter/SSEQTJ_8.5.5/com.ibm.websphere.ihs.doc/ihs/welc_ikeymangui.html?lang=en]" ]

[ [ "0a", "datapower; mq; websphere mq; ssl; mutual authentication mode; mq manager; 7993; 7993; 7993; machine type 7993 TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "0b", " The WebSphere DataPower MQ Client can be configured to use SSL in mutual authentication mode with a Remote WebSphere MQ Manager." ], [ "0c", "This step-by-step technote guides DataPower Appliance users on how to configure DataPower MQ Manager Object to use SSL in mutual authentication mode." ], [ "0d", "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." ], [ "0e", "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]" ], [ "0f", "RESOLVING THE PROBLEM" ], [ "0g", "In 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." ], [ "0h", "You should also have an understanding of how to configure DataPower MQ Manager Object that connects to remote WebSphere MQ Queue Manager (qmgr)." ], [ "0i", "This technote focuses on configuring DataPower MQ Client to use SSL in mutual authentication mode with Firmware Releases 3.8.2 and later fixpacks." ], [ "0j", "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." ], [ "0k", "WebSphere MQ configuration prerequisites" ], [ "0l", "The following three steps are necessary to make sure that the SSL configurations for the Remote MQ Server is correctly working." ], [ "0m", "Refer to IBM WebSphere MQ product manuals to configure MQ environment to work in SSL mutual authentication mode. 1." ], [ "0n", "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]. 2." ], [ "0o", "Configure WebSphere MQ Client to use SSL authentication. 3." ], [ "0p", "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." ], [ "0q", "Generate self signed key/certificate 1." ], [ "0r", "Generate the self signed key/certificate pair using the \"crypto tool\" from the DataPower device. 2." ], [ "0s", "Download the two files to your local machine." ], [ "0t", "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. 3." ], [ "0u", "Assuming that openssl tool (www.openssl.org [http://www.openssl.org]) is installed in the local machine." ], [ "0v", "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." ], [ "0w", "This step is necessary as MQ key database will not import key/certificate files created as PEM." ], [ "0x", " openssl pkcs12 -export -out dpmqclient-key.p12-in dpmqclient-sscert.pem-inkey dpmqclient-privkey.pem-name ibmwebspheremqadmin" ], [ "0y", " Note the value associated with \"-name\" parameter." ], [ "0z", "IBM WebSphereMQ client required a friendly label as \"ibmwebspheremq<userid>\" of the MQ client user." ], [ "0aa", "In this example, the user name is being used as \"admin\"." ], [ "0ab", "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." ], [ "0ac", "Please refer to Pages G58-62 in the 3.6.0-WebGui Guide for various fields as described in MQ Queue Manager configuration screen." ], [ "0ad", "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." ], [ "0ae", " * SSL Key Repository: The key database file name" ], [ "0af", " SSL Cipher Specification: TRIPLE_DES_SHA_US" ], [ "0ag", "To import a personal certificate using \"iKeycmd\" GUI, use the following commands in your host machine where the WebSphere MQ Server/Client is running." ], [ "0ah", " * UNIX * *" ], [ "0ai", " * gsk7cmd -cert -import -file filename -pw password -type pkcs12 -target filename -target_pw password -target_type cms * *" ], [ "0aj", " * Windows * *" ], [ "0ak", " * runmqckm -cert -import -file filename -pw password -type pkcs12 -target filename -target_pw password -target_type cms * * * *" ], [ "0al", " * -file" ], [ "0am", " * filenam * *" ], [ "0an", " * -pw" ], [ "0ao", " * password * *" ], [ "0ap", " * -type" ], [ "0aq", " * pkcs12 * *" ], [ "0ar", " * -target" ], [ "0as", " * filename * *" ], [ "0at", " * -target_pw" ], [ "0au", " * password * *" ], [ "0av", " * -target_type" ], [ "0aw", " * cms *" ], [ "0ax", "Generate the new password file" ], [ "0ay", "Follow these steps to generate the new password file. 1." ], [ "0az", "Start the iKeyman GUI using either the gsk7ikm command (on UNIX) or the strmqikm command (on Windows). 2." ], [ "0ba", "From the Key Database File menu, click Open." ], [ "0bb", "The Open window displays. 3." ], [ "0bc", "Click Key database type and select CMS (Certificate Management System). 4." ], [ "0bd", "Click Browse to navigate to the directory that contains the key database files. 5." ], [ "0be", "Select the key database file in which you want to save the certificate, for example key.kdb. 6. Click Open." ], [ "0bf", "The Password Prompt window displays. 7." ], [ "0bg", "Type the password you set when you created the key database and click OK. 8." ], [ "0bh", "The name of your key database file displays in the File Name field." ], [ "0bi", "The Personal Certificates menu will display both \"ibmwebspheremq<qmgr>\" and \"ibmwebspheremq<user>\" labels. 9." ], [ "0bj", "In the WebSphere MQ Certificate key database, there is one certificate assigned to the queue manager or client." ], [ "0bk", "The certificate's Friendly Name attribute contains the string ibmwebspheremq followed in lower case by the queue manager name or the client logon ID." ], [ "0bl", "This Friendly Name value becomes the label of the certificate in the GSKit key database." ], [ "0bm", "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." ], [ "0bn", "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] 10." ], [ "0bo", "From the key database File menu, click Stash Password." ], [ "0bp", "This will create the new password file as \"key.sth\"." ], [ "0bq", "Select OK and close the key database File. 11." ], [ "0br", "Upload the \"key.kdb\" and \"key.sth\" files to \"cert:\" directory of the DataPower box." ], [ "0bs", "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." ], [ "0bt", "The following screen shot shows the \"key.kdb\" and \"key.sth\" files are located in the \"cert:\" directory of the application domain." ], [ "0bu", "[/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\"." ], [ "0bv", "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] 12." ], [ "0bw", "Refresh the SSL security attribute of the MQ Manager to use this key database and password files from the host machine running MQ Server." ], [ "0bx", " Runmqsc <MQ Manager>" ], [ "0by", " Refresh security type(ssl)" ], [ "0bz", " End 13." ], [ "0ca", "Test your application to PUT/GET MQ message(s) using DataPower MQ client with the new configuration." ], [ "0cb", "Note: DataPower 3.8 and later firmware provides a separate method for the mq-qm object to use SSL in mutual authentication mode." ], [ "0cc", "This method uses DataPower SSL Proxy Profile that includes Crypto profile with Identification Credential." ], [ "0cd", "For more details, refer to DataPower InfoCenter on how to create SSL Proxy Profile:" ], [ "0ce", "https://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)" ], [ "0cf", "https://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)" ], [ "0cg", "https://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)" ], [ "0ch", "Note: The generation of key database can be done using IBM Key Management Tool which comes with MQ Product." ], [ "0ci", "Cross 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" ] ]

[ "0b", "0c", "0d", "0e", "0g", "0h", "0i", "0j", "0k", "0l", "0m", "0n", "0o", "0p", "0q", "0r", "0s", "0t", "0v", "0w", "0x", "0y", "0z", "0aa", "0ab", "0ac", "0ad", "0ae", "0af", "0ah", "0ai", "0aj", "0al", "0am", "0an", "0ao", "0ap", "0aq", "0ar", "0as", "0at", "0au", "0av", "0ax", "0ay", "0az", "0ba", "0bb", "0bc", "0bd", "0be", "0bf", "0bg", "0bh", "0bi", "0bj", "0bk", "0bl", "0bm", "0bo", "0bp", "0bq", "0bs", "0bt", "0bu", "0bv", "0bw", "0bx", "0bz", "0ca", "0cb", "0cc", "0cd", "0ce", "0cf", "0cg", "0ch", "0ci" ]

[ "datapower; timeout; session ; logoff; disable; expired; timing; drop; active users; active sessions; session; sessions; 7993; 7993; 7993; machine type 7993 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Your web browser session times out and you are logged off the IBM WebSphere DataPower appliance WebGUI session. \n\nCAUSE\nThe IBM WebSphere DataPower appliance WebGUI default session time-out value is 600 seconds.\n\nRESOLVING THE PROBLEM\nYou may change the default WebGUI session time-out or disable it: \n\n 1. Log-in using a user with administrative or \"privileged\" access. \n 2. Select Network on the Navigation Bar. \n 3. Select Web Management Service \n 4. Scroll down to the \"Idle Timeout\" field. Click in the field and set time in seconds for the desired time-out value. If set to \"0\" it will disable the time-out session value and users will no longer be prompted to log-in after an extended period of inactivity. \n\n\nConsequences of disabling the session time out: \n\nNote: It is not recommended to disable the time-out. \n\nIf the time-out session value is disabled and a WebGUI session is terminated by closing the browser without logging out, the session will be kept active. You will then notice that the list of active users on the device will get longer which may lead to slow responses as the number of active connections increase. \n\nTo prevent this from happening it is recommended that you: 1. Set an appropriate time-out value for your environment to ensure inactive sessions are cleaned up. \n 2. Always close a WebGUI session with a clean exit by clicking on the \"Logout\" button. \n\n\nNote: Rebooting the device will also clean out all of the active connections. \n\nTo check the connections, from the Navigation Bar select Status -> Active Users. \nFrom here, you can see all the active management connections and if desired manually disconnect unused connections.", "session; 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]", "DASH; DASHL2; DASHL2CONF; Session Timeout; Configuration; Controls; User; Group ; level TECHNOTE (FAQ)\n\nQUESTION\n Is it possible to set DASH session timeout parameters on a group and user level? \n\nCAUSE\nFor security reasons, customer wants to set DASH session timeout at the group and user level.\n\nANSWER\nSetting DASH session Time-out controls is not supported at the Group and User level. \n\nFor your convenience, here is a link for additional information on setting DASH session timeouts:\nwww.ibm.com/developerworks/community/blogs/69ec672c-dd6b-443d-add8-bb9a9a490eba/entry/dash_session_timeout_configuration_controls?lang=en [https://www.ibm.com/developerworks/community/blogs/69ec672c-dd6b-443d-add8-bb9a9a490eba/entry/dash_session_timeout_configuration_controls?lang=en]", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This document explains how to print tape/media session statistics. \n\nRESOLVING THE PROBLEM\nTo print tape/media session statistics, you should do the following: \n\n1. Start the System Service Tools by issuing the STRSST command. 2. Sign in to the service tools. 3. Select Option 1 - Start a service tool. 4. Select Option 1 - Product activity log. 5. Select Option 5 - Display or print removable media session statistics. 6. Specify the following on the Select Media Options panel:\n\nRemovable media......2\nVolume ID.......................*ALL\nPrint report......................Y\n\nas indicated in Figure 1 below:\n\nThis is a screen shot of the SELECT MEDIA OPTIONS panel that is display when you select Option 5 on the Product Activity Log menu. [/support/docview.wss?uid=nas8N1011974&aid=1] [/support/docview.wss?uid=nas8N1011974&aid=1]\nNotes:\na. Removable media type 2 is for most of the new LTO type cartridges such as all ULTRIUMn and 3592.\nb. If you know the volume ID of your backup, you can isolate results for that specific backup/cartridge/volume. 7. Specify a time period on the Set Time Period panel (Figure 2) that you would like the report to include (it defaults to the last 24 hours):\n\nThis is a screen shot of the SET TIME PERIOD option panel that is displayed to choose which session statistics to print. [/support/docview.wss?uid=nas8N1011974&aid=2] [/support/docview.wss?uid=nas8N1011974&aid=2] 8. Wait for Printing or spooling operation is complete message to post to the bottom of the screen 9. Press F3=Exit three times, and then press Enter to exit out of the service tools. 10. Issue the WRKSPLF command to locate the spooled report. The report will list as QPCSMPRT in your spooled output.\n\nAn example of the generated report is included below:\n\n[/support/docview.wss?uid=nas8N1011974&aid=4] [/support/docview.wss?uid=nas8N1011974&aid=3] \n\n\nCross reference information Segment Product Component Platform Version Edition Operating System IBM i 7.2 Operating System IBM i 7.1 Operating System IBM i 6.1 Operating System IBM i 7.3 \nHISTORICAL NUMBER\n 574567132", "WebSphere http session management time-out wasrun precedence overwrite TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n It is possible to set the HTTP Session time-out in various places on the IBM® WebSphere® Application Server Administrative Console. It is also possible to set HTTP Session time-out for the application packaging process. \n\nSince Session time-out can be set in multiple places, it is necessary to understand how the ultimate Session time-out for an application is determined. \n\nCAUSE\nApplication needs HTTP session time-out set.\n\nRESOLVING THE PROBLEM\nThe HTTP Session time-out can be set in the following places: \n\n * From the Administrative Console at the server, Enterprise application, and Web application levels \n * At the time when the application is packaged \n * In the application code\n\n\nSetting the HTTP Session time-out from the Administrative Console \n1. To set the HTTP Session time-out at the server level, navigate to Servers > Application Servers > Your Server > Web Container > Session Management. \n\nIn the Session time-out section of this window, you can select No time-out or Set time-out by clicking the appropriate radio button. If you choose to set the time-out, type the desired value in minutes in the box. \n\n\n2. To set the HTTP Session time-out at the Enterprise Application level, navigate to Applications > Enterprise Applications > Your Application > Session Management. \n\nCheck Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the application session to overwrite those values set at the parent, which in this case is the Server level. \n\n\n3. To set the HTTP Session time-out at the Web Application level, navigate to Applications > Enterprise Applications > Your Application > Web Module > Your Web App.war > Session Management. \n\nCheck Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the Application Session to overwrite those values set at the parent levels, which in this case is the Server or Enterprise Application level. \n\nAfter modifying these settings, save the master configuration. \n\nSetting HTTP Session time-out when application is packaged \n\nThe application developer can also select to set the HTTP Session time-out parameter when the application is packaged. This value is stored in the web.xml file for the Web application. \n\nThis setting overrides any session time-outs defined from the Administrative Console. Alter this setting by repackaging the application with a new value, or by modifying the web.xml file. The entry in the web.xml will be as follows: \n          <session-config> \n *          <session-timeout>60</session-timeout>\n * \n *       </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&amp;aid=1] Lowest level 2. Enterprise Application [/support/docview.wss?uid=swg21163875&amp;aid=1] Overrides the Server Level if Override is selected 3. Web Application [/support/docview.wss?uid=swg21163875&amp;aid=1] Overrides the Server and Enterprise Application settings if Override is selected 4. Application Level (web.xml) [/support/docview.wss?uid=swg21163875&amp;aid=1] Overrides Server, Enterprise Application, and Web Application settings 5. Application Code [/support/docview.wss?uid=swg21163875&amp;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" ]

[ [ "2a", "DASH; DASHL2; DASHL2CONF; Session Timeout; Configuration; Controls; User; Group ; level TECHNOTE (FAQ) QUESTION" ], [ "2b", " Is it possible to set DASH session timeout parameters on a group and user level? CAUSE" ], [ "2c", "For security reasons, customer wants to set DASH session timeout at the group and user level. ANSWER" ], [ "2d", "Setting DASH session Time-out controls is not supported at the Group and User level." ], [ "2e", "For your convenience, here is a link for additional information on setting DASH session timeouts: www.ibm.com/developerworks/community/blogs/69ec672c-dd6b-443d-add8-bb9a9a490eba/entry/dash_session_timeout_configuration_controls?lang=en [https://www.ibm.com/developerworks/community/blogs/69ec672c-dd6b-443d-add8-bb9a9a490eba/entry/dash_session_timeout_configuration_controls?lang=en]" ] ]

[ "2b", "2c", "2d" ]

[ " TECHNOTE (FAQ)\n\nQUESTION\n How do documents get in the stuck in processing Queue? \n\nCAUSE\nThere are multiple reasons which could cause documents to become stuck in the processing queue. The most common reasons: \n\n * Data restore was done, or \n * PC was rebooted during a process, or \n * Tried to use a retired communication session.\n\nANSWER\nTo get more detail about the reason for the problem, view the Audit Log for error messages. \n\nClick View > Audit Log\n\nTo resolve the problem: \n\n 1. Try to reset the document and reprocess the data: 1. Click on View > Processing \n 2. Highlight all documents \n 3. Click RESET button \n 4. Try sending data again. \n \n \n 2. Verify that routine cleanup has been done on temp and audit log files, and that the document count maintained in Gentran:Director's browser drawers meets the required system limits. \n\n\nFor more information about maintenance, see the White Paper entitled \"Maintenance Summary\" in Sterling Gentran:Director Documentation [http://www.ibm.com/support/docview.wss?uid=swg27023726#wp] Note: Gentran:Director system limitations: \n\n * No more than 1000 documents per interchange. \n * No more than 7500 InDrawer documents and 7500 OutDrawer documents in the system at any time. \n * No interchange should exceed 10 megabytes in size. \n * No document (EDI or Application Import) should exceed 2 megabytes in size. \n * If too many messages are being scanned, use Commerce Mail and pickup old Network Reports that are waiting.\n\n \n\nHISTORICAL NUMBER\n PRI102\nSCI3744", "EDC5124I; Too many open files; MMAPAREAMAX TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to configure IBM Jazz Reporting Service (JRS) (Report Builder) on z/OS fails with the message \"java.io.IOException: EDC5124I Too many open files\" in the SYSOUT log \n\nSYMPTOM\nThe JRS server fails to install and you find errors similar to the following the SYSOUT and SYSPRT log files.\n\n\nSYSOUT:\nSRVE0068E: An exception was thrown by one of the service metho\nds of the servlet ÝJtsRegistrationServlet¨ in application\nÝrs_war¨. Exception created :\nÝcom.hp.hpl.jena.tdb.base.file.FileException\n: BlockMgrMapped.segmentAllocate: Segment = 0\nCaused by: java.io.IOException: EDC5124I Too many open files.\n(errno2=0x07360344)\n\n\n\nSYSPRT\nTrace: 2016/09/30 14:36:04.390 02 t=7B2E88 c=UNK key=P8 tag= (13007004)\nSourceId: com.ibm.ws.webcontainer.servlet.ServletWrapper.service\nExtendedMessage: BBOO0220E: SRVE0068E: An exception was thrown by\none of the service methods of the servlet ÝJtsRegistrationServle\nt¨ in application Ýrs_war¨. Exception created :\nÝcom.hp.hpl.jena.tdb.base.file.FileException:\nBlockMgrMapped.segmentAllocate: Segmen\nt = 0\n.......\nCaused by: java.io.IOException: EDC5124I Too many open files.\n(errno2=0x07360344)\n\n\n\n\n\nCAUSE\nThe MMAPAREAMAX parameter needs to be configured to allow more open files. \n\nEven if the parameter is already configured to be 40960 you need to configure it for the appropriate user.\n\n\nENVIRONMENT\nThis affects servers on z/OS only.\n\n\n\nDIAGNOSING THE PROBLEM\nReview the relevant log files.\n\n\n\nRESOLVING THE PROBLEM\nThis indicates that the MMAPAREAMAX parameter needs to be configured.\n\nThis is discussed in the z/OS Tuning guide [https://jazz.net/library/article/817].\n\nPreviously we have seen that changing the user's parameter BTASRU value MMAPAREAMAX to 40960 resolved the problem.\n\nYou need to discuss this with your z/OS system administrator to see about changing this.", "ulimits; linux; unix; aix; openfiles; opensockets; sockets; socket; files; ulimit-n; limits.conf; configuration; security; etc; root; init; crontask; cron; nodeagent; dmgr; appserver; server; applicationserver; application; nofile; unlimited; 8000; 8192 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This document describes various ways to set ulimit values on UNIX and Linux operating systems as well as information that pertains to WebSphere Application Server \n\nSYMPTOM\nTuning ulimits correctly can overcome these errors: \n\n * Too Many Open Files \n * Could not lock User prefs. Unix Error Code 24. \n * Truncated Core Dumps / Heap Dumps\n\n\nRESOLVING THE PROBLEM\n \n\nIs it possible to display the current ulimit settings? The command ulimit -Xa will display all current settings that are set for the current login session, where X represents the hard (H) or soft (S) limits to be displayed. By default, if no value is supplied for X, soft limits will be displayed. However if a process is already running, it may have a different ulimit configurations than the current shell that you run the ulimit -a command in.\n\n\n\n\nHow are ulimts set? Soft vs. Hard limits Soft limits are the current setting for a particular limit. They can be increased only to the current hard limit setting. \n\nHard limits are the maximum limit that can be configured. Any changes to these require root access. \n\n \n\nTemporary Settings (for current session) \n\n * \n * ulimit -[H|S]limit_name limit_value\n\n\nTemporary settings are set via the command line using the ulimit command. The limit_name must be present in the command (see the chart below). These settings are only temporary for the current session and will be lost once the session is over or the terminal window is closed. \n\nThis syntax can be used within shell scripts. Any processes spawned from these shell scripts will also have the temporary settings for the lifetime they are running. \n\nBy default, the soft limit will be changed (as changing the hard limit needs root access). Use -H (for hard limits) or -S (for soft limits) to change specific hard or soft limits. \n\nNOTES: \n\nOn HP-UX, if you receive an error when setting a particular limit, and you have altered that particular hard limit, you may need to check and see if it had exceeded the kernel parameters. You can use kctune to check (and alter) these if necessary; check your HP-UX documentation for more information. \n\nFor Solaris, settings in the \"/etc/system\" configuration file also allow configuring of some kernel-wide limits. \n\n \n\nGlobal Settings \n\n[/support/docview.wss?uid=swg21469413&amp;aid=1] Any changes to these global configuration limits files should be performed by your system administrator. Instructions on how to edit the files can be found on the manpage or in the commented section of the configuration file, as they can vary between versions of UNIX or Linux. \n\n \n\nThe format of the file, which differs slightly on versions of AIX and Linux, allows individual limits per users or groups, as well as set hard and soft limits. The limits defined in this configuration file are set globally. \n\n \n\nChanges made to any limits file take effect after launching a new login shell (such as bash -l), or if the user logs out and logs back in to the system. \n\n \n\nNOTES: \n\nOn Solaris and HP-UX, changes made to your shell's profile configuration (.profile or .login) should also take effect on the next login shell launched, or when your user logs back in using the specific shell. \n\nFor kernel-wide settings, which usually require a restart of the operating system to take effect, HP-UX has the kctune command, while Solaris has the /etc/system configuration file. \n\n \n\nSpecifics for each Operating System:\nThe most up-to-date information on the limits can be found in the man page for \"ulimit\".\n\n\n\nAIX \nGlobal settings are generally set in the file /etc/security/limits, although there may be different limit files for LPARs and WPARs. \n\n \n\nPlease note that this table may not represent all ulimit items as they can vary between operating system versions. Consult the ulimit man page or the limits file for further information.\n\n\n\nCommand Line limit_name * /etc/security/limits Description ulimit -c [value] core\ncore_hard Core file size in 512 byte blocks. ulimit -d [value]\n(K bytes) data\ndata_hard Data segment size of processes in kilobytes. ulimit -f [value] fsize\nfsize_hard File size limit in 512 byes blocks. ulimit -n [value] nofiles\nnofiles_hard Max number of open files and/or sockets per process. ulimit -m [value]\n(K bytes) rss\nrss_hard The memory size of the process in kilobytes. ulimit -r [value] threads\nthreads_hard Max number of threads per process. ulimit -s [value]\n(K bytes) stack\nstack_hard The stack segment size in kilobytes. ulimit -t [value]\n(seconds) cpu\ncpu_hard Max per process CPU time (in seconds). ulimit -u [value] nproc\nnproc_hard Specifies the limit of the number of processes per user. * Values are in 512 byte blocks unless otherwise specified, check your man page for further information \n\n\nHP-UX \n\nThere is no global settings file on HP-UX. Instead, you would need to issue the specific ulimit command in your shell's (or user's) profile configuration (like .profile or .login). \n\nThere are similar kernel settings you can also set with kctune, such as \"maxfiles_lim\", but these kernel parameters do not normally need to be changed. Please refer to its man page for further information. \nPlease note that this table may not represent all ulimit items as they can vary between operating system versions. Consult the ulimit man page or your OS documentation for further information.\n\n\n\nCommand \"ulimit\" limit_name* Description ulimit -c [value] Core file size in 512 byte blocks. ulimit -d [value] Data segment size of processes in 512 byte blocks. ulimit -f [value] File size limit in 512 byes blocks. ulimit -n [value] Max number of open files and/or sockets per process. ulimit -m [value] The memory size of the process in 512 byte blocks. ulimit -s [value] The stack segment size in 512 byte blocks. ulimit -t [value]\n(seconds) Max per process CPU time (in seconds). * Values are in 512 byte blocks unless otherwise specified, check your man page for further information. \n\n\nLinux \nGlobal settings are set in the file /etc/security/limits.conf. \n\nThe format for setting each limit is as follows:\n<domain> <type> <item> <value> \n\n<domain> controls which users or groups will have these limits \n\n<type> is either the string \"soft\" or \"hard\" limits.\nThe hyphen \"-\" can also be used which represents both soft and hard limits \n\n<item> and <value> are shown in the table below. Most values can also use the string unlimited. \n\n \n\nPlease note that this table may not represent all ulimit items as they can vary between Linux variants. Consult the ulimit man page or the limits.conf file for further information.\n\n\n\nCommand Line limit_name /etc/security/limits.conf <item> Description ulimit -c [value] core Max core dump file size (KB) ulimit -d [value] data Max data size (KB) ulimit -f [value] fsize Max file size (KB) ulimit -l [value] memlock Max size of address space that can be locked into memory (KB) ulimit -n [value] nofile Max number of open files/sockets per process** ulimit -u [value] nproc Max number of processes for a single user ulimit -m [value] rss Max resident set size (KB) ulimit -s [value] stack The maximum stack size (KB) ulimit -t [value] cpu Max CPU time (minutes or seconds) ** There is a restriction that occurs on Red Hat Enterprise Linux that this value cannot be set to unlimited \n\n\n\n\n\n\n\nSolaris \n\nThere is no global settings file specifically for ulimits on Solaris (however you can set kernel-wide settings in the /etc/system file). Instead, you would need to issue the specific ulimit command in your shell's (or user's) profile configuration (like .profile or .login). \n\nAlso depending on the shell used, the ulimit command is slightly different. See the man page for further information. \n\nYou can also set kernel wide settings for many of these ulimits in the /etc/system file. \nFor example, \"set lim_fd_max = [value]\" and \"set rlim_fd_cur = [value]\" are respectively the global hard and soft file descriptor limits. See the system OS's documentation for information on the /etc/system file. \nPlease note that this table may not represent all ulimit items as they can vary between operating system versions. Consult the ulimit man page or your OS documentation for further information.\n\n\n\nCommand Line limit_name * \n(sh, ksh, bash) Command Line \n(csh) Description ulimit -c [value] ulimit coredumpsize [value]\n(K bytes) Core file size in 512 byte blocks. ulimit -d [value]\n(K bytes) ulimit datasize [value]\n(K bytes) Data segment size of processes in kilobytes. ulimit -f [value] ulimit filesize [value]\n(K bytes) File size limit in 512 byes blocks. ulimit -n [value] ulimit descriptors [value] Max number of open files and/or sockets per process (plus 1) ulimit -s [value]\n(K bytes) ulimit stacksize [value]\n(K bytes) The stack segment size in kilobytes. ulimit -t [value]\n(seconds) ulimit cputime [value]\n(seconds) Max per process CPU time (in seconds). ulimit -v [value]\n(K bytes) ulimit memorysize [value]\n(K bytes) Maximum size of virtual memory (in kilobytes) * Values are in 512 byte blocks unless otherwise specified, check your man page for further information. \n\n\n\n\nIf I am experiencing Too Many Open Files (Unix Error Code 24), can I increase the number of file descriptors? \nYes you can through the ulimit -n [value] command. However these settings won't take effect until you restart your application server (and nodeagent), making sure you restart on the same command line where you executed \"ulimit -n\". \n\nHowever, if you increase the value high enough and still run into these errors, you may want to check for a file descriptor leak (meaning a leak of opened files and/or sockets in your application code). The command lsof, offered on a variety of operating systems, can provide information on the quantity and types of file descriptors in use. \n\nFurther information can be found at this link: Too Many Open Files error message [http://www.ibm.com/support/docview.wss?uid=swg21067352] \n\n\nOn Linux, can I set the ulimit for the number of open files to unlimited? Certain versions of Red Hat Enterprise Linux do not allow this value to be set to unlimited due to a known issue in Red Hat Enterprise Linux 5 [https://bugzilla.redhat.com/show_bug.cgi?id=507159]. The limit must be set to an integer value no larger than 1048576. Other versions of Linux may not have this restriction. In the Information Center for WebSphere Application Server, there is a recommendation [http://www.ibm.com/support/knowledgecenter/en/SSAW57_8.0.0/com.ibm.websphere.nd.doc/info/ae/ae/tprf_tunelinux.html] of 8000. \n\nIf an attempt is made to set this ulimit to unlimited via the command line, an error will be displayed, and the old value will remain in place:\n[root] # ulimit -n unlimited\nbash: ulimit: open files: cannot modify limit: Operation not permitted\n\n\n \n\n[/support/docview.wss?uid=swg21469413&amp;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]", "Installation;Operating Environment; STERLINGNFX TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Too many open files error(s) received, ulimit is set to 2048, /var/log/messages indicates limit is 1024 \n\nSYMPTOM\n\n\nSUSE Linux Enterprise Server 9 only\n\nWhen GIS attempts to open a file or network socket during periods of peak load, an IOException (Too many open files) can be thrown. There will also be a log entry in /var/log/messages \"Open files rlimit 1024 reached for uid xxxx\" where xxxx is the uid of the GIS administrative user. This can occur on clustered systems, as well as non-clustered, but it may not happen on all nodes of a clustered system.\n\n/etc/security/limits.conf has been properly modified with increased limits, logging into the GIS administrative account indicates that the new limits are being used, and /etc/pam.d/login has the line requiring pam_limits.so for sessions.\n\nCustomer indicates that GIS is usually invoked by an automatic scheduler, rather than being manually invoked. lsof output indicates that the number of open files at the time of the error is significantly less than the limits configured in limits.conf, although the number of open files is higher than average for any nodes experiencing the issue.\n\n\n\nError Message /var/log/messages:\n\nOpen files rlimit 1024 reached for uid xxxx (xxxx is the GIS admin user) with a time stamp corresponding with an exception below.\n\nVarious GIS logs:\n\n[2009-02-05 15:01:53.734] ERROR 000310010057 UTIL.UTIL.ERR_IOException Got IOException in URL.send\njava.net.SocketException: Too many open files\nat java.net.Socket.createImpl(Socket.java(Compiled Code))\nat java.net.Socket.<init>(Socket.java(Compiled Code))\nat java.net.Socket.<init>(Socket.java(Compiled Code))\nat com.sterlingcommerce.woodstock.util.URL.send(URL.java(Compiled Code))\nat com.sterlingcommerce.woodstock.util.URL.fetch(URL.java(Compiled Code))\nat com.sterlingcommerce.woodstock.util.Util.removeCache(Util.java(Compiled Code))\nat com.sterlingcommerce.woodstock.services.translation.ExternalDataImpl.onSelect(ExternalDataImpl.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.rules.DBOpcodes.select_I__(DBOpcodes.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.rules.DBOpcodes.select_I__(DBOpcodes.java(Compiled Code))\nat sun.reflect.GeneratedMethodAccessor5896.invoke(Unknown Source)\nat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))\nat java.lang.reflect.Method.invoke(Method.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.rules.ExtendedRuleExecuter.executeRule(ExtendedRuleExecuter.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.blockprocessor.BlockSequence.runOnEndExtendedRule(BlockSequence.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.blockprocessor.BlockSequence.searchForward(BlockSequence.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.blockprocessor.BlockSequence.processFileFormat(BlockSequence.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.engine.TranslationEngineImpl.translateInput(TranslationEngineImpl.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.engine.TranslationEngineImpl.doTranslation(TranslationEngineImpl.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.engine.TranslationEngineImpl.translate(TranslationEngineImpl.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.engine.TranslationEngine.translate(TranslationEngine.java(Inlined Compiled Code))\nat com.sterlingcommerce.woodstock.services.edi.deenvelopex12.DeenvelopeX12ServiceImpl.processTransactions(DeenvelopeX12ServiceImpl.java(Compiled Code))\nat com.sterlingcommerce.woodstock.services.edi.deenvelopex12.DeenvelopeX12ServiceImpl.processGroups(DeenvelopeX12ServiceImpl.java(Compiled Code))\nat com.sterlingcommerce.woodstock.services.edi.deenvelopex12.DeenvelopeX12ServiceImpl.processData(DeenvelopeX12ServiceImpl.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.invokeService(ActivityEngineHelper.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.nextMainLogic(ActivityEngineHelper.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.next(ActivityEngineHelper.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.doWork(WorkFlowQueueListener.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.run(WorkFlowQueueListener.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.onMessage(WorkFlowQueueListener.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.onMessage(WorkFlowQueueListener.java(Inlined Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.queue.wfTransporter.run(wfTransporter.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.queue.BasicExecutor$Worker.run(BasicExecutor.java(Compiled Code))\nat java.lang.Thread.run(Thread.java(Compiled Code))\n\n\nRESOLVING THE PROBLEM\n\n\nIf GIS is invoked with an automatic scheduler (such as cron or Control-M), the daemons may not be PAM aware, so any changes made to /etc/security/limits.conf are ignored, and the default values for /bin/sh are used.\n\nThe most straightforward and least invasive solution is to modify the script being called by the scheduler to start GIS to increase the file descriptor limit by adding the line \"ulimit -n 2048\" (without the quotes).\n\n\n\nSee Novell bulletin 3302273 for further detail.\n\n\n\n\n\n \n\nHISTORICAL NUMBER\n NFX5068 \n\nPRODUCT ALIAS/SYNONYM\n \n\nFunction Area\n\n\nstartup\n\n\nEscalation ID\n\n\n4962281\n\n\nSeverity\n\n\nNormal\n\n\nType\n\n\nNormalFix", " SUBSCRIBE\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 * WinCollect agents use the configuration server to open\n connections from the remote agent to the Console to check for\n log source updates or configuration changes. An issue in the\n configuration server is not closing sockets correctly, which\n can cause ECS issues. This issue only affects WinCollect agents\n at version 7.2.0.\n \n This issue can lead to messages in both the qradar.error or\n qradar.log file for: ECS host.token \"too many open files\".\n \n When this issue occurs, administrators might notice the\n following:\n - Existing WinCollect deployments might notice that new agent\n installations do not register with the Console correctly.\n - Some WinCollect log sources might time out and stop reporting\n events.\n - On the Console, the logs might display an error message \"too\n many open files\", which can stop the ECS service.\n \n \n \n \n \n\nLOCAL FIX\n * Administrators who experience any of these issues with\n WinCollect 7.2.0 agents can download the latest WinCollect\n Configuration Server Protocol rpm file from IBM Fix Central.\n \n Latest versions:\n - PROTOCOL-WinCollectConfigServer-7.1-835960.noarch.rpm\n or\n - PROTOCOL-WinCollectConfigServer-7.2-835963.noarch.rpm\n \n Procedure\n 1. Download the appropriate WinCollect Configuration Server rpm\n for your QRadar Console.\n 2. Copy the rpm file to the Console.\n 3. To install the rpm file, type: rpm -Uvh\n PROTOCOL-WinCollectConfigServer-7.<version>.noarch.rpm\n 4. Log in to the Console.\n 5. Click the Admin tab.\n 6. Click Deploy Full Configuration and wait for the deploy to\n complete.\n Note: The next step logs off current users.\n 7. Click Advanced > Restart Web Server.\n The installation is complete.\n \n If log sources for WinCollect agents continue to time out,\n contact Customer Support for assistance.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * WinCollect agents use the configuration server to open\n connections from the remote agent to the Console to check for\n log source updates or configuration changes. An issue in the\n configuration server is not closing sockets correctly, which\n can cause ECS issues. This issue only affects WinCollect agents\n at version 7.2.0.\n \n This issue can lead to messages in both the qradar.error or\n qradar.log file for: ECS host.token \"too many open files\".\n \n When this issue occurs, administrators might notice the\n following:\n - Existing WinCollect deployments might notice that new agent\n installations do not register with the Console correctly.\n - Some WinCollect log sources might time out and stop reporting\n events.\n - On the Console, the logs might display an error message \"too\n many open files\", which can stop the ECS service.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * A protocol source RPM was released that closed a file handle\n leak in ecs that happened when WinCollect Agents timed out.\n PROTOCOL-WinCollectConfigServer-7.1-835960.noarch.rpm\n PROTOCOL-WinCollectConfigServer-7.2-835963.noarch.rpm\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IV60378\n \n \n * REPORTED COMPONENT NAME\n QRADAR SOFTWARE\n \n \n * REPORTED COMPONENT ID\n 5725QRDSW\n \n \n * REPORTED RELEASE\n 720\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-05-12\n \n \n * CLOSED DATE\n 2014-05-13\n \n \n * LAST MODIFIED DATE\n 2014-05-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 QRADAR SOFTWARE\n \n \n * FIXED COMPONENT ID\n 5725QRDSW\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R710 PSY\n UP" ]

[ [ "2a", "ulimits; linux; unix; aix; openfiles; opensockets; sockets; socket; files; ulimit-n; limits.conf; configuration; security; etc; root; init; crontask; cron; nodeagent; dmgr; appserver; server; applicationserver; application; nofile; unlimited; 8000; 8192 TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "2b", " This document describes various ways to set ulimit values on UNIX and Linux operating systems as well as information that pertains to WebSphere Application Server SYMPTOM" ], [ "2c", "Tuning ulimits correctly can overcome these errors:" ], [ "2d", " * Too Many Open Files" ], [ "2e", " * Could not lock User prefs." ], [ "2f", "Unix Error Code 24." ], [ "2g", " * Truncated Core Dumps / Heap Dumps" ], [ "2h", "RESOLVING THE PROBLEM" ], [ "2i", "Is it possible to display the current ulimit settings?" ], [ "2j", "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." ], [ "2k", "By default, if no value is supplied for X, soft limits will be displayed." ], [ "2l", "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." ], [ "2m", "How are ulimts set?" ], [ "2n", "Soft vs. Hard limits Soft limits are the current setting for a particular limit." ], [ "2o", "They can be increased only to the current hard limit setting." ], [ "2p", "Hard limits are the maximum limit that can be configured." ], [ "2q", "Any changes to these require root access." ], [ "2r", "Temporary Settings (for current session) *" ], [ "2s", " * ulimit -[H|S]limit_name limit_value" ], [ "2t", "Temporary settings are set via the command line using the ulimit command." ], [ "2u", "The limit_name must be present in the command (see the chart below)." ], [ "2v", "These settings are only temporary for the current session and will be lost once the session is over or the terminal window is closed." ], [ "2w", "This syntax can be used within shell scripts." ], [ "2x", "Any processes spawned from these shell scripts will also have the temporary settings for the lifetime they are running." ], [ "2y", "By default, the soft limit will be changed (as changing the hard limit needs root access)." ], [ "2z", "Use -H (for hard limits) or -S (for soft limits) to change specific hard or soft limits. NOTES:" ], [ "2aa", "On HP-UX, if you receive an error when setting a particular limit, and you have altered that particular hard limit, you may need to check and see if it had exceeded the kernel parameters." ], [ "2ab", "You can use kctune to check (and alter) these if necessary; check your HP-UX documentation for more information." ], [ "2ac", "For Solaris, settings in the \"/etc/system\" configuration file also allow configuring of some kernel-wide limits. Global Settings" ], [ "2ad", "[/support/docview.wss?uid=swg21469413&amp;aid=1] Any changes to these global configuration limits files should be performed by your system administrator." ], [ "2ae", "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." ], [ "2af", "The format of the file, which differs slightly on versions of AIX and Linux, allows individual limits per users or groups, as well as set hard and soft limits." ], [ "2ag", "The limits defined in this configuration file are set globally." ], [ "2ah", "Changes made to any limits file take effect after launching a new login shell (such as bash -l), or if the user logs out and logs back in to the system. NOTES:" ], [ "2ai", "On Solaris and HP-UX, changes made to your shell's profile configuration (.profile or .login) should also take effect on the next login shell launched, or when your user logs back in using the specific shell." ], [ "2aj", "For kernel-wide settings, which usually require a restart of the operating system to take effect, HP-UX has the kctune command, while Solaris has the /etc/system configuration file." ], [ "2ak", "Specifics for each Operating System:" ], [ "2al", "The most up-to-date information on the limits can be found in the man page for \"ulimit\". AIX" ], [ "2am", "Global settings are generally set in the file /etc/security/limits, although there may be different limit files for LPARs and WPARs." ], [ "2an", "Please note that this table may not represent all ulimit items as they can vary between operating system versions." ], [ "2ao", "Consult the ulimit man page or the limits file for further information." ], [ "2ap", "Command Line limit_name * /etc/security/limits Description ulimit -c [value] core" ], [ "2aq", "core_hard Core file size in 512 byte blocks." ], [ "2ar", "ulimit -d [value]" ], [ "2as", "(K bytes) data" ], [ "2at", "data_hard Data segment size of processes in kilobytes." ], [ "2au", "ulimit -f [value] fsize" ], [ "2av", "fsize_hard File size limit in 512 byes blocks." ], [ "2aw", "ulimit -n [value] nofiles" ], [ "2ax", "nofiles_hard Max number of open files and/or sockets per process." ], [ "2ay", "ulimit -m [value]" ], [ "2az", "(K bytes) rss" ], [ "2ba", "rss_hard The memory size of the process in kilobytes." ], [ "2bb", "ulimit -r [value] threads" ], [ "2bc", "threads_hard Max number of threads per process." ], [ "2bd", "ulimit -s [value]" ], [ "2be", "(K bytes) stack" ], [ "2bf", "stack_hard The stack segment size in kilobytes." ], [ "2bg", "ulimit -t [value] (seconds) cpu" ], [ "2bh", "cpu_hard Max per process CPU time (in seconds)." ], [ "2bi", "ulimit -u [value] nproc" ], [ "2bj", "nproc_hard Specifies the limit of the number of processes per user." ], [ "2bk", "* Values are in 512 byte blocks unless otherwise specified, check your man page for further information HP-UX" ], [ "2bl", "There is no global settings file on HP-UX." ], [ "2bm", "Instead, you would need to issue the specific ulimit command in your shell's (or user's) profile configuration (like .profile or .login)." ], [ "2bn", "There are similar kernel settings you can also set with kctune, such as \"maxfiles_lim\", but these kernel parameters do not normally need to be changed." ], [ "2bo", "Please refer to its man page for further information." ], [ "2bp", "Please note that this table may not represent all ulimit items as they can vary between operating system versions." ], [ "2bq", "Consult the ulimit man page or your OS documentation for further information." ], [ "2br", "Command \"ulimit\" limit_name* Description ulimit -c [value] Core file size in 512 byte blocks." ], [ "2bs", "ulimit -d [value] Data segment size of processes in 512 byte blocks." ], [ "2bt", "ulimit -f [value] File size limit in 512 byes blocks." ], [ "2bu", "ulimit -n [value] Max number of open files and/or sockets per process." ], [ "2bv", "ulimit -m [value] The memory size of the process in 512 byte blocks." ], [ "2bw", "ulimit -s [value] The stack segment size in 512 byte blocks." ], [ "2bx", "ulimit -t [value]" ], [ "2by", "(seconds) Max per process CPU time (in seconds)." ], [ "2bz", "* Values are in 512 byte blocks unless otherwise specified, check your man page for further information. Linux" ], [ "2ca", "Global settings are set in the file /etc/security/limits.conf." ], [ "2cb", "The format for setting each limit is as follows:" ], [ "2cc", "<domain> <type> <item> <value>" ], [ "2cd", "<domain> controls which users or groups will have these limits" ], [ "2ce", "<type> is either the string \"soft\" or \"hard\" limits." ], [ "2cf", "The hyphen \"-\" can also be used which represents both soft and hard limits" ], [ "2cg", "<item> and <value> are shown in the table below." ], [ "2ch", "Most values can also use the string unlimited." ], [ "2ci", "Please note that this table may not represent all ulimit items as they can vary between Linux variants." ], [ "2cj", "Consult the ulimit man page or the limits.conf file for further information." ], [ "2ck", "Command Line limit_name /etc/security/limits.conf <item> Description ulimit -c [value] core Max core dump file size (KB) ulimit -d [value] data Max data size (KB) ulimit -f [value] fsize Max file size (KB) ulimit -l [value] memlock Max size of address space that can be locked into memory (KB) ulimit -n [value] nofile Max number of open files/sockets per process** ulimit -u [value] nproc Max number of processes for a single user ulimit -m [value] rss Max resident set size (KB) ulimit -s [value] stack The maximum stack size (KB) ulimit -t [value] cpu Max CPU time (minutes or seconds) ** There is a restriction that occurs on Red Hat Enterprise Linux that this value cannot be set to unlimited Solaris" ], [ "2cl", "There is no global settings file specifically for ulimits on Solaris (however you can set kernel-wide settings in the /etc/system file)." ], [ "2cm", "Instead, you would need to issue the specific ulimit command in your shell's (or user's) profile configuration (like .profile or .login)." ], [ "2cn", "Also depending on the shell used, the ulimit command is slightly different." ], [ "2co", "See the man page for further information." ], [ "2cp", "You can also set kernel wide settings for many of these ulimits in the /etc/system file." ], [ "2cq", "For example, \"set lim_fd_max = [value]\" and \"set rlim_fd_cur = [value]\" are respectively the global hard and soft file descriptor limits." ], [ "2cr", "See the system OS's documentation for information on the /etc/system file." ], [ "2cs", "Please note that this table may not represent all ulimit items as they can vary between operating system versions." ], [ "2ct", "Consult the ulimit man page or your OS documentation for further information." ], [ "2cu", "Command Line limit_name *" ], [ "2cv", "(sh, ksh, bash) Command Line" ], [ "2cw", "(csh) Description ulimit -c [value] ulimit coredumpsize [value]" ], [ "2cx", "(K bytes) Core file size in 512 byte blocks." ], [ "2cy", "ulimit -d [value]" ], [ "2cz", "(K bytes) ulimit datasize [value]" ], [ "2da", "(K bytes) Data segment size of processes in kilobytes." ], [ "2db", "ulimit -f [value] ulimit filesize [value]" ], [ "2dc", "(K bytes) File size limit in 512 byes blocks." ], [ "2dd", "ulimit -n [value] ulimit descriptors [value] Max number of open files and/or sockets per process (plus 1) ulimit -s [value]" ], [ "2de", "(K bytes) ulimit stacksize [value]" ], [ "2df", "(K bytes) The stack segment size in kilobytes." ], [ "2dg", "ulimit -t [value]" ], [ "2dh", "(seconds) ulimit cputime [value]" ], [ "2di", "(seconds) Max per process CPU time (in seconds)." ], [ "2dj", "ulimit -v [value]" ], [ "2dk", "(K bytes) ulimit memorysize [value]" ], [ "2dl", "(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." ], [ "2dm", "If I am experiencing Too Many Open Files (Unix Error Code 24), can I increase the number of file descriptors?" ], [ "2dn", "Yes you can through the ulimit -n [value] command." ], [ "2do", "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\"." ], [ "2dp", "However, if you increase the value high enough and still run into these errors, you may want to check for a file descriptor leak (meaning a leak of opened files and/or sockets in your application code)." ], [ "2dq", "The command lsof, offered on a variety of operating systems, can provide information on the quantity and types of file descriptors in use." ], [ "2dr", "Further information can be found at this link: Too Many Open Files error message [http://www.ibm.com/support/docview.wss?uid=swg21067352]" ], [ "2ds", "On Linux, can I set the ulimit for the number of open files to unlimited?" ], [ "2dt", "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]." ], [ "2du", "The limit must be set to an integer value no larger than 1048576." ], [ "2dv", "Other versions of Linux may not have this restriction." ], [ "2dw", "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." ], [ "2dx", "If an attempt is made to set this ulimit to unlimited via the command line, an error will be displayed, and the old value will remain in place:" ], [ "2dy", "[root] # ulimit -n unlimited" ], [ "2dz", "bash: ulimit: open files: cannot modify limit: Operation not permitted" ], [ "2ea", "[/support/docview.wss?uid=swg21469413&amp;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." ], [ "2eb", "This will prevent any new processes from spawning by that user or group." ], [ "2ec", "If this is the root user, the system will slowly die as new processes will be unable to generate." ], [ "2ed", "A recovery disc will be needed to reset the value." ], [ "2ee", "On Red Hat Enterprise Linux 6, why are my settings for nproc (ulimit -u) not being honored." ], [ "2ef", "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." ], [ "2eg", "This file contains a line for nproc configured with a soft limit of 1024." ], [ "2eh", "* soft nproc 1024" ], [ "2ei", "The rationale for this was to prevent fork bombs from occurring, To keep using the limits.conf for your nproc ulimit settings, you would need to comment this line out by making the first character on the line a hash/pound symbol." ], [ "2ej", "#* soft nproc 1024" ], [ "2ek", "I am using an /etc/init.d script (or inittab) to start my application server and setting the global ulimit settings had no effect?" ], [ "2el", "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." ], [ "2em", "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." ], [ "2en", "At startup, the operating system hasn't begun to load specific profiles up, even the root user." ], [ "2eo", "When you see individual services and processes starting, these are all child processes of the init process" ], [ "2ep", "This was previously documented for AIX 6.1 in the following Knowledge Center article entitled \"telinit or init Command\", under the Environments section." ], [ "2eq", "Here's the quoted section:" ], [ "2er", "\"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." ], [ "2es", "The result is that a command that is successfully executed from the command line may not execute correctly when invoked by init." ], [ "2et", "Any command that has specific ulimit requirements should include specific actions to set the ulimit values as required.\" RELATED INFORMATION" ], [ "2eu", " Domino for Linux (see step 2) [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21377724]" ], [ "2ev", "AIX - IBM SDK 7.0 User Guide - Ulimits [http://publib.boulder.ibm.com/infocenter/java7sdk/v7r0/index.jsp?topic=%2Fcom.ibm.java.aix.70.doc%2Fuser%2Fulimits.html]" ], [ "2ew", "Linux - IBM SDK 7.0 User Guide - Ulimits [http://publib.boulder.ibm.com/infocenter/java7sdk/v7r0/index.jsp?topic=%2Fcom.ibm.java.lnx.70.doc%2Fuser%2Fulimits.html]" ] ]

[ "2i", "2j", "2k", "2l", "2dn", "2do", "2dq", "2dm", "2ds", "3aw", "3ax" ]

[ " TECHNOTE (FAQ)\n\nQUESTION\n How do documents get in the stuck in processing Queue? \n\nCAUSE\nThere are multiple reasons which could cause documents to become stuck in the processing queue. The most common reasons: \n\n * Data restore was done, or \n * PC was rebooted during a process, or \n * Tried to use a retired communication session.\n\nANSWER\nTo get more detail about the reason for the problem, view the Audit Log for error messages. \n\nClick View > Audit Log\n\nTo resolve the problem: \n\n 1. Try to reset the document and reprocess the data: 1. Click on View > Processing \n 2. Highlight all documents \n 3. Click RESET button \n 4. Try sending data again. \n \n \n 2. Verify that routine cleanup has been done on temp and audit log files, and that the document count maintained in Gentran:Director's browser drawers meets the required system limits. \n\n\nFor more information about maintenance, see the White Paper entitled \"Maintenance Summary\" in Sterling Gentran:Director Documentation [http://www.ibm.com/support/docview.wss?uid=swg27023726#wp] Note: Gentran:Director system limitations: \n\n * No more than 1000 documents per interchange. \n * No more than 7500 InDrawer documents and 7500 OutDrawer documents in the system at any time. \n * No interchange should exceed 10 megabytes in size. \n * No document (EDI or Application Import) should exceed 2 megabytes in size. \n * If too many messages are being scanned, use Commerce Mail and pickup old Network Reports that are waiting.\n\n \n\nHISTORICAL NUMBER\n PRI102\nSCI3744", "EDC5124I; Too many open files; MMAPAREAMAX TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to configure IBM Jazz Reporting Service (JRS) (Report Builder) on z/OS fails with the message \"java.io.IOException: EDC5124I Too many open files\" in the SYSOUT log \n\nSYMPTOM\nThe JRS server fails to install and you find errors similar to the following the SYSOUT and SYSPRT log files.\n\n\nSYSOUT:\nSRVE0068E: An exception was thrown by one of the service metho\nds of the servlet ÝJtsRegistrationServlet¨ in application\nÝrs_war¨. Exception created :\nÝcom.hp.hpl.jena.tdb.base.file.FileException\n: BlockMgrMapped.segmentAllocate: Segment = 0\nCaused by: java.io.IOException: EDC5124I Too many open files.\n(errno2=0x07360344)\n\n\n\nSYSPRT\nTrace: 2016/09/30 14:36:04.390 02 t=7B2E88 c=UNK key=P8 tag= (13007004)\nSourceId: com.ibm.ws.webcontainer.servlet.ServletWrapper.service\nExtendedMessage: BBOO0220E: SRVE0068E: An exception was thrown by\none of the service methods of the servlet ÝJtsRegistrationServle\nt¨ in application Ýrs_war¨. Exception created :\nÝcom.hp.hpl.jena.tdb.base.file.FileException:\nBlockMgrMapped.segmentAllocate: Segmen\nt = 0\n.......\nCaused by: java.io.IOException: EDC5124I Too many open files.\n(errno2=0x07360344)\n\n\n\n\n\nCAUSE\nThe MMAPAREAMAX parameter needs to be configured to allow more open files. \n\nEven if the parameter is already configured to be 40960 you need to configure it for the appropriate user.\n\n\nENVIRONMENT\nThis affects servers on z/OS only.\n\n\n\nDIAGNOSING THE PROBLEM\nReview the relevant log files.\n\n\n\nRESOLVING THE PROBLEM\nThis indicates that the MMAPAREAMAX parameter needs to be configured.\n\nThis is discussed in the z/OS Tuning guide [https://jazz.net/library/article/817].\n\nPreviously we have seen that changing the user's parameter BTASRU value MMAPAREAMAX to 40960 resolved the problem.\n\nYou need to discuss this with your z/OS system administrator to see about changing this.", "ulimits; linux; unix; aix; openfiles; opensockets; sockets; socket; files; ulimit-n; limits.conf; configuration; security; etc; root; init; crontask; cron; nodeagent; dmgr; appserver; server; applicationserver; application; nofile; unlimited; 8000; 8192 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This document describes various ways to set ulimit values on UNIX and Linux operating systems as well as information that pertains to WebSphere Application Server \n\nSYMPTOM\nTuning ulimits correctly can overcome these errors: \n\n * Too Many Open Files \n * Could not lock User prefs. Unix Error Code 24. \n * Truncated Core Dumps / Heap Dumps\n\n\nRESOLVING THE PROBLEM\n \n\nIs it possible to display the current ulimit settings? The command ulimit -Xa will display all current settings that are set for the current login session, where X represents the hard (H) or soft (S) limits to be displayed. By default, if no value is supplied for X, soft limits will be displayed. However if a process is already running, it may have a different ulimit configurations than the current shell that you run the ulimit -a command in.\n\n\n\n\nHow are ulimts set? Soft vs. Hard limits Soft limits are the current setting for a particular limit. They can be increased only to the current hard limit setting. \n\nHard limits are the maximum limit that can be configured. Any changes to these require root access. \n\n \n\nTemporary Settings (for current session) \n\n * \n * ulimit -[H|S]limit_name limit_value\n\n\nTemporary settings are set via the command line using the ulimit command. The limit_name must be present in the command (see the chart below). These settings are only temporary for the current session and will be lost once the session is over or the terminal window is closed. \n\nThis syntax can be used within shell scripts. Any processes spawned from these shell scripts will also have the temporary settings for the lifetime they are running. \n\nBy default, the soft limit will be changed (as changing the hard limit needs root access). Use -H (for hard limits) or -S (for soft limits) to change specific hard or soft limits. \n\nNOTES: \n\nOn HP-UX, if you receive an error when setting a particular limit, and you have altered that particular hard limit, you may need to check and see if it had exceeded the kernel parameters. You can use kctune to check (and alter) these if necessary; check your HP-UX documentation for more information. \n\nFor Solaris, settings in the \"/etc/system\" configuration file also allow configuring of some kernel-wide limits. \n\n \n\nGlobal Settings \n\n[/support/docview.wss?uid=swg21469413&amp;aid=1] Any changes to these global configuration limits files should be performed by your system administrator. Instructions on how to edit the files can be found on the manpage or in the commented section of the configuration file, as they can vary between versions of UNIX or Linux. \n\n \n\nThe format of the file, which differs slightly on versions of AIX and Linux, allows individual limits per users or groups, as well as set hard and soft limits. The limits defined in this configuration file are set globally. \n\n \n\nChanges made to any limits file take effect after launching a new login shell (such as bash -l), or if the user logs out and logs back in to the system. \n\n \n\nNOTES: \n\nOn Solaris and HP-UX, changes made to your shell's profile configuration (.profile or .login) should also take effect on the next login shell launched, or when your user logs back in using the specific shell. \n\nFor kernel-wide settings, which usually require a restart of the operating system to take effect, HP-UX has the kctune command, while Solaris has the /etc/system configuration file. \n\n \n\nSpecifics for each Operating System:\nThe most up-to-date information on the limits can be found in the man page for \"ulimit\".\n\n\n\nAIX \nGlobal settings are generally set in the file /etc/security/limits, although there may be different limit files for LPARs and WPARs. \n\n \n\nPlease note that this table may not represent all ulimit items as they can vary between operating system versions. Consult the ulimit man page or the limits file for further information.\n\n\n\nCommand Line limit_name * /etc/security/limits Description ulimit -c [value] core\ncore_hard Core file size in 512 byte blocks. ulimit -d [value]\n(K bytes) data\ndata_hard Data segment size of processes in kilobytes. ulimit -f [value] fsize\nfsize_hard File size limit in 512 byes blocks. ulimit -n [value] nofiles\nnofiles_hard Max number of open files and/or sockets per process. ulimit -m [value]\n(K bytes) rss\nrss_hard The memory size of the process in kilobytes. ulimit -r [value] threads\nthreads_hard Max number of threads per process. ulimit -s [value]\n(K bytes) stack\nstack_hard The stack segment size in kilobytes. ulimit -t [value]\n(seconds) cpu\ncpu_hard Max per process CPU time (in seconds). ulimit -u [value] nproc\nnproc_hard Specifies the limit of the number of processes per user. * Values are in 512 byte blocks unless otherwise specified, check your man page for further information \n\n\nHP-UX \n\nThere is no global settings file on HP-UX. Instead, you would need to issue the specific ulimit command in your shell's (or user's) profile configuration (like .profile or .login). \n\nThere are similar kernel settings you can also set with kctune, such as \"maxfiles_lim\", but these kernel parameters do not normally need to be changed. Please refer to its man page for further information. \nPlease note that this table may not represent all ulimit items as they can vary between operating system versions. Consult the ulimit man page or your OS documentation for further information.\n\n\n\nCommand \"ulimit\" limit_name* Description ulimit -c [value] Core file size in 512 byte blocks. ulimit -d [value] Data segment size of processes in 512 byte blocks. ulimit -f [value] File size limit in 512 byes blocks. ulimit -n [value] Max number of open files and/or sockets per process. ulimit -m [value] The memory size of the process in 512 byte blocks. ulimit -s [value] The stack segment size in 512 byte blocks. ulimit -t [value]\n(seconds) Max per process CPU time (in seconds). * Values are in 512 byte blocks unless otherwise specified, check your man page for further information. \n\n\nLinux \nGlobal settings are set in the file /etc/security/limits.conf. \n\nThe format for setting each limit is as follows:\n<domain> <type> <item> <value> \n\n<domain> controls which users or groups will have these limits \n\n<type> is either the string \"soft\" or \"hard\" limits.\nThe hyphen \"-\" can also be used which represents both soft and hard limits \n\n<item> and <value> are shown in the table below. Most values can also use the string unlimited. \n\n \n\nPlease note that this table may not represent all ulimit items as they can vary between Linux variants. Consult the ulimit man page or the limits.conf file for further information.\n\n\n\nCommand Line limit_name /etc/security/limits.conf <item> Description ulimit -c [value] core Max core dump file size (KB) ulimit -d [value] data Max data size (KB) ulimit -f [value] fsize Max file size (KB) ulimit -l [value] memlock Max size of address space that can be locked into memory (KB) ulimit -n [value] nofile Max number of open files/sockets per process** ulimit -u [value] nproc Max number of processes for a single user ulimit -m [value] rss Max resident set size (KB) ulimit -s [value] stack The maximum stack size (KB) ulimit -t [value] cpu Max CPU time (minutes or seconds) ** There is a restriction that occurs on Red Hat Enterprise Linux that this value cannot be set to unlimited \n\n\n\n\n\n\n\nSolaris \n\nThere is no global settings file specifically for ulimits on Solaris (however you can set kernel-wide settings in the /etc/system file). Instead, you would need to issue the specific ulimit command in your shell's (or user's) profile configuration (like .profile or .login). \n\nAlso depending on the shell used, the ulimit command is slightly different. See the man page for further information. \n\nYou can also set kernel wide settings for many of these ulimits in the /etc/system file. \nFor example, \"set lim_fd_max = [value]\" and \"set rlim_fd_cur = [value]\" are respectively the global hard and soft file descriptor limits. See the system OS's documentation for information on the /etc/system file. \nPlease note that this table may not represent all ulimit items as they can vary between operating system versions. Consult the ulimit man page or your OS documentation for further information.\n\n\n\nCommand Line limit_name * \n(sh, ksh, bash) Command Line \n(csh) Description ulimit -c [value] ulimit coredumpsize [value]\n(K bytes) Core file size in 512 byte blocks. ulimit -d [value]\n(K bytes) ulimit datasize [value]\n(K bytes) Data segment size of processes in kilobytes. ulimit -f [value] ulimit filesize [value]\n(K bytes) File size limit in 512 byes blocks. ulimit -n [value] ulimit descriptors [value] Max number of open files and/or sockets per process (plus 1) ulimit -s [value]\n(K bytes) ulimit stacksize [value]\n(K bytes) The stack segment size in kilobytes. ulimit -t [value]\n(seconds) ulimit cputime [value]\n(seconds) Max per process CPU time (in seconds). ulimit -v [value]\n(K bytes) ulimit memorysize [value]\n(K bytes) Maximum size of virtual memory (in kilobytes) * Values are in 512 byte blocks unless otherwise specified, check your man page for further information. \n\n\n\n\nIf I am experiencing Too Many Open Files (Unix Error Code 24), can I increase the number of file descriptors? \nYes you can through the ulimit -n [value] command. However these settings won't take effect until you restart your application server (and nodeagent), making sure you restart on the same command line where you executed \"ulimit -n\". \n\nHowever, if you increase the value high enough and still run into these errors, you may want to check for a file descriptor leak (meaning a leak of opened files and/or sockets in your application code). The command lsof, offered on a variety of operating systems, can provide information on the quantity and types of file descriptors in use. \n\nFurther information can be found at this link: Too Many Open Files error message [http://www.ibm.com/support/docview.wss?uid=swg21067352] \n\n\nOn Linux, can I set the ulimit for the number of open files to unlimited? Certain versions of Red Hat Enterprise Linux do not allow this value to be set to unlimited due to a known issue in Red Hat Enterprise Linux 5 [https://bugzilla.redhat.com/show_bug.cgi?id=507159]. The limit must be set to an integer value no larger than 1048576. Other versions of Linux may not have this restriction. In the Information Center for WebSphere Application Server, there is a recommendation [http://www.ibm.com/support/knowledgecenter/en/SSAW57_8.0.0/com.ibm.websphere.nd.doc/info/ae/ae/tprf_tunelinux.html] of 8000. \n\nIf an attempt is made to set this ulimit to unlimited via the command line, an error will be displayed, and the old value will remain in place:\n[root] # ulimit -n unlimited\nbash: ulimit: open files: cannot modify limit: Operation not permitted\n\n\n \n\n[/support/docview.wss?uid=swg21469413&amp;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]", "Installation;Operating Environment; STERLINGNFX TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Too many open files error(s) received, ulimit is set to 2048, /var/log/messages indicates limit is 1024 \n\nSYMPTOM\n\n\nSUSE Linux Enterprise Server 9 only\n\nWhen GIS attempts to open a file or network socket during periods of peak load, an IOException (Too many open files) can be thrown. There will also be a log entry in /var/log/messages \"Open files rlimit 1024 reached for uid xxxx\" where xxxx is the uid of the GIS administrative user. This can occur on clustered systems, as well as non-clustered, but it may not happen on all nodes of a clustered system.\n\n/etc/security/limits.conf has been properly modified with increased limits, logging into the GIS administrative account indicates that the new limits are being used, and /etc/pam.d/login has the line requiring pam_limits.so for sessions.\n\nCustomer indicates that GIS is usually invoked by an automatic scheduler, rather than being manually invoked. lsof output indicates that the number of open files at the time of the error is significantly less than the limits configured in limits.conf, although the number of open files is higher than average for any nodes experiencing the issue.\n\n\n\nError Message /var/log/messages:\n\nOpen files rlimit 1024 reached for uid xxxx (xxxx is the GIS admin user) with a time stamp corresponding with an exception below.\n\nVarious GIS logs:\n\n[2009-02-05 15:01:53.734] ERROR 000310010057 UTIL.UTIL.ERR_IOException Got IOException in URL.send\njava.net.SocketException: Too many open files\nat java.net.Socket.createImpl(Socket.java(Compiled Code))\nat java.net.Socket.<init>(Socket.java(Compiled Code))\nat java.net.Socket.<init>(Socket.java(Compiled Code))\nat com.sterlingcommerce.woodstock.util.URL.send(URL.java(Compiled Code))\nat com.sterlingcommerce.woodstock.util.URL.fetch(URL.java(Compiled Code))\nat com.sterlingcommerce.woodstock.util.Util.removeCache(Util.java(Compiled Code))\nat com.sterlingcommerce.woodstock.services.translation.ExternalDataImpl.onSelect(ExternalDataImpl.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.rules.DBOpcodes.select_I__(DBOpcodes.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.rules.DBOpcodes.select_I__(DBOpcodes.java(Compiled Code))\nat sun.reflect.GeneratedMethodAccessor5896.invoke(Unknown Source)\nat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))\nat java.lang.reflect.Method.invoke(Method.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.rules.ExtendedRuleExecuter.executeRule(ExtendedRuleExecuter.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.blockprocessor.BlockSequence.runOnEndExtendedRule(BlockSequence.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.blockprocessor.BlockSequence.searchForward(BlockSequence.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.blockprocessor.BlockSequence.processFileFormat(BlockSequence.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.engine.TranslationEngineImpl.translateInput(TranslationEngineImpl.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.engine.TranslationEngineImpl.doTranslation(TranslationEngineImpl.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.engine.TranslationEngineImpl.translate(TranslationEngineImpl.java(Compiled Code))\nat com.sterlingcommerce.woodstock.translator.engine.TranslationEngine.translate(TranslationEngine.java(Inlined Compiled Code))\nat com.sterlingcommerce.woodstock.services.edi.deenvelopex12.DeenvelopeX12ServiceImpl.processTransactions(DeenvelopeX12ServiceImpl.java(Compiled Code))\nat com.sterlingcommerce.woodstock.services.edi.deenvelopex12.DeenvelopeX12ServiceImpl.processGroups(DeenvelopeX12ServiceImpl.java(Compiled Code))\nat com.sterlingcommerce.woodstock.services.edi.deenvelopex12.DeenvelopeX12ServiceImpl.processData(DeenvelopeX12ServiceImpl.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.invokeService(ActivityEngineHelper.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.nextMainLogic(ActivityEngineHelper.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.next(ActivityEngineHelper.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.doWork(WorkFlowQueueListener.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.run(WorkFlowQueueListener.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.onMessage(WorkFlowQueueListener.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.onMessage(WorkFlowQueueListener.java(Inlined Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.queue.wfTransporter.run(wfTransporter.java(Compiled Code))\nat com.sterlingcommerce.woodstock.workflow.queue.BasicExecutor$Worker.run(BasicExecutor.java(Compiled Code))\nat java.lang.Thread.run(Thread.java(Compiled Code))\n\n\nRESOLVING THE PROBLEM\n\n\nIf GIS is invoked with an automatic scheduler (such as cron or Control-M), the daemons may not be PAM aware, so any changes made to /etc/security/limits.conf are ignored, and the default values for /bin/sh are used.\n\nThe most straightforward and least invasive solution is to modify the script being called by the scheduler to start GIS to increase the file descriptor limit by adding the line \"ulimit -n 2048\" (without the quotes).\n\n\n\nSee Novell bulletin 3302273 for further detail.\n\n\n\n\n\n \n\nHISTORICAL NUMBER\n NFX5068 \n\nPRODUCT ALIAS/SYNONYM\n \n\nFunction Area\n\n\nstartup\n\n\nEscalation ID\n\n\n4962281\n\n\nSeverity\n\n\nNormal\n\n\nType\n\n\nNormalFix", " SUBSCRIBE\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 * WinCollect agents use the configuration server to open\n connections from the remote agent to the Console to check for\n log source updates or configuration changes. An issue in the\n configuration server is not closing sockets correctly, which\n can cause ECS issues. This issue only affects WinCollect agents\n at version 7.2.0.\n \n This issue can lead to messages in both the qradar.error or\n qradar.log file for: ECS host.token \"too many open files\".\n \n When this issue occurs, administrators might notice the\n following:\n - Existing WinCollect deployments might notice that new agent\n installations do not register with the Console correctly.\n - Some WinCollect log sources might time out and stop reporting\n events.\n - On the Console, the logs might display an error message \"too\n many open files\", which can stop the ECS service.\n \n \n \n \n \n\nLOCAL FIX\n * Administrators who experience any of these issues with\n WinCollect 7.2.0 agents can download the latest WinCollect\n Configuration Server Protocol rpm file from IBM Fix Central.\n \n Latest versions:\n - PROTOCOL-WinCollectConfigServer-7.1-835960.noarch.rpm\n or\n - PROTOCOL-WinCollectConfigServer-7.2-835963.noarch.rpm\n \n Procedure\n 1. Download the appropriate WinCollect Configuration Server rpm\n for your QRadar Console.\n 2. Copy the rpm file to the Console.\n 3. To install the rpm file, type: rpm -Uvh\n PROTOCOL-WinCollectConfigServer-7.<version>.noarch.rpm\n 4. Log in to the Console.\n 5. Click the Admin tab.\n 6. Click Deploy Full Configuration and wait for the deploy to\n complete.\n Note: The next step logs off current users.\n 7. Click Advanced > Restart Web Server.\n The installation is complete.\n \n If log sources for WinCollect agents continue to time out,\n contact Customer Support for assistance.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * WinCollect agents use the configuration server to open\n connections from the remote agent to the Console to check for\n log source updates or configuration changes. An issue in the\n configuration server is not closing sockets correctly, which\n can cause ECS issues. This issue only affects WinCollect agents\n at version 7.2.0.\n \n This issue can lead to messages in both the qradar.error or\n qradar.log file for: ECS host.token \"too many open files\".\n \n When this issue occurs, administrators might notice the\n following:\n - Existing WinCollect deployments might notice that new agent\n installations do not register with the Console correctly.\n - Some WinCollect log sources might time out and stop reporting\n events.\n - On the Console, the logs might display an error message \"too\n many open files\", which can stop the ECS service.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * A protocol source RPM was released that closed a file handle\n leak in ecs that happened when WinCollect Agents timed out.\n PROTOCOL-WinCollectConfigServer-7.1-835960.noarch.rpm\n PROTOCOL-WinCollectConfigServer-7.2-835963.noarch.rpm\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IV60378\n \n \n * REPORTED COMPONENT NAME\n QRADAR SOFTWARE\n \n \n * REPORTED COMPONENT ID\n 5725QRDSW\n \n \n * REPORTED RELEASE\n 720\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-05-12\n \n \n * CLOSED DATE\n 2014-05-13\n \n \n * LAST MODIFIED DATE\n 2014-05-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 QRADAR SOFTWARE\n \n \n * FIXED COMPONENT ID\n 5725QRDSW\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R710 PSY\n UP" ]

[ [ "3a", "Installation;Operating Environment; STERLINGNFX TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "3b", " Too many open files error(s) received, ulimit is set to 2048, /var/log/messages indicates limit is 1024 SYMPTOM" ], [ "3c", "SUSE Linux Enterprise Server 9 only" ], [ "3d", "When GIS attempts to open a file or network socket during periods of peak load, an IOException (Too many open files) can be thrown." ], [ "3e", "There will also be a log entry in /var/log/messages \"Open files rlimit 1024 reached for uid xxxx\" where xxxx is the uid of the GIS administrative user." ], [ "3f", "This can occur on clustered systems, as well as non-clustered, but it may not happen on all nodes of a clustered system." ], [ "3g", "/etc/security/limits.conf has been properly modified with increased limits, logging into the GIS administrative account indicates that the new limits are being used, and /etc/pam.d/login has the line requiring pam_limits.so for sessions." ], [ "3h", "Customer indicates that GIS is usually invoked by an automatic scheduler, rather than being manually invoked." ], [ "3i", "lsof output indicates that the number of open files at the time of the error is significantly less than the limits configured in limits.conf, although the number of open files is higher than average for any nodes experiencing the issue." ], [ "3j", "Error Message /var/log/messages:" ], [ "3k", "Open files rlimit 1024 reached for uid xxxx (xxxx is the GIS admin user) with a time stamp corresponding with an exception below." ], [ "3l", "Various GIS logs:" ], [ "3m", "[2009-02-05 15:01:53.734] ERROR 000310010057 UTIL.UTIL.ERR_IOException Got IOException in URL.send" ], [ "3n", "java.net.SocketException: Too many open files" ], [ "3o", "at java.net.Socket.createImpl(Socket.java(Compiled Code))" ], [ "3p", "at java.net.Socket.<init>(Socket.java(Compiled Code))" ], [ "3q", "at java.net.Socket.<init>(Socket.java(Compiled Code))" ], [ "3r", "at com.sterlingcommerce.woodstock.util.URL.send(URL.java(Compiled Code))" ], [ "3s", "at com.sterlingcommerce.woodstock.util.URL.fetch(URL.java(Compiled Code))" ], [ "3t", "at com.sterlingcommerce.woodstock.util.Util.removeCache(Util.java(Compiled Code))" ], [ "3u", "at com.sterlingcommerce.woodstock.services.translation.ExternalDataImpl.onSelect(ExternalDataImpl.java(Compiled Code))" ], [ "3v", "at com.sterlingcommerce.woodstock.translator.rules.DBOpcodes.select_I__(DBOpcodes.java(Compiled Code))" ], [ "3w", "at com.sterlingcommerce.woodstock.translator.rules.DBOpcodes.select_I__(DBOpcodes.java(Compiled Code))" ], [ "3x", "at sun.reflect.GeneratedMethodAccessor5896.invoke(Unknown Source)" ], [ "3y", "at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))" ], [ "3z", "at java.lang.reflect.Method.invoke(Method.java(Compiled Code))" ], [ "3aa", "at com.sterlingcommerce.woodstock.translator.rules.ExtendedRuleExecuter.executeRule(ExtendedRuleExecuter.java(Compiled Code))" ], [ "3ab", "at com.sterlingcommerce.woodstock.translator.blockprocessor.BlockSequence.runOnEndExtendedRule(BlockSequence.java(Compiled Code))" ], [ "3ac", "at com.sterlingcommerce.woodstock.translator.blockprocessor.BlockSequence.searchForward(BlockSequence.java(Compiled Code))" ], [ "3ad", "at com.sterlingcommerce.woodstock.translator.blockprocessor.BlockSequence.processFileFormat(BlockSequence.java(Compiled Code))" ], [ "3ae", "at com.sterlingcommerce.woodstock.translator.engine.TranslationEngineImpl.translateInput(TranslationEngineImpl.java(Compiled Code))" ], [ "3af", "at com.sterlingcommerce.woodstock.translator.engine.TranslationEngineImpl.doTranslation(TranslationEngineImpl.java(Compiled Code))" ], [ "3ag", "at com.sterlingcommerce.woodstock.translator.engine.TranslationEngineImpl.translate(TranslationEngineImpl.java(Compiled Code))" ], [ "3ah", "at com.sterlingcommerce.woodstock.translator.engine.TranslationEngine.translate(TranslationEngine.java(Inlined Compiled Code))" ], [ "3ai", "at com.sterlingcommerce.woodstock.services.edi.deenvelopex12.DeenvelopeX12ServiceImpl.processTransactions(DeenvelopeX12ServiceImpl.java(Compiled Code))" ], [ "3aj", "at com.sterlingcommerce.woodstock.services.edi.deenvelopex12.DeenvelopeX12ServiceImpl.processGroups(DeenvelopeX12ServiceImpl.java(Compiled Code))" ], [ "3ak", "at com.sterlingcommerce.woodstock.services.edi.deenvelopex12.DeenvelopeX12ServiceImpl.processData(DeenvelopeX12ServiceImpl.java(Compiled Code))" ], [ "3al", "at com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.invokeService(ActivityEngineHelper.java(Compiled Code))" ], [ "3am", "at com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.nextMainLogic(ActivityEngineHelper.java(Compiled Code))" ], [ "3an", "at com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.next(ActivityEngineHelper.java(Compiled Code))" ], [ "3ao", "at com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.doWork(WorkFlowQueueListener.java(Compiled Code))" ], [ "3ap", "at com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.run(WorkFlowQueueListener.java(Compiled Code))" ], [ "3aq", "at com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.onMessage(WorkFlowQueueListener.java(Compiled Code))" ], [ "3ar", "at com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.onMessage(WorkFlowQueueListener.java(Inlined Compiled Code))" ], [ "3as", "at com.sterlingcommerce.woodstock.workflow.queue.wfTransporter.run(wfTransporter.java(Compiled Code))" ], [ "3at", "at com.sterlingcommerce.woodstock.workflow.queue.BasicExecutor$Worker.run(BasicExecutor.java(Compiled Code))" ], [ "3au", "at java.lang.Thread.run(Thread.java(Compiled Code))" ], [ "3av", "RESOLVING THE PROBLEM" ], [ "3aw", "If GIS is invoked with an automatic scheduler (such as cron or Control-M), the daemons may not be PAM aware, so any changes made to /etc/security/limits.conf are ignored, and the default values for /bin/sh are used." ], [ "3ax", "The most straightforward and least invasive solution is to modify the script being called by the scheduler to start GIS to increase the file descriptor limit by adding the line \"ulimit -n 2048\" (without the quotes)." ], [ "3ay", "See Novell bulletin 3302273 for further detail. HISTORICAL NUMBER NFX5068 PRODUCT ALIAS/SYNONYM Function Area startup Escalation ID 4962281 Severity Normal Type NormalFix" ] ]

[ "2i", "2j", "2k", "2l", "2dn", "2do", "2dq", "2dm", "2ds", "3aw", "3ax" ]

[ "cc; clearcase; download; version; 8.0; clearcase; cte; clearteam explorer extension; cadence extension; ccrc DOWNLOADABLE FILES\n\nABSTRACT\n IBM Rational ClearCase 8.0 has been made generally available on the IBM Passport Advantage Web site. \n\nDOWNLOAD DESCRIPTION\n\n\nTAB NAVIGATION\n * 8.0- selected tab,\n * Fix by Version [http://www.ibm.com/support/docview.wss?uid=swg27023149]\n\n\n\n\nThis release is a full product download. Download the product from Passport Advantage or IBM Software Group OEM Portal. \n\n * Passport Advantage clients: Passport Advantage and Passport Advantage Express clients are required to sign in to Passport Advantage Online [https://www.ibm.com/software/howtobuy/softwareandservices/passportadvantage] to download the image.\n \n \n * Non-Passport Advantage clients: If your organization did not purchase your software and support through Passport Advantage or Passport Advantage Express, you are required to sign in to the new IBM Software Group OEM Portal [https://www.ibm.com/software/howtobuy/softwareandservices/oem] to download the image.\n \n Note: This includes clients with Flexible Contract Type (FCT) license purchases and IBM Business Partners.\n \n For assistance with the IBM Software Group OEM Portal, visit the eCustomer care [https://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html] page.\n \n \n\n\n\n\n * For a detailed list of problems (APARs) solved in each individual Fix Pack version for this product, click the Fix by Version tab above.\n\n\nPREREQUISITES\nIBM Installation Manager 1.4.4 [http://www.ibm.com/support/docview.wss?&uid=swg24029226]. \n\nIf you are installing web-based components of Rational ClearCase, refer to WebSphere Application Server and IBM HTTP Server installation overview [http://publib.boulder.ibm.com/infocenter/cchelp/v8r0m0/index.jsp?topic=/com.ibm.rational.clearcase.cc_ms_install.doc/topics/c_WAS_IHS_ovw.htm] for installation requirements. \n\n\n\nSupporting Documentation Document Description Release information [http://www.ibm.com/support/docview.wss?uid=swg21504789] A description of the new features, known restrictions and links to other important information. Detailed System Requirements [http://www.ibm.com/support/docview.wss?uid=swg27020796] A detailed list of the supported hardware, operating systems and information related to IBM and third party software requirements. Information Center [http://publib.boulder.ibm.com/infocenter/cchelp/v8r0m0/index.jsp] Browse or search on-line information related to the deployment, configuration and usage of the product. \nINSTALLATION INSTRUCTIONS\nInstallation instructions can be found in the Release Notes.\n\nFor installation details on the ClearCase Integration with Cadence refer to technote 1456411 [http://www.ibm.com/support/docview.wss?uid=swg21456411]About the ClearCase integration with Cadence Design Framework II .\n\nRational ClearTeam Explorer can be installed using the IBM Installation Manager.\n\nURL LANGUAGE SIZE(Bytes) Installation instructions [http://publib.boulder.ibm.com/infocenter/cchelp/v8r0m0/nav/1] English 1 Installing Rational ClearTeam Explorer [http://www-01.ibm.com/support/knowledgecenter/SSSH27_8.0.0/com.ibm.rational.clearcase.cc_ms_install.doc/topics/c_inst_ccrc.htm] English 1 \nDOWNLOAD PACKAGE\nClick the link in the tab above to be taken to the Passport Advantage site to obtain the download package.\n\nThe ClearTeam Explorer and Cadence Integration Extensions are available for download on Fix Central [http://www-947.ibm.com/systems/support/fixes/en/fixcentral/help/faq_sw.html]: \n\n \n\nClearTeam Explorer Extension: 8.0.0.0-Rational-RCCRC-EXT-FP00 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm/Rational&product=ibm/Rational/Rational+ClearCase&release=All&platform=All&function=fixId&fixids=8.0.0.0-Rational-RCCRC-EXT-FP00] \n\n\nCadence Integration Extension: 8.0.0.0-Rational-RCC-CADENCE-EXT-FP00 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Rational&product=ibm/Rational/Rational+ClearCase&release=All&platform=All&function=fixId&fixids=8.0.0.0-Rational-RCC-CADENCE-EXT-FP00] \n\n\n\nPROBLEMS SOLVED\n For details on defects resolved in this release, refer to the Fix List [http://www.ibm.com/support/docview.wss?uid=swg27023148] document.\n\n\n\n\n\nTECHNICAL SUPPORT\n \n\nTAB NAVIGATION\n * General Support Information- selected tab,\n * Support Portal [http://www.ibm.com/software/rational/support/]\n * developerWorks [http://www.ibm.com/developerworks/rational/]\n * Jazz Community [http://jazz.net/]\n\n\n\n\nIBM Rational Software Support Communities \n\n * Support Portal: Click the Support Portal tab above to begin configuring your support portal experience to review FAQs, lists of known problems, fixes, and a wealth of important support information. \n * developerWorks: Click the developerWorks tab above 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 * Jazz Community: Click the Jazz Community tab above if you are using one of the Rational tools created using the Jazz platform to interact directly with the Jazz development teams 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", " TECHNOTE (FAQ)\n\nQUESTION\nIs addToKit.exe available for download from IBM Passport Advantage Online [https://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/LoginPage]? \n\nANSWER\n \n\nFor Notes 8.5.1 and higher releases, addToKit.exe is available for download from Passport Advantage. \n\n\n * Download the Notes install webkit from Passport Advantage.\n\n * Run the webkit and choose a temp directory to unpack the files to.\n\n * Cancel the install after the files are unpacked\n\n * Navigate to the temp directory under \\Utility\\NotesCustomizationKit_#_#.zip. You should see addToKit.exe in this directory. \n\n\nPrior to Notes 8.5.1, addToKit.exe is available in the following locations: \n\n\n * The \\Apps folder on the Notes install CD \n\n * Attached to technote #1366669 [http://www.ibm.com/support/docview.wss?uid=swg21366669] - Obtaining Notes 8.5 addToKit.exe and trimUpdateSite.exe tools\n\n\n\n * \n *", " PRODUCT LIFECYCLE\n\nABSTRACT\n IBM is pleased to announce a new support option available to you when your software reaches End of Service (EOS). IBM will offer Continuing Support for select ILG products and releases. This offering will provide you with continued access to the same knowledgeable global Support team you are working with today. \n\nCONTENT\nIBM is pleased to announce a new support option available to you when your software reaches End of Service (EOS). IBM will offer Continuing Support for select ILG products and releases. This offering will provide you with continued access to the same knowledgeable global Support team you are working with today.\n\nWorld-Class Software Support \n\nUnder your IBM Passport Advantage agreement's (International Passport Advantage Agreement or International Passport Advantage Express Agreement) Software Subscription and Support (S&S) terms, you receive comprehensive cross-platform technical assistance from a team of highly skilled Support experts. Additionally, you get flexible upgrade protection, access to the latest software versions and releases, remote technical support, 24x7 support for business-critical outages, online self-help resources, and unlimited electronic and voice access (where available) to world-class global IBM Software Support Centers.\n\nContinuing Support Option\n\nContinuing Support extends support for your software beyond its EOS date. When your software versions reach their End of Service date and support is no longer available through standard Software S&S, you now have the option for Continuing Support and no longer need to tackle support issues on your own. \n\nContinuing Support Program Benefits\n\nThis exciting offering allows you to enjoy many of the S&S benefits that you have told us matter most to you, including:\n\n· 7 days, 24-hour support for mission critical emergencies (Severity 1) \n· Provided by voice in most countries. \n· Provided in English, with the local language accommodated when possible. \n· Remote problem analysis and assistance during normal country business hours in your time zone. \n· Support for routine, short duration installation and usage questions. \n· Response time objective of two hours during prime shift for voice and electronic problem submissions.\n· Response objective for critical/emergency problems during off-shift hours is two hours. \n· Unlimited number of technical support incidents. \n· Access to documentation, technotes and other online product material. \n· Access to existing available fixes created before the product's EOS date to correct known defects.\n\nThe Continuing Support offering does not include:\n\n· Voice and electronic access support for code-related problems. \n· Development analysis of new defects. \n· Development of or packaging fixes that are not already available. \n· Support for Supporting Programs and third party components. \n· Infrastructure that are not included in the software version’s Hardware and Software Requirement page. \n\nProgram Participation\n\nTo receive Continuing Support, you only need to maintain active S&S for licenses deployed for the software. \n\nComplete Coverage for Mission Critical Installations\n\nIn addition to Continuing Support, IBM still provides the option for Service Extension (SE). Customers will have the choice between Continuing Support and Service Extension. For mission critical installations, it is highly recommended that you continue to pro-actively purchase a Service Extension to receive full defect and development support assistance. By adding this offering, you will be maintaining the same full defect support coverage you received before the End of Service date, further protecting your installation. If you require development or defect support assistance after the End of Service for any version, including during the life of Continuing Support or with an active Upgrade Bridge contract, you will be required to purchase a Service Extension at that time at IBM's specified charge in order to receive such support. Contact your IBM sales representative for more information, or to purchase these options.\n\nILG Products and Releases Covered Under Continuing Support Option\n\n\n * Content Classification 8.8.8 and later \n * Content Collector 4.0 and later \n * Content Collector for SAP Applications 4.0 and later \n * Content Integrator 8.6 and later \n * Content Integrator Enterprise Edition 8.6 and later \n * Content Integrator for z/OS 8.6 and later \n * eDiscovery Manager/Analyzer 2.2 and later \n * Enterprise Records 5.1 and later \n * Records Manager 8.5 and later \n * StoredIQ 7.6 and later \n * StoredIQ for Legal 2.0 and later\n\n\nFAQs\n\n1. Why should I take advantage of Continuing Support? \nContinuing Support provides flexibility for you to remain up and running on your software version with non-defect Support until you are able to upgrade to the latest version. Continuing Support provides uninterrupted access to many of the benefits of S&S and is more affordable than other options, such as a Service Extension. \n\n2. What is the cost of Continuing Support and how do I buy it? \nContinuing Support is available when you maintain active S&S. To avoid possible delays in receiving Support, you are encouraged to email [email protected] [[email protected]] or your Sales contact. \n\n3. I am on a software version which is out of support, and would like to benefit from this offering. \nContinuing Support is now available to clients running on select ILG products and releases as noted above. To learn more about Continuing Support for your installations, please contact your local sales representative or email inquiries to [email protected] [[email protected]] \n\n4. Are Limited Availability fix included with Continuing Support? \nContinuing Support assistance provides you with access to pre-existing and available fixes. Limited Availability fix will NOT be created as part of this offering. If a Limited Availability fix is required, you will need first to purchase and sign a contract for a Service Extension. \n\n5. Should I purchase a Service Extension (SE) instead of relying on Continuing Support assistance? \nIf your business requires the same comprehensive full-defect coverage it relied on before the EOS date, you will want to purchase a SE, if available. A SE is recommended for maximum coverage for your mission critical installations. \n\n6. What if I have already purchased a Service Extension (SE) for my software licenses? \nYou can take advantage of Continuing Support upon expiry of your Service Extension. \n\nFor more information \nTo get more information about the Continuing Support offering, email us at [email protected] [[email protected]]", " DOWNLOADABLE FILES\n\nABSTRACT\n This download document contains a complete listing of the software packages needed to upgrade an existing Lotus Sametime Gateway deployment to release 8.5, or install a new Gateway \n\nDOWNLOAD DESCRIPTION\n\n\nLotus® Sametime Gateway 8.5 is a platform that permits a local Sametime Standard 8.5 community to enjoy real-time collaboration with other Sametime communities and public instant messaging services such as AOL and Google Talk. Sametime Gateway replaces and enhances the Sametime SIP Gateway that was provided in Sametime releases prior to release 7.5.0.\n\nWhere can I get Sametime Gateway 8.5?\n\nThe complete Sametime product is available to customers from the IBM Passport Advantage Web site [http://www.ibm.com/software/howtobuy/passportadvantage/]. Locate the part number of your package in the tables below, and download it from Passport Advantage.\n\nFor information on locating and downloading packages in Passport Advantage, see Passport Advantage: How it work [http://www-01.ibm.com/software/passportadvantage/aboutpassport.html]s. [http://www-10.lotus.com/ldd/stwiki.nsf/dx/Using_Passport_Advantage_to_download_IBM_products_st852]If you are unable to locate a package, or experience difficulty downloading packages, contact the Passport Advantage eCustomer Care Team [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html] for assistance.\n\nMore information\n\nTo access a wide variety of technical resources for this product, see the Lotus Documentation page [http://www.ibm.com/developerworks/lotus/] at the IBM developerWorks Lotus web site.\n\nFor additional information, see the Sametime 8.5 \"System Requirements\" technote [http://www.ibm.com/support/docview.wss?rs=477&uid=swg27016451]\n\nDownloading and assembling the product Follow the Sametime Gateway 8.5 installation instructions [http://publib.boulder.ibm.com/infocenter/sametime/v8r5/index.jsp] in the information center.\n\n[http://www.ibm.com/i/c.gif] [http://www.ibm.com/i/c.gif] Downloadable images:\n\n\n\nIBM Lotus Sametime Gateway\n\nCZA6PML\n\nIBM Lotus Sametime Gateway Server 8.5 Windows IBM i Multilingual\n\nCZA6QML\n\nIBM Lotus Sametime Gateway Server 8.5 AIX Linux Solaris Multilingual\n\n\n\nIBM Lotus Sametime Standard 8.5 \n\nNote: For instructions on installing Sametime refer to the Lotus Sametime Standard 8.5 Download Document [http://www.ibm.com/support/docview.wss?rs=477&uid=swg24024322] \n\n\nPREREQUISITES\nPrior to installing the Lotus Sametime Gateway, install Lotus Sametime Standard 8.5\n\nURL LANGUAGE SIZE(Bytes) Lotus Sametime Standard 8.5 Download Document [http://www.ibm.com/support/docview.wss?rs=477&uid=swg24024322] US English 2900 \nINSTALLATION INSTRUCTIONS\n\n\nGeneral installation instructions are provided in the IBM Lotus Sametime 8.5 Quick Start Guide. The guide is available in .PDF format for all supported languages from the Sametime documentation page [http://www.ibm.com/developerworks/lotus/documentation/sametime/] at the IBM developerWorks Lotus web site. \n\nFor additional installation instructions, refer to the Lotus Sametime 8.5 Information Center. [http://publib.boulder.ibm.com/infocenter/sametime/v8r5/index.jsp] URL LANGUAGE SIZE(Bytes) Passport Advantage Online [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm] US English 2900 \n\n\nTECHNICAL SUPPORT\n \n\nPassport Advantage [http://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html]", "integration; hpqc; doors/qc; qci DOWNLOADABLE FILES\n\nABSTRACT\n IBM Rational DOORS for HP Quality Center Interface 3.5.0 has been made generally available on the IBM Passport Advantage Web site. \n\nDOWNLOAD DESCRIPTION\n\n\nTAB NAVIGATION\n * 3.5.0- selected tab,\n * Fix by Version [http://www.ibm.com/support/docview.wss?uid=swg27017121]\n\n\n\n\nThis release is a full product download. \n\n * Passport Advantage clients: Passport Advantage and Passport Advantage Express clients are required to sign in to Passport Advantage Online [https://www.ibm.com/software/howtobuy/softwareandservices/passportadvantage] to download the image.\n \n \n * Non-Passport Advantage clients: If your organization did not purchase your software and support through Passport Advantage or Passport Advantage Express, you are required to sign in to the new IBM Software Group OEM Portal [https://www.ibm.com/software/howtobuy/softwareandservices/oem] to download the image.\n \n Note: This includes clients with Flexible Contract Type (FCT) license purchases and IBM Business Partners.\n \n For assistance with the IBM Software Group OEM Portal, visit the eCustomer care [https://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html] page.\n \n \n\n\n\n\n * For a detailed list of problems (APARs) solved in this Fix Pack, click the Fix List link in the Problems solved section below.\n * For a detailed list of problems (APARs) solved in each individual Fix Pack version for this product, click the Fix by Version tab above.\n\n\nPREREQUISITES\n\n\nSupporting Documentation Document Description Rational DOORS for HP Quality Center Interface readme [http://publib.boulder.ibm.com/infocenter/doorshlp/v9/index.jsp?topic=/com.ibm.doors.install.doc/topics/ratlDOORS_QCI_3-5-0-0_readme.html.] A description of the new features, system requirements, known restrictions and links to other important information. Using Rational DOORS for HP Quality Center Interface [http://publib.boulder.ibm.com/infocenter/doorshlp/v9/index.jsp?topic=/com.ibm.doors.install.doc/topics/Quality_Center_Integration.pdf] Information about concepts and tasks in Rational DOORS for HP Quality Center Interface. INSTALLATION INSTRUCTIONS\nFor information about installing Rational DOORS for HP Quality Center Interface, see the Rational DOORS Information Center [http://publib.boulder.ibm.com/infocenter/doorshlp/v9/index.jsp?topic=/com.ibm.doors.install.doc/topics/c_installingqci.html].\n\nDOWNLOAD PACKAGE\nClick the link in the table below to be taken to the Passport Advantage site to obtain the download package.\n\nPROBLEMS SOLVED\nFor details on defects resolved in this release, refer to the Fix List [http://www.ibm.com/support/docview.wss?uid=swg27021690] document.\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options Passport Advantage 27/05/2011 English 1 HTTP [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm] \nTECHNICAL SUPPORT\n \n\nTAB NAVIGATION\n * General Support Information- selected tab,\n * Support Portal [http://www.ibm.com/software/rational/support/]\n * developerWorks [http://www.ibm.com/developerworks/rational/]\n * Jazz Community [http://jazz.net/]\n\n\n\n\nIBM Rational Software Support Communities \n\n * Support Portal: Click the Support Portal tab above to begin configuring your support portal experience to review FAQs, lists of known problems, fixes, and a wealth of important support information. \n * developerWorks: Click the developerWorks tab above 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 * Jazz Community: Click the Jazz Community tab above if you are using one of the Rational tools created using the Jazz platform to interact directly with the Jazz development teams 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=swg24029915&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24029915&aid=2]Problems (APARS) fixed\nPM01886, PM05355, PK84905, PM31555, PK83262, PM35254" ]

[ [ "0a", "cc; clearcase; download; version; 8.0; clearcase; cte; clearteam explorer extension; cadence extension; ccrc DOWNLOADABLE FILES ABSTRACT" ], [ "0b", " IBM Rational ClearCase 8.0 has been made generally available on the IBM Passport Advantage Web site. DOWNLOAD DESCRIPTION TAB NAVIGATION" ], [ "0c", " * 8.0- selected tab," ], [ "0d", " * Fix by Version [http://www.ibm.com/support/docview.wss?uid=swg27023149]" ], [ "0e", "This release is a full product download." ], [ "0f", "Download the product from Passport Advantage or IBM Software Group OEM Portal." ], [ "0g", " * Passport Advantage clients: Passport Advantage and Passport Advantage Express clients are required to sign in to Passport Advantage Online [https://www.ibm.com/software/howtobuy/softwareandservices/passportadvantage] to download the image." ], [ "0h", " * Non-Passport Advantage clients: If your organization did not purchase your software and support through Passport Advantage or Passport Advantage Express, you are required to sign in to the new IBM Software Group OEM Portal [https://www.ibm.com/software/howtobuy/softwareandservices/oem] to download the image." ], [ "0i", " Note: This includes clients with Flexible Contract Type (FCT) license purchases and IBM Business Partners." ], [ "0j", " For assistance with the IBM Software Group OEM Portal, visit the eCustomer care [https://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html] page." ], [ "0k", " * For a detailed list of problems (APARs) solved in each individual Fix Pack version for this product, click the Fix by Version tab above. PREREQUISITES" ], [ "0l", "IBM Installation Manager 1.4.4 [http://www.ibm.com/support/docview.wss?&uid=swg24029226]." ], [ "0m", "If you are installing web-based components of Rational ClearCase, refer to WebSphere Application Server and IBM HTTP Server installation overview [http://publib.boulder.ibm.com/infocenter/cchelp/v8r0m0/index.jsp?topic=/com.ibm.rational.clearcase.cc_ms_install.doc/topics/c_WAS_IHS_ovw.htm] for installation requirements." ], [ "0n", "Supporting Documentation Document Description Release information [http://www.ibm.com/support/docview.wss?uid=swg21504789] A description of the new features, known restrictions and links to other important information." ], [ "0o", "Detailed System Requirements [http://www.ibm.com/support/docview.wss?uid=swg27020796] A detailed list of the supported hardware, operating systems and information related to IBM and third party software requirements." ], [ "0p", "Information Center [http://publib.boulder.ibm.com/infocenter/cchelp/v8r0m0/index.jsp] Browse or search on-line information related to the deployment, configuration and usage of the product. INSTALLATION INSTRUCTIONS" ], [ "0q", "Installation instructions can be found in the Release Notes." ], [ "0r", "For installation details on the ClearCase Integration with Cadence refer to technote 1456411 [http://www.ibm.com/support/docview.wss?uid=swg21456411]About the ClearCase integration with Cadence Design Framework II ." ], [ "0s", "Rational ClearTeam Explorer can be installed using the IBM Installation Manager." ], [ "0t", "URL LANGUAGE SIZE(Bytes) Installation instructions [http://publib.boulder.ibm.com/infocenter/cchelp/v8r0m0/nav/1] English 1 Installing Rational ClearTeam Explorer [http://www-01.ibm.com/support/knowledgecenter/SSSH27_8.0.0/com.ibm.rational.clearcase.cc_ms_install.doc/topics/c_inst_ccrc.htm] English 1 DOWNLOAD PACKAGE" ], [ "0u", "Click the link in the tab above to be taken to the Passport Advantage site to obtain the download package." ], [ "0v", "The ClearTeam Explorer and Cadence Integration Extensions are available for download on Fix Central [http://www-947.ibm.com/systems/support/fixes/en/fixcentral/help/faq_sw.html]:" ], [ "0w", "ClearTeam Explorer Extension: 8.0.0.0-Rational-RCCRC-EXT-FP00 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm/Rational&product=ibm/Rational/Rational+ClearCase&release=All&platform=All&function=fixId&fixids=8.0.0.0-Rational-RCCRC-EXT-FP00]" ], [ "0x", "Cadence Integration Extension: 8.0.0.0-Rational-RCC-CADENCE-EXT-FP00 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Rational&product=ibm/Rational/Rational+ClearCase&release=All&platform=All&function=fixId&fixids=8.0.0.0-Rational-RCC-CADENCE-EXT-FP00] PROBLEMS SOLVED" ], [ "0y", " For details on defects resolved in this release, refer to the Fix List [http://www.ibm.com/support/docview.wss?uid=swg27023148] document. TECHNICAL SUPPORT TAB NAVIGATION" ], [ "0z", " * General Support Information- selected tab," ], [ "0aa", " * Support Portal [http://www.ibm.com/software/rational/support/]" ], [ "0ab", " * developerWorks [http://www.ibm.com/developerworks/rational/]" ], [ "0ac", " * Jazz Community [http://jazz.net/]" ], [ "0ad", "IBM Rational Software Support Communities" ], [ "0ae", " * Support Portal: Click the Support Portal tab above to begin configuring your support portal experience to review FAQs, lists of known problems, fixes, and a wealth of important support information." ], [ "0af", " * developerWorks: Click the developerWorks tab above 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/]." ], [ "0ag", " * Jazz Community: Click the Jazz Community tab above if you are using one of the Rational tools created using the Jazz platform to interact directly with the Jazz development teams and other community members, download product trials and betas and track developement progress." ], [ "0ah", "HELPFUL HINTS FOR OBTAINING TECHNICAL ASSISTANCE:" ], [ "0ai", "Before you contact IBM Rational Software Support, gather the background information that you need to describe the problem." ], [ "0aj", "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." ], [ "0ak", "To save time, know the answers to these questions:" ], [ "0al", " * What software versions were you running when the problem occurred?" ], [ "0am", " * Do you have logs, traces, or messages that are related to the problem?" ], [ "0an", " * Can you reproduce the problem?" ], [ "0ao", "If so, what steps do you take to reproduce it?" ], [ "0ap", " * Is there a workaround for the problem?" ], [ "0aq", "If so, be prepared to describe the workaround." ], [ "0ar", "If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support [http://www.ibm.com/software/support/exchangeinfo.html]." ], [ "0as", "Follow IBM Rational Client Support on Twitter [http://twitter.com/rationalsupport] | Facebook [http://facebook.com/rationalsupport] | YouTube [http://www.youtube.com/ibmrationalsupport] | devWorks Blog [https://www.ibm.com/developerworks/mydeveloperworks/blogs/nfrsblog/?lang=en]" ], [ "0at", " Back to top" ] ]

[ "0b", "0e", "0f", "0g", "0h", "0v", "0w", "0x" ]

[ " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Information Server Web Console Login problems.\n\nUnable to log in to ISF admin console \n\nSYMPTOM\nVarious errors when attempting login to Information Server Web Console. The directory configuration seems to be correct but you are still not able to login in to ISF admin console.\n\n\nDIAGNOSING THE PROBLEM\nTo debug further, you can turn on debug traces in ASBIdentityLoginModule. From WebSphere administrative console, \n\n 1. Go to Security -> Global security -> JAAS Configuration -> System logins. Click RMI_INBOUND -> JAAS login modules -> com.ascential.acs.security.auth.modules.websphere.ASBIdentityLoginModule -> Custom properties. Click New, and fill the form with Name as debug, Value as true, click OK. \n 2. Go to Security -> Global security -> JAAS Configuration -> System logins. Click WEB_INBOUND -> JAAS login modules -> com.ascential.acs.security.auth.modules.websphere.ASBIdentityLoginModule -> Custom properties. Click New, and fill the form with Name as debug, Value as true, click OK. \n 3. Click Ok, save link in the top screen and then save button to commit the change. \n 4. Restart WAS\n\n\nNow if you make a call to the login method of ISF authentication service from your test clients or you login using ISF admin console, then you see a lot of information like principalid of the user being logged in, user groups, user roles, etc... in the Websphere SystemOut.log. \nRESOLVING THE PROBLEM\nUse SystemOut.log to debug login problem. \n\nUnix/Linux default location for versions 8.0.1 and 8.1:\n/opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/SystemOut.log\n\nWindows default location for versions 8.0.1 and 8.1:\nC:\\IBM\\Websphere\\Application Server\\profiles\\default\\logs\\server1\\SystemOut.log\n\n\nUnix/Linux default location for version 8.5:\n/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1/SystemOut.log\n\nWindows default location for version 8.5:\nC:\\IBM\\WebSphere\\AppServer\\profiles\\InfoSphere\\logs\\server1\\SystemOut.log", "TIPL2; TIPL2LDAP; referrals; CWWIM4520E; DSID-0310063C TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n A subset of LDAP users are unable to log into Tivoli Integrated Portal. The following error is seen in the systemOut.log:\n\n\"...LDAP: error code 10 - 0000202B: RefErr: DSID-0310063C...\" \n\nCAUSE\nThe root LDAP error string (\"DSID-0310063C\" ) can happen in a Multiple Domain LDAP environment where a user account in DomainA contains referral data in DomainB, which is outside of the domain in which the account existed. In this case, the Authentication configuration within the WebSphere application server (WAS) failed to access a user that existed in DomainA, because that user belonged to a group association in DomainB, which was not accessible.\n\nDIAGNOSING THE PROBLEM\nAttempt to log into TIP with a non-working user, and then examine the systemOut log for an instance of the error similar to the following:\n\n###\n[3/21/13 7:31:10:230 EDT] 00000022 exception E com.ibm.ws.wim.adapter.ldap.LdapConnection getAttributes\ncom.ibm.websphere.wim.exception.WIMSystemException: CWWIM4520E The 'javax.naming.PartialResultException: [LDAP: error code 10 - 0000202B: RefErr: DSID-0310063C, data 0, 1 access points\nref 1: 'org.company.com'\n\\u0000]; Remaining name: 'CN=user,OU=accounting,DC=org,DC=company,DC=com'; Resolved object: 'com.sun.jndi.ldap.LdapCtx@3b343b34'' naming exception occurred during processing.\n###\n\nRESOLVING THE PROBLEM\nThe error was addressed by enabling referral following in the Websphere configuration. Here are the steps to change referrals to \"follow\":\n\n1. Log into the WAS Admin Console for TIP. You can launch the WAS Admin Console after logging into TIP, or log into the Admin Console directly using the following instructions:\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21618872 [http://www-01.ibm.com/support/docview.wss?uid=swg21618872]\n2. Once in the WAS Admin Console, go to Security > Global Security, and click the Configure button in the \"Available realm definitions\" section\n\n3. Click on the link for the LDAP server in the \"Repository identifier\" column of the \"Repositories in the realm\" table\n4. Set the \"Support referrals to other LDAP servers \" drop down value to follow, and then click \"Apply\", and then \"Save\".\n5. Log out, and restart TIP\n6. Test the failing logins.", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DOCUMENTATION ERROR.\n \n \n \n\nERROR DESCRIPTION\n * This APAR is a contiinuation of APAR, PM47070 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM47070]. It addresses\n issues that customer encountered with IBM WebSphere Application\n Server Version 7. These issues were resolved as information\n center updates for September, 2011.\n \n \n \n \n \n\nLOCAL FIX\n * N/A\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: This APAR provides a continuation of APAR *\n * PM47070 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM47070], which contains a *\n * cumulative list of the documentation issues *\n * for September, 2011 *\n * that affect users of IBM WebSphere *\n * Application Server Version 7.0. *\n ****************************************************************\n * PROBLEM DESCRIPTION: The Information Centers for WebSphere *\n * Application Server Version 7.0 need *\n * to reflect customer enhancement *\n * requests received in problem *\n * management records (PMRs). These *\n * enhancements can include fixing *\n * technical inaccuracies or clarifying *\n * vague information. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n See the Problem Conclusion section for a description of the\n issues, which are described in customer PMRs, and the\n documentation change or changes that will address these issues.\n Problem Conclusion: Note: We update our information centers\n monthly. The following\n Version 7.0 modifications will be available in September,\n 2011 update to the Information Centers. To access the latest\n on-line documentation, go to the product library page at\n http://www.ibm.com/software/webservers/appserv/library and\n select the version and product that is appropriate for your\n WebSphere Application Server environment.\n The following Version 7.0 issues continue the problem\n descriptions documented in APAR PM47070 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM47070] for WebSphere\n Application Server Version 7.0:\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * ID: 716550\n \n Problem: When using the administrative console to configure\n SPNEGO web authentication, you only need to specify the\n \"LTPA\" option and not the \"LTPA and Kerberos\" option on the\n administrative console. Also, after a realm change in\n federated repositories, the administrative console\n administrative users and group need to re-map existing\n user/role assignments using the configuration panel of the\n administrative console. The WebSphere Application Server\n information center Version 7 does not describe this process.\n Mistakes in configuring SPNEGO web authentication can result.\n \n \n Resolution: Topic, &#162;&#226;&#130;&#172; &#147;SPNEGO troubleshooting tips &#162;&#226;&#130;&#172; &#189; is\n adding a new section, &#162;&#226;&#130;&#172; &#147;Correcting realm change issues and\n subsequent SPNEGO logon failures &#162;&#226;&#130;&#172; &#189;, which reads as follows\n \n Correcting realm change issues and subsequent SPNEGO logon\n failures In a SPNEGO web authentication environment in which a\n realm change is to occur, errors can occur in making the realm\n change, which then can lead to subsequent SPNEGO logon\n failures. Here are the steps to correct these errors.\n \n Realm Change: The realm can consist of identities in the\n file-based repository that is built into the system, in one or\n more external repositories, or in both the built-in,\n file-based repository and one or more external repositories.\n You can change realms in a SPNEGO environment by changing the\n name as follows:\n 1. In the administrative console, click Security > Global\n security > Kerberos configuration > SPNEGO Web authentication\n and uncheck the Enable SPNEGO checkbox.\n 2 .In the administrative console, click Security > Global\n security.\n 3. Under User account repository, select Federated\n repositories from the Available realm definitions field and\n click Configure.\n 4. When you finish adding or updating your federated\n repository configuration, go to the Security > Global security\n panel and click Apply to validate the changes.\n 5. If you have removed a user/role identity and want it to\n function successfully under the new realm, you must add it\n back to the new realm after the realm name change.\n 6. Restart the deployment manager to ensure that these the\n user/role identity can function under the new realm.\n SPNEGO Web authentication: To ensure that the user/role\n changes can successfully logon under this new realm, perform\n the following:\n 1 .Ensure that the application server is running.\n 2 .In the administrative console, click Security > Global\n security\n 3. Under Authentication, highlight the radio button for LTPA.\n Note: The Kerberos and LTPA option is not be selectable unless\n you have configured Kerberos prior to this step. For SPNEGO,\n you ONLY need to use the LTPA option.\n 4. Click Apply. Users under the new realm can now SPNEGO logon.\n \n This same information will be added to the Version 8\n Information Center.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM49209\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE APP S\n \n \n * REPORTED COMPONENT ID\n 5724J0800\n \n \n * REPORTED RELEASE\n 700\n \n \n * STATUS\n CLOSED DOC\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 2011-10-03\n \n \n * CLOSED DATE\n 2011-10-04\n \n \n * LAST MODIFIED DATE\n 2011-10-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\nAPPLICABLE COMPONENT LEVELS", "ldap; websphere; exclude; bpm; configure; security repository TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When you attempt to start IBM Business Process Manager, it does not start properly and the CWWIM4538E error message is logged. \n\nSYMPTOM\nYou might see either or both of the following exceptions in the SystemOut during the start of IBM Business Process Manager: \n\nCWWIM4538E Multiple principals were found for the 'admin' principal name.\n\nCWSIA0004E: The authentication for the supplied user name admin and \nthe associated password was not successful\n\nThe CWWIM4538E message occurs when a user exists in more than one security provider. The CWSIA0004E message can occur when a the system user or administrator attempts to login and start the IBM Business Process Manager system. With multiple users present, IBM Business Process Manager cannot start properly.\n\n\nCAUSE\nIBM Business Process Manager ships with default internal users. These users might also be present in the LDAP system. If an overlap of users happens, IBM Business Process Manager cannot start properly and the CWWIM4538E error message is logged.\n\nIn WebSphere Application Server, each security user must be unique across all the federated repositories. This uniqueness requirement includes file based, LDAP, and custom security providers. For example, the user \"admin\" can only be in one of the configured repositories.\n\n\nRESOLVING THE PROBLEM\nThe connected LDAP repositories share one or more of the default users for IBM Business Process Manager. The following list contains the default users for each major IBM Business Process Manager product level: \n\n * IBM Business Process Manager 7.5: tw_admin, tw_author, tw_user, tw_webservice, tw_portal_admin, tw_runtime_server, bpmAuthor, admin \n * IBM Business Process Manager 8.0: tw_admin, tw_author, tw_user, tw_webservice, tw_portal_admin, tw_runtime_server, bpmAuthor, admin \n * IBM Business Process Manager 8.5: bpmadmin and deadmin (these are user defined and may be different)\n\n\nTo resolve this conflict, use a filter in the WebSphere security repository to exclude a user or group from the LDAP search. Complete the following steps:\n\n\n 1. Backup your WebSphere configuration before starting. The three files that are used in the configuration are security.xml, wimconfig.xml, and fileRegistry.xml. Make safe backups of these files and the deployment manager (DMGR) and other named profiles before beginning. \n 2. Login to the WebSphere Administrative console.The default URL and port is http://server_name:9060/ibm/console\n \n \n 3. Click Security > Global Security.\n \n \n 4. Click Federated Repositories.\n \n \n 5. Click the name of the configured LDAP provider. The following screen capture shows the LDAP configuration pages:\n \n \n [/support/docview.wss?uid=swg21674850&aid=1] [/support/docview.wss?uid=swg21674850&aid=1]\n \n \n 6. Under Additional Properties, click LDAP entity types as shown in the previous screen shot. When you click the link, the next page, which is the LDAP entity types page, shows where you can apply the filters.\n \n \n 7. Click PersonAccount as shown in the following screen shot:\n \n \n [/support/docview.wss?uid=swg21674850&aid=2] [/support/docview.wss?uid=swg21674850&aid=2]\n \n \n 8. In the search filter, place the name of the user or users to exclude from the LDAP search. The following screen shot shows the user \"admin\" being removed from search. Here 'cn' stands for common name. Consult with the LDAP configuration as the LDAP property to filter on might be different in the configuration for your provider. The rest of the search base is the location in the LDAP tree to start excluding users. \n \n \n [/support/docview.wss?uid=swg21674850&aid=3] [/support/docview.wss?uid=swg21674850&aid=3]\n \n \n 9. Click OK and click Save to Configuration.\n \n \n 10. Stop the IBM Business Process Manager servers, if they are running.\n \n \n 11. Stop the node agent. \n \n \n 12. Restart the node agent.\n \n \n 13. Verify in the WebSphere users and groups section of the WebSphere Administrative Console that the user is no longer visible.\n \n \n 14. Start the IBM Business Process Manager servers.\n\n\n\nThe same method applies to groups and organizational units.\n\nRELATED INFORMATION\n Configuring external security providers BPM v8.0 [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.0.0/com.ibm.wbpm.admin.doc/adminguide/topic/managing_users_extsecprov.html]\nConfigure LDAP with WebSphere Lombardi Edition [http://www.ibm.com/developerworks/websphere/bpmjournal/1106_yang/1106_yang.html]\nMaxResultsExceededException occurs during LDAP repos [http://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.wim.doc/maxresultsexceededexceptionoccursduringldaprepositorysearch.html]\nA MaxResultsExceededException: CWWIM1018E when using IB [https://developer.ibm.com/answers/questions/171644/a-maxresultsexceededexception-cwwim1018e-exception.html]\nServer startup issue with large LDAP [http://www.ibm.com/support/docview.wss?uid=swg21594714]\n\n\n \n\nPRODUCT ALIAS/SYNONYM\n BPM", " 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" ]

[ [ "3a", "ldap; websphere; exclude; bpm; configure; security repository TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "3b", " When you attempt to start IBM Business Process Manager, it does not start properly and the CWWIM4538E error message is logged. SYMPTOM" ], [ "3c", "You might see either or both of the following exceptions in the SystemOut during the start of IBM Business Process Manager:" ], [ "3d", "CWWIM4538E Multiple principals were found for the 'admin' principal name." ], [ "3e", "CWSIA0004E: The authentication for the supplied user name admin and" ], [ "3f", "the associated password was not successful" ], [ "3g", "The CWWIM4538E message occurs when a user exists in more than one security provider." ], [ "3h", "The CWSIA0004E message can occur when a the system user or administrator attempts to login and start the IBM Business Process Manager system." ], [ "3i", "With multiple users present, IBM Business Process Manager cannot start properly. CAUSE" ], [ "3j", "IBM Business Process Manager ships with default internal users." ], [ "3k", "These users might also be present in the LDAP system." ], [ "3l", "If an overlap of users happens, IBM Business Process Manager cannot start properly and the CWWIM4538E error message is logged." ], [ "3m", "In WebSphere Application Server, each security user must be unique across all the federated repositories." ], [ "3n", "This uniqueness requirement includes file based, LDAP, and custom security providers." ], [ "3o", "For example, the user \"admin\" can only be in one of the configured repositories." ], [ "3p", "RESOLVING THE PROBLEM" ], [ "3q", "The connected LDAP repositories share one or more of the default users for IBM Business Process Manager." ], [ "3r", "The following list contains the default users for each major IBM Business Process Manager product level:" ], [ "3s", " * IBM Business Process Manager 7.5: tw_admin, tw_author, tw_user, tw_webservice, tw_portal_admin, tw_runtime_server, bpmAuthor, admin" ], [ "3t", " * IBM Business Process Manager 8.0: tw_admin, tw_author, tw_user, tw_webservice, tw_portal_admin, tw_runtime_server, bpmAuthor, admin" ], [ "3u", " * IBM Business Process Manager 8.5: bpmadmin and deadmin (these are user defined and may be different)" ], [ "3v", "To resolve this conflict, use a filter in the WebSphere security repository to exclude a user or group from the LDAP search." ], [ "3w", "Complete the following steps: 1." ], [ "3x", "Backup your WebSphere configuration before starting." ], [ "3y", "The three files that are used in the configuration are security.xml, wimconfig.xml, and fileRegistry.xml." ], [ "3z", "Make safe backups of these files and the deployment manager (DMGR) and other named profiles before beginning. 2." ], [ "3aa", "Login to the WebSphere Administrative console.The default URL and port is http://server_name:9060/ibm/console 3." ], [ "3ab", "Click Security > Global Security. 4." ], [ "3ac", "Click Federated Repositories. 5." ], [ "3ad", "Click the name of the configured LDAP provider." ], [ "3ae", "The following screen capture shows the LDAP configuration pages:" ], [ "3af", " [/support/docview.wss?uid=swg21674850&aid=1] [/support/docview.wss?uid=swg21674850&aid=1] 6." ], [ "3ag", "Under Additional Properties, click LDAP entity types as shown in the previous screen shot." ], [ "3ah", "When you click the link, the next page, which is the LDAP entity types page, shows where you can apply the filters. 7." ], [ "3ai", "Click PersonAccount as shown in the following screen shot:" ], [ "3aj", " [/support/docview.wss?uid=swg21674850&aid=2] [/support/docview.wss?uid=swg21674850&aid=2] 8." ], [ "3ak", "In the search filter, place the name of the user or users to exclude from the LDAP search." ], [ "3al", "The following screen shot shows the user \"admin\" being removed from search." ], [ "3am", "Here 'cn' stands for common name." ], [ "3an", "Consult with the LDAP configuration as the LDAP property to filter on might be different in the configuration for your provider." ], [ "3ao", "The rest of the search base is the location in the LDAP tree to start excluding users." ], [ "3ap", " [/support/docview.wss?uid=swg21674850&aid=3] [/support/docview.wss?uid=swg21674850&aid=3] 9." ], [ "3aq", "Click OK and click Save to Configuration. 10." ], [ "3ar", "Stop the IBM Business Process Manager servers, if they are running. 11." ], [ "3as", "Stop the node agent. 12." ], [ "3at", "Restart the node agent. 13." ], [ "3au", "Verify in the WebSphere users and groups section of the WebSphere Administrative Console that the user is no longer visible. 14." ], [ "3av", "Start the IBM Business Process Manager servers." ], [ "3aw", "The same method applies to groups and organizational units. RELATED INFORMATION" ], [ "3ax", " Configuring external security providers BPM v8.0 [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.0.0/com.ibm.wbpm.admin.doc/adminguide/topic/managing_users_extsecprov.html]" ], [ "3ay", "Configure LDAP with WebSphere Lombardi Edition [http://www.ibm.com/developerworks/websphere/bpmjournal/1106_yang/1106_yang.html]" ], [ "3az", "MaxResultsExceededException occurs during LDAP repos [http://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.wim.doc/maxresultsexceededexceptionoccursduringldaprepositorysearch.html]" ], [ "3ba", "A MaxResultsExceededException: CWWIM1018E when using IB [https://developer.ibm.com/answers/questions/171644/a-maxresultsexceededexception-cwwim1018e-exception.html]" ], [ "3bb", "Server startup issue with large LDAP [http://www.ibm.com/support/docview.wss?uid=swg21594714] PRODUCT ALIAS/SYNONYM BPM" ] ]

[ "3b", "3d", "3e", "3g", "3i", "3j", "3l", "3m", "3n", "3o", "3p", "3q", "3v", "3w", "3x", "3y", "3ab", "3ac", "3ad", "3ae", "3ak", "3al", "3am", "3an", "3ap", "3aq", "3as", "3at", "3au" ]

[ "Impact 6.1; installation; Netcool/Impact; IMPACT6.1.0.0_install-00.log; failed; javasharedresources TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The IMPACT6.1.0.0_install-00.log shows the installer doesn't make it past step_00009, and will not properly start WAS server, which is needed to continue the installation process. \n\nSYMPTOM\nInstallation log doesn't get past this step: \n\n \"step_00009_IAGLOBAL_COI_STEP_StartWAS_ImpactProfile_eWAS_NameServer\", and WAS will not start. \n\n\nRESOLVING THE PROBLEM\nThe /tmp/javasharedresources/ directory had these permissions \"drwxrwxr-x\", but those needed be changed to \"drwxrwxrwx\", so that their non-root, which they're attempting to install Impact as, has proper access to write to this directory.", "ICO lockdown SCO IWDeployer temp jav TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n On Central Server 2, 3 and 4 for IBM SmartCloud Orchestrator, the /tmp/javasharedresources directory has 777 permissions, which is a potential security exposure. \n\nDIAGNOSING THE PROBLEM\nWhen you run the ls -al /tmp/javasharedresources command, you see the following directory permissions:\ndrwxrwxrwx 2 root root\n\nRESOLVING THE PROBLEM\nCentral Server 3\n\n\nOn Central Server 3, the Java™ cache is updated with 777 permissions each time the IBM Workload Deployer service is started. Use the sticky bit to change the permissions on the Java cache directory to a more secure 1777. To make this change, complete the following steps: \n\n 1. Open the /etc/init.d/iwd file and locate the following line: \n 172 \"touch /var/lock/subsys/$prog\"\n \n \n 2. Add the following line after the line that was mentioned in the previous step: \n chmod 1777 /tmp/javasharedresources\n\n\nCentral Server 2 and 4 \n\nOn Central Servers 2 and 4, Java runs under WebSphere Application Server. You can resolve the issue with the Java cache directory permissions by adding the following generic Java virtual machine argument to the servers: \n-Xshareclasses:none \n\n \n\nAfter you configure the argument and you restart WebSphere Application Server, the /temp/javasharedresources directory is not used. You can delete the directory on these two systems.The directory should not be automatically recreated after it has been deleted. \n\n \n\nThe generic JVM arguments are used to configure and adjust how the JVM functions. After the changes are made and applied, the server.xml file, which is the master configuration file, is updated. When the JVM is restarted, the new argument takes affect.\n\nUse the following steps to set the generic JVM arguments in the Administration Console for WebSphere Application Server on Central Server 2 and Central Server 4: \n\n * Application Server 1. Expand Servers > Server Type and click WebSphere application servers. \n 2. Click the name of your server. \n 3. Expand Java and Process Management and select Process Definition. \n 4. Under Additional Properties, click Java Virtual Machine. \n 5. Scroll down and locate the text box for Generic JVM arguments.\n \n \n * Node agent 1. Select System Administration > Node Agents. \n 2. Choose which node agent to edit. \n 3. Under Server Infrastructure, expand Java and Process Management and select Process Definition. \n 4. Under Additional Properties, click Java Virtual Machine. \n 5. Scroll down and locate the text box for Generic JVM arguments.\n \n \n * Deployment Manager 1. Select System Administration > Deployment manager. \n 2. Under Server Infrastructure, expand Java and Process Management and select Process Definition. \n 3. Under Additional Properties, click Java Virtual Machine. \n 4. Scroll down and locate the text box for Generic JVM arguments.", "peformance cache streams TECHNOTE (FAQ)\n\nQUESTION\n Why do you see a performance degredation with streamtool commands after a Streams upgrade? \n\nCAUSE\nThe java class cache is filled with old class files from the old product location, so new classes don't get cached\n\nANSWER\nIn order to populate the cache with the new classes you need to clear the java class cache. To do this perform the steps below. \n\n 1. List the class caches on each node with\n $java -Xshareclasses:listAllCaches\n Note the names of the caches that begin with com.ibm.streams \n 2. Clear each of the streams java class caches on each node with\n $ java -Xshareclasses:name=<cache_name>,destroy\n\n\nThis is done on all nodes. It can be done while streams is started but the new cleared cache won't be used until the process restarts, for example, new streamtool executions. It is not required to restart streams as the performance issue is only on process start. \n\nBelow is an example: \n\n$ java -Xshareclasses:listAllCaches \n\nListing all caches in cacheDir /tmp/javasharedresources/ \n\nCache name level cache-type feature OS shmid OS semid last detach time \n\nCompatible shared caches \ncom.ibm.streams.streamtool_jane Java8 64-bit persistent default Thu May 18 16:45:53 2017 \ncom.ibm.streams_jane Java8 64-bit persistent default Thu May 25 16:38:07 2017 \nsharedcc_jane Java8 64-bit persistent default Thu May 25 16:38:23 2017 \n\nIncompatible shared caches \nsharedcc_jane Java8 64-bit persistent mt In use \ncom.ibm.streams_jane Java8 64-bit persistent mt In use \ncom.ibm.streams.streamtool_jane Java8 64-bit persistent mt Thu May 18 16:01:59 2017 \n\n$ java -Xshareclasses:name=com.ibm.streams_jane,destroy \nJVMSHRC256I Persistent shared cache \"com.ibm.streams_jane\" has been destroyed \n$ java -Xshareclasses:name=com.ibm.streams.streamtool_jane,destroy \nJVMSHRC256I Persistent shared cache \"com.ibm.streams.streamtool_jane\" has been destroyed \n\nNote: Starting with IBM Streams version 4.2.1.0 , the streams java class cache will be cleared automatically on host controller startup, so this manual step is not necessary. RELATED INFORMATION\n java -Xshareclasses documentation [https://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.lnx.80.doc/diag/appendixes/cmdline/Xshareclasses.html]", "ITDS; TDS; IBM Tivoli Directory Server; thread dump; core file; hung server; hang; crash; dumpthreads TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n If the ITDS server appears hung or has generated a core file, it is important to collect a thread dump in order to identify the reason for the hang or crash condition. \n\nRESOLVING THE PROBLEM\n\nPurpose: Gather ibmslapd (or any) processes thread stacks. Usually used when the ibmslapd server process is hung but it can also be used for other processes as well. \n\nRequirements: \n\n * \n * \n * ulimit -c unlimited for the process we are collecting the thread dump for \n * The dumpthreads.sh script should be copied to the system and must have execute permission.\n\n\nUsage: dumpthreads.sh [ PID | program corefile ] \n\nTo verify you have the bos.adt.debug installed on your system, issue the following command: \n\n# lslpp -l | grep bos.adt.debug\n\n**Note: if this package is not installed, you can install from the AIX operating system media.\n\n\n1) To get a thread dump from a hung server: \n\nIn the case of a hung process, you will want to collect multiple thread dumps in succession. Typically 2-3 thread dumps about a minute apart is helpful. This will show whether or not the processes' threads are truly hung or if there is progress being made. \n\n1.1) Find the process ID (PID) of the ibmslapd server \n\nFrom a command prompt, type: \n\n# ps -ef | grep slapd \n\n**Note: if you are trying to collect a thread dump from a process other than ibmslapd, you will need to grep for that process. \n\n \n\n1.2) Collect the thread dump \n\nFrom a command prompt, invoke the dumpthreads.sh script with the process ID. \n\n# <path>/dumpthreads.sh PID > /tmp/threaddump1.out \n\nwhere PID is the process ID obtained in step 1.1 \n\ne.g.: Assuming dumpthreads.sh is in /tmp folder \n\n# /tmp/dumpthreads.sh 12345 > /tmp/threaddump1.out \n\nRepeat the above command multiple times at one minute intervals redirecting the output into different files. \n\n \n\n2) To get a thread dump from a core file: \n\nUnlike a process hang condition as described above, collecting a thread dump from a core file is a single collection. From the thread dump we are trying to identify the signature of the core file so that we can attempt to identify root cause. \n\nUsage: \n\n# <path>/dumpthreads.sh PROGRAM CORE > /tmp/threaddump.out \n\nwhere PROGRAM is the fully qualified path to the ibmslapd executable or the executable which generated the core, \n\nand CORE is the generated core file. \n\nibmslapd executable PROGRAM locations: \n\nITDS 6.3: /opt/IBM/ldap/V6.3/sbin/64/ibmslapd\nITDS 6.2: /opt/IBM/ldap/V6.2/sbin/64/ibmslapd\nITDS 6.1: /opt/IBM/ldap/V6.1/sbin/64/ibmslapd\nITDS 6.0: /opt/IBM/ldap/V6.0/sbin/64/ibmslapd\nITDS 5.2: /usr/ldap/bin/ibmslapd \n\nOther Examples of executable program locations: \n\nITDS 6.3: /opt/IBM/ldap/V6.3/sbin/64/bulkload\nITDS 6.2: /opt/IBM/ldap/V6.2/sbin/64/ldif2db\nITDS 6.1: /opt/IBM/ldap/V6.1/sbin/64/db2ldif\nITDS 6.0: /opt/IBM/ldap/V6.0/sbin/64/bulkload \n\nCORE file locations: \n\nITDS 6.x: <Location>/idsslapd-<instanceName>/workdir/\nITDS 5.2: Location from where ibmslapd process is started. \n\nVerify the the program which generated the CORE:\n# file core\ncore: AIX core file fulldump 64-bit, ibmslapd \n\nRun the dumpthreads script to collect the threads dump into a file:\ne.g.: Assuming the dumpthreads.sh is kept in /tmp \n\n# cd <path_where_core_file_is_present> \n\n# /tmp/dumpthreads.sh /opt/IBM/ldap/V6.3/sbin/64/ibmslapd core > /tmp/threaddump.out \n\nNote: if you have restarted ibmslapd then the core file will be renamed to something like core._2011-11-22-12_12_06. Use this file name in place of core when extracting thread dumps.\n\ndumpthreads.sh -> dumpthreads.sh [/support/docview.wss?uid=swg21268413&aid=2]dumpthreads.sh [/support/docview.wss?uid=swg21268413&aid=1]", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Error Message: ICH408I USER(U2) GROUP(G1 )\n NAME(####################)\n /tmp/javasharedresources/C290M4F1A64_memory_XYZU1_G35\n CL(FSOBJ ) FID(0000000000000000000000F500000000)\n \n INSUFFICIENT AUTHORITY TO OPEN\n \n ACCESS INTENT(RW-) ACCESS ALLOWED(OTHER R--)\n \n EFFECTIVE UID(2016814008) EFFECTIVE GID(0001326978)\n .\n Stack Trace: N/A\n .\n Running with the -Xtrace:print=j9prt.700 option will generate\n the following trace message:\n 17:34:48.972*0x2814ce00 j9prt.700 -\n ControlFileFDWithWriteLock (Info: could not chown file.)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * An incorrect call by the jvm while setting the group owner of\n the shared cache control files causes the group owner id to take\n a default value. Due to this, other users belonging to the same\n group as the creator are not able to access the cache, even when\n the groupaccess subparameter has been specified along with the\n -Xshareclasses option.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The jvm has been changed to correctly set the group owner of the\n shared cache control files to the group of the cache creator.\n .\n This APAR will be fixed in the following Java Releases:\n 8 SR5 FP10 (8.0.5.10)\n .\n Contact your IBM Product's Service Team for these Service\n Refreshes and Fix Packs.\n For those running stand-alone, information about the available\n Service Refreshes and Fix Packs can be found at:\n https://www.ibm.com/developerworks/java/jdk/ [https://www.ibm.com/developerworks/java/jdk/]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IJ03852\n \n \n * REPORTED COMPONENT NAME\n J9 COMMON CODE\n \n \n * REPORTED COMPONENT ID\n 620700127\n \n \n * REPORTED RELEASE\n 270\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 2018-02-01\n \n \n * CLOSED DATE\n 2018-02-01\n \n \n * LAST MODIFIED DATE\n 2018-06-05\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 J9 COMMON CODE\n \n \n * FIXED COMPONENT ID\n 620700127\n \n \n\nAPPLICABLE COMPONENT LEVELS" ]

[ [ "0a", "Impact 6.1; installation; Netcool/Impact; IMPACT6.1.0.0_install-00.log; failed; javasharedresources TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "0b", " The IMPACT6.1.0.0_install-00.log shows the installer doesn't make it past step_00009, and will not properly start WAS server, which is needed to continue the installation process. SYMPTOM" ], [ "0c", "Installation log doesn't get past this step:" ], [ "0d", " \"step_00009_IAGLOBAL_COI_STEP_StartWAS_ImpactProfile_eWAS_NameServer\", and WAS will not start." ], [ "0e", "RESOLVING THE PROBLEM" ], [ "0f", "The /tmp/javasharedresources/ directory had these permissions \"drwxrwxr-x\", but those needed be changed to \"drwxrwxrwx\", so that their non-root, which they're attempting to install Impact as, has proper access to write to this directory." ] ]

[ "0a", "0b", "0c", "0d", "0e", "0f", "1b", "1d", "1e", "1i", "1n" ]

[ "Impact 6.1; installation; Netcool/Impact; IMPACT6.1.0.0_install-00.log; failed; javasharedresources TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The IMPACT6.1.0.0_install-00.log shows the installer doesn't make it past step_00009, and will not properly start WAS server, which is needed to continue the installation process. \n\nSYMPTOM\nInstallation log doesn't get past this step: \n\n \"step_00009_IAGLOBAL_COI_STEP_StartWAS_ImpactProfile_eWAS_NameServer\", and WAS will not start. \n\n\nRESOLVING THE PROBLEM\nThe /tmp/javasharedresources/ directory had these permissions \"drwxrwxr-x\", but those needed be changed to \"drwxrwxrwx\", so that their non-root, which they're attempting to install Impact as, has proper access to write to this directory.", "ICO lockdown SCO IWDeployer temp jav TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n On Central Server 2, 3 and 4 for IBM SmartCloud Orchestrator, the /tmp/javasharedresources directory has 777 permissions, which is a potential security exposure. \n\nDIAGNOSING THE PROBLEM\nWhen you run the ls -al /tmp/javasharedresources command, you see the following directory permissions:\ndrwxrwxrwx 2 root root\n\nRESOLVING THE PROBLEM\nCentral Server 3\n\n\nOn Central Server 3, the Java™ cache is updated with 777 permissions each time the IBM Workload Deployer service is started. Use the sticky bit to change the permissions on the Java cache directory to a more secure 1777. To make this change, complete the following steps: \n\n 1. Open the /etc/init.d/iwd file and locate the following line: \n 172 \"touch /var/lock/subsys/$prog\"\n \n \n 2. Add the following line after the line that was mentioned in the previous step: \n chmod 1777 /tmp/javasharedresources\n\n\nCentral Server 2 and 4 \n\nOn Central Servers 2 and 4, Java runs under WebSphere Application Server. You can resolve the issue with the Java cache directory permissions by adding the following generic Java virtual machine argument to the servers: \n-Xshareclasses:none \n\n \n\nAfter you configure the argument and you restart WebSphere Application Server, the /temp/javasharedresources directory is not used. You can delete the directory on these two systems.The directory should not be automatically recreated after it has been deleted. \n\n \n\nThe generic JVM arguments are used to configure and adjust how the JVM functions. After the changes are made and applied, the server.xml file, which is the master configuration file, is updated. When the JVM is restarted, the new argument takes affect.\n\nUse the following steps to set the generic JVM arguments in the Administration Console for WebSphere Application Server on Central Server 2 and Central Server 4: \n\n * Application Server 1. Expand Servers > Server Type and click WebSphere application servers. \n 2. Click the name of your server. \n 3. Expand Java and Process Management and select Process Definition. \n 4. Under Additional Properties, click Java Virtual Machine. \n 5. Scroll down and locate the text box for Generic JVM arguments.\n \n \n * Node agent 1. Select System Administration > Node Agents. \n 2. Choose which node agent to edit. \n 3. Under Server Infrastructure, expand Java and Process Management and select Process Definition. \n 4. Under Additional Properties, click Java Virtual Machine. \n 5. Scroll down and locate the text box for Generic JVM arguments.\n \n \n * Deployment Manager 1. Select System Administration > Deployment manager. \n 2. Under Server Infrastructure, expand Java and Process Management and select Process Definition. \n 3. Under Additional Properties, click Java Virtual Machine. \n 4. Scroll down and locate the text box for Generic JVM arguments.", "peformance cache streams TECHNOTE (FAQ)\n\nQUESTION\n Why do you see a performance degredation with streamtool commands after a Streams upgrade? \n\nCAUSE\nThe java class cache is filled with old class files from the old product location, so new classes don't get cached\n\nANSWER\nIn order to populate the cache with the new classes you need to clear the java class cache. To do this perform the steps below. \n\n 1. List the class caches on each node with\n $java -Xshareclasses:listAllCaches\n Note the names of the caches that begin with com.ibm.streams \n 2. Clear each of the streams java class caches on each node with\n $ java -Xshareclasses:name=<cache_name>,destroy\n\n\nThis is done on all nodes. It can be done while streams is started but the new cleared cache won't be used until the process restarts, for example, new streamtool executions. It is not required to restart streams as the performance issue is only on process start. \n\nBelow is an example: \n\n$ java -Xshareclasses:listAllCaches \n\nListing all caches in cacheDir /tmp/javasharedresources/ \n\nCache name level cache-type feature OS shmid OS semid last detach time \n\nCompatible shared caches \ncom.ibm.streams.streamtool_jane Java8 64-bit persistent default Thu May 18 16:45:53 2017 \ncom.ibm.streams_jane Java8 64-bit persistent default Thu May 25 16:38:07 2017 \nsharedcc_jane Java8 64-bit persistent default Thu May 25 16:38:23 2017 \n\nIncompatible shared caches \nsharedcc_jane Java8 64-bit persistent mt In use \ncom.ibm.streams_jane Java8 64-bit persistent mt In use \ncom.ibm.streams.streamtool_jane Java8 64-bit persistent mt Thu May 18 16:01:59 2017 \n\n$ java -Xshareclasses:name=com.ibm.streams_jane,destroy \nJVMSHRC256I Persistent shared cache \"com.ibm.streams_jane\" has been destroyed \n$ java -Xshareclasses:name=com.ibm.streams.streamtool_jane,destroy \nJVMSHRC256I Persistent shared cache \"com.ibm.streams.streamtool_jane\" has been destroyed \n\nNote: Starting with IBM Streams version 4.2.1.0 , the streams java class cache will be cleared automatically on host controller startup, so this manual step is not necessary. RELATED INFORMATION\n java -Xshareclasses documentation [https://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.lnx.80.doc/diag/appendixes/cmdline/Xshareclasses.html]", "ITDS; TDS; IBM Tivoli Directory Server; thread dump; core file; hung server; hang; crash; dumpthreads TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n If the ITDS server appears hung or has generated a core file, it is important to collect a thread dump in order to identify the reason for the hang or crash condition. \n\nRESOLVING THE PROBLEM\n\nPurpose: Gather ibmslapd (or any) processes thread stacks. Usually used when the ibmslapd server process is hung but it can also be used for other processes as well. \n\nRequirements: \n\n * \n * \n * ulimit -c unlimited for the process we are collecting the thread dump for \n * The dumpthreads.sh script should be copied to the system and must have execute permission.\n\n\nUsage: dumpthreads.sh [ PID | program corefile ] \n\nTo verify you have the bos.adt.debug installed on your system, issue the following command: \n\n# lslpp -l | grep bos.adt.debug\n\n**Note: if this package is not installed, you can install from the AIX operating system media.\n\n\n1) To get a thread dump from a hung server: \n\nIn the case of a hung process, you will want to collect multiple thread dumps in succession. Typically 2-3 thread dumps about a minute apart is helpful. This will show whether or not the processes' threads are truly hung or if there is progress being made. \n\n1.1) Find the process ID (PID) of the ibmslapd server \n\nFrom a command prompt, type: \n\n# ps -ef | grep slapd \n\n**Note: if you are trying to collect a thread dump from a process other than ibmslapd, you will need to grep for that process. \n\n \n\n1.2) Collect the thread dump \n\nFrom a command prompt, invoke the dumpthreads.sh script with the process ID. \n\n# <path>/dumpthreads.sh PID > /tmp/threaddump1.out \n\nwhere PID is the process ID obtained in step 1.1 \n\ne.g.: Assuming dumpthreads.sh is in /tmp folder \n\n# /tmp/dumpthreads.sh 12345 > /tmp/threaddump1.out \n\nRepeat the above command multiple times at one minute intervals redirecting the output into different files. \n\n \n\n2) To get a thread dump from a core file: \n\nUnlike a process hang condition as described above, collecting a thread dump from a core file is a single collection. From the thread dump we are trying to identify the signature of the core file so that we can attempt to identify root cause. \n\nUsage: \n\n# <path>/dumpthreads.sh PROGRAM CORE > /tmp/threaddump.out \n\nwhere PROGRAM is the fully qualified path to the ibmslapd executable or the executable which generated the core, \n\nand CORE is the generated core file. \n\nibmslapd executable PROGRAM locations: \n\nITDS 6.3: /opt/IBM/ldap/V6.3/sbin/64/ibmslapd\nITDS 6.2: /opt/IBM/ldap/V6.2/sbin/64/ibmslapd\nITDS 6.1: /opt/IBM/ldap/V6.1/sbin/64/ibmslapd\nITDS 6.0: /opt/IBM/ldap/V6.0/sbin/64/ibmslapd\nITDS 5.2: /usr/ldap/bin/ibmslapd \n\nOther Examples of executable program locations: \n\nITDS 6.3: /opt/IBM/ldap/V6.3/sbin/64/bulkload\nITDS 6.2: /opt/IBM/ldap/V6.2/sbin/64/ldif2db\nITDS 6.1: /opt/IBM/ldap/V6.1/sbin/64/db2ldif\nITDS 6.0: /opt/IBM/ldap/V6.0/sbin/64/bulkload \n\nCORE file locations: \n\nITDS 6.x: <Location>/idsslapd-<instanceName>/workdir/\nITDS 5.2: Location from where ibmslapd process is started. \n\nVerify the the program which generated the CORE:\n# file core\ncore: AIX core file fulldump 64-bit, ibmslapd \n\nRun the dumpthreads script to collect the threads dump into a file:\ne.g.: Assuming the dumpthreads.sh is kept in /tmp \n\n# cd <path_where_core_file_is_present> \n\n# /tmp/dumpthreads.sh /opt/IBM/ldap/V6.3/sbin/64/ibmslapd core > /tmp/threaddump.out \n\nNote: if you have restarted ibmslapd then the core file will be renamed to something like core._2011-11-22-12_12_06. Use this file name in place of core when extracting thread dumps.\n\ndumpthreads.sh -> dumpthreads.sh [/support/docview.wss?uid=swg21268413&aid=2]dumpthreads.sh [/support/docview.wss?uid=swg21268413&aid=1]", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Error Message: ICH408I USER(U2) GROUP(G1 )\n NAME(####################)\n /tmp/javasharedresources/C290M4F1A64_memory_XYZU1_G35\n CL(FSOBJ ) FID(0000000000000000000000F500000000)\n \n INSUFFICIENT AUTHORITY TO OPEN\n \n ACCESS INTENT(RW-) ACCESS ALLOWED(OTHER R--)\n \n EFFECTIVE UID(2016814008) EFFECTIVE GID(0001326978)\n .\n Stack Trace: N/A\n .\n Running with the -Xtrace:print=j9prt.700 option will generate\n the following trace message:\n 17:34:48.972*0x2814ce00 j9prt.700 -\n ControlFileFDWithWriteLock (Info: could not chown file.)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * An incorrect call by the jvm while setting the group owner of\n the shared cache control files causes the group owner id to take\n a default value. Due to this, other users belonging to the same\n group as the creator are not able to access the cache, even when\n the groupaccess subparameter has been specified along with the\n -Xshareclasses option.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The jvm has been changed to correctly set the group owner of the\n shared cache control files to the group of the cache creator.\n .\n This APAR will be fixed in the following Java Releases:\n 8 SR5 FP10 (8.0.5.10)\n .\n Contact your IBM Product's Service Team for these Service\n Refreshes and Fix Packs.\n For those running stand-alone, information about the available\n Service Refreshes and Fix Packs can be found at:\n https://www.ibm.com/developerworks/java/jdk/ [https://www.ibm.com/developerworks/java/jdk/]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IJ03852\n \n \n * REPORTED COMPONENT NAME\n J9 COMMON CODE\n \n \n * REPORTED COMPONENT ID\n 620700127\n \n \n * REPORTED RELEASE\n 270\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 2018-02-01\n \n \n * CLOSED DATE\n 2018-02-01\n \n \n * LAST MODIFIED DATE\n 2018-06-05\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 J9 COMMON CODE\n \n \n * FIXED COMPONENT ID\n 620700127\n \n \n\nAPPLICABLE COMPONENT LEVELS" ]

[ [ "1a", "ICO lockdown SCO IWDeployer temp jav TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "1b", " On Central Server 2, 3 and 4 for IBM SmartCloud Orchestrator, the /tmp/javasharedresources directory has 777 permissions, which is a potential security exposure." ], [ "1c", "DIAGNOSING THE PROBLEM" ], [ "1d", "When you run the ls -al /tmp/javasharedresources command, you see the following directory permissions:" ], [ "1e", "drwxrwxrwx 2 root root" ], [ "1f", "RESOLVING THE PROBLEM" ], [ "1g", "Central Server 3" ], [ "1h", "On Central Server 3, the Java™ cache is updated with 777 permissions each time the IBM Workload Deployer service is started." ], [ "1i", "Use the sticky bit to change the permissions on the Java cache directory to a more secure 1777." ], [ "1j", "To make this change, complete the following steps: 1." ], [ "1k", "Open the /etc/init.d/iwd file and locate the following line:" ], [ "1l", " 172 \"touch /var/lock/subsys/$prog\" 2." ], [ "1m", "Add the following line after the line that was mentioned in the previous step:" ], [ "1n", " chmod 1777 /tmp/javasharedresources" ], [ "1o", "Central Server 2 and 4" ], [ "1p", "On Central Servers 2 and 4, Java runs under WebSphere Application Server." ], [ "1q", "You can resolve the issue with the Java cache directory permissions by adding the following generic Java virtual machine argument to the servers: -Xshareclasses:none" ], [ "1r", "After you configure the argument and you restart WebSphere Application Server, the /temp/javasharedresources directory is not used." ], [ "1s", "You can delete the directory on these two systems.The directory should not be automatically recreated after it has been deleted." ], [ "1t", "The generic JVM arguments are used to configure and adjust how the JVM functions." ], [ "1u", "After the changes are made and applied, the server.xml file, which is the master configuration file, is updated." ], [ "1v", "When the JVM is restarted, the new argument takes affect." ], [ "1w", "Use the following steps to set the generic JVM arguments in the Administration Console for WebSphere Application Server on Central Server 2 and Central Server 4:" ], [ "1x", " * Application Server 1." ], [ "1y", "Expand Servers > Server Type and click WebSphere application servers." ], [ "1z", " 2." ], [ "1aa", "Click the name of your server." ], [ "1ab", " 3." ], [ "1ac", "Expand Java and Process Management and select Process Definition." ], [ "1ad", " 4." ], [ "1ae", "Under Additional Properties, click Java Virtual Machine." ], [ "1af", " 5." ], [ "1ag", "Scroll down and locate the text box for Generic JVM arguments." ], [ "1ah", " * Node agent 1." ], [ "1ai", "Select System Administration > Node Agents." ], [ "1aj", " 2." ], [ "1ak", "Choose which node agent to edit." ], [ "1al", " 3." ], [ "1am", "Under Server Infrastructure, expand Java and Process Management and select Process Definition." ], [ "1an", " 4." ], [ "1ao", "Under Additional Properties, click Java Virtual Machine." ], [ "1ap", " 5." ], [ "1aq", "Scroll down and locate the text box for Generic JVM arguments." ], [ "1ar", " * Deployment Manager 1." ], [ "1as", "Select System Administration > Deployment manager." ], [ "1at", " 2." ], [ "1au", "Under Server Infrastructure, expand Java and Process Management and select Process Definition." ], [ "1av", " 3." ], [ "1aw", "Under Additional Properties, click Java Virtual Machine." ], [ "1ax", " 4." ], [ "1ay", "Scroll down and locate the text box for Generic JVM arguments." ] ]

[ "0a", "0b", "0c", "0d", "0e", "0f", "1b", "1d", "1e", "1i", "1n" ]

[ " NEWS\n\nABSTRACT\n IBM API Connect V5.0.6.2 is available, which addresses several APARs, and includes product enhancements. \n\nCONTENT\n\n\nIBM API Connect V5.0.6.2 is now available, which provides important development and APAR fixes, and includes product enhancements as well as a more consistent user experience. \n\nWe advise all users of IBM API Connect V5.0 to install this update to take advantage of the fixes. \n\n\nSUPPORT LIFECYCLE POLICY FOR IBM API CONNECT VERSION 5.0.6.X:\nIBM API Connect Version 5.0.6.x is a Maintenance Support Release and provides predictable support through regular, cumulative, in-place iFixes for a minimum period of two years. \n\nA Maintenance Support Release is a recommended product level for which support, including defect and security updates, will be provided over a specified period of time. A Maintenance Support Release is intended for customers that may need a longer term deployment for their environment. \n\n\nAPAR FIXES\nTHE FOLLOWING APARS WERE ADDRESSED BY IBM API CONNECT V5.0.6.2, ALONG WITH OTHER INTERNALLY RAISED QUALITY FIXES:\nAPAR Summary LI79354 API CONNECT: MANAGEMENT SERVER DISK FULL DUE TO /WIP AND/OR /IH_VAR BEING PUT ON ROOTFS INSTEAD OF SEPARATE MOUNT POINTS LI79496 API CONNECT: UNABLE TO FIND DEFINITION TYPE FOR SOAP HEADER LI79495 ERRORS REPORTED IN GATEWAY LOG BY MOBILEFIRST CODE LI79494 SPECIAL CHARACTERS IN GATEWAY PASSWORD MAY CAUSE APIS TO THROW 404 ERRORS LI79434 LOGSTASH ENCOUNTERED OOM CONDITION WHEN PAYLOAD ANALYTICS LOGGING IS USED TO LOG VERY LARGE PAYLOADS. LI79518 UPGRADE DEVELOPER PORTAL FROM APIM V4042 TO APIC V5061 FAILED WITH ERROR: ACCESS DENIED FOR USER 'ADMIN'@'LOCALHOST' LI79526 UNEXPECTED RESTART OF COLLECTIVE CONTROLLER MAY OCCUR LI79525 CONTENTS CONFIDENTIAL LI79524 TOO MANY CRON JOB IS SET TO DEFAULT LI79522 THE PARSING OF PARAM VALUES CONTAINING \"%25\" AND \"=\" REGRESSED IN V5061 FROM 5020 LI79523 A HTTP 204 RESPONSE CODE MAY NOT BE PROCESSED CORRECTLY WHEN USING AN INVOKE POLICY LI79519 API MANAGEMENT V5.0 ON IBM API MANAGEMENT CONNECT THE LB-HEALTH-CHECK REST CALL SOMETIMES RETURNS FALSE NEGATIVES LI79517 SETTING A CACHE-KEY OF AN EMPTY STRING DISABLES CACHING LI79515 MAP FAILS WITH A HTTP 500 WHEN REQUEST PARAMETERS ARE SPECIFIED LI79485 CALL AN API WITH A PATCH HTTP METHOD. OUR BACKEND FAILS BECAUSE TO ACCEPT THE PATCH METHOD. LI79510 MAP POLICY IS NOT MAPPING XSI:NIL=\"TRUE\" TO EMPTY STRING IN APIC V5. IT WAS WORKING IN APIM V4 LI79508 XML-TO-JSON POLICY ON API CONNECT MAY THROW ERROR WHEN BACKSLASH EXISTS IN XML DATA \n\nFUNCTIONAL CHANGES\nIn gateway responses, non-ASCII characters (above U+007f) in XML bodies are no longer converted to numeric character references. \n\nUPGRADE PATHS FOR API CONNECT:\nFor more information of details on IBM API Connect upgrade paths, see Supported Upgrade Paths. [http://www-01.ibm.com/support/docview.wss?uid=swg21984408] \n\nThere are specific validated upgrade paths between IBM® API Management Version 4.0 or later and IBM API Connect Version 5.0 or later. For more information, see Validated upgrade paths for API Connect [http://www.ibm.com/support/knowledgecenter/SSMNED_5.0.0/com.ibm.apic.overview.doc/overview_apic_upgrade_path.html] \n\nIn addition to the specific validated upgrade paths for the API Management appliance, you must upgrade your IBM DataPower Gateway appliance. For more information, see Upgrading DataPower for Gateway servers [http://www.ibm.com/support/knowledgecenter/SSMNED_5.0.0/com.ibm.apic.overview.doc/apply_main_gateway.html?lang=en-us]. \n\nUpgrading the gateway to firmware level 7.5.0.1 is strongly recommended for the best experience. \n\n\n\nDOWNLOADS:\n Full installation and upgrade files for IBM API Connect Version 5.0.6.2 (Enterprise, Professional & Essentials) can be downloaded from Fix Central: IBM API Connect Version 5.0.6.2 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.2&platform=All&function=all] \n\nEnsure that you have read and understood the above Important installation instructions before downloading and using the installation or upgrade files.\n\n\n\nWhat is Fix Central (FC)? [http://www.ibm.com/systems/support/fixes/en/fixcentral/help/faq_sw.html]", " NEWS\n\nABSTRACT\n WebSphere DataPower SOA Appliances firmware version 6.0.1 is now available for download on the following appliances: \n\nWebSphere DataPower B2B Appliance XB62\nWebSphere DataPower Integration Appliance XI52\nWebSphere DataPower Integration Appliance XI52 Virtual Edition\nWebSphere DataPower Integration Blade XI50B\nWebSphere DataPower Service Gateway XG45\nWebSphere DataPower Service Gateway XG45 Virtual Edition \n\nCONTENT\nRefer to the following documents for details about firmware version 6.0.1 now available: \n\n * WebSphere DataPower firmware V6.0.1 announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/897/ENUS213-584/index.html&lang=en&request_locale=en] \n\nRefer to the Release Notes [http://www-304.ibm.com/support/docview.wss?uid=swg27040581] for details on the Authorized Program Analysis Reports (APARs) included in this version. See also: * [http://www.ibm.com/support/docview.wss?rs=2362&uid=swg24014405]Link to the Fix Central site [http://www.ibm.com/support/fixcentral/]to begin the download process. \n * New to Fix Central? If so, see Fix download method for WebSphere DataPower SOA Appliances. [http://www.ibm.com/support/docview.wss?uid=swg21376557] \n * IBM WebSphere DataPower Appliance Support Lifecycle [http://www.ibm.com/support/docview.wss?uid=swg21246298] for reference\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower Integration Appliance XI52 Not Applicable Firmware 6.0.1.0 Edition Independent Business Integration WebSphere DataPower B2B Appliance XB62 Not Applicable Firmware 6.0.1.0 Edition Independent Business Integration WebSphere DataPower Service Gateway XG45 Not Applicable Firmware 6.0.1.0 Edition Independent Business Integration WebSphere DataPower Integration Blade XI50B Not Applicable Firmware 6.0.0 Edition Independent", " FIXES ARE AVAILABLE\nFix packs for DataPower XML Security Gateway version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034955]\nFix packs for DataPower B2B Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034956]\nFix packs for DataPower Integration Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034957]\nFix packs for DataPower Low Latency Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034958]\nFix packs for DataPower Service Gateway version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034959]\nFix packs for DataPower Service Gateway version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036407]\nFix packs for DataPower B2B Appliance version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036409]\nFix packs for DataPower Integration Appliance version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036410]\nFix packs for DataPower Service Gateway version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037486]\nFix packs for DataPower B2B Appliance version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037487]\nFix packs for DataPower Integration Appliance version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037488]\nFix packs for DataPower Gateway version 7.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24038524]\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 * When IMS backend server sends null response to DataPower via IMS\n Connect DataPower might time out.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * Affected are Datapower configurations using IMS Connect.\n \n A message shorter than expected received from the backend is\n ignored and ultimately times out.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Fix is available in 6.0.0.14, 6.0.1.10, 7.0.0.7 and 7.1.0.5.\n \n For a list of the latest fix packs available, please see:\n http://www-01.ibm.com/support/docview.wss?uid=swg21237631 [http://www-01.ibm.com/support/docview.wss?uid=swg21237631]\n \n \n \n \n \n\nTEMPORARY FIX\n * (none)\n \n \n \n \n \n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT06484\n \n \n * REPORTED COMPONENT NAME\n DATAPOWER\n \n \n * REPORTED COMPONENT ID\n DP1234567\n \n \n * REPORTED RELEASE\n 600\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-01-14\n \n \n * CLOSED DATE\n 2015-04-08\n \n \n * LAST MODIFIED DATE\n 2015-05-04\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 DATAPOWER\n \n \n * FIXED COMPONENT ID\n DP1234567\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R600 PSN\n UP\n \n \n * R601 PSN\n UP\n \n \n * R700 PSN\n UP\n \n \n * R710 PSN\n UP", "Forward Proxy XMLFW MPGW CONNECT TUNNEL TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n How to configure an IBM WebSphere DataPower SOA Appliance Service to proxy an SSL request to a remote proxy server using the CONNECT method for SSL tunneling? \n\nCAUSE\nMany common forward proxy servers expect requests in different formats depending on if they are proxying non-SSL or SSL requests.\n\nFor example, a non-SSL request to be proxied may come in the form of GET hostname:port/URI.\n\nFor SSL requests to be proxied, remote proxy servers are commonly configured to tunnel the request from the client to the backend server.\n\nIn the SSL request scenario, remote proxy servers will typically expect a CONNECT request and then tunnel the SSL request from the client to the backend server.\n\nUsers configuring DataPower may need a way to implement this CONNECT method for SSL tunneling to a remote Proxy Server.\n\n\n\n\nRESOLVING THE PROBLEM\nNon-SSL Proxy requests will work using either:\n\na) an XML Firewall when configuring in the HTTP Options tab, where the user can configure the Proxy Host and Port\n\nb) a Multi-Protocol Gateway when configuring an HTTP Proxy Policy in the User Agent\n\nSSL Proxy requests will work using the CONNECT method for SSL Tunneling when using a Multi-Protocol Gateway when configuring in a User Agent's HTTP Proxy Policy.\n\nThe XML Firewall service is not designed to use the CONNECT method for SSL Tunneling.", " FIXES ARE AVAILABLE\nFix packs for DataPower XML Security Gateway version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034955]\nFix packs for DataPower B2B Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034956]\nFix packs for DataPower Integration Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034957]\nFix packs for DataPower Low Latency Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034958]\nFix packs for DataPower Service Gateway version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034959]\nFix packs for DataPower Service Gateway version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036407]\nFix packs for DataPower B2B Appliance version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036409]\nFix packs for DataPower Integration Appliance version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036410]\nFix packs for DataPower Service Gateway version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037486]\nFix packs for DataPower B2B Appliance version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037487]\nFix packs for DataPower Integration Appliance version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037488]\nFix packs for DataPower Gateway version 7.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24038524]\nFix packs for DataPower Gateway version 7.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24039783]\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 * DataPower mq-qm object fails to connect with qmgr using SSL\n after firmware upgrade\n \n \n \n \n \n\nLOCAL FIX\n * Disable SSL.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Customer who uses secure connection with the new firmware\n cannot\n create MQ connections with MQ error code 2538 in the system log\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Fix is available in 6.0.0.17, 6.0.1.13, 7.0.0.10, 7.1.0.7 and\n 7.2.0.2\n \n For a list of the latest fix packs available, please see:\n http://www-01.ibm.com/support/docview.wss?uid=swg21237631 [http://www-01.ibm.com/support/docview.wss?uid=swg21237631]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT11147\n \n \n * REPORTED COMPONENT NAME\n DTAPWR B2B APL\n \n \n * REPORTED COMPONENT ID\n DP905XB62\n \n \n * REPORTED RELEASE\n 710\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-09-09\n \n \n * CLOSED DATE\n 2015-10-18\n \n \n * LAST MODIFIED DATE\n 2015-11-06\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 DTAPWR B2B APL\n \n \n * FIXED COMPONENT ID\n DP905XB62\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R600 PSY\n UP\n \n \n * R601 PSY\n UP\n \n \n * R700 PSY\n UP\n \n \n * R710 PSY\n UP\n \n \n * R720 PSY\n UP" ]

[ [ "3a", "Forward Proxy XMLFW MPGW CONNECT TUNNEL TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "3b", " 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? CAUSE" ], [ "3c", "Many common forward proxy servers expect requests in different formats depending on if they are proxying non-SSL or SSL requests." ], [ "3d", "For example, a non-SSL request to be proxied may come in the form of GET hostname:port/URI." ], [ "3e", "For SSL requests to be proxied, remote proxy servers are commonly configured to tunnel the request from the client to the backend server." ], [ "3f", "In 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." ], [ "3g", "Users configuring DataPower may need a way to implement this CONNECT method for SSL tunneling to a remote Proxy Server." ], [ "3h", "RESOLVING THE PROBLEM" ], [ "3i", "Non-SSL Proxy requests will work using either:" ], [ "3j", "a) an XML Firewall when configuring in the HTTP Options tab, where the user can configure the Proxy Host and Port" ], [ "3k", "b) a Multi-Protocol Gateway when configuring an HTTP Proxy Policy in the User Agent" ], [ "3l", "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." ], [ "3m", "The XML Firewall service is not designed to use the CONNECT method for SSL Tunneling." ] ]

[ "3b", "3e", "3f", "3g", "3l", "3m" ]

[ " A FIX IS AVAILABLE\nITCAM for WebSphere 6.1, Fixpack 4, 6.1.0-TIV-ITCAMfWAS_MP-FP0004 [http://www-01.ibm.com/support/docview.wss?uid=swg24021856]\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 * Configuring multiple jvms either through GUI or silent install\n appends\n multiple jvm names to GC_LOG_PATH. Here is a short description:\n Since the dcInputs.txt file is both input to and output from the\n config\n tool, there are some interesting effects. I ran a config with\n just\n three JVMs, but the gc log file string was still very long.\n I figured that the config tool was reading the GC_LOG_PATH from\n dcInputs.txt, and just keeping it. I tried manually removing\n this line\n from dcInputs.txt, and it after running config_dc, it put the\n entry\n back in there again. including more than just the three JVMs I\n configured, but less than the 19 that were already configured:\n GC_LOG_PATH=${LOG_ROOT}/pin_01_native_stderr.mbr_utilities_01.mk\n tgrt_01.\n low_impact_01.life_01.imco_invest_01.imco_01.gen_utilities_01.\n ent_logon_emp_01.ent_logon_01.ent_home_01.ent_common_01.ent_acco\n unts_01.\n log\n Configured JVMS were pin_01, mbr_utilities_01, mktgrt_01,\n low_impact_01, life_01, imco_invest_01, imco_01,\n gen_utilities_01,\n ent_logon_emp_01, ent_logon_01, ent_home_01, ent_common_01,\n ent_accounts_01, bkoffice_01, ent_services_01, crm56_svcs_01,\n ent_edd_01, bk_preapps_01, rip_01\n \n \n \n \n \n\nLOCAL FIX\n * Hotfix created.\n \n Note\n \n 1. The hotfix contain a README file and config_DC.jar which need\n to be\n used to replace the existing FP3_iFix2 version of config_DC.jar\n \n 2. The hotfix contain the code fix for the problem that GC log\n file name\n will be appended with server name even if user do not choose the\n GC log\n redirect check box during DC configuration.\n \n 3. The GC log settings exist in the generic JVM arguments before\n the DC\n configure will not be removed by configurator by design as\n configurator\n will take it as the customer customized option.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * CONFIGURING MULTIPLE JVMS EITHER THROUGH GUI OR SILENT INSTALL\n APPENDS MULTIPLE JVM NAMES TO GC_LOG_PATH\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * This is fixed by FP4\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PK60498\n \n \n * REPORTED COMPONENT NAME\n ITCAM WAS DIST\n \n \n * REPORTED COMPONENT ID\n 5724L6200\n \n \n * REPORTED RELEASE\n 610\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 2008-02-05\n \n \n * CLOSED DATE\n 2008-03-31\n \n \n * LAST MODIFIED DATE\n 2008-04-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 ITCAM WAS DIST\n \n \n * FIXED COMPONENT ID\n 5724L6200\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R610 PSY\n UP", "-XX:+PrintGCDateStamps; PrintGCDateStamps; date; stamps; verbosegc; oracle; solaris TECHNOTE (FAQ)\n\nQUESTION\n Can you have a verbose GC log with date and time format on an Oracle JVM? \n\nANSWER\nYes. You can do that by using -XX:+PrintGCDateStamps option which is introduced in Oracle Java 6 and later versions. You can use this option for IBM WebSphere Application Server (WSAS) 7.0 and later versions on Solaris and HP-UX platform. \nHow to use it:\nBy adding -XX:+PrintGCDateStamps option into generic JVM arguments and enabling verbose garbage collection (verbosegc) from the WSAS administrative console. \n\nSetting generic JVM arguments in WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21417365]\nEnabling verbose garbage collection (verbosegc) in WebSphere Application Server [http://www.ibm.com/support/docview.wss?uid=swg21114927]\n\n\n\nHow it works:\nBy the -XX:+PrintGCDateStamps option, Oracle JVM records each verbosegc cycle with new date and timestamp format into the native_stdout.log files by default. For example:\n\n2013-02-18T20:09:34.265+0900: [GC [DefNew: 89K->0K(4992K), 0.0004644 secs][Tenured: 7956K->143K(10944K), 0.0175816 secs] 8045K->143K(15936K), [Perm : 1801K->1801K(12288K)], 0.0181751 secs] [Times: user=0.02 sys=0.00, real=0.02 secs] \n\n\n\nHow to analyze the verbosegc logs:\nYou can use GCMV or PMAT for the analysis.\n\nVersion 2.7 of \"IBM Monitoring and Diagnostic Tools for Java - Garbage Collection and Memory Visualizer (GCMV)\" supports verbosegc logs from -XX:+PrintGCDateStamps option.\n\nUpdate: Garbage Collection and Memory Visualizer (GCMV) 2.7 for IBM Support Assistant [http://www.ibm.com/support/docview.wss?uid=swg21625005]\n\nVersion 4.4.1 of \"IBM Pattern Modeling and Analysis Tool for Java Garbage Collector (PMAT)\" is also supports this date and timestamp format for the analysis.\n\nIBM Pattern Modeling and Analysis Tool for Java Garbage Collector [http://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=22d56091-3a7b-4497-b36e-634b51838e11]", "mustgather; MustGather; AIX; 100% cpu; cpu; high cpu; ce; wasce; community edition; MustGatherDocument; WAS CE; WAS CE; WAS CE; WASCE; WASCE; WASCE; JBoss; JBoss; JBoss; Glassfish; Glassfish; Glassfish; App Server; App Server; WebSphere CE; WebSphere CE; WebSphere CE; WebSphere Community Edition; WebSphere Community Edition; WebSphere Community Edition; IBM CE; IBM CE; IBM CE; Open Source; Open Source; Open Source TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Collecting data for problems with WebSphere Application Server Community Edition 100% CPU on the AIX operating system. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save your time. \n\nRESOLVING THE PROBLEM\nThis document details the MustGather data to be collected for WebSphere Application Server Community Edition when 100% CPU usage is observed with IBM Java 1.5 or IBM Java 1.6 on the AIX operating system. \n\n\nSetup for 100% CPU on AIX\nThe first section of the document covers the necessary setup required prior to collection of the MustGather. The latter part covers the MustGather collection steps.\n\nEnsure javacore.txt generation is enabled\nThe Javadump (javacore) is a useful file to provide information about the general state of the Java runtime, and the applications running on it. In order to ensure this is generated, the relevant settings must be in place. Although they are set by default, it is possible that the default setting has been changed, so it is important to check that the correct settings are in place.\n\nCheck that the JVM is set to produce a javadump file when a user signal (SIGQUIT) occurs, by adding the following command line option: \n\n\n\njava -Xdump:what \nThe preceding command shows the options which are set, such as: \n\ndumpFn=doJavaDump\nevents=gpf+user+abort \nfilter=\nlabel=/usr/local/jdk/jre/bin/javacore.%Y%m%d.%H%M%S.%pid.txt\nrange=1..0\npriority=10\nrequest=exclusive \nThe preceding values are the default settings. At least events=user must be in place to generate javadumps on a user signal. \n\nOptions can be changed and set using the command line option: \n\n-Xdump:java[:=,...] \nSo, for example, to set the ability to generate javadump files on user signals you would use: \n\n-Xdump:java:events=user \n\nEnable verbose GC logging \nVerbose GC logging gives an insight into the actions that the Garbage Collector is taking. This allows an application to be monitored and better tuned for performance, in addition to being vital for diagnosing problems. \n\nVerbose GC logging is not enabled by default, and can be done by 1 of the following ways: * Enabling the generation of Verbose GC logging is done to direct the Verbose GC logging output to a single file using the following command line option:\n \n -Xverbosegclog:[DIR_PATH][FILE_NAME] \n Where: [DIR_PATH] is the directory where the file should be written [FILE_NAME] is the name of the file to write the logging to \n For example, \n java -Xverbosegclog:/tmp/verbose_output.xml \n Note: Ensure that the directory provided in [DIR_PATH] exists in the file system. \n \n * The logging can also be done in a circular fashion to a series of files, this is carried out using the following command line option:\n \n -Xverbosegclog:[DIR_PATH][FILE_NAME],X,Y \n Where: [DIR_PATH] is the directory where the file should be written [FILE_NAME] is the name of the file to write the logging to X is the number of files to write to Y is the number of GC cycles a file should contain \n The parameter needs to be set in the setenv.sh file located under the following directory: \n <WAS CE Installation Directory>/bin \n Edit the setenv.sh file, then locate \"JAVA_OPTS=\" line and append the parameter to the existing list.\n \n For example: \n JAVA_OPTS=-Xms128m -Xmx512m -Xverbosegclog:/tmp/verbose-ouput.xml \n \n \n\nEnable process size monitoring, CPU profiling and paging usage * Monitoring the process size\n Follow the Process Size Monitoring for IBM Java technote [http://www.ibm.com/support/docview.wss?uid=swg21222446] and collect the process size monitoring logs.\n \n \n * Monitor the CPU Profiling\n Profiling the CPU usage on AIX can be achieved using the tprof utility, as carried out with the following command: \n \n ./tprof_ps.sh tprof_ps \n Which uses the following script: \n #! /bin/ksh\n TPROF_LOG=$1\n \n mkdir $TPROF_LOG\n cd $TPROF_LOG\n tprof -skex sleep 60\n ps avwwwg > ps-w-tprof.log\n \n cd ..\n \n \n * Monitoring the paging usage\n Monitoring the paging usage on AIX can be achieved using the vmstat utility, as carried out with the following command:\n \n ./vmstat.sh vmstat.log \n Which uses the following script: \n #!/bin/ksh\n #log file name\n VMSTAT_LOG=$1\n # Adjust LIMIT & SLEEP_TIME to suite your purpose/need.\n # There Lre 288- 5 minute intervals in a day\n LIMIT=288\n #sleep for 5 minutes\n SLEEP_TIME=300\n while true\n do\n i=0\n echo >$VMSTAT_LOG\n while [ $i -le \"$LIMIT\" ];\n do\n date >> $VMSTAT_LOG;\n vmstat 5 12 >> $VMSTAT_LOG;\n i=`expr $i + 1`;\n sleep $SLEEP_TIME;\n done\n done \n Where: LIMIT is the number of log cycles before the log file rolls over SLEEP_TIME is the amount of time between each log cycle \n \n \n\nMustGather collection \nHaving ensured that AIX is properly setup for MustGather collection, follow these steps to collect the data files: 1. Take a snapshot of the network activity using the following command:\n \n netstat -an netstat_before.out \n \n 2. Run CPU Profiling for the current CPU activity\n \n \n 3. Take a listing of the current processes:\n \n ps -efHm > ps_efhm.txt \n Note: If you face problems with the preceding command, try to run the following in succession: \n ps -efm > ps_efm.txt\n ps -efH > ps_efh.txt \n \n 4. Generate 3 javacore.txt files, taken 2 minutes apart from the time of 100% CPU usage using kill command as shown below:\n \n kill -3 [PID_of_server_JVM] \n \n 5. Take a second snapshot of network activity:\n \n netstat -an netstat_after.out \n \n 6. Collect the verbose GC output.\n \n \n 7. Collect the CPU monitoring output.\n \n \n 8. Collect the process size monitoring.\n \n \n 9. Collect the paging size usage monitoring.\n \n \n\nAdditional Information * Recent changes to the server before the 100% CPU usage\n \n \n * Brief description of the applications running while 100% CPU usage\n \n \n * Collect general information of the server as discussed here [http://www.ibm.com/support/docview.wss?uid=swg21231419#generalMustGather]\n\n\nThese data files should then be submitted to IBM Support as given at the bottom of this technote. \n\nTip to save you time: If you open and update your PMRs electronically, using Service Request [http://www.ibm.com/software/support/probsub.html] [http://www.ibm.com/software/support/probsub.html], update the PMR to indicate that data has been sent.", "verbosegc log rotation HP Solaris JVM rotate file TECHNOTE (FAQ)\n\nQUESTION\n How can I write verbose gc output to a log file other than the native_stdout? \n\nCAUSE\nBy default, Solaris and HP-UX do not write verbose GC to a log file. This must be configured.\n\nANSWER\n \n\nWAS 8.5.0.2 (and higher), WAS 8.0.0.6 (and higher), WAS 7.0.0.27 (and higher):\n\nSolaris:\nAdd the following parameters to the generic JVM arguments:\n\n-XX:+PrintGCDetails \n-XX:+PrintGCDateStamps \n-XX:+PrintHeapAtGC \n-Xloggc:/tmp/gc.log\n\nTo enable log file rotation:\n-XX:+UseGCLogFileRotation\n-XX:NumberOfGCLogFiles=10\n-XX:GCLogFileSize=10M\n\n\nnotes:\n-Xloggc:<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]", "MustGatherDocument; mustgather; mustgather; mustgather; Read first; readfirst; must gather; component; troubleshooting; trouble shooting; TopTenDocument; MustGatherReadFirstDocument; Performance; Slow; Debug TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Collect troubleshooting data for memory related issues for InfoSphere Master Data Management (MDM) Standard Edition (SE) or Advanced Edition (AE). Gathering this information before calling IBM support will help familiarize you with the troubleshooting process, save you time and improve time to resolution. \n\nRESOLVING THE PROBLEM\n\n\nPurpose of this document: To provide instructions for data collection during a performance test for InfoSphere MDM. Collecting data for Out of Memory errors with IBM InfoSphere Master Data Management (MDM) Server Advanced Edition (AE) or Standard Edition (SE). Gathering this MustGather information before calling IBM Support will help familiarize you with the troubleshooting process and save you time. \n\n\n\n\n\n\nThe information in this technote is in addition to MustGather: Read first Performance data collection for InfoSphere MDM [http://www.ibm.com/support/docview.wss?uid=swg21700894] Gathering general information section. \n\n\n\n\n Section 1: JVM Memory Usage/GC logs \n\nThe GC logs are helpful to understand heap memory usage over a period of time, overhead of GC etc. \n\nFor an application running under WebSphere Application Server, Enable verbose GC using the WebSphere Application Server Administrator console. \nApplicationServer->YourServer ->Process definition->Java Virtual Machine->Java verbose GC (enabled)\n\nIn this case, the native_stderr.log contains the GC logs. This can be found in the same directory as other JVM logs (e.g. SystemOut.log)\n\nFor a standalone java application (e.g. BatchProcessor client for MDM) the GC logs can be generated by adding “–verbose:gc” option for JVM command line. The GC logs by default are written to stderr stream. These can be diverted to a specific log file by supplying JVM options. For example “-Xverbosegclog:/SOME_PATH/batch_gc.log” would save the logs to the specified path.\n\n\n captured at a point during execution. For example, the information can be about the operating system, the application environment, threads, stacks, locks, and memory. By default, a Javadump occurs when the JVM terminates unexpectedly. A Javadump can also be triggered by sending specific signals to the JVM. Javadumps are human readable.\n\n\nSection 2. JVM Thread dumps (Javacore) \n\nJavadump produces files that contain diagnostic information related to the JVM and a Java application\n\nTo generate the javacore (but no heapdump) at user signal, add the JVM option -Xdump:java to java command line (generic JVM arguments on WAS admin console)\n\nTo signal the JVM, you can use the following on AIX and Linux \n\nkill -3 <PID of JVM Process>\n\nBy default, the javacore files are generated under the <PROFILE_HOME> directory. For example. /usr/IBM/WebSphere/AppServer/profiles/AppSrv01/\n\n\n\n\n Section 3: JVM Heapdumps \n\nHeapdumps contains a dump of live objects in the java heap at that moment. This dump is stored in a Portable Heap Dump (PHD) file, a compressed binary format. By default, a Heapdump is produced when the Java heap is exhausted. A hepdump can also be triggered by sending specific signals to the JVM. \n\nTo generate the heapdump (and javacore) at user signal, add the JVM option -Xdump:heap to java command line (generic JVM arguments on WAS admin console)\n\nTo signal the JVM, you can use the following on AIX and Linux \n\nkill -3 <PID of JVM Process>\n\nBy default, the heapdumps are generated under the <PROFILE_HOME> directory. For example. /usr/IBM/WebSphere/AppServer/profiles/AppSrv01/\n\n\n\nSection 4: MDM Service Activity Monitor (SAM) \n\nSAM is a very lightweight feature, to get high level picture of every transaction in MDM Server. By default, the output goes to transactiondata*.log. The default location is the same directory as the WebSphere Application Server SystemOut.log file. SAM logs have one line per transaction, with comma separated entries. To enable SAM do the following\n\n1. Change configelement table\nupdate configelement set value='true',LAST_UPDATE_DT=current_timestamp where name in ('/IBM/DWLCommonServices/Report/Listener/enabled','/IBM/DWLCommonServices/Report/Broadcaster/enabled')\n\n2. Change the properties files in properties.jar. You would need to extract the files in a temp folder, edit the files as specified below, and then recreate the jar file.\n\nLocate the properties.jar \n\nUSER_INSTALL_ROOT/installedApps/<MyCell>/<My_Server.ear>/properties.jar\n\nThere are two properties inside the jar file that need to be changed for the following purpose:\n\na. Modify the file called sam.properties for fields to be logged. For example, the \"sam.reports\" entry in sam.properties should be set as follows for performance troubleshooting (Note: the following is ONE line, no carriage returns): \n\nsam.reports=transactionName,requestName,requesterName,clientTransactionName,sessionId,transactionId,requestID,responseSize,transactionStatus,startDateTime,endDateTime,executionTime,sam_NumberOfInsert,sam_TotalTimeOfInsert,sam_MostExpensiveInsertTime,sam_NumberOfUpdate,sam_TotalTimeOfUpdate,sam_MostExpensiveUpdateTime,sam_NumberOfDelete,sam_TotalTimeOfDelete,sam_MostExpensiveDeleteTime,sam_NumberOfSelect,sam_TotalTimeOfSelect,sam_MostExpensiveSelectTime,sam_SuspectProcessingFlag,sam_SuspectPoolSize,sam_NumberOfA1,sam_NumberOfA2,sam_NumberOfB,sam_NumberOfC\n\nb. Make changes for location and size of the log files. The out of box settings are generally sufficient for normal use. If you expect too may transactions during your tests, then increase the logging space. The log settings for this file are in Log4J.properties under properties.jar file.\n\nlog4j.appender.transactionData_file=org.apache.log4j.RollingFileAppender\nlog4j.appender.transactionData_file.Encoding=UTF-8\nlog4j.appender.transactionData_file.Threshold=ALL\nlog4j.appender.transactionData_file.layout.ConversionPattern=%m%n\nlog4j.appender.transactionData_file.layout=org.apache.log4j.PatternLayout\nlog4j.appender.transactionData_file.File=../../../logs/MY_SERVER/transactiondata.log\nlog4j.appender.transactionData_file.MaxBackupIndex=10\nlog4j.appender.transactionData_file.MaxFileSize=100MB\n# The next line controls the level of output for the TransactionDataListener logger\n# [ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF]\nlog4j.logger.com.dwl.base.report.mbean.TransactionDataListener=INFO, transactionData_file\n\n3. InfoSphere MDM restart is required for step 1 and 2 above to be effective. \n\n\n\nSECTIONS BELOW ARE OPTIONAL \n\n\nSection 1: DB Layer Monitoring \n\nA. Applicable to DB2 on LUW\nCollect a snapshot for the test duration, by running the commands as below on a db2 prompt\n1. Start the monitoring \ndb2 connect to MYDB\ndb2 -v reset monitor all\ndb2 -v update monitor switches using bufferpool on sort on lock on statement on table on uow on timestamp on\ndb2 -v get monitor switches\n\n2. Run you tests\n\n3. After the tests are over, run the following \ndb2 -v get snapshot for all on MYDB > MySnapShot.out\ndb2 -v update monitor switches using bufferpool off sort off lock off statement off table off uow off timestamp off\ndb2 -v terminate\n\nB. Applicable to DB2/Z\n1. Collect SMF reports basic accounting class 1,2,3,7,8 and statistics class 1,3,4,5,6\nNote: The accounting and statistics traces do not have real overhead and recommended to be turn on even in production environment.\n\ndb2 accounting classes 1,2,3,7,8 long format report\n-START TRACE(A) CLASS(1,2,3,7,8) DEST(SMF)\ndb2 statistics classes 1,3,4,5,6 report\n-START TRACE(S) CLASS(1,3,4,5,6) DEST(SMF)\n\n2. RMF reports – I/O details and CPU utilization (RMF summary report)\n\n3. To see the text of the SQL statements and associated statistics for those dynamic SQL statements, please enable dynamic statement caching first on your DB2 for z/OS subsystem by setting zparm CACHEDYN=YES, then start IFCID 316, 317, and 318. \n\nDNC collection instructions:\na. START TRACE(P) CLASS(30) IFCID(316,317,318) DEST(SMF)\nb. run test\nc. check and clean Dynamic cache tables \nDELETE FROM DSN_STATEMENT_CACHE_TABLE\nd. extract all statements from the global cache and to dump the statistics information to DSN_STATEMENT_CACHE_TABLE\nEXPLAIN STMTCACHE ALL \ne. select to the file inserted rows from the DSN_STATEMENT_CACHE_TABLE table\nf. Important: Stopping the trace will reset all statistics. It is important to complete the steps 3-5 before turning off the monitor trace.\ng. STOP TRACE(P) CLASS(30) IFCID(316, 317, 318)\n\nC. Applicable to Oracle\n1. Collect AWR report covering the entire duration for main test (only).\n\n\n\nRELATED INFORMATION\n MustGather: Read first Performance data collection for [http://www-01.ibm.com/support/docview.wss?uid=swg21700894]\n\n\n\n\nPRODUCT ALIAS/SYNONYM\n Master Data Management\nMDM\nInfoSphere IBM Master Data Management\nInfoSphere IBM Master Data Management Server\nMDM Server" ]

[ [ "3a", "verbosegc log rotation HP Solaris JVM rotate file TECHNOTE (FAQ) QUESTION" ], [ "3b", " How can I write verbose gc output to a log file other than the native_stdout? CAUSE" ], [ "3c", "By default, Solaris and HP-UX do not write verbose GC to a log file." ], [ "3d", "This must be configured. ANSWER" ], [ "3e", "WAS 8.5.0.2 (and higher), WAS 8.0.0.6 (and higher), WAS 7.0.0.27 (and higher): Solaris:" ], [ "3f", "Add the following parameters to the generic JVM arguments: -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintHeapAtGC -Xloggc:/tmp/gc.log" ], [ "3g", "To enable log file rotation: -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=10M notes: -Xloggc:<fileName>" ], [ "3h", " * ex: -Xloggc:/tmp/gc.log" ], [ "3i", "-XX:+UseGCLogFileRotati o n * Enabled GC log rotation, requires -Xloggc" ], [ "3j", "-XX:NumberOfGClogFiles= <num_of_files> * Set the number of files to use when rotating logs, must be >= 1." ], [ "3k", "The rotated log files will use the following naming scheme, <filename>.0, <filename>.1, ..., <filename>.n-1." ], [ "3l", "-XX:GCLogFileSize=<number>K (or M) * The size of the log file at which point the log will be rotated, must be >= 8K. HP:" ], [ "3m", "Add the following parameters to the generic JVM arguments: -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintHeapAtGC -Xverbosegc:file= /tmp/gc_pid$$.vgc" ], [ "3n", "To enable log file rotation: -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=10M" ], [ "3o", "note : $$ maps to the PID of the java process RELATED INFORMATION" ], [ "3p", " 6941923 : RFE: Handling large log files produced by lon [http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6941923]" ], [ "3q", "Enabling verbose garbage collection (verbosegc) in WebS [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21114927]" ], [ "3r", "Where to set generic JVM arguments in WebSphere Applica [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21417365]" ], [ "3s", "Verify Java SDK version shipped with IBM WebSphere Appl [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27005002]" ], [ "3t", "HP-UX Java 6.0.18 - Handling large GC log files [http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03119431/c03119431.pdf]" ], [ "3u", "HP-UX Java 7.0.05 - Handling large GC log files [http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03123467/c03123467.pdf]" ], [ "3v", "Oracle - Java HotSpot VM Options [http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html]" ] ]

[ "3a", "3b", "3d", "3e", "3f", "3g", "3h", "3i", "3j", "3k", "3l", "3m", "3n", "3o" ]

[ "IE; cookie; hostname; browser; set-cookie; wasrequrl TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nIf hostnames do not comply with IETF's specifications, browsers may not set the cookies that WebSphere Portal needs to function properly.\n\nSYMPTOM\nHTTP 400 error during a request for wps/myportal/... Specifically: \n\n1. Prior to user authentication, browser issues HTTP GET for ...//host_name.ibm.com/wps/myportal/... \n\n2. WebSphere Application Server responds with a 302 redirect to location ...//host_name.ibm.com/wps/redirect with a header like: \n\nset-cookie: WASReqURL=.../wps/myportal/...; path=/ \n\n3. The browser issues an HTTP GET for ...//host_name.ibm.com/wps/redirect but does not include the WASReqURL cookie with the request. \n\n4. The server responds with HTTP 400. \n\n \n\nThis same problem can manifest itself differently for different configurations and test cases. In general, the symptom is: \n\n1. Server's response includes set-cookie header with no domain. \n\n2. Subsequent requests from the browser do not include the cookie from (1).\n\n\nCAUSE\nWhen set-cookie does not include a domain, the IETF's RFC 6265 (5.3 #6) instructs user agents to treat the hostname as the domain. If the hostname is invalid (RFC 952, RFC 1123), the user agent might not store the cookie at all or might store it in such a way that it cannot retrieve it for use in subsequent requests. \n\nActual behavior depends on the specific browser's implementation. The behavior described in this technote has been observed on Microsoft Internet Explorer.\n\n\nDIAGNOSING THE PROBLEM\nCapture HTTP headers with Fiddler or a similar tool. Inspect the set-cookie headers from the server. Check to see whether the client presents these cookies in subsequent requests. If not, check to see if the client addresses the server with a hostname that does not comply with the RFCs. For example, any hostname that includes an underscore (\"_\").\n\n\n\nRESOLVING THE PROBLEM\nChange the hostnames of WebSphere Portal and/or any proxies which provide access such that they comply with the RFCs.\n\nRELATED INFORMATION\n RFC 952 [http://tools.ietf.org/html/rfc952]\nRFC 1123 [http://tools.ietf.org/html/rfc1123#section-2.1]\nRFC 6265 [http://tools.ietf.org/html/rfc6265#section-5.3]\nFiddler [http://www.fiddlertool.com]", "HTTP; Redirect; 302; non idempotent TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n DataPower is preventing POST based HTTP redirect in accordance with RFC and displays this as part of the error in the logs:\n\nRedirect and failed due to non idempotent request method. (RFC 2616 sec 10.3) \n\nSYMPTOM\nThis technote pertains to the following errors. \n\nExample 1: This example shows the service getting the following message: a Backside header failed to parse due to: Failed to establish a backside connection with a HTTP Redirect and failed due to non idempotent request method. (RFC 2616 sec 10.3) message.\n\nweb-application-firewall (CookieEncrypt): Backside header failed to \nparse due to: Failed to establish a backside connection \n12:20:53 webapp-firewall warn 60452 10.176.3.97 HTTP Redirect from \n'http://10.176.3.97:8080/cgi-bin/WebObjects.exe/IndvGate.woa/5/wo/2jHo28 \nQYOlhC2RZ1XQ15DE5OKo8/0.1.2.27.3.SecureSignOn.1' failed due to non \nidempotent request method. (RFC 2616 sec 10.3)\n\nExample 2: This example shows an HTTP response code 302,HTTP Redirect and failed due to non idempotent request method - RFC 2616 sec 10.3 message.\n\nWed May 21 2008 10:39:11 [mpgw][info] mpgw(ECP-MPGW): \ntid(369602)[9.65.237.170]: HTTP response code 302 for \n'http://9.65.237.170:8080/forum/ucplogin.php?mode=login' \nWed May 21 2008 10:39:11 [mpgw][warn] mpgw(ECP-MPGW): \ntid(369602)[9.65.237.170]: HTTP Redirect from \n'http://9.65.237.170:8080/forum/ucplogin.php?mode=login' failed due to\nnon idempotent request method - RFC 2616 sec 10.3. \nWed May 21 2008 10:39:11 [mpgw][error] mpgw(ECP-MPGW): \ntid(369602)[9.65.237.170]: Backside header failed to parse due to: \nFailed to establish a backside connection\n\n\nCAUSE\n302,HTTP Redirect and failed due to non idempotent request method - RFC 2616 sec 10.3 message.\n\nThis is caused by the adherence to the HTTP RFC 2616 by the Datapower Appliance. \nFor additional information on the RFC you may see this page RFC2616 [http://www.w3.org/Protocols/rfc2616/rfc2616.html]\n\n\nENVIRONMENT\nWebSphere DataPower XI50 and XS40\n\n\n\nDIAGNOSING THE PROBLEM\nBackside header failed to parse due to: Failed to establish a backside connection failed due to non idempotent request method. (RFC 2616 sec 10.3)\n\n\n\nRESOLVING THE PROBLEM\nTo resolve the issue, the IBM WebSphere DataPower SOA appliance web application firewall can be configured to handle these \"302 Redirects\". Follow the steps outlined in the attached document that explain how to configure a web application firewall to handle the redirects using the attached ResetLocation.xsl stylesheet. With the specified edit for your environment, this file will handle most simple use cases and may also be edited to handle any additional requirements for your specific business solution.\n\nsampleForRedirects.doc [/support/docview.wss?uid=swg21318593&aid=2] [/support/docview.wss?uid=swg21318593&aid=1]ResetLocation.xsl [/support/docview.wss?uid=swg21318593&aid=4] [/support/docview.wss?uid=swg21318593&aid=3]\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower XML Security Gateway XS40 Not Applicable Firmware 4.0.1, 3.8.2, 3.8.1, 3.8, 3.7.3 Edition Independent Business Integration WebSphere DataPower SOA Appliances General Firmware 4.0.1, 3.8.2, 3.8.1, 3.8, 3.7.3 Edition Independent", " SUBSCRIBE\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 * When this error is logged as a result of malformed HTTP\n requests, the message insert values might be corrupted.\n \n 0x80e005ea\n Malformed method headers (%s) for HTTP request, from URL %s.\n Explanation:\n \n The HTTP request method did not conform to one specified by RFC\n 2616 or was prohibited by your configuration.\n Administrator response:\n \n Check your method against RFC 2616 and your configuration. The\n most commonly employed method is POST.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * Corrected problem where HTTP services might log message with\n corrupted message inserts\n when malformed HTTP request is received.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The fix will be available in 3.8.2.17.\n \n For a list of the latest fix packs available, please see:\n http://www-01.ibm.com/support/docview.wss?uid=swg21237631 [http://www-01.ibm.com/support/docview.wss?uid=swg21237631]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IC88958\n \n \n * REPORTED COMPONENT NAME\n DATAPOWER\n \n \n * REPORTED COMPONENT ID\n DP1234567\n \n \n * REPORTED RELEASE\n 382\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-12-10\n \n \n * CLOSED DATE\n 2012-12-19\n \n \n * LAST MODIFIED DATE\n 2013-01-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 DATAPOWER\n \n \n * FIXED COMPONENT ID\n DP1234567\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R382 PSY\n UP", "iphone blackberry mobile google android browsers browser TECHNOTE (FAQ)\n\nQUESTION\n What browsers are supported with IBM Security Access Manager? \n\nANSWER\n\nClient Support Statement:\n\n\n\n[/support/docview.wss?uid=swg21516843&amp;aid=1]WebSEAL\n[/support/docview.wss?uid=swg21516843&amp;aid=2]Web Portal Manager WebSEAL HTTP Client Support Statement \n\nEnd user operations \nThis refers to clients used for non-administrative connections, such as authenticating to WebSEAL and connecting to applications protected by WebSEAL. In lieu of providing a list of specific clients supported by WebSEAL, which may limit the breadth of clients WebSEAL can support, we state that WebSEAL generally supports clients that conform to the HTTP 1.1 standard as defined by RFC 2616. This is not a comprehensive statement. of support because WebSEAL relies on a number of client characteristics that are either not defined or loosely defined by RFC 2616. Examples of such characteristics include, but are not limited to: Cookie management, SSL support, and concurrency of multiple connections. Widely used browsers such as Firefox, Chrome, Safari and Internet Explorer support such characteristics during typical usage. The extension of browser capabilities that modify these characteristics can, however, introduce compatibility problems with WebSEAL. The same is true of other client types, such as mobile applications or rich clients. Compatibility complications that cannot be resolved through modification of the environment or configuration of the WebSEAL product are not supported. \n\n\nWeb Portal Manager Client Support Statement \n\nAdministrative operations \nThis refers to clients for use with the Web Portal Manager graphical user interface. To find the list of supported browsers please refer to the release notes documentation for the version of Tivoli Access Manager for e-business in use. (Release Notes > Installation, configuration, upgrade, and migration information > Software requirements > Tivoli Access Manager supported Web browsers) \n Back to top \n\n \n\nPRODUCT ALIAS/SYNONYM\n ITAM TAM PD", "cache caching HTTP TECHNOTE (FAQ)\n\nQUESTION\n Does the 'Cache Response to POST and PUT Requests' violate the HTTP 1.1 specifications with respect to caching? \n\nCAUSE\nVersion 6.0.0 introduced the Cache Response to POST and PUT Requests option to the document cache policy of the XML manager. This option allows for specific caching use cases, which include web services caching.\nFor example, most web services use the POST request exclusively. Responses to POST requests are cacheable according to the specification, but only when the responses include explicit freshness information. Additionally, a secondary caching key beyond the resource URI is typically needed to distinguish the response for one POST request from another. This secondary key could be achieved by use of the Vary header, but DataPower does not support the Vary header as a secondary caching key. \nMost web services that could benefit from caching would not respond to requests with the explicit freshness information nor the Vary header.\n\nTherefore, a solution was needed in the web services gateway that sits in front of these web services.\n\n\nANSWER\nYou can enable the Cache Response to POST and PUT Requests option only when the Fixed caching policy type is selected. The Fixed caching policy type violates the HTTP 1.1 specification with respect to caching when determining whether or not a response can be cached, and the time to live (TTL) of a cache response. With the Fixed caching policy type, the majority of the HTTP cache control headers are ignored. Instead, the response is forced to be cached for as long as specified in the TTL property of DataPower caching policy. \n\n\nBeyond the violations associated with the Fixed caching policy type, the Cache Response to POST and PUT Requests option violates the following aspects of the HTTP 1.1 specifications. \n\n * RFC 7231 section 4.3.3 [https://tools.ietf.org/html/rfc7231#section-4.3.3] states \"Response to POST requests are only cacheable when they include explicit freshness information.\" With the option enabled, DataPower caches the response to a POST request regardless of the freshness information. \n * RFC 7231 section 4.3.4 [https://tools.ietf.org/html/rfc7231#section-4.3.4] states \"Response to the PUT method are not cacheable.\" With the option enabled, DataPower caches the response to a PUT request. \n * RFC 7234 section 2 [https://tools.ietf.org/html/rfc7234#section-2] states \"The primary cache key consists of the request method and target URI.\" \n DataPower only uses the target URI as the primary cache key. If a secondary cache-key is needed, specify one using the x-dp-cache-key HTTP header. \n * RFC 7234 section 4 [https://tools.ietf.org/html/rfc7234#section-4] states \"A cache MUST write through requests with methods that are unsafe to the origin server.\" With the the option enabled, DataPower does not write through PUT and POST requests to the origin server that have fresh responses in the cache. \n * RFC 7234 section 4.4 [https://tools.ietf.org/html/rfc7234#section-4.4] states \"A cache MUST invalidate the effective Request URI as well as the URI(s) in the Location and Content-Location response header fields (if present) when a non-error status code is received in response to an unsafe request method.\" With the option enabled, DataPower does not invalidate existing cached entries on PUT and POST requests." ]

[ [ "1a", "HTTP; Redirect; 302; non idempotent TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "1b", " DataPower is preventing POST based HTTP redirect in accordance with RFC and displays this as part of the error in the logs:" ], [ "1c", "Redirect and failed due to non idempotent request method." ], [ "1d", "(RFC 2616 sec 10.3) SYMPTOM" ], [ "1e", "This technote pertains to the following errors." ], [ "1f", "Example 1: This example shows the service getting the following message: a Backside header failed to parse due to: Failed to establish a backside connection with a HTTP Redirect and failed due to non idempotent request method." ], [ "1g", "(RFC 2616 sec 10.3) message." ], [ "1h", "web-application-firewall (CookieEncrypt): Backside header failed to" ], [ "1i", "parse due to: Failed to establish a backside connection" ], [ "1j", "12:20:53 webapp-firewall warn 60452 10.176.3.97 HTTP Redirect from 'http://10.176.3.97:8080/cgi-bin/WebObjects.exe/IndvGate.woa/5/wo/2jHo28" ], [ "1k", "QYOlhC2RZ1XQ15DE5OKo8/0.1.2.27.3.SecureSignOn.1' failed due to non" ], [ "1l", "idempotent request method." ], [ "1m", "(RFC 2616 sec 10.3)" ], [ "1n", "Example 2: This example shows an HTTP response code 302,HTTP Redirect and failed due to non idempotent request method - RFC 2616 sec 10.3 message." ], [ "1o", "Wed May 21 2008 10:39:11 [mpgw][info] mpgw(ECP-MPGW):" ], [ "1p", "tid(369602)[9.65.237.170]: HTTP response code 302 for 'http://9.65.237.170:8080/forum/ucplogin.php?mode=login'" ], [ "1q", "Wed May 21 2008 10:39:11 [mpgw][warn] mpgw(ECP-MPGW):" ], [ "1r", "tid(369602)[9.65.237.170]: HTTP Redirect from" ], [ "1s", "'http://9.65.237.170:8080/forum/ucplogin.php?mode=login' failed due to" ], [ "1t", "non idempotent request method - RFC 2616 sec 10.3." ], [ "1u", "Wed May 21 2008 10:39:11 [mpgw][error] mpgw(ECP-MPGW):" ], [ "1v", "tid(369602)[9.65.237.170]: Backside header failed to parse due to:" ], [ "1w", "Failed to establish a backside connection CAUSE" ], [ "1x", "302,HTTP Redirect and failed due to non idempotent request method - RFC 2616 sec 10.3 message." ], [ "1y", "This is caused by the adherence to the HTTP RFC 2616 by the Datapower Appliance." ], [ "1z", "For additional information on the RFC you may see this page RFC2616 [http://www.w3.org/Protocols/rfc2616/rfc2616.html] ENVIRONMENT" ], [ "1aa", "WebSphere DataPower XI50 and XS40" ], [ "1ab", "DIAGNOSING THE PROBLEM" ], [ "1ac", "Backside header failed to parse due to: Failed to establish a backside connection failed due to non idempotent request method." ], [ "1ad", "(RFC 2616 sec 10.3)" ], [ "1ae", "RESOLVING THE PROBLEM" ], [ "1af", "To resolve the issue, the IBM WebSphere DataPower SOA appliance web application firewall can be configured to handle these \"302 Redirects\"." ], [ "1ag", "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." ], [ "1ah", "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." ], [ "1ai", "sampleForRedirects.doc [/support/docview.wss?uid=swg21318593&aid=2] [/support/docview.wss?uid=swg21318593&aid=1]ResetLocation.xsl [/support/docview.wss?uid=swg21318593&aid=4] [/support/docview.wss?uid=swg21318593&aid=3]" ], [ "1aj", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower XML Security Gateway XS40 Not Applicable Firmware 4.0.1, 3.8.2, 3.8.1, 3.8, 3.7.3 Edition Independent Business Integration WebSphere DataPower SOA Appliances General Firmware 4.0.1, 3.8.2, 3.8.1, 3.8, 3.7.3 Edition Independent" ] ]

[ "1b", "1c", "1d", "1e", "1f", "1g", "1n", "1x", "1y", "1ae", "1af", "1ag", "1ai" ]

[ "datapower; failed; parse; process; error; network; connection; persistent; headers; response headers; failed to process response headers; 7993; 7993; 7993; machine type 7993 TECHNOTE (FAQ)\n\nQUESTION\n What does this error mean?\n\nGeneral error that is always seen:\n[servicetype][error] wsgw(policyrule): tid(196761)[error][x.x.x.x]: Failed to process response headers\n\nSpecifically from a Web Service Gateway:\n[ws-proxy][error] wsgw(Proxy): tid(1234567)[10.2.3.4]: Backside header failed to parse due to: Failed to process response headers\n[ws-proxy][error] wsgw(Proxy): tid(1234567)[error][10.2.3.4]: Failed to process response headers \n\nAdditional log information might be seen while at the debug log level.\n\n\nCAUSE\nWhen you read this error, keep in mind that it is thrown from a rule within a policy of a service. This error almost always means that the policy did not receive any data. If you increase the logging from error to debug, you should see network failures surrounding the response header error.\n\n\n\nIn almost every event, this error is caused by a connection failure.\nThe error is correct, the service did not receive any response headers or data. The key to help confirm this is to increase the log level to debug. This will allow you to see the network debug errors around the context of the service error.\n\n\nANSWER\nThe classic causes of this are either of these two: \n\n\n\n \n\nA slow response that causes the connection to timeout before receiving the response\nA failed connection attempt due to a closed persistent connection or some other connection issue that prevents the WebSphere® DataPower device® from connecting to the backend. For example, a reused connection would be attempted and found to already be closed out by something outside of DataPower®.\nAn example of this is explained here:\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21417934&wv=1 [http://www-01.ibm.com/support/docview.wss?uid=swg21417934&wv=1]\n\nThere are a broad range of network errors that can trigger this to error. A packet trace is the key to capture the problem and confirm what type of failure is the cause. A log with event subscription of \"all\" \"debug\" will also help correlate and confirm the packet trace data.\n\nIn some cases, a simple work around to try is to lower the DataPower persistent timeout or disable persistent connections. If this does not prevent the problem, then analysis of the packet trace and error report are required.", "tsamp; tsa; samp; monitorcommandtimeout; GBLRESRM_MONITOR_TIMEOUT; GBLRESRM_MONITOR_TI; monitor command timeout; monitor command time out TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Found error messages in syslogs and error report showing that IBM.GblResRM is reporting an error condition. \n\nSYMPTOM\nSyslogs:\nOct 30 19:25:37 NC106152 daemon:err|error GblResRM[15204516]: (Recorded using libct_ffdc.a cv 2):::Error ID: :::Reference ID: :::Template ID: d889c2ac:::Details File: :::Location: RSCT,Application.C,1.92.3.59,4876 :::GBLRESRM_MONITOR_TIMEOUT IBM.Application monitor command timed out. Resource name res1\n\nError Report:\n---------------------------------------------------------------------------\nLABEL: GBLRESRM_MONITOR_TI\nIDENTIFIER: D889C2AC\n\nDate/Time: Thu Oct 30 19:27:11 2014\nSequence Number: 7004\nMachine Id: 00F6A84B4C00\nNode Id: NC106152\nClass: O\nType: PERM\nWPAR: Global\nResource Name: GblResRM\n\nDescription\nIBM.Application monitor command timed out.\n\n\n\nCAUSE\n1) What is a monitor command timeout: \n\nA monitor command timeout occurs when a set amount of time has passed after TSAMP issues a monitor command and the monitor command has not exited/finished. This set amount of time is set when the resource is created and can be found in the persistent attributes for all IBM.Application resources. \n\n2) What happens when a monitor command times out:\nWhen the monitor command runs in excess of the time (in seconds) set in the MonitorCommandTimeout attribute, then TSAMP will kill the monitor command script and issue the above messages. When this happens the resource who's monitor command was killed is marked with the OpState of \"Unknown\" and no further automation action will be taken against that resource until such a time as a monitor command returns within the MonitorCommandTimout timeframe with a valid OpState value.\n\nTo check the value of the MonitorCommandTimeout attribute issue the following command on either node as root:\nlsrsrc -s 'Name like\"%\" && ResourceType=1' IBM.Application Name MonitorCommandTimeout\n\n3) What causes monitor command timeouts:\nA monitor command timeout is typically due to a increased load on the system making what are typically simple commands take longer to complete. TSAMP uses shells scripts to monitor resources and those scripts can vary in complexity depending on what is needed for the solution. \nIf monitor command timeouts are occurring and there is no extra load on the systems, then likely the value of the MonitorCommandTimeout attribute has been set to aggressive and needs to be relaxed.\n\n\nRESOLVING THE PROBLEM\nTo adjust the MonitorCommandTimeout attribute for a resource, you will need to know what the value is for the resource currently. In this example we are using an IBM.Application resource called \"res1\": \n\nFirst you should find out how long the time out needs to be set for. This is not always easy as your time frame for testing might not match the load level during the times when the monitor command timeout messages are appearing. However, to test how long it takes for the monitor command to return follow the steps below: \n\nIssue the following command on any node:\n[root@NC106152 /]# lsrsrc -s 'Name =\"res1\"' IBM.Application MonitorCommand MonitorCommandTimeout UserName\nResource Persistent Attributes for IBM.Application\nresource 1:\nMonitorCommand = \"/usr/sbin/rsct/sapolicies/fileapp/fileapp.sh status res1\"\nMonitorCommandTimeout = 5\nUserName = \"root\"\nresource 2:\nMonitorCommand = \"/usr/sbin/rsct/sapolicies/fileapp/fileapp.sh status res1\"\nMonitorCommandTimeout = 5\nUserName = \"root\"\nresource 3:\nMonitorCommand = \"/usr/sbin/rsct/sapolicies/fileapp/fileapp.sh status res1\"\nMonitorCommandTimeout = 5\nUserName = \"root\"\n\nThe issue the command as the user \"UserName\", with the following syntax :\n\ntime <MonitorCommand as shown within quotes in above output>\n\nHere's an example :\n[root@NC106152 /]# time /usr/sbin/rsct/sapolicies/fileapp/fileapp.sh status res1\n\nreal 1m0.006s\nuser 0m0.002s\nsys 0m0.002s\n\n1 minute and 6 thousandths of a second was how long this monitor command took to complete. \n\n \n\nTo adjust the timeout issue the following command as root on either node: \n\nchrsrc -s 'Name =\"res1\"' IBM.Application MonitorCommandTimeout=10 \n\n \n\nAfter changing this value, you should monitor your cluster for repeats of the timeout messages and ensure that the problem has been taken care of. \n\n \n\nNote: You should not adjust this too high as it affects how quickly TSAMP will detect and react to an outage. You want it high enough to get valid operational state.", "50170000000OSMLAA4 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Wrapper process restarting the hub even though the hub was running OK.\n\n\nCAUSE\nThe timeout being exceeded can be caused by a number of issues. The common ones would be waiting on the CPU because it is at 100% capacity, or waiting on I/O from the disk. This has been seen when an Anti-Virus application is running on the Application Server.\n\nRESOLVING THE PROBLEM\n In this case the engine was slow to respond to ping requests because it was busy, but the engine was not crashing. We modified the wrapper.conf so that the wrapper would give more time for the engine to respond before restarting the process. \n\nThe wrapper process has a socket connection to the jvm and by default will ping it every 5 seconds to ensure the JVM has not gone away (crashed) or hung. It will wait 30 seconds (default) for a response to it's ping. If no response is received, it's assumed to be hung and the wrapper process will kill -9 the jvm and restart it.\n\nYou can adjust the interval and timeout.\n\nwrapper.ping.timeout = 30 (default), 0 means never timeout but setting this to 0 means if the process dies unexpectedly the wrapper will not automatically restart it. The value of the timeout needs to be at least 5 seconds longer than the value of the interval.\n\nwrapper.ping.interval = 5 (default).\n\n\n\nHISTORICAL NUMBER\n 840", "meeting; connection; refused TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nNote: This technote applies to IBM Sametime 8.5.2 Interim Feature Release 1. \n\nAnything over 200 simultaneous connections to a Meeting server will be refused.\n\n\nSYMPTOM\nAny time there are a large number of users attempting to perform the same action at the same time on a single Meeting server, this issue may be at play. For example, let's say 1000 users are in a meeting room where a document is being shared. The first page is being shared and discussed audibly, leading to several minutes of room inactivity. Then, the presenter moves to the tenth page in the document. Many of the users in the room may not see the new page because there were too many clients all requesting that page that were coming from a state of inactivity.\n\n\nCAUSE\nIn Windows Server 2008, Microsoft disabled the ability to configure the Connection Backlog; therefore, the maximum backlog allowed is 200 simultaneous connection requests.\n\n\n\nENVIRONMENT\nSametime Meetings on Windows Server 2008\n\n\n\nRESOLVING THE PROBLEM\nA keep-alive was introduced into the Meetings Connect and web clients. This keep-alive always maintains at least one open connection between a client and a server, even during times of room inactivity. Because of this, 1000 users suddenly requesting a new slide from the server will not result in connection refusal because the connections already exist. \n\nBy default, WebSphere sets a timeout of 60 seconds for persistent HTTP and HTTPS connections. This setting can be found by accessing the WebSphere Admin Console and going to Servers -> Server Types -> WebSphere application servers -> STMeetingServer -> Web Container Settings -> Web container transport chains. Click on \"WCInboundDefault\" for HTTP or \"WCInboundDefaultSecure\" for HTTPS. On each page, look for \"Persistent timeout\" under \"HTTP inbound channel\" to see what the timeout setting is. \n\nBecause the WebSphere default timeout is 60 seconds, our keep-alive is set to occur every 55 seconds so that the connections always remain active. If, however, you have changed the WebSphere Inbound Persistent Connection timeout to a different value, you should change the Meetings keep-alive value so that it is just less than the persistent timeout value. This Meetings keep-alive setting is stored as a server configuration item. Using your Sametime System Console, you can change this value by editing your Meeting server configuration and changing the value for \"meetingroom.keepAliveTime\" (value is in milliseconds).", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This document walks you through the usual suspect settings that can trigger unwanted TM1 timeouts. This document is geared for Windows Server 2008 R2, however the majority will still be applicable to other Windows operating systems.\n\n\n\nSYMPTOM\nYou are encountering one or more of the following errors or scenarios in your TM1 environment, whether it be TM1Web, Contributor/Applications, Perspectives, or others: \n\n * Server Error in '/TM1Web' Application. Request timed out. \n * System.Web.HttpException: Request timed out. \n * ERROR Applix.TM1.Web.Page.TM1WebPageUtils - <Your Web session has timed out. Please login again.> \n * Session timed out. Please login again… \n * Error -2 occurred pinging your cognos passport. \n * Operation Failed\n\n\nRESOLVING THE PROBLEM\nTroubleshooting Steps:\n1. Check the tm1s.cfg file of the TM1Server(s) you are having trouble with, and look for the IdleConnectionTimeOutSeconds parameter. If the parameter exists, adjust as desired.\n\n\n2. Open the Internet Information Services (IIS) Manager. Expand 'ServerName', expand 'Sites. Right-click 'Default Web Site', select 'Manage Web Site' > 'Advanced Settings...'. Expand 'Connection Limits' and adjust the 'Connection Time-out' setting.\n\n\n3. In IIS, Expand 'ServerName', expand 'Sites' and 'Default Web Site', right-click the 'TM1Web' virtual directory. Select 'Manage Web Site' > 'Advanced Settings...'. Make note of the 'Application Pool' parameter, as this is the Application Pool TM1Web runs on.\n\nIn IIS, Expand 'ServerName' and select 'Application Pools'. Right-click the 'Application Pool' TM1Web runs on, and select 'Advanced Settings'. Within 'Process Model', adjust the 'Idle Time-out (minutes)' parameter as desired.\n\n\n4. Navigate to your TM1Web install directory (\\TM1InstallPath\\TM1_64\\TM1Web), and open the web.config file with Notepad. Look for the following line: <httpRuntime executionTimeout=\"110\" /> . Adjust the httpRuntime executionTimeout as desired.\n\n\n5. In the same web.config file from Step 3, look for the following line:\n<sessionState mode=\"InProc\" stateConnectionString=\"tcpip=127.0.0.1:42424\" sqlConnectionString=\"data source=127.0.0.1;Trusted_Connection=yes\" cookieless=\"false\" timeout=\"20\" /> . Adjust the timeout parameter as desired. \n\nUsing all of the above settings, double-check what you have put in to each to ensure you are consistent and that the values make sense. Also, verify that you set it appropriately for minutes vs. seconds. After you have verified the above, you will need to reset your webserver for the changes to take effect.\n\nTo reset your webserver, open Command Prompt (right-click, and select ‘Run as Administrator’), and type ‘iisreset’ and press enter (no quotes). You will be notified when the server has come back online.\n\n\n\nAdditional Considerations:\n\nCAM Namespace:\nIf you use a CAM Namespace as your authentication source for TM1, you will want to do the following:\n\n6. Check the tm1s.cfg file of the TM1Server(s) you are having trouble with, and look for the ClientPingCAMPassport parameter. If the parameter exists, make note of the value. \n\n * Still in your tm1s.cfg file, look at your ServerCAMURI parameter. It should look similar to http;//server:9300/p2pd/servlet/dispatch<⁄font>. You will need your Cognos BI Administrator to check the Cognos Configuration for this BI server, and verify the ‘Ping timeout in seconds’ and 'Inactivity timeout in seconds' settings - these two should be set about the same (default is 3600). \n * Back in your tm1s.cfg file, configure the ClientPingCAMPassport to be at least half of what is listed as the Ping timeout in seconds/Inactivity timeout in seconds on your BI Dispatcher, or lower. For example, assuming the dispatcher timeouts are set to 3600, then the tm1s.cfg ClientPingCAMPassport parameter should be set to 1800 or lower (default is 900).\n \n If you made changes to your tm1s.cfg file, you will need to restart your TM1 Server for the changes to take effect.\n\n7. Load Balancing / Network Topology: \nIf you have load balancing or a unique network topology in your environment, you need to ensure: \n * That your Load Balancers are using a ‘sticky’ or ‘persistent’ connection, so that once a session is opened on one server, it remains on that one server until the session has been terminated. \n * That any third party timeouts are configured to match your desired TM1 Timeout settings. Note, you will likely need to engage your network team to uncover all potential timeouts. For example: * Siteminder or Webseal IDLE time out settings \n * F5 timeouts, including ‘Default Forwarding Virtual Timeout’\n \n \n\n\nSummary: \nAfter following this document, you should now be familiar with the following timeout parameters: * IdleConnectionTimeOutSeconds (tm1s.cfg) \n * Connection Timeout (Default Website Advanced Settings, IIS) \n * Application Pool Recycling Timeout (AppPool Advanced Settings, IIS \n * httpRuntime executionTimeout (web.config, TM1Web) \n * sessionState timeout (web.config, Tm1Web)\n\n\nOptional Parameters (depending on your configuration): * ClientPingCAMPassport (tm1s.cfg) \n * Ping timeout in seconds (Cognos Configuration of BI Dispatcher) \n * Inactivity timeout in seconds (Cognos Configuration of BI Content Manager) \n * Load balancing (Sticky / Persistent Sessions) \n * Load balancing, Siteminder, or Webseal timeouts\n\n\n\nIf you have additional questions, or are still experiencing issues in your environment, please log a PMR with IBM Support and provide the following information: * description of timeout problem/error received \n * tm1s.cfg file \n * web.config file from TM1Web \n * screenshots of all configurable IIS settings \n * version detail of the TM1 environment \n * tm1web.log \n * any additional/relevant environment details" ]

[ [ "0a", "datapower; failed; parse; process; error; network; connection; persistent; headers; response headers; failed to process response headers; 7993; 7993; 7993; machine type 7993 TECHNOTE (FAQ) QUESTION" ], [ "0b", " What does this error mean?" ], [ "0c", "General error that is always seen:" ], [ "0d", "[servicetype][error] wsgw(policyrule): tid(196761)[error][x.x.x.x]: Failed to process response headers" ], [ "0e", "Specifically from a Web Service Gateway:" ], [ "0f", "[ws-proxy][error] wsgw(Proxy): tid(1234567)[10.2.3.4]: Backside header failed to parse due to: Failed to process response headers" ], [ "0g", "[ws-proxy][error] wsgw(Proxy): tid(1234567)[error][10.2.3.4]: Failed to process response headers" ], [ "0h", "Additional log information might be seen while at the debug log level. CAUSE" ], [ "0i", "When you read this error, keep in mind that it is thrown from a rule within a policy of a service." ], [ "0j", "This error almost always means that the policy did not receive any data." ], [ "0k", "If you increase the logging from error to debug, you should see network failures surrounding the response header error." ], [ "0l", "In almost every event, this error is caused by a connection failure." ], [ "0m", "The error is correct, the service did not receive any response headers or data." ], [ "0n", "The key to help confirm this is to increase the log level to debug." ], [ "0o", "This will allow you to see the network debug errors around the context of the service error. ANSWER" ], [ "0p", "The classic causes of this are either of these two:" ], [ "0q", "A slow response that causes the connection to timeout before receiving the response" ], [ "0r", "A failed connection attempt due to a closed persistent connection or some other connection issue that prevents the WebSphere® DataPower device® from connecting to the backend." ], [ "0s", "For example, a reused connection would be attempted and found to already be closed out by something outside of DataPower®." ], [ "0t", "An example of this is explained here: http://www-01.ibm.com/support/docview.wss?uid=swg21417934&wv=1 [http://www-01.ibm.com/support/docview.wss?uid=swg21417934&wv=1]" ], [ "0u", "There are a broad range of network errors that can trigger this to error." ], [ "0v", "A packet trace is the key to capture the problem and confirm what type of failure is the cause." ], [ "0w", "A log with event subscription of \"all\" \"debug\" will also help correlate and confirm the packet trace data." ], [ "0x", "In some cases, a simple work around to try is to lower the DataPower persistent timeout or disable persistent connections." ], [ "0y", "If this does not prevent the problem, then analysis of the packet trace and error report are required." ] ]

[ "0a", "0d", "0f", "0g", "0i", "0k", "0l", "0m", "0p", "0q", "0r", "0s", "0u", "0v", "0x" ]

[ " SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere Application Server is shipped with IBM Tivoli Network Manager IP Edition versions 3.9 and 4.1.1; IBM WebSphere Application Server is a required product for IBM Tivoli Network Manager IP Edition version 4.2. Information about a security vulnerability affecting IBM HTTP Server, a product which is a component in IBM WebSphere Application Server, has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nPlease consult the security bulletin Information disclosure in IBM HTTP Server (CVE-2017-12613) [http://www-01.ibm.com/support/docview.wss?uid=swg22013598] for vulnerability details and information about fixes.\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Tivoli Network Manager IP Edition 3.9, 4.1.1 and 4.2 \n\nREMEDIATION/FIXES\nRefer to the following security bulletins for vulnerability details and information about fixes addressed by IBM WebSphere Application Server, which is shipped with IBM Tivoli Network Manager IP Edition versions 3.9 and 4.1.1; and a product required by IBM Tivoli Network Manager IP Edition version 4.2. \n\nPrincipal Product and Version(s) Affected Supporting Product and Version Affected Supporting Product Security Bulletin IBM Tivoli Network Manager IP Edition 3.9 Bundled the TIP version 2.1.0.x, which bundles IBM WebSphere version 7.0.0.x. Information disclosure in IBM HTTP Server (CVE-2017-12613) [http://www-01.ibm.com/support/docview.wss?uid=swg22013598]\nSee Section \"For V7.0.0.0 through 7.0.0.43:\" IBM Tivoli Network Manager IP Edition 4.1.1 Bundled the TIP version 2.2.0.x, which bundles IBM WebSphere version 7.0.0.x. Information disclosure in IBM HTTP Server (CVE-2017-12613) [http://www-01.ibm.com/support/docview.wss?uid=swg22013598]\nSee Section \"For V7.0.0.0 through 7.0.0.43:\" IBM Tivoli Network Manager IP Edition 4.2.0 IBM Tivoli Network Manager IP Edition 4.2 requires the installation of 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.. Information disclosure in IBM HTTP Server (CVE-2017-12613) [http://www-01.ibm.com/support/docview.wss?uid=swg22013598]\nSee Section \"For V8.5.0.0 through 8.5.5.13:\" \nPlease also note the end of support 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] from 12 September 2017 for selected Netcool product versions. You can find detailed information on whether the product version you have installed in your environment is affected by this end of service announcement by following the Netcool End of Support Knowledge Collection [https://www-01.ibm.com/support/entdocview.wss?uid=swg22009231] . If your product version is affected, IBM recommend to upgrade your product version to the latest supported version of your product. Please contact your IBM account manager for any question you might have or for any assistance you may require for upgrading an end of service announced offering. 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 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 April 2018 - 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.", " SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere Application Server is shipped as a component of IBM WebSphere Commerce. Information about a potential security vulnerability affecting the WebSphere Application Server was published in a security bulletin. \n\nVULNERABILITY DETAILS\nConsult the security bulletin Information Disclosure in WebSphere Application Server (CVE-2017-1743) [http://www-01.ibm.com/support/docview.wss?uid=swg22013601]for vulnerability details and information about fixes.\n\nAFFECTED PRODUCTS AND VERSIONS\nWebSphere Commerce versions 7.0.0.0 or higher fix pack\nWebSphere Commerce versions 8.0.0.0 or higher fix pack or higher mod pack\n\nREMEDIATION/FIXES\n \n\nPrincipal Product and Version(s) Affected Supporting Product and Version Affected Supporting Product Security Bulletin WebSphere Commerce V7.0 WebSphere Application Server 7.0.0\nWebSphere Application Server 8.5.5 Information Disclosure in WebSphere Application Server (CVE-2017-1743) WebSphere Commerce V8.0 WebSphere Application Server 8.5.5 Information Disclosure in WebSphere Application Server (CVE-2017-1743) 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 24 May 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. \n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Commerce WebSphere Commerce - Express Security IBM i, Linux, Windows 7.0 Express Commerce WebSphere Commerce Developer Enterprise Security Windows 8.0, 7.0 All Editions Commerce WebSphere Commerce Professional Security AIX, IBM i, Linux, Solaris, Windows 8.0, 7.0 Professional Edition", "WMB IIB SECURITY BULLETIN\n\nSUMMARY\n OpenSSL vulnerabilities were disclosed on May 3, 2016 by the OpenSSL Project. The DataDirect ODBC Drivers used by WebSphere Message Broker and IBM Integration Bus have addressed the applicable CVEs. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-2107 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2107]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error when the connection uses an AES CBC cipher and the server support AES-NI. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via the POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt traffic.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112854 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112854] 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\nCVEID: CVE-2016-2176 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2176]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, by sending an overly long ASN.1 string to the X509_NAME_oneline() function; an attacker could exploit this vulnerability to return arbitrary stack data in the buffer.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112858 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112858] 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\nFor users of ODBC SSL using the DataDirect drivers:\n\n\n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus\n\n\nV10\n\nIT16038 The APAR is available in fix pack 10.0.0.6\n\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24042654 [https://www-304.ibm.com/support/docview.wss?uid=swg24042654] IBM Integration Bus\n\n\nV9\n\nIT10511, IT16038 The APAR is available in fix pack 9.0.0.6\n[https://www-304.ibm.com/support/docview.wss?uid=swg24042598]\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24042598 [https://www-304.ibm.com/support/docview.wss?uid=swg24042598] WebSphere Message Broker V8 IT14826, IT16038, IT15532 The APAR is available in fix pack 8.0.0.8\n[https://www-304.ibm.com/support/docview.wss?uid=swg24042925]\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 xx- Nov-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\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker 8.0 \nPRODUCT ALIAS/SYNONYM\n WMB IIB", "CVE-2017-1681 SECURITY BULLETIN\n\nSUMMARY\n In the WebSphere Application Server where the Rational Asset Manager is deployed, a potential information disclosure vulnerability is identified. Information about this security vulnerability affecting WebSphere Application Server 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\n \n\nIBM Rational Asset Manager 7.5 and 7.5.1. \n\nNOTE: Rational Asset Manager 7.5.2 and later versions does not support embedded WebSphere Application Server.\n\nREMEDIATION/FIXES\nRefer to the following security bulletin for vulnerability details and information about fixes addressed by IBM WebSphere Application Server (WAS). \n\n \n\n * Affected Supporting Product\n\n * Affected Supporting Product Security Bulletin\n\n * \n\n * Security Bulletin: Information disclosure in WebSphere Application Server (CVE-2017-1681)\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\nNone \n\nCHANGE HISTORY\n * 16 MAR 2018: 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.", "WMB 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" ]

[ [ "4a", "WMB IIB SECURITY BULLETIN SUMMARY" ], [ "4b", " 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. VULNERABILITY DETAILS" ], [ "4c", "CVEID: CVE-2017-1126 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1126]" ], [ "4d", "DESCRIPTION: 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." ], [ "4e", "CVSS Base Score: 5.3" ], [ "4f", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/121341 [https://exchange.xforce.ibmcloud.com/vulnerabilities/121341] for the current score" ], [ "4g", "CVSS Environmental Score*: Undefined" ], [ "4h", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)" ], [ "4i", "AFFECTED PRODUCTS AND VERSIONS" ], [ "4j", "IBM Integration Bus V9.0.0.0 - V9.0.0.8 and V10.0.0.0 - V10.0.0.9" ], [ "4k", " WebSphere Message Broker V8.0.0.0 - V8.0.0.8 REMEDIATION/FIXES" ], [ "4l", "Product VRMF APAR Remediation/Fix IBM Integration Bus V10.0.0.0-V10.0.0.9 IT18731/" ], [ "4m", "IT21161 The APARs are available in fix pack 10.0.0.10" ], [ "4n", "http://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/" ], [ "4o", "IT21161 The APARs are available in fix pack 9.0.0.9" ], [ "4p", "http://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/" ], [ "4q", "IT21161 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]" ], [ "4r", "For a fix for APAR IT21161, please contact IBM support." ], [ "4s", "Websphere Message Broker V8 is no longer in full support; IBM recommends upgrading to a fixed, supported version/release/platform of the product." ], [ "4t", "If you are an extended support customer and require a fix, this is available only for the latest fixpack (8.0.0.9)." ], [ "4u", "To obtain the fix contact IBM support." ], [ "4v", "WORKAROUNDS AND MITIGATIONS None" ], [ "4w", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS" ], [ "4x", " Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. REFERENCES" ], [ "4y", "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]" ], [ "4z", "On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION" ], [ "4aa", "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]" ], [ "4ab", "IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] CHANGE HISTORY" ], [ "4ac", " 29 September 2017: Original version published" ], [ "4ad", "*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score." ], [ "4ae", "Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. DISCLAIMER" ], [ "4af", "According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\"" ], [ "4ag", "IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE." ], [ "4ah", "CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. RELATED INFORMATION #" ], [ "4ai", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker AIX, HP-UX, Linux, Solaris, Windows 8.0 PRODUCT ALIAS/SYNONYM" ], [ "4aj", " WMB IIB" ] ]

[ "4b", "4c", "4d", "4e", "4f", "4g", "4i", "4j", "4k", "4l", "4m", "4n", "4o", "4p", "4q", "4r", "4s", "4t", "4u" ]

[ " FIXES ARE AVAILABLE\nFixes integrated in WebSphere Portal 8.0.0.1 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24034497]\nFixes integrated in WebSphere Portal 7.0.0.1 & 7.0.0.2 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24029452]\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * On two servers, one with Portal 7.0.0.2 CF24 and one with\n 8.0.0.1 CF07.\n Create a library with default content on the 7002 server\n Create a credential vault on the 8001 server\n Open the subscriber portlet on 8001 and create a\n syndicator/subscriber pair for the library created\n The wizard can see the 7002 libraries but fails at the last\n screen with an error\n Errors appear in the logs on both the 7002 and 8001 server.\n \n \n \n \n \n\nLOCAL FIX\n * SydicationWizardHelper in 80 is expecting a attrbute called\n SYND_FAILED_CREATE. It's new in 80. So this cause a NPE when\n syndication 7 to 8. Adding this attribute in the return fix\n this\n issue.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * On two servers, one with Portal 7.0.0.2 CF24 and one with\n 8.0.0.1 CF07.\n Create a library with default content on the 7002 server\n Create a credential vault on the 8001 server\n Open the subscriber portlet on 8001 and create a\n syndicator/subscriber pair for the library created\n The wizard can see the 7002 libraries but fails at the last\n screen with an error\n Errors appear in the logs on both the 7002 and 8001 server.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Fix the NPE on both 7002 and 8001\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM97774\n \n \n * REPORTED COMPONENT NAME\n LOTUS WEB CONT\n \n \n * REPORTED COMPONENT ID\n 5724I2900\n \n \n * REPORTED RELEASE\n 700\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 2013-09-24\n \n \n * CLOSED DATE\n 2013-10-15\n \n \n * LAST MODIFIED DATE\n 2013-10-15\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 LOTUS WEB CONT\n \n \n * FIXED COMPONENT ID\n 5724I2900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R700 PSY\n UP", " \nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * \"PathNotFoundException while syndicating a deleted item\"\n \n \n \n \n \n\nLOCAL FIX\n * NA\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Detailed Problem Description:\n \n The following scenario exhibits the problem:\n Create a new library and create items in the library\n Create a syndicator / subscriber pair and rebuild the syndicator\n Stop portal on both machines\n From <wps>/config on both the syndicator and subscriber run:\n WPSconfig[.sh|.bat] wcm-reset-event-log\n Start portal on both machines\n Rebuild the syndicator\n Update items on the first library and create a second library\n with some items that reference into first library. For example,\n create contents in the second library using authoring templates\n from the first.\n Edit the syndicator to add the new library\n Update the syndicator. The syndication is successful, but the\n following exception appears in the log:\n [6/8/07 3:57:11:797 PDT] 0000003a VersioningSer E\n /7d7c070045a25314879defddc740cc36/0/jcr:versionedNode\n \n javax.jcr.PathNotFoundException:\n /7d7c070045a25314879defddc740cc36/0/jcr:versionedNode\n at com.ibm.icm.jcr.NodeImpl.getNode(NodeImpl.java:1013)\n at com.ibm.icm.jcr.NodeImpl.getNode(NodeImpl.java:926)\n at\n com.ibm.icm.jcr.service.version.VersionServiceImpl.restoreToRela\n tivePath(VersionServiceImpl.java:1226)\n at\n com.ibm.icm.jcr.service.version.VersionImpl.restoreToAbsolutePat\n h(VersionImpl.java:680)\n at\n com.ibm.workplace.wcm.services.versioning.VersioningServiceImpl.\n restoreToAbsolutePath(VersioningServiceImpl.java:2891)\n at\n com.ibm.workplace.wcm.services.versioning.VersioningServiceImpl.\n getDeletedVersionAsControllable(VersioningServiceImpl.java:6226)\n at\n com.ibm.workplace.wcm.services.versioning.VersioningServiceImpl.\n getDeleted(VersioningServiceImpl.java:4883)\n at\n com.ibm.workplace.wcm.services.versioning.VersioningServiceImpl.\n getDeleted(VersioningServiceImpl.java:4773)\n at\n com.ibm.workplace.wcm.services.versioning.VersioningServiceUtils\n .getDeletedForSyndication(VersioningServiceUtils.java:887)\n at\n com.aptrix.deployment.syndicator.ItemDispatcher.fetchItemVersion\n (ItemDispatcher.java:363)\n at\n com.aptrix.deployment.syndicator.ItemDispatcher.fetchItem(ItemDi\n spatcher.java:643)\n at\n com.aptrix.deployment.syndicator.ItemDispatcher.dispatchItem(Ite\n mDispatcher.java:261)\n at\n com.aptrix.deployment.syndicator.ItemDispatcher.process(ItemDisp\n atcher.java:209)\n at\n com.presence.connect.business.module.ModuleManager.launchBusines\n s(ModuleManager.java:121)\n at\n com.presence.connect.business.module.ModuleManager.launchBusines\n s(ModuleManager.java:384)\n at\n com.presence.connect.RequestExecutable.execute(RequestExecutable\n .java:84)\n at com.presence.connect.dispatcher.Task.run(Task.java:151)\n at\n com.presence.connect.ConnectClient.processSynchronous(ConnectCli\n ent.java:167)\n at\n com.presence.connect.ConnectServlet.process(ConnectServlet.java:\n 298)\n at\n com.presence.connect.ConnectServlet.doGet(ConnectServlet.java:12\n 0)\n at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)\n at\n javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled\n Code))\n at\n com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr\n apper.java(Compiled Code))\n at\n com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser\n vletWrapper.java(Compiled Code))\n at\n com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleReques\n t(CacheServletWrapper.java(Compiled Code))\n at\n com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.\n java(Compiled Code))\n at\n com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLin\n k.java(Compiled Code))\n at\n com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscr\n imination(HttpInboundLink.java(Compiled Code))\n at\n com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewIn\n formation(HttpInboundLink.java(Compiled Code))\n at\n com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complet\n e(HttpICLReadCallback.java(Compiled Code))\n at\n com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(Wor\n kQueueManager.java(Compiled Code))\n at\n com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueue\n Manager.java(Compiled Code))\n at\n com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueue\n Manager.java(Compiled Code))\n at\n com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueu\n eManager.java(Compiled Code))\n at\n com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled\n Code))\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Problem Analysis:\n \n Sometimes the base version in the JCR has the same timestamp as\n the first real version. If this is true, the base version will\n be returned when retrieving a version by date. The base version\n is not usable for retrieving the actual versions of WCM items\n and trying to use it in that manner causes the exception.\n \n Failing Module: WCM - Web Content Management (General)\n \n Problem Solution:\n \n If a retrieved version is the base version, the succeeding\n versions are retrieved until one with the same timestamp is\n retrieved.\n \n \n Affected Users: All Users\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PK46689\n \n \n * REPORTED COMPONENT NAME\n WRKPLC WEB CON\n \n \n * REPORTED COMPONENT ID\n 5724I2900\n \n \n * REPORTED RELEASE\n 60A\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 2007-06-07\n \n \n * CLOSED DATE\n 2007-08-30\n \n \n * LAST MODIFIED DATE\n 2007-08-30\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 WRKPLC WEB CON\n \n \n * FIXED COMPONENT ID\n 5724I2900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R601 PSY\n UP\n \n \n * R60C PSY\n UP", "WPv7000eGA; migrating; migrate; migration; V7.0; v7; WCM; out-of-box page; out of the box; page; authoring portlet; may not reach; cannot reach; cannot access; no access; exceptions; IWKAP0009E; Servlet not enabled TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nAfter migrating to IBM WebSphere Portal V7.0, you may not be able to navigate to or display the Web Content Manager (WCM) out-of-box page or the authoring portlet. In addition, some related functions in the user interface might not work or might generate exceptions when accessed. Clicking buttons in the authoring portlet may generate the following error in the log: \n\n * \n * IWKAP0009E: Servlet not enabled\n * \n\n\nIf this occurs, you must re-enable these features manually after migration. \nCAUSE\nThe migration process can disable some new out-of-the-box features if the feature did not exist in the previous release or if it was updated. In particular, the Portal page required for the reserved authoring portlet is missing and the permissions on the AJAX proxy servlet are not set correctly.\n\n\nRESOLVING THE PROBLEM\nTo re-enable the affected features manually after migration, do the following: \n\n\n1. Make sure that the page on which the WCM authoring portlet is installed uses a theme with client-side rendering such as the Page Builder theme.\n\n2. Deploy the hidden Portal page on which the reserved authoring portlet is installed. \n\n\n3. Run the following task from the wp_profile_root / Config Engine directory. \n * Cluster note:\n * \n\n * Windows:\n * \n * \n * ConfigEngine.bat install-wcm-hidden-authoring-page -DWasPassword=\n * password\n * \n * \n * U\n * NIX:\n * \n * ./ConfigEngine.sh install-wcm-hidden-authoring-page -DWasPassword=\n * password\n * \n * \n * i/S\n * y\n * stem\n * :\n * \n * ConfigEngine.sh install-wcm-hidden-authoring-page -DWasPassword=\n * password\n * \n * \n * z/OS \n * \n * :\n * \n * ./ConfigEngine.sh install-wcm-hidden-authoring-page -DWasPassword=\n * password\n \n\nNo restart of the Portal server is required. \n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management IBM Web Content Manager Migration AIX, IBM i, Linux, Solaris, Windows, z/OS 7.0, 6.1", " A FIX IS AVAILABLE\nFixes integrated in WebSphere Portal 8.5.0.0 and V9.0 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24037786]\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * When syndication is used to update an existing item on the\n \n subscriber, the internal UUID of the any element (such as a\n file\n resource element on a content) that already exists on the item\n \n is not updated/corrected to match the corresponding item\n \n resource element from source item on the syndicator.\n \n \n \n Example: If a content contains a file resource element, then\n the\n direct link to the file attachment from both the syndicator and\n subscriber server may not match (as the resource URL is based\n on\n the internal ID of the resource element itself).\n \n \n \n If the corresponding item on the subscriber does not contain an\n element with the same name or the actual item itself does not\n \n exist at all on the subscriber server, then syndication will\n add\n the element correctly to the target item with the same matching\n internal UUID.\n \n \n \n Note: Syndication will always preserve the internal UUID for\n \n elements and resources. If a library export/import is performed\n or was used in the past to populate the server with initial\n \n data, then the internal resource UUID will not be preserved.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * When syndication is used to update an existing item on the\n subscriber, the internal UUID of the any element (such as a file\n resource element on a content) that already exists on the item\n is not updated/corrected to match the corresponding item\n resource element from source item on the syndicator.\n \n \n Example: If a content contains a file resource element, then the\n direct link to the file attachment from both the syndicator and\n subscriber server may not match (as the resource URL is based on\n the internal ID of the resource element itself).\n \n \n \n If the corresponding item on the subscriber does not contain an\n element with the same name or the actual item itself does not\n exist at all on the subscriber server, then syndication will add\n the element correctly to the target item with the same matching\n internal UUID.\n \n \n Note: Syndication will always preserve the internal UUID for\n elements and resources. If a library export/import is performed\n or was used in the past to populate the server with initial\n data, then the internal resource UUID will not be preserved.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * A code fix for this issue is integrated into the WebSphere\n Portal & WCM Combined Cumulative Fix 14 (PI73835 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI73835]) for Portal 8.5\n and 9.0 available from Fix Central:\n \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=PI73835\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI80562\n \n \n * REPORTED COMPONENT NAME\n LOTUS WEB CONT\n \n \n * REPORTED COMPONENT ID\n 5724I2900\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 2017-04-26\n \n \n * CLOSED DATE\n 2017-06-27\n \n \n * LAST MODIFIED DATE\n 2017-06-27\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 LOTUS WEB CONT\n \n \n * FIXED COMPONENT ID\n 5724I2900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R850 PSY\n UP", " FIXES ARE AVAILABLE\n6.1.0.1 Download: WebSphere Portal and Web Content Management V6.1, fix pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24020387]\n6.1.0.2 Download: WebSphere Portal and Web Content Management V6.1, fix pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24022898]\n6.1.0.3 Download: WebSphere Portal and WCM V6.1 fix pack 3, 6.1.5 feature pack [http://www-01.ibm.com/support/docview.wss?uid=swg24025054]\n6.1.0.4 Download: WebSphere Portal and WCM V6.1.0 fix pack 4 & 6.1.5 fix pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24026394]\n6.1.0.5 Download: WebSphere Portal and WCM V6.1.0 fix pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24027475]\n6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24030970]\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * During All item syndication, draft items are failing to\n syndicate correctly (changes to draft not reflected on\n subscriber, draft not being removed on subscriber after\n publish on syndicator, ect.)\n ..\n Affected USERS: All\n ..\n The WCM code has been updated to check the last modified date of\n the draft if no draft exists it will then use the published\n content's date.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * Syndication does not syndicate draft updates if there is a\n published version of the content.\n ..\n AFFECTED USERS: ALL\n .\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Updates to draft content that have a published version do not\n get syndicated even when 'all items' syndication is used.\n Create and Delete of the draft get syndicated but updates to the\n same draft content do not get syndicated.\n .\n The code is using the published contents last modified date\n rather than the draft contents last modified date. When package\n generator builds the package it first checks for a create date\n on a non-draft then a draft. It should check the draft first\n because if a draft exists an update would have to be performed\n on the draft and not the live content.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PK72557\n \n \n * REPORTED COMPONENT NAME\n LOTUS WEB CONT\n \n \n * REPORTED COMPONENT ID\n 5724I2900\n \n \n * REPORTED RELEASE\n 60H\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 2008-09-22\n \n \n * CLOSED DATE\n 2008-09-23\n \n \n * LAST MODIFIED DATE\n 2008-09-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\nMODULES/MACROS\n * WCM\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n LOTUS WEB CONT\n \n \n * FIXED COMPONENT ID\n 5724I2900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R60H PSY\n UP\n \n \n * R610 PSY\n UP" ]

[ [ "0a", " FIXES ARE AVAILABLE" ], [ "0b", "Fixes integrated in WebSphere Portal 8.0.0.1 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24034497]" ], [ "0c", "Fixes integrated in WebSphere Portal 7.0.0.1 & 7.0.0.2 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24029452] APAR STATUS" ], [ "0d", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "0e", " * On two servers, one with Portal 7.0.0.2 CF24 and one with" ], [ "0f", " 8.0.0.1 CF07." ], [ "0g", " Create a library with default content on the 7002 server" ], [ "0h", " Create a credential vault on the 8001 server" ], [ "0i", " Open the subscriber portlet on 8001 and create a" ], [ "0j", " syndicator/subscriber pair for the library created" ], [ "0k", " The wizard can see the 7002 libraries but fails at the last" ], [ "0l", " screen with an error" ], [ "0m", " Errors appear in the logs on both the 7002 and 8001 server. LOCAL FIX" ], [ "0n", " * SydicationWizardHelper in 80 is expecting a attrbute called" ], [ "0o", " SYND_FAILED_CREATE." ], [ "0p", "It's new in 80." ], [ "0q", "So this cause a NPE when" ], [ "0r", " syndication 7 to 8." ], [ "0s", "Adding this attribute in the return fix" ], [ "0t", " this" ], [ "0u", " issue. PROBLEM SUMMARY" ], [ "0v", " * On two servers, one with Portal 7.0.0.2 CF24 and one with" ], [ "0w", " 8.0.0.1 CF07." ], [ "0x", " Create a library with default content on the 7002 server" ], [ "0y", " Create a credential vault on the 8001 server" ], [ "0z", " Open the subscriber portlet on 8001 and create a" ], [ "0aa", " syndicator/subscriber pair for the library created" ], [ "0ab", " The wizard can see the 7002 libraries but fails at the last" ], [ "0ac", " screen with an error" ], [ "0ad", " Errors appear in the logs on both the 7002 and 8001 server. PROBLEM CONCLUSION" ], [ "0ae", " * Fix the NPE on both 7002 and 8001 TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "0af", " * APAR NUMBER" ], [ "0ag", " PM97774" ], [ "0ah", " * REPORTED COMPONENT NAME" ], [ "0ai", " LOTUS WEB CONT" ], [ "0aj", " * REPORTED COMPONENT ID" ], [ "0ak", " 5724I2900" ], [ "0al", " * REPORTED RELEASE" ], [ "0am", " 700" ], [ "0an", " * STATUS" ], [ "0ao", " CLOSED PER" ], [ "0ap", " * PE" ], [ "0aq", " NoPE" ], [ "0ar", " * HIPER" ], [ "0as", " NoHIPER" ], [ "0at", " * SPECIAL ATTENTION" ], [ "0au", " NoSpecatt" ], [ "0av", " * SUBMITTED DATE" ], [ "0aw", " 2013-09-24" ], [ "0ax", " * CLOSED DATE" ], [ "0ay", " 2013-10-15" ], [ "0az", " * LAST MODIFIED DATE" ], [ "0ba", " 2013-10-15" ], [ "0bb", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "0bc", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "0bd", " * FIXED COMPONENT NAME" ], [ "0be", " LOTUS WEB CONT" ], [ "0bf", " * FIXED COMPONENT ID" ], [ "0bg", " 5724I2900" ], [ "0bh", "APPLICABLE COMPONENT LEVELS" ], [ "0bi", " * R700 PSY" ], [ "0bj", " UP" ] ]

[ "0n", "0o", "0p", "0q", "0r", "0s" ]

[ "ITM Virtual environments install NMA N4 unable find bundle prerequisites CI addbundles TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The installation of NMA agent from package ITM for Virtual Environment V7.2.0.3 is failing with both remote or local installation on Linux x86-64. \n\nSYMPTOM\n1) The import of the whole bundle using command: \n\n/opt/IBM/ITM/bin/tacmd addbundles -i <inst_media>/ITMfVE_Agents/unix\n\nwill fail with message:\n\nUnable to find bundle prerequisite: ci 06.22.04.000 li6263\n\n--\n\n2) Even if you succeed in importing the bundle, the remote deploy of N4 agent on a Linux X86_64 fails because the installer recognizes the target node as a 64bit while the agent comes with a different architecture (li6263).\n\n--\n\n3) If you try to install the ITM for VE agents locally on a Linux x86_64, the usual installation procedure does not work for the same reason of point 2.\nThe installer recognizes the target node as a 64bit platform and the agents are 32bit and so it does not show the expected list of agents.\n\n\nCAUSE\nThe causes for the three scenarios depends on wrong prerequisite levels packaged into ITM for VE 7.2.0.3 for NMA agent, and on unexpected architecture recognized by the installer when trying to install the agent on the target node, if this one is a Linux x86-64.\n\n\nRESOLVING THE PROBLEM\nThe issues should be corrected at Installer level, APAR IV84919 has been opened to fix them. \n\nAnyway, since the correction involves the installation component, it will not be available until next release, when the Installation package will be built again. \n\nUntil then, you can bypass the issue with some manual steps. \n\n--------------- \n\n1) If the import of agent bundle using command tacmd addbundles fails with message: \n\nUnable to find bundle prerequisite: ci 06.22.04.000 li6263\n\nthis occurs because some agents, particularly N4 agent, have old prerequisites for shared components (ax, ui, gs,jr) that are not part of the ITM_for_VE bundle. \n\nThere is actually a workaround to correctly import the bundle in the depot, but it will not be of any help because remote installation of N4 agent will then fail due to the problem described in item number 2. \n\nIt can be anyway useful to know the workaround as it can be applied to other agents for which remote installation instead correctly works.\n\nYou must verify if the prerequisites mentioned in the error message are already present in your depot by using command tacmd viewdepot.\nBeside of the one mentioned in the error message, you must be sure that also the other wanted prerequisites are already present in the depot.\n\nN4 agent has the following prerequisites:\n\nProduct Code : n4 \nDeployable : True \nVersion : 062200000 \nDescription : Monitoring Agent for Network Devices \nHost Type : li6263 \nHost Version : li6263,lx8266 \nPrerequisites: ci:062204000 la:ipaddr05400 gs:074027000 jr:051201000 \nui:062204000 ax:062204000\n\nIf all of them are already in the depot, then you can run the tamcd addbundles using flag \"-n\" (ignore prerequisites), this will allow to correctly import the agent bundle.\n\nIf you do not have the wanted prerequisite levels, you have two possible options:\n\na) retrieve and add them into depot from other ITM installation packages\nb) modify the agent dsc files and change the level of the components required by the agent to match the level delivered with the bundle.\n\nFor example, ITM for Virtual Environment 7.2.0.3 delivers CI component at level 06.30.05.000, so if we consider N4 agent, you may need to change the file n4li6263.dsc in the rows:\n\n<PrereqProdCode>ci</PrereqProdCode>\n\n<PrereqVersion>\n\n<Version>06</Version>\n\n<Release>22</Release>\n\n<Mod>04</Mod>\n\n<Level>000</Level>\n\n\nto \n\n\n<PrereqProdCode>ci</PrereqProdCode>\n\n<PrereqVersion>\n\n<Version>06</Version>\n\n<Release>30</Release>\n\n<Mod>05</Mod>\n\n<Level>000</Level> \n\n \n\nThe same for other components in case they are also missing from your depot. \n\nThe dsc files are into <installation_media>/ITMfVE_Agents/unix folder. \n\nRepeat the tacmd addbundles command and it should now work fine. \n\nAs previously said, please consider that this scenario may occur also for agents different than N4, and the workaround is applicable also for them. \n\nOf course the target dsc file name changes accordingly to the agent type and related architecture. \n\n \n\n2) The above workaround can help in case the issue is only related to backleveled prerequisite packages. \n\nAnyway, once you applied it, if the target node for the N4 agent is a Linux x86-64, you will anyway not be able to install it remotely.\nThe remote deploy of N4 agent on a Linux X86_64 fails because the installer recognizes the target node as a 64bit while the agent comes with a different architecture (li6263). \nThe quickest workaround in this case is to install the agent locally.\n\n3) If you try to install the ITM for VE agents locally on a Linux x86_64, the usual installation procedure does not work for the same reason of point 2. \nThe installer recognizes the target node as a 64bit platform and the agents are 32bit. \nSo the installer menu will show no available agents to be installed.\n\nYou need to proceed as follow:\n\na) Run the local installation of N4 agent on target machine and proceed as usual when you are prompted with Installer initial questions.\nb) Select Other operating systems when you are showed this panel\n\n[/support/docview.wss?uid=swg21983839&aid=1] [/support/docview.wss?uid=swg21983839&aid=1]\n\nc) Then select Linux Intel R2.6 R3.0 (32 bit)\n\n[/support/docview.wss?uid=swg21983839&aid=2] [/support/docview.wss?uid=swg21983839&aid=2]\n\nd) At this point you will see the list of agents that can be installed on the machine. Select the option for the n4 agent and installation will be completed successfully\n\n[/support/docview.wss?uid=swg21983839&aid=3] [/support/docview.wss?uid=swg21983839&aid=3]\n\n \n\nPRODUCT ALIAS/SYNONYM\n IBM Tivoli Monitoring for Virtual Environments V7.2.0.3", "5724C04LN TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Does IBM Tivoli Monitoring OS agent for Linux support Red Hat Enterprise Linux Server 7? \n\nENVIRONMENT\nITM 6.3, 6.23\n\nRESOLVING THE PROBLEM\nYes, ITM OS agent version 6.30 Fix Pack 3 is certified on Red Hat Enterprise Linux Server 7 \n\nRed Hat Enterprise Linux Server 7 support requires additional steps and/or prerequisites before installing IBM Tivoli Monitoring Version 6.3.0 Fix Pack 3\n\nNote: There is an issue with the compat-libstdc++-33-3.2.3-71.el7 version that currently ships with Red Hat Enterprise Linux Server 7 that affects agents on platforms pSeries and zSeries and some 32 bit agents on x86_64. Until Red Hat provides an update the compat-libstdc++-33.xxx libraries from Red Hat Enterprise Linux Server 6.4 or later should be used.\n\n- IBM Tivoli Monitoring Version 6.3.0 Fix Pack 3 is upgrade install only. In order to initially install IBM Tivoli Monitoring, obtain the IBM Tivoli Monitoring Version 6.3.0 Fix Pack 2 pristine installation media. (Passport Advantage: Part number CIQ3QML). This is specified in the User Guide: http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/dld_itm63fp2.htm [http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/dld_itm63fp2.htm]\n\n- Before installing from the V6.3.0.2 media, run the following from the command line:\nsetarch $(uname -m) --uname-2.6\n\nNote: This will put you in a special shell where \"uname -r\" should show \"2.6.xxxx\" for kernel version\n\n- Install and configure IBM Tivoli Monitoring Version 6.3.0 Fix Pack 2. You will get a prerequisites failure for the Operating System, but you can ignore the failure and continue installation. Once complete you can now exit from the special shell (just type exit on the command line) and then upgrade to 6.3.0 Fix Pack 3 as per normal upgrade install.\n\nNote: Remote Deploy of 6.3.0 Fix Pack 3 OS agent should work without any special steps but the compat-libstdc++-33.xxx issue still applies for pSeries and zSeries.\n\nIn addition to this, ITM OS agent version 6.23 Fix Pack 3 is certified on Red Hat Enterprise Linux Server 7 as well. However, it is recommended that customer use 6.30 Fix Pack 3.\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management IBM Tivoli Monitoring V6", "ITCAM; J2EE; uplift; Refresh Pack; prerequisites; CAMJ2ALL; CAMJ2INST TECHNOTE (FAQ)\n\nQUESTION\n When trying to install 7.1.1-TIV-ITCAM_J2EE-Windows-RP001 on a Windows 2008 R2 64-bit, the installation returns the following error popup message:\nThe Agent Compatibility Package in version 06230400 is required but unavailable.\nHow can I solve this? \n\nCAUSE\nThe Agent Compatibility Package is not bundled with ITCAM for J2EE 7.1.1.\nThe Agent Compatibility Package is not installed on the involved server, or it is of a version older than the one required.\nITM 6.2.3 FP4 is the minimum prerequisite ITM version supported with ITCAM for J2EE agent v7.1.1.\n\nE.g. if you have ITM 6.2.3 FP1 components installed, you will have this component installed:\n\nAC 32/64 Bit Agent Compatibility Package\nWIX64 Version: 06.23.01.00 Build: 201202220943\n\nbesides other Windows 64-bit ITM components, and you will get this error message.\n\n\nANSWER\nThe AC component can be found on the Agents DVD. \n\n\nComplete the following steps on the 64-bit Windows system where a 64-bit agent is installed: \n1. Locate the installation media for IBM Tivoli Monitoring V6.2.3 FP4 (or later). \n\n2. From the WINDOWS subdirectory of the Tivoli Monitoring installation media, run setup.exe. The installation wizard starts. \n\n3. On the Select Features page, leave all of the existing check boxes selected. The following two components are selected by default: \n\n \n\n * 32/64 Bit Agent Compatibility Package (x86-64 only) \n * Tivoli Enterprise Monitoring Agent Framework (x86-64 only)\n\n\nIBM recommends you install the AC component at the same version as the Windows OS agent (component code NT). \n\n4. Follow the instructions on the Tivoli Monitoring installation wizard to complete the installation of the agent compatibility package. \n\n5. Run the ITCAM for J2EE 7.1.1 installation wizard to complete the installation of ITCAM for J2EE. \n\nImportant: You can install the agent compatibility package from any media where it is bundled, but the version that is installed must be equal to or greater than V6.2.3 Fix Pack 4. \n\nYou can also refer to the following documentation link for further details: \nhttp://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/install/acpinstall.htm?cp=SSTFXA_6.3.0&lang=en [http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/install/acpinstall.htm?cp=SSTFXA_6.3.0&lang=en]", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DOCUMENTATION ERROR.\n \n \n \n\nERROR DESCRIPTION\n * A change is required to the ICO 2.4.0.1 Installation/Integration\n documentation, Installing IBM Tivoli Monitoring, \"Packages\n Used for Installation\":\n \n http://www-01.ibm [http://www-01.ibm]\n .com/support/knowledgecenter/SS4KMC_2.4.0.1/com.ibm.sco.doc_2\n .4/r_itm_packages.html?lang=en\n \n The part number for the following package is incorrect:\n \n CIL2AEN - IBM Tivoli Monitoring V6.3.0.1 Base, Linux (64-bit\n Env.), English\n \n The part number: CIL2AEN does not match the description listed\n here:\n http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.i\n bm.itm.doc_6.3/dld_itm63fp1.htm [http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/dld_itm63fp1.htm]\n \n CIL2AEN needs to be changed to CIL2CEN in the ICO doc.\n \n i.e.\n \n CIL2CEN - IBM Tivoli Monitoring V6.3.0.1 Base, Linux (64-bit\n Env.), English\n \n \n \n \n \n\nLOCAL FIX\n * N/A\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM Cloud Orchestrator 2.4\n ****************************************************************\n * PROBLEM DESCRIPTION:\n ITM part numbers are incorrect.\n \n ICO Enterprise Edition 2.4.0.1 is bundling ITM 6.3.0.2 (not\n 6.3.0.1).\n All references to ITM part numbers need review.\n \n ****************************************************************\n * RECOMMENDATION:\n Review the next update of IBM Cloud Orchestrator 2.4\n Installation and Administration Guide and Information Center\n when available.\n \n The documentation changes can also be found in the conclusion\n section below.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * You need several packages to install IBM&#169; Tivoli&#169; Monitoring\n 6.3.0.2. All of its components can also be installed in silent\n mode.\n \n The following packages are required to install IBM Tivoli\n Monitoring 6.3.0.2:\n \n CIQ3JEN - IBM Tivoli Monitoring V6.3.0.2 Base, Linux (64-bit\n Env.), English\n \n CIQ3PML - IBM Tivoli Monitoring V6.3.0.2 Dashboards for Servers\n and Authorization Policy Components Assembly Multiplatform,\n Multilingual\n \n CIQ3MML - IBM Tivoli Monitoring V6.3.0.2 Language Support\n Multiplatform Multilingual\n \n Monitoring Agent for Linux\n \n To monitor the entire IBM&#169; Cloud Orchestrator environment,\n install Monitoring Agent on each Linux computer and configure it\n with the host name of your Tivoli Enterprise Monitoring Server.\n \n For more information about installing the operating system\n agents, see Installing monitoring agents.\n \n The operating system agents are delivered with the following\n package:\n \n CIQ3QML - IBM Tivoli Monitoring V6.3.0.2 Agents, Multiplatform,\n Multilingual\n \n The KVM agent requires the following packages:\n \n CIQ4HEN - IBM Tivoli Monitoring for Virtual Environments\n V7.2.0.2 VMware VI, KVM, NetApp Storage and NMA Agents and\n Support Files, Windows and Linux, English, Multiplatform\n \n CIQ4JML - IBM Tivoli Monitoring for Virtual Environments\n V7.2.0.2 Agent Language Pack, Multiplatform, Multilingual\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n ZZ00347\n \n \n * REPORTED COMPONENT NAME\n SMRTCLOUD ORCHS\n \n \n * REPORTED COMPONENT ID\n 5725H2800\n \n \n * REPORTED RELEASE\n 240\n \n \n * STATUS\n CLOSED DOC\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-09\n \n \n * CLOSED DATE\n 2015-02-11\n \n \n * LAST MODIFIED DATE\n 2015-02-11\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\nAPPLICABLE COMPONENT LEVELS", "5724V09ORTR; 5724V09OR TECHNOTE (FAQ)\n\nQUESTION\n For agent depot located on Unix system, what are the steps to add ITCAM Extended agent for Oracle, V6.3.1 (product code RZ) bundles for Unix and Windows platforms? \n\nCAUSE\nThe steps to add agent bundles for Unix and Windows platforms are different.\n\nANSWER\n \n\nI) Steps to add bundles for Unix and Linux platforms:\n\nUse install.sh in the Extended Oracle Agent V6.3.1 product CD and select following option:\n\n2) Install products to depot for remote deployment (requires TEMS).\n\nPlease enter a valid number: 2\n\nA list of products available for remote deployment will be displayed. Navigate using \"F) Forward page\" option to display the list of RZ agent bundles for Unix platforms. Note that this list does not include agent bundle for Windows platform. See section II) for adding Windows bundles.\nSelect options you want to install from the displayed list and follow prompts to install the required bundles.\n\nThe following product packages are available for depot installation:\n\nCode Decription(version) [base platform:supported platforms]\n\n1) ax IBM Tivoli Monitoring Shared Libraries(06.22.02.000) [aix523:aix523,aix533]\n2) ax IBM Tivoli Monitoring Shared Libraries(06.22.02.000) [aix526:aix526,aix536]\n...\n\n42) rz Monitoring Agent for Oracle Database Extended(06.31.00.000) [aix523:aix523,aix533]\n...\n53) rz Monitoring Agent for Oracle Database Extended(06.31.00.000) [sol606:sol606]\n\nII) Steps to add bundles for Windows platform:\n\nAgent bundles for Windows platform are located in WINDOWS/Deploy directory in the CD image. Use tacmd addbundles command specifying path to Windows bundle with '-i' option on the command line. For example:\n\n[root]:CZJ9CML>/opt/IBM/ITM/bin/tacmd addbundles -i ./WINDOWS/Deploy -t rz\n\nKUICAB023I: Are you sure you want to add the following bundles to the /opt/IBM/ITM/tables/HUBCAM/depot depot?\n\nProduct Code : RZ\nDeployable : True\nVersion : 063100000\nDescription : Monitoring Agent for Oracle Database Extended\nHost Type : WIX64\nHost Version : WIX64\nPrerequisites:\n\nProduct Code : RZ\nDeployable : True\nVersion : 063100000\nDescription : Monitoring Agent for Oracle Database Extended\nHost Type : WINNT\nHost Version : WINNT\nPrerequisites:\n\nKUICAB024I: Enter Y for yes or N for no: Y\n\nKUICAB020I: Adding bundles to the /opt/IBM/ITM/tables/HUBCAM/depot depot. The time required to complete this operation depends on the number and size of the added bundles.\n\nKUICAB022I: The following bundles were successfully added to the /opt/IBM/ITM/tables/HUBCAM/depot depot:\n\nProduct Code : RZ\nDeployable : True\nVersion : 063100000\nDescription : Monitoring Agent for Oracle Database Extended\nHost Type : WIX64\nHost Version : WIX64\nPrerequisites:\n\nProduct Code : RZ\nDeployable : True\nVersion : 063100000\nDescription : Monitoring Agent for Oracle Database Extended\nHost Type : WINNT\nHost Version : WINNT" ]

[ [ "0a", "ITM Virtual environments install NMA N4 unable find bundle prerequisites CI addbundles TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "0b", " The installation of NMA agent from package ITM for Virtual Environment V7.2.0.3 is failing with both remote or local installation on Linux x86-64. SYMPTOM" ], [ "0c", "1) The import of the whole bundle using command:" ], [ "0d", "/opt/IBM/ITM/bin/tacmd addbundles -i <inst_media>/ITMfVE_Agents/unix" ], [ "0e", "will fail with message:" ], [ "0f", "Unable to find bundle prerequisite: ci 06.22.04.000 li6263 --" ], [ "0g", "2) Even if you succeed in importing the bundle, the remote deploy of N4 agent on a Linux X86_64 fails because the installer recognizes the target node as a 64bit while the agent comes with a different architecture (li6263). --" ], [ "0h", "3) If you try to install the ITM for VE agents locally on a Linux x86_64, the usual installation procedure does not work for the same reason of point 2." ], [ "0i", "The installer recognizes the target node as a 64bit platform and the agents are 32bit and so it does not show the expected list of agents. CAUSE" ], [ "0j", "The causes for the three scenarios depends on wrong prerequisite levels packaged into ITM for VE 7.2.0.3 for NMA agent, and on unexpected architecture recognized by the installer when trying to install the agent on the target node, if this one is a Linux x86-64." ], [ "0k", "RESOLVING THE PROBLEM" ], [ "0l", "The issues should be corrected at Installer level, APAR IV84919 has been opened to fix them." ], [ "0m", "Anyway, since the correction involves the installation component, it will not be available until next release, when the Installation package will be built again." ], [ "0n", "Until then, you can bypass the issue with some manual steps. ---------------" ], [ "0o", "1) If the import of agent bundle using command tacmd addbundles fails with message:" ], [ "0p", "Unable to find bundle prerequisite: ci 06.22.04.000 li6263" ], [ "0q", "this occurs because some agents, particularly N4 agent, have old prerequisites for shared components (ax, ui, gs,jr) that are not part of the ITM_for_VE bundle." ], [ "0r", "There is actually a workaround to correctly import the bundle in the depot, but it will not be of any help because remote installation of N4 agent will then fail due to the problem described in item number 2." ], [ "0s", "It can be anyway useful to know the workaround as it can be applied to other agents for which remote installation instead correctly works." ], [ "0t", "You must verify if the prerequisites mentioned in the error message are already present in your depot by using command tacmd viewdepot." ], [ "0u", "Beside of the one mentioned in the error message, you must be sure that also the other wanted prerequisites are already present in the depot." ], [ "0v", "N4 agent has the following prerequisites:" ], [ "0w", "Product Code : n4" ], [ "0x", "Deployable : True" ], [ "0y", "Version : 062200000" ], [ "0z", "Description : Monitoring Agent for Network Devices" ], [ "0aa", "Host Type : li6263" ], [ "0ab", "Host Version : li6263,lx8266" ], [ "0ac", "Prerequisites: ci:062204000 la:ipaddr05400 gs:074027000 jr:051201000 ui:062204000 ax:062204000" ], [ "0ad", "If all of them are already in the depot, then you can run the tamcd addbundles using flag \"-n\" (ignore prerequisites), this will allow to correctly import the agent bundle." ], [ "0ae", "If you do not have the wanted prerequisite levels, you have two possible options:" ], [ "0af", "a) retrieve and add them into depot from other ITM installation packages" ], [ "0ag", "b) modify the agent dsc files and change the level of the components required by the agent to match the level delivered with the bundle." ], [ "0ah", "For example, ITM for Virtual Environment 7.2.0.3 delivers CI component at level 06.30.05.000, so if we consider N4 agent, you may need to change the file n4li6263.dsc in the rows: <PrereqProdCode>ci</PrereqProdCode> <PrereqVersion> <Version>06</Version> <Release>22</Release> <Mod>04</Mod> <Level>000</Level> to <PrereqProdCode>ci</PrereqProdCode> <PrereqVersion> <Version>06</Version> <Release>30</Release> <Mod>05</Mod> <Level>000</Level>" ], [ "0ai", "The same for other components in case they are also missing from your depot." ], [ "0aj", "The dsc files are into <installation_media>/ITMfVE_Agents/unix folder." ], [ "0ak", "Repeat the tacmd addbundles command and it should now work fine." ], [ "0al", "As previously said, please consider that this scenario may occur also for agents different than N4, and the workaround is applicable also for them." ], [ "0am", "Of course the target dsc file name changes accordingly to the agent type and related architecture." ], [ "0an", "2) The above workaround can help in case the issue is only related to backleveled prerequisite packages." ], [ "0ao", "Anyway, once you applied it, if the target node for the N4 agent is a Linux x86-64, you will anyway not be able to install it remotely." ], [ "0ap", "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)." ], [ "0aq", "The quickest workaround in this case is to install the agent locally." ], [ "0ar", "3) If you try to install the ITM for VE agents locally on a Linux x86_64, the usual installation procedure does not work for the same reason of point 2." ], [ "0as", "The installer recognizes the target node as a 64bit platform and the agents are 32bit." ], [ "0at", "So the installer menu will show no available agents to be installed." ], [ "0au", "You need to proceed as follow:" ], [ "0av", "a) Run the local installation of N4 agent on target machine and proceed as usual when you are prompted with Installer initial questions." ], [ "0aw", "b) Select Other operating systems when you are showed this panel [/support/docview.wss?uid=swg21983839&aid=1] [/support/docview.wss?uid=swg21983839&aid=1]" ], [ "0ax", "c) Then select Linux Intel R2.6 R3.0 (32 bit) [/support/docview.wss?uid=swg21983839&aid=2] [/support/docview.wss?uid=swg21983839&aid=2]" ], [ "0ay", "d) At this point you will see the list of agents that can be installed on the machine." ], [ "0az", "Select the option for the n4 agent and installation will be completed successfully [/support/docview.wss?uid=swg21983839&aid=3] [/support/docview.wss?uid=swg21983839&aid=3] PRODUCT ALIAS/SYNONYM" ], [ "0ba", " IBM Tivoli Monitoring for Virtual Environments V7.2.0.3" ] ]

[ "0a", "0b", "0c", "0d", "0e", "0f", "0g", "0h", "0i", "0j", "0k", "0l", "0m", "0n", "0o", "0p", "0q", "0r", "0s", "0t", "0u", "0v", "0w", "0x", "0y", "0z", "0aa", "0ab", "0ac", "0ad", "0ae", "0af", "0ag", "0ah", "0ai", "0aj", "0ak", "0al", "0am", "0an", "0ao", "0ap", "0aq", "0ar", "0as", "0at", "0au", "0av", "0aw", "0ax", "0ay", "0az", "0ba" ]

[ "upgrade; migrate; CLM; DNG; RQM; RTC; RRC; DOORS; Team Concert; Quality Manager; repotools; addTables; reindex; finalizeApplicationMigration; suspendIndexer; resumeIndexer TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n CRJAZ1143I errors are shown in the command console as well as repotools logs when attempting to execute any repotools commands in in IBM Rational Collaborative Lifecycle Management (CLM). \n\nSYMPTOM\nThe following error is observed in the console and in the repotools log file. The error is not specific to the bundle below and may reference other bundles. \n\n\n2015-12-31 01:27:21,347 CRJAZ1143I Failed to register OSGi services for descriptor: ServiceProviderElementDescriptor@28152815, implementationClass=\"com.ibm.team.repository.service.internal.XFrameOptionsService\", bundle=\"com.ibm.team.repository.service\", componentId=\"com.ibm.team.repository\", startPolicy=<EARLY>.\njava.lang.NoClassDefFoundError: net.jazz.ajax.IXFrameOptionsService\nat java.lang.ClassLoader.defineClassImpl(Native Method)\nat java.lang.ClassLoader.defineClass(ClassLoader.java:287)\n\n\n\nCAUSE\nThe error may be caused by one of two things:\n\n1) An iFix was applied to the server and repotools was not reprovisioned\n2) An incomplete/corrupt installation of the software\n\n\nRESOLVING THE PROBLEM\nThe problem can usually be resolved by executing the repotools-<app> -clean command for the application returning the error. For example: \n\n \n\nWindows: \n\n\nrepotools-rm.bat -clean \n\nrepotools-jts.bat -clean \n\nrepotools-ccm.bat -clean \n\nrepotools-qm.bat -clean\n\n\n\n\n \n\nLinux/UNIX: \n\n\n./repotools-rm.sh -clean \n\n./repotools-jts.sh -clean \n\n./repotools-ccm.sh -clean \n\n./repotools-qm.sh -clean\n\n\n\n\n \n\nIf the problem is not resolved after running repotools -clean, a new installation may be required to resolve the problem. \n\nUsually if the problem is related to an incomplete/corrupted installation directory, it will prevent you from completing a successful configuration. If you believe the installation is corrupt on a system that has previously been configured successfully and contains important data, please contact support [http://www-01.ibm.com/software/rational/support/contact.html] for recommendations before attempting an uninstall/re-install.", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The installation log contains one or more UTLS0002E error messages and FFDC events indicating a shared library JAR supporting Installed Optional Packages could not be resolved when installing an application on a multiple node network deployment, where the Deployment Manager and the target Application Server(s) are hosted by different nodes. \n\nSYMPTOM\nWhen installing an application into a multiple node network deployment, where the Deployment Manager and the target Application Server(s) are hosted by different nodes, the installation log will contain messages similar to the one below whenever the target Application Server configuration contains shared libraries, and the paths to the JARs configured in the shared library class path do not exist on the Deployment Manager. \n\nUTLS0002E: The shared library IBM_BPM_Process_Server_Shared_Library contains a classpath entry which does not resolve to a valid jar file, the library jar file is expected to be found at /home/svtuser/IBM/WebSphere/AppServer/BPM/Lombardi/process-server/lib/procsrv_resources.jar.\n\nThe error message is emitted along with the following FFDC call stack indicating the application install task is processing an Installed Optional Packages configured for the application. \n\n[2/26/13 6:11:25:624 CST] 0000005e ModuleManifes 3 Exception:\njava.util.zip.ZipException: error in opening zip file\nat java.util.zip.ZipFile.open(Native Method)\nat java.util.zip.ZipFile.<init>(ZipFile.java:150)\nat java.util.jar.JarFile.<init>(JarFile.java:149)\nat java.util.jar.JarFile.<init>(JarFile.java:86)\nat com.ibm.ws.runtime.ModuleManifestParser.addInstalledOptionalPackages(ModuleManifestParser.java:218)\nat com.ibm.ws.management.application.task.InstalledOptionalPackageTask.buildMap(InstalledOptionalPackageTask.java:321)\nat com.ibm.ws.management.application.task.InstalledOptionalPackageTask.install(InstalledOptionalPackageTask.java:187)\nat com.ibm.ws.management.application.task.InstalledOptionalPackageTask.performTask(InstalledOptionalPackageTask.java:115)\nat com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:315)\nat com.ibm.ws.management.application.AppManagementImpl.runScheduler(AppManagementImpl.java:2820)\nat com.ibm.ws.management.application.AppManagementImpl._installApplicationAsSystem(AppManagementImpl.java:395)\nat com.ibm.ws.management.application.AppManagementImpl.access$100(AppManagementImpl.java:131)\nat com.ibm.ws.management.application.AppManagementImpl$2.run(AppManagementImpl.java:340)\nat com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:5453)\nat com.ibm.ws.security.auth.ContextManagerImpl.runAsSpecified(ContextManagerImpl.java:5544)\nat com.ibm.ws.management.application.AppManagementImpl._installApplication(AppManagementImpl.java:338)\nat com.ibm.ws.management.application.AppManagementImpl.installApplicationLocal(AppManagementImpl.java:303)\nat com.ibm.ws.management.bla.util.J2EEManagementOp.installJ2EEApp(J2EEManagementOp.java:89)\nat com.ibm.ws.management.bla.content.steps.SaveCompUnit._performJ2EEOp(SaveCompUnit.java:473)\nat com.ibm.ws.management.bla.content.steps.SaveCompUnit.execute(SaveCompUnit.java:134)\nat com.ibm.wsspi.management.bla.op.compound.Phase.execute(Phase.java:151)\nat com.ibm.wsspi.management.bla.op.compound.CompoundOperation._doPhaseExecute(CompoundOperation.java:102)\nat com.ibm.wsspi.management.bla.op.compound.CompoundOperation.doExecute(CompoundOperation.java:85)\nat com.ibm.wsspi.management.bla.op.Operation.execute(Operation.java:158)\nat com.ibm.wsspi.management.bla.op.compound.CompoundOperation.execute(CompoundOperation.java:68)\nat com.ibm.ws.management.bla.commands.ADTCommand$OperationScheduler.run(ADTCommand.java:616)\nat java.lang.Thread.run(Thread.java:772)\n\nThe error messages appearing in the above stack context should be ignored whenever the application does not use Installed Optional Packages. In the event the application does use Installed Optional Packages, the error messages are valid and the resulting application deployment will lack the shared library references required to make the packages within the library JARs visible to the application at runtime. This is a current limitation that will be resolved in future releases.\n\n\nCAUSE\nThe symptom occurs whenever the paths declared in the class path of a shared library configured on a target Application Server do not exist on the Deployment Manager.\n\n\nRESOLVING THE PROBLEM\nThe problem can be resolved by deploying the shared library JARs into the same absolute path on both the Deployment Manager and the target Application Server(s) nodes.\n\nRELATED INFORMATION\n#WebSphere Application Server Network Deployment [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/index.jsp?topic=%2Fcom.ibm.websphere.nd.multiplatform.doc%2Fae%2Fccws_installoptpkg.html]\n\n\n \n\nHISTORICAL NUMBER\n 745241", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Shortly after installing the WebSphere Application Server product, the profile create process failed. This document describes the error and solution. \n\nRESOLVING THE PROBLEM\nShortly after installing the WebSphere Application Server product, the profile create process failed. This document describes the error and solution. \n\nProblem: \nThe manageprofiles command/script failed with the following error:\n\njava.lang.reflect.InvocationTargetException\nat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\nat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)\nat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)\nat java.lang.reflect.Method.invoke(Method.java:600)\nat com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213)\nat com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93)\nat com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74)\nat org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)\nat org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)\nat org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)\nat org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)\nat org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)\nat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\nat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)\nat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)\nat java.lang.reflect.Method.invoke(Method.java:600)\nat org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)\nat org.eclipse.core.launcher.Main.basicRun(Main.java:282)\nat org.eclipse.core.launcher.Main.run(Main.java:981)\nat com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:341)\nat com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:111)\nCaused by: java.lang.NoClassDefFoundError: org.eclipse.emf.ecore.EFactory\nat java.lang.ClassLoader.defineClass(ClassLoader.java:275)\nat org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:160)\nat org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:550)\nat org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:520)\nat org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:451)\nat org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass_LockClassName(ClasspathManager.java:430)\nat org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:417)\nat org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)\nat org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:334)\nat org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:386)\nat org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:347)\nat org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)\nat java.lang.ClassLoader.loadClass(ClassLoader.java:619)\nat java.lang.J9VMInternals.verifyImpl(Native Method)\nat java.lang.J9VMInternals.verify(J9VMInternals.java:72)\nat java.lang.J9VMInternals.verify(J9VMInternals.java:70)\nat java.lang.J9VMInternals.initialize(J9VMInternals.java:134)\n\nResolution: \nThis type of error can be caused when the OSGI cache becomes damaged. The OsgiCfgInit script can be used to clean the cache. \n\nThe instructions for WAS v7 Express are as follows:\n\n1. Issue the STRQSH command.\n2. Type cd /qibm/proddata/websphere/appserver/v7/express/bin\n3. osgicfgInit\n\nYou should receive a message that the cache was cleaned.\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Operating System IBM i 6.1 Operating System IBM i 7.1 \nHISTORICAL NUMBER\n 627181361", "RTC; DM; RSADM; sourcecontrol; org.eclipse.core.internal.filesystem.Policy.error; org.eclipse.core.runtime.CoreException TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to import an IBM Rational Software Architect workspace results in the error \"No file system is defined for scheme: sourcecontrol\" and no resources are imported, when using IBM Rational Software Architect Design Manager and IBM Rational Team Concert. \n\nSYMPTOM\nSteps to reproduce: \n\n 1. Install IBM Rational Team Concert server, IBM Rational Design Manager server, IBM Rational Software Architect, IBM Rational Software Architect Design Manager Client and IBM Rational Team Concert Client Extension, in the same IBM Installation Manager Package Group, and IBM Rational Software Design Manager Import Engine\n \n 2. Start Rational Software Architect on a new workspace\n \n 3. Create a new UML Modeling Project with some UML models\n \n 4. Share the UML Modeling Project in Rational Team Concert\n \n 5. Configure the Design Manager Import Engine with the default value for the Eclipse Installation Directory\n \n 6. Configure the Import Definition in Design Manager\n \n 7. Select to import the entire workspace created in Step 2\n \n 8. Request the import from Design Manager\n\n\nResults: * The modeling project is not imported \n * This stack trace appears in the Rational Software Architect workspace, in the .metadata\\.log file:\n\n\n!SESSION 2013-04-10 17:52:34.350 -----------------------------------------------\neclipse.buildId=unknown\njava.fullversion=JRE 1.6.0 IBM J9 2.4 Windows Server 2008 R2 amd64-64 jvmwa6460sr11-20120801_118201 (JIT enabled, AOT enabled)\nJ9VM - 20120801_118201\nJIT - r9_20120608_24176ifx1\nGC - 20120516_AA\nBootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US\nFramework arguments: -application com.ibm.xtools.rmpc.importEngineHook\nCommand-line arguments: -data C:\\temp\\workspace -application com.ibm.xtools.rmpc.importEngineHook\n\n!ENTRY org.eclipse.equinox.app 0 0 2013-04-10 17:52:36.303\n!MESSAGE Product com.ibm.xtools.importengine.product could not be found.\n\n!ENTRY org.eclipse.core.resources 2 10035 2013-04-10 17:52:36.459\n!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.\n\n!ENTRY org.eclipse.core.resources 4 567 2013-04-10 17:52:36.975\n!MESSAGE Workspace restored, but some problems occurred.\n!SUBENTRY 1 org.eclipse.core.resources 4 567 2013-04-10 17:52:36.975\n!MESSAGE Could not read metadata for 'ModelingProjectInRTC'.\n!STACK 1\norg.eclipse.core.runtime.CoreException: No file system is defined for scheme: sourcecontrol\nat org.eclipse.core.internal.filesystem.Policy.error(Policy.java:55)\nat org.eclipse.core.internal.filesystem.Policy.error(Policy.java:50)\nat org.eclipse.core.internal.filesystem.InternalFileSystemCore.getFileSystem(InternalFileSystemCore.java:65)\nat org.eclipse.core.internal.filesystem.InternalFileSystemCore.getStore(InternalFileSystemCore.java:107)\nat org.eclipse.core.filesystem.EFS.getStore(EFS.java:470)\nat org.eclipse.core.internal.localstore.FileStoreRoot.createStore(FileStoreRoot.java:105)\nat org.eclipse.core.internal.localstore.FileSystemResourceManager.initializeStore(FileSystemResourceManager.java:512)\nat org.eclipse.core.internal.localstore.FileSystemResourceManager.read(FileSystemResourceManager.java:735)\nat org.eclipse.core.internal.resources.SaveManager.restoreMetaInfo(SaveManager.java:876)\nat org.eclipse.core.internal.resources.SaveManager.restoreMetaInfo(SaveManager.java:856)\nat org.eclipse.core.internal.resources.SaveManager.restore(SaveManager.java:705)\nat org.eclipse.core.internal.resources.SaveManager.startup(SaveManager.java:1527)\nat org.eclipse.core.internal.resources.Workspace.startup(Workspace.java:2134)\nat org.eclipse.core.internal.resources.Workspace.open(Workspace.java:1883)\nat org.eclipse.core.resources.ResourcesPlugin.start(ResourcesPlugin.java:410)\nat org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)\nat java.security.AccessController.doPrivileged(AccessController.java:277)\nat org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)\nat org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)\nat org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:370)\nat org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:284)\nat org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:417)\nat org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:265)\nat org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:106)\nat org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:453)\nat org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)\nat org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:393)\nat org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:33)\nat org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:466)\nat org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)\nat org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)\nat org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)\nat java.lang.ClassLoader.loadClass(ClassLoader.java:626)\nat com.ibm.xtools.rmpc.importhook.internal.ImportHook.calculateDeltaOperations(ImportHook.java:112)\nat com.ibm.xtools.rmpc.importhook.internal.ImportHook.start(ImportHook.java:69)\nat org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)\nat org.eclipse.equinox.internal.app.AnyThreadAppLauncher.run(AnyThreadAppLauncher.java:26)\nat java.lang.Thread.run(Thread.java:738) \n\n\n\nCAUSE\nThe Design Manager Import Engine contains a basic Eclipse installation. This is not appropriate for importing projects stored in Rational Team Concert.\n\n\n\nENVIRONMENT\n \n\n * IBM Rational Software Architect 8.5.1 \n * IBM Rational Software Architect Design Manager 4.0.1 \n * IBM Rational Team Concert 4.0.1\n\nDIAGNOSING THE PROBLEM\nMethod 1: \n\n \n\n 1. Click Start > Programs > Rational Software Architect Design Manager Import Engine > Configure import engine\n \n \n 2. Verify the value of the text field is Eclipse Installation Directory\n\n\nMethod 2: \n 1. Open the log fileC:\\Program Files\\IBM\\RSADMImportEngine\\importEngine.log\n \n \n 2. Check that the value of the entry is Eclipse directory\n\n\nApr 10, 2013 3:51:39 PM INFO : Import engine starts \nApr 10, 2013 3:51:39 PM INFO : Engine name: MyImportEngine \nApr 10, 2013 3:51:39 PM INFO : User id: jazzadmin \nApr 10, 2013 3:51:39 PM INFO : Front server url: https://dm-fully-qualified-hostname:9443/dm \nApr 10, 2013 3:51:39 PM INFO : Eclipse directory: C:/Program Files/IBM/RSADMImportEngine/ \n\nRESOLVING THE PROBLEM\nSOLUTION \n\n \n\n 1. Click Start > Programs > Rational Software Architect Design Manager Import Engine > Configure import engine\n \n \n 2. Set the value of the text field Eclipse Installation Directory to be the installation of the Rational Team Concert Client. In this case, since Rational Team Concert Client Extension was installed on an existing installation of Rational Software Architect, the value of the directory is C:\\Program Files\\IBM\\SDP as in the following screen capture:\n\n\n[/support/docview.wss?uid=swg21634062&aid=1] [/support/docview.wss?uid=swg21634062&aid=1] \n\nLeverage the Jazz Community The Jazz based products have an active community that can provide you with additional resources. Browse and contribute to the User forums, contribute to the Team Blog and review the Team wiki.\n\nReview technote 1319600: Leveraging the Jazz Community on Jazz.net [http://www.ibm.com/support/docview.wss?uid=swg21319600] for details.\n\n\n\nRELATED INFORMATION\n#DM Import with ANT [https://jazz.net/wiki/bin/view/Main/RSADM_RTC_And_Ant]\nImport Engine [http://pic.dhe.ibm.com/infocenter/rdmhelp/v4/index.jsp?topic=%2Fcom.ibm.rcam.install.doc%2Ftopics%2Ft_import_engine_configure_rsa.html]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Software Development Rational Team Concert Integrations: IBM Linux, Windows 4.0, 4.0.0.1, 4.0.0.2, 4.0.1, 4.0.2 Software Development Rational Software Architect Integrations: IBM Linux, Windows 8.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.4.1, 8.0.4.2, 8.5, 8.5.1 Software Development Rational Software Architect for WebSphere Software Integrations: IBM Linux, Windows 8.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.4.1, 8.0.4.2, 8.5, 8.5.1", "NFS; remote drive; mount drive ; 1308281 TECHNOTE (FAQ)\n\nQUESTION\n Can IBM® Installation Manager be installed on a UNIX® or Linux® NFS mounted disk? \n\nANSWER\nDo not install the IBM Installation Manager on an NFS mounted disk. \n\nOn AIX® for example, some of the JRE folders are not being deleted when the IBM Installation Manager uninstalls but is deleted after waiting for 10 minutes. This causes the JRE folder to not be uninstalled during an uninstall operation. Other UNIX and Linux operating systems have similar issues. \n\nOnly install the Installation Manager on a local disk." ]

[ [ "4a", "NFS; remote drive; mount drive ; 1308281 TECHNOTE (FAQ) QUESTION" ], [ "4b", " Can IBM® Installation Manager be installed on a UNIX® or Linux® NFS mounted disk? ANSWER" ], [ "4c", "Do not install the IBM Installation Manager on an NFS mounted disk." ], [ "4d", "On AIX® for example, some of the JRE folders are not being deleted when the IBM Installation Manager uninstalls but is deleted after waiting for 10 minutes." ], [ "4e", "This causes the JRE folder to not be uninstalled during an uninstall operation." ], [ "4f", "Other UNIX and Linux operating systems have similar issues." ], [ "4g", "Only install the Installation Manager on a local disk." ] ]

[ "4a", "4b", "4c", "4d", "4e", "4f", "4g" ]

[ " A FIX IS AVAILABLE\nIBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009) [http://www-01.ibm.com/support/docview.wss?uid=swg24032067]\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 * Environment:\n Windows\n Siebel Agent 6.24, image part number CZV4CEN\n Problem Description:\n After installed and configured 6.24 Siebel Agent, two symtoms\n showed\n 1. Agent Connection Status is \"No\" in the Agent Connection\n Status view of the agent's top level workspace in the\n agent's top level workspace in the Tivoli Enterprise Portal.\n \n \n 2. Examination of the configuration values set in the cfg file\n and those shown in the agent's log file proves that default\n values from the wrong configuration section were used.\n \n Recreate Instructions:\n 1. Install the \"Monitoring Agent for Siebel\" on Windows.\n 2. Configure an instance of the Monitoring Agent for Siebel.\n Example:\n Server Type:\n Instance Name: sections\n Server type(s): Siebel server only\n Server Type: Server\n Siebel Enterprise name: SCRM\n Siebel Server name: s80winorac5\n Siebel Server base install directory:\n S:\\siebel\\siebsrvr\n Siebel Server Admin ID: SADMIN\n Siebel Server Admin password: ******\n Siebel Server software version: version 8.0\n Siebel Gateway Name Server and optional port:\n S:\\siebel\\gtwysrvr\n Additional logs:\n <Leave all 10 fields blank>\n 3. Start the agent instance.\n 4. Open the kubsieb log file (example: C:\\IBM\\ITM\\TMAITM6\n \\logs\\S80WINORAC5_ub_sections_kubsieb_4cc06d37-01.log)\n 5. [PROBLEM] Find \"KUB_SIEBEL_ENTERPRISE\". You should see it\n set to the value \"siebel\"\n 6. Open the configuration file for the agent instance\n (example: C:\\IBM\\ITM\\TMAITM6\\s80winorac5_ub_sections.cfg)\n 7. Confirm\n a. SERVER_TYPE=SERVER\n b. KUB_SIEBEL_ENTERPRISE=SCRM inside SECTION=KUB_SERVER\n (\"SCRM\" should have been seen in the log in step 5\n above.)\n c. KUB_SIEBEL_ENTERPRISE=siebel inside\n SECTION=KUB_SERVER_AND_GATEWAY\n (This should NOT have been used unless the\n SERVER_TYPE was\n \"SERVER_AND_GATEWAY\")\n \n \n Additional Information:\n 1. more information is in defect 140524 and technotes\n http://www-01.ibm.com/support/docview.wss?uid=swg21450348 [http://www-01.ibm.com/support/docview.wss?uid=swg21450348]\n 2. Siebel Agent 6.24 (CZV4CEN) is based on installer 06220200\n 3. To recreate the issue Siebel server is not required.\n The following info is from the Agent team\n Q1: Is a Siebel server required to recreate the issue?\n No, if you consider this an ITM Config write defect.\n You can see the error\n in the cfg file after configuration as described in\n http://www-01.ibm.com/support/docview.wss?uid=swg21450348 [http://www-01.ibm.com/support/docview.wss?uid=swg21450348]\n \n Q2: If yes, is the Sieble server on the same machine(local)\n as the Siebel agent or remotely on another machine?\n The Siebel agent is a local agent only.\n \n Q3: If local, please ask the Seible Agent team to provide\n test environment with Sieble Server to recreate, debug and\n test Please see the answer to question 1 about not needing\n Siebel server.\n you consider this and ITM Config read defect, then I can work\n on providing access to a Siebel Server, however, can you\n please use the information in\n http://www-01.ibm.com/support/docview.wss?uid=swg21450348 [http://www-01.ibm.com/support/docview.wss?uid=swg21450348]\n to determine whether is is an ITM Config write or ITM Config\n read defect.\n \n \n \n \n Local Fix:\n Reconfigure the agent instance and configure values for all\n server types that share configuration variables with the\n target server type. Then re-select\n the correct server type and complete the configuration.\n \n \n For example, when configuring for a Siebel server only:\n \n 1. Choose \"Both Siebel and Gateway server\".\n 2. Click Next, and fill in all fields that are also used on\n the Siebel server\n only server type (all fields except the Siebel Gateway\n Name Server base install directory>.\n 3. Click Back, select \"Siebel server only\", then complete\n the configuration.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * Configuration of an IBM Tivoli Composite Application Manager for\n Applications Agent for Siebel CRM instance with the server type\n of \"Siebel server only\" does not work correctly.\n \n \n During agent configuration, the unused server type sections are\n written to the configuration file with default values. When the\n agent is started, some of those default values are used, instead\n of the values from the selected server type section.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Support has been added for agents to specify whether default\n values are used instead of the values from the selected server\n type section. For this to be effective, the Siebel agent needs\n to implement this new setting (see APAR IV19099).\n \n The fix for this APAR is contained in the following maintenance\n packages:\n \n \n | fix pack | 6.2.2-TIV-ITM-FP0009\n \n \n \n \n \n\nTEMPORARY FIX\n * Reconfigure the agent instance and configure values for all\n server types that share configuration variables with the target\n server type. Then re-select the correct server type and complete\n the configuration.\n \n For example, when configuring a Siebel server:\n \n 1. Choose \"Both Siebel and Gateway server\".\n 2. Click Next, and fill in all fields that are also used on\n the \"Siebel server only\" server type. Excluded the Siebel\n Gateway Name Server base install directory field.\n 3. Click Back and select \"Siebel server only\", then\n complete the configuration.\n \n \n \n \n \n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IV13951\n \n \n * REPORTED COMPONENT NAME\n OMEG DIST INSTA\n \n \n * REPORTED COMPONENT ID\n 5608A41CI\n \n \n * REPORTED RELEASE\n 622\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-01-25\n \n \n * CLOSED DATE\n 2012-03-31\n \n \n * LAST MODIFIED DATE\n 2012-06-28\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 IV19099\n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n OMEG DIST INSTA\n \n \n * FIXED COMPONENT ID\n 5608A41CI\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R622 PSY\n UP", "CAMJ2ALL CAMJ2CD MustGather log ITCAMfJ2EE J2EE \"ITCAM for J2EE\" Gather \"Log Gathering\" \"Collecting Data\" Collect Collecting Data Agent TECHNOTE (FAQ)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n UK English \n\nQUESTION\n How do I collect the J2EE DC and TEMA logs? \n\nANSWER\n\n1. Please Collect \"yj\" and/or \"ht\" version from TEMS, TEPS, TEMA, and send the output. \n\nCommand on Windows : <ITM_HOME>\\bin\\kincinfo -i \non UNIX/Linux : <ITM_HOME>/bin/cinfo -i \n2. Collect MS, DC, TEMA data using following instruction and send the ouptut. \n\n\n*** Collecting J2EE 7.1.1 Data \nNote : Since the J2EE agent is composed by two parts, Data Collector and TEMA, you can separately collect data from them by invoking the two following scripts as \" root\": \n\n=====> Data Collector (DC) Location Windows: <ITM_HOME>\\TMAITM6\\j2eedc\\7.1.1.0.0\\itcamdc\\bin\\cyn_collector.cmd\nUnix : <ITM_HOME>/<architecture>/yj/j2eedc/7.1.1.0.0/itcamdc/bin/cyn_collector.sh\n\n* example: \n- Windows platform :\nC:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\itcamdc\\bin\\cyn_collector.cmd\n- Linux 64 bit platform : \nopt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/itcamdc/bin/cyn_collector.sh Usage/\nOutput Windows : %TEMP%\\CYN\\*.zip \nUnix : <ITM_HOME>/tmp/CYN/<hostname>-CYNenv.jar\n=====> TEMA Location Windows : <ITM_HOME>\\TMAITM6\\kyjcollect.cmd\nUnix : <ITM_HOME>/<architecture>/yj/bin/kyjcollect.sh\n\n* example: \n- Windows platform : C:\\IBM\\ITM\\TMAITM6\\kyjcollect.cmd\n- Linux 64 bit platform : opt/IBM/ITM/lx8266/yj/bin/kyjcollect.sh Usage/\nOutput Windows : %TEMP%\\kyj\\*.jar\nUnix : $HOME/tmp/kyj/kyjcollect-$HOSTNAME.tar.gz \n\n* example:\n- Linux : /root/tmp/kyj/kyjcollect-<hostname>.tar.gz\n- AIX, Solaris, HPUX : /tmp/kyj/kyjcollect-<hostname>.tar.gz \n\n*** Collecting J2EE 6.1 FP4 or higher version using script \n=============> Managing Server (MS) Location on Window/Unix/Linux : <MS_HOME>/bin/MS_Gather_Data.sh\n\nNote: On Windows, the user must run the script in a Korn Shell environment. Usage/\nOutput on Windows/Unix/Linux :\n<MS_HOME>/bin/MS_Gather_Data.sh [pmr][was_home][appServer]\n\nNote: [was_home] = directory where the MS Visualization Engine is installed \n=============> Data Collector (DC) Location on Windows : <DC_HOME>\\itcamdc\\bin\\cyn_collector_j2.cmd\non Unix/Linux : <DC_HOME>/itcamdc/bin/cyn_collector_J2.sh Output on Windows : <DC_HOME>\\collect.jar\non Unix/Linux : <DC_HOME>/collect.tar.gz =============> TEMA Location on Windows : <ITM_HOME>\\TMAITM6\\kyjcollect.cmd \non Unix/Linux : <ITM_HOME>/<arch>/yj/bin/kyjcollect.sh \nwhere <arch>= location that indicates the platforms\n(ex: sol283 for Solaris, aix513 for AIX, and hp11 for HP-UX).\nUsage on Windows : <ITM_HOME>\\TMAITM6\\kyjcollect.cmd \non Unix/Linux : <ITM_HOME>/<arch>/yj/bin/kyjcollect.sh Output on Windows : %TEMP%\\kyj\\*.jar\non Unix/Linux : $HOME/tmp/kyj/kyjcollect-<hostname>.tar.gz \n\n\nBack to top \n\n*** MANUAL J2EE 6.1 Data Collection *** \nManaging Server (MS) Data - manual \n* Window and Unix Location <MS_HOME>/logs/am_stderr.log\n<MS_HOME>/logs/am_stdout.log\n<TIVOLI_LOGS>/msg-<component>.log\n<TIVOLI_LOGS>/trace-<component>.log\n<TIVOLI_LOGS>/audit-ms.log \n\nData Collector (DC) Data - manual \n* Windows and Unix \n\nFor the version lower than ITCAM for J2EE 6.1 FixPack 4 Here are the logs required for each application server. The logs are from the following directory: <TIVOLI_LOGS>/nodename.instancename \n\nApplication Server Logs to Collect WebLogic, WASCE, J2SE msg-dc.log, trace-dc.log, msg-dc-native.log, trace-dc-native.log NetWeaver msg-dc-sap.log, trace-dc-sap.log, msg-dc-native.log, trace-dc-native.log Tomcat msg-dc-Standard.log, trace-dc-Standard.log, msg-dc-native.log, trace-dc-native.log Oracle msg-dc.log, trace-dc.log, trace-dc-bcm.log, msg-dc-native.log, trace-dc-native.log JBoss msg-dc-Unified.log, trace-dc-Unified.log, trace-dc-bcm.log, msg-dc-native.log, trace-dc-native.log \n\nFor the version ITCAM for J2EE 6.1 FixPack 4 or higher Here are the logs required for each application server. The logs are from the following directory: <TIVOLI_LOGS>/nodename.instancename \n\nApplication Server Logs to Collect WebLogic msg-dc-ParentLast.log, trace-dc-ParentLast.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log WASCE, J2SE msg-dc.log, trace-dc.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log NetWeaver msg-dc-sap.log, trace-dc-sap.log, msg-dc-native.log, trace-dc-native.log ,msg-dc-bcm.log, trace-dc-bcm.log Tomcat msg-dc-tomcat.log, trace-dc-tomcat.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log Oracle msg-dc.log, trace-dc.log, trace-dc-bcm.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log JBoss msg-dc-jboss.log, trace-dc-jboss.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log \n\nAgent (TEMA) Data - manual \n* Windows Location <ITM_HOME>/logs/kyj-tema-trace.log, \n<ITM_HOME>/logs/kyj-tema-msg.log,\n<ITM_HOME>/logs/KYJ.Primary.*.*JVM.log \n* Unix Location <ITM_HOME>/<PLATFORM>/logs/kyj-tema-trace.log, \n<ITM_HOME>/<PLATFORM>/logs/kyj-tema-msg.log,\n<ITM_HOME>/logs/KYJ.Primary.*.*JVM.log \n\nBack to top \n\n*******J2EE Installation Error Logs (for all version) ******* \nManaging Server (MS) Data - install error log \n\nManaging Server Installation Error Logs (for all version) \nComponents Logs to Collect Managing Server specific logs * Windows : C:\\Program Files\\ibm\\tivoli\\common\\CYN\\logs \n* Unix : /var/ibm/tivoli/common/CYN/logs Embedded DB2 logs * Windows : <user's My Documents directory>\\DB2LOG\n* Unix : /tmp/db2setup.* Embedded WebSphere Application Server ** Windows and Unix :\n<MS_HOME>/temp\n<J2EEAPP_HOME>/logs Embedded WebSphere Application Server Refresh Pack ** Windows and Unix :\n<J2EEAPP_HOME>/logs/update \n\n\nData Collector (DC) Data - install error log \n* Window and Unix Location <TIVOLI_LOGS>/trace-install.log\n<TIVOLI_LOGS>/launchContainer/\n<TIVOLI_LOGS>/platformUtils/\nIf you use NetWeaver, <TIVOLI_LOGS>/config.log \nBack to top \n\nPRODUCT ALIAS/SYNONYM\n ITCAM for J2EE", "TCserver Tacton TCsite Configurator Tomcat6 Tomcat TEMA J2EE configuration fails CAMADALL CAMADINST TECHNOTE (FAQ)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n US English \n\nQUESTION\n Is ITCAM for J2EE supported with TCsite Tacton Configurator Server? \n\nANSWER\nTCsite Tacton Configurator Server (TCsite) is a product used to configure the Tomcat6 server and other applications, it runs on the Tomcat6 J2EE server. \n\n\nAt this time, the TCsite Tacton Configurator Server product is not supported for use with ITCAM for J2EE v7.1.1. \n\nHowever, we've seen the TCsite Tacton Configurator Server (tcserver) work with the ITCAM for J2EE product and the bundled Tomcat server successfully get configured... its just not a supported configuration at this time.\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli Composite Application Manager for J2EE ITCAM J2EE BASE Solaris, AIX, HP-UX, Linux, Windows 7.1.1 \nPRODUCT ALIAS/SYNONYM\n ITCAMfAD ITCAM4J2EE ITCAM for J2EE", "ITCAM; J2EE; Tomcat; Windows; Service; CAMJ2ALL; CAMJ2INST; CAMJ2TCDC TECHNOTE (FAQ)\n\nQUESTION\n What is the correct procedure to configure the ITCAM for J2EE Data Collector for Tomcat to run as a Windows service? \n\nCAUSE\nThere is an option to specify the Tomcat Windows Service during GUI configuration of the ITCAM J2EE 7.1.1 agent/DC. This option does not work and will result in a failed configuration.\n\n\n\n[/support/docview.wss?uid=swg21961542&aid=1] [/support/docview.wss?uid=swg21961542&aid=1]\n\nThis option will be removed from the drop down menu for the Tomcat DC Configuration, according to APAR PI43783.\n\n\nANSWER\nTomcat on Windows platforms must be installed from a base distribution, that is extracting a .zip file named like apache-tomcat-7.0.62.zip, even though one plans to start Tomcat only as a Window Service, and not with a startup script. \n\n\nIf you install Tomcat from the Windows Service Installer (e.g. apache-tomcat-7.0.62.exe), rather than a base distribution, some of the command-line and startup scripts for launching Tomcat will not be included, and you won't be able to complete the following procedure.\n\n\n1- Configure the DC using the Normal Startup option.\n\n[/support/docview.wss?uid=swg21961542&aid=2] [/support/docview.wss?uid=swg21961542&aid=2]\n\nOn a supported Windows 64-bits platform with the YJ 7.1.1.0.0 installed in E:\\IBM\\ITM\\, and with a Tomcat 7 running a supported version of Sun HotSpot JRE , this will result in the following stanza being added into the <AppServer_home>\\bin\\catalina.bat file:\n\n\nREM -----Configurator of DC Begin----------\n\nset PATH=E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\toolkit\\lib\\win64;%PATH%\nset JAVA_OPTS=-Xbootclasspath/p:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\toolkit\\lib\\bcm-bootstrap.jar -Xbootclasspath/p:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\itcamdc\\lib\\ppe.probe-bootstrap.jar -Xbootclasspath/p:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\itcamdc\\lib\\ext\\tomcat\\tomcat.bcm.jar -agentlib:am_sun_16=E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\runtime\\tomcat70.nc114017.romelab.it.ibm.com.Tomcat7\\dc.env.properties -Xloggc:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\runtime\\tomcat70.nc114017.romelab.it.ibm.com.Tomcat7\\gc.log -XX:-TraceClassLoading -XX:-TraceClassUnloading -Dcom.sun.management.jmxremote -Dsun.lang.ClassLoader.allowArraySyntax=true %JAVA_OPTS%\n\nREM -----Configurator of DC End----------\n\n\nYou might want to check at this point if the DC is correctly started when you start the Tomcat via the startup.bat script, even though you will start Tomcat as a Windows Service in the future.\n\n\n2- Right-click the Tomcat Service icon on the Windows taskbar and click Configure.\n\n3- When the Apache Tomcat properties window opens, click the Java™ tab.\n\n4- From the open catalina.bat file, copy the value for JAVA_OPTS, and paste it into the text box labelled Java Options (in the Apache Tomcat Properties window).\n\n-Xbootclasspath/p:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\toolkit\\lib\\bcm-bootstrap.jar\n-Xbootclasspath/p:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\itcamdc\\lib\\ppe.probe-bootstrap.jar\n-Xbootclasspath/p:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\itcamdc\\lib\\ext\\tomcat\\tomcat.bcm.jar\n-agentlib:am_sun_16=E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\runtime\\tomcat70.nc114017.romelab.it.ibm.com.Tomcat7\\dc.env.properties\n-Xloggc:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\runtime\\tomcat70.nc114017.romelab.it.ibm.com.Tomcat7\\gc.log\n-XX:-TraceClassLoading\n-XX:-TraceClassUnloading\n-Dcom.sun.management.jmxremote\n-Dsun.lang.ClassLoader.allowArraySyntax=true\n\n\n[/support/docview.wss?uid=swg21961542&amp;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<DC_home>\\toolkit\\lib\\<win_arch>\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.", "1404257; RTC; service; windows; 32-bit; 64-bit; tomcat5; tomcat5w; valid; Win32; application TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\nThis technote explains how to download and configure 64 bit Tomcat to run as a service when using IBM Rational Team Concert.\n\nSYMPTOM\nFollowing the instructions as detailed in the Jazz.net Technote Running Jazz Team Server in Tomcat as a Windows Service [http://jazz.net/library/techtip/72] on a 64-bit platform (see link below), the Tomcat service would not start properly. The following error is encountered at service startup: \n\n * \n * [2009-08-20 14:54:14] [info] Running Service...\n * [2009-08-20 14:54:14] [info] Starting service... \n * [2009-08-20 14:54:15] [174 javajni.c] [error] %1 is not a valid Win32 application. \n * [2009-08-20 14:54:15] [947 prunsrv.c] [error] Failed creating java C:\\IBM\\JazzTeamServer\\server\\jre\\bin\\j9vm\\jvm.dll \n * [2009-08-20 14:54:15] [1202 prunsrv.c] [error] ServiceStart returned 1 \n * [2009-08-20 14:54:16] [info] Run service finished. \n * [2009-08-20 14:54:16] [info] Procrun finished.\n\nENVIRONMENT\nMicrosoft Windows 2008 Server x64\n\n\n\nDIAGNOSING THE PROBLEM\nOperating system is Microsoft Windows 64-bit \n\nError message at service startup: [174 javajni.c] [error] %1 is not a valid Win32 application.\n\n\n\nRESOLVING THE PROBLEM\nTo resolve this issue: \n\n 1. [http://svn.apache.org/viewvc/tomcat/tc5.5.x/tags/TOMCAT_5_5_23/connectors/procrun/bin/]Go to <rtc_server_install_dir>/server/tomcat/bin directory and uninstall the 32-bit service by running:service remove Tomcat5\n \n Note: The old service may be cached somewhere - when in doubt, reboot\n \n 2. Rename the 32-bit service wrapper:\n copy <rtc_server_install_dir>/server/tomcat/bin/tomcat5.exe to tomcat5.exe.32bit (or any name you want to call it) \n 3. Copy the 64-bit service wrapper:\n RTC 2.X: copy /server/tomcat/bin/procrun/amd64/tomcat5.exe to the /server/tomcat/bin directory \n RTC 3.X: copy /server/tomcat/bin/procrun/x64/tomcat5.exe to the /server/tomcat/bin directory \n 4. Proceed with service configuration as detailed in TN0010: Running Jazz Team Server in Tomcat as a Windows Service - [http://jazz.net/library/techtip/72]with the exception that the path to the jvm.dll is not correct for an RTC 2.x product (it should be \"<rtc_server_install_dir>/server/jre/bin/j9vm/jvm.dll\") \n 5. Once service started, verify the Rational Team Concert Server can be reached.\n \n \n\n\nLeverage the Jazz Community: Jazz and Rational Team Concert have an active community that can provide you with additional resources. Browse and contribute to the User forums, contribute to the Team Blog and review the Team wiki.\nRefer to technote 1319600 [http://ibm.com/support/docview.wss?rs=3488&&uid=swg21319600] for details and links.\n\n\n\nRELATED INFORMATION\n#jazz.net work item 85748 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/85748]\nRunning RTC Server in Tomcat as a Windows Service [http://jazz.net/library/technote/72]\njazz.net work item 102573 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/102573]\n\n\n\n\n\n\nCross Reference information Segment Product Component Platform Version Edition Software Development Rational Project Conductor Team Server Windows 1.0, 1.0.0.1 Software Development Rational Quality Manager Web App Server Windows 2.0, 2.0.0.1, 2.0.1 Software Development Rational Requirements Composer Web App Server Windows 2.0, 2.0.0.1, 2.0.0.2 Software Development Rational Team Concert Web App Server Windows 2.0.0.1, 2.0" ]

[ [ "3a", "ITCAM; J2EE; Tomcat; Windows; Service; CAMJ2ALL; CAMJ2INST; CAMJ2TCDC TECHNOTE (FAQ) QUESTION" ], [ "3b", " What is the correct procedure to configure the ITCAM for J2EE Data Collector for Tomcat to run as a Windows service? CAUSE" ], [ "3c", "There is an option to specify the Tomcat Windows Service during GUI configuration of the ITCAM J2EE 7.1.1 agent/DC." ], [ "3d", "This option does not work and will result in a failed configuration. [/support/docview.wss?uid=swg21961542&aid=1] [/support/docview.wss?uid=swg21961542&aid=1]" ], [ "3e", "This option will be removed from the drop down menu for the Tomcat DC Configuration, according to APAR PI43783. ANSWER" ], [ "3f", "Tomcat 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." ], [ "3g", "If you install Tomcat from the Windows Service Installer (e.g." ], [ "3h", "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." ], [ "3i", "1- Configure the DC using the Normal Startup option. [/support/docview.wss?uid=swg21961542&aid=2] [/support/docview.wss?uid=swg21961542&aid=2]" ], [ "3j", "On 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 <AppServer_home>\\bin\\catalina.bat file:" ], [ "3k", "REM -----Configurator of DC Begin---------- set PATH=E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\toolkit\\lib\\win64;%PATH%" ], [ "3l", "set 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%" ], [ "3m", "REM -----Configurator of DC End----------" ], [ "3n", "You 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." ], [ "3o", "2- Right-click the Tomcat Service icon on the Windows taskbar and click Configure." ], [ "3p", "3- When the Apache Tomcat properties window opens, click the Java™ tab." ], [ "3q", "4- 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). -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 [/support/docview.wss?uid=swg21961542&amp;aid=3]" ], [ "3r", "6- Add to the System Environment Variable PATH into the System Environment Variables the same value that was set for PATH into the catalina.bat: <DC_home>\\toolkit\\lib\\<win_arch>" ], [ "3s", "in our Windows 64-bits example: E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\toolkit\\lib\\win64" ], [ "3t", "Apart 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 [/support/docview.wss?uid=swg21961542&aid=4] [/support/docview.wss?uid=swg21961542&aid=4]" ], [ "3u", "7- Restart Windows." ] ]

[ "3b", "3c", "3d", "3e", "3f", "3g", "3h", "3i", "3j", "3k", "3l", "3m", "3n", "3o", "3p", "3q", "3r", "3s", "3t", "3u" ]

[ " SUBSCRIBE\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 * Fixes to Service Registry for 6.3.0.2\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * Null pointer error during configuration update resolved\n PropertyQuery for _sdoType returns null, now resolved\n Behaviour of nested API calls in plugins changed to match\n previous releases\n Improved handling of JMS topic limit being reached\n Unable to load WSDL due to stale connection and SQLCODE 514 to\n DB2 for z/OS Activity Logging database, now resolved\n Transition attribute in configurable modifier trigger files is\n being ignored, now resolved\n Improvement to handling of SCA modules during upgrade to WSRR\n V7.0\n Exception thrown in RequiredModelMBean during export of SCA\n module, now resolved\n Retrieving an SCA Export Object does not return its contained\n module, now resolved\n Improved DB2 configuration in the installer, to reduce database\n deadlocking\n Delete does not remove content from the W_ARTIFACT_BLOB table,\n now resolved\n Performance improvement for Activity Logging\n Performance improvement loading WSDLs\n WSDL port under the SCA WebService export binding added\n Property Queries can now handle properties of type date\n Improvement to concurrency behaviour when using DB2 V9.7, V9.5,\n V9.1 and Oracle databases\n Message added with information when creating Capability Version\n Null pointer error when updating a WSDL after generating a WS-I\n validator report, now resolved\n ServicePolicy now included in the Technical Model Class\n RAM sync fails relationship on Specification, now resolved\n Publishing WSDLs from RAM fails to load imported XSDs, now\n resolved\n When loading a WSDL document the relationship from GlobalType to\n XSDType not always created, now resolved\n Error deleting WMQ Queues, now resolved\n When loading WMQ WSDLs links to WSDL ports not being created for\n Queues and Queue Managers, now resolved\n Incorrect path setting in the updatewsrr script, now resolved\n Install now works with DB2 V9.7\n NameNotFoundException from Policy Authoring UI due to no\n reference to ActivityLogging bean, now resolved\n Policy4J: Embedded policy missing wsu prefix on Id attribute,\n now resolved\n PolicyAuthoring UDD does not correctly support\n AttributeSelectors as a child of an Assertion, now resolved\n Policy Authoring UI not refreshing the content of an\n AttributeSelector correctly, now resolved\n File locking during promotion improved\n Some properties are returned as null by REST property queries,\n now resolved\n Configuration of service discovery improved\n Wrong infocenter link in the UI Configuration perspective, now\n resolved\n Null pointer error in UI with browser locale set to en-gb, now\n resolved\n Exceptions during the upgrade data capture of SCA modules, now\n resolved\n Modifiers can run too early during upgrade data load, now\n resolved\n SCAs with WebService export bindings can now be migrated from\n V6.2 to V6.3\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * To resolve these issues, apply fix pack 2\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IZ67237\n \n \n * REPORTED COMPONENT NAME\n SERVICE REGISTR\n \n \n * REPORTED COMPONENT ID\n 5724N7200\n \n \n * REPORTED RELEASE\n 630\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 2009-12-21\n \n \n * CLOSED DATE\n 2009-12-21\n \n \n * LAST MODIFIED DATE\n 2010-02-01\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 SERVICE REGISTR\n \n \n * FIXED COMPONENT ID\n 5724N7200\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R630 PSY\n UP", "SCA.RecycleDestinations; custom properties; SCA destinations; event sequencing; SCA modules; message queue TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When a Service Component Architecture (SCA) module is uninstalled, by default, its associated destinations are removed, even if there are still messages in the destination queue. In some situations, such as when Event Sequencing is used, messages on the destinations must be preserved.\n\n\n\nRESOLVING THE PROBLEM\nTo resolve this issue, use the SCA.recycleDestinations custom Java™ virtual machine (JVM) property for the module. Set the property to false to preserve SCA destinations.\n\n \n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Process Server AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows, z/OS 7.0.0.5 Business Integration WebSphere Enterprise Service Bus SCA AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows, z/OS 7.5, 7.0.0.5 \nPRODUCT ALIAS/SYNONYM\n BPM\nWPS\nWESB", "iid; ibm integration designer; exception; security; login TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You receive the exception message javax.security.auth.login.LoginException: Incorrect authDataEntry and alias is: SCA_Auth_Alias when you run a SCA module with a MQ or a JMS import binding. \n\nSYMPTOM\nIn IBM Business Process Manager (BPM) V8.5, when you run a SCA module with a MQ or a JMS import binding, the following error is thrown by the server in SystemOut.log: \n\n\n[1/22/14 16:15:39:892 CST] 00000152 WSDefaultPrin W SECJ4062W: Cannot\nfind the credential information.\n[1/22/14 16:15:39:892 CST] 00000152 PrivExAction E J2CA0044E: The\nConnection Manager failed to get a Subject from the security service\nassociated with ConnectionFactory sca/resource/mqjms/SCA.\nMQJMS/Callback_CF. Received exception javax.security.auth.login.\nLoginException: Incorrect authDataEntry and alias is: SCA_Auth_Alias\nat com.ibm.ws.security.auth.j2c.WSDefaultPrincipalMapping.\ngetMappedSubject(WSDefaultPrincipalMapping.java:529)\nat com.ibm.ejs.j2c.PrivExAction.run(PrivExAction.java:158)\nat com.ibm.ws.security.util.AccessController.doPrivileged\n(AccessController.java:118)\nat com.ibm.ejs.j2c.ServerFunction.getSubject(ServerFunction.java:1202)\nat com.ibm.ejs.j2c.ServerFunction.getFinalSubject(ServerFunction.java:\n1290)\nat com.ibm.ejs.j2c.ConnectionManager.allocateConnection\n(ConnectionManager.java:988)\nat com.ibm.ws.sib.api.jmsra.impl.JmsJcaConnectionFactoryImpl.\ncreateConnection(JmsJcaConnectionFactoryImpl.java:289)\nat com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.\ncreateConnection(JmsManagedConnectionFactoryImpl.java:162)\nat com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.\ncreateConnection(JmsManagedConnectionFactoryImpl.java:135)\n\n\n\nCAUSE\nThe generated web project for this module containing the ibm-web-bnd.xmi file still has a reference to SCA_Auth_Alias, which is an alias that was created by IBM Business Process Manager in a previous release. The alias has been removed in V8.5 and therefore no longer valid in V8.5.\n\nThis has been identified as a product defect under APAR JR50028.\n\n\nDIAGNOSING THE PROBLEM\nLog into the WebSphere Administrative Console, click \"Resources > JMS > connection factories\", and check if there is a connection factory with JNDI \"sca/resource/mqjms/SCA.MQJMS/Callback_CF\". \n\nIf it exists, click the connection factory name. You should see that the authentication alias in the\nconfiguration page is an alias other than the SCA_Auth_Alias, which is the authentication alias defined in the deployed module.\n\n\nRESOLVING THE PROBLEM\nWorkaround 1: \n\n \n\n 1. Log into the WebSphere Administrative Console, create the old SCA_Auth_Alias on the server with an ID that has administrative authority. \n 2. Under \"Resources > JMS > connection factories\", look for the connection factory with JNDI \"sca/resource/mqjms/SCA.MQJMS/Callback_CF\", click the connection factory name, and modify the authentication alias in the configuration page to SCA_Auth_Alias. \n 3. Re-install the SCA module.\n\n\nWorkaround 2: \n 1. Update the generated web project's ibm-web-bnd.xmi file in the SCA module from 'SCA_Auth_Alias' to 'DeAdminAlias', or to another user-defined administrative alias that exists in the WebSphere Administrative Console. \n 2. Save the file and do not build the module again. The change to the ibm-web-bnd.xmi file must be applied again after the module is rebuilt, as the build will overwrite the change. \n 3. Re-install the SCA module.\n\n\nFor instance, \n\nChange: \n\n<resRefBindings xmi:id=\"ResourceRefBinding_1390586116336\" \njndiName=\"sca/resource/mqjms/SCA.MQJMS/Callback_CF\" loginConfigurationName= \"DefaultPrincipalMapping\"> \n<bindingResourceRef href=\"WEB-INF/web.xml#ResourceRef_1390586116336\"/> \n<properties xmi:id=\"Property_1390586116333\" name=\"com.ibm.mapping.authDataAlias\" \nvalue=\"SCA_Auth_Alias\"/> \n</resRefBindings> \n\nTo this: \n\n<resRefBindings xmi:id=\"ResourceRefBinding_1390586116336\" \njndiName=\"sca/resource/mqjms/SCA.MQJMS/Callback_CF\" loginConfigurationName= \n\"DefaultPrincipalMapping\"> \n<bindingResourceRef href=\"WEB-INF/web.xml#ResourceRef_1390586116336\"/> \n<properties xmi:id=\"Property_1390586116333\" name=\"com.ibm.mapping.authDataAlias\" \nvalue=\"DeAdminAlias\"/> \n</resRefBindings> \n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Advanced Service Component Architecture (SCA) AIX, Linux, Linux zSeries, Solaris, Windows, z/OS 8.5.0.1, 8.5", "Retry Mechanism on asynchronous invocation TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You are using asynchronous invocation between two SCA modules and you apply a Java™ Message Service (JMS) binding to combine them. The target service module throws a system exception, such as a transaction time out. JMS then retries the invocation according to the configuration of the Service Integration Bus (SIBus). \n\nSYMPTOM\nIf there is asynchronous invocation between two modules (A and B) and JMS binding is applied between them, module B is triggered twice after a transaction time out exception occurs on module B. \n\n\nCAUSE\nThe Service Component Architecture (SCA) uses SIB to transport messages between components. These destinations are created when a module is installed for WebSphere Process Server or WebSphere Enterprise Service Bus. The SIBus has a built-in retry mechanism that uses message driven beans (MDBs). During an invocation, if the target service returns a system exception, such as a transaction time out, SCA rolls back the current transaction. This rollback causes the invocation message to be put back on the SIBus onto a destination that represents the module to which the target service belongs. The SIBus continues to resubmit the message until a threshold on the module destination is reached. The default failed delivery threshold is two.\n\nRESOLVING THE PROBLEM\nTo configure the retry behavior, modify the Maximum Failed Deliveries attribute to a value of 0 (zero) on the destination ESB_M_UploadDACSRouter_1.Request of the target module (module B). \n\n\n\nTo control the retrying mechanism, complete the following steps in the administrative console: \n\n 1. Navigate to the Service Integration Bus Browser section.\n \n \n 2. Select the bus on which module B is located. Typically, this bus is SCA.APPLICATION.BUS.\n \n \n 3. Navigate to the destinations folder.\n \n \n 4. Locate the request destination that the JMS binding relies on and select it.\n \n \n 5. Scroll down to the Exception destination area and set the value of Maximum failed deliveries per message to 0 (zero).\n\n \n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Enterprise Service Bus SIBus AIX, HP-UX, Linux, Solaris, Windows 7.0.0.4, 7.0.0.3, 7.0.0.2, 7.0.0.1", "v70feprnote; esbv70feprnote; WSWS4004E; v70rnotes TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Retrieving the WSDL document in the administrative console does not support Service Component Architecture (SCA) modules for exports with JAX-WS bindings. \n\nSYMPTOM\nAfter deploying an SCA module that contains an export with the JAX-WS binding, if you use the WebSphere Process Server V7.0.0.x or WebSphere Enterprise Service Bus V7.0.0.x administrative console to select Services > Service providers > Service provider name of your deployed module, and then click the WSDL document link under Additional Properties, you receive the following error message: \n\nWSWS4004E: The wsdl-file for module <your Web module name> was not found in the module.\n\n\nCAUSE\nThe web service endpoints of SCA module exports with JAX-WS bindings are registered in WebSphere Process Server V7.0.0.x or WebSphere ESB V7.0.0.x in a way that does not use JAX-WS annotations. However, the administrative console retrieves the WSDL document using JAX-WS annotated classes.\n\n\nENVIRONMENT\nWebSphere Process Server V7.0.0.x, WebSphere ESB V7.0.0.x\n\n\n\nRESOLVING THE PROBLEM\nGet the WSDL description of an endpoint defined by a SCA module containing an export with a JAX-WS binding by sending an HTTP GET request to the endpoint URL with ?wsdl added to the end of the URL. For example, type the URL with ?wsdl added into the address field of a web browser. In order to retrieve the WSDL description, the SCA module must be deployed and in the started state.\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Enterprise Service Bus AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows" ]

[ [ "1a", "SCA.RecycleDestinations; custom properties; SCA destinations; event sequencing; SCA modules; message queue TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "1b", " 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." ], [ "1c", "In some situations, such as when Event Sequencing is used, messages on the destinations must be preserved." ], [ "1d", "RESOLVING THE PROBLEM" ], [ "1e", "To resolve this issue, use the SCA.recycleDestinations custom Java™ virtual machine (JVM) property for the module." ], [ "1f", "Set the property to false to preserve SCA destinations." ], [ "1g", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Process Server AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows, z/OS 7.0.0.5 Business Integration WebSphere Enterprise Service Bus SCA AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows, z/OS 7.5, 7.0.0.5 PRODUCT ALIAS/SYNONYM BPM WPS WESB" ] ]

[ "1b", "1f" ]

[ " 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", " TECHNOTE (FAQ)\n\nQUESTION\n To have access to ICM Web, do all users have to be web-enabled even when web access is determined by SSO ? \n\nANSWER\nYes, each user needing access to ICM must be web enabled irrespective of whether SSO is being used to determine web access or not.", " DIRECT LINKS TO FIXES\nIBM Case Manager V5.1.0 Fix Pack 3 for Windows [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.1.0.3-ICM-WIN-FP003&source=SAR]\nIBM Case Manager V5.1.0 Fix Pack 3 for Solaris [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.1.0.3-ICM-SOLARIS-FP003&source=SAR]\nIBM Case Manager V5.1.0 Fix Pack 3 for Linux [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.1.0.3-ICM-LINUX-FP003&source=SAR]\nIBM Case Manager V5.1.0 Fix Pack 3 Client for Linux for System z [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.1.0.3-ICM-CLIENT-ZLINUX-FP003&source=SAR]\nIBM Case Manager V5.1.0 Fix Pack 3 Client for Windows [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.1.0.3-ICM-CLIENT-WIN-FP003&source=SAR]\nIBM Case Manager V5.1.0 Fix Pack 3 Client for Solaris [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.1.0.3-ICM-CLIENT-SOLARIS-FP003&source=SAR]\nIBM Case Manager V5.1.0 Fix Pack 3 Client for Linux [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.1.0.3-ICM-CLIENT-LINUX-FP003&source=SAR]\nIBM Case Manager V5.1.0 Fix Pack 3 Client for AIX [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.1.0.3-ICM-CLIENT-AIX-FP003&source=SAR]\nIBM Case Manager V5.1.0 Fix Pack 3 for AIX [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.1.0.3-ICM-AIX-FP003&source=SAR]\nIBM Case Manager V5.1.0 Fix Pack 3 for Linux for System z [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.1.0.3-ICM-ZLINUX-FP003&source=SAR]\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 * When Single Sign-On (SSO) using Kerberos or SPNEGO is enabled,\n the Deploy Solution task in Case Manager Administration Client\n generates the following error:\n \n The IBM Case Manager REST protocol returned the 401 response\n code. Use Enterprise Manager to look at the deployment logs in\n ICM > IBM Case Manager > Solution Deployments > SSO. The\n following response was returned:\n <html><head><title>An NTLM Token was\n received.</title></head><body>Your browser configuration is\n correct, but you have not logged into a supported Microsoft(R)\n Windows(R) Domain. <p>Please login to the application using the\n normal login page.</html>\n \n The deployment error log could not be found.\n \n \n \n \n \n\nLOCAL FIX\n * Deploy Solution in CMAC cannot be used with SSO enabled. To\n deploy in the production environment, disable SSO.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n * System Administrators who want to run Case Manager *\n * Administration Client's Deploy Solution task. *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * See Error Description *\n ****************************************************************\n * RECOMMENDATION: *\n * To fix this problem, apply IBM Case Manager V5.1.0.1 Interim *\n * Fix 1 or later releases. *\n ****************************************************************\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The fix for this problem is provided in IBM Case Manager\n V5.1.0.1 Interim Fix 1 and later releases.\n \n A fix was made in the Case Manager Administration Client (CMAC)\n such that when Single Sign-On (SSO) using Kerberos/SPNEGO is\n enabled, the Deploy Solution task in Case Manager Administration\n Client succeeds.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PJ40200\n \n \n * REPORTED COMPONENT NAME\n CASE MGR ADMIN\n \n \n * REPORTED COMPONENT ID\n 5725A1502\n \n \n * REPORTED RELEASE\n 510\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-04-24\n \n \n * CLOSED DATE\n 2012-05-23\n \n \n * LAST MODIFIED DATE\n 2012-05-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 CASE MGR ADMIN\n \n \n * FIXED COMPONENT ID\n 5725A1502\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R510 PSY\n UP", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\n DIRECT LINKS TO FIXES\n5.2.1.7-ICM-ZLINUX-FP007 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.2.1.7-ICM-ZLINUX-FP007&source=SAR]\n5.2.1.7-ICM-WIN-FP007 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.2.1.7-ICM-WIN-FP007&source=SAR]\n5.2.1.7-ICM-LINUX-FP007 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.2.1.7-ICM-LINUX-FP007&source=SAR]\n5.2.1.7-ICM-AIX-FP007 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.2.1.7-ICM-AIX-FP007&source=SAR]\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * When a user opens a case that contains a manually launched task\n in the ready state the \"Start\" and \"Disable\" buttons are enabled\n even when the user does not have permission to start or disable\n the task. If the user does not have permission to start or\n disable the task, then Start and Disable should be disabled.\n When the user clicks the Start to launch the task will result in\n the following error:\n \n The following error occurred while processing a request on the\n application server: The requester has insufficient access rights\n to perform the requested operation.\n --------------------------------------------------\n An error occurred on the application server.\n Additional information about the error is in the application\n server log files.\n FNRPA0628\n \n \n Steps to reproduce:\n 1. Create solution with a manually launched task\n 2. Save and deploy solution\n 3. Add 2 users to solution role, e.g. User1 and User2\n 4. Change User2 to remove access permission to case folder for\n solution\n 5. Login to case client as User1, create a case, save and logout\n 6. Login to case client as User2, open case with task in Ready\n state\n \n Expected results:\n The Start and Disable are both disabled, since User2 does not\n have permission to start or disable the Ready task\n \n Actual results:\n Start and Disable are both enable. User encounters an error\n attempting to start the Ready task\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n * Case client users without sufficient permission to start or *\n * to disable a \"ready\" task *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * See Error Description *\n ****************************************************************\n * RECOMMENDATION: *\n * Upgrade to 5.2.1.7-ICM-FP007 and later release to address *\n * this issue. *\n ****************************************************************\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Missing checks of current user permission and disabling the\n start and disable where appropriate. Added code to only enable\n start and disable when the current user has appropriate\n permission. This fix is included in 5.2.1.7-ICM-FP007 and later\n releases.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PJ44931\n \n \n * REPORTED COMPONENT NAME\n CASE MGR CLIENT\n \n \n * REPORTED COMPONENT ID\n 5725A1501\n \n \n * REPORTED RELEASE\n 521\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 2017-08-04\n \n \n * CLOSED DATE\n 2017-08-22\n \n \n * LAST MODIFIED DATE\n 2017-08-22\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 PJ45075 [http://www-01.ibm.com/support/docview.wss?uid=swg1PJ45075]\n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n CASE MGR CLIENT\n \n \n * FIXED COMPONENT ID\n 5725A1501\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R521 PSY\n UP", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\n DIRECT LINKS TO FIXES\nIBM Case Manager V5.2.1 Fix Pack 5 for Linux for System Z [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.2.1.5-ICM-ZLINUX-FP005&source=SAR]\nIBM Case Manager V5.2.1 Fix Pack 5 for Windows [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.2.1.5-ICM-WIN-FP005&source=SAR]\nIBM Case Manager V5.2.1 Fix Pack 5 for Linux [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.2.1.5-ICM-LINUX-FP005&source=SAR]\nIBM Case Manager V5.2.1 Fix Pack 5 for AIX [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FCase+Manager&fixids=5.2.1.5-ICM-AIX-FP005&source=SAR]\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * When the user role is configured with more than 2 in-baskets the\n Get Next button does not work when the In-basket is first\n loaded. This issue occurs when the \"hide work item in role\n in-baskets\" is also set via the Work Page In-basket widget and\n the My Work in-basket is not the first tab for the role.\n \n Steps to reproduce:\n 1. Created 2 Roles in Case Builder (i.e. Role1, Role2)\n 2. In the Work page, In-basket toolbar widget, add a 'Get Next'\n button, with the 'Get next work item' action\n 3. In the Work page, In-basket Widget, select 'hide work item in\n role in-baskets'\n 4. Using Process Designer add the Role2 In-basket to Role1.\n Arrange the In-baskets so that the My Work In-basket appears\n last\n 5. Log on icm with user belongs to Role1.\n 6. In the Work page, when it first loaded, click on 'Get Next'\n button.\n \n Expected Results: The next work item is opened via the Work\n Detail page, or a popup message indicating there is no work\n \n Actual Results: Nothing happens when you click Get Next.\n \n \n \n \n \n\nLOCAL FIX\n * There are several workarounds available for this issue:\n 1. Switching to different In-basket and then switch back, the\n Get Next button will then work.\n 2. Change the in-basket order to have 'My Work' in-basket as the\n first tab\n 3. Do not set 'hide work item in Role in-basket'\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n * Customer requiring the use of Get Next button and Hide Work *\n * Item functionality where users have more than 2 in-baskets. *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * See Error Description *\n ****************************************************************\n * RECOMMENDATION: *\n * It is recommended to apply 5.2.1.5-ICM-FP005 or a later *\n * release. *\n ****************************************************************\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * This issue has been resolved in 5.2.1.5-ICM-FP005. The Get Next\n button will be functional for users with multiple in-baskets,\n Get Next button configured, and the Hide Work Item in role\n in-baskets enabled.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PJ44284\n \n \n * REPORTED COMPONENT NAME\n CASE MGR CLIENT\n \n \n * REPORTED COMPONENT ID\n 5725A1501\n \n \n * REPORTED RELEASE\n 521\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 2016-07-14\n \n \n * CLOSED DATE\n 2016-08-15\n \n \n * LAST MODIFIED DATE\n 2016-08-15\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 CASE MGR CLIENT\n \n \n * FIXED COMPONENT ID\n 5725A1501\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R521 PSY\n UP" ]

[ [ "0a", " PRODUCT DOCUMENTATION ABSTRACT" ], [ "0b", " 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." ], [ "0c", "However, the option should be disabled. CONTENT" ], [ "0d", "IBM Content Navigator disables the Log Out option under SSO environments." ], [ "0e", "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." ], [ "0f", "If 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." ], [ "0g", "To remove the Log Out option: 1." ], [ "0h", "In the administration tool, select Menus. 2." ], [ "0i", "Enter \"User\" in the Name contains filter field. 3." ], [ "0j", "Select the Default banner user session context menu and click Copy. 4." ], [ "0k", "Enter a name for the new menu such as \"Banner user session context menu - no Log Out option\". 5." ], [ "0l", "Remove the Log Out from the Selected list. 6." ], [ "0m", "Save the new menu. 7." ], [ "0n", "Open the Desktops configuration, then open your desktop configuration. 8." ], [ "0o", "Select the Menus tab and scroll to the Feature Context Menus section. 9." ], [ "0p", "Select the new menu that you created for the Banner user session context menu menu type. 10." ], [ "0q", "Save your desktop." ], [ "0r", "The change to the menus takes effect when the modified desktop is reloaded." ], [ "0s", "Cross reference information Segment Product Component Platform Version Edition Enterprise Content Management Case Manager AIX, Linux, Linux on System z, Windows 5.2.1.0" ] ]

[ "0b", "0c", "0d", "0e" ]

[ "too; many; open; files; suse; redhat; im; installation; manager; update; upgrade; ZipException; RTC TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to install or upgrade IBM Rational Team Concert products on Linux platforms using IBM Installation Manager result in the error \"Too many open files\". \n\nSYMPTOM\nIn many cases when this failure occurs, the Installation Manager will report that the install/update was successful, however checking the Installation Manager logs will reveal an error with stack traces as shown below. \n\nThe Rational Team Concert Eclipse Client does not start successfully after install or update. \n\nThe splash-screen shows but is immediately followed by an error dialog. \n\n \n\nThe following error message can be found in the IBM Installation Manager log: \n\njava.util.zip.ZipException: Too many open files /opt/IBM/IBMIMShared/plugins/org.eclipse.equinox.p2.updatesite_1.0.1.R34x_v20080808-1156.jar\nat java.util.zip.ZipFile.open(Native Method)\nat java.util.zip.ZipFile.<init>(ZipFile.java:238)\nat java.util.zip.ZipFile.<init>(ZipFile.java:268)\n(...)\n\nCAUSE\nRefer to jazz.net work item 87837 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/87837] for details.\n\n\n\nENVIRONMENT\nInstalling or updating the Rational Team Concert Eclipse Client version 2.0 or later with non-English language packs on Linux.\n\n\n\nDIAGNOSING THE PROBLEM\nTo see the current limits on the number of open files, run this command in a shell logged in as the user who performs product installation: \n\n\nulimit -n \n\n\nThe typical default is 1024. \n\n\nThe recommended limit is 65536 or higher.\n\n\n\nRESOLVING THE PROBLEM\nTo resolve this problem the limit of open files needs to be increased on Linux before installing or updating Rational Team Concert products.\n\n\nThere are two ways to configure the Linux system limits to avoid this problem. \n\n\n * If you have system administrator privileges (root account), the file /etc/security/limits.conf can be modified to include these lines: \n \n * hard nofile 65536 \n \n * soft nofile 65536 \n \n Restart the linux system after the limits.conf file is modified. \n \n * An individual user can increase the limits within a running shell with the following command: \n \n ulimit -n 65536 \n \n Note: If this solution is used, the Rational Team Concert launchpad or IBM Installation Manager must be started from the same shell to inherit the modified limits. \n\n\n\nIf Rational Team Concert is running on IBM WebSphere, the WebSphere startup script may need to be edited to include this configuration. 1. Navigate to the ../etc/init.d/was startup script\n \n 2. Add ulimit -n 65536 to the startup script\n \n\n\nSpecial instructions for Ubuntu As found in work item 153531 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/153531], Ubuntu sounds like not respecting the wildcard in /etc/security/limits.conf for the root user:\n\n\n * Change the above instructions for /etc/security/limits.conf to:\n root soft nofile 65536\n root hard nofile 65536\n \n * You can check the actual running process settings using: cat /proc/<pid>/limits\n \n * If you run as root, check the ulimit using: /bin/bash -c \"ulimit -n\"\n\n\n\n\n\n\nIf Rational Team Concert is running on IBM WebSphere, the WebSphere startup script may need to be edited to include this configuration. 1. Navigate to the ../etc/init.d/was startup script\n \n \n 2. Add ulimit -n 65536 to the startup script\n \n \n 3. Ensure that the Interscope Wily Agent is not running on WebSphere. \n There is a known defect with IBM Java 6 JVM (found in WebSphere 7.0.0.17) when using the Interscope Agent. This defect is fixed by APAR IZ99243, but it is advised to turn off the Interscope Agent.\n\n\n\n\n\n\nNote: Once these new settings have been applied, please proceed with a server re-index so as to fix possibly corrupted server indexes: \n\n * Rational Team Concert 2.x: <RTC_install_dir>/server/repotools -reindex Rational Team Concert 3.x: <RTC_install_dir>/server/repotools-jts -reindex \n * \n\nLeverage the Jazz Community Jazz and Rational Team Concert have an active community that can provide you with additional resources. Browse and contribute to the User forums, contribute to the Team Blog and review the Team wiki.\nRefer to technote 1319600 [http://ibm.com/support/docview.wss?uid=swg21319600] for details and links.\n\n\n\nRELATED INFORMATION\n#jazz.net work item 87837 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/87837]\njazz.net work item 139705 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/139705]\nUbuntu - jazz.net work item 153531 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/153531]\nA Korean translation is available [http://www.ibm.com/support/docview.wss?uid=swg21595834]", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n User launches the FAP Client. User clicks tab \"Data Marts\" and highlights relevant data mart. User clicks 'Start' and then clicks on the 'Logs' tab to track the progress.\nSoon after the Data Mart starts, the DM publish stops with an error.\nThe TM1 server has crashed/stopped too. \n\nSYMPTOM\nFAP Client: \n\n[/support/docview.wss?uid=swg21584569&aid=1] [/support/docview.wss?uid=swg21584569&aid=1]\nDescription\nINFO: FAP Service Started\nINFO: New active source detected and added to scheduling: <data_mart name>\nINFO: New active datamart detected and added to scheduling: <data_mart name>\nINFO: Start initial publish for datamart <data_mart name>\nINFO: Start initial publish of structure\nERROR: Could not execute TI process:Dim1_ExtDimProcess\n\nIn addition \n\n * If hover over the message \"Could not execute TI process...\", then you see \"SystemServerConnectionInvalid\" popup message \n * Also, the TM1 server's Windows service (e.g. called \"TM1 Server x64 / fap\") has stopped (on the TM1 server itself)\n\n\nIn the Event Viewer (Application Log): \nLog Name: Application \nSource: Application Error \nDate: 13/02/2012 13:34:23 \nEvent ID: 1000 \nTask Category: (100) \nLevel: Error \nKeywords: Classic \nUser: N/A \nComputer: SERVERNAME \nDescription: \nFaulting application name: tm1sd.exe, version: 9.5.20000.11857, time stamp: 0x4d5068c5 \nFaulting module name: SQORA32.DLL, version: 11.2.0.1, time stamp: 0x4bb1d732 \nException code: 0xc0000094 \nFault offset: 0x000000000001228a \nFaulting process id: 0x828 \nFaulting application start time: 0x01ccea542bb7e52a \nFaulting application path: C:\\Program Files\\Cognos\\TM1\\bin\\tm1sd.exe \nFaulting module path: C:\\app64\\Administrator\\product\\11.2.0\\client_1\\BIN\\SQORA32.DLL \nReport Id: 70380cb6-5647-11e1-9d62-0050569c41ea CAUSE\nThere are many potential causes for the 'Could not execute TI process:Dim1_ExtDimProcess' error. \n\n * For more examples, see separate IBM Technote #1446983\n\n\nThis Technote specifically relates to the scenario where the FAP data mart publish has failed, due to the TM1 server itself (the Windows service \" TM1 Server x64 / xxxx\") crashing/stopping. * In turn, the cause why the TM1 server has crashed is because of a third-party (Oracle) bug in their client software, which causes memory problems on the server when using Oracle's \"SQLFetchScroll ODBC\" API method to communicate to the database server. * For more information, see separate Technotes #1455342 & 1440596.\n \n \n\nENVIRONMENT\nController/FAP database hosted on Oracle database server.\n\n\n\nRESOLVING THE PROBLEM\nReconfigure TM1 server to communicate to the Oracle server via an alternative method (different Oracle API). \n\n * This is achieved by using the following setting: UseSQLExtendedFetch=T\n\n\nSteps: \n\n 1. Logon to TM1 server as an administrator \n 2. Using Windows Explorer, browse to the location of your TM1 server (for example C:\\TM1Data\\FAP) \n 3. Open the file \"Tm1s.CFG\" in NOTEPAD.EXE \n 4. Underneath the heading \"[TM1S]\", add the following line: UseSQLExtendedFetch=T \n 5. Save the file \n 6. Restart the TM1 Windows service (e.g. \"TM1 Server x64 / fap\")\n\nRELATED INFORMATION\n#1446983 - ** Troubleshooting ** \"Could not execute TI p [http://www.ibm.com/support/docview.wss?uid=swg21446983]\n1455342 - Oracle driver problem when importing data to [http://www.ibm.com/support/docview.wss?uid=swg21455342]\n1440596 - TM1 Turbo Integrator process crashes server w [http://www.ibm.com/support/docview.wss?uid=swg21440596]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics Cognos TM1 TM1 Windows 9.5.2", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n User received the below error while accessing the Cogos Portal\n\"AAA-SYS-0001 - java.util.MissingResourceException: Can't find bundle for base name DispatcherMessages, locale fr\" \n\nSYMPTOM\nErrors found in pogo log files \n\nERROR [contentmanager.coordinator.ActiveCMControl] Timer-23: DPR-CMI-4007 Impossible d'exécuter une instance active de Content Manager sur le noeud IP local. Pour plus d'information, consultez les journaux détaillés du répartiteur et de Content Manager. Assurez-vous que le service local de Content Manager est démarré. com.cognos.pogo.bibus.CommandExecutionException: Failed to send HTTP request or read HTTP response\nat com.cognos.pogo.bibus.BIBusCommand.handleDefaultException(BIBusCommand.java:310)\n\n\nFATAL [m.cognos.pogo.reportservice.ProcessManager] CAMLPS-ProcessMgrThread: External Report Server process CAM_LPSvr cannot be started java.io.IOException: Cannot run program \"/u03/cognos/c10_64/bin64/CAM_LPSvr\" (in directory \"/u03/cognos/c10_64/bin64\"): java.io.IOException: error=24, Too many open files\nat java.lang.ProcessBuilder.start(Unknown Source)\n\n\nCAUSE\nulimit\n\n\nENVIRONMENT\nLinux Cognos 10.1.1\n\n\n\nDIAGNOSING THE PROBLEM\nopen files (-n) 1024 \n\n\n\nRESOLVING THE PROBLEM\nIncrease the open file limit \n\nThe minimum is 2048 like documented in \"IBM Cognos Business Intelligence Version 10.1.1: Installation and Configuration Guide\" \n- Requirement: Operating system specifications File descriptor limit set to 2048 on UNIX and Linu", "wasrun; wasjdk; open; files; too; ProblemDeterminationDocument; JCC was appserver app server TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote explains how to debug the \"Too many open files\" error message on Microsoft Windows, AIX, Linux and Solaris operating systems. \n\nSYMPTOM\nThe following messages could be displayed when the process has exhausted the file handle limit: \n\njava.io.IOException: Too many open files\n\n[3/14/15 9:26:53:589 EDT] 14142136 prefs W Could not lock User prefs. Unix error code 24.\n\nNew sockets/file descriptors can not be opened after the limit has been reached. \n\n\nCAUSE\nSystem configuration limitation.\n\nWhen the \"Too Many Open Files\" error message is written to the logs, it indicates that all available file handles for the process have been used (this includes sockets as well). In a majority of cases, this is the result of file handles being leaked by some part of the application. This technote explains how to collect output that identifies what file handles are in use at the time of the error condition.\n\n\nRESOLVING THE PROBLEM\n\n\n\n\nDetermine Ulimits\n\nOn UNIX and Linux operating systems, the ulimit for the number of file handles can be configured, and it is usually set too low by default. Increasing this ulimit to 8000 is usually sufficient for normal runtime, but this depends on your applications and your file/socket usage. Additionally, file descriptor leaks can still occur even with a high value. \n\nDisplay the current soft limit:\nulimit -Sn\n\nDisplay the current hard limit:\nulimit -Hn\n\nOr capture a Javacore, the limit will be listed in that file under the name NOFILE:\nkill -3 PID\n\n\nPlease see the following document if you would like more information on where you can edit ulimits:\nGuidelines for setting ulimits (WebSphere Application Server)\nhttp://www.IBM.com/support/docview.wss?rs=180&uid=swg21469413 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21469413]\n\n\nOperating Systems \n\nWindows By default, Windows does not ship with a tool to debug this type of problem. Instead Microsoft provides a tool that you can download called Process Explorer [http://technet.microsoft.com/en-us/sysinternals/bb896653]. This tool identifies the open handles/files associated with the Java™ process (but usually not sockets opened by the Winsock component) and determines which handles are still opened. These handles result in the \"Too many open files\" error message. \n\nTo display the handles, click on the Gear Icon [/support/docview.wss?uid=swg21067352&amp;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", "DASHL2; JazzSM; too many open files; ulimit; open files; descriptors TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The Dashboard Application Services Hub (DASH) - JazzSM service shuts down automatically after running for a few hours. The systemOut log has messages indicating: \"Too many open files\" \n\nCAUSE\nThe open files ulimit option is set too low for the OS user that run the DASH server process\n\nDIAGNOSING THE PROBLEM\nThe SystemOut may contain messages like:\n###\n[9/30/15 9:09:07:765 EDT] 000000a6 HttpMethodDir I \norg.apache.commons.httpclient.HttpMethodDirector executeWithRetry I/O \nexception (java.net.SocketException) caught when processing request: Too\nmany open files \n### \n\nCheck the ulimit settings for the user. Execute the following on the command line:\n\nulimit -a \n\nRESOLVING THE PROBLEM\nWebsphere Support generally recommends a minimum value of 8000 for the open files ulimit setting. To increase the value to 8000 execute:\n\nulimit -n 8000\n\nThat value can be used initially and increased if it determined to be too low. The value is only good for the current log in session. Once a working value is determined, the value must be set at the system level to make it permanent. The following Websphere documentation provides more detail on setting the ulimit value:\n\n\n\n\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21469413 [http://www-01.ibm.com/support/docview.wss?uid=swg21469413]" ]

[ [ "0a", "too; many; open; files; suse; redhat; im; installation; manager; update; upgrade; ZipException; RTC TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "0b", " Attempts to install or upgrade IBM Rational Team Concert products on Linux platforms using IBM Installation Manager result in the error \"Too many open files\". SYMPTOM" ], [ "0c", "In many cases when this failure occurs, the Installation Manager will report that the install/update was successful, however checking the Installation Manager logs will reveal an error with stack traces as shown below." ], [ "0d", "The Rational Team Concert Eclipse Client does not start successfully after install or update." ], [ "0e", "The splash-screen shows but is immediately followed by an error dialog." ], [ "0f", "The following error message can be found in the IBM Installation Manager log:" ], [ "0g", "java.util.zip.ZipException: Too many open files /opt/IBM/IBMIMShared/plugins/org.eclipse.equinox.p2.updatesite_1.0.1.R34x_v20080808-1156.jar" ], [ "0h", "at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:238) at java.util.zip.ZipFile.<init>(ZipFile.java:268) (...) CAUSE" ], [ "0i", "Refer to jazz.net work item 87837 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/87837] for details. ENVIRONMENT" ], [ "0j", "Installing or updating the Rational Team Concert Eclipse Client version 2.0 or later with non-English language packs on Linux." ], [ "0k", "DIAGNOSING THE PROBLEM" ], [ "0l", "To see the current limits on the number of open files, run this command in a shell logged in as the user who performs product installation: ulimit -n" ], [ "0m", "The typical default is 1024." ], [ "0n", "The recommended limit is 65536 or higher." ], [ "0o", "RESOLVING THE PROBLEM" ], [ "0p", "To resolve this problem the limit of open files needs to be increased on Linux before installing or updating Rational Team Concert products." ], [ "0q", "There are two ways to configure the Linux system limits to avoid this problem." ], [ "0r", " * If you have system administrator privileges (root account), the file /etc/security/limits.conf can be modified to include these lines:" ], [ "0s", " * hard nofile 65536" ], [ "0t", " * soft nofile 65536" ], [ "0u", " Restart the linux system after the limits.conf file is modified." ], [ "0v", " * An individual user can increase the limits within a running shell with the following command:" ], [ "0w", " ulimit -n 65536" ], [ "0x", " Note: If this solution is used, the Rational Team Concert launchpad or IBM Installation Manager must be started from the same shell to inherit the modified limits." ], [ "0y", "If Rational Team Concert is running on IBM WebSphere, the WebSphere startup script may need to be edited to include this configuration. 1." ], [ "0z", "Navigate to the ../etc/init.d/was startup script 2." ], [ "0aa", "Add ulimit -n 65536 to the startup script" ], [ "0ab", "Special instructions for Ubuntu As found in work item 153531 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/153531], Ubuntu sounds like not respecting the wildcard in /etc/security/limits.conf for the root user:" ], [ "0ac", " * Change the above instructions for /etc/security/limits.conf to:" ], [ "0ad", " root soft nofile 65536" ], [ "0ae", " root hard nofile 65536" ], [ "0af", " * You can check the actual running process settings using: cat /proc/<pid>/limits" ], [ "0ag", " * If you run as root, check the ulimit using: /bin/bash -c \"ulimit -n\"" ], [ "0ah", "If Rational Team Concert is running on IBM WebSphere, the WebSphere startup script may need to be edited to include this configuration. 1." ], [ "0ai", "Navigate to the ../etc/init.d/was startup script 2." ], [ "0aj", "Add ulimit -n 65536 to the startup script 3." ], [ "0ak", "Ensure that the Interscope Wily Agent is not running on WebSphere." ], [ "0al", " There is a known defect with IBM Java 6 JVM (found in WebSphere 7.0.0.17) when using the Interscope Agent." ], [ "0am", "This defect is fixed by APAR IZ99243, but it is advised to turn off the Interscope Agent." ], [ "0an", "Note: Once these new settings have been applied, please proceed with a server re-index so as to fix possibly corrupted server indexes:" ], [ "0ao", " * Rational Team Concert 2.x: <RTC_install_dir>/server/repotools -reindex Rational Team Concert 3.x: <RTC_install_dir>/server/repotools-jts -reindex *" ], [ "0ap", "Leverage the Jazz Community Jazz and Rational Team Concert have an active community that can provide you with additional resources." ], [ "0aq", "Browse and contribute to the User forums, contribute to the Team Blog and review the Team wiki." ], [ "0ar", "Refer to technote 1319600 [http://ibm.com/support/docview.wss?uid=swg21319600] for details and links. RELATED INFORMATION" ], [ "0as", "#jazz.net work item 87837 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/87837]" ], [ "0at", "jazz.net work item 139705 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/139705]" ], [ "0au", "Ubuntu - jazz.net work item 153531 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/153531]" ], [ "0av", "A Korean translation is available [http://www.ibm.com/support/docview.wss?uid=swg21595834]" ] ]

[ "0l", "0m", "0n", "0o", "0p", "0q", "0r", "0s", "0t", "0u", "0w", "0x", "3l", "3m", "3n", "3o", "3p", "3q", "3s", "4d", "4k", "4n", "4o", "4p", "4q", "4r" ]

[ "too; many; open; files; suse; redhat; im; installation; manager; update; upgrade; ZipException; RTC TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to install or upgrade IBM Rational Team Concert products on Linux platforms using IBM Installation Manager result in the error \"Too many open files\". \n\nSYMPTOM\nIn many cases when this failure occurs, the Installation Manager will report that the install/update was successful, however checking the Installation Manager logs will reveal an error with stack traces as shown below. \n\nThe Rational Team Concert Eclipse Client does not start successfully after install or update. \n\nThe splash-screen shows but is immediately followed by an error dialog. \n\n \n\nThe following error message can be found in the IBM Installation Manager log: \n\njava.util.zip.ZipException: Too many open files /opt/IBM/IBMIMShared/plugins/org.eclipse.equinox.p2.updatesite_1.0.1.R34x_v20080808-1156.jar\nat java.util.zip.ZipFile.open(Native Method)\nat java.util.zip.ZipFile.<init>(ZipFile.java:238)\nat java.util.zip.ZipFile.<init>(ZipFile.java:268)\n(...)\n\nCAUSE\nRefer to jazz.net work item 87837 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/87837] for details.\n\n\n\nENVIRONMENT\nInstalling or updating the Rational Team Concert Eclipse Client version 2.0 or later with non-English language packs on Linux.\n\n\n\nDIAGNOSING THE PROBLEM\nTo see the current limits on the number of open files, run this command in a shell logged in as the user who performs product installation: \n\n\nulimit -n \n\n\nThe typical default is 1024. \n\n\nThe recommended limit is 65536 or higher.\n\n\n\nRESOLVING THE PROBLEM\nTo resolve this problem the limit of open files needs to be increased on Linux before installing or updating Rational Team Concert products.\n\n\nThere are two ways to configure the Linux system limits to avoid this problem. \n\n\n * If you have system administrator privileges (root account), the file /etc/security/limits.conf can be modified to include these lines: \n \n * hard nofile 65536 \n \n * soft nofile 65536 \n \n Restart the linux system after the limits.conf file is modified. \n \n * An individual user can increase the limits within a running shell with the following command: \n \n ulimit -n 65536 \n \n Note: If this solution is used, the Rational Team Concert launchpad or IBM Installation Manager must be started from the same shell to inherit the modified limits. \n\n\n\nIf Rational Team Concert is running on IBM WebSphere, the WebSphere startup script may need to be edited to include this configuration. 1. Navigate to the ../etc/init.d/was startup script\n \n 2. Add ulimit -n 65536 to the startup script\n \n\n\nSpecial instructions for Ubuntu As found in work item 153531 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/153531], Ubuntu sounds like not respecting the wildcard in /etc/security/limits.conf for the root user:\n\n\n * Change the above instructions for /etc/security/limits.conf to:\n root soft nofile 65536\n root hard nofile 65536\n \n * You can check the actual running process settings using: cat /proc/<pid>/limits\n \n * If you run as root, check the ulimit using: /bin/bash -c \"ulimit -n\"\n\n\n\n\n\n\nIf Rational Team Concert is running on IBM WebSphere, the WebSphere startup script may need to be edited to include this configuration. 1. Navigate to the ../etc/init.d/was startup script\n \n \n 2. Add ulimit -n 65536 to the startup script\n \n \n 3. Ensure that the Interscope Wily Agent is not running on WebSphere. \n There is a known defect with IBM Java 6 JVM (found in WebSphere 7.0.0.17) when using the Interscope Agent. This defect is fixed by APAR IZ99243, but it is advised to turn off the Interscope Agent.\n\n\n\n\n\n\nNote: Once these new settings have been applied, please proceed with a server re-index so as to fix possibly corrupted server indexes: \n\n * Rational Team Concert 2.x: <RTC_install_dir>/server/repotools -reindex Rational Team Concert 3.x: <RTC_install_dir>/server/repotools-jts -reindex \n * \n\nLeverage the Jazz Community Jazz and Rational Team Concert have an active community that can provide you with additional resources. Browse and contribute to the User forums, contribute to the Team Blog and review the Team wiki.\nRefer to technote 1319600 [http://ibm.com/support/docview.wss?uid=swg21319600] for details and links.\n\n\n\nRELATED INFORMATION\n#jazz.net work item 87837 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/87837]\njazz.net work item 139705 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/139705]\nUbuntu - jazz.net work item 153531 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/153531]\nA Korean translation is available [http://www.ibm.com/support/docview.wss?uid=swg21595834]", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n User launches the FAP Client. User clicks tab \"Data Marts\" and highlights relevant data mart. User clicks 'Start' and then clicks on the 'Logs' tab to track the progress.\nSoon after the Data Mart starts, the DM publish stops with an error.\nThe TM1 server has crashed/stopped too. \n\nSYMPTOM\nFAP Client: \n\n[/support/docview.wss?uid=swg21584569&aid=1] [/support/docview.wss?uid=swg21584569&aid=1]\nDescription\nINFO: FAP Service Started\nINFO: New active source detected and added to scheduling: <data_mart name>\nINFO: New active datamart detected and added to scheduling: <data_mart name>\nINFO: Start initial publish for datamart <data_mart name>\nINFO: Start initial publish of structure\nERROR: Could not execute TI process:Dim1_ExtDimProcess\n\nIn addition \n\n * If hover over the message \"Could not execute TI process...\", then you see \"SystemServerConnectionInvalid\" popup message \n * Also, the TM1 server's Windows service (e.g. called \"TM1 Server x64 / fap\") has stopped (on the TM1 server itself)\n\n\nIn the Event Viewer (Application Log): \nLog Name: Application \nSource: Application Error \nDate: 13/02/2012 13:34:23 \nEvent ID: 1000 \nTask Category: (100) \nLevel: Error \nKeywords: Classic \nUser: N/A \nComputer: SERVERNAME \nDescription: \nFaulting application name: tm1sd.exe, version: 9.5.20000.11857, time stamp: 0x4d5068c5 \nFaulting module name: SQORA32.DLL, version: 11.2.0.1, time stamp: 0x4bb1d732 \nException code: 0xc0000094 \nFault offset: 0x000000000001228a \nFaulting process id: 0x828 \nFaulting application start time: 0x01ccea542bb7e52a \nFaulting application path: C:\\Program Files\\Cognos\\TM1\\bin\\tm1sd.exe \nFaulting module path: C:\\app64\\Administrator\\product\\11.2.0\\client_1\\BIN\\SQORA32.DLL \nReport Id: 70380cb6-5647-11e1-9d62-0050569c41ea CAUSE\nThere are many potential causes for the 'Could not execute TI process:Dim1_ExtDimProcess' error. \n\n * For more examples, see separate IBM Technote #1446983\n\n\nThis Technote specifically relates to the scenario where the FAP data mart publish has failed, due to the TM1 server itself (the Windows service \" TM1 Server x64 / xxxx\") crashing/stopping. * In turn, the cause why the TM1 server has crashed is because of a third-party (Oracle) bug in their client software, which causes memory problems on the server when using Oracle's \"SQLFetchScroll ODBC\" API method to communicate to the database server. * For more information, see separate Technotes #1455342 & 1440596.\n \n \n\nENVIRONMENT\nController/FAP database hosted on Oracle database server.\n\n\n\nRESOLVING THE PROBLEM\nReconfigure TM1 server to communicate to the Oracle server via an alternative method (different Oracle API). \n\n * This is achieved by using the following setting: UseSQLExtendedFetch=T\n\n\nSteps: \n\n 1. Logon to TM1 server as an administrator \n 2. Using Windows Explorer, browse to the location of your TM1 server (for example C:\\TM1Data\\FAP) \n 3. Open the file \"Tm1s.CFG\" in NOTEPAD.EXE \n 4. Underneath the heading \"[TM1S]\", add the following line: UseSQLExtendedFetch=T \n 5. Save the file \n 6. Restart the TM1 Windows service (e.g. \"TM1 Server x64 / fap\")\n\nRELATED INFORMATION\n#1446983 - ** Troubleshooting ** \"Could not execute TI p [http://www.ibm.com/support/docview.wss?uid=swg21446983]\n1455342 - Oracle driver problem when importing data to [http://www.ibm.com/support/docview.wss?uid=swg21455342]\n1440596 - TM1 Turbo Integrator process crashes server w [http://www.ibm.com/support/docview.wss?uid=swg21440596]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics Cognos TM1 TM1 Windows 9.5.2", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n User received the below error while accessing the Cogos Portal\n\"AAA-SYS-0001 - java.util.MissingResourceException: Can't find bundle for base name DispatcherMessages, locale fr\" \n\nSYMPTOM\nErrors found in pogo log files \n\nERROR [contentmanager.coordinator.ActiveCMControl] Timer-23: DPR-CMI-4007 Impossible d'exécuter une instance active de Content Manager sur le noeud IP local. Pour plus d'information, consultez les journaux détaillés du répartiteur et de Content Manager. Assurez-vous que le service local de Content Manager est démarré. com.cognos.pogo.bibus.CommandExecutionException: Failed to send HTTP request or read HTTP response\nat com.cognos.pogo.bibus.BIBusCommand.handleDefaultException(BIBusCommand.java:310)\n\n\nFATAL [m.cognos.pogo.reportservice.ProcessManager] CAMLPS-ProcessMgrThread: External Report Server process CAM_LPSvr cannot be started java.io.IOException: Cannot run program \"/u03/cognos/c10_64/bin64/CAM_LPSvr\" (in directory \"/u03/cognos/c10_64/bin64\"): java.io.IOException: error=24, Too many open files\nat java.lang.ProcessBuilder.start(Unknown Source)\n\n\nCAUSE\nulimit\n\n\nENVIRONMENT\nLinux Cognos 10.1.1\n\n\n\nDIAGNOSING THE PROBLEM\nopen files (-n) 1024 \n\n\n\nRESOLVING THE PROBLEM\nIncrease the open file limit \n\nThe minimum is 2048 like documented in \"IBM Cognos Business Intelligence Version 10.1.1: Installation and Configuration Guide\" \n- Requirement: Operating system specifications File descriptor limit set to 2048 on UNIX and Linu", "wasrun; wasjdk; open; files; too; ProblemDeterminationDocument; JCC was appserver app server TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote explains how to debug the \"Too many open files\" error message on Microsoft Windows, AIX, Linux and Solaris operating systems. \n\nSYMPTOM\nThe following messages could be displayed when the process has exhausted the file handle limit: \n\njava.io.IOException: Too many open files\n\n[3/14/15 9:26:53:589 EDT] 14142136 prefs W Could not lock User prefs. Unix error code 24.\n\nNew sockets/file descriptors can not be opened after the limit has been reached. \n\n\nCAUSE\nSystem configuration limitation.\n\nWhen the \"Too Many Open Files\" error message is written to the logs, it indicates that all available file handles for the process have been used (this includes sockets as well). In a majority of cases, this is the result of file handles being leaked by some part of the application. This technote explains how to collect output that identifies what file handles are in use at the time of the error condition.\n\n\nRESOLVING THE PROBLEM\n\n\n\n\nDetermine Ulimits\n\nOn UNIX and Linux operating systems, the ulimit for the number of file handles can be configured, and it is usually set too low by default. Increasing this ulimit to 8000 is usually sufficient for normal runtime, but this depends on your applications and your file/socket usage. Additionally, file descriptor leaks can still occur even with a high value. \n\nDisplay the current soft limit:\nulimit -Sn\n\nDisplay the current hard limit:\nulimit -Hn\n\nOr capture a Javacore, the limit will be listed in that file under the name NOFILE:\nkill -3 PID\n\n\nPlease see the following document if you would like more information on where you can edit ulimits:\nGuidelines for setting ulimits (WebSphere Application Server)\nhttp://www.IBM.com/support/docview.wss?rs=180&uid=swg21469413 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21469413]\n\n\nOperating Systems \n\nWindows By default, Windows does not ship with a tool to debug this type of problem. Instead Microsoft provides a tool that you can download called Process Explorer [http://technet.microsoft.com/en-us/sysinternals/bb896653]. This tool identifies the open handles/files associated with the Java™ process (but usually not sockets opened by the Winsock component) and determines which handles are still opened. These handles result in the \"Too many open files\" error message. \n\nTo display the handles, click on the Gear Icon [/support/docview.wss?uid=swg21067352&amp;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", "DASHL2; JazzSM; too many open files; ulimit; open files; descriptors TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The Dashboard Application Services Hub (DASH) - JazzSM service shuts down automatically after running for a few hours. The systemOut log has messages indicating: \"Too many open files\" \n\nCAUSE\nThe open files ulimit option is set too low for the OS user that run the DASH server process\n\nDIAGNOSING THE PROBLEM\nThe SystemOut may contain messages like:\n###\n[9/30/15 9:09:07:765 EDT] 000000a6 HttpMethodDir I \norg.apache.commons.httpclient.HttpMethodDirector executeWithRetry I/O \nexception (java.net.SocketException) caught when processing request: Too\nmany open files \n### \n\nCheck the ulimit settings for the user. Execute the following on the command line:\n\nulimit -a \n\nRESOLVING THE PROBLEM\nWebsphere Support generally recommends a minimum value of 8000 for the open files ulimit setting. To increase the value to 8000 execute:\n\nulimit -n 8000\n\nThat value can be used initially and increased if it determined to be too low. The value is only good for the current log in session. Once a working value is determined, the value must be set at the system level to make it permanent. The following Websphere documentation provides more detail on setting the ulimit value:\n\n\n\n\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21469413 [http://www-01.ibm.com/support/docview.wss?uid=swg21469413]" ]

[ [ "3a", "wasrun; wasjdk; open; files; too; ProblemDeterminationDocument; JCC was appserver app server TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "3b", " This technote explains how to debug the \"Too many open files\" error message on Microsoft Windows, AIX, Linux and Solaris operating systems. SYMPTOM" ], [ "3c", "The following messages could be displayed when the process has exhausted the file handle limit:" ], [ "3d", "java.io.IOException: Too many open files" ], [ "3e", "[3/14/15 9:26:53:589 EDT] 14142136 prefs W Could not lock User prefs." ], [ "3f", "Unix error code 24." ], [ "3g", "New sockets/file descriptors can not be opened after the limit has been reached. CAUSE" ], [ "3h", "System configuration limitation." ], [ "3i", "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)." ], [ "3j", "In a majority of cases, this is the result of file handles being leaked by some part of the application." ], [ "3k", "This technote explains how to collect output that identifies what file handles are in use at the time of the error condition." ], [ "3l", "RESOLVING THE PROBLEM Determine Ulimits" ], [ "3m", "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." ], [ "3n", "Increasing this ulimit to 8000 is usually sufficient for normal runtime, but this depends on your applications and your file/socket usage." ], [ "3o", "Additionally, file descriptor leaks can still occur even with a high value." ], [ "3p", "Display the current soft limit: ulimit -Sn" ], [ "3q", "Display the current hard limit: ulimit -Hn" ], [ "3r", "Or capture a Javacore, the limit will be listed in that file under the name NOFILE:" ], [ "3s", "kill -3 PID" ], [ "3t", "Please see the following document if you would like more information on where you can edit ulimits:" ], [ "3u", "Guidelines for setting ulimits (WebSphere Application Server) http://www.IBM.com/support/docview.wss?rs=180&uid=swg21469413 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21469413] Operating Systems" ], [ "3v", "Windows By default, Windows does not ship with a tool to debug this type of problem." ], [ "3w", "Instead Microsoft provides a tool that you can download called Process Explorer [http://technet.microsoft.com/en-us/sysinternals/bb896653]." ], [ "3x", "This tool identifies the open handles/files associated with the Java™ process (but usually not sockets opened by the Winsock component) and determines which handles are still opened." ], [ "3y", "These handles result in the \"Too many open files\" error message." ], [ "3z", "To display the handles, click on the Gear Icon [/support/docview.wss?uid=swg21067352&amp;aid=1] in the toolbar (or press CTRL+ H to toggle the handles view)." ], [ "3aa", "The icon will change to the icon for DLL files (so you can toggle it back to the DLL view)." ], [ "3ab", "It is important that you change the Refresh Rate." ], [ "3ac", "Select View > Update Speed, and change it to 5 seconds. [/support/docview.wss?uid=swg21067352&aid=2] [/support/docview.wss?uid=swg21067352&aid=2]" ], [ "3ad", "There is also another Microsoft utility called Handle that you can download from the following URL: https://technet.microsoft.com/en-us/sysinternals/bb896655.aspx [https://technet.microsoft.com/en-us/sysinternals/bb896655.aspx]" ], [ "3ae", "This tool is a command line version of Process Explorer." ], [ "3af", "The URL above contains the usage instructions. AIX" ], [ "3ag", "The commands lsof and procfiles are usually the best commands to determine what files and sockets are opened.. lsof" ], [ "3ah", "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:" ], [ "3ai", "lsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out" ], [ "3aj", "This output does not give the actual file names to which the handles are open." ], [ "3ak", "It provides only the name of the file system (directory) in which they are contained." ], [ "3al", "The lsof command indicates if the open file is associated with an open socket or a file." ], [ "3am", "When it references a file, it identifies the file system and the inode, not the file name." ], [ "3an", "It is best to capture lsof several times to see the rate of growth in the file descriptors. procfiles" ], [ "3ao", "The procfiles command does provide similar information, and also displays the full filenames loaded." ], [ "3ap", "It may not show sockets in use." ], [ "3aq", "procfiles -n [PID] > procfiles.out" ], [ "3ar", "Other commands (to display filenames that are opened)" ], [ "3as", "INODES and DF" ], [ "3at", "df -kP filesystem_from_lsof | awk '{print $6}' | tail -1" ], [ "3au", ">> Note the filesystem name" ], [ "3av", "find filesystem_name -inum inode_from_lsof -print > filelist.out" ], [ "3aw", ">> Shows the actual file name svmon" ], [ "3ax", "svmon -P PID -m | grep pers (for JFS)" ], [ "3ay", "svmon -P PID -m | grep clnt (for JFS2, NFS)" ], [ "3az", "(this opens files in the format: filesystem_device:inode)" ], [ "3ba", "Use the same procedure as above for finding the actual file name." ], [ "3bb", "Linux To determine if the number of open files is growing over a period of time, issue lsof to report the open files against a PID on a periodic basis. For example:" ], [ "3bc", "lsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out" ], [ "3bd", "The output will provide you with all of the open files for the specified PID." ], [ "3be", "You will be able to determine which files are opened and which files are growing over time." ], [ "3bf", "It is best to capture lsof several times to see the rate of growth in the file descriptors." ], [ "3bg", "Alternately you can list the contents of the file descriptors as a list of symbolic links in the following directory, where you replace PID with the process ID." ], [ "3bh", "This is especially useful if you don't have access to the lsof command:" ], [ "3bi", "ls -al /proc/PID/fd" ], [ "3bj", "Solaris Run the following commands to monitor open file (socket) descriptors on Solaris: pfiles" ], [ "3bk", "/usr/proc/bin/pfiles [ PID ] > pfiles.out lsof" ], [ "3bl", "lsof -p [ PID ] > lsof.ou t" ], [ "3bm", "This will get one round of lsof output." ], [ "3bn", "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:" ], [ "3bo", "lsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out" ], [ "3bp", "It is best to capture lsof several times to see the rate of growth in the file descriptors. HP-UX lsof" ], [ "3bq", "lsof -p [ PID ] > lsof.out" ], [ "3br", "This will get one round of lsof output." ], [ "3bs", "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:" ], [ "3bt", "lsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out" ], [ "3bu", "It is best to capture lsof several times to see the rate of growth in the file descriptors." ], [ "3bv", "Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK" ] ]

[ "0l", "0m", "0n", "0o", "0p", "0q", "0r", "0s", "0t", "0u", "0w", "0x", "3l", "3m", "3n", "3o", "3p", "3q", "3s", "4d", "4k", "4n", "4o", "4p", "4q", "4r" ]

[ "too; many; open; files; suse; redhat; im; installation; manager; update; upgrade; ZipException; RTC TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to install or upgrade IBM Rational Team Concert products on Linux platforms using IBM Installation Manager result in the error \"Too many open files\". \n\nSYMPTOM\nIn many cases when this failure occurs, the Installation Manager will report that the install/update was successful, however checking the Installation Manager logs will reveal an error with stack traces as shown below. \n\nThe Rational Team Concert Eclipse Client does not start successfully after install or update. \n\nThe splash-screen shows but is immediately followed by an error dialog. \n\n \n\nThe following error message can be found in the IBM Installation Manager log: \n\njava.util.zip.ZipException: Too many open files /opt/IBM/IBMIMShared/plugins/org.eclipse.equinox.p2.updatesite_1.0.1.R34x_v20080808-1156.jar\nat java.util.zip.ZipFile.open(Native Method)\nat java.util.zip.ZipFile.<init>(ZipFile.java:238)\nat java.util.zip.ZipFile.<init>(ZipFile.java:268)\n(...)\n\nCAUSE\nRefer to jazz.net work item 87837 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/87837] for details.\n\n\n\nENVIRONMENT\nInstalling or updating the Rational Team Concert Eclipse Client version 2.0 or later with non-English language packs on Linux.\n\n\n\nDIAGNOSING THE PROBLEM\nTo see the current limits on the number of open files, run this command in a shell logged in as the user who performs product installation: \n\n\nulimit -n \n\n\nThe typical default is 1024. \n\n\nThe recommended limit is 65536 or higher.\n\n\n\nRESOLVING THE PROBLEM\nTo resolve this problem the limit of open files needs to be increased on Linux before installing or updating Rational Team Concert products.\n\n\nThere are two ways to configure the Linux system limits to avoid this problem. \n\n\n * If you have system administrator privileges (root account), the file /etc/security/limits.conf can be modified to include these lines: \n \n * hard nofile 65536 \n \n * soft nofile 65536 \n \n Restart the linux system after the limits.conf file is modified. \n \n * An individual user can increase the limits within a running shell with the following command: \n \n ulimit -n 65536 \n \n Note: If this solution is used, the Rational Team Concert launchpad or IBM Installation Manager must be started from the same shell to inherit the modified limits. \n\n\n\nIf Rational Team Concert is running on IBM WebSphere, the WebSphere startup script may need to be edited to include this configuration. 1. Navigate to the ../etc/init.d/was startup script\n \n 2. Add ulimit -n 65536 to the startup script\n \n\n\nSpecial instructions for Ubuntu As found in work item 153531 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/153531], Ubuntu sounds like not respecting the wildcard in /etc/security/limits.conf for the root user:\n\n\n * Change the above instructions for /etc/security/limits.conf to:\n root soft nofile 65536\n root hard nofile 65536\n \n * You can check the actual running process settings using: cat /proc/<pid>/limits\n \n * If you run as root, check the ulimit using: /bin/bash -c \"ulimit -n\"\n\n\n\n\n\n\nIf Rational Team Concert is running on IBM WebSphere, the WebSphere startup script may need to be edited to include this configuration. 1. Navigate to the ../etc/init.d/was startup script\n \n \n 2. Add ulimit -n 65536 to the startup script\n \n \n 3. Ensure that the Interscope Wily Agent is not running on WebSphere. \n There is a known defect with IBM Java 6 JVM (found in WebSphere 7.0.0.17) when using the Interscope Agent. This defect is fixed by APAR IZ99243, but it is advised to turn off the Interscope Agent.\n\n\n\n\n\n\nNote: Once these new settings have been applied, please proceed with a server re-index so as to fix possibly corrupted server indexes: \n\n * Rational Team Concert 2.x: <RTC_install_dir>/server/repotools -reindex Rational Team Concert 3.x: <RTC_install_dir>/server/repotools-jts -reindex \n * \n\nLeverage the Jazz Community Jazz and Rational Team Concert have an active community that can provide you with additional resources. Browse and contribute to the User forums, contribute to the Team Blog and review the Team wiki.\nRefer to technote 1319600 [http://ibm.com/support/docview.wss?uid=swg21319600] for details and links.\n\n\n\nRELATED INFORMATION\n#jazz.net work item 87837 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/87837]\njazz.net work item 139705 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/139705]\nUbuntu - jazz.net work item 153531 [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/153531]\nA Korean translation is available [http://www.ibm.com/support/docview.wss?uid=swg21595834]", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n User launches the FAP Client. User clicks tab \"Data Marts\" and highlights relevant data mart. User clicks 'Start' and then clicks on the 'Logs' tab to track the progress.\nSoon after the Data Mart starts, the DM publish stops with an error.\nThe TM1 server has crashed/stopped too. \n\nSYMPTOM\nFAP Client: \n\n[/support/docview.wss?uid=swg21584569&aid=1] [/support/docview.wss?uid=swg21584569&aid=1]\nDescription\nINFO: FAP Service Started\nINFO: New active source detected and added to scheduling: <data_mart name>\nINFO: New active datamart detected and added to scheduling: <data_mart name>\nINFO: Start initial publish for datamart <data_mart name>\nINFO: Start initial publish of structure\nERROR: Could not execute TI process:Dim1_ExtDimProcess\n\nIn addition \n\n * If hover over the message \"Could not execute TI process...\", then you see \"SystemServerConnectionInvalid\" popup message \n * Also, the TM1 server's Windows service (e.g. called \"TM1 Server x64 / fap\") has stopped (on the TM1 server itself)\n\n\nIn the Event Viewer (Application Log): \nLog Name: Application \nSource: Application Error \nDate: 13/02/2012 13:34:23 \nEvent ID: 1000 \nTask Category: (100) \nLevel: Error \nKeywords: Classic \nUser: N/A \nComputer: SERVERNAME \nDescription: \nFaulting application name: tm1sd.exe, version: 9.5.20000.11857, time stamp: 0x4d5068c5 \nFaulting module name: SQORA32.DLL, version: 11.2.0.1, time stamp: 0x4bb1d732 \nException code: 0xc0000094 \nFault offset: 0x000000000001228a \nFaulting process id: 0x828 \nFaulting application start time: 0x01ccea542bb7e52a \nFaulting application path: C:\\Program Files\\Cognos\\TM1\\bin\\tm1sd.exe \nFaulting module path: C:\\app64\\Administrator\\product\\11.2.0\\client_1\\BIN\\SQORA32.DLL \nReport Id: 70380cb6-5647-11e1-9d62-0050569c41ea CAUSE\nThere are many potential causes for the 'Could not execute TI process:Dim1_ExtDimProcess' error. \n\n * For more examples, see separate IBM Technote #1446983\n\n\nThis Technote specifically relates to the scenario where the FAP data mart publish has failed, due to the TM1 server itself (the Windows service \" TM1 Server x64 / xxxx\") crashing/stopping. * In turn, the cause why the TM1 server has crashed is because of a third-party (Oracle) bug in their client software, which causes memory problems on the server when using Oracle's \"SQLFetchScroll ODBC\" API method to communicate to the database server. * For more information, see separate Technotes #1455342 & 1440596.\n \n \n\nENVIRONMENT\nController/FAP database hosted on Oracle database server.\n\n\n\nRESOLVING THE PROBLEM\nReconfigure TM1 server to communicate to the Oracle server via an alternative method (different Oracle API). \n\n * This is achieved by using the following setting: UseSQLExtendedFetch=T\n\n\nSteps: \n\n 1. Logon to TM1 server as an administrator \n 2. Using Windows Explorer, browse to the location of your TM1 server (for example C:\\TM1Data\\FAP) \n 3. Open the file \"Tm1s.CFG\" in NOTEPAD.EXE \n 4. Underneath the heading \"[TM1S]\", add the following line: UseSQLExtendedFetch=T \n 5. Save the file \n 6. Restart the TM1 Windows service (e.g. \"TM1 Server x64 / fap\")\n\nRELATED INFORMATION\n#1446983 - ** Troubleshooting ** \"Could not execute TI p [http://www.ibm.com/support/docview.wss?uid=swg21446983]\n1455342 - Oracle driver problem when importing data to [http://www.ibm.com/support/docview.wss?uid=swg21455342]\n1440596 - TM1 Turbo Integrator process crashes server w [http://www.ibm.com/support/docview.wss?uid=swg21440596]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics Cognos TM1 TM1 Windows 9.5.2", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n User received the below error while accessing the Cogos Portal\n\"AAA-SYS-0001 - java.util.MissingResourceException: Can't find bundle for base name DispatcherMessages, locale fr\" \n\nSYMPTOM\nErrors found in pogo log files \n\nERROR [contentmanager.coordinator.ActiveCMControl] Timer-23: DPR-CMI-4007 Impossible d'exécuter une instance active de Content Manager sur le noeud IP local. Pour plus d'information, consultez les journaux détaillés du répartiteur et de Content Manager. Assurez-vous que le service local de Content Manager est démarré. com.cognos.pogo.bibus.CommandExecutionException: Failed to send HTTP request or read HTTP response\nat com.cognos.pogo.bibus.BIBusCommand.handleDefaultException(BIBusCommand.java:310)\n\n\nFATAL [m.cognos.pogo.reportservice.ProcessManager] CAMLPS-ProcessMgrThread: External Report Server process CAM_LPSvr cannot be started java.io.IOException: Cannot run program \"/u03/cognos/c10_64/bin64/CAM_LPSvr\" (in directory \"/u03/cognos/c10_64/bin64\"): java.io.IOException: error=24, Too many open files\nat java.lang.ProcessBuilder.start(Unknown Source)\n\n\nCAUSE\nulimit\n\n\nENVIRONMENT\nLinux Cognos 10.1.1\n\n\n\nDIAGNOSING THE PROBLEM\nopen files (-n) 1024 \n\n\n\nRESOLVING THE PROBLEM\nIncrease the open file limit \n\nThe minimum is 2048 like documented in \"IBM Cognos Business Intelligence Version 10.1.1: Installation and Configuration Guide\" \n- Requirement: Operating system specifications File descriptor limit set to 2048 on UNIX and Linu", "wasrun; wasjdk; open; files; too; ProblemDeterminationDocument; JCC was appserver app server TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote explains how to debug the \"Too many open files\" error message on Microsoft Windows, AIX, Linux and Solaris operating systems. \n\nSYMPTOM\nThe following messages could be displayed when the process has exhausted the file handle limit: \n\njava.io.IOException: Too many open files\n\n[3/14/15 9:26:53:589 EDT] 14142136 prefs W Could not lock User prefs. Unix error code 24.\n\nNew sockets/file descriptors can not be opened after the limit has been reached. \n\n\nCAUSE\nSystem configuration limitation.\n\nWhen the \"Too Many Open Files\" error message is written to the logs, it indicates that all available file handles for the process have been used (this includes sockets as well). In a majority of cases, this is the result of file handles being leaked by some part of the application. This technote explains how to collect output that identifies what file handles are in use at the time of the error condition.\n\n\nRESOLVING THE PROBLEM\n\n\n\n\nDetermine Ulimits\n\nOn UNIX and Linux operating systems, the ulimit for the number of file handles can be configured, and it is usually set too low by default. Increasing this ulimit to 8000 is usually sufficient for normal runtime, but this depends on your applications and your file/socket usage. Additionally, file descriptor leaks can still occur even with a high value. \n\nDisplay the current soft limit:\nulimit -Sn\n\nDisplay the current hard limit:\nulimit -Hn\n\nOr capture a Javacore, the limit will be listed in that file under the name NOFILE:\nkill -3 PID\n\n\nPlease see the following document if you would like more information on where you can edit ulimits:\nGuidelines for setting ulimits (WebSphere Application Server)\nhttp://www.IBM.com/support/docview.wss?rs=180&uid=swg21469413 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21469413]\n\n\nOperating Systems \n\nWindows By default, Windows does not ship with a tool to debug this type of problem. Instead Microsoft provides a tool that you can download called Process Explorer [http://technet.microsoft.com/en-us/sysinternals/bb896653]. This tool identifies the open handles/files associated with the Java™ process (but usually not sockets opened by the Winsock component) and determines which handles are still opened. These handles result in the \"Too many open files\" error message. \n\nTo display the handles, click on the Gear Icon [/support/docview.wss?uid=swg21067352&amp;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", "DASHL2; JazzSM; too many open files; ulimit; open files; descriptors TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The Dashboard Application Services Hub (DASH) - JazzSM service shuts down automatically after running for a few hours. The systemOut log has messages indicating: \"Too many open files\" \n\nCAUSE\nThe open files ulimit option is set too low for the OS user that run the DASH server process\n\nDIAGNOSING THE PROBLEM\nThe SystemOut may contain messages like:\n###\n[9/30/15 9:09:07:765 EDT] 000000a6 HttpMethodDir I \norg.apache.commons.httpclient.HttpMethodDirector executeWithRetry I/O \nexception (java.net.SocketException) caught when processing request: Too\nmany open files \n### \n\nCheck the ulimit settings for the user. Execute the following on the command line:\n\nulimit -a \n\nRESOLVING THE PROBLEM\nWebsphere Support generally recommends a minimum value of 8000 for the open files ulimit setting. To increase the value to 8000 execute:\n\nulimit -n 8000\n\nThat value can be used initially and increased if it determined to be too low. The value is only good for the current log in session. Once a working value is determined, the value must be set at the system level to make it permanent. The following Websphere documentation provides more detail on setting the ulimit value:\n\n\n\n\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21469413 [http://www-01.ibm.com/support/docview.wss?uid=swg21469413]" ]

[ [ "4a", "DASHL2; JazzSM; too many open files; ulimit; open files; descriptors TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "4b", " The Dashboard Application Services Hub (DASH) - JazzSM service shuts down automatically after running for a few hours." ], [ "4c", "The systemOut log has messages indicating: \"Too many open files\" CAUSE" ], [ "4d", "The open files ulimit option is set too low for the OS user that run the DASH server process" ], [ "4e", "DIAGNOSING THE PROBLEM" ], [ "4f", "The SystemOut may contain messages like: ###" ], [ "4g", "[9/30/15 9:09:07:765 EDT] 000000a6 HttpMethodDir I" ], [ "4h", "org.apache.commons.httpclient.HttpMethodDirector executeWithRetry I/O" ], [ "4i", "exception (java.net.SocketException) caught when processing request: Too" ], [ "4j", "many open files ###" ], [ "4k", "Check the ulimit settings for the user." ], [ "4l", "Execute the following on the command line: ulimit -a" ], [ "4m", "RESOLVING THE PROBLEM" ], [ "4n", "Websphere Support generally recommends a minimum value of 8000 for the open files ulimit setting." ], [ "4o", "To increase the value to 8000 execute:" ], [ "4p", "ulimit -n 8000" ], [ "4q", "That value can be used initially and increased if it determined to be too low." ], [ "4r", "The value is only good for the current log in session." ], [ "4s", "Once a working value is determined, the value must be set at the system level to make it permanent." ], [ "4t", "The following Websphere documentation provides more detail on setting the ulimit value: http://www-01.ibm.com/support/docview.wss?uid=swg21469413 [http://www-01.ibm.com/support/docview.wss?uid=swg21469413]" ] ]

[ "0l", "0m", "0n", "0o", "0p", "0q", "0r", "0s", "0t", "0u", "0w", "0x", "3l", "3m", "3n", "3o", "3p", "3q", "3s", "4d", "4k", "4n", "4o", "4p", "4q", "4r" ]

[ "IBM Sterling Connect:Express for z/OS version 4.3.0 supports TLS versions V1.1 and V1.2 TECHNOTE (FAQ)\n\nQUESTION\n Does IBM Sterling Connect:Express for z/OS version 4.3.0 support TLS versions V1.1 and V1.2? \n\nCAUSE\nIBM Sterling Connect Express with SSL code based on GSKSSL, implements only TLS versions V1, but not V1.1 or V1.2.\n\nThe GSKSSL environment is configured dynamically based on monitor SYSIN and based on SSLCFG SYSIN for each transfer (in or out).\n\nIBM Sterling Connect:Express for z/OS does not update the environment variables, but sets values through GSK API:\ngsk_attribute_set_enum(env_handle, GSK_PROTOCOL_TLSV1, \nGSK_PROTOCOL_TLSV1_ON);\n\ngsk_attribute_set_enum(soc_handle, GSK_PROTOCOL_TLSV1, \nGSK_PROTOCOL_TLSV1_ON);\n\nANSWER\nIBM Sterling Connect:Express for z/OS code will be modified to support TLS versions V1.1 and V1.2 and an Enhancement Request number 368318 was raised.\nThis implies adding config keywords in the monitor SYSIN and SSLCFG and take into account the new gskssl.h values below:\n\nGSK_PROTOCOL_TLSV1 = 407, \nGSK_PROTOCOL_TLSV1_1 = 412, \nGSK_PROTOCOL_TLSV1_2 = 421 \nGSK_PROTOCOL_TLSV1_ON = 518, /* GSK_PROTOCOL_TLSV1 */ \nGSK_PROTOCOL_TLSV1_OFF = 519, /* GSK_PROTOCOL_TLSV1 */ \nGSK_PROTOCOL_USED_TLSV1 = 520, /* GSK_PROTOCOL_USED */ \nGSK_PROTOCOL_TLSV1_1_ON = 530, /* GSK_PROTOCOL_TLSV1_1 */ \nGSK_PROTOCOL_TLSV1_1_OFF = 531, /* GSK_PROTOCOL_TLSV1_1 */ \nGSK_PROTOCOL_USED_TLSV1_1 = 532, /* GSK_PROTOCOL_USED */ \nGSK_PROTOCOL_TLSV1_2_ON = 558, /* GSK_PROTOCOL_TLSV1_2 */ \nGSK_PROTOCOL_TLSV1_2_OFF = 559, /* GSK_PROTOCOL_TLSV1_2 */ \nGSK_PROTOCOL_USED_TLSV1_2 = 560 /* GSK_PROTOCOL_USED */", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS NEW FUNCTION.\n \n \n \n\nERROR DESCRIPTION\n * C:D BUI is using an outdated Jetty server that uses only an SSL\n connection. Various Security Scanners detect cipher suite\n vulnerabilities when scanning port 8443.\n Replace the Jetty version with version 9.4.6 that does support\n TLS v1.2\n \n \n \n \n \n\nLOCAL FIX\n * No workaround available.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Jetty 6.1 currently included in CD BUI does not support TLS 1.2.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Need newer version of Jetty.\n \n \n \n \n \n\nTEMPORARY FIX\n * IT24543\n \n \n \n \n \n\nCOMMENTS\n * Updated CD/Browser iFix placed on EcuRep for customer to\n download and test.\n \n \n \n \n \n\nAPAR INFORMATION\n * APAR NUMBER\n IT24543\n \n \n * REPORTED COMPONENT NAME\n STR CD BROWSER\n \n \n * REPORTED COMPONENT ID\n 5725C9901\n \n \n * REPORTED RELEASE\n 150\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 2018-03-27\n \n \n * CLOSED DATE\n 2018-04-17\n \n \n * LAST MODIFIED DATE\n 2018-04-17\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 STR CD BROWSER\n \n \n * FIXED COMPONENT ID\n 5725C9901\n \n \n\nAPPLICABLE COMPONENT LEVELS", "StoredIQ TLS secure SSL TECHNOTE (FAQ)\n\nQUESTION\n Does StoredIQ support TLS v1.2? \n\nCAUSE\nTLS 1.0 is being phased out and moving to 1.2\n\nANSWER\nYes, StoredIQ 7.6.0.5 and above support TLS 1.2. TLS 1.2 is supported both on Application Stack and Dataserver", "z/os SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Connect Enterprise SSL gsk errors after applying latest\n maintenance\n \n CMB2181E - C:E TCP TCP/IP REQUEST TCPRECV FAILED WITH RC=0071,\n RS=011C.\n \n Also, client needs to know if she has AES based Ciphers in\n production?\n CMB349I - BASE150 P040115 FI49022\n \n 23.32.35 STC02972 CMB2200E - C:E TCP THRD=FTPC0001\n REQ=SSLSOINI RC=406 RS=GSK_ERR_IO\n 23.32.35 STC02972 CMB2173E - C:E TCP FTP CLIENT SESSION\n TERMINATED ON FTPC0001 DUE TO SCRIPT UserErr RC=0008.\n 23.32.35 STC02972 CMB2129I - C:E TCPS FTP CLIENT SESSION END\n ON THREAD=FTPC0001, RMT=FSSLBOA , CC=0934.\n \n Level 3 Support has determined:\n \n The 1503 that we are receiving is a GOODBYE alert and we are\n not handling it correctly. We only are checking for 150300\n (SSL v3) or 150301 (TLS v1.0) but in Sally's case they are\n sending us a 150303 (which is TLS v1.2).\n \n \n \n \n \n\nLOCAL FIX\n * N/A\n \n \n \n \n \n\nPROBLEM SUMMARY\n * TLS READ/WRITE errors after connection was disconnected.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Buffer contained 1503xx alert that was not being properly\n checked for TLS v1.1 and v1.2.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI72438\n \n \n * REPORTED COMPONENT NAME\n STR CON ENT Z/O\n \n \n * REPORTED COMPONENT ID\n 5655X0500\n \n \n * REPORTED RELEASE\n 150\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 2016-11-16\n \n \n * CLOSED DATE\n 2017-01-04\n \n \n * LAST MODIFIED DATE\n 2017-01-04\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 STR CON ENT Z/O\n \n \n * FIXED COMPONENT ID\n 5655X0500\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R150 PSY\n UP", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n If you are using a version of IBM Business Process Manager (BPM) earlier than V8.5.6.0, you will need to update and reconfigure your IBM BPM factory settings to allow communication using the TLS V1.2 protocol. \n\nCAUSE\nThe factory configuration settings in versions of IBM BPM prior to V8.5.6.0 only allow TLS V1.0 and V1.1. Products that require TLS V1.2 cannot communicate with IBM BPM V8.5.6.0 by default.\nNote: The earlier versions of TLS (V1.0 and V1.1) currently work when using IBM Blueworks Live, however, effective 07/01/2017, TLS V1.2 will be required.\n\n\nRESOLVING THE PROBLEM\nTo update the default configurations to support TLS V1.2, run the attached setSSLProtocol.py script as follows: \n\n\n1. Stop the servers of your BPM environment.\n\n2. Run the script using this command:\nOn Windows\nwsadmin -conntype none -profileName <profileName> -f sslProtocol.py \nOn UNIX/Linux\nwsadmin.sh -conntype none -profileName <profileName> -f sslProtocol.py \nwhere <profileName> is either the stand-alone profile for BPM Express, or the deployment manager profile for BPM Standard and BPM Advanced.\n\n3. Restart the servers of your BPM environment\n\nsetSSLProtocol.py [/support/docview.wss?uid=swg21997889&aid=2]setSSLProtocol.py [/support/docview.wss?uid=swg21997889&aid=1]\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Security AIX, Linux, Solaris, Windows 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 Security Linux, Windows 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 BWL\nBPM" ]

[ [ "2a", "StoredIQ TLS secure SSL TECHNOTE (FAQ) QUESTION" ], [ "2b", " Does StoredIQ support TLS v1.2? CAUSE" ], [ "2c", "TLS 1.0 is being phased out and moving to 1.2 ANSWER" ], [ "2d", "Yes, StoredIQ 7.6.0.5 and above support TLS 1.2." ], [ "2e", "TLS 1.2 is supported both on Application Stack and Dataserver" ] ]

[ "2d", "2e" ]

[ " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n We'd like to uninstall Guardium S-TAP which was installed via GIM, but there is an issue with our network and therefore we can't do it via GIM. In this situation, how do we uninstall Guardium S-TAP directly on the DB server? \n\nSYMPTOM\nThere is a problem between the S-TAP on DB server and the Guardium appliance, such that we can't un-install the S-TAP from the Guardium GUI console using GIM.\n\n\nRESOLVING THE PROBLEM\nThe following is based on an AIX Server - used as an example . \n\nPlease attempt the following steps to clean up Guardium modules from the DB server. \n\n\n1. Attempt an un-install of S-TAP via GIM. See the following manual page for details. \n\n\n * \n * <your_guardium>\n * \n * \n * \n * \n\n\n\n2 Uninstall GIM client \n\n * \n * root\n * \n * \n * \n * <installation_directory> /modules/GIM/current/uninstall.pl \n \n * \n * \n * \n * <your_guardium>\n * \n * \n \n \n [ NOTE] <installation_directory> is something like this: * /usr/local/guardium/\n \n \n\n\n\n3 (Optional) This is a workaround to be taken only if the S-TAP uninstaller in step 1 didn't work. \n * \n * \n * <installation_directory> /modules/KTAP/current/guard_ktap_loader stop \n \n \n * \n * \n * \n * \n * \n * \n * \n * \n * /etc/drivers/guard_ktap_loader start \n \n \n * \n * \n * <some_number>\n * \n * \n * \n * <installation_directory>\n * \n * \n * \n * \n * \n\n\n4. Reboot the system - This action will unload K-TAP completely and reload /etc/inittab \n * \n * \n * genkex | grep tap \n \n \n * \n * install_assist\n * \n\n\n\n\n5. Reset Client from Guardium GUI \n * \n * \n * \n * \n * \n * Reset Client\n * \n * \n\n\nRELATED INFORMATION\n Installing Guardium Installation Manager - GIM [http://www.ibm.com/support/docview.wss?uid=swg21514571 ]\nInstalling STAP with IBM InfoSphere GIM [http://www.ibm.com/support/docview.wss?uid=swg21569157 ]\nUninstall the Guardium GIM agent and all modules [http://www.ibm.com/support/docview.wss?uid=swg21512709 ]", " 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]", "Guardium GIM STAP install use TECHNOTE (FAQ)\n\nQUESTION\n How to use IBM InfoSphere Guardium Installation Manager (GIM) \n\nANSWER\nIBM InfoSphere Guardium Installation Manager (GIM) simplifies the task of managing the IBM InfoSphere Guardium remote modules such as S-TAP, K-TAP and CAS. \n\nGIM is particularly useful when there are several STAP clients and manually installing or upgrading each and every one of them can be cumbersome and error prone. GIM provides the ability to upload the STAP clients centrally and distributing them to the STAP hosts.\n\nGIM is comprised of two parts - GIM Server and GIM Client. The server component is installed as part of an IBM InfoSphere Guardium appliance or Central Management installation and performs such duties as registering GIM clients, providing a list of available updates that are ready for download and installed on client servers, transferring software updates to the client server, and updating the installation status of clients. \n\nThe GIM client application must be installed manually for the first time on all the database server machines. It performs duties such as registering to the GIM server, initiate a request to check for software updates, installing the new software, updating module parameters, and uninstalling modules. \n\nGIM's UI can be accessed from the GUI of the appliance and provides the user the ability to install, uninstall, upgrade IBM InfoSphere Guardium bundles and modules as well as provide feedback about database servers, installed modules, and statuses. Equivalent CLI commands also exist.\n\n\n\nGIM Activity Reference URL How to install GIM http://www.ibm.com/support/docview.wss?uid=swg21514571 [http://www.ibm.com/support/docview.wss?uid=swg21514571] How to install STAP using GIM http://www.ibm.com/support/docview.wss?uid=swg21569157 [http://www.ibm.com/support/docview.wss?uid=swg21569157]", "Security Guardium S-TAP for Db2 on z/OS V9.1 PTF UI48571 changed S-TAP filtering behavior TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n PTF UI48571 no longer filters the CREATE, ALTER, DROP, GRANT and REVOKE SQL Statements. \n\nSYMPTOM\nPTF UI48571 no longer filters the CREATE, ALTER, DROP, GRANT and REVOKE SQL Statements at the S-TAP level.\n\n\nAll CREATE, ALTER, DROP, GRANT, and REVOKE statements are streamed to Guardium collector.\nAs a result, CREATE, ALTER, DROP, and GRANT and REVOKE SQL Statements events can be shown in Guardium reports regardless of the installed S-TAP policy for the audited Db2 Subsystem.\n\n\n\nCAUSE\nWorking as designed.\n\n\n\nENVIRONMENT\nV9.1\n\n\n\n\nRESOLVING THE PROBLEM\nFollow these steps to filter CREATE, ALTER, DROP, and GRANT and REVOKE SQL Statements events at the Guardium appliance level:\n\n1. In the installed policy, update the Command field to include/exclude the following event types: \n\n· Failed Authorizations \n\n· Failed Authid changes \n\n· DB2 commands \n\n· Grants and Revokes \n\n· DB2 Utilities \n\n· Set Current SQLID \n\n2. On the Guardium appliance, create, update, then install a policy rule with an action of SKIP LOGGING to discard events that are received from the S-TAP Collector Agent.\n\n3. Update the Guardium appliance report to include/exclude the following types for specific objects/users/etc.: \n\n· Failed Authorizations \n\n· Failed Authid changes \n\n· DB2 commands \n\n· Grants and Revokes \n\n· DB2 Utilities \n\n· Set Current SQLID\n\nRELATED INFORMATION\n PI81339: COMPATIBILITY APAR FOR STAP 10.1.3 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI81339]\n\n\n\n\nPRODUCT ALIAS/SYNONYM\n S-TAP For DB2", "p4009; timestamp; z/OS S-TAP TECHNOTE (FAQ)\n\nQUESTION\n Why the DB time stamp from z/OS DB server has changed after applying patch V10p4009 on IBM Security Guardium ? \n\nCAUSE\nStarting V10p4009, Guardium and z/OS S-TAP converts the timestamp data from the local time zone of DB servers to the local time zone of collector, aggregator.\n\nANSWER\nIt's important for the collector and db server to operate (or at least mimic operating) in the same timezone to ensure that operations work as expected on the appliance, including, for example, export operations from the collectors to the aggregators, which relies on session timestamp information to determine which Guardium audit data to export to the aggregator. If the timezones are different, you run the risk of actually missing audit data in the aggregated reporting especially if the two time zones span the midnight boundary. There are many other Guardium operations that rely on timestamp data as well. \n\nFor this reason, V10 DB2 S_TAP and snif patch v10p4009 added code to convert the z STAP information to the collector timezone before logging it. (Previously, the S-TAP only sent a timezone string of the database local time.) For most organizations, this is not an issue as it is best practice to have collector and database server in the same timezone. For those who have their z/OS STAPs in a different timezone (or set those servers to GMT for example so it acts as if it's in a different timezone), you may see a timestamp change from what you had before. \n\nAfter many years of having the z/OS STAP traffic be treated differently to other platforms. Patch V10p4009 was finally issued to bring the z/OS STAP platforms in line with how traffic is processed from other platforms such as Linux, Unix and Windows." ]

[ [ "1a", " TECHNOTE (FAQ) QUESTION" ], [ "1b", " What can cause an STAP to fail to connect properly - I get the following messages in the logs:-" ], [ "1c", "/tmp/guard_stap.stderr.txt on the DB Server :-" ], [ "1d", "\"Server <ip_addr> wasn't heard from for nn sec during this attempt (nnn sec total), closing and re-opening\"" ], [ "1e", "and from the Guardium Appliance - via fileserver in the /log/opt-ibm-guardium-log/snif/snif.log" ], [ "1f", "\"Unauthorized client connecting from <ip_addr> ,rejecting\" CAUSE" ], [ "1g", "One reason for these errors could be that the S-TAP Approval Needed is checked in the S-TAP Certification screen on the Appliance like this :- [/support/docview.wss?uid=swg22009818&aid=1] [/support/docview.wss?uid=swg22009818&aid=1] ANSWER" ], [ "1h", "Uncheck the Approval box and the S-TAPs should start connecting . [/support/docview.wss?uid=swg22009818&aid=2] [/support/docview.wss?uid=swg22009818&aid=2]" ] ]

[ "1b", "1d", "1e", "1f", "1g", "1h" ]

[ "z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * After migration to ENFM, query 3 and/or query17 in DSNTESQ\n returns some rows for tablespaces that should have been dropped\n during the ENFM processing. During the processing of the\n tablespaces links are being replaced by the RIs. For some\n tables the RIs are not successfully created which causes the\n incosistency during the drop of redundant tablespaces.\n \n \n \n \n \n\nLOCAL FIX\n * n/a\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All customers who are migrating to DB2 10 *\n * for z/OS or DB2 11 for z/OS are affected by *\n * this change. *\n ****************************************************************\n * PROBLEM DESCRIPTION: After migrating to DB2 10 for z/OS *\n * sample job DSNTESQ queries QUERY3 *\n * and/or QUERY17 return rows. *\n ****************************************************************\n * RECOMMENDATION: Apply corrective PTF when available. *\n ****************************************************************\n During the V8 migration process several catalog tables are\n dropped. One of these tables was SYSIBM.SYSLINKS. When the\n SYSLINKS table is dropped we also eliminate the link information\n from the SYSIBM.SYSRELS catalog table. The link rows eliminated\n have a RELOBID1 = 0 and a pound sign ('#') in the RELNAME\n column.\n \n If there is a failure during the V8 ENFM process that drops and\n deletes this link information it will not be attempted again.\n Having this link information in the DB2 catalog will not impact\n anything in V8 or V9. However, if this link information is still\n in the SYSRELS catalog table during the V10 ENFM process then it\n will most likely cause problems.\n \n If the SYSRELS catalog table contains link information in it\n during V10 ENFM processing then the ENFM process may have\n problems creating referential integrity between various catalog\n tables. If there is missing referential integrity between\n catalog tables then this can lead to orphan rows in the catalog\n that might impact future SQL.\n \n In one of the reported cases, DB2 was not able to create\n referential integrity between the SYSTABLESPACE and\n SYSTABLEPART catalog tables. Then when a table space was dropped\n the SYSTABLESPACE row was dropped but the SYSTABLEPART rows\n remained. This made them orphans.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The following premigration jobs in the noted releases have been\n updated with new queries that look for link rows in the SYSRELS\n catalog table that should have been eliminated:\n \n DB2 9 for Z/OS:\n \n DSNTIJPA (premigration checkout for DB2 10) - new query 39\n \n DB2 10 for Z/OS:\n \n DSNTIJPB (premigration checkout for DB2 11) - new query 27\n DSNTIJPM (premigration checkout for DB2 10) - new query 39\n \n DB2 11 for Z/OS:\n \n DSNTIJPM (premigration checkout for DB2 11) - new query 27\n \n In the reported problem cases the remaining link information\n in SYSRELS was different and the missing referential integrity\n between catalog tables was also different. Because of this,\n customers should contact IBM service if any of these queries\n return rows.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI13252\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 A10\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-03-07\n \n \n * CLOSED DATE\n 2014-06-05\n \n \n * LAST MODIFIED DATE\n 2014-07-01\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 UI18611 UI18612 UI18613\n \n \n\nMODULES/MACROS\n * DSNTIJPA DSNTIJPB DSNTIJPM\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 * RA10 PSY UI18611 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI18611]\n UP14/06/21 P F406\n \n \n * RB10 PSY UI18612 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI18612]\n UP14/06/21 P F406\n \n \n * R910 PSY UI18613 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI18613]\n UP14/06/21 P F406\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.", "netezza pda dashdb latin9 migrate Column expansion table TECHNOTE (FAQ)\n\nQUESTION\n How to migrate a table from PureData for Analytics to dashDB with latin9 conversion and column expansion into suitable tablespace? \n\nANSWER\nIf you are going to create an empty table using db_migrate script there are two aspects which need to be considered.\n1. Column expansion\n2. Tablespace\n\ndb_migrate with latin9 conversion fix installed will create a table in dashDB in the way that all the char or varchar type columns will be created with CODEUNITS32 keyword instead of OCTETS.\n\nCODEUNITS32 indicates that the units for the length attribute are Unicode UTF-32 code units which approximate counting in characters. \nhttps://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.sql.ref.doc/doc/r0008470.html?pos=2 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.sql.ref.doc/doc/r0008470.html?pos=2]\n\nFor example: \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * 100 CODEUNITS32\n * \n * \n * \n * 50 CODEUNITS32\n * \n * \n * \n * 10 CODEUNITS32\n * \n * \n * \n * \n * \n\n\nThe same table would be defined in the following way, without latin9 conversion fix. * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * 100 OCTETS\n * \n * \n * \n * 50 OCTETS\n * \n * \n * \n * 10 OCTETS\n * \n * \n * \n * \n * \n\n\n\nAnother aspect is the tablespace within which a table is being created. db_migrate does not support destination tablespace selection option. \nWe workaround it in the following way: \n\n * \n * \n * \n * \n * \n * \n * $ db2look -d BLUDB -a -e -x -o BLUDB_schema.sql\n * \n * \n * \n * $ db2look -d BLUDB -t tablename -a -e -x -o tablename.sql\n\n\n\n- The script is manually edited - only ODS tables are left. All the tables are assigned to the appropriate tablespace. \nIn the example below USERSPACE1 is replaced by TABLESPACE_1. \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * USERSPACE1\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * TABLESPACE_1\n * \n * \n * \n\n\n\n- Empty ODS table or tables are dropped from BLUDB. \n- Edited schema script is executed and it creates tables within suitable tablespace. \n\nThe assumption is that tablespaces are already defined within BLUDB database. Below is the excerpt from the script which was used to create custom tablespaces. \n\nCONNECT TO BLUDB; \nCREATE LARGE TABLESPACE TableSpace_1 IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 32768 MANAGED BY AUTOMATIC STORAGE USING STOGROUP \"IBMSTOGROUP\" EXTENTSIZE 4 PREFETCHSIZE AUTOMATIC BUFFERPOOL \"IBMDEFAULTBP\" OVERHEAD INHERIT AUTORESIZE YES MAXSIZE NONE TRANSFERRATE INHERIT DATA TAG INHERIT; \nCREATE LARGE TABLESPACE TableSpace_2 IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 32768 MANAGED BY AUTOMATIC STORAGE USING STOGROUP \"IBMSTOGROUP\" EXTENTSIZE 4 PREFETCHSIZE AUTOMATIC BUFFERPOOL \"IBMDEFAULTBP\" OVERHEAD INHERIT AUTORESIZE YES MAXSIZE NONE TRANSFERRATE INHERIT DATA TAG INHERIT;", "AIX SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS FIXED IF NEXT.\n \n \n \n\nERROR DESCRIPTION\n * The reporting of deduplication ratios via the Tivoli Storage\n Manager server command QUERY STGPOOL F=D output and occupancy\n table might be inaccurate. The reason being is that deduplicated\n chunks of data which are used as base data for same data\n matches, might not be included in the calculations. Since these\n data chunks are truly occupying storage space they should cost\n against the deduplication ratio value and in some cases, they\n are not.\n \n The result is that the deduplication ratio might be slightly\n higher than reality.\n \n Customer/L2 Diagnostics :\n The best way to show an example is by using an the output from\n the \"tsm_dedup_stats.pl\" script. This is attached in the\n tech note 1596944:\n \n Determining the impact of deduplication on a\n Tivoli Storage Manager server database and storage pools\n http://www-01.ibm.com/support/docview.wss?uid=swg21596944 [http://www-01.ibm.com/support/docview.wss?uid=swg21596944]\n \n This can be used to get deduplication information and stats for\n a given environment. Here is an example from the script output\n that shows the stgpool utilization information:\n \n Pool: DEDUP-POOL\n Type: PRIMARY Est. Cap. (MB): 11372626.3 Pct Util: 64.7\n Reclaim Thresh: 100 Reclaim Procs: 1 Next Pool:\n Identify Procs: 2 Dedup Saved:9273226\n \n \n Logical stored (MB): 5285872.39\n Dedup Not Stored (MB): 9273226.86\n Total Managed (MB): 14559099.25\n \n Volume count: 228\n AVG volume size: 49879\n Number of chunks: 52501740\n Avg chunk size: 342824\n \n The storage utilization of the storage pool does not match with\n the logical value (+ reclaim pct) of the storage pool.\n \n 11372626 * 64% = 7.3 TB\n \n The percent reclaim for this environment was 412 GB\n \n The following server select command shows:\n \n select sum(est_capacity_mb*pct_reclaim/100) as\n \"Reclaimable (MB)\" from volumes where stgpool_name='DEDUP-POOL'\n \n Reclaimable (MB) = 412GB\n \n \n Logical Stored + Reclaimable = 5.7 TB\n \n At this point, there is 7.3 TB of used space in the storage\n pool but we are only accounting for 5.7 TB. A good portion of\n the rest of that space is deleted base chunks which are no\n longer assigned to client files (they have been expired).\n \n Tivoli Storage Manager Versions Affected:\n Tivoli Storage Manager Server version 6.1, 6.2 and 6.3 on all\n platforms\n \n Initial Impact:\n low\n \n Additional Keywords:\n TSM zz61 zz62 zz63 dedup\n \n \n \n \n \n\nLOCAL FIX\n * Run the following DB2 command to get the \"real\" values:\n \n db2 \"select cast( sum(bfaa.lsize)/(1024*1024*1024) as\n decimal(10,2) ) as LOGICAL_OCC_GB,\n cast( sum(bfaa.rsize)/(1024*1024*1024) as decimal(10,2) ) as\n MANAGED_OCC_GB from bf_aggregate_attributes bfaa left join\n af_bitfiles afbf on (afbf.srvid=bfaa.srvid and\n afbf.bfid=bfaa.superbfid) where bfaa.srvid=0 and\n afbf.poolid=<poolid>\"\n \n The storage pool id <poolid> can be captured via the server\n SHOW command: show sspool\n The number in brackets after the storage pool name is the\n poolid\n \n The above will give the true logical and reporting\n (before dedup). The LOGICAL value here can be added to any\n reclaimable space and it should get us close to the storage\n pool utilization.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All Tivoli Storage Manager server users. *\n ****************************************************************\n * PROBLEM DESCRIPTION: See error description. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n This problem is projected to be fixed in a future version of\n the\n Tivoli Storage Manager server. Note that this is subject to\n change at the discretion of IBM.\n \n \n Affected platforms: AIX, HP-UX, Solaris, Linux, and Windows.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IC90010\n \n \n * REPORTED COMPONENT NAME\n TSM SERVER\n \n \n * REPORTED COMPONENT ID\n 5698ISMSV\n \n \n * REPORTED RELEASE\n 63L\n \n \n * STATUS\n CLOSED FIN\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 2013-02-05\n \n \n * CLOSED DATE\n 2013-02-22\n \n \n * LAST MODIFIED DATE\n 2013-02-22\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\nAPPLICABLE COMPONENT LEVELS\n * R61A PSY\n UP\n \n \n * R61H PSY\n UP\n \n \n * R61L PSY\n UP\n \n \n * R61S PSY\n UP\n \n \n * R61W PSY\n UP\n \n \n * R62A PSY\n UP\n \n \n * R62H PSY\n UP\n \n \n * R62L PSY\n UP\n \n \n * R62S PSY\n UP\n \n \n * R62W PSY\n UP\n \n \n * R63A PSY\n UP\n \n \n * R63H PSY\n UP\n \n \n * R63L PSY\n UP\n \n \n * R63S PSY\n UP\n \n \n * R63W PSY\n UP", "SQL1763N; Alter Tablespace; reclaimable storage; DMS; Automatic storage table spaces; MON_GET_TABLESPACE; RECLAIMABLE_SPACE_ENABLED; SMS; DB2 Version 9.7; lower high water mark TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Receiving SQL1763N error with Reason Code 11 while running \"Alter Tablespace\" command to reclaim unused storage space against DMS or automatic storage tablespaces. \n\nSYMPTOM\nFollowing reasons apply: \n\n * If the DMS or automatic storage tablespaces are not created in DB2 Version 9.7 or later, as the \"Reclaimable Storage\" is not available in tablespaces created in earlier versions(V9.1/V9.5) of the DB2 product. \n * Trying to alter a SMS tablespace as this feature is not supported on SMS tablespaces. \n\n\nExample testcase on a TEMPSPACE1 SMS tablespace. \n\n * \n * \n * DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL1763N Invalid ALTER TABLESPACE statement for table space \"TEMPSPACE1\" due to reason \"11\" SQLSTATE=429BC \n * \n \n\n\nDIAGNOSING THE PROBLEM\nMON_GET_TABLESPACE table function and RECLAIMABLE_SPACE_ENABLED monitor element can be used to identify whether the tablespace is enabled for reclaimable storage or not. Example: \ndb2 \"SELECT varchar(tbsp_name, 30) as tbsp_name, tbsp_type, RECLAIMABLE_SPACE_ENABLED FROM TABLE(MON_GET_TABLESPACE('',-2))\" \n\n \n\nSnippet of the output: \n\n \n\nTBSP_NAME TBSP_TYPE RECLAIMABLE_SPACE_ENABLED\n----------------- ----------- -------------------------\nSYSCATSPACE DMS 1\nTEMPSPACE1 SMS 0\nUSERSPACE1 DMS 1 \n\nIf the RECLAIMABLE_SPACE_ENABLED monitor element returns a value of 1, then the tablespace is enabled for reclaimable storage. Otherwise, it returns a value of 0.\n\n\n\nRESOLVING THE PROBLEM\nTo use the reclaimable storage feature, make sure to create the DMS or automatic storage tablespaces in DB2 Version 9.7 or later. Example testcase on SYSCATSPACE DMS tablespace which has reclaimable storage enabled. \n\n \n\n * \n * \n * \n * \n * \n\n\nNote: \nTablespaces migrated from DB2 V9.1/V9.5 to V9.7 won't get upgraded directly to use the reclaimable storage feature. RELATED INFORMATION\n Reclaimable storage [http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.dbobj.doc/doc/c0055392.html]", "z/os A FIX IS AVAILABLE\nDB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24044110]\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 * Runstats command with the 'tablesample' clause may fail\n with error SQL2310N on a range partitioned table.\n \n The problem occurs if the partitions of the table are in\n different tablespaces; specifically, if at least one partition\n is in a reclaimable storage tablespace and at least one\n is in a non-reclaimable storage tablespace.\n \n The runstats command will return the following error:\n \n SQL2310N The utility could not generate statistics. Error\n \"-1655\" was returned.\n \n You may observe an error similar to the following in the\n db2diag.log:\n \n 014-07-12-13.00.14.536372-240 I14654250E5351 LEVEL:\n Severe\n PID : 30761 TID : 47011709577536 PROC :\n db2sysc 0\n INSTANCE: instance NODE : 000 DB : DB1\n APPHDL : 0-5034 APPID:\n 11.111.111.111.11111.140712145209\n AUTHID : AUTHID HOSTNAME: hostname\n EDUID : 148 EDUNAME: db2agent (db1) 0\n FUNCTION: DB2 UDB, buffer pool services, sqlb_verify_page,\n probe:3\n MESSAGE : ZRC=0x86020001=-2046689279=SQLB_BADP \"page is bad\"\n DIA8400C A bad page was encountered.\n DATA #1 : String, 64 bytes\n Error encountered trying to read a page - information follows :\n DATA #2 : String, 23 bytes\n Page verification error\n DATA #3 : Page ID, PD_TYPE_SQLB_PAGE_ID, 4 bytes\n 17\n DATA #4 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 96 bytes\n Obj: {pool:10;obj:206;type:0} Parent={10;206}\n \n \n \n \n \n\nLOCAL FIX\n * Avoid using the 'tablesample' clause in the runstats command.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n * DB2 LUW *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * See Error Description *\n ****************************************************************\n * RECOMMENDATION: *\n * Local Fix: Avoid using the 'tablesample' clause in the *\n * runstats command. *\n ****************************************************************\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Upgrade to v10.5 FP7\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT03627\n \n \n * REPORTED COMPONENT NAME\n DB2 FOR LUW\n \n \n * REPORTED COMPONENT ID\n DB2FORLUW\n \n \n * REPORTED RELEASE\n A50\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 2014-08-06\n \n \n * CLOSED DATE\n 2015-03-13\n \n \n * LAST MODIFIED DATE\n 2016-04-29\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n IT03372 [http://www-01.ibm.com/support/docview.wss?uid=swg1IT03372]\n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n DB2 FOR LUW\n \n \n * FIXED COMPONENT ID\n DB2FORLUW\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * RA10 PSY\n UP\n \n \n * RA50 PSY\n UP" ]

[ [ "3a", "SQL1763N; Alter Tablespace; reclaimable storage; DMS; Automatic storage table spaces; MON_GET_TABLESPACE; RECLAIMABLE_SPACE_ENABLED; SMS; DB2 Version 9.7; lower high water mark TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "3b", " Receiving SQL1763N error with Reason Code 11 while running \"Alter Tablespace\" command to reclaim unused storage space against DMS or automatic storage tablespaces. SYMPTOM" ], [ "3c", "Following reasons apply:" ], [ "3d", " * 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." ], [ "3e", " * Trying to alter a SMS tablespace as this feature is not supported on SMS tablespaces." ], [ "3f", "Example testcase on a TEMPSPACE1 SMS tablespace. * *" ], [ "3g", " * DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command." ], [ "3h", "During SQL processing it returned: SQL1763N Invalid ALTER TABLESPACE statement for table space \"TEMPSPACE1\" due to reason \"11\" SQLSTATE=429BC *" ], [ "3i", "DIAGNOSING THE PROBLEM" ], [ "3j", "MON_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:" ], [ "3k", "db2 \"SELECT varchar(tbsp_name, 30) as tbsp_name, tbsp_type, RECLAIMABLE_SPACE_ENABLED FROM TABLE(MON_GET_TABLESPACE('',-2))\"" ], [ "3l", "Snippet of the output:" ], [ "3m", "TBSP_NAME TBSP_TYPE RECLAIMABLE_SPACE_ENABLED" ], [ "3n", "----------------- ----------- -------------------------" ], [ "3o", "SYSCATSPACE DMS 1" ], [ "3p", "TEMPSPACE1 SMS 0" ], [ "3q", "USERSPACE1 DMS 1" ], [ "3r", "If the RECLAIMABLE_SPACE_ENABLED monitor element returns a value of 1, then the tablespace is enabled for reclaimable storage." ], [ "3s", "Otherwise, it returns a value of 0." ], [ "3t", "RESOLVING THE PROBLEM" ], [ "3u", "To use the reclaimable storage feature, make sure to create the DMS or automatic storage tablespaces in DB2 Version 9.7 or later." ], [ "3v", "Example testcase on SYSCATSPACE DMS tablespace which has reclaimable storage enabled. * * * * * Note:" ], [ "3w", "Tablespaces migrated from DB2 V9.1/V9.5 to V9.7 won't get upgraded directly to use the reclaimable storage feature. RELATED INFORMATION" ], [ "3x", " Reclaimable storage [http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.dbobj.doc/doc/c0055392.html]" ] ]

[ "3a", "3b", "3c", "3d", "3e", "3j", "3r", "3t", "3u" ]

[ "fix pack; Cast Iron fix pack; 7.0.0.1; Cast Iron Cloud Integration DOWNLOADABLE FILES\n\nABSTRACT\n Fix Central download links for WebSphere Cast Iron Cloud integration 7.0.0.1 \n\nDOWNLOAD DESCRIPTION\n\n\nTAB NAVIGATION\n * Overview [http://www.ibm.com/support/docview.wss?uid=swg21678176]- selected tab,\n * Included Fixes [http://www.ibm.com/support/docview.wss?uid=swg27042466]\n * Known Issues [http://www.ibm.com/support/docview.wss?uid=swg27042468]\n * Download Links [http://www.ibm.com/support/docview.wss?uid=swg24037918]\n\n\n\n[<a href=]\" >What is Fix Central (FC)? Image Name Date Published Language Size (MB) FixCentral Link WebSphere DataPower Cast Iron Appliance XH40 Edition 7.0.0.1 **Upgrade Only** Firmware Image 30th June, 2014 US English 616 MB FC [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Cast+Iron+Cloud+integration&release=7.0.0.1&platform=All&function=fixId&fixids=7.0.0.1-WS-WCI-20140628-1200_H11_64.scrypt2&includeRequisites=1&includeSupersedes=0&downloadMethod=http&source=fc] WebSphere Cast Iron Hypervisor Edition 7.0.0.1 **Upgrade Only** Firmware Image 30th June, 2014 US English 540 MB FC [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Cast+Iron+Cloud+integration&release=7.0.0.0&platform=All&function=fixId&fixids=7.0.0.1-WS-WCI-20140628-1200_H11_64.vcrypt2&includeRequisites=1&includeSupersedes=0&downloadMethod=http&source=fc] WebSphere Cast Iron Hypervisor Edition 7.0.0.1 Virtual Appliance Image - VMWare (.ova) 30th June, 2014 US English 1 GB FC [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Cast+Iron+Cloud+integration&release=7.0.0.1&platform=All&function=fixId&fixids=7.0.0.1-WS-WCI-20140628-1200_H11_64.ova&includeRequisites=1&includeSupersedes=0&downloadMethod=http&source=fc] WebSphere Cast Iron Hypervisor Edition 7.0.0.1 Virtual Appliance Image - Xen (.tar) 30th June, 2014 US English 1,012 MB FC [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Cast+Iron+Cloud+integration&release=7.0.0.1&platform=All&function=fixId&fixids=7.0.0.1-WS-WCI-20140628-1200_H11_64-xen&includeRequisites=1&includeSupersedes=0&downloadMethod=http&source=fc] WebSphere Cast Iron Secure Connector 7.0.0.1 installation images 30th June, 2014 US English FC [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Cast+Iron+Cloud+integration&release=7.0.0.1&platform=All&function=fixId&fixids=7.0.0.1-WS-WCI-20140628-1200_H11_64.32bit.sc-linux,7.0.0.1-WS-WCI-20140628-1200_H11_64.32bit.sc-win,7.0.0.1-WS-WCI-20140628-1200_H11_64.sc-linux,7.0.0.1-WS-WCI-20140628-1200_H11_64.sc-win&includeSupersedes=0&downloadMethod=http&source=fc] WebSphere Cast Iron Studio 7.0.0.2 All installation images 30th June, 2014 US English \nChinese Simplified \nChinese Traditional \nFrench \nGerman \nItalian \nJapanese \nKorean \nPortuguese Brazilian \nSpanish FC [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Cast+Iron+Cloud+integration&release=7.0.0.1&platform=All&function=fixId&fixids=7.0.0.1-WS-WCI-20140628-1200_H12_64.32bit.studio,7.0.0.1-WS-WCI-20140628-1200_H12_64.studio&includeSupersedes=0&downloadMethod=http&source=fc] \n\nPRODUCT ALIAS/SYNONYM\n Cast Iron\nCI", " SECURITY BULLETIN\n\nSUMMARY\n An authenticated user with authority to send a specially crafted message could cause a SDR or CLUSSDR channel to remain in a running state but not process messages. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-1285 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1285]\nDESCRIPTION: IBM MQ could allow an authenticated user with authority to send a specially crafted message that would cause a channel to remain in a running state but not process messages.\nCVSS Base Score: 3.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/125146 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125146] 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 \n\n * IBM MQ 8.0.0.0 - 8.0.0.6 maintenance levels\n\nIBM MQ V9 * IBM MQ 9.0.0.0 - 9.0.0.1 maintenance levels\n\nIBM MQ Appliance V8 * IBM MQ Appliance 8.0.0.0 - 8.0.0.6 maintenance levels\n\n\nIBM MQ V9 CD * IBM MQ V9.0.1 - V9.0.2\n\nIBM MQ Appliance V9 CD * IBM MQ Appliance V9.0.1 and V9.0.2\n\nREMEDIATION/FIXES\nIBM MQ V8 Apply Fix Pack 8.0.0.7 [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=swg24042009]\nIBM MQ Appliance V8\nApply Fix Pack 8.0.0.7 for MQ Appliance [https://www-01.ibm.com/support/docview.wss?uid=swg22005832] \n\nIBM MQ V9 CD \n\nUpgrade to 9.0.3 [http://www-01.ibm.com/support/docview.wss?uid=swg24043697]\nIBM MQ Appliance V9 CD\nUpgrade to 9.0.3 [http://www-01.ibm.com/support/docview.wss?uid=swg24043697].\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 16 October 2017: Added v8 and v9 LTS fix details\n29 June 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.", "shift; phase; date; GMT TECHNOTE (FAQ)\n\nQUESTION\n What is the effect of Leap Second time addition on Web GUI? \n\nCAUSE\nOccasionally, a leap second is added to Coordinated Universal Time (UTC) in order to synchronize atomic clocks with astronomical time to within 0.9 seconds.\n\nANSWER\nThere is no impact of this time addition to Web GUI.\n\n \n\nPRODUCT ALIAS/SYNONYM\n OMNIbus", " 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", " TECHNOTE (FAQ)\n\nQUESTION\n How does the IBM DataPower Gateway process NTP leap second events? \n\nCAUSE\nThe International Earth Rotation and Reference Systems Service (IERS) periodically declares the need for a leap second. The NTP server operator then decides whether to insert or propagate the leap second or simply absorb the leap second as a change in the reference time.\nThis document is not intended to describe a leap second itself; rather it is to describe how the DataPower Gateway processes a leap second. If you need additional information on leap seconds, there are Internet resources.\n\n\nANSWER\nThe DataPower Simple Network Time Protocol (SNTP) configuration includes a \"refresh interval\" that has a default value of 900 seconds. With each refresh interval timer event, the NTP client processes a single transaction with the NTP server. \n\n\nWhen a leap second occurs, the NTP server or servers used by the DataPower Gateway might insert the leap second indicator into the NTP protocol header. This insertion is designed to stage the leap second event ahead of time. When the NTP server sets this signal in the NTP response, NTP clients can choose to add or remove 1 second at the midnight crossing on June 30 or December 31. The NTP server administrator can decide to enable this property weeks or days before the event. The DataPower Gateway SNTP implementation ignores the leap second indicator and continues normal operation.\n\nAfter the leap second event occurs, the DataPower Gateway SNTP implementation refreshes the current time reference from the NTP server and make corrections as needed. If the NTP server has corrected its own time, then the reference time passed to the DataPower Gateway includes all or a portion of the correction. If the correction on the NTP server is incomplete at the time of first request from DataPower Gateway following the event, then the full correction does not take place on the DataPower Gateway until the correction has fully completed on the NTP server. \n\nThe DataPower Gateway absorbs leap seconds as they are absorbed by the NTP server or servers and communicated as the reference time in responses sent to the DataPower Gateway. \n\nThe DataPower Gateway logs the time change at the \"info\" log level as in the following example log message:\n\n7:59:07 PM system information 207 0x80e0031f ntp-service (NTP Service): NTP time adjustment of 1000097 microseconds \n\nThis message reflects the 1 second change that is introduced by the leap second on an NTP server that used a step correction to implement leap second.\n\nNote: The DataPower Gateway SNTP implementation uses slew correction for offsets of 0.5 seconds or less and step corrections when offset is greater than 0.5 seconds. If the NTP server uses step correction to process leap second event, then this results in a step correction in DataPower Gateway." ]

[ [ "3a", " FLASH (ALERT) ABSTRACT" ], [ "3b", " 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." ], [ "3c", "A leap second is scheduled for 31 December 2016 at 23h 59m 60s UTC." ], [ "3d", "In the past, the addition of leap seconds caused some systems running older Linux kernels to fail." ], [ "3e", "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." ], [ "3f", "Other FDCs are also possible. CONTENT" ], [ "3g", "On 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." ], [ "3h", "Prior leap second insertions, including the 30 June 2016 leap second, caused some Linux systems to exhibit unexplained high CPU usage." ], [ "3i", "IBM MQ and WebSphere MQ use the Native POSIX Thread Library (NPTL) which relies on futuxes (\"fast userspace mutexes\") for synchronization between threads." ], [ "3j", "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: *" ], [ "3k", " * Leap Second to be added on December 31st 2016 * * *" ], [ "3l", " * General information on Leap Second 2016 *" ], [ "3m", " * Fixes and workarounds to avoid issues caused by Leap Second 2015 * * *" ], [ "3n", " * Addition of leap second causes spuriously high CPU usage and futex lockups" ], [ "3o", "Contact 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." ], [ "3p", "If you encounter this problem, the following workaround may resolve the high CPU usage." ], [ "3q", "As root, run:" ], [ "3r", " * date -s \"$(LC_ALL=C date)\" PRODUCT ALIAS/SYNONYM" ], [ "3s", " IBM MQ WMQ WebSphere MQ MQSeries" ] ]

[ "3b", "3d", "3e", "3h", "3i", "3j", "3n" ]

[ " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS SUGGESTION FOR FUTURE RELEASE.\n \n \n \n\nERROR DESCRIPTION\n * BPC overloaded modelled faults are not distinguished by\n the Mediation Flow Component. A BPC flow can set a Fault Name\n field amongst other details for a thrown fault, however a\n Mediation Flow Component is only able to distinguish between\n modelled faults using their BO Type.\n \n If two different modelled faults have the same BO Type, the\n modelled fault that is selected is not consistent, even if\n the BPC module has given them different Fault Names.\n \n \n \n \n \n\nLOCAL FIX\n * n/a\n \n \n \n \n \n\nPROBLEM SUMMARY\n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n\nCOMMENTS\n * If you experience this issue there is a workaround by using\n different Business Objects for each of the modelled faults.\n This allows the mediation to select the correct one. To\n implement this workaround you should perform the following:\n \n 1) Create new Business Objects in the library for each\n modelled fault. For example, Fault1 and Fault2 that both have\n the same structure as the previous common BO.\n \n 2) Change the 'Type' fields of the modelled faults in the\n interface to use these new Business Objects instead of the\n common Business Object.\n \n 3)In the BPC flow replace the use of the common Business\n Object with one of the new Business Objects as appropriate.\n Every instance of the common Business Object will need be to\n changed.\n \n When the flow is run, the BPC process will throw a different\n Business Object for the different faults, which can then be\n matched to the correct modelled fault flow in the mediation.\n \n NOTE: APAR JR28228 [http://www-01.ibm.com/support/docview.wss?uid=swg1JR28228] allows the BPC faults with common Business\n Objects to be distinguished when using an SCA binding, however\n the above workaround is still required when using a Mediation\n Flow Component.\n \n \n \n \n \n\nAPAR INFORMATION\n * APAR NUMBER\n IC55468\n \n \n * REPORTED COMPONENT NAME\n WEB ESB FOR WIN\n \n \n * REPORTED COMPONENT ID\n 5724I8200\n \n \n * REPORTED RELEASE\n 200\n \n \n * STATUS\n CLOSED SUG\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 2008-02-27\n \n \n * CLOSED DATE\n 2008-07-10\n \n \n * LAST MODIFIED DATE\n 2008-07-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\nAPPLICABLE COMPONENT LEVELS", " 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", " TECHNOTE (FAQ)\n\nQUESTION\n Which APIs are available in WebSphere Process Server Version 7 to interact with business processes and human tasks? \n\nANSWER\nWebSphere Process Server version 7.0 offers three APIs to interact with business processes and human tasks: \n\n * Business Flow Manager \n * Human Task Manager \n * Business Process Choreographer Explorer components\n\n\nThe documentation for these interfaces can be found in the IBM WebSphere Business Process Management information center: * Go to http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wps.doc/welcome_wps.html [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wps.doc/welcome_wps.html] \n * Select WebSphere Process Server for Multiplatforms, Version 7.0 \n * For general Business Process Choreographer API concepts, navigate to Developing > Developing client applications for business processes and tasks at http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.websphere.bpc.doc/doc/bpc/t6ovr.html [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.websphere.bpc.doc/doc/bpc/t6ovr.html]\n\n\nThe following generic programming interfaces can be used for building client applications that interact with business processes and human tasks: * Enterprise JavaBeans (EJB), \n * Web service, \n * Java Message Service (JMS), \n * Representational State Transfer Services (REST) \n\n\nFor a comparison of these interfaces, refer to the following information center topics: * Comparison of the programming interfaces for interacting with business processes and human tasks at http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.websphere.bpc.doc/doc/bpc/cbpcapi_compare.html [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.websphere.bpc.doc/doc/bpc/cbpcapi_compare.html] \n * Business Flow Manager API comparison http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.bpc.doc/doc/bpc/rbpcapi_comparebfm.htm [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.bpc.doc/doc/bpc/rbpcapi_comparebfm.htm] \n * Human Task Manager API comparison http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.bpc.doc/doc/bpc/rbpcapi_comparehtm.htm [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.bpc.doc/doc/bpc/rbpcapi_comparehtm.htm]\n\n\n\nUse the following links to navigate to the Java documentation for the Business Process Choreographer APIs: \n\nBusiness Flow Manager APIs (Package com.ibm.bpe.api): \nhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wbpmcore.javadoc.doc/web/apidocs/com/ibm/bpe/api/package-summary.html [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wbpmcore.javadoc.doc/web/apidocs/com/ibm/bpe/api/package-summary.html] \n\nHuman Task Manager APIs and SPIs \n(Package com.ibm.task.api): \nhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wbpmcore.javadoc.doc/web/apidocs/com/ibm/task/api/package-summary.html [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wbpmcore.javadoc.doc/web/apidocs/com/ibm/task/api/package-summary.html] \n(Package com.ibm.wbit.tel): \nhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.websphere.wbpmcore.javadoc.doc/web/apidocs/com/ibm/wbit/tel/package-summary.html [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.websphere.wbpmcore.javadoc.doc/web/apidocs/com/ibm/wbit/tel/package-summary.html] \n(Package com.ibm.task.spi) \nhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wbpmcore.javadoc.doc/web/apidocs/com/ibm/task/spi/package-summary.html [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wbpmcore.javadoc.doc/web/apidocs/com/ibm/task/spi/package-summary.html] \n\nWebSphere Process Server REST Interface \nhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.bspace.help.api.rest.doc/rest/wsprocessserver/index.htm [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.bspace.help.api.rest.doc/rest/wsprocessserver/index.htm] \n\n\nBusiness Process Choreographer Explorer components APIs 1. Go to \n http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wps.doc/welcome_wps.html [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wps.doc/welcome_wps.html] \n 2. Navigate to the following topics in the information center:\n WebSphere Process Server ... Version 7.0 > Reference > Programming information > Generated API and SPI documentation \n 3. Expand the Generated API and SPI documentation navigation tree, then you can see the following Business Process Choreographer Explorer components related packages:\n com.ibm.bpc.clientcore\n com.ibm.bpc.clientcore.converter\n com.ibm.bpc.clientcore.exception\n com.ibm.bpe.clientmodel\n com.ibm.bpe.clientmodel.bean\n com.ibm.bpe.jsf.component.taglib\n com.ibm.bpe.jsf.handler\n com.ibm.task.clientmodel\n com.ibm.task.clientmodel.bean\n\n\nUse the following links to navigate to some Business Process Choreographer related interfaces: \nBusiness Space Information Center\nhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.bspace.ic.main.doc/welcome/bspace_welcome.html [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.bspace.ic.main.doc/welcome/bspace_welcome.html]\n- Developing widgets\nhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.bspace.help.devt.doc/doc/developing_widgets/developingwidgets.html [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.bspace.help.devt.doc/doc/developing_widgets/developingwidgets.html]\n- WebSphere Process Server REST Interface http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.bspace.help.api.rest.doc/rest/wsprocessserver/index.htm [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.bspace.help.api.rest.doc/rest/wsprocessserver/index.htm]\n\n\nBusiness objects and service data objects (SDO) APIs\nhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.wbit.help.main.doc/topics/sdoapi.html [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.wbit.help.main.doc/topics/sdoapi.html]\nBusiness Object APIs (Package com.ibm.websphere.bo):\nhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wbpmcore.javadoc.doc/web/apidocs/com/ibm/websphere/bo/package-summary.html [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wbpmcore.javadoc.doc/web/apidocs/com/ibm/websphere/bo/package-summary.html]\n\n\nSCA Client APIs (Package com.ibm.websphere.sca): \nhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wbpmcore.javadoc.doc/web/apidocs/com/ibm/websphere/sca/package-summary.html [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wbpmcore.javadoc.doc/web/apidocs/com/ibm/websphere/sca/package-summary.html]\nFor instance to locate and invoke a business process as a service.\n\n\nUse the following link to navigate to the Business Process Choreographer Samples Web Page:\nhttp://publib.boulder.ibm.com/bpcsamp/index.html [http://publib.boulder.ibm.com/bpcsamp/index.html]\n\nTo find the API code examples and code snippets, use the following navigation paths:\nSelect > Interaction with Processes >. \n\nThe following topics are available:\nInteraction with processes and human tasks\n- SCA\n- SCA - JMS binding\n- Web service - SOAP\n- EJB API - Overview\n- EJB API - Details\n- Web service API - J2EE client\n- Web service API - .NET client\n- REST API\n- Query Properties\n- Query Tables\n- Query Table Builder\n- Custom JSF client\nSelect > Human Task Features > . \n- Different subtopics contain API code snippets. \nSelect > SDO Programming > . The following topics are available:\n- Basic Service Data Object (SDO) Programming API\n- Advanced Service Data Object (SDO) Programming API\n- Service Data Object (SDO) Programming API Content Assist\n\n\nFor API information of other WebSphere Process Server versions, go to \nhttp://www.ibm.com/software/integration/wps/library/index.html [http://www.ibm.com/software/integration/wps/library/index.html]\nand navigate to the WebSphere Process Server version you want to select.\nUse the navigation pane or the search capability to find the API topics.", " A FIX IS AVAILABLE\nWebSphere Enterprise Service Bus V6.2.0 Fix Pack 2 (6.2.0.2) [http://www-01.ibm.com/support/docview.wss?uid=swg24024407]\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 internal name for storing custom queries in the BPC Explorer\n also contains the userID that logged on to BPC Explorer. In case\n this userID gets too long, the field for the name to store the\n custom query on the DB is too short.\n This results then in an SQL error message and the user cannot\n store any custom view within the BPC Explorer anymore.\n \n \n \n \n \n\nLOCAL FIX\n * N/A\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Saving BPC Explorer personalized/customized views requires a\n unique name.\n The user ID was part of the generated name, but with a long user\n ID the length of the name exceeds the allowed maximum.\n Name generation has been improved to make sure that the maximum\n length is not exceeded.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Problem will be fixed with V6202\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IZ53467\n \n \n * REPORTED COMPONENT NAME\n BUS PRC CHOREOG\n \n \n * REPORTED COMPONENT ID\n 5655FLW11\n \n \n * REPORTED RELEASE\n 620\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 2009-06-17\n \n \n * CLOSED DATE\n 2009-07-20\n \n \n * LAST MODIFIED DATE\n 2009-07-20\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n IZ53464\n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n BUS PRC CHOREOG\n \n \n * FIXED COMPONENT ID\n 5655FLW11\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R620 PSY\n UP", " FIXES ARE AVAILABLE\nVersion 8.0.1 Fix Pack 2 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24035701]\nVersion 7.5.1 Fix Pack 2 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24036462]\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 * IndexOutOfBoundsException for BPC Explorer \"Manage Views\" if\n customer has stored queries in database.\n \n If a customer has created stored queries without user-defined\n properties in his database he will not be able to use the\n \"Manage Views\" option in BPC Explorer.\n A java.lang.IndexOutOfBoundsException is thrown.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * No further details available.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * All stored queries are checked if they are valid stored queries\n for BPC Explorer. Invalid stored queries are ignored.\n \n \n \n \n \n\nTEMPORARY FIX\n * Not applicable\n \n \n \n \n \n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n JR45795\n \n \n * REPORTED COMPONENT NAME\n BPM ADVANCED\n \n \n * REPORTED COMPONENT ID\n 5725C9400\n \n \n * REPORTED RELEASE\n 801\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 2013-02-20\n \n \n * CLOSED DATE\n 2015-02-06\n \n \n * LAST MODIFIED DATE\n 2015-02-06\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n JR45713 [http://www-01.ibm.com/support/docview.wss?uid=swg1JR45713]\n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n BPM ADVANCED\n \n \n * FIXED COMPONENT ID\n 5725C9400\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R801 PSN\n UP" ]

[ [ "1a", " DOWNLOADABLE FILES ABSTRACT" ], [ "1b", " In Business Process Manager Advanced Version 8.0.1, the default protocol used by Business Process Choreographer Explorer was changed to use HTTPS." ], [ "1c", "You can switch it back to HTTP. DOWNLOAD DESCRIPTION" ], [ "1d", "When 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." ], [ "1e", "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." ], [ "1f", "Attention: It is not recommend to use the insecure HTTP protocol." ], [ "1g", "Using HTTP for the Business Process Choreographer Explorer can open your organization to possible security problems." ], [ "1h", "Switching to HTTP" ], [ "1i", "If you need to switch Business Process Choreographer Explorer from HTTPS to use HTTP, complete the following actions: 1." ], [ "1j", "Download the unsecureExplorer.ant script file, which is attached near the bottom of this page. 2." ], [ "1k", "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." ], [ "1l", " * On Linux, UNIX-based and z/OS platforms, delete the install_root/ProcessChoreographer/internal/bpcexplorer_secure_backup.ear file." ], [ "1m", " * On Microsoft Windows platforms, delete the" ], [ "1n", " install_root\\ProcessChoreographer\\internal\\bpcexplorer_secure_backup.ear file. 3." ], [ "1o", "Run the script to patch the bpcexplorer.ear file." ], [ "1p", "In a network deployment environment, you must run the script on the deployment manager." ], [ "1q", "* On Linux, UNIX-based and z/OS platforms, enter the following command:" ], [ "1r", " install_root/ws_ant.sh -f unsecureExplorer.ant" ], [ "1s", " * On Windows platforms, enter the following command:" ], [ "1t", " install_root\\ws_ant.bat -f unsecureExplorer.ant" ], [ "1u", " Note: A backup copy of the original EAR file is created named bpcexplorer_secure_backup.ear. 4." ], [ "1v", "Deploy the patched bpcexplorer.ear file by updating the profile." ], [ "1w", "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]." ], [ "1x", " * 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]." ], [ "1y", "Remember: 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." ], [ "1z", "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." ], [ "1aa", "Switching back to HTTPS" ], [ "1ab", "If you need to switch Business Process Choreographer Explorer back from HTTP to HTTPS, complete the following actions: 1." ], [ "1ac", "Change to the directory where the backup EAR file is located." ], [ "1ad", "* On Linux, UNIX-based and z/OS platforms, its location is" ], [ "1ae", " install_root/ProcessChoreographer/internal" ], [ "1af", " * On Windows platforms, its location is" ], [ "1ag", " install_root\\ProcessChoreographer\\internal 2." ], [ "1ah", "In that directory, copy or rename the backup EAR file bpcexplorer_secure_backup.ear to bpcexplorer.ear and overwrite any existing copy. 3." ], [ "1ai", "Deploy the original HTTPS version by updating the profile." ], [ "1aj", "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]." ], [ "1ak", " * 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]." ], [ "1al", "Download file unsecureExplorer.ant [/support/docview.wss?uid=swg24034421&aid=2]unsecureExplorer.ant [/support/docview.wss?uid=swg24034421&aid=1] PRODUCT ALIAS/SYNONYM BPM" ] ]

[ "1b", "1c", "1d", "1e", "1i", "1j", "1o", "1p", "1q", "1r", "1s", "1t", "1u" ]

[ " FIXES ARE AVAILABLE\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.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 * Installing JAVA 7.1 on RHEL 7.1 fails with error \" No Supported\n Operating System Found.\" The prereq checker files doesn't have\n RHEL 7.x listed.\n \n \n \n \n \n\nLOCAL FIX\n * you can bypass operating-system prerequisite checking, add\n disableOSPrereqChecking=true to the config.ini file in\n IM_install_root/eclipse/configuration and restart Installation\n Manager.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server *\n ****************************************************************\n * PROBLEM DESCRIPTION: Installing JAVA 7.1 on RHEL 7.1 fails *\n * with error \"No Supported Operating *\n * System Found.\" *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n The Installation Manager fails to install JAVA 7.1 on RHEL\n 7.1 with error \"No Supported Operating System Found\". The\n failure is caused by the JAVA 7.1 OS prereq bundle because\n RHEL 7.x is not included the JAVA 7.1 supported operating\n system list.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * For the fix, we added RHEL 7.x in the JAVA 7.1 supported\n operating system list which is carried by the JAVA 7.1 OS\n prereq bundle.\n \n The fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.5.7. 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 PI41712\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-05-25\n \n \n * CLOSED DATE\n 2015-06-25\n \n \n * LAST MODIFIED DATE\n 2015-06-25\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", "requirements requirements requirements requirement system prereqs prereq prereqs prereq prereqs prereq requirement system requirements soe soe soe; SystemRequirementsDocument PRODUCT DOCUMENTATION\n\nABSTRACT\n This document contains system requirements for WebSphere MQ V6 on Linux for System p. \n\nCONTENT\n \n\nOperating Systems [/support/docview.wss?uid=swg27006271&amp;aid=1] * Red Hat Enterprise Linux (RHEL) V3.0 with Update 2 or later update \n * Red Hat Enterprise Linux (RHEL) V4.0 or later update [see note 9] \n * Red Hat Enterprise Linux (RHEL) V5.0 or later update [see notes 5, 9 and 12] \n * SUSE Linux Enterprise Server (SLES) V9#notes with SP1 or later update \n * SUSE Linux Enterprise Server (SLES) V10 or later update [see note 2] \n * SUSE Linux Enterprise Server (SLES) V11 or later update [see note 10]\n\nHardware Requirements [/support/docview.wss?uid=swg27006271&amp;aid=1] * Linux for iSeries and pSeries: 64-bit iSeries and pSeries IBM POWER processor-based systems only, capable of running the required level of a compatible operating system with enough storage to meet the combined requirements of the programming prerequisites, WebSphere MQ, the access methods and the application programs. \n * POWER7 systems are supported with WebSphere MQ 6.0.1.0 or later when the guidance in IBM Developer Kits support for IBM Power7™ systems [http://www.ibm.com/developerworks/java/jdk/power7/index.html] is adhered to.\n\nJava and JMS Client [/support/docview.wss?uid=swg27006271&amp;aid=1] * 32-bit * IBM 32-bit SDK for Linux for iSeries and pSeries, Java 2 Technology Edition V1.4.2 (supported on pSeries only, supplied with WebSphere MQ) \n * IBM 32-bit SDK for Linux for iSeries and pSeries, Java 2 Technology Edition V5.0 (SR1 or above) [Only if the JDK is supplied with another IBM product] \n * IBM 32-bit SDK for Linux for iSeries and pSeries, Java 2 Technology Edition V6.0 (SR3 or above) [see note 8]\n \n \n * 64-bit * IBM 64-bit SDK for Linux for iSeries and pSeries, Java 2 Technology Edition V1.4.2 (supported on pSeries only, supplied with WebSphere MQ) \n * IBM 64-bit SDK for Linux for iSeries and pSeries, Java 2 Technology Edition V5.0 (SR1 or above) [Only if the JDK is supplied with another IBM product] \n * IBM 64-bit SDK for Linux for iSeries and pSeries, Java 2 Technology Edition V6.0 (SR3 or above) [see note 8]\n \n \n\nDatabases [/support/docview.wss?uid=swg27006271&amp;aid=1] Where IBM WebSphere MQ is acting as the transaction manager.\n * DB2 Universal Database V8.2 [see note 1] \n * IBM DB2 V9.1 for Linux, UNIX, and Windows (JDBC/XA not supported) [see note 2]\n\nCompilers [/support/docview.wss?uid=swg27006271&amp;aid=1] * GNU C Compiler (gcc) and g++ V3.2 \n * GNU C Compiler (gcc) and g++ V3.3 \n * GNU C Compiler (gcc) and g++ V3.4 [see note 7] \n * GNU C Compiler (gcc) and g++ V4.1 [see note 7] \n * Micro Focus Server Express V4.0 (COBOL) \n * Micro Focus Server Express V5.0 (COBOL) \n * Micro Focus Server Express V5.1 (COBOL) [see note 11] \n\nConnectivity [/support/docview.wss?uid=swg27006271&amp;aid=1] * IBM Communications Server for Linux V6.2 \n * TCP/IP (IPv4 and IPv6 provided by the operating system)\n\nTransaction Manager [/support/docview.wss?uid=swg27006271&amp;aid=1] Where one of these products is acting as the transaction manager and IBM WebSphere MQ is acting as a resource manager, it's recommended that you contact the transaction manager vendor in the first instance for support. \n * IBM WebSphere Application Server V5.1 or later Fix Pack (for SLES V9 only) \n * IBM WebSphere Application Server V6.0.1 or later \n * IBM WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2 (see this document [http://www.ibm.com/support/docview.wss?rs=175&context=SSAL2T&q1=resiliency&uid=swg21307212&loc=en_US&cs=utf-8&lang=en] for more information) \n * IBM WebSphere Application Server, including the WebSphere Application Server client container, V6.1 (see this document [http://www.ibm.com/support/docview.wss?rs=175&context=SSAL2T&q1=resiliency&uid=swg21307203&loc=en_US&cs=utf-8&lang=en] for more information) \n * IBM WebSphere Application Server, including the WebSphere Application Server client container, V7.0 (see this document [http://www.ibm.com/support/docview.wss?rs=171&context=SSFKSJ&dc=DB540&uid=swg21316899&loc=en_US&cs=UTF-8&lang=en&rss=ct171websphere] for more information)\n\nSOAP Support [/support/docview.wss?uid=swg27006271&amp;aid=1] * IBM 32-bit or 64-bit SDK for Linux for iSeries and pSeries, Java 2 Technology Edition V1.4.2 (supported on pSeries only, supplied with WebSphere MQ) \n * Apache Axis V1.1 (supplied with WebSphere MQ) \n\nCryptography Cards [/support/docview.wss?uid=swg27006271&amp;aid=1] Refer to the Cryptography Card List for WebSphere MQ v6 and v7 [http://www.ibm.com/support/docview.wss?rs=171&context=SSFKSJ&context=SSEP7X&q1=cryptography&uid=swg21326434&loc=en_US&cs=utf-8&lang=en] document for further information. \n\nNotes: \n\n 1. JDBC/XA usage is not supported on this platform. \n 2. Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. \n 3. WebSphere MQ V6.0.2.0 or later is required. \n 4. For details of the Support Statement for JCA (on WebSphere MQ V6.0.2.1 or later only) please see here. [http://www.ibm.com/support/docview.wss?rs=171&uid=swg27009524] \n 5. WMQ Fix Pack 6.0.2.3 or later is required. \n 6. Defect support is available for virtualisation 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 virtualisation environments. WebSphere MQ Support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the virtualisation environment itself. \n 7. On Linux platforms, if you need to use SSL in a C++ MQ application then you must link the application against the libstdc++.so.5 runtime library. This is because the version of the GSkit SSL libraries supplied with MQ depends on libstdc++.so.5 and this GSkit version is not compatible with other C++ runtime library versions. MQ C++ applications built against the GCC 3.2 or 3.3 C++ runtime libraries comply with this restriction and will be able to use SSL. \n 8. WMQ Fix Pack 6.0.2.5 or later is required. \n 9. SELinux must be disabled. \n 10. WMQ Fix Pack 6.0.2.6 or later is required. \n 11. WebSphere MQ V6.0.2.8 or later is required. \n 12. Defect support is available for Linux environments that are fully compatible - both source and binary - with Red Hat Enterprise Linux V5. 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.\n 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\n\n\nChange History \n * 30 August 2005: Added support for RHEL V4.0. \n * 26 October 2005: Modifications to the format and minor clarifications. \n * 9 February 2006: Clarified WebSphere Application Server FP support. \n * 2 May 2006: Added support for IBM SDK V5.0. \n * 27 June 2006: Added \"or later maintenance update\" to the Red Hat operating systems. \n * 6 October 2006: Added \"SP1 or later\" to SLES 9. \n * 24 January 2007: Added note 1 \"Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.\" \n * 1 February 2007: Added support for SLES V10 or later. \n * 7 February 2007: Added support for IBM DB2 Universal Database V9.1 (JDBC/XA not supported) \n * 30 March 2007: Added note 4. \n * 12 July 2007: Made change to databases IBM DB2 and Connectivity TCP/IP \n * 04 February 2008: Added RHEL V5.0 support. \n * 10 March 2008: Added virtualisation note. \n * 15 March 2008: Added support for Micro Focus Server Express V5.0 (COBOL). \n * 17 June 2008: Added support for GNU C Compiler (gcc) and g++ V4.1. \n * 19 June 2008: Added SSL note 7. \n * 10 July 2008: In the Transaction Manager section added the IBM WebSphere Application Server V6.0.2 and V6.1 entries. \n * 10 November 2008: Added support for IBM WebSphere Application Server, including the WebSphere Application Server client container, V7.0. \n * 11 November 2008: Added support for Red Hat Enterprise Linux (RHEL) V5.1 and V5.2. \n * 22 December 2008: Added the Cryptography Cards section. \n * 7 April 2009: Added support for IBM 32/64-bit SDK for Linux for iSeries and pSeries, Java 2 Technology Edition V6.0. \n * 9 July 2009: Added support for Red Hat Enterprise Linux (RHEL) V5.3 and SUSE Linux Enterprise Server (SLES) V11. \n * 22 October 2009: Added support for Micro Focus Server Express V5.1 (COBOL). \n * 14 April 2010: Added support for Red Hat Enterprise Linux (RHEL) V5.4. \n * 20 July 2010: Clarified POWER7 support. \n * 10 May 2011: Added the Linux Redhat V5.0 compatibility support statement. \n * 2 July 2012: Changed expiry date to keep current. \n * 2 July 2014: Changed expiry date to keep current. \n * 5 July 2016: Changed expiry date to keep current.\n\nRELATED INFORMATION\n All WebSphere MQ System requirements [http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006467]\nWebSphere MQ Library [http://www.ibm.com/software/integration/wmq/library/]\nWebSphere MQ Recommended Fixes [http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\n\n\n\nPRODUCT ALIAS/SYNONYM\n WMQ MQ", " 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.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 NEW FUNCTION.\n \n \n \n\nERROR DESCRIPTION\n * Add EJBDeploy support to specify a different JDK than the one\n being used by WebSphere Application Server.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Portal *\n * Server. *\n ****************************************************************\n * PROBLEM DESCRIPTION: IBM WebSphere Portal Server users are *\n * not able to specify an alternate JDK *\n * to be used by the ejbdeploy component. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n EJBDeploy fails with error \"Java runtime version not\n supported\".\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The EJBDeploy component was modified to support being run\n using a JDK other than the one configured with the IBM\n WebSphere Portal Server installation.\n \n The fix for this APAR is currently targeted for inclusion in\n WebSphere Application Server v8.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 PI63329\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 2016-05-31\n \n \n * CLOSED DATE\n 2016-08-15\n \n \n * LAST MODIFIED DATE\n 2016-08-15\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 * R850 PSY\n UP", " A FIX IS AVAILABLE\nPI73197:Enable Java 8 Support for EJBDeploy on WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24043474]\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 * Java 8 is not supported for EJBDeploy on WebSphere\n Application Server 8.5.5.9 or later\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: EJBDeploy does not run on Java 8 *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n EJBDeploy does not run on Java 8\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The fix for this APAR is targeted for inclusion in 2Q2018.\n \n Please refer to the Recommended Updates page for delivery\n 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 PI73197\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 2016-12-05\n \n \n * CLOSED DATE\n 2017-03-13\n \n \n * LAST MODIFIED DATE\n 2018-07-16\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", "EJB; EJBDeploy TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Learning more about EJBDeploy is the first step in the troubleshooting process. This document provides you with educational information that can help you learn more about this topic. \n\nRESOLVING THE PROBLEM\n \n\nTAB NAVIGATION\n * Learning more [http://www.ibm.com/support/docview.wss?uid=swg21994741]- selected tab,\n * Troubleshooting [http://www.ibm.com/support/docview.wss?uid=swg21994742]\n * Collect data [http://www.ibm.com/support/docview.wss?uid=swg21260603]\n\nGetting background information on EJBDeploy \n\n All Java Enterprise Edition (Java EE ) EJB applications go through an EJB deployment phase in which your application is customized to run in an application server. Typically, this is accomplished by a deployment tool that is specific to the application server. It generates code to allow your EJB to run within an EJB container. Some application server products' deployment tools alter the bytecode of your application classes rather than generating code ;however, the end result is similar. \n\nThe EJBDeploy Tool \n\nHistorically, EJB deployment in the Application Server product has been performed by the EJBDeploy tool, which is included with WebSphere® Application Server and packaged with the development tools for the WebSphere products. \nThe EJBDeploy tool inspects the external interfaces for your enterprise beans, generates wrapper code as .java files, and compiles the code using the javac compiler. The resulting .class files are packaged in your EJB module with your application code. For modules including and previous to EJB 2.1, the EJBDeploy tool must be invoked manually. \nPlease note that in WebSphere Application Server 8.5.5.x and below, the tool can only deploy Java EE applications compiled with a JDK level of 7 or below. To deploy JDK 8 compiled web applications, please upgrade to WebSphere Application Server V9." ]

[ [ "3a", " A FIX IS AVAILABLE" ], [ "3b", "PI73197:Enable Java 8 Support for EJBDeploy on WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24043474] SUBSCRIBE" ], [ "3c", "You can track all active APARs for this component. APAR STATUS" ], [ "3d", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "3e", " * Java 8 is not supported for EJBDeploy on WebSphere" ], [ "3f", " Application Server 8.5.5.9 or later LOCAL FIX PROBLEM SUMMARY" ], [ "3g", " * ****************************************************************" ], [ "3h", " * USERS AFFECTED: All users of IBM WebSphere Application *" ], [ "3i", " * Server *" ], [ "3j", " ****************************************************************" ], [ "3k", " * PROBLEM DESCRIPTION: EJBDeploy does not run on Java 8 *" ], [ "3l", " ****************************************************************" ], [ "3m", " * RECOMMENDATION: *" ], [ "3n", " ****************************************************************" ], [ "3o", " EJBDeploy does not run on Java 8 PROBLEM CONCLUSION" ], [ "3p", " * The fix for this APAR is targeted for inclusion in 2Q2018." ], [ "3q", " Please refer to the Recommended Updates page for delivery" ], [ "3r", " information:" ], [ "3s", " http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980] TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "3t", " * APAR NUMBER" ], [ "3u", " PI73197" ], [ "3v", " * REPORTED COMPONENT NAME" ], [ "3w", " WEBSPHERE APP S" ], [ "3x", " * REPORTED COMPONENT ID" ], [ "3y", " 5724J0800" ], [ "3z", " * REPORTED RELEASE" ], [ "3aa", " 850" ], [ "3ab", " * STATUS" ], [ "3ac", " CLOSED PER" ], [ "3ad", " * PE" ], [ "3ae", " NoPE" ], [ "3af", " * HIPER" ], [ "3ag", " NoHIPER" ], [ "3ah", " * SPECIAL ATTENTION" ], [ "3ai", " NoSpecatt / Xsystem" ], [ "3aj", " * SUBMITTED DATE" ], [ "3ak", " 2016-12-05" ], [ "3al", " * CLOSED DATE" ], [ "3am", " 2017-03-13" ], [ "3an", " * LAST MODIFIED DATE" ], [ "3ao", " 2018-07-16" ], [ "3ap", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "3aq", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "3ar", " * FIXED COMPONENT NAME" ], [ "3as", " WEBSPHERE APP S" ], [ "3at", " * FIXED COMPONENT ID" ], [ "3au", " 5724J0800" ], [ "3av", "APPLICABLE COMPONENT LEVELS" ] ]

[ "3e", "3k", "3o", "3p" ]

[ " DOWNLOADABLE FILES\n\nABSTRACT\n This cumulative fix pack updates JRules V7.1.1 (7.1.1, 7.1.1.1, 7.1.1.2, 7.1.1.3 or 7.1.1.4) to V7.1.1.5. \n\nDOWNLOAD DESCRIPTION\nThis cumulative fix pack updates JRules V7.1.1 (7.1.1, 7.1.1.1, 7.1.1.2, 7.1.1.3 or V7.1.1.4) to V7.1.1.5. \n\nThis fix pack does not work directly with earlier versions of JRules. Users of V7.0 and V7.1.0 should update to V7.1.1 in order to install V7.1.1.5.\n\nThis fix pack is entitled. Only customers who have purchased JRules V7.1.1 can download this fix pack.\n\nPREREQUISITES\nWebSphere ILOG JRules V7.1.1\n\nDOWNLOAD PACKAGE\nWebSphere ILOG JRules V7.1.1.5 \n\n\nPROBLEMS SOLVED\nFor details on problems fixed in this fix pack, refer to the Fix list for V7.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27019787#7114] document.\n\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options WebSphere ILOG JRules V7.1.1.5 Windows 18 Oct 2012 Language Independent 4000000000 HTTP [http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+ILOG+JRules&release=All&platform=All&function=fixId&fixids=7.1.1.5-WebSphere-JRules-Windows-fp0005&includeRequisites=1&includeSupersedes=0&do] WebSphere ILOG JRules V7.1.1.5 UNIX 18 Oct 2012 Language Independent 4000000000 HTTP [http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+ILOG+JRules&release=All&platform=All&function=fixId&fixids=7.1.1.5-WebSphere-JRules-Unix-fp0005&includeRequisites=1&includeSupersedes=0&downl] \nTECHNICAL SUPPORT\n \n\n * Contact 1-800-IBM-SERV (U.S. only) or visit the WebSphere ILOG JRules Support site [http://www-947.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_ILOG_JRules].\n * Passport Advantage Online support [http://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html] \n * Fix List for WebSphere ILOG JRules BRMS V7.1.1.5 [http://www-01.ibm.com/support/docview.wss?uid=swg27019787#7115]\n * Known limitations in WebSphere Business Rule Management System V7.1.1 [http://www-01.ibm.com/support/docview.wss?uid=swg21498138]\n * WebSphere ILOG JRules BRMS V7.1 Download document [http://www-01.ibm.com/support/docview.wss?uid=swg24030938]\n\n\n\n [/support/docview.wss?uid=swg24033599&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24033599&aid=2]Problems (APARS) fixed\nRS00677, RS00691, RS00706, RS00752, RS00784, RS00787, RS00788, RS00794, RS00806, RS00814, RS00826, RS00831, RS00832, RS00838, RS00844, RS00847, RS00858, RS00866, RS00903, RS00927, RS00951, RS00957, RS00979, RS01004, RS01030, RS01031, RS01036, RS01053, RS01065, RS01066, RS01103, RS01137", "DB; rule designer; decision center TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Synchronization between Rule Studio and Rule Team Server (RTS) fails with a \"WRONG DATA TYPE\" error. \n\nSYMPTOM\nYou get the following error when publishing a project to RTS on WebLogic: \n\n<Debug> <JDBCDriverLogging> <aixth98> <appdev_jrules_aixth98> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> \n<1333129090586> <BEA-000000> <java.sql.SQLException: [BEA][DB2 JDBC Driver][DB2]VALUE OF INPUT HOST VARIABLE NUM 2 NOT USED; WRONG DATA TYPE \n\n\nCAUSE\nA non-supported database driver is used. \n\n\nENVIRONMENT\nThe above error is displayed when using the WebLogic driver for DB2 with JRules V7.1, since only IBM drivers are supported in that version.\n\n\n\nDIAGNOSING THE PROBLEM\nRefer to the server logs for the full error message and make sure you are using one of the supported drivers.\n\n\n\nRESOLVING THE PROBLEM\nSwitch to a supported driver. \n\nRefer to the following links to find the list of supported drivers in the product hardware and software requirements for the version you are using.\n\nRELATED INFORMATION\n#JRules V7.0 hardware and software requirements [http://www.ibm.com/support/docview.wss?uid=swg27015807]\nJRules V7.1 hardware and software requirements [http://www.ibm.com/support/docview.wss?uid=swg27018135]\nODM hardware and software requirements [http://www.ibm.com/support/docview.wss?uid=swg27023067]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Modules:Rule Team Server Platform Independent 8.5, 8.0, 7.5", "RES; Rule Session Factories; RES packaging TECHNOTE (FAQ)\n\nQUESTION\n Which RES execution component should I package in my application if I use IlrPOJOSessionFactory? \n\nANSWER\nIn JRules 7, there are several rules session factories (IlrEJB3SessionFactory, IlrJ2SESessionFactory, IlrPOJOSessionFactory, IlrExtendedJ2SESessionFactory, IlrExtendedPOJOSessionFactory) for client application to connect to RES for rule invocations. \n\nIn a JEE environment, if you prefer to have a simple and non-ejb approach (web application or decision service), you can make use of IlrPOJOSessionFactory APIs for rule session creation. The execution component that is required to package together with the application will be simply jrules-res-session-java.jar. This jar file can be found at <JRules_Installed_dir>\\executionserver\\lib folder. \n\n \n\nFor JRules version 7.0.X, refer to JRules documentation at:\nWebSphere ILOG JRules V7.0 > Rule Studio online help > Executing rules > Tasks > Assembling and packaging a Rule Execution Server application > Packaging Java rule sessions [http://publib.boulder.ibm.com/infocenter/brjrules/v7r0/index.jsp?topic=/ilog.rules.jrules.doc/Content/Business_Rules/Documentation/_pubskel/JRules/ps_JRules_Global854.html] \n\nFor JRules version 7.1.X, refer to JRules documentation at:\nWebSphere ILOG JRules BRMS V7.1 > Rule Execution Server > Introducing Rule Execution Server > Assembling and packaging a Rule Execution Server application > Packaging Java rule sessions [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_Global966.html] \n\n\nRELATED INFORMATION\n#Choose a rule session to call RES on JEE server [http://www-01.ibm.com/support/docview.wss?uid=swg21400825]\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", "ILOG Rules for COBOL DOWNLOADABLE FILES\n\nABSTRACT\n This document describes how to download WebSphere ILOG Rules for COBOL V7.1.1.4 eAssembly images from IBM Passport Advantage Online. \n\nDOWNLOAD DESCRIPTION\n\n\n WebSphere ILOG Rules for COBOL V7.1.1.4 is an extension to WebSphere ILOG JRules V7.1.1.4. With Rules for COBOL, you can use the JRules business rule management system (BRMS) to create and manage business rules written for native COBOL data structures, deploy the rules in COBOL, and share business rules across multiple platforms. \n\nNote\n\nV7.1.1.4 is not compatible with Rules for COBOL V7.0.x and V7.1.0. Users of these versions should update to V7.1.1 before installing V7.1.1.4. \n\nContents\n\n This document provides a list of the eAssembly images for Rules for COBOL V7.1.1 and V7.1.1.4, and describes how to download the images from IBM Passport Advantage Online. \n\nMore information\n\n For further information about this product, see the WebSphere ILOG Decision Validation Services home page [http://www.ibm.com/software/integration/business-rule-management/decision-validation-services/support/index.html]. \n\nDownloading and assembling the product\n\n 1. Navigate your browser to the Find Downloads and Media [http://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/sdma/SDMA?PO=DOWNLOAD_FIND_BY_PART_NUMBER] page on IBM Passport Advantage Online.\n 2. Sign in using your IBM ID.\n 3. Select the Find by part number search option under Download finder options.\n 4. Search for each downloadable image by part number (parts are listed below).\n 5. Download all of the parts you require.\n 6. Unpack each of the parts into a separate directory on your system.\n 7. Follow the instructions in the documentation to install the product.\n\n[http://www.ibm.com/i/c.gif] Assembly Part Number Assembly Description Images Image Description CRBD1ML WebSphere ILOG Rules for COBOL V7.1 eAssembly CZM2WML WebSphere ILOG BRMS Rules for COBOL V7.1.1 for Windows Multilingual CZM2XML WebSphere ILOG BRMS Rule Studio for Rules for COBOL V7.1.1 for Windows Multilingual CI3IKML WebSphere ILOG Rules for COBOL V7.1.1.4 for Windows Multilingual CI3ILML WebSphere ILOG Rule Studio for COBOL V7.1.1.4 for Windows Multilingual CI3GTFR WebSphere ILOG BRMS Documentation French V7.1.1.4 for Windows CI3GUDE WebSphere ILOG BRMS Documentation German V7.1.1.4 for Windows CI3GVES WebSphere ILOG BRMS Documentation Spanish V7.1.1.4 for Windows CI3GWIT WebSphere ILOG BRMS Documentation Italian V7.1.1.4 for Windows CI3GXBP WebSphere ILOG BRMS Documentation Brazilian Portuguese V7.1.1.4 for Windows CI3GYNL WebSphere ILOG BRMS Documentation Dutch V7.1.1.4 for Windows CI3GZJA WebSphere ILOG BRMS Documentation Japanese V7.1.1.4 for Windows CI3H0KO WebSphere ILOG BRMS Documentation Korean V7.1.1.4 for Windows CI3H1SC WebSphere ILOG BRMS Documentation Simplified Chinese V7.1.1.4 for Windows CI3H2TC WebSphere ILOG BRMS Documentation Traditional Chinese V7.1.1.4 for Windows CI3H3RU WebSphere ILOG BRMS Documentation Russian V7.1.1.4 for Windows DOWNLOAD PACKAGE\nLinks to File(s): \n\nLabel or File Name URL [/support/docview.wss?uid=swg24030963&amp;aid=1] Download Director Platform Pkg Rel Date Language Size (Bytes) IBM Passport Advantage Online http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm] [/support/docview.wss?uid=swg24030963&amp;aid=1] [/support/docview.wss?uid=swg24030963&amp;aid=1] Windows 3/19/2010 English 3013607424 [/support/docview.wss?uid=swg24030963&amp;aid=1] [/support/docview.wss?uid=swg24030963&amp;aid=1] [/support/docview.wss?uid=swg24030963&amp;aid=1] [/support/docview.wss?uid=swg24030963&amp;aid=1] [/support/docview.wss?uid=swg24030963&amp;aid=1] [/support/docview.wss?uid=swg24030963&amp;aid=1] [/support/docview.wss?uid=swg24030963&amp;aid=1] [/support/docview.wss?uid=swg24030963&amp;aid=1] TECHNICAL SUPPORT\n \n\n * Contact 1-800-IBM-SERV (U.S. only) or visit the WebSphere ILOG Rules for COBOL Support site [http://www-947.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_ILOG_Rules_for_COBOL].\n * Passport Advantage Online support [http://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html] \n * Fix List for WebSphere ILOG JRules BRMS V7.1.1.4 [http://www-01.ibm.com/support/docview.wss?uid=swg27019787#7114]\n * Known limitations in WebSphere Business Rule Management System V7.1.1 [http://www-01.ibm.com/support/docview.wss?uid=swg21498138]\n * WebSphere ILOG JRules BRMS V7.1 Download document [http://www-01.ibm.com/support/docview.wss?uid=swg24030938]\n\n\n\n [/support/docview.wss?uid=swg24030963&aid=2]Problems (APARS) fixed [/support/docview.wss?uid=swg24030963&aid=3]Problems (APARS) fixed\nRS00742", " TECHNOTE (FAQ)\n\nQUESTION\n How do I migrate the database that contains the RuleApps deployed to Rule Execution Server from one version to another? \n\nCAUSE\nThe data structure has undergone some refactoring between JRules V6.7 and V7.0. \n\nFor instance, the RULESET_RESOURCES table for storing ruleset has been modified: in V6.7, the ruleset archive was split into several parts for storage but in V7.0 and later, it is stored as a CLOB. \n\nThere is no change between V7.X versions. \n\nAs a conclusion, you cannot reuse the Rule Execution Server V6.7 database tables directly with Rule Execution Server V7.1. \n\n\nANSWER\nIf you are migrating between V7.X versions, you can reuse the Rule Execution Server database schema directly with the new version. \n\n \n\nIf you are migrating from V6.X, you must proceed in two steps: \n\n 1. Set up a new Rule Execution Server database schema and create the Rule Execution Server V7.1 tables as explained in the documentation at WebSphere ILOG JRules BRMS V7.1: Java EE add-ons [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.install.doc/Content/Business_Rules/Documentation/_pubskel/JRules_Application_Servers/ps_Installing_JRules_IC.html] > Installing on <your application server> > Installing Rule Execution Server > Installing Rule Execution Server on <your application server>. \n 2. Migrate the V6.7 RuleApps to Rule Execution Server V7.1 in one of the following ways:\n\n\nOption 1 : Using Rule Execution Server Ant tasks * Use the JRules V6.7 res-fetch-all Ant task to back up all your RuleApps to a single RuleApp archive. Or use the JRules 6.7 res-fetch Ant task to back up a specific RuleApp. \n * Install and configure Rule Execution Server V7.1 according to the installation documentation [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.install.doc/Content/Business_Rules/Documentation/_pubskel/JRules_Application_Servers/ps_Installing_JRules_IC.html] on your server and using the new database schema. \n * Deploy the RuleApp archive to the new Rule Execution Server by running the JRules V7.1 res-deploy Ant task. \n\n\nOption 2: Using the Rule Execution Server management console * From the Rule Execution Server V6.7 console, click the Server Info tab and click Backup RuleApps to back up all the deployed RuleApps. A JAR archive file containing all the RuleApps is generated. \n * Install and configure Rule Execution Server V7.1 according to the installation documentation [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.install.doc/Content/Business_Rules/Documentation/_pubskel/JRules_Application_Servers/ps_Installing_JRules_IC.html] on your server and using the new database schema. \n * Access the Rule Execution Server V7.1 console, click the Server Info tab and click Restore RuleApps to restore the RuleApp.\n\n\nIf you are migrating from V7.1 to V7.5/V8.X, no ruleApp migration is needed, you can reuse the database. However, if you want to use the new managed XOM feature introduced in V7.5, you need to extend the database to include the XOM repository. You will do so either : \n\n * through theInstallation Settings Wizard that you will be prompted when accessing the new Rule Execution Server console, \n * or by running thexomrepository_<DatabaseName>.sqlscript found in directory <ODM_75/8X_installDir>/executionserver/databases on the existing database schema.\n\n\nFor more information on the managed XOM feature, see section Decision Server Rules V7.5 > Managing business rule execution in Rule Execution Server Deploying Java XOMs [http://publib.boulder.ibm.com/infocenter/dmanager/v7r5/topic/com.ibm.dserver.res/Content/Business_Rules/_pubskel/Infocenter_Primary/ps_DS_Rule_Execution_Server1500.html] of the documentation.\" RELATED INFORMATION\n#Migrating between JRules/WODM versions [http://www.ibm.com/support/docview.wss?uid=swg21589725]\nMigrating a Rule Project to JRules v7.0 and v7.1 [http://www.ibm.com/support/docview.wss?uid=swg21591800]\nMigrating to Rule Team Server v7.0 and v7.1 [http://www.ibm.com/support/docview.wss?uid=swg21591798]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Decision Server Maintenance Platform Independent 7.5 All Editions" ]

[ [ "4a", " TECHNOTE (FAQ) QUESTION" ], [ "4b", " How do I migrate the database that contains the RuleApps deployed to Rule Execution Server from one version to another? CAUSE" ], [ "4c", "The data structure has undergone some refactoring between JRules V6.7 and V7.0." ], [ "4d", "For instance, the RULESET_RESOURCES table for storing ruleset has been modified: in V6.7, the ruleset archive was split into several parts for storage but in V7.0 and later, it is stored as a CLOB." ], [ "4e", "There is no change between V7.X versions." ], [ "4f", "As a conclusion, you cannot reuse the Rule Execution Server V6.7 database tables directly with Rule Execution Server V7.1. ANSWER" ], [ "4g", "If you are migrating between V7.X versions, you can reuse the Rule Execution Server database schema directly with the new version." ], [ "4h", "If you are migrating from V6.X, you must proceed in two steps: 1." ], [ "4i", "Set up a new Rule Execution Server database schema and create the Rule Execution Server V7.1 tables as explained in the documentation at WebSphere ILOG JRules BRMS V7.1: Java EE add-ons [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.install.doc/Content/Business_Rules/Documentation/_pubskel/JRules_Application_Servers/ps_Installing_JRules_IC.html] > Installing on <your application server> > Installing Rule Execution Server > Installing Rule Execution Server on <your application server>. 2." ], [ "4j", "Migrate the V6.7 RuleApps to Rule Execution Server V7.1 in one of the following ways:" ], [ "4k", "Option 1 : Using Rule Execution Server Ant tasks * Use the JRules V6.7 res-fetch-all Ant task to back up all your RuleApps to a single RuleApp archive." ], [ "4l", "Or use the JRules 6.7 res-fetch Ant task to back up a specific RuleApp." ], [ "4m", " * Install and configure Rule Execution Server V7.1 according to the installation documentation [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.install.doc/Content/Business_Rules/Documentation/_pubskel/JRules_Application_Servers/ps_Installing_JRules_IC.html] on your server and using the new database schema." ], [ "4n", " * Deploy the RuleApp archive to the new Rule Execution Server by running the JRules V7.1 res-deploy Ant task." ], [ "4o", "Option 2: Using the Rule Execution Server management console * From the Rule Execution Server V6.7 console, click the Server Info tab and click Backup RuleApps to back up all the deployed RuleApps." ], [ "4p", "A JAR archive file containing all the RuleApps is generated." ], [ "4q", " * Install and configure Rule Execution Server V7.1 according to the installation documentation [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.install.doc/Content/Business_Rules/Documentation/_pubskel/JRules_Application_Servers/ps_Installing_JRules_IC.html] on your server and using the new database schema." ], [ "4r", " * Access the Rule Execution Server V7.1 console, click the Server Info tab and click Restore RuleApps to restore the RuleApp." ], [ "4s", "If you are migrating from V7.1 to V7.5/V8.X, no ruleApp migration is needed, you can reuse the database." ], [ "4t", "However, if you want to use the new managed XOM feature introduced in V7.5, you need to extend the database to include the XOM repository." ], [ "4u", "You will do so either :" ], [ "4v", " * through theInstallation Settings Wizard that you will be prompted when accessing the new Rule Execution Server console," ], [ "4w", " * or by running thexomrepository_<DatabaseName>.sqlscript found in directory <ODM_75/8X_installDir>/executionserver/databases on the existing database schema." ], [ "4x", "For more information on the managed XOM feature, see section Decision Server Rules V7.5 > Managing business rule execution in Rule Execution Server Deploying Java XOMs [http://publib.boulder.ibm.com/infocenter/dmanager/v7r5/topic/com.ibm.dserver.res/Content/Business_Rules/_pubskel/Infocenter_Primary/ps_DS_Rule_Execution_Server1500.html] of the documentation.\" RELATED INFORMATION" ], [ "4y", "#Migrating between JRules/WODM versions [http://www.ibm.com/support/docview.wss?uid=swg21589725]" ], [ "4z", "Migrating a Rule Project to JRules v7.0 and v7.1 [http://www.ibm.com/support/docview.wss?uid=swg21591800]" ], [ "4aa", "Migrating to Rule Team Server v7.0 and v7.1 [http://www.ibm.com/support/docview.wss?uid=swg21591798]" ], [ "4ab", "Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Decision Server Maintenance Platform Independent 7.5 All Editions" ] ]

[ "4b", "4c", "4d", "4e", "4f", "4g", "4h", "4i", "4j", "4k", "4l", "4m", "4n", "4p", "4q" ]

[ "seed 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", "guardium-open-mic WEBCAST\n\nABSTRACT\n IBM Security Guardium Support will host an Open Mic on Tuesday 04 April 2017, introducing a new prototype dashboard that can be used to provide Guardium Administrators with a quick visual check for various spikes on the Appliance over the last Month. \n\nCONTENT\n\n\n\nMany customers suffer with Guardium Appliances filling up and often remedial action is only taken once the system has become full and Technical Support is engaged. This Open Mic will introduce a prototype dashboard that can be used to provide Guardium Administrators with a quick visual check for various spikes on the Appliance over the last Month. Along with the usual Alerts, the dashboard can be used to proactively fix increased DB Usage and System Usage problems before the system fills.\n\nThe Open Mic will allow for feedback on the concept as well as discussion of what other reports / tools are used by customers to monitor and react to the Appliance space filling.\n\nThe webcast is provided by IBM Security Guardium Technical Support. Our goal is to provide insight and to teach on-going sessions that help both users and administrators understand, maintain, troubleshoot, and resolve issues with their IBM Security products. Throughout the event, attendees will be encouraged to comment or ask questions in the Q&A Panel within the WebEx conference. Join us for this interactive, educational, and lively session. \n.\n\n\n\nWeb conference \nTopic: Introducing a new Guardium \"Data Distributions Dashboard\" \nDate: Tuesday, 04 April, 2017 \nTime: 11:00 AM Eastern US time for 60 minutes \n\n\nJoin the web conference to view the presentation, hear audio, and participate in group web chat: \nhttps://ibmsecuritysupport.webex.com/ibmsecuritysupport/onstage/g.php?MTID=e2ecc6750b5fa5803ec987da4b4a7c4eb [https://ibmsecuritysupport.webex.com/ibmsecuritysupport/onstage/g.php?MTID=e2ecc6750b5fa5803ec987da4b4a7c4eb] \nWebEx conference ID: 665 939 665 \n\nPlease be aware that if you connect to the audio using your computer and you wish to ask questions by voice, a computer microphone is required. Click here for more information on how the WebEx conferencing works: http://www-01.ibm.com/support/docview.wss?uid=swg27048875 [http://www-01.ibm.com/support/docview.wss?uid=swg27048875] \n\n\n\nAdd to calendar \nDataDistributionDashboard0404.ics [/support/docview.wss?uid=swg27049532&aid=2]DataDistributionDashboard0404.ics [/support/docview.wss?uid=swg27049532&aid=1] \n\nBy participating in this call, you give your irrevocable consent to IBM to record any statements that you may make during the call, as well as to IBM's use of such recording in any and all media, including for video postings on YouTube. If you object, please do not connect to this call. \n\n\n\nPresentation \nOpenMic_Guardium_Dist_Dashboard.pdf [/support/docview.wss?uid=swg27049532&aid=4]OpenMic_Guardium_Dist_Dashboard.pdf [/support/docview.wss?uid=swg27049532&aid=3] \n\nRelated technote: \nIBM Guardium Distributions Dashboard and Reports - Analyse spikes in database and system space usage on a Guardium Appliance [http://www.ibm.com/support/docview.wss?uid=swg22001191] \n\n( http://www.ibm.com/support/docview.wss?uid=swg22001191 [http://www.ibm.com/support/docview.wss?uid=swg22001191] ) \n\n\n\nReplay A recording of the session will be available on the IBM Security Support You Tube channel [https://www.youtube.com/playlist?list=PLFip581NcL2UkJI2LYOTmCKZ3tAtWMFGG] \n\n\n\nHow to ask questions Post your question at the bottom of this document and it will be answered in the dW Answers forum! \n\n\n\nAbout Open Mic Webcasts IBM Security Systems Support wants to help you take full advantage of your products. Join us for our Open Mic Webcast series as technical experts share their knowledge and answer your questions. These webcasts are designed to address specific topics and provide an in-depth and focused technical exchange in a convenient online webcast format. \n\n\nVisit the Support technical exchanges for Security Systems [https://www.ibm.com/support/entry/portal/scheduled_tech_exchanges/ibm_security/ibm_security_support_(general)?productContext=-551864534] page to see lists of all scheduled and past Open Mic events \n[https://www-947.ibm.com/support/entry/myportal/scheduled_tech_exchanges/security_systems/security_systems_support_%28general%29?productContext=-1089885148] \nTo be on the mailing list that gets notified about Security Support's Open Mic webcasts, Send an e-mail to [email protected] [[email protected]?subject=ste%20subscribe%20InfraSec] with the subject line: \n\nste subscribe guardium \n\nWe welcome you to follow us on Twitter [http://bit.ly/1jZ80d3] @AskIBMSecurity [http://bit.ly/1jZ80d3]. \n\n\n\nORIGINAL PUBLICATION DATE\n 2017/3/10", "ISS_OPEN_MIC; STEwebcastDocument; NRT WEBCASTS\n\nABSTRACT\nThe Development team explained what is included in V6.0.0.20 and V7.0.1.10 of IBM Security Identity Manager (ISIM) released in July, 2018.\n\nCONTENT\nIBM Security Identity Manager (ISIM) developers covered the new enhancements and serviceability items, as well as common customer pain points for which solutions are being provided in the new releases of 6.0.0.20 and 7.0.1.10.\n\nHow to ask questions \nPost your question at the bottom of this document and it will be answered in the dW Answers forum [https://developer.ibm.com/answers/topics/isim.html].\n\n\nAudio Replay \nA recording of the session is available on the IBM Security Support YouTube channel [https://www.youtube.com/user/IBMSecuritySupport] athttps://youtu.be/FXTMCHfVvWk [https://youtu.be/FXTMCHfVvWk] and as a course in the IBM Security Learning Academy [https://www.securitylearningacademy.com] at https://www.securitylearningacademy.com/course/view.php?id=3205 [https://www.securitylearningacademy.com/course/view.php?id=3205] \n\n\nAbout Open Mic Webcasts \nIBM Security Support wants to help you take full advantage of your products. Join us for our Open Mic Webcast series as technical experts share their knowledge and answer your questions. These webcasts are designed to address specific topics and provide an in-depth and focused technical exchange in a convenient online webcast format.\nVisit the Support technical exchanges for IBM Security page to see lists of all scheduled and past Open Mic events.\n\nGet notified of future Open Mic sessions by subscribing to your product's \"Webcasts\" document type at My Notifications [http://www-01.ibm.com/software/support/einfo.html].\nWe welcome you to follow us on Twitter @AskIBMSecurity. [https://twitter.com/askibmsecurity]\n\nPRESENTATION\nThe four sections of the presentation are combined, and attached here.\n\nISIM%206.0%20FP20-7.0.1%20FP10.pdf [https://www-prd-trops.events.ibm.com/sites/default/files/inline-files/ISIM%206.0%20FP20-7.0.1%20FP10.pdf]\n\nAUDIO\nClick here for more information on how the WebEx conferencing works: http://www.ibm.com/support/docview.wss?uid=swg27048875 [http://www.ibm.com/support/docview.wss?uid=swg27048875]\n\nCOPYRIGHT DATE\n2018\n\nORIGINAL PUBLICATION DATE\n2018-07-12", "appsec-open-mic; ISS_OPEN_MIC; STEwebcastDocument WEBCAST\n\nABSTRACT\n Lost sources have a negative impact on scan coverage. AppScan Source does not directly classify lost sources in the same way as it does with lost sinks. Welooked at how to discover lost sources by using informational findings as well as the sometimes cryptic \"Scan Coverage Findings.\" Understanding and resolving lost sources will offer a big return, in that it dramatically improves the quality of findings and the scan coverage. \n\nCONTENT\nMembers of the Application Security Support and Development teams shared information on lost sources. The presentation by lead SAST researcher Stephen Teilhet included: \n\n1. What are lost sources and how to identify them \n2. How to define lost sources to improve scan coverage \n\nAfter the presentation, we opened the phone line to take questions from the audience. Throughout the event, attendees asked questions in the IBM SmartCloud Meeting Web chat. It was an interesting and educational session. \n\n\n * Topic: Demystifying lost sources in AppScan Source \n * Date: Tuesday, 14 April 2015 \n * Time: 11:00 AM EDT (15:00 UTC/GMT, UTC-4 hours)\n\n\nPresentation OpenMic_AppScanSource-LostSources_2015-04-14.pdf [/support/docview.wss?uid=swg27045364&aid=2]OpenMic_AppScanSource-LostSources_2015-04-14.pdf [/support/docview.wss?uid=swg27045364&aid=1] \n\n\nAudio Replay The recording of the session is available on the IBM Security Support You Tube channel [https://www.youtube.com/IBMSecuritySupport]: \nhttps://www.youtube.com/watch?v=vXFRB37yTsE [https://www.youtube.com/watch?v=vXFRB37yTsE] \n\n\n\nHow to ask questions on the topic We set aside a post in the AppScan Source Customer Forum on IBM developerWorks for you to ask questions about lost sources in AppScan Source. \nForum: [https://www.ibm.com/developerworks/community/forums/html/topic?id=ad49ee48-107b-4130-bba5-c3b9f469b56f] http://bit.ly/IBMopenmicAppScanSrce04142015forum [http://bit.ly/IBMopenmicAppScanSrce04142015forum] \n\n\nAbout Open Mic Webcasts IBM Security Systems Support wants to help you take full advantage of your products. Join us for our Open Mic Webcast series as technical experts share their knowledge and answer your questions. These webcasts are designed to address specific topics and provide an in-depth and focused technical exchange in a convenient online webcast format. Our goal of open mics is to provide insight on how your solution works and to teach on-going sessions that help both users and administrators understand, maintain, troubleshoot, and resolve issues. \n\nVisit the Support technical exchanges for Security Systems [https://www-947.ibm.com/support/entry/myportal/scheduled_tech_exchanges/security_systems/security_systems_support_%28general%29?productContext=-1089885148] page to see lists of all scheduled and past Open Mic events \n[https://www-947.ibm.com/support/entry/myportal/scheduled_tech_exchanges/security_systems/security_systems_support_%28general%29?productContext=-1089885148]To be notified about Security Support's Open Mic webcasts, follow us on Twitter [http://bit.ly/1jZ80d3] @AskIBMSecurity [http://bit.ly/1jZ80d3].", "ISS_OPEN_MIC OPEN_MIC; STEwebcastDocument; guardium-open-mic; guardium-open-mic WEBCAST\n\nABSTRACT\n Carolina Leme from Guardium Technical Support discusses Guardium user management in this Open Mic from Thursday May 31st, 2018. \n\nCONTENT\nThis Open Mic discusses user management in the Guardium environment (accessmgr, cli, gui, root), and details:\n\n\n * What to keep How to create users How to unlock How to reset \n\n\n\nReplay \nA recording of the session is available on the Security YouTube channel. [https://youtu.be/rpq4-hdKZ_E] \n\n\n\nPresentation \nGuardium User Management.pdf [/support/docview.wss?uid=swg27051124&aid=2]Guardium User Management.pdf [/support/docview.wss?uid=swg27051124&aid=1] \n\n\nHow to ask questions Post your question at the bottom of this document and it will be answered in the dW Answers forum! \n\n\n\nAbout Open Mic Webcasts IBM Security Systems Support wants to help you take full advantage of your products. Join us for our Open Mic Webcast series as technical experts share their knowledge and answer your questions. These webcasts are designed to address specific topics and provide an in-depth and focused technical exchange in a convenient online webcast format. \n\n\nTo be on the mailing list that gets notified about Security Support's Open Mic webcasts, Send an e-mail to [email protected] [[email protected]?subject=ste%20subscribe%20InfraSec] with the subject line: \n\nste subscribe guardium \n\nWe welcome you to follow us on Twitter [http://bit.ly/1jZ80d3] @AskIBMSecurity [http://bit.ly/1jZ80d3]. \n\n\n\nORIGINAL PUBLICATION DATE\n 2018/5/16" ]

[ [ "0a", "seed lost; idsgendirksf; Encryption Seed Value; key stash file TECHNOTE (TROUBLESHOOTING)" ], [ "0b", "THIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S): English PROBLEM(ABSTRACT)" ], [ "0c", " 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." ], [ "0d", "RESOLVING THE PROBLEM" ], [ "0e", "There is NO way to recover the seed value used during the instance creation if it has been lost." ], [ "0f", "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." ], [ "0g", "These utilities can be supplied with the new encryption seed and the salt value of the new instance." ], [ "0h", "Thus the data would be preserved(alongwith the passwords) on this new instance." ], [ "0i", "Here are the steps to follow: 1." ], [ "0j", "Set up a new instance says \"newinst\"." ], [ "0k", "$> idsicrt -I newinst -e thisismyencryptionseed -l (/home/newinst) -n" ], [ "0l", "$> idscfgdb -I newinst -w ldap -a newinst -t newinst -l (/home/newinst) -n" ], [ "0m", "$> idscfgsuf -s \"o=ibm,c=us\" -I newinst -n" ], [ "0n", "$> idsdnpw -u cn=root -p root -I newinst -n 2." ], [ "0o", "Note the encryption seed - \"thisismyencryptionseed\"." ], [ "0p", "Let us call this new_encryptionseed 3." ], [ "0q", "Once this new instance is setup note down the salt value generated by the new server instance by searching for \"cn=crypto,cn=localhost\"." ], [ "0r", "$> ldapsearch -D <administrator DN> -w <administrator password> -b \"cn=crypto,cn=localhost\" -s base objectclass=* ibm-slapdCryptoSalt" ], [ "0s", "Let us call this value: new_saltvalue 4." ], [ "0t", "Lets assume that the instance name with the forgotten encryption seed is \"oldinst\" 5." ], [ "0u", "Use the db2ldif utility on the instance with the forgotten encryptionseed, oldinst with the following options -" ], [ "0v", "$> db2ldif -o outputfile -I oldinst -k new_encryptionseed -t new_saltvalue 6." ], [ "0w", "Once this step is successfully completed the entire data from \"oldinst\" would be dumped in outputfile. 7." ], [ "0x", "Use the utilities like ldif2db to re-load all the data into the new server instance. HISTORICAL NUMBER" ] ]

[ "0c", "0e", "0f", "0g", "0h", "0j", "0o", "0p", "0q", "0r", "0s", "0t", "0u", "0v", "0w", "0x" ]

[ " SECURITY BULLETIN\n\nSUMMARY\n IBM Integration BusおよびWebSphere Message Brokerは、インストール時にオブジェクトに対して誤った権限を設定し、ローカルの攻撃者が特定のファイルを操作する可能性があります。\n\n\n\nVULNERABILITY DETAILS\n脆弱性の詳細：\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\n影響のある製品・バージョン： \n\n次の製品に影響があります。 \n\n * IBM Integration Bus V10 \n * IBM Integration Bus V9 \n * WebSphere Message Broker V8\n\nREMEDIATION/FIXES\n修正策： \n\n\n\n製品 VRMF APAR 修正 IBM Integration Bus V10 IT14845 APAR IT14845 は 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] IBM Integration Bus V9 IT14845 APAR IT14845 は Fix Pack 9.0.0.6 に含まれます。\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24042598 [https://www-304.ibm.com/support/docview.wss?uid=swg24042598] WebSphere Message Broker V8 IT14845 APAR IT14845 は 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サポートの終了した製品を使用されている場合、サポートされているバージョンへアップグレードされることを推奨いたします。 WORKAROUNDS AND MITIGATIONS\n回避策/軽減策：\n現行のフィックスパックのインストールで問題を軽減するには、次のコマンドを実行します。\n\nfind <IIB install dir>/isadc -type d -exec chmod 755 {} \\;\nfind <IIB install dir>/isadc -type f -exec chmod 644 {} \\;\nfind <IIB install dir>/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\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. 参照情報：\n[IBMサイト]\nこの文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。\nSecurity Bulletin: IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object ( CVE-2016-0394 ) [http://www.ibm.com/support/docview.wss?uid=swg21985013]\n\n公開済みのフィックスパックについては、以下のサイトよりご利用いただけます。\nRecommended fixes for IBM Integration Bus and WebSphere Message Broker [http://www-01.ibm.com/support/docview.wss?uid=swg27006041]\n\nフィックス・パックの公開予定については、以下のサイトよりご確認いただけます。\nIBM Integration Bus and WebSphere Message Broker planned maintenance release dates [http://www-01.ibm.com/support/docview.wss?uid=swg27006308]\n\n[CVSS情報]\n独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html]\nJVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html]\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. \n関連情報： \n. \n【お問合せ先】 \n技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。 \nIBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html] \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 An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21985013 ]\n\n\n \n\n\nクロスリファレンス情報 区分 製品 コンポーネント プラットフォーム バージョン エディション Business Integration WebSphere Message Broker 8.0", "WMB IIB SECURITY BULLETIN\n\nSUMMARY\n OpenSSL vulnerabilities were disclosed on September 22, September 26, and November 10, 2016 by the OpenSSL Project. The DataDirect ODBC Drivers used by WebSphere Message Broker and IBM Integration Bus have addressed the applicable CVEs. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-6303 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6303]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an integer overflow in the MDC2_Update function. By using unknown attack vectors, a remote attacker could exploit this vulnerability to trigger an out-of-bounds write and cause the application to crash.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117023 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117023] 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-2182 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2182]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an out-of-bounds write in the TS_OBJ_print_bio function in crypto/bn/bn_print.c. A remote attacker could exploit this vulnerability using a specially crafted value to cause the application to crash.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116342 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116342] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L) \n\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\nCVEID: CVE-2016-6306 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6306]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by missing message length checks when parsing certificates. A remote authenticated attacker could exploit this vulnerability to trigger an out-of-bounds read and cause a denial of service.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117112 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117112] 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\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-2016-7055 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7055]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an error in a Broadwell-specific Montgomery multiplication procedure. By sending specially crafted data, a remote attacker could exploit this vulnerability to trigger errors in public-key operations in configurations where multiple remote clients select an affected EC algorithm and cause a denial of service.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118748 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118748] 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, V9 \n\nWebSphere Message Broker V8\n\nREMEDIATION/FIXES\n\nFor users of ODBC SSL using the DataDirect drivers:\n\n\n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus\n\n\nV10\n\nIT17992 The APAR is available in fix pack 10.0.0.8\nhttps://www.ibm.com/support/docview.wss?uid=swg24043443 [https://www.ibm.com/support/docview.wss?uid=swg24043443] IBM Integration Bus\n\n\nV9\n\nIT17992 The APAR is available in fix pack 9.0.0.7 [https://www-304.ibm.com/support/docview.wss?uid=swg24042598]\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043227 [http://www-01.ibm.com/support/docview.wss?uid=swg24043227] WebSphere Message Broker V8 IT17992 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=IT17992 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT17992] \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 20-Mar-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", "WMB IIB SECURITY BULLETIN\n\nSUMMARY\n The Windows graphical user interface installer (setup.exe) used by WebSphere Message Broker, IBM Integration Bus, IBM Integration Bus Healthcare Pack, IBM Integration Bus Manufacturing Pack, and IBM Integration Bus Retail Pack, is susceptible to a DLL-planting vulnerability, where a malicious DLL that is present in the Windows search path could be loaded by the operating system in place of the genuine file.\n\n\n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-4560 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4560]\nDESCRIPTION: Flexera InstallAnywhere could allow a local attacker to gain elevated privileges on the system, caused by an untrusted search path. An attacker could exploit this vulnerability, by using a Trojan horse DLL in the current working directory of a setup-launcher executable file, to gain elevated privileges on the system.\nCVSS Base Score: 7.8\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113016 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113016] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nThe vulnerability affects the executable (.exe file extension) installers and fix packs: \n\nIBM Integration Bus V9 for Windows (V9.0.0.0 -> V9.0.0.5) \n\nWebSphere Message Broker V8 for Windows (V8.0.0.0 -> V8.0.0.7) \n\nIBM Integration Bus Healthcare Pack V3 for Windows (V3.0.0.0 -> V3.0.0.1) \n\nWebSphere Message Broker Connectivity Pack for Healthcare V8 for Windows (V8.0.0.0) \n\nWebSphere Message Broker Connectivity Pack for Healthcare V7 for Windows (V7.0.0.0 -> V7.0.0.2) \n\nIBM Integration Bus Manufacturing Pack V1 for Windows (V1.0.0.0 -> V1.0.0.1) \n\nIBM Integration Bus Retail Pack V1 for Windows (V1.0.0.0)\n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus Manufacturing Pack V1 IT15616 The APAR is available in Fix Pack 1.0.0.2\n[http://www-01.ibm.com/support/docview.wss?uid=swg21987596]\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21987596 [http://www-01.ibm.com/support/docview.wss?uid=swg21987596] IBM Integration Bus V9 IT15601 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 IT15601 The APAR is available in Fix Pack 8.0.0.8\n[https://www-304.ibm.com/support/docview.wss?uid=swg24042925]\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24042925 [https://www-304.ibm.com/support/docview.wss?uid=swg24042925] IBM Integration Bus Retail Pack V1 IT15611 IBM Integration Bus Retail Pack 1.0.0.0 has been repackaged to no longer be susceptible to the described vulnerability. The updated package is available via IBM Passport Advantage. \nThe following link directs you to the Passport Advantage Online web site. Passport Advantage is a secure web site that requires an account ID and password. http://www.ibm.com/software/how-to-buy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/how-to-buy/passportadvantage/pao_customers.htm] \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\n\nWORKAROUNDS AND MITIGATIONS\nComplete these steps to work around the InstallAnywhere vulnerability.\n\nTo avoid the untrusted search path vulnerability, where users could gain increased privileges, complete the following steps:\n1) Create a new, empty, secure directory in a temporary location.\nThe directory must not exist previously and only the administrator should have write access to it.\n2) Either copy or move the installer executable, or unpack the installation zip file into the new, empty folder created in Step 1.\n3) Ensure that there are no DLL files in this directory.\n4) Launch the installer executable from its new location.\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 22 -Jul-2016 - Original version Published\n26-Jul-2016 - Rectified truncation of Title text\n17 Aug 2017 - Added IBM Integration Bus Manufacturing Pack fix link\n28 Nov 2016- Added IBM Integration Bus Retail pack fix 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\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21988825]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Windows 8.0 Business Integration IBM Integration Bus Healthcare Pack Windows 3.0 Business Integration IBM Integration Bus Manufacturing Pack Windows 1.0 Business Integration IBM Integration Bus Retail Pack Windows 1.0 \nPRODUCT ALIAS/SYNONYM\n WMB IIB", " 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 - CVE-2016-2119, CVE-2016-5841 and CVE-2016-5842 \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-2119, CVE-2016-5841, and CVE-2016-5842. \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", "WMB IIB SECURITY BULLETIN\n\nSUMMARY\n IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object on unix platforms, which exposes it to an unintended actor. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-0394 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0394]\nDESCRIPTION: IBM Integration Bus and WebSphere Message broker set incorrect permissions for an object, which could allow a local attacker to manipulate certain files. \nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112643 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112643] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Integration Bus V9 \n\nWebSphere Message Broker V8\n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus V9 IT14845 The APAR is available in Fix Pack 9.0.0.6 https://www-304.ibm.com/support/docview.wss?uid=swg24042598 [https://www-304.ibm.com/support/docview.wss?uid=swg24042598]\n\nWebSphere Message Broker V8 IT14845 The APAR is available in Fix Pack 8.0.0.8\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24042925 [https://www-304.ibm.com/support/docview.wss?uid=swg24042925] \nFor unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product. \n\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : \nhttp://www.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n\nWORKAROUNDS AND MITIGATIONS\nTo mitigate the problem with a current V8 or V9 fix pack installation on Unix platforms, you can run the following commands: \n\nfind <IIB install dir>/isadc -type d -exec chmod 755 {} \\;\nfind <IIB install dir>/isadc -type f -exec chmod 644 {} \\;\nfind <IIB install dir>/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" ]

[ [ "0a", " SECURITY BULLETIN SUMMARY" ], [ "0b", " IBM Integration BusおよびWebSphere Message Brokerは、インストール時にオブジェクトに対して誤った権限を設定し、ローカルの攻撃者が特定のファイルを操作する可能性があります。 VULNERABILITY DETAILS 脆弱性の詳細：" ], [ "0c", "CVEID: CVE-2016-0394 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0394]" ], [ "0d", "DESCRIPTION: IBM Integration Bus and WebSphere Message broker set incorrect permissions for an object, which could allow a local attacker to manipulate certain files." ], [ "0e", "CVSS Base Score: 4" ], [ "0f", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112643 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112643] for the current score" ], [ "0g", "CVSS Environmental Score*: Undefined" ], [ "0h", "CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)" ], [ "0i", "AFFECTED PRODUCTS AND VERSIONS 影響のある製品・バージョン： 次の製品に影響があります。" ], [ "0j", " * IBM Integration Bus V10" ], [ "0k", " * IBM Integration Bus V9" ], [ "0l", " * WebSphere Message Broker V8 REMEDIATION/FIXES 修正策：" ], [ "0m", "製品 VRMF APAR 修正 IBM Integration Bus V10 IT14845 APAR IT14845 は Fix Pack 10.0.0.7 に含まれます。" ], [ "0n", "https://www-304.ibm.com/support/docview.wss?uid=swg24043068 [https://www-304.ibm.com/support/docview.wss?uid=swg24043068] IBM Integration Bus V9 IT14845 APAR IT14845 は Fix Pack 9.0.0.6 に含まれます。" ], [ "0o", "https://www-304.ibm.com/support/docview.wss?uid=swg24042598 [https://www-304.ibm.com/support/docview.wss?uid=swg24042598] WebSphere Message Broker V8 IT14845 APAR IT14845 は Fix Pack 8.0.0.8 に含まれます。 https://www-304.ibm.com/support/docview.wss?uid=swg24042925 [https://www-304.ibm.com/support/docview.wss?uid=swg24042925]" ], [ "0p", "サポートの終了した製品を使用されている場合、サポートされているバージョンへアップグレードされることを推奨いたします。 WORKAROUNDS AND MITIGATIONS 回避策/軽減策： 現行のフィックスパックのインストールで問題を軽減するには、次のコマンドを実行します。" ], [ "0q", "find <IIB install dir>/isadc -type d -exec chmod 755 {} \\;" ], [ "0r", "find <IIB install dir>/isadc -type f -exec chmod 644 {} \\;" ], [ "0s", "find <IIB install dir>/isadc -type f -name *.sh -print -exec chmod 755" ], [ "0t", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS" ], [ "0u", " Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. REFERENCES" ], [ "0v", "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]" ], [ "0w", "On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] . 参照情報： [IBMサイト]" ], [ "0x", "この文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。" ], [ "0y", "Security Bulletin: IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object ( CVE-2016-0394 ) [http://www.ibm.com/support/docview.wss?uid=swg21985013] 公開済みのフィックスパックについては、以下のサイトよりご利用いただけます。" ], [ "0z", "Recommended fixes for IBM Integration Bus and WebSphere Message Broker [http://www-01.ibm.com/support/docview.wss?uid=swg27006041] フィックス・パックの公開予定については、以下のサイトよりご確認いただけます。" ], [ "0aa", "IBM Integration Bus and WebSphere Message Broker planned maintenance release dates [http://www-01.ibm.com/support/docview.wss?uid=swg27006308] [CVSS情報]" ], [ "0ab", "独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html]" ], [ "0ac", "JVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html] RELATED INFORMATION" ], [ "0ad", "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]" ], [ "0ae", "IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] . 関連情報： . 【お問合せ先】 技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。" ], [ "0af", "IBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html]" ], [ "0ag", "*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score." ], [ "0ah", "Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. DISCLAIMER" ], [ "0ai", "According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\"" ], [ "0aj", "IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE." ], [ "0ak", "CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. 関連情報" ], [ "0al", " An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21985013 ]" ], [ "0am", "クロスリファレンス情報 区分 製品 コンポーネント プラットフォーム バージョン エディション Business Integration WebSphere Message Broker 8.0" ] ]

[ "0b", "0d", "0i", "0j", "0k", "0l", "0m", "0n", "0o", "0p", "0q", "0r", "0s", "0y", "0z", "4b", "4c", "4i", "4j", "4k", "4l", "4m", "4p", "4q", "4r", "4s", "4t" ]

[ " SECURITY BULLETIN\n\nSUMMARY\n IBM Integration BusおよびWebSphere Message Brokerは、インストール時にオブジェクトに対して誤った権限を設定し、ローカルの攻撃者が特定のファイルを操作する可能性があります。\n\n\n\nVULNERABILITY DETAILS\n脆弱性の詳細：\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\n影響のある製品・バージョン： \n\n次の製品に影響があります。 \n\n * IBM Integration Bus V10 \n * IBM Integration Bus V9 \n * WebSphere Message Broker V8\n\nREMEDIATION/FIXES\n修正策： \n\n\n\n製品 VRMF APAR 修正 IBM Integration Bus V10 IT14845 APAR IT14845 は 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] IBM Integration Bus V9 IT14845 APAR IT14845 は Fix Pack 9.0.0.6 に含まれます。\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24042598 [https://www-304.ibm.com/support/docview.wss?uid=swg24042598] WebSphere Message Broker V8 IT14845 APAR IT14845 は 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サポートの終了した製品を使用されている場合、サポートされているバージョンへアップグレードされることを推奨いたします。 WORKAROUNDS AND MITIGATIONS\n回避策/軽減策：\n現行のフィックスパックのインストールで問題を軽減するには、次のコマンドを実行します。\n\nfind <IIB install dir>/isadc -type d -exec chmod 755 {} \\;\nfind <IIB install dir>/isadc -type f -exec chmod 644 {} \\;\nfind <IIB install dir>/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\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. 参照情報：\n[IBMサイト]\nこの文書は、米国 IBM 社の資料を翻訳した参考文書です。翻訳元の文書は、以下のリンクよりご参照ください。\nSecurity Bulletin: IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object ( CVE-2016-0394 ) [http://www.ibm.com/support/docview.wss?uid=swg21985013]\n\n公開済みのフィックスパックについては、以下のサイトよりご利用いただけます。\nRecommended fixes for IBM Integration Bus and WebSphere Message Broker [http://www-01.ibm.com/support/docview.wss?uid=swg27006041]\n\nフィックス・パックの公開予定については、以下のサイトよりご確認いただけます。\nIBM Integration Bus and WebSphere Message Broker planned maintenance release dates [http://www-01.ibm.com/support/docview.wss?uid=swg27006308]\n\n[CVSS情報]\n独立行政法人 情報処理推進機構: 共通脆弱性評価システムCVSS概説 [http://www.ipa.go.jp/security/vuln/CVSS.html]\nJVN iPedia: CVSS計算ソフトウェア日本語版 [http://jvndb.jvn.jp/cvss/ja.html]\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. \n関連情報： \n. \n【お問合せ先】 \n技術的な内容に関して、サービス契約のあるお客様はIBMサービス・ラインにお問い合わせください。 \nIBM サービス・ライン [http://www.ibm.com/jp/news/20070420001.html] \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 An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21985013 ]\n\n\n \n\n\nクロスリファレンス情報 区分 製品 コンポーネント プラットフォーム バージョン エディション Business Integration WebSphere Message Broker 8.0", "WMB IIB SECURITY BULLETIN\n\nSUMMARY\n OpenSSL vulnerabilities were disclosed on September 22, September 26, and November 10, 2016 by the OpenSSL Project. The DataDirect ODBC Drivers used by WebSphere Message Broker and IBM Integration Bus have addressed the applicable CVEs. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-6303 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6303]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an integer overflow in the MDC2_Update function. By using unknown attack vectors, a remote attacker could exploit this vulnerability to trigger an out-of-bounds write and cause the application to crash.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117023 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117023] 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-2182 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2182]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an out-of-bounds write in the TS_OBJ_print_bio function in crypto/bn/bn_print.c. A remote attacker could exploit this vulnerability using a specially crafted value to cause the application to crash.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116342 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116342] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L) \n\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\nCVEID: CVE-2016-6306 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6306]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by missing message length checks when parsing certificates. A remote authenticated attacker could exploit this vulnerability to trigger an out-of-bounds read and cause a denial of service.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117112 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117112] 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\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-2016-7055 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7055]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an error in a Broadwell-specific Montgomery multiplication procedure. By sending specially crafted data, a remote attacker could exploit this vulnerability to trigger errors in public-key operations in configurations where multiple remote clients select an affected EC algorithm and cause a denial of service.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118748 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118748] 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, V9 \n\nWebSphere Message Broker V8\n\nREMEDIATION/FIXES\n\nFor users of ODBC SSL using the DataDirect drivers:\n\n\n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus\n\n\nV10\n\nIT17992 The APAR is available in fix pack 10.0.0.8\nhttps://www.ibm.com/support/docview.wss?uid=swg24043443 [https://www.ibm.com/support/docview.wss?uid=swg24043443] IBM Integration Bus\n\n\nV9\n\nIT17992 The APAR is available in fix pack 9.0.0.7 [https://www-304.ibm.com/support/docview.wss?uid=swg24042598]\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043227 [http://www-01.ibm.com/support/docview.wss?uid=swg24043227] WebSphere Message Broker V8 IT17992 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=IT17992 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT17992] \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 20-Mar-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", "WMB IIB SECURITY BULLETIN\n\nSUMMARY\n The Windows graphical user interface installer (setup.exe) used by WebSphere Message Broker, IBM Integration Bus, IBM Integration Bus Healthcare Pack, IBM Integration Bus Manufacturing Pack, and IBM Integration Bus Retail Pack, is susceptible to a DLL-planting vulnerability, where a malicious DLL that is present in the Windows search path could be loaded by the operating system in place of the genuine file.\n\n\n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-4560 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4560]\nDESCRIPTION: Flexera InstallAnywhere could allow a local attacker to gain elevated privileges on the system, caused by an untrusted search path. An attacker could exploit this vulnerability, by using a Trojan horse DLL in the current working directory of a setup-launcher executable file, to gain elevated privileges on the system.\nCVSS Base Score: 7.8\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113016 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113016] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nThe vulnerability affects the executable (.exe file extension) installers and fix packs: \n\nIBM Integration Bus V9 for Windows (V9.0.0.0 -> V9.0.0.5) \n\nWebSphere Message Broker V8 for Windows (V8.0.0.0 -> V8.0.0.7) \n\nIBM Integration Bus Healthcare Pack V3 for Windows (V3.0.0.0 -> V3.0.0.1) \n\nWebSphere Message Broker Connectivity Pack for Healthcare V8 for Windows (V8.0.0.0) \n\nWebSphere Message Broker Connectivity Pack for Healthcare V7 for Windows (V7.0.0.0 -> V7.0.0.2) \n\nIBM Integration Bus Manufacturing Pack V1 for Windows (V1.0.0.0 -> V1.0.0.1) \n\nIBM Integration Bus Retail Pack V1 for Windows (V1.0.0.0)\n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus Manufacturing Pack V1 IT15616 The APAR is available in Fix Pack 1.0.0.2\n[http://www-01.ibm.com/support/docview.wss?uid=swg21987596]\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21987596 [http://www-01.ibm.com/support/docview.wss?uid=swg21987596] IBM Integration Bus V9 IT15601 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 IT15601 The APAR is available in Fix Pack 8.0.0.8\n[https://www-304.ibm.com/support/docview.wss?uid=swg24042925]\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24042925 [https://www-304.ibm.com/support/docview.wss?uid=swg24042925] IBM Integration Bus Retail Pack V1 IT15611 IBM Integration Bus Retail Pack 1.0.0.0 has been repackaged to no longer be susceptible to the described vulnerability. The updated package is available via IBM Passport Advantage. \nThe following link directs you to the Passport Advantage Online web site. Passport Advantage is a secure web site that requires an account ID and password. http://www.ibm.com/software/how-to-buy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/how-to-buy/passportadvantage/pao_customers.htm] \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\n\nWORKAROUNDS AND MITIGATIONS\nComplete these steps to work around the InstallAnywhere vulnerability.\n\nTo avoid the untrusted search path vulnerability, where users could gain increased privileges, complete the following steps:\n1) Create a new, empty, secure directory in a temporary location.\nThe directory must not exist previously and only the administrator should have write access to it.\n2) Either copy or move the installer executable, or unpack the installation zip file into the new, empty folder created in Step 1.\n3) Ensure that there are no DLL files in this directory.\n4) Launch the installer executable from its new location.\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 22 -Jul-2016 - Original version Published\n26-Jul-2016 - Rectified truncation of Title text\n17 Aug 2017 - Added IBM Integration Bus Manufacturing Pack fix link\n28 Nov 2016- Added IBM Integration Bus Retail pack fix 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\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21988825]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Windows 8.0 Business Integration IBM Integration Bus Healthcare Pack Windows 3.0 Business Integration IBM Integration Bus Manufacturing Pack Windows 1.0 Business Integration IBM Integration Bus Retail Pack Windows 1.0 \nPRODUCT ALIAS/SYNONYM\n WMB IIB", " 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 - CVE-2016-2119, CVE-2016-5841 and CVE-2016-5842 \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-2119, CVE-2016-5841, and CVE-2016-5842. \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", "WMB IIB SECURITY BULLETIN\n\nSUMMARY\n IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object on unix platforms, which exposes it to an unintended actor. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-0394 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0394]\nDESCRIPTION: IBM Integration Bus and WebSphere Message broker set incorrect permissions for an object, which could allow a local attacker to manipulate certain files. \nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112643 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112643] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Integration Bus V9 \n\nWebSphere Message Broker V8\n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus V9 IT14845 The APAR is available in Fix Pack 9.0.0.6 https://www-304.ibm.com/support/docview.wss?uid=swg24042598 [https://www-304.ibm.com/support/docview.wss?uid=swg24042598]\n\nWebSphere Message Broker V8 IT14845 The APAR is available in Fix Pack 8.0.0.8\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24042925 [https://www-304.ibm.com/support/docview.wss?uid=swg24042925] \nFor unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product. \n\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : \nhttp://www.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n\nWORKAROUNDS AND MITIGATIONS\nTo mitigate the problem with a current V8 or V9 fix pack installation on Unix platforms, you can run the following commands: \n\nfind <IIB install dir>/isadc -type d -exec chmod 755 {} \\;\nfind <IIB install dir>/isadc -type f -exec chmod 644 {} \\;\nfind <IIB install dir>/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" ]

[ [ "4a", "WMB IIB SECURITY BULLETIN SUMMARY" ], [ "4b", " IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object on unix platforms, which exposes it to an unintended actor. VULNERABILITY DETAILS" ], [ "4c", "CVEID: CVE-2016-0394 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0394]" ], [ "4d", "DESCRIPTION: IBM Integration Bus and WebSphere Message broker set incorrect permissions for an object, which could allow a local attacker to manipulate certain files." ], [ "4e", "CVSS Base Score: 4" ], [ "4f", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112643 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112643] for the current score" ], [ "4g", "CVSS Environmental Score*: Undefined" ], [ "4h", "CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)" ], [ "4i", "AFFECTED PRODUCTS AND VERSIONS" ], [ "4j", "IBM Integration Bus V9" ], [ "4k", "WebSphere Message Broker V8 REMEDIATION/FIXES" ], [ "4l", "Product VRMF APAR Remediation/Fix IBM Integration Bus V9 IT14845 The APAR is available in Fix Pack 9.0.0.6 https://www-304.ibm.com/support/docview.wss?uid=swg24042598 [https://www-304.ibm.com/support/docview.wss?uid=swg24042598]" ], [ "4m", "WebSphere Message Broker V8 IT14845 The APAR is available in Fix Pack 8.0.0.8 https://www-304.ibm.com/support/docview.wss?uid=swg24042925 [https://www-304.ibm.com/support/docview.wss?uid=swg24042925]" ], [ "4n", "For unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product." ], [ "4o", "The planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : http://www.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006308]" ], [ "4p", "WORKAROUNDS AND MITIGATIONS" ], [ "4q", "To mitigate the problem with a current V8 or V9 fix pack installation on Unix platforms, you can run the following commands:" ], [ "4r", "find <IIB install dir>/isadc -type d -exec chmod 755 {} \\;" ], [ "4s", "find <IIB install dir>/isadc -type f -exec chmod 644 {} \\;" ], [ "4t", "find <IIB install dir>/isadc -type f -name *.sh -print -exec chmod 755" ], [ "4u", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS" ], [ "4v", " Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. IMPORTANT NOTE" ], [ "4w", " 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." ], [ "4x", "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]." ], [ "4y", "Security and integrity APARs and associated fixes will be posted to this portal." ], [ "4z", "IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. REFERENCES" ], [ "4aa", "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]" ], [ "4ab", "On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION" ], [ "4ac", "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]" ], [ "4ad", "IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] CHANGE HISTORY" ], [ "4ae", " 28-Nov-2016 - Original version Published" ], [ "4af", "04-Apr-2017 - Removed v10 (distributed) from affected list, text change to explicitly mention 'on unix platforms'" ], [ "4ag", "*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score." ], [ "4ah", "Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. DISCLAIMER" ], [ "4ai", "According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\"" ], [ "4aj", "IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE." ], [ "4ak", "CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. RELATED INFORMATION" ], [ "4al", " A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21995532]" ], [ "4am", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker 8.0 PRODUCT ALIAS/SYNONYM" ], [ "4an", " WMB IIB" ] ]

[ "0b", "0d", "0i", "0j", "0k", "0l", "0m", "0n", "0o", "0p", "0q", "0r", "0s", "0y", "0z", "4b", "4c", "4i", "4j", "4k", "4l", "4m", "4p", "4q", "4r", "4s", "4t" ]

[ " WHITE PAPER\n\nABSTRACT\n You can configure log4j to generate trace logs for both FileNet P8 Content Platform Engine and IBM Connections Waltz at the same time. \n\nCONTENT\nStarting with FileNet P8 version 5.2, IBM Connections Waltz comes bundled with FileNet P8 Content Platform Engine (CPE). If standard logging procedures are followed, the logs for both CPE and Waltz cannot be generated at the same time. \n\nThis white paper shows how to generate CPE and Waltz logs concurrently. It comes with an attached log4j.xml file, which you can use as a starting point. Screen shots are based on IBM® WebSphere® Application Server 7.0. \n\nConfiguration Steps\n\n1) Download the attached log4j.xml file and save it in the c:\\temp folder. The file contains log4j settings for both CPE and Waltz. \n\n2) On the WebSphere server that hosts the FileNet P8 Content Platform Engine, add the following JVM arguments:\n\n-DskipTLC=true -Dlog4j.configuration=file:/c:/temp/log4j.xml [file:///c:/temp/log4j.xml] \n\n[/support/docview.wss?uid=swg27040423&aid=1] [/support/docview.wss?uid=swg27040423&aid=1]\n\n3) Save the change and restart the WebSphere Application Server. The system is now ready to generate trace logs for CPE and Waltz concurrently.\n\nNote: Syntax-errors in log4j.xml will be logged to the SystemErr.log file of the WebSphere Server hosting FileNet.\n\nLog File Location \n\nWith the default settings in log4j.xml file, the following three logs are generated: \n· p8_server_error.log \n· p8_server_trace.log \n· waltz.sonata.trace.log\n\nThey are located in the following path: \n\napp_server_root_dir\\profiles\\AppSrv01\\logs\\\n\nFor example, here is the location on a Windows server:\n\nC:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\AppSrv01\\logs\\\n\nWith the default log4j settings, CPE trace log messages are in the p8_server_trace.log file, while Waltz trace messages are in the waltz.sonata.trace.log file.\n\nConfiguration Variations\n\nThe log4j in the XML file can be configured for the following purposes. \n\nTroubleshooting Functional Issues\n\nWith the default log4j settings, detailed trace messages are logged for security troubleshooting. For CPE, both EJB and Security sub-systems are enabled. To troubleshoot security-related issues use the log4j.xml file as-is, without modification. \n\n[/support/docview.wss?uid=swg27040423&aid=2] [/support/docview.wss?uid=swg27040423&aid=2]\n\nTroubleshooting Performance Issues \n\nTurn on timer flags to troubleshoot performance issues in directory service area. Turn off detail level for CPE’s Security sub-system. Otherwise, it will generate more directory service calls and add more performance overhead. \n\n[/support/docview.wss?uid=swg27040423&aid=3] [/support/docview.wss?uid=swg27040423&aid=3]\n\nLog CPE and Waltz Messages in the Same File\n\nBoth CPE and Waltz trace messages can be logged to the same file (p8_server_trace.log) by adding FileNetTraceRollingAppender to the root logger. \n\n[/support/docview.wss?uid=swg27040423&aid=4] [/support/docview.wss?uid=swg27040423&aid=4]\n\n\n\n\nlog4j.xml [/support/docview.wss?uid=swg27040423&aid=6]log4j.xml [/support/docview.wss?uid=swg27040423&aid=5]", " TECHNOTE (FAQ)\n\nQUESTION\n What data should you collect for problems with the IBM UrbanCode Deploy WebSphere Application Server – Deployment and WebSphere Application Server – Configure plugins? \n\nCAUSE\nThe IBM UrbanCode Deploy WebSphere Application Server – Deployment and WebSphere Application Server – Configure plugins store logs in different locations from other UrbanCode Deploy plugins, because they expose Actions from the Resource Tree, that can be triggered without executing an Application/Component process. Additionally, the level of logging can be increased in the Component steps of the WebSphere Application Server – Configure plugin, resulting in the creation of additional log files.\n\nANSWER\nDepending on the action you are performing, you can find diagnostic information in different locations. \n\nWebSphere Application Server – Deployment plugin\n\n\n * WebSphere (Cell) Discovery\n * If you executed the WebSphere (Cell) Discovery interactively, by adding an Agent to the Resource Tree, then the log can be found in:\n \n Resources > Agent Resource > History\n \n Configuration Task History > WebSphere Discovery > Actions > Output log\n \n [/support/docview.wss?uid=swg2C1000185&aid=1] [/support/docview.wss?uid=swg2C1000185&aid=1] \n * Alternatively, you could run this as a process, as follows:\n \n 1. Take the parent resource of the agent, and create a Resource Property called: \n \n websphere.profilePath\n \n that refers to the location of the WAS Profile and could be set to a value like: \n \n C:\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01 \n \n 2. Create a Generic process onto which you drop the step: \n \n Java > WebSphere > Deployment > WebSphere Discovery\n \n 3. Execute the step on the Agent Resource \n \n In this case, the diagnostic information is contained in the output of the Generic process step. \n \n Provide this file to support after clicking on Download All Logs.\n \n [/support/docview.wss?uid=swg2C1000185&aid=2] [/support/docview.wss?uid=swg2C1000185&aid=2]\n \n \n\n * WebSphere Topology Discovery\n * If you executed the WebSphere Topology Discovery from the menu:\n \n Actions > Configure using WebSphere Topology Discovery \n \n available on the discovered WebSphere Cell in the Resource Tree, then the log can be found in:\n \n Resources > WebSphere Cell Resource > History\n \n Configuration Task History > WebSphere Topology Discovery > Actions > Output log\n \n [/support/docview.wss?uid=swg2C1000185&aid=3] [/support/docview.wss?uid=swg2C1000185&aid=3]\n \n * Alternatively, you could have executed the WebSphere Configuration Discovery as a Generic process, following these steps:\n \n 1. Drop the step Configuration Discovery > Update from Live Configuration \n \n 2. In the parameter: Plugin Step, select WebSphere Topology Discovery from the drop down list. \n \n 3. Change the value of the Resource parameter from ${p:resource.parent.path} to ${p:resource.path} (this is required only if running as a Generic process, as opposed to a Component Process, since in a Component process the desired resource is the parent of the Component itself).\n \n In this case the diagnostic information is contained in the output of the Generic process.\n \n Provide this file to support after clicking on Download All Logs.\n \n \n\n\nWebSphere Application Server – Configure plugin \n\n \n\n * WebSphere Configuration Discovery\n \n Starting with v17 of the WAS Configure plugin, the execution of following menu of the Resource Tree:\n \n Actions > Configure using WebSphere Configuration Discovery \n \n is deprecated, in favor of the usage of the Component Step: \n \n Java > WebSphere > Configuration > WebSphere Configuration Discovery\n \n [/support/docview.wss?uid=swg2C1000185&amp;aid=4]\n \n Starting with v25 of the WAS - Configure plugin, after you drop this step on the canvas, you can augment the logging level by doing the following:\n \n Show hidden properties > Logging level > change from Info to Debug\n \n [/support/docview.wss?uid=swg2C1000185&aid=5] [/support/docview.wss?uid=swg2C1000185&aid=5]\n \n If the Logging Level is set to Debug/Trace, you will see additional icons for log files next to the output log: debug.log and redo.log.\n \n Provide the complete set of logs to IBM Support after clicking on Download All Logs.\n \n [/support/docview.wss?uid=swg2C1000185&aid=6] [/support/docview.wss?uid=swg2C1000185&aid=6]\n \n * WebSphere Configuration Apply\n \n The Component process step:\n \n Java > WebSphere > Configuration > WebSphere Configuration Apply \n \n has the same option for increasing the logging level. \n \n [/support/docview.wss?uid=swg2C1000185&aid=7] [/support/docview.wss?uid=swg2C1000185&aid=7]\n \n The files debugLog.txt and redoLog.txt can be found as described above.\n \n Provide these file to IBM Support after clicking on Download All Logs.\n \n \n * WebSphere Configuration Compare\n \n The Component process steps:\n \n Java > WebSphere > Configuration > WebSphere Configuration Compare \n \n Java > WebSphere > Configuration > WebSphere Get Compare Results \n \n have the same option for increasing the logging level and the same method for obtaining the resulting debugLog.txt and redoLog.txt, as described above.\n \n Provide these file to IBM Support after clicking on Download All Logs.", "mustgatherdocument; IBM Forms; IBM Forms API; IBM Forms Server; troubleshooting; mustgather; support; documentation; wpf; wpf.pel; pel file; logs; log files; problem management record; PMR TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nThis document will aid in problem determination and save time resolving Problem Management Records (PMRs) for IBM Forms products. \n\nCollecting this data early, even before opening a PMR, helps IBM Support determine: \n\n * If symptoms match known problems (rediscovery) \n * If there is a non-defect problem that can be identified and resolved \n * The root cause, which can accelerate the development of a code fix\n\nRESOLVING THE PROBLEM\nA. Gather general information\nWhen working with IBM Support, every problem must have a corresponding problem management record (PMR) opened for it. There are several potential problem areas that will need to be investigated. \n\nInclude the following general information:\n\n\n 1. Provide all software being used including all service packs. Note: If you do not know how to collect the version information for one of the products listed above, please refer to our collecting data technote titled. How to determine version information for IBM Forms [http://www.ibm.com/support/docview.wss?uid=swg21457001].\n \n 2. Provide hardware specifics (i.e. CPU, available hard dive space, memory, and so on)\n \n 3. Describe the problem in detail giving step by step instructions and screen shots to duplicate the issue. What is the error? How is it manifested (i.e. popups, server crash, and so on)\n \n 4. How often does the problem occur?\n \n 5. Provide the form and servlet/portlet application code experiencing the issue. Note: If a simplified application that is able to duplicate the issue and can be deployed without requiring outside resources is provided, this will cut down on investigation times.\n \n 6. What is the business impact that the issue is causing (how many users affected)? What are your current time lines? When do you absolutely need this issue resolved by?\n \n 7. Provide an architectural overview of the server. Helpful when clustering and multiple servers are involved.\n \n 8. Additional contact information - phone number and e-mail address\n \n 9. Log files (see Step C)\n\n\nCOLLECTING DATA USING IBM SUPPORT ASSISTANT\n 1. Download ISA Lite [https://www-304.ibm.com/support/docview.wss?uid=swg24029414] and extract it to your WAS_HOME directory.\n \n \n 2. Start ISA Lite by running runISALite.[sh|bat].\n \n \n 3. Select the following collector: IBM Forms General Data Collection\n \n \n 4. Follow the prompts to automatically submit the collected data to IBM Support.\n 5. \n\nNote: Due to limited functionality of tool, ISA Lite will only collect logs for runtime issues. This tool currently is not able to collect logs generated by wpf.pel file or install specific issues. Please review section B and C of the 'Collecting data manually' section for further information. This functionality will be added in a later iteration of the tool.\n\nCOLLECTING DATA MANUALLY\nB. Gather debug information \n\n\nTo help IBM Support with its troubleshooting, take the following steps to create debug information:\n\nOn a Windows® system, create an empty text file in the C: directory or the user profile directory named wpf.pel. \n\nYou can confirm the user profile directory path by running the 'set USERPROFILE' command on the command line. \n\nMake sure the extension is .pel rather than .pel.txt. Re-run your application when this file exists. Note: We look for the pel file in the user profile directory first. \n\nIBM Forms generates log files first on the C: drive else the user profiles temp directory. \n\nYou can confirm the temp directory's location by running the 'set temp' command on the command line.\n\nWhen working with Viewer, a masqform.log will be generated. When working with Webform Server or the API, a java.log will be created. \n\nOn a Unix system, create an empty text file in the /etc directory or in the current working directory (Translator or custom application using Forms API). When this file exists, IBM Forms Server products will generate a debug.log in the current working directory.\n\nFor debugging signature issues, open the pel file in a text editor and add the word 'signmessage'. This will create signmessage-java-x.xml files in the same location as the pel file.\n\nFor debugging Webform Server or Forms Experience Builder (FEB) issues, you can increase the debug log level to finest under Websphere's Admin Console;Troubleshooting -> Logs and trace -> TranslatorServer -> Change log detail levels and modify com.ibm.form.*. *=info is default log level.\n\nie. *=info: com.ibm.form.*=finest\n\nNote: For SharedFileCache issues (database out of sync, Cache locking), you may want to refine your tracing to:\n\n*=info: com.ibm.form.webform.logging.facility.fom.*=FINE: \n\ncom.ibm.form.webform.logging.facility.fom.FormInstances=FINEST\n\nNote: For debugging issues where you need to log all activity between your front end application that extends our framework and the translator, you may want to refine your tracing under the server you have deployed your application (ie. server1) to:\n\n*=info: com.ibm.form.webform.framework.*=FINEST\n\nC. Gather log files \n\nViewer \n\n1. See section B \n\nDesigner \n\n1. .log file under C:\\<path to workspace>\\workspace\\.metadata if a runtime error is encountered. \n\n2. Core and javacore files in C:\\Program Files (x86)\\IBM\\Forms Designer\\8.0\\platform\\eclipse if Designer experiences a crash. \n\nWebform Server \n\nInstall issues \n\nWhen running into an install/uninstall issue, please provide the following logs \n\nIf the install does not let you select the finish button in the install process, please provide the following logs: \n\nWindows: \nC:\\Users\\ <user>\\AppData\\Local\\Temp\\FormsServerInstall-xx.log \nC:\\Users\\ <user>\\AppData\\Local\\Temp\\FormsServerUninstall-xx.log \n\nUnix: \n<System Temp dir>/FormsServerInstall-xx.log \n<System Temp dir>/FormsServerUninstall-xx.log \n\nIf the install/uninstall finishes with serious errors, please provide the following zip file: \n\n<IBM Forms Install Dir>\\Server\\8.0\\logs.zip \n\nRuntime issues \n\nSee section B \n\nZip the WebSphere Application Server logs folder \n\n<WebSphere Install Dir>\\AppServer\\profiles\\ <profileName>\\logs \n\nWebSphere Portal logs \n\n<WebSphere Install Dir>\\PortalServer\\log \n<WebSphere Install Dir>\\AppServer\\profiles\\ <profileName>\\logs\\ffdc \n<WebSphere Install Dir>\\AppServer\\logs \n\n<IBM Forms Install Dir>\\Translator\\translator.properties \n\nForms Experience Builder (FEB) \n\nZip the WebSphere Aplication Server logs folder in a manual deployment of FEB: \n\n<WebSphere Install Dir>\\AppServer\\profiles\\ <profileName>\\logs \n\nIf you use WASCE during the FEB install, zip and upload the following folder: \n\n<FEB install location>/WebSphere/AppServerCommunityEdition/var/log \n\nProvide the Builder_config.properties file \n\nWindows: C:\\ibm\\forms\\extensions \nUnix: /opt/ibm/forms/extensions \n\nAPI \n\nSee section B \n\nZip the WebSphere Application Server logs folder \n\n<WebSphere Install Dir>\\AppServer\\profiles\\ <profileName>\\logs \nEXCHANGING DATA WITH IBM SUPPORT\nFollow the instructions to send diagnostic information to IBM support, and be sure to provide all information captured above. This step requires that a PMR be opened if not already: \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?rs=180&uid=swg21153852]", "Trace logs; performance TECHNOTE (FAQ)\n\nQUESTION\n What information should be collected when I experience a problem with IBM Case History/Case Visualizer component of the IBM Case Manager 5.2? \n\nANSWER\nMust Gather for the IBM Case History/Case Visualizer 5.2.x software \n\n\nCollecting data before calling IBM support will help you understand the problem and save time analyzing the data. \n\n\nCollecting data early, before opening the PMR, helps IBM® Support quickly determine if: \n• Symptoms match known problems (rediscovery). \n• There is a non-defect problem that can be identified and resolved. \n• There is a defect that identifies a workaround to reduce severity.\n\nLocating the root cause of a problem can speed development of a code fix. \n\n\n\nDescribing the Problem \n\n\nThis background information is needed for opening a PMR, but is not gathered by the data collector: \n• How often does this problem occur? \n• Can the problem be reproduced? And if so, how is it reproduced? \n• How many users are affected by this problem? \n• Is the problem in newly exercised functionality? Or was this previously working and now it's stopped working? \n• What, if anything, has been changed? \n• What is the business impact of this problem? \n• Is there a workaround? \n\n\nGathering Operating System Versions, Settings and Logs \n\nThese commands collect: \n• OS Version \n• OS Environment Variables \n• OS Kernel parameters \n• OS running processes \n• OS networking information \n• OS locale information \n• OS log files \n\nRun the following commands on the Content Foundation Content Platform Engine server and collect the output: \n\n\nAIX Servers \n\nCommand​ Collects​ /usr/sbin/instfix -ivq ​ OS Patches or Maintenance level​ env ​ OS Environment Variables​ errpt -a​ OS Configuration & Error Reporting​ /usr/sbin/lsattr -E -l sys0 ​ OS Kernel parameters​ ps -ef​ currently running processes​ netstat -an​ socket information​ locale​\nlocale -a​ locale information​ /var/adm/syslog/syslog.log​ include system log files​ \n\nSolaris Servers Command​ Collects​ /usr/bin/showrev -a ​ OS Patches or Maintenance level​ env ​ OS Environment Variables​ /usr/sbin/prtdiag -v ​ OS Configuration & Error Reporting​ /usr/sbin/sysdef -D ​\n/usr/bin/getconf -a​ OS Kernel parameters​ ps -ef​ currently running processes​ netstat -an​ socket information​ locale​\nlocale -a​ locale information​ /var/adm/messages & /var/log/syslog​ include system log files​ \n\n\nWindows Servers Command​ Collects​ WMIC /OUTPUT:C:\\ProcessList.txt PROCESS get Caption,Processid,Usermodetime,Commandline​ current running processes including the command line​ set​ OS Environment Variables​ Windows 2003: ​\ncscript C:\\windows\\system32\\eventquery.vbs ​\n/L application /R 1000 /V ​\ncscript C:\\windows\\system32\\eventquery.vbs ​\n/L system /R 1000 /V ​\n​\nWindows 2008 and newer:​\nwevtutil epl System Systemlog.evtx​\nwevtutil epl Application Applicationlog.evtx​ OS Event Logs​ netstat -an​ socket information​ chcp​ display code page​ \n\n\nLinux Servers Command​ Collects​ uname -a​ OS Version​ /usr/bin/showrev -a ​ OS Patches or Maintenance level​ env ​ OS Environment Variables​ /usr/sbin/prtdiag -v ​ OS Configuration & Error Reporting​ /usr/sbin/sysdef -D ​\n/usr/bin/getconf -a ​ OS Kernel parameters​ /usr/bin/getconf -a​ configuration info​ /bin/dmesg​ messages​ ps -ef​ currently running processes​ netstat -an​ socket information​ locale​\nlocale -a​ locale information​ /var/log/messages.*​ include system log files​ \n\n\nPing pages for supporting components: \n\nBecause the Case History interacts with the Content Platform Engine, Case Manager, Content Navigator and Case Foundation, it is useful to collect their ping pages to make sure that all the components have the same client versions. \n\nFor Content: http://<cpe-server name>:<cpe-port #>/FileNet/Engine \nFor Process: http://<cpe-server name>:<cpe-port #>/peengine/IOR/ping \nFor Case Manager: http://<server name>:<port #>/CaseManager/CASEREST/v1/in \nFor Content Navigator: http://<icn-server name>:<icn-port #>/navigator/Ping \n\n\nCollect the following database information for Case History installation and configuration issues: \n\n• Database type \n• Database version \n• Local or remote database. \n• Joint or Separate database instance from Target Object Store \n\n\nCase History Logs and Traces \n\nThe main log where Case History information is logged is the pesvr_system.log file which can be found under a location similar to the following: \n\n...\\WebSphere\\AppServer\\profiles\\AppSrv01\\FileNet\\server1\\pesvr_system.log \n\nDepending on the issue you are troubleshooting you will need to enable vwtool tracing. To enable the tracing follow the steps detailed in the link below: \nhttp://www-01.ibm.com/support/docview.wss?uid=swg21678454 [http://www-01.ibm.com/support/docview.wss?uid=swg21678454] \nEnable the following tracing options:\n• Case History Publishing (Trace the Case History event publishing process) \n• Case History Collect (Trace the event collection process which queries the event logs) \n• Case History Database (Trace the database query statements that are run by Case History) \n• Case History RPC (Trace the remote procedure calls from the Administration Console for Content Platform Engine)\n• Case History Performance (Trace Case History Performance) \n• Case History Upgrade (Trace the Case History upgrade operation)\n\n\n\nLogs: \n\n\nApplication server logs\nShould the issue be related to not being able to see the Case Visualizer data in a Case or issues with the Case Visualizer widget collect the following IBM Case Manager Client log. The IBM® Case Manager Client records log messages to the IBM Content Navigator log file. To configure debug level logging for IBM® Case Manager web applications, you must enable debugging on the IBM Content Navigator server and restart the IBM Content Navigator server. \n\n\nProcedure: \nTo configure logging settings in IBM Content Navigator: \n1. Log in to the IBM Content Navigator administration desktop. \n2. Click the Settings tab and then click the Logging subtab. \n3. Set the logging level for the applications to Debug. \n4. Click Save and then click Close. \n5. Log out of the IBM Content Navigator administration desktop. \n6. Restart the application server instance where IBM Content Navigator is deployed.\n\nThe IBM® Case Manager Client records log messages to the IBM Content Navigator log file. \n\nFor further information about log files in IBM Content Navigator, see the IBM Content Navigator documentation: http://pic.dhe.ibm.com/infocenter/cmgmt/v8r4m0/topic/com.ibm.installingeuc.doc/eucts002.htm [http://pic.dhe.ibm.com/infocenter/cmgmt/v8r4m0/topic/com.ibm.installingeuc.doc/eucts002.htm] \n\nWebSphere Application Server \nIn WebSphere® Application Server, all logging information is written to the SystemOut.log file. By default, this log file is in the following subdirectory of the WebSphere Application Server installation directory: \n\nWAS_profile_location/logs/server/\n\n\nAdditional data collection: \n\n \nIn order to identify whether the issue is with Case History data collection, run the following database queries and collect the output.\n\nCapture the output of the following SQL statements at the same time. \n\n\nFrom the CE database:\n- select max(audit_sequence) FROM Event\n\n\nFrom the PE database collect the output of the below statements for each of the event logs on the system:\n- select max(F_SeqNumber) FROM VWLog1_111 \n- select count(F_SeqNumber) FROM WVL1_111 where F_SeqNumber > 123456789\n(Note: 123456789 is an example value. Please set the value that is seen in the CH_X_PEEventState table to run the query.)\n\nFrom the Case History database:\n- select * from CH_X_PEEventState\n- select * from CH_X_CEEventState\n\n\nCheck the indexes on CE log tables:\n\nTo understand if there any performance issues, check if the following index exists for the Event table on the CE database:\ni3 on event (u<xy>_CMACMCASEFOLDER, AUDIT_SEQUENCE desc) \n\n\nThis database retrieval index efficiently retrieves the case history in the Event table in target object stores.\n\nMaintain the PE Event log tables:\n\nMake sure maintenance is being carried out on a regular basis on the PE Event log tables to prevent performance issues with Case History:\nhttp://www-01.ibm.com/support/docview.wss?uid=swg27036649 [http://www-01.ibm.com/support/docview.wss?uid=swg27036649]\n\n\nScreenshots: \n\n \nIt may be appropriate to include screenshots of errors or other symptoms that will help us understand the problem.", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Trace analysis information for the logging component in the WebSphere® 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® 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® 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." ]

[ [ "0a", " WHITE PAPER ABSTRACT" ], [ "0b", " You can configure log4j to generate trace logs for both FileNet P8 Content Platform Engine and IBM Connections Waltz at the same time. CONTENT" ], [ "0c", "Starting with FileNet P8 version 5.2, IBM Connections Waltz comes bundled with FileNet P8 Content Platform Engine (CPE)." ], [ "0d", "If standard logging procedures are followed, the logs for both CPE and Waltz cannot be generated at the same time." ], [ "0e", "This white paper shows how to generate CPE and Waltz logs concurrently." ], [ "0f", "It comes with an attached log4j.xml file, which you can use as a starting point." ], [ "0g", "Screen shots are based on IBM® WebSphere® Application Server 7.0. Configuration Steps" ], [ "0h", "1) Download the attached log4j.xml file and save it in the c:\\temp folder." ], [ "0i", "The file contains log4j settings for both CPE and Waltz." ], [ "0j", "2) On the WebSphere server that hosts the FileNet P8 Content Platform Engine, add the following JVM arguments:" ], [ "0k", "-DskipTLC=true -Dlog4j.configuration=file:/c:/temp/log4j.xml [file:///c:/temp/log4j.xml] [/support/docview.wss?uid=swg27040423&aid=1] [/support/docview.wss?uid=swg27040423&aid=1]" ], [ "0l", "3) Save the change and restart the WebSphere Application Server." ], [ "0m", "The system is now ready to generate trace logs for CPE and Waltz concurrently." ], [ "0n", "Note: Syntax-errors in log4j.xml will be logged to the SystemErr.log file of the WebSphere Server hosting FileNet." ], [ "0o", "Log File Location" ], [ "0p", "With the default settings in log4j.xml file, the following three logs are generated: · p8_server_error.log · p8_server_trace.log · waltz.sonata.trace.log" ], [ "0q", "They are located in the following path: app_server_root_dir\\profiles\\AppSrv01\\logs\\" ], [ "0r", "For example, here is the location on a Windows server: C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\AppSrv01\\logs\\" ], [ "0s", "With the default log4j settings, CPE trace log messages are in the p8_server_trace.log file, while Waltz trace messages are in the waltz.sonata.trace.log file. Configuration Variations" ], [ "0t", "The log4j in the XML file can be configured for the following purposes." ], [ "0u", "Troubleshooting Functional Issues" ], [ "0v", "With the default log4j settings, detailed trace messages are logged for security troubleshooting." ], [ "0w", "For CPE, both EJB and Security sub-systems are enabled." ], [ "0x", "To troubleshoot security-related issues use the log4j.xml file as-is, without modification. [/support/docview.wss?uid=swg27040423&aid=2] [/support/docview.wss?uid=swg27040423&aid=2]" ], [ "0y", "Troubleshooting Performance Issues" ], [ "0z", "Turn on timer flags to troubleshoot performance issues in directory service area." ], [ "0aa", "Turn off detail level for CPE’s Security sub-system." ], [ "0ab", "Otherwise, it will generate more directory service calls and add more performance overhead. [/support/docview.wss?uid=swg27040423&aid=3] [/support/docview.wss?uid=swg27040423&aid=3]" ], [ "0ac", "Log CPE and Waltz Messages in the Same File" ], [ "0ad", "Both CPE and Waltz trace messages can be logged to the same file (p8_server_trace.log) by adding FileNetTraceRollingAppender to the root logger. [/support/docview.wss?uid=swg27040423&aid=4] [/support/docview.wss?uid=swg27040423&aid=4]" ], [ "0ae", "log4j.xml [/support/docview.wss?uid=swg27040423&aid=6]log4j.xml [/support/docview.wss?uid=swg27040423&aid=5]" ] ]

[ "0b", "0c", "0e", "0f", "0i", "0p", "0q", "0s", "0ad", "4k", "4l", "4m", "4n", "4o", "4q", "4r", "4u", "4v", "4w", "4z", "4aa", "4ac", "4ae" ]

[ " WHITE PAPER\n\nABSTRACT\n You can configure log4j to generate trace logs for both FileNet P8 Content Platform Engine and IBM Connections Waltz at the same time. \n\nCONTENT\nStarting with FileNet P8 version 5.2, IBM Connections Waltz comes bundled with FileNet P8 Content Platform Engine (CPE). If standard logging procedures are followed, the logs for both CPE and Waltz cannot be generated at the same time. \n\nThis white paper shows how to generate CPE and Waltz logs concurrently. It comes with an attached log4j.xml file, which you can use as a starting point. Screen shots are based on IBM® WebSphere® Application Server 7.0. \n\nConfiguration Steps\n\n1) Download the attached log4j.xml file and save it in the c:\\temp folder. The file contains log4j settings for both CPE and Waltz. \n\n2) On the WebSphere server that hosts the FileNet P8 Content Platform Engine, add the following JVM arguments:\n\n-DskipTLC=true -Dlog4j.configuration=file:/c:/temp/log4j.xml [file:///c:/temp/log4j.xml] \n\n[/support/docview.wss?uid=swg27040423&aid=1] [/support/docview.wss?uid=swg27040423&aid=1]\n\n3) Save the change and restart the WebSphere Application Server. The system is now ready to generate trace logs for CPE and Waltz concurrently.\n\nNote: Syntax-errors in log4j.xml will be logged to the SystemErr.log file of the WebSphere Server hosting FileNet.\n\nLog File Location \n\nWith the default settings in log4j.xml file, the following three logs are generated: \n· p8_server_error.log \n· p8_server_trace.log \n· waltz.sonata.trace.log\n\nThey are located in the following path: \n\napp_server_root_dir\\profiles\\AppSrv01\\logs\\\n\nFor example, here is the location on a Windows server:\n\nC:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\AppSrv01\\logs\\\n\nWith the default log4j settings, CPE trace log messages are in the p8_server_trace.log file, while Waltz trace messages are in the waltz.sonata.trace.log file.\n\nConfiguration Variations\n\nThe log4j in the XML file can be configured for the following purposes. \n\nTroubleshooting Functional Issues\n\nWith the default log4j settings, detailed trace messages are logged for security troubleshooting. For CPE, both EJB and Security sub-systems are enabled. To troubleshoot security-related issues use the log4j.xml file as-is, without modification. \n\n[/support/docview.wss?uid=swg27040423&aid=2] [/support/docview.wss?uid=swg27040423&aid=2]\n\nTroubleshooting Performance Issues \n\nTurn on timer flags to troubleshoot performance issues in directory service area. Turn off detail level for CPE’s Security sub-system. Otherwise, it will generate more directory service calls and add more performance overhead. \n\n[/support/docview.wss?uid=swg27040423&aid=3] [/support/docview.wss?uid=swg27040423&aid=3]\n\nLog CPE and Waltz Messages in the Same File\n\nBoth CPE and Waltz trace messages can be logged to the same file (p8_server_trace.log) by adding FileNetTraceRollingAppender to the root logger. \n\n[/support/docview.wss?uid=swg27040423&aid=4] [/support/docview.wss?uid=swg27040423&aid=4]\n\n\n\n\nlog4j.xml [/support/docview.wss?uid=swg27040423&aid=6]log4j.xml [/support/docview.wss?uid=swg27040423&aid=5]", " TECHNOTE (FAQ)\n\nQUESTION\n What data should you collect for problems with the IBM UrbanCode Deploy WebSphere Application Server – Deployment and WebSphere Application Server – Configure plugins? \n\nCAUSE\nThe IBM UrbanCode Deploy WebSphere Application Server – Deployment and WebSphere Application Server – Configure plugins store logs in different locations from other UrbanCode Deploy plugins, because they expose Actions from the Resource Tree, that can be triggered without executing an Application/Component process. Additionally, the level of logging can be increased in the Component steps of the WebSphere Application Server – Configure plugin, resulting in the creation of additional log files.\n\nANSWER\nDepending on the action you are performing, you can find diagnostic information in different locations. \n\nWebSphere Application Server – Deployment plugin\n\n\n * WebSphere (Cell) Discovery\n * If you executed the WebSphere (Cell) Discovery interactively, by adding an Agent to the Resource Tree, then the log can be found in:\n \n Resources > Agent Resource > History\n \n Configuration Task History > WebSphere Discovery > Actions > Output log\n \n [/support/docview.wss?uid=swg2C1000185&aid=1] [/support/docview.wss?uid=swg2C1000185&aid=1] \n * Alternatively, you could run this as a process, as follows:\n \n 1. Take the parent resource of the agent, and create a Resource Property called: \n \n websphere.profilePath\n \n that refers to the location of the WAS Profile and could be set to a value like: \n \n C:\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01 \n \n 2. Create a Generic process onto which you drop the step: \n \n Java > WebSphere > Deployment > WebSphere Discovery\n \n 3. Execute the step on the Agent Resource \n \n In this case, the diagnostic information is contained in the output of the Generic process step. \n \n Provide this file to support after clicking on Download All Logs.\n \n [/support/docview.wss?uid=swg2C1000185&aid=2] [/support/docview.wss?uid=swg2C1000185&aid=2]\n \n \n\n * WebSphere Topology Discovery\n * If you executed the WebSphere Topology Discovery from the menu:\n \n Actions > Configure using WebSphere Topology Discovery \n \n available on the discovered WebSphere Cell in the Resource Tree, then the log can be found in:\n \n Resources > WebSphere Cell Resource > History\n \n Configuration Task History > WebSphere Topology Discovery > Actions > Output log\n \n [/support/docview.wss?uid=swg2C1000185&aid=3] [/support/docview.wss?uid=swg2C1000185&aid=3]\n \n * Alternatively, you could have executed the WebSphere Configuration Discovery as a Generic process, following these steps:\n \n 1. Drop the step Configuration Discovery > Update from Live Configuration \n \n 2. In the parameter: Plugin Step, select WebSphere Topology Discovery from the drop down list. \n \n 3. Change the value of the Resource parameter from ${p:resource.parent.path} to ${p:resource.path} (this is required only if running as a Generic process, as opposed to a Component Process, since in a Component process the desired resource is the parent of the Component itself).\n \n In this case the diagnostic information is contained in the output of the Generic process.\n \n Provide this file to support after clicking on Download All Logs.\n \n \n\n\nWebSphere Application Server – Configure plugin \n\n \n\n * WebSphere Configuration Discovery\n \n Starting with v17 of the WAS Configure plugin, the execution of following menu of the Resource Tree:\n \n Actions > Configure using WebSphere Configuration Discovery \n \n is deprecated, in favor of the usage of the Component Step: \n \n Java > WebSphere > Configuration > WebSphere Configuration Discovery\n \n [/support/docview.wss?uid=swg2C1000185&amp;aid=4]\n \n Starting with v25 of the WAS - Configure plugin, after you drop this step on the canvas, you can augment the logging level by doing the following:\n \n Show hidden properties > Logging level > change from Info to Debug\n \n [/support/docview.wss?uid=swg2C1000185&aid=5] [/support/docview.wss?uid=swg2C1000185&aid=5]\n \n If the Logging Level is set to Debug/Trace, you will see additional icons for log files next to the output log: debug.log and redo.log.\n \n Provide the complete set of logs to IBM Support after clicking on Download All Logs.\n \n [/support/docview.wss?uid=swg2C1000185&aid=6] [/support/docview.wss?uid=swg2C1000185&aid=6]\n \n * WebSphere Configuration Apply\n \n The Component process step:\n \n Java > WebSphere > Configuration > WebSphere Configuration Apply \n \n has the same option for increasing the logging level. \n \n [/support/docview.wss?uid=swg2C1000185&aid=7] [/support/docview.wss?uid=swg2C1000185&aid=7]\n \n The files debugLog.txt and redoLog.txt can be found as described above.\n \n Provide these file to IBM Support after clicking on Download All Logs.\n \n \n * WebSphere Configuration Compare\n \n The Component process steps:\n \n Java > WebSphere > Configuration > WebSphere Configuration Compare \n \n Java > WebSphere > Configuration > WebSphere Get Compare Results \n \n have the same option for increasing the logging level and the same method for obtaining the resulting debugLog.txt and redoLog.txt, as described above.\n \n Provide these file to IBM Support after clicking on Download All Logs.", "mustgatherdocument; IBM Forms; IBM Forms API; IBM Forms Server; troubleshooting; mustgather; support; documentation; wpf; wpf.pel; pel file; logs; log files; problem management record; PMR TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nThis document will aid in problem determination and save time resolving Problem Management Records (PMRs) for IBM Forms products. \n\nCollecting this data early, even before opening a PMR, helps IBM Support determine: \n\n * If symptoms match known problems (rediscovery) \n * If there is a non-defect problem that can be identified and resolved \n * The root cause, which can accelerate the development of a code fix\n\nRESOLVING THE PROBLEM\nA. Gather general information\nWhen working with IBM Support, every problem must have a corresponding problem management record (PMR) opened for it. There are several potential problem areas that will need to be investigated. \n\nInclude the following general information:\n\n\n 1. Provide all software being used including all service packs. Note: If you do not know how to collect the version information for one of the products listed above, please refer to our collecting data technote titled. How to determine version information for IBM Forms [http://www.ibm.com/support/docview.wss?uid=swg21457001].\n \n 2. Provide hardware specifics (i.e. CPU, available hard dive space, memory, and so on)\n \n 3. Describe the problem in detail giving step by step instructions and screen shots to duplicate the issue. What is the error? How is it manifested (i.e. popups, server crash, and so on)\n \n 4. How often does the problem occur?\n \n 5. Provide the form and servlet/portlet application code experiencing the issue. Note: If a simplified application that is able to duplicate the issue and can be deployed without requiring outside resources is provided, this will cut down on investigation times.\n \n 6. What is the business impact that the issue is causing (how many users affected)? What are your current time lines? When do you absolutely need this issue resolved by?\n \n 7. Provide an architectural overview of the server. Helpful when clustering and multiple servers are involved.\n \n 8. Additional contact information - phone number and e-mail address\n \n 9. Log files (see Step C)\n\n\nCOLLECTING DATA USING IBM SUPPORT ASSISTANT\n 1. Download ISA Lite [https://www-304.ibm.com/support/docview.wss?uid=swg24029414] and extract it to your WAS_HOME directory.\n \n \n 2. Start ISA Lite by running runISALite.[sh|bat].\n \n \n 3. Select the following collector: IBM Forms General Data Collection\n \n \n 4. Follow the prompts to automatically submit the collected data to IBM Support.\n 5. \n\nNote: Due to limited functionality of tool, ISA Lite will only collect logs for runtime issues. This tool currently is not able to collect logs generated by wpf.pel file or install specific issues. Please review section B and C of the 'Collecting data manually' section for further information. This functionality will be added in a later iteration of the tool.\n\nCOLLECTING DATA MANUALLY\nB. Gather debug information \n\n\nTo help IBM Support with its troubleshooting, take the following steps to create debug information:\n\nOn a Windows® system, create an empty text file in the C: directory or the user profile directory named wpf.pel. \n\nYou can confirm the user profile directory path by running the 'set USERPROFILE' command on the command line. \n\nMake sure the extension is .pel rather than .pel.txt. Re-run your application when this file exists. Note: We look for the pel file in the user profile directory first. \n\nIBM Forms generates log files first on the C: drive else the user profiles temp directory. \n\nYou can confirm the temp directory's location by running the 'set temp' command on the command line.\n\nWhen working with Viewer, a masqform.log will be generated. When working with Webform Server or the API, a java.log will be created. \n\nOn a Unix system, create an empty text file in the /etc directory or in the current working directory (Translator or custom application using Forms API). When this file exists, IBM Forms Server products will generate a debug.log in the current working directory.\n\nFor debugging signature issues, open the pel file in a text editor and add the word 'signmessage'. This will create signmessage-java-x.xml files in the same location as the pel file.\n\nFor debugging Webform Server or Forms Experience Builder (FEB) issues, you can increase the debug log level to finest under Websphere's Admin Console;Troubleshooting -> Logs and trace -> TranslatorServer -> Change log detail levels and modify com.ibm.form.*. *=info is default log level.\n\nie. *=info: com.ibm.form.*=finest\n\nNote: For SharedFileCache issues (database out of sync, Cache locking), you may want to refine your tracing to:\n\n*=info: com.ibm.form.webform.logging.facility.fom.*=FINE: \n\ncom.ibm.form.webform.logging.facility.fom.FormInstances=FINEST\n\nNote: For debugging issues where you need to log all activity between your front end application that extends our framework and the translator, you may want to refine your tracing under the server you have deployed your application (ie. server1) to:\n\n*=info: com.ibm.form.webform.framework.*=FINEST\n\nC. Gather log files \n\nViewer \n\n1. See section B \n\nDesigner \n\n1. .log file under C:\\<path to workspace>\\workspace\\.metadata if a runtime error is encountered. \n\n2. Core and javacore files in C:\\Program Files (x86)\\IBM\\Forms Designer\\8.0\\platform\\eclipse if Designer experiences a crash. \n\nWebform Server \n\nInstall issues \n\nWhen running into an install/uninstall issue, please provide the following logs \n\nIf the install does not let you select the finish button in the install process, please provide the following logs: \n\nWindows: \nC:\\Users\\ <user>\\AppData\\Local\\Temp\\FormsServerInstall-xx.log \nC:\\Users\\ <user>\\AppData\\Local\\Temp\\FormsServerUninstall-xx.log \n\nUnix: \n<System Temp dir>/FormsServerInstall-xx.log \n<System Temp dir>/FormsServerUninstall-xx.log \n\nIf the install/uninstall finishes with serious errors, please provide the following zip file: \n\n<IBM Forms Install Dir>\\Server\\8.0\\logs.zip \n\nRuntime issues \n\nSee section B \n\nZip the WebSphere Application Server logs folder \n\n<WebSphere Install Dir>\\AppServer\\profiles\\ <profileName>\\logs \n\nWebSphere Portal logs \n\n<WebSphere Install Dir>\\PortalServer\\log \n<WebSphere Install Dir>\\AppServer\\profiles\\ <profileName>\\logs\\ffdc \n<WebSphere Install Dir>\\AppServer\\logs \n\n<IBM Forms Install Dir>\\Translator\\translator.properties \n\nForms Experience Builder (FEB) \n\nZip the WebSphere Aplication Server logs folder in a manual deployment of FEB: \n\n<WebSphere Install Dir>\\AppServer\\profiles\\ <profileName>\\logs \n\nIf you use WASCE during the FEB install, zip and upload the following folder: \n\n<FEB install location>/WebSphere/AppServerCommunityEdition/var/log \n\nProvide the Builder_config.properties file \n\nWindows: C:\\ibm\\forms\\extensions \nUnix: /opt/ibm/forms/extensions \n\nAPI \n\nSee section B \n\nZip the WebSphere Application Server logs folder \n\n<WebSphere Install Dir>\\AppServer\\profiles\\ <profileName>\\logs \nEXCHANGING DATA WITH IBM SUPPORT\nFollow the instructions to send diagnostic information to IBM support, and be sure to provide all information captured above. This step requires that a PMR be opened if not already: \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?rs=180&uid=swg21153852]", "Trace logs; performance TECHNOTE (FAQ)\n\nQUESTION\n What information should be collected when I experience a problem with IBM Case History/Case Visualizer component of the IBM Case Manager 5.2? \n\nANSWER\nMust Gather for the IBM Case History/Case Visualizer 5.2.x software \n\n\nCollecting data before calling IBM support will help you understand the problem and save time analyzing the data. \n\n\nCollecting data early, before opening the PMR, helps IBM® Support quickly determine if: \n• Symptoms match known problems (rediscovery). \n• There is a non-defect problem that can be identified and resolved. \n• There is a defect that identifies a workaround to reduce severity.\n\nLocating the root cause of a problem can speed development of a code fix. \n\n\n\nDescribing the Problem \n\n\nThis background information is needed for opening a PMR, but is not gathered by the data collector: \n• How often does this problem occur? \n• Can the problem be reproduced? And if so, how is it reproduced? \n• How many users are affected by this problem? \n• Is the problem in newly exercised functionality? Or was this previously working and now it's stopped working? \n• What, if anything, has been changed? \n• What is the business impact of this problem? \n• Is there a workaround? \n\n\nGathering Operating System Versions, Settings and Logs \n\nThese commands collect: \n• OS Version \n• OS Environment Variables \n• OS Kernel parameters \n• OS running processes \n• OS networking information \n• OS locale information \n• OS log files \n\nRun the following commands on the Content Foundation Content Platform Engine server and collect the output: \n\n\nAIX Servers \n\nCommand​ Collects​ /usr/sbin/instfix -ivq ​ OS Patches or Maintenance level​ env ​ OS Environment Variables​ errpt -a​ OS Configuration & Error Reporting​ /usr/sbin/lsattr -E -l sys0 ​ OS Kernel parameters​ ps -ef​ currently running processes​ netstat -an​ socket information​ locale​\nlocale -a​ locale information​ /var/adm/syslog/syslog.log​ include system log files​ \n\nSolaris Servers Command​ Collects​ /usr/bin/showrev -a ​ OS Patches or Maintenance level​ env ​ OS Environment Variables​ /usr/sbin/prtdiag -v ​ OS Configuration & Error Reporting​ /usr/sbin/sysdef -D ​\n/usr/bin/getconf -a​ OS Kernel parameters​ ps -ef​ currently running processes​ netstat -an​ socket information​ locale​\nlocale -a​ locale information​ /var/adm/messages & /var/log/syslog​ include system log files​ \n\n\nWindows Servers Command​ Collects​ WMIC /OUTPUT:C:\\ProcessList.txt PROCESS get Caption,Processid,Usermodetime,Commandline​ current running processes including the command line​ set​ OS Environment Variables​ Windows 2003: ​\ncscript C:\\windows\\system32\\eventquery.vbs ​\n/L application /R 1000 /V ​\ncscript C:\\windows\\system32\\eventquery.vbs ​\n/L system /R 1000 /V ​\n​\nWindows 2008 and newer:​\nwevtutil epl System Systemlog.evtx​\nwevtutil epl Application Applicationlog.evtx​ OS Event Logs​ netstat -an​ socket information​ chcp​ display code page​ \n\n\nLinux Servers Command​ Collects​ uname -a​ OS Version​ /usr/bin/showrev -a ​ OS Patches or Maintenance level​ env ​ OS Environment Variables​ /usr/sbin/prtdiag -v ​ OS Configuration & Error Reporting​ /usr/sbin/sysdef -D ​\n/usr/bin/getconf -a ​ OS Kernel parameters​ /usr/bin/getconf -a​ configuration info​ /bin/dmesg​ messages​ ps -ef​ currently running processes​ netstat -an​ socket information​ locale​\nlocale -a​ locale information​ /var/log/messages.*​ include system log files​ \n\n\nPing pages for supporting components: \n\nBecause the Case History interacts with the Content Platform Engine, Case Manager, Content Navigator and Case Foundation, it is useful to collect their ping pages to make sure that all the components have the same client versions. \n\nFor Content: http://<cpe-server name>:<cpe-port #>/FileNet/Engine \nFor Process: http://<cpe-server name>:<cpe-port #>/peengine/IOR/ping \nFor Case Manager: http://<server name>:<port #>/CaseManager/CASEREST/v1/in \nFor Content Navigator: http://<icn-server name>:<icn-port #>/navigator/Ping \n\n\nCollect the following database information for Case History installation and configuration issues: \n\n• Database type \n• Database version \n• Local or remote database. \n• Joint or Separate database instance from Target Object Store \n\n\nCase History Logs and Traces \n\nThe main log where Case History information is logged is the pesvr_system.log file which can be found under a location similar to the following: \n\n...\\WebSphere\\AppServer\\profiles\\AppSrv01\\FileNet\\server1\\pesvr_system.log \n\nDepending on the issue you are troubleshooting you will need to enable vwtool tracing. To enable the tracing follow the steps detailed in the link below: \nhttp://www-01.ibm.com/support/docview.wss?uid=swg21678454 [http://www-01.ibm.com/support/docview.wss?uid=swg21678454] \nEnable the following tracing options:\n• Case History Publishing (Trace the Case History event publishing process) \n• Case History Collect (Trace the event collection process which queries the event logs) \n• Case History Database (Trace the database query statements that are run by Case History) \n• Case History RPC (Trace the remote procedure calls from the Administration Console for Content Platform Engine)\n• Case History Performance (Trace Case History Performance) \n• Case History Upgrade (Trace the Case History upgrade operation)\n\n\n\nLogs: \n\n\nApplication server logs\nShould the issue be related to not being able to see the Case Visualizer data in a Case or issues with the Case Visualizer widget collect the following IBM Case Manager Client log. The IBM® Case Manager Client records log messages to the IBM Content Navigator log file. To configure debug level logging for IBM® Case Manager web applications, you must enable debugging on the IBM Content Navigator server and restart the IBM Content Navigator server. \n\n\nProcedure: \nTo configure logging settings in IBM Content Navigator: \n1. Log in to the IBM Content Navigator administration desktop. \n2. Click the Settings tab and then click the Logging subtab. \n3. Set the logging level for the applications to Debug. \n4. Click Save and then click Close. \n5. Log out of the IBM Content Navigator administration desktop. \n6. Restart the application server instance where IBM Content Navigator is deployed.\n\nThe IBM® Case Manager Client records log messages to the IBM Content Navigator log file. \n\nFor further information about log files in IBM Content Navigator, see the IBM Content Navigator documentation: http://pic.dhe.ibm.com/infocenter/cmgmt/v8r4m0/topic/com.ibm.installingeuc.doc/eucts002.htm [http://pic.dhe.ibm.com/infocenter/cmgmt/v8r4m0/topic/com.ibm.installingeuc.doc/eucts002.htm] \n\nWebSphere Application Server \nIn WebSphere® Application Server, all logging information is written to the SystemOut.log file. By default, this log file is in the following subdirectory of the WebSphere Application Server installation directory: \n\nWAS_profile_location/logs/server/\n\n\nAdditional data collection: \n\n \nIn order to identify whether the issue is with Case History data collection, run the following database queries and collect the output.\n\nCapture the output of the following SQL statements at the same time. \n\n\nFrom the CE database:\n- select max(audit_sequence) FROM Event\n\n\nFrom the PE database collect the output of the below statements for each of the event logs on the system:\n- select max(F_SeqNumber) FROM VWLog1_111 \n- select count(F_SeqNumber) FROM WVL1_111 where F_SeqNumber > 123456789\n(Note: 123456789 is an example value. Please set the value that is seen in the CH_X_PEEventState table to run the query.)\n\nFrom the Case History database:\n- select * from CH_X_PEEventState\n- select * from CH_X_CEEventState\n\n\nCheck the indexes on CE log tables:\n\nTo understand if there any performance issues, check if the following index exists for the Event table on the CE database:\ni3 on event (u<xy>_CMACMCASEFOLDER, AUDIT_SEQUENCE desc) \n\n\nThis database retrieval index efficiently retrieves the case history in the Event table in target object stores.\n\nMaintain the PE Event log tables:\n\nMake sure maintenance is being carried out on a regular basis on the PE Event log tables to prevent performance issues with Case History:\nhttp://www-01.ibm.com/support/docview.wss?uid=swg27036649 [http://www-01.ibm.com/support/docview.wss?uid=swg27036649]\n\n\nScreenshots: \n\n \nIt may be appropriate to include screenshots of errors or other symptoms that will help us understand the problem.", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Trace analysis information for the logging component in the WebSphere® 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® 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® 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." ]

[ [ "4a", " TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "4b", " Trace analysis information for the logging component in the WebSphere® Application Server. SYMPTOM" ], [ "4c", "Does not display." ], [ "4d", "RESOLVING THE PROBLEM" ], [ "4e", "This document contains troubleshooting information for logging problems in the WebSphere® Application Server." ], [ "4f", "This can help address common issues with this component before calling IBM support and save you time. TAB NAVIGATION * *" ], [ "4g", " * Troubleshoot- selected tab, *" ], [ "4h", " * Collect data [http://www.ibm.com/support/docview.wss?uid=swg21321060] Overview" ], [ "4i", "You will find common questions in this section that may help resolve your logging problems. 1." ], [ "4j", "How do I use JCL with WebSphere® Application Server?" ], [ "4k", "For 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] 2." ], [ "4l", "What are IBM recommendations regarding SLF4J and Logback?" ], [ "4m", "In 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])." ], [ "4n", "JUL provides a good, ubiquitous logging infrastructure, which is suitable for most applications, and integrates with WebSphere Application Server log and trace." ], [ "4o", "Using JUL directly also avoids extra log/trace API \"hops\" that are introduced by using other log/trace frameworks that map to JUL." ], [ "4p", "The WAS logs are generated using JUL Handlers connected to the root JUL Logger." ], [ "4q", "In 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." ], [ "4r", "For example, you may have code already written with Log4J." ], [ "4s", "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." ], [ "4t", "Further, trace spec settings you make in WAS do not control Log4J logger settings." ], [ "4u", "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." ], [ "4v", "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. 3." ], [ "4w", "How can I get WAS logs to go to syslog or the Windows EventLog?" ], [ "4x", "There are a number of places that users have asked to be able to direct logs to in the past." ], [ "4y", "Most notably, a number of customers have asked for the ability to send logs to syslog." ], [ "4z", "WebSphere 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." ], [ "4aa", "Once content is sent to JUL, it can be handled in a variety of flexible ways:" ], [ "4ab", "1) 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." ], [ "4ac", "We also send the log content over JMX notifications, which allows for remote access." ], [ "4ad", "2) 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." ], [ "4ae", "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." ], [ "4af", "3) If users want to do something even more custom, they can write their own JUL Handlers and plug them into WebSphere Application Server. 4." ], [ "4ag", "I am unable to turn on WebSphere Application Server trace." ], [ "4ah", "The trace state sets to *=off?" ], [ "4ai", "The systemOut.log shows:" ], [ "4aj", "[5/26/15 14:10:44:746 EDT] 000000d9 ManagerAdmin I TRAS0018I: The trace state has changed." ], [ "4ak", "The new trace state is *=off." ], [ "4al", "The problem is related to the below two JVM arguments: -Djava.util.logging.configureByLoggingPropertiesFile=TRUE -Djava.util.logging.config.file=<path>/logging.properties" ], [ "4am", "Verify if the above 2 JVM arguments are configured." ], [ "4an", "If yes, temporary disable it so WAS trace can be enabled. 5." ], [ "4ao", "The WebSphere Application Server logging has stopped, what may have caused this?" ], [ "4ap", "The user might have disabled the trace by setting trace output to none." ], [ "4aq", "Setting runtime trace output to none impacts the JVM logs." ], [ "4ar", "To do that, the runtime trace spec will be set to *=off, which means to turn off all log levels." ], [ "4as", "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." ], [ "4at", "For example, set to *=info, which is the default." ], [ "4au", "Verify if the commons-logging.jar and commons-logging.properties exist in the JVM classpath." ], [ "4av", "If yes, suggest to remove it and put them inside the application (with parent_last setting) or put them in the isolated shared library. 6." ], [ "4aw", "How can I separate my logs into separate files for each application?" ], [ "4ax", "In WAS V8.5, we added the application name to log and trace records stored using HPEL (High Performance Extensible Logging)." ], [ "4ay", "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)." ], [ "4az", "For 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" ], [ "4ba", "WAS_INSTALL_ROOT\\bin> logViewer -includeExtensions appName=app2 > app2.log" ], [ "4bb", "WAS_INSTALL_ROOT\\bin> logViewer -includeExtensions appName=app3 > app3.log" ], [ "4bc", "or see everything in one file as follows:" ], [ "4bd", "WAS_INSTALL_ROOT\\bin> logViewer > all.log 7." ], [ "4be", "How can I add my own java.util.logging.Handler to WAS?" ], [ "4bf", "To 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): import java.util.logging.Handler; import java.util.logging.Level; import java.util.logging.LogRecord;" ], [ "4bg", "public class MyHandler extends Handler {" ], [ "4bh", "public void close() { }" ], [ "4bi", "public void flush() { }" ], [ "4bj", "public void publish(LogRecord record) {" ], [ "4bk", "if (record.getLevel().intValue() >= Level.SEVERE.intValue()) {" ], [ "4bl", "// do something... } } }" ], [ "4bm", "In your application you can add that Handler to the root logger as follows: import java.util.logging.Handler; import java.util.logging.Logger; ..." ], [ "4bn", "Handler myHandler = new MyHandler();" ], [ "4bo", "Logger logger = Logger.getLogger(\"\"); logger.addHandler(myHandler); ... 8." ], [ "4bp", "Why can't I set my own log levels using the Logger setLevel method?" ], [ "4bq", "The application server can run in two modes." ], [ "4br", "By 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." ], [ "4bs", "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." ], [ "4bt", "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." ], [ "4bu", "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." ], [ "4bv", "Alternately, you can have the server to be configured by the JRE's logging.properties file by setting the java.util.logging.configureByLoggingPropertiesFile property." ], [ "4bw", "In this mode, the application server will not touch the logger levels -- you cannot update the levels through the admin console, nor through wsadmin." ], [ "4bx", "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." ], [ "4by", "In this mode, you can specify anything you would normally specify in your logging.properties file." ], [ "4bz", "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. 9." ], [ "4ca", "How can I get java.util.logging to initialize from a jre/bin/logging.properties file in the application server?" ], [ "4cb", "You can do this via system property: java.util.logging.configureByLoggingPropertiesFile=true" ], [ "4cc", "Note that if you do set up your server in this mode, we will not manage your logger levels via the admin console." ], [ "4cd", "Note 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." ], [ "4ce", "If you do use this system property, and you want to change logger levels, you have two choices: *" ], [ "4cf", " * 2) Set the Logger levels programatically using the Logger.setLevel method 10." ], [ "4cg", "How can I get the full logger name from log and trace records?" ], [ "4ch", "The full logger name can be handy to know for enabling trace." ], [ "4ci", "How you get to it depends on what log and trace mode you use:" ], [ "4cj", "Basic log and trace mode:" ], [ "4ck", "The 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:" ], [ "4cl", "[4/14/11 9:41:45:218 EDT] 00000021 QuickLogTest W hello fine 54857" ], [ "4cm", "There is no way to get the full logger name from basic formatted logs." ], [ "4cn", "You need to switch to advanced format for your logs/trace if you want to see the full logger name." ], [ "4co", "Once in advanced format, log contents appear as follows:" ], [ "4cp", "[4/14/11 9:41:45:218 EDT] 00000021 W UOW= source=com.ibm.somelogger.QuickLogTest org= prod= component= thread=[WebContainer : 4]" ], [ "4cq", "hello fine 54857" ], [ "4cr", "HPEL log and trace mode:" ], [ "4cs", "You can use the HPEL LogViewer command line tool to output the log/trace content in either basic or advanced format." ], [ "4ct", "> logviewer -format basic ...." ], [ "4cu", "[4/14/11 9:41:45:218 EDT] 00000021 QuickLogTest W hello fine 54857 ...." ], [ "4cv", "> logviewer -format advanced ...." ], [ "4cw", "[4/14/11 9:41:45:218 EDT] 00000021 W UOW= source=com.ibm.somelogger.QuickLogTest org= prod= component= thread=[WebContainer : 4]" ], [ "4cx", "hello fine 54857 ... 11." ], [ "4cy", "How can I write HPEL content to a database?" ], [ "4cz", "If you want to write to a Database, any of the following options will work:" ], [ "4da", "1) Write your own log handler (that writes to a database) and plug it into JSR47." ], [ "4db", "(see the Java doc for java.util.logging.Handler)" ], [ "4dc", "2) Write an HPEL reading Java application to read the content from an HPEL log repository and write it to a database" ], [ "4dd", "3) 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. 12." ], [ "4de", "How do you tune HPEL for optimal performance in tWAS?" ], [ "4df", "In the server.xml, jvmEntries element:" ], [ "4dg", "- Ensure debugMode is set to false" ], [ "4dh", "- Ensure RAS JMX notifications are disabled by including -Dcom.ibm.ejs.ras.disablerasnotifications=true in genericJvmArguments" ], [ "4di", "- Ensure -Xquickstart is not in the list of genericJvmArguments" ], [ "4dj", "<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\"> In hpelModel.xml:" ], [ "4dk", "- Ensure textLog is disabled." ], [ "4dl", "<hpelTextLog xmi:id=\"HPELTextLog_1\" enabled=\"false\" dataDirectory=\"${SERVER_LOG_ROOT}\"/> 13." ], [ "4dm", "How can I tell who is writing to System.err / System.out ?" ], [ "4dn", "Add the following to your genericJvmArgument s : -Xtrace:print=mt,trigger=method{com/ibm/ejs/ras/System*. *,jstacktrace} 14." ], [ "4do", "How can I identify what code is writing to System.out.println?" ], [ "4dp", "Add the following to your genericJvmArguments and restart the server to see a stack trace for each call to System.out.println: -Xtrace:print=mt,trigger=method{java/io/PrintStream.println,jstacktrace}" ], [ "4dq", "A 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." ], [ "4dr", "03:41:01.245*0x3277900 mt.0 > java/io/PrintStream.println(Ljava/lang/String;)V Bytecode method, This = 7fffff49f98" ], [ "4ds", "03:41:01.247 0x3277900 j9trc_aux.0 - jstacktrace:" ], [ "4dt", "03:41:01.248 0x3277900 j9trc_aux.1 - [1] java.io.PrintStream.println (PrintStream.java:829)" ], [ "4du", "03:41:01.248 0x3277900 j9trc_aux.1 - [2] com.ibm.jvm.io.ConsolePrintStream.println (ConsolePrintStream.java:311)" ], [ "4dv", "03:41:01.250 0x3277900 j9trc_aux.1 - [3] Hello.printHello (Hello.java:15)" ], [ "4dw", "03:41:01.251 0x3277900 j9trc_aux.1 - [4] Hello.main (Hello.java:9)Hello World" ], [ "4dx", "03:41:01.253 0x3277900 mt.6 < java/io/PrintStream.println(Ljava/lang/String;)V Bytecode method 15." ], [ "4dy", "How can I see who called a particular method?" ], [ "4dz", "Add the following to your genericJvmArguments: -Xtrace:print=mt,trigger=method{java/util/logging/Logger.setLevel,jstacktrace} 16." ], [ "4ea", "What are the .owner files for in the log directory?" ], [ "4eb", "The server creates a .owner file for each of the log files." ], [ "4ec", "The file content indicates which cell/node/server is the rightful user of the similarly named log file." ], [ "4ed", "This is used as a sort of locking mechanism to make sure that users don't improperly configure their systems." ], [ "4ee", "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." ], [ "4ef", "For 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] 17." ], [ "4eg", "How can I correlate information from thread stacks in the javacore with information in my SystemOut.log file?" ], [ "4eh", "There are a few ways to correlate content in WAS logs/trace with content in javacore thread dumps:" ], [ "4ei", "Best option, if you are using WebSphere Application Server 8.0 / 8.5: Applies to:" ], [ "4ej", "WAS 8.0.0.4 and above running with Java 626 SR4 and above" ], [ "4ek", "WAS 8.5.0.2 and above running with Java 7 SR3 and above or Java 626 SR4 and above" ], [ "4el", "In 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." ], [ "4em", "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." ], [ "4en", "In WAS 8.5.0.2 and above, the thread id used in the logs/trace matches with the Java thread id by default." ], [ "4eo", "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]" ], [ "4ep", "Another option if you are using High Performance Extensible Logging (HPEL) / Binary Logging: Applies to:" ], [ "4eq", "Full profile WAS 8.0.0.0 and above" ], [ "4er", "Liberty profile WAS 8.5.5.0 and above Full Profile:" ], [ "4es", "Use the HPEL logViewer command to output the logs in advanced format so you can see the full thread name:" ], [ "4et", "> logViewer -format advanced (basic is the default format) Liberty Profile:" ], [ "4eu", "Use the binaryLog command line tool to output the logs in advanced format so you can see the full thread name:" ], [ "4ev", "> binaryLog view --format=advanced" ], [ "4ew", "You will get output that looks like the following:" ], [ "4ex", "[4/14/11 9:41:45:218 EDT] 00000021 W UOW= source=com.ibm.somelogger.QuickLogTest org= prod= component= thread=[WebContainer : 4]" ], [ "4ey", "The javacore contains the same thread name:" ], [ "4ez", "3XMTHREADINFO \"WebContainer : 4\" J9VMThread:0x1578D700, j9thread_t:0x150D0D04, java/lang/Thread:0x02517CE0, state:R, prio=5" ], [ "4fa", "3XMTHREADINFO1 (native thread ID:0x15B0, native priority:0x5, native policy:UNKNOWN)" ], [ "4fb", "3XMTHREADINFO3 Java callstack:" ], [ "4fc", "4XESTACKTRACE at com/ibm/io/async/AsyncLibrary.aio_getioev2(Native Method)" ], [ "4fd", "Another option if you are using Advanced format for your SystemOut.log / trace.log: Applies to:" ], [ "4fe", "All currently supported WebSphere Application Server releases." ], [ "4ff", "Change your log/trace format to Advanced." ], [ "4fg", "The Advanced format contains the full thread name, as does the javacore." ], [ "4fh", "Advanced format Log:" ], [ "4fi", "[4/14/11 9:41:45:218 EDT] 00000021 W UOW= source=com.ibm.somelogger.QuickLogTest org= prod= component= thread=[WebContainer : 4]" ], [ "4fj", "The javacore contains the same thread name:" ], [ "4fk", "3XMTHREADINFO \"WebContainer : 4\" J9VMThread:0x1578D700, j9thread_t:0x150D0D04, java/lang/Thread:0x02517CE0, state:R, prio=5" ], [ "4fl", "3XMTHREADINFO1 (native thread ID:0x15B0, native priority:0x5, native policy:UNKNOWN)" ], [ "4fm", "3XMTHREADINFO3 Java callstack:" ], [ "4fn", "4XESTACKTRACE at com/ibm/io/async/AsyncLibrary.aio_getioev2(Native Method)" ], [ "4fo", "What to do next" ], [ "4fp", "If 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." ] ]

[ "0b", "0c", "0e", "0f", "0i", "0p", "0q", "0s", "0ad", "4k", "4l", "4m", "4n", "4o", "4q", "4r", "4u", "4v", "4w", "4z", "4aa", "4ac", "4ae" ]

[ "z/os A FIX IS AVAILABLE\nRational Team Concert 6.0.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24044342]\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 * In IBM Rational Team Concert Enterprise Extensions, after\n applying 6.0.1 ifix013, CCM.logs are generating excessive\n entries of CRRTC1033E and CRJAZ1033I when a build result is\n deleted that includes a build report with details that now can\n not be parsed.\n \n 2017-06-28 07:01:01,898 [ Thread-15120] WARN\n y.maintenance.BuildMapBuildResultDeleteParticipant - Caught\n exception attempting to parse contents of build or promotion\n report for cleanup\n org.xml.sax.SAXParseException: The reference to entity\n \"CBLDB2CMPDFLT\" must end with the ';' delimiter.\n \tat\n org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseExcepti\n on(Unknown Source)\n \tat\n org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown\n Source)\n ...\n \tat org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)\n \tat\n com.ibm.team.enterprise.build.buildmap.compatability.maintenance\n .BuildMapBuildResultDeleteParticipant$1.run(BuildMapBuildResultD\n eleteParticipant.java:82)\n \tat java.lang.Thread.run(Thread.java:809)\n 2017-06-28 07:01:02,902 [ccm: AsynchronousTaskRunner-5 @@ 07:00]\n ERROR com.ibm.team.build -\n CRRTC3011E: The contributions to a build,\n _Qpu9kQtXEeOks9obGf8jQQ, could not be pruned by the pruning\n extension,\n com.ibm.team.enterprise.build.buildmap.maintenance.BuildMapBuild\n ResultDeleteParticipant, because an error occurred.\n com.ibm.team.repository.common.InternalRepositoryException:\n CRJAZ1033I Failed to fetch content _mTFkQAtaEeOtLI0HenwcLQ.\n \tat\n com.ibm.team.repository.service.internal.RdbRepositoryDataMediat\n or.fetchContent(RdbRepositoryDataMediator.java:1406)\n \tat\n com.ibm.team.repository.service.internal.ContentService.doRetrie\n veContent(ContentService.java:1408)\n \t...\n \tat\n com.ibm.team.enterprise.build.buildmap.compatability.maintenance\n .BuildMapBuildResultDeleteParticipant.doDelete(BuildMapBuildResu\n ltDeleteParticipant.java:98)...\n \tat\n com.ibm.team.build.internal.service.delete.BuildResultContributi\n onsPruner.deleteBuildResultContributions(BuildResultContribution\n sPruner.java:212)\n \tat\n com.ibm.team.build.internal.service.delete.BuildResultContributi\n onsPruner.deleteBuildResultContributions(BuildResultContribution\n sPruner.java:167)\n \tat\n com.ibm.team.build.internal.service.delete.BuildResultContributi\n onsPruner.prune(BuildResultContributionsPruner.java:133)\n \tat\n com.ibm.team.build.internal.service.InternalTeamBuildService$1Pr\n uneResultsRunnable.run(InternalTeamBuildService.java:240)\n \tat\n com.ibm.team.build.internal.service.AbstractTeamBuildService.run\n WithoutException(AbstractTeamBuildService.java:314)\n \tat\n com.ibm.team.build.internal.service.InternalTeamBuildService.pru\n neBuildResults(InternalTeamBuildService.java:253)\n ...\n Caused by:\n com.ibm.team.repository.common.InternalRepositoryException:\n CRJAZ2713E Failed to move the content to an output stream for\n the content \"StoredContent(_mTFkQAtaEeOtLI0HenwcLQ, text/xml,\n 5355, None, HashCode(0x39873fe2))\".\n \tat\n com.ibm.team.repository.service.internal.ContentService$ContentD\n irectToStream.receiveContent(ContentService.java:2323)\n \tat\n com.ibm.team.repository.service.internal.db.filestorage.ContentS\n torage.visitContentById(ContentStorage.java:344)\n \tat\n com.ibm.team.repository.service.internal.RdbRepositoryDataMediat\n or.fetchContent(RdbRepositoryDataMediator.java:1397)\n \t... 86 more\n Caused by: java.io.IOException: Pipe closed\n \tat\n java.io.PipedInputStream.checkStateForReceive(PipedInputStream.j\n ava:273)\n \t\t... 88 more\n \n In the 10 MB split CCM with an original size of 50 MB, there are\n 847 occurrences of this information message.\n \n To recreate:\n 1. Open a Enterprise Extensions build result.\n 2. Remove the buildReport.xml attached.\n 3. Attach a buildReport.xml that has some specific input build\n file that cannot be parsed such as\n <inputs:buildFile>&W</inputs:buildFile>.\n 4. Delete the build result.\n 5. Wait for 15 minutes and review the ccm log.\n \n Defect:\n https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#act\n ion=com.ibm.team.workitem.viewWorkItem&id=427371 [https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=427371]\n \n \n \n \n \n\nLOCAL FIX\n * None - recycle and clean up logs before they exceed space\n limitations\n Log settings can be changed to wrap and be limited to a specific\n number and size in log4j.properties for each application.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * See Jazz Work Item 442767 on jazz.net\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Fixed in 6.0.4 iFix005 Dev + Validation\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI84763\n \n \n * REPORTED COMPONENT NAME\n JAZZ TEAM SRVR\n \n \n * REPORTED COMPONENT ID\n 5724V8210\n \n \n * REPORTED RELEASE\n 601\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 2017-07-19\n \n \n * CLOSED DATE\n 2017-11-14\n \n \n * LAST MODIFIED DATE\n 2017-11-14\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 JAZZ TEAM SRVR\n \n \n * FIXED COMPONENT ID\n 5724V8210\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R604 PSN\n UP", " SUBSCRIBE\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 * SAP role subform error when trying to view the SAP authorization\n roles assigned to a user\n \n \n The error in ITIM trace.log is:\n <Exception><![CDATA[; Line#: 1; Column#: 267\n javax.xml.transform.TransformerException: The reference to\n entity\n \"E_2_GB01_HR_MANAGER\" must end with the ';' delimiter.\n \n The user has the following SAP authorisation roles:\n Z:ECC6_SAP_EMPLOYEE_ERP|20080604|99991231|\n Z&E_2_GB01_HR_MANAGER|20080604|99991231|\n The subform breaks when it tries to load Z&E_2_GB01_HR_MANAGER.\n I know\n this because when I removed it, the form loads fine.\n Interestingly, the role comes back as Z+E_2_GB01_HR_MANAGER\n under\n supporting data, rather than account data.\n \n Unfortunately the subform load error still occurs when role\n Z&E_2_GB01_HR_MANAGER|20080819|20090819| is present. Appears the\n subform\n does not like the & (ampersand).\n \n .\n \n Customr Recreate: yes\n L2 Support Recreate: none\n \n Desired Behavior: able to view the SAP authorisation roles\n assigned to\n the user Steps\n Duplicate:view the SAP Authorisation roles\n Environment:ESR: TIM 46 FP68\n \n \n \n \n \n\nLOCAL FIX\n * n/a\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Users affected:\n Customers using SAP Sub Forms and having role names with an &\n ampersand character.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * This fix for this APAR is contained in the\n following maintenance packages:\n | Fixpack | 4.6.0-TIV-TIM-FP0079\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IZ30480\n \n \n * REPORTED COMPONENT NAME\n IBM TIV ID MGR\n \n \n * REPORTED COMPONENT ID\n 5724C3403\n \n \n * REPORTED RELEASE\n 460\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 2008-08-25\n \n \n * CLOSED DATE\n 2008-09-24\n \n \n * LAST MODIFIED DATE\n 2008-09-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\nMODULES/MACROS\n * SERVER\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n IBM TIV ID MGR\n \n \n * FIXED COMPONENT ID\n 5724C3403\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R460 PSY\n UP", "XSD; 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 &lt;, &gt;, &quot;, &apos; and &amp;). \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", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Client gets SAXParseException while updating spec\n value with ?&amp;? inside <value> tag.\n \n Snippet of sample request xml:\n \n <ProductSpecValueBObj>\n <ProductSpecValueId/>\n ...\n \n <AttributeValueBObj>\n <Action>update</Action>\n <Path>/MyProductSpec</Path>\n <Value>\n <![CDATA[\n <MyProductSpec\n xmlns=\"http://www.example.com/MyProductSpec/internal/00000001\"\n xmlns:ps=\"http://www.example.com/MyProductSpec/internal/00000001\n \">\n <MyProdName>My ProductName &amp; Testing\n </MyProdName>\n \n </MyProductSpec>\n ]]>\n </Value>\n </AttributeValueBObj>\n </ProductSpecValueBObj>\n \n Snippet of sample response xml:\n \n <DWLError>\n <ComponentType>99</ComponentType>\n <Detail>com.ibm.mdm.common.jpal.JPALException:\n org.xml.sax.SAXParseException: The entity name must immediately\n follow the '&amp;' in the entity reference.</Detail>\n <ErrorMessage>Handle Schema Validation\n Failed.</ErrorMessage>\n <ErrorType>READERR</ErrorType>\n <LanguageCode>100</LanguageCode>\n <ReasonCode>9606</ReasonCode>\n <Severity>0</Severity>\n \n <Throwable>com.ibm.mdm.common.jpal.JPALException:\n org.xml.sax.SAXParseException: The entity name must immediately\n follow the '&amp;' in the entity reference.</Throwable>\n </DWLError>\n \n \n \n \n \n\nLOCAL FIX\n * This problem has been fixed in 9.0.2.25. Please download and\n install this PTF if you experience this problem.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * See Above\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Originally reported as PMR #30469,379,000\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IC88364\n \n \n * REPORTED COMPONENT NAME\n MASTR DATA MGT\n \n \n * REPORTED COMPONENT ID\n 5724S7800\n \n \n * REPORTED RELEASE\n 902\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-11-19\n \n \n * CLOSED DATE\n 2013-02-11\n \n \n * LAST MODIFIED DATE\n 2013-02-11\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 MASTR DATA MGT\n \n \n * FIXED COMPONENT ID\n 5724S7800\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R902 PSY\n UP", " SUBSCRIBE\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 * After adding a report and assigning it name or\n \n description containing language specific character\n an information that no BIRT reports are available\n was displayed. In error.log you can find:\n 2012-12-10 13:55:09,335 [http-9430-Processor20] ERROR\n util.BirtUtil -\n Could not unmarshal report list\n javax.xml.bind.UnmarshalException\n - with linked exception:\n [org.xml.sax.SAXParseException: Invalid byte 2 of 4-byte UTF-8\n sequence.\n ]\n After the fix such characters will be available.\n \n \n \n \n \n\nLOCAL FIX\n * remove language specific characters from report.xml file\n \n \n \n \n \n\nPROBLEM SUMMARY\n * After adding a report and assigning it name or description\n containing language\n specific character an information that no BIRT reports are\n available was\n displayed. In error.log you can find: 2012-12-10 13:55:09,335\n [http-9430-Processor20] ERROR util.BirtUtil - Could not\n unmarshal report list\n javax.xml.bind.UnmarshalException - with linked exception:\n [org.xml.sax.SAXParseException: Invalid byte 2 of 4-byte UTF-8\n sequence. ] After\n the fix such characters will be available.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The fix for this APAR is contained in the following maintenance\n packages:\n | Fix Pack | 7.2.1-TIV-ITADDM-FP0004\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IV33162\n \n \n * REPORTED COMPONENT NAME\n APP DEPENDENCY\n \n \n * REPORTED COMPONENT ID\n 5724N5500\n \n \n * REPORTED RELEASE\n 720\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-12-10\n \n \n * CLOSED DATE\n 2013-01-31\n \n \n * LAST MODIFIED DATE\n 2013-01-31\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 APP DEPENDENCY\n \n \n * FIXED COMPONENT ID\n 5724N5500\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R721 PSY\n UP" ]

[ [ "1a", " SUBSCRIBE You can track all active APARs for this component. APAR STATUS" ], [ "1b", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "1c", " * SAP role subform error when trying to view the SAP authorization" ], [ "1d", " roles assigned to a user" ], [ "1e", " The error in ITIM trace.log is:" ], [ "1f", " <Exception><!" ], [ "1g", "[CDATA[; Line#: 1; Column#: 267" ], [ "1h", " javax.xml.transform.TransformerException: The reference to" ], [ "1i", " entity" ], [ "1j", " \"E_2_GB01_HR_MANAGER\" must end with the ';' delimiter." ], [ "1k", " The user has the following SAP authorisation roles:" ], [ "1l", " Z:ECC6_SAP_EMPLOYEE_ERP|20080604|99991231|" ], [ "1m", " Z&E_2_GB01_HR_MANAGER|20080604|99991231|" ], [ "1n", " The subform breaks when it tries to load Z&E_2_GB01_HR_MANAGER." ], [ "1o", " I know" ], [ "1p", " this because when I removed it, the form loads fine." ], [ "1q", " Interestingly, the role comes back as Z+E_2_GB01_HR_MANAGER" ], [ "1r", " under" ], [ "1s", " supporting data, rather than account data." ], [ "1t", " Unfortunately the subform load error still occurs when role" ], [ "1u", " Z&E_2_GB01_HR_MANAGER|20080819|20090819| is present. Appears the" ], [ "1v", " subform" ], [ "1w", " does not like the & (ampersand)." ], [ "1x", " ." ], [ "1y", " Customr Recreate: yes" ], [ "1z", " L2 Support Recreate: none" ], [ "1aa", " Desired Behavior: able to view the SAP authorisation roles" ], [ "1ab", " assigned to" ], [ "1ac", " the user Steps" ], [ "1ad", " Duplicate:view the SAP Authorisation roles" ], [ "1ae", " Environment:ESR: TIM 46 FP68 LOCAL FIX" ], [ "1af", " * n/a PROBLEM SUMMARY" ], [ "1ag", " * Users affected:" ], [ "1ah", " Customers using SAP Sub Forms and having role names with an &" ], [ "1ai", " ampersand character. PROBLEM CONCLUSION" ], [ "1aj", " * This fix for this APAR is contained in the" ], [ "1ak", " following maintenance packages:" ], [ "1al", " | Fixpack | 4.6.0-TIV-TIM-FP0079 TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "1am", " * APAR NUMBER" ], [ "1an", " IZ30480" ], [ "1ao", " * REPORTED COMPONENT NAME" ], [ "1ap", " IBM TIV ID MGR" ], [ "1aq", " * REPORTED COMPONENT ID" ], [ "1ar", " 5724C3403" ], [ "1as", " * REPORTED RELEASE" ], [ "1at", " 460" ], [ "1au", " * STATUS" ], [ "1av", " CLOSED PER" ], [ "1aw", " * PE" ], [ "1ax", " NoPE" ], [ "1ay", " * HIPER" ], [ "1az", " NoHIPER" ], [ "1ba", " * SPECIAL ATTENTION" ], [ "1bb", " NoSpecatt" ], [ "1bc", " * SUBMITTED DATE" ], [ "1bd", " 2008-08-25" ], [ "1be", " * CLOSED DATE" ], [ "1bf", " 2008-09-24" ], [ "1bg", " * LAST MODIFIED DATE" ], [ "1bh", " 2008-09-24" ], [ "1bi", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "1bj", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: MODULES/MACROS" ], [ "1bk", " * SERVER FIX INFORMATION" ], [ "1bl", " * FIXED COMPONENT NAME" ], [ "1bm", " IBM TIV ID MGR" ], [ "1bn", " * FIXED COMPONENT ID" ], [ "1bo", " 5724C3403" ], [ "1bp", "APPLICABLE COMPONENT LEVELS" ], [ "1bq", " * R460 PSY" ], [ "1br", " UP" ] ]

[ "1c", "1e", "1g", "1h", "1i", "1j", "1n", "1u", "1v" ]

[ "siebel; utf; codepage; connectivity TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The WebSphere Adapter for Siebel cannot connect to the Siebel server either on runtime or during the artifact discovery. Error message is \" <Error><ErrorCode>8211</ErrorCode> <ErrMsg>Code Page \"UTF-8\" is not supported. Use \"-encoding\" option to change the file encoding. (SBL-JCA-328) </ErrMsg></Error>\".\n\nThis technote is intended for the WebSphere Message Broker environment.\nIf you experience the same in a WebSphere Application Server environment, please refer to the workaround provided in technote:\nhttp://www.ibm.com/support/docview.wss?uid=swg21393552 [http://www.ibm.com/support/docview.wss?uid=swg21393552] \n\nCAUSE\nSiebel systems with version less than 8.0 does not allow the syntax of the codepage to be \"UTF-8\".\n\nDIAGNOSING THE PROBLEM\n1. Check that the Siebel dependency jars can be accessed from the adapter.\n\n\n\n\n2. Even though you might not receive the error message \"UTF-8\" is not supported. Use \"-encoding\" option to change the file encoding. (SBL-JCA-328) \", have a look for the error \"Could not open a session in 4 attempts. {1} (SBL-JCA-200)\". \n\n3. Problem occurs during adapter runtime but also during artifact discovery.\n\n\nRESOLVING THE PROBLEM\nThe cause of this problem can be an incorrect codepage or the syntax of a correct codepage is wrong. \n\nFor Siebel systems with version less than 8.0, verify the supported codepages as given below:\nSiebel Java™ Bean [http://download.oracle.com/docs/cd/E05553_01/books/OIRef/OIRefProgramming24.html#wp1004955]\n\nAs you can find in the list above, the codepage \"utf8\" is supported which means that we have to set this codepage syntax before connecting to the Siebel server.\n\nFor the WebSphere Application server environment, please proceed as described in the technote:WebSphere Adapter for Siebel Business Applications V6.1 Connectivity Problem due to Codepage Error [http://www.ibm.com/support/docview.wss?uid=swg21393552]\n\nFor the WebSphere Message Broker (WMB) environment, please proceed as given below for a workaround to the problem. \n\nModify the file \"eclipse.ini\" in the WMB Toolkit install folder (For example: c:\\Program Files\\IBM\\WMBT700) to set the JVM property \"file.encoding\" to \"utf8\". \nAdd the line \"-Dfile.encoding=utf8\" after \"-vmargs\":\n\n----- Sample ini ------\n-vm \nC:\\Program Files\\IBM\\WMBT700\\jdk\\jre\\bin\\javaw.exe\n-startup\nplugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar \n-install\nC:\\Program Files\\IBM\\WMBT700\n--launcher.library\nplugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080\n731 \n-vmargs \n-Dfile.encoding=utf8\n-Xquickstart\n-Xms40m \n----- Sample ini end ------\n\nThe WMB Toolkit needs to be restarted to reflect the change. \n\n\nRELATED INFORMATION\n#Siebel Connectivity for WAS env [http://www.ibm.com/support/docview.wss?uid=swg21393552 ]\n\n\n\n\n\n\nCross Reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker", " SUBSCRIBE\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 * Siebel Adapter ignores field value with\n SBL-DAT.\n \n - Problem observed with Siebel Adapter 7.0.0.3\n and WMB 7.0.0.2, AIX\n \n - When a request fails through Siebel Request node,\n then Siebel system can returns an error with tag \"Description\"\n and the field value <SBL-DAT..>.\n \n - On the Siebel system side, the error message is complete,\n on Siebel Adapter side, the error message does not contain\n any content in the description field, \"SBL-DAT\" is being\n ignored.\n \n \n \n \n \n\nLOCAL FIX\n * - no local fix or workaround\n \n \n \n \n \n\nPROBLEM SUMMARY\n * - When a request fails through Siebel Request node, then Siebel\n system returns an error with tag \"Description\" and the field\n value <SBL-DAT..>.\n \n - On the Siebel system side, the error message is complete, on\n Siebel Adapter side, the error message does not contain any\n content in the description field, \"SBL-DAT\" is being ignored.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * This has been fixed in 7.0.0.3_IF04. Please contact IBM Customer\n Support for the fix.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n JR39237\n \n \n * REPORTED COMPONENT NAME\n WEBS ADAPT SIEB\n \n \n * REPORTED COMPONENT ID\n 5724L8000\n \n \n * REPORTED RELEASE\n 700\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 2011-03-25\n \n \n * CLOSED DATE\n 2011-11-08\n \n \n * LAST MODIFIED DATE\n 2011-11-08\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 ADAPT SIEB\n \n \n * FIXED COMPONENT ID\n 5724L8000\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R700 PSY\n UP", " TECHNOTE (FAQ)\n\nQUESTION\n The Siebel connection of WebSphere Adapter for Siebel eBusiness Applications is established with the default settings. You may need to modify the connection settings, such as connection timeout, according to your product environment. \n\nANSWER\nSiebel adapter uses the Siebel API (Java Data Bean) to interact with the Siebel server. The Siebel API also provides a way to configure the connection settings on the client side.\nCreate a siebel.properties file and save it in the classpath of the adapter (For example, <adapter project>\\connectorModule) and restart the adapter and broker to pick up the settings to establish the required connections.\n\nThis is applicable for all supported brokers.\n\nA detailed description of the Siebel.properties file is given below:\n\nSiebel.properties File \n\nThe siebel.properties file, which is located in your classpath, can be used to provide default parameters for client applications connecting to Siebel applications using the Java Data Bean. \n\nThe table below shows the properties in the siebel.properties file. \n\n[/support/docview.wss?uid=swg21366662&amp;aid=1] [/support/docview.wss?uid=swg21366662&amp;aid=1] [/support/docview.wss?uid=swg21366662&amp;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]", "waemlv61rnote; wasblv61rnote; wapsftv61rnote; WebSphere Adapter 6.1; WebSphere Transformation Extender 8.2; WebSphere Adapter for Email; WebSphere Adapter for Siebel; WebSphere Adapter for PeopleSoft; Adapter Inbound Card; Adapter Outbound Card TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n On the UNIX platform, WebSphere Adapter Version 6.1 can run on WebSphere Transformation Extender Version 8.2; however, there are known limitations when using it in the following situations:\n\n\nWhen using WebSphere Adapter for Email on WebSphere Transformation Extender on the Solaris platform, you might see the following errors:\n- During outbound processing, a null pointer exception might be generated that can lead to the crash of the core engine.\n- During inbound processing, the following exception might be generated: ResourceException: Failed to establish event manager resulting in wrong output data.\n\nWhen using WebSphere Adapter for Siebel on the AIX platform, you might see the following errors:\n- During outbound processing, a null pointer exception might be generated, which might result in the complete blockage of outbound operations.\n- During inbound processing, thef Siebel Inbound launcher might have difficutly starting, and you might see the following message: Server is unable to get the status of the system on port number 7,002.\n\nWhen using WebSphere Adapter for PeopleSoft on the Solaris platform, you can expect to see the following errors:\n- During outbound processing, a null pointer exception might be generated that may lead to the crash of the core engine.\n- During inbound processing, the following execption might be generated: Error code: -1003 , Error message: null, java.lang.IllegalArgumentException. This can result in complete blockage of inbound operations. \n\nRESOLVING THE PROBLEM\nThese are known issues with WebSphere Transformation Extender. They will be addressed by the APAR PK58507 [http://www.ibm.com/support/docview.wss?uid=swg1PK58507].\n\n\n\nCross Reference information Segment Product Component Platform Version Edition Business Integration WebSphere Transformation Extender AIX, Solaris 8.2", " PRODUCT DOCUMENTATION\n\nABSTRACT\nThis technical document is an index of the available WBI Adapter for SAP technical notes, technical documentation and important flash messages.\n\nCONTENT\n\n\n 1. MissingDataException thrown by WebSphere Adapter for SAP Software if required IDocControlRecord parameters are missing [http://www-01.ibm.com/support/docview.wss?uid=swg21461015]\n 2. WebSphere Adapter for SAP and/or WebSphere Business Integration Adapter for mySAP.com has exceeded its max number of conversations [http://www-01.ibm.com/support/docview.wss?uid=swg21458337]\n 3. MustGather: Collecting Data for Problems with the WebSphere Adapter for SAP [http://www-01.ibm.com/support/docview.wss?uid=swg21438193]\n 4. JCo 2.1.9 is supported by the Adapter for mySAP.com, Version 6.0.9 [http://www-01.ibm.com/support/docview.wss?uid=swg21426068]\n 5. Problem Determination for SAP JCo [http://www-01.ibm.com/support/docview.wss?uid=swg21418488]\n 6. Local Transaction support in the WebSphere Adapter for SAP Applications [http://www-01.ibm.com/support/docview.wss?uid=swg21408299]\n 7. How to activate JCo tracing for SAP JCo using a JVM parameter on WebSphere Process Server V6.0, V6.1, or V6.2 [http://www-01.ibm.com/support/docview.wss?uid=swg21404884]\n 8. Points to be considered while tuning performance of WebSphere Business Integration mysap adapter [http://www-01.ibm.com/support/docview.wss?uid=swg21403480]\n 9. SAP dependencies when using the WebSphere Business Integration Adapter for mySAP.com with the Advanced Event Processing (AEP) interface [http://www-01.ibm.com/support/docview.wss?uid=swg21397708]\n 10. Unique RFCProgramId required for Inbound scenarios with Websphere Adapter for SAP [http://www-01.ibm.com/support/docview.wss?uid=swg21368076]\n 11. Minimum authorizations for Enterprise Service Discovery of JCA Adapter for SAP Software - ALE and BAPI module [http://www-01.ibm.com/support/docview.wss?uid=swg21293351]\n 12. Adapter for SAP does not process outbound messages from SAP [http://www-01.ibm.com/support/docview.wss?uid=swg21285085]\n 13. SAPODA error: Export failed due to any/all of the following unresolved dependencies: sap_idoccontrol [http://www-01.ibm.com/support/docview.wss?uid=swg21270152]\n 14. New connector specific properties added to the mySAP.com adapter. [http://www-01.ibm.com/support/docview.wss?uid=swg21258305]\n 15. JCo 2.1.8 is supported by the Adapter for mySAP.com, Version 6.0.7 [http://www-01.ibm.com/support/docview.wss?uid=swg21254449]\n 16. SAP Object Discovery Agent (ODA) generates an ImportException exception when trying to generate DEBMAS05 or DEBMAS06 business objects from SAP ECC 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg21253802]\n 17. Error message 28069 stating \"\"Server function ?????? could not be found\"\" [http://www-01.ibm.com/support/docview.wss?uid=swg21243205]\n 18. Length of attributes for SAP data types TIMS and DATS [http://www-01.ibm.com/support/docview.wss?uid=swg21233583]\n 19. WebSphere Business Integration Adapter for mySAP.com Extension module: fix pack transport for 4.7 and higher contains import errors when loaded into a Unicode SAP WebAS [http://www-01.ibm.com/support/docview.wss?uid=swg21230829]\n 20. Microsoft .dlls for JCo 2.1.4 and above [http://www-01.ibm.com/support/docview.wss?uid=swg21220665]\n 21. Troubleshooting the Adapter for mySAP.com [http://www-01.ibm.com/support/docview.wss?uid=swg21208860]\n 22. WSDL documents generated by the tooling in SAPXI 3.0 can now be consumed by the IBM WebSphere Business Integrator Adapter for SAPXI Object Discovery Agent. [http://www-01.ibm.com/support/docview.wss?uid=swg21202441]\n\nORIGINAL PUBLICATION DATE\n2016-12-12" ]

[ [ "2a", " TECHNOTE (FAQ) QUESTION" ], [ "2b", " The Siebel connection of WebSphere Adapter for Siebel eBusiness Applications is established with the default settings." ], [ "2c", "You may need to modify the connection settings, such as connection timeout, according to your product environment. ANSWER" ], [ "2d", "Siebel adapter uses the Siebel API (Java Data Bean) to interact with the Siebel server." ], [ "2e", "The Siebel API also provides a way to configure the connection settings on the client side." ], [ "2f", "Create a siebel.properties file and save it in the classpath of the adapter (For example, <adapter project>\\connectorModule) and restart the adapter and broker to pick up the settings to establish the required connections." ], [ "2g", "This is applicable for all supported brokers." ], [ "2h", "A detailed description of the Siebel.properties file is given below: Siebel.properties File" ], [ "2i", "The siebel.properties file, which is located in your classpath, can be used to provide default parameters for client applications connecting to Siebel applications using the Java Data Bean." ], [ "2j", "The table below shows the properties in the siebel.properties file." ], [ "2k", "[/support/docview.wss?uid=swg21366662&amp;aid=1] [/support/docview.wss?uid=swg21366662&amp;aid=1] [/support/docview.wss?uid=swg21366662&amp;aid=1] Property Type Property Description Siebel Connection Manager Connection properties siebel.conmgr.txtimeout Indicates the transaction timeout (in milliseconds)." ], [ "2l", "Defaults to 600000 = 10 minutes." ], [ "2m", "siebel.conmgr.poolsize Indicates the connection pool size." ], [ "2n", "Connection pool maintains a set of connections to a specific server process." ], [ "2o", "Defaults to 2." ], [ "2p", "Max connection pool size is 500. siebel.conmgr.sesstimeout Indicates the transaction timeout (in seconds) on the client side." ], [ "2q", "Defaults to 2700 = 45 minutes." ], [ "2r", "siebel.conmgr.retry Indicates the number of open session retries." ], [ "2s", "Defaults to 3. siebel.conmgr.jce" ], [ "2t", "siebel.conmgr.virtualhosts Indicates the usage of Java Cryptography Extension." ], [ "2u", "1 for jce usage and 0 for no usage." ], [ "2v", "A listing of virtual servers representing a group of like servers that perform the same function, for example, call center functions." ], [ "2w", "An incoming login for the call center Virtual Server will try servers from the list in a round-robin fashion." ], [ "2x", "An example of such a list follows: VirtualServer1=sid1:host:port,sid2:host:port...;VirtualServer2=... where:" ], [ "2y", "Virtual Servers = an assigned list of real Siebel Servers with host names and port numbers (of the local SCB)." ], [ "2z", "Siebel Generated code for JCA/JDB properties siebel.connection.string Specifies the Siebel connection string." ], [ "2aa", "siebel.user.name Specifies the user name to be used for logging in to Object Manager." ], [ "2ab", "siebel.user.password Specifies the password to be used for logging in to Object Manager." ], [ "2ac", "siebel.user.language Specifies the user's preferred language." ], [ "2ad", "siebel.user.encrypted Specifies whether the username and password is encrypted." ], [ "2ae", "siebel.jdb.classname Specifies the default JDB classname Java System Properties file.encoding Indicates the code page on the client side." ], [ "2af", "For example, cp1252, utf8, unicodeBig, cp942." ], [ "2ag", "NOTE: Java System Properties are System Properties, not Siebel Properties." ], [ "2ah", "The following is a sample siebel.properties file:" ], [ "2ai", "siebel.connection.string = siebel.tcpip.rsa.none://test.siebel.com/siebel/sseobjmgr_enu/test" ], [ "2aj", "siebel.conmgr.txtimeout = 3600" ], [ "2ak", "siebel.conmgr.poolsize = 5" ], [ "2al", "siebel.conmgr.sesstimeout = 300000" ], [ "2am", "siebel.properties [/support/docview.wss?uid=swg21366662&aid=3] [/support/docview.wss?uid=swg21366662&aid=2]" ] ]

[ "2d", "2e", "2f", "2g", "2j", "2l", "2m", "2p", "2q", "2r" ]

[ "hang scan ie8 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Remote scanning using scanner freezes or stops when using Internet Explorer 8 or later. \n\nSYMPTOM\nAdditional symptoms include: \n\n * The web page may crash and recover (close and quickly reopen). \n * The freeze may occur during or after scanning the first page.\n\n\nCAUSE\nInternet Explorer (IE) 8 and later includes its own version of Data Execution Prevention (DEP) which can cause the above symptoms and prevent scanning from running.\n\nENVIRONMENT\nInternet Explorer 8 and later\n\n\n\nRESOLVING THE PROBLEM\nTo disable DEP: \n\n 1. In the browser, open the Tools menu, and select Internet Options. \n 2. Select the Advanced tab. \n 3. Uncheck Enable memory protection to mitigate online attacks. \n 4. Close all windows, restart the browser and start scanning again.\n\n\nNote: If using Datacap 8.1, this issue has been fixed in 8.1 Fix Pack 1.", "RUP; IE6; Rational Unified Platform; Internet Explorer; Copyright link; 1280685 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When running Rational Unified Process® in Microsoft® Internet Explorer 6, the Web page returns with only the following line displayed \"Copyright IBM Corp. 1987, 2004. All Rights Reserved.\" \n\nCAUSE\nThis is due to the security settings of the Internet Explorer.\n\nRESOLVING THE PROBLEM\nTo resolve this problem, please follow the steps below to set up the correct settings: \n\n 1. Open Internet Explorer 6\n \n 2. Go to Tools > Internet Options\n \n 3. In the Internet Options dialogue, click the Advanced tab\n \n 4. In the Advanced tab, scroll down and select the Security section \n \n 5. Select the option Allow active content to run in files on My Computer\n \n 6. Click Apply and then OK\n \n 7. Restart RUP", "cache cached IE link favourites favorites hyperlink URL error TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When trying to access a previously saved link to a report in Cognos Connection, the user receives the following error:\n\nRSV-BBP-0022 The absolute affinity request 'asynchWait_Request' failed, the requested session does not exist.\n\nDPR-ERR-2082 An error has occurred. Please contact your administrator. The complete error has been logged by CAF with SecureErrorID: \n\nSYMPTOM\nA user cannot access a previously saved link to a report when using Internet Explorer. The user can access the link using a different web browser (such as Firefox), or on another machine.\n\nCAUSE\nInternet Explorer is using a cached version of the page rather than the most recent version.\n\nENVIRONMENT\nOperating System: Windows\n\n\nWeb Browser: Internet Explorer\n\n\nDIAGNOSING THE PROBLEM\nThe link to a report may have worked previously but now is no longer working (the session has expired). Other users can access this link with no issues, or the user can access the same link using a different browser.\n\n\n\nRESOLVING THE PROBLEM\nSet the browser settings to check for newer versions of stored pages on every visit to the page. \n\nSteps: \n\n1. Open Internet Explorer \n\n2. Go to Tools -> Internet Options... \n\n3. In the General tab, under Temporary Internet Files, click on Settings... \n\n4. Select 'Every visit to the Page' for Check for newer versions of stored pages, then click OK. \n\n5. Close and re-open the browser and try accessing the link again.", " TECHNOTE (FAQ)\n\nQUESTION\n I want to enable Web Reputation Scan for HTTPS in IE broswer: how do it ? \n\nANSWER\n\n1. Run Task \"ID 162 - Web Reputation - Enable HTTPS Web Reputation Scanning\"\n\n2. Run Web Reputation Blocked - Approved List Wizard to specify https sites to be bocked.\n\nNote :\n\n- Is not possible for WebRep module to block any https sites as it is just used to specify which URL to block. However, there's an option of blocking the ports 443 and 4343 through the Firewall module.\n\n- HTTPS Web Reputation is only supported on Internet Explorer and Mozilla FireFox browsers.\n\n- Internet Explorer will require third-party browser extensions to be enabled:\n\n\n * \n * TmIEPlugInBHO \n * \n * \n\n- Internet Explorer Enhanced Security Configuration (IE SEC) has to be turned off or removed: \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n *", " TECHNOTE (FAQ)\n\nQUESTION\n How do I get my audio to work for my ProveIt! Assessments? \n\nANSWER\nBefore we are able to start troubleshooting any audio issues, please safely log out of your session following these steps:\nIf you are running a Windows Operating System\n· Hold down the Ctrl, Alt and Delete keys at the same time\n\n· Select the Task Manager option\n· Select the Applications tab\n· Select the internet browser icon that you are accessing your assessment through\n· Select End Task\n· Repeat this step until all browser web pages are closed\n\nIf you are running a Macintosh Operating System\n· Hold down the Command, Option and Esc keys at the same time \n· Select the internet browser icon that you are accessing your assessment through\n· Select Force Quit\n· Repeat this step until all browser web pages are closed\n\nPlease follow the troubleshooting steps that are appropriate for the Operating System and web-browser you are using.\n\nWindows\nWe would recommend using either Internet Explorer or Mozilla Firefox for the audio assessments. Below are the troubleshooting steps that should assist you with the audio for your test:\n\nInternet Explorer\n· Open Internet Explorer \n· Select Tools from the Menu bar - Press [Alt] + [T] on your keyboard\n· Select Internet Options \n· Click on the Advanced Tab\n· Scroll down until you see the Multimedia Section\n· Check the box – Play sounds in WebPages\n· Select the Security tab\n· Click Custom Level\n· Scroll down until you see the Miscellaneous section\n· Locate the Access Data Sources across Domains option and Enable\n· Click Ok\n· Click Yes\n· Click on the General Tab\n· Click the Delete button located under Browsing History\n· Check the box for Temporary Internet Files and Cookies \n· Click Delete\n· Select Tools from the Menu bar - Press [Alt] + [T] on your keyboard\n· Click on Compatibility View settings\n· Type Proveit.com under Add this website\n· Click Add \n· Type Proveit2.com under Add this website\n· Click Add\nProveit.com and Proveit2.com should now appear in the box located under:\nWebsites you’ve added to Compatibility View\n\n· Ensure all check-boxes below are checked\n· Click Close\n· Close completely out of Internet Explorer\n· Reopen Internet Explorer and attempt your test again\n\n\nMozilla Firefox\nIf you are having trouble with the audio using Mozilla Firefox you will need to install a specific version of Apple QuickTime.\n\nYou will need to begin by removing any other versions of Apple QuickTime you have installed. To do this, please follow the steps below:\n\nOpen the Start Menu at the lower left-hand corner of your screen\n· If you are using Windows 8 – hold down the Windows key and X on your keyboard\n· Select Control Panel\n· Click on one of the following options: \no Uninstall a Program\no Programs and Features\no Add or Remove a Program\n· Scroll through the list until you locate Apple QuickTime\n· Select Apple QuickTime and click on Remove\n· Once Apple QuickTime has been removed from the list you may close the control panel\n\nTo install Apple QuickTime 7.6, please use the link provided below:\nhttps://support.apple.com/kb/DL762?locale=en_US [https://support.apple.com/kb/DL762?locale=en_US] \n· Click on Download\n· Click on Save File\n· Click on the blue arrow when it appears in the top-right corner of your screen\n· Select Show All Downloads\n· Click on the QuickTimeInstaller\n· Select Run\n· You will see a window that says “Welcome to the QuickTime 7 Installer”\n· Select Next\n· You will see the License Agreement and will need to select Yes to continue\n· Click on Install\n· It may ask if you want to make changes to the computer\n· Select Yes\n· You will see a message that says “QuickTime 7 has been successfully installed on your computer”\n· Select Finish\n· It may ask if you want to upgrade from video watcher to video maker \n· Select No Thanks\n· Restart your computer and attempt your test again.\n· If you continue to experience issues after installing Apple QuickTime, you may need to clear the Cache and Cookies. Please follow the steps provided below:\n· Open Mozilla Firefox\n· Select History from the Menu Bar &nbsp; -&nbsp;&nbsp; Press [Alt] + [S] on your keyboard\n· Click on Clear Recent History\n· In the drop-down next to Time Range to Clear\n· Select Everything\n· In the details section, place a check-mark next to Cookies and Cache\n· Click on Clear Now\n· Close completely out of Mozilla Firefox\n· Reopen Mozilla Firefox and attempt your test once more\n\nMacintosh\nWe would recommend using either Safari or Mozilla Firefox for the audio assessments. Below are the troubleshooting steps that should assist you with the audio for your test:\n\nPlease Note: Any Mac with Operating Systems 10.10.5 and above are not compatible with the audio tests and sound will not play. You must take the test from a different computer in this case.\n\nTo find out the Operating System version: Click on the APPLE in the left hand corner, then click on About this Mac. It will display the OS X version 10.#.#\n\nYou will first want to ensure that there are no updates for your computer\n· Click on the Apple icon in the top left hand corner of your screen. \n· Click on Software Update\n· Select Check for Updates\n· If there are any updates you will need to restart the computer and attempt your test again\n· If you continue to experience issues after updating your system, you may need to clear the browser’s Cache and Cookies. Please follow the steps provided for your web-browser:\n\nSafari\n· Open Safari\n· Click on Safari in the top left hand corner of your screen\n· Select Preferences\n· Click on the Advanced tab\n· Place a check-mark next to Show Develop Menu and close this window\n· Select Develop from the Menu bar\n· Click on Empty Caches\n· Close completely out of Safari \n· Reopen Safari and attempt your test again\n\nMozilla Firefox\n· Will also need the specific version of Quicktime previously outlined. Follow the same instructions and go to the same link for the Firefox for Windows installation given above. If you already have Quicktime 7.7, you will need to remove it first. Simply uninstall by searching for the program in the finder and then dragging it to the Trash/Recycle bin on your desktop.\n· Once Quicktime has been installed and the computer restarted follow these steps before you attempt the test again:\no Open Mozilla Firefox\no Select History from the Menu Bar\no Click on Clear Recent History\no In the drop down next to Time Range to Clear, select Everything\no In the details section, place a check-mark next to Cookies and Cache\no Click on Clear Now\no Close completely out of Mozilla Firefox\no Reopen Mozilla Firefox and attempt your test again" ]

[ [ "0a", "hang scan ie8 TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "0b", " Remote scanning using scanner freezes or stops when using Internet Explorer 8 or later. SYMPTOM" ], [ "0c", "Additional symptoms include:" ], [ "0d", " * The web page may crash and recover (close and quickly reopen)." ], [ "0e", " * The freeze may occur during or after scanning the first page. CAUSE" ], [ "0f", "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. ENVIRONMENT" ], [ "0g", "Internet Explorer 8 and later" ], [ "0h", "RESOLVING THE PROBLEM" ], [ "0i", "To disable DEP: 1." ], [ "0j", "In the browser, open the Tools menu, and select Internet Options. 2." ], [ "0k", "Select the Advanced tab. 3." ], [ "0l", "Uncheck Enable memory protection to mitigate online attacks. 4." ], [ "0m", "Close all windows, restart the browser and start scanning again." ], [ "0n", "Note: If using Datacap 8.1, this issue has been fixed in 8.1 Fix Pack 1." ] ]

[ "0b", "0d", "0e", "0f", "0g", "0h", "0i", "0j", "0k", "0l", "0m", "0n" ]

[ "TPAEUI timeout maximo session seconds minutes hours never time logout TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This documentation provides info about changing timeout settings for Test environments. \n\nRESOLVING THE PROBLEM\nMaximo displays a warning message when an user session is about to timeout. (Your session will time out in X seconds). The timeout sets the amount of time the server waits for certain events before failing a request. \n\n[/support/docview.wss?uid=swg21961137&amp;aid=1]\n\nBy default, client sessions are timed out after 30 minutes of inactivity. As per Maximo System Administration guide, in order to change this value, you can edit the web.xml file. \n\nYou will have to find the session-config section and change the session-timeout element to a different value. For example, in the web.xml file, replacing the session-timeout parameter from 30 to 60 increases the timeout period from 30 minutes to 60 minutes.\n\nIncreasing the session-timeout element to a higher value consumes additional memory and that's why it is recommended not to increase to a high value.\n\nHowever, for some internal TEST environments, you may want to disable timeout, to have sessions never time out, since the environment will not be a Production system, and will be intended only for testing.\n\nThat would be possible if you configure the timeout setting to a negative value, such as -1.\n\nThis following instructions outlines the steps to change the timeout settings.\n\n1. Edit web.xml which you will find in the following directory using a simple text editor like Notepad:\n\n...[maximo root]/applications/maximo/maximouiweb/webmodule/WEB-INF\n\n2. Change the value in the session-timeout tag in session-config section as follows, setting the timeout to -1 :\n\n<session-config>\n<!-- The session-timeout element defines the default session timeout interval for all sessions created in this web application. The specified timeout must be expressed in a whole number of minutes. -->\n<session-timeout>-1</session-timeout>\n</session-config>\n\nIn the above example, the session timeout is set for a negative value, which will make sessions to never timeout.\n\n3. Save and close the file.\n\n4. Rebuild and redeploy the maximo EAR file by following the procedure in your Maximo Installation Guide.\n\nShould you need any assistance, please contact IBM Maximo Support\n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21968303]", " TECHNOTE (FAQ)\n\nQUESTION\n How can the timeout value for the WPG console be modified? \n\nCAUSE\nThe default session timeout value of 30 minutes may not be acceptable for some scenarios, e.g. \n\n * Users in secure environments might need shorter session timeout periods to ensure security, in case they leave their machine and forget to log off the console. \n * Users might need longer session timeout periods if they respond slower than typical users for accessibility reasons.\n\n\nANSWER\nThe timeout value for the WPG console can be set in the WAS admin console via Servers -> Application servers -> bcgserver -> Web Container Settings -> Web container -> Session management -> Session timeout. \n\nThe value (default = 30) is provided in minutes.\n[/support/docview.wss?uid=swg21322947&aid=1] [/support/docview.wss?uid=swg21322947&aid=1]\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Partner Gateway Advanced Edition Not Applicable AIX, HP-UX, Linux, Solaris, Windows 6.1.0, 6.1.0.1, 6.1.0.2, 6.1.0.3, 6.1.1 Advanced, Enterprise", " FIXES ARE AVAILABLE\nOperational Decision Manager V8.8.1 Mod Pack [http://www-01.ibm.com/support/docview.wss?uid=swg24042247]\nOperational Decision Manager V8.7.1.2 Fix Pack [http://www-01.ibm.com/support/docview.wss?uid=swg24042348]\nOperational Decision Manager V8.8.1 Download Document [http://www-01.ibm.com/support/docview.wss?uid=swg24042245]\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 * When using the administrative console to tune the session\n timeout , for example to set 120s:\n Enterprise Applications > teamserver-WAS85 > Session management\n > Session Timeout > Set timeout > 120\n Then save, stop teamserver-WAS85, start teamserver-WAS85, the\n application does not start, it is corrupted.\n \n \n \n \n \n\nLOCAL FIX\n * recreate sample server\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Changing session timeout in WAS will stop it and start a\n duplicated applicationConfig created in the deployment\n settings, then the solution is to remove the code that is\n creating this unused/malformed section.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The code is fixed\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n RS02344\n \n \n * REPORTED COMPONENT NAME\n WDS FOR RULES\n \n \n * REPORTED COMPONENT ID\n 5725B6903\n \n \n * REPORTED RELEASE\n 880\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 2016-03-15\n \n \n * CLOSED DATE\n 2016-03-18\n \n \n * LAST MODIFIED DATE\n 2016-03-18\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\nMODULES/MACROS\n * 999\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WDS FOR RULES\n \n \n * FIXED COMPONENT ID\n 5725B6903\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R880 PSY\n UP", " 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", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n \nPerformance to retrieve users from LDAP server can be improved using ibm-allGroups parameter. It is also important to understand the settings for security cache timeout as it is related to refresh interval for the security cache. \n\nRESOLVING THE PROBLEM\nCertain directory servers like IBM® Tivoli Directory Server allow client to directly query user's group membership from user entry's attributes. The group membership is an operational attribute, and it is available on demand. In IBM directory server, a group membership lookup could be done by searching the ibm-allGroups attribute for the user entry. When client provides a valid LTPA token, WebSphere® Application Server will make 3 LDAP calls to map the Token to a validated security subject, however, the 3 LDAP calls can be reduced to 1 by using ibm-allGroups parameter. Significant performance improvements were noticed on the LDAP server with ibm-allGroups parameter setting in WebSphere Application Server..\n\nThis parameter can be set on WebSphere Application Server admin console:\nSecurity > User Registries > LDAP Advanced LDAP settings. On the LDAP settings panel change the Group Member ID Map setting to the following value: ibm-allGroups:member;ibm-allGroups:uniqueMember\n\nSecurity Cache Timeout:\nThe size of the security cache is related to the credential/subject A credential is an internal representation of a validated user. Credential size can significantly increase if a user belongs to many groups. So it is not desirable to have too many groups for a member.\nSecurity authentication cache can reduce and delay calls to directory servers and thus provide performance improvements. The security cache timeout value specifies how long an inactive security credential stays in the security cache. The security cache timeout value is relative to the last active time of the credential. The timeout setting specifies how often to refresh the security-related caches. The credential is refreshed and a new one is created once the credential is close to security cache timeout value and at that time a call to LDAP will be made. \n\nThis parameter can be set on WAS admin console:\nSecurity->Global security->cache timeout\n\nCredential:\n\nA credential is an internal representation of a validated user, and it contains at least following attributes: \n\nrealmname (like wasLDAP.ibm.com:636); \nusername (like testUser) \nuniqueusername (like uid=testuser,dc=austin,dc=ibm,dc=com) \nprimaryGroupId (like group:wasLDAP.ibm.com:636/cn=my primary group,dc=austin,dc=ibm,dc=com) \naccessId (user:wasLDAP.ibm.com:636/uid=testuser,dc=austin,dc=ibm,dc=com) \ncredential Tokens \nexpirationTime \nAll groupIds (list all groups a user belongs to, and realm is appended to each group) \n\n\nCache keys include:\nrealm:user\nrealm:uniqueSecurityName\nLTPA token\nrealm:loginName \nadditional keys. \n\nA credential lives in security cache no less than security cache timeout value, and no more than 1.5* security cache timeout value. For example, if the security cache size for one user is C, and total concurrent users are T, the cache size is about (1 + 1.5)/2*C*T = 1.25*C*T. Security cache timeout calculation is different from LTPA expiration, while LTPA token expiration is not reset once it is time stamped, the security cache timeout is reset when it is referenced. So security cache timeout is the timeout since last referenced. \n\nQuestion: \nWhat are the consequences on the memory of WebSphere Application Server if a user is in many groups for example 500 groups? What is considered a large group? \nAnswer:\nUser's group memberships are included in user's credential. If a user belongs to too many groups, credential size will be increased significantly, as a result, the credential cache size becomes big. We suggest to limit the number of groups a user belongs to. \n\nQuestion: \nWhat are the consequences of setting the security cache from 10 minutes to 1 hour?\nAnswer:\n10 minutes are considered the minimal timeout. A good starting point for security cache timeout value is 10 minutes, however this can vary based on client requirements. Cache timeout too small will force credential removed too often, and may refresh credential many times even before a user session is completed. Too large cache timeout will result in too many users in cache, and consume too much memory. User has to make a compromise, and choose a proper value that fits their environment.\n\nQuestion:\nHow does the cache get flushed? Is it by entry? When? \nAnswer:\nCredential cache could be flushed out in two ways. One is when it is accessed, and \ncredential is expired. If a user access an expired or about to be expired credential, the credential would be removed from cache. We also have a background monitor to remove credential out of cache if the credential is not referenced in certain time period, which is greater than security cache timeout value but less than 1.5* security cache timeout value.\n\nQuestion:\nWhen a new LTPAToken is created (and added to the cache), does this imply that the credential (WSCredential in the cache) is recreated (or updated, especially the expiration attribute)? \nAnswer: \nIf logging in with a new token (i.e., the token is not exactly the same old token), a new credential would be created. \n\nQuestion:\nWhat are the relations between cache time-out and the other time-out?\nAnswer:\nSecurity Cache timeout value determines how long a credential will live in cache if it is not referenced directly. The other security related timeout is LTPA Token expiration time. The ltpa expiration specifies how long a token is validated since it is created. Generally, we recommend LTPA expiration time greater than 2*security cache timeout value. If a credential is in cache and its ltpa token is expired, and if a user accesses this credential, this credential would be removed first, then user will be asked to re-authenticate itself. \n\n \n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK" ]

[ [ "3a", " TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "3b", " How to resolve \"Transaction timed out after 601 seconds\" error while performing certain operations in Rule Team Server (RTS)/Decision Center (DC)? SYMPTOM" ], [ "3c", "While generating ruleapps in RTS/DC, the following error is thrown after a few minutes (typically 5 or 10 minutes): On WebLogic:" ], [ "3d", "Rule Team Server has encountered an unexpected error." ], [ "3e", "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." ], [ "3f", "[Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 601 seconds BEA1-5057DF8C316E1C1224CD]'." ], [ "3g", "No further JDBC access is allowed within this transaction. ... On WebSphere:" ], [ "3h", "TimeoutManage I WTRN0006W: Transaction XXX has timed out after 300 seconds." ], [ "3i", "TimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 3,5,main]." ], [ "3j", "The stack trace of this thread when the timeout occurred was: ilog.rules.brl.parsing.parser.earley.IlrEarleyParser.errorRecovery(IlrEarleyParser.java:1046) ilog.rules.brl.parsing.parser.earley.IlrEarleyParser.buildCharts(IlrEarleyParser.java:772) ilog.rules.brl.parsing.parser.earley.IlrEarleyParser.parse(IlrEarleyParser.java:511) ... CAUSE" ], [ "3k", "The transaction timeout for RTS/DC is set to 10 minutes by default in the teamserver web module deployment descriptor (WEB-INF/web.xml), and application servers also have container level transaction timeouts that are configurable." ], [ "3l", "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." ], [ "3m", "RESOLVING THE PROBLEM" ], [ "3n", "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." ], [ "3o", "You will find the property in the file web.xml defined as below: ... <context-param>" ], [ "3p", "<description>Modify the timeout value that is associated with transactions (in seconds)</description> <param-name>ilog.rules.teamserver.transaction.timeout</param-name> <param-value>600</param-value> </context-param> ..." ], [ "3q", "Another place to look for are application server specific transaction timeout configurations." ], [ "3r", "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]." ], [ "3s", "Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Platform Independent 7.5 Enterprise Business Integration IBM Operational Decision Manager Platform Independent 8.0.1, 8.0 Enterprise" ] ]

[ "3k", "3n", "3o" ]

[ " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n I am running the Sentinel 8.1 License Manager to manage my licenses for SPSS 16, a few older versions of SPSS and some non-SPSS programs. I have set up my license manager to allow for commuter licenses. I am able to check out commuter licenses on machines running older versions of SPSS, but not for SPSS 16. There is no error message - I simply click on the commuter option and nothing happens.\n\nFor troubleshooting purposes I used a # character to comment out the non-SPSS licenses from the lservrc file in the license manager, restarted the license manager service, and I was then was able to check out Statistics commuter licenses. This, however, is inconvenient because I really need to have all of my programs monitored by the same server. How can I get around this problem? \n\nRESOLVING THE PROBLEM\nThis issue was resolved in SPSS Statistics version 18.0.\n\n \n\nHISTORICAL NUMBER\n 77043", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n I am attempting to check out a network license of SPSS for Windows on my laptop. Spsscommute.exe displays the modules, but renders no commutable licenses (0 out of 0 left). I can launch SPSS for Windows and obtain a license. What is the problem? \n\nRESOLVING THE PROBLEM\nCommuter licensing must be enabled on the machine where the SPSS Sentinel License Manager resides. \n\n1. Right-click My Computer and choose Properties.\n\n2. Click the Advanced tab and select Environment Variables.\n\n3. Locate the LSERVOPTS system variable and edit it. Find the \"-com 0\" parameter and either remove it to make all network licenses commutable or change the value to the percentage of licenses you want to be commutable. A valid value is between 0 and 100.\n\n4. Restart the computer\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]\n\n\n \n\nHISTORICAL NUMBER\n 59091", " TECHNOTE (FAQ)\n\nQUESTION\n How do I transfer my IBM SPSS product/software license from one machine to another? \n\nANSWER\nIt is not possible, nor required, to transfer a license from an existing product installation to a new product installation in order to use the product on a new host machine/computer. \nDue to the nature of the IBM SPSS software licensing technology, a license created for use on one product host machine/computer can not be used on a different host machine/computer. \n\nUnless otherwise specified in your IBM software licensing agreement, the following is the case:\n\n\n * A valid Authorized User product authorization code can be used to license up to two (2) product installations used by the same individual. \n * A valid Site license allows for more than one user to license product installations using the same authorization code. \n * Compliance with your IBM software licensing agreement does not require a transfer of a license from one host machine/computer to a different one. \n * Compliance with your IBM software licensing agreement does not require the previously installed IBM SPSS product to be uninstalled in order to install and license the same product on a new host machine/computer. \n * Compliance with your IBM software licensing agreement does not require the removal of the license of the previously installed product. \n * Compliance with your IBM software licensing agreement does not require the return of previously issued licenses.\n\n\nNote: Copying/pasting the installed software folders/files from one host machine/computer to another will not result in a working version of the product. \n\nIf you wish to install and license an IBM SPSS product on a new computer, you need only: \n\n1. Install the software on the new host machine/computer. * If you downloaded your software from IBM.com, you can move the .zip file from the old machine to the new. Please make sure to extract the files from the .zip file before beginning the install.\n \n * If you need to download the software, a number of tutorial videos are available here [http://www.ibm.com/software/passportadvantage/PassportAdvantageOnlinevideos.html]. \n\n2. License the software on the new host machine/computer. \n * If you have authorization code for the product, you may use this authorization code. \n * If you are using a pre-existing authorization code and receive a 'You are not allowed to generate any more new licenses' message, instructions for resolving this issue can be found here. [http://www.ibm.com/support/docview.wss?uid=swg21480566] \n * If you do not have an authorization code for the product, instructions for creating an authorization code can be found here. [http://www-01.ibm.com/support/docview.wss?uid=swg21980065] \n * If you have more than one authorization code available to you, instructions for confirming the authorization code can be found make sure you are here [http://www.ibm.com/support/docview.wss?uid=swg21486143]. \n\nComplete! \n\nYou should now be able to run your software. \n\nIf encounter a problem, please contact IBM SPSS Support. \n\nThere are multiple ways to contact support. \n\nYour support contact depends on the Support Contract you chose at time of purchase. \n * Customers with current support contracts can open a Support Request on Support Portal [https://www.ibm.com/support/home/?lnk=msdTS-supo-usen]. \n * Everyone can use the Predictive Analytics Community Licensing Forums [https://developer.ibm.com/answers/topics/spsslicensing.html] to do the same. \n * Students can use the Predictive Analytics Community Student Forums [https://developer.ibm.com/answers/topics/spssstudent.html].\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Modeler", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n I am running SPSS Custom Tables. I have a multiple response group in the rows of the table. I'd like to get a chi-square or a column proportions test on this multiple response group, but SPSS doesn't allow me to do so. How can I test column proportions or run a chi-square test on my table? \n\nRESOLVING THE PROBLEM\nSPSS 14 now allows for inferential statistics of Custom Tables that have multiple response groups in them. If you do not have SPSS 14 for Windows, please contact your local SPSS Sales office for a copy.\n\nSPSS previously did not allow for inferential statistical testing on multiple response groups since such statistics violate certain assumptions. For example, one of the assumptions in doing a chi-square is that the responses of the row variables are independent from each other. A multiple response group violates that basic assumption. As such, the chi-square statistic will be inflated. \n\nThe same assumption on independence is made for the test of column proportions. If, for example, we had a variable on a five-point scale, and we had a dichotomous variable in the column, we could do a test of proportions because, in a sense, we're testing the proportion of one row (such as \"Strongly Agree\") against the other rows. But with a multiple response group the same respondent would probably have responses in more than one cell in the five-point multiple-response scale, and the statistics as such would be on somewhat shaky ground\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 41795", " TECHNOTE (FAQ)\n\nQUESTION\n I am using IBM SPSS/PASW Statistics for Windows and am trying to use syntax to order the bars in a bar chart based on the statistic. I know that I can make this change to the chart after I've created it, but I'm not sure how to make this modification prior to chart creation. Can this be done? \n\nANSWER\nYes, it is possible to modify the Graphics Production Language (GPL) so that the chart is sorted based upon the statistic at creation time. You will change the SCALE variable to sort.statistic(summary.mean)(Varname))). Note that the varname will be your variable name as defined in the GPL. \n\nBelow is an example using the \"Employee Data.sav\" dataset. \n\n* Sort bars by statistic before chart creation.\nGGRAPH\n/GRAPHDATASET NAME=\"graphdataset\" VARIABLES=educ MEAN(id)[name=\n\"MEAN_id\"] MISSING=LISTWISE REPORTMISSING=NO\n/GRAPHSPEC SOURCE=INLINE.\nBEGIN GPL\nSOURCE: s=userSource(id(\"graphdataset\"))\nDATA: educ=col(source(s), name(\"educ\"), unit.category())\nDATA: MEAN_id=col(source(s), name(\"MEAN_id\"))\nGUIDE: axis(dim(1), label(\"Here is the new title on the X-Axis\"))\nGUIDE: axis(dim(2), label(\"Mean Employee Code\"))\nSCALE: cat(dim(1), sort.statistic(summary.mean(MEAN_id)))\nSCALE: linear(dim(2), include(0))\nELEMENT: interval(position(educ*MEAN_id), shape.interior(shape.square))\nEND GPL\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 69675" ]

[ [ "2a", " TECHNOTE (FAQ) QUESTION" ], [ "2b", " How do I transfer my IBM SPSS product/software license from one machine to another? ANSWER" ], [ "2c", "It is not possible, nor required, to transfer a license from an existing product installation to a new product installation in order to use the product on a new host machine/computer." ], [ "2d", "Due to the nature of the IBM SPSS software licensing technology, a license created for use on one product host machine/computer can not be used on a different host machine/computer." ], [ "2e", "Unless otherwise specified in your IBM software licensing agreement, the following is the case:" ], [ "2f", " * A valid Authorized User product authorization code can be used to license up to two (2) product installations used by the same individual." ], [ "2g", " * A valid Site license allows for more than one user to license product installations using the same authorization code." ], [ "2h", " * Compliance with your IBM software licensing agreement does not require a transfer of a license from one host machine/computer to a different one." ], [ "2i", " * Compliance with your IBM software licensing agreement does not require the previously installed IBM SPSS product to be uninstalled in order to install and license the same product on a new host machine/computer." ], [ "2j", " * Compliance with your IBM software licensing agreement does not require the removal of the license of the previously installed product." ], [ "2k", " * Compliance with your IBM software licensing agreement does not require the return of previously issued licenses." ], [ "2l", "Note: Copying/pasting the installed software folders/files from one host machine/computer to another will not result in a working version of the product." ], [ "2m", "If you wish to install and license an IBM SPSS product on a new computer, you need only: 1." ], [ "2n", "Install the software on the new host machine/computer." ], [ "2o", "* If you downloaded your software from IBM.com, you can move the .zip file from the old machine to the new." ], [ "2p", "Please make sure to extract the files from the .zip file before beginning the install." ], [ "2q", " * If you need to download the software, a number of tutorial videos are available here [http://www.ibm.com/software/passportadvantage/PassportAdvantageOnlinevideos.html]. 2." ], [ "2r", "License the software on the new host machine/computer." ], [ "2s", " * If you have authorization code for the product, you may use this authorization code." ], [ "2t", " * If you are using a pre-existing authorization code and receive a 'You are not allowed to generate any more new licenses' message, instructions for resolving this issue can be found here. [http://www.ibm.com/support/docview.wss?uid=swg21480566]" ], [ "2u", " * If you do not have an authorization code for the product, instructions for creating an authorization code can be found here. [http://www-01.ibm.com/support/docview.wss?uid=swg21980065]" ], [ "2v", " * If you have more than one authorization code available to you, instructions for confirming the authorization code can be found make sure you are here [http://www.ibm.com/support/docview.wss?uid=swg21486143]. Complete!" ], [ "2w", "You should now be able to run your software." ], [ "2x", "If encounter a problem, please contact IBM SPSS Support." ], [ "2y", "There are multiple ways to contact support." ], [ "2z", "Your support contact depends on the Support Contract you chose at time of purchase." ], [ "2aa", " * Customers with current support contracts can open a Support Request on Support Portal [https://www.ibm.com/support/home/?lnk=msdTS-supo-usen]." ], [ "2ab", " * Everyone can use the Predictive Analytics Community Licensing Forums [https://developer.ibm.com/answers/topics/spsslicensing.html] to do the same." ], [ "2ac", " * Students can use the Predictive Analytics Community Student Forums [https://developer.ibm.com/answers/topics/spssstudent.html]." ], [ "2ad", "Cross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Modeler" ] ]

[ "2a", "2b", "2c", "2d", "2e", "2f", "2g", "2h", "2i", "2j", "2k", "2l", "2m", "2n", "2o", "2p", "2r", "2s", "2t", "2u", "2v", "2w", "2x", "2y", "2z", "2aa", "2ab" ]

[ " FIXES ARE AVAILABLE\nPM13911; 7.0.0.7: Problems using SQL Server as a data store [http://www-01.ibm.com/support/docview.wss?uid=swg24027230]\n7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX [http://www-01.ibm.com/support/docview.wss?uid=swg24027977]\n7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX [http://www-01.ibm.com/support/docview.wss?uid=swg24027999]\n7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i [http://www-01.ibm.com/support/docview.wss?uid=swg24028000]\n7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux [http://www-01.ibm.com/support/docview.wss?uid=swg24028001]\n7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris [http://www-01.ibm.com/support/docview.wss?uid=swg24028002]\n7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24028003]\n7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24028004]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX [http://www-01.ibm.com/support/docview.wss?uid=swg24028875]\n7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24028881]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX [http://www-01.ibm.com/support/docview.wss?uid=swg24029071]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i [http://www-01.ibm.com/support/docview.wss?uid=swg24029072]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux [http://www-01.ibm.com/support/docview.wss?uid=swg24029073]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris [http://www-01.ibm.com/support/docview.wss?uid=swg24029074]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24029075]\n7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17 [http://www-01.ibm.com/support/docview.wss?uid=swg24029634]\n7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24029894]\n7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19 [http://www-01.ibm.com/support/docview.wss?uid=swg24030660]\n7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21 [http://www-01.ibm.com/support/docview.wss?uid=swg24031366]\n7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23 [http://www-01.ibm.com/support/docview.wss?uid=swg24032493]\n7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25 [http://www-01.ibm.com/support/docview.wss?uid=swg24033267]\n7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27 [http://www-01.ibm.com/support/docview.wss?uid=swg24033882]\n7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29 [http://www-01.ibm.com/support/docview.wss?uid=swg24034966]\n7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31 [http://www-01.ibm.com/support/docview.wss?uid=swg24036768]\n7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24035324]\n7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33 [http://www-01.ibm.com/support/docview.wss?uid=swg24037573]\n7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35 [http://www-01.ibm.com/support/docview.wss?uid=swg24038310]\n7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37 [http://www-01.ibm.com/support/docview.wss?uid=swg24039338]\n7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39 [http://www-01.ibm.com/support/docview.wss?uid=swg24041013]\n7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41 [http://www-01.ibm.com/support/docview.wss?uid=swg24041931]\n7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43 [http://www-01.ibm.com/support/docview.wss?uid=swg24043400]\n7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45 [http://www-01.ibm.com/support/docview.wss?uid=swg24044551]\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 * One of the following problems are seen using\n Microsoft SQL Server as the data store for a Service\n Integration Bus messaging engine:\n \n * If an attempt is made to start a messaging engine\n against a schema that does not exist, the messaging engine\n fails to start even though the \"Create tables\" checkbox\n is ticked and all necessary authority to create the\n schema has been granted.\n For other databases, the schema is automatically created\n under these circumstances.\n \n * If an attempt is made to run the DDL generated by\n by the sibDDLGenerator against a schema that does not\n exist, the DDL fails to create the tables for the\n messaging engine.\n For other databases, the generated DDL contains\n DDL to create the schema if it does not exist.\n \n * The sibDDLGenerator tool fails if '2008' is specified\n as the database version.\n \n * The following exception occurs and prevents startup of the\n messaging engine, when using a JDBC Version 2.0 driver:\n CWSIS1530E: The data type, -9, was found instead of the\n expected type, 12, for column, URI, in table,\n IBMWSSIB.SSIBCLASSMAP.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: Users of the default messaging provider for *\n * IBM WebSphere Application Server using *\n * Microsoft SQL Server as the data store *\n * for a Service Integration Bus messaging *\n * engine *\n ****************************************************************\n * PROBLEM DESCRIPTION: Cannot configure Microsoft SQL Server *\n * as a data store when using a JDBC 2.0 *\n * driver, or without manually creating *\n * the schema *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n The behavior of the Service Integration Bus is incorrect for\n Microsoft SQL Server in the following ways:\n * The \"Create tables\" tickbox does not cause the messaging\n engine to automatically create the schema if it does not exist\n * The sibDDLGenerator tool does not generate DDL to create\n the schema for the messaging engine\n * The sibDDLGenerator tool does not allow '2008' to be\n specified as a database version for Microsoft SQL Server\n * A messaging engine fails to start when a JDBC 2.0 driver\n is used to connect to the database\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The fix for this APAR corrects issues as follows, when\n using Microsoft SQL Server as a data store:\n * A messaging engine will automatically create a messaging\n engine's schema during startup if:\n 1) It does not exist\n 2) The \"Create tables\" tickbox is enabled\n 3) The authority to query the existing schemas is available,\n using a SELECT query against SYS.SCHEMAS\n 4) The authority to issue the CREATE SCHEMA command\n is available.\n * The DDL generated by the sibDDLGenerator for Microsoft\n SQL Server includes commands to create the schema.\n * The sibDDLGenerator tool accepts '2008' as a valid version\n when combined with system 'sqlserver'\n * A messaging engine can start successfully against a\n data store hosted in Microsoft SQL Server, when using\n a JDBC 2.0 driver.\n \n The fix for this APAR is currently targeted for inclusion in\n fix pack 7.0.0.13. 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 PM13911\n \n \n * REPORTED COMPONENT NAME\n PLAT MSG COM\n \n \n * REPORTED COMPONENT ID\n 620800101\n \n \n * REPORTED RELEASE\n 300\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 2010-05-06\n \n \n * CLOSED DATE\n 2010-06-21\n \n \n * LAST MODIFIED DATE\n 2010-06-21\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 PLAT MSG COM\n \n \n * FIXED COMPONENT ID\n 620800101\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R300 PSY\n UP", " FIXES ARE AVAILABLE\n8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24035935]\n8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24037250]\n8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24038133]\n8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24038539]\n8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24039425]\n8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040035]\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.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 * A Service Integration Bus (SIB) Message Engine fails to start\n when using Microsoft SQL Server 2005 for the data store.\n SibMessage E ME name ] CWSIS0002E: The messaging engine\n encountered an exception while starting.\n \n Exception: com.ibm.ws.sib.msgstore.PersistenceException:\n CWSIS1501E: The data source has produced an unexpected\n exception:com.microsoft.sqlserver.jdbc.SQLServerException:\n Column,parameter, or variable #5: Cannot find data type\n DATETIME2.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: Users of the default messaging provider *\n * for IBM WebSphere Application Server *\n * version 8.5. *\n ****************************************************************\n * PROBLEM DESCRIPTION: Messaging engine (ME) cannot start in *\n * if Microsoft SQL Server 2005 is *\n * configured as a datastore. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n Messaging engine (ME) fails to start in WebSphere Application\n Server V8.5 if Microsoft SQL Server 2005 database is\n configured as a datastore. This is due to incompatible\n datatype \"DATETIME2\" which is valid from SQLServer 2008\n version and above. \"DATETIME2\" datatype for SQLServer was\n introduced in WebSphere Application Server V8.5 to store the\n ME's last database updated timestamp.\n This problem is only applicable with WebSphere Application\n Server V8.5 with Microsoft SQL Server version 2005 database.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Source code has been modified to change the data type as\n \"DATETIME\" which is compatible with SQL Server 2005 version\n and above versions.\n \n The fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.5.1. 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 PM85314\n \n \n * REPORTED COMPONENT NAME\n WAS SIB & SIBWS\n \n \n * REPORTED COMPONENT ID\n 620800101\n \n \n * REPORTED RELEASE\n 300\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 2013-03-21\n \n \n * CLOSED DATE\n 2013-06-11\n \n \n * LAST MODIFIED DATE\n 2013-06-11\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 WAS SIB & SIBWS\n \n \n * FIXED COMPONENT ID\n 620800101\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R850 PSY\n UP", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n I.T. administrator logs onto the Controller application server, and launches 'IBM Cognos Controller Configuration'. Administrator selects 'Database connections for publish to datamart', and chooses the relevant database connection. Administrator fills in the sections (for example 'Provider', 'User ID', 'Password' etc) and clicks 'save'. \n\nAdministrator receives error message. \n\nSYMPTOM\n[/support/docview.wss?uid=swg21367341&amp;aid=1] \n\nThe specified database and the publish for datamart database don't have the same provider.\n\n\nCAUSE\nController only supports publishing datamarts to the same type of database as the application's repository database.\n\nIn other words, the following are supported: \n\n * Microsoft SQL application repository (source) <=supported_publish=> MS SQL data mart (target) \n * Oracle application repository <=supported_publish=> Oracle data mart target \n * DB2 application repository <=supported_publish=> DB2 data mart target.\n\nENVIRONMENT\nThe source database (the Controller application database repository) uses one provider (for example DB2's IBMDADB2.DB2COPY1)... \n\n[/support/docview.wss?uid=swg21367341&aid=2] [/support/docview.wss?uid=swg21367341&aid=2]\n\n...but the Data Mart (target) is configured to use a different provider (for example Microsoft SQL's SQLNCLI11.1):\n[/support/docview.wss?uid=swg21367341&aid=3] [/support/docview.wss?uid=swg21367341&aid=3]\n\n\nRESOLVING THE PROBLEM\nEnsure that the same values for 'provider' as in both the 'application' database connections and 'data mart' connections configuration sections.\n\n \n\nHISTORICAL NUMBER\n 1041446", "RN7.5; RN7.5.0.2; RN7.5.0.1; SRX; cannot connect to server; cannot customize workflows TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n To customize workflows for lifecycles in IBM Rational Asset Manager, the included IBM Rational Team Concert server must connect to a Rational Team Concert Eclipse client. If you use a Rational Team Concert V2.0.0.2 Eclipse client to connect to the Rational Team Concert server, the connection might work but then fail, and error messages are displayed. \n\nSYMPTOM\nThe messages might be like these messages: \n\n * DSRA1300E: Feature is not implemented: javax.sql.PooledConnection.addStatementEventListener \n * DSRA8230W: The application server is unable to determine if a transaction should be resolved because data source custom property nonTransactionalDataSource is configured but data source custom property commitOrRollbackOnCleanup is not configured\n \n In a typical SQL Server installation on IBM WebSphere Application Server V7, you might see the DSRA1300E message several times. The message is displayed every time a new connection to the SQL Server database is made. However, if you see a high number of these messages, the database connections are not being shared and are not being returned to WebSphere Application Server. \n\nENVIRONMENT\nThis issue occurs in an environment that uses SQL Server 2008, WebSphere Application Server V7, and the Rational Team Concert server in Rational Asset Manager V7.5.\n\n\n\nRESOLVING THE PROBLEM\n\n\n 1. In the Rational Team Concert V2.0.0.2 Eclipse client, make sure that the repository connection is specified. For example: https://hostname_of_rtc_server:9443/jazz \n 2. \n 3. In the WebSphere Application Server administration console, add the defaultConnectionTypeOverride property, and set the value to unshared. If you are using the embedded version of WebSphere Application Server, you can add the property in the resources.xml file.", " TECHNOTE (FAQ)\n\nQUESTION\n Do IBM WebSphere Application Server versions prior to V6.1 work with Microsoft SQL Server 2005? \n\nANSWER\nWebSphere Application Server versions prior to V6.1 were written to be compatible with the Microsoft SQL Server 2000 database. However, Microsoft SQL Server 2005 is not fully forward compatible from Microsoft SQL Server 2000, and therefore WebSphere Application Server versions prior to V6.1 are not fully compatible with Microsoft SQL Server 2005. \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n\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 z/OS 6.0" ]

[ [ "0a", " FIXES ARE AVAILABLE" ], [ "0b", "PM13911; 7.0.0.7: Problems using SQL Server as a data store [http://www-01.ibm.com/support/docview.wss?uid=swg24027230]" ], [ "0c", "7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX [http://www-01.ibm.com/support/docview.wss?uid=swg24027977]" ], [ "0d", "7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX [http://www-01.ibm.com/support/docview.wss?uid=swg24027999]" ], [ "0e", "7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i [http://www-01.ibm.com/support/docview.wss?uid=swg24028000]" ], [ "0f", "7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux [http://www-01.ibm.com/support/docview.wss?uid=swg24028001]" ], [ "0g", "7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris [http://www-01.ibm.com/support/docview.wss?uid=swg24028002]" ], [ "0h", "7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24028003]" ], [ "0i", "7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24028004]" ], [ "0j", "7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX [http://www-01.ibm.com/support/docview.wss?uid=swg24028875]" ], [ "0k", "7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24028881]" ], [ "0l", "7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX [http://www-01.ibm.com/support/docview.wss?uid=swg24029071]" ], [ "0m", "7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i [http://www-01.ibm.com/support/docview.wss?uid=swg24029072]" ], [ "0n", "7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux [http://www-01.ibm.com/support/docview.wss?uid=swg24029073]" ], [ "0o", "7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris [http://www-01.ibm.com/support/docview.wss?uid=swg24029074]" ], [ "0p", "7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24029075]" ], [ "0q", "7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17 [http://www-01.ibm.com/support/docview.wss?uid=swg24029634]" ], [ "0r", "7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24029894]" ], [ "0s", "7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19 [http://www-01.ibm.com/support/docview.wss?uid=swg24030660]" ], [ "0t", "7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21 [http://www-01.ibm.com/support/docview.wss?uid=swg24031366]" ], [ "0u", "7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23 [http://www-01.ibm.com/support/docview.wss?uid=swg24032493]" ], [ "0v", "7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25 [http://www-01.ibm.com/support/docview.wss?uid=swg24033267]" ], [ "0w", "7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27 [http://www-01.ibm.com/support/docview.wss?uid=swg24033882]" ], [ "0x", "7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29 [http://www-01.ibm.com/support/docview.wss?uid=swg24034966]" ], [ "0y", "7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31 [http://www-01.ibm.com/support/docview.wss?uid=swg24036768]" ], [ "0z", "7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24035324]" ], [ "0aa", "7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33 [http://www-01.ibm.com/support/docview.wss?uid=swg24037573]" ], [ "0ab", "7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35 [http://www-01.ibm.com/support/docview.wss?uid=swg24038310]" ], [ "0ac", "7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37 [http://www-01.ibm.com/support/docview.wss?uid=swg24039338]" ], [ "0ad", "7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39 [http://www-01.ibm.com/support/docview.wss?uid=swg24041013]" ], [ "0ae", "7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41 [http://www-01.ibm.com/support/docview.wss?uid=swg24041931]" ], [ "0af", "7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43 [http://www-01.ibm.com/support/docview.wss?uid=swg24043400]" ], [ "0ag", "7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45 [http://www-01.ibm.com/support/docview.wss?uid=swg24044551] SUBSCRIBE" ], [ "0ah", "You can track all active APARs for this component. APAR STATUS" ], [ "0ai", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "0aj", " * One of the following problems are seen using" ], [ "0ak", " Microsoft SQL Server as the data store for a Service" ], [ "0al", " Integration Bus messaging engine:" ], [ "0am", " * If an attempt is made to start a messaging engine" ], [ "0an", " against a schema that does not exist, the messaging engine" ], [ "0ao", " fails to start even though the \"Create tables\" checkbox" ], [ "0ap", " is ticked and all necessary authority to create the" ], [ "0aq", " schema has been granted." ], [ "0ar", " For other databases, the schema is automatically created" ], [ "0as", " under these circumstances." ], [ "0at", " * If an attempt is made to run the DDL generated by" ], [ "0au", " by the sibDDLGenerator against a schema that does not" ], [ "0av", " exist, the DDL fails to create the tables for the" ], [ "0aw", " messaging engine." ], [ "0ax", " For other databases, the generated DDL contains" ], [ "0ay", " DDL to create the schema if it does not exist." ], [ "0az", " * The sibDDLGenerator tool fails if '2008' is specified" ], [ "0ba", " as the database version." ], [ "0bb", " * The following exception occurs and prevents startup of the" ], [ "0bc", " messaging engine, when using a JDBC Version 2.0 driver:" ], [ "0bd", " CWSIS1530E: The data type, -9, was found instead of the" ], [ "0be", " expected type, 12, for column, URI, in table," ], [ "0bf", " IBMWSSIB.SSIBCLASSMAP. LOCAL FIX PROBLEM SUMMARY" ], [ "0bg", " * ****************************************************************" ], [ "0bh", " * USERS AFFECTED: Users of the default messaging provider for *" ], [ "0bi", " * IBM WebSphere Application Server using *" ], [ "0bj", " * Microsoft SQL Server as the data store *" ], [ "0bk", " * for a Service Integration Bus messaging *" ], [ "0bl", " * engine *" ], [ "0bm", " ****************************************************************" ], [ "0bn", " * PROBLEM DESCRIPTION: Cannot configure Microsoft SQL Server *" ], [ "0bo", " * as a data store when using a JDBC 2.0 *" ], [ "0bp", " * driver, or without manually creating *" ], [ "0bq", " * the schema *" ], [ "0br", " ****************************************************************" ], [ "0bs", " * RECOMMENDATION: *" ], [ "0bt", " ****************************************************************" ], [ "0bu", " The behavior of the Service Integration Bus is incorrect for" ], [ "0bv", " Microsoft SQL Server in the following ways:" ], [ "0bw", " * The \"Create tables\" tickbox does not cause the messaging" ], [ "0bx", " engine to automatically create the schema if it does not exist" ], [ "0by", " * The sibDDLGenerator tool does not generate DDL to create" ], [ "0bz", " the schema for the messaging engine" ], [ "0ca", " * The sibDDLGenerator tool does not allow '2008' to be" ], [ "0cb", " specified as a database version for Microsoft SQL Server" ], [ "0cc", " * A messaging engine fails to start when a JDBC 2.0 driver" ], [ "0cd", " is used to connect to the database PROBLEM CONCLUSION" ], [ "0ce", " * The fix for this APAR corrects issues as follows, when" ], [ "0cf", " using Microsoft SQL Server as a data store:" ], [ "0cg", " * A messaging engine will automatically create a messaging" ], [ "0ch", " engine's schema during startup if:" ], [ "0ci", " 1) It does not exist" ], [ "0cj", " 2) The \"Create tables\" tickbox is enabled" ], [ "0ck", " 3) The authority to query the existing schemas is available," ], [ "0cl", " using a SELECT query against SYS.SCHEMAS" ], [ "0cm", " 4) The authority to issue the CREATE SCHEMA command" ], [ "0cn", " is available." ], [ "0co", " * The DDL generated by the sibDDLGenerator for Microsoft" ], [ "0cp", " SQL Server includes commands to create the schema." ], [ "0cq", " * The sibDDLGenerator tool accepts '2008' as a valid version" ], [ "0cr", " when combined with system 'sqlserver'" ], [ "0cs", " * A messaging engine can start successfully against a" ], [ "0ct", " data store hosted in Microsoft SQL Server, when using" ], [ "0cu", " a JDBC 2.0 driver." ], [ "0cv", " The fix for this APAR is currently targeted for inclusion in" ], [ "0cw", " fix pack 7.0.0.13." ], [ "0cx", "Please refer to the Recommended Updates" ], [ "0cy", " page for delivery information:" ], [ "0cz", " http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980] TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "0da", " * APAR NUMBER" ], [ "0db", " PM13911" ], [ "0dc", " * REPORTED COMPONENT NAME" ], [ "0dd", " PLAT MSG COM" ], [ "0de", " * REPORTED COMPONENT ID" ], [ "0df", " 620800101" ], [ "0dg", " * REPORTED RELEASE" ], [ "0dh", " 300" ], [ "0di", " * STATUS" ], [ "0dj", " CLOSED PER" ], [ "0dk", " * PE" ], [ "0dl", " NoPE" ], [ "0dm", " * HIPER" ], [ "0dn", " NoHIPER" ], [ "0do", " * SPECIAL ATTENTION" ], [ "0dp", " NoSpecatt" ], [ "0dq", " * SUBMITTED DATE" ], [ "0dr", " 2010-05-06" ], [ "0ds", " * CLOSED DATE" ], [ "0dt", " 2010-06-21" ], [ "0du", " * LAST MODIFIED DATE" ], [ "0dv", " 2010-06-21" ], [ "0dw", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "0dx", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "0dy", " * FIXED COMPONENT NAME" ], [ "0dz", " PLAT MSG COM" ], [ "0ea", " * FIXED COMPONENT ID" ], [ "0eb", " 620800101" ], [ "0ec", "APPLICABLE COMPONENT LEVELS" ], [ "0ed", " * R300 PSY" ], [ "0ee", " UP" ] ]

[ "0ah", "0ai", "0bh", "0bu", "0bw", "0bx", "0by", "0bz", "0ce", "0cv", "0cw", "4b", "4c", "4d" ]

[ " FIXES ARE AVAILABLE\nPM13911; 7.0.0.7: Problems using SQL Server as a data store [http://www-01.ibm.com/support/docview.wss?uid=swg24027230]\n7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX [http://www-01.ibm.com/support/docview.wss?uid=swg24027977]\n7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX [http://www-01.ibm.com/support/docview.wss?uid=swg24027999]\n7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i [http://www-01.ibm.com/support/docview.wss?uid=swg24028000]\n7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux [http://www-01.ibm.com/support/docview.wss?uid=swg24028001]\n7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris [http://www-01.ibm.com/support/docview.wss?uid=swg24028002]\n7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24028003]\n7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24028004]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX [http://www-01.ibm.com/support/docview.wss?uid=swg24028875]\n7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24028881]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX [http://www-01.ibm.com/support/docview.wss?uid=swg24029071]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i [http://www-01.ibm.com/support/docview.wss?uid=swg24029072]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux [http://www-01.ibm.com/support/docview.wss?uid=swg24029073]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris [http://www-01.ibm.com/support/docview.wss?uid=swg24029074]\n7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24029075]\n7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17 [http://www-01.ibm.com/support/docview.wss?uid=swg24029634]\n7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24029894]\n7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19 [http://www-01.ibm.com/support/docview.wss?uid=swg24030660]\n7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21 [http://www-01.ibm.com/support/docview.wss?uid=swg24031366]\n7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23 [http://www-01.ibm.com/support/docview.wss?uid=swg24032493]\n7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25 [http://www-01.ibm.com/support/docview.wss?uid=swg24033267]\n7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27 [http://www-01.ibm.com/support/docview.wss?uid=swg24033882]\n7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29 [http://www-01.ibm.com/support/docview.wss?uid=swg24034966]\n7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31 [http://www-01.ibm.com/support/docview.wss?uid=swg24036768]\n7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24035324]\n7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33 [http://www-01.ibm.com/support/docview.wss?uid=swg24037573]\n7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35 [http://www-01.ibm.com/support/docview.wss?uid=swg24038310]\n7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37 [http://www-01.ibm.com/support/docview.wss?uid=swg24039338]\n7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39 [http://www-01.ibm.com/support/docview.wss?uid=swg24041013]\n7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41 [http://www-01.ibm.com/support/docview.wss?uid=swg24041931]\n7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43 [http://www-01.ibm.com/support/docview.wss?uid=swg24043400]\n7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45 [http://www-01.ibm.com/support/docview.wss?uid=swg24044551]\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 * One of the following problems are seen using\n Microsoft SQL Server as the data store for a Service\n Integration Bus messaging engine:\n \n * If an attempt is made to start a messaging engine\n against a schema that does not exist, the messaging engine\n fails to start even though the \"Create tables\" checkbox\n is ticked and all necessary authority to create the\n schema has been granted.\n For other databases, the schema is automatically created\n under these circumstances.\n \n * If an attempt is made to run the DDL generated by\n by the sibDDLGenerator against a schema that does not\n exist, the DDL fails to create the tables for the\n messaging engine.\n For other databases, the generated DDL contains\n DDL to create the schema if it does not exist.\n \n * The sibDDLGenerator tool fails if '2008' is specified\n as the database version.\n \n * The following exception occurs and prevents startup of the\n messaging engine, when using a JDBC Version 2.0 driver:\n CWSIS1530E: The data type, -9, was found instead of the\n expected type, 12, for column, URI, in table,\n IBMWSSIB.SSIBCLASSMAP.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: Users of the default messaging provider for *\n * IBM WebSphere Application Server using *\n * Microsoft SQL Server as the data store *\n * for a Service Integration Bus messaging *\n * engine *\n ****************************************************************\n * PROBLEM DESCRIPTION: Cannot configure Microsoft SQL Server *\n * as a data store when using a JDBC 2.0 *\n * driver, or without manually creating *\n * the schema *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n The behavior of the Service Integration Bus is incorrect for\n Microsoft SQL Server in the following ways:\n * The \"Create tables\" tickbox does not cause the messaging\n engine to automatically create the schema if it does not exist\n * The sibDDLGenerator tool does not generate DDL to create\n the schema for the messaging engine\n * The sibDDLGenerator tool does not allow '2008' to be\n specified as a database version for Microsoft SQL Server\n * A messaging engine fails to start when a JDBC 2.0 driver\n is used to connect to the database\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The fix for this APAR corrects issues as follows, when\n using Microsoft SQL Server as a data store:\n * A messaging engine will automatically create a messaging\n engine's schema during startup if:\n 1) It does not exist\n 2) The \"Create tables\" tickbox is enabled\n 3) The authority to query the existing schemas is available,\n using a SELECT query against SYS.SCHEMAS\n 4) The authority to issue the CREATE SCHEMA command\n is available.\n * The DDL generated by the sibDDLGenerator for Microsoft\n SQL Server includes commands to create the schema.\n * The sibDDLGenerator tool accepts '2008' as a valid version\n when combined with system 'sqlserver'\n * A messaging engine can start successfully against a\n data store hosted in Microsoft SQL Server, when using\n a JDBC 2.0 driver.\n \n The fix for this APAR is currently targeted for inclusion in\n fix pack 7.0.0.13. 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 PM13911\n \n \n * REPORTED COMPONENT NAME\n PLAT MSG COM\n \n \n * REPORTED COMPONENT ID\n 620800101\n \n \n * REPORTED RELEASE\n 300\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 2010-05-06\n \n \n * CLOSED DATE\n 2010-06-21\n \n \n * LAST MODIFIED DATE\n 2010-06-21\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 PLAT MSG COM\n \n \n * FIXED COMPONENT ID\n 620800101\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R300 PSY\n UP", " FIXES ARE AVAILABLE\n8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24035935]\n8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24037250]\n8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24038133]\n8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24038539]\n8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24039425]\n8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040035]\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.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 * A Service Integration Bus (SIB) Message Engine fails to start\n when using Microsoft SQL Server 2005 for the data store.\n SibMessage E ME name ] CWSIS0002E: The messaging engine\n encountered an exception while starting.\n \n Exception: com.ibm.ws.sib.msgstore.PersistenceException:\n CWSIS1501E: The data source has produced an unexpected\n exception:com.microsoft.sqlserver.jdbc.SQLServerException:\n Column,parameter, or variable #5: Cannot find data type\n DATETIME2.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: Users of the default messaging provider *\n * for IBM WebSphere Application Server *\n * version 8.5. *\n ****************************************************************\n * PROBLEM DESCRIPTION: Messaging engine (ME) cannot start in *\n * if Microsoft SQL Server 2005 is *\n * configured as a datastore. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n Messaging engine (ME) fails to start in WebSphere Application\n Server V8.5 if Microsoft SQL Server 2005 database is\n configured as a datastore. This is due to incompatible\n datatype \"DATETIME2\" which is valid from SQLServer 2008\n version and above. \"DATETIME2\" datatype for SQLServer was\n introduced in WebSphere Application Server V8.5 to store the\n ME's last database updated timestamp.\n This problem is only applicable with WebSphere Application\n Server V8.5 with Microsoft SQL Server version 2005 database.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Source code has been modified to change the data type as\n \"DATETIME\" which is compatible with SQL Server 2005 version\n and above versions.\n \n The fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.5.1. 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 PM85314\n \n \n * REPORTED COMPONENT NAME\n WAS SIB & SIBWS\n \n \n * REPORTED COMPONENT ID\n 620800101\n \n \n * REPORTED RELEASE\n 300\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 2013-03-21\n \n \n * CLOSED DATE\n 2013-06-11\n \n \n * LAST MODIFIED DATE\n 2013-06-11\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 WAS SIB & SIBWS\n \n \n * FIXED COMPONENT ID\n 620800101\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R850 PSY\n UP", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n I.T. administrator logs onto the Controller application server, and launches 'IBM Cognos Controller Configuration'. Administrator selects 'Database connections for publish to datamart', and chooses the relevant database connection. Administrator fills in the sections (for example 'Provider', 'User ID', 'Password' etc) and clicks 'save'. \n\nAdministrator receives error message. \n\nSYMPTOM\n[/support/docview.wss?uid=swg21367341&amp;aid=1] \n\nThe specified database and the publish for datamart database don't have the same provider.\n\n\nCAUSE\nController only supports publishing datamarts to the same type of database as the application's repository database.\n\nIn other words, the following are supported: \n\n * Microsoft SQL application repository (source) <=supported_publish=> MS SQL data mart (target) \n * Oracle application repository <=supported_publish=> Oracle data mart target \n * DB2 application repository <=supported_publish=> DB2 data mart target.\n\nENVIRONMENT\nThe source database (the Controller application database repository) uses one provider (for example DB2's IBMDADB2.DB2COPY1)... \n\n[/support/docview.wss?uid=swg21367341&aid=2] [/support/docview.wss?uid=swg21367341&aid=2]\n\n...but the Data Mart (target) is configured to use a different provider (for example Microsoft SQL's SQLNCLI11.1):\n[/support/docview.wss?uid=swg21367341&aid=3] [/support/docview.wss?uid=swg21367341&aid=3]\n\n\nRESOLVING THE PROBLEM\nEnsure that the same values for 'provider' as in both the 'application' database connections and 'data mart' connections configuration sections.\n\n \n\nHISTORICAL NUMBER\n 1041446", "RN7.5; RN7.5.0.2; RN7.5.0.1; SRX; cannot connect to server; cannot customize workflows TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n To customize workflows for lifecycles in IBM Rational Asset Manager, the included IBM Rational Team Concert server must connect to a Rational Team Concert Eclipse client. If you use a Rational Team Concert V2.0.0.2 Eclipse client to connect to the Rational Team Concert server, the connection might work but then fail, and error messages are displayed. \n\nSYMPTOM\nThe messages might be like these messages: \n\n * DSRA1300E: Feature is not implemented: javax.sql.PooledConnection.addStatementEventListener \n * DSRA8230W: The application server is unable to determine if a transaction should be resolved because data source custom property nonTransactionalDataSource is configured but data source custom property commitOrRollbackOnCleanup is not configured\n \n In a typical SQL Server installation on IBM WebSphere Application Server V7, you might see the DSRA1300E message several times. The message is displayed every time a new connection to the SQL Server database is made. However, if you see a high number of these messages, the database connections are not being shared and are not being returned to WebSphere Application Server. \n\nENVIRONMENT\nThis issue occurs in an environment that uses SQL Server 2008, WebSphere Application Server V7, and the Rational Team Concert server in Rational Asset Manager V7.5.\n\n\n\nRESOLVING THE PROBLEM\n\n\n 1. In the Rational Team Concert V2.0.0.2 Eclipse client, make sure that the repository connection is specified. For example: https://hostname_of_rtc_server:9443/jazz \n 2. \n 3. In the WebSphere Application Server administration console, add the defaultConnectionTypeOverride property, and set the value to unshared. If you are using the embedded version of WebSphere Application Server, you can add the property in the resources.xml file.", " TECHNOTE (FAQ)\n\nQUESTION\n Do IBM WebSphere Application Server versions prior to V6.1 work with Microsoft SQL Server 2005? \n\nANSWER\nWebSphere Application Server versions prior to V6.1 were written to be compatible with the Microsoft SQL Server 2000 database. However, Microsoft SQL Server 2005 is not fully forward compatible from Microsoft SQL Server 2000, and therefore WebSphere Application Server versions prior to V6.1 are not fully compatible with Microsoft SQL Server 2005. \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n\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 z/OS 6.0" ]

[ [ "4a", " TECHNOTE (FAQ) QUESTION" ], [ "4b", " Do IBM WebSphere Application Server versions prior to V6.1 work with Microsoft SQL Server 2005? ANSWER" ], [ "4c", "WebSphere Application Server versions prior to V6.1 were written to be compatible with the Microsoft SQL Server 2000 database." ], [ "4d", "However, Microsoft SQL Server 2005 is not fully forward compatible from Microsoft SQL Server 2000, and therefore WebSphere Application Server versions prior to V6.1 are not fully compatible with Microsoft SQL Server 2005. * * * * * * * * * * * * *" ], [ "4e", "Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK Application Servers WebSphere Application Server for z/OS z/OS 6.0" ] ]

[ "0ah", "0ai", "0bh", "0bu", "0bw", "0bx", "0by", "0bz", "0ce", "0cv", "0cw", "4b", "4c", "4d" ]

[ " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * A message flow configured to make an ODBC connection to a\n Microsoft SQL Server database using Kerberos authentication\n fails with the following java IllegalArgumentException error:\n \n BIP3701E: A Java exception was thrown whilst calling the Java\n JNI method 'com_ibm_broker_security_MbKerberosHelper_kinit'. The\n Java exception was 'java.lang.IllegalArgumentException: wrong\n number of arguments'. The Java stack trace was\n 'Frame : 0 java.lang.IllegalArgumentException: wrong number of\n arguments|\n @: sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native\n Method)|\n @:\n sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeCons\n tructorAccessorImpl.java:86)|\n @:\n sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Delega\n tingConstructorAccessorImpl.java:58)|\n @:\n java.lang.reflect.Constructor.newInstance(Constructor.java:542)|\n @:\n com.ibm.broker.security.MbKerberosHelper.kinit(MbKerberosHelper.\n java:54)|'.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of IBM Integration Bus version 10 or App Connect\n Enterprise v11 using Kerberos authentication with ODBC\n connections to Microsoft SQL Server.\n \n \n Platforms affected:\n MultiPlatform\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n A message flow configured to make an ODBC connection to a\n Microsoft SQL Server database using Kerberos authentication\n fails with the following java IllegalArgumentException error:\n \n BIP3701E: A Java exception was thrown whilst calling the Java\n JNI method 'com_ibm_broker_security_MbKerberosHelper_kinit'. The\n Java exception was 'java.lang.IllegalArgumentException: wrong\n number of arguments'. The Java stack trace was\n 'Frame : 0 java.lang.IllegalArgumentException: wrong number of\n arguments|\n @:\n sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeMet\n hod)|\n @:\n sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeCons\n tructorAccessorImpl.java:86)|\n @:\n sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Delega\n tingConstructorAccessorImpl.java:58)|\n @:\n java.lang.reflect.Constructor.newInstance(Constructor.java:542)|\n @:\n com.ibm.broker.security.MbKerberosHelper.kinit(MbKerberosHelper.\n java:54)|'.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The product now correctly calls the kinit API.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v10.0 10.0.0.13\n v11.0 11.0.0.1\n \n The latest available maintenance can be obtained from:\n http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]\n \n If the maintenance level is not yet available,information on\n its planned availability can be found on:\n http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT24371\n \n \n * REPORTED COMPONENT NAME\n INTEGRATION BUS\n \n \n * REPORTED COMPONENT ID\n 5724J0540\n \n \n * REPORTED RELEASE\n A00\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 2018-03-14\n \n \n * CLOSED DATE\n 2018-06-13\n \n \n * LAST MODIFIED DATE\n 2018-06-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 INTEGRATION BUS\n \n \n * FIXED COMPONENT ID\n 5724J0540\n \n \n\nAPPLICABLE COMPONENT LEVELS", "z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * If WBI-FN MSIF receives a File which contains a blank in the\n FileInfo Tag (e.g.:\n <Sw:FileInfo>SwCompression=None; ;Test=Y</Sw:FileInfo>\n \n Error events\n \n DNFO1057E 8/17/09 11:45:53 AM GEBAC DNF_O_FT\n c3e2d840e6d4c9f14040404040404040c4a64c4830d4038c Processing the\n message of type SNL_SERVER (SNL Sw:HandleFileRequest) failed for\n 'RCV'\n request 'Initial' in state 'Initial' and condition 'new'; see\n event 'DNFO9501E' for more information.\n DNFO9501E 8/17/09 11:45:53 AM GEBAC DNF_O_FT\n c3e2d840e6d4c9f14040404040404040c4a64c4830d4038c Internal\n error;\n reason='org.w3c.dom.DOMException: INVALID_CHARACTER_ERR: An\n invalid or illegal XML character is specified. '.\n \n are raised, and CIN stops processing;\n continue of File processing (successful CIN restart) is only\n possible after deleting the request message for this transfer\n from the Queue.\n \n \n \n \n \n\nLOCAL FIX\n * Contact the sender of the file and ask to specify FileInfo as\n defined by SWIFT\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users *\n ****************************************************************\n * PROBLEM DESCRIPTION: CIN STOPS ON RECEIVING A FILE WITH A *\n * BLANK IN FILEINFO TAG *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n Formerly, when WebSphere BI for FN MSIF received a file which\n contained a blank in the FileInfo tag, error events DNFO1057E\n and DNFO9501E were raised, and CIN stopped processing. To\n continue file processing (successful CIN restart) was possible\n only after deleting the request message for this transfer\n from the queue. That required to contact the sender of the\n file and ask to specify FileInfo as defined by SWIFT.\n Now, the behaviour is changed.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * CIN STOPS ON RECEIVING A FILE WITH A BLANK IN FILEINFO TAG\n This behaviour is changed.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PK94119\n \n \n * REPORTED COMPONENT NAME\n MS FOR SN IA AN\n \n \n * REPORTED COMPONENT ID\n 5655FIN02\n \n \n * REPORTED RELEASE\n 31F\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 2009-08-18\n \n \n * CLOSED DATE\n 2009-10-08\n \n \n * LAST MODIFIED DATE\n 2009-11-04\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 PK96255 [http://www-01.ibm.com/support/docview.wss?uid=swg1PK96255] UK50785\n \n \n\nMODULES/MACROS\n * DNF10062 DNF10063 DNF10065\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n MS FOR SN IA AN\n \n \n * FIXED COMPONENT ID\n 5655FIN02\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R31F PSY UK50785 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK50785]\n UP09/10/10 P F910\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.", " A FIX IS AVAILABLE\nIBM WebSphere Business Modeler Advanced V7.0.0.0 Fix Pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24026455]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS FIXED IF NEXT.\n \n \n \n\nERROR DESCRIPTION\n * Using the namespace http://dummy/2009 the log shows this error\n on export to WID:\n \n ----------------------------------------------------------------\n \n !MESSAGE RunExportAction:RunExportAction: exception caught\n java.lang.reflect.InvocationTargetException\n \n !MESSAGE RunExportAction:RunExportAction: exception caused by\n org.w3c.dom.DOMException: INVALID_CHARACTER_ERR: An invalid or\n illegal XML character is specified.\n ----------------------------------------------------------------\n \n \n With namespace http://dummy/a2009 everything works fine.\n \n \n \n \n \n\nLOCAL FIX\n * -\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Fix to be delivered in Modeler 7.0.0.2, targetting beginning 2nd\n quarter 2010.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n * Test fix delivered to single customer\n \n \n \n \n \n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n JR35225\n \n \n * REPORTED COMPONENT NAME\n WBI MODELER AE\n \n \n * REPORTED COMPONENT ID\n 5724I7500\n \n \n * REPORTED RELEASE\n 700\n \n \n * STATUS\n CLOSED FIN\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 2009-12-23\n \n \n * CLOSED DATE\n 2010-01-26\n \n \n * LAST MODIFIED DATE\n 2010-01-26\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\nAPPLICABLE COMPONENT LEVELS\n * R700 PSY\n UP", " SUBSCRIBE\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 * In WebSphere Application Server V6, the performance servlet\n (PerfServlet) outputs performance data using the J2EE 1.4\n Performance Data Framework by default. However, it can provide\n output in the WebSphere V5 format when the 'version=5' parameter\n is specified:\n http://hostname/wasPerfTool/servlet/perfservlet?version=5 [http://hostname/wasPerfTool/servlet/perfservlet?version=5]\n .\n This may result in illegal XML characters being output by the\n PerfServlet, causing the following error to appear in the web\n browser:\n .\n org.w3c.dom.DOMException: INVALID_CHARACTER_ERR: An\n invalid or illegal XML character is specified.\n at org.apache.xerces.dom.CoreDocumentImpl.createElement(Unknown\n Source)\n at com.ibm.ws.pmi.perfServlet60.XmlPrinter.generateStats(XmlPri\n nter.java:359)\n ...\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: WebSphere Application Server version 6.0 *\n * Performance Servlet users querying version 5 *\n * format output containing xml characters *\n * '%' or '!' (percent sign or exclamation *\n * point). *\n ****************************************************************\n * PROBLEM DESCRIPTION: Illegal xml character exceptions *\n * thrown when requesting version 5 *\n * format output including the '%' or '!' *\n * characters. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n Illegal xml character exceptions thrown when requesting\n version 5 format output including the '%' or '!' characters.\n These characters were in the list of characters filtered.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Simply added '%' and '!' to the list of characters that are\n filtered from the element and/or attribute creation process.\n \n Target fixpack: 6.0.2.11\n Please refer to the recommended updates page for delivery\n 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 PK23814\n \n \n * REPORTED COMPONENT NAME\n WEBSPH APP SERV\n \n \n * REPORTED COMPONENT ID\n 5724J0800\n \n \n * REPORTED RELEASE\n 60A\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 2006-04-21\n \n \n * CLOSED DATE\n 2006-04-24\n \n \n * LAST MODIFIED DATE\n 2006-05-25\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\nMODULES/MACROS\n * PMI\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WEBSPH APP SERV\n \n \n * FIXED COMPONENT ID\n 5724J0800\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R60A PSY\n UP\n \n \n * R60H PSY\n UP\n \n \n * R60I PSY\n UP\n \n \n * R60P PSY\n UP\n \n \n * R60S PSY\n UP\n \n \n * R60W PSY\n UP\n \n \n * R60Z PSY\n UP", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n SI executes a SFTP Get service using parm \"RemoteFilePattern\" and the filename contains a wild card to pull all available files, the files are not retrieved and the BP hangs in Waiting_On_IO. This problem occurs attempting to get a file and the filename contains a space. When this situation occurs the SI SFTP Client log for the SFTP Get service will post error 'INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified.' \n\n\nSYMPTOM\nThe SFTP Client log during the SFTP Get post error 'INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified.' \n\nSFTP Get service attempt to retrieve a filename but the file is not retrieved, the BP hangs in Waiting_On_IO and must be manually terminated.\n\n\nCAUSE\nSFTP Get service to retrieve a file and the filename contains a space, for example a filename of positions.txt 2 (see space is just prior to the 2). \nThis has been identified as a product defect under APAR IC96126.\n\nDIAGNOSING THE PROBLEM\nAs a workaround, recommend using an underscore in the filename instead of using a space. \n\nRESOLVING THE PROBLEM\nApply APAR IC96126.\n\n \n\nHISTORICAL NUMBER\n 382687" ]

[ [ "0a", " SUBSCRIBE TO THIS APAR" ], [ "0b", "By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available." ], [ "0c", "You can track this item individually or track all items by product." ], [ "0d", "Notify me when this APAR changes." ], [ "0e", "Notify me when an APAR for this component changes. APAR STATUS" ], [ "0f", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "0g", " * A message flow configured to make an ODBC connection to a" ], [ "0h", " Microsoft SQL Server database using Kerberos authentication" ], [ "0i", " fails with the following java IllegalArgumentException error:" ], [ "0j", " BIP3701E: A Java exception was thrown whilst calling the Java" ], [ "0k", " JNI method 'com_ibm_broker_security_MbKerberosHelper_kinit'. The" ], [ "0l", " Java exception was 'java.lang.IllegalArgumentException: wrong" ], [ "0m", " number of arguments'." ], [ "0n", "The Java stack trace was" ], [ "0o", " 'Frame : 0 java.lang.IllegalArgumentException: wrong number of" ], [ "0p", " arguments|" ], [ "0q", " @: sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native" ], [ "0r", " Method)|" ], [ "0s", " @:" ], [ "0t", " sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeCons" ], [ "0u", " tructorAccessorImpl.java:86)|" ], [ "0v", " @:" ], [ "0w", " sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Delega" ], [ "0x", " tingConstructorAccessorImpl.java:58)|" ], [ "0y", " @:" ], [ "0z", " java.lang.reflect.Constructor.newInstance(Constructor.java:542)|" ], [ "0aa", " @:" ], [ "0ab", " com.ibm.broker.security.MbKerberosHelper.kinit(MbKerberosHelper." ], [ "0ac", " java:54)|'. LOCAL FIX PROBLEM SUMMARY" ], [ "0ad", " * ****************************************************************" ], [ "0ae", " USERS AFFECTED:" ], [ "0af", " All users of IBM Integration Bus version 10 or App Connect" ], [ "0ag", " Enterprise v11 using Kerberos authentication with ODBC" ], [ "0ah", " connections to Microsoft SQL Server." ], [ "0ai", " Platforms affected:" ], [ "0aj", " MultiPlatform" ], [ "0ak", " ****************************************************************" ], [ "0al", " PROBLEM DESCRIPTION:" ], [ "0am", " A message flow configured to make an ODBC connection to a" ], [ "0an", " Microsoft SQL Server database using Kerberos authentication" ], [ "0ao", " fails with the following java IllegalArgumentException error:" ], [ "0ap", " BIP3701E: A Java exception was thrown whilst calling the Java" ], [ "0aq", " JNI method 'com_ibm_broker_security_MbKerberosHelper_kinit'. The" ], [ "0ar", " Java exception was 'java.lang.IllegalArgumentException: wrong" ], [ "0as", " number of arguments'." ], [ "0at", "The Java stack trace was" ], [ "0au", " 'Frame : 0 java.lang.IllegalArgumentException: wrong number of" ], [ "0av", " arguments|" ], [ "0aw", " @:" ], [ "0ax", " sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeMet" ], [ "0ay", " hod)|" ], [ "0az", " @:" ], [ "0ba", " sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeCons" ], [ "0bb", " tructorAccessorImpl.java:86)|" ], [ "0bc", " @:" ], [ "0bd", " sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Delega" ], [ "0be", " tingConstructorAccessorImpl.java:58)|" ], [ "0bf", " @:" ], [ "0bg", " java.lang.reflect.Constructor.newInstance(Constructor.java:542)|" ], [ "0bh", " @:" ], [ "0bi", " com.ibm.broker.security.MbKerberosHelper.kinit(MbKerberosHelper." ], [ "0bj", " java:54)|'. PROBLEM CONCLUSION" ], [ "0bk", " * The product now correctly calls the kinit API." ], [ "0bl", " ---------------------------------------------------------------" ], [ "0bm", " The fix is targeted for delivery in the following PTFs:" ], [ "0bn", " Version Maintenance Level" ], [ "0bo", " v10.0 10.0.0.13" ], [ "0bp", " v11.0 11.0.0.1" ], [ "0bq", " The latest available maintenance can be obtained from:" ], [ "0br", " http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041]" ], [ "0bs", " If the maintenance level is not yet available,information on" ], [ "0bt", " its planned availability can be found on:" ], [ "0bu", " http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308]" ], [ "0bv", " --------------------------------------------------------------- TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "0bw", " * APAR NUMBER" ], [ "0bx", " IT24371" ], [ "0by", " * REPORTED COMPONENT NAME" ], [ "0bz", " INTEGRATION BUS" ], [ "0ca", " * REPORTED COMPONENT ID" ], [ "0cb", " 5724J0540" ], [ "0cc", " * REPORTED RELEASE" ], [ "0cd", " A00" ], [ "0ce", " * STATUS" ], [ "0cf", " CLOSED PER" ], [ "0cg", " * PE" ], [ "0ch", " NoPE" ], [ "0ci", " * HIPER" ], [ "0cj", " NoHIPER" ], [ "0ck", " * SPECIAL ATTENTION" ], [ "0cl", " NoSpecatt / Xsystem" ], [ "0cm", " * SUBMITTED DATE" ], [ "0cn", " 2018-03-14" ], [ "0co", " * CLOSED DATE" ], [ "0cp", " 2018-06-13" ], [ "0cq", " * LAST MODIFIED DATE" ], [ "0cr", " 2018-06-13" ], [ "0cs", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "0ct", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "0cu", " * FIXED COMPONENT NAME" ], [ "0cv", " INTEGRATION BUS" ], [ "0cw", " * FIXED COMPONENT ID" ], [ "0cx", " 5724J0540" ], [ "0cy", "APPLICABLE COMPONENT LEVELS" ] ]

[ "0af", "0ag", "0ai", "0ak", "0ao", "0aq", "0bk", "0bn", "0bo", "0bp" ]

[ " SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition that is shipped with IBM WebSphere Application Server for Bluemix. These issues were disclosed as part of the IBM Java SDK updates in January 2016 and includes the vulnerability commonly referred to as \"SLOTH\". \n\nVULNERABILITY DETAILS\nThis bulletin covers all applicable Java SE CVE's published by Oracle as part of their January 2016 Critical Patch Update which affects IBM SDK, Java Technology Edition. There are other advisories included in the IBM Java SDK but WebSphere Application Server is not vulnerable to them. You will need to evaluate your own code to determine if you are vulnerable. Please refer to the Reference section for more information on the advisories not applicable to WebSphere Application Server. \n\nCVEID:CVE-2016-0475 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0475]\nDESCRIPTION:An unspecified vulnerability related to the Libraries component has partial confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 5.8\nCVSS Temporal Score: Seehttps://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\nCVEID:CVE-2016-0466 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0466]\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: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/109948 [https://exchange.xforce.ibmcloud.com/vulnerabilities/109948]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-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. This vulnerability is commonly known as \"SLOTH\".\nCVSS Base Score: 7.1\nCVSS Temporal Score: Seehttps://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/UI:U/C:H/I:L/A:N) \n\nCVEID:CVE-2016-0448 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0448]\nDESCRIPTION:An unspecified vulnerability related to the JMX component could allow a remote attacker to obtain sensitive information.\nCVSS Base Score: 4\nCVSS Temporal Score: Seehttps://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\nAFFECTED PRODUCTS AND VERSIONS\nThis vulnerability affects the following versions and releases of IBM WebSphere Application Server for Bluemix: \n\n * Version 8.5.5 Full Profile and Liberty Profile \n * Version 8.0 \n\nREMEDIATION/FIXES\nTo patch an existing service instance refer to the IBM WebSphere Application Server bulletin: Security Bulletin: Multiple vulnerabilities in IBM® Java SDK affect WebSphere Application Server January 2016 CPU (CVE-2016-0475, CVE-2016-0466, CVE-2015-7575, CVE-2016-0448) [http://www-01.ibm.com/support/docview.wss?uid=swg21975424]\n\nAlternatively, delete the vulnerable service instance and create a new instance. The new maintenance will be included.\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] \nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] Oracle's January 2016 CPU Advisory [http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html#AppendixJAVA] \nIBM SDK, Java Technology Edition Security Alerts page [http://www.ibm.com/developerworks/java/jdk/alerts/] 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\nCVE-2015-7575 was reported to IBM by Karthikeyan Bhargavan at INRIA in Paris, France \n\nCHANGE HISTORY\n 19 February 2016: 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.", " SECURITY BULLETIN\n\nSUMMARY\n OpenSSL vulnerabilities were disclosed on September 22, 2016 and September 26, 2016 by the OpenSSL Project. OpenSSL is used by IBM Community Server Server. IBM Community Server has addressed the applicable CVEs. \n\nVULNERABILITY DETAILS\n\nCVEID: CVE-2016-6303 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6303]\nDESCRIPTION:\nOpenSSL is vulnerable to a denial of service, caused by an integer overflow in the MDC2_Update function. By using unknown attack vectors, a remote attacker could exploit this vulnerability to trigger an out-of-bounds write and cause the application to crash.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117023 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117023] 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-2182 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2182]\nDESCRIPTION:\nOpenSSL is vulnerable to a denial of service, caused by an out-of-bounds write in the TS_OBJ_print_bio function in crypto/bn/bn_print.c. A remote attacker could exploit this vulnerability using a specially crafted value to cause the application to crash.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116342 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116342] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L)\n\nCVEID: CVE-2016-2178 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2178]\nDESCRIPTION:\nOpenSSL 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\nCVEID: CVE-2016-6302 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6302]\nDESCRIPTION:\nOpenSSL is vulnerable to a denial of service, caused by the failure to consider the HMAC size during validation of the ticket length by the tls_decrypt_ticket function A remote attacker could exploit this vulnerability using a ticket that is too short to cause a denial of service.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117024 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117024] 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-6304\nDESCRIPTION:\nOpenSSL is vulnerable to a denial of service, caused by multiple memory leaks in t1_lib.c during session renegotiation. By sending an overly large OCSP Status Request extension, a remote attacker could exploit this vulnerability to consume all available memory resources.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117110 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117110] 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\nCVEID: CVE-2016-2179 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2179]\nDESCRIPTION:\nOpenSSL is vulnerable to a denial of service. By sending specially crafted DTLS record fragments to fill up buffer queues, a remote attacker could exploit this vulnerability to open a large number of simultaneous connections and consume all available memory resources.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116343 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116343] 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-6306 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6306]\nDESCRIPTION:\nOpenSSL is vulnerable to a denial of service, caused by missing message length checks when parsing certificates. A remote authenticated attacker could exploit this vulnerability to trigger an out-of-bounds read and cause a denial of service.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117112 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117112] 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\nCVEID: CVE-2016-2177 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2177]\nDESCRIPTION:\nOpenSSL 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-2180 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2180]\nDESCRIPTION:\nOpenSSL is vulnerable to a denial of service, caused by an out-of-bounds read in the TS_OBJ_print_bio function. A remote attacker could exploit this vulnerability using a specially crafted time-stamp file to cause the application to crash.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/115829 [https://exchange.xforce.ibmcloud.com/vulnerabilities/115829] 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\nCVEID: CVE-2016-2181 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2181]\nDESCRIPTION:\nOpenSSL is vulnerable to a denial of service, caused by an error in the DTLS replay protection implementation. By sending a specially crafted sequence number, a remote attacker could exploit this vulnerability to cause valid packets to be dropped.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116344 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116344] 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:\nOpenSSL 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\nIBM Sametime Community Server aersion 9 HF1\n\nREMEDIATION/FIXES\nUpgrade to Sametime 9.0.1 FP1 - http://www.ibm.com/support/docview.wss?uid=swg22004587 [http://www.ibm.com/support/docview.wss?uid=swg22004587]\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 August 25. 2017 - First 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.", " SECURITY BULLETIN\n\nSUMMARY\n PowerKVM is affected by numerous vulnerabilities in OpenSSL. IBM has now addressed these vulnerabilities. \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\nCVEID: CVE-2016-2179 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2179]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service. By sending specially crafted DTLS record fragments to fill up buffer queues, a remote attacker could exploit this vulnerability to open a large number of simultaneous connections and consume all available memory resources.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116343 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116343] 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-2180 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2180]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an out-of-bounds read in the TS_OBJ_print_bio function. A remote attacker could exploit this vulnerability using a specially crafted time-stamp file to cause the application to crash.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/115829 [https://exchange.xforce.ibmcloud.com/vulnerabilities/115829] 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\nCVEID: CVE-2016-2181 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2181]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an error in the DTLS replay protection implementation. By sending a specially crafted sequence number, a remote attacker could exploit this vulnerability to cause valid packets to be dropped.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116344 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116344] 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-2182 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2182]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an out-of-bounds write in the TS_OBJ_print_bio function in crypto/bn/bn_print.c. A remote attacker could exploit this vulnerability using a specially crafted value to cause the application to crash.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116342 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116342] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L) \n\nCVEID: CVE-2016-6302 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6302]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by the failure to consider the HMAC size during validation of the ticket length by the tls_decrypt_ticket function A remote attacker could exploit this vulnerability using a ticket that is too short to cause a denial of service.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117024 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117024] 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-6304 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6304]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service. By repeatedly requesting renegotiation, a remote authenticated attacker could send an overly large OCSP Status Request extension to consume all available memory resources.\nCVSS Base Score: 6.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117110 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117110] 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\nCVEID: CVE-2016-6306 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6306]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by missing message length checks when parsing certificates. A remote authenticated attacker could exploit this vulnerability to trigger an out-of-bounds read and cause a denial of service.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117112 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117112] 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\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 in the Triple-DES on 64-bit block 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\nPowerKVM 2.1 and PowerKVM 3.1\n\nREMEDIATION/FIXES\nCustomers can update PowerKVM systems by using \"yum update\". \n\nFix images are made available via Fix Central. For version 3.1, see https://ibm.biz/BdHggw [https://ibm.biz/BdHggw]. This issue is addressed as of 3.1.0.2 update 3 or later. \n\nFor version 2.1, see https://ibm.biz/BdEnT8 [https://ibm.biz/BdEnT8]. This issue is addressed as of PowerKVM 2.1.1.3-65 update 13 or later. Customers running v2.1 are, in any case, encouraged to upgrade to v3.1. \n\nFor v2.1 systems currently running fix levels of PowerKVM prior to 2.1.1, please see http://download4.boulder.ibm.com/sar/CMA/OSA/05e4c/0/README [http://download4.boulder.ibm.com/sar/CMA/OSA/05e4c/0/README] for prerequisite fixes and instructions.\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 5 October 2016 - 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.", "WMB IIB SECURITY BULLETIN\n\nSUMMARY\n OpenSSL vulnerabilities were disclosed on September 22, September 26, and November 10, 2016 by the OpenSSL Project. The DataDirect ODBC Drivers used by WebSphere Message Broker and IBM Integration Bus have addressed the applicable CVEs. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-6303 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6303]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an integer overflow in the MDC2_Update function. By using unknown attack vectors, a remote attacker could exploit this vulnerability to trigger an out-of-bounds write and cause the application to crash.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117023 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117023] 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-2182 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2182]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an out-of-bounds write in the TS_OBJ_print_bio function in crypto/bn/bn_print.c. A remote attacker could exploit this vulnerability using a specially crafted value to cause the application to crash.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116342 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116342] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L) \n\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\nCVEID: CVE-2016-6306 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6306]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by missing message length checks when parsing certificates. A remote authenticated attacker could exploit this vulnerability to trigger an out-of-bounds read and cause a denial of service.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117112 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117112] 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\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-2016-7055 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7055]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an error in a Broadwell-specific Montgomery multiplication procedure. By sending specially crafted data, a remote attacker could exploit this vulnerability to trigger errors in public-key operations in configurations where multiple remote clients select an affected EC algorithm and cause a denial of service.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118748 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118748] 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, V9 \n\nWebSphere Message Broker V8\n\nREMEDIATION/FIXES\n\nFor users of ODBC SSL using the DataDirect drivers:\n\n\n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus\n\n\nV10\n\nIT17992 The APAR is available in fix pack 10.0.0.8\nhttps://www.ibm.com/support/docview.wss?uid=swg24043443 [https://www.ibm.com/support/docview.wss?uid=swg24043443] IBM Integration Bus\n\n\nV9\n\nIT17992 The APAR is available in fix pack 9.0.0.7 [https://www-304.ibm.com/support/docview.wss?uid=swg24042598]\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043227 [http://www-01.ibm.com/support/docview.wss?uid=swg24043227] WebSphere Message Broker V8 IT17992 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=IT17992 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT17992] \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 20-Mar-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", "PSIRT; CVE; vulnerability; NSC SECURITY BULLETIN\n\nSUMMARY\n OpenSSL vulnerabilities were disclosed on September 22 and 26, 2016 by the OpenSSL Project. OpenSSL is used by IBM Security Network Controller. IBM Security Network Controller has addressed the applicable CVEs. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-6304 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6304]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by multiple memory leaks in t1_lib.c during session renegotiation. By sending an overly large OCSP Status Request extension, a remote attacker could exploit this vulnerability to consume all available memory resources.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117110 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117110] 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\nCVEID: CVE-2016-6303 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6303]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an integer overflow in the MDC2_Update function. By using unknown attack vectors, a remote attacker could exploit this vulnerability to trigger an out-of-bounds write and cause the application to crash.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117023 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117023] 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-6308 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6308]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by a memory allocation error in dtls1_preprocess_fragment() prior to the excessive message length check. By initiating multiple connection attempts, a remote authenticated attacker could send an overly large DTLS message to exhaust all available memory resources.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117114 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117114] 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\nCVEID: CVE-2016-2181 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2181]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an error in the DTLS replay protection implementation. By sending a specially crafted sequence number, a remote attacker could exploit this vulnerability to cause valid packets to be dropped.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116344 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116344] 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-6309 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6309]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by a use-after-free when handling message sizes. By sending an overly large message, a remote attacker could exploit this vulnerability to possibly execute arbitrary code on the system or cause the application to crash.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117148 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117148] 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-7052 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7052]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by a missing CRL sanity check. By attempting to use CRLs, a remote attacker could exploit this vulnerability to cause the application to crash.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117149 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117149] 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 Security Network Controller 1.0.X\n\nREMEDIATION/FIXES\n \n\nProduct VRMF Remediation/First Fix IBM Security Network Controller 1.0.X Proventia NSC update 15 (fw 1.0.4100) [https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=IBM%20Security&product=ibm/Tivoli/IBM+Security+Network+Active+Bypass&release=All&platform=All&function=fixId&fixids=20161220_Proventia_Network_Security_Controller_update-15_fw1.0.4100&includeRequisites=1&includeSupersedes=0&downloadMethod=http] IBM Security Network Controller 1.0.X Proventia NSC update 15 (fw 1.0.4100M) [https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=IBM%20Security&product=ibm/Tivoli/IBM+Security+Network+Active+Bypass&release=All&platform=All&function=fixId&fixids=20161220_Proventia_Network_Security_Controller_update-15_fw1.0.4100M&includeRequisites=1&includeSupersedes=0&downloadMethod=http&login=true] \nFor IBM Security Network Controller products at Firmware versions 1.X, IBM recommends upgrading to 1.0.4100M/1.0.4100 depending on current firmware installed. Update 1.0.4100M and 1.0.4100 are the supported firmware release 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\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 Original publish date: Dec 23, 2016 \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." ]

[ [ "3a", "WMB IIB SECURITY BULLETIN SUMMARY" ], [ "3b", " OpenSSL vulnerabilities were disclosed on September 22, September 26, and November 10, 2016 by the OpenSSL Project." ], [ "3c", "The DataDirect ODBC Drivers used by WebSphere Message Broker and IBM Integration Bus have addressed the applicable CVEs. VULNERABILITY DETAILS" ], [ "3d", "CVEID: CVE-2016-6303 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6303]" ], [ "3e", "DESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an integer overflow in the MDC2_Update function." ], [ "3f", "By using unknown attack vectors, a remote attacker could exploit this vulnerability to trigger an out-of-bounds write and cause the application to crash." ], [ "3g", "CVSS Base Score: 5.3" ], [ "3h", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117023 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117023] for the current score" ], [ "3i", "CVSS Environmental Score*: Undefined" ], [ "3j", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)" ], [ "3k", "CVEID: CVE-2016-2182 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2182]" ], [ "3l", "DESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an out-of-bounds write in the TS_OBJ_print_bio function in crypto/bn/bn_print.c." ], [ "3m", "A remote attacker could exploit this vulnerability using a specially crafted value to cause the application to crash." ], [ "3n", "CVSS Base Score: 4.3" ], [ "3o", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116342 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116342] for the current score" ], [ "3p", "CVSS Environmental Score*: Undefined" ], [ "3q", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L)" ], [ "3r", "CVEID: CVE-2016-2177 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2177]" ], [ "3s", "DESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by the incorrect use of pointer arithmetic for heap-buffer boundary checks." ], [ "3t", "By leveraging unexpected malloc behavior, a remote attacker could exploit this vulnerability to trigger an integer overflow and cause the application to crash." ], [ "3u", "CVSS Base Score: 5.9" ], [ "3v", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113890 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113890] for the current score" ], [ "3w", "CVSS Environmental Score*: Undefined" ], [ "3x", "CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H)" ], [ "3y", "CVEID: CVE-2016-2178 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2178]" ], [ "3z", "DESCRIPTION: 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." ], [ "3aa", "An attacker could exploit this vulnerability using a cache-timing attack to recover the private DSA key." ], [ "3ab", "CVSS Base Score: 5.3" ], [ "3ac", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113889 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113889] for the current score" ], [ "3ad", "CVSS Environmental Score*: Undefined" ], [ "3ae", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)" ], [ "3af", "CVEID: CVE-2016-6306 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6306]" ], [ "3ag", "DESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by missing message length checks when parsing certificates." ], [ "3ah", "A remote authenticated attacker could exploit this vulnerability to trigger an out-of-bounds read and cause a denial of service." ], [ "3ai", "CVSS Base Score: 4.3" ], [ "3aj", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117112 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117112] for the current score" ], [ "3ak", "CVSS Environmental Score*: Undefined" ], [ "3al", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L)" ], [ "3am", "CVEID: CVE-2016-2183 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2183]" ], [ "3an", "DESCRIPTION: 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." ], [ "3ao", "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." ], [ "3ap", "This vulnerability is known as the SWEET32 Birthday attack." ], [ "3aq", "CVSS Base Score: 3.7" ], [ "3ar", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116337 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116337] for the current score" ], [ "3as", "CVSS Environmental Score*: Undefined" ], [ "3at", "CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)" ], [ "3au", "CVEID: CVE-2016-7055 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7055]" ], [ "3av", "DESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an error in a Broadwell-specific Montgomery multiplication procedure." ], [ "3aw", "By sending specially crafted data, a remote attacker could exploit this vulnerability to trigger errors in public-key operations in configurations where multiple remote clients select an affected EC algorithm and cause a denial of service." ], [ "3ax", "CVSS Base Score: 5.3" ], [ "3ay", "CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118748 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118748] for the current score" ], [ "3az", "CVSS Environmental Score*: Undefined" ], [ "3ba", "CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)" ], [ "3bb", "AFFECTED PRODUCTS AND VERSIONS" ], [ "3bc", " IBM Integration Bus V10, V9" ], [ "3bd", "WebSphere Message Broker V8 REMEDIATION/FIXES" ], [ "3be", "For users of ODBC SSL using the DataDirect drivers:" ], [ "3bf", "Product VRMF APAR Remediation/Fix IBM Integration Bus V10" ], [ "3bg", "IT17992 The APAR is available in fix pack 10.0.0.8" ], [ "3bh", "https://www.ibm.com/support/docview.wss?uid=swg24043443 [https://www.ibm.com/support/docview.wss?uid=swg24043443] IBM Integration Bus V9" ], [ "3bi", "IT17992 The APAR is available in fix pack 9.0.0.7 [https://www-304.ibm.com/support/docview.wss?uid=swg24042598]" ], [ "3bj", "http://www-01.ibm.com/support/docview.wss?uid=swg24043227 [http://www-01.ibm.com/support/docview.wss?uid=swg24043227] WebSphere Message Broker V8 IT17992 An interim fix is available from IBM Fix Central http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT17992 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT17992]" ], [ "3bk", "For unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product." ], [ "3bl", "The planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : http://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308]" ], [ "3bm", "WORKAROUNDS AND MITIGATIONS None" ], [ "3bn", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS" ], [ "3bo", " Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. IMPORTANT NOTE" ], [ "3bp", " 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." ], [ "3bq", "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]." ], [ "3br", "Security and integrity APARs and associated fixes will be posted to this portal." ], [ "3bs", "IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. REFERENCES" ], [ "3bt", "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]" ], [ "3bu", "On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION" ], [ "3bv", "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]" ], [ "3bw", "IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] CHANGE HISTORY" ], [ "3bx", " 20-Mar-2017 - Original version published" ], [ "3by", "*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score." ], [ "3bz", "Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. DISCLAIMER" ], [ "3ca", "According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\"" ], [ "3cb", "IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE." ], [ "3cc", "CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. RELATED INFORMATION #" ], [ "3cd", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker 8.0 PRODUCT ALIAS/SYNONYM" ], [ "3ce", " WMB IIB" ] ]

[ "3bc", "3bd", "3be", "3bf", "3bg", "3d", "3af", "3ag", "3ah", "3ac", "3ad", "3m", "3n" ]