Datasets:

manu

/

tech_qa

like 0

[ "IBM Exit() action within User Defined Function in Impact Policy Language - United States netcool; impact; netcool/impact; nci; ipl; policy; language; exit; exit(); function; user; defined; custom; udf; parser; action; set; global; variable; var; get; setglobalvar; getglobalvar; globalvar TECHNOTE (FAQ)\n\nQUESTION\n and how to exit the Policy process from within a Custom Function \n\nCAUSE\nUsing the Exit() parser function within a User Defined (or Custom) Function in Impact Policy Language (IPL) will not exit the Policy process, it will only exit the User Defined Function.\n\nANSWER\nThis is because the Exit() parser function in IPL is designed to exit the immediate scope. To carry the action outside of the User Defined Function to the Policy level one would have to set a variable that is then tested immediately after the User Defined Function call - for example:", "* \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * SetGlobalVar(\"ExitNow\", 1);\n * \n * Exit();\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * SetGlobalVar(\"ExitNow\", 1);\n * \n * Exit();\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * If(GetGlobalVar(\"ExitNow\") == 1)\n * \n * {\n Log(ID+WP+\": Existing policy...\");\n \n * Exit\n * ();\n }\n\n\nThe above example ties in somewhat with the exampled configuration from the TechNote \"Event Flagging with Go_NoGo checking\" [ link below] and uses structured logging as covered in the TechNote \"Structured logging in Policies\" [ link below].", "If the User Defined Function was nested within another User Defined Function one would have to exit each layer to return the Policy layer before the Exit() action would exit the Policy. \nRELATED INFORMATION\n Event Flagging with Go_NoGo checking [http://www-01.ibm.com/support/docview.wss?uid=swg21675015]\nStructured Logging in Policies [http://www-01.ibm.com/support/docview.wss?uid=swg21596180]" ]

[ "This is because the Exit() parser function in IPL is designed to exit the immediate scope. To carry the action outside of the User Defined Function to the Policy level one would have to set a variable that is then tested immediately after the User Defined Function call" ]

[ 0 ]

[ "IBM Guide to properly setting up SSL within the IBM HTTP Server - United States ssl; handshake; secure socket layer; handshake failed; enable; ssl config; ssl setup; setup; IHS; crl; revocation; ssl; ssl; ssl; configure; config; config; config TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The following information can be used as a guide for setting up the Secure Sockets Layer (SSL) within the IBM HTTP Server. This document covers information on setting up SSL virtualhosts, creating keyfiles, certificates along with how to protect access to directories and URLs to specific ciphers. Also, included is documentation on how to trace and record SSL traffic between a client browser and the Web server. \n\nRESOLVING THE PROBLEM\nThe following steps help guide you through the proper set up of SSL within the IBM HTTP Server:", "1. Confirm that the Global Security Kit (GSKit) is installed and meets the minimum requirements\n \n \n 2. Create a key database file and certificates needed to authenticate the Web server during an SSL handshake\n \n \n 3. Enable SSL directives within the IBM HTTP Server configuration file (httpd.conf)\n \n \n 4. Other considerations when enabling SSL directives within the IBM HTTP Server configuration file (httpd.conf)\n \n \n 5. Information that IBM WebSphere® Support needs to debug SSL configuration and certificate issues related to the IBM HTTP Server", "1. Confirm that the Global Security Kit is installed and meets the minimum requirements\n \n The Global Security Kit (GSKit) is a required component for the Secure Sockets Layer (SSL) enablement within the IBM HTTP Server. Therefore, it is important to confirm that a supported version of the Global Security Kit is installed prior to enabling SSL.\n \n For a complete listing of IBM HTTP Server releases and corresponding Global Security Kit versions, click IBM HTTP Server: Global Security Kit (GSKit) supported versions [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21173214].\n \n \n \n 2. Create a key database file and certificates needed to authenticate the Web server during an SSL handshake\n \n The iKeyman GUI, which is included within the IBM HTTP Server distribution, can be used to create a key database file (for example: key.kdb) needed to store personal server certificates required by the client browser during an SSL handshake.", "For quick information on how to create a key database file and personal server certificates, refer to the technote IKEYMAN, How do I...? [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21006430] \n \n More extensive information on using the iKeyman GUI to create key database files and certificates is located here: * For releases of IBM HTTP Server v7.0 [http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Fwelc_ikeymangui.html] \n * For releases of IBM HTTP Server v8.0 [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Fwelc_ikeymangui.html] \n * For releases of IBM HTTP Server v8.5 [http://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.ihs.doc/ihs/welc_ikeymangui.html]", "* For releases of IBM HTTP Server v9.0 [https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.0/com.ibm.websphere.ihs.doc/ihs/welc_ikeymangui.html] \n \n \n \n \n 3. Enable SSL directives within the IBM HTTP Server's configuration file (httpd.conf)\n 1. Verify that the SSL modules are uncommented\n * For Microsoft® Windows®:\n \n \n LoadModule ibm_ssl_module modules/mod_ibm_ssl.so [/support/docview.wss?uid=swg21179559&amp;aid=1]\n \n \n * For UNIX® platforms:\n \n \n LoadModule ibm_ssl_module modules/mod_ibm_ssl.so [/support/docview.wss?uid=swg21179559&amp;aid=2]\n \n \n \n \n 2. Create an SSL virtualhost stanza using the following examples and directives", "If you are enabling one Web site for SSL, and the hostname is the same as the one already defined in the Global Scope for non-SSL (port 80), you can enable SSL as follows. This virtualhost uses the default hostname defined by the ServerName directive in the Global Scope and the IP address associated with it.\n \n http://www.mycompany.com (non-SSL) 192.168.1.102 https://www.mycompany.com (SSL) 192.168.1.102\n \n Example 1:\n \n Listen 80\n ServerName www.mycompany.com\n \n <Directory \"c:/Program Files/IBM HTTP Server/htdocs\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n \n DocumentRoot \"c:/program files/ibm http server/htdocs\"\n DirectoryIndex index.html\n \n Listen 443\n <VirtualHost :443>\n SSLEnable\n SSLClientAuth None\n </VirtualHost>\n \n SSLDisable", "KeyFile \"c:/program files/ibm http server/key.kdb\"\n SSLV2Timeout 100\n SSLV3Timeout 1000 [/support/docview.wss?uid=swg21179559&amp;aid=3]\n \n If you are enabling one Web site for SSL and the ServerName is different than the ServerName already defined in the Global Scope for non-SSL (port 80), you can enable SSL as follows. Both hostnames must be registered in DNS to a separate IP address, and both IP addresses must be configured on local network interface cards.\n \n http://www.mycompany.com (non-SSL) 192.168.1.102 http://www.mycompany2.com (non-SSL) 192.168.1.103 https://www.mycompany2.com (SSL) 192.168.1.103\n \n Example 2:\n \n Listen 80\n ServerName www.mycompany.com\n \n <Directory \"c:/Program Files/IBM HTTP Server/htdocs\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>", "DocumentRoot \"c:/program files/ibm http server/htdocs\"\n DirectoryIndex index.html\n \n <VirtualHost 192.168.1.103:80>\n ServerName www.mycompany2.com\n <Directory \"c:/Program Files/IBM HTTP Server/htdocs2\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n DocumentRoot \"c:/program files/ibm http server/htdocs2\"\n DirectoryIndex index2.html\n </VirtualHost>\n \n Listen 443\n <VirtualHost 192.168.1.103:443>\n ServerName www.mycompany2.com\n SSLEnable\n SSLClientAuth None\n <Directory \"c:/Program Files/IBM HTTP Server/htdocs2\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n DocumentRoot \"c:/program files/ibm http server/htdocs2\"\n DirectoryIndex index2.html\n </VirtualHost>\n \n SSLDisable", "KeyFile \"c:/program files/ibm http server/key.kdb\"\n SSLV2Timeout 100\n SSLV3Timeout 1000 \n If you are enabling multiple Web sites for SSL, you can enable SSL as follows. All hostnames must be registered in DNS to a separate IP address. Also, all the IP addresses must be configured on a local network interface card. You must use the SSLServerCert directive to identify which personal server certificate in the key database file is passed to the client browser during the SSL handshake for each Web site. If the SSLServerCert directive is not defined, the IBM HTTP Server passes whatever certificate in the key database file is marked(*) as the \"default key\".", "For more information on why different IP addresses are required when enabling multiple Web sites for SSL: IP-Based Virtual Hosting must be used if configuring multiple SSL Virtual Host [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21045922]http://www.mycompany.com (non-SSL) 192.168.1.102 https://www.mycompany.com (non-SSL) 192.168.1.102 http://www.mycompany2.com (non-SSL) 192.168.1.103 https://www.mycompany2.com (SSL) 192.168.1.103 http://www.mycompany3.com (non-SSL) 192.168.1.104 https://www.mycompany3.com (SSL) 192.168.1.104\n \n Example 3:\n \n Listen 80\n ServerName www.mycompany.com\n \n <Directory \"c:/Program Files/IBM HTTP Server/htdocs\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n \n DocumentRoot \"c:/program files/ibm http server/htdocs\"\n DirectoryIndex index.html", "<VirtualHost 192.168.1.103:80>\n ServerName www.mycompany2.com\n <Directory \"c:/Program Files/IBM HTTP Server/htdocs2\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n DocumentRoot \"c:/program files/ibm http server/htdocs2\"\n DirectoryIndex index2.html\n </VirtualHost>\n \n <VirtualHost 192.168.1.104:80>\n ServerName www.mycompany3.com\n <Directory \"c:/Program Files/IBM HTTP Server/htdocs3\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n DocumentRoot \"c:/program files/ibm http server/htdocs3\"\n DirectoryIndex index3.html\n </VirtualHost>\n \n Listen 443\n <VirtualHost 192.168.1.102:443>\n ServerName www.mycompany.com\n SSLEnable\n SSLClientAuth None\n SSLServerCert mycompany", "<Directory \"c:/Program Files/IBM HTTP Server/htdocs\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n DocumentRoot \"c:/program files/ibm http server/htdocs\"\n DirectoryIndex index.html\n </VirtualHost>\n \n <VirtualHost 192.168.1.103:443>\n ServerName www.mycompany2.com\n SSLEnable\n SSLClientAuth None\n SSLServerCert mycompany2\n <Directory \"c:/Program Files/IBM HTTP Server/htdocs2\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n DocumentRoot \"c:/program files/ibm http server/htdocs2\"\n DirectoryIndex index2.html\n </VirtualHost>\n \n <VirtualHost 192.168.1.104:443>\n ServerName www.mycompany3.com\n SSLEnable\n SSLClientAuth None\n SSLServerCert mycompany3\n <Directory \"c:/Program Files/IBM HTTP Server/htdocs3\">", "Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n DocumentRoot \"c:/program files/ibm http server/htdocs3\"\n DirectoryIndex index3.html\n </VirtualHost>\n \n SSLDisable\n KeyFile \"c:/program files/ibm http server/key.kdb\"\n SSLV2Timeout 100\n SSLV3Timeout 1000 \n \n \n \n \n 4. Other considerations when enabling SSL directives within the IBM HTTP Server configuration file (httpd.conf).\n \n * How to rewrite HTTP (port 80) requests to HTTPS (port 443)\n The rewrite module (mod_rewrite.c) provided with the IBM HTTP Server can be used as an effective way to automatically rewrite all HTTP requests to HTTPS. For complete information click How to rewrite HTTP (port 80) requests to HTTPS (port 443) [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21114864].", "* Logging SSL request information in the access log for IBM HTTP Server\n The IBM HTTP Server implementation provides Secure Sockets Layer (SSL) environment variables that are configurable with the LogFormat directive in httpd.conf. For complete information click Logging SSL request information in the access log for IBM HTTP Server [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21176455].\n \n \n * Enabling Certificate Revocation Lists (CRL) in the IBM HTTP Server", "Certificate revocation provides the ability to revoke a client certificate given to the IBM HTTP Server by the browser when the key is compromised or when access permission to the key is revoked. CRL represents a database that contains a list of certificates revoked before their scheduled expiration date. For complete information: * For releases of IBM HTTP Server v7.0 [http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Fcihs_crlinssl.html] \n * For releases of IBM HTTP Server v8.5 [http://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.ihs.doc/ihs/cihs_crlinssl.html] \n * For releases of IBM HTTP Server v8.0 [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Fcihs_crlinssl.html]", "5. Information that IBM WebSphere Support needs to debug SSL configuration and certificate issues related to the IBM HTTP Server\n * MustGather: SSL handshake and configuration problems [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21141302]\n \n * MustGather: CMS key database (.kdb) and certificate problems [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21141303]", "* \n * Brief description of the SSL directives discussed in this document\n * \n \n Listen\n * \n * \n * \n * \n * SSLEnable\n * \n * \n * \n * \n * SSLClientAuth None\n * \n * \n * \n * \n * SSLDisable\n * \n * \n * \n * \n * KeyFile\n * \n * \n * \n * \n * SSLV2Timeout\n * \n * \n * \n * \n * SSLV3Timeout\n * \n * \n * \n * \n * SSLServerCert\n * \n * \n * \n * \n * SSLCipherSpec\n * \n * \n * \n * \n * SSLCipherRequire\n * \n * \n * \n * \n * \n *", "* For releases of IBM HTTP Server v7.0 [http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Frihs_ssldirs.html] For releases of IBM HTTP Server v8.0 [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Frihs_ssldirs.html] For releases of IBM HTTP Server v8.5 [http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.ihs.doc/ihs/rihs_ssldirs.html] For releases of IBM HTTP Server v9.0 [https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.0/com.ibm.websphere.ihs.doc/ihs/rihs_ssldirs.html]" ]

[ "The following steps help guide you through the proper set up of SSL within the IBM HTTP Server: \n\n 1. Confirm that the Global Security Kit (GSKit) is installed and meets the minimum requirements\n \n \n 2. Create a key database file and certificates needed to authenticate the Web server during an SSL handshake\n \n \n 3. Enable SSL directives within the IBM HTTP Server configuration file (httpd.conf)\n \n \n 4. Other considerations when enabling SSL directives within the IBM HTTP Server configuration file (httpd.conf)\n \n \n 5. Information that IBM WebSphere® Support needs to debug SSL configuration and certificate issues related to the IBM HTTP Server" ]

[]

[ "IBM Security Bulletin: IBM Tivoli Network Manager IP Edition is affected by an Apache CXF vulnerability (CVE-2017-3156) - United States SECURITY BULLETIN\n\nSUMMARY\n Vulnerability has been addressed in the Apache CXF component of Tivoli Network Manager IP Edition. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-3156 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3156]\nDESCRIPTION: Apache CXF could provide weaker than expected security, caused by the failure to use the OAuth2 Hawk and JOSE MAC Validation code. A remote attacker could exploit this vulnerability using timing attacks to obtain sensitive information.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/130249 [https://exchange.xforce.ibmcloud.com/vulnerabilities/130249] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N)", "AFFECTED PRODUCTS AND VERSIONS\nTivoli Network Manager IP Edition 4.1.1 (Huawei MTOSI Collector install)\nTivoli Network Manager IP Edition 4.2.0 (Huawei MTOSI Collector install)\n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation/First Fix Tivoli Network Manager IP Edition 4.1.1 IV99816 Please call IBM service and reference APAR IV99816, to obtain a fix if needed for 4.1.1 release. Tivoli Network Manager IP Edition 4.2.0 IV99816 CXF 3.1.10 has been upgraded in 4.2 FixPack 3.\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043575 [http://www-01.ibm.com/support/docview.wss?uid=swg24043575] WORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "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\nCHANGE HISTORY\n 15 September 2017 : Original Version Published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.", "DISCLAIMER\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." ]

[ "CVEID: CVE-2017-3156 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3156]\nDESCRIPTION: Apache CXF could provide weaker than expected security, caused by the failure to use the OAuth2 Hawk and JOSE MAC Validation code. A remote attacker could exploit this vulnerability using timing attacks to obtain sensitive information.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/130249 [https://exchange.xforce.ibmcloud.com/vulnerabilities/130249] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N)" ]

[ 0 ]

[ "IBM 2035 MQRC_NOT_AUTHORIZED Connecting to WebSphere MQ from WebSphere Application Server via CLIENT Bindings - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This article covers the most common reasons why an application running in WebSphere Application Server receives a 2035 MQRC_NOT_AUTHORIZED error when connecting to MQ as a client over a network. Quick steps to work around the MQRC_NOT_AUTHORIZED errors during development are provided in the 'Resolving the problem' section, as well as considerations for implementing security in production environments. A summary is also provided of behavior for outbound scenarios with container-managed and component-managed security, as well as inbound behavior for listener ports and activiation specifications \n\nSYMPTOM\nJMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED')\n\n\nCAUSE\nThe two most likely reasons why the connection is refused by MQ are as follows:", "1. The user identifier passed across the client connection from the application server to MQ is not known on the server where the MQ queue manager is running, is not authorised to connect to MQ, or is longer than 12 characters and has been truncated.\n We discuss how this user identifier is obtained and passed over the connection in more detail below.\n For queue managers running on Windows, the following error might be seen in the MQ error logs for this scenario:\n AMQ8075: Authorization failed because the SID for entity 'wasuser' cannot be obtained.\n For UNIX no entry in the MQ error logs would be seen by default.\n See technote MQS_REPORT_NOAUTH environment variable can be used to better diagnose return code 2035 [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg21299319] for details of enabling error log entries on all platforms.", "2. The user identifier passed across the client connection from the application server to MQ is a member of the 'mqm' group on the server hosting the MQ queue manager, and a Channel Authentication Record (CHLAUTH) exists that blocks administrative access to the queue manager. WebSphere MQ configures a CHLAUTH record by default in WebSphere MQ Version 7.1 and later that blocks all MQ admins from connecting as a client to the queue manager.\n The following error in the MQ error logs would be seen for this scenario:\n AMQ9777: Channel was blocked", "See the Error logs on Windows, UNIX and Linux systems [http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/topic/com.ibm.mq.tro.doc/q039560_.htm] section of the MQ Information Center for the location of the MQ error logs. \nDIAGNOSING THE PROBLEM\nTo understand the cause of the MQRC_NOT_AUTHORIZED reason code, you need to understand what username (and password) is being used by MQ to authorise the application server. \n\nPlease note that WebSphere MQ V7.5 and earlier does not provide any out-of-the box password authentication system for client connections.\nPassword authentication is provided out of the box in IBM MQ V8.0. More details on the new IBM MQ V8.0 security features are available in this presentation [https://www.slideshare.net/MoragHughson/websphere-mq-v8-security-deep-dive].", "For WebSphere MQ V7.5 and earlier, this means that while the understanding provided in this technote over how usernames/passwords are passed from the application server to MQ is helpful for development environments, solving the security requirements of production environments usually also requires one of the following approaches:", "* Mutual SSL/TLS authentication.\n MQ provides out-of-the-box features to authenticate a remotely attaching client using the digital certificate they provide for SSL/TLS transport security. For example by configuring an SSLPEER rule on the SVRCONN channel to match the Distinguished Name in the certificate of the WebSphere Application Server, and establishing trust in the issuer of that certificate. \n * A custom, or 3rd party supplied, WebSphere MQ Security Exit\n A security exit can be written for MQ that performs username and password authentication against a repository, such as the local operating system on the MQ server, or an LDAP repository.\n When using a security exit for authentication it is important that SSL/TLS transport security is still configured, to ensure passwords are not sent in plain text.", "MCA user ID (MCAUSER) configured on the Server Connection (SVRCONN) channel If an MCAUSER is configured on the SVRCONN channel that the application server is using to connect, and no security exit or mapping Channel Authentication Record is installed, then this overrides the username provided by the application server. \n\nIt is common practice for many customers to set an MCAUSER on every SVRCONN channel, and use mutual SSL/TLS authentication exclusively for authentication. \n\nDefault behaviour when no credentials are supplied in the application server", "If no credentials are supplied by the application on the createConnection call, and neither of the component managed or container managed security systems described below are configured, then WebSphere Application Server provides a blank username to MQ. This causes MQ to authorise the client based on the userid that the MQ listener is running under. In the majority of cases this is 'mqm' on UNIX/Linux systems and 'MUSR_MQADMIN' on Windows. \n\nAs these are administrative MQ users, they will be blocked by default in WebSphere MQ V7.1 and higher, with a AMQ9777 error logged in the error logs of the queue manager. \n\nContainer-managed security for outbound connections \n\nThe recommended way to configure the username and password passed to MQ by the application server for outbound connections, is to use container-managed security. Outbound connections are those created using a Connection Factory, rather than a Listener Port or Activation Specification.", "Usernames of 12 characters or less are passed to MQ by the appliaction server. Usernames longer than 12 characters in length will be truncated, either during authorisation (on UNIX), or in the MQMD of messages that are sent. \n\nContainer-managed security means that the deployment descriptor, or EJB 3.0 annotations, of the application declare a resource reference with authentication type set to Container. \n\nThen when the application looks up the Connection Factory in JNDI, it does so indirectly via the resource reference. For example an EJB 2.1 application would perform a JNDI lookup as follows, where \"jms/MyResourceRef\" has been declared as a resource reference in the deployment descriptor: \n\nConnectionFactory myCF = (ConnectionFactory)ctx.lookup(\"java:comp/env/jms/MyResourceRef\")", "An EJB 3.0 application might declare an annotated object property on the bean as follows:\n@Resource(name = \"jms/MyResourceRef\", \nauthenticationType = AuthenticationType.CONTAINER)\nprivate javax.jms.ConnectionFactory myCF; \n\nWhen the application is deployed by an administrator, they bind this authentication alias to an actual Connection Factory that has been created in JNDI, and assign it a J2C authentication alias on deployment. \n\nIt is the username and password contained in this authentication alias that is then passed to MQ/JMS by the application server when the application connects. This approach puts the administrator in control of which username and password is used by each application, and prevents a different application from looking up the connection factory in JNDI directly to connect with the same username and password.", "A default container-managed authentication alias can be supplied on the configuration panels in the administrative console for MQ connection factories. This default will only be used in the case that an application uses a resource reference configured for container-managed security, but the administrator has not bound it to an authentication alias during deployment. A screen shot is provided below:\n[/support/docview.wss?uid=swg21636093&aid=1] [/support/docview.wss?uid=swg21636093&aid=1] \n\nDefault component-managed authentication alias for outbound connections \n\nFor cases where it is impractical to change the application to use container-managed security, or to change it to supply a username and password directly on the createConnection call, it is possible to supply a default.", "This default is called the \"component-managed authentication alias\" and cannot be configured via the administrative console (since WebSphere Application Server Version 7.0 when it was removed from the panels MQ connection factories). The below scripting samples show how to configure it using wsadmin:", "* JACL:\n wsadmin>set cell [ $AdminConfig getid \"/Cell:mycell\" ]\n \n mycell(cells/mycell|cell.xml#Cell_1)\n \n wsadmin>$AdminTask listWMQConnectionFactories $cell\n \n MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)\n \n wsadmin>$AdminTask modifyWMQConnectionFactory MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104) { -componentAuthAlias myalias }\n \n MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104) \n * Jython:\n wsadmin>cell = AdminConfig.getid(\"/Cell:mycell\")\n \n wsadmin>AdminTask.listWMQConnectionFactories(cell)\n \n 'MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)'\n \n wsadmin>AdminTask.modifyWMQConnectionFactory('MyCF(cells/mycell|resos urces.xml#MQConnectionFactory_1247500675104)', \"-componentAuthAlias myalias\")\n \n 'MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)'", "Authentication alias for inbound MDB connections using an activation specification For inbound connections using an activation specification an authentication alias can be specified by the administrator when deploying the application, or a default authentication alias can be specified on the activation specification via the administrative console. \n\nAuthentication alias for inbound MDB connections using a listener port \n\nFor inbound connections using a listener port, the value specified in the \"Container-managed authentication alias\" setting of the connection factory (seen in the above screenshot) is used. \n\nOn zOS, first the \"Container-managed authentication alias\" is checked and used if set, then the \"Component-managed authentication alias\" is checked and used it set.\n\n\nRESOLVING THE PROBLEM\nThe simplest steps to resolve the 2035 MQRC_NOT_AUTHORIZED errors in a development environment, where full transport security is not required, are as follows:", "1. Choose a user that you want WebSphere Application Server to be authenticated as. Typically the user chosen should have authority relevant to the context of the operations required by the application running in WebSphere Application Server and no more. For example, 'mqm' or other super user is not appropriate. \n 2. If this user is an MQ administrative user, then relax the Channel Authentication Record (CHLAUTH) security in MQ V7.1 or higher, so that administrative connections are not blocked on the SVRCONN channel you wish to use. An example MQSC command to do this for a SVRCONN channel called 'WAS.CLIENTS' is provided as follows:\n SET CHLAUTH('WAS.CLIENTS') TYPE(BLOCKUSER) USERLIST(ALLOWANY) \n 3. Configure the SVRCONN channel to set the MCA user ID (MCAUSER) to the user you have chosen. An example MQSC command to configure a SVRCONN channel to use 'myuser' as the MCA user ID is provided as follows:\n ALTER CHL('WAS.CLIENTS') CHLTYPE(SVRCONN) MCAUSER('myuser')", "The following additional considerations are important for production environments: For all production environments where transport security is required, SSL/TLS security must be configured between the application server and MQ. \n\nIn order to configure SSL/TLS transport security, you must establish the appropriate trust between the MQ queue manager and WebSphere Application Server. The application server, who initiates the SSL/TLS handshake, must always be configured to trust the certificate provided by the MQ queue manager . If the application server is configured to send a certificate to the MQ queue manager, then the queue manager must also be configured to trust it. \n\nIf trust is not correctly configured on both sides, you will encounter 2393 MQRC_SSL_INITIALIZATION_ERROR reason codes after enabling SSL/TLS on the connection.", "If you do not have a security exit that performs username and password authentication, then you should configure mutual SSL/TLS authentication on your Server Connection channel to cause the queue manager to require a trusted certificate is provided by the application server. To do this you set \"SSL Authentication\" to \"Required\" in the MQ Explorer or SSLCAUTH(REQUIRED) via MQSC. \n\nIf you do have a security exit that performs username and password authentication installed in your MQ server, then configure your application to supply a username and password for validation by that security exit. The details of how to configure the username and password passed to MQ by the application server are described above in the \"Diagnosing the problem\" section.", "All Server Connection channels that do not have SSL/TLS security applied should be disabled. Example MQSC commands to disable the SYSTEM.DEF.SVRCONN channel are provided as follows (these assume no user exists on the MQ server called 'NOAUTH'):\nALTER CHL(SYSTEM.DEF.SVRCONN) CHLTYPE(SVRCONN) MCAUSER('NOAUTH')\nSTOP CHL(SYSTEM.DEF.SVRCONN) \n\nDetails of how to configure the private certificate and trust of a MQ queue manager, and to enable SSL security on a Server Connection channel, see the following locations in the MQ information center:", "* To configure the certificates and trust of the MQ queue manager see the following topic:\n Configuring SSL on queue managers [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/index.jsp?topic=%2Fcom.ibm.mq.explorer.doc%2Fe_ssl_channels.htm] \n * To configure the Server Connection channel, used by applications running in the application server to connect to MQ, see the following topic:\n Configuring SSL channels [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.explorer.doc/e_ssl_channels.htm]", "Details of how you configure trust within WebSphere Application Server, and whether the application server sends a certificate to MQ for authentication, are in the following locations in the WebSphere Application Server information center: * To create or modify an SSL Configuration containing the appropriate SSL/TLS configuration for connecting to MQ, see the following topic:\n SSL configurations [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-base-dist&topic=csec_sslconfigs]", "Note that MQ requires you specify a matching Cipher Suite / Cipher Spec on both sides of the connection, as it checks the negotiated Cipher Suite matches the SSLCIPH setting on the channel after the handshake is complete. As a result the WebSphere Application Server SSL Configuration should be configured to contain only the Cipher Suite that matches the SSLCIPH setting on the Server Connection channel. See the following topic in the MQ information center for details of matching pairs:\n CipherSuite and CipherSpec name mappings for connections to a WebSphere® MQ queue manager [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.msc.doc/xms_csecure_mapping_wmq.html] \n * To enable SSL/TLS on a client connection, and choose which SSL Configuration to use, see the \"Use SSL to secure communication with Websphere MQ\", \"Centrally managed\" and \"Specific configuration\" sections of the following topics on Connection Factories and Activation Specifications", "WebSphere MQ messaging provider connection factory settings [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=umj_pjcfm]\n WebSphere MQ messaging provider activation specification settings [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=umj_pasm]", "Cross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server for z/OS Java Messaging Service (JMS) z/OS, OS/390 8.5, 8.0, 7.0 Business Integration WebSphere Business Monitor AIX, HP-UX, Linux, Solaris, Windows, z/OS 7.5.1, 7.5, 7.0 Advanced, Basic Business Integration WebSphere Message Broker Environment AIX, HP-UX, Linux, Solaris, Windows, z/OS 9.0, 8.0, 7.0 Business Integration WebSphere MQ Clients AIX, HP-UX, IBM i, Linux, Windows 8.0, 7.5, 7.1, 7.0" ]

[ "Default component-managed authentication alias for outbound connections \n\nFor cases where it is impractical to change the application to use container-managed security, or to change it to supply a username and password directly on the createConnection call, it is possible to supply a default. \n\nThis default is called the \"component-managed authentication alias\" and cannot be configured via the administrative console (since WebSphere Application Server Version 7.0 when it was removed from the panels MQ connection factories). The below scripting samples show how to configure it using wsadmin: \n\n * JACL:\n wsadmin>set cell [ $AdminConfig getid \"/Cell:mycell\" ]\n \n mycell(cells/mycell|cell.xml#Cell_1)\n \n wsadmin>$AdminTask listWMQConnectionFactories $cell\n \n MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)\n \n wsadmin>$AdminTask modifyWMQConnectionFactory MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104) { -componentAuthAlias myalias }\n \n MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104) \n * Jython:\n wsadmin>cell = AdminConfig.getid(\"/Cell:mycell\")\n \n wsadmin>AdminTask.listWMQConnectionFactories(cell)\n \n 'MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)'\n \n wsadmin>AdminTask.modifyWMQConnectionFactory('MyCF(cells/mycell|resos urces.xml#MQConnectionFactory_1247500675104)', \"-componentAuthAlias myalias\")\n \n 'MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)'" ]

[]

[ "IBM Rational Application Developer Support Policy for 64 bit technology - United States RSM; RSD; RSA; RAD; caspian64 bit; 64-bit; RAD 7 64 bit; RAD 7 OS; operating system; Rational Application Developer; X64; Windows 64 bit; supported OS; AMD; PMR #13878; 379; 000; 13878379000; 1263677; 64bit; 64 bit; 32 bit; 32bit; 32-bit; 64-bit; O/S; OS; requirements; system requirements; 8.0.3; 8.0; 7.5; v8.0.3; v7.5; v7.0; v8.0; v7.5.4; 803; windows 7; server; profile; websphere; test environment; create profile; button; greyed; Run Profile Management Tool ; disabled; IBM Software Development Kit; SDK; JRE; Program Files(x86); WAS; websphere application server; clearcase; scm; clearcase scm adapter; rational requisitepro; reqpro; heap size; jvm; max os x; os x; osx; mac TECHNOTE (FAQ)", "QUESTION\n What is the support policy for using IBM Rational Application Developer for WebSphere Software, IBM Rational Software Architect, IBM Rational Software Modeler or IBM Rational Systems Developer version 7.x and 8.x with 64-bit operating systems for Microsoft Windows or Linux? \n\nCAUSE\nThe 7.0.0.x, v7.5.x and v8.0 to 8.0.2 versions of these applications were not designed to take advantage of 64 bit computing and only use 32-bit technology.\n\nANSWER\nThe following IBM Rational Software version 7.x products are only supported on specified 64 bit operating systems running in 32 bit mode: \n\n * Rational Application Developer for WebSphere Software \n * Rational Software Architect \n * Rational Software Modeler \n * Rational Systems Developer", "Similarly, Rational Application Developer (RAD) and Rational Software Architect (RSA) version 8.0 to 8.0.2 are only supported on specified 64 bit operating systems running in 32 bit mode. Rational Application Developer v8.0.3+ is available as a 64-bit application install on specified 64-bit operating systems, in addition to a 32-bit application install.\nThere is only one installation package. When installing RAD/RSA using IBM Installation Manager, on the Location page , if your operating system is 64-bit, then select 64-bit or 32-bit to install the product in the corresponding bit mode. \n\n \n\nThese products will be referred to generically as Rational Software Development Platform (RSDP) based products. For example, WebSphere Integration Developer v6.x/7.x is RSDP based. \n\nExamples of some 64 bit Operating Systems:", "* Microsoft Windows XP Professional x64 Edition (running on an AMD or Intel processor) \n * Microsoft Windows 7 Professional 64-bit \n * Red Hat Linux Enterprise Server 4+ running on x86-64 bit \n * RAD 9.0 under 9.0.1 introduced support for Mac OS x - Lion 10.7 32 bit (with Oracle JDK for Mac OS X 7.0 Update 40) and Mountain Lion 10.8 - 32 bit. Likewise for RSA for WebSphere 9.0.0.1.\n RAD 9.0.1.1 introduced support for 64-bit exploit on Mac OS x Mavericks 10.9 ( with Oracle JDK for Mac OS X 7.0 Update 71)\n RSA 9.1.2 introduced support for 64-bit exploit on Mac OS X Yosemite 10.10 and OS X El Capitan 10.11 (with Oracle JDK 7.0 Update 75 for OS X)\n\n\n\nNote: RSDP 32-bit JVM based products, do not require any additional or special set-up on a supported 64-bit operating system (O/S). \nThey run on the provided/supported 32-bit JVM for that RSDP product, as is.", "Review the following documents for more details on the system requirements: \n * (7014264) Rational Application Developer System Requirements List [http://www.ibm.com/support/docview.wss?uid=swg27014264] \n * (7014274) Rational Software Architect Family System Requirements List [http://www.ibm.com/support/docview.wss?uid=swg27014274] \n * (7014269) Rational Software Modeler System Requirements List [http://www.ibm.com/support/docview.wss?uid=swg27014269]", "The above items such as the Rational Application Developer System Requirements List cover latest versions and operating systems such as Windows Vista and Windows 7. Support is limited to 32 bit mode on 64 bit operating systems on all versions prior to Rational Application Developer 8.0.3. For more information consult: \nKnown problems and limitations to installing 64-bit Rational Application Developer [http://www.ibm.com/support/docview.wss?uid=swg21499482] \nas referred to by the above Rational Application Developer System Requirements List. The following technote: \n- Benefits, requirements, limitations, and known issues for Rational Software Architect products running as 64-bit applications starting from v8.0.3 [http://www-01.ibm.com/support/docview.wss?uid=swg27021665] \n, especially Benefits, describes what is possible with a larger heap size with the 64-bit JVM.", "In deciding if you want a 64-bit install of RAD/RSA, it is useful to know that the ClearCase SCM Adapter and the Rational RequisitePro integration features/plugins are not supported or provided. These are only available as 32-bit eclipse plugins. \n\nIf you have any further questions, contact IBM Support for Rational Application Developer, or the appropriate IBM RSDP product support team. \n\n\nWebSphere Servers that are shipped with RSDP products: \n\nThe various WebSphere Application Server v6.x/7.x servers shipped with Rational Application Developer or Rational Software Architect {for WebSphere} prior to v8.0.4 are only provided as 32 bit editions. As of Rational Application Developer or Rational Software Architect {for WebSphere} v8.0.4+, 64 bit editions of WebSphere Application Server v6.x/7.x servers are shipped in addition to the 32 bit editions.", "The WebSphere Application Server v8.x (not beta) server shipped with Rational Application Developer or Rational Software Architect {for WebSphere} v8.0.3+ is provided as one edition, and there is an installation option to install either the 32 bit or 64 bit JVM/JRE (IBM Software Development Kit (SDK)). Any 64 bit edition or 64-bit JVM requires a supported 64 bit operating system. This IBM Education Assistant Module/PDF : IBM WebSphere Application Server V8 Distributed platform installation [http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/topic/com.ibm.iea.was_v8/was/8.0/Installation/WASV8_dist_install.pdf] , demonstrates selecting a 32-bit or 64-bit SDK as part of a WAS v8.0 install using IBM Installation manager. If the WAS v8.0 installation is on a 32-bit operating system, this feature choice between IBM 32-bit SDK Java 6.0 or IBM 64-bit SDK Java 6.0 is not available and the installation will automatically default to the IBM 32-bit SDK Java 6.0.", "The shipped WebSphere Portal Server v6.x/7.x servers are 32 bit or 64 bit editions. depending on whether you chose the IBM WebSphere Application Server Network Deployment, 32-bit or 64-bit server to install on.", "Note: It is possible to work with any 64 bit remotely accessible or local stand-alone WebSphere Application Server v6.x/7.x/8.x. In Rational Application Developer 8.0.3+ be aware of the Info Center topic: Creating profiles for WebSphere Application Server on a 64-bit machine [Creating%20profiles%20for%20WebSphere%20Application%20Server%20on%20a%2064-bit%20machine] and see this APAR opened against RAD 8.5.1/8.5.5 : PI06339: A 64-bit install of the WebSphere Application Server Profile Management Tool may not launch on Windows 7. RELATED INFORMATION\n Benefits for RSA v8.0.3 products running as 64-bit app [http://www.ibm.com/support/docview.wss?uid=swg27021665]\nInternet Explorer v9+ required if using 64-bit Bit Mode [http://www.ibm.com/support/docview.wss?uid=swg21502701]\nRAD 8.0.3+ IC: Creating profiles for WAS on a 64-bit ma [http://publib.boulder.ibm.com/infocenter/radhelp/v8/index.jsp?topic=/com.ibm.servertools.doc/topics/rbitmachine.html]", "Rational ClearCase SCM adapter not available for 64-bit [http://www.ibm.com/support/docview.wss?uid=swg21502974]\nCannot install the Java Visual Editor in RAD 64 bit [http://www.ibm.com/support/docview.wss?uid=swg21499219]\nRAD64bit Known problems to install or run [http://www.ibm.com/support/docview.wss?uid=swg21499482]\nWAS V8.0 & V8.5 64-bit Install offer Program Files (x86 [https://developer.ibm.com/answers/questions/175210/why-does-was-v80-and-v85-offer-program-files-x86-a.html]\nAbout SCM Adapter support on 64 Bit [http://www.ibm.com/support/docview.wss?uid=swg21460547]\nConversion of 32 bit to 64 bit WAS on the same machine [http://www.ibm.com/support/docview.wss?uid=swg21625930]\nRAD901: Installing RAD for WebSphere Software [http://www-01.ibm.com/support/knowledgecenter/SSRTLW_9.0.1/com.ibm.rad.install.doc/topics/t_install_product.html]\nRAD 9.0.x: new features and enhancements-9.0.1-new_OSup [http://www-01.ibm.com/support/docview.wss?uid=swg27038836#whatsnew_901_OSupdates]", "RAD 9.0.1 System Requirements - O/S [http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/osForProduct?deliverableId=1374678040873#osFamily-1]\nRSA(4WS) 9.0.x: new features and enhancements [http://www.ibm.com/support/docview.wss?uid=swg27038488]\nRSA 9.1.2: new features and enhancements - jdk [http://www-01.ibm.com/support/docview.wss?uid=swg27041555#whatsnew_912_JTE]\nA simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21504145]", "Cross reference information Segment Product Component Platform Version Edition Software Development Rational Software Architect Documentation Linux, Windows 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4, 7.0.0.5, 7.0.0.6, 7.0.0.7, 7.0.0.8 Software Development Rational Software Modeler Documentation Windows, Linux 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4 Software Development Rational Systems Developer Documentation Linux, Solaris, Windows 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4 Software Development Rational Software Architect for WebSphere Software General Information Linux, Windows 7.5, 7.5.1, 7.5.2" ]

[ "the Rational RequisitePro integration features/plugins are not supported or provided. These are only available as 32-bit eclipse plugins." ]

[ 6 ]

[ "IBM Starting WebSphere Application Server gives warning message - Could not lock User prefs - United States Websphere; startup; FileSystemPreferences; user prefs; prefs; Could not lock User prefs TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Warning message issued during the non-root or root startup of WebSphere stating that it can not lock the user or system preferences. \n\nSYMPTOM\nThe following message can be seen in the systemout.log: \n\n[9/11/11 18:03:19:921 EDT] 00000001 prefs W java.util.prefs.FileSystemPreferences syncWorld Couldn't flush user prefs: java.util.prefs.BackingStoreException: Couldn't get file lock.\n[9/11/11 18:03:49:929 EDT] 00000001 prefs W java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode Could not lock User prefs. Unix error code 2.", "CAUSE\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 :", "NOTE : The \"dot\" in front of the directories below represent that these are \"hidden\" directories. So the \"dot\" must be in front of the directory name to go into the directory or to access them. \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.", "For root : 1. Create a Java system pref directory\n sudo mkdir -p /etc/.java/.systemPrefs \n 2. Restart the application server." ]

[ "The non-root ID that is being used to start WebSphere Application Server does not have a user_home directory. Therefore this non-root ID is unable to access the root user's \"/etc/.java/.systemPrefs\". This produces the aforementioned warning messages every 30 seconds in the profile_root/logs/server_name/systemout.log.\n\nThe root ID used to start Websphere Application Server can not find the Java system pref file." ]

[ 1 ]

[ "IBM Getting a warning message 'You do not have the correct administrator privileges' when attempting to license a SPSS Statistics product on Mac OS. - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You have successfully installed an IBM SPSS Statistics product on a Mac computer. When you start the License Authorization Wizard (LAW) to enter the authorization code for licensing.\n\nYou receive the following message:\n\n\n\"Warning! You do not have the correct administrator privileges to license this product. Log in as administrator and try again, or contact your network administrator to correct this issue.\n\n\"\n\nOnce this message is displayed the only option available is \"OK\" to click on and you cannot enter your authorization code. \n\nRESOLVING THE PROBLEM\nBelow is a picture of the warning: \n\n[/support/docview.wss?uid=swg21966637&aid=1] [/support/docview.wss?uid=swg21966637&aid=1]\n\nIf you encounter this message, perform the following procedure:", "1. If open, close the IBM SPSS Statistics product. \n 2. If open, close the License Authorization Wizard. \n 3. Open Finder. \n 4. Select the 'Go' menu. \n 5. Select the 'Utilities' menu. \n 6. Open the 'Terminal' program. \n 7. Type (copy/paste) the following command:\n \n cd /Applications/IBM/SPSS/Statistics/ \n 8. \n 9. Press Enter/Return. \n 10. Perform the procedure corresponding to the Statistics product version as described below:\n\n\nStatistics Release 20 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 20\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.", "Statistics Release 21 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 21\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nStatistics Release 22 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 22\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\n\nStatistics Release 23 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 23\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.", "Statistics Release 24 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 24\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product. \n 7. \n 8. \n\nStatistics Release 25 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 25\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nTo confirm the changes have been made (1) In the Terminal window change directory to below path (example for release 22) \n\ncd /Applications/IBM/SPSS/Statistics/22/SPSSStatistics.app/Contents \n\nthen, type the following: \n\nls -l \n\n(2) Press Enter/Return.", "If you see some or all of subfolders shows a group ownership other than 'admin' (as displayed in Picture1), the procedure did not succeed. You will need to have your Mac IT support contact IBM SPSS Support for further assistance. \n\nPicture1:\n[/support/docview.wss?uid=swg21966637&aid=2] [/support/docview.wss?uid=swg21966637&aid=2]\n\nPicture 2: \n\nIf you see some or all of subfolders shows a group ownership of 'admin' (as displayed in Picture2), the procedure was successful.\n[/support/docview.wss?uid=swg21966637&aid=3] [/support/docview.wss?uid=swg21966637&aid=3]\n\nThis behavior is also reported on the following product correction report (APAR): [https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI41134]\n[https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI41134]\nhttps://www.ibm.com/support/entdocview.wss?uid=swg1PI41134 [https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI41134]\n\nAn IBM ID is required to access this material.", "If needed, an IBM ID may be created at https://ibm.biz/ibm_web_id [https://ibm.biz/ibm_web_id]\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\nNeed more help? Our Licensing forum is Live! [https://developer.ibm.com/answers/topics/spsslicensing.html]" ]

[ "Type (copy/paste) the following command: \n \n sudo chown -R root:admin 20\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product." ]

[ 1 ]

[ "IBM Insufficient ulimit Value Causes Native OutOfMemory - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n An out of memory may be observed on a system running WebSphere Application Server on Linux or AIX that is due to ulimit restrictions on number of process/threads per user. Further investigation may reveal a \"Failed to create a thread:\" message within the generated javacore which would indicate a native out of memory issue has been encountered. The cause of the problem may be an insufficient ulimit setting. While this type of issue can occur on any level of Linux, or AIX, the issue is most likely to be seen in systems running multiple instances of WebSphere Application Server using one userid. The following will outline how to identify if a process ulimit is the culprit and what WebSphere Application Server Support recommends to fix the case. \n\nSYMPTOM\nAn out of memory Dump Event such as:", "\"systhrow\" (00040000) Detail \"java/lang/OutOfMemoryError\"\n\"Failed to create a thread: retVal -1073741830, errno 11\" received\n\nNote: This detailed message will appear only in javacores.\n\n\nDIAGNOSING THE PROBLEM\nWhen using WebSphere Application Server, ulimits can be set to fix or tune around a number of problems. For more on how to set a ulimit refer to the \"Guidelines for setting ulimits [http://www-01.ibm.com/support/docview.wss?uid=swg21469413]\" Technote which goes into detail on setting different ulimits on various operating systems and the difference between the soft and hard limit. This article is concerned particularly with the \"-u\" ulimit or \"nproc\" limit on Linux, the ulimit - r on AIX which affects the number of threads allowed for a single user process running WebSphere Application Server.", "The AIX issue is less commonly seen as it limits then number of threads for a process but is seen in application servers with very large thread pools, This is becoming more common in 64bit addressing JVMs running complex applications. WebSphere Application support recommends setting the ulimit -r ulimited on AIX.\n\nThe nproc limit usually only counts processes on a server towards determining this number. Linux systems running WebSphere Application Server are a particular case. The nproc limit on Linux counts the number of threads within all processes that can exist for a given user. To determine the ulimit settings of a WebSphere Application Server process running on Linux refer to \"How to determine the ulimit settings of a running WebSphere Application Server process on Linux [http://www-01.ibm.com/support/docview.wss?uid=swg21407889]\".\n\nUser Limits (in bytes except for NOFILE and NPROC)", "type soft limit hard limit RLIMIT_AS unlimited unlimited RLIMIT_CORE unlimited unlimited RLIMIT_CPU unlimited unlimited RLIMIT_DATA unlimited unlimited RLIMIT_FSIZE unlimited unlimited RLIMIT_LOCKS unlimited unlimited RLIMIT_MEMLOCK 65536 65536 RLIMIT_NOFILE 65536 65536 RLIMIT_NPROC 131072 131072 \n\nFor most cases of older versions of Linux this value will be defaulted to around 2048. For out of the box Red Hat Enterprise Linux (RHEL) 6 the default value for nproc will be set to 1024. This low default setting for larger systems will not allow for enough threads in all processes. \n\nWebSphere Application Server Support recommends setting the ulimit -u or nproc to a value of 131072 when running on Linux to safely account for all the forked threads within processes that could be created.", "By using this recommended value a sufficient number of threads in all processes will be allowed and will not be a limiting factor for the environment. Increasing the limit to the suggested value should have no negative impact. When the number of threads in all processes reaches the -u ulimit, an out of memory error message will be thrown. This issue can be avoided by increasing this limit. Be aware that if the number of threads/processes reaches the recommended number of 131072 or close, the issue may be deeper and continuing to increase the -u ulimit will only prove to be a temporary fix. \n\nOnce the ulimit is increased, the WebSphere Application Server will need to be restarted to use the \nnew setting. In the case of WebSphere Application Server ND, the nodeagent and the servers on the nodes will need to be restarted." ]

[ "WebSphere Application Server Support recommends setting the ulimit -u or nproc to a value of 131072 when running on Linux to safely account for all the forked threads within processes that could be created." ]

[ 3 ]

[ "IBM Problems installing NMA agent (N4 agent) on Linux x86-64 - United States ITM Virtual environments install NMA N4 unable find bundle prerequisites CI addbundles TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The installation of NMA agent from package ITM for Virtual Environment V7.2.0.3 is failing with both remote or local installation on Linux x86-64. \n\nSYMPTOM\n1) The import of the whole bundle using command: \n\n/opt/IBM/ITM/bin/tacmd addbundles -i <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--", "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.\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---------------", "1) 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:", "Product 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>", "<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.", "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.\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", "[/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" ]

[ "The issues should be corrected at Installer level, APAR IV84919 has been opened to fix them. \n\nAnyway, since the correction involves the installation component, it will not be available until next release, when the Installation package will be built again." ]

[ 1 ]

[ "IBM Guidelines for setting ulimits (WebSphere Application Server) - United States ulimits; linux; unix; aix; openfiles; opensockets; sockets; socket; files; ulimit-n; limits.conf; configuration; security; etc; root; init; crontask; cron; nodeagent; dmgr; appserver; server; applicationserver; application; nofile; unlimited; 8000; 8192 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This document describes various ways to set ulimit values on UNIX and Linux operating systems as well as information that pertains to WebSphere Application Server \n\nSYMPTOM\nTuning ulimits correctly can overcome these errors: \n\n * Too Many Open Files \n * Could not lock User prefs. Unix Error Code 24. \n * Truncated Core Dumps / Heap Dumps\n\n\nRESOLVING THE PROBLEM", "Is it possible to display the current ulimit settings? The command ulimit -Xa will display all current settings that are set for the current login session, where X represents the hard (H) or soft (S) limits to be displayed. By default, if no value is supplied for X, soft limits will be displayed. However if a process is already running, it may have a different ulimit configurations than the current shell that you run the ulimit -a command in.\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", "Temporary settings are set via the command line using the ulimit command. The limit_name must be present in the command (see the chart below). These settings are only temporary for the current session and will be lost once the session is over or the terminal window is closed. \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.", "For 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:", "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. \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.", "Command 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", "There is no global settings file on HP-UX. Instead, you would need to issue the specific ulimit command in your shell's (or user's) profile configuration (like .profile or .login). \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.", "Command \"ulimit\" limit_name* Description ulimit -c [value] Core file size in 512 byte blocks. ulimit -d [value] Data segment size of processes in 512 byte blocks. ulimit -f [value] File size limit in 512 byes blocks. ulimit -n [value] Max number of open files and/or sockets per process. ulimit -m [value] The memory size of the process in 512 byte blocks. ulimit -s [value] The stack segment size in 512 byte blocks. ulimit -t [value]\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", "<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", "Solaris \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.", "Command 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.", "If 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]", "On Linux, can I set the ulimit for the number of open files to unlimited? Certain versions of Red Hat Enterprise Linux do not allow this value to be set to unlimited due to a known issue in Red Hat Enterprise Linux 5 [https://bugzilla.redhat.com/show_bug.cgi?id=507159]. The limit must be set to an integer value no larger than 1048576. Other versions of Linux may not have this restriction. In the Information Center for WebSphere Application Server, there is a recommendation [http://www.ibm.com/support/knowledgecenter/en/SSAW57_8.0.0/com.ibm.websphere.nd.doc/info/ae/ae/tprf_tunelinux.html] of 8000. \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", "[/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", "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. \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", "This was previously documented for AIX 6.1 in the following Knowledge Center article entitled \"telinit or init Command\", under the Environments section. Here's the quoted section: \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.\"", "RELATED 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]" ]

[ "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." ]

[ 1 ]

[ "IBM WebSphere Portal V6.1.0.5 and V6.1.5.2 hardware and software requirements - AIX - United States DSRdoc; SystemRequirementsDocument; prereq; coreq; installation prerequisites; 6105eGA 6152eGA V6105 V6.1.0.5 6.1.0.5 6105 6152 PRODUCT DOCUMENTATION\n\nABSTRACT\n IBM WebSphere Portal V6.1.0.5 and 6.1.5.2 hardware and software requirements on an AIX operating system. The hardware and software requirements reflect the versions of prerequisites and corequisites that were tested with WebSphere Portal V6.1.0.5 and 6.1.5.2. \n\nCONTENT\n\n\n\nTAB NAVIGATION\n * AIX [http://www.ibm.com/support/docview.wss?uid=swg27019359]\n * i5/OS [http://www.ibm.com/support/docview.wss?uid=swg27019362]\n * Windows [http://www.ibm.com/support/docview.wss?uid=swg27019366]\n\nIBM AIX\n\n\n\n\nWebSphere Portal Server Version 6.1.0.5 and 6.1.5.2 (AIX)", "This page describes the minimum product levels that need to be installed before opening a problem report with IBM WebSphere Portal Technical Support. The software versions and any maintenance levels listed on this page have been explicitly verified as working. \n\nEARLIER LEVEL OF A LISTED SOFTWARE: Software versions at a lower level than those noted on this page are unsupported. LDAP software at an earlier level is considered untested and best effort support only. For more details and exceptions, refer to the WebSphere Portal 6.1.x Support Statement [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc_v6101/overview/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 6.1.x in WebSphere Portal Support Statement Addendum - Unsupported Products [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27012957] (#7012957 [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27012957]).", "LATER LEVEL OF A LISTED SOFTWARE: Because other products frequently ship fixes, updates, and new releases, testing every configuration is not possible. In general, you can install and run with updates to supported products if those updates are compatible with the tested versions. For more details and exceptions, refer to the WebSphere Portal 6.1.x Support Statement [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc_v6101/overview/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 6.1.x in WebSphere Portal Support Statement Addendum - Unsupported Products [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27012957] (#7012957 [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27012957]).", "UNLISTED SOFTWARE: Software not listed on this page at any level is unsupported. LDAP software not listed is considered untested and best effort support only. For more details and exceptions, refer to the WebSphere Portal 6.1.x Support Statement [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc_v6101/overview/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 6.1.x in WebSphere Portal Support Statement Addendum - Unsupported Products [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27012957] (#7012957 [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27012957]).", "Operating systems\nsupported with 32-bit WebSphere Application Server and WebSphere Portal [/support/docview.wss?uid=swg27019359&amp;aid=1] * AIX Version 7 Release 1 (64-bit operating system) \n * AIX Version 6 Release 1 Technology level 0 Service release 4 (6100-00-04), or with higher Technology or Service release level (64-bit operating system) \n * AIX 5L Version 5 Release 3 Technology level 7 Service release 1 (5300-07-01), or with higher Technology or Service release level (32-bit or 64-bit operating system)", "[/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] Operating systems\nsupported with 64-bit WebSphere Application Server and WebSphere Portal [/support/docview.wss?uid=swg27019359&amp;aid=1] * AIX Version 7 Release 1 (64-bit operating system) \n * AIX Version 6 Release 1 Technology level 0 Service release 4 (6100-00-04), or with higher Technology or Service release level (64-bit operating system) \n * AIX 5L Version 5 Release 3 Technology level 7 Service release 1 (5300-07-01), or with higher Technology or Service release level (64-bit operating system)", "[/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] AIX hardware requirements [/support/docview.wss?uid=swg27019359&amp;aid=1] * IBM POWER family of processors \n * Disk space requirements: * Minimum 2.5 GB free disk space for installation for WebSphere Portal \n * Minimum 1.0 GB free disk space for installation for WebSphere Application Server \n * Minimum 4 GB total disk space recommended for installation \n \n \n * Physical memory: Under minimal load, WebSphere Portal can function with 2GB of RAM. However, 4GB is an optimal starting point for RAM in a production environment. \n * CD-ROM drive", "[/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] Application Servers\nThe WebSphere-supplied Java SDK is required for both the run time and any remote Java clients. [/support/docview.wss?uid=swg27019359&amp;aid=1] * WebSphere Application Server V7.0.0.11 with IBM SDK 1.6 SR12 (WebSphere Application Server product site) [http://www.ibm.com/software/webservers/appserv/was/]#1a#1b#1b \n * WebSphere Application Server V6.1.0.31 with IBM SDK 1.5 SR7 (WebSphere Application Server product site) [http://www.ibm.com/software/webservers/appserv/was/]#1a#1b * Note: IBM Java SDK V5 reached end of service in 2015. If you continue to use WebSphere Application Server 6.1.x after that date with extended support, Java SDK V5 is no longer included", "Refer to \"Required WebSphere Interim Fixes for WebSphere Portal V6.1.0.5 and V6.1.5.2 [http://www.ibm.com/support/docview.wss?uid=swg24027476]\" for the complete list of fixes required for WebSphere Application Server. [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] Optional WebSphere Servers [/support/docview.wss?uid=swg27019359&amp;aid=1] * WebSphere Application Server SCA feature pack 1.0.1.5 \n * WebSphere Application Server XML feature pack 1.0.0.5 \n * WebSphere Process Server V6.2.0.2*, 6.1.2.3, and 6.1.0.4 (all via Client Install option only with WAS 6.1x releases) *Refer to technote #1398123 for Process Server V6.2 Client installation [http://www.ibm.com/support/docview.wss?uid=swg21398123] \n * WebSphere Virtual Enterprise (formerly \"Extended Deployment\") V6.1.1.1, 6.1.0.5 (WebSphere Extended Deployment product site [http://www.ibm.com/software/webservers/appserv/extend/])", "JavaScript Library [/support/docview.wss?uid=swg27019359&amp;aid=1] * Dojo V1.3.2 or 1.1.1\n\nTo take advantage of the support for Microsoft Internet Explorer V8.0 or to use the new features in 6.1.5.2 such as Mashups integration and the Page Builder Theme, you will need to use Dojo V1.3.2. Refer to the topic \"Using a different Dojo version [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/topic/com.ibm.wp.ent.doc_v615/admin/epc_use_prior_dojo.html]\" for more information. [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] Databases\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n[/support/docview.wss?uid=swg27019359&amp;aid=1] * Derby V10.1 and 10.3", "* IBM DB2 Universal Database (DB2 product site) [http://www.ibm.com/software/data/db2/9/] (also supports High Availability Disaster Recovery (HADR) Feature) * V9.7 FP1 for Linux, Unix, Windows \n * V9.5 for Linux, Unix, Windows: Enterprise Server Edition 9.5 FP5, Express Edition 9.5 FP5, Workgroup Server Edition 9.5 FP5 (viper 2) (including HADR) \n * V9.1 for Linux, Unix, Windows: Enterprise Server Edition 9.1 FP9, Express Edition 9.1 FP9, Workgroup Server Edition 9.1 FP9 (including HADR) \n * V8.1 for Linux, Unix, Windows: Enterprise Server Edition 8.1 FP16, Express Edition 8.1 FP16, Workgroup Server Edition 8.1 FP16 (including HADR)\n \n \n * IBM DB2 for z/OS V9.1 and V8.1, PUT level 0901 or later maintenance (DB2 for z/OS product site) [http://www.ibm.com/software/data/db2/zos/]#2 (also supports High Availability Disaster Recovery (HADR) Feature) \n * WebSphere Information Integrator V8.2 FP4", "* Oracle (Oracle Database product site) [http://www.oracle.com/database/index.html] (Oracle Database clustering using RAC on all supported Oracle levels. Supports connect time failover#3a) * Standard/Enterprise V9.2.0.8, 10.1.0.5 Patch 4, 10.2.0.4 and 10.2.0.5 (patchset 8202632) (including RAC) (Supports Automatic Storage Management (ASM) Feature) \n * Oracle 11gR2 V11.2.0.1 (including RAC) \n * Oracle 11gR1 V11.1.0.7 (including RAC)\n \n \n \n * Microsoft SQL Server (Microsoft product site) [http://www.microsoft.com] * Enterprise Edition 2008 SP1 [http://www.microsoft.com] \n * Enterprise Edition 2005 SP3", "[/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] Java Database Connectivity (JDBC) Drivers [/support/docview.wss?uid=swg27019359&amp;aid=1] * DataDirect Connect JDBC 4.0 (type 4) (DataDirect Connect JDBC product site [http://www.datadirect.com/products/jdbc/index.ssp]) \n * DB2 Driver for JDBC and SQLJ 3.1 (type 2/4) \n * JCC JDBC driver level 3.58.90 or above to connect to DB2 for z/OS Note: Use the JDBC drivers provided with DB2 LUW V9.7 FP2 when the Portal is not also running on z/OS \n * Derby embedded JDBC Driver \n * Microsoft SQL Server JDBC Driver 1.2 or 2.0 (Microsoft SQL Server JDBC Driver site [http://msdn.microsoft.com/en-us/data/aa937724.aspx]) \n * Oracle 9i or 10g or 11g JDBC Driver Thin (type 4) (Oracle JDBC product site [http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html])", "[/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] Web servers\n[/support/docview.wss?uid=swg27019359&amp;aid=1] * Apache HTTP Server V2.0.5.9 (Apache Server product site) [http://httpd.apache.org/] (Apache Server 2.0.5.9 includes CERT Advisory CA-2002-17) \n * Apache HTTP Server V2.2 (Apache Server product site) [http://httpd.apache.org/] (Apache 2.2.x is supported with WebSphere Application Server 7.0.#4a)#4a \n * IBM HTTP Server for WAS V7.0 and 6.1 (IBM HTTP Server product site) (HTTP Server 7.0 is supported with WebSphere Application Server 7.0 only) [http://www.ibm.com/software/webservers/httpservers/]", "* IBM HTTP Server for iSeries V7R1, V6R1 and V5R4 (IBM HTTP Server product site) [http://www-03.ibm.com/systems/i/software/http/index.html](HTTP Server for i5/OS is provided natively on System i5 and is not bundled with or installed by WebSphere Portal. For V5R4, supported group PTF is SF99114 level 13; for V6R1, supported group PTF is SF99115 level 1. For V5R4, the license program number is 5722DG1; for V6R1, the license program number is 5761DG1. Issue the GO LICPGM to display all the installed licensed programs. For WebSphere Application 6.1.0.21 on V6R1M0, apply SI35071. For WebSphere Application 7.0.0.1 on V6R1M0, apply SI35078) \n * Microsoft Internet Information Services (IIS) V7.5 or 7.0 (only for WAS 7 environments) and 6.0 (Microsoft product site) [http://www.microsoft.com]", "* IBM Lotus Domino Enterprise Server V8.5.2, 8.5.1, 8.5, 8.0.2, 8.0.1, 8.0 and V7.0.3, 7.0.2, 7.0.1 (Lotus Domino product site) [http://www.lotus.com/products/product4.nsf/wdocs/dominohomepage]#4d(To use Lotus Domino Version 7.0 with WebSphere Application Server 6.1, you must install the Web Server plug-in for Lotus Domino Server Version 6 which is a part of the Web Server plug-in for WebSphere Application Server 6.1) \n * Sun Java System Web Server 7 Update 8 or 6.1 SP12 (Sun product site) [http://www.sun.com/products/]", "[/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] Web browsers\n(required for administration/configuration, sample program execution and launch pad. There is no restriction nor certification of Web browsers on clients that connect the server to display content) [/support/docview.wss?uid=swg27019359&amp;aid=1] * 6.1.0.5: * Microsoft Internet Explorer 8.0, 7.0, 6.0 (Microsoft product site) [http://www.microsoft.com] \n * Firefox V3.6, 3.5, 3.0, 2.0, 1.5.0.7 (Firefox product site) [http://www.mozilla.org/] \n * Apple Safari 3.2 and higher (Apple product site) [http://www.apple.com/safari/] \n * Apple Safari 4.0, 4.0.5 (Apple product site) [http://www.apple.com/safari/]", "Safari is not supported for use with the Common Mail portlet. For additional information, see Limitations on Safari Web browser. Mashup Integration not supported with Safari for Windows. [http://www.ibm.com/support/docview.wss?uid=swg21320077]\n * Opera 9.52 and higher [http://www.ibm.com/support/docview.wss?uid=swg21320077](Opera product site) [http://www.opera.com/products/]\n Drag and Drop functionality of administering portlets and pages is not supported with Opera. Opera is not supported for use with the Common Mail portlet or the Domino and Extended Products Portlets. For additional information, see Limitations on Opera Web browser. [http://www.ibm.com/support/docview.wss?uid=swg21318444]\n \n \n * \n * 6.1.5.2: * Microsoft Internet Explorer 8.0, 7.0, 6.0 (Microsoft product site) [http://www.microsoft.com] \n PageBuilder, Mashup Integration and Wiki/Blogs in V6.1.5.2 are not supported or functional when using Microsoft Internet Explorer V6.0.#6f", "* Firefox V3.6, 3.5, 3.0 (Firefox product site) [http://www.mozilla.org/] \n * Apple Safari 3.2 and higher (Apple product site) [http://www.apple.com/safari/] \n * Apple Safari 4.0, 4.0.5 (Apple product site) [http://www.apple.com/safari/]\n Safari is not supported for use with the Common Mail portlet. For additional information, see Limitations on Safari Web browser. Mashup Integration not supported with Safari for Windows. [http://www.ibm.com/support/docview.wss?uid=swg21320077]#6a#6e \n * Opera 9.52 and higher (Opera product site) [http://www.opera.com/products/]\n Drag and Drop functionality of administering portlets and pages is not supported with Opera. Opera is not supported for use with the Common Mail portlet or the Domino and Extended Products Portlets. For additional information, see Limitations on Opera Web browser. [http://www.ibm.com/support/docview.wss?uid=swg21318444]#6b", "[/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] LDAP servers\n[/support/docview.wss?uid=swg27019359&amp;aid=1] * IBM Lotus Domino Enterprise Server V8.5.2, 8.5.1, 8.5, 8.0.2, 8.0.1, 8.0 and V7.0.3, 7.0.2, 7.0.1 (Lotus Domino product site) [http://www.lotus.com/products/product4.nsf/wdocs/dominohomepage] For 7.0.2 and 7.0.1: Apply SPR KLIN6LRTHJ to be able to return Groups and Users by direct lookup. Turkish users should use version 7.0.3 or later.#7a \n * IBM Tivoli Directory Server 6.2, 6.1 and 6.0 (IBM Tivoli Directory Server product site) [http://www.ibm.com/software/tivoli/products/directory-server/] Add the fix for APAR IO02714 on applicable releases, available at IBM Support.#7b \n * IBM z/OS Security Server 1.7 and 1.6 (IBM z/OS Security Server product site) [http://www.ibm.com/systems/z/advantages/security/index.html]", "* IBM z/OS.e Security Server 1.7 and 1.6 (IBM z/OS Security Server product site) \n * Novell eDirectory 8.8 or 8.7.3 (Novell eDirectory product site) [http://www.novell.com/products/edirectory/] \n * Sun Java System Directory Server 7, 6.3, 6.1, and 6 (Sun product site) [http://www.sun.com/products/] \n * Microsoft Active Directory 2008, including Lightweight Directory Server (AD LDS, previously referred to as \"Application Mode\" or ADAM) \n * Windows Active Directory 2000 and 2003 including Application Mode", "[/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] Software for collaboration - Domino and Extended Products (optional) [/support/docview.wss?uid=swg27019359&amp;aid=1] * IBM Lotus Domino Enterprise Server V8.5.2, 8.5.1, 8.5, 8.0.2, 8.0.1, 8.0 and V7.0.3, 7.0.2, 7.0.1, 6.5.6 (IBM Lotus product site) [http://www.ibm.com/developerworks] Domino V8.5.2 also needs the fix applied for SPR DPOS895USS, contact Domino Technical Support for the fix. \n * IBM Lotus Domino Document Manager V7 and 6.5.1 \n * IBM Lotus Sametime V8.5, 8.0.2, 8.0, 7.5.1 and 7.5 (IBM Lotus product site) [http://www.ibm.com/developerworks]", "[/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] Software for content management (optional) [/support/docview.wss?uid=swg27019359&amp;aid=1] * IBM Lotus Web Content Management V6.1.0.5 or 6.1.5.2 (IBM Lotus Web Content Management product site) [http://www.ibm.com/software/lotus/products/webcontentmanagement/] \n * Ephox EditLive IBM LWCM OEM version 3.4.1.41 (which includes EditLive version 7.0.1.46.) (Ephox EditLive product site [http://www.ephox.com]) \n * IBM Lotus Quickr V8.5, 8.1.1 (IBM Lotus product site) [http://www.ibm.com/developerworks] \n * 6.1.5.2: IBM Lotus FileNet P8 V4.5 (IBM Lotus product site) [http://www.ibm.com/developerworks] \n * 6.1.5.2: IBM Content Manager V8.4 (IBM Content Manager product site) [http://www.ibm.com/software/data/cm/cmgr/]", "[/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] Supported Java Runtime Environments - Web Content Management authoring portlet [/support/docview.wss?uid=swg27019359&amp;aid=1] * Java Runtime Environments (requires one) V1.6.x or 1.5.x (Sun product site) [http://www.sun.com/products/]", "[/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] External Security software (optional) [/support/docview.wss?uid=swg27019359&amp;aid=1] * IBM Tivoli Access Manager V6.1 and 6.0 for trust association interceptor and enhanced trust association interceptor (support for Subject creation) (Tivoli Access Manager product site) [http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/] When using Tivoli Access Manager 6.0 for authorization or integrated user provisioning with WebSphere Portal, the Tivoli Access Manager AMJRTE component must be at the Version 5.1 fix pack 2 level or later. This version of AMJRTE component is automatically installed with WebSphere Application Server Version 5.1.1 or later, but must still be configured to work with WebSphere Portal.", "* IBM Tivoli Access Manager V6.0 for Java Authorization Contract for Containers (JACC) (Tivoli Access Manager product site) [http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/] When using Tivoli Access Manager 6.0 for authorization or integrated user provisioning with WebSphere Portal, the Tivoli Access Manager AMJRTE component must be at the Version 5.1 fix pack 2 level or later. This version of AMJRTE component is automatically installed with WebSphere Application Server Version 5.1.1 or later, but must still be configured to work with WebSphere Portal \n * Computer Associates SiteMinder V6.0", "[/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=1] Software for portlet development [/support/docview.wss?uid=swg27019359&amp;aid=1] * IBM Rational Application Developer V7.5 and 7.0.6 (plugin for UTE) \n * IBM Portlet Factory V6.1.5, 6.1\n\n[/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=2] [/support/docview.wss?uid=swg27019359&aid=3] [/support/docview.wss?uid=swg27019359&aid=3] Software for license management [/support/docview.wss?uid=swg27019359&amp;aid=1] * IBM Tivoli License Compliance Manager V2.3\n\n[/support/docview.wss?uid=swg27019359&amp;aid=1] [/support/docview.wss?uid=swg27019359&amp;aid=4] [/support/docview.wss?uid=swg27019359&aid=5] [/support/docview.wss?uid=swg27019359&aid=5]", "Related information\n[http://d02was006.southbury.ibm.com/support/dcf/preview.wss?host=d02dbs88.southbury.ibm.com&db=support/swg/swgdocs.nsf&unid=2D60E6429AA6F54285256FB00046AC9D&taxOC=SSCVS22&MD=2005/02/25%2008:02:00&sid=]Detailed system requirements [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27007791]\nWebSphere Portal Information Centers and more [http://www.ibm.com/developerworks/websphere/zones/portal/proddoc.html]\nSupport Statement [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc/overview/inst_req_supt.html] \n\nSee disclaimer. \n\nTop of page", "Disclaimer\nIBM reserves the right to change specifications and other product information without prior notice. This publication could include technical inaccuracies or typographical errors. References herein to IBM products and services do not imply that IBM intends to make them available in other countries. IBM PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. \n\nTop of page \n\n\n\n\nORIGINAL PUBLICATION DATE\n 2009/9/1" ]

[ "Oracle 11gR2 V11.2.0.1 (including RAC)" ]

[ 11 ]

[ "IBM Deletion of virtual portal fails with transaction timeout - United States virtual portal; timeout; delete; portlet; EJPAH4000E; EJPEB0804E; rollbackexception; admin; WTRN0006W TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nAttempt to delete virtual portal via Virtual Portal Manager portlet fails with error:\n\nEJPAH4000E: Failed to delete virtual portal \n\nAttempts to delete the virtual portal using the ConfigEngine task \"delete-virtual-portal\" may fail as well.\n\n\nCAUSE\nWith the introduction of Managed Pages in WebSphere Portal 8.0, virtual portal deletions require more transaction time when removing from the system. This increased transaction time can lead to an error situation if either of the following timeouts is exceeded: \n\n * the total and/or maximum transaction lifetime timeout value(s) for the server \n * the WCM component's transaction timeout\n\nDIAGNOSING THE PROBLEM\nSystemOut.log may show the following: \n\nExample #1:", "[9/10/12 10:08:43:757 AMT] 0000001a TimeoutManage I WTRN0006W: Transaction 00000139B080F02D0000000236122A9CB64A65E5C73B006CE4605EA6BEA57CC3F6A1783B00000139B080F02D0000000236122A9CB64A65E5C73B006CE4605EA6BEA57CC3F6A1783B00000001 has timed out after 120 seconds.\n\n[datestamp] 00000055 JTATransactio E RT0025E: Failed to save user transaction\ncom.ibm.icm.ci.CDMTransactionException\nat com.ibm.icm.ci.JCRUserTransaction.commit(JCRUserTransaction.java:189)\nat com.ibm.icm.ci.JTATransaction.commit(JTATransaction.java:166)\nat com.ibm.icm.jcr.RepositoryImpl.deleteWorkspace(RepositoryImpl.java:804)\nat com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:336)\n....\nCaused by: javax.transaction.RollbackException\nat com.ibm.tx.jta.impl.TransactionImpl.stage3CommitProcessing(TransactionImpl.java:1254)\n....", "[datestamp] 00000055 DeleteVPComma E com.ibm.wps.command.vp.DeleteVPCommand AbstractCommand.throwCommandException EJPEB0804E: DeleteVPCommand: An exception in the data backend occurred.\ncom.ibm.portal.resolver.exceptions.LocalizedIOException: EJPFB0002E: Exception occurred.\nat com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler.onVirtualPortalDeleted(JcrWorkspaceVirtualPortalHandler.java:348)\n....\nCaused by: javax.transaction.RollbackException\nat com.ibm.tx.jta.impl.TransactionImpl.stage3CommitProcessing(TransactionImpl.java:1254)\n.... \n\nExample #2:", "[datestamp] 000000f4 TimeoutManage I WTRN0006W: Transaction PA_MageVirtualPortals#MgeVirtualPortals.war#ManageVirtualPortals 00000143FA0D566200000001680EB7144589A0582D368B51A9A958DDACFF4F62EA89D95C00000143FA0D566200000001680EB7144589A0582D368B51A9A958DDACFF4F62EA89D95C00000001 has timed out after 120 seconds.\n[datestamp] 000000f4 TimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 8,5,main]. The stack trace of this thread when the timeout occurred was: \njava.net.SocketInputStream.socketRead0(Native Method)\njava.net.SocketInputStream.read(SocketInputStream.java:150)\njava.net.SocketInputStream.read(SocketInputStream.java:121)\ncom.ibm.db2.jcc.t4.x.b(x.java:208)\ncom.ibm.db2.jcc.t4.x.c(x.java:360)\ncom.ibm.db2.jcc.t4.x.c(x.java:473)\ncom.ibm.db2.jcc.t4.x.v(x.java:1241)\ncom.ibm.db2.jcc.t4.ab.a(ab.java:61)\ncom.ibm.db2.jcc.t4.p.a(p.java:50)\ncom.ibm.db2.jcc.t4.rb.b(rb.java:220)", "com.ibm.db2.jcc.am.po.qc(po.java:3498)\ncom.ibm.db2.jcc.am.po.b(po.java:4461)\ncom.ibm.db2.jcc.am.po.ic(po.java:799)\ncom.ibm.db2.jcc.am.po.executeUpdate(po.java:777)\ncom.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteUpdate(WSJdbcPreparedStatement.java:1187)\ncom.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeUpdate(WSJdbcPreparedStatement.java:804)\ncom.ibm.icm.da.portable.common.sql.PPreparedStatement.executeUpdate(PPreparedStatement.java:83) com.ibm.icm.da.portable.data.DeleteWorkspace.deleteWideTableData(DeleteWorkspace.java:359)\ncom.ibm.icm.da.portable.data.DeleteWorkspace.deleteWorkspace(DeleteWorkspace.java:130) com.ibm.icm.da.portable.data.DataManager.deleteWorkspace(DataManager.java:700)\ncom.ibm.icm.ci.workspace.impl.PDeleteWorkspaceImpl.deleteWorkspace(PDeleteWorkspaceImpl.java:84) com.ibm.icm.ci.workspace.impl.WorkspaceService.deleteWorkspace(WorkspaceService.java:270) com.ibm.icm.jcr.RepositoryImpl.deleteWorkspace(RepositoryImpl.java:808)", "com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:336)\ncom.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:324) com.ibm.wps.ac.impl.UnrestrictedAccessImpl.run(UnrestrictedAccessImpl.java:84)\ncom.ibm.wps.command.ac.ExecuteUnrestrictedCommand.execute(ExecuteUnrestrictedCommand.java:90) com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler.onVirtualPortalDeleted(JcrWorkspaceVirtualPortalHandler.java:345)\ncom.ibm.wps.command.vp.VirtualPortalHandlerImpl.onVirtualPortalDeleted(VirtualPortalHandlerImpl.java:396)\ncom.ibm.wps.command.vp.DeleteVPCommand.execute(DeleteVPCommand.java:178 com.ibm.wps.portlets.managevirtualportals.actions.DoDeleteVirtualPortalAction.deleteVirtualPortal(DoDeleteVirtualPortalAction.java:151)\n....", "RESOLVING THE PROBLEM\n1. Increase the total transaction lifetime timeout and maximum transaction timeout values (for example, to 600 seconds or greater) using the instructions in the Related information section below. \n\n2. If the problem persists after addressing the change in suggestion #1 and the error in SystemOut.log shows that the timeout still occurs after 120 seconds (as opposed to the increased value that you just set), then update to Cumulative Fix (CF) 9 or later to get the fix for APAR PI04872 and then add (or update if already exists) the following custom property to the WCM_WCMConfigService Resource Environment Provider: \n\nName: wcm.transaction.timeout \n\nValue: 600 (for example) \n\nNote: There is not a target value for a transaction timeouts that applies to every customer environment. The goal should be to find a value that allows the virtual portal deletion to succeed but does not introduce significant delay in being alerted for other transaction timeouts.", "RELATED INFORMATION\n#Transaction settings [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/tjta_settlog.html]\nPI04872 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI04872]\nSetting Resource Environment Provider custom properties [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Setting_service_configuration_properties_wp8]" ]

[ "With the introduction of Managed Pages in WebSphere Portal 8.0, virtual portal deletions require more transaction time when removing from the system. This increased transaction time can lead to an error situation if either of the following timeouts is exceeded: \n\n * the total and/or maximum transaction lifetime timeout value(s) for the server \n * the WCM component's transaction timeout" ]

[ 0 ]

[ "IBM Rational Host Access Transformation Services 9.0 - United States service release; modpack; mod pack; upgrade; refresh; refresh pack DOWNLOADABLE FILES\n\nABSTRACT\n IBM Rational Host Access Transformation Services 9.0 has been made generally available and contains fixes to version 9.0. \n\nDOWNLOAD DESCRIPTION\n \n\nTable of Contents Sections Description * What's new\n\nThis section provides an overview on what is new in this release with a description of any new functions or enhancements when applicable. * Impact assessment\n\nThis section provides information related to the impact of this release to allow you to assess how your environment may be affected. * Prerequisites\n\nThis section provides important information to review prior to the installation of this release. * Download package\n\nThis section provides the direct link to obtain the download package for installation in your environment. * Installation instructions", "This section provides the installation instructions necessary to apply this release into your environment. * Known problems\n\nThis section contains a link to the known problems (open defects) identified at the time of this release. Supporting Documentation Document Description * Detailed System Requirements [http://www.ibm.com/support/docview.wss?uid=swg27011794]\n\nClick to review the detailed system requirements information for a complete list of hardware requirements, supported operating systems, prerequisites and optional supported software, with component-level details and operating system restrictions. * Information Center [http://pic.dhe.ibm.com/infocenter/hatshelp/v90/index.jsp]", "The information center provides you with user assistance for the product. You can view, browse, and search online information related to the product. You can also visit IBM Product information [http://www.ibm.com/support/publications/us/library/index.shtml#letter_R] page to browse for additional information centers. * Fix List [http://www.ibm.com/support/docview.wss?uid=swg27027491]\n\nClick to review a complete list of the defects (APARs) resolved in this release including a list of resolved defects for the entire version family. PREREQUISITES\n IBM Installation Manager, Version 1.6.3.1 [http://www.ibm.com/support/docview.wss?uid=swg27025142] or later is required to install HATS 9.0.\n\nINSTALLATION INSTRUCTIONS\n For installation instructions, see Installing HATS [http://pic.dhe.ibm.com/infocenter/hatshelp/v90/topic/com.ibm.hats.doc/doc/gsinstal.htm] in the Rational Host Access Transformation Services (HATS) V9.0 Information Center.\n\nDOWNLOAD PACKAGE", "Download options Access type Description Passport Advantage [https://www.ibm.com/software/howtobuy/softwareandservices/passportadvantage] Passport Advantage and Passport Advantage Express clients are required to sign in to download the software package. IBM OEM software [https://www.ibm.com/software/howtobuy/softwareandservices/oem] IBM Software Group OEM offerings are designed for partners who develop and sell business solutions with embedded or bundled IBM middleware software. Clients with Flexible Contract Type (FCT) license purchases and IBM Business Partners must sign in to download the software package. HOW CRITICAL IS THIS FIX?", "Impact Assessment Impact Description Recommended This release is a service release of Rational Host Access Transformation Services 9.0. It contains new features as well as fixes for client-reported and internally found defects. PROBLEMS SOLVED\n Click the Fix List link in the table of contents above to review a list of the problems solved in this release.\n\nKNOWN SIDE EFFECTS\n The following defects were not resolved in this release.", "APAR Description IC94113 [http://www.ibm.com/support/docview.wss?uid=swg1IC94113] DBCS characters behind DDS window border are garbled. IC94307 [http://www.ibm.com/support/docview.wss?uid=swg1IC94307] Rich client: Part of DBCS fixed character is damaged. \nFor up-to-date information about known issues and workarounds, see Rational Host Access Transformation Service 9.0 - Known issues and workarounds [http://www.ibm.com/support/docview.wss?uid=swg27038663]. \nCHANGE HISTORY\n For what's new in HATS 9.0, see the Rational Host Access Transformation Services (HATS) V9.0 Information Center [http://pic.dhe.ibm.com/infocenter/hatshelp/v90/index.jsp]. \n\n \n\nBack to top\n\n\nTECHNICAL SUPPORT\n \n\nTAB NAVIGATION\n * General Support Information- selected tab,\n * Support Resources [http://www.ibm.com/support/docview.wss?uid=swg27020747]- selected tab,\n\n\n\n\nIBM Rational Software Support Communities", "* Visit the IBM Support Portal [http://www.ibm.com/support/entry/portal/Overview/Software/Rational/product] to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.\n \n \n * Visit developerWorks [http://www.ibm.com/developerworks/rational/] to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community [http://www.ibm.com/developerworks/rfe/].\n \n \n * Visit the Jazz Community [http://jazz.net/] if you use a Rational product created using the Jazz platform to interact directly with the Jazz development team and other community members, download product trials and betas and track developement progress.", "HELPFUL 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.", "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]. \n\n \n\nFollow IBM Rational Client Support on Twitter [http://twitter.com/rationalsupport] | Facebook [http://facebook.com/rationalsupport] | YouTube [http://www.youtube.com/ibmrationalsupport] | devWorks Blog [https://www.ibm.com/developerworks/mydeveloperworks/blogs/nfrsblog/?lang=en]\n\n\n\n\n Back to top \n\n [/support/docview.wss?uid=swg24035040&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24035040&aid=2]Problems (APARS) fixed\nIC87102, IC87488, IC87959, IC88940, IC88981, IC89933, IC91191, IC91370, IC91420, IC92195" ]

[ "For installation instructions, see Installing HATS [http://pic.dhe.ibm.com/infocenter/hatshelp/v90/topic/com.ibm.hats.doc/doc/gsinstal.htm] in the Rational Host Access Transformation Services (HATS) V9.0 Information Center." ]

[ 2 ]

[ "IBM Monitoring for Virtual Environments: VMware VI 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001 - United States DOWNLOADABLE FILES\n\nABSTRACT\n This is an Interim Fix for IBM Tivoli Monitoring for Virtual Environments: VMware VI 7.2 Fix Pack 2 reports \n\nDOWNLOAD DESCRIPTION\n(C) Copyright International Business Machines Corporation 2015. \n\n\n All rights reserved.\n\nComponent: IBM(R) Tivoli(R) Monitoring for Virtual Environments: VMware VI\nAgent TCR Reports, Version 7.2 Fix Pack 2\n\nComponent ID: 5724L92AG\n\nInterim Fix: 0001, 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001\n\nDate: January 23, 2015\n\nContents:\n\n1.0 General description\n2.0 Problems fixed\n3.0 Architecture and prerequisites\n4.0 Image directory contents\n5.0 Installation instructions\n6.0 Additional installation information\n7.0 Known problems and workarounds\n8.0 Additional product information\n9.0 Copyright and trademark information\n10.0 Notices\n\n\n1.0 General description\n-----------------------", "This interim fix resolves the APARs and defects listed in the\n\"Problems Fixed\" section below. \n\n\n2.0 Problems fixed\n------------------\n\nThe following problems are addressed by this fix.\n\n2.1 APARs\n---------------\nNone.", "2.2 Defects\n-----------\nDefect: 210286\nAbstract: Update model for VM PARTITION\nAdditional information: For \"Free_Space\" and \"Used_Space\" attributes, the\ndefault aggregation is defined not as AVG but as SUM. It usually\nworks as expected but if there were two entries which have same\n\"Timestamp\", the \"VM_PARTITION\" attribute group's data is shown\nwith doubled values.\nDefect: 212729\nAbstract: Drill through feature is not working in VE 7.2 FP2 reports\nAdditional information: A few VMware VI reports are showing the following\nmessage, when we try drill through by clicking on report chart:\nRSV-CM-0005 Content Manager did not return an object for the\nrequested search path.\nDefect: 212776\nAbstract: Datacenter parameter/prompt is missing in a few VM reports\nAdditional information: The Datacenter parameter/prompt is missing in the\nfollowing VMware VI reports: VM Heat Chart, Bottom N VMs by\nResource Pool and Top N VMs By Resource Pool.\nDefect: 212851", "Abstract: Place Date range parameter after the Resource prompts\nAdditional information: A few VMware VI reports contain time selection over\nresource selection. Therefore to make uniformity across the reports,\nplace Date range parameter after the resource prompts (like Data\nCenter and Cluster).\nDefect: 212924\nAbstract: Unsorted resources e.g.Cluster on parameter selection page\nAdditional information: Most of the VMware VI reports sometimes display \nunsorted resources (viz. Data Center, Cluster, Host Servers, VMs\netc.) on parameter selection (aka prompt) page.\nDefect: 212925\nAbstract: Incorrect caption/label for Host Server resource parameter\nAdditional information: Incorrect caption/label for the resource parameter\ne.g. In Network usage by VMs report, the \"Host Server(s)\" drop\ndown list title needs to be corrected as \"Host Server\" as user\ncan select only one host in this report.", "2.3 Enhancements\n------------------\nFeature: 210245\nAbstract: Enhance model to add SAMPLES.\nAdditional information: Add SAMPLES query item/column for each summarized\nattribute group view (viz. Hourly, Daily, Weekly and Monthly)\nin existing VMware VI Agent reports data model.\nFeature: 213018\nAbstract: RFE 60331: Require a new report for Cluster Utilization Details\nAdditional information: Require a new cluster level report like the Host \nServer Utilization Details report, which is useful and included the\nactual data points from the graph at the bottom of the report.\nDefect: 213084\nAbstract: Provide a choice to select date range or start & end week\nAdditional information: Provide a parameter choice (aka date filter option)\nto either select date range or start and end week of the year in\nthe following VMware VI reports: Cluster Weekly Comparison and\nHost Servers Weekly Comparison.\n\n2.4 Superseded fixes\n---------------------\nNone.", "2.5 APARs and defects included from superseded fixes\n---------------------------------------------------------------\nNone.\n\n\n3.0 Architecture and prerequisites\n----------------------------------\n\nThis fix is supported on all operating systems listed in the IBM Tivoli\nMonitoring for Virtual Environments: Dashboard, Reporting, and Capacity Planning\nUser's Guide, version 7.2 Fix Pack 2. See chapter 9 for information on the Tivoli\nCommon Reporting.\n\nThe User's Guide is here:\n\nhttp://www.ibm.com/support/knowledgecenter/SS9U76_7.2.0.2/com.ibm.tivoli.itmvs.doc_7.2.0.2/vedrcp72fp2_user.pdf [http://www.ibm.com/support/knowledgecenter/SS9U76_7.2.0.2/com.ibm.tivoli.itmvs.doc_7.2.0.2/vedrcp72fp2_user.pdf]\n\nPlease refer to the IBM Software Product Compatability Reports (SPCR)\nfor the latest operating system certification information:\nhttp://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]", "3.1 Prerequisites for this fix\n------------------------------\n\nThe prerequisite level for this fix is defined in Chapter 9 of the IBM Tivoli\nMonitoring for Virtual Environments: Dashboard, Reporting, and Capacity Planning\nUser's Guide, version 7.2 Fix Pack 2.\n\n\n4.0 Image directory content\n---------------------------\n\nThis fix image contains the following files:\n- 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001.README - This README file\n- 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001.zip - Fix archive .zip format.\n\nThe fix archive file contains the following directories and files,\nwhich is the same as the format found in the reports directory\nof the IBM Tivoli Monitoring for Virtual Environments V7.2 Fix Pack 2\nDashboards, Capacity Planner and Reports (TMVE), Multilingual media \nas found on Passport Advantage:\n- gui\n- lib\n- model\n- reports\n- scripts\n- setup_aix.bin\n- setup_hpux.bin\n- setup_linux.bin\n- setup_solaris.bin\n- setup_windows.exe\n- silent_installer.properties\n- tcr_install.properties", "Note that this Interim Fix is a complete replacement of these\nfiles.\n\n5.0 Installation instructions\n-----------------------------\nThis fix can be installed over an existing installation or as\na new install. Expand the archive file, \n7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001.zip, and copy the files in any\nlocation on the same computer where the Tivoli Common Reporting \nserver is installed.", "Use the following procedure to import reports that are bundled by using\nthe report installer:\n1. From the \\7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001 directory on the product file, run the \ncommand appropriate for your operating system:\n• setup_aix.bin (for AIX)\n• setup_hpux.bin (for HP-UX)\n• setup_linux.bin (for Linux)\n• setup_solaris.bin (for Solaris)\n• setup_windows.exe (for Windows)\nThe installer window opens.\n2. Choose your language and click OK.\n3. On the Welcome page click Next.\n4. Specify the Tivoli Common Reporting installation directory, such as\n<JazzSM_Home>/reporting if you are using Tivoli Common Reporting 3.1 or\nlater with Jazz for Service Management and <TIP_Home>/TCRComponents if\nyou are using Tivoli Common Reporting 2.1.1 with Tivoli Integrated Portal.\nYou can use the default folder or use the Browse button to provide the\npath. Click Next.\n5. Choose the reports you want to install. Click Next.\n6. Enter the Tivoli Common Reporting user name and password. Click Next.", "7. For each data source and data script, enter the data source configuration \ninformation. Enter the following details for the selected cognos reports, and \nthen click Next:\n• In the Enter the database username field, enter the administrator user name.\n• In the Enter the user password field, enter the password.\n• In the Choose the database type list, select the database type.\n• In the Enter the database name field, enter the warehouse database name. For DB2\nor Oracle, enter the database name. For MS SQL, enter the ODBC Data Source Name.\n8. On the Data Script runDbScript Configuration page:\na. Click the JDBC User Credentials tab, and enter the Tivoli Data Warehouse database \nuser name and password to be used during the installation. Check the box to skip \ndefining the data source now.\nb. Click the JDBC Database Credentials tab, and select database type. Edit the JDBC URL, \nJDBC driver file names, and JDBC driver class for the selected database type and then \nclick Next.", "• For DB2 database, required driver files are db2jcc.jar and db2jcc_license_cu.jar \n(Note: JDBC credentials must have db2admin privileges.)\n• For Oracle database, required driver file is oraclethin.jar\n• For MS SQL Server database, required driver file is sqljdbc.jar\n9. On the Report Installer Summary page, verify the reports to be installed, click Install, \nand wait for the installer to finish.\n10. The post-installation report is displayed. Check if the installation was successfully \nfinished and click Done.", "Results:\nAgent reports are now installed on your Tivoli Common Reporting server.\n\nAlternatively, see Topic: Importing reports by using the report installer \nin Chapter 17 of the IBM Tivoli Monitoring Administrator's Guide, \nversion 6.3 Fix Pack 2 for install instructions.\n\nThe Administrator's Guide is here:\n\nhttp://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/itm63fp2_admin.pdf [http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/itm63fp2_admin.pdf]\n\n\n6.0 Additional installation information\n---------------------------------------\nNone\n\n\n7.0 Known problems and workarounds\n----------------------------------\nNone\n\n\n8.0 Additional product information\n----------------------------------\nNone \n\n\n9.0 Copyright and trademark information\n---------------------------------- \nA current list of IBM trademarks is available on the Web at \"Copyright\nand trademark information\" at www.ibm.com/legal/copytrade.shtml.", "10.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.", "Java and all Java-based trademarks and logos are trademarks or\nregistered trademarks of Oracle and/or its affiliates. \n\nUNIX is a registered trademark of The Open Group in the United States \nand other countries.\n\nLinux is a registered trademark of Linus Torvalds in the United States,\nother countries, or both.\n\nOther company, product, or service names may be trademarks or service\nmarks of others.", "Third-Party License Terms and Conditions, Notices and Information\n-----------------------------------------------------------------\nThe license agreement for this product refers you to this file for\ndetails concerning terms and conditions applicable to third party\nsoftware code included in this product, and for certain notices and\nother information IBM must provide to you under its license to\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.", "Notwithstanding the terms and conditions of any other agreement you\nmay have with IBM or any of its related or affiliated entities\n(collectively \"IBM\"), the third party software code identified below\nare \"Excluded Components\" and are subject to the following terms and\nconditions:\n\n- the Excluded Components are provided on an \"AS IS\" basis\n- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND\nCONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT\nNOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE\nAND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND\nFITNESS FOR A PARTICULAR PURPOSE\n- IBM will not be liable to you or indemnify you for any claims\nrelated to the Excluded Components\n- IBM will not be liable for any direct, indirect, incidental,\nspecial, exemplary, punitive or consequential damages with respect\nto the Excluded Components. \n\nPREREQUISITES\nIBM Tivoli Monitoring for Virtual Environments: VMware VI Agent, version 7.2 Fix Pack 2", "INSTALLATION INSTRUCTIONS\nPlease refer to the full README contained in the Download Description section above for general installation instructions.\n\nDOWNLOAD PACKAGE\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001 23 Jan 2015 English 53552332 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm/Tivoli&product=ibm/Tivoli/Tivoli+Monitoring+for+Virtual+Servers&release=All&platform=All&function=fixId&fixids=7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001&includeSupersedes=0] [ ]" ]

[ "Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001 23 Jan 2015 English 53552332 FC" ]

[ 16 ]

[ "IBM JDBC driver or database insufficiencies cause administration portlets to fail. - United States RT0002E; JDBC; database; driver; RepositoryException; PLS; EJPAS0017E TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nYou attempt to create a new page via the Manage Pages portlet or add a portlet to a page via the Edit Layout portlet and encounter an error.", "SYMPTOM\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...", "CAUSE\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:", "WAS 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]" ]

[ "The JDBC driver does not meet WebSphere Portal v8's prerequisites." ]

[ 2 ]

[ "IBM Security Bulletin: Apache Commons FileUpload Vulnerabilities in IBM WebSphere MQ File Transfer Edition component (CVE-2016-1000031) - United States SECURITY BULLETIN\n\nSUMMARY\n The DiskFileItem class in Apache Commons Fileupload before version 1.3.3, used in IBM WebSphere MQ File Transfer Edition, specifically the Web Gateway component, could allow remote attackers to execute arbitrary code under the context of the current process, causing an undefined behavior. \n\nVULNERABILITY DETAILS", "CVEID:CVE-2016-1000031 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031]\nDESCRIPTION:Apache Commons FileUpload, used in IBM WebSphere MQ File Transfer Edition, could allow deserialization of untrusted data in the DiskFileItem class of the FileUpload library. A remote attacker could exploit this vulnerability to execute arbitrary code under the context of the current process.\nCVSS Base Score: 9.8\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/117957 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117957]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) \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", "REMEDIATION/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", "*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." ]

[ "CVEID:CVE-2016-1000031 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031]\nDESCRIPTION:Apache Commons FileUpload, used in IBM WebSphere MQ File Transfer Edition, could allow deserialization of untrusted data in the DiskFileItem class of the FileUpload library. A remote attacker could exploit this vulnerability to execute arbitrary code under the context of the current process.\nCVSS Base Score: 9.8\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/117957 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117957]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)" ]

[ 1 ]

[ "IBM How Connect TDWC 9.3 to TWS Engine lower level release - United States dwc 93; connect; SSL ; TLS TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n DWC 9.3 users cannot connect to TWS Engine lower level releases (8.5.1 until 9.2) \n\nSYMPTOM\nUnable to connect to TWS 8.5.1 ,8.6 or 9.1/9.2 from DWC 9.3. \n\nCheck the WAS SystemOut.log for error :\n\nSSL0080E: javax.net.ssl.SSLHandshakeException - The client and server could not negotiate the desired level of security. Reason: Server chose SSLv3, \nbut that protocol version is not enabled or not supported by the client. javax.net.ssl.SSLHandshakeException: Server chose SSLv3, but that protocol version is not enabled or not supported by the client.\n\n\nCAUSE\nDWC 9.3 is packaged with WAS 8.5.5.4 and due to known vulnerabilities has SSLV3 disabled. However TWS 9.2 and earlier versions use SSLv3 by default and so the DWC 9.3 cannot connect\n\n\nRESOLVING THE PROBLEM\nYou can solve this problem by configuring your TWS engines to use TLS instead of SSL :", "Backup and edit : \n\nTWA_HOME/WAS/TWSProfile/config/cells/TWSNodeCell/security.xml \n\nFind sslProtocol and change \"SSL_TLS\" to \"TLS\" \n\nFind ssl.protocol and change value=\"SSL\" to value=\"TLS\" \n\nBackup and edit : \n\nTWA_HOME/WAS/TWSProfile/properties/ssl.client.props \n\nFind com.ibm.ssl.protocol=SSL and change to com.ibm.ssl.protocol=TLS \n\nBackup and edit : \n\nTWA_HOME/WAS/TWSProfile/temp/ssl.client.props \n\nFind com.ibm.ssl.protocol=SSL and change to com.ibm.ssl.protocol=TLS \n\nStop and restart WAS. \n\n*Be aware that your Engines are now using TLS and so you must also reconfigure any DWC 9.2 or 9.1 installations that need to connect to those engines. You would change them to use TLS in the same way as above but also by the same changes in these copies of security.xml and ssl.client.props : \n\nTWA_HOME/JazzSM/profile/config/cells/JazzSMNode01Cell/security.xml \n\nTWA_HOME/JazzSM/profile/properties/ssl.client.props \n\nTWA_HOME/JazzSM/profile/temp/ssl.client.props", "Please consider that since you configure with TLS the WAS of TWS Engine also the Dynamic Agent can be impacted. \n\nSee technote 1689332." ]

[ "DWC 9.3 is packaged with WAS 8.5.5.4 and due to known vulnerabilities has SSLV3 disabled. However TWS 9.2 and earlier versions use SSLv3 by default and so the DWC 9.3 cannot connect" ]

[ 0 ]

[ "IBM Handling 302 redirect error message in a Web Application Firewall - United States HTTP; Redirect; 302; non idempotent TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n DataPower is preventing POST based HTTP redirect in accordance with RFC and displays this as part of the error in the logs:\n\nRedirect and failed due to non idempotent request method. (RFC 2616 sec 10.3) \n\nSYMPTOM\nThis technote pertains to the following errors. \n\nExample 1: This example shows the service getting the following message: a Backside header failed to parse due to: Failed to establish a backside connection with a HTTP Redirect and failed due to non idempotent request method. (RFC 2616 sec 10.3) message.", "web-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.", "Wed 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", "DIAGNOSING 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]", "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" ]

[ "To resolve the issue, the IBM WebSphere DataPower SOA appliance web application firewall can be configured to handle these \"302 Redirects\"." ]

[ 3 ]

[ "IBM Automatically renew trusted credential - United States security; trusted credentials SSO renew TECHNOTE (FAQ)\n\nQUESTION\n How do I choose the value to use for the Security > Authentication > Automatically renew trusted credential setting? \n\nANSWER\nFor IBM Cognos Business Intelligence(BI) deployments that do not implement a single sign-on (SSO) solution, stored credentials used for running scheduled activities can be automatically updated. When a user logs into the IBM Cognos BI application with a user name and password, the trusted credential used to run schedules when not logged in will be refreshed as well. This removes the burden from the end user of having to remember to manually refresh their trusted credentials and may eliminate failed activities caused by changed or expired user credentials.\nThe credential refresh behaviour is controlled by the Security > Authentication > Automatically renew trusted credential setting in Cognos Configuration.", "* Primary namespace only (default setting): When you log on to the first namespace of your session, if you have trusted credentials for that account, the credentials are updated for the primary account only. All other credentials for other namespaces are not updated.\n \n * Off: Credentials are not updated in any namespace.\n \n * All namespaces: When you log on to the first namespace, your credentials are updated as described for \"Primary namespace only\". When you log on to additional namespaces, if your trusted credentials associated with the primary account contain logon information for that namespace, then those trusted credentials are updated. NOTE: Do not use the All namespaces option if users authenticate into secondary namespaces as different users.\n\n\nA user's trusted credentials for a namespace will only be renewed once per day.", "It is NOT possible to use SSO with the feature 'Automatically Renew Trusted Credentials' found in Cognos BI. The reason for this is due to the following:", "\"A trusted credential is special because the namespace credentials it stores must be usable at any time, not depending on any timestamp. This rules out SSO tickets like Kerberos tokens or SAP tokens as they will expire after a short time and will become unusable. A suitable trusted credential therefore usually is a pair consisting of a user name and a password. However, for SSO based authentication to IBM Cognos BI, there is no password available to the namespace that can be stored into the trusted credential. Therefore, this feature will only work for basic authentication, when the user provides a user name and password to the login screen.\" RELATED INFORMATION\n Proven Practices: Securing the IBM Cognos 10 BI Environ [http://www.ibm.com/developerworks/data/library/cognos/security/cognos_bi_platform/page602.html]\nCognos Analytics 11 Equivalent Technote [http://www-01.ibm.com/support/docview.wss?uid=swg21998776]" ]

[ "For IBM Cognos Business Intelligence(BI) deployments that do not implement a single sign-on (SSO) solution, stored credentials used for running scheduled activities can be automatically updated. When a user logs into the IBM Cognos BI application with a user name and password, the trusted credential used to run schedules when not logged in will be refreshed as well. This removes the burden from the end user of having to remember to manually refresh their trusted credentials and may eliminate failed activities caused by changed or expired user credentials.\nThe credential refresh behaviour is controlled by the Security > Authentication > Automatically renew trusted credential setting in Cognos Configuration." ]

[ 0 ]

[ "IBM Tivoli Network Manager IP Edition 4.2.0 Fix Pack 3, 4.2.0-TIV-ITNMIP-FP0003 - United States DOWNLOADABLE FILES\n\nABSTRACT\n This fix pack is a cumulative fix release and addresses several APARs and internally found issues since the release of Tivoli Network Manager IP Edition 4.2.0 Fix Pack 2. \n\nDOWNLOAD DESCRIPTION\nWHAT'S NEW: [http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__descriptio]\n\n\nhttp://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__descriptio [http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__descriptio]n\n\nSummary of the Enhancements included in this Fix Pack:\nThe following features and functions are introduced in Fix Pack 3.\n\nSupport for SLES 12.0 \n\n * \n\n\nSupport for DB2 version 11.1 *", "Support for IBM zLinux Systems * \n * Red Hat Enterprise zLinux Server 7.3 (s390x, 64 bit) SuSE zLinux Enterprise Server (SLES) 12.0 SP1(s390x,64 bit) \n * \n * \n * \n * \n * https://www.ibm.com/software/passportadvantage/pao_customer.html\n * \n\n\nOffline geographical maps * \n\n\nCustom geographical map layers * \n\n\nRegional aggregation for geographical maps * \n\n\nBefore installing or upgrading Network Manager, refer to the Fix Pack Release notes: \nhttp://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html [http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html] \n\n\n===================================================================== \nSummary of fixes in V4.2.0 Fix Pack 3 \n===================================================================== \nFor details of an individual APAR, go to www.ibm.com/support [www.ibm.com/support] then enter the APAR name/# in \"Search Support\" then select search.", "IV89573 EXPAT XML PARSER VULNERABILITIES IV90563 DELAY RCA REPROCESSING UPON SEEING CLEAR FOR ROOTCAUSE ALERT IV90626 CISCO WEBTOOLS SEND EMPTY EMAIL IV90807 SLOW PROCESSING IN STITCHER SWITCHFDBTOCONNECTIONS IV91086 THE DISCOVERY PROCESSES CANNOT BE STARTED FROM THE ITNM GUI WHEN ITNM IS INSTALLED IN A MASTER/SLAVE SETUP IV91094 IP Filtered view incorrectly skips links between non-matched interfaces IV91222 COLLAPSING A SUBGRAPH LEAVES THE NODES AN UNUSABLE DISTANCE FROM EACH OTHER. IV91592 TELLABS JAVA COLLECTOR TO DISPLAY CARD NAMES. IV91725 TIMER THREADS ARE NOT TIMELY GARBAGE COLLECTED IN THE STRUCTURE BROWSER TREE. IV92191 Huawei MPLSTelnet parse the recent 'display ip vpn-instance verbose' format incorrectly. This result in incorrect association of VPN Name and the respective interface IV92353 POLLER CORES STARTING SNMP POLICIES WITH ENTITIES IN SCOPE THAT HAVE NO IFNAME IV92982 RCA PLUGIN SGMENTATION FAULT OVER SMALLER NUMBER OF CHANGES IV93054 ITNM DEVICESTRUCTURE - INFERFACE", "EVENTS NOT INCLUDED IV93591 NO DATA BEING DISPLAYED ON TOP N PERFORMERS WIDGET IN THE NETWORK HEALTH DASHBOARD IV94005 DYNAMIC DISTINCT NETWORK VIEW CREATES EXTRA/DUPLICATE VIEWS. IV94658 LOCAL TYPE TOOLS FOR CONTEXT MENU IS NOT SUPPORTED BY ITNM 4.2", "Known problems with V4.2.0 Fix Pack 3 \nhttp://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html#relnotes__problems [http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html#relnotes__problems] PREREQUISITES\nPrerequisites and Installation Instructions \n\nSee http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_installing.html [http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_installing.html]\n\nINSTALLATION INSTRUCTIONS\nIBM TIVOLI NETWORK MANAGER IP EDITION V4.2.0 FIX PACK 3\n=======================================================\n\nBuild 4.2.0.34\nThis document describes the known problems and APAR fixes for Network Manager V4.2.0 Fix Pack 3.\n\nCopyright IBM Corporation 2017", "1 WHAT'S NEW\nSee http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__description [http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__description]\n\n2 INSTALLATION\nSee http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_installing.html [http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_installing.html]\n\n3 POSTINSTALLATION AND CONFIGURATION\nSee http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_postinstallationtaskssummary.html [http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_postinstallationtaskssummary.html]", "4 KNOWN PROBLEMS AND LIMITATIONS\nSee http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__problems [http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__problems]\n\n5 SUMMARY OF APAR FIXES IN NETWORK MANAGER V4.2.0 FIX PACK 3\nSee http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__apar-fixes [http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__apar-fixes]\n\nURL LANGUAGE SIZE(Bytes) 4.2.0_README_FP0003 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0_README_FP0003&source=SAR] English 7178 \nDOWNLOAD PACKAGE", "Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options", "What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 4.2.0-TIV-ITNMIP-AIX-FP0003 28 Apr 2017 Language Independent 3091689671 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0-TIV-ITNMIP-AIX-FP0003&source=SAR] [ ] 4.2.0-TIV-ITNMIP-Linux-FP0003 28 Apr 2017 Language Independent 3091689662 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0-TIV-ITNMIP-Linux-FP0003&source=SAR] [ ] 4.2.0-TIV-NOIHD-AIX-FP0003 28 Apr 2017 Language Independent 27899824 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0-TIV-NOIHD-AIX-FP0003&source=SAR] [ ] 4.2.0-TIV-NOIHD-Linux-FP0003 28 Apr 2017 Language Independent 27899818 FC", "[http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0-TIV-NOIHD-Linux-FP0003&source=SAR] [ ]" ]

[ "http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__description" ]

[ 5 ]

[ "IBM How to Rollback From a Fix Pack or Interim Fix to an Earlier Build - United States uninstall; revert; downgrade; hotsite; HS; out; fixpack TECHNOTE (FAQ)\n\nQUESTION\n There may be times when there is a need to remove a previously installed Fix Pack or Interim Fix (hotsite) and revert to the original installed version. This document describes how to roll back an installed Fix Pack or Interim Fix applied to Cognos BI. \n\nANSWER\nAssuming create backup was selected, there will be a folder with the backup under the uninstall directory. Use these files to roll back. In version 10.2.1 FP1 and above there is no option to create a backup, instead backups are automatically created in the <cognos_install>/bkp directory.\nNote that the backup directories only contain copies of all individual files that were modified by the fix pack or interim fix, not the entire contents of the original directory.", "Care must also be taken when removing interim fixes to ensure that there weren't later interim fixes applied which also contain some of the same files. It is recommended that a full system and content store backup be performed before attempting.\n\nSteps:", "1. Stop the Cognos service and ensure that Cognos Configuration is not running. \n 2. When setting up the configuration of a newly installed Cognos BI environment, it is important to note that if you configure the new installation against the original content store, it is permanently upgraded to the new version and can no longer be used in the original environment. As a result, always create a backup of the content store prior to upgrading.\n If a roll back to the original version is required, you can simply restore the backup. However, any work done after the content store has been upgraded (reports, models, security, etc...) to the new version will be lost, as all of this information is saved in the content store.\n If you try to revert back to an earlier environment configured against the upgraded content store, you will get an error similar to the one below:", "CM-CFG-5027 Unable to upgrade the content store to the to the version N that is compatible with this version of Content Manager. The current version of the content store is M. \n 3. Also, please refer to the notes on the fix pack which would include perquisites on Backup/Restore of content store and also other requirements. \n 4. For versions 8 - 10.2.1: In the <cognos_install>/uninstall/backup directory there will be a list of date stamped folders with the applied fix packs and/or interim fixes. \n For versions 10.2.1 FP1 and above: This is stored in the <cognos_install>/bkp directory \n 5. Go into the folders and check the cmplst.txt file and check for the correct version to revert to. \n 6. Once the correct version is found, copy the contents of the whole folder and paste it at the <cognos_install> level, which will overwrite the files applied by fix pack or interim fix update. \n 7. Start the Cognos service.", "HISTORICAL NUMBER\n 1028034" ]

[ "Stop the Cognos service and ensure that Cognos Configuration is not running. \n 2. When setting up the configuration of a newly installed Cognos BI environment, it is important to note that if you configure the new installation against the original content store, it is permanently upgraded to the new version and can no longer be used in the original environment. As a result, always create a backup of the content store prior to upgrading.\n If a roll back to the original version is required, you can simply restore the backup. However, any work done after the content store has been upgraded (reports, models, security, etc...) to the new version will be lost, as all of this information is saved in the content store.\n If you try to revert back to an earlier environment configured against the upgraded content store, you will get an error similar to the one below:\n CM-CFG-5027 Unable to upgrade the content store to the to the version N that is compatible with this version of Content Manager. The current version of the content store is M. \n 3. Also, please refer to the notes on the fix pack which would include perquisites on Backup/Restore of content store and also other requirements. \n 4. For versions 8 - 10.2.1: In the <cognos_install>/uninstall/backup directory there will be a list of date stamped folders with the applied fix packs and/or interim fixes. \n For versions 10.2.1 FP1 and above: This is stored in the <cognos_install>/bkp directory \n 5. Go into the folders and check the cmplst.txt file and check for the correct version to revert to. \n 6. Once the correct version is found, copy the contents of the whole folder and paste it at the <cognos_install> level, which will overwrite the files applied by fix pack or interim fix update. \n 7. Start the Cognos service." ]

[]

[ "IBM Using -Xgc:preferredHeapBase with -Xcompressedrefs - United States TECHNOTE (FAQ)\n\nQUESTION\n \"Why does the JVM report a native out-of-memory (NOOM) when using compressed references? I am using a 64bit JVM and I clearly have plenty of memory left. How can I resolve this problem?\" \n\nCAUSE", "*In this note, please refer to Java Versioning: Java Version.Release.ServiceRelease.FixPack \nex: Java 7.1.4.6 is the same as Java 7.1 SR4 FP6 is the same as Java 7 R1 SR4 FP6. \nThe IBM JVM will automatically use compressed references [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html]when using a maximum heap size less than 25GB. This automated behavior was introduced in Java 6.1.5.0 and Java 7.0.4.0*. Compressed references (CR) decreases the size of Java objects making better use of available memory space. This better use of space results in improved JVM performance. *(Java 7.0.1.1 and later uses compressed references by default on z/OS) \n\nSee Introducing WebSphere Compressed Reference Technology [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf] for detailed information on how Compressed References work.", "\"When using compressed references, the size of the field used in the Java object for the Class Pointer and the Monitor/Lock is 32 bits instead of the 64bits that would be available in non-compressed mode. Because we are using 32 bits to store the location of these, and they are located in native (non-Java heap) memory, they must be allocated in the first 4GB of the address space - the maximum range we can address with the 32 bits.\" ~IBM Java Development Team \n\nIf the Java heap itself is small (-Xmx), the JVM may allocate it in the lower 4GB of address space along with the Class Pointers and Monitors/Locks. If these Class Pointers, Monitors/Locks and Java heap (if included) cannot fit in the lower 4GB, a native out of memory (NOOM) [http://www.ibm.com/developerworks/library/j-nativememory-linux/] will be thrown. \nANSWER\nWhy Use Compressed References?", "Below the 4GB mark, the JVM does not have to perform any compression/decompression of the address pointer at runtime. Therefore, the best performance will be attained if the Class Pointers, Monitors/Locks and Java heap can all be contained comfortably within the lowest 4GB of the address space. \n\n \n\nDetermining Address Location of Java Heap Memory \n\nTo verify if the Java heap has memory regions below the 4GB mark, check the \"Object Memory\" section in the javacore:\n\nConvert the \"start\" address from the hex value to a GB value [http://ss64.com/convert.html]. In the example below, 0x000000000F010000=0.23GB which is below the the 4GB (0x0000000100000000) mark.\n\n\n\n * [/support/docview.wss?uid=swg21660890&amp;aid=1]\n\n\nSetting the Preferred Heap Base with -Xgc:preferredHeapBase", "Starting with Java 6.1.6.0 and Java 7.0.5.0, and later, the JVM will determine if the Java heap will fit comfortably in the lower 4GB. If it is too large, the JVM will automatically allocate the Java heap above the 4GB mark (APAR IV37797 [http://www-01.ibm.com/support/docview.wss?uid=swg1IV37797]).", "NOTE: In IBM System z platforms (i.e. z/OS and z/Linux), automatic shift of the heap above the 4GB address space does NOT occur because on these platforms, there is an additional performance penalty \nassociated with higher shift values. To resolve Native OOM issues due to a shortage of heap memory in the lower region on z platforms, use -Xnocompressedrefs (see below).", "See related: IBM Knowledge Center - JVMJ9GC089W [https://www.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.messages/diag/appendixes/messages/j9gc/message_jvmj9gc089.html] However, in earlier Java 6.1 and Java 7.0 versions (earlier than Java 6.1.6.0 and Java 7.0.5.0), if the Java heap can not fit in the lower 4GB, a NOOM will occur. To avoid this problem, the generic JVM argument [http://www-01.ibm.com/support/docview.wss?uid=swg21417365] -Xgc:preferredHeapBase=<address> [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html] can be used to ensure the Java heap is allocated above the 4GB address space. This will leave more room for the Class Pointer and Monitor/Lock memory.", "* \n * \n * \n * \n * \n * \n * This will locate the Java heap starting at the 4GB mark thus leaving the lower 4GB for the other processes.\n\n\nIncrease Maximum Heap Size to Force Heap Allocation Above the 4GB mark \n\nAnother way to ensure that the heap is allocated above the 4GB mark (Java 6.1.6.0 and Java 7.0.5.0 and later) is to set a maximum heap size equal to or greater than 4GB. For example -Xmx4G will ensure that the heap will have to be allocated above the 4GB mark. This will not work in earlier versions of the JVM since these earlier versions allowed the heap to straddle the 4GB mark, placing part of the memory above and some below (fixed as part of APAR IV37797) . \n\n \n\nFurther Investigation", "If after setting -Xgc:preferredHeapBase=<address> or -Xmx4G a NOOM is still encountered (Java 6.1.6.0 and Java 7.0.5.0 and later), then further investigation is required at the application level. Look to decrease the size and usage of the applications Class Pointers and Monitors/Locks. Additionally, there are some WebSphere Application Server troubleshooting methods that may help reduce the native memory footprint. See: IBM Troubleshooting native memory issues [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21373312].\n\nReserving Low-Memory Space with -Xmcrs\n\nIf there is still free memory in the system when a Native OutOfMemory (NOOM) occurs, then the problem may be a shortage of memory in the low-memory region (under 4GB). Even if the Java heap is located above this boundary, other data associated with Java objects can be located in the low-memory region.", "The OS memory allocator will deal out low-memory freely, thus memory resources in the lower boundary may run out. Later when the JVM tries to allocate memory for an artifact which is required to be allocated in low-memory (because the JVM has only reserved a 32bit pointer for it) it fails and throws an OutOfMemoryError.\n\nStarting in Java 6.0.16.3, Java 6.1.8.3, Java 7.0.8.10, Java 7.1.2.10, there is a parameter -Xmcrs [http://www-01.ibm.com/support/knowledgecenter/SSYKE2_6.0.0/com.ibm.java.doc.diagnostics.60/diag/appendixes/cmdline/xmcrs.html] which allows the JVM to increase the amount of low memory it reserves on startup. With this setting, as long as the low-memory usage by the JVM does not exceed the -Xmcrs value, NOOM in the lower boundary will be avoided.\n\nTo set this parameter, first decide what a reasonable value for your lower memory requirements may be. Reasonable value is unique to each environment so there is not a general recommendation.", "* -Xmcrs<reasonable_value_for_lower_memory>\n\n * \n * NATIVEMEMINFO subcomponent dump routine\n * \n * \n * \n * \n * \n * \n * \n * \n * [/support/docview.wss?uid=swg21660890&amp;aid=2]\n *", "Disabling Compressed References with -Xnocompressedrefs As a last resort, if the native memory still can not be contained under the 4GB mark, you can set -Xnocompressedrefs [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/appendixes/cmdline/Xnocompressedrefs.html] as a generic JVM argument. [http://www-01.ibm.com/support/docview.wss?uid=swg21417365] Using -Xnocompressedrefs will remove the use of compressed references and therefore remove the lower 4GB memory restriction on the Class Pointers and Monitors/Locks. This will however, result in a significant increase in Java heap memory requirements. It is not uncommon for 70% more heap space to be required. Due to the increased memory requirements it is strongly advised that the Java heap size is adjusted to a larger value and garbage collection is monitored and retuned as required.", "Additionally, some benchmarks show a 10-20% relative throughput decrease when disabling compressed references: \"Analysis shows that a 64-bit application without CR yields only 80-85% of 32-bit throughput but with CR yields 90-95%. Depending on application requirements, CR can improve performance up to 20% over standard 64-bit.\" See:ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf].", "Before using -Xnocompressedrefs as a solution, first rule out the possibility of a native memory leak. Since using -Xnocompressedrefs will allow the the native memory to grow unbounded, a leak in native memory will lead to process size growth eventually leading to a process that needs to be paged out. The paging will incur performance overhead which will eventually lead to an unstable environment. Therefore careful consideration must be used when selecting -Xnocompressedrefs as a solution.\n\n\nMemory Map Considerations \n\nThe below figure is a generalization of how the JVM handles addresses in each section of the memory map based on heap size and compressed references (CR). Please note that at each stage beyond having all of the Java memory contained below the 4GB mark, there will be performance consequences: \n\n\n\n[/support/docview.wss?uid=swg21660890&amp;aid=3]", "No Compressed References Overhead using -Xnocompressedrefs \nor\n-Xmx > 25GB -increased memory footprint\n-fewer/larger objects stored on heap leads to more frequent GC\n-lower cache and translation look aside buffer (TLB) utilization [/support/docview.wss?uid=swg21660890&amp;aid=4] Compressed References Overhead maximum heap address used by the Java JVM process is below 4GB none maximum heap address used by the Java JVM process is above 4GB but below 32GB compression/decompression of address pointers \n\n\nGetting Assistance From IBM Support \nIf further assistance will be required from IBM WebSphere Support, please set the following -Xdump [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/tools/dumpagents_syntax.html] parameters in the generic JVM arguments [http://www-01.ibm.com/support/docview.wss?uid=swg21417365]: \n * \n * \n *", "Then restart the JVM and recreate the problem. Once the NOOM is encountered, process the resulting system core with jextract [http://www-01.ibm.com/support/docview.wss?uid=swg21577379]. Send the jextracted core file, heapdump, javacore, snap trace, systemOut.log, native_stderr.log, native_stdout.log and systemErr.log to IBM Support [http://www-01.ibm.com/support/docview.wss?uid=swg21153852] for further analysis. \nRELATED INFORMATION\n Linux/Windows - Thanks for the memory [http://www.ibm.com/developerworks/library/j-nativememory-linux/]\nAIX - Thanks for the Memory [http://www.ibm.com/developerworks/library/j-nativememory-aix/]\nIntroducing WebSphere Compressed Reference Technology [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf]\nCompressed references [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html]", "IBM Java Compressed References and Native OOMs [https://www.ibm.com/developerworks/community/blogs/kevgrig/entry/ibm_java_compressed_references_and_native_ooms]" ]

[ "To avoid this problem, the generic JVM argument [http://www-01.ibm.com/support/docview.wss?uid=swg21417365] -Xgc:preferredHeapBase=<address> [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html] can be used to ensure the Java heap is allocated above the 4GB address space. This will leave more room for the Class Pointer and Monitor/Lock memory." ]

[ 6 ]

[ "IBM Installation Manager does not work if symbolic links are used for Installation Manager of installed product locations - United States RN1.5; RN1.5.1; RN1.5.0.1; RN1.5.2; RN1.5.3; RN1.6; RN1.6.1; RN1.6.2; RN1.6.3; RN1.6.3.1; RN1.7; RN1.7.1; RN1.7.2; SRX; 1628092; RATLC02668456; IPL; Symlink TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You install IBM Installation Manager by using symbolic links at the root level for the agent data location or the installation location or for both locations and after a system change or system restart you cannot start Installation Manager or you cannot use Installation Manager to update or uninstall products.", "CAUSE\nWhen you install Installation Manager, the values for the agent data directory, the Installation Manager binaries, and the installation directories for products are stored internally as absolute paths with all the symbolic links resolved. If a symbolic link is used as part of the path for any of these directories or binaries, the symbolic link is replaced with its target value.\nSimilarly, when a product is installed with Installation Manager, the values for the installation location and shared resources directory are stored internally as absolute paths with all symbolic links resolved.", "If the symbolic links change their values, the absolute path names for directories that are used by Installation Manager might change. When the Installation Manager starts, it will initialize itself using the data in the agent data location. However, the stored values for the paths to the agent data directory, Installation Manager binaries, or product installation locations do not point to the new locations. Installation Manager might fail to start, or might be unable to update or uninstall products that are installed.\n\n\nRESOLVING THE PROBLEM\nWhen choosing locations for the agent data directory, the Installation Manager binaries, shared resources directory, and the installation directories for products, do not use paths that include symbolic links.", "If Installation Manager is using paths that no longer exist, create the old paths manually and mount the affected file systems at the original locations that are used by Installation Manager. Verify that the user IDs for Installation Manager have read access to each level of the recreated paths." ]

[ "You install IBM Installation Manager by using symbolic links at the root level for the agent data location or the installation location or for both locations and after a system change or system restart you cannot start Installation Manager or you cannot use Installation Manager to update or uninstall products." ]

[ 0 ]

[ "IBM Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-5461) - United States SECURITY BULLETIN\n\nSUMMARY\n IBM MQ Appliance has addressed a vulnerability in Network Security Services (NSS).", "VULNERABILITY DETAILS\nCVEID:CVE-2017-5461 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5461]\nDESCRIPTION:Mozilla Firefox could allow a remote attacker to execute arbitrary code on the system, caused by an out-of-bounds write during Base64 decoding operation in the Network Security Services (NSS) library. By persuading a user to visit a specially-crafted website, a remote attacker could exploit this vulnerability using unknown attack vectors to execute arbitrary code on the vulnerable system or cause a denial of service.\nCVSS Base Score: 8.8\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/125002 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125002]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ Appliance 8.0 \n\nMaintenance levels between 8.0.0.0 and 8.0.0.6\nIBM MQ Appliance 9.0.x Continuous Delivery (CD) Release", "Continuous delivery updates between 9.0.1 and 9.0.3\n\nREMEDIATION/FIXES\nIBM MQ Appliance 8.0 \n\nApply fixpack 8.0.0.7 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&release=8.0.0.6&platform=All&function=all]\nIBM MQ Appliance 9.0.x Continuous Delivery (CD) Release \n\nApply the ifix for APAR IT21888 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&release=9.0.3&platform=All&function=all]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "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\nCHANGE HISTORY\n 24 Aug 2017 Updated to include IBM MQ Appliance 9.0.x CD release\n14 Jul 2017 Original version published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.", "DISCLAIMER\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." ]

[ "CVEID:CVE-2017-5461 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5461]\nDESCRIPTION:Mozilla Firefox could allow a remote attacker to execute arbitrary code on the system, caused by an out-of-bounds write during Base64 decoding operation in the Network Security Services (NSS) library. By persuading a user to visit a specially-crafted website, a remote attacker could exploit this vulnerability using unknown attack vectors to execute arbitrary code on the vulnerable system or cause a denial of service.\nCVSS Base Score: 8.8\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/125002 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125002]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H)" ]

[ 1 ]

[ "IBM Policy (EJQAB0067E) and JCR Login (WSP0005E) exceptions in System*.logs - United States EJQAB0067E; WSP0005E; LoginException; policy; theme; attribute; JCR TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nPolicy (EJQAB0067E) and JCR Login (WSP0005E) exceptions occur in the System* logs when accessing Portal pages after user authentication.\n\nSYMPTOM\nSystemOut.log shows:\n\n[datestamp] 00000241 PolicyService E com.ibm.wps.policy.services.PolicyService getPolicy Exception calling storage api: com.ibm.portal.WpsException: EJQAB0067E: An error occurred while getting the policy root. \n[datestamp] 00000241 PolicyManager E com.ibm.wps.policy.services.PolicyManagerServerSideImpl getPVSByPath throwing exception. PVS type not found for theme/SingleTopNav\n\nSystemErr.log shows:", "[datestamp] 00000241 SystemErr R javax.jcr.LoginException: WSP0005E: Error calling IConnectionManager.logon() for reason: User id can not be null.: WSP0005E: Error calling IConnectionManager.logon() for reason: User id can not be null.\n....\n[datestamp] 00000241 SystemErr R Caused by: com.ibm.icm.da.DBAccessException: User id can not be null\n[datestamp] 00000241 SystemErr R at com.ibm.icm.da.portable.connection.Logon.logon(Logon.java:177)\n\n\nCAUSE\nAuthenticated user does not have the attribute defined in the backend user registry which matches the attribute defined in the store.puma_default.user.fbadefault.filter property in WP PumaStoreService Resource Environment Provider. Such attribute is used by JCR when querying for theme policy information.\n\nDIAGNOSING THE PROBLEM\nCollect the following:", "* LDIF export of a sample user that hits this problem (if the backend user registry is LDAP) * If you cannot determine a specific user causing the error, you can use the following tracestring to confirm:\n \n *=info:com.ibm.wps.policy.services.*=finest:com.ibm.wps.policy.commands.*=finest\n \n Then look for the following line in trace.log: com.ibm.wps.policy.services.PolicyService PolicyService() ENTRY userid contructor: {DN of user} \n \n \n * Resources.xml - can be found under * <wp_profile>/config/cells/<cellname>/clusters/<clustername>/ for cluster \n * <wp_profile>/config/cells/<cellname>/nodes/<nodename>/servers/<portalservername>/ for standalone", "Locate the WP PumaStoreService Resource Environment Provider in resources.xml and confirm if there is a defined property name for store.puma_default.user.fbadefault.filter. If not, then the default and active value for such property is \"uid\". If it does exist, then verify the attribute defined for the value. Then check the LDIF export for the user to confirm if such attribute is defined. \nRESOLVING THE PROBLEM\nCreate/update the store.puma_default.user.fbadefault.filter custom property for the WP PumaStoreService Resource Environment Provider via the Integrated Solutions Console to an attribute that exists for all Portal users in the backend user registry (for example, \"cn\").\n\nRELATED INFORMATION\n#Puma Store Service [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Puma_Store_Service_wp8]\nSetting service configuration properties [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Setting_service_configuration_properties_wp8?OpenDocument&sa=true]" ]

[ "Create/update the store.puma_default.user.fbadefault.filter custom property for the WP PumaStoreService Resource Environment Provider via the Integrated Solutions Console to an attribute that exists for all Portal users in the backend user registry (for example, \"cn\")." ]

[ 3 ]

[ "IBM Pdcollect tool for ITM IBM i OS agent - United States ITM_TEMA_DIST_CONFIGURATION ITM_i5_Agent 5724C04 A4 OS/400 i5/OS IBMi IBM i pdcollect TECHNOTE (FAQ)\n\nQUESTION\n How do I collect logs and files for the IBM i OS agent? \n\nANSWER\nThe pdcollect tool for the IBM i OS agent allows you to easily and quickly collect the most commonly used information from an IBM i system for IBM Support to investigate a problem. The tool gathers log files, configuration information, version information, job information, message queue information, and basic system information. \n\nPdcollect is delivered in the IBM i OS agent beginning in ITM 6.23 FP5 and ITM 6.30 FP3. It is located in the following IFS directory: \n\n\n/QIBM/ProdData/IBM/ITM/bin/pdcollect.sh", "Pdcollect is also available as a downloadable file which is stored in an IFS directory chosen by the user. Download the following zip file to a local workstation and extract its contents. Follow the instructions in readme.txt for further information on installing the tool. \n\n pdcollect_ibmi_1.4.zip [/support/docview.wss?uid=swg21657023&aid=2]pdcollect_ibmi_1.4.zip [/support/docview.wss?uid=swg21657023&aid=1] \n\n The tool is executed by issuing the following shell script command in Qshell:\n\n<directory>/pdcollect.sh \n\nwhere <directory> is the IFS directory where the tool is stored. \n\nYou must execute pdcollect while running under a user profile that you use to run IBM Tivoli Monitoring to avoid problems with object authorities. \n\nThe output from the tool is a single compressed file that can be sent in binary form to IBM Support if requested. The output file is stored at the following location: \n\n /tmp/ITM/pdcollect_ibmi.tar.Z", "The output file is overwritten each time the tool is run. Copy or rename the output file after each invocation if more than one data collection is needed. \n\nInstructions to view the data that has been collected is displayed in a message at the end of pdcollect processing. \n\nThe pdcollect tool for the IBM i OS agent does not collect information from the Tivoli Enterprise Monitoring Server (TEMS) or Tivoli Enterprise Portal Server (TEPS) systems. You may be asked to collect additional information from your TEMS or TEPS systems separately." ]

[ "The pdcollect tool for the IBM i OS agent allows you to easily and quickly collect the most commonly used information from an IBM i system for IBM Support to investigate a problem. The tool gathers log files, configuration information, version information, job information, message queue information, and basic system information." ]

[ 0 ]

[ "IBM Insufficient Access Error adding documents to FileNet Content Engine - United States FNRCE0001E; E_ACCESS_DENIED; unable to add document TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n User is getting a security error when attempting to add a document to a folder in an object store via FileNet Workplace XT or FileNet Enterprise Manager.\n\n\nSecurity Error seen: The requester has insufficient access rights to perform the requested operation. \n\nCAUSE\nUser does not have Create_Instance right on the security permission of the ReferentialContainmentRelationship and DynamicReferentialContainmentRelationship classes and cannot create these objects when adding documents.\n\nDIAGNOSING THE PROBLEM", "* User has necessary rights to the document class, folders and object store but can't add document. \n * User does not have necessary Create_Instance rights on the ReferentialContainmentRelationship and DynamicReferentialContainmentRelationship classes. \n * Error seen in the P8_server_error.log:\n \n YYYY-06-08T17:53:19.706Z 56005600 ENG FNRCE0001E - ERROR method name: checkUpdatePermissions principal name: username Global Transaction: true User Transaction: false Exception Info: The requester has insufficient access rights to perform the requested operation.\n com.filenet.api.exception.EngineRuntimeException: FNRCE0001E: E_ACCESS_DENIED: The requester has insufficient access rights to perform the requested operation. failedBatchItem=0 errorStack={\n \n\nRESOLVING THE PROBLEM\nSteps to resolve issue:", "1. Log in to FileNet Enterprise Manager. \n 2. Grant the user CREATE_INSTANCE rights to the Security permission of the ReferentialContainmentRelationship and DynamicReferentialContainmentRelationship classes. \n 3. Re-try adding the document." ]

[ "User does not have Create_Instance right on the security permission of the ReferentialContainmentRelationship and DynamicReferentialContainmentRelationship classes and cannot create these objects when adding documents." ]

[ 0 ]

[ "IBM IV67523 Move local data from CANDLEHOME to another file system - United States 6.30.05.00 CANDLEHOME CANDLEDATA itmCANDLEDATA.sh TECHNOTE (FAQ)\n\nQUESTION\n How do I move local data such as configuration files, log files, historical data, etc. from CANDLEHOME to a different file system? \n\nCAUSE\nSince its inception, IBM Tivoli Monitoring (ITM) has stored local data such as configuration files, log files, and historical data together with the installation files in CANDLEHOME. For example, ITM normally installs in a directory named /opt/IBM/ITM. Within that directory, it stores programs in subdirectory names like /opt/IBM/ITM/bin and /opt/IBM/ITM/classes. It also stores local data in subdirectory names like /opt/IBM/ITM/config and /opt/IBM/ITM/logs. This homogeneous design is a problem for installations that require an approach that keeps code in /opt and stores data in the /var file system.\n\nANSWER\nIntroduction", "Under APAR IV67523, ITM added a new mechanism to move local data to a different file system. For example, data typically stored in /opt/IBM/ITM/config and /opt/IBM/ITM/logs can be redirected to /var/IBM/ITM/config and /var/IBM/ITM/logs. This new file system location is designated by the user at installation time, and it is referred to as CANDLEDATA. A conversion utility is provided to implement CANDLEDATA for existing installations. \n\nThe CANDLEDATA mechanism is available with ITM 6.30.05.00. \n\n \n\n\n\n\n\n\nHow CANDLEDATA Works \n\nThe CANDLEDATA mechanism is implemented primarily using symbolic links. This means most of the underlying code in ITM is unaware of CANDLEDATA. This also means the CANDLEDATA mechanism is limited to Linux and UNIX platforms. \n\nThe rest of this section shows examples of links where CANDLEHOME=/opt/IBM/ITM and CANDLEDATA=/var/IBM/ITM. You can define different locations for your own installation. \n\n \n\nBase Directory Links", "The following local data directories are always linked from CANDLEHOME to CANDLEDATA:\n\n\n * /opt/IBM/ITM/InstallITM -> /var/IBM/ITM/InstallITM\n * \n * /opt/IBM/ITM/config -> /var/IBM/ITM/config\n * \n * /opt/IBM/ITM/kt1v3depot -> /var/IBM/ITM/kt1v3depot\n * \n * /opt/IBM/ITM/localconfig -> /var/IBM/ITM/localconfig\n * \n * /opt/IBM/ITM/logs -> /var/IBM/ITM/logs\n * \n * /opt/IBM/ITM/patchlogs -> /var/IBM/ITM/patchlogs\n * \n * /opt/IBM/ITM/tables -> /var/IBM/ITM/tables\n * \n * /opt/IBM/ITM/tmaitm6/agentdepot -> /var/IBM/ITM/tmaitm6/agentdepot\n * \n * /opt/IBM/ITM/tmp -> /var/IBM/ITM/tmp\n\nThese directories and links are automatically generated by ITM when the system is installed or converted to use CANDLEDATA. \n\n \n\nGeneral Agent Directory Links \n\nIn addition to the base set of directory links, most agents have general links for TEMA data:", "* /opt/IBM/ITM/ATTRLIB -> /var/IBM/ITM/ATTRLIB\n * \n * /opt/IBM/ITM/<platform>/<pc>/tables/ATTRLIB -> /var/IBM/ITM/ATTRLIB/<pc>\n * \n * /opt/IBM/ITM/EIFLIB -> /var/IBM/ITM/EIFLIB\n * \n * /opt/IBM/ITM/<platform>/<pc>/tables/EIFLIB -> /var/IBM/ITM/EIFLIB/<pc>\n * \n * /opt/IBM/ITM/hist -> /var/IBM/ITM/hist\n * \n * /opt/IBM/ITM/<platform>/<pc>/hist -> /var/IBM/ITM/hist/<pc>\n * \n * /opt/IBM/ITM/psit -> /var/IBM/ITM/psit\n * \n * /opt/IBM/ITM/<platform>/<pc>/psit -> /var/IBM/ITM/psit/<pc>\n\n\nThese directories and links are automatically generated by ITM when the agent is converted to use CANDLEDATA. \n\nSpecial Agent Directory Links \n\nSome agents have links that are specific to that agent. For example, the LZ and UX agents create the following link for the Watchdog component to store local data:\n\n\n * /opt/IBM/ITM/kca -> /var/IBM/ITM/kca\n\n\nThese directories and links are automatically generated by ITM when the agent is converted to use CANDLEDATA. \n\nCANDLEDATA <-> CANDLEHOME Directory Links", "The CANDLEHOME and CANDLEDATA directories also have cross references to each other:\n\n\n * /opt/IBM/IBM/registry/CANDLEDATA -> /var/IBM/ITM\n * \n * /opt/IBM/ITM <- /var/IBM/ITM/CANDLEHOME\n\n\nThese links are all automatically generated by ITM when the system is installed or converted to use CANDLEDATA. \n\nConfiguration Variables exploited by CANDLEDATA \n\nIn addition to symbolic links, some individual components have special configuration settings to redirect agent-specific data to CANDLEDATA. ITM redirects data using the following configuration variables:\n\n\n * CTIRA_SIT_PATH\n * \n * CANDLEHOME/\n * <platform>/<pc>/psit\n * \n * \n * KCA_IP_DIR\n * \n * CANDLEHOME/kca\n * \n * \n * KCAWD_WRITE_DIR \n * \n * CANDLEHOME/kca\n * \n *", "Notes: 1. While the variables point to CANDLEHOME/xxx, the directory links cause the local data to be written to the corresponding CANDLEDATA/xxx. \n 2. If you use configuration overrides that set these configuration variables, you'll need to review how those overrides work in an environment configured to use CANDLEDATA. In most cases, you'll want to remove your overrides.\n\n\nConfiguration Variables affected by CANDLEDATA\nThe symbolic links established by ITM for CANDLEDATA assume standard agent configuration. If you've modified any of the following, data will be continue to be redirected to the location you specified instead of the CANDLEDATA directory:\n. \n\n * ATTRLIB\n * \n * CTIRA_HIST_DIR\n * \n * EIFLIB\n * \n *", "When converting an existing CANDLEHOME, ITM migrates any data in the original directories before linking them to CANDLEDATA. If you've modified any of the following, you must consider whether you need to change the setting and migrate the data manually: \n. * CTIRA_SIT_FILE\n * \n * \n\nBy default, all of the following configuration variables direct data to /opt/IBM/ITM/localconfig. ITM migrates data from /opt/IBM/ITM/localconfig to /var/IBM/ITM/localconfig and then links the two. If you've modified any of these, you must consider whether you need to change the setting and migrate the data manually: \n. * CTIRA_THRESHOLDS \n * \n * IRA_EVENT_EXPORT_SNMP_TRAP_CONFIG\n * \n * \n * IRA_LOCALCONFIG_DIR\n * \n * \n * IRA_PRIVATE_SITUATION_CONFIG\n * \n * \n * IRA_SERVICE_INTERFACE_DEFAULT_PAGE\n * \n * \n * IRA_SERVICE_INTERFACE_DIR\n * \n * \n * KXX_FCP_SCRIPT_DEFINITIONS \n\n\n\n\n\nKnown Restrictions", "1. The CANDLEDATA mechanism is available only for ITM on Linux and UNIX. ITM on Windows continues to keep local data under CANDLEHOME. \n . \n 2. No facility is provided switch from a CANDLEHOME+CANDLEDATA implementation back to a unified CANDLEHOME implementation. To do this, you must uninstall and reinstall ITM.\n . \n 3. No facility is provided to move CANDLEDATA from one directory to another. To do this, you must uninstall and reinstall ITM.\n . \n 4. The CANDLEHOME and CANDLEDATA arrangement is a 1:1 relationship. * Only one CANDLEHOME can use a given CANDLEDATA. This means a given CANDLEDATA cannot be shared with multiple CANDLEHOMEs. \n * A given CANDLEHOME can only use one CANDLEDATA. This means components cannot be split amongst multiple CANDLEDATAs.\n .", "5. The monitoring server and portal server cannot exploit CANDLEDATA. * The conversion utility will not convert an existing CANDLEHOME if it contains the monitoring server or portal server. \n * The installer warns if CANDLEDATA is specified and the install image contains the monitoring server or portal server. However, the installer does not prevent monitoring server or portal server from being installed. \n * ITM does not allow the monitoring server to start if CANDLEDATA is implemented. \n * ITM does not allow the portal server to start if CANDLEDATA is implemented.\n .\n \n \n 6. Not all agents have been verified to work with CANDLEDATA. Before using CANDLEDATA, check with the support group for each of the agents you intend to install.\n . \n 7. System Monitor Agents (SMA) can exploit CANDLEDATA. However, the SMA installer does not create CANDLEDATA. These agents must be converted to use CANDLEDATA after they are installed.\n .", "8. The CANDLEDATA mechanism is intended only for current agents. If the agent media contains installer 6.30.00.00 or above, it should be ok to use with CANDLEDATA. \n \n Some older or discontinued agents such as the Universal Agent (UM) and UNIX Logs agent (UL) cannot use CANDLEDATA reliably. ITM does not prevent older or discontinued agents from being installed into a new CANDLEHOME with CANDLEDATA implemented. \n . \n 9. When CANDLEDATA is in use, ITM implements internal overrides for the following configuration variables: CTIRA_SIT_PATH, KCA_IP_DIR, and KCAWD_WRITE_DIR. * If you've already overridden any of these configuration variables, you must remove the overrides before converting a given component. \n * If you've overridden these with CANDLEHOME/config/xx.environment, the conversion utility will detect and warn about them. Your overrides will win, so you must remove them.", "* If you've overridden these with the old method of sourcing a script into CANDLEHOME/config/xx.ini, the conversion utility cannot detect them. However, the CANDLEDATA overrides will win.\n .\n \n \n 10. The prerequisite scanner does not know about CANDLEDATA. It continues to assume everything is stored in CANDLEHOME. This means: * No space checking is performed for CANDLEDATA. \n * Results are somewhat inflated for CANDLEHOME.\n .\n \n \n 11. The conversion utility does not check for space when converting an existing new CANDLEHOME to use CANDLEDATA. Make sure there is enough space in CANDLEDATA before starting the conversion process.", "Agents Verified with CANDLEDATA\n\nThe following agents have been verified to run properly when CANDLEDATA is implemented:\n\n\n * LO\n * \n * \n * LZ\n * \n * \n * UD\n * \n * \n * UX\n * \n * \n\nFor other agents, contact the corresponding support team. \n\n\n\n\n\n\nSetting Up a New Local Installation with CANDLEDATA\n\nFor new installations, you can define the location for local data at installation time.\n\nLocal install (interactive):", "* \n * CANDLEDATA\n * \n * CANDLEHOME\n * \n * \n * \n * # ./install.sh\n * \n * INSTALL\n * \n * \n * Enter the name of the IBM Tivoli Monitoring installation directory.\n * \n * [ default = /opt/IBM/ITM ]:\n * \n * \"/opt/IBM/ITM\" does not exist\n * \n * Try to create it [ 1-yes, 2-no; \"1\" is default ]?\n * \n * Creating directory \"/opt/IBM/ITM\"...\n * \n * \n * Enter the name of the IBM Tivoli Monitoring local data directory.\n * \n * [ default = /opt/IBM/ITM ]: /var/IBM/ITM\n * \n * \"/var/IBM/ITM\" does not exist\n * \n * Try to create it [ 1-yes, 2-no; \"1\" is default ]?\n * \n * Creating directory \"/var/IBM/ITM\"...\n * \n * itmCANDLEDATA.sh: Installation directory \"/opt/IBM/ITM\" successfully converted to use data directory \"/var/IBM/ITM\".\n * \n * \n * \n * CANDLEDATA\n * \n * \n * \n * \n * CANDLEDATA\n * \n * CANDLEHOME\n * \n * CANDLEDATA\n * \n * CANDLEHOME\n * \n * CANDLEHOME\n *", "Local install (silent): \n * \n * CANDLEDATA\n * \n * CANDLEDATA\n * \n * \n * \n * install.sh \n [-l \n * CANDLEDATA\n * ] \n * \n Where: * -l\n * \n * CANDLEHOME\n * \n \n \n * \n * \n * CANDLEDATA\n * \n * install.sh\n * \n * \n * \n * \n * CANDLEDATA\n * \n * CANDLEHOME\n * \n * CANDLEDATA\n * \n * install.sh\n * \n\n\n\n\n\n\n\nStarting an agent for the first time with CANDLEDATA \n\nWhen you specify CANDLEDATA at install time, ITM establishes the base directory links. All agent-specific conversion is handled the first time a given agent is started. When this happens, an extra message is included in the agent start output: Here is an example:\n\n# itmcmd agent start ux\nProcessing. Please wait...\nitmCANDLEDATA.sh: Component ux successfully converted to use data directory \"/var/IBM/ITM\".\nStarting Monitoring Agent for UNIX OS ...\nMonitoring Agent for UNIX OS started \n\n \n\n\n\n\n\n\nConverting an existing installation or new agents to use CANDLEDATA", "For existing installations, ITM provides a utility to convert a CANDLEHOME to use CANDLEDATA. You can also use this utility to convert a newly installed agent before it is started. Under the covers, the installer runs this same utility. \n\nitmCANDLEDATA.sh\n[-b yes|no] \n[-h CANDLEHOME] \n[-l CANDLEDATA] \n[-f no|yes] \n[-p PC|*]\n[-r no|yes] \n\nWhere: \n\n * \n * -b\n * \n * yes\n * \n * CANDLEDATA\n * \n * CANDLEHOME\n * \n * CANDLEHOME\n * \n * no\n * \n * CANDLEDATA\n * \n * \n * \n * -h\n * \n * \n * \n * -l\n * \n * CANDLEHOME\n * \n * CANDLEDATA\n * \n * \n * \n * -f\n * \n * no\n * \n * yes\n * \n * \n * \n * -p\n * \n * *\n * \n * \n * \n * -r\n * \n * no\n * \n * yes\n * \n\n\nIf you set the CANDLEHOME or CANDLEDATA environment variables before launching the installer, then those values are used as though they had been passed with the command options. If both the command option is used and the environment variable is defined before the conversion utility is started, the command option takes precedence.", "Example 1: Conversion of a typical CANDLEHOME can be performed with an incantation similar to this: * \n * itmCANDLEDATA.sh -l /var/IBM/ITM -b yes -p \"*\" -r yes\n\n\nExample 2: Conversion of a newly installed agent to a CANDLEHOME where CANDLEDATA is already implemented can be performed with an incantation similar to this: * \n * itmCANDLEDATA.sh -b no -p \"ux\" -r yes\n\n\n\n\n\n\n\nUsing CANDLEDATA with Remote Deploy\n\nYou can define the location for local data remotely:\n\ntacmd createnode (new installations):\n\n\n * \n * CANDLEDATA\n * \n * CANDLEDATA\n * \n * \n * \n * tacmd createnode ... -o ENV_CANDLEDATA=\n * data_directory\n * ...\n * \n * \n * \n * install.sh\n * \n * CANDLEDATA\n * \n *", "tacmd executecommand + itmCANDLEDATA.sh (existing installations): \n * \n * CANDLEDATA\n * \n * tacmd updateagent\n * \n * CANDLEDATA\n * \n * tacmd executecommand\n * \n * \n * \n * tacmd executecommand ... -c \"/opt/IBM/ITM/bin/itmCANDLEDATA.sh -l /var/IBM/ITM -p \\\"*\\\" -b yes -r yes > /tmp/itmCANDLEDATA_remote.log 2>&1 &\"\n * \n * \n * \n *", "* Launches the conversion utility on the agent (/opt/IBM/ITM/bin/itmCANDLEDATA.sh). Specifies the local data directory (-l /var/IBM/ITM). Specifies all agents are to be converted (-p \\\"*\\\"). Note that the quotes are escaped because the entire command string is quoted. Specifies the CANDLEDATA directory is to be built (-b yes). Specifies the agents are to be restarted (-r yes). Redirects STDOUT and STDERR to a log file (> /tmp/itmCANDLEDATA_remote.log 2>&1). Note that the standard -o/-e/-d/-v options for tacmd executecommand don't function properly because of the agent restart. Note also that /tmp is used instead of /opt/IBM/ITM/logs; the latter is moved during the conversion process and therefore must be inactive. Launches the command in the background (trailing &). tacmd executecommand waits for the commands to complete, and this is signaled by a communication from the agent. However, since the agent is restarted by the command, it will never reply to tacmd executecommand. Running", "the command in the background allows tacmd executecommand to complete normally.", "Other Implications \n\nThe following general ITM utilities have been updated to run properly when CANDLEDATA is implemented:", "* cinfo - The output heading indicates the location of CANDLEDATA if it implemented. \n * itmcmd agent start - Agent configurations are automatically updated if CANDLEDATA is implemented. Also, the portal server is prevented from starting if CANDLEDATA is implemented. \n * itmcmd server start - The monitoring server is prevented from starting if CANDLEDATA is implemented. \n * secureMain - Permissions and ownership in CANDLEDATA are maintained just as in CANDLEHOME. If secureMain was run before CANDLEDATA is implemented, the conversion utility automatically runs secureMain again as part of the conversion process. However, if you run the conversion utility as a nonroot user (not recommended), you must run secureMain manually after conversion is complete. \n * tacmd pdcollect and pdcollect - Data is gathered from CANDLEDATA just as from CANDLEHOME.", "* uninstall.sh - Relevant data is removed from in CANDLEDATA just as from CANDLEHOME. For uninstall.sh REMOVE EVERYTHING, both the CANDLEHOME and CANDLEDATA directories are removed." ]

[ "The CANDLEDATA mechanism is available with ITM 6.30.05.00." ]

[ 1 ]

[ "IBM Security Bulletin: Malicious File Download vulnerability in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) - CVE-2016-9693 - United States SECURITY BULLETIN\n\nSUMMARY\n A comma separated file (CSV) download feature exists in IBM BPM and WLE and is available for anonymous users. An attacker can craft a URL that can trigger a download of attacker-supplied content under an attacker-supplied file name onto the victim's machine.", "VULNERABILITY DETAILS\nCVEID:CVE-2016-9693 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9693]\nDESCRIPTION:IBM Business Process Manager has a file download capability that is vulnerable to a set of attacks. Ultimately, an attacker can cause an unauthenticated victim to download a malicious payload. An existing file type restriction can be bypassed so that the payload might be considered executable and cause damage on the victim's machine.\nCVSS Base Score: 7.1\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/119517 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119517]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L)", "AFFECTED PRODUCTS AND VERSIONS\n- WebSphere Lombardi Edition V7.2.0.0 - V7.2.0.5\n- IBM Business Process Manager Advanced V7.5.0.0 - V7.5.1.2\n- IBM Business Process Manager Advanced V8.0.0.0 - V8.0.1.3\n- IBM Business Process Manager Advanced V8.5.0.0 - V8.5.7.0 including cumulative fix 2016.12\n\nREMEDIATION/FIXES\nInstall IBM BPM or WLE interim fix JR57149 [http://www-01.ibm.com/support/docview.wss?uid=swg1JR57149]as appropriate for your current version.", "* IBM Business Process Manager Advanced [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Advanced&release=All&platform=All&function=aparId&apars=JR57149] \n * IBM Business Process Manager Standard [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Standard&release=All&platform=All&function=aparId&apars=JR57149] \n * IBM Business Process Manager Express [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Express&release=All&platform=All&function=aparId&apars=JR57149] \n * WebSphere Lombardi Edition [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Lombardi+Edition&release=All&platform=All&function=aparId&apars=JR57149]", "As IBM Business Process Manager V7.5 and WebSphere Lombardi Edition are out of general support, customers with a support extension contract can contact IBM support to request the fix. The fix disables the vulnerable URL and uses HTML5 features to trigger CSV download without server interaction. \n\nFor WebSphere Lombardi Edition 7.2.0.0 through 7.2.0.5 \n\n * Install Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24034270] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149] \n\nFor IBM BPM V7.5.0.0 through V7.5.1.2: * Upgrade to minimal Refresh Pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24031230], install Fix Pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24036462] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]", "For IBM BPM V8.0.0.0 through V8.0.1.3 * Upgrade to minimal Refresh Pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24033777], install Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24037734] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.0.0 through V8.5.0.2 * Install Fix Pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24040683] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.5.0 * Apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]", "For IBM BPM V8.5.6.0 through V8.5.6.0 CF2 * Install CF2 [http://www-01.ibm.com/support/docview.wss?uid=swg24041303] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.7.0 through V8.5.7.0 CF 2016.12 * Install CF 2016.12 [https://www.ibm.com/support/docview.wss?uid=swg27048992] and then apply iFix JR57149 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "IMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nACKNOWLEDGEMENT\nThe vulnerability was reported to IBM by Nalla Muthu S and Prasath K", "CHANGE HISTORY\n 24 Feb 2017: initial version published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.", "Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Express Security Linux, Windows 8.5.7.CF201612, 8.5.7.CF201609, 8.5.7.CF201606, 8.5.7, 8.5.6.2, 8.5.6.1, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration IBM Business Process Manager Standard Security AIX, Linux, Solaris, Windows 8.5.7.CF201612, 8.5.7.CF201609, 8.5.7.CF201606, 8.5.7, 8.5.6.2, 8.5.6.1, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration WebSphere Lombardi Edition Security AIX, HP-UX, Linux, Solaris, Windows 7.2.0.5, 7.2.0.4, 7.2.0.3, 7.2.0.2, 7.2.0.1, 7.2" ]

[ "CVEID:CVE-2016-9693 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9693]\nDESCRIPTION:IBM Business Process Manager has a file download capability that is vulnerable to a set of attacks. Ultimately, an attacker can cause an unauthenticated victim to download a malicious payload. An existing file type restriction can be bypassed so that the payload might be considered executable and cause damage on the victim's machine.\nCVSS Base Score: 7.1\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/119517 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119517]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L)" ]

[ 1 ]

[ "IBM Security Bulletin: Potential Privilege Escalation in WebSphere Application Server Admin Console (CVE-2017-1731) - United States SECURITY BULLETIN\n\nSUMMARY\n There is a potential privilege escalation in WebSphere Application Server Admin Console. \n\nVULNERABILITY DETAILS\n\nCVEID: CVE-2017-1731 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1731]\nDESCRIPTION: IBM WebSphere Application Server could provide weaker than expected security when using the Administrative Console. An authenticated remote attacker could exploit this vulnerability to possibly gain elevated privileges.\nCVSS Base Score: 8.8\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/134912 [https://exchange.xforce.ibmcloud.com/vulnerabilities/134912] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)", "AFFECTED PRODUCTS AND VERSIONS\nThis vulnerability affects the following versions and releases of IBM WebSphere Application Server: \n\n * Version 9.0 \n * Version 8.5 \n * Version 8.0 \n * Version 7.0\n\nREMEDIATION/FIXES\n The recommended solution is to apply the interim fix, Fix Pack or PTF containing APARs PI89498 for each named product as soon as practical.\n\nFor WebSphere Application Server traditional and WebSphere Application Server Hypervisor Edition:", "For V9.0.0.0 through 9.0.0.6: \n· Upgrade to minimal fix pack levels as required by interim fixes and then apply Interim Fix PI89498 [http://www-01.ibm.com/support/docview.wss?uid=swg24044512] [http://www-01.ibm.com/support/docview.wss?uid=swg24044155] [http://www-01.ibm.com/support/docview.wss?uid=swg24043596] [http://www-01.ibm.com/support/docview.wss?uid=swg24042712] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24042513] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24044155] [http://www-01.ibm.com/support/docview.wss?uid=swg24044154]\n--OR-- \n· Apply Fix Pack 9.0.0.7 or later.", "For V8.5.0.0 through 8.5.5.13: \n· Upgrade to minimal fix pack levels as required by interim fixes and then apply Interim Fix PI89498 [http://www-01.ibm.com/support/docview.wss?uid=swg24044512] [http://www-01.ibm.com/support/docview.wss?uid=swg24044445]\n--OR-- \n· Apply Fix Pack 8.5.5.14 or later (targeted availability 3Q2018). \n\nFor V8.0.0.0 through 8.0.0.14: \n· Upgrade to a minimal fix pack levels as required by interim fix and then apply Interim Fix PI89498 [http://www-01.ibm.com/support/docview.wss?uid=swg24044512] \n--OR-- \n· Apply Fix Pack 8.0.0.15 or later.", "For V7.0.0.0 through 7.0.0.43: \n· Upgrade to a minimal fix pack levels as required by interim fix and then apply Interim Fix PI89498 [http://www-01.ibm.com/support/docview.wss?uid=swg24044512] [http://www-01.ibm.com/support/docview.wss?uid=swg24044445] [http://www-01.ibm.com/support/docview.wss?uid=swg24043596] [http://www-01.ibm.com/support/docview.wss?uid=swg24042712] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24042513] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394]\n--OR-- \n· Apply Fix Pack 7.0.0.45 or later. \n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "IMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 29 January 2018: original document published", "*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." ]

[ "· Upgrade to a minimal fix pack levels as required by interim fix and then apply Interim Fix PI89498 [http://www-01.ibm.com/support/docview.wss?uid=swg24044512] \n--OR-- \n· Apply Fix Pack 8.0.0.15 or later." ]

[ 3 ]

[ "IBM Configuring access for HTTP and HTTPS in Jazz for Service Management - United States jazzsm11relnotes; jazzsm1101relnotes; jazzsm1102; jazzsm1103relnotes; relnotes; jazzsm1110relnotes; jazzsm1120relnotes; jazzsm1121relnotes; HTTP; HTTPS TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n By default, the Jazz™ for Service Management application server requires HTTPS access. You can set up the environment for both HTTP and HTTPS, however HTTP access is not supported. \n\nCAUSE\nFor security reasons, HTTP access is disabled by default and is not supported. \n\nRESOLVING THE PROBLEM\nBefore you begin\n\n\nAfter installing Dashboard Application Services Hub and before beginning this procedure, log in to the console to ensure that it has connectivity and can start successfully. \n\nAbout this task \n\nConfiguring for HTTP and HTTPS console access involves editing theweb.xmlfile of Web components. Use this procedure to identify and edit the appropriate Web XML files.", "Important: These steps are provided for information purposes only, as setting up the environment for HTTP access is not supported. \n\nProcedure \n\n1. Change to the following directory:JazzSM_WAS_Profile/config/cells/JazzSMNode01Cell/applications. \n\n2. From this location, locate theweb.xmlfiles in the following directories: \n\n * For the Integrated Solutions Console web application archive:isc.ear/deployments/isc/isclite.war/WEB-INF \n * For the Charts web application archive:isc.ear/deployments/isc/TIPChartPortlet.war/WEB-INF \n * For the Dashboard Application Services Hub Change Password web application archive:isc.ear/deployments/isc/TIPChangePasswd.war/WEB-INF\n\n\n3. Open one of the web.xmlfiles using a text editor. 4. Find the<transport-guarantee>element. The initial value of all<transport-guarantee>elements isCONFIDENTIAL, meaning that secure access is always required.", "5. Change the setting toNONEto enable both HTTP and HTTPS requests. The element now reads:<transport-guarantee>NONE</transport-guarantee>. \n\n6. Save the file, and then repeat these steps for the otherweb.xmldeployment files. \n\n7. Stop and restart the server. [http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/admin/psc_ctr_admin_restart_jazzsm_servers.html] \n\nExample", "The following example is a section of theweb.xmlfile forTIPChangePasswdwhere the transport-guarantee parameter is set toNONE:\n<security-constraint>\n<display-name>\nChangePasswdControllerServletConstraint</display-name>\n<web-resource-collection>\n<web-resource-name>ChangePasswdControllerServlet</web-resource-name>\n<url-pattern>/*</url-pattern>\n</web-resource-collection>\n<auth-constraint>\n<description>Roles</description>\n<role-name>administrator</role-name>\n<role-name>operator</role-name>\n<role-name>configurator</role-name>\n<role-name>monitor</role-name>\n<role-name>iscadmins</role-name>\n</auth-constraint>\n<user-data-constraint>\n<transport-guarantee>NONE</transport-guarantee>\n</user-data-constraint>\n</security-constraint> \n\nWhat to do next", "Users must now specify a different port, depending on the mode of access. The default port numbers are as follows:\nhttp://<host_name>:16310/ibm/console\nUse the HTTP port for logging in to the Dashboard Application Services Hub on the HTTP port .\nhttps://<host_name>:16311/ibm/console\nUse the HTTPS secure port for logging in to the Dashboard Application Services Hub. \n\nNote:If you want to use single sign-on (SSO) then you must use the fully qualified domain name of the Dashboard Application Services Hub host." ]

[ "By default, the Jazz™ for Service Management application server requires HTTPS access. You can set up the environment for both HTTP and HTTPS, however HTTP access is not supported." ]

[ 0 ]

[ "IBM Security Bulletin: IBM MQ is affected by a potential denial of service to channel processes (CVE-2017-1557) - United States SECURITY BULLETIN\n\nSUMMARY\n An IBM MQ application with authority to connect to a remote queue manager could send a malicious request that could cause undefined behaviour within the channel process servicing that connection, including a loss of service for other connections being serviced by the same channel process.", "VULNERABILITY DETAILS\nCVEID:CVE-2017-1557 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1557]\nDESCRIPTION:IBM MQ could allow an authenticated user with authority to send a specially crafted request that could cause a channel process to cease processing further requests.\nCVSS Base Score: 4.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/131547 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131547]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ and IBM MQ Appliance v8.0.0.0 to v8.0.0.7 \n\nIBM MQ v9.0.0.0 LTS to v9.0.0.1 LTS \n\nIBM MQ and IBM MQ Appliance v9.0.1 CD to v9.0.3 CD\n\nREMEDIATION/FIXES\nIBM MQ and IBM MQ Appliance v8.0.0.0 to v8.0.0.7 \n\nApply fix pack 8.0.0.8 [http://www-01.ibm.com/support/docview.wss?uid=swg22010861] \n\nIBM MQ v9.0.0.0 LTS to v9.0.0.1 LTS", "Apply fix pack 9.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24044038] \n\nIBM MQ and IBM MQ Appliance v9.0.1 CD to v9.0.3 CD \n\nApply IBM MQ 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 22 Dec 2017 - Original Published", "*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." ]

[ "CVEID:CVE-2017-1557 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1557]\nDESCRIPTION:IBM MQ could allow an authenticated user with authority to send a specially crafted request that could cause a channel process to cease processing further requests.\nCVSS Base Score: 4.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/131547 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131547]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L)" ]

[ 1 ]

[ "IBM Unable to add Centera Device in FileNet Content Engine - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Errors received clicking \"Test Connection\" when configuring Centera Device in FileNet Enterprise Manager \n\nSYMPTOM\nAfter entering configuration information in FEM Fixed Content Device Wizard the following error is received: \n\nFile = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ \n\n \n\nThe [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path). \n\n \n\nError in the p8_server_error.log:", "2011-06-06T18:54:57.245Z 00C900C9 ENG FNRCC0110E - ERROR method name: initialize principal name: P270IH Global Transaction: true User Transaction: false Exception Info: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed.\ncom.filenet.api.exception.EngineRuntimeException: FNRCC0110E: CONTENT_FCP_OPERATION_FAILED: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed. failedBatchItem=0 errorStack={\n\nCaused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path) failedBatchItem=0\n\nCaused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path)", "CAUSE\nChanges made to the setCenteraLibPath.sh or setCenteraLibPath were not picked up by the WAS startup script. The WAS Content Engine instance was restarted from within the WAS console and not from the command line. In this Instance the setCenteraLibPath.sh file was added to the setupcmdLine.sh file but was not recognized . This caused the CenteraSDK path to not be loaded. \n\n\nENVIRONMENT\nIBM Websphere\n\n\n\nDIAGNOSING THE PROBLEM\nFollowing error is received when \"Test Connection\" is clicked: \n\nFile = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ \n\n \n\nThe [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path).\n\n\nRESOLVING THE PROBLEM\nAfter making any changes to the setCenteraLibPath.sh or setCenteraLibPath.bat file restart WebSphere from the IBM console or the changes will not be detected.", "Cross reference information Segment Product Component Platform Version Edition Enterprise Content Management FileNet Content Manager Content Engine \nHISTORICAL NUMBER\n 41550\n180\n000" ]

[ "Changes made to the setCenteraLibPath.sh or setCenteraLibPath were not picked up by the WAS startup script. The WAS Content Engine instance was restarted from within the WAS console and not from the command line. In this Instance the setCenteraLibPath.sh file was added to the setupcmdLine.sh file but was not recognized . This caused the CenteraSDK path to not be loaded." ]

[ 2 ]

[ "IBM Using -Xgc:preferredHeapBase with -Xcompressedrefs - United States TECHNOTE (FAQ)\n\nQUESTION\n \"Why does the JVM report a native out-of-memory (NOOM) when using compressed references? I am using a 64bit JVM and I clearly have plenty of memory left. How can I resolve this problem?\" \n\nCAUSE", "*In this note, please refer to Java Versioning: Java Version.Release.ServiceRelease.FixPack \nex: Java 7.1.4.6 is the same as Java 7.1 SR4 FP6 is the same as Java 7 R1 SR4 FP6. \nThe IBM JVM will automatically use compressed references [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html]when using a maximum heap size less than 25GB. This automated behavior was introduced in Java 6.1.5.0 and Java 7.0.4.0*. Compressed references (CR) decreases the size of Java objects making better use of available memory space. This better use of space results in improved JVM performance. *(Java 7.0.1.1 and later uses compressed references by default on z/OS) \n\nSee Introducing WebSphere Compressed Reference Technology [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf] for detailed information on how Compressed References work.", "\"When using compressed references, the size of the field used in the Java object for the Class Pointer and the Monitor/Lock is 32 bits instead of the 64bits that would be available in non-compressed mode. Because we are using 32 bits to store the location of these, and they are located in native (non-Java heap) memory, they must be allocated in the first 4GB of the address space - the maximum range we can address with the 32 bits.\" ~IBM Java Development Team \n\nIf the Java heap itself is small (-Xmx), the JVM may allocate it in the lower 4GB of address space along with the Class Pointers and Monitors/Locks. If these Class Pointers, Monitors/Locks and Java heap (if included) cannot fit in the lower 4GB, a native out of memory (NOOM) [http://www.ibm.com/developerworks/library/j-nativememory-linux/] will be thrown. \nANSWER\nWhy Use Compressed References?", "Below the 4GB mark, the JVM does not have to perform any compression/decompression of the address pointer at runtime. Therefore, the best performance will be attained if the Class Pointers, Monitors/Locks and Java heap can all be contained comfortably within the lowest 4GB of the address space. \n\n \n\nDetermining Address Location of Java Heap Memory \n\nTo verify if the Java heap has memory regions below the 4GB mark, check the \"Object Memory\" section in the javacore:\n\nConvert the \"start\" address from the hex value to a GB value [http://ss64.com/convert.html]. In the example below, 0x000000000F010000=0.23GB which is below the the 4GB (0x0000000100000000) mark.\n\n\n\n * [/support/docview.wss?uid=swg21660890&amp;aid=1]\n\n\nSetting the Preferred Heap Base with -Xgc:preferredHeapBase", "Starting with Java 6.1.6.0 and Java 7.0.5.0, and later, the JVM will determine if the Java heap will fit comfortably in the lower 4GB. If it is too large, the JVM will automatically allocate the Java heap above the 4GB mark (APAR IV37797 [http://www-01.ibm.com/support/docview.wss?uid=swg1IV37797]).", "NOTE: In IBM System z platforms (i.e. z/OS and z/Linux), automatic shift of the heap above the 4GB address space does NOT occur because on these platforms, there is an additional performance penalty \nassociated with higher shift values. To resolve Native OOM issues due to a shortage of heap memory in the lower region on z platforms, use -Xnocompressedrefs (see below).", "See related: IBM Knowledge Center - JVMJ9GC089W [https://www.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.messages/diag/appendixes/messages/j9gc/message_jvmj9gc089.html] However, in earlier Java 6.1 and Java 7.0 versions (earlier than Java 6.1.6.0 and Java 7.0.5.0), if the Java heap can not fit in the lower 4GB, a NOOM will occur. To avoid this problem, the generic JVM argument [http://www-01.ibm.com/support/docview.wss?uid=swg21417365] -Xgc:preferredHeapBase=<address> [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html] can be used to ensure the Java heap is allocated above the 4GB address space. This will leave more room for the Class Pointer and Monitor/Lock memory.", "* \n * \n * \n * \n * \n * \n * This will locate the Java heap starting at the 4GB mark thus leaving the lower 4GB for the other processes.\n\n\nIncrease Maximum Heap Size to Force Heap Allocation Above the 4GB mark \n\nAnother way to ensure that the heap is allocated above the 4GB mark (Java 6.1.6.0 and Java 7.0.5.0 and later) is to set a maximum heap size equal to or greater than 4GB. For example -Xmx4G will ensure that the heap will have to be allocated above the 4GB mark. This will not work in earlier versions of the JVM since these earlier versions allowed the heap to straddle the 4GB mark, placing part of the memory above and some below (fixed as part of APAR IV37797) . \n\n \n\nFurther Investigation", "If after setting -Xgc:preferredHeapBase=<address> or -Xmx4G a NOOM is still encountered (Java 6.1.6.0 and Java 7.0.5.0 and later), then further investigation is required at the application level. Look to decrease the size and usage of the applications Class Pointers and Monitors/Locks. Additionally, there are some WebSphere Application Server troubleshooting methods that may help reduce the native memory footprint. See: IBM Troubleshooting native memory issues [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21373312].\n\nReserving Low-Memory Space with -Xmcrs\n\nIf there is still free memory in the system when a Native OutOfMemory (NOOM) occurs, then the problem may be a shortage of memory in the low-memory region (under 4GB). Even if the Java heap is located above this boundary, other data associated with Java objects can be located in the low-memory region.", "The OS memory allocator will deal out low-memory freely, thus memory resources in the lower boundary may run out. Later when the JVM tries to allocate memory for an artifact which is required to be allocated in low-memory (because the JVM has only reserved a 32bit pointer for it) it fails and throws an OutOfMemoryError.\n\nStarting in Java 6.0.16.3, Java 6.1.8.3, Java 7.0.8.10, Java 7.1.2.10, there is a parameter -Xmcrs [http://www-01.ibm.com/support/knowledgecenter/SSYKE2_6.0.0/com.ibm.java.doc.diagnostics.60/diag/appendixes/cmdline/xmcrs.html] which allows the JVM to increase the amount of low memory it reserves on startup. With this setting, as long as the low-memory usage by the JVM does not exceed the -Xmcrs value, NOOM in the lower boundary will be avoided.\n\nTo set this parameter, first decide what a reasonable value for your lower memory requirements may be. Reasonable value is unique to each environment so there is not a general recommendation.", "* -Xmcrs<reasonable_value_for_lower_memory>\n\n * \n * NATIVEMEMINFO subcomponent dump routine\n * \n * \n * \n * \n * \n * \n * \n * \n * [/support/docview.wss?uid=swg21660890&amp;aid=2]\n *", "Disabling Compressed References with -Xnocompressedrefs As a last resort, if the native memory still can not be contained under the 4GB mark, you can set -Xnocompressedrefs [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/appendixes/cmdline/Xnocompressedrefs.html] as a generic JVM argument. [http://www-01.ibm.com/support/docview.wss?uid=swg21417365] Using -Xnocompressedrefs will remove the use of compressed references and therefore remove the lower 4GB memory restriction on the Class Pointers and Monitors/Locks. This will however, result in a significant increase in Java heap memory requirements. It is not uncommon for 70% more heap space to be required. Due to the increased memory requirements it is strongly advised that the Java heap size is adjusted to a larger value and garbage collection is monitored and retuned as required.", "Additionally, some benchmarks show a 10-20% relative throughput decrease when disabling compressed references: \"Analysis shows that a 64-bit application without CR yields only 80-85% of 32-bit throughput but with CR yields 90-95%. Depending on application requirements, CR can improve performance up to 20% over standard 64-bit.\" See:ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf].", "Before using -Xnocompressedrefs as a solution, first rule out the possibility of a native memory leak. Since using -Xnocompressedrefs will allow the the native memory to grow unbounded, a leak in native memory will lead to process size growth eventually leading to a process that needs to be paged out. The paging will incur performance overhead which will eventually lead to an unstable environment. Therefore careful consideration must be used when selecting -Xnocompressedrefs as a solution.\n\n\nMemory Map Considerations \n\nThe below figure is a generalization of how the JVM handles addresses in each section of the memory map based on heap size and compressed references (CR). Please note that at each stage beyond having all of the Java memory contained below the 4GB mark, there will be performance consequences: \n\n\n\n[/support/docview.wss?uid=swg21660890&amp;aid=3]", "No Compressed References Overhead using -Xnocompressedrefs \nor\n-Xmx > 25GB -increased memory footprint\n-fewer/larger objects stored on heap leads to more frequent GC\n-lower cache and translation look aside buffer (TLB) utilization [/support/docview.wss?uid=swg21660890&amp;aid=4] Compressed References Overhead maximum heap address used by the Java JVM process is below 4GB none maximum heap address used by the Java JVM process is above 4GB but below 32GB compression/decompression of address pointers \n\n\nGetting Assistance From IBM Support \nIf further assistance will be required from IBM WebSphere Support, please set the following -Xdump [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/tools/dumpagents_syntax.html] parameters in the generic JVM arguments [http://www-01.ibm.com/support/docview.wss?uid=swg21417365]: \n * \n * \n *", "Then restart the JVM and recreate the problem. Once the NOOM is encountered, process the resulting system core with jextract [http://www-01.ibm.com/support/docview.wss?uid=swg21577379]. Send the jextracted core file, heapdump, javacore, snap trace, systemOut.log, native_stderr.log, native_stdout.log and systemErr.log to IBM Support [http://www-01.ibm.com/support/docview.wss?uid=swg21153852] for further analysis. \nRELATED INFORMATION\n Linux/Windows - Thanks for the memory [http://www.ibm.com/developerworks/library/j-nativememory-linux/]\nAIX - Thanks for the Memory [http://www.ibm.com/developerworks/library/j-nativememory-aix/]\nIntroducing WebSphere Compressed Reference Technology [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf]\nCompressed references [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html]", "IBM Java Compressed References and Native OOMs [https://www.ibm.com/developerworks/community/blogs/kevgrig/entry/ibm_java_compressed_references_and_native_ooms]" ]

[ "when using compressed references? I am using a 64bit JVM and I clearly have plenty of memory left. How can I resolve this problem?\" \n\nCAUSE\n \n\n*In this note, please refer to Java Versioning: Java Version.Release.ServiceRelease.FixPack \nex: Java 7.1.4.6 is the same as Java 7.1 SR4 FP6 is the same as Java 7 R1 SR4 FP6. \nThe IBM JVM will automatically use compressed references [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html]when using a maximum heap size less than 25GB. This automated behavior was introduced in Java 6.1.5.0 and Java 7.0.4.0*. Compressed references (CR) decreases the size of Java objects making better use of available memory space. This better use of space results in improved JVM performance. *(Java 7.0.1.1 and later uses compressed references by default on z/OS) \n\nSee Introducing WebSphere Compressed Reference Technology [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf] for detailed information on how Compressed References work. \n\n\"When using compressed references, the size of the field used in the Java object for the Class Pointer and the Monitor/Lock is 32 bits instead of the 64bits that would be available in non-compressed mode. Because we are using 32 bits to store the location of these, and they are located in native (non-Java heap) memory, they must be allocated in the first 4GB of the address space - the maximum range we can address with the 32 bits.\"" ]

[]

[ "IBM Unable to add Centera Device in FileNet Content Engine - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Errors received clicking \"Test Connection\" when configuring Centera Device in FileNet Enterprise Manager \n\nSYMPTOM\nAfter entering configuration information in FEM Fixed Content Device Wizard the following error is received: \n\nFile = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ \n\n \n\nThe [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path). \n\n \n\nError in the p8_server_error.log:", "2011-06-06T18:54:57.245Z 00C900C9 ENG FNRCC0110E - ERROR method name: initialize principal name: P270IH Global Transaction: true User Transaction: false Exception Info: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed.\ncom.filenet.api.exception.EngineRuntimeException: FNRCC0110E: CONTENT_FCP_OPERATION_FAILED: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed. failedBatchItem=0 errorStack={\n\nCaused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path) failedBatchItem=0\n\nCaused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path)", "CAUSE\nChanges made to the setCenteraLibPath.sh or setCenteraLibPath were not picked up by the WAS startup script. The WAS Content Engine instance was restarted from within the WAS console and not from the command line. In this Instance the setCenteraLibPath.sh file was added to the setupcmdLine.sh file but was not recognized . This caused the CenteraSDK path to not be loaded. \n\n\nENVIRONMENT\nIBM Websphere\n\n\n\nDIAGNOSING THE PROBLEM\nFollowing error is received when \"Test Connection\" is clicked: \n\nFile = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ \n\n \n\nThe [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path).\n\n\nRESOLVING THE PROBLEM\nAfter making any changes to the setCenteraLibPath.sh or setCenteraLibPath.bat file restart WebSphere from the IBM console or the changes will not be detected.", "Cross reference information Segment Product Component Platform Version Edition Enterprise Content Management FileNet Content Manager Content Engine \nHISTORICAL NUMBER\n 41550\n180\n000" ]

[ "After making any changes to the setCenteraLibPath.sh or setCenteraLibPath.bat file restart WebSphere from the IBM console or the changes will not be detected." ]

[ 2 ]

[ "IBM Automated data collection capability provided by wpcollector tool - United States wpcollector isalite isa lite data collection collector diagnostics TECHNOTE (FAQ)\n\nQUESTION\n What are the benefits of the wpcollector tool? How do I use this tool? \n\nANSWER\nWpcollector is a command line tool that automates the collection of portal logs and configuration files. Using automated log collection early in the Case life cycle can greatly reduce the number of doc requests that are made by Support. \n\nWpcollector is delivered with WebSphere Portal beginning with the 7.0 release. If tracing is required for the problem scenario, you must manually enable traceStrings and recreate the problem PRIOR to running wpcollector. \n\nTo run wpcollector, please follow the steps, below:\n\n\n\n * If IBM Support has requested tracing, enable it as instructed by the L2 Support Engineer and then recreate the problem. If no tracing is requested, proceed to the step, below:", "* If using Microsoft Windows, Unix/Linux, or IBM i, run the following script from the <wp_profile_root> [http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/reference/wpsdirstr.dita]/PortalServer/bin/ directory to begin the collection: * \n * \n * Unix/Linux: wpcollector.sh \n * i: wpcollector.sh \n * \n * Tip: To specify the option for collecting files for the Deployment Manager profile, use the \"dmgr.root\" parameter. For example: \n * wpcollector.bat -Ddmgr.root=/opt/IBM/WebSphere/profiles/dmgr_profile\n \n \n * If using IBM z/OS, proceed as follows [../reference/wpsdirstr.html%5C]: * \n * \n * In the Portal configuration panel, select Collect Diagnostics. \n * Follow the Customization Dialog instructions for submitting the Collect Diagnostics job (EJPSLOGS). \n *", "* Tip: To collect data from the Deployment Manager, the only requirement is to submit the job from the system where the Deployment Manager is installed (i.e. so it can access the files). There is no prompt in the ISPF panel for this.\n \n \n * Locate the wp.mustgather-<timestamp>.zip file in the <wp_profile_root> [http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/reference/wpsdirstr.dita]/filesForAutoPD/ directory and follow the instructions in \"Exchanging information with IBM Technical Support for problem determination\" [http://www-01.ibm.com/support/docview.wss?uid=swg21153852] to manually FTP the collection to IBM. If using z/OS, there may be additional z/OS-specific files required, such as WebSphere Portal servant region or controller region joblogs. Wpcollector currently does not collect these files. Your L2 Support Engineer will inform you in the event these files are needed and provide instructions for collecting them.", "* If tracing was requested and enabled, please follow the instructions provided by the L2 Support Engineer to disable tracing from the environment\n\nRELATED INFORMATION\n Data Collection and Symptom Analysis [http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/trouble/tbl_apdt_over.dita?lang=en]" ]

[ "Wpcollector is a command line tool that automates the collection of portal logs and configuration files. Using automated log collection early in the Case life cycle can greatly reduce the number of doc requests that are made by Support." ]

[ 0 ]

[ "IBM PI37248: A PROPERTY FILE BASED CONFIGURATION (PFBC) FILE MIGHT FAIL TO AP PLY. - United States FIXES ARE AVAILABLE\n8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040035]\n8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24040425]\n8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24040533]\n8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041178]\n8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24041590]\n8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24041819]\n8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]", "8.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]", "SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.", "ERROR DESCRIPTION\n * A PFBC file might fail to apply. Wsadmin will show an error\n similar to this:\n \n java.lang.Exception: java.lang.Exception: ADMG0660E:\n Properties File Validation during command\n applyConfigProperties failed. See Report file for details.\n \n The report file will contain an error similar to this:\n Error=java.lang.NullPointerException\n at\n com.ibm.websphere.management.configservice.ConfigServiceHelper.g\n etConfigDataType(ConfigServiceHelper.java:235)\n at\n com.ibm.ws.management.configservice.WorkspaceHelper.getType(Work\n spaceHelper.java:563)\n at\n com.ibm.ws.management.configservice.WorkspaceHelper.getDelegator\n (WorkspaceHelper.java:584)\n at\n com.ibm.ws.management.configservice.ConfigServiceImpl.getAttribu\n tes(ConfigServiceImpl.java:2102)\n at\n com.ibm.ws.management.commands.properties.resources.common.Apply\n Properties.setProperties(ApplyProperties.java:240)\n \n \n \n \n \n\nLOCAL FIX", "PROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server Property File Based Configuration *\n ****************************************************************\n * PROBLEM DESCRIPTION: A Property File Based Configuration *\n * (PFBC) file might fail to apply. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n A recent (8.5.5.5) parser change introduced a problem where\n types that have default values noted in the file and are not\n Strings can be incorrectly processed. For example:\n isolatedClassLoader=false #boolean,default(false)\n might be incorrectly processed, and as a result, the file\n might not apply.", "PROBLEM CONCLUSION\n * The parsing code is updated so the problem no longer occurs.\n \n The fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.5.6. Please refer to the Recommended Updates\n page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI37248\n \n \n * REPORTED COMPONENT NAME\n WEBS APP SERV N\n \n \n * REPORTED COMPONENT ID\n 5724H8800\n \n \n * REPORTED RELEASE\n 850\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt / Xsystem\n \n \n * SUBMITTED DATE\n 2015-03-18\n \n \n * CLOSED DATE\n 2015-03-20\n \n \n * LAST MODIFIED DATE\n 2015-03-24", "* 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" ]

[ "The parsing code is updated so the problem no longer occurs.\n \n The fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.5.6." ]

[ 5 ]

[ "IBM Removing a failed install from the ITM i5/OS agent - United States i5 removal TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n If an ITM i5/OS agent DLTLICPGM 5724C04 command fails then we have to remove the various parts of the agent that have been installed. This has to be done by hand because the DLTLICPGM 5724C04 command will fail as the unistall encounter some issues during uninstall. This technote will show how to do it. \n\nSYMPTOM\nRSTLICPGM command fails to install the ITM i5/OS agent. \n\nDLTLICPGM 5724C04 command fails to uninstall the agent\n\n\nCAUSE\nRSTLICPGM/DLTLICPGM 5724C04 command failed to finish correctly and leaves the agent in an unknown state.\n\n\nENVIRONMENT\nIBM i / i5/OS machines\n\n\n\nDIAGNOSING THE PROBLEM\nRSTLICPGM and DLTLICPGM 5724C04 fail for the i5 agent.\n\n\n\nRESOLVING THE PROBLEM\n \n\n To delete the ITM i5/OS agent do the following :- \n\nFirst try DLTLICPGM 5724C04 for the Tivoli agent. If that does not work then do \nthe following i5/OS commands :", "DLTLIB QAUTOMON \nDLTLIB QAUTOTMP \nDLTUSRPRF QAUTOMON and choose to remove all objects owned by this user.\n\nstart qsh \ndelete /QIBM/USERDATA/IBM/ITM and all sub directories in it. \ndelete /QIBM/PRODDATA/IBM/ITM and all sub directories in it. \n\nRetry the RSTLICPGM commands specified in the user guide. \nhttp://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/osibmi/pcinstall_a4_ug.htm?lang=en [http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/osibmi/pcinstall_a4_ug.htm?lang=en]\n\n\n\nPRODUCT ALIAS/SYNONYM\n ITM OS/400 agent\nITM i5/OS agent\nITM IBM i agent\n5724C04" ]

[ "To delete the ITM i5/OS agent do the following :- \n\nFirst try DLTLICPGM 5724C04 for the Tivoli agent. If that does not work then do \nthe following i5/OS commands : \n\nDLTLIB QAUTOMON \nDLTLIB QAUTOTMP \nDLTUSRPRF QAUTOMON and choose to remove all objects owned by this user.\n\nstart qsh \ndelete /QIBM/USERDATA/IBM/ITM and all sub directories in it. \ndelete /QIBM/PRODDATA/IBM/ITM and all sub directories in it. \n\nRetry the RSTLICPGM commands specified in the user guide." ]

[]

[ "IBM Operational Decision Manager V8.5.1.2 Fix Pack - United States DOWNLOADABLE FILES\n\nABSTRACT\n This cumulative fix pack updates Operational Decision Manager V8.5.1 and V8.5.1.1 to V8.5.1.2. \n\nDOWNLOAD DESCRIPTION\nThis fix pack is entitled. Only customers who have purchased Operational Decision Manager V8.5.1 can use this fix pack.\n\n\nHow to install the fix pack\nIf you are not installing both Operational Decision Manager components, skip the instructions regarding Decision Center or Decision Server.\n\n\n 1. For Decision Center, download 8.5.1-WS-ODM_DC-<OS>-FP002.zip, and extract its files. (Change <OS> to match your platform: AIX, HPUX, LINUX, OS400, SOLARIS, ZOS, or WIN32.) \n 2. Extract the archive to a new folder, named WDC. \n 3. For Decision Server, Download 8.5.1-WS-ODM_DS-<OS>-FP002.zip, and extract its files. (Change <OS> to match your platform: AIX, HPUX, LINUX, OS400, SOLARIS, ZOS, or WIN32.) \n 4. Extract the archive to a new folder, named WDS.", "Installing by using IBM Installation Manager: 1. Launch IBM Installation Manager. \n 2. In the toolbar menu, open File > Preferences and do the following: \n 3. Select repositories. \n 4. For Decision Center, click Add Repository. \n 5. Browse to the extracted folder WDC\\updates. \n 6. Select the file repository.config. \n 7. For Decision Server, click Add Repository. \n 8. Browse to the extracted folder WDS\\updates. \n 9. Select the file repository.config. \n 10. Make sure the repositories are selected in the Repositories list. \n 11. Click Apply to save your changes, and click OK to close the Repositories list. \n 12. Click Update to update your installation. \n 13. Follow the instructions in the installation manager to complete the installation.\n\n\nInstalling by using the Installation Manager command line: 1. Locate the imcl command under <IM installation>/eclipse/tools. \n 2. Run the commandimcl updateAll -repositories WDC/updates,WDS/updates -acceptLicense.", "* Use the option -installDirectory <install path of ODM 8.5.1> to update a specific installation. \n * If you update only Decision Server or Decision Center, specify the repository accordingly.\n\n\nApplying the fix pack \nAfter you install the fix pack, you might have to do additional steps to apply the fix pack in your environment. To complete the update, see When and how to apply a modification or fix pack [http://www-01.ibm.com/support/docview.wss?uid=swg21665766].", "Warning: \nIf you have installed interim fixes for Operational Decision Manager V8.5.1, you must uninstall the fixes before you can install this fix pack. You must also stop the Operational Decision Manager sample server for this installation. If you do not uninstall the fixes and stop the server, the installation of the fix pack fails. If you attempt to install the fix pack without uninstalling the interim fixes, the installer uninstalls the interim fixes before the installer fails. In this case, stop the sample server and restart the installation. INSTALLATION INSTRUCTIONS\nFollow the instructions provided in the following resources:\n\nDOWNLOAD PACKAGE\n\n\n\nPROBLEMS SOLVED\nFix List for IBM Operational Decision Manager [http://www.ibm.com/support/docview.wss?uid=swg27023767]", "Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs]", "What is DD? [http://www6.software.ibm.com/dldirector/doc/DDfaq_en.html] ODM 8.5.1.0 AIX 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=AIX&function=all] [ ] DD ODM 8.5.1.0 HPUX 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=HPUX&function=all] [ ] DD ODM 8.5.1.0 Linux PPC 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Linux+PPC&function=all] [ ] DD ODM 8.5.1.0 Linux x86 30 Jan 2015 Language Independent 4000000000 FC", "[http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Linux+x86&function=all] [ ] DD ODM 8.5.1.0 Linux zSeries 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Linux+zSeries&function=all] [ ] DD ODM 8.5.1.0 OS/400 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=OS/400&function=all] [ ] DD ODM 8.5.1.0 Solaris 32-bit SPARC 30 Jan 2015 Language Independent 4000000000 FC", "[http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Solaris+32-bit,SPARC&function=all] [ ] DD ODM 8.5.1.0 Solaris 64-bit SPARC 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Solaris+64-bit,SPARC&function=all] [ ] DD ODM 8.5.1.0 Solaris 32-bit x86 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Solaris+32-bit,x86&function=all] [ ] DD ODM 8.5.1.0 Solaris 64-bit x86 30 Jan 2015 Language Independent 4000000000 FC", "[http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Solaris+64-bit,x86&function=all] [ ] DD ODM 8.5.1.0 Windows 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Windows&function=all] [ ] DD", "[/support/docview.wss?uid=swg24039235&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24039235&aid=2]Problems (APARS) fixed", "PI31830, PI31844, RS01612, RS01617, RS01630, RS01631, RS01635, RS01641, RS01645, RS01646, RS01653, RS01661, RS01664, RS01667, RS01668, RS01669, RS01670, RS01671, RS01680, RS01682, RS01683, RS01685, RS01686, RS01689, RS01690, RS01693, RS01694, RS01695, RS01697, RS01698, RS01700, RS01704, RS01707, RS01708, RS01709, RS01710, RS01711, RS01712, RS01714, RS01715, RS01716, RS01718, RS01720, RS01723, RS01725, RS01728, RS01733, RS01734, RS01735, RS01737, RS01743, RS01744, RS01748, RS01750, RS01751, RS01752, RS01754, RS01755, RS01760, RS01763, RS01768, RS01770, RS01774, RS01775, RS01779, RS01784, RS01790, RS01792, RS01793, RS01794, RS01795, RS01796, RS01798, RS01801, RS01804, RS01806, RS01809, RS01811, RS01813, RS01814, RS01817, RS01818, RS01819, RS01821, RS01824, RS01825, RS01827, RS01828, RS01831, RS01832, RS01850, RS01853, RS01854, RS01855, RS01856, RS01858, RS01859, RS01860, RS01862, RS01699" ]

[ "This cumulative fix pack updates Operational Decision Manager V8.5.1 and V8.5.1.1 to V8.5.1.2." ]

[ 0 ]

[ "IBM WebSphere SDK Java Technology Edition 8.0 Minimum Supported Operating Systems - United States RELEASE NOTES\n\nABSTRACT\n IBM WebSphere SDK Java Technology Edition 8.0 Minimum Supported Operating Systems \n\nCONTENT\nWebSphere Application Server 8.5.5 announced IBM WebSphere SDK Java Technology Edition 8.0 as an option for Java. \n\n\n\n\n * Liberty added support in fix pack 5 \n * WebSphere Application Server traditional added support for installing this SDK as an extension in 8.5.5.9 * In 8.5.5.11 and later, this SDK is available as an option on new installations. \n * In 8.5.5.14 and later, it is planned that this SDK will be required for all new installations and all updates (fixpacks).\n \n \n\nThe following are the minimum supported OS levels for IBM WebSphere SDK Java Technology Edition 8.0 in WebSphere Application Server. Action Required:\n\n * \n * \n * .0\n * \n\n\nOperating System minimums:", "* AIX\n * AIX 6.1 TL7 \n AIX 7.1 TL3 \n * HP-UX IA64\n * HP-UX 11i v3 (11.31) \n * IBM i\n * IBM i V7R1 \n * Linux\n * RedHat Enterprise Linux 6 \n RedHat Enterprise Linux 7 \n SLES 11.1 (SP1) \n SLES 12 \n Ubuntu 12.04 LTS \n Ubuntu 14.04 LTS \n Ubuntu 16.04 LTS \n * Windows\n * Windows 7 service pack 1 \n Windows 8 (not Metro) \n Windows Server 2012 \n Windows Server 2016 \n * Solaris \n * Solaris 11 \n * z/OS\n * z/OS 1.13 \n z/OS 2.1 \n z/OS 2.2 \n\n\n\nComponent specific notes: * WebSphere Application Server installations between 8.5.5.11 and 8.5.5.14 require an explicit user selection to determine the default IBM WebSphere SDK Java Technology Edition on new installations. \n * IBM HTTP Server and the Webserver Plug-in between 8.5.5.11 and 8.5.5.14 defaults to IBM WebSphere SDK Java Technology Edition 8.0. No explicit selection is required. These components do not use Java at runtime." ]

[ "Operating System minimums: \n\n * AIX\n * AIX 6.1 TL7 \n AIX 7.1 TL3 \n * HP-UX IA64\n * HP-UX 11i v3 (11.31) \n * IBM i\n * IBM i V7R1 \n * Linux\n * RedHat Enterprise Linux 6" ]

[]

[ "IBM Writing Verbose GC To A Specified Log In Solaris and HP-UX - United States verbosegc log rotation HP Solaris JVM rotate file TECHNOTE (FAQ)\n\nQUESTION\n How can I write verbose gc output to a log file other than the native_stdout? \n\nCAUSE\nBy default, Solaris and HP-UX do not write verbose GC to a log file. This must be configured.\n\nANSWER\n \n\nWAS 8.5.0.2 (and higher), WAS 8.0.0.6 (and higher), WAS 7.0.0.27 (and higher):\n\nSolaris:\nAdd the following parameters to the generic JVM arguments:\n\n-XX:+PrintGCDetails \n-XX:+PrintGCDateStamps \n-XX:+PrintHeapAtGC \n-Xloggc:/tmp/gc.log\n\nTo enable log file rotation:\n-XX:+UseGCLogFileRotation\n-XX:NumberOfGCLogFiles=10\n-XX:GCLogFileSize=10M\n\n\nnotes:\n-Xloggc:<fileName> \n\n * ex: -Xloggc:/tmp/gc.log \n\n-XX:+UseGCLogFileRotati o n * Enabled GC log rotation, requires -Xloggc", "-XX:NumberOfGClogFiles= <num_of_files> * Set the number of files to use when rotating logs, must be >= 1. The rotated log files will use the following naming scheme, <filename>.0, <filename>.1, ..., <filename>.n-1. \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", "note : $$ 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]" ]

[ "Add the following parameters to the generic JVM arguments:\n\n-XX:+PrintGCDetails \n-XX:+PrintGCDateStamps \n-XX:+PrintHeapAtGC \n-Xloggc:/tmp/gc.log" ]

[ 0 ]

[ "IBM Rule Team Server/Decision Center is timing out while performing certain operations - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n How to resolve \"Transaction timed out after 601 seconds\" error while performing certain operations in Rule Team Server (RTS)/Decision Center (DC)? \n\nSYMPTOM\nWhile generating ruleapps in RTS/DC, the following error is thrown after a few minutes (typically 5 or 10 minutes): \n\nOn WebLogic: \n\nRule Team Server has encountered an unexpected error. The internal error message is: #{SelectionBean.asynchAction}: javax.faces.el.EvaluationException: java.lang.RuntimeException: java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 601 seconds BEA1-5057DF8C316E1C1224CD]'. No further JDBC access is allowed within this transaction. \n\n...", "On 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.", "RESOLVING 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].", "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" ]

[ "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." ]

[ 2 ]

[ "IBM DataPower firmware version 6.0 will enable TLS v1.2 or v1.1 by default - United States ssl tsl client hello handshake fail failed version 6.0 TECHNOTE (FAQ)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n English \n\nQUESTION\n Why would some outgoing SSL handshakes fail with firmware version 6.0 but not prior firmware versions? \n\nCAUSE\nBeginning in firmware version 6.0 and above, the default SSL settings have changed. The Crypto profiles now have TLSv1.2 and 1.1 which will be enabled by default. This affects the protocol version included in the Client Hello when DataPower is acting as the SSL client. If TLSv1.2 is not supported, the server still negotiates to the most secure supported protocol (e.g. TLSv1.1, TLSv1.0, SSLv3) if enabled. \n\nSome legacy servers with non-compliant implementations of SSL may reject connection attempts when TLSv1.2 or TLSv1.1 are used. In these cases, the handshake fails without properly negotiating to a mutually agreeable protocol.", "The TLS versions 1.1 and 1.2 are part of the requirements for being compliant with NIST SP800-131a.\n\n\n\nANSWER\nUpgrade the SSL server to a version compliant with the SSL/TLS specifications. If required you may disable TLSv1.2 and TLSv1.1 within the Crypto Profile to allow compatibility. \n\n\nWithin the domain simply navigate to the Objects> Crypto Configuration> Crypto Profile>\nThen simply click on your specific profile to view the Options selection and see what SSL protocol versions are supported.\n\nAny further questions or issues please feel free to contact DataPower support. A packet trace and error report would be the most helpful information in viewing the problem." ]

[ "Some legacy servers with non-compliant implementations of SSL may reject connection attempts when TLSv1.2 or TLSv1.1 are used. In these cases, the handshake fails without properly negotiating to a mutually agreeable protocol." ]

[ 0 ]

[ "IBM PI34677: MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION - United States A FIX IS AVAILABLE\nFixes integrated in WebSphere Portal 8.5.0.0 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24037786]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * During Portal Start-Up following error is shown:\n --------------------\n 0000005e MBeanStarter E com.ibm.wps.\n \n scripting.server.MBeanStarter loadExtensions failed to load\n extension:\n key: ServerExt.applications / value:\n com.ibm.wps.scripting.server.\n ApplicationServerExtensions", "LOCAL 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", "PROBLEM 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" ]

[ "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" ]

[ 1 ]

[ "IBM An unexpected ruleset version is executed - United States TECHNOTE (FAQ)\n\nQUESTION\n Why is Rule Execution Server (RES) not executing the expected version of a ruleset ?\nWhat are the possible causes after a hot deployment for Rule Execution Server not to use the updated ruleset ? \n\nCAUSE\nPossible causes for unexpected versions to be executed are: \n- the RES client requesting execution may be passing a wrong ruleset path\n- a hot deploy notification was not sent by the RES console, or not received by all the Execution Units (XU)\n- the ruleset parsing policy may be delaying the use of a ruleset version until its parsing is complete\n- the updated ruleset cannot be parsed successfully and RES falls back on an earlier active version that parses", "ANSWER\nFirst validate that the RES components (the Execution Unit, the Management Console and the Client Application bundling the RES client library, which may be HTDS, MTDS, the SSP or a custom application) have been installed properly as per the documentation, see Configuring Rule Execution Server [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.config/config_ds_res/tpc_res_config.html]. \n\nThe ruleset version that is executed depends first on the ruleset path that is requested. Specifying a ruleset path with no version ( such as /MyRuleApp/MyRuleset/ ) is interpreted as a request to execute the highest version of the ruleset, as opposed to a version specific ruleset path ( such as /MyRuleApp/2.0/MyRuleset/1.0 ). Validate that the executed ruleset path is indeed unexpected considering the requested ruleset path.", "A common situation for an unexpected ruleset version to be executed is that of a hot deployment that is not successfully completed. The more frequent causes for the hot deployment not to happen as expected are:", "* Permission issue: the user publishing the ruleset update must have sufficient administrative rights ( Monitor role in WebSphere Application Server ) in order for the deployment to notify all the Execution Units of the ruleset update through JMX. For example on WebSphere Application Server see Mapping the resAdministrators group to the Monitor role [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.config/config_ds_res_was8/tsk_was_map_admin_group.html]", "* Version mismatch between the Execution Unit(s) and the Management Console: in order for the Management Console to detect the presence of execution units the versions of these components must match down to the fix level. For example 7.1.1.4 Management Console would not interact properly with a 7.1.1.3 Execution Unit. The version of the RES console is displayed in the \"About\" link (top right corner). The version of the Execution Unit can be seen in the resource adapter ra.xml file where a resourceadapter-version tag shows the version. For example with the WebSphere Application Server this can seen through: Resources > Resource adapters > XU > Deployment Descriptor", "* Asynchronous ruleset parsing is used : in this mode, while an updated ruleset is being parsed, an earlier version of the ruleset can be used for executions that are requested at that time. Note that there is no guarantee of which specific earlier version of the ruleset may be used since it is a factor of which versions are available in the deprecated ruleset cache and whether garbage collection has occurred. In order to remove any uncertainty on the version that can be executed, it is possible to either turn off the asynchronous mode [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_config_asynchron_turnoff.html], or force synchronous parsing in asynchronous mode [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_config_forcing_sync_pars.html].", "* Notification scope is limited to one cell : by design the RES notification mechanism only works within one WebSphere Application Server Cell ( or one JBoss domain, or one Weblogic domain ), so a Management Console may only notify Execution Units that are running on servers in the same cell as the RES Console. See XU notification in a cluster over multiple cells [http://www-01.ibm.com/support/docview.wss?uid=swg21458245]. If you need to implement notifications to several cells at once, the document Ruleset updates and programmatic notification of RES eXecution Unit [http://www-01.ibm.com/support/docview.wss?uid=swg21418646] can be useful. \n * Parsing failure of an updated ruleset : leading the XU to fall back on an earlier active version that parses successfully", "* Ruleset update was only written to persistence: writing directly to RES persistence with the ant tasks res-write-db or res-write-file [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_deploy_rlapp_ant.html] does not trigger a notification, so the update may only been seen after server restart. \n * XU MBean is not activated in Java SE mode : See Activating the XU MBean in Java SE [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_config_xu_mbean_jse.html] \n * Multiple Java SE Execution Units are deployed in the same JVM: See Rule Execution Server J2SE mode hot deployment does not seem to work [http://www-01.ibm.com/support/docview.wss?uid=swg21585251]", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere ILOG JRules Modules:Execution Server (BRES / RES) Platform Independent 7.1.1, 7.1, 7.0.3, 7.0.2, 7.0.1, 7.0" ]

[ "Possible causes for unexpected versions to be executed are: \n- the RES client requesting execution may be passing a wrong ruleset path\n- a hot deploy notification was not sent by the RES console, or not received by all the Execution Units (XU)\n- the ruleset parsing policy may be delaying the use of a ruleset version until its parsing is complete\n- the updated ruleset cannot be parsed successfully and RES falls back on an earlier active version that parses" ]

[ 0 ]

[ "IBM Tivoli Composite Application Manager for Applications 721 FP2: Monitoring Agent for Sybase Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002) - United States Sybase Agent; OY; KOY; 5724B96SO; ITM; ITCAM DOWNLOADABLE FILES\n\nABSTRACT\n This fix resolves the APARs and defects and provides the enhancements listed \nin the \"Problems Fixed\" section below. \n\nDOWNLOAD DESCRIPTION\nCopyright International Business Machines Corporation 2018.\n\n\nAll rights reserved.\n\nComponent: IBM® Tivoli® Composite Application Manager for Applications 721 FP2: \nMonitoring Agent for Sybase® Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002)\n\nFix Pack: 0002\nComponent ID: 5724B96SO\nDate: December 8, 2017\n\nTable of contents:\n\n1.0 General description\n2.0 Problems fixed\n3.0 Architecture and prerequisites\n4.0 Image directory contents\n5.0 Installation instructions\n6.0 Additional installation information\n7.0 Known problems and workarounds\n8.0 Additional product information\n9.0 Copyright and trademark information\n10.0 Notices", "1.0 General description\n=======================\nThis fix contains the APARs and defects that are specified in the \"Problems \nfixed\" section. \n\n2.0 Problems fixed\n==================\nThe following problems are addressed by this fix.\n\n2.1 APARs \n----------\nAPAR :IV95149 \nAbstract :While installing Sybase agent \"find / -name ASE-*\" command takes too \nlong on system containing large disk and high volume mounts\nAdditional Information: While installing Sybase agent, prereqchecker invokes the SybaseVersion_plug.sh \nscript which executes the \"find\" command from root for finding Sybase server version.The \"find /\" command takes\na long time on systems with large disks, high volume of mounts.", "2.2 Enhancements \n----------------\nRFE :86384 \nAbstract :Monitor availability of the Sybase backup Server, Job Server and \ndatabase job failures. \nAdditional Information: To monitor sybase backup server and job server status two new attributes were \nadded in existing attribute group Server Details.And to monitor failed job in database \ntwo new attribute groups Job Details and Job Summary were added.\n\n\n3.0 Architecture and prerequisites\n===================================\nThis fix is supported on all operating systems listed in Compatibility report website.\nFor information about system requirements, go to the software product\ncompatibility reports website, and search for the ITCAM for Applications\nproduct:\n(http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]).", "3.1 Prerequisites for this fix\n-------------------------------\nThe minimum required version of IBM Tivoli Monitoring is V6.2.2 FP2\n\n\n4.0 Image directory contents\n==============================\nElectronic Part Number: ITCAM Apps Ag for Sybase CNN25ML\n\nThe following folder structure of the image is created:\n\n1. Sybase Agent Installer\n-WINDOWS folder: \nThis folder contains the binary files for installing the 32-bit agent.\nThe folder also contains the Prereqchecker utility in the prereqchecker folder\nfor the Sybase agent.\n\n- unix folder:\nThis folder contains the binary files for installing the 32-bit agent on Unix\nplatform. The folder also contains the Prereqchecker utility in the\nprereqchecker folder for the Sybase agent.\n\nThis fix image contains the following files and directories:\nAUTORUN.INF \n[Deploy] \nDeployLnk.sh\nREADME.TXT \n[unix] \nnotices\n[WINDOWS] \ninstall.sh \nkcirunas.cfg\n[license] \nsilent_install.txt \nsilent_config.txt", "2. Sybase Support Installer\n-WINDOWS folder: \nThis folder contains the Windows agent support files for the Tivoli Enterprise\nMonitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Desktop\nclient, and Tivoli Enterprise Browser client.\n\n- Unix folder:\nThis folder contains the non-Windows agent support files for the Tivoli\nEnterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli\nEnterprise Desktop client, and Tivoli Enterprise Browser client.\n\nThis fix image contains the following files and directories:\nAUTORUN.INF \nDeployLnk.sh \n[WINDOWS] \nREADME.TXT \n[unix] \nnotices\ninstall.sh \nkcirunas.cfg \ntmv630fp6-d5334a-201511302339.appsall.tar\n[license] \nsilent_install.txt \nsilent_config.txt\n\nNote: \nIf you are working in a UNIX environment, use install.sh file to install. \nIf you are working in a Windows environment, you can choose setup.exe \nunder directory [WINDOWS] or [WIA64] according your Windows platform.", "5.0 Installation instructions\n=============================\n\nWhen this fix pack image is downloaded from the IBM Software Support Web site, \nthese rules apply:\n* You can locally install the fix pack only on a system that already hosts a \nlicensed copy of IBM Tivoli Monitoring for Databases. Similar to other \nupgrade software, the fix pack image also can be locally installed on a \ncomputer where the product software is not already installed.\n* You can populate agents to the depot.\n* You can remotely deploy agents to existing or new installations.", "When this fix pack image is downloaded from Passport Advantage, these rules \napply:\n* You can locally install the fix pack on a system that already hosts a \nlicensed copy of IBM Tivoli Monitoring for Databases.\n* You can locally install the fix pack on a system that does not already host \na licensed copy of IBM Tivoli Monitoring for Databases.\n* You can populate agents to the depot.\n* You can remotely deploy agents to existing or new installations.\n\n\n5.1 Before installing the fix\n-----------------------------\n- The prerequisites listed under section 3.1 entitled 'Upgrade prerequisites \nfor this fix' must be installed when for upgrade.\n\n- For the purpose of this README, the symbol <CANDLEHOME> is the \nIBM Tivoli Monitoring installation directory. The default value\nfor CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\\ibm\\itm'\non Windows systems.", "- If you have customized the Monitoring Agent for Sybase Agent \noy.ini file on UNIX system, this file should be backed up before the fix \ninstall. After this fix is installed, edit the latest oy.ini file and merge \nyour modifications into this oy.ini file.\n\n\n5.2 Local agent install and update (including silent installation)\n--------------------------------------------------------------\n1. Transfer the appropriate archive file (CNN25ML.tar.gz or .iso) to a temporary \ndirectory on the system that contains the agent code to be updated. \nFor the purpose of this README, the symbol <TEMP> represents the fully \nqualified path to this directory.\nNote: On Windows, this includes the drive letter. \n\n2. Expand the archive file using the tar command on UNIX systems or \nan unzip utility on Windows systems. This creates a directory \nstructure that contains fixes for all of the supported platforms.", "3. Use the procedures in the \"ITCAM for Applications, Version 7.2.1.2 \nInstallation and Setup Guide\" to install the agent.\n\n4. Use the procedures in the specific database monitoring agent user's\nguide to complete the installation and configuration.\n\n5. After agent upgrade bitness of agent binary should be same as pre-upgrade on x86-64 \nbit windows. Agent do not support upgrade to 64 bit binary.\n\n\n5.3 Remote agent update and installation\n----------------------------------------\n1. Transfer the appropriate archive file (CNN25ML.tar.gz or .iso) to \na temporary directory on the IBM Tivoli Enterprise \nMonitoring Server system. For the purpose of this README, the \nsymbol <TEMP> represents the fully qualified path to this directory.\nNote: On Windows, this includes the drive letter. \n\n2. Expand the archive file using the tar command on UNIX systems or an \nunzip utility on Windows systems. This creates a directory structure\nthat contains fixes for all of the supported operating systems.", "3. To add the fix pack bundles into the remote deploy depot, use the\ntacmd addBundles command found in $CANDLEHOME/bin on UNIX systems\nor in %CANDLE_HOME%\\bin on Windows systems. For more information\non the tacmd addBundles command, see Appendix A. Commands reference\nof the \"IBM Tivoli Monitoring Administrator's Guide.\"\n\nOn a UNIX system: if the fix was expanded to \n<TEMP>/CNN25ML:\n> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CNN25ML/WINDOWS/Deploy -t oy -f\n> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CNN25ML/unix -t oy -f \n\nwhere:\n-i is the directory that contains the deployment bundles to be\nadded to the depot.\n-t is the product code of the product to add, in this case or \nrepresents the Monitoring Agent for Sybase Agent\n-f performs the actions without asking for confirmation", "On a Windows system: if the fix was expanded to \n<TEMP>/CNN25ML:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i <TEMP>\\CNN25ML\\WINDOWS\\Deploy -t oy -f\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i <TEMP>\\CNN25ML\\unix -t oy -f \n\nwhere:\n-i is the directory that contains the deployment bundles to be\nadded to the depot. \n-t is the product code of the product to add, in this case oy \nrepresents the Monitoring Agent for Sybase Agent\n-f performs the actions without asking for confirmation\n\n5. To log in to the Tivoli Enterprise Monitoring server, and deploy\nthe fix to the appropriate nodes where the agent is running, use\nthe following tacmd commands. For more information on the\ntacmd login and updateAgent commands, see Appendix A. Commands\nreference of the \"IBM Tivoli Monitoring Administrator's Guide.\"\n\nOn a UNIX system: \n> $CANDLEHOME/bin/tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> $CANDLEHOME/bin/tacmd listSystems", "The output shows the managed system name for the OS agent on the \nremote system to be updated. Use this value as the target of the\ntacmd updateAgent command. \n\n> $CANDLEHOME/bin/tacmd updateAgent -t oy \n-n <Managed system name>\n-v 062002000\n\nOn a Windows system:\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> %CANDLE_HOME%/bin/tacmd listSystems\n\nThe output shows the managed system name for the OS agent on the \nremote system to be updated. Use this value as the target of the\ntacmd updateAgent command. \n\n> %CANDLE_HOME%\\bin\\tacmd updateAgent -t OY \n-n <Managed system name>\n-v 062002000\n\nIf there are not prior version koy agent on remote system .Then use \nbelow tacmd addSystem command.\n\n> %CANDLE_HOME%\\bin\\tacmd addSystem -t OY \n-n <Managed system name> \n-p INSTANCE=\"<Sybase instance name>\"", "Note:\n- The <Sybase instance name> is the Sybase agent instance name to be monitored on \nremote system.\n- The component (-t) for the updateAgent command is specified as \ntwo characters (oy), not three characters (koy).\n- The node (-n) for the updateAgent command is the managed system\nname of the operating system (OS) agent to be updated. The \ntarget node for an updateAgent command is always an OS agent.\n-Remote installation will fail if the MTEMS window is open on the agent machine.\n\n5.4 Agent support update\n------------------------\nUse the following steps to update the Tivoli Enterprise Monitoring \nServer, Tivoli Enterprise Portal Server, or Tivoli Enterprise Portal\nDesktop:\n\n1. Transfer the appropriate archive file (CNN25ML.tar.gz or .iso) to \nthe IBM Tivoli Enterprise Monitoring Servers, IBM Tivoli\nEnterprise Portal Servers or Tivoli Enterprise Portal desktops. \n\n2. Expand the archive file using the tar command on UNIX systems or an \nunzip utility on Windows systems.", "3. Use the procedures in the \"ITCAM for Applications, Version 7.2.1.2\nInstallation and Setup Guide.\"\n\n4. Use the procedures in the specific database monitoring agent user's\nguide to complete the installation and configuration.\n\n5. If the Tivoli Enterprise Monitoring Server being updated is remote (not a \nHub Tivoli Enterprise Monitoring Server) then restart the Tivoli Enterprise \nMonitoring Server.\n\n\n\n6.0 Additional installation information\n=======================================\n6.1 Verifying the update\n-------------------------\n1.To verify whether the agent is updated correctly, use the tacmd command to\nview the current version of the agent after the agent is restarted. Ensure that\nyou log on to the Tivoli Enterprise Monitoring Server before you view the agent\nversion.\nFor example,\n\nOn UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring installation\ndirectory, the default location is /opt/IBM/ITM.", "> $CANDLEHOME/bin/tacmd login -s <server>\n-u <itmuser> \n-p <password>\n> $CANDLEHOME/bin/tacmd listSystems -t OY\n\nOn Windows systems, where %CANDLE_HOME% is the IBM Tivoli Monitoring\ninstallation directory, the default location is C:\\IBM\\ITM.\n\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n> %CANDLE_HOME%\\bin\\tacmd listSystems -t OY\n\nNote:\nThe component (-t) for the tacmd listSystems command is specified as two\ncharacters (OY), not three characters (KOY).\n\nWhen the agent is updated, the agent version is changed to 06.20.02.00.\nAfter the agent is restarted, you can also use the GUI to verify whether the\nagent was updated. For the agent on Windows systems, the version number is\n06.20.02.00.\n\n2.To verify whether the agent support files are updated correctly, use the\nkincinfo command on Windows systems or the cinfo command on Linux or UNIX\nsystems.", "On UNIX or Linux systems:\nTo validate that all components have been installed, run the following command:\n$CANDLEHOME/bin/cinfo -i\n\nSample output for the cinfo command on a UNIX or Linux systems\n----------------------------------------------------------\n[root@HJS-SYB-1 bin]# ./cinfo\n\n*********** Wed Nov 29 23:53:13 IST 2017 ******************\nUser: root Groups: root\nHost name : HJS-SYB-1 Installer Lvl:06.30.06.00\nCandleHome: /opt/IBM0611/ITM\n***********************************************************\n\n-- CINFO Menu --\n1) Show products installed in this CandleHome\n2) Show which products are currently running\n3) Show configuration settings\n4) Exit CINFO\n1\n\n*********** Wed Nov 29 23:53:15 IST 2017 ******************\nUser: root Groups: root\nHost name : HJS-SYB-1 Installer Lvl:06.30.06.00\nCandleHome: /opt/IBM0611/ITM\n***********************************************************\n...Product inventory\n\nax IBM Tivoli Monitoring Shared Libraries\nlx8266 Version: 06.30.06.00", "gs IBM GSKit Security Interface\nlx8266 Version: 08.00.50.36\n\njr Tivoli Enterprise-supplied JRE\nlx8266 Version: 07.09.01.00\n\noy Monitoring Agent for Sybase server\nlx8266 Version: 06.20.02.00\n\nui Tivoli Enterprise Services User Interface\n\nOn Windows systems:\nTo validate that all components have been installed, run the following command:\n%CANDLE_HOME%\\bin\\kincinfo –i\n\nSample output of the kincinfo command on a Windows System\n----------------------------------------------------------\nC:\\IBM\\ITM\\BIN>kincinfo -i\n********** Thursday, November 30, 2017 10:10:02 AM **********\nUser : Administrator Group : NA\nHost Name : HJ-IBMIBM6737 Installer : Ver: 063006000\nCandleHome : C:\\IBM\\ITM\nInstallitm : C:\\IBM\\ITM\\InstallITM\n*************************************************************\n...Product Inventory\n\nIN Install INS/Windows Install Component\nWINNT Version: 06.30.06.00 Build: 201511302132\n\nIN TEMA(32-bit) INS/ITM 6.x Agent Install Component\nWINNT Version: 06.30.06.00 Build: 201511302132", "IN TEMA(64-bit) INS/ITM 6.x Agent Install Component Extensions\nWINNT Version: 06.30.06.00 Build: 201511302132\n\nAC KAC(64-bit) CMA/32/64 Bit Agent Compatibility Package\nWIX64 Version: 06.30.06.00 Build: 201511302132\n\nGL KGL(64-bit) CMA/Tivoli Enterprise Monitoring Agent Framework\nWIX64 Version: 06.30.06.00 Build: d5334a\n\nGL KGL(32-bit) CMA/Tivoli Enterprise Monitoring Agent Framework\nWINNT Version: 06.30.06.00 Build: d5334a\n\nGS KGS(64-bit) GSK/IBM GSKit Security Interface\nWIX64 Version: 08.00.50.36 Build: d5313a\n\nGS KGS(32-bit) GSK/IBM GSKit Security Interface\nWINNT Version: 08.00.50.36 Build: d5313a\n\nJM KJM(32-bit) JVM/Embedded JVM\nWINNT Version: 07.09.01.00 Build: 201506221629\n\nNT KNT(32-bit) CMA/Monitoring Agent for Windows OS\nWINNT Version: 06.30.00.00 Build: 30321\n\nOY KOY(32-bit) CMA/Monitoring Agent for Sybase Server\nWINNT Version: 06.20.02.00 Build: 72651\n\nUE KUE(32-bit) CMA/Tivoli Enterprise Services User Interface Extensions\nWINNT Version: 06.30.06.00 Build: d5334a", "UI KUI(32-bit) CLI/Tivoli Enterprise Services User Interface\nWINNT Version: 06.30.06.00 Build: 201511302132\n\n\n7.0 Known problems and workarounds\n==================================\nProblem: Sybase agent configuration is not working using itmcmd manage \ncommand from GUI on Solaris 11\nWorkaround:\nFor Solaris 11:\nRun './itmcmd config -A oy' present at location:<CandleHome>/bin\n\nProblem: Prereqchecker which is integrated with the installer fails on \nwindows platform.\nWorkaround: \nFor Windows:\nRun on command prompt ‘prereq_checker.bat KOY’ present at location:\nInstallerPath\\Sybase_Agent_Installer\\WINDOWS\\prereqchecker\n\nFor Unix:\nRun ‘./prereq_checker.sh KOY’ present at location:\nInstallerPath\\Sybase_Agent_Installer\\unix\\prereqchecker\n\nProblem: Registry entries are not cleared when agent is uninstalled on 64 bit\nwindows platform.\nWorkaround: Delete registry entries manually from path:\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Candle\\KOY\\610\\", "Problem: When running the verification step in the \"itmcmd config -A oy\"\nfunction on a Solaris 10 system, the following output from the verification\nprogram is produced: \"user needs read authority to\".\nWorkaround: Issue \"ps -ef | grep koyagent\" to locate the koyagent process and\nissue \"kill -9\" for that process. Check the Navigator tree in the Tivoli\nEnterprise Portal for an offline koyagent entry and clear the offline entry.\nThe Monitoring Agent for Sybase Server that was configured by \"itmcmd config\" \nis unaffected by this problem. \n\nProblem: When running multiple remote deploys and agent upgrades, a task\ntimeout occurs during either the remote deployment or the agent upgrade. \nWorkaround: Restart the OS Agent following the task timeout and before\nperforming the next remote deployment or agent upgrade.", "Problem: If you are installing this fix into a depot on a Windows computer, and\nWinZip(R) is used to extract this fix, text files in the depot might contain\nCTRL-Ms. When this fix is remotely deployed to a UNIX machine from the Tivoli\nEnterprise Monitoring Server or depot on Windows, the installation fails. The\nCTRL-Ms are caused by extracting the fix using WinZip with \"TAR file smart\nCR/LF conversion\" option enabled. This extraction causes WinZip to put CTRL-Ms\nin text files when they are extracted on UNIX through remote deployment. \nWorkaround: If you are using WinZip for the fix installation for the Tivoli\nEnterprise Monitoring Server on Windows, disable the default \"TAR file smart\nCR/LF conversion\" option. \n\nProblem: In the Tivoli Enterprise Portal, the instance name is displayed\ninstead of the host name in the Navigation tree. \nFor example the Navigation tree might look like this,\nMySid\nSybase\nAlert Log\n...\ninstead of this,\nMyHost\nSybase - MySid\nAlert Log\n...", "The problem is that the length of the managed node name, <SID>:<HOSTNAME>:SYB,\nexceeds the length supported by the portal. A possible cause is that the\nfully-qualified host name is being used. If 'uname -n' on the Monitoring Agent\nfor Sybase Server computer returns a fully-qualified host name, then this host\nname is the cause. \nWorkaround: Override the host name with an appropriate shorter name by adding\nthe following line to oy.config: \nexport COLL_HOSTNAME=<short name>\n\n\n8.0 Additional product information \n==================================\nSteps for enabling SDA (Self-describing agent)\nFor Windows:\n1.On the computer where the monitoring server is installed, in the Manage\nTivoli Enterprise Monitoring Services application, right-click the agent and \nselect Advanced→ Edit ENV file.\n2.Edit the existing environment variable to: TEMA_SDA=Y.", "For UNIX:\n1.On the computer where the monitoring agent is installed, change to the\n<Install_dir>/config/ directory.\n2.Open the coordinating file:\nFor single-instance agents: <pc>.ini \nFor multi-instance agents: <pc>_<instance>.ini file \nWhere pc is the two-character product code.\n3.Edit the existing environment variable to: TEMA_SDA=Y.", "9.0 Copyright and trademark information \n========================================\nIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of\nInternational Business Machines Corp., registered in many jurisdictions\nworldwide. Other product and service names might be trademarks of IBM or other\ncompanies. A current list of IBM trademarks is available on the Web at\n\"Copyright and trademark information\" at ww.ibm.com/legal/copytrade.shtml.\nMicrosoft, Windows, Windows NT, and the Windows logo are trademarks of\nMicrosoft Corporation in the United States, other countries, or both. Java and\nall Java-based trademarks are trademarks of Sun Microsystems, Inc. in the\nUnited States, other countries, or both. UNIX is a registered trademark of The\nOpen Group in the United States and other countries. Linux is a registered\ntrademark of Linus Torvalds in the United States, other countries, or both.\nOther company, product, or service names may be trademarks or service marks of \nothers.", "10.0 Notices\n==================\nThis information was developed for products and services offered in the United\nStates. IBM may not offer the products, services, or features discussed in this\ndocument in other countries. Consult your local IBM representative for\ninformation on the products and services currently available in your area. Any\nreference to an IBM product, program, or service is not intended to state or\nimply that only that IBM product, program, or service may be used. Any\nfunctionally equivalent product, program, or service that does not infringe any\nIBM intellectual property right may be used instead. However, it is the user's\nresponsibility to evaluate and verify the operation of any non-IBM product,\nprogram, or service.\nIBM may have patents or pending patent applications covering subject matter\ndescribed in this document. The furnishing of this document does not grant you\nany license to these patents. You can send license inquiries, in writing, to:", "IBM Director of Licensing\nIBM Corporation\nNorth Castle Drive\nArmonk, NY 10504-1785\nU.S.A.\nThe following paragraph does not apply to the United Kingdom or any other\ncountry where such provisions are inconsistent with local law:\nINTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION \"AS IS\"\nWITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT\nLIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR\nFITNESS FOR A PARTICULAR PURPOSE.\nSome states do not allow disclaimer of express or implied warranties in certain\ntransactions, therefore, this statement may not apply to you.", "INSTALLATION INSTRUCTIONS\nSybase Server Agent 620 FP2 installer can be downloaded from IBM passport advantage using part number CNN25ML.\n\n\nURL LANGUAGE SIZE(Bytes) 6.2.0-TIV-ITM_SYB-FP0002 (CNN25ML) [https://w3-03.ibm.com/software/xl/download/ticket.wss] English 1722240862 \nDOWNLOAD PACKAGE\nSybase Server Agent 620 FP2 installer can be downloaded from IBM passport advantage using part number CNN25ML.\n\nIBM Tivoli Composite Application Manager for Applications 721 FP2: \nMonitoring Agent for Sybase Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002) (CNN25ML) \n\n\n\nPRODUCT ALIAS/SYNONYM\n OY\nKOY\nSybase Agent \n\n [/support/docview.wss?uid=swg24044440&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24044440&aid=2]Problems (APARS) fixed\nIV95149" ]

[ "Component: IBM® Tivoli® Composite Application Manager for Applications 721 FP2: \nMonitoring Agent for Sybase® Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002)\n\nFix Pack: 0002\nComponent ID: 5724B96SO\nDate: December 8, 2017" ]

[ 0 ]

[ "IBM Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server (CVE-2017-3735) - United States SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere MQ 5.3 and IBM MQ 8 for HPE NonStop have addressed a vulnerability in which OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate", "VULNERABILITY DETAILS\nCVEID: CVE-2017-3735 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3735]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate. An attacker could exploit this vulnerability to trigger an out-of-bounds read, resulting in an incorrect text display of the certificate.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/131047 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131047] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nAll versions of WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server\n\nREMEDIATION/FIXES\nFor MQ 5.3", "* \n * \n * \n * \n * \n * \n * \n * \n * \n * https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=5.3.1.14&platform=HP+NonStop&function=all\n * \n\nFor MQ 8 \n * \n\n * \n * here\n * \n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]", "*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." ]

[ "CVEID: CVE-2017-3735 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3735]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate. An attacker could exploit this vulnerability to trigger an out-of-bounds read, resulting in an incorrect text display of the certificate.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/131047 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131047] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N)" ]

[ 1 ]

[ "IBM Content Collector V4.0.1 Fix Pack 3 - United States DOWNLOADABLE FILES\n\nABSTRACT\n This document contains links to the download page for IBM Content Collector V4.0.1 Fix Pack 3 \n\nDOWNLOAD DESCRIPTION\n \n\nIBM CONTENT COLLECTOR DOWNLOADS\n * All versions [http://www.ibm.com/support/docview.wss?uid=swg27040223] \n * Version 4.0.1 Fix Pack 3- selected tab, \n\n\nApply IBM Content Collector V4.0.1 Fix Pack 3 to upgrade from IBM Content Collector V4.0.1 to IBM Content Collector V4.0.1.3. \n\nBelow is the list of the problems that were fixed in this fix pack.", "APAR Number APAR Abstract HE12445 [http://www.ibm.com/support/docview.wss?uid=swg1HE12445] ICC reporting \"SOLID Table Error 13011: Table GENERIC_DATA does not exist\" or \"Connection switch, some session context may be lost\" HE12488 [http://www.ibm.com/support/docview.wss?uid=swg1HE12488] SOME DOCUMENTS INTERMITTENTLY FAILED INDEXING WITH \"COULD NOT BE PROCESSED AS A REGULAR EMAIL\" ERROR. HE12491 [http://www.ibm.com/support/docview.wss?uid=swg1HE12491] IBM Content Collector cannot delete the entry from the Blacklist table in the solidDB HE12436 [http://www.ibm.com/support/docview.wss?uid=swg1HE12436] EXCEL FILES CANNOT BE INDEXED DUE TO 100% CPU CONSUMPTION task missing HE12490 [http://www.ibm.com/support/docview.wss?uid=swg1HE12490] Domino Template Enablement in IBM Content Collector setup tools causes an error when enable domino template. HE12513 [http://www.ibm.com/support/docview.wss?uid=swg1HE12513] TAG FILES REMAIN FOR ICC SOFTWARE COMPONENTS WHICH ARE NOT ACTUALLY INSTALLED.", "HE12526 [http://www.ibm.com/support/docview.wss?uid=swg1HE12526] EXPRESSION DOES NOT GET SAVED IN THE 'WS CALL WEB SERVICE' TASK HE12529 [http://www.ibm.com/support/docview.wss?uid=swg1HE12529] Mailbox randomly is skipped in the ICC cluster HE12537 [http://www.ibm.com/support/docview.wss?uid=swg1HE12537] CONTENT COLLECTOR INSTALLATION FAILS WITH ACCESS IS DENIED ERROR ON WASSERVICE.EXE FILE PREREQUISITES", "IBM Content Collector V4.0.1 Fix Pack 3 can be used with the following IBM Content Collector version:", "URL LANGUAGE SIZE(Bytes) Prerequisites for IBM Content Collector V4.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27042658] English 1 \nINSTALLATION INSTRUCTIONS\nRead the fix pack readme files for specific information about installing the fix pack packages.\n\nURL LANGUAGE SIZE(Bytes) 4.0.1.3-IBM-ICC-FP003 [https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=Enterprise%2BContent%2BManagement&product=ibm/Information+Management/Content+Collector&release=All&platform=All&function=fixId&fixids=4.0.1.3-IBM-ICC-FP003&includeRequisites=1&includeSup] English 1 \nDOWNLOAD PACKAGE\nThe IBM Content Collector V4.0.1 Fix Pack 3 download package consists of the following files:", "* 4.0.1.3-IBM-ICC-FP003.pdf: Readme file \n * 4.0.1.3-IBM-ICC-Server-FP003.zip \n * 4.0.1.3-IBM-ICC-OWA-FP003.zip \n * 4.0.1.3-IBM-ICC-P8CSS-AIX-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-P8CSS-Linux-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-P8CSS-SOLARIS-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-P8CSS-WIN-FP003.zip \n * 4.0.1.3-IBM-ICC-P8CSS-Linuxz-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-CM8Text-AIX-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-CM8Text-Linux-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-CM8Text-Solaris-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-CM8Text-WIN-FP003.zip \n * 4.0.1.3-IBM-ICC-CM8Text-Linuxz-FP003.tar.gz\n\nHOW CRITICAL IS THIS FIX?\nThis fix addresses vulnerabilities that are described in CVE-2016-0363 and CVE-2016-0376 which are disclosed as part of IBM Runtime Environment Java Technology Edition, Version 6 in April 2016. \n\nFor further information see the Readme File for IBM Content Collector V4.0.1 Fix Pack 3", "[/support/docview.wss?uid=swg24042387&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24042387&aid=2]Problems (APARS) fixed\nHE12445 HE12488 HE12491 HE12436 HE12490 HE12513 HE12526 HE12529 HE12537" ]

[ "Apply IBM Content Collector V4.0.1 Fix Pack 3 to upgrade from IBM Content Collector V4.0.1 to IBM Content Collector V4.0.1.3." ]

[ 0 ]

[ "IBM Security Network Protection firmware 5.3.1 release notes - United States release notes; readme; firmware; xgs FIX README\n\nABSTRACT\n IBM Security Network Protection Firmware Version 5.3.1 is a firmware update for the XGS NGIPS network protection platform. This release provides the following updates to IBM Security Network Protection Firmware Version 5.3.1. \n\nCONTENT\nServiceability and support enhancements:", "* You can now get additional information about your system through the command line within your \"Tools\" directory. We have added the Sysinfo command that will display system CPU, memory, and storage information in command line interface (CLI).\n Note: A complete list of CLI commands are located in the Command-line interface [http://www.ibm.com/support/knowledgecenter/SSHLHV_5.3.1/com.ibm.alps.doc/references/alps_command_line_interface.htm] section in the Knowledge Center.\n \n * New to this release we have added a services mode within CLI. These commands will allow you to restart key services within the appliance. These services are listed below: * Packet processing \n * Packet Capture \n * Local Management Interface (LMI) \n * License and Update (LUM) \n * SiteProtector Communication", "* You can now view and search logs from the command line using the \"less\" and \"tail\" commands from within logs mode. Log files found using the less command are System, Webserver, Updates and Analysis logs. \n \n * With the admin-sftp account you can now retrieve Snapshots, Packet Captures, and support files. This account uses the same password as the admin account. \n Note: More details on admin-sftp can be found in the Downloading files with an SFTP client [http://www.ibm.com/support/knowledgecenter/SSHLHV_5.3.1/com.ibm.alps.doc/tasks/alps_downloading_sftp.htm]documentation on the Knowledge Center. [http://www.ibm.com/support/knowledgecenter/SSHLHV_5.3.1/com.ibm.alps.doc/tasks/alps_downloading_sftp.htm]", "Response enhancement: * Forwarded events (Remote Syslog Alert Responses) will show the same details as the content sent to SiteProtector. \n * Support for using the TCP protocol when creating Remote Syslog Alert Responses to prevent messages being truncated and improve delivery reliability over using UDP.\n\n\nNetwork Access Policy enhancement: * You can now use the network access policy to control network access when the HTTP X-Forward-For (XFF) header is enabled. The network policy can use the XFF header along with the packet source to control network traffic.\n\n\nIPS Policy enhancements: * You can now derive a new IPS object from an existing IPS object by right-clicking on an IPS object and left-clicking on Clone.\n \n * When enabling network, transport-layer, and status events in a non-default IPS object, a warning message is shown. This will help to minimize what may be seen as a false negative.", "Performance: * Inspection throughput increase for XGS 7100 up to 25Gbps, FPL5 (25Gbps) added.\n\n\nMiscellaneous updates and implementation changes: * Top 10 URLs and URL categories widget in the Local Management Interface have been disabled by default. Given the limited popularity of this feature, coupled with the performance impact in certain situations, we disabled the feature by default. You can re-enable it by using the advanced parameter tune.url.topten.tracking=true. \n \n * We have removed the MultiCast Domain Name System (mDNS), under some configurations it caused security risks within the appliance.\n \n * Support for mutual certificate authentication for communication between the Network Security appliance and SiteProtector.\n\n\nKnown issues: \nYou can find a list of known issues for IBM Security Network Protection 5.3.1 in Technote 1715537: Known issues for IBM Security Network Protection version 5.3.1 [http://www.ibm.com/support/docview.wss?uid=swg21715537].", "[/support/docview.wss?uid=swg21902778&aid=1] [https://ibm.biz/BdHdZx] [/support/docview.wss?uid=swg21902778&aid=2] [http://ibm.biz/InfraSecForumTechnote] [/support/docview.wss?uid=swg21902778&aid=3] [http://ibm.biz/SecSuptUTube] [/support/docview.wss?uid=swg21902778&aid=4] [http://ibm.biz/InfraSecFixes] [/support/docview.wss?uid=swg21902778&aid=5] [http://ibm.biz/FlexLicLogin] [/support/docview.wss?uid=swg21902778&aid=6] [http://ibm.biz/MyNotification] [/support/docview.wss?uid=swg21902778&aid=7] [http://ibm.biz/ContactSecSupport] \nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21903740]" ]

[ "You can now derive a new IPS object from an existing IPS object by right-clicking on an IPS object and left-clicking on Clone." ]

[ 3 ]

[ "IBM Use\"isolate the resource provider\" to establish data source connections using a different JDBC driver from the same database vendor - United States isolate this resource provider TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Customer has defined 3 Oracle JDBC Providers at cell, node and server\nscope. Client have following configuration in websphere JDBC provider. \n\nIn Cell Scope - C:\\jdbc\\ojdbc5\\ojdbc5.jar \n\nIn Node Scope - C:\\jdbc\\ojdbc6_g\\ojdbc6_g.jar \n\nIn Server Scope- C:\\jdbc\\ojdbc6\\ojdbc6.jar \n\nIn this case value of JDBC driver path in WebSphere variable is identical. Nornally, If JDBC provider configure at server level then server level driver will get load first. But in this case since all three drivers are from same vendor, So we can not control which driver is picking up. In this case \n\"C:\\jdbc\\ojdbc6\\ojdbc6.jar\" should be loaded first but instated, ojdbc5.jar was load first\n\n[13. 4. 5 12:05:15:625 KST] 00000023 CompoundClass < loadClass \n\noracle.jdbc.driver.OracleDriver", "loader=com.ibm.ws.bootstrap.ExtClassLoader@5dc95dc9 \n\nsource=file:/C:/jdbc/ojdbc5/ojdbc5.jar Exit \n\n\n\n\n\n\nSYMPTOM\nDue to multiple JDBC drivers from the same vendor were configured in different scopes, the wrong driver class was loaded.\n\n\nCAUSE\nWhen multiple versions of the JDBC driver are configured in WebSphere Application Server, irrespective of the scopes, there is a possibility of a collision of the classes and we cannot predict from which version of the driver jar the class got loaded.", "RESOLVING THE PROBLEM\n In order to support the existence of multiple versions of the driver jars, the \"Isolate this resource provider\" configuration helps to ensure there are no conflicts. This needs to be configured on each JDBC Provider. You cannot isolate only one resource provider, all the provider configurations in different scopes will have to be configured with the \"Isolate this resource provider\" setting. In this scenario, the resource provider classes from different versions of the jars are not imported or accessed to verify if the isolation has indeed worked. In order to use the server-scoped resource provider the datasource using the server-scoped jdbc provider will have to be referenced from the application after isolating the resource providers and using a resource reference in the application.", "Go to the JDBC Provider and enable \"isolate the resource provider\". When \"Isolate this resource provider\" is enabled, it ensures that only the jar that was specified in the classpath will be used for all the datasources under that particular JDBC provider. \n\n \n\nHere are links to Knowledge Center articles which contain further information on the setting: \n\n\nJDBC provider settings [https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.0/com.ibm.websphere.nd.multiplatform.doc/ae/udat_manjdbcprodet.html]\n\nConsiderations for isolated resource providers [https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.0/com.ibm.websphere.nd.multiplatform.doc/ae/rdat_isolatedlimitations.html]" ]

[ "When multiple versions of the JDBC driver are configured in WebSphere Application Server, irrespective of the scopes, there is a possibility of a collision of the classes and we cannot predict from which version of the driver jar the class got loaded." ]

[ 1 ]

[ "IBM Security Bulletin: IBM MQ clients connecting to an MQ queue manager can cause a SIGSEGV in the amqrmppa channel process terminating it. (CVE-2018-1371) - United States SECURITY BULLETIN\n\nSUMMARY\n An IBM MQ client connecting to an MQ queue manager can cause a SIGSEGV in the queue manager's amqrmppa channel process, terminating it. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2018-1371 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1371]\nDESCRIPTION: An IBM MQ client connecting to an MQ queue manager can cause a SIGSEGV in the amqrmppa channel process terminating it.\nCVSS Base Score: 6.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/137771 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137771] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ V8.0 \n\n * Maintenance level 8.0.0.8\n\n\nIBM MQ V9 LTS * Maintenance level 9.0.0.2", "IBM MQ V9 CD * IBM MQ version 9.0.4\n\nREMEDIATION/FIXES\nIBM MQ V8.0 \n\nApply FixPack 8.0.0.9 [http://www-01.ibm.com/support/docview.wss?uid=swg22015103] \nIBM MQ V9 LTS * Apply FixPack 9.0.0.3 [http://www-01.ibm.com/support/docview.wss?uid=swg24044508]\n\n\nIBM MQ V9 CD * Upgrade to 9.0.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24043463]\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]", "CHANGE HISTORY\n 01 Feb 2018: Original Version published\n13 April 2018: Added 9.0.5, 9.0.0.3 and 8.0.0.9 FixPack details \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.", "Cross reference information Segment Product Component Platform Version Edition Business Integration IBM MQ Business Integration IBM MQ Advanced Business Integration IBM MQ Advanced for Developers" ]

[ "CVEID: CVE-2018-1371 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1371]\nDESCRIPTION: An IBM MQ client connecting to an MQ queue manager can cause a SIGSEGV in the amqrmppa channel process terminating it.\nCVSS Base Score: 6.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/137771 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137771] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)" ]

[ 0 ]

[ "IBM How to change Siebel connection settings using the siebel.properties file in WebSphere Adapter for Siebel eBusiness Applications - United States TECHNOTE (FAQ)\n\nQUESTION\n The Siebel connection of WebSphere Adapter for Siebel eBusiness Applications is established with the default settings. You may need to modify the connection settings, such as connection timeout, according to your product environment. \n\nANSWER\nSiebel adapter uses the Siebel API (Java Data Bean) to interact with the Siebel server. The Siebel API also provides a way to configure the connection settings on the client side.\nCreate a siebel.properties file and save it in the classpath of the adapter (For example, <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", "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. \n\nThe table below shows the properties in the siebel.properties file.", "[/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.", "A 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:", "Virtual Servers = an assigned list of real Siebel Servers with host names and port numbers (of the local SCB). Siebel Generated code for JCA/JDB properties siebel.connection.string Specifies the Siebel connection string. siebel.user.name Specifies the user name to be used for logging in to Object Manager. siebel.user.password Specifies the password to be used for logging in to Object Manager. siebel.user.language Specifies the user's preferred language. siebel.user.encrypted Specifies whether the username and password is encrypted. siebel.jdb.classname Specifies the default JDB classname Java System Properties file.encoding Indicates the code page on the client side. For example, cp1252, utf8, unicodeBig, cp942. NOTE: Java System Properties are System Properties, not Siebel Properties. \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", "siebel.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]" ]

[ "Siebel adapter uses the Siebel API (Java Data Bean) to interact with the Siebel server. The Siebel API also provides a way to configure the connection settings on the client side.\nCreate a siebel.properties file and save it in the classpath of the adapter (For example, <adapter project>\\connectorModule) and restart the adapter and broker to pick up the settings to establish the required connections." ]

[ 0 ]

[ "IBM Required gtk libraries for IBM Installation Manager on AIX - United States gtk; motif TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM Installation Manager requires gtk libraries to support the graphical user interface (GUI). \n\nSYMPTOM\nInstallation Manager reports errors when the gtk libraries are not installed. \n\nExamples of the reported errors:\n\n\n * SWT library could not be loaded:", "# ./install\n00:00.92 ERROR [main] org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory safeLogged\nCould not load SWT library. Reasons:\n/root/Desktop/InstallationManager/configuration/org.eclipse.osgi/bundles/633/1/.cp/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\nswt-pi-gtk (Not found in java.library.path)\n/root/.swt/lib/aix/ppc/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\n/root/.swt/lib/aix/ppc/libswt-pi-gtk.a (A file or directory in the path name does not exist.)\njava.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:\n/root/Desktop/InstallationManager/configuration/org.eclipse.osgi/bundles/633/1/.cp/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\nswt-pi-gtk (Not found in java.library.path)\n/root/.swt/lib/aix/ppc/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)", "/root/.swt/lib/aix/ppc/libswt-pi-gtk.a (A file or directory in the path name does not exist.)\njava.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:\n/root/Desktop/InstallationManager/configuration/org.eclipse.osgi/bundles/633/1/.cp/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\nswt-pi-gtk (Not found in java.library.path)\n/root/.swt/lib/aix/ppc/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\n/root/.swt/lib/aix/ppc/libswt-pi-gtk.a (A file or directory in the path name does not exist.)\nat org.eclipse.swt.internal.Library.loadLibrary(Library.java:331)\nat org.eclipse.swt.internal.Library.loadLibrary(Library.java:240)\nat org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:22)\nat java.lang.J9VMInternals.initializeImpl(Native Method)\n...\nThe displayed failed to initialize. See the log /root/Desktop/InstallationManager/configuration/1361168761043.log for details.", "* Segmentation error occurs when the gtk libraries are installed but are not at the required versions", "Unhandled exception\nType=Segmentation error vmState=0x00040000\nJ9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033\nHandler1=F0739208 Handler2=F05F5F1C\nR0=D3D9FDCC R1=3013EEF0 R2=F077B69C R3=F0779450\nR4=00000000 R5=00000000 R6=00000000 R7=00000000\nR8=1220000F R9=1220000F R10=F0687A0C R11=000034E0\nR12=03222C60 R13=30C7DD00 R14=31FAA028 R15=F05851EC\nR16=00000007 R17=00000000 R18=F073B388 R19=30C7DD50\nR20=32935C30 R21=31FAA040 R22=00000000 R23=30000BC8\nR24=10010E04 R25=F05F7130 R26=30148364 R27=0000007E\nR28=CFACCBB8 R29=F073AB7C R30=D3DC1410 R31=F0779430\nIAR=D3DB63A8 LR=D3D9FDE8 MSR=0000D032 CTR=D3DE0E70\nCR=22004084 FPSCR=82000000 XER=0000001B TID=00000000\nMQ=00000000\nFPR0 329d3fd000000110 (f: 272.000000, d: 6.943460e-65)\nFPR1 41e0000000000000 (f: 0.000000, d: 2.147484e+09)\nFPR2 c1e0000000000000 (f: 0.000000, d: -2.147484e+09)\nFPR3 4330000001e00000 (f: 31457280.000000, d: 4.503600e+15)\nFPR4 4330080000000000 (f: 0.000000, d: 4.512396e+15)", "FPR5 4133851800000000 (f: 0.000000, d: 1.279256e+06)\nFPR6 4133851800000000 (f: 0.000000, d: 1.279256e+06)\nFPR7 4330080000138518 (f: 1279256.000000, d: 4.512396e+15)\nFPR8 005f0031002e0034 (f: 3014708.000000, d: 6.897895e-307)\nFPR9 002e0038002e0076 (f: 3014774.000000, d: 8.344265e-308)\nFPR10 0032003000310033 (f: 3211315.000000, d: 1.001324e-307)\nFPR11 0030003200320035 (f: 3276853.000000, d: 8.900720e-308)\nFPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)\nFPR13 4028000000000000 (f: 0.000000, d: 1.200000e+01)\nFPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)", "FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nTarget=2_40_20110203_074623 (AIX 7.1)\nCPU=ppc (8 logical CPUs) (0xc0000000 RAM)\n----------- Stack Backtrace -----------\n(0xD3D9F81C)\n(0xD43D5E48)\n(0xD43D8698)\n(0xD43D1D38)\n(0xD43D1B24)\n(0xD3E4ABA0)\n(0xD43D3058)\n(0xD43D3200)\n(0xD0F0ED18)\n(0xD0F1536C)\n(0xD0F19438)\n(0xD2B1DF48)\n(0xD2AE7780)\n(0xD2AE7A30)\n(0xD1516BAC)\n(0xD2AE78E4)\n(0xD2AE7E24)\n(0xD2AEC6C4)\n(0x100013C0)\n(0xD04FCD88)\n---------------------------------------", "JVMDUMP006I Processing dump event \"gpf\", detail \"\" - please wait.\nJVMDUMP032I JVM requested System dump using '/opt/IBM/InstallationManager/eclipse/core.YYYY0318.095945.7798784.0001.dmp' in response to an event\nNote: \"Enable full CORE dump\" in smit is set to FALSE and as a result there will be limited threading information in core file.\nJVMDUMP010I System dump written to /opt/IBM/InstallationManager/eclipse/core.YYYY0318.095945.7798784.0001.dmp\nJVMDUMP032I JVM requested Java dump using '/opt/IBM/InstallationManager/eclipse/javacore.YYYY0318.095945.7798784.0002.txt' in response to an event\nJVMDUMP010I Java dump written to /opt/IBM/InstallationManager/eclipse/javacore.YYYY0318.095945.7798784.0002.txt\nJVMDUMP032I JVM requested Snap dump using '/opt/IBM/InstallationManager/eclipse/Snap.YYYY0318.095945.7798784.0003.trc' in response to an event\nJVMDUMP010I Snap dump written to /opt/IBM/InstallationManager/eclipse/Snap.YYYY0318.095945.7798784.0003.trc", "JVMDUMP013I Processed dump event \"gpf\", detail \"\".\nSegmentation fault (core dumped)", "CAUSE\nInstallation Manager is an Eclipse Rich Client Program application based on the open source project found at http://www.eclipse.org [http://www.eclipse.org]. Eclipse changed the window system requirement from motif to gtk on UNIX operating systems. For AIX, this Eclipse window system change requires the gtk libraries to be installed to support the GUI. For Installation Manager, the GUI is the wizard mode of operation. \n\nYou can use Installation Manager without the gtk libraries. For information on console mode, command-line mode, or silent mode; see the Installation Manager Information Center [http://pic.dhe.ibm.com/infocenter/install/v1r6/topic/com.ibm.cic.agent.ui.doc/topics/c_modes.html]. Silent mode uses a response file and command-line mode is supported by all packages. For console mode, check your product documentation to verify that the product supports console mode.\n\n\nRESOLVING THE PROBLEM\nTo use the GUI, the gtk+ RPM and dependencies must be available on AIX.", "Install this set of RPMs on AIX:\n\n\natk-1.12.3-2.aix5.2.ppc.rpm\ncairo-1.8.8-1.aix5.2.ppc.rpm\nexpat-2.0.1-1.aix5.2.ppc.rpm\nfontconfig-2.4.2-1.aix5.2.ppc.rpm\nfreetype2-2.3.9-1.aix5.2.ppc.rpm\ngettext-0.10.40-6.aix5.1.ppc.rpm\nglib2-2.12.4-2.aix5.2.ppc.rpm\ngtk2-2.10.6-4.aix5.2.ppc.rpm\nlibjpeg-6b-6.aix5.1.ppc.rpm\nlibpng-1.2.32-2.aix5.2.ppc.rpm\nlibtiff-3.8.2-1.aix5.2.ppc.rpm\npango-1.14.5-4.aix5.2.ppc.rpm\npixman-0.12.0-3.aix5.2.ppc.rpm\nxcursor-1.1.7-3.aix5.2.ppc.rpm\nxft-2.1.6-5.aix5.1.ppc.rpm\nxrender-0.9.1-3.aix5.2.ppc.rpm\nzlib-1.2.3-3.aix5.1.ppc.rpm\n\nThe installed RPMs must be of the minimum versions listed above.\n\nTo install the RPM versions specified above take the following steps:", "1. Download the gtk2_bundle_v2.tar package [ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/ezinstall/ppc/] (version 'v2') containing all the RPMs and the install script to a new directory. \n \n \n 2. Decompress the tar file. \n You can use the command tar -xvf gtk2_bundle_<version>.tar to decompress the file.\n \n \n 3. Open the decompressed directory gtk2_bundle_<version> and run the install.sh script.\n \n The script will check if the required RPMs are installed at the compatible level. If they are not, the script will prompt to install the compatible versions.\n \n \n 4. Verify the environment variable LIBPATH contains a path to the installed libraries. \n For example LIBPATH=/opt/freeware/lib/\n\n\nNote that if you download and install RPMs individually, we have found that the following libraries are incompatible: * glib2-2.14.6-2 and gtk2-2.10.6-5", "RELATED INFORMATION\n#Unreadable characters in the GUI when using X11 [http://www.ibm.com/support/docview.wss?uid=swg21661861]" ]

[ "To use the GUI, the gtk+ RPM and dependencies must be available on AIX. \n\n\nInstall this set of RPMs on AIX:" ]

[]

[ "IBM Security Bulletin: Multiple vulnerabilities in IBM® Java SDK affect WebSphere Application Server that ships with WebSphere Enterprise Service Bus (CVE-2015-2613, CVE-2015-2601, CVE-2015-4749, CVE-2015-2625, CVE-2015-1931) - United States SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition that is shipped with IBM WebSphere Application Server that ships with WebSphere Enterprise Service Bus. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2015-2613 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2613]\nDESCRIPTION:An unspecified vulnerability and Java SE Embedded related to the JCE component could allow a remote attacker to obtain sensitive information.\nCVSS Base Score: 5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104734 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104734]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)", "CVEID:CVE-2015-2601 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2601]\nDESCRIPTION:An unspecified vulnerability related to the JCE component could allow a remote attacker to obtain sensitive information.\nCVSS Base Score: 5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104733 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104733]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)\nCVEID:CVE-2015-4749 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4749]\nDESCRIPTION:An unspecified vulnerability related to the JNDI component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 4.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104740 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104740]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:N/A:P)", "CVEID:CVE-2015-2625 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2625]\nDESCRIPTION:An unspecified vulnerability related to the JSSE component could allow a remote attacker to obtain sensitive information.\nCVSS Base Score: 2.6\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104743 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104743]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:N/A:N)\n\nCVEID:CVE-2015-1931 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1931]\nDESCRIPTION:IBM Java Security Components store plain text data in memory dumps, which could allow a local attacker to obtain information to aid in further attacks against the system.\nCVSS Base Score: 2.1\nCVSS Temporal Score: Seehttp://xforce.iss.net/xforce/xfdb/102967 [http://xforce.iss.net/xforce/xfdb/102967]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:L/AC:L/Au:N/C:P/I:N/A:N)", "AFFECTED PRODUCTS AND VERSIONS\nWebSphere Enterprise Service Bus 6.2\nWebSphere Enterprise Service Bus 7.0\nWebSphere Enterprise Service Bus 7.5\n\nREMEDIATION/FIXES\nPlease consult the security bulletin Multiple vulnerabilities in IBM® Java SDK affect WebSphere Application Server July 2015 CPU [http://www-01.ibm.com/support/docview.wss?uid=swg21962931] for vulnerability details and information about fixes.\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] CHANGE HISTORY\n 4th September 2015: Original version published", "*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." ]

[ "CVEID:CVE-2015-2613 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2613]\nDESCRIPTION:An unspecified vulnerability and Java SE Embedded related to the JCE component could allow a remote attacker to obtain sensitive information.\nCVSS Base Score: 5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104734 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104734]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)" ]

[ 0 ]

[ "IBM Getting java.io.NotSerializableException when SessionObjectSize counter is enabled - United States java.io.NotSerializableException SessionObjectSize counter PMI enabled disable serializable TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When PMI (Performance Monitoring Infrastructure) is enabled with SessionObjectSize counter enabled, getting NotSerializableException. The SystemOut.log shows something similar to:", "[4/10/07 5:25:42:618 EDT] 00000091 SessionContex E Exception is: java.io.NotSerializableException: com.com1.dept.nls.model.someModel \nat java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java(Compiled Code)) \n... \nat java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java(CompiledCode)) \nat com.ibm.ws.webcontainer.httpsession.SessionContextMBeanAdapter.getSessionsInfo(SessionContextMBeanAdapter.java(Compiled Code)) \nat com.ibm.ws.webcontainer.httpsession.SessionTrackingPMIApplicationData$1.getRuntimeInfo(SessionTrackingPMIApplicationData.java(Inlined Compiled Code)) ... \nat com.ibm.ws.pmi.server.modules.ServletSessionsModule$SessionObjSize.updateStatistic(ServletSessionsModule.java(Compiled Code)) \nat com.ibm.ws.pmi.server.data.SpdStatExternal.updateExternal(SpdStatExternal.java(Compiled Code)) \nat com.ibm.websphere.pmi.server.PmiAbstractModule.update(PmiAbstractModule.java(Compiled Code)) \n...", "The error does not affect application functionality. Disabling SessionObjectSize counter makes the error stop occurring. \n\nCAUSE\nWebSphere® Application Server Session Manager throws NotSerializableException when it tries to serialize non-serializable SessionData from the application before sending it to PMI.\n\nRESOLVING THE PROBLEM\nThe application needs to ensure there is no session object that is not serializable. The object needs to implement java™.io.Serializable interface.\n\n \n\nHISTORICAL NUMBER\n 53925\nL6Q\n000" ]

[ "WebSphere® Application Server Session Manager throws NotSerializableException when it tries to serialize non-serializable SessionData from the application before sending it to PMI.\n\nRESOLVING THE PROBLEM\nThe application needs to ensure there is no session object that is not serializable. The object needs to implement java™.io.Serializable interface." ]

[ 2 ]

[ "IBM Security Bulletin: WebSphere Message Broker and IBM Integration Bus are affected by Open Source Tomcat vulnerability (CVE-2016-3092) - United States WMB IIB SECURITY BULLETIN\n\nSUMMARY\n WebSphere Message Broker and IBM Integration Bus are affected by Open Source Apache Tomcat vulnerability. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-3092 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092]\nDESCRIPTION: Apache Tomcat is vulnerable to a denial of service, caused by an error in the Apache Commons FileUpload component. By sending file upload requests, an attacker could exploit this vulnerability to cause the server to become unresponsive.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/114336 [https://exchange.xforce.ibmcloud.com/vulnerabilities/114336] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)", "AFFECTED PRODUCTS AND VERSIONS\n IBM Integration Bus V10.0 & V9.0 \n\nWebSphere Message Broker V8.0 \n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus V10\nIT15719 An interim fix is available from IBM Fix Central for all platforms.\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719]", "The APAR is targeted to be available in fix pack 10.0.0.7 IBM Integration Bus V9\nIT15719 An interim fix is available from IBM Fix Central for all platforms.\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719]", "The APAR is targeted to be available in fix pack 9.0.0.7 WebSphere Message Broker\nV8\nIT15719 An interim fix is available from IBM Fix Central for all platforms.\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibms~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT15719 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibms~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT15719]\n\nThe APAR is targeted to be available in fix pack 8.0.0.8 \nFor unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product. \n\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : \nhttp://www.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n\nWORKAROUNDS AND MITIGATIONS\nNone known", "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.", "REFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT\nNone \n\nCHANGE HISTORY\n 27 Oct 2016 - Original version Published\n\n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.", "DISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker AIX, HP-UX, Linux, Solaris, Windows 8.0 \nPRODUCT ALIAS/SYNONYM\n WMB IIB" ]

[ "CVEID: CVE-2016-3092 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092]\nDESCRIPTION: Apache Tomcat is vulnerable to a denial of service, caused by an error in the Apache Commons FileUpload component. By sending file upload requests, an attacker could exploit this vulnerability to cause the server to become unresponsive.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/114336 [https://exchange.xforce.ibmcloud.com/vulnerabilities/114336] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)" ]

[ 0 ]

[ "IBM Too Many Open Files error message - United States wasrun; wasjdk; open; files; too; ProblemDeterminationDocument; JCC was appserver app server TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote explains how to debug the \"Too many open files\" error message on Microsoft Windows, AIX, Linux and Solaris operating systems. \n\nSYMPTOM\nThe following messages could be displayed when the process has exhausted the file handle limit: \n\njava.io.IOException: Too many open files\n\n[3/14/15 9:26:53:589 EDT] 14142136 prefs W Could not lock User prefs. Unix error code 24.\n\nNew sockets/file descriptors can not be opened after the limit has been reached. \n\n\nCAUSE\nSystem configuration limitation.", "When the \"Too Many Open Files\" error message is written to the logs, it indicates that all available file handles for the process have been used (this includes sockets as well). In a majority of cases, this is the result of file handles being leaked by some part of the application. This technote explains how to collect output that identifies what file handles are in use at the time of the error condition.\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", "Please 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.", "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). 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..", "lsof \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)", "INODES 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.", "Alternately you can list the contents of the file descriptors as a list of symbolic links in the following directory, where you replace PID with the process ID. This is especially useful if you don't have access to the lsof command: \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", "This will get one round of lsof output. If you want to determine if the number of open files is growing over time, you can issue the command with the -r option to capture multiple intervals: \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" ]

[ "On UNIX and Linux operating systems, the ulimit for the number of file handles can be configured, and it is usually set too low by default. Increasing this ulimit to 8000 is usually sufficient for normal runtime, but this depends on your applications and your file/socket usage. Additionally, file descriptor leaks can still occur even with a high value. \n\nDisplay the current soft limit:\nulimit -Sn\n\nDisplay the current hard limit:\nulimit -Hn\n\nOr capture a Javacore, the limit will be listed in that file under the name NOFILE:\nkill -3 PID" ]

[ 1 ]

[ "IBM Important Information about the WebSphere MQ Configuration Agent, Withdrawn from IBM OMEGAMON for Messaging on z/OS V7.5 - United States PRODUCT DOCUMENTATION\n\nABSTRACT\n Starting with V7.5, IBM OMEGAMON for Messaging on z/OS no longer delivers the component called WebSphere MQ Configuration Agent, referred to as MQ Configuration in the rest of this document, because there are other recommended ways to configure IBM MQ. It is stabilized in the previous V7.3 release, but MQ Configuration will be supported as long as V7.3 is in support. The components in V7.5 are the IBM MQ Monitoring Agent and the IBM Integration Bus Monitoring Agent, both of which have enhancements in V7.5 that address monitoring requirements you may have. You can upgrade your OMEGAMON for Messaging monitoring components to V7.5 while using the previous release of MQ Configuration.", "Whether or not you want to continue using MQ Configuration when you install and configure OMEGAMON for Messaging V7.5, there may be steps you need to take, so please review this document prior to installing and configuring V7.5. \n\nCONTENT\nFirst, please determine whether you have previously installed and configured the MQ Configuration component. If you have not done so previously, there is no need for you to consider the rest of this document. For this determination, please examine the following:", "· SMP/E: Are the FMIDs for MQ Configuration installed? The FMIDs are HKMC730 and HKCF730, or HKMC710 and HKCF710 if you are using the V7.1 level. \n· PARMGEN: In your PARMGEN configuration for each runtime environment, does the “Include Products in this PARMGEN RTE panel (KCIP@PGI)” (under step “1 KCIJPCFG Set-up/Refresh PARMGEN work environment” navigation from the PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU), have the line for “KMC OMEGAMON for Messaging – WebSphere MQ Configuration” selected for configuration in the environment? \n\nIf the answers are “yes” to both of the above questions, then you do need to continue with the following general steps, which are documented in detail below:", "1) Determine whether there are any users of MQ Configuration in your environment. There are many cases in which the MQ Configuration component is installed and configured in PARMGEN, but no one is actually using it. It is important to determine this in order to decide which step to take next.\n\n2) If you do not have users of MQ Configuration, or you want to remove it anyway, there may be steps required when you are installing and configuring OMEGAMON for Messaging V7.5 especially if you previously configured a shared agent address space for MQ monitoring (KMQ) and MQ configuration (KMC) agents. \n\n3) If you do have users of MQ Configuration and want to continue supporting that usage, you need to follow recommendations when you are installing and configuring OMEGAMON for Messaging V7.5 upgraded products.\n\n\nHere are the details:\n\n1) Suggested ways to determine whether there are any users of MQ Configuration:", "a. In the Tivoli Enterprise Portal (TEP), using an administrator user ID, click Edit->Administer Users to check whether any users or groups have access to the Configuration navigator view. For users and/or groups that have been configured for TEP, check the Navigator Views tab to see if any of them have “Configuration” in their Assigned Views. If no one is allowed access to the Configuration navigator, then they are not using MQ Configuration feature. \n\nb. Another item to check in Administer Users is whether any user or group has the Permissions tab showing that View or Modify permission has been authorized for WebSphere MQ Configuration Authorities “Configure” authority. Some user or group should have permission to use this feature if it is used by anyone.", "c. Check whether there are configured names that reflect queue managers in your environment. Click on the Configuration navigator in the view drop-down list in the Navigator pane, then click on Defined View on the left. In the middle Defined Tree pane on the workspace, expand the various “+” items, and with the help of someone who knows MQ queue managers in your environment, see if any of the expanded items reflect queue managers actually in your environment. There will be default and example items shipped with the product, but you are looking for names reflecting MQ at your site. If there are no names that reflect queue managers in your environment, then no one is using MQ Configuration.", "d. If it appears that there is usage of MQ Configuration, it would still be good to check with MQ users at your site to see if they actually require it. Perhaps they have experimented with it but do not actually use it regularly. If the OMEGAMON feature for MQ Configuration is not absolutely required in your environment, the recommendation would be to review all the ways that the IBM MQ product offers to configure and administer MQ, some of which are new in recent releases. Also, remember that the OMEGAMON MQ Monitoring agent offers the Take Action facility to issue any MQSC configuration command if the user is authorized.\n\n\n2) If there are no users of MQ Configuration, or you want to remove it anyway:", "a. If you use a Serverpac that contains the upgraded OMEGAMON for Messaging V7.5 components to install, the MQ Configuration FMIDs (HKMC730 and HKCF730) are not installed because they are not included in the Serverpac. However, depending on your previous configuration, the missing MQ Configuration component could cause unexpected results in your LPAR runtime environment (RTE), so check and act on the following items prior to installation and configuration of OMEGAMON for Messaging V7.5:\n\n1. If your Hub TEMS is configured on the z/OS platform and there are RKCF* DDNAME statements in your existing Hub TEMS started task JCL, update the TEMS started task JCL to remove those RKCF* DDNAME statements.", "2. If MQ Configuration (KMC) and MQ Monitoring (KMQ) agents are running in a shared agent address space, make sure that the owner of that address space is the MQ Monitoring agent. For the MQ Monitoring agent to be the owner, the related PARMGEN LPAR RTE profile parameters for OMEGAMON for Messaging components may need adjusting, as depicted in the following example before and after settings:\n\nBefore (MQ Configuration owns the Agent address space called OMEGMQ):\nISREDDE2 %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE_NAME%) \nCommand ===> \nKMC_AGT_STC OMEGMQ\nKMC_AGT_STC_OWNER “”\nKMQ_AGT_STC “”\nKMQ_AGT_STC_OWNER OMEGMQ\n\nAfter (MQ Monitoring owns the Agent address space called OMEGMQ): \nISREDDE2 %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE_NAME%) \nCommand ===>\nKMQ_AGT_STC OMEGMQ\nKMQ_AGT_STC_OWNER “”", "Tip: Please review the SMPE06 upgrade scenario [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe06_parmgenref.htm?pos=2] in the OMEGAMON Shared Knowledge Center as part of deploying these changes. You can use the refreshed OMEGMQ OMEGAMON for Messaging – KMQ Agent-only address space in the RTE’s W/RKANSAMU dataset for refreshing the original shared address space in your system procedure library. The only delta would be the RKMCAPLA DDNAME, which can be staged for removal.\n\nb. If you install OMEGAMON for Messaging V7.5 as a CBPDO into an existing SMP/E CSI, the MQ Configuration FMIDs will remain installed, but since you are not using MQ Configuration, it is recommended you follow these steps:\n\n1. If MQ Configuration (KMC) and MQ Monitoring (KMQ) agents are running in a shared agent address space, make sure that the owner of that address space is the MQ Monitoring agent. See item a.2 above for more details.", "2. In the “Include Products in this PARMGEN RTE panel (KCIP@PGI)” (under step “1 KCIJPCFG Set-up/Refresh PARMGEN work environment” navigation from the PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU), deselect the line with “KMC OMEGAMON for Messaging – WebSphere MQ Configuration” so that it will be removed from the runtime environment (RTE) during reconfiguration/upgrade of the RTE. Follow one of the SMPEnn upgrade scenarios [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe04_parmgenref.htm?pos=2] documented in the OMEGAMON Shared Knowledge Center.", "Tip: Prior to upgrading the RTE, you also have the option to SMP/E delete the HKMC730 and HKCF730 FMIDs from the existing CSI. When you start the PARMGEN configuration phase of the upgrade, the inexistence of these deleted FMIDs is PARMGEN’s trigger to delete the product from the RTE upon reconfiguration following any of the SMPEnn upgrade scenarios (SMPE04 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe04_parmgenref.htm?pos=2], SMPE05 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe05_parmgenref.htm?pos=2] or SMPE06 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe06_parmgenref.htm?pos=2]). \n\n\n3) If there are users of MQ Configuration, and you want to continue supporting that usage:", "a. It is highly recommended that you install OMEGAMON for Messaging V7.5 as a CBPDO into the existing SMP/E CSI so that MQ Configuration remains available. If you do this, there are no other steps required, however, the following step is also highly recommended: \n\n1. If MQ Configuration (KMC) and MQ Monitoring (KMQ) agents are running in a shared agent address space, separate them into their own address spaces, since they will be running at different product levels. For this, the related PARMGEN LPAR RTE profile parameters for OMEGAMON for Messaging components may need adjusting to be like the following example in which MQ Configuration is running in an address space called OMEGMC and MQ Monitoring is running in an address space called OMEGMQ:\n\nISREDDE2 %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE_NAME%) \nCommand ===> \nKMC_AGT_STC OMEGMC\nKMC_AGT_STC_OWNER “”\nKMQ_AGT_STC OMEGMQ\nKMQ_AGT_STC_OWNER “”", "b. If you were to install OMEGAMON for Messaging V7.5 in a Serverpac, you would need to retain your old SMP/E CSI and maintain a separate PARMGEN runtime environment in order to use MQ Configuration separately. This may be acceptable to you if you already separate MQ Configuration from the rest of your monitoring infrastructure, with its own Hub TEMS, etc. In this case, for the configuration that will contain OMEGAMON for Messaging V7.5, please see item 2 above, steps a.1 and a.2 in case they would apply to that particular configuration.", "c. OMEGAMON for Messaging V7.5 application support does not include application support for the MQ Configuration component. If you need to re-install application support for MQ Configuration for any reason, you should use the latest V7.3 level of application support. For z/OS customers, that is available with DVD LCD7-3513-08 at the following link: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]\n\n\nFor more information about OMEGAMON for Messaging V7.5, please see this link to the product documentation:\nhttps://www.ibm.com/support/knowledgecenter/SSRLD6_7.5.0/welcome_omxe_msg750.html [https://www.ibm.com/support/knowledgecenter/SSRLD6_7.5.0/welcome_omxe_msg750.html]", "For more information about OMEGAMON installation and configuration with PARMGEN, please see this link to the shared documentation:\nhttps://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/shared_welcome/welcome.htm?pos=2 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/shared_welcome/welcome.htm?pos=2]", "For more information about recommended ways to configure IBM MQ, please see the following links:\nAdministering IBM MQ [https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.adm.doc/q019950_.htm]\nConfiguring queue managers on z/OS [https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.con.doc/q019070_.htm]\nUsing IBM z/OSMF to automate IBM MQ [https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.con.doc/q019925_.htm]\nSupport continuous configuration deployments for IBM MQ with UrbanCode [https://www.ibm.com/developerworks/library/d-continuous-configuration-deployments-urbancode-mq-trs/index.html] \n\n\n\n\n\nORIGINAL PUBLICATION DATE\n 2017/10/26" ]

[ "Starting with V7.5, IBM OMEGAMON for Messaging on z/OS no longer delivers the component called WebSphere MQ Configuration Agent, referred to as MQ Configuration in the rest of this document, because there are other recommended ways to configure IBM MQ." ]

[ 0 ]

[ "IBM Security Bulletin: IBM WebSphere MQ MQXR insecure passwords (CVE-2015-2012) - United States SECURITY BULLETIN\n\nSUMMARY\n The Telemetry (MQXR) service can be configured to use SSL/TLS connections - the passphrase used to access the keystore is written to the file system in clear text in a properties file that is world readable. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-2012 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2012]\nDESCRIPTION: IBM WebSphere MQ stores the MQXR keystore password in clear text in a world readable file.\nCVSS Base Score: 2.1\nCVSS Temporal Score: See http://xforce.iss.net/xforce/xfdb/103923 [http://xforce.iss.net/xforce/xfdb/103923] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:L/AC:L/Au:N/C:P/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM WebSphere MQ 8.0 \n\n * 8.0.0.3 and earlier maintenance levels\n\n\nIBM WebSphere MQ 7.5 * 7.5.0.5 and earlier maintenance levels", "IBM WebSphere MQ 7.1 * 7.1.0.6 and earlier maintenance levels\n\nREMEDIATION/FIXES\nIBM WebSphere MQ 8.0 \n\nInstall fixpack 8.0.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg21969244] \nIBM WebSphere MQ 7.5 * Apply Interim fix IT09866 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+MQ&release=7.5.0.5&platform=All&function=aparId&apars=IT09866]\n\n\nIBM WebSphere MQ 7.1 * Install fixpack 7.1.0.7 [http://www-01.ibm.com/support/docview.wss?uid=swg21965293]\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "REFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] CHANGE HISTORY\n 01 February 2016: Original Copy Published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.", "DISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.\n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21977183]" ]

[ "CVEID: CVE-2015-2012 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2012]\nDESCRIPTION: IBM WebSphere MQ stores the MQXR keystore password in clear text in a world readable file.\nCVSS Base Score: 2.1\nCVSS Temporal Score: See http://xforce.iss.net/xforce/xfdb/103923 [http://xforce.iss.net/xforce/xfdb/103923] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:L/AC:L/Au:N/C:P/I:N/A:N)" ]

[ 0 ]

[ "IBM HTTP Session time-out settings and overwrite precedence rules - United States WebSphere http session management time-out wasrun precedence overwrite TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n It is possible to set the HTTP Session time-out in various places on the IBM® WebSphere® Application Server Administrative Console. It is also possible to set HTTP Session time-out for the application packaging process. \n\nSince Session time-out can be set in multiple places, it is necessary to understand how the ultimate Session time-out for an application is determined. \n\nCAUSE\nApplication needs HTTP session time-out set.\n\nRESOLVING THE PROBLEM\nThe HTTP Session time-out can be set in the following places: \n\n * From the Administrative Console at the server, Enterprise application, and Web application levels \n * At the time when the application is packaged \n * In the application code", "Setting 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.", "3. To set the HTTP Session time-out at the Web Application level, navigate to Applications > Enterprise Applications > Your Application > Web Module > Your Web App.war > Session Management. \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.", "This setting overrides any session time-outs defined from the Administrative Console. Alter this setting by repackaging the application with a new value, or by modifying the web.xml file. The entry in the web.xml will be as follows: \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.", "1. 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" ]

[ "The HTTP Session time-out can be set in the following places: \n\n * From the Administrative Console at the server, Enterprise application, and Web application levels \n * At the time when the application is packaged \n * In the application code" ]

[ 0 ]

[ "IBM Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) - United States SECURITY BULLETIN\n\nSUMMARY\n The Logjam Attack on TLS connections using the Diffie-Hellman (DH) key exchange protocol affects IBM WebSphere MQ Internet Pass-thru (MQIPT).", "VULNERABILITY DETAILS\nCVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]\nDESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as \"Logjam\".\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)", "AFFECTED PRODUCTS AND VERSIONS\nThe affected ciphersuite is available in all versions of IBM WebSphere MQ Internet Pass-thru (MQIPT) prior to 2.1.0.2\n\nREMEDIATION/FIXES\nSupportPac MS81: IBM WebSphere MQ Internet Pass-Thru\nUsers of IBM WebSphere MQ Internet Pass-Thru 2.1.0.1, 2.0 and older releases should first upgrade to IBM WebSphere MQ Internet Pass-Thru 2.1.0.2 [http://www.ibm.com/support/docview.wss?uid=swg24006386].\n\nWORKAROUNDS AND MITIGATIONS\nNone.\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "REFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT\nReported to IBM by the WeakDH team at https://weakdh.org [https://weakdh.org] \n\nCHANGE HISTORY\n 11th June 2015: Original version published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.", "DISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.\n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21962347]" ]

[ "CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]\nDESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as \"Logjam\".\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)" ]

[ 1 ]

[ "IBM How to find details of Corrupted Object from the entries in db2diag.log? - United States TECHNOTE (FAQ)\n\nQUESTION\n How to find details of Corrupted Object from the entries in db2diag.log? \n\nANSWER\nWhen we have corruption in the database we may received following kind of entries in db2diag.log \nThese also notify object where we t where we have detected corruption in the Database.\n\nSample db2diag.log entry for Corruption.\n\n2016-05-04-03.13.05.261082-360 I3442A358 LEVEL: Error \nPID : 393470 TID : 1 PROC : db2pfchr 0 \nINSTANCE: db2inst1 NODE : 000 \nFUNCTION: DB2 UDB, buffer pool services, sqlbReadAndReleaseBuffers,probe:13 \nRETCODE : ZRC=0x86020001=-2046689279=SQLB_BADP \"page is bad\" \nDIA8400C A bad page was encountered.", "2016-05-04-03.13.05.264301-360 I3801A437 LEVEL: Error \nPID : 393470 TID : 1 PROC : db2pfchr 0 \nINSTANCE: db2inst1 NODE : 000 \nFUNCTION: DB2 UDB, buffer pool services, sqlbReadAndReleaseBuffers, \nprobe:13 \nDATA #1 : String, 158 bytes \nObj={pool:3;obj:21;type:0} State=x27 Parent={3;21}, EM=1120, PP0=1152 \nPage=51235 Cont=17 Offset=2848 BlkSize=15 \nsqlbReadAndReleaseBuffers error: num-pages=16\n\n\nBased on this information dumped in db2diag.log entry we can Identify {pool:3;obj:21;type:0} is the Object is corrupted.\n\ne.g. Obj={pool:3;obj:21;type:0}\n\nPool = Tablespace ID\nObj = Object ID\nType = Type of the Object\n\nIf Type is 0 its Table Object ,If its 1 then its Index. \n\nWe can find the Name of the Object using following query, to further backup the Definition for future reference.\n\ndb2 \"select char(tabname,20), char(tabschema,20) from syscat.tables where tableid=<ObjectID> and tbspaceid=<Tablepace id>\"", "Obj={pool:3;obj:21;type:0}\ndb2 \"select char(tabname,20), char(tabschema,20) from syscat.tables where tableid=21 and tbspaceid=3\"\n\nRELATED INFORMATION\n SYSCAT.TABLES catalog view [http://www.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.sql.ref.doc/doc/r0001063.html?lang=en]" ]

[ "When we have corruption in the database we may received following kind of entries in db2diag.log \nThese also notify object where we t where we have detected corruption in the Database." ]

[ 0 ]

[ "IBM JMSExceptions CWSIT0006E and CWSIA0241E on bus connect - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Your application throws JMS exceptions CWSIT0006E and CWSIA0241E when trying to connect to a WebSphere Application Server (WAS) Service Integration Bus (SIBus). \n\nSYMPTOM\nApplication throws the following JMS exceptions in the stack trace while trying to connect to the SIBus: \n\nJMSException caught\njavax.jms.JMSException: CWSIA0241E: An exception was received during the call to the method\nJmsManagedConnectionFactoryImpl.createConnection:\ncom.ibm.websphere.sib.exception.SIResourceException: CWSIT0006E: It is not possible to contact\na messaging engine in bus YOURBUS..\nat\ncom.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:225)\nat\ncom.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:148)", "CAUSE\nThis can be caused by a stopped messaging engine, a wrong or misspelled bus name (case-sensitive) in the connection factory settings or, the HA manager is not able to find the running messaging engine.\n\n\nRESOLVING THE PROBLEM\nThe error messages CWSIA0241E and CWSIT0006E indicate that when the connection was attempted, there were no running messaging engines available on the specified bus. To see why the messaging engines were not available, check the SystemOut.log for applicable messages. Examine the SystemOut.log file starting at the time period when the application experienced the problem and search backward. \n\n\nCheck for the CWSID0016I which indicates status of the Messaging Engine activity. You may see messages like this:\n\nSibMessage I [:] CWSID0016I: Messaging engine [mename]is in state Stopping.\nSibMessage I [:] CWSID0016I: Messaging engine [mename]is in state Stopped.\n\nThe solution for this problem is to start the messaging engine.", "If the messaging engine is running and you still see these errors at the application side, other possible reasons for this problem are:\n\n1) Check provider end points. The value for the provider endpoints should be in the format of host_name:port_number:BootstrapBasicMessaging.\n\nIn the JMS connection factory, you can define a list of provider endpoints that govern which servers the application will attempt to connect to. If you have defined these endpoints, ensure that the messaging engines for these servers have all started and that the port and transport chains defined in the endpoint list are correct. Also, ensure that the values for the Connection proximity (bus, cluster, host or server) and the Target groups and Target significance settings are appropriate. For example, if the Target significance value is Required and no suitable messaging engine could be located, then this would cause a connection failure. Please refer to the following links for how to set provider endpoints:", "Default messaging provider queue connection factory [Settings] : [https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/SIBJMSQueueConnectionFactory_DetailForm.html]\n\nDefault messaging provider topic connection factory [Settings]: [https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/SIBJMSTopicConnectionFactory_DetailForm.html]\n\nRestart the server after making the change.\n\n2) If your environment is heavily loaded, the HA manager might not be able to locate the running messaging engine within three seconds. In this case, check if there are any hung threads in the SystemOut.log, and resolve them if possible. Next, consider increasing the value of sib.trm.linger from three to give the HA manager more time to locate a messaging engine.", "Tune the sib.trm.linger property value in the sib.properties file to set the messaging engine lookup delay so that the Work Load Manager (WLM) waits for a longer period of time before returning an error. Please refer to information below on how to set this property in the sib.properties. \n\n1)<WAS_HOME>/properties : The properties declared under this location would be applicable to all the profiles in that installation.\n\n2)<PROFILE_ROOT>/properties : The properties declared here are applicable for all the servers on this profile\n\nIf a property is defined at both <PROFILE_ROOT>/properties and <WAS_HOME>/properties, then the property defined at <PROFILE_ROOT>/properties would take precedence.\n\nAfter resetting the property you must restart the server.", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere MQ Not Applicable Business Integration WebSphere Process Server Business Integration WebSphere Service Registry and Repository Business Integration IBM Business Process Manager Standard Business Integration WebSphere Enterprise Service Bus Business Integration WebSphere Partner Gateway Advanced Edition Configuration Business Integration WebSphere MQ Configuration \nPRODUCT ALIAS/SYNONYM\n WebSphere Application Server WAS SIB SIBUS SI BUS" ]

[ "If your environment is heavily loaded, the HA manager might not be able to locate the running messaging engine within three seconds. In this case, check if there are any hung threads in the SystemOut.log, and resolve them if possible. Next, consider increasing the value of sib.trm.linger from three to give the HA manager more time to locate a messaging engine.\n\nTune the sib.trm.linger property value in the sib.properties file to set the messaging engine lookup delay so that the Work Load Manager (WLM) waits for a longer period of time before returning an error. Please refer to information below on how to set this property in the sib.properties. \n\n1)<WAS_HOME>/properties : The properties declared under this location would be applicable to all the profiles in that installation.\n\n2)<PROFILE_ROOT>/properties : The properties declared here are applicable for all the servers on this profile\n\nIf a property is defined at both <PROFILE_ROOT>/properties and <WAS_HOME>/properties, then the property defined at <PROFILE_ROOT>/properties would take precedence.\n\nAfter resetting the property you must restart the server." ]

[]

[ "IBM Security Bulletin: IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object on unix platforms ( CVE-2016-0394 ) - United States WMB IIB SECURITY BULLETIN\n\nSUMMARY\n IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object on unix platforms, which exposes it to an unintended actor. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-0394 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0394]\nDESCRIPTION: IBM Integration Bus and WebSphere Message broker set incorrect permissions for an object, which could allow a local attacker to manipulate certain files. \nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112643 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112643] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)", "AFFECTED 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]", "WORKAROUNDS 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.", "IMPORTANT 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]", "CHANGE 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.", "RELATED 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" ]

[ "CVEID: CVE-2016-0394 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0394]\nDESCRIPTION: IBM Integration Bus and WebSphere Message broker set incorrect permissions for an object, which could allow a local attacker to manipulate certain files. \nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112643 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112643] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)" ]

[ 0 ]

[ "IBM Portal upgrades fail during ejbdeploy with 'Error is Platform not running' message - United States 7001eGA TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nPortal upgrades fails during ejbdeploy with 'Error is Platform not running' message. This could happen for any v6.1.0.x , v7.0.0.x, or v8.0.0.x upgrade", "SYMPTOM\nIn the ConfigTrace.log, the following exception can be seen:\n==========================\n[wsadmin] ADMA5016I: Installation of wps started.\n[wsadmin] ADMA5058I: Application and module versions are validated with versions of deployment targets.\n[wsadmin] ADMA5018I: The EJBDeploy program is running on file /var/tmp/app5791171104868981175.ear.\n[wsadmin] Starting workbench.\n[wsadmin] EJB Deploy configuration directory: /opt/IBM/WebSphere/AppServer/profiles/dmgrProfile/ejbdeploy/configuration/\n[wsadmin] framework search path: /opt/IBM/WebSphere/AppServer/deploytool/itp/plugins\n[wsadmin] build: RAD753-I20090617_1116\n[wsadmin] An unexpected exception was thrown. Halting execution.\n[wsadmin] Shutting down workbench.\n[wsadmin] Error executing deployment: java.lang.IllegalStateException. Error is Platform not running.\n[wsadmin] java.lang.IllegalStateException: Platform not running\n[wsadmin] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:374)", "[wsadmin] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n[wsadmin] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)\n[wsadmin] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)\n[wsadmin] at java.lang.reflect.Method.invoke(Method.java:597)\n[wsadmin] at com.ibm.etools.ejbdeploy.batch.impl.BootLoaderLoader.run(BootLoaderLoader.java:487)\n[wsadmin] at com.ibm.etools.ejbdeploy.batch.impl.BatchDeploy.execute(BatchDeploy.java:106)\n[wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:106)\n[wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.deploy(EJBDeploy.java:349)\n[wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.main(EJBDeploy.java:311)\n[wsadmin] EJBDeploy level: @build@\n[wsadmin] ADMA5008E: The EJBDeploy program failed on file /var/tmp/app5791171104868981175.ear. Exception: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy", "[wsadmin] ADMA0063E: An error occurred during Enterprise JavaBeans (EJB) deployment. Exception: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy\n[wsadmin] ADMA5011I: The cleanup of the temp directory for application wps is complete.\n[wsadmin] ADMA5069E: The installation of application wps failed. This application was in the middle of a full update and therefore is uninstalled from the configuration session. Discard your current configuration session immediately to recover the application. Do not save changes to the WebSphere Application Server configuration repository. The application is not uninstalled from this repository. Until the current configuration session is discarded you do not see this application in the current session.", "[wsadmin] WASX7017E: Exception received while running file \"/opt/IBM/WebSphere/AppServer/profiles/wp_profile/ConfigEngine/config/work/was/curJaclScript.jacl\"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7418E: Application update for wps failed: see previous messages for details.", "[wsadmin] WASX7341W: No \"save\" was performed before the interactive scripting session exited; configuration changes will not be saved.\n/opt/IBM/WebSphere/AppServer/profiles/wp_profile/ConfigEngine/config/includes/apply_PTF.xml:59: Java returned: 105\n==========================\n\nCAUSE\nThis exception can happen during ejbdeploy after the WebSphere Application Server has been upgraded, and old OSGI cache remains for the ejbdeploy tool. The OSGI class of the ejbdeploy tool contains class information within the deploytool folder and can become stale if the content inside deploytool has changed. \n\n\n\nRESOLVING THE PROBLEM\nTo resolve the problem, complete the following steps: \n\n\n1. Delete/Remove the contents of the following directory EXCEPT for the 'config.ini' file, if it exists (the paths are different depending on your backend WAS version):\n\nWebSphere Application Server v6.1.x: \n<profile root>/deploytools/configuration", "WebSphere Application Server v7.0.x: \n<profile root>/ejbdeploy/configuration\n<AppServer root>/deploytool/itp/configuration\n\n\nWebSphere Application Server v8.0.x:\n<profile root>/ejbdeploy/configuration\n<AppServer root>/deploytool/itp/configuration\n\n\nCluster Environments: Do this for both the DMGR profile and the node profile.\n\nNote: The deploytools and ejbdeploy directories may not exist on all nodes. They are created when ejbdeploy is executed successfully for the first time. If it has never been executed successfully in your environment, then the directories will not be there.\n\n2. Re-attempt the WebSphere Portal upgrade.\n\n\n\n\n * \n *" ]

[ "This exception can happen during ejbdeploy after the WebSphere Application Server has been upgraded, and old OSGI cache remains for the ejbdeploy tool. The OSGI class of the ejbdeploy tool contains class information within the deploytool folder and can become stale if the content inside deploytool has changed." ]

[ 5 ]

[ "IBM The affect of the auto-update feature for Oracle JDK 7 on IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation - United States NEWS\n\nABSTRACT\n The IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation products support Oracle JDK 7, but do not support Oracle JDK 8. \n\nCONTENT\nOn Windows operating systems, because the upgrade to Oracle JDK 8 is enabled by default, you might not be aware that the upgrade has occurred. This Oracle JDK 8 issue applies to the Mac OS as well.\n\n\n\nSYMPTOM\nYou might see one of the following messages in the log file on Windows and Mac OS machines that originate from the WebSphere Application Server Liberty Profile: \n\n * TRAS0033E: Runtime injection of detailed method trace failed for class <class name> with exception <exception name> \n * CWWKC0044W: An exception occurred while scanning class and annotation data.", "RESOLUTION\nAs stated on the Java SE at a Glance [http://www.oracle.com/technetwork/java/javase/overview/index.html] page, Oracle is automatically migrating users with the auto-update feature enabled from Oracle JDK 7 to Oracle JDK 8. However, a number of IBM and third-party dependencies for IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation do not support Oracle JDK 8.", "* Windows operating systems\n If you have already migrated to Oracle JDK 8, you need to revert to Oracle JDK 7 using the following steps: 1. Uninstall Oracle JDK 8.\n \n \n 2. Download the latest version of Oracle JDK 7 from the Java SE Downloads [http://www.oracle.com/technetwork/java/javase/downloads/index.html] tab of the Oracle web site.\n \n \n 3. Reinstall Oracle JDK 7.\n \n \n \n To disable the JDK auto-update feature on Windows operating systems, see the Change Automatic Update Settings [http://java.com/en/download/help/java_update.xml#adv] section of the Oracle Java Auto Update documentation.\n \n \n * Mac OS\n If you have already migrated to Oracle JDK 8, you need to revert to Oracle JDK 7 using the following steps: 1. Uninstall Oracle JDK 8. For more information, see the How do I uninstall Java 7 and later versions on my Mac? [https://www.java.com/en/download/help/mac_uninstall_java.xml] information on the Oracle web site.", "2. Download the latest version of Oracle JDK 7 from the Java SE Downloads [http://www.oracle.com/technetwork/java/javase/downloads/index.html] tab of the Oracle web site. For more information, see JDK 7 Installation for Mac OS X [http://docs.oracle.com/javase/7/docs/webnotes/install/mac/mac-jdk.html].\n \n \n 3. Reinstall Oracle JDK 7. \n \n \n \n \n On the Mac OS operating system, you are explicitly asked if you want to update your Java version. Do not update the Java version to Java 8. To verify your Java version, see How do I update Java for my Mac? [https://www.java.com/en/download/help/mac_java_update.xml]", "Cross reference information Segment Product Component Platform Version Edition Mobile- Speech and Enterprise Access IBM Worklight Security Mac OS X, Windows 6.2, 6.1, 6.0, 5.0.6, 5.0.5 Consumer, Enterprise Mobile- Speech and Enterprise Access IBM Mobile Foundation Security Mac OS X, Windows 6.0, 5.0.6, 5.0.5 Consumer, Enterprise" ]

[ "The IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation products support Oracle JDK 7, but do not support Oracle JDK 8." ]

[ 0 ]

[ "IBM WebSphere DataPower M/T 9235 appliance might incorrectly report failure of both power supplies - United States TECHNOTE (FAQ)\n\nQUESTION\n The IBM WebSphere DataPower M/T 9235 appliance might incorrectly report the failure of both power supplies. This message is not reported on all appliances and can occur rarely in the field. \n\nANSWER\nThe following message would be present in the DataPower logs: \n\nSystem power supply #2 has failed.\n\nor logging event code: \n\n0x80400022 System power supply #2 \n\n\nThe problem can be confirmed by issuing the following commands on the appliance CLI:\n\nco \ntest hardware \nexit \n\nThe following output from the test hardware command confirms this problem: \n\n[failure] Power supply '1' has no AC input power, or is not present.\n[failure] Power supply '2' has no AC input power, or is not present.\n\nOther results in the test hardware command might also show incorrect values.", "This problem does not affect the operation of the appliance other than the continuous reporting power supply failure message. \n\nTo confirm the power supplies are working normally you may check the LED status on the power supplies. If the LED's are green the power supplies are working normally.\n\n\nTo recover from the false errors perform a reboot of the appliance: \n\nFrom the WebGUI: \n\nControl Panel → System Control → In the “Shutdown” section choose “Reboot System” then click “Shutdown” \n\n \n\nFrom the CLI: \n\ntop \n\nshutdown reboot \n\ny \n\n\nThis problem is caused by a highly intermittent error that may allow the sensor reading mechanism to get into a bad state. This bad state then generates the false error messages. In most cases, a reboot of the appliance will reset the sensors and no additional errors are logged. The highly intermittent error rarely occurs again on the same appliance", "If the issue reoccurs on the same appliance contact IBM DataPower support [http://www.ibm.com/support/docview.wss?uid=swg21236322] with the following information: \n\n1) How many times have you seen the issue on the same appliance? \n\n2) Gather the outputs for the following CLI commands:\nshow clock\nshow version\nshow ipmi\nshow sensors-other\nconfig\nservice show\ntest hardware" ]

[ "In most cases, a reboot of the appliance will reset the sensors and no additional errors are logged." ]

[ 1 ]

[ "IBM PI37248: A PROPERTY FILE BASED CONFIGURATION (PFBC) FILE MIGHT FAIL TO AP PLY. - United States FIXES ARE AVAILABLE\n8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040035]\n8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24040425]\n8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24040533]\n8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041178]\n8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24041590]\n8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24041819]\n8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]", "8.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]", "SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.", "ERROR DESCRIPTION\n * A PFBC file might fail to apply. Wsadmin will show an error\n similar to this:\n \n java.lang.Exception: java.lang.Exception: ADMG0660E:\n Properties File Validation during command\n applyConfigProperties failed. See Report file for details.\n \n The report file will contain an error similar to this:\n Error=java.lang.NullPointerException\n at\n com.ibm.websphere.management.configservice.ConfigServiceHelper.g\n etConfigDataType(ConfigServiceHelper.java:235)\n at\n com.ibm.ws.management.configservice.WorkspaceHelper.getType(Work\n spaceHelper.java:563)\n at\n com.ibm.ws.management.configservice.WorkspaceHelper.getDelegator\n (WorkspaceHelper.java:584)\n at\n com.ibm.ws.management.configservice.ConfigServiceImpl.getAttribu\n tes(ConfigServiceImpl.java:2102)\n at\n com.ibm.ws.management.commands.properties.resources.common.Apply\n Properties.setProperties(ApplyProperties.java:240)\n \n \n \n \n \n\nLOCAL FIX", "PROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server Property File Based Configuration *\n ****************************************************************\n * PROBLEM DESCRIPTION: A Property File Based Configuration *\n * (PFBC) file might fail to apply. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n A recent (8.5.5.5) parser change introduced a problem where\n types that have default values noted in the file and are not\n Strings can be incorrectly processed. For example:\n isolatedClassLoader=false #boolean,default(false)\n might be incorrectly processed, and as a result, the file\n might not apply.", "PROBLEM CONCLUSION\n * The parsing code is updated so the problem no longer occurs.\n \n The fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.5.6. Please refer to the Recommended Updates\n page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI37248\n \n \n * REPORTED COMPONENT NAME\n WEBS APP SERV N\n \n \n * REPORTED COMPONENT ID\n 5724H8800\n \n \n * REPORTED RELEASE\n 850\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt / Xsystem\n \n \n * SUBMITTED DATE\n 2015-03-18\n \n \n * CLOSED DATE\n 2015-03-20\n \n \n * LAST MODIFIED DATE\n 2015-03-24", "* 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" ]

[ "The parsing code is updated so the problem no longer occurs.\n \n The fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.5.6." ]

[ 5 ]

[ "IBM Diagnosing a java.lang.StackOverflowError - United States StackOverflow; overflowing; recursion; recursively; jit; JustInTime; Hot; Spot; WebSphere; Just-In-Time TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Stack Overflow exceptions can occur when a thread stack continues to grow in size until reaching the maximum limit. \n\nSYMPTOM\n A stack overflow can result from: \n\n * A deeply nested application \n * An infinite loop within an application \n * A problem in just-in-time (JIT) compiled code \n * Applications requiring a larger stack size, especially ones relying on XML, GUI, or java2D classes. \n * Native method calls", "Stack overflow issues are frequently masked by Out of Memory exceptions. By resolving the memory constraints, the stack overflow can be resolved. \nCAUSE\nWhen a stack overflow occurs, the amount of stack space required by the program exceeds what is configured for the stack in the Java™ Virtual Machine (JVM) process, or the native stack size configured by the operating system. \nSome applications require stacks that are larger than the default size; for example, a graphics-intensive Java program can require a larger stack, which may require an increase in the stack size to avoid StackOverflow.\n\n\nDIAGNOSING THE PROBLEM\nLook for either Out of Memory messages or java.lang.StackOverflow in the server logs. The process may continue to run after either of these messages are seen. \n\n\nIf a crash did occur, a javacore should have generated on IBM SDK. You will either see the signal as SIGSEGV, SIGILL, SIGABRT, or SIGBUS. Usually the current thread will indicate the following", "pending=java.lang.StackOverflowError \nRESOLVING THE PROBLEM\n \n\n\n\n\n[/support/docview.wss?uid=swg21162896&aid=1]Explanations and Solutions\n[/support/docview.wss?uid=swg21162896&amp;aid=2]Detailed Configuration Options \n\n\n\n\n\n\n \n\nExplanations and Solutions \n\nInfinite Recursion \nIf an application is performing recursion, the maximum stack size can easily be reached and a Stack Overflow exception is thrown. The thread stack has a limited size and eventually its space will run out as the thread stack grows without bounds. \n\nSome traits of recursion: \n- Large thread stacks that appear to repeat \n- An infinite loop that continuously spawns off threads \n- Very large XML documents loaded into the Document Object Model (DOM) \n- JSP or servlets calling itself (usually by executing forward or include to itself) \n- Repeated calls in native functions", "Increasing the thread stack size allows for larger thread stacks. However if the recursion continues to trigger a stack overflow, the next step is to identify what code is causing the recursion from javacores, thread dumps, or even system core files. \n\nA thread stack that indicates it's too large to display can be an indicator of stack overflow. This is especially true if the stack appears to repeat (such as recursive method calls). \n\nJIT/HotSpot Compiled Code", "The JIT/HotSpot compiler (JIT) is designed to speed up the JVM execution times by compiling method calls. This can speed up execution time, but as more aggressive optimizations are used, this can inadvertently cause recursion, resulting in stack overflow or crash. The documents linked below explain how to debug JIT and HotSpot compiler issues: * JIT Problem Determination for IBM SDK 5.0 and 6.0 using -Xjit [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21294023] \n * Debugging HotSpot failures on the Solaris and HP-UX operating environment [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21081179]\n\n\n\nDepleted Native Stack \nIt is almost guaranteed that a crash will occur if the native stack runs out of space. System cores can be used to identify long and possibly recursively looping native thread stacks.", "To resolve, increase the native stack size (usually by adjusting the operating system limit for stack size) to accommodate the recursive native calls; however, identifying the recursive native calls will help determine the root cause of the stack overflow. \n\n\n\n\n[/support/docview.wss?uid=swg21162896&amp;aid=3] Back to top \n\n[http://www.ibm.com/i/v14/rules/dotted_blue_rule_443.gif] \n\n \n\nDetailed Configuration Options \n\nAdjusting the Stack Sizes (Xss and Xmso) options \nIf this does not work, you can adjust the stack sizes. Doubling the stack size is suggested as a first step; however, every thread that the JVM creates will consume memory. Be careful to not exhaust your physical and heap memory resources.", "For every Java thread, there are two stacks that are utilized. One is for Java code for method calls, and the other is for native C code (on Solaris and HP-UX, only the native stack is utilized). These are adjustable and can be raised to provide more room on the stacks to prevent an overflow. \n\n * Maximum Thread Stack Size (-Xss)\n * \n * \n * \n * \n * -Xss<size> \n * \n * <size>\n * \n * nn[k|m|g|K|M|G]\n * \n * \n * \n * \n * \n * \n * there is no distinction between native and thread stack sizes\n * \n * only \n * \n * HP-UX\n * \n * \n * \n * -XX:MainThreadStackSize=<size> \n * \n * \n * \n * \n * \n * \n * \n * Initial Thread Stack Size (-Xiss)\n * \n * This is only for distributed platforms (AIX, Linux, Windows)\n * \n * \n * \n * \n * \n * -Xiss<size> \n * \n * <size>\n * \n * nn[k|m|g|K|M|G]\n * \n * \n * \n * \n * Initial Native Stack Size (-Xmso)\n * \n * This is only for distributed platforms (AIX, Linux, Windows)\n * \n * \n * \n * \n * \n * \n * -Xmso<size> \n * \n * <size>\n * \n * nn[k|m|g|K|M|G]\n * \n * \n * \n *", "Default Values \nThis is a chart of default sizes for the various stack size arguments. This is subject to change due to upgrades of the SDK.", "[/support/docview.wss?uid=swg21162896&amp;aid=4]\nValue [/support/docview.wss?uid=swg21162896&amp;aid=4]\nAIX [/support/docview.wss?uid=swg21162896&amp;aid=4]\nLinux [/support/docview.wss?uid=swg21162896&amp;aid=4]\nWindows [/support/docview.wss?uid=swg21162896&amp;aid=4]\nSolaris [/support/docview.wss?uid=swg21162896&amp;aid=4]\nHP-UX [/support/docview.wss?uid=swg21162896&amp;aid=4]\nInitial Thread Stack Size [/support/docview.wss?uid=swg21162896&amp;aid=4]\n2KB [/support/docview.wss?uid=swg21162896&amp;aid=4]\n2KB [/support/docview.wss?uid=swg21162896&amp;aid=4]\n2KB [/support/docview.wss?uid=swg21162896&amp;aid=4]\nNot Adjustable [/support/docview.wss?uid=swg21162896&amp;aid=4]\nNot Adjustable [/support/docview.wss?uid=swg21162896&amp;aid=4]\nMaximum Thread Stack Size [/support/docview.wss?uid=swg21162896&amp;aid=4]\n256KB (32-bit)\n512KB (64-bit) [/support/docview.wss?uid=swg21162896&amp;aid=4]\n256KB (32-bit)\n512KB (64-bit) [/support/docview.wss?uid=swg21162896&amp;aid=4]\n256KB (32-bit)", "512KB (64-bit) [/support/docview.wss?uid=swg21162896&amp;aid=4]\nNot Adjustable [/support/docview.wss?uid=swg21162896&amp;aid=4]\nNot Adjustable [/support/docview.wss?uid=swg21162896&amp;aid=4]\nNative Stack Size [/support/docview.wss?uid=swg21162896&amp;aid=4]\n256KB [/support/docview.wss?uid=swg21162896&amp;aid=4]\n256KB [/support/docview.wss?uid=swg21162896&amp;aid=4]\n32KB (32-bit)\n256KB (64-bit) [/support/docview.wss?uid=swg21162896&amp;aid=4]\n512KB (32-bit)\n1024KB (64-bit) [/support/docview.wss?uid=swg21162896&amp;aid=4]\n64KB (PA-RISC)\n1024KB (Itanium) [/support/docview.wss?uid=swg21162896&amp;aid=4]\n[/support/docview.wss?uid=swg21162896&amp;aid=4]\n[/support/docview.wss?uid=swg21162896&amp;aid=4]\n[/support/docview.wss?uid=swg21162896&amp;aid=4]\n[/support/docview.wss?uid=swg21162896&amp;aid=4]\n[/support/docview.wss?uid=swg21162896&amp;aid=4]\n[/support/docview.wss?uid=swg21162896&amp;aid=5] Back to top", "Examples of Stack Overflow", "Server Logs \nThese logs may contain references to StackOverflow, alongside other messages. Thread stacks may accompany these messages, indicating if there is a recursive call. \n * SystemOut.log example\n \n * [3/14/15 3:14:15:926 CST] 31415926 BaseMap W CWOBJ0006W: An exception occurred:\n * \n * com.ibm.websphere.objectgrid.ObjectGridRuntimeException: java.lang.StackOverflowError\n * \n * <<Thread stack may follow this message>>\n * \n \n * \n * \n * \n * SystemErr.log example\n \n * [3/14/15 3:14:15:926 PST] 31415926 SystemErr R Caused by: java.lang.StackOverflowError\n * \n * at java.util.Hashtable.get(Hashtable.java:461)\n * \n * at com.ibm.ws.webcontainer.srt.SRTServletRequest.getParameter(SRTServletRequest.java:1257)\n * \n * at psdi.webclient.system.session.WebClientSession.applySkin(WebClientSession.java:295)\n * \n * at psdi.webclient.system.controller.AppInstance.render(AppInstance.java:1177)\n * \n * at psdi.webclient.system.controller.AppInstance.render(AppInstance.java:1213)\n *", "* at psdi.webclient.system.controller.AppInstance.render(AppInstance.java:1213)\n * \n * ...\n * \n \n *", "Javacore \n\nIn javacores, look for \"StackOverflowError\" in the thread name entry: 3XMTHREADINFO \"ORB.thread.pool : 19\" (TID:10167F78, sys_thread_t:E072BCE0, state:R, native ID:E06BEBA0) prio=5: pending=java.lang.StackOverflowError \nSystem Dump (processed with jextract and DTFJ Dump Analyzer) \n\nLook for this message near the end of a very large stack. This particular example had 1000 recursively called entries. Java stack frames dump is too long: <analyzererror> \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK" ]

[ "Adjusting the Stack Sizes (Xss and Xmso) options \nIf this does not work, you can adjust the stack sizes. Doubling the stack size is suggested as a first step; however, every thread that the JVM creates will consume memory. Be careful to not exhaust your physical and heap memory resources. \n\nFor every Java thread, there are two stacks that are utilized. One is for Java code for method calls, and the other is for native C code (on Solaris and HP-UX, only the native stack is utilized). These are adjustable and can be raised to provide more room on the stacks to prevent an overflow." ]

[]

[ "IBM Security Bulletin: Incorrect saved channel status enquiry could cause denial of service for IBM MQ (CVE-2017-1236) - United States SECURITY BULLETIN\n\nSUMMARY\n IBM MQ could allow an authenticated user to potentially cause a denial of service by issuing an incorrect saved channel status inquiry. \n\nVULNERABILITY DETAILS\n\nCVEID:CVE-2017-1236 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1236]\nDESCRIPTION:IBM MQ could allow an authenticated user to potentially cause a denial of service by saving an incorrect channel status inquiry.\nCVSS Base Score: 3.1\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/124354 [https://exchange.xforce.ibmcloud.com/vulnerabilities/124354]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ 9.0.2 Continuous Delivery \n\nIBM MQ Appliance 9.0.x Continuous Delivery \n\nIBM MQ 9.0 LTS \n\nIBM MQ 8.0 \n\nIBM MQ 8.0 Appliance", "REMEDIATION/FIXES\nIBM MQ 9.0.2 Continuous Delivery \n\nApply IBM MQ 9.0.3 Continuous Delivery release or later. \n\nIBM MQ Appliance 9.0.x Continuous Delivery \n\nApply continuous delivery update 9.0.3 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&release=9.0.2&platform=All&function=all] or later. \n\nIBM MQ 9.0 LTS \n\nApply Fix Pack 9.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24044038]. \n\nIBM MQ 8.0 \n\nApply Fix Pack 8.0.0.7 [http://www-01.ibm.com/support/docview.wss?uid=swg22005832]. \n\nIBM MQ Appliance 8.0 \n\nApply Fix Pack 8.0.0.7 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&release=8.0.0.5&platform=All&function=all].\n\nWORKAROUNDS AND MITIGATIONS\nIBM MQ Appliance; Affected Queue manager must be restarted. \n\nIBM MQ 9.0.2 CD : Restart the failed command server on the queue manager.", "IBM MQ 9.0 LTS : Restart the failed command server on the queue manager. \n\nIBM MQ 8.0 : Restart the failed command server on the queue manager.\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.", "REFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 09 Jan 2018: Updated\n06 Oct 2017: Updated at 9002 GA\n15 Jun 2017: Original version published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.", "DISCLAIMER\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." ]

[ "CVEID:CVE-2017-1236 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1236]\nDESCRIPTION:IBM MQ could allow an authenticated user to potentially cause a denial of service by saving an incorrect channel status inquiry.\nCVSS Base Score: 3.1\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/124354 [https://exchange.xforce.ibmcloud.com/vulnerabilities/124354]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L)" ]

[ 0 ]

[ "IBM How to troubleshoot the error \"Failed to process response headers\" - United States datapower; failed; parse; process; error; network; connection; persistent; headers; response headers; failed to process response headers; 7993; 7993; 7993; machine type 7993 TECHNOTE (FAQ)\n\nQUESTION\n What does this error mean?\n\nGeneral error that is always seen:\n[servicetype][error] wsgw(policyrule): tid(196761)[error][x.x.x.x]: Failed to process response headers\n\nSpecifically from a Web Service Gateway:\n[ws-proxy][error] wsgw(Proxy): tid(1234567)[10.2.3.4]: Backside header failed to parse due to: Failed to process response headers\n[ws-proxy][error] wsgw(Proxy): tid(1234567)[error][10.2.3.4]: Failed to process response headers \n\nAdditional log information might be seen while at the debug log level.", "CAUSE\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:", "A 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.", "In 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." ]

[ "In almost every event, this error is caused by a connection failure.\nThe error is correct, the service did not receive any response headers or data. The key to help confirm this is to increase the log level to debug. This will allow you to see the network debug errors around the context of the service error." ]

[ 1 ]

[ "IBM Content Collector Configuration Store is corrupted - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM Content Collector Configuration Store Service cannot be started successfully due to database corruption. \n\nSYMPTOM\nCannot start the IBM Content Collector Configuration Store Service\n\n\nCAUSE\nTransaction log gets corrupted when IBM Content Collector server runs out of disk space. \n\nRESOLVING THE PROBLEM", "1. Shutdown the IBM Content Collector Configuration Store Service if it is running. \n 2. Make a backup copy of all files under the following directory:\n C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\n \n C:\\ProgramData may be hidden by default. Show hidden folders by changing the configuration in Folder and Search options > View tab > Hidden files and folders > Show hidden files, folders, and drives. \n 3. Free up disk space on the drive \n 4. Delete the following files:\n C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\\logs\\*\n C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\\solmsg.out\n C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\\solerror.out\n \n Important: \n Delete only the files under C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\\logs\\. \n Do not delete the folder itself.", "5. If restoring the configuration store to a previously backed up copy is required, run afuConfigStoreTool -backup to restore the backup copy. See production documentation for more information on running this tool. Otherwise, proceed to the next step. \n 6. Restart IBM Content Collector services.", "RELATED INFORMATION\n IBM Content Collector Information Center [http://pic.dhe.ibm.com/infocenter/email/v4r0m0/index.jsp]" ]

[ "Transaction log gets corrupted when IBM Content Collector server runs out of disk space." ]

[ 0 ]

[ "IBM DataPower Gateways Firmware Support Lifecycle - United States datapower;support;lifecycle;support lifecycle;maintenance;firmware;release;releases;firmware releases;upgrade;upgrades;features;defect NEWS\n\nABSTRACT\nThis document provides information on the IBM DataPower Gateway Firmware Support Lifecycle.\n\nCONTENT\nIBM® DataPower® Gateway is a purpose-built gateway that provides security, traffic control, mediation and optimized access to a full range of mobile, web, application programming interface (API), service-oriented architecture (SOA), B2B and cloud workloads. It supports multi-cloud deployment and is available in Docker container, Linux application, VMware virtual machine and physical appliance form factors.\n\nIBM provides flexible support options to meet the needs of your business and minimize any business impact. The IBM DataPower Gateways end-of-service support policy applies differently between hardware and firmware.\n\nHardware", "DataPower physical appliance hardware is supported for a minimum of five years, starting at the General Availability of the new product. Beginning with the 8436 models, standard appliance service and support is available for five years from the end-of-marketing (EOM) date as described in the IBM Appliance Support Handbook [http://www.ibm.com/support/customercare/sas/f/applhandbook/home.html].\n\nFor end-of-service information on physical appliances, see IBM DataPower Gateways End of Service dates [http://www.ibm.com/support/docview.wss?uid=swg21317845]. \n\nFirmware \n\nBusinesses are building modernized digital platforms to drive innovation and disruption within the industry. IBM DataPower Gateways are a core component in these platforms and it needs to deliver new business functionality to keep pace with business innovation.", "Effective with DataPower Gateway firmware V7.6 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS217-265&appname=USN], DataPower introduces a Continuous Delivery (CD) model to accelerate delivery of new capabilities and meet market needs. DataPower CD will consist of two releases:\n\n 1. CD release approximately once per quarter * Only the most recent CD release is supported at a given time.\n \n \n 2. Long Term Support (LTS) release every 12 months. * LTS releases are for customer seeking enhanced stability and do not wish to upgrade on the CD schedule, while CD releases are intended for customers seeking the latest features.\n * The first LTS release post 7.6 GA will be within two years. Subsequent LTS releases will occur every 12 months.\n * LTS releases will be supported for a minimum of 2 years.", "Firmware V7.6 and later have no extended support plan available for any release of DataPower Gateway. IBM will publish a notice of support discontinuance (end-of-service) for a LTS releases at least 12 months before the effective date.\n\nFirmware V7.5 and earlier will remain on the traditional IBM DataPower Gateway support model where they will be supported for a minimum of 2 years. There is no extended support plan available for any of these releases. IBM will publish a notice of support discontinuance (end-of-service) for releases at least 12 months before the effective date.\n\nNote: IBM DataPower Gateways customers can use the following table to track how long their version and release of a particular firmware level will be supported. By using the information in this table, customers can effectively plan their firmware investment without any gaps in support.", "Release Support Model GA date End-of-service date Comment 7.7.0 \n7.7.1.0 \n7.7.1.1 \n7.7.1.2 CD 03/2018 [http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&supplier=897&letternum=ENUS218-018] \n06/08/2018 \n06/29/2018 \n07/27/2018 06/08/2018 \n06/29/2018 \n07/27/2018 \nPlanning Information 7.6.0 LTS 07/2017 [http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&supplier=897&letternum=ENUS217-265] Planning Information 7.5.0 \n7.5.1 \n7.5.2 Traditional 03/2016 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/897/ENUS216-024/index.html&lang=en&request_locale=en] \n06/2016 \n09/2016 04/30/2019 \n04/30/2019", "04/30/2019 7.5.x Withdrawal Announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/897/ENUS918-054/index.html&request_locale=nul] 7.2.0 Traditional 06/2015 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS215-108/index.html&lang=en&request_locale=en] 09/30/2018 7.2.0 Withdrawal Announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS917-138/index.html&lang=en&request_locale=en] 7.1.0 Traditional 11/2014 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/897/ENUS214-394/index.html&lang=en&request_locale=en] 09/30/2018 7.1.0 Withdrawal Announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS917-138/index.html&lang=en&request_locale=en] 7.0.0 Traditional 06/2014 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/897/ENUS214-117/index.html&lang=en&request_locale=en] 09/30/2017 7.0.0 Withdrawal", "Announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/897/ENUS916-117/index.html&lang=en&request_locale=en] 6.0.2 (Common Criteria) Traditional 05/2015 6.0.1 Traditional 12/2013 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/5/649/ENUSA13-1105/index.html&lang=en&request_locale=en] 06/19/2016 6.0.1 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21882726] 6.0.0 Traditional 06/2013 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS213-172/index.html&lang=en&request_locale=en] 06/19/2016 6.0.0 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21882726] 5.0.0 Traditional 06/2012 [http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS112-064] 06/30/2015 5.0.0 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21677137] 4.0.2 Traditional 09/2011", "[http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS211-288/index.html&lang=en&request_locale=en] 11/30/2014 4.0.2 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21649637] 4.0.1 Traditional 06/2011 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/1/897/ENUS211-141/index.html&lang=en&request_locale=en] 06/30/2014 4.0.1 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21642813] 4.0.0 Traditional 06/2011 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/1/897/ENUS211-141/index.html&lang=en&request_locale=en] 09/30/2013 4.0.0 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21612021] 3.8.2 Traditional 12/2010 [https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS211-284] 09/30/2013 3.8.2 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21612021] 3.8.1", "Traditional 06/2010 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS210-108/index.html&lang=en&request_locale=en] 12/31/2012 3.8.1 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21511811] 3.8.0 Traditional 11/2009 [https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS109-581] 09/30/2012 3.8.0 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21511811] 3.7.3 Traditional 04/2009 12/31/2011 3.7.3 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21457788] 1.0.0 Traditional 12/2008 12/31/2010 1.0.0 Announcement Archived 3.7.2 Traditional 12/2008 12/31/2010 3.7.2 Announcement Archived 3.7.1 Traditional 08/2008 08/31/2010 3.7.1 Announcement Archived 3.7.0 Traditional 07/2008 08/31/2010 3.7.0 Announcement Archived 3.6.1 Traditional 12/2007 12/31/2009 3.6.1 Announcement Archived 3.6.0 Traditional 10/2006 08/31/2009 3.6.0", "Announcement Archived 3.5.1 Traditional 06/2006 02/28/2009 3.5.1 Announcement Archived", "Notes:", "* For information on current DataPower firmware versions, see Supported Firmware versions and recommended upgrade levels for IBM DataPower Gateways \".\n * Refer to the Contact Support [http://www.ibm.com/support/docview.wss?uid=swg21236322] page for how to reach IBM DataPower Gateways Support.\n * Customers are responsible for completing migration activities to currently supported levels before a release level reaches end-of-support.\n * Short duration support extensions are available on a case-by-case basis, for an additional fee, immediately following the end-of-support for a specific firmware level. Extensions would be for a very limited time period with limited terms and conditions. An extension is intended to provide support while customers complete their migration to a supported release.\n\n[https://www-prd-trops.events.ibm.com/sites/default/files/support/swg/swgtech.nsf/0/ec1cbaaf35990704852571f0006aa83d/Content/0.528A.jpg]" ]

[ "Effective with DataPower Gateway firmware V7.6 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS217-265&appname=USN], DataPower introduces a Continuous Delivery (CD) model to accelerate delivery of new capabilities and meet market needs. DataPower CD will consist of two releases:\n\n 1. CD release approximately once per quarter * Only the most recent CD release is supported at a given time.\n \n \n 2. Long Term Support (LTS) release every 12 months." ]

[ 2 ]

[ "IBM How to format server trace using ARSTFMT on Content Manager OnDemand 8.5.x.x and 9.0.x.x on Windows platform - United States server trace; ARSTFMT; Content Manager OnDemand TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Formatting CMOD V8.5.x.x and 9.0.x.x Server traces on Windows platform \n\nSYMPTOM\nCMOD Server trace output is unreadable\n\n\nCAUSE\nIn CMOD V8.5.0.0 and later, the trace file is written in binary. To convert the trace file from its binary format, use the ARSTFMT command found in the bin directory of your OnDemand server V8.5 and later installation.\n\nENVIRONMENT\nWindows\n\nRESOLVING THE PROBLEM\nOpen command prompt - navigate to the CMOD\\9.0\\bin directory and issue ARSTFMT as follows:\n\narstfmt -i C:\\Users\\IBM_ADMIN\\path\\to\\file -o C:\\Users\\IBM_ADMIN\\path\\to\\file\\name.txt\n\n\n\n\nwhere the C:\\Users\\IBM_ADMIN\\path\\to\\file is the unreadable trace file and C:\\Users\\IBM_ADMIN\\path\\to\\file\\name.txt is the name of the formatted trace file.", "RELATED INFORMATION\n Enable ODWEK tracing [http://www-01.ibm.com/support/docview.wss?uid=swg21240220]\nHow to enable trace in Content Manager OnDemand server [http://www-01.ibm.com/support/docview.wss?uid=swg21330810]" ]

[ "Open command prompt - navigate to the CMOD\\9.0\\bin directory and issue ARSTFMT as follows:\n\narstfmt -i C:\\Users\\IBM_ADMIN\\path\\to\\file -o C:\\Users\\IBM_ADMIN\\path\\to\\file\\name.txt\n\n\n\n\nwhere the C:\\Users\\IBM_ADMIN\\path\\to\\file is the unreadable trace file and C:\\Users\\IBM_ADMIN\\path\\to\\file\\name.txt is the name of the formatted trace file." ]

[ 0 ]

[ "IBM web server Plugin may need LD_LIBRARY_PATH when used with Apache 2.2 - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM web server Plug-in provides the connection between the web server tier and the IBM WebSphere Application Server (WAS) tier.\n\nWhen using Apache 2.2 web server on Linux operating systems, the IBM web server Plug-in may need to have the LD_LIBRARY_PATH environment variable set in a certain way, in order to be able to locate the IBM Global Security Kit (GSKit) libraries needed for SSL (HTTPS).\n\nWithout the GSKit libraries, the IBM web server Plug-in will be unable to initialize SSL, and will use only HTTP for connections to the WAS appservers. \n\nSYMPTOM\nDuring web server start-up, errors like the following will be logged into the Plug-in log file (http_plugin.log):", "ERROR: lib_security: loadSecurityLibrary: Failed to load gsk library from /opt/IBM/WebSphere/Plugins/gsk8/gsk8_64\nERROR: ws_transport: transportInitializeSecurity: Unable to load security library\nERROR: ws_server: serverAddTransport: Failed to initialize security\nERROR: ws_server: serverAddTransport: HTTPS Transport is skipped\n\n\nRESOLVING THE PROBLEM\nTo resolve the problem, you must set the LD_LIBRARY_PATH environment variable to point to the library directory of the GSKit that comes with the IBM web server Plug-in. The precise directory location will depend of the version of Plug-in, and on the bit depth being used (32-bit or 64-bit). \n\n \n\nFor example..... \n\nIf you installed the 32-bit Plug-in v7.0 and are using with a 32-bit Apache 2.2, use this: \n\nexport LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk7/lib/ \n\n \n\nIf you installed the 64-bit Plug-in v7.0 and are using it with a 32-bit Apache 2.2, use this: \n\nexport LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk7/gsk7_32/lib/", "If you installed the 64-bit Plug-in v7.0 and are using it with a 64-bit Apache 2.2, use this: \n\nexport LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk7/gsk7_64/lib64/ \n\n \n\nIf you installed the 32-bit Plug-in v8.x and are using with a 32-bit Apache 2.2, use this: \n\nexport LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk8/lib/ \n\n \n\nIf you installed the 64-bit Plug-in v8.x and are using it with a 32-bit Apache 2.2, use this: \n\nexport LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk8/gsk8_32/lib/ \n\n \n\nIf you installed the 64-bit Plug-in v8.x and are using it with a 64-bit Apache 2.2, use this: \n\nexport LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk8/gsk8_64/lib64/ \n\n \n\n \n\nPlease note that for Apache 2.2 on Linux, simply setting the LD_LIBRARY_PATH environment variable from the command line prior to starting the web server, MAY NOT WORK. In that case, you must set this variable as follows...\n\nFor SLES and SUSE Linux add the export command into the /usr/sbin/envvars file.", "For RHEL Linux add the export command into the /etc/sysconfig/httpd file.\n\nBy adding the export command into the files shown above, it means that the environment variable will be set when the web server is started. That will enable the Plug-in to be able to locate the appropriate GSKit libraries and be able to initialize SSL transports. \n\n\n\nRELATED INFORMATION\n#Web server plug-in setupGSKitLibPath script contains in [http://www-01.ibm.com/support/docview.wss?uid=swg21441018]" ]

[ "To resolve the problem, you must set the LD_LIBRARY_PATH environment variable to point to the library directory of the GSKit that comes with the IBM web server Plug-in. The precise directory location will depend of the version of Plug-in, and on the bit depth being used (32-bit or 64-bit)." ]

[ 1 ]

[ "IBM NoClassDefFoundError running Java class selected from server plugin jar - United States wid; noclassdeffounderror; java; jar TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The visual snippet editor allows you to search and find methods in classes available only on a restricted basis at runtime. A runtime exception occurs when the Java™ snippet calls a method in a class found in one of the plugin JARs in the server's plugins directory. \n\nCAUSE\nSome of the Java methods found in the JARs in the server's plugin directory are available to be called, but some of them are considered internal use only and an exception is thrown if you try to call them from user code.\n\nDIAGNOSING THE PROBLEM\nA runtime exception is detected in the server log naming a class and method called from a visual snippet in the application.", "RESOLVING THE PROBLEM\nThe reason the method you selected in the snippet editor cannot be called in the JAR in the plugins directory is because of the architecture of the server. JARs in the plugins directory have a list that specifies what classes in the JAR can be called. This is called the exports list, and it is honored by the class loader the server uses. Classes not on the list are considered internal use only. Thus, not all classes in the server plugin JARs are available to be called by user code. \n\nYou can call any method when the JAR is in the server's library directorym because it is not being treated as a plugin and a different class loader is used, one which does not implement the exports list.", "The snippet editor is not aware of this mechanism so it treats a plugin JAR the same as a regular Java JAR file. That is it allows you to select the (unavailable) class and method to call in your program. The resolution is to make sure that classes you call in plugin JARs appear on the exports list. \n\nFor example you may search for StringUtils and find the class org.apache.commons.lang.StringUtils in the WebSphere JAR plugin/com.ibm.ws.jpa.jar. This class is used internally by the plugin and it is not exported. In this case you must download the class you need directly from Apache and place the JAR in the server's classpath." ]

[ "Some of the Java methods found in the JARs in the server's plugin directory are available to be called, but some of them are considered internal use only and an exception is thrown if you try to call them from user code." ]

[ 0 ]

[ "IBM ITCAM for Microsoft (R) App : SQL Server 6.3.1.8-TIV-ITM_SQL-IF0001 - United States KOQ; OQ DOWNLOADABLE FILES\n\nABSTRACT\n This fix resolves the APARs and defects listed in the \"Problems Fixed\" \n\nDOWNLOAD DESCRIPTION\nCopyright International Business Machines Corporation 2016. \n\n\nAll rights reserved.\n\nComponent: IBM(R) Tivoli(R) Composite Application Manager for Microsoft(R) Applications:\nMicrosoft(R) SQL Server Agent, Version 6.3.1.8\n\nComponent ID: 5724B96MO\n\nInterim Fix 0001, (6.3.1.8-TIV-ITM_SQL-IF0001)\n\nDate: March 30, 2016\n\nContents:\n\n1.0 General description\n2.0 Problems fixed\n3.0 Architecture and prerequisites\n4.0 Image directory contents\n5.0 Installation instructions\n6.0 Additional installation information\n7.0 Known problems and workarounds\n8.0 Additional product information\n9.0 Notices\n\n\n1.0 General description\n=======================\nThis fix resolves the APARs and defects listed in the \"Problems Fixed\"\nsection below.", "2.0 Problems fixed\n==================\n2.1 APARS:\n-------------------\nAPAR: IV79406\nAbstract: Duplicated entries of SQL Server on TADDM portal.\nAdditional Information: SQL Server instance discovered from ITM \nDLA and TADDM Sensor was not reconciling on TADDM \nand duplicates were seen. The reason for duplicates\nwas that the DLA naming rules were not matching \nwith the Sensors naming rules.\n\nAPAR: IV82234 \nAbstract: False databases are reported as Suspected.\nAdditional Information: The data collected for Database Detail is written\nin <InstanceName>_DBD_PREV file. Due to improper file handling the \ncollector logs were written into this file which was causing collector \nlogs to be seen on the portal and triggering false alerts.\n\n2.2 DEFECTS:\n-----------------\nDEFECT: 138512\nAbstract: Improvement of table detail (KOQTBLD) algorithm.\nAdditional Information: The Table Detail information is now sorted \nbased on COLL_TBLD_SORTBY.", "DEFECT: 138519\nAbstract: Default instance of SQL Server is identified as 'MSSQLSERVER' \ninstead of hostname.\nAdditional Information: The default instance of SQL server used to get \nconfigured with hostname and not MSSQLSERVER. \nIn an environment, where there was default instance and \na named instance having same name as hostname had issues \nin configuration.\n\nDEFECT: 140838\nAbstract: Collector process crashes when collecting Statistics Summary\nattribute group.\nAdditional Information: There was an access violation exception as agent\nis trying to read from the memory that is already freed up.\n\n2.3 Superseded fixes\n--------------------\nNone\n\n2.4 APARs and defects included from superseded fixes\n----------------------------------------------------\nNone", "3.0 Architecture and prerequisites\n==================================\nThis fix is supported on all operating systems listed in the \nIBM Tivoli Monitoring: Microsoft SQL Server agent prerequisites Document,\nversion 6.3.1 or from the following link:\nhttp://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=A54AA300920511E292EE9F030925FE1B&duComponent=Server_A5707A80920511E292EE9F030925FE1 [http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=A54AA300920511E292EE9F030925FE1B&duComponent=Server_A5707A80920511E292EE9F030925FE1]\n\n\nThe following link is for the Tivoli operating system and application\nsupport matrix. Please refer to this matrix for the latest \ncertification information.\n\nhttp://www-969.ibm.com/software/reports/compatibility/clarity/index.html [http://www-969.ibm.com/software/reports/compatibility/clarity/index.html]", "3.1 Prerequisites for this fix\n------------------------------\nThe prerequisite level for this fix is as follows:\n\nLocal Agent Upgrade: \n- ITCAMMA: Monitoring Agent for Microsoft SQL Server, Version 6.3.1.8 \n\nRemote Agent Upgrade:\n- IBM Tivoli Monitoring, Version V6.23 Fix Pack 3 with OS Support\n- ITCAMMA: Monitoring Agent for Microsoft SQL Server, Version 6.3.1.8 \n- Monitoring Agent for Windows OS, Version V6.23 Fix Pack 3\n\nAs this fix is cumulative, it can be installed on any fix level for this version,\nrelease and mod level above the prerequisite.\n\n\n4.0 Image directory contents\n============================\nThis fix image contains the following files:\n\n- 6.3.1.8-TIV-ITM_SQL-IF0001.README - This is the README file\n- 6.3.1.8-TIV-ITM_SQL-IF0001.tar - Fix archive .tar format\n- 6.3.1.8-TIV-ITM_SQL-IF0001.zip - Fix archive .zip format", "Note: The .tar and .zip files are identical in content. Use the .tar\nfile if you are working in a UNIX(R) environment; use the .zip file\nif you are working in a Windows(R) environment.\n\nThe fix archive file contains the following files:\n6.3.1.8-TIV-ITM_SQL-IF0001/koq_tems_teps_tepd_if0001.tar\n6.3.1.8-TIV-ITM_SQL-IF0001/koq_tems_teps_tepd_if0001.zip\n6.3.1.8-TIV-ITM_SQL-IF0001/KOQ_winnt_tema_if0001.cab\n6.3.1.8-TIV-ITM_SQL-IF0001/KOQ_wix64_tema_if0001.cab\n6.3.1.8-TIV-ITM_SQL-IF0001/KOQWINNT.dsc\n6.3.1.8-TIV-ITM_SQL-IF0001/KOQWIX64.dsc\n6.3.1.8-TIV-ITM_SQL-IF0001/oq_dd.properties\n6.3.1.8-TIV-ITM_SQL-IF0001/oq_dd_063108001.xml\n6.3.1.8-TIV-ITM_SQL-IF0001/itmpatch.exe\n\n\n5.0 Installation instructions\n=============================\nThis fix can only be installed over an existing installation. \nUse the following steps to install this fix.", "5.1 Before installing the fix\n-----------------------------\n- The prerequisites listed under section 3.1 entitled 'Prerequisites\nfor this fix' must be installed before this fix can be installed.\n\n- With reference to this README, the symbol <CANDLEHOME> is the\nIBM Tivoli Monitoring installation directory. The default value\nfor CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\\IBM\\ITM'\non Windows systems.\n\nBefore installing this fix on UNIX systems, set the environment\nvariable CANDLEHOME to the IBM Tivoli Monitoring installation\ndirectory.\n\nFor example:\n> CANDLEHOME=/opt/IBM/ITM\n> export CANDLEHOME\n\n- Refer to section 7.0 entitled \"Known problems and workarounds\"\nbefore installation.\n\n- Because there is no uninstall utility for this fix, make sure to\nperform a backup of your environment before installing this fix.", "5.2 Local agent update\n----------------------\n1. Transfer the appropriate archive file\n(6.3.1.8-TIV-ITM_SQL-IF0001.tar or .zip) to a temporary directory\non the system that contains the agent code to be updated. For\nthe purpose of this README, the symbol <TEMP> represents the\nfully qualified path to this directory.\nNote: On Windows systems, this path includes the drive letter.\n\n2. Expand the archive file using the \"tar\" command on UNIX systems\nor an extract utility on Windows systems. This step creates a\ndirectory structure that contains fixes for all of the \nsupported platforms.\n\n3. Use the \"itmpatch\" command to install the fix for that agent\nplatform. For more information on the \"itmpatch\" command, see\nsection 6.2.\n\nOn Windows systems, if the fix was expanded to\n<TEMP>\\6.3.1.8-TIV-ITM_SQL-IF0001, the install command is:\n\nFor 32 bit Agent:\n> <TEMP>\\6.3.1.8-TIV-ITM_SQL-IF0001\\itmpatch -h <CANDLEHOME>\n-i <TEMP>\\6.3.1.8-TIV-ITM_SQL-IF0001\\KOQ_winnt_tema_if0001.cab", "For 64 bit Agent:\n> <TEMP>\\6.3.1.8-TIV-ITM_SQL-IF0001\\itmpatch -h <CANDLEHOME> \n-i <TEMP>\\6.3.1.8-TIV-ITM_SQL-IF0001\\KOQ_wix64_tema_if0001.cab\n\nNote : Use \"itmpatch\" command from <TEMP>\\6.3.1.8-TIV-ITM_SQL-IF0001\\ \ntemporary directory.\n\n5.3 Remote agent update\n-----------------------\n1. Transfer the appropriate archive file\n(6.3.1.8-TIV-ITM_SQL-IF0001.tar or .zip) to a temporary directory\non the IBM Tivoli Enterprise Monitoring Server system. For the\npurpose of this README, the symbol <TEMP> represents the fully\nqualified path to this directory.\nNote: On Windows systems, this path includes the drive letter.\n\n2. Expand the archive file using the \"tar\" command on UNIX systems\nor an extract utility on Windows systems. This step creates a \ndirectory structure that contains fixes for all of the \nsupported platforms.", "3. To add the agent fix bundles into the remote deploy depot, use\nthe \"tacmd addBundles\" command found in $CANDLEHOME/bin on UNIX\nsystems or in %CANDLE_HOME%\\bin on Windows systems. For more\ninformation on the \"tacmd addBundles\" command, see the IBM Tivoli\nMonitoring Administrator's Guide.\n\nOn UNIX systems,\nif the fix was expanded to <TEMP>/6.3.1.8-TIV-ITM_SQL-IF0001:\n> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.3.1.8-TIV-ITM_SQL-IF0001\n\nOn Windows systems,\nif the fix was expanded to <TEMP>\\6.3.1.8-TIV-ITM_SQL-IF0001:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -n -i <TEMP>\\6.3.1.8-TIV-ITM_SQL-IF0001\n\nwhere:\n-n indicates that prerequisite bundles are not automatically\nadded. The -n parameter must be used because the fix \ndirectory does not contain any prerequisites that the fix\nmight require. Please see Section 3.1 for the prerequisites\nfor this fix.\n-i is the directory that contains the deployment bundles to \nbe added to the depot.", "4. To log in to the Tivoli Enterprise Monitoring server, and deploy\nthe fix to the appropriate nodes where the agent is running, use\nthe following \"tacmd\" commands. For more information on the\n\"tacmd login\" and \"tacmd updateAgent\" commands, see \"IBM Tivoli \nMonitoring Command Reference\".\n\nOn UNIX systems: \n> $CANDLEHOME/bin/tacmd login -s <server>\n-u <itmuser>\n-p <password>\n\n> $CANDLEHOME/bin/tacmd listSystems\n\nThe output shows the Managed System Name for the OS agent on the\nremote system to be updated. Use this value as the target of the\n\"tacmd updateAgent\" command.\n\n> $CANDLEHOME/bin/tacmd updateAgent -t OQ -n <Managed system name> -v 063108001\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.", "> %CANDLE_HOME%\\bin\\tacmd updateAgent -t OQ -n <Managed system name> -v 063108001\n\nNote:\n- The component (-t) for the \"tacmd updateAgent\" command is \nspecified as two characters (oq), not three characters (koq).\n- The node (-n) for the \"tacmd updateAgent\" command is the\nmanaged system name of the operating system (OS) agent to be\nupdated.\nThe target node for the \"tacmd updateAgent\" command is always\nan OS agent.\n\n5. To check if Remote Agent Update is SUCCESS/INPROGRESS/FAILED use the command \n>tacmd getDeployStatus <transaction id>\n\nwhere transaction id is the id provided after updateAgent command.\n\n5.4 Agent support update\n------------------------\nUse the following steps to update the Tivoli Enterprise Monitoring Server, \nTivoli Enterprise Portal Server, or Tivoli Enterprise Portal Desktop.", "1. Transfer the appropriate archive file\n6.3.1.8-TIV-ITM_SQL-IF0001.tar or .zip) to the \nTivoli Enterprise Monitoring Servers, Tivoli Enterprise Portal Servers\nor Tivoli Enterprise Portal Desktops.\n\n2. Expand the archive file using the \"tar\" command on UNIX systems\nor an extract utility on Windows systems. This step creates a \ndirectory structure that contains fixes for all of the supported\nplatforms.\n\n3. Expand the archive file (koq_tems_teps_tepd_if0001.tar or .zip)\nthat contains the updates for Tivoli Enterprise Monitoring Server, \nTivoli Enterprise Portal Server, and Tivoli Enterprise Portal Desktop \nusing the \"tar\" command on UNIX systems or an \nextract utility on Windows systems. This step creates a \ndirectory structure that includes a subdirectory called CD-ROM,\nwith the necessary updates.\n\n4. Use the Application Support Installer(ASI) script to launch either \nGUI installation or silent installation of the application \nsupport files.", "Note: For IBM Tivoli Monitoring Version 6.3 or above, one\nof the following additional steps must be performed.\n\n1. Acquire a platform-specific pre-packaged JRE version \nof the Application Support Installer (ASI). See IBM \nTivoli Monitoring Application Support Installer, \n6.2-TIV-ITM_ASI-IF0002 at \nhttp://www-01.ibm.com/support/docview.wss?uid=swg24034924 [http://www-01.ibm.com/support/docview.wss?uid=swg24034924]\nfor download and installation instructions.\n\n2. Specify the '-j javahome' parameter with the path to \na java(r) 1.5 or java 1.6 installation when running \nthe itmasi.sh or itmasi.bat script described below. \n\nGUI installation option\n------------------------\nThe GUI can be started by using one of the following commands\nfrom within the CD-ROM directory where setup.jar is located.\n\nOn UNIX systems:\n> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>] \n\nOn Windows systems:\n> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]", "where:\n-h <CANDLEHOME> - Required. The path to the IBM Tivoli\nMonitoring installation directory.\n\n-j <JAVAHOME> - Optional. The fully-qualified path to the\n\"bin\" directory where Java(R) is installed.\nThe location of Java on your system might\nvary.\n\nWhen prompted by the Application Support Installer for the \ninstallable media directory, select the CD-ROM directory, not\nthe component directory. The installer can install updates for \nmultiple components at the same time.\n\nSilent installation option\n--------------------------\nTo use the silent installation option, use one of the following\ncommands from within the CD-ROM directory where setup.jar is \nlocated.", "Note: Agent support upgrade for IBM Tivoli Monitoring Version 6.3 \nor above on Linux, zLinux, Solaris and windows operating systems \nrequires the following files contained in interim fix \n6.2-TIV-ITM_ASI-IF0002. This is applicable to both GUI and \nsilent installation option of agent support upgrade.\n- Linux: setupLinux.bin\n- zLinux: setupLinux390.bin\n- Solaris: setupSolaris.bin\n- Windows: setupwin32.exe\n\nFollow the installation instructions contained in the\n\"6.2-TIV-ITM_ASI-IF0002.README\".\n\nOn UNIX systems:\n> ./itmasi.sh -h <CANDLEHOME>[-silent] \n[-r <response file>] \n[-j <JAVAHOME>] \n\nOn Windows systems:\n> itmasi -h <CANDLEHOME> [-silent] \n[-r <response file>] \n[-j <JAVAHOME>] \n\nwhere:\n-h <CANDLEHOME> - Required. The path to the IBM Tivoli\nMonitoring installation directory.\n\n-r <response file> - Required. Customized response file name.\nThe default response file \"response.txt\" in\nthe CD-ROM directory can be copied and\nmodified as per your environment.", "-j <JAVAHOME> - Optional. The fully-qualified path to the\n\"bin\" directory where Java(R) is installed.\nThe location of Java on your system might\nvary.\n\n5. The next panel presented by the Application Support Installer \nasks for the selection of which Tivoli Monitoring components\nyou want to add application support to.\nFor this fix, the check boxes should be set as follows:\n\nUnchecked - Tivoli Enterprise Monitoring Server(TEMS)\nChecked - Tivoli Enterprise Portal Server(TEPS)\nChecked - Tivoli Enterprise Desktop Client(TEPD)\n\nContinue through the remaining GUI panels selecting the\nMicrosoft SQL Server 06.31.08.01 support to complete the\ninstallation.\n\nNote: When support is installed using CLI or GUI for any of the\nabove Tivoli Monitoring components, they are restarted. \n\n\n6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise\nPortal Browser was running when the update was installed, it\nmust be restarted.", "6.0 Additional installation information\n=======================================\nAny existing Microsoft SQL Server Agent instances should be restarted\nafter the installation of this fix.\n\n6.1 Installation instructions for agent baroc file\n--------------------------------------------------\nFix (6.3.1.8-TIV-ITM_SQL-IF0001) includes changes to the agent\nbaroc files which need to be reinstalled. If you have already\ninstalled these baroc files, there are no additional installation\nsteps. If not, refer to IBM Tivoli Monitoring, Installation\nand Setup Guide under \"Installing monitoring agent baroc files\non the event server\" in \"Installing the IBM Tivoli Enterprise\nConsole Event Synchronization\" section for more information.\n\n6.2 Additional information on using \"itmpatch\" command\n----------------------------------------------------\nThe \"itmpatch\" command has the following syntax.\n\nUsage: itmpatch -h <installation home> [OPTIONS]", "itmpatch -h <installation home>\n-t { <patch_file_directory> | <patch_file> }\n\nitmpatch -h <installation home>\n-i { <patch_file_directory> | <patch_file> }\n\nwhere:\n-h Specifies the IBM Tivoli Monitoring installation directory\n-i Specifies the path to the directory or patch file to be \ninstalled\n-t Generates a report of the actions to be taken by the patch\n\nFor example, on UNIX systems:\n- To preview the fix installation, use the \"-t\" option:\n> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>\n\n- To install the fix, use the \"-i\" option:\n> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>\n\nwhere:\n<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring \ninstallation directory. On Windows systems, this path must include\nthe drive letter.\n<TEMP> represents the fully qualified directory specification where\nthe fix is located. On Windows systems, this must include the drive\nletter.", "6.3 Verifying the update\n------------------------\n1. To verify the agent was updated correctly, use the \"tacmd\" command\nto view the agent's current version after the agent is restarted.\nYou are required to log in to a Tivoli Enterprise Monitoring\nServer prior to viewing the agent version.\n\nFor example:\nOn UNIX systems, where $CANDLEHOME is the IBM Tivoli \nMonitoring installation directory, the default location\nis '/opt/IBM/ITM'.\n\n> $CANDLEHOME/bin/tacmd login -s <server>\n-u <itmuser>\n-p <password>\n> $CANDLEHOME/bin/tacmd listSystems -t OQ\n\nOn Windows systems, where %CANDLE_HOME% is the IBM Tivoli\nMonitoring installation directory, the default location\nis 'C:\\IBM\\ITM'.\n\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> %CANDLE_HOME%\\bin\\tacmd listSystems -t OQ \n\nNote:\n- The component (-t) for the tacmd \"listSystems\" command is \nspecified as two characters (OQ), not three characters (KOQ).\n\nWhen the agent update is successful, the agent version is:\n06.31.08.01.", "After the agent is restarted, you can also use the GUI to verify\nthe agent was successfully updated.\nFor the agent on Windows systems, the version number is \n06.31.08.01.\n\n2. To verify the agent support files were updated correctly, use \nthe \"kincinfo\" command on Windows systems or the \"cinfo\" command\non Linux or UNIX systems. The sample output below shows the \nversions of the Tivoli Enterprise Portal Server, Tivoli \nEnterprise Monitoring Server, or Tivoli Enterprise Portal\nDesktop systems after this fix has been successfully applied.\n\nNote: The displayed build date and installation date might not \nbe accurate. This is known problem.\n\nOn UNIX or Linux systems:\n-------------------------\nTo validate that all components have been installed, run the\nfollowing command:\n\n./cinfo -i\n\nOn Windows systems:\n-------------------\nTo validate that all components have been installed, run the\nfollowing command:\n\nFor example:\n> %CANDLE_HOME%\\InstallITM\\kincinfo -i", "C:\\Users\\Administrator>kincinfo -i\n************* Monday, March 21, 2016 6:18:11 PM *************\nUser : Administrator Group : NA\nHost Name : ESX1-SQL-T-9 Installer : Ver: 063004000\nCandleHome : C:\\IBM\\ITM\nInstallitm : C:\\IBM\\ITM\\InstallITM\n*************************************************************\n...Product Inventory\nOQ TEMS App Support/Microsoft SQL Server Support\nWINNT Version: 06.31.08.00 Build: 60071\n\nOQ TEPS App Support/Microsoft SQL Server Support\nWINNT Version: 06.31.08.01 Build: 60711\n\nOQ TEPB App Support/Microsoft SQL Server Support\nWINNT Version: 06.31.08.00 Build: 60071\n\nOQ TEPD App Support/Microsoft SQL Server Support\nWINNT Version: 06.31.08.01 Build: 60711\n\n\n\n7.0 Known problems and workarounds\n==================================\nAbstract: itmpatch command fails during upgrade\nProblem: When itmpatch command is executed, it fails while upgrading\nagent fix pack. The following error message is \ndisplayed:", "Version 06.31.08.XX of product koq is currently installed.\nThe patch requires that you must have at least version\n06.31.08.XX of product installed to apply this patch.\nWorkaround: Use the itmpatch.exe provided in patch file \n6.3.1.8-TIV-ITM_SQL-XXXXXX.zip or \n6.3.1.8-TIV-ITM_SQL-XXXXXX.tar file.\n\nAbstract: English characters are getting displayed in Agent support \ninstaller having Non-English language operating system.\nProblem: In Non-English language operating system, when agent \nsupport installer is executed it shows English characters.\nWorkaround: None", "Abstract: Installing support for patch fails on ITM 6.3.0\nProblem: When you try to install the support for this patch on ITM\n6.3.0, the installation fails with following error:\nThe wizard cannot continue because of the following error: \ncould not load wizard specified in /wizard.inf (104)\nWorkaround: Use the pre-packaged binaries for itmasi available at:\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24034924 [http://www-01.ibm.com/support/docview.wss?uid=swg24034924]\n\nAbstract: Crash encountered in event viewer for koqagent.exe\nProblem: Sometimes while stopping the koqagent process, the collection\nprocess is not getting completed. When koqagent.exe stops, the\nthread spawned by it gets terminated forcefully. Hence it's\ncausing a crash.\nWorkaround: None", "Abstract: Application support installation fails on Non Windows OS.\nProblem: While installing the application support on the machines\nhaving Operating system other than windows, the support\ninstallation using ASI fails if the temporary directory \nwhere the patch files are extracted has spaces.\nWorkaround: Use the temporary directory without space.\n\nAbstract: MSSQL Agent collector crashes.\nProblem: Sometimes the job 'syspolicy_purge_history' fails and \nthe collector crashes.\nWorkaround: 1. Disable scheduling of system job 'syspolicy_purge_history'.\n2. Disable detail trace logging.", "Abstract: MSSQL Agent collector process keeps on restarting.\nProblem: If the default instance is configured before patch upgrade then \nafter patch upgrade the collector process keeps on restarting \nWorkaround: In this patch, the name of default instance is changed from \nHOSTNAME to MSSQLSERVER (Defect 138519). Hence, the previously \nconfigured default instance with name as HOSTNAME will not \nwork properly. So, it is required to unconfigure default \ninstance (with name hostname) and configure it with name as \nMSSQLSERVER.", "Following are the steps to unconfigure and configure:\n1. Open Manage Tivoli Enterprise Monitoring Services \n(MTEMS) window. \n2. Right click on template row and go to \n\"Configure Using Defaults\".\n3. Select the default instance with name as HOSTNAME \nfrom 'Server To Monitor' list box and click on \">>\" button \nto unconfigure it.\n4. Select the instance with name 'MSSQLSERVER' in \n'Database Servers Available' list box and click on \"<<\" button\nto configure this instance.\n5. Set the configuration parameters and start the agent.\n\nAbstract: KOQ.SAVE registry is created for 631FP8 agent\nProblem: When a configured instance is un-configured or 631FP8 agent is \nuninstalled, the KOQ.SAVE registry is created.\nWorkaround: In case of upgrade to 6318IF1, manually delete the \nKOQ.SAVE registry. \n\n\n8.0 Additional product information\n==================================\nNone", "9.0 Notices\n===========\nThis information was developed for products and services offered in \nthe United States. IBM may not offer the products, services, or \nfeatures discussed in this document in other countries. Consult your\nlocal IBM representative for information on the products and services\ncurrently available in your area. Any reference to an IBM product, \nprogram, or service is not intended to state or imply that only that\nIBM product, program, or service may be used. Any functionally \nequivalent product, program, or service that does not infringe any \nIBM intellectual property right may be used instead. However, it is \nthe user's responsibility to evaluate and verify the operation of any\nnon-IBM product, program, or service.\n\nIBM may have patents or pending patent applications covering subject\nmatter described in this document. The furnishing of this document \ndoes not grant you any license to these patents. You can send license\ninquiries, in writing, to:", "IBM Director of Licensing\nIBM Corporation\nNorth Castle Drive\nArmonk, NY 10504-1785\nU.S.A.\n\nThe following paragraph does not apply to the United Kingdom \nor any other country where such provisions are inconsistent \nwith local law:\n\nINTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION \n\"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, \nINCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF \nNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.\n\nSome states do not allow disclaimer of express or implied warranties\nin certain transactions, therefore, this statement may not apply \nto you.", "Trademarks and service marks\n----------------------------\nIBM, the IBM logo, and ibm.com are trademarks or registered trademarks\nof International Business Machines Corp., registered in many\njurisdictions worldwide. Other product and service names might be\ntrademarks of IBM or other companies. A current list of IBM trademarks \nis available on the Web at \"Copyright and trademark information\" at \nwww.ibm.com/legal/copytrade.shtml [www.ibm.com/legal/copytrade.shtml].\n\nMicrosoft, Windows, Windows NT, and the Windows logo are trademarks\nof Microsoft Corporation in the United States, other countries, or \nboth.\n\nJava and all Java-based trademarks are trademarks of Sun Microsystems, \nInc. in the United States, other countries, or both.\n\nUNIX is a registered trademark of The Open Group in the United States \nand other countries.\n\nLinux is a registered trademark of Linus Torvalds in the United States,\nother countries, or both.", "Other company, product, or service names may be trademarks or service\nmarks of others.\n\nPREREQUISITES\n- IBM Tivoli Monitoring, Version V6.23 Fix Pack 3 with OS Support\n- ITCAMMA: Monitoring Agent for Microsoft SQL Server, Version 6.3.1.8\n\nINSTALLATION INSTRUCTIONS\nPlease refer to the README contained in the 'Description' section above for general installation instructions.\n\nDOWNLOAD PACKAGE\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 6.3.1.8-TIV-ITM_SQL-IF0001 30-Mar-16 English 37159939 FC [http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?product=ibm/Tivoli/Tivoli+Composite+Application+Manager+for+Microsoft+Applications&function=fixId&fixids=6.3.1.8-TIV-ITM_SQL-IF0001&includeRequisites=1&includeSupersedes=0&downloadMethod=http] [ ] \nPRODUCT ALIAS/SYNONYM\n SQL Agent", "[/support/docview.wss?uid=swg24041994&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24041994&aid=2]Problems (APARS) fixed\nIV79406, IV82234" ]

[ "Abstract: Default instance of SQL Server is identified as 'MSSQLSERVER' \ninstead of hostname.\nAdditional Information: The default instance of SQL server used to get \nconfigured with hostname and not MSSQLSERVER. \nIn an environment, where there was default instance and \na named instance having same name as hostname had issues \nin configuration." ]

[ 2 ]

[ "IBM ERRORCODE=-4499, The application server rejected establishment of the connection. - United States -4499; JCC; SQL State = 08004; Error Code = -4; 499 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n \nAttempt to connect to a database using Type 4 JCC driver fails with the following exception:\n\njava.sql.SQLException: \n[jcc][t4][2057][11264][3.53.95] The application server rejected establishment of the connection. An attempt was made to access a database, <database name>, which was either not found or does \nnot support transactions. ERRORCODE=-4499, \nSQLSTATE=08004 DSRA0010E: SQL State = 08004, Error Code = -4,499 \n\n\n\nCAUSE\nUsing DCS DB alias or local alias name of the database in the connection string will cause this error.\n\nRESOLVING THE PROBLEM\n \n\nThe URL format for IBM Data Server Driver for JDBC and SQLJ type 4 connectivity is:\n\n\n * \"jdbc:db2://<server name>: <portnumber>/<database name>\";", "In the Type 4 JDBC JCC driver connection string used, \n * If the connection is to a DB2 for Linux,Unix,Windows server, the database name should be the Target database name in the database server, it should not be the local alias name cataloged in the client. \n * If the connection is to a DB2 for z/OS server, database name is the DB2 location name that is defined during installation. All characters in the DB2 location name must be upper-case characters. The IBM Data Server Driver for JDBC and SQLJ does not convert lower-case characters in the database value to upper-case for IBM Data Server Driver for JDBC and SQLJ type 4 connectivity. \n * The location name can be found by executing the following SQL statement on the server: * SELECT CURRENT SERVER FROM SYSIBM.SYSDUMMY1;\n \n \n The target database name can also be found from the DCS directory on the client using the command: * db2 list dcs directory.", "[/support/docview.wss?uid=swg21443723&aid=1] [/support/docview.wss?uid=swg21443723&aid=1] \nFor further discussion on this topic, visit this developerWorks forum thread: \nhttps://www.ibm.com/developerworks/community/forums/html/topic?id=1cd04237-a9dd-4061-9c38-f9043786691a [https://www.ibm.com/developerworks/community/forums/html/topic?id=1cd04237-a9dd-4061-9c38-f9043786691a] \nRELATED INFORMATION\n Type 4 JCC connection String: [http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.apdv.java.doc/src/tpc/imjcc_r0052342.html]" ]

[ "Using DCS DB alias or local alias name of the database in the connection string will cause this error." ]

[ 0 ]

[ "IBM Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects WebSphere Message Broker and IBM Integration Bus (CVE-2015-7575) - United States WMB IIB SECURITY BULLETIN\n\nSUMMARY\n The MD5 “SLOTH” vulnerability on TLS 1.2 affects WebSphere Message Broker and IBM Integration Bus", "VULNERABILITY DETAILS\nCVEID: CVE-2015-7575 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575]\nDESCRIPTION: The TLS protocol could allow weaker than expected security caused by a collision attack when using the MD5 hash function for signing a ServerKeyExchange message during a TLS handshake. An attacker could exploit this vulnerability using man-in-the-middle techniques to impersonate a TLS server and obtain credentials.\nCVSS Base Score: 7.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109415 [https://exchange.xforce.ibmcloud.com/vulnerabilities/109415] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Integration Bus V9, V10 \n\nWebSphere Message Broker V8\n\nREMEDIATION/FIXES\nFor users of ODBC SSL using the DataDirect drivers:", "You might be vulnerable to SLOTH vulnerability, if you have not applied APAR IT09602 released in August 2015. (Please refer the bulletin at \nhttp://www.ibm.com/support/docview.wss?uid=swg21958955 [http://www.ibm.com/support/docview.wss?uid=swg21958955] for more details)\n\n\n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus V10 IT09602 The APAR is available in fix pack 10.0.0.2 and above. IBM Integration Bus V9 IT09602 The APAR is available in fix pack 9.0.0.5 and above. WebSphere Message Broker \n\nV8\nIT09602 An interim fix is available from IBM Fix Central for all platforms.\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT09602 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT09602]", "The APAR is targeted to be available in fix pack 8.0.0.7. For unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product. \n\nYou should verify thst applying this fix does not cause any compatibility issues. The fix prevents the currently-practical SLOTH attack against the RSA-MD5 client authentication. IBM recommends that you avoid using ciphers which use an MD5 or SHA-1 signature hash. \n\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : \nhttp://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "IMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] ACKNOWLEDGEMENT\nReported to IBM by Karthikeyan Bhargavan at INRIA in Paris, France", "CHANGE HISTORY\n 23 Jan 2016 - Original version Published\n\n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.\n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21977747]", "Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Not Applicable AIX, HP-UX, Linux, Solaris, Windows 10.0, 9.0 \nPRODUCT ALIAS/SYNONYM\n WMB IIB" ]

[ "CVEID: CVE-2015-7575 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575]\nDESCRIPTION: The TLS protocol could allow weaker than expected security caused by a collision attack when using the MD5 hash function for signing a ServerKeyExchange message during a TLS handshake. An attacker could exploit this vulnerability using man-in-the-middle techniques to impersonate a TLS server and obtain credentials.\nCVSS Base Score: 7.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109415 [https://exchange.xforce.ibmcloud.com/vulnerabilities/109415] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N)" ]

[ 1 ]

[ "IBM Using the \"reinitialize\" CLI command to reconfigure an appliance. - United States datapower; init; initialize; reinitialize; reinit; reset; factory settings; settings; 7993; 7993; 7993; machine type 7993 DPRecovery TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n If you need to reconfigure an IBM WebSphere DataPower SOA appliance you can use the \"reinitialize\" CLI command. \n\nRESOLVING THE PROBLEM\nNote: The appliance should NOT be initialized if sitation described in the technote exists - http://www-01.ibm.com/support/docview.wss?uid=swg21659259 [http://www-01.ibm.com/support/docview.wss?uid=swg21659259] - appliance gets into Fail-Safe mode. It may be necessary to return the appliance to IBM for repair.\nThe reinit CLI command will allow you to reconfigure an IBM WebSphere DataPower SOA appliance. The reinit CLI command will allow you to delete (not erase) all existing configuration and data from an IBM WebSphere DataPower SOA appliance.", "When the reinitialize command completes, your network IP configurations, user accounts and other configuration options, are no longer accessible. \n\nYou will only be able to connect to the appliance using the serial connection. \n\nYou will need to configure your Ethernet and all other settings again using the information in the product information center available from our library page [http://www.ibm.com/software/integration/datapower/library/index.html].\n\nImportant points:", "* Make sure you have a working serial connection to the appliance. \n \n \n * The admin password will revert to the initial value of \"admin\" after the command executes.\n \n \n * A firmware image must be on the appliance prior to running the command. The firmware image used for the last upgrade of the device is removed from the file system automatically when the device reboots. Use DataPower's File Management WebGUI option to confirm you have an image or use these CLI commands:\n xi52# configure\n xi52# dir image:\n If an image file is not found, you will need to load a firmware image to the appliance into the image:/// directory. For example: you can use the WebGUI file management options or from the Control Panel, choose the System Control icon, the under Boot Image, choose the firmware file upload options.", "* Use the DataPower File Management to confirm you have sufficient file space. If you don't have sufficient file space, you can delete domains or other files to free up file space to allow the firmware image to be loaded to the appliance. \n \n \n * reinit is a CLI command available in the config-flash# mode, for example:\n \n xi52# configure terminal\n Global configuration mode \n xi52(config)# flash \n Flash configuration mode \n xi52(config-flash)#\n reinit <filename> \n \n Where <filename> represents a firmware image contained within the image:/// directory. This will be the firmware image which will be installed during the reinit process. For more CLI commands, refere to the following doc link:\n http://pic.dhe.ibm.com/infocenter/wsdatap/v5r0m0/nav/4_4 [http://pic.dhe.ibm.com/infocenter/wsdatap/v5r0m0/nav/4_4]", "* After the appliance reboots: * If the firmware image used was for V5 or newer, you will need to accept the license at first logon to the WebGui Configure the appliance per the instructions in the appliances configuration guide. This and other documentation on the appliance is available from our library page [http://www.ibm.com/software/integration/datapower/library/index.html].", "The command is documented in the information center. This and other documentation on the appliance is available from our library page [http://www.ibm.com/software/integration/datapower/library/index.html]. \n\nIf your appliance has the optional RAID (hard drives) reinitialize the RAID using the information in our RAID technote [http://www.ibm.com/support/docview.wss?uid=swg21358544]. \n\nIf your appliance has the optional HSM, reinitialize the HSM following the instructions in our HSM book or infocenter for your release of the product. These are available on our library page [http://www.ibm.com/software/integration/datapower/library/documentation/]. \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM DataPower Gateway Virtual Edition Business Integration IBM DataPower Gateways" ]

[ "The reinit CLI command will allow you to reconfigure an IBM WebSphere DataPower SOA appliance. The reinit CLI command will allow you to delete (not erase) all existing configuration and data from an IBM WebSphere DataPower SOA appliance." ]

[ 0 ]

[ "IBM Security Bulletin: The WebAdmin context for WebSphere Message Broker Version 8 allows directory listings (CVE-2016-6080) - United States WMB IIB SECURITY BULLETIN\n\nSUMMARY\n The WebAdmin context for WebSphere Message Broker Version 8 allows directory listings. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-6080 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6080]\nDESCRIPTION: The WebAdmin context for WebSphere Message Broker allows directory listings, which could disclose sensitive information to the attacker.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117560 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117560] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nWebSphere Message Broker V8\n\nREMEDIATION/FIXES", "Product VRMF APAR Remediation/Fix WebSphere Message Broker V8 IT16698 The APAR is available in Fix Pack 8.0.0.8\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24042925 [https://www-304.ibm.com/support/docview.wss?uid=swg24042925] \n\nFor unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product. \nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : \nhttp://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "IMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 1 Dec 2016 - Original version published", "*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.\n\n \n\nPRODUCT ALIAS/SYNONYM\n WMB IIB" ]

[ "CVEID: CVE-2016-6080 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6080]\nDESCRIPTION: The WebAdmin context for WebSphere Message Broker allows directory listings, which could disclose sensitive information to the attacker.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117560 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117560] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)" ]

[ 0 ]

[ "IBM Generating Java diagnostic dumps for IBM Integration Bus - United States mqiinfo; java dumps; java core; core; force TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Use the procedures below to collect java diagnostics dumps from IBM Integration Bus (IIB).\n\nJava diagnostic dumps contain:\n- all Java threads running in a process (Java core or javacore files)\n- objects populating the heap space (Heap dump or heapdump files)\n- tracepoint information (Snap trace or snaptrace files)\n- internal system information (System dump)\n\nThese files can be used to diagnose problems such as lock conditions, loops, or memory allocation in Java code. \n\nGathering this information before calling IBM Support will help familiarize you with the troubleshooting process and save you time. \n\nRESOLVING THE PROBLEM\n\n\nJAVACORE DUMP INSTRUCTIONS", "New javacore dump commands have been made available from IIB v10.0.0.9, onwards. \n- The new procedure uses the mqsichangeproperties command. \n- The old procedure uses a custom message flow, and is only applicable for operating systems that use the IBM JRE. \n\nNote: \nCollection of Java core dumps is an invasive activity and will impact the performance of the Integration Server process. \n\nJAVA DUMP COMMAND FOR IIB V10.0.0.9+\nUse this command to generate a Java dump on IIB v10.0.0.9+:\nmqsichangeproperties <Int.Node> -e <Int.Server> -o ComIbmInternalSupportManager/Java/JVM -n dump -v <dump_type>\n\nThe following dump types are supported:\n\nAll Platforms \n\n-v heap Produces a Java Heap dump \n\nIBM JRE Platforms (All platforms except HP and Solaris) -v core Produces a javacore -v system Produces a system dump -v all Produces a heapdump, javacore, and system dump \nDump files are output to $MQSI_WORKPATH/common/errors", "JAVA DUMP PROCEDURE FOR IIB PRIOR TO V10.0.0.9\nUse this procedure to create an IIB message flow that will trigger a Java dump for an Integration Server:\n\n1. Create a new message flow containing an Input node and a JavaCompute node.\n2. In the JavaCompute node, call the method 'com.ibm.jvm.Dump.JavaDump()'.\n3. Deploy your message flow to the target Integration Server.\n4. Recreate the conditions that necessitate the Java dump.\n5. Invoke your message flow by sending a message to the Input node.\n6. The dump files should be output to $MQSI_WORKPATH/common/errors.\n\nNote:\nThis procedure requires the use of the IBM JRE.\nTherefore, it is not suitable on Solaris or HP platforms which do not use the IBM JRE.", "RELATED INFORMATION\n Triggering a java dump [http://www.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.win.70.doc/diag/tools/javadump_trigger.html]\nEnabling a java dump [http://www.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.lnx.70.doc/diag/tools/javadump_enable.html]\n\n\n\n\nPRODUCT ALIAS/SYNONYM\n WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI IIB" ]

[ "Use this command to generate a Java dump on IIB v10.0.0.9+:\nmqsichangeproperties <Int.Node> -e <Int.Server> -o ComIbmInternalSupportManager/Java/JVM -n dump -v <dump_type>" ]

[ 1 ]

[ "IBM PI34677: MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION - United States A FIX IS AVAILABLE\nFixes integrated in WebSphere Portal 8.5.0.0 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24037786]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * During Portal Start-Up following error is shown:\n --------------------\n 0000005e MBeanStarter E com.ibm.wps.\n \n scripting.server.MBeanStarter loadExtensions failed to load\n extension:\n key: ServerExt.applications / value:\n com.ibm.wps.scripting.server.\n ApplicationServerExtensions", "LOCAL 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", "PROBLEM 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" ]

[ "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." ]

[ 1 ]

[ "IBM What are the supported Apple Macintosh Operating System Versions for IBM SPSS Statistics? - United States SPSS mac macintosh Apple Macintosh statistics OS supported version compatibility matrix leopard Snow Leopard Lion Mountain Lion 10.8 Mavericks 10.9 22 Yosemite 10.10 (Yosemite) el capitan 10.11 spss 24 Sierra 10.12 High Sierra 10.13 TECHNOTE (FAQ)\n\nQUESTION\n I would like to know what are the supported Macintosh Operating system versions for IBM SPSS Statistics versions? \n\nANSWER\nPlease see the list below. It is strongly recommended to review the platform information on IBM Software Product Compatibility Reports [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.jsp]. The installation of IBM SPSS Statistics software on Apple Macintosh OSX operating systems requires an Intel processor. \n\nA) Apple Macintosh MacOS High Sierra (10.13)", "Support for IBM SPSS Statistics 25 only. Please note that no other SPSS release will be officially supported on High Sierra, but older versions like SPSS Statistics 24 may run as well on High Sierra. \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.", "C) 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", "Note: 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", "- 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***", "Note: 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.", "RELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]" ]

[ "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." ]

[ 5 ]

[ "IBM FileNet Workplace XT war and ear files are unusually small - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When creating the IBM FileNet Workplace XT archive files with either the Content Platform Engine Client Files installation or the IBM Case Manager's \"Deploy IBM FileNet Workplace XT\" configuration manager task , the resulting war and ear files are only a few kilobytes in size and contain the create_web_client_war.sh and create_web_client_ear.sh files.\n\n\n\nDIAGNOSING THE PROBLEM\nThe ceclient_install_log or warerr.log file will contain the following error:\n\nERROR:\n\"create_web_client_war.sh[5]: cd: .WorkplaceXT: [No such file or\ndirectory]\"\n\nWhen attempting to install the resulting archive file to IBM WebSphere Application Server, the following error is returned.\n\nIWAE0006E Archive is not a valid WAR File because the deployment descriptor can not be found (case sensitive): WEB-INF/web.xml", "RESOLVING THE PROBLEM\nThe create_web_client_war.sh script that creates the web_client.war file contains a change directory (CD) operating system command so the WorkplaceXT directory will be included in the archive. This CD command fails with a \"No such file or directory\" error. \n\nThis failure can be caused by the CDPATH operating system environment variable being set. The CDPATH environment variable is used to define the base directory to be used for the CD command. A side effect of setting the CDPATH is that CD commands in scripts may jump to unintended directories. \n\n \n\nFor example, the error below indicates that the operating system cannot find the WorkplaceXT directory off the root of the file system instead of the expected \"<WorkplaceXT_install_directory>/IBM/FileNet/webclient/\" directory. \n\n \n\nERROR:\n\"create_web_client_war.sh[5]: cd: .WorkplaceXT: [No such file or\ndirectory]", "To resolve this problem, unset the CDPATH operating system environment variable while creating the IBM FileNet Workplace XT war and ear files." ]

[ "This failure can be caused by the CDPATH operating system environment variable being set. The CDPATH environment variable is used to define the base directory to be used for the CD command. A side effect of setting the CDPATH is that CD commands in scripts may jump to unintended directories." ]

[ 1 ]

[ "IBM The version of the IBM Content Search Services client embedded in the IBM FileNet Content Platform Engine is not compatible with the IBM FileNet Content Search Services server. - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The version of the IBM FileNet Content Search Services client included in the IBM FileNet Content Platform Engine is not compatible with the IBM Content Search Services server.", "DIAGNOSING THE PROBLEM\nThe p8_server_error.log file from the IBM FileNet Content Platform Engine will have an error similar to the following:\n2017-03-22T13:13:07.102 1BCC84C0 CBR FNRCB0036W - WARN A problem\noccurred during a search using TextSearchServer\nId={B4FDE211-BE1A-44A1-B0CA-E50A75E4283A};\ndisplayName= xxxxxxxxx on attempt 1 of 1. An alternate text\nsearch server will be\ntried.\\ncom.filenet.api.exception.EngineRuntimeException: FNRCB0036E:\nCBR_TS_ACCESSING_TEXT_SEARCH_SERVER_FAILED: IBM Content Search Services\ncould not communicate with the server that runs on the\nxxxxxxxx:8191 host and port. The server is not\nstarted. Start the server. For information about starting the server,\nsee \"Starting or stopping IBM Content Search Services servers\" in the\nIBM FileNet P8 information center.\\n at\ncom.ibm.filenet.cse.cascade.CSECascadeBase.getTSS(CSECascadeBase.java:71\n)\\n at\n...\ncaused by\n...\nIQQG0205E The client [version: 5.2.0.2] is not compatible with the", "server [version: 2.1.0.0-1.1-4140.FP4]. The client supports server\nversions [[5.2.0.2]]. The server supports client versions [[1.0.0.0,\n1.5.0.0, 1.5.0.1, 2.0.0.0, 2.1.0.0]].", "RESOLVING THE PROBLEM\nThe version of the IBM FileNet Content Search Services client files that are included in the IBM FileNet Content Platform Engine must match the version IBM FileNet Content Search Services server. Please check the readme files for your installed IBM FileNet Content Platform Engine and IBM FileNet Content Search Services fix packs as they will include fix pack requirements. \n\n \n\nFor example IBM Content Search Services 5.2.1.5 fix pack reports the following requirements. \n\n\nPrerequisites \n\nThis fix pack requires: \n\n * 5.2.1.0-P8CSS or any of the following\n 5.2.1.0-P8CSS-IF001 or 5.2.1.0-P8CSS-IF002 or 5.2.1.2-P8CSS-FP002 or 5.2.1.2-P8CSS-IF001 or 5.2.1.3-P8CSS-FP003 or 5.2.1.3-P8CSS-IF001 \n * 5.2.1.5-P8CPE-FP005" ]

[ "The version of the IBM FileNet Content Search Services client files that are included in the IBM FileNet Content Platform Engine must match the version IBM FileNet Content Search Services server. Please check the readme files for your installed IBM FileNet Content Platform Engine and IBM FileNet Content Search Services fix packs as they will include fix pack requirements." ]

[ 3 ]

[ "IBM PI19804: SQLCODE401 FROM DSNXOBFC FOR A SQL PROCEDURE WHEN USING INLIST IN IF STATEMENT - United States z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Sqlcode401 from dsnxobfc for a sql procedure when using inlist\n in if statement\n error will be received when coding something like this\n p1: begin\n decalre ws_types char(2) default 'SN';\n declare ws_typew char(2) default 'WS';\n \n if invar in (ws_types, ws_typew) then\n set outvar = 0;\n end if;\n \n Additional symptoms and search keywords\n SQLIN, SQLCODE401, SQLPROCEDURE, SQLSP, SQLSTOREDPROC\n \n \n \n \n \n\nLOCAL FIX\n * N/A", "PROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All DB2 11 for z/OS users of a compiled SQL *\n * scalar function or native SQL procedure *\n * containing control statement with IN-LIST *\n * predicate which references SQL variables. *\n ****************************************************************\n * PROBLEM DESCRIPTION: SQLCODE -401 or unexpected ABEND0C4 *\n * or ABEND04E may occur for a CREATE *\n * PROCEDURE/FUNCTION statement that *\n * contains control statement with an *\n * IN-LIST predicate which references SQL *\n * variables. *\n * *\n ****************************************************************", "* RECOMMENDATION: *\n ****************************************************************\n The following examples help to illustrate the problem.\n \n Example#1. statement which issued SQLCODE -401 incorrectly.\n CREATE PROCEDURE SYSADM.CTEST(\n IN PCTYPE CHAR(4),\n OUT PRC INTEGER)\n LANGUAGE SQL\n DETERMINISTIC\n MODIFIES SQL DATA\n DYNAMIC RESULT SETS 1\n DISABLE DEBUG MODE\n PTEST: BEGIN\n DECLARE WC_CTYPE_PGMS CHAR(4) DEFAULT 'PGMS';\n DECLARE WC_CTYPE_PGMD CHAR(4) DEFAULT 'PGMD';\n IF PCTYPE IN (WC_CTYPE_PGMS, WC_CTYPE_PGMD) THEN\n SET PRC = 0;\n END IF;\n RETURN;\n END PTEST?\n \n Example#2. statement which issued ABEND0C4.\n CREATE PROCEDURE SYSADM.CTEST(\n IN PCTYPE CHAR(4),\n OUT PRC INTEGER)\n LANGUAGE SQL\n DETERMINISTIC\n MODIFIES SQL DATA\n DYNAMIC RESULT SETS 1\n DISABLE DEBUG MODE\n PTEST: BEGIN", "DECLARE WC_CTYPE_PGMS CHAR(4) DEFAULT 'PGMS';\n DECLARE WC_CTYPE_PGMD CHAR(4) DEFAULT 'PGMD';\n IF (CASE\n WHEN PCTYPE IN ('PGMS', 'PGMM', WC_CTYPE_PGMD, 'PGNN')\n THEN 'PGMM'\n ELSE 'PGMN'\n END\n ) = 'PGMM' THEN\n SET PRC = 0;\n END IF;\n RETURN;\n END PTEST?\n \n Example#3. statement which issued ABEND04E.\n CREATE PROCEDURE SYSADM.CTEST(\n IN PCTYPE CHAR(4),\n OUT PRC INTEGER)\n LANGUAGE SQL\n DETERMINISTIC\n MODIFIES SQL DATA\n DYNAMIC RESULT SETS 1\n DISABLE DEBUG MODE\n PTEST: BEGIN\n DECLARE WC_CTYPE_PGMS CHAR(4) DEFAULT 'PGMS';\n DECLARE WC_CTYPE_PGMD CHAR(4) DEFAULT 'PGMD';\n IF PCTYPE IN ('PGMS', 'PGMN', WC_CTYPE_PGMD, 'PGMG') THEN\n SET PRC = 0;\n END IF;\n RETURN;\n END PTEST?\n \n DB2 does not process the SQL variables in the IN-LIST predicate\n properly which can result in the incorrect SQLCODE or unexpected\n ABEND.", "PROBLEM CONCLUSION\n * DB2 has been modified correctly to process SQL variables in the\n IN-LIST predicate to avoid the problem.\n \n Additional keywords: SQLCODE401 SQLIN SQLCREATE SQLSP\n SQLSTOREDPROC SQLNATIVESQLPL SQLUDF\n SQLPROCEDURE\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI19804\n \n \n * REPORTED COMPONENT NAME\n DB2 OS/390 & Z/\n \n \n * REPORTED COMPONENT ID\n 5740XYR00\n \n \n * REPORTED RELEASE\n B10\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2014-06-12\n \n \n * CLOSED DATE\n 2014-08-18\n \n \n * LAST MODIFIED DATE\n 2014-10-02\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n UI20622\n \n \n\nMODULES/MACROS\n * DSNXOP0", "FIX INFORMATION\n * FIXED COMPONENT NAME\n DB2 OS/390 & Z/\n \n \n * FIXED COMPONENT ID\n 5740XYR00\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * RB10 PSY UI20622 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI20622]\n UP14/09/03 P F409\n \n \n\nFIX IS AVAILABLE\n * SELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL. YOU WILL BE REQUIRED TO SIGN IN. DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES." ]

[ "DB2 has been modified correctly to process SQL variables in the\n IN-LIST predicate to avoid the problem." ]

[ 4 ]

[ "IBM PI50993:Apache HTTPComponents vulnerabilities in WebSphere Application Server (CVE-2012-6153, CVE-2014-3577) - United States PI50993; PI50993; PI50993 DOWNLOADABLE FILES\n\nABSTRACT\n Apache HTTPComponents vulnerabilities in WebSphere Application Server (CVE-2012-6153, CVE-2014-3577) \n\nDOWNLOAD DESCRIPTION\nPI50993 resolves the following problem:\n\nERROR DESCRIPTION:\nApache HTTPComponents vulnerabilities in WebSphere Application Server \nLOCAL FIX: \n\nPROBLEM SUMMARY:\nApache HTTPComponents vulnerabilities in WebSphere Application Server\n\nPROBLEM CONCLUSION:\nApache HTTPComponents vulnerabilities in WebSphere Application Server \n\nPREREQUISITES\nNone\n\nINSTALLATION INSTRUCTIONS\nPlease review the readme.txt for detailed installation instructions.", "URL LANGUAGE SIZE(Bytes) Readme [ftp://public.dhe.ibm.com/software/websphere/appserv/support/fixes/PI50993/8.0.0.11/readme.txt] US English 2260 Readme [ftp://public.dhe.ibm.com/software/websphere/appserv/support/fixes/PI50993/8.5.5.7/readme.txt] US English 2296 \nDOWNLOAD PACKAGE\n\n\nKNOWN SIDE EFFECTS\nThere would be NoClassDefFoundError observed after applying the fix because the API in HTTPCore and HTTPClient libraries are no long visible to application. To resolve this error, application may need to be updated with HTTPCore and HTTPClient libraries bundled.", "Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 8.5.5.6-WS-WASProd-IFPI50993 12-03-2015 US English 254093 HTTP [http://www-933.ibm.com/eserver/support/fixes/fixcentral/swgquickorder?fixes=8.5.5.6-WS-WASProd-IFPI50993&productid=WebSphere%20Application%20Server&brandid=5] 8.0.0.10-WS-WASProd-IFPI50993 12-03-2015 US English 253242 HTTP [http://www-933.ibm.com/eserver/support/fixes/fixcentral/swgquickorder?fixes=8.0.0.10-WS-WASProd-IFPI50993&productid=WebSphere%20Application%20Server&brandid=5] \nTECHNICAL SUPPORT\n Contact IBM Support using SR (http://www.ibm.com/software/support/probsub.html [http://www.ibm.com/software/support/probsub.html]), visit the WebSphere Application Server support web site (http://www.ibm.com/software/webservers/appserv/was/support/ [http://www.ibm.com/software/webservers/appserv/was/support/]), or contact 1-800-IBM-SERV (U.S. only).", "[/support/docview.wss?uid=swg24041394&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24041394&aid=2]Problems (APARS) fixed\nPI50993" ]

[ "There would be NoClassDefFoundError observed after applying the fix because the API in HTTPCore and HTTPClient libraries are no long visible to application. To resolve this error, application may need to be updated with HTTPCore and HTTPClient libraries bundled." ]

[ 1 ]

[ "IBM Learning more about EJBDeploy - United States EJB; EJBDeploy TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Learning more about EJBDeploy is the first step in the troubleshooting process. This document provides you with educational information that can help you learn more about this topic. \n\nRESOLVING THE PROBLEM\n \n\nTAB NAVIGATION\n * Learning more [http://www.ibm.com/support/docview.wss?uid=swg21994741]- selected tab,\n * Troubleshooting [http://www.ibm.com/support/docview.wss?uid=swg21994742]\n * Collect data [http://www.ibm.com/support/docview.wss?uid=swg21260603]\n\nGetting background information on EJBDeploy", "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", "Historically, 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." ]

[ "Please note that in WebSphere Application Server 8.5.5.x and below, the tool can only deploy Java EE applications compiled with a JDK level of 7 or below. To deploy JDK 8 compiled web applications, please upgrade to WebSphere Application Server V9." ]

[ 2 ]

[ "IBM MustGather: Sessions and session management problems in WebSphere Application Server - United States MustGather; MustGather; MustGather; httpsession; session; session manager; isa; collector; autopd; auto pd; MustGatherDocument TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Collecting data for problems with the IBM WebSphere Application Server sessions and session management component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data. \n\nRESOLVING THE PROBLEM\n\n\nCollecting data for problems with the IBM WebSphere Application Server sessions and session management component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.", "To improve the accuracy of complete data collection, IBM recommends you use the automated data collectors within IBM Support Assistant. Not only will the automated collector gather the equivalent of the manual process, it will also provide a secure file transfer of the collection to IBM.", "COLLECTING DATA USING THE IBM SUPPORT ASSISTANT DATA COLLECTOR\n 1. \n 2. WebSphere Application Server V8.0.0.6\n 3. \n 4. (ISADC)\n 5. \n 6. ISADC\n 7. \n 8. Using the IBM Support Assistant Data Collector.\n 9. \n 10. \n 11. \n 12. Using the ISA Data Collector: * To run ISADC from command line, go to your app_server_root/bin directory and run isadc.[sh|bat]\n \n \n * To download, install and run ISADC locally:\n > Obtain the IBM Support Assistant Data collector online ISA Data Collector site for WebSphere Application Server. [http://public.dhe.ibm.com/software/isa/isadc/?taxonomy=ApplicationServer] \n \n > > Select the option to collect from this or another system using a downloadable utility. Download and extract the zip file to your WAS_HOME directory. From a command line, run isadc.[sh|bat] or launch index.html to use the web interface.\n \n \n \n \n \n \n 13. To download and run ISADC in your browser:", "> Obtain the IBM Support Assistant Data collector online ISA Data Collector site for WebSphere Application Server. [http://public.dhe.ibm.com/software/isa/isadc/?taxonomy=ApplicationServer] \n \n > Select the option to collect from this system using the current browser and click Start Collection.\n \n \n \n 14. Select the Runtime > Session Management Problem collector and click Start.\n \n \n 15. Follow the prompts to automatically submit the collected data to IBM Support.", "COLLECTING DATA MANUALLY\n \nSessions and Session Management specific MustGather information:\nThe first step in solving a problem with your HTTPSession in Application Server is to reproduce the problem with session tracing enabled. Adding debug code to the application simplifies the task of identifying the problem.\n\nInstructions for setting up the trace:", "1. In the WebSphere Application Server administrative console, expand the Troubleshooting section and click Logs and Trace.\n \n \n 2. Click the link for your server.\n \n \n 3. Click Diagnostic Trace.\n \n \n 4. Make sure Enable Log is checked, Maximum File Size is 100MB, Historical Files is 10, and specify a File Name. You may have to select different values for Maximum File Size and Historical Files as per the frequency of the problem or as suggested by support team.\n \n \n 5. Click OK.\n \n \n 6. Click on Change Log Level Details.\n \n \n 7. In the text box for Trace Specification, enter the following string (type without spaces) depending on the method that you persist session data: * Trace strings for V7.0 and V8.0 releases * If you do not use any persistence:\n com.ibm.ws.session.*=all:com.ibm.ws.webcontainer.srt.*=all\n \n \n * If you use database persistence:", "com.ibm.ws.session.*=all:com.ibm.ws.webcontainer.srt.*=all:WAS.j2c=all:RRA=all\n \n \n * If you use memory-to-memory persistence:\n com.ibm.ws.session.*=all:com.ibm.ws.webcontainer.srt.*=all:com.ibm.ws.drs.*=all\n \n \n \n \n * Trace strings for V6.0 and V6.1 releases * If you do not use any persistence:\n com.ibm.ws.webcontainer.httpsession.*=all:com.ibm.ws.webcontainer.srt.*=all\n \n \n * If you use database persistence:\n com.ibm.ws.webcontainer.httpsession.*=all:com.ibm.ws.webcontainer.srt.*=all:WAS.j2c=all:RRA=all\n \n \n * If you use memory-to-memory persistence:\n com.ibm.ws.webcontainer.httpsession.*=all:com.ibm.ws.webcontainer.srt.*=all:com.ibm.ws.drs.*=all\n \n \n \n \n \n \n 8. Click apply and save your configuration.\n \n \n 9. Stop the Application Server.", "10. Enable a plug-in trace by changing the LogLevel attribute from Error to Trace in the plugin-cfg.xml file. This file is located in the following directory:\n \n install_root/profiles/profile_name/config/cells/cell_name/nodes/\n web_server_node_name/servers/server_name\n \n \n For more information on capturing plug-in trace, refer MustGather document for plug-in [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21174894].\n \n 11. Stop the Web server.\n \n \n 12. Clear all logs for the Application Server: * trace.log \n * SystemOut.log \n * SystemErr.log\n \n \n \n \n 13. Start the Application Server.\n \n \n 14. Start the Web server.\n \n \n 15. Reproduce your problem. \n \n \n 16. Capture the cookie information from the browser by typing the following text in the address bar:\n javascript:document.cookie\n \n \n 17. Collect the following: * Trace file from the diagnostic trace.", "* All files in the following directory:\n install_root/profiles/profile_name/logs/server_name\n \n \n * All files in the following directory:\n install_root/profiles/profile_name/logs/ffdc\n \n \n * The server.xml file located in the following directory:\n install_root/profiles/profile_name/config/cells/cell_name/nodes/\n node_name/servers/server_name\n \n \n * The http_plugin.log file.\n \n \n * The sessionID that encountered the problem or was captured in step 16.\n \n \n * historyReport.html generated by running the tool genHistoryReport.bat or genHistoryReport.sh, located in the install_root/bin directory; historyreport.html is generated in the working directory of where the genHistoryReport tool is run.\n \n \n \n 18. Follow instructions to send diagnostic information to IBM support [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21153852].", "For a listing of all technotes, downloads, and educational materials specific to the Session and Sessions Management component, search the WebSphere Application Server support site [http://www.ibm.com/software/webservers/appserv/was/support/].", "Related information \nSubmitting information to IBM support [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21153852] \nSteps to getting support for WebSphere Application Server [http://www.ibm.com/developerworks/websphere/support/appserver_support.html] \nMustGather: Read first for WebSphere Application Server [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21145599] \nTroubleshooting guide for WebSphere Application Server [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27005324] \nEXCHANGING DATA WITH IBM SUPPORT\nTo diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:", "* IBM Support Assistant (ISA) \n * Service Request (SR)\n * E-mail \n * FTP to the Enhanced Customer Data Repository (ECuRep)\n\n\n\n\nInstructions for exchanging information with IBM Support [http://www.ibm.com/support/docview.wss?uid=swg21153852]\n\nREAD FIRST AND RELATED MUSTGATHERS\nMustGather: Read first for WebSphere Application Server [http://www.ibm.com/support/docview.wss?uid=swg21145599]\n\n\n\n\n Classloader problem [http://www.ibm.com/support/docview.wss?uid=swg21196187] Dynamic Cache Problem [http://www.ibm.com/support/docview.wss?uid=swg21193837] JNDI Problem [http://www.ibm.com/support/docview.wss?uid=swg21143296] JTS Problem [http://www.ibm.com/support/docview.wss?uid=swg21153216] ORB Problem [http://www.ibm.com/support/docview.wss?uid=swg21157005] Scheduler Problem [http://www.ibm.com/support/docview.wss?uid=swg21220349] Workload Management Problem [http://www.ibm.com/support/docview.wss?uid=swg21052165]", "RELATED INFORMATION\n Recording your screen to share with IBM Support [https://www.ibm.com/developerworks/community/blogs/IBMElectronicSupport/entry/recording_your_screen_to_share_with_support?lang=en]\n\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server - Express Java SDK AIX, HP-UX, Linux, Solaris, Windows Application Servers Runtimes for Java Technology Java SDK" ]

[ "The first step in solving a problem with your HTTPSession in Application Server is to reproduce the problem with session tracing enabled. Adding debug code to the application simplifies the task of identifying the problem." ]

[ 4 ]

[ "IBM Security Bulletin: Integration server HTTP listener exposes stack trace in WebSphere Message Broker and IBM Integration Bus - United States WMB IIB SECURITY BULLETIN\n\nSUMMARY\n Integration server HTTP listener exposes stack trace in WebSphere Message Broker and IBM Integration Bus", "VULNERABILITY DETAILS\nCVEID: CVE-2016-2961 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2961]\nDESCRIPTION: IBM Integration Bus uses the Apache Tomcat server for serving HTTP requests for the HTTPInput and SOAPInput nodes. A vulnerability exists where an unauthenticated, remote attacker can send a malformed HTTP POST request to the integration server HTTP listener. The attacker could use the information in the Java stack trace to identify the version of Apache Tomcat in use.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113806 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113806] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\n IBM Integration Bus V10.0, V9.0 \n\nWebSphere Message Broker V8.0\n\nREMEDIATION/FIXES", "Product VRMF APAR Remediation/Fix IBM Integration Bus V10 IT15188 The APAR is available in fix pack 10.0.0.5 IBM Integration Bus\n\n\nV9\n\nIT15188 An interim fix is available from IBM Fix Central for all platforms\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15188 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15188]", "The APAR is targeted to be available in fix pack 9.0.0.6 WebSphere Message Broker V8 IT15188 An interim fix is available from IBM Fix Central for all platforms\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT15188 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT15188]\n\nThe APAR is targeted to be available in fix pack 8.0.0.8 \nFor unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product. \nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : \nhttp://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308]", "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.", "REFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] CHANGE HISTORY\n 21-Jun-2016 - Original version Published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.", "DISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.\n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21986827]\n\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker 8.0 \nPRODUCT ALIAS/SYNONYM\n WMB IIB" ]

[ "CVEID: CVE-2016-2961 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2961]\nDESCRIPTION: IBM Integration Bus uses the Apache Tomcat server for serving HTTP requests for the HTTPInput and SOAPInput nodes. A vulnerability exists where an unauthenticated, remote attacker can send a malformed HTTP POST request to the integration server HTTP listener. The attacker could use the information in the Java stack trace to identify the version of Apache Tomcat in use.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113806 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113806] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)" ]

[ 1 ]

[ "IBM Security Bulletin: Security vulnerabilities have been identified in IBM DB2 shipped with WebSphere Remote Server (CVE-2014-8730) - United States SECURITY BULLETIN\n\nSUMMARY\n IBM DB2 is shipped as a component of WebSphere Remote Server. Information about security vulnerabilities affecting IBM DB2 has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nFor vulnerability details, see the security bulletin TLS padding vulnerability affects IBM DB2 LUW (CVE-2014-8730) [http://www.ibm.com/support/docview.wss?uid=swg21692618]. \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nPrincipal Product and Version(s) Affected Supporting Product and Version WebSphere Remote Server V6.1, 6.2, 6.2.1, 7.0, 7.1, 7.1.1, 7.1.2, 8.5 IBM DB2 Workgroup Server Edition \nV9.1, 9.5, 9.7, 10.1, 10.5 GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "REFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] CHANGE HISTORY\n 27 March 2015: Original Version Published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.", "DISCLAIMER\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." ]

[ "For vulnerability details, see the security bulletin TLS padding vulnerability affects IBM DB2 LUW (CVE-2014-8730)" ]

[ 0 ]

[ "IBM WCM page and authoring portlet may not display after migration - United States WPv7000eGA; migrating; migrate; migration; V7.0; v7; WCM; out-of-box page; out of the box; page; authoring portlet; may not reach; cannot reach; cannot access; no access; exceptions; IWKAP0009E; Servlet not enabled TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nAfter migrating to IBM WebSphere Portal V7.0, you may not be able to navigate to or display the Web Content Manager (WCM) out-of-box page or the authoring portlet. In addition, some related functions in the user interface might not work or might generate exceptions when accessed. Clicking buttons in the authoring portlet may generate the following error in the log: \n\n * \n * IWKAP0009E: Servlet not enabled\n *", "If 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 *", "* 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" ]

[ "1. Make sure that the page on which the WCM authoring portlet is installed uses a theme with client-side rendering such as the Page Builder theme.\n\n2. Deploy the hidden Portal page on which the reserved authoring portlet is installed. \n\n\n3. Run the following task from the wp_profile_root / Config Engine directory." ]

[ 1 ]

[ "IBM After restoring BigFix server database, ILMT/BFI/SUA server may not import all the data since the restore correctly - United States sequance number; resotre; database; missing data; gap TECHNOTE (TROUBLESHOOTING)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n English \n\nPROBLEM(ABSTRACT)\n After you restore the BigFix database and run an import, new data is not displayed in BFI/SUA/LMT even after successful ETL imports. \n\nSYMPTOM\nNot all data reported already by endpoints to BigFix server are visible in LMT/BFI console. This may include scan results, capacity data, etc.\n\n\nCAUSE\nBFI/SUA/LMT is designed to import only newly created data. To achieve this, the data is marked with the so-called sequence number. The sequence number is incremented during every change, upload, scan, etc. Every import contains data starting from the sequence number reported during the last successful import to the current sequence number.", "When the database is restored, the sequence number is restored to the value from the time when the database backup was created. Because of that, it might happen that the sequence number after the restoration is lower than the sequence number reported during the last successful import. In such case, the first import after the database restoration does not include any data. After that import, the sequence number is updated and the next import contains new data. Depending on your scan settings, you might need to wait some time for the import that contains new data. \n\nWhen the database is restored, the sequence number is restored to the value from the time when the database backup was created.\n\nData for the period from the last successful import before the restoration of the database until the restoration is never imported (obviously, as the data was removed by restoring the DB) and needs to be re-generated by re-running the scans if needed.", "Data from DB restoration time until first successful import is also by default not imported (causing a gap). To cover this gap you may follow the procedure described below.\n\n\n\nRESOLVING THE PROBLEM\nWarning: The following procedure will impact the length of the first import after the sequence is reset. After performing below steps ALL DATA from all endpoints available on BigFix server side will be imported (not only covering the problematic gap). For big environments the impact may be huge and it is better to re-run scans on selected endpoints instead.\n\n1) Ensure that the import is not running and stop the BFI/SUA/LMT server.\n2) To reset the sequence for all data sources and import all data, run the following query on the BFI/SUA/LMT database:\n\nDB2:\nUPDATE dbo.DATASOURCE_SEQUENCES set LAST_SEQUENCE = blob(x'0000000000000000');\n\nMSSQL:\nUPDATE dbo.datasource_sequences set last_sequence = 0x0000000000000000;\n\n3) Start the BFI/SUA/LMT. \n4) Run an import.", "Cross reference information Segment Product Component Platform Version Edition Security IBM BigFix Inventory" ]

[ "1) Ensure that the import is not running and stop the BFI/SUA/LMT server.\n2) To reset the sequence for all data sources and import all data, run the following query on the BFI/SUA/LMT database:\n\nDB2:\nUPDATE dbo.DATASOURCE_SEQUENCES set LAST_SEQUENCE = blob(x'0000000000000000');\n\nMSSQL:\nUPDATE dbo.datasource_sequences set last_sequence = 0x0000000000000000;\n\n3) Start the BFI/SUA/LMT. \n4) Run an import." ]

[ 2 ]

[ "IBM Configuring the Tomcat Data Collector to run as a Windows service - United States ITCAM; J2EE; Tomcat; Windows; Service; CAMJ2ALL; CAMJ2INST; CAMJ2TCDC TECHNOTE (FAQ)\n\nQUESTION\n What is the correct procedure to configure the ITCAM for J2EE Data Collector for Tomcat to run as a Windows service? \n\nCAUSE\nThere is an option to specify the Tomcat Windows Service during GUI configuration of the ITCAM J2EE 7.1.1 agent/DC. This option does not work and will result in a failed configuration.\n\n\n\n[/support/docview.wss?uid=swg21961542&aid=1] [/support/docview.wss?uid=swg21961542&aid=1]\n\nThis option will be removed from the drop down menu for the Tomcat DC Configuration, according to APAR PI43783.\n\n\nANSWER\nTomcat on Windows platforms must be installed from a base distribution, that is extracting a .zip file named like apache-tomcat-7.0.62.zip, even though one plans to start Tomcat only as a Window Service, and not with a startup script.", "If 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----------", "set 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.", "2- 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]", "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:\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." ]

[ "There is an option to specify the Tomcat Windows Service during GUI configuration of the ITCAM J2EE 7.1.1 agent/DC. This option does not work and will result in a failed configuration." ]

[ 0 ]

[ "IBM When attempting to install a second Portal 8.5 instance on the same machine you receive the error, \"ERROR: Error executing the work flow. Step 'Basic Config' FAILED!\" - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nIn this case, the customer had a business requirement that required installing 2 separate Portal installs on the same AIX machine. The first instance of Portal installed successfully. However, the second Portal instance failed during install with the following error....\n\nERROR: Error executing the work flow. Step 'Basic Config' FAILED!.\nCheck the logs for additional error messages.\n[/opt/wps85/scm/PortalServer/installer/wp.\nconfig/wizard/repository/repository_actions.xml:622]", "SYMPTOM\nThe IIM logs shows the following...\n[04/02/2015 17:29:30] PLPR0013I: Saving Console Enterprise Application\n[04/02/2015 17:29:30] PLPR0014I: Closing Console Enterprise Application\n[04/02/2015 17:29:48] PLPR0003I: Opening Console Enterprise Application\n- /opt/was85/base/scm/systemApps/isclite.ear\n[04/02/2015 17:30:01] PLPR0014I: Closing Console Enterprise Application", "StdErr: </message>\n</entry>\n<entry num='1037' time='1428010201865' elapsed='58:37.48' level='INFO'\nthread='Worker-1'>\n<logger>global</logger>\n<class>com.ibm.cic.agent.internal.core.IMLoggerImpl</class>\n<method>info</method>\n<message>Reset current process umask from 022 to 022.</message>\n</entry>\n<entry num='1038' time='1428010201937' elapsed='58:37.55' level='ERROR'\nuid='CRIMA1217E' thread='Worker-1'>\n<logger>com.ibm.cic.common.logging.LogManager</logger>\n<class>org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory\n</class>\n<method>safeLogged</method>\n<message>\n<key>A problem occurred during the execution of the {0} file.\nERROR: Error executing the work flow. Step 'Basic Config' FAILED!.\nCheck the logs for additional error messages.\n[/opt/wps85/scm/PortalServer/installer/wp.config/wizard/repository/repos\nitory_actions.xml:622]", "A package has an issue that cannot be resolved by Installation Manager.\nIdentify the package that has the issue by looking at the installation\nhistory. In Installation Manager, click File &gt; Installation History.\nIn console mode, enter S: View Installation History. Contact IBM\ncustomer support.</key>\n\n<arg>/opt/wps85/scm/PortalServer/installer/wp.config/wizard/repository/r\nepository_actions.xml</arg>\n</message>\n</entry>\n</log>\n\n\nCAUSE\nIn this case, the problem was caused by the fact that the first Portal install was still running when the second Portal install was attempted\n\n\nENVIRONMENT\nPortal 8.5 \n\nAIX\n\n\nDIAGNOSING THE PROBLEM\nFurther review of the IIM logs earlier in the install sequence shows the following message.. \n\n\nERROR 06:32.98 Running processes have been detected that may\ninterfere with the current operation. Stop all WebSphere and related\nprocesses before continue.", "RESOLVING THE PROBLEM\nStop all WebSphere processes on the machine and attempt to install the second Portal instance again" ]

[ "Stop all WebSphere processes on the machine and attempt to install the second Portal instance again" ]

[ 4 ]

[ "IBM What are the supported Apple Macintosh Operating System Versions for IBM SPSS Statistics? - United States SPSS mac macintosh Apple Macintosh statistics OS supported version compatibility matrix leopard Snow Leopard Lion Mountain Lion 10.8 Mavericks 10.9 22 Yosemite 10.10 (Yosemite) el capitan 10.11 spss 24 Sierra 10.12 High Sierra 10.13 TECHNOTE (FAQ)\n\nQUESTION\n I would like to know what are the supported Macintosh Operating system versions for IBM SPSS Statistics versions? \n\nANSWER\nPlease see the list below. It is strongly recommended to review the platform information on IBM Software Product Compatibility Reports [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.jsp]. The installation of IBM SPSS Statistics software on Apple Macintosh OSX operating systems requires an Intel processor. \n\nA) Apple Macintosh MacOS High Sierra (10.13)", "Support for IBM SPSS Statistics 25 only. Please note that no other SPSS release will be officially supported on High Sierra, but older versions like SPSS Statistics 24 may run as well on High Sierra. \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.", "C) 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", "Note: 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", "- 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***", "Note: 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.", "RELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]" ]

[ "Support for IBM SPSS Statistics 25 only. Please note that no other SPSS release will be officially supported on High Sierra, but older versions like SPSS Statistics 24 may run as well on High Sierra." ]

[ 1 ]

[ "IBM HTTP Session time-out settings and overwrite precedence rules - United States WebSphere http session management time-out wasrun precedence overwrite TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n It is possible to set the HTTP Session time-out in various places on the IBM® WebSphere® Application Server Administrative Console. It is also possible to set HTTP Session time-out for the application packaging process. \n\nSince Session time-out can be set in multiple places, it is necessary to understand how the ultimate Session time-out for an application is determined. \n\nCAUSE\nApplication needs HTTP session time-out set.\n\nRESOLVING THE PROBLEM\nThe HTTP Session time-out can be set in the following places: \n\n * From the Administrative Console at the server, Enterprise application, and Web application levels \n * At the time when the application is packaged \n * In the application code", "Setting 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.", "3. To set the HTTP Session time-out at the Web Application level, navigate to Applications > Enterprise Applications > Your Application > Web Module > Your Web App.war > Session Management. \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.", "This setting overrides any session time-outs defined from the Administrative Console. Alter this setting by repackaging the application with a new value, or by modifying the web.xml file. The entry in the web.xml will be as follows: \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.", "1. 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" ]

[ "Check Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the application session to overwrite those values set at the parent, which in this case is the Server level." ]

[ 1 ]

[ "IBM Gathering detailed JazzSM Page and Widget information - United States DASHL2FAQ; Page; Widget; release; detailed; information TECHNOTE (FAQ)\n\nQUESTION\n How can I get detailed information about defined Pages and the Widgets on the Page? \n\nCAUSE\nPage and Widget release information that will be needed for PMR's\n\nANSWER\nThere are two options, display information about the Page and defined widgets and wires on the page, or show information about just the widgets. Both methods are explained below. \n\nIn the upper right portion of the displayed Page, right click on the icon followed by either the \"About\" or \"Edit Page\" on the pull down menu item as shown below. \n\n[/support/docview.wss?uid=swg21976068&amp;aid=1]\n\nThe \"About\" selection will show the following information about the Page and Widgets widgets, wires defined on the Page:", "\"Console\", \"General\" information showing the DASH version, layout of the page and information about each of the defined widgets and wires on the page. Below is an example of the Widget information displayed:\n\n[/support/docview.wss?uid=swg21976068&aid=2] [/support/docview.wss?uid=swg21976068&aid=2]\n[/support/docview.wss?uid=swg21976068&aid=3] [/support/docview.wss?uid=swg21976068&aid=3]\n\nThe second option is to display only the information about a single widget. \n\nSelecting the \"Edit Page\" shown in the first screen shot above, you an then right click on the widgets, select \"About\" from the pulldown as shown below, \n\n\n[/support/docview.wss?uid=swg21976068&amp;aid=4]\n\n[/support/docview.wss?uid=swg21976068&aid=5] [/support/docview.wss?uid=swg21976068&aid=5]" ]

[ "There are two options, display information about the Page and defined widgets and wires on the page, or show information about just the widgets." ]

[ 0 ]

[ "IBM Is using a monitored JBoss Application Server with ITCAM for J2EE supported in a Windows service? - United States J2EE JBoss server Windows service LA2 fix TECHNOTE (FAQ)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n US English \n\nQUESTION\n Is using a monitored JBoss Application Server with ITCAM for J2EE supported in a Windows service? \n\nANSWER\nWhen you configure the JBoss Application Service to run as a Windows service, you will download the JBoss native connectors [http://jbossweb.jboss.org/downloads/jboss-native-2-0-10] and modify the service.bat file. \n\nThe JBoss service is not available to run as a Windows service when configured with the ITCAM for J2EE agent/DC because this involves changes to the JBoss native connector files and this is currently not supported. Additionally, there's no option to specify the Service name when configuring the JBoss server during the configuration steps.", "If you are using JBoss AS 7.1 or JBoss EAP 6.1.0 or 6.2.0 or 6.3.0, then you will need the to use the latest patch first, [https://developer.ibm.com/answers/questions/208313/how-do-i-download-the-new-itcam-for-j2ee-711-la-if.html]then run the standalone.bat (or domain.bat) program from the command-line after successful configuration. \n\nNote: If you have a Tomcat server, then you will be able to use that server in a Service, the technote is here. [http://www.ibm.com/support/docview.wss?uid=swg21961542]\n\n \n\nPRODUCT ALIAS/SYNONYM\n ITCAM for J2EE" ]

[ "The JBoss service is not available to run as a Windows service when configured with the ITCAM for J2EE agent/DC" ]

[ 0 ]