id
string | question
string | answer
string | is_impossible
bool | contexts
list |
|---|---|---|---|---|
TRAIN_Q400 | Security Bulletin: IBM MQ termination of a client application causes denial of service (CVE-2017-1235)
I need to understand details regarding Security Bulletin: IBM MQ termination of a client application causes denial of service (CVE-2017-1235). Where can I find this information?
| CVEID: CVE-2017-1235 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1235]
DESCRIPTION: IBM MQ could allow an authenticated user to cause a premature termination of a client application thread, which could potentially cause denial of service.
CVSS Base Score: 3.1
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/123914 [https://exchange.xforce.ibmcloud.com/vulnerabilities/123914] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L) | false | [
{
"filename": "swg22005415.txt",
"text": "Title: IBM Security Bulletin: IBM MQ termination of a client application causes denial of service (CVE-2017-1235) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n Termination during an MQGET call of a client application running on a channel with SHARECNV=1, could cause a SIGSEGV and termination of the channel agent process. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-1235 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1235]\nDESCRIPTION: IBM MQ could allow an authenticated user to cause a premature termination of a client application thread, which could potentially cause denial of service.\nCVSS Base Score: 3.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/123914 [https://exchange.xforce.ibmcloud.com/vulnerabilities/123914] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ V8.0 \n\nIBM MQ V8.0.0.6 and earlier maintenance levels. \n\nIBM MQ V9.0 Long Term Support Release \n\nIBM MQ V9.0.0.1 and earlier maintenance levels. \n\nIBM MQ V9.0 Continuous Delivery Release \n\nIBM MQ Continuous delivery update 9.0.3 and earlier maintenance levels.\n\nREMEDIATION/FIXES\nIBM MQ V8.0 \n\nApply 8.0.0.7 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.7&platform=All&function=all&useReleaseAsTarget=true] maintenance level. \n\nIBM MQ V9.0 Long Term Support Release \n\nApply 9.0.0.2 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=9.0.0.2&platform=All&function=all&useReleaseAsTarget=true] maintenance level. \n\nIBM MQ V9.0 Continuous Delivery Release \n\nApply continuous delivery update 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348] or later\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY."
}
] |
TRAIN_Q401 | How do I tell when there are mismatched MQ jars in my application server?
Mismatched jar files can cause strange and unpredictable errors when using the MQ JMS classes from a .war file. | If your Java EE application (.ear or .war) bundles a copy of any MQ jar files, you should remove them and rely on the ones from the installed MQ Resource Adapter instead. | false | [
{
"filename": "swg21681142.txt",
"text": "Title: IBM Solving IBM MQ Java code version mismatches using the mqjavalist.sh script - United States\n\nText:\nWebSphere MQ WMQ TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When Java™ SE applications and Java EE application servers such as WebSphere Application Server do not use a consistent set of MQ Java archives, applications can fail in unpredictable ways. If WebSphere Application Server notices a mismatch, it issues this message: \"MQJCA1008 The WebSphere MQ classes for JMS were found in the class path but were not the correct version. This error can occur if the application server finds an earlier version of the WebSphere MQ classes for JMS in the class path. The error can also occur if you do not configure WebSphere Application Server to use the correct version of the WebSphere MQ classes for JMS.\" \n\nENVIRONMENT\nThe mqjavalist.sh script runs on Linux and UNIX systems and can identify Java archives and classes from MQ V5.3 and later versions. Although the mqjavalist.sh script does not run on Windows systems, it is possible to zip up a directory structure on Windows in order to examine it with mqjavalist.sh on a different system. To use the mqjavalist.sh script, download it from the bottom of this page, copy it to the target system, and make the script executable. Make sure that either the unzip command or the Java jar command is available in your PATH before running mqjavalist.sh. For example:\n\n\n\n 1. Preparing to run mqjavalist.sh\n 2. \n 3. sh> chmod +x mqjavalist.sh \n sh> PATH=$PATH:/opt/java7/bin \n \n\n\n\n\nDIAGNOSING THE PROBLEM\nIBM MQ ships a number of Java archives (jar files) that applications use to connect to MQ and work with messages. For Java EE environments, MQ provides a Resource Adapter called wmq.jmsra.rar which contains the jar files required by JMS applications. Java SE and Java EE applications must use a consistent set of MQ jar files at the same maintenance level, or else they might experience a wide variety of problems including intermittent errors, performance problems, and other failures.\n\nIt is common to find multiple versions of the MQ jar files in the Java CLASSPATH, or invalidly bundled in Java applications (.ear, .war, and .jar files). Finding and eliminating duplicate copies of the MQ jar files can be a difficult task, but the mqjavalist.sh script simplifies that task on Linux and UNIX systems.\n\n\n\n * Syntax\n * Examples\n * WebSphere Application Server\n * Sample output\n * Resolving problems\n * Download\n\n\n\nSYNTAX\n\n 1. mqjavalist.sh -? | -h \n 2. \n 3. mqjavalist.sh [-v] [-r] [-f File] -d Directory ...\n 4. \n 5. \n 6. \n 7. -?:\n 8. \n 9. \n 10. -h:\n 11. \n 12. \n 13. -v:\n 14. \n 15. \n 16. -r:\n 17. \n 18. \n 19. -f File:\n 20. \n 21. \n 22. -d Directory:\n 23. \n 24. \n 25. \n 26. \n 27. \n 28. The mqjavalist.sh script can take several minutes to complete, depending on the number of Java archives to search and whether you perform a recursive examination of archive files. While running, the script regularly prints its status and the percentage of work completed.\n\n\nBack to top\n\n\n\nEXAMPLES\n\n 1. Search for MQ files under /usr/IBM/WebSphere and save the results to the file mqlist.txt:\n \n mqjavalist.sh -f mqlist.txt -d /usr/IBM/WebSphere\n 2. \n 3. \n 4. Perform a recursive search of archives under /opt/IBM:\n \n mqjavalist.sh -r -d /opt/IBM\n 5. \n 6. \n 7. Recursively search archive files under the /opt/IBM/IIB and /opt/mqm directories and enable verbose output to ~/output.txt:\n \n mqjavalist.sh -vrf ~/output.txt -d /opt/IBM/IIB -d /opt/mqm\n 8. \n\n\nBack to top\n\n\n\nWEBSPHERE APPLICATION SERVER\n\nWebSphere Application Server and other IBM products built on WebSphere Application Server normally show the MQ jar files in more than one location. Except as noted below, the copies of the MQ jar files should match the versions listed on this page [https://www.ibm.com/support/docview.wss?uid=swg21248089]. Any copies of the MQ jar files other than those listed below might represent a problem: \n\n\n 1. WebSphere Application Server V8.5.5, V8.5 and V8.0\n 2. \n 3. \n\n\n\n 1. WebSphere Application Server V7.0\n 2. \n 3. \n 4. \n 5. \n 6. If you created a WebSphere Application Server V7.0 profile before applying fix pack 7.0.0.1 or later, you must update the profile to use the correct MQ Resource Adapter path [https://www.ibm.com/support/knowledgecenter/SSAW57_7.0.0/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tmj_wmqra_restoredefault.html]. Otherwise, the application servers in that profile will use the old MQ Resource Adapter jars under the profile installedConnectors/wmq.jmsra.rar directory rather than the MQ jars in the main installedConnectors/wmq.jmsra.rar directory, which are kept up to date by WebSphere Application Server fix packs.\n\n\n 1. WebSphere Application Server V6.1\n 2. \n 3. \n\n\n\nBack to top\n\n\n\nSAMPLE OUTPUT\n\n 1. sh> \n 2. ./mqjavalist.sh -r -f mqlist.txt -d /opt/IBM/WebSphere/AppServer\n 3. \n 4. Running mqjavalist.sh V1.4 on SUSE Linux Enterprise Server 10 (ppc) with arguments: -r -f mqlist.txt -d /opt/IBM/WebSphere/AppServer\n \n mqjavalist.sh: Searching directory /opt/IBM/WebSphere/AppServer\n mqjavalist.sh: 2180 possible Java archives found\n 1. Found 80 MQ classes in classes.jar in WMQHTTP.war in /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/aemtux1Cell01/applications/WMQHTTP_war.ear/WMQHTTP_war.ear:\n root root 145600 2014-07-16 13:56 /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/aemtux1Cell01/applications/WMQHTTP_war.ear/WMQHTTP_war.ear\n 2. Found 80 MQ classes in /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/aemtux1Cell01/WMQHTTP_war.ear/WMQHTTP.war/WEB-INF/lib/classes.jar:\n root root 156845 2013-09-25 18:02 /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/aemtux1Cell01/WMQHTTP_war.ear/WMQHTTP.war/WEB-INF/lib/classes.jar\n 3. Found 80 MQ classes in classes.jar in WMQHTTP.war in /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/aemtux1Cell01/applications/WMQHTTP_war.ear/WMQHTTP_war.ear:\n root root 145600 2014-07-16 13:57 /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/aemtux1Cell01/applications/WMQHTTP_war.ear/WMQHTTP_war.ear\n 4. Found com.ibm.mq.commonservices.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ Common Service\n Implementation-Version: ${version.number} - ${build.level}\n Implementation-Vendor: IBM Corporation\n 5. Found com.ibm.mq.connector.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ J2EE Connector Architecture\n Implementation-Version: 7.1.0.0-k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 6. Found com.ibm.mq.headers.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 /wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 7. Found com.ibm.mq.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 8. Found com.ibm.mq.jmqi.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 9. Found com.ibm.mq.jmqi.local.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 10. Found com.ibm.mq.jmqi.remote.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 11. Found com.ibm.mq.jmqi.system.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 12. Found com.ibm.mq.jms.admin.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: JMS Common Client API/SPI\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 13. Found com.ibm.mq.pcf.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 14. Found com.ibm.mqjms.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: JMS Client Common Facade\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 15. Found dhbcore.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Version: \"DH610-GOLD\"\n Implementation-Title: \"Webscale Distribution Hub Core\"\n Implementation-Vendor: \"IBM Corporation\"\n 16. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.jar:\n root root 1115668 2012-10-15 12:56 com.ibm.mq.jmqi.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 17. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.commonservices.jar:\n root root 728387 2012-10-15 12:56 com.ibm.mq.commonservices.jar\n Implementation-Title: WebSphere MQ Common Service\n Implementation-Version: ${version.number} - ${build.level}\n Implementation-Vendor: IBM Corporation\n 18. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.remote.jar:\n root root 546407 2012-10-15 12:56 com.ibm.mq.jmqi.remote.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 19. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jar:\n root root 448745 2012-10-15 12:56 com.ibm.mq.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 20. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jms.admin.jar:\n root root 358016 2012-10-15 12:56 com.ibm.mq.jms.admin.jar\n Implementation-Title: JMS Common Client API/SPI\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 21. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mqjms.jar:\n root root 352254 Aug 01 11:49 com.ibm.mqjms.jar\n Implementation-Title: JMS Common Client facade\n Implementation-Version: 7.0.1.5 - k701-105-110419\n Implementation-Vendor: IBM Corporation\n 22. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.connector.jar:\n root root 339396 2012-10-15 12:56 com.ibm.mq.connector.jar\n Implementation-Title: WebSphere MQ J2EE Connector Architecture\n Implementation-Version: 7.1.0.0-k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 23. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.headers.jar:\n root root 338572 2012-10-15 12:56 com.ibm.mq.headers.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 24. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.local.jar:\n root root 224747 2012-10-15 12:56 com.ibm.mq.jmqi.local.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 25. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.system.jar:\n root root 209738 2012-10-15 12:56 com.ibm.mq.jmqi.system.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 26. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.pcf.jar:\n root root 125200 2012-10-15 12:56 com.ibm.mq.pcf.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 27. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/dhbcore.jar:\n root root 2011835 2012-10-15 12:56 dhbcore.jar\n Implementation-Version: \"DH610-GOLD\"\n Implementation-Title: \"Webscale Distribution Hub Core\"\n Implementation-Vendor: \"IBM Corporation\"\n mqjavalist.sh: 27 jar files with MQ code found in /opt/IBM/WebSphere/AppServer\n \n mqjavalist.sh: 27 total jar files with MQ code found\n mqjavalist.sh: Results saved to mqlist.txt\n \n \n \n 5. \n 6. Back to top\n\nRESOLVING THE PROBLEM\n\nReview the output from mqjavalist.sh to determine where copies of the MQ jar files have been found. Not all duplicates represent a problem, unless they are being loaded by your Java SE application or Java EE application server at runtime. If the com.ibm.mq.commonservices.jar file shows an implementation version of ${version.number} - ${build.level} just ignore it.\n\nIn the sample output above, entries #16 through #27 represent the jar files for the installed MQ Resource Adapter. They all show an implementation version of 7.1.0.0 - k000-L111005.1 except for #21, com.ibm.mqjms.jar, which shows an implementation version of 7.0.1.5 - k701-105-110419. Because the jar file versions are not in sync, MQ JMS will not function as expected.\n\nIn cases like this, the wmq.jmsra.rar file should contain a copy of the MQ jar at the right level for the application server. Entry #14 in the mqjavalist.sh output shows the com.ibm.mqjms.jar file with an implementation version of 7.1.0.0 - k000-L111005.1, which is what we need. Use the jar program to extract the com.ibm.mqjms.jar file from the wmq.jmsra.rar archive, then copy it over the back-level version of the jar. Use chown and chmod to ensure the permissions on the file are correct.\n\nIn other cases, you might find that the classpath for the application server, or for your Java SE application, is picking up extra copies of the MQ jar files. Eliminating unnecessary classpath entries can resolve the problem.\n\nIf your Java EE application (.ear or .war) bundles a copy of any MQ jar files, you should remove them and rely on the ones from the installed MQ Resource Adapter instead.\n\nBack to top\n\n\nAdditional Keywords: \ntroubleshoot troubleshooting trouble shoot classloader classpath configuration scripts\n\n\n\nDOWNLOAD\n 1. \n 2. mqjavalist.sh [/support/docview.wss?uid=swg21681142&aid=2]mqjavalist.sh\n\n\n\n\nDISCLAIMER: All source code and/or binaries attached to this document are referred to here as \"the Program\". IBM is not providing program services of any kind for the Program. IBM is providing the Program on an \"AS IS\" basis without warranty of any kind. IBM WILL NOT BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM, OR ITS RESELLER, HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Back to top"
}
] |
TRAIN_Q402 | Why am I getting StaleConnectionException on WebSphere side while Oracle is throwing 'OALL8 is in an inconsistent state'?
In the WebSphere Application Server SystemOut.log file we see this message:
ConnectionEve A J2CA0056I: TheConnection Manager received a fatal connection error from the Resource Adapter for resource jdbc/<data source name>. The exception which was received is com.ibm.websphere.ce.cm.StaleConnectionException: OALL8 is in an inconsistent state:java.sql.SQLException: OALL8 is in an inconsistent state.
How can this be resolved? | In WebSphere Application Server, the StaleConnectionException is issued when the database vendor issues an exception indicating that a connection currently in the connection pool is no longer valid. | false | [
{
"filename": "swg21063645.txt",
"text": "Title: IBM Demystifying the WebSphere StaleConnectionException - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n What is the StaleConnectionException, why is it issued by WebSphere Application Server, and what should be done about it? \n\nRESOLVING THE PROBLEM\nIn WebSphere Application Server, the StaleConnectionException is issued when the database vendor issues an exception indicating that a connection currently in the connection pool is no longer valid. This can happen for many reasons, including: \n\n * The application tries to get a connection and fails, as when the database is not started.\n \n \n * A connection is no longer usable due to a database failure. When an application tries to use a connection it has previously obtained, the connection is no longer valid. In this case, all connections currently in use by an application can get this error when they try to use the connection.\n \n \n * The application using the connection has already called close() and then tries to use the connection again.\n \n \n * The application tries to use a JDBC™ resource, such as a statement, obtained on a now-stale connection.\n\n\nWhen the StaleConnectionException is issued, the behavior is determined by the Purge Policy setting for the connection pool. If the Purge Policy is set to EntirePool, the entire pool is flushed. But if the Purge Policy is set to FailingConnectionOnly, only the connection that caused the StaleConnectionException is purged from the pool. \n\nAn application can recover from bad connections by explicitly catching the StaleConnectionException and getting a new connection from the pool. Numerous exceptions issued by DB2, Oracle, DataDirect (for connecting to SQLServer), Sybase, and Informix are currently mapped to the StaleConnectionException, which makes recovery easier for the application programmer. The following pseudocode provides an example of how to recover from a StaleConnectionException: \n\n//get a userTransaction\njavax.transaction.UserTransaction tran = getSessionContext().getUserTransaction();\n//retry indicates whether to retry or not\n//numOfRetries states how many retries have\n// been attempted\nboolean retry = false;\nint numOfRetries = 0;\njava.sql.Connection conn = null;\njava.sql.Statement stmt = null;\ndo {\ntry {\n//begin a transaction\ntran.begin();\n//Assumes that a datasource has already been obtained\n//from JNDI\nconn = ds.getConnection();\nconn.setAutoCommit(false);\nstmt = conn.createStatement();\nstmt.execute(\"INSERT INTO EMPLOYEES VALUES\n(0101, 'Bill', 'R', 'Smith')\");\ntran.commit();\nretry = false;\n} catch(java.sql.SQLException sqlX)\n{\n// If the error indicates the connection is stale, then\n// rollback and retry the action\nif (com.ibm.websphere.rsadapter.WSCallHelper\n.getDataStoreHelper(ds)\n.isConnectionError(sqlX))\n{\ntry {\ntran.rollback();\n} catch (java.lang.Exception e) {\n//deal with exception\n//in most cases, this can be ignored\n}\nif (numOfRetries < 2) {\nretry = true;\nnumOfRetries++;\n} else {\nretry = false;\n}\n}\nelse\n{\n//deal with other database exception\nretry = false\n}\n} finally {\n//always cleanup JDBC resources\ntry {\nif(stmt != null) stmt.close();\n} catch (java.sql.SQLException sqle) {\n//usually can ignore\n}\ntry {\nif(conn != null) conn.close();\n} catch (java.sql.SQLException sqle) {\n//usually can ignore\n}\n}\n} while (retry) ; \n\nFurther details about WebSphere Connection Pooling are located in the WebSphere Application Server Knowledge Center article Connection pooling [https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/cdat_conpool.html]\n\nKnowledge Center article Exceptions pertaining to data access [https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/cdat_daexcp.html] contains details on the StaleConnectionException error\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK"
}
] |
TRAIN_Q403 | Help with Security Bulletin: IBM PureApplication System is affected by a security vulnerability. (CVE-2015-1890)
I need to understand details regarding "Security Bulletin: IBM PureApplication System is affected by a security vulnerability (CVE-2015-1890)". Where can I find this information? | CVEID: CVE-2015-1890 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1890]
DESCRIPTION: IBM General Parallel File System could allow someone who has access to a snap file generated by the gpfs.snap tool (/usr/lpp/mmfs/bin/gpfs.snap) to read the private keys of certificates used by GPFS for daemon communications via the TLS protocol.
CVSS Base Score: 3.5
CVSS Temporal Score: See [https://exchange.xforce.ibmcloud.com/]https://exchange.xforce.ibmcloud.com/vulnerabilities/101382 [https://exchange.xforce.ibmcloud.com/vulnerabilities/101382] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:S/C:P/I:N/A:N) | false | [
{
"filename": "swg21964025.txt",
"text": "Title: IBM Security Bulletin: IBM PureApplication System is affected by a security vulnerability. (CVE-2015-1890) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n A security vulnerability have been identified in the General Parallel File System gpfs.snap service tool that affects IBM PureApplication System. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-1890 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1890] \n\nDESCRIPTION: IBM General Parallel File System could allow someone who has access to a snap file generated by the gpfs.snap tool (/usr/lpp/mmfs/bin/gpfs.snap) to read the private keys of certificates used by GPFS for daemon communications via the TLS protocol.\nCVSS Base Score: 3.5\nCVSS Temporal Score: See [https://exchange.xforce.ibmcloud.com/]https://exchange.xforce.ibmcloud.com/vulnerabilities/101382 [https://exchange.xforce.ibmcloud.com/vulnerabilities/101382] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:S/C:P/I:N/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nThis vulnerability affects IBM PureApplication Server and the GPFS pattern type included in: \n\n * \n * \n * \n\nREMEDIATION/FIXES\nThe solution is to upgrade the IBM PureApplication System to the following fix levels and update deployments that implement the GPFS pattern type using the GPFS Pattern Interim Fix: \nIBM PureApplication System V2.1 \n\n * \n * GPFS Pattern Interim Fix is located at: http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=update-gpfs-1.2.1.0&includeSupersedes=0 [http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=update-gpfs-1.2.1.0&includeSupersedes=0] \n\n\n\nIBM PureApplication System V2.0 * \n * GPFS Pattern Interim Fix is located at: http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=update-gpfs-1.2.0.0_1.2.0.1_and_1.2.0.2&includeSupersedes=0 [http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=update-gpfs-1.2.0.0_1.2.0.1_and_1.2.0.2&includeSupersedes=0] \n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT\nNone \n\nCHANGE HISTORY\n 10 August 2015: Original Version Published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY."
}
] |
TRAIN_Q404 | Why do I get "error: The admin task reported the following: null" if uploading a DataPower scrypt3 firmware image file WAS 8.x DataPower Appliance Manager?
How can I manage a set of DataPower appliances that shall run v7 firmware images by using WebSphere Application Server 8.x DataPower Appliance Manager?I get "error: The admin task reported the following: null" if uploading a DataPower scrypt3, while scrypt2 works fine. | - | true | [] |
TRAIN_Q405 | How do I define JMS objects for MQ?
Where and how do I defined JMS objects used by an MQ JMS application? | - | true | [] |
TRAIN_Q406 | Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect API Connect
I need to understand details regarding Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect API Connect ( CVE-2016-5548). Where can I find this information? | CVEID: CVE-2016-5548 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5548]
DESCRIPTION: An unspecified vulnerability related to the Libraries component could allow a remote attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.
CVSS Base Score: 6.5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/120864 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120864] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) | false | [
{
"filename": "swg22006126.txt",
"text": "Title: IBM Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect API Connect - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM® Runtime Environment Java™ used by IBM API Connect. \n\nThese issues were disclosed as part of the IBM Java SDK updates in January 2017 and April 2017. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-5546 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5546]\nDESCRIPTION: An unspecified vulnerability related to the Libraries component has no confidentiality impact, high integrity impact, and no availability impact.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/120869 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120869] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) \n\nCVEID: CVE-2016-5548 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5548]\nDESCRIPTION: An unspecified vulnerability related to the Libraries component could allow a remote attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 6.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/120864 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120864] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) \n\nCVEID: CVE-2016-5549 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5549]\nDESCRIPTION: An unspecified vulnerability related to the Libraries component could allow a remote attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 6.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/120863 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120863] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) \n\nCVEID: CVE-2016-5547 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5547]\nDESCRIPTION: An unspecified vulnerability related to the Libraries component could allow a remote attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/120871 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120871] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) \n\nCVEID: CVE-2016-2183 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2183]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error in the DES/3DES cipher, used as a part of the SSL/TLS protocol. By capturing large amounts of encrypted traffic between the SSL/TLS server and the client, a remote attacker able to conduct a man-in-the-middle attack could exploit this vulnerability to recover the plaintext data and obtain sensitive information. This vulnerability is known as the SWEET32 Birthday attack.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116337 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116337] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) \n\nCVEID: CVE-2017-3511 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3511]\nDESCRIPTION: An unspecified vulnerability related to the Java SE JCE component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 7.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/124890 [https://exchange.xforce.ibmcloud.com/vulnerabilities/124890] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM API Connect V5.0.0.0 - V5.0.7.2\n\nREMEDIATION/FIXES\n \n\nAffected Product Addressed in VRMF APAR Remediation/First Fix IBM API Connect \n\nV5.0.0.0 - 5.0.6.2 5.0.6.3 LI79749 Addressed in IBM API Connect V5.0.6.3.\n\nFollow this link and find the \"APIConnect_Management\" and \"apiconnect-collective-controller\" packages:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.2&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.2&platform=All&function=all] IBM API Connect\n\nV5.0.7.0 - 5.0.7.2 5.0.8.0 LI79749 Addressed in IBM API Connect V5.0.8.0.\n\nFollow this link and find the \"APIConnect_Management\" and \"apiconnect-collective-controller\" packages:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all] GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \nIBM Java SDK January 2017 Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg21997194] \nIBM Java SDK April 2017 Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg22002169] \nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 11 September 2017: original document published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY."
}
] |
TRAIN_Q407 | Help with Multiple vulnerabilities have been identified in WebSphere Application Server shipped with WSRR
I need to understand details regarding Multiple vulnerabilities have been identified in WebSphere Application Server shipped with WebSphere Service Registry and Repository (CVE-2017-1583, CVE-2011-4343). What products are affected? | - | true | [] |
TRAIN_Q408 | Help with Fix Pack 6 for WMB V8
Where can I find more information about WebSphere Message Broker (WMB) Fix Pack 6?
| - | true | [] |
TRAIN_Q409 | OpenSSL Heartbleed (CVE-2014-0160) vulnerability and IBM Support Assistant ISA
Ref. IBM Product Security Incident Response Team - https://www-304.ibm.com/connections/blogs/PSIRT/entry/openssl_heartbleed_cve_2014_0160?lang=en_us
Any statements we can share regarding OpenSSL usage in ISA (v4, v5)since it's neither listed here in NOT affected by this vulnerability? | - | true | [] |
TRAIN_Q410 | how to disable clickjacking at ICN?
We need to secure IBM Content navigator 2.0.3 Fixpack (FileNet P8 5.2.1 FP5, OS AIX 7.1) on our Production environment against malicious activity in the following ways:
Disable clickjacking i.e. it was observed that the server didn't return an X-Frame-Options header. The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render | - | true | [] |
TRAIN_Q411 | Support for Domino 9.0.1 with ICC?
Is Domino v9.0.1 and FP's supported for ICC? | Starting with IBM Content Collector 4.0.1 Fix Pack 6, IBM Lotus Domino/Notes 9.0.1 FP7,FP8 are supported
Starting with IBM Content Collector 4.0.1 Fix Pack 4, IBM Lotus Domino/Notes 9.0.1 FP6 is supported
Starting with IBM Content Collector 4.0.1 Fix Pack 2, IBM Lotus Domino/Notes 9.0.1 FP4, FP5, Mozilla Firefox 35 and Microsoft Edge are supported. IBM Content Collector supports the latest fix packs of the server and client software. | false | [
{
"filename": "swg27042658.txt",
"text": "Title: IBM Prerequisites for IBM Content Collector Version 4.0.1 - United States\n\nText:\n PRODUCT DOCUMENTATION\n\nABSTRACT\n This document details the system requirements for IBM Content Collector Version 4.0.1. \n\nCONTENT\n \n\nAlways up-to-date system requirement reports can be dynamically generated by using the Software Product Compatibility Reports (SPCR) tool [http://www-969.ibm.com/software/reports/compatibility/clarity/index.html]. \n\nFrom the Content Collector product tabs below you can select detailed system requirement reports for different contexts (by Operating System, by component). Note that clicking a link will always generate a new, up-to-date report.\n\nImportant:\nBecause other products frequently ship fixes, updates, and new releases, testing every configuration is not possible. In general, you can install and run with updates to supported products if those updates are forward compatible.\n\nAlways check for the latest IBM Content Collector security bulletins in the IBM Support Portal and make sure to have the required fixes applied.\n\nPRODUCT REQUIREMENTS FOR IBM CONTENT COLLECTOR\n * All versions [http://www.ibm.com/support/docview.wss?uid=swg27040212] \n * Version 4.0.1- selected tab, \n\n * HARDWARE REQUIREMENTS\n \n * Content Collector server\n * Client workstations\n * SOFTWARE PREREQUISITES\n \n * Operating system and software\n * Web application server\n * COLLECTION SOURCE SYSTEMS\n \n * Lotus Domino\n * Microsoft Exchange\n * SMTP email\n * Microsoft SharePoint\n * IBM Connections\n * File system\n\n * ARCHIVE SYSTEMS\n \n * IBM Content Manager\n * IBM FileNet P8\n * LEGACY RESTORE\n \n * Legacy restore\n * RETENTION POLICY DISTRIBUTION SUPPORT\n \n * Retention Policy Distribution Support\n * OPTIONAL SOFTWARE\n \n * Optional software\n\n\n\n\n\nIBM CONTENT COLLECTOR PRODUCTS\n * Content Collector for Email\n\n * Content Collector for File Systems\n\n * Content Collector for IBM Connections\n\n * Content Collector for Microsoft SharePoint\n\n\n\n\n\nLegend \n\nx86 Intel 32-bit processors, including IBM System x, eServer xSeries, and BladeCenter servers X86-64 64-bit AMD Opteron (AMD64) and Intel Xeon (EM64T) processors, including IBM System x and BladeCenter servers \n\nHARDWARE REQUIREMENTS\nIBM CONTENT COLLECTOR SERVER\nThe following table contains the minimum and the recommended hardware requirements for the server where IBM Content Collector is installed.\n\n \n\nHardware requirements Minimum Recommended Processor 2 dual-core processors\nx86 or x86-64 2 six-core processors\nx86 or x86-64 Processor speed 2.5 GHz > 3 GHz System memory (RAM) 4 GB 8 GB Hard disk Hard drive with sufficient capacity 2 enterprise class hard drives with 10000 RPM or better Disk space For IBM Content Collector program package, prerequisite software, temporary data, and log information 150 GB > 150 GB For each IBM Content Collector server that is intended to run an SMTP Receiver instance 750 GB redundant storage\n\nIf multiple Content Collector servers are deployed in a scale-out setup to archive documents from SMTP email systems, this storage must be on a fast NAS device and shared between all Content Collector servers. 1 TB redundant storage For IBM Connections archiving 10 GB redundant storage\n\nIf multiple Content Collector servers are deployed in a scale-out setup to archive IBM Connections documents, this storage must be on a fast NAS device and shared between all Content Collector servers. > 10 GB Supported virtualization environments for IBM Content Collector are VMware ESX and ESXi 4, 5, and 5.1 and Microsoft HyperV Server 2008, 2008 R2, and 2012.\n\nBack to top\n\nCLIENT WORKSTATIONS\nThe hardware capacity of connected client workstations must be sufficient to run the supported client applications:\n\n * Lotus Notes or Lotus iNotes\n * Microsoft Outlook or Outlook Web App\n\nIn addition, the minimum hardware requirements for mobile support are contained in the following form(OWA Extension mobile support on iPhone and iPad, iNotes Extension mobile support on iPad only) starting with IBM Content Collector 4.0.1 Fix Pack 2 \n\n \n\nHardware iOS Capacity iPad mini 9.x 16GB iPad with Retina 9.x 16GB iPhone 6 9.x 16GB For more information, see the client software documentation.\n\nBack to top\n\n\n\nSOFTWARE PREREQUISITES\nPREREQUISITES FOR THE IBM CONTENT COLLECTOR SERVER\nThe following section describes the operating system and other software that is required on the system where IBM Content Collector Server is installed.\n\nOPERATING SYSTEM\nIBM Content Collector can be installed on servers with one of the following operating systems:\n\nOperating systems Editions Architectures Fixes Windows Server 2008 * Standard Edition \n * Enterprise Edition\n\n * 32-bit (x86) \n * 64-bit (x86-64)\n\nService Pack 2 Windows Server 2008 R2 * Standard Edition \n * Enterprise Edition\n\n * 64-bit (x86-64)\n\nService Pack 1 Windows Server 2012 * Datacenter Edition \n * Standard Edition\n\n * 64-bit (x86-64)\n\n[/support/docview.wss?uid=swg27042658&aid=1] Windows Server 2012 R2 * Datacenter Edition \n * Standard Edition\n\n * 64-bit (x86-64)\n\n[/support/docview.wss?uid=swg27042658&aid=1] Windows Server 2016 * Datacenter Edition \n * Standard Edition\n\n * 64-bit (x86-64)\n\n[/support/docview.wss?uid=swg27042658&aid=1] IBM Content Collector does not support Server Core and Nano server installations. Note that if IBM Content Collector is installed on Windows Server 2012 R2, you can use only IBM Content Manager Enterprise Edition V8.5 as an IBM Content Manager target repository.\n\n\nREQUIRED SOFTWARE\nThe following software must be installed on the server where IBM Content Collector is installed.\nImportant: \n\n * On a 64-bit operating system, IBM Content Collector Server runs in 32-bit compatibility mode. Therefore, IBM Content Collector Server requires the 32-bit version of all software prerequisites. \n * For performance reasons, do not colocate the IBM Content Collector Server and the archive system on one server in a production environment. This setup can be used for testing or demonstration purposes, but it is not officially supported.\n\nSoftware Required for which scenarios Notes DB2 Information Integrator for Content Required for IBM Content Manager V8.4 repositories See IBM Content Manager. IBM Content Manager V8 API Required for IBM Content Manager V8.5 repositories See IBM Content Manager. FileNet Content Engine .NET and Java clients Required for IBM FileNet P8 repositories See IBM FileNet P8. IBM FileNet IDM Desktop 4.0.x Required for IBM FileNet Image Services repositories [/support/docview.wss?uid=swg27042658&aid=1] Microsoft .NET Framework 4.0 or 4.5 Always required When using Microsoft .NET version 4.5 on a Windows Server 2008 or Windows Server 2008 R2 operating system, Microsoft .NET Framework 4.5.1 is required. Lotus Domino 8.5.0 server with the latest fix pack \nLotus Domino 8.5.3 FP6 server\nLotus Domino 8.5.4 server\nIBM Domino 9.0 or 9.0.1 FP2 server\nIBM Domino 9.0.1 FP4 server\nIBM Domino 9.0.1 FP5 server\nIBM Domino 9.0.1 FP6 server\nIBM Domino 9.0.1 FP7 server\nIBM Domino 9.0.1 FP8 server Required if you want to archive Lotus Notes documents The Lotus Domino server provides a Lotus Notes API for processing Lotus Notes documents. Microsoft Outlook 2007 Service Pack 3 (or later)\nMicrosoft Outlook 2010 Service Pack 1 (or later)\nMicrosoft Outlook 2013\nMicrosoft Outlook 2016 Required if you want to archive email from Microsoft Exchange servers The Microsoft Outlook client provides the Messaging API (MAPI) for email processing. Microsoft Windows DST update KB 955839 [http://support.microsoft.com/kb/955839] Always required [/support/docview.wss?uid=swg27042658&aid=1] Microsoft Windows Server 2008 R2 SP1 hotfix KB 2732673 [http://support.microsoft.com/kb/2732673]\nMicrosoft Windows Server 2008 R2 SP1 hotfix KB 2728738 [http://support.microsoft.com/kb/2728738]\nMicrosoft Windows Server 2008 R2 SP1 hotfix KB 2831013 [http://support.microsoft.com/kb/2831013]\nMicrosoft Windows Server 2008 R2 hotfix KB 2831154 [http://support.microsoft.com/kb/2831154] Required if the File System Connector is used [/support/docview.wss?uid=swg27042658&aid=1] Back to top\n\nWEB SERVER APPLICATIONS\nIBM WEBSPHERE APPLICATION SERVER\nIBM Content Collector requires IBM WebSphere Application Server to run the Configuration Web Service and to perform search and restore operations. Typically, there is no need to check for compatible versions because IBM Content Collector comes with an embedded version of WebSphere Application Server Version 8.0.\n\nHowever, you can deploy some of the IBM Content Collector web applications to an external web application server. IBM Content Collector supports the base edition of IBM WebSphere Application Server for AIX, Linux, and Windows. The Network Deployment edition is not supported. Always install the latest fix pack. The following versions are supported: \n\n * 8.0.0.13 \n * 8.5\n\nIf you use an external web application server, make sure that the following prerequisites that are required for IBM Content Collector Server are also installed on the separate web application server: \n\n * Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package \n * Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package ATL Security Update \n * Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package \n\nHow to get: \n\nYou can purchase IBM WebSphere Application Server from the following website: WebSphere Application Server [http://www.ibm.com/support/docview.wss?uid=swg27024129]\n\nIBM CONTENT COLLECTOR WEB APPLICATION BROWSERS\nThe IBM Content Collector web applications support the following browsers: \n\nBrowsers Versions Mozilla Firefox * 14 \n * 17 or 24 Extended Support Release (ESR) \n * 24 \n * 28 \n * 31 Extended Support Release (ESR) \n * 32 \n * 33 \n * 34 \n * 35\n\nMicrosoft Internet Explorer * 8 \n * 9 \n * 10 \n * 11\n\nMicrosoft Edge * 20\n\nChrome * 60\n\nMicrosoft Edge is supported starting with IBM Content Collector 4.0.1 Fix Pack 2. \n\nHow to get: \n\nYou can obtain Mozilla Firefox from www.mozilla.com [http://www.mozilla.com] and Microsoft Internet Explorer from www.microsoft.com [http://www.microsoft.com].\n\nBack to top\n\n\n\nCOLLECTION SOURCE SYSTEMS\nLOTUS DOMINO\nSERVER AND CLIENTS\nThe following table describes the supported versions of Lotus Domino for Domino mail servers and the supported versions of Lotus Notes for Notes mail clients:\n\nServer software Client software Other software requirements Notes * Lotus Domino 8.5.0 \n * Lotus Domino 8.5.1 \n * Lotus Domino 8.5.2 \n * Lotus Domino 8.5.3 FP6 \n * Domino 9.0 \n * Domino 9.0.1 FP2 \n * Domino 9.0.1 FP4 \n * Domino 9.0.1 FP5 \n * Domino 9.0.1 FP6 \n * Domino 9.0.1 FP7 \n * Domino 9.0.1 FP8\n\n * Lotus Notes 8.5.0 \n * Lotus Notes 8.5.1 \n * Lotus Notes 8.5.2 \n * Lotus Notes 8.5.3 FP6 \n * Notes 9.0 (along with the Browser plug-in) \n * Notes 9.0.1 (along with the Browser plug-in) \n * Notes 9.0.1 FP2 \n * Notes 9.0.1 FP4 \n * Notes 9.0.1 FP5 \n * Notes 9.0.1 FP6 \n * Notes 9.0.1 FP7 \n * Notes 9.0.1 FP8\n\n * Windows 7 Service Pack 1 (32-bit and 64-bit) \n * Windows 8 Professional Edition \n * Windows 8.1 Professional Edition \n * Mac OS X 10.8.x (32-bit and 64-bit) \n * Mac OS X 10.9.x (32-bit and 64-bit) \n * Windows 10 Professional Edition \n * Windows 10 Enterprise Edition\n\n * Mozilla Firefox 14 \n * Mozilla Firefox 17 or 24 Extended Support Release (ESR) \n * Mozilla Firefox 24 \n * Mozilla Firefox 28 \n * Mozilla Firefox 31 Extended Support Release (ESR) \n * Mozilla Firefox 32 \n * Mozilla Firefox 33 \n * Mozilla Firefox 34 \n * Mozilla Firefox 35 \n * Microsoft Internet Explorer 8 \n * Microsoft Internet Explorer 9 \n * Microsoft Internet Explorer 10 \n * Microsoft Internet Explorer 11 \n * Microsoft Edge\n\nOn Mac OS X, Lotus Notes R8.5.1 Fix Pack 2 or higher is required.\n\nOffline repositories, collecting additional archiving information, and automatic document retrieval is not supported for Lotus Notes clients on Mac OS.\n\nThe Notes 9.0 Browser plug-in provides these Content Collector functions: * Interactive restore \n * Settings \n * Help\n\n * Lotus iNotes 8.5.0 \n * Lotus iNotes 8.5.1 \n * Lotus iNotes 8.5.2 \n * Lotus iNotes 8.5.3 FP6 \n * iNotes 9.0 \n * iNotes 9.0.1 FP2 \n * iNotes 9.0.1 FP4 \n * iNotes 9.0.1 FP5 \n * iNotes 9.0.1 FP6 \n * iNotes 9.0.1 FP7 \n * iNotes 9.0.1 FP8\n\niNotes must have been configured when the Domino server was initially configured. Starting with IBM Content Collector 4.0.1 Fix Pack 6, IBM Lotus Domino/Notes 9.0.1 FP7,FP8 are supported\n\nStarting with IBM Content Collector 4.0.1 Fix Pack 4, IBM Lotus Domino/Notes 9.0.1 FP6 is supported \n\n Starting with IBM Content Collector 4.0.1 Fix Pack 2, IBM Lotus Domino/Notes 9.0.1 FP4, FP5, Mozilla Firefox 35 and Microsoft Edge are supported. IBM Content Collector supports the latest fix packs of the server and client software. \n\nWindows 10 is supported starting with IBM Content Collector 4.0.1 Fix Pack 2.\n\nIf you want to use the IBM Content Collector Offline Repository in Notes, the following packages are required on the workstation that runs the Notes client, depending on the version of IBM Content Collector that was used to enable the Domino template: \n\nContent Collector version used to enable Domino template Required package on client workstation IBM Content Collector 2.2 (or earlier) Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC Security Update [http://www.microsoft.com/en-us/download/details.aspx?id=26347] IBM Content Collector 3.0, 4.0, or 4.0.1 Microsoft Visual C++ 2010 Redistributable Package [http://www.microsoft.com/downloads/details.aspx?FamilyID=A7B7A05E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en&displaylang=en] To use IBM Content Collector Search, Lotus Notes R8.5.1 or later with standard configuration is required. Basic configuration is not supported. \n\nIf you want to use IBM Content Collector Search in Notes against a database without an index, the following packages are required on the workstation that runs the Notes client:\n\n * Microsoft Visual C++ 2010 Redistributable Package [http://www.microsoft.com/downloads/details.aspx?FamilyID=A7B7A05E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en&displaylang=en]\n * Microsoft Security Advisory: Insecure library loading could allow remote code execution [http://support.microsoft.com/kb/2533623] \n\n\n\nHow to get: \n\nYou can purchase Domino from the following website: IBM Domino [http://www.ibm.com/support/docview.wss?uid=swg24033984]\n\nVIRTUALIZATION\nThe following table describes the supported virtualization methods and software versions for running a Lotus Notes client on Citrix:\n\n\nVirtualization Method Required software Virtual desktop Lotus Domino/Lotus Notes 8.5.3 or \nDomino/Notes 9.0 Social Edition\nCitrix XenDesktop 7.0 Domino/Notes 9.0\nCitrix XenDesktop 7.5 or later Application installed on server Lotus Domino/Lotus Notes 8.5.3 or \nDomino/Notes 9.0 Social Edition\nCitrix XenApp 6.5 Application streamed to server Lotus Domino/Lotus Notes 8.5.3 or \nDomino/Notes 9.0 Social Edition\nCitrix XenApp 6.5 Application streamed to client Lotus Domino/Lotus Notes 8.5.1 or \nDomino/Notes 9.0 Basic\nCitrix XenApp 6.5 Hosted application in your datacenter Domino/Notes 9.0 \nCitrix XenDesktop/Citrix XenApp 7.5 or later Local Access App Domino/Notes 9.0 \nCitrix XenDesktop/Citrix XenApp 7.5 or later Microsoft Application Virtualization applications (App-V) Domino/Notes 9.0 \nCitrix XenDesktop/Citrix XenApp 7.5 or later For the virtualization method application streamed to client, the following restriction applies:\n\n * Automatic client document retrieval does not work in the standard configuration of Notes client version 8.5, 8.5.3, or 9.\n\n \n\n\nBack to top\n\nMICROSOFT EXCHANGE\nSERVER\nThe following table describes the supported versions of Microsoft Exchange Server:\n\nServer software Notes * Microsoft Exchange Server 2007 Standard and Enterprise Edition with Service Pack 3 Update Rollup 11 \n * Microsoft Exchange Server 2010 Standard and Enterprise Edition with Service Pack 2 Update Rollup 4 or Service Pack 3 \n * Microsoft Exchange Server 2013 Standard and Enterprise Edition with Service Pack 1 (KB2860242 [http://support.microsoft.com/kb/2860242]) \n * Microsoft Exchange Server 2016 Standard and Enterprise Edition \n\nYou must not install Microsoft Exchange Server on the IBM Content Collector server. How to get:\nYou can purchase Microsoft Exchange Server from www.microsoft.com [http://www.microsoft.com].\n\nOUTLOOK EXTENSION\nBefore you add the IBM Content Collector Outlook Extension to a client workstation, ensure that the required software is installed on that workstation: \n\nOperating system Client application Other software requirements Notes * Windows 7 Professional Service Pack 1 \n * Windows 7 Ultimate Service Pack 1 \n * Windows 7 Enterprise Service Pack 1 \n * Windows 8 Professional Edition \n * Windows 8.1 Professional Edition \n * Windows 10 Professional Edition \n * Windows 10 Enterprise Edition\n\n * Microsoft Outlook 2007 Service Pack 3 \n * Microsoft Outlook 2010 Service Pack 2 \n * Microsoft Outlook 2013 \n * Microsoft Outlook 2016\n\n * .NET Framework 4.5 (or later)\n\nYou can install the IBM Content Collector Outlook Extension irrespective of the language in which Outlook is installed.\n\nAn Outlook logon profile containing the parameters for the connection to the Exchange server must exist.\n\nThere are different Outlook extension installable to be used with 32-Bit and 64-Bit versions of Microsoft Outlook * Mozilla Firefox 14, 17 or 24 ESR, 24, 28, 31 ESR, 32, 33, 34, or 35 \n * Microsoft Internet Explorer 8, 9, 10, or 11 \n * Microsoft Edge \n * Chrome 60\n\nMicrosoft Outlook 64 Bit version is supported starting with IBM Content Collector 4.0.1 Fix Pack 8 with Outlook Extension (64-bit) installable.\n\nWindows 10, Microsoft Edge and Microsoft Outlook 2016 are supported starting with IBM Content Collector 4.0.1 Fix Pack 2.\n\nChrome browser is supported starting with IBM Content Collector 4.0.1 Fix Pack 6\n\nVIRTUALIZATION\nThe following table describes the supported virtualization methods and software versions for running Outlook Extension on Citrix:\n\n\nVirtualization Method Required software Virtual desktop Microsoft Outlook 2010\nCitrix XenDesktop 7.5 or later\nMicrosoft Outlook 2013\nCitrix XenDesktop 7.6 or later Hosted application in your datacenter Microsoft Outlook 2010\nCitrix XenDesktop/Citrix XenApp 7.5 or later\nMicrosoft Outlook 2013\nCitrix XenDesktop/Citrix XenApp 7.6 or later Local Access App Microsoft Outlook 2010\nCitrix XenDesktop/Citrix XenApp 7.5 or later\nMicrosoft Outlook 2013\nCitrix XenDesktop/Citrix XenApp 7.6 or later Microsoft Application Virtualization applications (App-V) Microsoft Outlook 2010\nCitrix XenDesktop/Citrix XenApp 7.5 or later\nMicrosoft Outlook 2013\nCitrix XenDesktop/Citrix XenApp 7.6 or later \n\n\nOUTLOOK WEB APP (OWA)\n Outlook Web App (OWA) Extension\n\nTo install the IBM Content Collector Outlook Web App Extension on the Exchange server, the following requirements must be met: \n\nExchange Server version (required) Other software requirements Notes * Microsoft Exchange Server 2007 Service Pack 3 (or later) \n * Microsoft Exchange Server 2010 SP2 \n * Microsoft Exchange Server 2013 SP1 \n * Microsoft Exchange Server 2016 \n\n.NET Framework 4.5 Full Profile (or later) The OWA Extension must be installed on the Exchange Server that has the Client Access Server (CAS) role. Outlook Web App (OWA) Service\n\nApart from the Outlook Web App Extension that is installed on the Exchange server, the Outlook Web App Service is installed on top of a Microsoft Internet Information Service (IIS) Server. The following table lists the operating system and other requirements for the OWA Service.\n\n \n\nExchange Server version Operating system for the Outlook Web App Service (required) Other software requirements * Microsoft Exchange Server 2007 Service Pack 3 (or later) \n * Microsoft Exchange Server 2010 SP2\n\n * Windows Server 2008 Service Pack 2 \n * Windows Server 2008 R2 Service Pack 1\n\n * Microsoft IIS Server 6 or 7 \n * .NET Framework 4.5\n\n * Microsoft Exchange Server 2013 SP1\n\n * Windows Server 2008 R2 Service Pack 1 \n * Windows Server 2012 R2\n\n * Microsoft IIS Server 7.5 (or later)\n\n * Microsoft Exchange Server 2016 \n\n * Windows Server 2012 \n * Windows Server 2012 R2\n\n * .NET Framework 4.5.2\n\nIn the Internet Information Service (IIS) Manager: \n\n * Set the Web Service Extension ASP.NET V4.5 to Allowed. \n * Set the identity of the application pool where the OWA service resides to NetworkService. \n * Set the .NET Framework version to v4.5 \n * Disable the forms authentication method for the OWA Service (afuowa) after the installation. IBM Content Collector OWA Service does not support forms authentication in Microsoft IIS 7.0. \n\n\nHow to get: \n\nYou can purchase Microsoft IIS Server and .NET Framework from www.microsoft.com [http://www.microsoft.com].\n\n\nOutlook Web App (OWA) client \n\nTo be able to use the Outlook Web App functions, clients require the following software on their workstations: \n\n \n\nExchange Server version Software prerequisites for OWA clients * Microsoft Exchange Server 2007 Service Pack 3 (or later) \n * Microsoft Exchange Server 2010 SP2\n\n * .NET Framework 2.0 (or later) \n * Microsoft Internet Explorer 8, 9, or 10\n\n * Microsoft Exchange Server 2013 SP1\n\n * Microsoft Internet Explorer 9, 10 or 11 \n * Google Chrome 13 \n * Microsoft Edge\n\n * Microsoft Exchange Server 2016 \n\n * Microsoft Internet Explorer 10 or 11 \n * Microsoft Edge\n\nThe following restrictions apply: \n\n * IBM Content Collector OWA support does not work with if the option \"Use the blind and low vision experience\" in the OWA settings is used. \n * IBM Content Collector OWA support works only with OWA Premium Mode. \n * IBM Content Collector OWA support on Exchange 2010 supports only the Internet Explorer browser and not Apple Safari, Mozilla Firefox, and so on although Microsoft OWA 2010 supports other browsers. \n * IBM Content Collector OWA support on Exchange 2013 supports the Google Chrome browser in Apple Mac OS X 10.9.x (32-bit and 64-bit) \n * Microsoft Edge is supported starting with IBM Content Collector 4.0.1 Fix Pack 2 \n * IBM Content Collector OWA support on Exchange 2016 is supported starting from IBM Content Collector 4.0.1 Fix Pack 3 Back to top\n \n \n \n \n \n\nSMTP EMAIL\nIBM Content Collector can archive SMTP/MIME email. The source mail system requires a specific setup to send all SMTP/MIME email to be processed to IBM Content Collector. \nIn addition to SMTP forwarding for Microsoft Exchange and Lotus Domino, the respective setup has been tested for these mail systems:\n\n\n\nMail system Notes Microsoft Exchange Online See technote 1648828 [http://www.ibm.com/support/docview.wss?uid=swg21648828] for information about how to set up journal forwarding from Microsoft Exchange Online to IBM Content Collector. Google Mail for Business See technote 1648572 [http://www.ibm.com/support/docview.wss?uid=swg21648572] for information about archiving email from Google Mail for Business with IBM Content Collector. \nBack to top\n\nMICROSOFT SHAREPOINT\nThe following table describes the supported versions of Microsoft SharePoint: \n\n \n\nMicrosoft SharePoint Notes Microsoft SharePoint Server 2010 with Service Pack 2 (Standard or Enterprise edition) [/support/docview.wss?uid=swg27042658&aid=1] Microsoft SharePoint Foundation 2010 with Service Pack 2 Microsoft SharePoint Server 2013 with Service Pack 1 (Standard or Enterprise edition) Only functionality that is also provided by Microsoft SharePoint 2010 is supported. Microsoft SharePoint Foundation 2013 with Service Pack 1 Microsoft SharePoint Server 2016 (Standard and Enterprise edition) Only functionality that is also provided by older Microsoft SharePoint servers is supported. \nMicrosoft SharePoint Foundation edition is no longer available in the SharePoint Server 2016 release. As an alternative end users can use 180 days trial for Standard or Enterprise edition.\n\nHow to get:\nYou can purchase Microsoft SharePoint from www.microsoft.com [http://www.microsoft.com].\n\nBack to top\n\nIBM CONNECTIONS\n\nThe following table describes the supported versions of IBM Connections: \n\n \n\nIBM Connections IBM Connections 4.5 Documents from IBM Connections can be archived in the following archive systems: \n\n * IBM Content Manager Enterprise Edition (all supported versions) \n * IBM FileNet P8 Content Engine 5.1 or later with IBM Content Search Services\n\nHow to get: \n\nYou can purchase IBM Connections from the following website: IBM Connections [http://www.ibm.com/support/docview.wss?uid=swg24034473].\n\nBack to top\n\nFILE SYSTEM SUPPORT\nThe following table describes supported file systems. \n\nFile system Notes NTFS V3.1\n\nDepending on the repository capabilities, the maximum supported file size is up to 30 GB.\n\nIBM Content Collector supports Microsoft SMB Protocol versions 1.0, 2.0 and 3.0 for Windows file server ReFS (Windows 2012) Novell Netware V6.5 SP 8 Novell Open Enterprise Server 2 SP3\nNovell Open Enterprise Server 11 Samba V3.3 Services for NFS for Windows 2008, 2008 R2, 2012, 2016 Windows Server 2016 is supported as File System collection source starting with IBM Content Collector 4.0.1 Fix Pack 8\n\nRestriction: If IBM Content Collector is installed on Windows 2008 and you are archiving from Novell file servers, Novell Client 2 SP1 IR 6 or later must be installed. \n\nThe File System Repository Connector also allows for archiving to cloud file systems. \n\n\nBack to top\n\n\n\nARCHIVE SERVERS\nIBM CONTENT MANAGER\nREPOSITORY SOFTWARE\nThe following table describes the supported operating systems and the connector that is required on the IBM Content Collector server: \n\nArchive system (repository software) Operating system Required connector on IBM Content Collector Server Notes IBM Content Manager Enterprise Edition V8.4.2 Fix Pack 3 and V8.4.3 Fix Pack 3\n\nFor the required level of the database management system, see the IBM Content Manager system requirements [http://www.ibm.com/support/docview.wss?uid=swg27036382]. * AIX \n * Linux \n * Windows\n\nIBM Content Manager Version 8 connector The connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3 or V8.4.3 Fix Pack 3. Use the Setup Type Connector.\n\nSupport for IBM Content Manager V8.4 on Linux requires a Linux 32-bit system on an Intel platform or Linux for System z. For details, see the technote Content Manager Enterprise Edition Version 8.4 support for 32-bit / 64-bit for Linux/UNIX/Windows [http://www.ibm.com/support/docview.wss?uid=swg21293849].\n\nImportant: For IBM Content Manager Enterprise Edition V8.4.3, apply the fix that is described in Security Bulletin: Content Manager Enterprise Edition and use of Oracle Outside In Technology Security Vulnerability (CVE-2013-5791, CVE-2013-5763) [http://www.ibm.com/support/docview.wss?uid=swg21660964]. IBM Content Manager Enterprise Edition V8.5\n\nFor the required level of the database management system, see the IBM Content Manager system requirements [http://www.ibm.com/support/docview.wss?uid=swg27038464]. * AIX \n * Linux \n * Windows\n\nIBM Content Manager Version 8 connector On 64-bit systems, the connector is provided by the configuration manager that is included in IBM Content Manager Enterprise Edition V8.5. On 32-bit systems, the connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3 or V8.4.3 Fix Pack 3.\n\nConfigure item types to be enabled for indexing by Net Search Extender and not DB2 Text Search.\n\nIf you use IBM Content Manager Version 8.5 on AIX, text search requires IBM Content Collector Text Search Support V4.0.\n\nImportant: For IBM Content Manager Enterprise Edition V8.5, apply the fix that is described in Security Bulletin: Content Manager Enterprise Edition and use of Oracle Outside In Technology Security Vulnerability (CVE-2013-5791, CVE-2013-5763) [http://www.ibm.com/support/docview.wss?uid=swg21660964]. IBM Content Manager Enterprise Edition V8.5 Fix Pack 4\n\nFor the required level of the database management system, see the IBM Content Manager system requirements [http://www.ibm.com/support/docview.wss?uid=swg27038464]. * AIX \n * Linux \n * Windows\n\nIBM Content Manager Version 8 connector On 64-bit systems, the connector is provided by the configuration manager that is included in IBM Content Manager Enterprise Edition V8.5 Fix Pack 4. On 32-bit systems, the connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3 or V8.4.3 Fix Pack 3.\n\nConfigure item types to be enabled for indexing by Net Search Extender and not DB2 Text Search.\n\nIf you use IBM Content Manager Version 8.5 Fix Pack 4 on AIX, text search requires IBM Content Collector Text Search Support V4.0. IBM Content Manager for z/OS Version V8.4.2, V8.4.3, and V8.4.3 Fix Pack 1\n * z/OS\n\nIBM Content Manager Version 8 connector The connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3, V8.4.3, or V8.4.3 Fix Pack 1. Use the Setup Type Connector.\n\nIBM Content Manager for z/OS can be used as a repository for files and Microsoft SharePoint documents. Email documents are supported starting with V8.4.3 Fix Pack 1. Text search is not supported. IBM Content Manager for z/OS V8.5 * z/OS\n\nIBM Content Manager Version 8 connector On 64-bit systems, the connector is provided by the configuration manager that is included in IBM Content Manager Enterprise Edition V8.5. On 32-bit systems, the connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3 or V8.4.3 Fix Pack 3.\n\nText search is not supported. How to get:\nYou can purchase IBM Content Manager from the following websites:\n\n\n * Content Manager Enterprise Edition [http://www.ibm.com/support/docview.wss?uid=swg24035460]\n * Content Manager for z/OS [http://www.ibm.com/software/products/us/en/conmanzos]\n\nTEXT-SEARCH FUNCTION\nTo enable the text-search function (full-text search) for a Content Manager archive system, the IBM Content Collector indexer for text search must be installed. While IBM Content Collector supports archiving to Content Manager archive systems with DB2 databases or Oracle databases, the text-search function is not supported for archive systems with Oracle databases.\n\n The indexer for text search requires IBM Content Manager Enterprise Edition and the following software:\n\nNet Search Extender\nThe required version depends on the version of DB2 that is used by IBM Content Manager. Additional Net Search Extender e-fixes (required) Notes AIX Power 6.1 and 7.1 IBM Net Search Extender 9.1 for DB2 V9.1 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24024133] [/support/docview.wss?uid=swg27042658&aid=1] [/support/docview.wss?uid=swg27042658&aid=1] IBM Net Search Extender and the required fix packs and e-fixes must be installed on the IBM Content Manager server. Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 AIX Power 6.1 and 7.1 IBM Net Search Extender 9.5 for DB2 V9.5 Fix Pack 5 [http://www.ibm.com/support/docview.wss?uid=swg24025481] Windows\n\nIC58821\nIP22989 Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 AIX Power 6.1 and 7.1 IBM Net Search Extender 9.7 for DB2 V9.7 Fix Pack 4 [http://www.ibm.com/support/docview.wss?uid=swg24029745] [/support/docview.wss?uid=swg27042658&aid=1] [/support/docview.wss?uid=swg27042658&aid=1] Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 AIX Power 6.1 and 7.1 IBM Net Search Extender 10.1 for DB2 V10.1 Fix Pack 2 [http://www.ibm.com/support/docview.wss?uid=swg24033997] [/support/docview.wss?uid=swg27042658&aid=1] [/support/docview.wss?uid=swg27042658&aid=1] Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 AIX Power 6.1 and 7.1 IBM Net Search Extender 10.5 for DB2 10.5 Fixpack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040522] [/support/docview.wss?uid=swg27042658&aid=1] [/support/docview.wss?uid=swg27042658&aid=1] Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 How to get: \n\nYou can download IBM Content Manager fix packs and Net Search Extender e-fixes from the following websites:\n\n * Content Manager fix packs [http://www.ibm.com/support/docview.wss?uid=swg27009038]\n * Net Search Extender e-fixes [ftp://public.dhe.ibm.com/ps/products/db2extenders/fixes]\n\nBack to top\n\nIBM FILENET P8\nREPOSITORY SOFTWARE\nThe following table describes the supported operating systems and the FileNet APIs that are required for the IBM Content Collector server: \n\nArchive system (repository software) Operating system Required APIs on IBM Content Collector Server Notes IBM FileNet P8 Content Engine 5.0.0.1, 5.1 Fix Pack 2, 5.2, or 5.2.1 \n\nFor the required level of the database management system, see the IBM FileNet P8 system requirements [http://www.ibm.com/support/docview.wss?uid=swg27013654]. * AIX \n * Linux \n * Solaris \n * Windows\n\n.NET Clients The .NET Clients component is provided through the FileNet P8 Content Engine installer. Java Clients (Other Applications) The Java Clients component is provided through the FileNet P8 Content Engine Client installer. [/support/docview.wss?uid=swg27042658&aid=1] Important: For IBM FileNet P8 Content Engine 5.1 and 5.2, apply the fix that is described in Security Bulletin: IBM FileNet Content Manager and IBM Content Foundation – Oracle Outside In Technology security vulnerabilities (CVE-2013-5791, CVE-2013-5763) [http://www.ibm.com/support/docview.wss?uid=swg21660219]. IBM Content Foundation V5.2 or V5.2.1 \n\nFor the required level of the database management system, see the IBM Content Foundation system requirements [http://www.ibm.com/support/docview.wss?uid=swg27038265]. * AIX \n * Linux \n * Solaris \n * Windows\n\n.NET Clients The .NET Clients component is provided through the IBM Content Foundation Content Platform Engine installer. Java Clients (Other Applications) The Java Clients component is provided through the IBM Content Foundation Content Platform Engine installer. [/support/docview.wss?uid=swg27042658&aid=1] Important: For IBM Content Foundation V5.2.0, apply the fix that is described in Security Bulletin: IBM FileNet Content Manager and IBM Content Foundation – Oracle Outside In Technology security vulnerabilities (CVE-2013-5791, CVE-2013-5763) [http://www.ibm.com/support/docview.wss?uid=swg21660219]. IBM FileNet Image Services 4.1.2 or 4.2 * AIX \n * HP-UX \n * Solaris \n * Windows\n\nIBM FileNet IDM Desktop IBM FileNet Image Services can only be used as a repository for files. It is not suitable for email. Text search and retrieving archived content through stub links is not supported. If you use IBM FileNet P8 with IBM Legacy Content Search Engine (Verity), dynamic retention management is not supported.\n\nImportant: The fix pack level of the Content Engine of IBM Content Collector Server must match the fix pack level of the Content Engine server for both the .NET Clients and the Java Clients components.\n\nHow to get: \n\nYou can purchase FileNet P8 from the following websites:\n\n\n * FileNet Content Manager [http://www.ibm.com/support/docview.wss?uid=swg24034227]\n * Content Foundation [http://www.ibm.com/support/docview.wss?uid=swg24034868]\n * FileNet Image Services [http://www.ibm.com/support/docview.wss?uid=swg24020652]\n\nTEXT-SEARCH FUNCTION\nThe text-search function (full-text search) for FileNet archive systems with IBM Legacy Content Search Engine requires Autonomy IDOL K2. With IBM Legacy Content Search Engine (Verity), dynamic retention management is not supported\n\nTo use the text-search function (full-text search) for FileNet archive systems with IBM Content Search Services, IBM Content Collector Content Search Services Support must be installed on the Content Search Services server. If the Content Search Services server runs on AIX, Linux, or Solaris, ensure that Java 1.6 is installed. \n\nContent Search Services Support requires the following FileNet P8 components: \n\n\nFileNet P8 components Required on which server Operating system Notes IBM FileNet P8 Content Engine 5.1 Fix Pack 3 with IF001 or later, or 5.2 Fix Pack 2 with IF001 or later, or 5.2.1\nIBM Content Foundation V5.2 or V5.2.1 FileNet P8 Content Engine server * AIX \n * Linux \n * Solaris \n * Windows\n\nInterim Fixes are available on Fix Central [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=FileNet+Product+Family&product=ibm/Information+Management/FileNet+Content+Engine&release=5.1.0.0&platform=All&function=all].\n\nThe FileNet P8 Content Engine server must be configured to use Content Search Services. IBM FileNet P8 Content Search Engine Client 5.1 Fix Pack 2 or Content Search Engine Client 5.2 Content Search Services server * AIX \n * Linux \n * Solaris \n * Windows\n\nThe client component is provided through the FileNet P8 Content Engine Client 5.1 installer or the FileNet P8 Content Engine 5.2 installer. IBM FileNet P8 Content Search Services 5.1 with IF005 or later, or 5.2 with IF002 or later, or 5.2.1\n\nFor details about the supported operating systems, see the IBM FileNet P8 system requirements [http://www.ibm.com/support/docview.wss?uid=swg27013654]. Content Search Services server * AIX \n * Linux \n * Windows\n\nInterim Fixes are available on Fix Central [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=FileNet+Product+Family&product=ibm/Information+Management/FileNet+Content+Search+Services&release=5.1.0.0&platform=All&function=all].\n\nImportant: For IBM FileNet P8 Content Search Services 5.1 and 5.2, apply the fix that is described in Security Bulletin: IBM FileNet Content Manager and IBM Content Foundation – Oracle Outside In Technology security vulnerabilities (CVE-2013-5791, CVE-2013-5763) [http://www.ibm.com/support/docview.wss?uid=swg21660219]. Java Clients (Other Applications) 5.1 Fix Pack 2 or 5.2 * Content Search Services server \n * IBM Content Collector server\n\n * AIX \n * Linux \n * Solaris \n * Windows\n\nThe Java Clients component is provided through the FileNet P8 Content Engine Client 5.1 installer or the FileNet P8 Content Engine 5.2 installer. .NET Clients 5.1 Fix Pack 2 or 5.2 IBM Content Collector server * AIX \n * Linux \n * Solaris \n * Windows\n\nThe .NET Clients component is provided through the FileNet P8 Content Engine installer. \nThe text-search function (full-text search) for IBM Content Foundation requires the Content Search Services component. Back to top\n\n\n\nLEGACY RESTORE\n\nLegacy restore provides access to documents that were archived with IBM CommonStore for Lotus Domino or IBM CommonStore for Exchange Server. Legacy restore supports the same archive systems as the CommonStore products and has the same system requirements to connect to these archive systems as the CommonStore products:\n\nSystem requirements for IBM CommonStore for Lotus Domino [http://www.ibm.com/support/docview.wss?uid=swg27010342]\nSystem requirements for IBM CommonStore for Exchange Server [http://www.ibm.com/support/docview.wss?uid=swg27010343]\n\nIn addition, Legacy Restore also supports the archive systems IBM Content Manager Enterprise Edition V8.5 and IBM Content Manager for z/OS V8.5. \n\nThere are some limitations when using IBM Content Collector Legacy Restore instead of the CommonStore products, including the following restrictions: \n\n * IBM Content Collector Legacy Restore provides read-only access to documents, but no write access. \n * For documents that are stored in Content Manager OnDemand or Content Manager for z/OS, search is not supported. \n * For multi-part document model item types in Content Manager 8, only the first part can be previewed.\n\nIBM Content Collector Legacy Restore supports the same operating systems as IBM Content Collector Server. \n\nBack to top\n\n\n\n\n\n\nRETENTION POLICY DISTRIBUTION SUPPORT\nTo use IBM Content Collector Retention Policy Distribution Support, you must install IBM Atlas Policy Suite, which is the client interface in Global Retention Policy and Schedule Management for managing document retention schedules.\n\nThe following table describes the supported versions of IBM Atlas Policy Suite:\n\n\n\nIBM Atlas Policy Suite IBM Atlas Policy Suite 6.0.3 How to get: \n\nYou can purchase IBM Atlas Policy Suite from the following website: IBM Atlas Policy Suite [https://www.ibm.com/support/entdocview.wss?uid=swg24036335]. \n\nBack to top\n\n\n\n\n\n\nOPTIONAL SOFTWARE\nThe following table describes the software that is required if you want to use optional functions of IBM Content Collector:\n\nFunction Software Use IBM eDiscovery Manager to search and collect archived documents IBM eDiscovery Manager V2.2.1 or V2.2 Fix Pack 4 Use IBM Content Classification to classify documents IBM Content Classification V8.8 Declare records against documents in a FileNet P8 archive system IBM Enterprise Records V5.1.1, V5.1.2, or V5.2 Fix Pack 1 Access documents in an archive system IBM FileNet Workplace XT V1.1.5 Fix Pack 1 or Fix Pack 2\nIBM Content Navigator V2.0, V2.0.1, V2.0.2, V2.0.3, V3.0 or V3.0.1 How to get: \n\nYou can purchase these products from the following websites:\n\n * IBM eDiscovery Manager [http://www.ibm.com/support/docview.wss?uid=swg24035931]\n * IBM Content Classification [http://www.ibm.com/support/docview.wss?uid=swg24029115]\n * IBM Enterprise Records [http://www.ibm.com/support/docview.wss?uid=swg24035858]\n * IBM Content Navigator [http://www.ibm.com/support/docview.wss?uid=swg24034327]\n\nBack to top\n\n\n\nIBM CONTENT COLLECTOR PRODUCT REPORTS\nCONTENT COLLECTOR FOR EMAIL\nREQUIREMENTS\nBY PLATFORM\n * Mac OS [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&osPlatforms=Mac OS]\n\n * Windows [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&osPlatforms=Windows]\n\n * Supported Hypervisors [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/vesForProduct?deliverableId=1385722855736]\n\n\n\n\nREQUIREMENTS\nBY COMPONENT\n * FileNet P8 Content Search Services Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_862A48C058E511E3A11D923472D26C14]\n * Legacy Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_8626C65058E511E3A11D923472D26C14]\n * Notes Client Extension [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Desktop_862AE50058E511E3A11D923472D26C14]\n\n * Outlook Extension [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Desktop_862BA85058E511E3A11D923472D26C14]\n * Outlook Web App Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_862789A058E511E3A11D923472D26C14]\n * Server [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_862825E058E511E3A11D923472D26C14]\n\n * SharePoint Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_8628E93058E511E3A11D923472D26C14]\n * Text Search Support for Content Manager [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_8629857058E511E3A11D923472D26C14]\n\n\n\n\nRELATED REQUIREMENTS\nNo related requirements.\n\n\n\n\n Back to top \n\nCONTENT COLLECTOR FOR FILE SYSTEMS\nREQUIREMENTS\nBY PLATFORM\n * Windows [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&osPlatforms=Windows]\n\n\n * Supported Hypervisors [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/vesForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A]\n\n\n\n\nREQUIREMENTS\nBY COMPONENT\n * FileNet P8 Content Search Services Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&duComponentIds=Server_F6D064B0C7E811E4A93F4F818B63D91A]\n\n * Server [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&duComponentIds=Server_F6C89C80C7E811E4A93F4F818B63D91A]\n\n * Text Search Support for Content Manager [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&duComponentIds=Server_F6C9D500C7E811E4A93F4F818B63D91A]\n\n\n\n\n\n\nRELATED REQUIREMENTS\nNo related requirements.\n\n\n\n\n Back to top \n\nCONTENT COLLECTOR FOR IBM CONNECTIONS\nREQUIREMENTS\nBY PLATFORM\n * Windows [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&osPlatforms=Windows]\n\n\n * Supported Hypervisors [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/vesForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A]\n\n\n\n\nREQUIREMENTS\nBY COMPONENT\n * FileNet P8 Content Search Services Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&duComponentIds=Server_1CE258D0C7ED11E4A93F4F818B63D91A]\n\n * Server [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&duComponentIds=Server_1CE035F0C7ED11E4A93F4F818B63D91A]\n\n * Text Search Support for Content Manager [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&duComponentIds=Server_1CE1BC90C7ED11E4A93F4F818B63D91A]\n\n\n\n\nRELATED REQUIREMENTS\nNo related requirements.\n\n \n\n\n\n\n Back to top \n\nCONTENT COLLECTOR FOR MICROSOFT SHAREPOINT\nREQUIREMENTS\nBY PLATFORM\n * Windows [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&osPlatforms=Windows]\n\n\n * Supported Hypervisors [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/vesForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A]\n\n\n\n\nREQUIREMENTS\nBY COMPONENT\n * FileNet P8 Content Search Services Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E3176240C7EB11E4A93F4F818B63D91A]\n * Server [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E3151850C7EB11E4A93F4F818B63D91A]\n\n * SharePoint Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E315DBA0C7EB11E4A93F4F818B63D91A]\n * Text Search Support for Content Manager [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E3169EF0C7EB11E4A93F4F818B63D91A]\n\n\n\n\nRELATED REQUIREMENTS\nNo related requirements.\n\n\n\n\n Back to top"
}
] |
TRAIN_Q412 | Can't delete BPD instances in Process Designer
I'm not sure what is wrong with some BPD instances.
When an instance is Active, but seems to not be able determine the next activity, I can't delete that instance in the Process Designer.
Every time I try to delete or terminate the instance, this message appears "Delete BPD Instances (0%)", but it get stuck there and nothing happens.
I checked the Event Monitor, and there are few Jobs scheduled there... All show the same message: Notify BPD xxxxx of notification. Is this a tip what could be going wrong?
What is the possible solution to this issue? | - | true | [] |
TRAIN_Q413 | VScan not working after migrating Datacap Application from 8.1 to 9.0.1
Hello,
I have recently migrated one datacap application developed in Datacap 8.1 to Datacap 9.0.1. I followed the complete instruction provided in the link
http://www.ibm.com/support/knowledgecenter/SSZRWV_9.0.1/com.ibm.dc.develop.doc/dcadv001.htm
After migration, when I tried to execute the application using Datacap Desktop. I got errors that "This batch has no data to process. Aborting" and "Unable to run queue". I am attaching the screenshots of error. I am also attaching the DStudio rule's screenshot.
I have verified and configured all the required settings.
Please guide if someone has faced the similar issue and resolved it.
Thanks.
| The "Bind DCO type to panel" for Datacap Desktop is case-sensitive. Be sure the DCO name matches as it appears in Datacap Studio (both the spelling and case-sensitivity). | false | [
{
"filename": "swg21967312.txt",
"text": "Title: IBM Error when launching Scan task from Datacap Desktop. - United States\n\nText:\nDesktop; No data; Scan; VScan TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Receiving the following error message when attempting to launch up Scan task from Datacap Desktop:\n\"This batch has no data to process. Aborting.\" \n\nThen followed by this error: \n\"Unable to run queue.\" \n\nDIAGNOSING THE PROBLEM\nThe panel for TravelDocs contained a value with all upper-case letter [eg. TRAVELDOCS], which caused the error to occur when attempting to launch the Scan task from Datacap Desktop\n\nRESOLVING THE PROBLEM\nThe \"Bind DCO type to panel\" for Datacap Desktop is case-sensitive. Be sure the DCO name matches as it appears in Datacap Studio (both the spelling and case-sensitivity). \n\nLogon to TMWeb client. \n\nGo to Administrator tab \n\nSelect the VScan task from the Workflow. \n\nClick Setup under Program. \n\nThen change the value of the Panel to match what is in Datacap Studio. For example \"TRAVELDOCS\" to \"TravelDocs\" \n\nClick Save\n\n[/support/docview.wss?uid=swg21967312&aid=1] [/support/docview.wss?uid=swg21967312&aid=1]\n\n[/support/docview.wss?uid=swg21967312&aid=2] [/support/docview.wss?uid=swg21967312&aid=2]\n[/support/docview.wss?uid=swg21967312&aid=3] [/support/docview.wss?uid=swg21967312&aid=3]"
}
] |
TRAIN_Q414 | Is MQ V7.0 is going out of support?
Is Websphere MQ V7.0 is going out of support? | IBM has withdrawn support for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ for z/OS V7.0.1 and V7.0.0, | false | [
{
"filename": "swg21674407.txt",
"text": "Title: IBM Announcement: End of Support for WebSphere MQ and WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 and WebSphere MQ Telemetry V7.0.1 - United States\n\nText:\n NEWS\n\nABSTRACT\n IBM has withdrawn support for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ for z/OS V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition for z/OS V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1. \n\nCONTENT\n\n\nTAB NAVIGATION\n * WebSphere MQ and File Transfer Edition V7.0.1 and V7.0.0 • MQ Telemetry V7.0.1 selected tab\n\nTAB NAVIGATION\n * What were the end of support dates for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1?\n * Do these announcements affect WebSphere MQ File Transfer Edition V7.0.4, V7.0.3 and V7.0.2, WebSphere MQ Advanced Message Security V7.0.1, or WebSphere MQ Hypervisor Edition V7.0.1?\n * What replacement products are available?\n * How do I check which version I am currently running?\n * Is any information available to help me upgrade to a later version?\n * How do I purchase a support extension for my current version?\n * When a WebSphere MQ server product goes out of support, does the client and file transfer agent also go out of support?\n * Are these products still supported when they are bundled with another IBM product?\n * Is the WebSphere MQ V7.0 Resource Adapter supported in WebSphere Application Server?\n * Is documentation still available for these products?\n * How do I obtain installation images for these products if I still need them?\n * Is there an IBM MQ V9.0 or MQ V8.0 trial version available for download?\n\n\n\n[/support/docview.wss?uid=swg21674407&aid=1]\n\n\n\n\nWHAT ARE THE END OF SUPPORT DATES FOR WEBSPHERE MQ V7.0.1 AND V7.0.0, WEBSPHERE MQ FILE TRANSFER EDITION V7.0.1 AND V7.0.0, AND WEBSPHERE MQ TELEMETRY V7.0.1?\n\n * \n * Product Version Release Date End of Support Platforms WebSphere MQ V7.0.1 28 Aug 2009 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-245] 30 Apr 2015 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] AIX, HP-UX (Itanium), HP-UX (PA-RISC), i5/OS, Linux (POWER), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC), Solaris (x86-64), Windows (x86) WebSphere MQ for z/OS V7.0.1 25 Sep 2009 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-248] 30 Sep 2015 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-150] z/OS WebSphere MQ V7.0.0 16 Jun 2008 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-068] 30 Apr 2015 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] AIX, HP-UX (Itanium), HP-UX (PA-RISC), i5/OS, Linux (POWER), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC), Solaris (x86-64), Windows (x86) WebSphere MQ for z/OS V7.0.0 27 Jun 2008 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-067] 30 Sep 2011 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS910-014] z/OS WebSphere MQ File Transfer Edition V7.0.1 05 Jun 2009 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-118] 30 Sep 2014 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-158] AIX, HP-UX (Itanium), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC), Windows (x86) WebSphere MQ File Transfer Edition for z/OS V7.0.1 12 Jun 2009 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-119] 30 Sep 2014 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-149] z/OS WebSphere MQ File Transfer Edition V7.0.0 05 Dec 2008 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-331] 30 Sep 2014 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-158] AIX, HP-UX (Itanium), Linux (x86), Solaris (SPARC), Windows (x86) WebSphere MQ File Transfer Edition for z/OS V7.0.0 12 Dec 2008 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-339] 30 Sep 2014 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-149] z/OS WebSphere MQ Telemetry V7.0.1 27 Aug 2010 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS210-201] 30 Sep 2015 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] Linux (x86-64), Windows (x86) \n * \n * Review lifecycle dates for all IBM MQ and WebSphere MQ products [http://www.ibm.com/software/support/lifecycleapp/PLCSearch.wss?q=%28+%22IBM+MQ%22+OR+%22WebSphere+MQ%22+%29+AND+NOT+%28+Tivoli+OR+Adapter+OR+Broker+OR+Integrator+OR+Workflow+OR+%22Low+Latency+Messaging%22+%29]\n \n End of support information for WebSphere MQ V7.5 and WebSphere MQ Hypervisor Edition V7.5 [http://www.ibm.com/support/docview.wss?&uid=swg21996472]\n \n End of support information for WebSphere MQ V7.1, WebSphere MQ File Transfer Edition V7.0.4, V7.0.3 and V7.0.2, WebSphere MQ Advanced Message Security V7.0.1, and WebSphere MQ Hypervisor Edition V7.0.1 [http://www.ibm.com/support/docview.wss?&uid=swg21980668]\n \n \n * Back to top\n\n\n\n\nDO THESE ANNOUNCEMENTS AFFECT WEBSPHERE MQ FILE TRANSFER EDITION V7.0.4, V7.0.3 AND V7.0.2, WEBSPHERE MQ ADVANCED MESSAGE SECURITY V7.0.1, OR WEBSPHERE MQ HYPERVISOR EDITION V7.0.1?\n\n * IBM has subsequently announced the end of support for these products [http://www.ibm.com/support/docview.wss?uid=swg21980668] on all platforms including z/OS:\n * \n * Lifecycle dates for WebSphere MQ V7.0 products [http://www.ibm.com/software/support/lifecycleapp/PLCSearch.wss?q=%28%22WebSphere+MQ+%22+AND+%227.0%22%29+OR+%28%22WebSphere+MQ+File+Transfer+Edition+%22+AND+%28%227.0.4%22+OR+%227.0.3%22+OR+%227.0.2%22%29%29+OR+%28%22WebSphere+MQ+Advanced+Message+Security+%22+AND+%227.0.1%22%29] \n * \n * Back to top\n\n\n\n\nWHAT REPLACEMENT PRODUCTS ARE AVAILABLE?\n\n * Replacements for WebSphere MQ V7.0.1 and V7.0.0 include IBM MQ or IBM MQ Advanced V9.0 and V8.0. WebSphere MQ or WebSphere MQ Advanced V7.5 are also available (except on IBM i), but their end of support date is 30 Apri 2018 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117].\n * Replacements for WebSphere MQ for z/OS V7.0.1 and V7.0.0 include IBM MQ, IBM MQ Advanced, or IBM MQ Value Unit Edition for z/OS V9.0 and V8.0.0.\n * Replacements for WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 include IBM MQ Advanced V9.0 and V8.0. WebSphere MQ Advanced V7.5 is also available (except on IBM i), but its end of support date is 30 April 2018 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117]. The Advanced license allows use of the Managed File Transfer and Advanced Message Security components which are now built into MQ and replace the former File Transfer Edition and Advanced Message Security products.\n * Replacements for WebSphere MQ File Transfer Edition for z/OS V7.0.1 and V7.0.0 include IBM MQ Advanced for z/OS V9.0 and V8.0.0. The Advanced license allows use of the Managed File Transfer and Advanced Message Security components which are now built into MQ for z/OS and replace the former File Transfer Edition for z/OS and Advanced Message Security for z/OS products.\n * The replacement for WebSphere MQ Telemetry V7.0.1 is IBM MQ or IBM MQ Advanced V9.0 or V8.0, all of which include Telemetry as a component of the MQ product. WebSphere MQ or WebSphere MQ Advanced V7.5 are also available (except on IBM i), but their end of support date is 30 April 2018 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117].\n * \n * \n * Back to top\n\n\n\n\nHOW DO I CHECK WHICH VERSION I AM CURRENTLY RUNNING?\n\n * Follow these general instructions [http://www.ibm.com/support/docview.wss?uid=swg21621707] or the IBM MQ Knowledge Center instructions [http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.ref.adm.doc/q083280_.htm] to display your IBM MQ or WebSphere MQ version on all platforms except for z/OS with the command: dspmqver\n * On z/OS, look for message CSQY000I [http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.ref.doc/csq_y.htm] in the MSTR joblog to determine your version.\n * Follow the IBM MQ Knowledge Center instructions [http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.wmqfte.doc/display_ver_cmd.htm] to display your Managed File Transfer or WebSphere MQ File Transfer Edition version with the command: fteDisplayVersion\n * WebSphere MQ Telemetry V7.0.1 only runs on WebSphere MQ V7.0.1 (fix pack 7.0.1.3 and later) on Linux (x86-64) and Windows (x86). Although there is no command to display the WebSphere MQ Telemetry version, if your WebSphere MQ version is V7.0.1 and you have a WebSphere MQ Telemetry service and channels [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.tt.doc/tt_intro.htm] configured, then you are running WebSphere MQ Telemetry V7.0.1.\n * \n * Back to top\n\n\n \n[/support/docview.wss?uid=swg21674407&aid=2]\n\n \n\n\n\n\nIS ANY INFORMATION AVAILABLE TO HELP ME UPGRADE TO A LATER VERSION?\n\n * The IBM MQ and WebSphere MQ Migration Guide [https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/websphere_mq_ibm_mq_migration_guide] is available to view online or download:\n * IBM MQ and WebSphere MQ Migration Guide [https://www.ibm.com/developerworks/community/blogs/aimsupport/resource/MQ_migration/WMQ_Migration.pdf] \n * \n * The IBM Knowledge Center also includes information to assist you in migrating to a supported version of IBM MQ or WebSphere MQ:\n * Migrating and upgrading to IBM MQ V9.0 [http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.mig.doc/q006180_.htm] Migrating and upgrading to IBM MQ V8.0 [http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.mig.doc/q006180_.htm] Migrating and upgrading to WebSphere MQ V7.5 [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.mig.doc/q006180_.htm] \n * \n * The following WebSphere Support Technical Exchange presentations may be helpful if you are considering running multiple MQ installations on your system:\n * Webcast replay: WebSphere MQ Multi-Version - First Steps [http://www.ibm.com/support/docview.wss?uid=swg27024276] Webcast replay: WebSphere MQ Multi-Version - Environment Considerations and Management [http://www.ibm.com/support/docview.wss?uid=swg27024340] \n * \n * Back to top\n\n\n\n\nHOW DO I PURCHASE A SUPPORT EXTENSION FOR MY CURRENT VERSION?\n\n * Support extensions are available for an additional fee. To purchase extended support for WebSphere MQ or any of the other products, please contact your local IBM sales representative.\n * US Customers should contact Customer Support Operations at 1-877-426-6006, option #2. If you provide your IBM customer number, they can quickly find your sales representative.\n * Customers in other geographies should refer to the IBM directory of worldwide support contacts to find sales contact numbers in your region:\n * \n * IBM Directory of Worldwide Contacts [http://www.ibm.com/planetwide/] \n * \n * Back to top\n\n\n\n\nWHEN AN WEBSPHERE MQ SERVER PRODUCT GOES OUT OF SUPPORT, DOES THE CLIENT AND FILE TRANSFER AGENT ALSO GO OUT OF SUPPORT?\n\n * Yes. WebSphere MQ V7.0 clients and WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 agents go out of support at the same time as the server.\n * \n * Back to top\n\n\n [/support/docview.wss?uid=swg21674407&aid=3] \n\n\n\n\nARE THESE PRODUCTS STILL SUPPORTED WHEN THEY ARE BUNDLED WITH ANOTHER IBM PRODUCT?\n\n * Yes, support is available for all bundled components until the IBM product that includes them is withdrawn from support. However, they are only supported when used by the bundling IBM product. Unrelated usage is not supported.\n * \n * Find the end of support date for your IBM software product [http://www.ibm.com/software/support/lifecycle/index_a_z.html] \n * \n * Back to top\n\n\n\n\nIS THE WEBSPHERE MQ V7.0 RESOURCE ADAPTER SUPPORTED IN WEBSPHERE APPLICATION SERVER?\n\n * Yes, the WebSphere MQ V7.0 Resource Adapter [http://www.ibm.com/support/docview.wss?uid=swg21248089#7dotx_0] shipped with WebSphere Application Server V8.0 and V7.0 is supported through 30 April 2018 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-143], when both of those versions of WebSphere Application Server end support, or longer if you purchase a WebSphere Application Server support extension.\n \n * Similarly, the WebSphere MQ V7.1 Resource Adapter [http://www.ibm.com/support/docview.wss?uid=swg21248089#7dotx_0_0] shipped with WebSphere Application Server V8.5.x is supported as long as that version of WebSphere Application Server remains in support, or longer if you purchase a WebSphere Application Server support extension.\n \n * However, if you manually install your own copy of the WebSphere MQ V7.x Resource Adapter in WebSphere Application Server or any third-party Java EE server, it will go out of support with the corresponding WebSphere MQ server version.\n \n * The IBM MQ V8.0 and V9.0 Resource Adapters cannot be installed in WebSphere Application Server V8.5.x, V8.0 and V7.0 because those versions support JMS 1.1 while the IBM MQ Resource Adapters implement JMS 2.0. WebSphere Application Server V9.0 ships with the IBM MQ V9.0 Resource Adapter [http://www.ibm.com/support/docview.wss?uid=swg21248089#7dotx_0_0_0] and includes full support for JMS 2.0. The version of MQ Resource Adapter you use must be supported by your Java EE server but does not need to match the version of the queue managers to which you wish to connect.\n \n * Back to top\n\n \n\n\n\n\nIS DOCUMENTATION STILL AVAILABLE FOR THESE PRODUCTS?\n\n * Yes. Online documentation is available in the IBM Knowledge Center, while downloadable Information Center installations and PDF versions of the manuals are available from the MQ Library page.\n * \n * WebSphere MQ V7.0.1 Knowledge Center [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.helphome.v70.doc/WelcomePagev7r0.htm] WebSphere MQ V7.0.1 library of downloadable documentation [http://www.ibm.com/software/integration/wmq/library/library701.html] WebSphere MQ V7.0.0 library of downloadable documentation [http://www.ibm.com/software/integration/wmq/library/library700.html] WebSphere MQ File Transfer Edition V7.0.4 Knowledge Center [http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/welcome/WelcomePagev7r0.html] WebSphere MQ Telemetry V7.0.1 [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.tt.doc/tt_intro.htm] \n * \n * Back to top\n\n\n\n\nHOW DO I OBTAIN INSTALLATION IMAGES FOR THESE PRODUCTS IF I STILL NEED THEM?\n\n * Installation images for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1 are no longer available from Passport Advantage [https://www.ibm.com/software/passportadvantage/pao_customer.html]. Contact IBM if you have an urgent business need for these installation images.\n * \n * Back to top\n\n\n \n[/support/docview.wss?uid=swg21674407&aid=4]\n\n \n\n\n\n\nIS THERE AN IBM MQ V9.0 OR MQ V8.0 TRIAL VERSION AVAILABLE FOR DOWNLOAD?\n\n * You can obtain a full-featured trial version of IBM MQ to evaluate for 90 days:\n * \n * Try IBM MQ now [https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?pkgid=&S_SRCID=ESD-WSMQ-EVAL&source=ESD-WSMQ-EVAL&S_TACT=109J84RW&S_CMP=web_ibm_ws_appint_ct_wmq-ov&S_PKG=CR9H9ML&s=&id=2009-08-28+03%3A34%3A46.648052R&fam=&cat=&l=English+International&m=download&ibm-continue=Continue] \n * \n * Back to top\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere MQ File Transfer Edition Not Applicable AIX, HP-UX, Linux, Solaris, Windows, z/OS 7.0.1, 7.0 All Editions Business Integration WebSphere MQ Telemetry Not Applicable Linux, Windows Business Integration IBM MQ \nPRODUCT ALIAS/SYNONYM\n WebSphere MQ WMQ"
}
] |
TRAIN_Q415 | Unable to login to FileNet Workplace XT 1.1.5.x. Getting error, Problem initializing encryption/decryption with keyID.
We are having issue while trying to login Workplace XT. Getting the error message below as soon as I hit after giving credentials.
Error Message: com.filenet.wcm.api.EncryptionException: Problem initializing encryption/decryption with keyId 7d3f93e3, size 256 bits. java.home=/opt/IBM/WebSphere/AppServer/java/jre. Cause: java.security. InvalidKeyException: Illegal key size or default parameters
IBM WAS 8.5.5.9 Workplace XT 1.1.5 | This behavior occurs if Workplace XT is configured to use Maximum strength keys (>128bit) during installation. | false | [
{
"filename": "swg21501900.txt",
"text": "Title: IBM Unable to log on to FileNet WorkplaceXT receive an AE SecurityCheckFilter error - United States\n\nText:\nAE SecurityCheckFilter; JSSE; unlimited strength TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Unable to log on to FileNet WorkplaceXT - AE SecurityCheckFilter error \n\nSYMPTOM\nWhen attempting to log on to FileNet WorkplaceXT deployed on an IBM WebSphere Application Server, the following error is displayed : \n\nException Message: [Filter AE SecurityCheckFilter]: filter is unavailable. \nFilter AE SecurityCheckFilter: filter is unavailable. \n\n\nDIAGNOSING THE PROBLEM\nSystemOut.log may contain the following exception : \n\n\nProblem initializing encryption/decryption with keyId abcd1234, size 256 bits. java.home=<<WAS_home>>\\AppServer\\java\\jre. Cause: java.security.InvalidKeyException: Illegal key size or default parameters\ncom.filenet.wcm.api.EncryptionException: Problem initializing encryption/decryption with keyId abcd1234, size 256 bits. java.home=<<WAS_home>>\\AppServer\\java\\jre. Cause: java.security.InvalidKeyException: Illegal key size or default parameters\nat com.filenet.wcm.api.impl.CryptoHelper.getCipher(CryptoHelper.java:93)\nat com.filenet.wcm.api.impl.CryptoHelper.doEncryptOrDecrypt(CryptoHelper.java:104)\nat com.filenet.wcm.api.impl.SessionImpl.getTokenSymmetric(SessionImpl.java:771)\nat com.filenet.wcm.api.impl.SessionImpl.getToken(SessionImpl.java:741)\nat com.filenet.ae.toolkit.server.util.credentials.UserTokenUtil.getUserToken(UserTokenUtil.java:131)\nat com.filenet.ae.toolkit.server.servlet.filter.SecurityCheckFilter.doFilter(SecurityCheckFilter.java:51)\n....\n\n\n\nRESOLVING THE PROBLEM\nThis behavior occurs if Workplace XT is configured to use Maximum strength keys (>128bit) during installation. In this case, the JRE used by the J2EE Application server, for example <<WAS_home>>\\AppServer\\java\\jre should contain unlimited strength policy files, otherwise it will be unable to encrypt / decrypt user tokens. \n\n \n\n * One option is to install the JSSE unlimited strength jar files for the JRE used by the J2EE Application Server. For IBM JREs, more info can be found at \n \n https://www.ibm.com/developerworks/java/jdk/security/ [https://www.ibm.com/developerworks/java/jdk/security/] \n \n \n * Another option is to regenerate the encryption keys using 128bit encryption which doesn't require the unlimited strength policy .jar files. Please refer to the P8 Infocenter for usage information on the com.filenet.wcm.api.util.MakeCryptoKeys utility."
}
] |
TRAIN_Q416 | Why are the component parameters missing for the Enable Hold and Virtual Interview Multiple Response functionality?
Why are the component parameters missing for the Enable Hold and Virtual Interview Multiple Response functionality? | The documentation references a MULTIPLE_RESPONSES_FOR_HOLD_VI_ALLOWED and a MULTIPLE_RESPONSES_INTERVIEW_AUTO_COMPLETE parameter that is supposed to be under the VIRTUAL_INTERVIEW_CONFIGURATION component.These component parameters are not automatically added as part of the database upgrade scripts. | false | [
{
"filename": "swg21984301.txt",
"text": "Title: IBM Component parameters missing for Enable Hold and Virtual Interview Multiple Response functionality - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why are the component parameters missing for the Enable Hold and Virtual Interview Multiple Response functionality? \n\nCAUSE\n \n\nThe documentation references a MULTIPLE_RESPONSES_FOR_HOLD_VI_ALLOWED and a MULTIPLE_RESPONSES_INTERVIEW_AUTO_COMPLETE parameter that is supposed to be under the VIRTUAL_INTERVIEW_CONFIGURATION component.These component parameters are not automatically added as part of the database upgrade scripts.\n\n\nANSWER\nTo enable the Enable Hold and Virtual Interview Multiple Response functionality you can manually create the component parameters. To do this go to the Admin > Components screen. \n\n 1. Search for the VIRTUAL_INTERVIEW_CONFIGURATION component. \n 2. Click on \"Edit\". \n 3. Click on \"Add Parameter\". \n 4. Set the new parameter with the name \"MULTIPLE_RESPONSES_FOR_HOLD_VI_ALLOWED\" and a value of \"True\" or \"False\" depending on your use of the functionality. \n 5. Click on \"Add Parameter\" again. \n 6. Set the new parameter with the name \"MULTIPLE_RESPONSES_INTERVIEW_AUTO_COMPLETE\" and a value of \"True\" or \"False\" depending on your use of the functionality. \n 7. Click on \"Save and Close\"."
}
] |
TRAIN_Q417 | What happens if I run arssyscr -I instance_name -r without having Report Distribution enabled or installed?
What will I see if I run arssyscr -I instance_name -r without having Report Distribution enabled or installed in CMOD v9.0? | You will see the "table or view does not exist" errors in your Systemlog | false | [
{
"filename": "swg21672402.txt",
"text": "Title: IBM What happens if I run arssyscr -I instance_name -r without having Report Distribution enabled or installed? - United States\n\nText:\narssyscr; Report Distribution TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Running arssyscr -I instance_name -r during upgrade without RDF installed or enabled can lead to errors during load. \n\nSYMPTOM\nYou will see errors similar to (depending on database brand) \nDB Error: ORA-00942: table or view does not exist -- SQLSTATE=, SQLCODE=942, File=arsrddb.c, \nLine=951 in your systemlog\n\n\nCAUSE\nIssuing the arssyscr -I (instance name) -r command will trigger arssockd to check for the ARSDBBUNDT (RDF tables), which do not exist. \n\nDIAGNOSING THE PROBLEM\nYou will see the \"table or view does not exist\" errors in your Systemlog\n\nRESOLVING THE PROBLEM\nYou will need to rename the Report Distribution tables and delete the Application, Application Group and Folders by performing the steps below:\n\nYou are going to want to change the Report Distribution table name: \n\nThis test is done on DB2, but It should be the same for (Oracle or SQL \nServer). \nThat is [2] and [3], to rename to object name, you need to log on your \ndatabase command session: \n\n\n[1] Shutdown arssockd \n\n[2] Rename the Application Group name \n\nc:\\>db2 \"select agid, name, agid_name from arsag where name = 'System \nReport Distribution'\" \nAGID NAME \nAGID_NAME \n----------- ------------------------------------------------------------ \n--------- \n5007 System Report Distribution \nSR \n1 record(s) selected. \n\n\nc:\\>db2 \"update arsag set name = 'System Report Distribution DELETE' \nWHERE name = 'System Report Distribution'\" \nDB20000I The SQL command completed successfully. \n\n\n[3] Rename the Folder name \n\nc:\\>db2 \"select name from arsfol where name like 'System Report \nDistribution%'\" \nNAME \n------------------------------------------------------------ \nSystem Report Distribution - Bundles \nSystem Report Distribution - Deliveries \nSystem Report Distribution - Reports \n3 record(s) selected. \n\nc:\\>db2 \"update arsfol set name = 'System Report Distribution - Bundles \nDELETE' where name = 'System Report Distribution - Bundles'\" \nDB20000I The SQL command completed successfully. \n\nc:\\>db2 \"update arsfol set name = 'System Report Distribution - \nDeliveries DELETE' where name = 'System Report Distribution - \nDeliveries'\" \nDB20000I The SQL command completed successfully. \n\nc:\\>db2 \"update arsfol set name = 'System Report Distribution - Reports \nDELETE' where name = 'System Report Distribution - Reports'\" \nDB20000I The SQL command completed successfully. \n\n[3] Start up arssockd \n\n[4] Use the Admin GUI to delete the RD Application group, Applications, \nand Folders"
}
] |
TRAIN_Q418 | Request for Sample working RUN() Function for ITX
Hi Guys,
Anyone can share your simple RUN() function to trigger another map for ITX?
Appreciate if some example can be shared!
Thanks in advance!!
Cheers! | - | true | [] |
TRAIN_Q419 | Does double the number of instances equal double through put in IIB / WMB?
If I double the number of instances of an IBM Integration Bus (IIB) or WebSphere Message Broker (WMB) flow should I get double the through put? | - | true | [] |
TRAIN_Q420 | How can I investigate hangs in MQ or in applications?
Are there any tools to help get to the bottom of hangs? | - | true | [] |
TRAIN_Q421 | Authorization code issue
like many of the other questions posted on here ... I'm having trouble authenticating my SPSS authorization code. Then there is an issue getting a license code back from the IBM proxy server to complete my download. Please help. | For installation & licensing issues on Student version and Graduate pack, contact your vendor. | false | [
{
"filename": "swg21592093.txt",
"text": "Title: IBM SPSS Student Version and Graduate Pack Resources - United States\n\nText:\nSPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http://www.hearne.software/Software/SPSS-Grad-Packs-for-Students-by-IBM/FAQ] \n * On the Hub [http://onthehub.com/] \n * StudentDiscounts.com [http://studentdiscounts.com/contact-us.aspx] \n * JourneyEd [https://www.journeyed.com/contact] \n * thinkEDU [https://thinkedu.desk.com/] \n * Studica [http://www.studica.com/technical-support]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version"
}
] |
TRAIN_Q422 | Help with Security Bulletin: Vulnerability in SSLv3 affects IID and WID (CVE-2014-3566)
I need to understand details regarding Security Bulletin: Vulnerability in SSLv3 affects IBM Integration Designer and WebSphere Integration Developer (CVE-2014-3566). Where can I find this information? | CVE-ID: CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566]
DESCRIPTION: IBM Integration Designer and WebSphere Integration Developer could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plaintext of encrypted connections.
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/97013 [https://exchange.xforce.ibmcloud.com/vulnerabilities/97013] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N) | false | [
{
"filename": "swg21689914.txt",
"text": "Title: IBM Security Bulletin: Vulnerability in SSLv3 affects IBM Integration Designer and WebSphere Integration Developer (CVE-2014-3566) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n SSLv3 contains a vulnerability that has been referred to as the Padding Oracle On Downgraded Legacy Encryption (POODLE) attack. SSLv3 is enabled in IBM Integration Designer and WebSphere Integration Developer. \n\nVULNERABILITY DETAILS\nCVE-ID: CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566]\n\nDESCRIPTION: IBM Integration Designer and WebSphere Integration Developer could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plaintext of encrypted connections.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/97013 [https://exchange.xforce.ibmcloud.com/vulnerabilities/97013] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nThis vulnerability affects some versions and releases of IBM Integration Designer and WebSphere Integration Developer.\n\nREMEDIATION/FIXES\nIBM recommends that you review your entire environment to identify areas that enable the SSLv3 protocol and take appropriate mitigation and remediation actions. The most immediate mitigation action that can be taken is disabling SSLv3. You should verify disabling SSLv3 does not cause any compatibility issues.\n\nNote that other related products are also affected by this vulnerability. In the context of applying fixes, you will also want to update Installation Manager to version 1.8 or later.\n\nTo fully mitigate the POODLE vulnerability for server side components, an additional fix for IBM Integration Designer and WebSphere Integration Developer is required (JR51720): \n\n * WebSphere Integration Developer V7.5.1.2 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Integration+Designer&release=7.5.1.2&platform=All&function=aparId&apars=JR51720] \n * IBM Integration Designer V8.0.1.3 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Integration+Designer&release=8.0.1.3&platform=All&function=aparId&apars=JR51720] \n * IBM Integration Designer V8.5.5.0 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Integration+Designer&release=8.5.5&platform=All&function=aparId&apars=JR51720]\n\nWORKAROUNDS AND MITIGATIONS\nCustomers who cannot or do not want to install the fix recommended in the \"Remediation/Fixes\" section of this security bulletin can disable the use of SSLv3 using manual configuration as described in \"Workarounds and Mitigations\" under the \"Client configuration files\" section in the following bulletin: Security Bulletin: Vulnerability in SSLv3 affects IBM WebSphere Application Server (CVE-2014-3566) [http://www.ibm.com/support/docview.wss?uid=swg21687173]\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \nSecurity Bulletin: Vulnerability in SSLv3 affects IBM WebSphere Application Server (CVE-2014-3566) [http://www.ibm.com/support/docview.wss?uid=swg21687173] \nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 2014-11-14- Original Version Published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. \n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Integration Developer Security Linux, Windows 7.0.0.5, 7.0.0.4, 7.0.0.3, 7.0.0.2, 7.0.0.1, 7.0, 6.2.0.3, 6.2.0.2, 6.2.0.1, 6.2, 6.1.2"
}
] |
TRAIN_Q423 | Report stuck in current queue
We have one report that has been showing in the admin current
activities status tab for 20+ days and we have had 2 full re-starts
since then. Also it appears we have interactive jobs staying around as well for past days and days.
How can we clean this up ? | Dropping the NC* tables that use this script:
Steps:
1. Stop the Cognos Service
2. Take a physical backup of the Content Store or Notification database
3. Select the appropriate folder for your content store or notification database type under <install>/configuration/schemas/delivery/<dbtype>/
4. Run NC_DROP_<dbtype>.sql against the content store or notification database
4. Restart Cognos Services.
Should dropping the NC* tables not resolve the issue, then restore the content or notification store from the last backup version. | false | [
{
"filename": "swg21371279.txt",
"text": "Title: IBM Scheduled Cognos BI reports are stuck in Pending state - United States\n\nText:\ndeployment TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Schedules Cognos Business Intelligience reports are not running. Scheduled reports are stuck in \"Pending\" state forever. \n\n- Renewing credentials does not resolve the issue. After credentials are renewed, user still receives the same error indicating that the credentials are invalid.\n\n- Enabling the \"Run as the Owner\" option does not resolve the issue \n\nSYMPTOM\nThe provided credentials are invalid.\nCNC-SEC-3403 The user account information is invalid, or it is missing in Content Manager. \nCAM-AAA-0102 Unable to authenticate. The user must select a namespace.\n...\nYour session has expired.\nSelect a namespace for authentication\n\n\nCAUSE\nContent Store corrupted.\n\nRESOLVING THE PROBLEM\nDropping the NC* tables that use this script: \n\nSteps:\n1. Stop the Cognos Service\n2. Take a physical backup of the Content Store or Notification database\n3. Select the appropriate folder for your content store or notification database type under <install>/configuration/schemas/delivery/<dbtype>/ \n4. Run NC_DROP_<dbtype>.sql against the content store or notification database \n4. Restart Cognos Services. \n\nShould dropping the NC* tables not resolve the issue, then restore the content or notification store from the last backup version.\n\nRELATED INFORMATION\n Cognos Analytics Equivalent [http://www.ibm.com/support/docview.wss?uid=swg22001203]"
}
] |
TRAIN_Q424 | Unable to unistall Data Studio 3.1.1 on Windows
We use Data Studio 3.1.1.0 with DB2 WSE V9.7 FP11 on Windows 2008. While trying to new version of Data Studio 4.1.2, we are able to install it successfully. But unable to uninstall the existing 3.1.1.0, getting the jvm error "Could not find the main class". How we can delete it?
| Please try to uninstall all products including Install Manager
(IM) then reinstall IM and Data Studio 4.1.2. | false | [
{
"filename": "swg21991414.txt",
"text": "Title: IBM How can uninstall Data Studio 3.1.1 where Control Panel uninstall process gets an error? - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n We are able to install Data Studio (DS) 4.1.2 successfully but unable to uninstall the \nexisting Data Studio 3.1.1. When uninstall Data Studio 3.1.1 from Control Panel, it \nraises an error message pop-up window and can not uninstall it. Here is the message:\n\n+-------------------------------------------------------------------------\n| Java Virtual Machine Launcher\n+-------------------------------------------------------------------------\n| X Could not find the main class: com.zerog.lax.LAX. Program will exit.\n+-------------------------------------------------------------------------\n\nHow can uninstall Data Studio 3.1.1 where Control Panel uninstall process gets an error?\n\n\nCAUSE\nIt is an known behavior/limitation. \n\nANSWER\nIt may be happened where two versions Data Studio 3.1.1 and 4.1.2 installed machine. \n\nHere is an workaround. Please try to uninstall all products including Install Manager \n(IM) then reinstall IM and Data Studio 4.1.2. Below are detailed steps:\n\n1. Use IM to uninstall as many packages as possible.\n\n2. Identify the packages that are still installed, and manually clean \nthem up.\n\nExample on Windows:\n- C:\\Program Files\\IBM\\{IBMIMShared | SDPShared}\n\n3. Delete IBM Installation Manager.\n\nExample on Windows:\n- Delete the IM install directory:\nC:\\Program Files\\IBM\\Installation Manager\\\n- Delete the AppData directory (IM Agent Data):\nWindows 7: C:\\ProgramData\\IBM\\Installation Manager\n- Delete the Windows registry (regedit) entry : \nHKEY_LOCAL_MACHINE\\SOFTWARE\\IBM\\Installation Manager\n- re-install IM\n\n4. Reinstall DS 4.1.2 and other products.\n\nNote:\nThis behavior might be changed without notice in the future. We can confirm whether this technote\nis valid or not by following above.\nPlease contact your Sales Rep to submit a potential design change towards a future release.\nOr please open a ticket, Request For Enhancement at https://www.ibm.com/developerworks/rfe/ [https://www.ibm.com/developerworks/rfe/]"
}
] |
TRAIN_Q425 | Upgrading the feature level to 8 for a VOB and ACLs
We have upgraded to Clearcase version 8.0.1.3 ( on Windows 2008 Server)
How to upgrade the feature level of a single VOB from 5 to 8 ? | Execute the following two commands:
1. cleartool chflevel -replica <new feature level> replica:<replica name>@\<vob tag>
2. cleartool chflevel -family <new feature level> vob:\<vob tag> | false | [
{
"filename": "swg21150579.txt",
"text": "Title: IBM Raise the feature level of a single VOB without increasing the feature level for other VOBs on the server - United States\n\nText:\nfeature level; chflevel; unreplicated; non-replicated; base; clearcase; 1150579; feature levels; replicated VOB TECHNOTE (FAQ)\n\nQUESTION\n How can you increase the feature level of a single non-replicated IBM Rational ClearCase VOB without increasing the feature level for the other VOBs on the server? \n\nANSWER\n \n\nExecute the following two commands: \n\n 1. cleartool chflevel -replica <new feature level> replica:<replica name>@\\<vob tag>\n \n \n 2. cleartool chflevel -family <new feature level> vob:\\<vob tag>\n\n\n\nNotes: * These commands are used for replicated VOB as well; however, there are special considerations that need to be taken when changing the feature level of a VOB that is replicated. Review the MultiSite Administrator's Guide under the topic of Feature levels [http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m1/index.jsp?topic=/com.ibm.rational.clearcase.cc_ms_admin.doc/c_feature_levels.htm]for more details.\n \n * If a VOB is used in a UCM environment, the PVOB and all Component VOBs must be at the same feature level in order to utilize the features of that level.\n\n\nExample: \n\n 1. Open a command prompt and set into a view\n \n \n 2. Mount and change directory into the VOB tag\n \n \n 3. Describe the VOB to show current feature level\n \n > cleartool describe -long vob:.\n versioned object base \"/vobstore/test_vob\"\n created 23-Mar-01.09:36:29 by John Doe (jdoe.group1@host1)\n VOB family feature level: 2\n VOB storage host:pathname \"host1:/vobstore/test_vob.vbs\"\n VOB storage global pathname \"/net/host1/vobstore/test_vob.vbs\"\n database schema version: 53\n VOB ownership:\n owner ibm.com/jdoe\n group ibm.com/group1\n Additional groups:\n group ibm.com/other\n VOB holds objects from the following views:\n Attributes:\n FeatureLevel = 2 \n \n \n 4. Determine the replica name (by default is original)\n \n > cleartool lsreplica\n For VOB replica \"/vobstore/test_vob\":\n 23-Mar.09:36 jdoe replica \"original\"\n \n \n 5. Change the feature level. * Step 1:\n > cleartool chflevel -replica 3 replica:original@/vobstore/test_vob\n Replica feature level raised to 3.\n \n \n * Step 2:\n > cleartool chflevel -family 3 vob:/vobstore/test_vob\n cleartool: Warning: Raising the VOB family feature level may make it impossible to move this VOB to servers running an earlier revision of ClearCase and to create MultiSite replicas of this VOB on such servers.\n Raise VOB family feature level? [no] y\n VOB family feature level raised to 3.\n \n \n \n \n 6. Describe the VOB to show new feature level:\n \n > cleartool describe -long vob:.\n versioned object base \"/vobstore/test_vob\"\n created 23-Mar-01.09:36:29 by John Doe (jdoe.group1@host1)\n VOB family feature level: 3\n VOB storage host:pathname \"host1:/vobstore/test_vob.vbs\"\n VOB storage global pathname \"/net/host1/vobstore/test_vob.vbs\"\n database schema version: 53\n VOB ownership:\n owner ibm.com/jdoe\n group ibm.com/user\n Additional groups:\n group ibm.com/other\n VOB holds object from the following views:\n Attributes:\n FeatureLevel = 3 \n\n\nReview the ClearCase Command Reference Guide on the topic of chflevel (cleartool man chflevel) for more information. \n\n \n\n\n\n\n\nRELATED INFORMATION\n#About Feature Levels and ClearCase [http://www.ibm.com/support/docview.wss?uid=swg21119269]"
}
] |
TRAIN_Q426 | Help with Security Bulletin: IBM MQ Clients can send a specially crafted message that could cause a channel to SIGSEGV. (CVE-2017-1747)
I need to understand details regarding Security Bulletin: IBM MQ Clients can send a specially crafted message that could cause a channel to SIGSEGV. (CVE-2017-1747). Where can I find this information? | CVEID: CVE-2017-1747 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1747]
DESCRIPTION: A specially crafted message could cause a denial of service in an IBM MQ application consuming messages that the application needs to perform data conversion on.
CVSS Base Score: 5.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/135520 [https://exchange.xforce.ibmcloud.com/vulnerabilities/135520] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H) | false | [
{
"filename": "swg22012992.txt",
"text": "Title: IBM Security Bulletin: IBM MQ Clients can send a specially crafted message that could cause a channel to SIGSEGV. (CVE-2017-1747) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n A specially crafted message could cause a denial of service in an IBM MQ application consuming messages that the application needs to perform data conversion on. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-1747 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1747]\nDESCRIPTION: A specially crafted message could cause a denial of service in an IBM MQ application consuming messages that the application needs to perform data conversion on.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/135520 [https://exchange.xforce.ibmcloud.com/vulnerabilities/135520] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ V9 LTS\nMaintenance levels 9.0.0.0 - 9.0.0.2 \n\nIBM MQ V9 CD\nMaintenance levels 9.0.0 - 9.0.4\n\nREMEDIATION/FIXES\nIBM MQ V9 LTS\nApply FixPack 9.0.0.3 [http://www-01.ibm.com/support/docview.wss?uid=swg24044508] \n\nIBM MQ V9 CD\nUpgrade to IBM MQ version 9.0.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24043463]\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 28 March 2018: Original Version published\n29 March 2018: Correction to bulletin to remove HPE Nonstop as affected platform. \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. \n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM MQ Business Integration IBM MQ Advanced Business Integration IBM MQ Advanced for Developers"
}
] |
TRAIN_Q427 | Setting session timeouts and precedence
What are the different ways to set the session timeout values. What takes more precedence? | The HTTP Session time-out can be set in the following places:
* From the Administrative Console at the server, Enterprise application, and Web application levels
* At the time when the application is packaged
* In the application code | false | [
{
"filename": "swg21163875.txt",
"text": "Title: IBM HTTP Session time-out settings and overwrite precedence rules - United States\n\nText:\nWebSphere http session management time-out wasrun precedence overwrite TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n It is possible to set the HTTP Session time-out in various places on the IBM® WebSphere® Application Server Administrative Console. It is also possible to set HTTP Session time-out for the application packaging process. \n\nSince Session time-out can be set in multiple places, it is necessary to understand how the ultimate Session time-out for an application is determined. \n\nCAUSE\nApplication needs HTTP session time-out set.\n\nRESOLVING THE PROBLEM\nThe HTTP Session time-out can be set in the following places: \n\n * From the Administrative Console at the server, Enterprise application, and Web application levels \n * At the time when the application is packaged \n * In the application code\n\n\nSetting the HTTP Session time-out from the Administrative Console \n1. To set the HTTP Session time-out at the server level, navigate to Servers > Application Servers > Your Server > Web Container > Session Management. \n\nIn the Session time-out section of this window, you can select No time-out or Set time-out by clicking the appropriate radio button. If you choose to set the time-out, type the desired value in minutes in the box. \n\n\n2. To set the HTTP Session time-out at the Enterprise Application level, navigate to Applications > Enterprise Applications > Your Application > Session Management. \n\nCheck Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the application session to overwrite those values set at the parent, which in this case is the Server level. \n\n\n3. To set the HTTP Session time-out at the Web Application level, navigate to Applications > Enterprise Applications > Your Application > Web Module > Your Web App.war > Session Management. \n\nCheck Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the Application Session to overwrite those values set at the parent levels, which in this case is the Server or Enterprise Application level. \n\nAfter modifying these settings, save the master configuration. \n\nSetting HTTP Session time-out when application is packaged \n\nThe application developer can also select to set the HTTP Session time-out parameter when the application is packaged. This value is stored in the web.xml file for the Web application. \n\nThis setting overrides any session time-outs defined from the Administrative Console. Alter this setting by repackaging the application with a new value, or by modifying the web.xml file. The entry in the web.xml will be as follows: \n <session-config> \n * <session-timeout>60</session-timeout>\n * \n * </session-config>\n\n \n\nWhere the \"session-timeout\" is an integer value for the desired session time-out in minutes. \nSetting HTTP Session time-out from the application code \n\nFinally, the HTTP Session time-out can be set in the application code. The programmer can invoke the setMaxInactiveInterval() method on HttpSession object to set the time-out value as desired. This setting overrides any time-out defined in the application package or made from the Administrative Console. \n\nHTTP Session time-out Override Precedence Summary \n\nThe list below shows the precedence from which the final HTTP Session time-out is derived. \n\n1. Server Level [/support/docview.wss?uid=swg21163875&aid=1] Lowest level 2. Enterprise Application [/support/docview.wss?uid=swg21163875&aid=1] Overrides the Server Level if Override is selected 3. Web Application [/support/docview.wss?uid=swg21163875&aid=1] Overrides the Server and Enterprise Application settings if Override is selected 4. Application Level (web.xml) [/support/docview.wss?uid=swg21163875&aid=1] Overrides Server, Enterprise Application, and Web Application settings 5. Application Code [/support/docview.wss?uid=swg21163875&aid=1] Overrides all other settings RELATED INFORMATION\n A simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21659740]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK"
}
] |
TRAIN_Q428 | ITMv6 issue: Cognos reports run for an extended period, sometimes never finishes
ITMv6 issue: Cognos reports run for an extended period, sometimes never finishes
| TCR 2.1/2.1.1 server provides a default setting for heap size, a minimum size (xms) of 512MB and a maximum size (xmx) of 1024MB. | false | [
{
"filename": "swg21585678.txt",
"text": "Title: IBM Increasing Java Heap Memory in IBM Tivoli Common Reporting 2.1/2.1.1 - United States\n\nText:\nTCR - Tivoli Common Reporting TECHNOTE (FAQ)\n\nQUESTION\n How to increase Java heap memory size in IBM Tivoli Common Reporting (TCR) 2.1/2.1.1 versions? \n\nCAUSE\nRunning a large scale report with Default java heap settings might result in OutOfMemory error\n\nANSWER\nTCR 2.1/2.1.1 server provides a default setting for heap size, a minimum size (xms) of 512MB and a maximum size (xmx) of 1024MB. \n\nIn order to change the heap memory size, execute the following command:\n<INST>/tipv2/bin/wsadmin.sh[.bat] -user <USERNAME> -password <PASSWORD> -f <INST>/tipv2/profiles/TIPProfile/bin/changeMem.py --xms <MINVALUE> --xmx <MAXVALUE>\n\nwhere <INST> is the TCR Installation folder like /opt/IBM/tivoli\n<MINVALUE> can be 1024 and <MAXVALUE> can be 1843 (1GB and 1.8GB respectively)\n\nNOTE: In order to avoid OutOfMemory error, it is recommended to be within the 2GB limit (for 32 bit architectures - maximum memory can be 2^32)\nFor 64-bit JVM, the maximum heap value can be upto 50% of the available physical memory. Reason being maximum memory will be 2^64 which is 16 exabytes which is a very huge number! \n1 exabyte = 1024*1024*1024 Gigabyte!\nPlease refer to the links provided in the 'Related Infomation' section to learn more on the Java sizing and heap information.\n\nTo test the JVM's maximum heap memory support, please follow the below test:\na) Open command line / shell script and navigate to <INST>/tipv2/java/jre/bin folder\nb) Execute this command: java -Xmx1843m hello\n- if java accepts this 1.8GB setting, then it will throw the \"class not found\" error for hello\n- if java does not accept this value, then it gives the \"Initialization error\" and \"Failed to instantiate heap\" message!\n- You can try to increase the value of Xmx and see where it breaks\n- For 32-bit JVM, it is not advised to set this value beyond 1843m but for 64-bit JVM, value can be upto 50% of the available physical memory.\n\nAfter setting the new values, restart the TCR server for the changes to take effect.\n\nRELATED INFORMATION\n Sizing the Java Heap [http://publib.boulder.ibm.com/infocenter/javasdk/tools/index.jsp?topic=%2Fcom.ibm.java.doc.igaa%2F_1vg000139b8b453-11951f1e7ff-8000_1001.html]\nJava code to Java Heap [http://www.ibm.com/developerworks/java/library/j-codetoheap/index.html]"
}
] |
TRAIN_Q429 | Does Portal 7.0.0.2 CF20 support upgrading the DB2 JDBC Driver from 4.11.77 to 4.18.60?
Does Portal 7.0.0.2 CF20 support upgrading the DB2 JDBC Driver from 4.11.77 to 4.18.60? | IBM DB2 Universal JDBC Provider (XA) from DB2 z/OS (type 4) Version and future fix packs All Applicable AIX OS Requires APAR PK93123 for DB2 on z/OS V8.1 and V9.1. You can obtain the fix from DB2 on z/OS support or IBMLINK. | false | [
{
"filename": "swg27020885.txt",
"text": "Title: IBM WebSphere Portal V7.0.0.2 hardware and software requirements - United States\n\nText:\nDSRdoc; DSR; WPv7002eGA; hardware; software; requirements; portal 7.0.0.2; V7.0.0.2; 7002eGA PRODUCT DOCUMENTATION\n\nABSTRACT\n WebSphere Portal V7.0.0.2 hardware and software requirements for Server, Enable and Extend editions, as well as Lotus Web Content Management V7.0.0.2, on supported Linux platforms and distributions. \n\nCONTENT\n\n\nThis page describes the minimum product levels that need to be installed before opening a problem report with IBM WebSphere Portal Technical Support. The software versions and any maintenance levels listed on this page have been explicitly verified as working. \n\nEARLIER LEVEL OF A LISTED SOFTWARE: Software versions at a lower level than those noted on this page are unsupported. LDAP software at an earlier level is considered untested and best effort support only. For more details and exceptions, refer to the WebSphere Portal Support Statement [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc/overview/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 7.0.0.2 in WebSphere Portal Support Statement Addendum - Unsupported Products [http://www.ibm.com/support/docview.wss?uid=swg27019552] (#7019552 [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27019552]). \n\nLATER LEVEL OF A LISTED SOFTWARE: Because other products frequently ship fixes, updates, and new releases, testing every configuration is not possible. In general, you can install and run with updates to supported products if those updates are compatible with the tested versions. For more details and exceptions, refer to the WebSphere Portal Support Statement [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc/overview/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 7.0.0.2 in WebSphere Portal Support Statement Addendum - Unsupported Products [http://www.ibm.com/support/docview.wss?uid=swg27019552] (#7019552 [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27019552]). \n\nUNLISTED SOFTWARE: Software not listed on this page at any level is unsupported. LDAP software not listed is considered untested and best effort support only. For more details and exceptions, refer to the WebSphere Portal Support Statement [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc/overview/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 7.0.0.2 in WebSphere Portal Support Statement Addendum - Unsupported Products [http://www.ibm.com/support/docview.wss?uid=swg27019552] (#7019552 [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27019552]). \n\n\nWEBSPHERE PORTAL SERVER, ENABLE, EXTEND AND LOTUS WEB CONTENT MANAGEMENT 7.0.0.2\nTAB NAVIGATION\n * AIX - selected tab, \n * IBM i \n * Linux \n * Solaris \n * Windows \n\nTAB NAVIGATION\n * AIX \n\n\n\n\nOUTLINE\n * Hardware Requirements * Disk Space \n * Media Drive \n * Memory \n * Processor \n \n \n * Software Requirements * Operating System \n * Application Servers \n \n \n * Optional Supported Software * Application Servers \n * Collaboration \n * Databases \n * Identity Management \n * Java Technology \n * JDBC Drivers \n * Miscellaneous \n * Process Server \n * Security \n * Tools \n * Virtualization \n * Web Browsers \n * WebDAV Client \n * Web Servers \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Disk Space All Applicable AIX OS Minimum 2.5 GB free disk space for installation for WebSphere Portal\nMinimum 1.4 GB free disk space for installation for WebSphere Application Server\nMinimum 4 GB total disk space recommended for installation\n\nMedia Drive All Applicable AIX OS A CD/DVD drive is required.\n\nMemory All Applicable AIX OS Physical memory requirements and recommendations for WebSphere Portal:\n\n * Under minimal load, WebSphere Portal can function with 2GB of RAM and a remote database.\n * In a production environment, 4GB is an optimal starting point for RAM.\n\nProcessor All Applicable AIX OS IBM POWER family of processors\n\n Back to top \n\nOperating Systems Operating System Attributes Notes AIX Platform listing of supported OS AIX 5.3 POWER System and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: POWER System Technology and service release level requirements:\n * Technology level 12 or later\n * Service release 1 or later\n\nFor example: (5300-07-01)\n\nWebSphere Application Server requirements depending on operating system bit:\n * 32-bit JDK/WebSphere Application Server on 32-bit OS\n * 32-bit JDK/WebSphere Application Server on 64-bit OS\n * 64-bit JDK/WebSphere Application Server on 64-bit OS\n\nAIX 6.1 POWER System and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: POWER System Technology and service release level requirements: \n\n * Technology level 5 or later. \n * Service release 2 or later. \n\nFor example: 6100-04-02 \n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK/WebSphere Application Server on 64-bit OS \n * 64-bit JDK/WebSphere Application Server on 64-bit OS \n\nAIX 7.1 POWER System and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: POWER System WebSphere Application Server requirements depending on operating system bit: * 32-bit JDK/WebSphere Application Server on 64-bit OS \n * 64-bit JDK/WebSphere Application Server on 64-bit OS \n\n Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers WebSphere Application Server 7.0.0.19 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Application_Server] All Applicable AIX OS Download mandatory APAR PM52049 for WebSphere Application server 7.0.0.19 from this site -\n\n Fix Central Link for PM52049 [http://www-933.ibm.com/support/fixcentral/swg/selectFix?product=ibm/WebSphere/WebSphere+Application+Server&fixids=7.0.0.19-WS-WAS-IFPM52049&source=dbluesearch&function=fixId&parent=ibm/WebSphere]\n\n [http://www.ibm.com/support/docview.wss?uid=swg24029137]\n\n1. IBM Java SDK V5 reached end of service in 2015. If you continue to use WebSphere Application Server 7.0.x after that date with extended support, Java SDK V5 is no longer included. It is recommended that you upgrade to IBM Java SDK V6.\n\n2. IBM Java SDK V6 will reach end of service in Apr 2018. If you continue to use WebSphere Application Server 7.0.x after that date with extended support, Java SDK V6 is no longer included.\n\n Back to top \n\nOptional Supported Software Group Product Applicable OS Notes Application Servers WebSphere Application Server Feature Pack for XML 1.0.0.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/xml/index.html] All Applicable AIX OS WebSphere Application Server V7 Feature Pack for Communications Enabled Applications 1.0.0.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/cea/] All Applicable AIX OS WebSphere Application Server V7 Feature Pack for Service Component Architecture 1.0.1.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/sca/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Application_Server] All Applicable AIX OS WebSphere eXtreme Scale 7.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/extremescale/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_eXtreme_Scale] All Applicable AIX OS Requires version 7.1.0.0 WebSphere Virtual Enterprise 6.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/extend/virtualenterprise/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Virtual_Enterprise] All Applicable AIX OS Requires fix pack version 6.1.1.2 Collaboration IBM Connections 3.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/IBM_Connections] All Applicable AIX OS Lotus Connections 2.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Connections] All Applicable AIX OS Lotus Connections 3.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Connections] All Applicable AIX OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable AIX OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable AIX OS Lotus Quickr for Domino 8.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_Domino] All Applicable AIX OS Lotus Quickr for Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_Domino] All Applicable AIX OS Lotus Quickr for WebSphere Portal 8.1.1 Feature Packs and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_WebSphere_Portal] All Applicable AIX OS Lotus Quickr for WebSphere Portal 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_WebSphere_Portal] All Applicable AIX OS Lotus Sametime Entry 8.0 and future mod levels and fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/entry/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable AIX OS IBM Lotus Sametime Entry 8.0.2 requires hot fix BMUY-87SL83 \n\nLotus Sametime Entry 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/entry/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable AIX OS Requires hot fix BMUY-87SL83\n\nLotus Sametime Standard 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/standard/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable AIX OS Requires hot fix BMUY-87SL83\n\nDatabases Apache Derby 10.3 and future fix packs All Applicable AIX OS Not supported in a production environment.\n\nDB2 9 for Linux, UNIX and Windows 9.1.0.9 and future fix packs All Applicable AIX OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Enterprise Server Edition 9.7.0.1 and future fix packs (overview) [http://www.ibm.com/software/data/db2/linux-unix-windows/edition-enterprise.html] (support) [http://www.ibm.com/software/data/db2/support/db2_9/] All Applicable AIX OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\n Database parameter 'cur_commit' must be set to 'DISABLED' for database of WebSphere Portal 7\n\nDB2 for i5/OS 6.1 and future fix packs All Applicable AIX OS DB2 for i5/OS 7.1 and future fix packs All Applicable AIX OS DB2 for i5/OS V5R4 and future fix packs All Applicable AIX OS DB2 for z/OS 9.1 and future fix packs (overview) [http://www.ibm.com/software/data/db2/zos/] (support) [http://www.ibm.com/software/data/db2/support/db2zos/] All Applicable AIX OS High Availability Disaster Recovery (HADR) Feature is supported.\n\n WebSphere Portal 7.0 works with DB2 for z/OS V9.1 - PUT level 0912.\n\n The following are required:\n\n * APAR PK75093 or later\n * APAR PK92163:\n http://www-01.ibm.com/support/docview.wss?uid=swg1PK92163 [http://www-01.ibm.com/support/docview.wss?uid=swg1PK92163]\n * APAR PK68265\n\nDB2 for z/OS 10.1 and future fix packs (overview) [http://www.ibm.com/software/data/db2/zos/] (support) [http://www.ibm.com/software/data/db2/support/db2zos/] All Applicable AIX OS DB2 pureScale Feature for Enterprise Server Edition 9.8.0.3 and future fix packs All Applicable AIX OS Requires 7.0.0.1 CF007 or higher.\n\n Refer to the steps documented here: http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open]\n\nDB2 Universal Database for z/OS 8.1 and future fix packs All Applicable AIX OS WebSphere Portal 7.0 works with DB2 for z/OS V8.1 - PUT level 0912 or later service level.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Workgroup Server Edition 9.5.0.5 and future fix packs (overview) [http://www.ibm.com/software/data/db2/linux-unix-windows/edition-workgroup.html] (support) [http://www.ibm.com/software/data/db2/support/db2_9/] All Applicable AIX OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nMicrosoft SQL Server Enterprise Edition 2005 SP2 and future fix packs All Applicable AIX OS Microsoft SQL Server Enterprise Edition 2008 and future fix packs All Applicable AIX OS Microsoft SQL Server Enterprise Edition 2008 R2 All Applicable AIX OS Oracle Database 10g Enterprise Edition Release 1 10.1.0.5 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 10g Enterprise Edition Release 2 10.2.0.4 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 10g Standard Edition Release 1 10.1.0.5 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 10g Standard Edition Release 2 10.2.0.4 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.6 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.7 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 11g Enterprise Edition Release 2 11.2.0.2 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.6 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.7 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 11g Standard Edition Release 2 11.2.0.2 and future fix packs All Applicable AIX OS See Note #3 Identity Management IBM z/OS.e Security Server 1.6 and future fix packs All Applicable AIX OS IBM z/OS.e Security Server 1.7 and future fix packs All Applicable AIX OS IBM z/OS Security Server 1.6 and future fix packs All Applicable AIX OS IBM z/OS Security Server 1.7 and future fix packs All Applicable AIX OS Lotus Domino 8.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable AIX OS Lotus Domino 8.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable AIX OS Lotus Domino 8.0.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable AIX OS Lotus Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable AIX OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable AIX OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable AIX OS Microsoft Active Directory 2003 and future fix packs All Applicable AIX OS Microsoft Active Directory 2008 and future fix packs All Applicable AIX OS Microsoft Active Directory Application Mode (ADAM) 2003 and future fix packs All Applicable AIX OS Microsoft AD LDS(Lightweight Directory Services) Windows 2008 and future fix packs All Applicable AIX OS Novell eDirectory 8.7.3 and future fix packs All Applicable AIX OS Novell eDirectory 8.8 and future fix packs All Applicable AIX OS Sun Java System Directory Server 6.1 and future fix packs All Applicable AIX OS Service Pack 10 or later is required. Sun Java System Directory Server 6.3 and future fix packs All Applicable AIX OS Sun Java System Directory Server 7.0 and future fix packs All Applicable AIX OS Tivoli Directory Server 6.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable AIX OS Tivoli Directory Server 6.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable AIX OS Fix pack 4 or later is required. Tivoli Directory Server 6.2 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable AIX OS Java Technology IBM Runtime Environment, Java Technology Edition 6.0 and future mod levels and fix packs All Applicable AIX OS Requirements:\n\n * Java version included or recommended by WebSphere Application Server 7.0.0.19.\n\nSun Java SDK/JRE/JDK 6.0 Update 17 and future fix packs All Applicable AIX OS Supported Java runtime environments 1.5.x or 1.6.x (requires one) for the Web Content Management authoring portlet\n\nJDBC Drivers Apache Derby 10.3 JDBC 4.0 and future fix packs All Applicable AIX OS Derby is a non-production environment. V10.3.3.1 or later is required. DataDirect Connect for JDBC 4.0 (type 4) and future fix packs All Applicable AIX OS DB2 Driver for JDBC and SQLJ (type 2/4) 4.0 and future fix packs All Applicable AIX OS DB2 9.5 and DB2 9.7 require DB2 Driver for JDBC and SQLJ (type 2/4) 4.0 IBM Application Connectivity to DB2 for z/OS Feature Version and future fix packs All Applicable AIX OS IBM DB2 Universal JDBC Provider (XA) from DB2 z/OS (type 4) Version and future fix packs All Applicable AIX OS Requires APAR PK93123 for DB2 on z/OS V8.1 and V9.1. You can obtain the fix from DB2 on z/OS support or IBMLINK. IBM Toolbox for Java/JTOpen JDBC Driver 6.0 and future fix packs All Applicable AIX OS Check for the latest jt400.jar file at:http://sourceforge.net/projects/jt400/files/ [http://sourceforge.net/projects/jt400/files/] Microsoft SQL Server JDBC Driver 2.0 and future fix packs All Applicable AIX OS Microsoft SQL Server JDBC Driver 3.0 All Applicable AIX OS Oracle JDBC Driver (XA) 10g Any and future fix packs All Applicable AIX OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nOracle JDBC Driver (XA) 11g 11.2.0.2 and future fix packs All Applicable AIX OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nMiscellaneous IBM License Metric Tool 7.2.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/license-metric-tool/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMLicenseMetricTool.html] All Applicable AIX OS Tivoli Directory Integrator 7.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-integrator/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryIntegrator.html] All Applicable AIX OS Tivoli License Compliance Manager 2.3 Fixpack 1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/license-mgr/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliLicenseManager.html] All Applicable AIX OS Process Server WebSphere Process Server 7.0.0.3 and future fix packs (overview) [http://www.ibm.com/software/integration/wps/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Process_Server] All Applicable AIX OS Security CA SiteMinder 6.0 and future fix packs All Applicable AIX OS Tivoli Access Manager for e-business 6.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliAccessManagerfore-business.html] All Applicable AIX OS Tivoli Access Manager for e-business 6.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliAccessManagerfore-business.html] All Applicable AIX OS Tools Rational Application Developer for WebSphere Software 8.0 and future fix packs (overview) [http://www.ibm.com/software/awdtools/developer/application/index.html] (support) [http://www.ibm.com/software/awdtools/developer/application/support/index.html] All Applicable AIX OS WebSphere Portlet Factory 7.0 and future fix packs (overview) [http://www.ibm.com/software/genservers/portletfactory/] (support) [http://www.ibm.com/software/genservers/portletfactory/support/] All Applicable AIX OS Virtualization IBM PowerVM Hypervisor (LPAR, DPAR, Micro-Partition) any supported version and future fix packs All Applicable AIX OS IBM PR/SM any version and future fix packs All Applicable AIX OS Red Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.4 and future fix packs All Applicable AIX OS WPAR: Product installed in System Workload Partition AIX 6.1 and future fix packs AIX 5.3 POWER System,\nAIX 6.1 POWER System Refer to the following technote for installation instructions: \n\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21426713 [http://www-01.ibm.com/support/docview.wss?uid=swg21426713] \n\nWPAR: Product installed in System Workload Partition AIX 7.1 and future fix packs AIX 7.1 POWER System Web Browsers Apple Safari 4.0 and future fix packs All Applicable AIX OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nGoogle Chrome 8 and future releases, mod levels and fix packs All Applicable AIX OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at\n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 6.0 SP2 and future fix packs All Applicable AIX OS Internet Explorer 6.0 SP2 on Windows XP SP1/SP2 and Windows 2000 SP4 and Windows 2003. Support for Microsoft Internet Explorer v6.0 is deprecated in this release and due to its limited capabilities many WebSphere Portal features do not function or render correctly, including Client-Side Aggregation (CSA), Page Builder, Mashup integration, Wikis and Blogs. Some legacy pages and themes can be successfully rendered by Microsoft Internet Explorer v6.0, but use of this Web browser is not recommended.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 7.0 and future fix packs All Applicable AIX OS Internet Explorer 7.0 is supported on all versions of Windows that are supported by WebSphere Portal.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 8.0 and future fix packs All Applicable AIX OS See Note #1 Microsoft Internet Explorer 9.0 and future fix packs All Applicable AIX OS Refer to the IE9 Support statement for more information:\n\n http://www.ibm.com/support/docview.wss?uid=swg21496054 [http://www.ibm.com/support/docview.wss?uid=swg21496054]\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMozilla Firefox 3.0 and future fix packs All Applicable AIX OS See Note #1 Mozilla Firefox 3.5 and future fix packs All Applicable AIX OS See Note #1 Mozilla Firefox 3.6 and future fix packs All Applicable AIX OS See Note #1 Mozilla Firefox 4.0 and future releases, mod levels and fix packs All Applicable AIX OS See Note #1 Opera 10.0 and future fix packs All Applicable AIX OS See Note #1 WebDAV Client davfs2 1.4.6 All Applicable AIX OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nJSCAPE AnyClient 2.2 All Applicable AIX OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nSRT WebDrive 9.1 All Applicable AIX OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nWeb Servers Apache HTTP Server 2.0.59 and future fix packs All Applicable AIX OS Apache HTTP Server 2.2 and future fix packs All Applicable AIX OS IBM HTTP Server 6.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/httpservers/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_HTTP_Server] All Applicable AIX OS IBM HTTP Server 7.0 and future fix packs (overview) [http://www.ibm.com/software/webservers/httpservers/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_HTTP_Server] All Applicable AIX OS IBM HTTP Server for i5/OS Any and future fix packs All Applicable AIX OS IBM HTTP Server for i5/OS versions V5R4, V6R1 and V7R1\n\nIBM HTTP Server for z/OS Any and future fix packs All Applicable AIX OS Lotus Domino 8.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable AIX OS Lotus Domino 8.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable AIX OS Lotus Domino 8.0.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable AIX OS Lotus Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable AIX OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable AIX OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable AIX OS Microsoft Internet Information Services 6.0 and future fix packs All Applicable AIX OS Microsoft Internet Information Services 7.0 and future fix packs All Applicable AIX OS Microsoft Internet Information Services 7.5 and future fix packs All Applicable AIX OS Supported as Web server plugins when hosted on the Windows Server 2008 R2 edition. Sun Java System Web Server 6.1 SP10 and future fix packs All Applicable AIX OS Sun Java System Web Server 6.1 Service pack 10 or later is required.\n\nSun Java System Web Server 7.0 Update 8 and future fix packs All Applicable AIX OS Sun Java System Web Server 7.0 Update 8 or later is required.\n\n Back to top \n\n\n\n\nTAB NAVIGATION\n * IBM i \n\n\n\n\nOUTLINE\n * Hardware Requirements * Disk Space \n * Media Drive \n * Memory \n * Processor \n \n \n * Software Requirements * Operating System \n * Application Servers \n \n \n * Optional Supported Software * Application Servers \n * Collaboration \n * Databases \n * Identity Management \n * Java Technology \n * JDBC Drivers \n * Miscellaneous \n * Process Server \n * Security \n * Tools \n * Virtualization \n * Web Browsers \n * WebDAV Client \n * Web Servers \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Disk Space All Applicable IBM i OS Minimum 5.0 GB free disk space with 6 disk arms (cache is desired) for installation for WebSphere Portal\n\nMedia Drive All Applicable IBM i OS A CD/DVD drive is required.\n\nMemory All Applicable IBM i OS Physical memory: 8 GB minimum\nProduction environments and environments featuring multiple profiles will require more memory.\nNote: The amount of memory assigned to the *INTERACT pool should be set at a minimum of well over 1 GB and a maximum of 100%. If the *INTERACT pool cannot be given enough memory, then the database tasks have to be started with SBMJOB so that they run in the *BASE pool.\n\nProcessor All Applicable IBM i OS Recent System i5 and eServer i5 models with at least 3800 CPW\nSystem i model 820 with processor feature 2395\n\n Back to top \n\nOperating Systems Operating System Attributes Notes IBM i Platform listing of supported OS IBM i 5.4 POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System See Note #7 IBM i 6.1 POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System See Note #7 IBM i 7.1 POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System See Note #7 Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers WebSphere Application Server 7.0.0.19 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Application_Server] All Applicable IBM i OS Download mandatory APAR PM52049 for WebSphere Application server 7.0.0.19 from this site -\n\n Fix Central Link for PM52049 [http://www-933.ibm.com/support/fixcentral/swg/selectFix?product=ibm/WebSphere/WebSphere+Application+Server&fixids=7.0.0.19-WS-WAS-IFPM52049&source=dbluesearch&function=fixId&parent=ibm/WebSphere]\n\n [http://www.ibm.com/support/docview.wss?uid=swg24029137]\n\n Back to top \n\nOptional Supported Software Group Product Applicable OS Notes Application Servers WebSphere Application Server Feature Pack for XML 1.0.0.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/xml/index.html] All Applicable IBM i OS WebSphere Application Server V7 Feature Pack for Communications Enabled Applications 1.0.0.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/cea/] All Applicable IBM i OS WebSphere Application Server V7 Feature Pack for Service Component Architecture 1.0.1.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/sca/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Application_Server] All Applicable IBM i OS WebSphere eXtreme Scale 7.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/extremescale/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_eXtreme_Scale] All Applicable IBM i OS Requires version 7.1.0.0 WebSphere Virtual Enterprise 6.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/extend/virtualenterprise/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Virtual_Enterprise] All Applicable IBM i OS Requires fix pack version 6.1.1.2 Collaboration IBM Connections 3.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/IBM_Connections] All Applicable IBM i OS Lotus Connections 2.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Connections] All Applicable IBM i OS Lotus Connections 3.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Connections] All Applicable IBM i OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable IBM i OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable IBM i OS Lotus Quickr for Domino 8.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_Domino] All Applicable IBM i OS Lotus Quickr for Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_Domino] All Applicable IBM i OS Lotus Quickr for WebSphere Portal 8.1.1 Feature Packs and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_WebSphere_Portal] All Applicable IBM i OS Lotus Quickr for WebSphere Portal 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_WebSphere_Portal] All Applicable IBM i OS Lotus Sametime Entry 8.0 and future mod levels and fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/entry/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable IBM i OS IBM Lotus Sametime Entry 8.0.2 requires hot fix BMUY-87SL83 \n\nLotus Sametime Entry 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/entry/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable IBM i OS Requires hot fix BMUY-87SL83\n\nLotus Sametime Standard 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/standard/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable IBM i OS Requires hot fix BMUY-87SL83\n\nDatabases DB2 for i5/OS 6.1 and future fix packs All Applicable IBM i OS DB2 for i5/OS 7.1 and future fix packs All Applicable IBM i OS DB2 for i5/OS V5R4 and future fix packs All Applicable IBM i OS DB2 for z/OS 10.1 and future fix packs (overview) [http://www.ibm.com/software/data/db2/zos/] (support) [http://www.ibm.com/software/data/db2/support/db2zos/] All Applicable IBM i OS Microsoft SQL Server Enterprise Edition 2008 R2 All Applicable IBM i OS Identity Management IBM Tivoli Directory Server for iSeries V5R4 and future fix packs All Applicable IBM i OS IBM Tivoli Directory Server for iSeries V6R1 and future fix packs All Applicable IBM i OS IBM Tivoli Directory Server for iSeries V7R1 and future fix packs All Applicable IBM i OS IBM z/OS.e Security Server 1.6 and future fix packs All Applicable IBM i OS IBM z/OS.e Security Server 1.7 and future fix packs All Applicable IBM i OS IBM z/OS Security Server 1.6 and future fix packs All Applicable IBM i OS IBM z/OS Security Server 1.7 and future fix packs All Applicable IBM i OS Lotus Domino 8.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable IBM i OS Lotus Domino 8.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable IBM i OS Lotus Domino 8.0.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable IBM i OS Lotus Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable IBM i OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable IBM i OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable IBM i OS Microsoft Active Directory 2003 and future fix packs All Applicable IBM i OS Microsoft Active Directory 2008 and future fix packs All Applicable IBM i OS Microsoft Active Directory Application Mode (ADAM) 2003 and future fix packs All Applicable IBM i OS Microsoft AD LDS(Lightweight Directory Services) Windows 2008 and future fix packs All Applicable IBM i OS Novell eDirectory 8.7.3 and future fix packs All Applicable IBM i OS Novell eDirectory 8.8 and future fix packs All Applicable IBM i OS Sun Java System Directory Server 6.1 and future fix packs All Applicable IBM i OS Service Pack 10 or later is required. Sun Java System Directory Server 6.3 and future fix packs All Applicable IBM i OS Sun Java System Directory Server 7.0 and future fix packs All Applicable IBM i OS Tivoli Directory Server 6.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable IBM i OS Tivoli Directory Server 6.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable IBM i OS Fix pack 4 or later is required. Tivoli Directory Server 6.2 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable IBM i OS Java Technology IBM Runtime Environment, Java Technology Edition 6.0 and future mod levels and fix packs All Applicable IBM i OS J2SE 6.0 32-bit for IBM i V5R4\nProduct 5722JV1, option 11 with latest Java group PTF applied\nJ2SE 6.0 32-bit for IBM i V6R1\nProduct 5761JV1, option 11 with latest Java group PTF applied\nJ2SE 6.0 64-bit for IBM i V6R1\nProduct 5761JV1, option 12 with latest Java group PTF applied\n\nSun Java SDK/JRE/JDK 6.0 Update 17 and future fix packs All Applicable IBM i OS Java Developer Kit 6.0 64-bit for IBM i V5R4\nProduct 5722JV1, option 10 with latest Java group PTF applied \nJava Developer Kit 6.0 64-bit for IBM i V6R1\nProduct 5761JV1, option 10 with latest Java group PTF applied JDBC Drivers IBM Toolbox for Java/JTOpen JDBC Driver 6.0 and future fix packs All Applicable IBM i OS Check for the latest jt400.jar file at:http://sourceforge.net/projects/jt400/files/ [http://sourceforge.net/projects/jt400/files/] Microsoft SQL Server JDBC Driver 3.0 All Applicable IBM i OS Miscellaneous IBM License Metric Tool 7.2.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/license-metric-tool/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMLicenseMetricTool.html] All Applicable IBM i OS Tivoli Directory Integrator 7.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-integrator/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryIntegrator.html] All Applicable IBM i OS Tivoli License Compliance Manager 2.3 Fixpack 1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/license-mgr/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliLicenseManager.html] All Applicable IBM i OS Process Server WebSphere Process Server 7.0.0.3 and future fix packs (overview) [http://www.ibm.com/software/integration/wps/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Process_Server] All Applicable IBM i OS Security CA SiteMinder 6.0 and future fix packs All Applicable IBM i OS Tivoli Access Manager for e-business 6.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliAccessManagerfore-business.html] All Applicable IBM i OS Tivoli Access Manager for e-business 6.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliAccessManagerfore-business.html] All Applicable IBM i OS Tools Rational Application Developer for WebSphere Software 8.0 and future fix packs (overview) [http://www.ibm.com/software/awdtools/developer/application/index.html] (support) [http://www.ibm.com/software/awdtools/developer/application/support/index.html] All Applicable IBM i OS WebSphere Portlet Factory 7.0 and future fix packs (overview) [http://www.ibm.com/software/genservers/portletfactory/] (support) [http://www.ibm.com/software/genservers/portletfactory/support/] All Applicable IBM i OS Virtualization IBM PowerVM Hypervisor (LPAR, DPAR, Micro-Partition) any supported version and future fix packs All Applicable IBM i OS IBM PR/SM any version and future fix packs All Applicable IBM i OS Red Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.4 and future fix packs All Applicable IBM i OS Web Browsers Apple Safari 4.0 and future fix packs All Applicable IBM i OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nGoogle Chrome 8 and future releases, mod levels and fix packs All Applicable IBM i OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at\n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 6.0 SP2 and future fix packs All Applicable IBM i OS Internet Explorer 6.0 SP2 on Windows XP SP1/SP2 and Windows 2000 SP4 and Windows 2003. Support for Microsoft Internet Explorer v6.0 is deprecated in this release and due to its limited capabilities many WebSphere Portal features do not function or render correctly, including Client-Side Aggregation (CSA), Page Builder, Mashup integration, Wikis and Blogs. Some legacy pages and themes can be successfully rendered by Microsoft Internet Explorer v6.0, but use of this Web browser is not recommended.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 7.0 and future fix packs All Applicable IBM i OS Internet Explorer 7.0 is supported on all versions of Windows that are supported by WebSphere Portal.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 8.0 and future fix packs All Applicable IBM i OS See Note #1 Microsoft Internet Explorer 9.0 and future fix packs All Applicable IBM i OS Refer to the IE9 Support statement for more information:\n\n http://www.ibm.com/support/docview.wss?uid=swg21496054 [http://www.ibm.com/support/docview.wss?uid=swg21496054]\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMozilla Firefox 3.0 and future fix packs All Applicable IBM i OS See Note #1 Mozilla Firefox 3.5 and future fix packs All Applicable IBM i OS See Note #1 Mozilla Firefox 3.6 and future fix packs All Applicable IBM i OS See Note #1 Mozilla Firefox 4.0 and future releases, mod levels and fix packs All Applicable IBM i OS See Note #1 Opera 10.0 and future fix packs All Applicable IBM i OS See Note #1 WebDAV Client davfs2 1.4.6 All Applicable IBM i OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nJSCAPE AnyClient 2.2 All Applicable IBM i OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nSRT WebDrive 9.1 All Applicable IBM i OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nWeb Servers Apache HTTP Server 2.0.59 and future fix packs All Applicable IBM i OS Apache HTTP Server 2.2 and future fix packs All Applicable IBM i OS IBM HTTP Server 6.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/httpservers/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_HTTP_Server] All Applicable IBM i OS IBM HTTP Server 7.0 and future fix packs (overview) [http://www.ibm.com/software/webservers/httpservers/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_HTTP_Server] All Applicable IBM i OS IBM HTTP Server for i5/OS Any and future fix packs All Applicable IBM i OS IBM HTTP Server for i5/OS versions V5R4, V6R1 and V7R1\n\nIBM HTTP Server for z/OS Any and future fix packs All Applicable IBM i OS Lotus Domino 8.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable IBM i OS Lotus Domino 8.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable IBM i OS Lotus Domino 8.0.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable IBM i OS Lotus Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable IBM i OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable IBM i OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable IBM i OS Microsoft Internet Information Services 6.0 and future fix packs All Applicable IBM i OS Microsoft Internet Information Services 7.0 and future fix packs All Applicable IBM i OS Microsoft Internet Information Services 7.5 and future fix packs All Applicable IBM i OS Supported as Web server plugins when hosted on the Windows Server 2008 R2 edition. Sun Java System Web Server 6.1 SP10 and future fix packs All Applicable IBM i OS Sun Java System Web Server 6.1 Service pack 10 or later is required.\n\nSun Java System Web Server 7.0 Update 8 and future fix packs All Applicable IBM i OS Sun Java System Web Server 7.0 Update 8 or later is required.\n\n Back to top \n\n\n\n\nTAB NAVIGATION\n * Red Hat Enterprise Linux (RHEL) \n * Red Hat Enterprise Linux (RHEL) Server \n * Red Hat Enterprise Linux (RHEL) Workstation \n * SUSE Linux Enterprise Desktop (SLED) \n * SUSE Linux Enterprise Server (SLES) \n\n\n\n\nOUTLINE\n * Hardware Requirements * Disk Space \n * Media Drive \n * Memory \n * Processor \n \n \n * Software Requirements * Operating System \n * Application Servers \n \n \n * Optional Supported Software * Application Servers \n * Collaboration \n * Databases \n * Identity Management \n * Java Technology \n * JDBC Drivers \n * Miscellaneous \n * Process Server \n * Security \n * Tools \n * Virtualization \n * Web Browsers \n * WebDAV Client \n * Web Servers \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Disk Space All Applicable Linux OS Minimum 2.5 GB free disk space for installation for WebSphere Portal\nMinimum 1.4 GB free disk space for installation for WebSphere Application Server\nMinimum 4 GB total disk space recommended for installation\n\nMedia Drive All Applicable Linux OS A CD/DVD drive is required.\n\nMemory All Applicable Linux OS Physical memory requirements and recommendations for WebSphere Portal:\n\n * Under minimal load, WebSphere Portal can function with 2GB of RAM and a remote database.\n * In a production environment, 4GB is an optimal starting point for RAM.\n\nProcessor Red Hat Enterprise Linux (RHEL) 4 Update 6 AS/ES x86-32,\nRed Hat Enterprise Linux (RHEL) 4 Update 6 AS/ES x86-64,\nRed Hat Enterprise Linux (RHEL) 4 Update 6 Desktop x86-32,\nRed Hat Enterprise Linux (RHEL) 4 Update 6 WS x86-32,\nRed Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform x86-32,\nRed Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform x86-64,\nRed Hat Enterprise Linux (RHEL) 5 Update 2 Desktop editions x86-32,\nRed Hat Enterprise Linux (RHEL) Server 6 x86-32,\nRed Hat Enterprise Linux (RHEL) Server 6 x86-64,\nRed Hat Enterprise Linux (RHEL) Workstation 6 x86-32,\nRed Hat Enterprise Linux (RHEL) Workstation 6 x86-64,\nSUSE Linux Enterprise Desktop (SLED) 10.0 SP2 x86-32,\nSUSE Linux Enterprise Desktop (SLED) 11.0 x86-32,\nSUSE Linux Enterprise Server (SLES) 10 SP2 x86-32,\nSUSE Linux Enterprise Server (SLES) 10 SP2 x86-64,\nSUSE Linux Enterprise Server (SLES) 11 x86-32,\nSUSE Linux Enterprise Server (SLES) 11 x86-64,\nSUSE Linux Enterprise Server (SLES) 9 SP4 x86-32,\nSUSE Linux Enterprise Server (SLES) 9 SP4 x86-64 Processor: CPU speeds of late-model, mid-range to high-end servers are recommended (32-bit or 64-bit support). Pentium 800 MHz or equivalent at a minimum. Production environments should consider the Pentium 4 processor at 1.4 GHz or higher. AMD Opteron, Intel EM64T\n\nRed Hat Enterprise Linux (RHEL) 4 Update 6 AS/ES POWER System,\nRed Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform POWER System,\nRed Hat Enterprise Linux (RHEL) Server 6 POWER System,\nSUSE Linux Enterprise Server (SLES) 10 SP2 POWER System,\nSUSE Linux Enterprise Server (SLES) 11 POWER System,\nSUSE Linux Enterprise Server (SLES) 9 SP4 POWER System IBM System i (iSeries) IBM System p (pSeries), IBM OpenPower, or IBM BladeCenter.\nSystem p includes IBM system product lines System i5 models that support LPAR (64-bit support only) with minimum of 450 CPW in Linux Partition, System p models that support Linux (64-bit support only), BladeCenter JS20, and OpenPower that are based on IBM System p architecture technology and run the same Linux distributions from Red Hat and Novell SUSE.\n\nRed Hat Enterprise Linux (RHEL) 4 Update 6 AS/ES System z,\nRed Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform System z,\nRed Hat Enterprise Linux (RHEL) Server 6 System z,\nSUSE Linux Enterprise Server (SLES) 10 SP2 System z,\nSUSE Linux Enterprise Server (SLES) 11 System z,\nSUSE Linux Enterprise Server (SLES) 9 SP4 System z System z processors\n\n Back to top \n\nOperating Systems Operating System Attributes Notes Linux Platform listing of supported OS Red Hat Enterprise Linux (RHEL) 4 Update 6 AS/ES POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System WebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK/WebSphere Application Server on 64-bit OS \n * 64-bit JDK/WebSphere Application Server on 64-bit OS \n\nRed Hat Enterprise Linux (RHEL) 4 Update 6 AS/ES System z and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: System z See Note #8 Red Hat Enterprise Linux (RHEL) 4 Update 6 AS/ES x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #5 Red Hat Enterprise Linux (RHEL) 4 Update 6 AS/ES x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #7 Red Hat Enterprise Linux (RHEL) 4 Update 6 Desktop x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #2 Red Hat Enterprise Linux (RHEL) 4 Update 6 WS x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #2 Red Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System See Note #7 Red Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform System z and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: System z See Note #8 Red Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #5 Red Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #7 Red Hat Enterprise Linux (RHEL) 5 Update 2 Desktop editions x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #2 Red Hat Enterprise Linux (RHEL) Server 6 POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System WebSphere Application Server requirements depending on operating system bit:\n\n• 32-bit JDK/WebSphere Application Server on 64-bit OS\n• 64-bit JDK/WebSphere Application Server on 64-bit OS Red Hat Enterprise Linux (RHEL) Server 6 System z and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: System z WebSphere Application Server requirements depending on operating system bit:\n\n• 64-bit JDK/WebSphere Application Server on 64-bit OS Red Hat Enterprise Linux (RHEL) Server 6 x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 WebSphere Application Server requirements depending on operating system bit:\n\n• 32-bit JDK/WebSphere Application Server on 32-bit OS Red Hat Enterprise Linux (RHEL) Server 6 x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 WebSphere Application Server requirements depending on operating system bit:\n\n• 32-bit JDK/WebSphere Application Server on 64-bit OS\n• 64-bit JDK/WebSphere Application Server on 64-bit OS Red Hat Enterprise Linux (RHEL) Workstation 6 x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 WebSphere Application Server requirements depending on operating system bit:\n\n• 32-bit JDK/WebSphere Application Server on 32-bit OS Red Hat Enterprise Linux (RHEL) Workstation 6 x86-64 and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: x86-64 See Note #8 SUSE Linux Enterprise Desktop (SLED) 10.0 SP2 x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #2 SUSE Linux Enterprise Desktop (SLED) 11.0 x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #2 SUSE Linux Enterprise Server (SLES) 10 SP2 POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System See Note #7 SUSE Linux Enterprise Server (SLES) 10 SP2 System z and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: System z See Note #8 SUSE Linux Enterprise Server (SLES) 10 SP2 x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #4 SUSE Linux Enterprise Server (SLES) 10 SP2 x86-64 and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: x86-64 See Note #6 SUSE Linux Enterprise Server (SLES) 11 POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System See Note #6 SUSE Linux Enterprise Server (SLES) 11 System z and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: System z WebSphere Application Server requirements depending on operating system bit:\n\n * 64-bit JDK/WebSphere Application Server on 64-bit OS\n\nSUSE Linux Enterprise Server (SLES) 11 x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #5 SUSE Linux Enterprise Server (SLES) 11 x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #7 SUSE Linux Enterprise Server (SLES) 9 SP4 POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System See Note #7 SUSE Linux Enterprise Server (SLES) 9 SP4 System z and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: System z See Note #8 SUSE Linux Enterprise Server (SLES) 9 SP4 x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #5 SUSE Linux Enterprise Server (SLES) 9 SP4 x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #7 Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers WebSphere Application Server 7.0.0.19 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Application_Server] All Applicable Linux OS Download mandatory APAR PM52049 for WebSphere Application server 7.0.0.19 from this site -\n\n Fix Central Link for PM52049 [http://www-933.ibm.com/support/fixcentral/swg/selectFix?product=ibm/WebSphere/WebSphere+Application+Server&fixids=7.0.0.19-WS-WAS-IFPM52049&source=dbluesearch&function=fixId&parent=ibm/WebSphere]\n\n [http://www.ibm.com/support/docview.wss?uid=swg24029137]\n\n Back to top \n\nOptional Supported Software Group Product Applicable OS Notes Application Servers WebSphere Application Server Feature Pack for XML 1.0.0.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/xml/index.html] All Applicable Linux OS WebSphere Application Server V7 Feature Pack for Communications Enabled Applications 1.0.0.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/cea/] All Applicable Linux OS WebSphere Application Server V7 Feature Pack for Service Component Architecture 1.0.1.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/sca/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Application_Server] All Applicable Linux OS WebSphere eXtreme Scale 7.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/extremescale/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_eXtreme_Scale] All Applicable Linux OS Requires version 7.1.0.0 WebSphere Virtual Enterprise 6.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/extend/virtualenterprise/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Virtual_Enterprise] All Applicable Linux OS Requires fix pack version 6.1.1.2 Collaboration IBM Connections 3.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/IBM_Connections] All Applicable Linux OS Lotus Connections 2.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Connections] All Applicable Linux OS Lotus Connections 3.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Connections] All Applicable Linux OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Linux OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Linux OS Lotus Quickr for Domino 8.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_Domino] All Applicable Linux OS Lotus Quickr for Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_Domino] All Applicable Linux OS Lotus Quickr for WebSphere Portal 8.1.1 Feature Packs and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_WebSphere_Portal] All Applicable Linux OS Lotus Quickr for WebSphere Portal 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_WebSphere_Portal] All Applicable Linux OS Lotus Sametime Entry 8.0 and future mod levels and fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/entry/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable Linux OS IBM Lotus Sametime Entry 8.0.2 requires hot fix BMUY-87SL83 \n\nLotus Sametime Entry 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/entry/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable Linux OS Requires hot fix BMUY-87SL83\n\nLotus Sametime Standard 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/standard/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable Linux OS Requires hot fix BMUY-87SL83\n\nDatabases Apache Derby 10.3 and future fix packs All Applicable Linux OS Not supported in a production environment.\n\nDB2 9 for Linux, UNIX and Windows 9.1.0.9 and future fix packs All Applicable Linux OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Enterprise Server Edition 9.7.0.1 and future fix packs (overview) [http://www.ibm.com/software/data/db2/linux-unix-windows/edition-enterprise.html] (support) [http://www.ibm.com/software/data/db2/support/db2_9/] All Applicable Linux OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\n Database parameter 'cur_commit' must be set to 'DISABLED' for database of WebSphere Portal 7\n\nDB2 for i5/OS 6.1 and future fix packs All Applicable Linux OS DB2 for i5/OS 7.1 and future fix packs All Applicable Linux OS DB2 for i5/OS V5R4 and future fix packs All Applicable Linux OS DB2 for z/OS 9.1 and future fix packs (overview) [http://www.ibm.com/software/data/db2/zos/] (support) [http://www.ibm.com/software/data/db2/support/db2zos/] All Applicable Linux OS High Availability Disaster Recovery (HADR) Feature is supported.\n\n WebSphere Portal 7.0 works with DB2 for z/OS V9.1 - PUT level 0912.\n\n The following are required:\n\n * APAR PK75093 or later\n * APAR PK92163:\n http://www-01.ibm.com/support/docview.wss?uid=swg1PK92163 [http://www-01.ibm.com/support/docview.wss?uid=swg1PK92163]\n * APAR PK68265\n\nDB2 for z/OS 10.1 and future fix packs (overview) [http://www.ibm.com/software/data/db2/zos/] (support) [http://www.ibm.com/software/data/db2/support/db2zos/] All Applicable Linux OS DB2 pureScale Feature for Enterprise Server Edition 9.8.0.3 and future fix packs All Applicable Linux OS Requires 7.0.0.1 CF007 or higher.\n\n Refer to the steps documented here: http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open]\n\nDB2 Universal Database for z/OS 8.1 and future fix packs All Applicable Linux OS WebSphere Portal 7.0 works with DB2 for z/OS V8.1 - PUT level 0912 or later service level.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Workgroup Server Edition 9.5.0.5 and future fix packs (overview) [http://www.ibm.com/software/data/db2/linux-unix-windows/edition-workgroup.html] (support) [http://www.ibm.com/software/data/db2/support/db2_9/] All Applicable Linux OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nMicrosoft SQL Server Enterprise Edition 2005 SP2 and future fix packs All Applicable Linux OS Microsoft SQL Server Enterprise Edition 2008 and future fix packs All Applicable Linux OS Microsoft SQL Server Enterprise Edition 2008 R2 All Applicable Linux OS Oracle Database 10g Enterprise Edition Release 1 10.1.0.5 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 10g Enterprise Edition Release 2 10.2.0.4 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 10g Standard Edition Release 1 10.1.0.5 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 10g Standard Edition Release 2 10.2.0.4 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.6 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.7 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 11g Enterprise Edition Release 2 11.2.0.2 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.6 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.7 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 11g Standard Edition Release 2 11.2.0.2 and future fix packs All Applicable Linux OS See Note #3 Identity Management IBM z/OS.e Security Server 1.6 and future fix packs All Applicable Linux OS IBM z/OS.e Security Server 1.7 and future fix packs All Applicable Linux OS IBM z/OS Security Server 1.6 and future fix packs All Applicable Linux OS IBM z/OS Security Server 1.7 and future fix packs All Applicable Linux OS Lotus Domino 8.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Linux OS Lotus Domino 8.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Linux OS Lotus Domino 8.0.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Linux OS Lotus Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Linux OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Linux OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Linux OS Microsoft Active Directory 2003 and future fix packs All Applicable Linux OS Microsoft Active Directory 2008 and future fix packs All Applicable Linux OS Microsoft Active Directory Application Mode (ADAM) 2003 and future fix packs All Applicable Linux OS Microsoft AD LDS(Lightweight Directory Services) Windows 2008 and future fix packs All Applicable Linux OS Novell eDirectory 8.7.3 and future fix packs All Applicable Linux OS Novell eDirectory 8.8 and future fix packs All Applicable Linux OS Sun Java System Directory Server 6.1 and future fix packs All Applicable Linux OS Service Pack 10 or later is required. Sun Java System Directory Server 6.3 and future fix packs All Applicable Linux OS Sun Java System Directory Server 7.0 and future fix packs All Applicable Linux OS Tivoli Directory Server 6.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable Linux OS Tivoli Directory Server 6.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable Linux OS Fix pack 4 or later is required. Tivoli Directory Server 6.2 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable Linux OS Java Technology IBM Runtime Environment, Java Technology Edition 6.0 and future mod levels and fix packs All Applicable Linux OS Requirements:\n\n * Java version included or recommended by WebSphere Application Server 7.0.0.19.\n\nSun Java SDK/JRE/JDK 6.0 Update 17 and future fix packs All Applicable Linux OS Supported Java runtime environments 1.5.x or 1.6.x (requires one) for the Web Content Management authoring portlet\n\nJDBC Drivers Apache Derby 10.3 JDBC 4.0 and future fix packs All Applicable Linux OS Derby is a non-production environment. V10.3.3.1 or later is required. DataDirect Connect for JDBC 4.0 (type 4) and future fix packs All Applicable Linux OS DB2 Driver for JDBC and SQLJ (type 2/4) 4.0 and future fix packs All Applicable Linux OS DB2 9.5 and DB2 9.7 require DB2 Driver for JDBC and SQLJ (type 2/4) 4.0 IBM Application Connectivity to DB2 for z/OS Feature Version and future fix packs All Applicable Linux OS IBM DB2 Universal JDBC Provider (XA) from DB2 z/OS (type 4) Version and future fix packs All Applicable Linux OS Requires APAR PK93123 for DB2 on z/OS V8.1 and V9.1. You can obtain the fix from DB2 on z/OS support or IBMLINK. IBM Toolbox for Java/JTOpen JDBC Driver 6.0 and future fix packs All Applicable Linux OS Check for the latest jt400.jar file at:http://sourceforge.net/projects/jt400/files/ [http://sourceforge.net/projects/jt400/files/] Microsoft SQL Server JDBC Driver 2.0 and future fix packs All Applicable Linux OS Microsoft SQL Server JDBC Driver 3.0 All Applicable Linux OS Oracle JDBC Driver (XA) 10g Any and future fix packs All Applicable Linux OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nOracle JDBC Driver (XA) 11g 11.2.0.2 and future fix packs All Applicable Linux OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nMiscellaneous IBM License Metric Tool 7.2.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/license-metric-tool/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMLicenseMetricTool.html] All Applicable Linux OS Tivoli Directory Integrator 7.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-integrator/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryIntegrator.html] All Applicable Linux OS Tivoli License Compliance Manager 2.3 Fixpack 1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/license-mgr/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliLicenseManager.html] All Applicable Linux OS Process Server WebSphere Process Server 7.0.0.3 and future fix packs (overview) [http://www.ibm.com/software/integration/wps/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Process_Server] All Applicable Linux OS Security CA SiteMinder 6.0 and future fix packs All Applicable Linux OS Tivoli Access Manager for e-business 6.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliAccessManagerfore-business.html] All Applicable Linux OS Tivoli Access Manager for e-business 6.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliAccessManagerfore-business.html] All Applicable Linux OS Tools Rational Application Developer for WebSphere Software 8.0 and future fix packs (overview) [http://www.ibm.com/software/awdtools/developer/application/index.html] (support) [http://www.ibm.com/software/awdtools/developer/application/support/index.html] All Applicable Linux OS WebSphere Portlet Factory 7.0 and future fix packs (overview) [http://www.ibm.com/software/genservers/portletfactory/] (support) [http://www.ibm.com/software/genservers/portletfactory/support/] All Applicable Linux OS Virtualization IBM PowerVM Hypervisor (LPAR, DPAR, Micro-Partition) any supported version and future fix packs All Applicable Linux OS IBM PR/SM any version and future fix packs All Applicable Linux OS KVM in SUSE Linux Enterprise Server (SLES) 11 SUSE Linux Enterprise Server (SLES) 11 POWER System,\nSUSE Linux Enterprise Server (SLES) 11 System z,\nSUSE Linux Enterprise Server (SLES) 11 x86-32,\nSUSE Linux Enterprise Server (SLES) 11 x86-64 Red Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.4 and future fix packs All Applicable Linux OS VMware ESX 4.0 and future releases, mod levels and fix packs All Applicable Linux OS VMware ESXi 4.0 and future releases, mod levels and fix packs All Applicable Linux OS z/VM 6.1 and future fix packs (overview) [http://www.vm.ibm.com/] All Applicable Linux OS Web Browsers Apple Safari 4.0 and future fix packs All Applicable Linux OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nGoogle Chrome 8 and future releases, mod levels and fix packs All Applicable Linux OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at\n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 6.0 SP2 and future fix packs All Applicable Linux OS Internet Explorer 6.0 SP2 on Windows XP SP1/SP2 and Windows 2000 SP4 and Windows 2003. Support for Microsoft Internet Explorer v6.0 is deprecated in this release and due to its limited capabilities many WebSphere Portal features do not function or render correctly, including Client-Side Aggregation (CSA), Page Builder, Mashup integration, Wikis and Blogs. Some legacy pages and themes can be successfully rendered by Microsoft Internet Explorer v6.0, but use of this Web browser is not recommended.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 7.0 and future fix packs All Applicable Linux OS Internet Explorer 7.0 is supported on all versions of Windows that are supported by WebSphere Portal.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 8.0 and future fix packs All Applicable Linux OS See Note #1 Microsoft Internet Explorer 9.0 and future fix packs All Applicable Linux OS Refer to the IE9 Support statement for more information:\n\n http://www.ibm.com/support/docview.wss?uid=swg21496054 [http://www.ibm.com/support/docview.wss?uid=swg21496054]\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMozilla Firefox 3.0 and future fix packs All Applicable Linux OS See Note #1 Mozilla Firefox 3.5 and future fix packs All Applicable Linux OS See Note #1 Mozilla Firefox 3.6 and future fix packs All Applicable Linux OS See Note #1 Mozilla Firefox 4.0 and future releases, mod levels and fix packs All Applicable Linux OS See Note #1 Opera 10.0 and future fix packs All Applicable Linux OS See Note #1 WebDAV Client davfs2 1.4.6 All Applicable Linux OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nJSCAPE AnyClient 2.2 All Applicable Linux OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nSRT WebDrive 9.1 All Applicable Linux OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nWeb Servers Apache HTTP Server 2.0.59 and future fix packs All Applicable Linux OS Apache HTTP Server 2.2 and future fix packs All Applicable Linux OS IBM HTTP Server 6.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/httpservers/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_HTTP_Server] All Applicable Linux OS IBM HTTP Server 7.0 and future fix packs (overview) [http://www.ibm.com/software/webservers/httpservers/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_HTTP_Server] All Applicable Linux OS IBM HTTP Server for i5/OS Any and future fix packs All Applicable Linux OS IBM HTTP Server for i5/OS versions V5R4, V6R1 and V7R1\n\nIBM HTTP Server for z/OS Any and future fix packs All Applicable Linux OS Lotus Domino 8.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Linux OS Lotus Domino 8.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Linux OS Lotus Domino 8.0.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Linux OS Lotus Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Linux OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Linux OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Linux OS Microsoft Internet Information Services 6.0 and future fix packs All Applicable Linux OS Microsoft Internet Information Services 7.0 and future fix packs All Applicable Linux OS Microsoft Internet Information Services 7.5 and future fix packs All Applicable Linux OS Supported as Web server plugins when hosted on the Windows Server 2008 R2 edition. Sun Java System Web Server 6.1 SP10 and future fix packs All Applicable Linux OS Sun Java System Web Server 6.1 Service pack 10 or later is required.\n\nSun Java System Web Server 7.0 Update 8 and future fix packs All Applicable Linux OS Sun Java System Web Server 7.0 Update 8 or later is required.\n\n Back to top \n\n\n\n\nTAB NAVIGATION\n * Solaris \n\n\n\n\nOUTLINE\n * Hardware Requirements * Disk Space \n * Media Drive \n * Memory \n * Processor \n \n \n * Software Requirements * Operating System \n * Application Servers \n \n \n * Optional Supported Software * Application Servers \n * Collaboration \n * Databases \n * Identity Management \n * Java Technology \n * JDBC Drivers \n * Miscellaneous \n * Process Server \n * Security \n * Tools \n * Virtualization \n * Web Browsers \n * WebDAV Client \n * Web Servers \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Disk Space All Applicable Solaris OS Minimum 2.5 GB free disk space for installation for WebSphere Portal\nMinimum 1.4 GB free disk space for installation for WebSphere Application Server\nMinimum 4 GB total disk space recommended for installation\n\nMedia Drive All Applicable Solaris OS A CD/DVD drive is required.\n\nMemory All Applicable Solaris OS Physical memory requirements and recommendations for WebSphere Portal:\n\n * Under minimal load, WebSphere Portal can function with 2GB of RAM and a remote database.\n * In a production environment, 4GB is an optimal starting point for RAM.\n\nProcessor Solaris 10 x86-64 AMD Opteron (64 bit kernel support only); Intel EM64T (64 bit kernel support only) \n\n Back to top \n\nOperating Systems Operating System Attributes Notes Solaris Platform listing of supported OS Solaris 10 SPARC and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: SPARC WebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK/Application Server on 64-bit OS\n * 64-bit JDK/Application Server on 64-bit OS\n\nSolaris 10 x86-64 and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: x86-64 See Note #8 Solaris 9 SPARC and future OS fix packs Bitness: 32 Bit\nHardware platform: SPARC WebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK/WebSphere Application Server on 64-bit OS \n\n Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers WebSphere Application Server 7.0.0.19 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Application_Server] All Applicable Solaris OS Download mandatory APAR PM52049 for WebSphere Application server 7.0.0.19 from this site -\n\n Fix Central Link for PM52049 [http://www-933.ibm.com/support/fixcentral/swg/selectFix?product=ibm/WebSphere/WebSphere+Application+Server&fixids=7.0.0.19-WS-WAS-IFPM52049&source=dbluesearch&function=fixId&parent=ibm/WebSphere]\n\n [http://www.ibm.com/support/docview.wss?uid=swg24029137]\n\n Back to top \n\nOptional Supported Software Group Product Applicable OS Notes Application Servers WebSphere Application Server Feature Pack for XML 1.0.0.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/xml/index.html] All Applicable Solaris OS WebSphere Application Server V7 Feature Pack for Communications Enabled Applications 1.0.0.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/cea/] All Applicable Solaris OS WebSphere Application Server V7 Feature Pack for Service Component Architecture 1.0.1.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/sca/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Application_Server] All Applicable Solaris OS WebSphere eXtreme Scale 7.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/extremescale/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_eXtreme_Scale] All Applicable Solaris OS Requires version 7.1.0.0 WebSphere Virtual Enterprise 6.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/extend/virtualenterprise/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Virtual_Enterprise] All Applicable Solaris OS Requires fix pack version 6.1.1.2 Collaboration IBM Connections 3.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/IBM_Connections] All Applicable Solaris OS Lotus Connections 2.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Connections] All Applicable Solaris OS Lotus Connections 3.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Connections] All Applicable Solaris OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Solaris OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Solaris OS Lotus Quickr for Domino 8.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_Domino] All Applicable Solaris OS Lotus Quickr for Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_Domino] All Applicable Solaris OS Lotus Quickr for WebSphere Portal 8.1.1 Feature Packs and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_WebSphere_Portal] All Applicable Solaris OS Lotus Quickr for WebSphere Portal 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_WebSphere_Portal] All Applicable Solaris OS Lotus Sametime Entry 8.0 and future mod levels and fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/entry/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable Solaris OS IBM Lotus Sametime Entry 8.0.2 requires hot fix BMUY-87SL83 \n\nLotus Sametime Entry 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/entry/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable Solaris OS Requires hot fix BMUY-87SL83\n\nLotus Sametime Standard 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/standard/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable Solaris OS Requires hot fix BMUY-87SL83\n\nDatabases Apache Derby 10.3 and future fix packs All Applicable Solaris OS Not supported in a production environment.\n\nDB2 9 for Linux, UNIX and Windows 9.1.0.9 and future fix packs All Applicable Solaris OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Enterprise Server Edition 9.7.0.1 and future fix packs (overview) [http://www.ibm.com/software/data/db2/linux-unix-windows/edition-enterprise.html] (support) [http://www.ibm.com/software/data/db2/support/db2_9/] All Applicable Solaris OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\n Database parameter 'cur_commit' must be set to 'DISABLED' for database of WebSphere Portal 7\n\nDB2 for i5/OS 6.1 and future fix packs All Applicable Solaris OS DB2 for i5/OS 7.1 and future fix packs All Applicable Solaris OS DB2 for i5/OS V5R4 and future fix packs All Applicable Solaris OS DB2 for z/OS 9.1 and future fix packs (overview) [http://www.ibm.com/software/data/db2/zos/] (support) [http://www.ibm.com/software/data/db2/support/db2zos/] All Applicable Solaris OS High Availability Disaster Recovery (HADR) Feature is supported.\n\n WebSphere Portal 7.0 works with DB2 for z/OS V9.1 - PUT level 0912.\n\n The following are required:\n\n * APAR PK75093 or later\n * APAR PK92163:\n http://www-01.ibm.com/support/docview.wss?uid=swg1PK92163 [http://www-01.ibm.com/support/docview.wss?uid=swg1PK92163]\n * APAR PK68265\n\nDB2 for z/OS 10.1 and future fix packs (overview) [http://www.ibm.com/software/data/db2/zos/] (support) [http://www.ibm.com/software/data/db2/support/db2zos/] All Applicable Solaris OS DB2 pureScale Feature for Enterprise Server Edition 9.8.0.3 and future fix packs All Applicable Solaris OS Requires 7.0.0.1 CF007 or higher.\n\n Refer to the steps documented here: http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open]\n\nDB2 Universal Database for z/OS 8.1 and future fix packs All Applicable Solaris OS WebSphere Portal 7.0 works with DB2 for z/OS V8.1 - PUT level 0912 or later service level.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Workgroup Server Edition 9.5.0.5 and future fix packs (overview) [http://www.ibm.com/software/data/db2/linux-unix-windows/edition-workgroup.html] (support) [http://www.ibm.com/software/data/db2/support/db2_9/] All Applicable Solaris OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nMicrosoft SQL Server Enterprise Edition 2005 SP2 and future fix packs All Applicable Solaris OS Microsoft SQL Server Enterprise Edition 2008 and future fix packs All Applicable Solaris OS Microsoft SQL Server Enterprise Edition 2008 R2 All Applicable Solaris OS Oracle Database 10g Enterprise Edition Release 1 10.1.0.5 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 10g Enterprise Edition Release 2 10.2.0.4 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 10g Standard Edition Release 1 10.1.0.5 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 10g Standard Edition Release 2 10.2.0.4 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.6 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.7 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 11g Enterprise Edition Release 2 11.2.0.2 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.6 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.7 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 11g Standard Edition Release 2 11.2.0.2 and future fix packs All Applicable Solaris OS See Note #3 Identity Management IBM z/OS.e Security Server 1.6 and future fix packs All Applicable Solaris OS IBM z/OS.e Security Server 1.7 and future fix packs All Applicable Solaris OS IBM z/OS Security Server 1.6 and future fix packs All Applicable Solaris OS IBM z/OS Security Server 1.7 and future fix packs All Applicable Solaris OS Lotus Domino 8.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Solaris OS Lotus Domino 8.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Solaris OS Lotus Domino 8.0.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Solaris OS Lotus Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Solaris OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Solaris OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Solaris OS Microsoft Active Directory 2003 and future fix packs All Applicable Solaris OS Microsoft Active Directory 2008 and future fix packs All Applicable Solaris OS Microsoft Active Directory Application Mode (ADAM) 2003 and future fix packs All Applicable Solaris OS Microsoft AD LDS(Lightweight Directory Services) Windows 2008 and future fix packs All Applicable Solaris OS Novell eDirectory 8.7.3 and future fix packs All Applicable Solaris OS Novell eDirectory 8.8 and future fix packs All Applicable Solaris OS Sun Java System Directory Server 6.1 and future fix packs All Applicable Solaris OS Service Pack 10 or later is required. Sun Java System Directory Server 6.3 and future fix packs All Applicable Solaris OS Sun Java System Directory Server 7.0 and future fix packs All Applicable Solaris OS Tivoli Directory Server 6.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable Solaris OS Tivoli Directory Server 6.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable Solaris OS Fix pack 4 or later is required. Tivoli Directory Server 6.2 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable Solaris OS Java Technology IBM Runtime Environment, Java Technology Edition 6.0 and future mod levels and fix packs All Applicable Solaris OS Requirements:\n\n * Java version included or recommended by WebSphere Application Server 7.0.0.19.\n\nSun Java SDK/JRE/JDK 6.0 Update 17 and future fix packs All Applicable Solaris OS Supported Java runtime environments 1.5.x or 1.6.x (requires one) for the Web Content Management authoring portlet\n\nJDBC Drivers Apache Derby 10.3 JDBC 4.0 and future fix packs All Applicable Solaris OS Derby is a non-production environment. V10.3.3.1 or later is required. DataDirect Connect for JDBC 4.0 (type 4) and future fix packs All Applicable Solaris OS DB2 Driver for JDBC and SQLJ (type 2/4) 4.0 and future fix packs All Applicable Solaris OS DB2 9.5 and DB2 9.7 require DB2 Driver for JDBC and SQLJ (type 2/4) 4.0 IBM Application Connectivity to DB2 for z/OS Feature Version and future fix packs All Applicable Solaris OS IBM DB2 Universal JDBC Provider (XA) from DB2 z/OS (type 4) Version and future fix packs All Applicable Solaris OS Requires APAR PK93123 for DB2 on z/OS V8.1 and V9.1. You can obtain the fix from DB2 on z/OS support or IBMLINK. IBM Toolbox for Java/JTOpen JDBC Driver 6.0 and future fix packs All Applicable Solaris OS Check for the latest jt400.jar file at:http://sourceforge.net/projects/jt400/files/ [http://sourceforge.net/projects/jt400/files/] Microsoft SQL Server JDBC Driver 2.0 and future fix packs All Applicable Solaris OS Microsoft SQL Server JDBC Driver 3.0 All Applicable Solaris OS Oracle JDBC Driver (XA) 10g Any and future fix packs All Applicable Solaris OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nOracle JDBC Driver (XA) 11g 11.2.0.2 and future fix packs All Applicable Solaris OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nMiscellaneous IBM License Metric Tool 7.2.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/license-metric-tool/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMLicenseMetricTool.html] All Applicable Solaris OS Tivoli Directory Integrator 7.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-integrator/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryIntegrator.html] All Applicable Solaris OS Tivoli License Compliance Manager 2.3 Fixpack 1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/license-mgr/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliLicenseManager.html] All Applicable Solaris OS Process Server WebSphere Process Server 7.0.0.3 and future fix packs (overview) [http://www.ibm.com/software/integration/wps/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Process_Server] All Applicable Solaris OS Security CA SiteMinder 6.0 and future fix packs All Applicable Solaris OS Tivoli Access Manager for e-business 6.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliAccessManagerfore-business.html] All Applicable Solaris OS Tivoli Access Manager for e-business 6.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliAccessManagerfore-business.html] All Applicable Solaris OS Tools Rational Application Developer for WebSphere Software 8.0 and future fix packs (overview) [http://www.ibm.com/software/awdtools/developer/application/index.html] (support) [http://www.ibm.com/software/awdtools/developer/application/support/index.html] All Applicable Solaris OS WebSphere Portlet Factory 7.0 and future fix packs (overview) [http://www.ibm.com/software/genservers/portletfactory/] (support) [http://www.ibm.com/software/genservers/portletfactory/support/] All Applicable Solaris OS Virtualization IBM PR/SM any version and future fix packs All Applicable Solaris OS Red Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.4 and future fix packs All Applicable Solaris OS Web Browsers Apple Safari 4.0 and future fix packs All Applicable Solaris OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nGoogle Chrome 8 and future releases, mod levels and fix packs All Applicable Solaris OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at\n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 6.0 SP2 and future fix packs All Applicable Solaris OS Internet Explorer 6.0 SP2 on Windows XP SP1/SP2 and Windows 2000 SP4 and Windows 2003. Support for Microsoft Internet Explorer v6.0 is deprecated in this release and due to its limited capabilities many WebSphere Portal features do not function or render correctly, including Client-Side Aggregation (CSA), Page Builder, Mashup integration, Wikis and Blogs. Some legacy pages and themes can be successfully rendered by Microsoft Internet Explorer v6.0, but use of this Web browser is not recommended.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 7.0 and future fix packs All Applicable Solaris OS Internet Explorer 7.0 is supported on all versions of Windows that are supported by WebSphere Portal.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 8.0 and future fix packs All Applicable Solaris OS See Note #1 Microsoft Internet Explorer 9.0 and future fix packs All Applicable Solaris OS Refer to the IE9 Support statement for more information:\n\n http://www.ibm.com/support/docview.wss?uid=swg21496054 [http://www.ibm.com/support/docview.wss?uid=swg21496054]\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMozilla Firefox 3.0 and future fix packs All Applicable Solaris OS See Note #1 Mozilla Firefox 3.5 and future fix packs All Applicable Solaris OS See Note #1 Mozilla Firefox 3.6 and future fix packs All Applicable Solaris OS See Note #1 Mozilla Firefox 4.0 and future releases, mod levels and fix packs All Applicable Solaris OS See Note #1 Opera 10.0 and future fix packs All Applicable Solaris OS See Note #1 WebDAV Client davfs2 1.4.6 All Applicable Solaris OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nJSCAPE AnyClient 2.2 All Applicable Solaris OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nSRT WebDrive 9.1 All Applicable Solaris OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nWeb Servers Apache HTTP Server 2.0.59 and future fix packs All Applicable Solaris OS Apache HTTP Server 2.2 and future fix packs All Applicable Solaris OS IBM HTTP Server 6.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/httpservers/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_HTTP_Server] All Applicable Solaris OS IBM HTTP Server 7.0 and future fix packs (overview) [http://www.ibm.com/software/webservers/httpservers/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_HTTP_Server] All Applicable Solaris OS IBM HTTP Server for i5/OS Any and future fix packs All Applicable Solaris OS IBM HTTP Server for i5/OS versions V5R4, V6R1 and V7R1\n\nIBM HTTP Server for z/OS Any and future fix packs All Applicable Solaris OS Lotus Domino 8.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Solaris OS Lotus Domino 8.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Solaris OS Lotus Domino 8.0.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Solaris OS Lotus Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Solaris OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Solaris OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Solaris OS Microsoft Internet Information Services 6.0 and future fix packs All Applicable Solaris OS Microsoft Internet Information Services 7.0 and future fix packs All Applicable Solaris OS Microsoft Internet Information Services 7.5 and future fix packs All Applicable Solaris OS Supported as Web server plugins when hosted on the Windows Server 2008 R2 edition. Sun Java System Web Server 6.1 SP10 and future fix packs All Applicable Solaris OS Sun Java System Web Server 6.1 Service pack 10 or later is required.\n\nSun Java System Web Server 7.0 Update 8 and future fix packs All Applicable Solaris OS Sun Java System Web Server 7.0 Update 8 or later is required.\n\n Back to top \n\n\n\n\nTAB NAVIGATION\n * Windows 7 \n * Windows Server 2003 \n * Windows Server 2008 \n * Windows Vista \n * Windows XP \n\n\n\n\nOUTLINE\n * Hardware Requirements * Disk Space \n * Media Drive \n * Memory \n \n \n * Software Requirements * Operating System \n * Application Servers \n \n \n * Optional Supported Software * Application Servers \n * Collaboration \n * Databases \n * Identity Management \n * Java Technology \n * JDBC Drivers \n * Miscellaneous \n * Process Server \n * Security \n * Tools \n * Virtualization \n * Web Browsers \n * WebDAV Client \n * Web Servers \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Disk Space All Applicable Windows OS Minimum 2.5 GB free disk space for installation for WebSphere Portal\nMinimum 1.4 GB free disk space for installation for WebSphere Application Server\nMinimum 4 GB total disk space recommended for installation\n\nMedia Drive All Applicable Windows OS A CD/DVD drive is required.\n\nMemory All Applicable Windows OS Physical memory requirements and recommendations for WebSphere Portal:\n\n * Under minimal load, WebSphere Portal can function with 2GB of RAM and a remote database.\n * In a production environment, 4GB is an optimal starting point for RAM.\n\n Back to top \n\nOperating Systems Operating System Attributes Notes Windows Platform listing of supported OS Windows 7 Enterprise x86-32 Bitness: 32 Bit\nHardware platform: x86-32 Support for developer platform only.\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK/WebSphere Application Server on 32-bit OS\n\nWindows 7 Enterprise x86-64 Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 Support for developer platform only.\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK/WebSphere Application Server on 64-bit OS\n * 64-bit JDK/WebSphere Application Server on 64-bit OS\n\nWindows 7 Professional x86-32 Bitness: 32 Bit\nHardware platform: x86-32 Support for developer platform only.\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK/WebSphere Application Server on 32-bit OS\n\nWindows 7 Professional x86-64 Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 Support for developer platform only.\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK/WebSphere Application Server on 64-bit OS\n * 64-bit JDK/WebSphere Application Server on 64-bit OS\n\nWindows Server 2003 R2 Standard Edition x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 Base Level Service: SP2\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK/WebSphere Application Server on 32-bit OS\n\nWindows Server 2003 R2 Standard Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 Base Level Service: SP2\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK/WebSphere Application Server on 64-bit OS\n * 64-bit JDK/WebSphere Application Server on 64-bit OS\n\nWindows Server 2003 SP2 Datacenter Edition x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #4 Windows Server 2003 SP2 Datacenter Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2003 SP2 Enterprise Edition x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #4 Windows Server 2003 SP2 Enterprise Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2003 SP2 Standard Edition x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #4 Windows Server 2003 SP2 Standard Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2008 R2 Datacenter Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2008 R2 Enterprise Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2008 R2 Standard Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2008 SP2 Datacenter Edition x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #4 Windows Server 2008 SP2 Datacenter Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2008 SP2 Enterprise Edition x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #4 Windows Server 2008 SP2 Enterprise Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2008 SP2 Standard Edition x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #4 Windows Server 2008 SP2 Standard Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Vista Enterprise x86-32 Bitness: 32 Bit\nHardware platform: x86-32 Supported for developer platform only\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK/WebSphere Application Server on 32-bit OS\n\nWindows Vista Enterprise x86-64 Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 Supported for developer platform only.\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK/WebSphere Application Server on 64-bit OS\n * 64-bit JDK/WebSphere Application Server on 64-bit OS\n\nWindows XP SP2 Professional x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 Supported for developer platform only.\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK/WebSphere Application Server on 32-bit OS\n\nWindows XP SP2 Professional x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 Supported for developer platform only.\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK/WebSphere Application Server on 64-bit OS\n * 64-bit JDK/WebSphere Application Server on 64-bit OS\n\n Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers WebSphere Application Server 7.0.0.19 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Application_Server] All Applicable Windows OS Download mandatory APAR PM52049 for WebSphere Application server 7.0.0.19 from this site -\n\n Fix Central Link for PM52049 [http://www-933.ibm.com/support/fixcentral/swg/selectFix?product=ibm/WebSphere/WebSphere+Application+Server&fixids=7.0.0.19-WS-WAS-IFPM52049&source=dbluesearch&function=fixId&parent=ibm/WebSphere]\n\n [http://www.ibm.com/support/docview.wss?uid=swg24029137]\n\n Back to top \n\nOptional Supported Software Group Product Applicable OS Notes Application Servers WebSphere Application Server Feature Pack for XML 1.0.0.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/xml/index.html] All Applicable Windows OS WebSphere Application Server V7 Feature Pack for Communications Enabled Applications 1.0.0.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/cea/] All Applicable Windows OS WebSphere Application Server V7 Feature Pack for Service Component Architecture 1.0.1.7 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/was/featurepacks/sca/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Application_Server] All Applicable Windows OS WebSphere eXtreme Scale 7.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/extremescale/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_eXtreme_Scale] All Applicable Windows OS Requires version 7.1.0.0 WebSphere Virtual Enterprise 6.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/appserv/extend/virtualenterprise/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Virtual_Enterprise] All Applicable Windows OS Requires fix pack version 6.1.1.2 Collaboration IBM Connections 3.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/IBM_Connections] All Applicable Windows OS Lotus Connections 2.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Connections] All Applicable Windows OS Lotus Connections 3.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/connections/index.html] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Connections] All Applicable Windows OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Windows OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Windows OS Lotus Quickr for Domino 8.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_Domino] All Applicable Windows OS Lotus Quickr for Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_Domino] All Applicable Windows OS Lotus Quickr for WebSphere Portal 8.1.1 Feature Packs and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_WebSphere_Portal] All Applicable Windows OS Lotus Quickr for WebSphere Portal 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/quickr/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Quickr_for_WebSphere_Portal] All Applicable Windows OS Lotus Sametime Entry 8.0 and future mod levels and fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/entry/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable Windows OS IBM Lotus Sametime Entry 8.0.2 requires hot fix BMUY-87SL83 \n\nLotus Sametime Entry 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/entry/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable Windows OS Requires hot fix BMUY-87SL83\n\nLotus Sametime Standard 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/sametime/standard/] (support) [http://www.ibm.com/software/lotus/support/sametime/support.html] All Applicable Windows OS Requires hot fix BMUY-87SL83\n\nDatabases Apache Derby 10.3 and future fix packs All Applicable Windows OS Not supported in a production environment.\n\nDB2 9 for Linux, UNIX and Windows 9.1.0.9 and future fix packs All Applicable Windows OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Enterprise Server Edition 9.7.0.1 and future fix packs (overview) [http://www.ibm.com/software/data/db2/linux-unix-windows/edition-enterprise.html] (support) [http://www.ibm.com/software/data/db2/support/db2_9/] All Applicable Windows OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\n Database parameter 'cur_commit' must be set to 'DISABLED' for database of WebSphere Portal 7\n\nDB2 for i5/OS 6.1 and future fix packs All Applicable Windows OS DB2 for i5/OS 7.1 and future fix packs All Applicable Windows OS DB2 for i5/OS V5R4 and future fix packs All Applicable Windows OS DB2 for z/OS 9.1 and future fix packs (overview) [http://www.ibm.com/software/data/db2/zos/] (support) [http://www.ibm.com/software/data/db2/support/db2zos/] All Applicable Windows OS High Availability Disaster Recovery (HADR) Feature is supported.\n\n WebSphere Portal 7.0 works with DB2 for z/OS V9.1 - PUT level 0912.\n\n The following are required:\n\n * APAR PK75093 or later\n * APAR PK92163:\n http://www-01.ibm.com/support/docview.wss?uid=swg1PK92163 [http://www-01.ibm.com/support/docview.wss?uid=swg1PK92163]\n * APAR PK68265\n\nDB2 for z/OS 10.1 and future fix packs (overview) [http://www.ibm.com/software/data/db2/zos/] (support) [http://www.ibm.com/software/data/db2/support/db2zos/] All Applicable Windows OS DB2 pureScale Feature for Enterprise Server Edition 9.8.0.3 and future fix packs All Applicable Windows OS Requires 7.0.0.1 CF007 or higher.\n\n Refer to the steps documented here: http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open]\n\nDB2 Universal Database for z/OS 8.1 and future fix packs All Applicable Windows OS WebSphere Portal 7.0 works with DB2 for z/OS V8.1 - PUT level 0912 or later service level.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Workgroup Server Edition 9.5.0.5 and future fix packs (overview) [http://www.ibm.com/software/data/db2/linux-unix-windows/edition-workgroup.html] (support) [http://www.ibm.com/software/data/db2/support/db2_9/] All Applicable Windows OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nMicrosoft SQL Server Enterprise Edition 2005 SP2 and future fix packs All Applicable Windows OS Microsoft SQL Server Enterprise Edition 2008 and future fix packs All Applicable Windows OS Microsoft SQL Server Enterprise Edition 2008 R2 All Applicable Windows OS Oracle Database 10g Enterprise Edition Release 1 10.1.0.5 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 10g Enterprise Edition Release 2 10.2.0.4 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 10g Standard Edition Release 1 10.1.0.5 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 10g Standard Edition Release 2 10.2.0.4 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.6 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.7 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 11g Enterprise Edition Release 2 11.2.0.2 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.6 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.7 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 11g Standard Edition Release 2 11.2.0.2 and future fix packs All Applicable Windows OS See Note #3 Identity Management IBM z/OS.e Security Server 1.6 and future fix packs All Applicable Windows OS IBM z/OS.e Security Server 1.7 and future fix packs All Applicable Windows OS IBM z/OS Security Server 1.6 and future fix packs All Applicable Windows OS IBM z/OS Security Server 1.7 and future fix packs All Applicable Windows OS Lotus Domino 8.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Windows OS Lotus Domino 8.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Windows OS Lotus Domino 8.0.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Windows OS Lotus Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Windows OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Windows OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Windows OS Microsoft Active Directory 2003 and future fix packs All Applicable Windows OS Microsoft Active Directory 2008 and future fix packs All Applicable Windows OS Microsoft Active Directory Application Mode (ADAM) 2003 and future fix packs All Applicable Windows OS Microsoft AD LDS(Lightweight Directory Services) Windows 2008 and future fix packs All Applicable Windows OS Novell eDirectory 8.7.3 and future fix packs All Applicable Windows OS Novell eDirectory 8.8 and future fix packs All Applicable Windows OS Sun Java System Directory Server 6.1 and future fix packs All Applicable Windows OS Service Pack 10 or later is required. Sun Java System Directory Server 6.3 and future fix packs All Applicable Windows OS Sun Java System Directory Server 7.0 and future fix packs All Applicable Windows OS Tivoli Directory Server 6.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable Windows OS Tivoli Directory Server 6.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable Windows OS Fix pack 4 or later is required. Tivoli Directory Server 6.2 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-server/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html] All Applicable Windows OS Java Technology IBM Runtime Environment, Java Technology Edition 6.0 and future mod levels and fix packs All Applicable Windows OS Requirements:\n\n * Java version included or recommended by WebSphere Application Server 7.0.0.19.\n\nSun Java SDK/JRE/JDK 6.0 Update 17 and future fix packs All Applicable Windows OS Supported Java runtime environments 1.5.x or 1.6.x (requires one) for the Web Content Management authoring portlet\n\nJDBC Drivers Apache Derby 10.3 JDBC 4.0 and future fix packs All Applicable Windows OS Derby is a non-production environment. V10.3.3.1 or later is required. DataDirect Connect for JDBC 4.0 (type 4) and future fix packs All Applicable Windows OS DB2 Driver for JDBC and SQLJ (type 2/4) 4.0 and future fix packs All Applicable Windows OS DB2 9.5 and DB2 9.7 require DB2 Driver for JDBC and SQLJ (type 2/4) 4.0 IBM Application Connectivity to DB2 for z/OS Feature Version and future fix packs All Applicable Windows OS IBM DB2 Universal JDBC Provider (XA) from DB2 z/OS (type 4) Version and future fix packs All Applicable Windows OS Requires APAR PK93123 for DB2 on z/OS V8.1 and V9.1. You can obtain the fix from DB2 on z/OS support or IBMLINK. IBM Toolbox for Java/JTOpen JDBC Driver 6.0 and future fix packs All Applicable Windows OS Check for the latest jt400.jar file at:http://sourceforge.net/projects/jt400/files/ [http://sourceforge.net/projects/jt400/files/] Microsoft SQL Server JDBC Driver 2.0 and future fix packs All Applicable Windows OS Microsoft SQL Server JDBC Driver 3.0 All Applicable Windows OS Oracle JDBC Driver (XA) 10g Any and future fix packs All Applicable Windows OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nOracle JDBC Driver (XA) 11g 11.2.0.2 and future fix packs All Applicable Windows OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nMiscellaneous IBM License Metric Tool 7.2.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/license-metric-tool/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMLicenseMetricTool.html] All Applicable Windows OS Tivoli Directory Integrator 7.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/directory-integrator/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMDirectoryIntegrator.html] All Applicable Windows OS Tivoli License Compliance Manager 2.3 Fixpack 1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/license-mgr/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliLicenseManager.html] All Applicable Windows OS Process Server WebSphere Process Server 7.0.0.3 and future fix packs (overview) [http://www.ibm.com/software/integration/wps/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Process_Server] All Applicable Windows OS Security CA SiteMinder 6.0 and future fix packs All Applicable Windows OS Tivoli Access Manager for e-business 6.0 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliAccessManagerfore-business.html] All Applicable Windows OS Tivoli Access Manager for e-business 6.1 and future fix packs (overview) [http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/] (support) [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliAccessManagerfore-business.html] All Applicable Windows OS Tools Rational Application Developer for WebSphere Software 8.0 and future fix packs (overview) [http://www.ibm.com/software/awdtools/developer/application/index.html] (support) [http://www.ibm.com/software/awdtools/developer/application/support/index.html] All Applicable Windows OS WebSphere Portlet Factory 7.0 and future fix packs (overview) [http://www.ibm.com/software/genservers/portletfactory/] (support) [http://www.ibm.com/software/genservers/portletfactory/support/] All Applicable Windows OS Virtualization IBM PR/SM any version and future fix packs All Applicable Windows OS Red Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.4 and future fix packs All Applicable Windows OS VMware ESX 4.0 and future releases, mod levels and fix packs All Applicable Windows OS VMware ESXi 4.0 and future releases, mod levels and fix packs All Applicable Windows OS Web Browsers Apple Safari 4.0 and future fix packs All Applicable Windows OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nGoogle Chrome 8 and future releases, mod levels and fix packs All Applicable Windows OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at\n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 6.0 SP2 and future fix packs All Applicable Windows OS Internet Explorer 6.0 SP2 on Windows XP SP1/SP2 and Windows 2000 SP4 and Windows 2003. Support for Microsoft Internet Explorer v6.0 is deprecated in this release and due to its limited capabilities many WebSphere Portal features do not function or render correctly, including Client-Side Aggregation (CSA), Page Builder, Mashup integration, Wikis and Blogs. Some legacy pages and themes can be successfully rendered by Microsoft Internet Explorer v6.0, but use of this Web browser is not recommended.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 7.0 and future fix packs All Applicable Windows OS Internet Explorer 7.0 is supported on all versions of Windows that are supported by WebSphere Portal.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 8.0 and future fix packs All Applicable Windows OS See Note #1 Microsoft Internet Explorer 9.0 and future fix packs All Applicable Windows OS Refer to the IE9 Support statement for more information:\n\n http://www.ibm.com/support/docview.wss?uid=swg21496054 [http://www.ibm.com/support/docview.wss?uid=swg21496054]\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n\nMozilla Firefox 3.0 and future fix packs All Applicable Windows OS See Note #1 Mozilla Firefox 3.5 and future fix packs All Applicable Windows OS See Note #1 Mozilla Firefox 3.6 and future fix packs All Applicable Windows OS See Note #1 Mozilla Firefox 4.0 and future releases, mod levels and fix packs All Applicable Windows OS See Note #1 Opera 10.0 and future fix packs All Applicable Windows OS See Note #1 WebDAV Client davfs2 1.4.6 All Applicable Windows OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nJSCAPE AnyClient 2.2 All Applicable Windows OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nSRT WebDrive 9.1 All Applicable Windows OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27023805]\n\nWeb Servers Apache HTTP Server 2.0.59 and future fix packs All Applicable Windows OS Apache HTTP Server 2.2 and future fix packs All Applicable Windows OS IBM HTTP Server 6.1 and future fix packs (overview) [http://www.ibm.com/software/webservers/httpservers/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_HTTP_Server] All Applicable Windows OS IBM HTTP Server 7.0 and future fix packs (overview) [http://www.ibm.com/software/webservers/httpservers/] (support) [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_HTTP_Server] All Applicable Windows OS IBM HTTP Server for i5/OS Any and future fix packs All Applicable Windows OS IBM HTTP Server for i5/OS versions V5R4, V6R1 and V7R1\n\nIBM HTTP Server for z/OS Any and future fix packs All Applicable Windows OS Lotus Domino 8.0 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Windows OS Lotus Domino 8.0.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Windows OS Lotus Domino 8.0.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Windows OS Lotus Domino 8.5 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Windows OS Lotus Domino 8.5.1 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Windows OS Lotus Domino 8.5.2 and future fix packs (overview) [http://www.ibm.com/software/lotus/products/domino/] (support) [http://www.ibm.com/software/lotus/support/domino/support.html] All Applicable Windows OS Microsoft Internet Information Services 6.0 and future fix packs All Applicable Windows OS Microsoft Internet Information Services 7.0 and future fix packs All Applicable Windows OS Microsoft Internet Information Services 7.5 and future fix packs All Applicable Windows OS Supported as Web server plugins when hosted on the Windows Server 2008 R2 edition. Sun Java System Web Server 6.1 SP10 and future fix packs All Applicable Windows OS Sun Java System Web Server 6.1 Service pack 10 or later is required.\n\nSun Java System Web Server 7.0 Update 8 and future fix packs All Applicable Windows OS Sun Java System Web Server 7.0 Update 8 or later is required.\n\n Back to top \n\n\n\n\nNOTES\n * Note #1: For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n \n http://www-01.ibm.com/support/docview.wss?uid=swg27016293 [http://www-01.ibm.com/support/docview.wss?uid=swg27016293]\n \n \n * Note #2: Development Platform Only\n WebSphere Application Server requirements depending on operating system bit:\n \n * 32-bit JDK/WebSphere Application Server on 32-bit OS\n \n \n * Note #3: Includes Support for Oracle RAC.\n \n \n * Note #4: WebSphere Application Server requirements depending on operating system bit:\n \n * 32-bit JDK/WebSphere Application Server on 32-bit OS\n \n \n * Note #5: WebSphere Application Server requirements depending on operating system bit:\n \n * 32-bit JDK/WebSphere Application Server on 32-bit OS\n \n \n * Note #6: WebSphere Application Server requirements depending on operating system bit:\n \n * 32-bit JDK/WebSphere Application Server on 64-bit OS\n * 64-bit JDK/WebSphere Application Server on 64-bit OS\n \n \n * Note #7: WebSphere Application Server requirements depending on operating system bit:\n \n * 32-bit JDK/WebSphere Application Server on 64-bit OS\n * 64-bit JDK/WebSphere Application Server on 64-bit OS\n \n \n * Note #8: WebSphere Application Server requirements depending on operating system bit:\n \n * 64-bit JDK/WebSphere Application Server on 64-bit OS"
}
] |
TRAIN_Q430 | DASH 3.1.2.1 to 3.1.3.0 taking long time
DASH 3.1.2.1 to 3.1.3.0 taking long time. How to fix this? | The upgrade must be initiated by using the attached script, which gives the non-root user (who originally installed this Jazz for Service Management instance) the correct permissions for the upgrade process. | false | [
{
"filename": "swg21985946.txt",
"text": "Title: IBM Upgrading to Jazz for Service Management Version 1.1.3.0 using Installation Manager results in a permission denied error - United States\n\nText:\njazzsm1130relnotes TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When upgrading Jazz for Service Management to Version 1.1.3.0 using Installation Manager, the installation fails with the following error:\n\nCannot run program \"/space/IBM/JazzSM/ui/bin/wrapper.sh\" (in directory \"/space/IBM/JazzSM/ui/bin\"): error=13, Permission denied [/space/IBM/JazzSM/install/tip/tipWrapp\nerInstall.xml:215] \n\nCAUSE\nDuring the upgrade process the non-root user does not have the correct permissions to run the shell script. This is due to the following:\n1. Jazz for Service Management is installed as a non-root user\n2. Installation Manager is installed in user mode through root user\n\n\nRESOLVING THE PROBLEM\nThe upgrade must be initiated by using the attached script, which gives the non-root user (who originally installed this Jazz for Service Management instance) the correct permissions for the upgrade process. \n\n\nThe script takes two mandatory arguments and one optional argument.\n\nUsage: ./JazzSMgrpModeUpgrade.sh \"IM_Install_Location\" \n\"JazzSM_Install_Location [http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/ref/psc_r_pathnames.html]\"\"[Response_file_with_absolute_Path]\"\n\nFor example (showing default installation paths): ./JazzSMgrpModeUpgrade.sh \"/home/root/IBM/InstallManager/\" \"/opt/IBM/JazzSM/\" \"/opt/Download/dash_upgrade_rsp.xml\"\n\n\nFor IM GUI mode installation, provide the 2 mandatory arguments; IM_Install_Location and JazzSM_Install_Location. \nThis argument combination invokes Installation Manager in GUI mode and lead you through the rest of the upgrade process.\n\nFor IM Silent installation, provide all 3 arguments; IM_Install_Location , JazzSM_Install_Location, and Response_file_with_absolute_Path.\nThis argument combination invokes Installation Manager in silent mode to upgrade JazzSM.\n\nJazzSMgrpModeUpgrade.sh [/support/docview.wss?uid=swg21985946&aid=2]JazzSMgrpModeUpgrade.sh [/support/docview.wss?uid=swg21985946&aid=1]"
}
] |
TRAIN_Q431 | Install path under "Program Files"
My path for the OS agent is e:\Program Files\IBM. Is there any issues or underlying problems if I install under "Program Files"? Just want to make sure no issues with a "space" in the install path. | Getting the below error when you try to install ITM on Window OS
"D:\Program Files\IBM\ITM" includes blanks. Due to your system settings the installation path cannot include blanks, please specify location with no spaces. | false | [
{
"filename": "swg21961222.txt",
"text": "Title: IBM Trouble installing ITM on Windows OS - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Getting the below error when you try to install ITM on Window OS \n\n\"D:\\Program Files\\IBM\\ITM\" includes blanks. Due to your system settings the installation path cannot include blanks, please specify location with no spaces. \n\nSYMPTOM\nWhen you try to install ITM on \" C:\\Program Files\\IBM\\ITM\" it woks fine but when we try to install it on \"D:\\Program Files\\IBM\\ITM\" we get the below error:\n\n\n\"D:\\Program Files\\IBM\\ITM\" includes blanks. Due to your system settings the installation path cannot include blanks, please specify location with no spaces.\n\nIf you take out the spaces and use D:\\ProgramFiles\\IBM\\ITM, the install will continue. \n\n\nRESOLVING THE PROBLEM\n \n\nCouple of ways to fix this... \n\n \n\n1. Remove the space in the directory path and install the ITM on a directory without spaces. \n\nExample : D:\\IBM\\ITM \n\n \n\n2. Check the NTFS 8.3 name creation and enable the 8.3 naming creation to install the ITM on a directory path with spaces.\n\ncheck the value on the below registry location \n\n\nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\FileSystem\\NtfsDisable8dot3NameCreation\n\nIn case NtfsDisable8dot3NameCreation is set to (2), this means the following: NTFS sets the 8.3 naming convention creation on a per volume basis.\n\nYou can check the 8.3 name creation using this command for the volumes that are impacted.\n\nFor example, if the %TEMP% folder is located on c:\\, but you are installing on d:\\, then you should run these commands: \n\n\nfsutil 8dot3name query c:\nfsutil 8dot3name query d:\n\nYou will get an output like this:\nThe volume state is: 0 (8dot3 name creation is enabled).\nThe registry state is: 2 (Per volume setting - the default). \n\n\nValue and Meaning\n\n0 NTFS creates short file names. This setting enables applications that cannot process long file names and computers that use different code pages to find the files.\n1 NTFS does not create short file names. Although this setting increases file performance, applications that cannot process long file names, and computers that use different code pages, might not be able to find the files.\n2 NTFS sets the 8.3 naming convention creation on a per volume basis.\n3 NTFS disables 8dot3 name creation on all volumes except the system volume. \n\n \n\nmore detail... \n\n\nhttps://technet.microsoft.com/en-us/library/cc959352.aspx [https://technet.microsoft.com/en-us/library/cc959352.aspx]"
}
] |
TRAIN_Q432 | Maintenance Manager login with LDAP
I"m trying to set up NENU to run on a 9.0.1 application. I've created the application and configured the ruleset but it will not connect to the application.
In the Knowledge base it says that if using LDAP to leave the UserID, Password and Station ID blank.
I have tried this in multiple configuration but it simply will not connect and says the Userid and Password are invalid.
Anyone have expedite on how to connect using LDAP?
Here is the error message when using a userid
Running SetupOpenApplication Action...
16:07:24.569 (47) t:1C90 p:53A7028 !!! ERROR !!!: Cannot login to application:'APPLICATIONAME', server:'tms', admin:'tmadmin', engine:'tmengine', user name:'ntprod\svc_datacap_tst', station:'btcedcswd212v'. Error message from aTM:'Login name and/or password invalid.
Please try again.'
16:07:24.569 (0) t:1C90 p:53A7028 Running SetupDisconnectAll Action...
If I remove the username, password and station, the error message is the same except the userID has xxx.com\svc_datacap_tst as the userid which is incorrect. | - | true | [] |
TRAIN_Q433 | Optim license
We bought Optim 11.3, Test data management and data masking module....
I wonder how to get a Optim license?
| See the attached document for a full explanation of which license keys might be required, how to request them if they are, and how to self-entitle your Optim product if they are not.
Optim license key technote.doc [/support/docview.wss?uid=swg21973794&aid=2]Optim license key technote.doc | false | [
{
"filename": "swg21973794.txt",
"text": "Title: IBM Optim, Optim Connect, ODM, and Optim zOS licensing - United States\n\nText:\nlicense key; password; fix pack; enable; license file; Open Data Manager; ODM; entitle TECHNOTE (FAQ)\n\nQUESTION\n Are license keys still required for Optim Distributed, Optim Connect, ODM, and Optim zOS products? \n\nANSWER\nSee the attached document for a full explanation of which license keys might be required, how to request them if they are, and how to self-entitle your Optim product if they are not.\n\nOptim license key technote.doc [/support/docview.wss?uid=swg21973794&aid=2]Optim license key technote.doc [/support/docview.wss?uid=swg21973794&aid=1]"
}
] |
TRAIN_Q434 | DataPower upgrade "extracting firmware firmware parsing error" "Error while processing Action ... "
I am trying to upgrade my DataPower Gateway Appliance and am receiving the message(s) similar to:
"extracting firmware firmware parsing error"
OR
"Error while processing Action ... Validate boot image failed "Validation Failed"
How can I resolve this? | - | true | [] |
TRAIN_Q435 | Why does WebSphere Portal take over 30 minutes to start up and show hung thread message on thread server.startup?
Why does WebSphere Portal take over 30 minutes to start up and show hung thread message on thread server.startup?
Example message from SystemOut.log:
[3/3/15 5:58:47:293 EST] 00000019 ThreadMonitor W WSVR0605W: Thread "server.startup : 1" (00000015) has been active for 692705 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung. at java.io.UnixFileSystem.getBooleanAttributes0(Native Method) at
....
org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.DirectoryArchiveLoadStrategyImpl.addDirectory(DirectoryArchiveLoadStrategyImpl.java:31) ..... | - | true | [] |
TRAIN_Q436 | Can you delete temporary data that is generated by IBM Business Process Manager?
In the OS temporary directories, there are many files generated for BPM. These files are created on the following operations:
create TWX snapshot for export
access a managed asset during process execution
create offline install package
The following temporary directories are used for storing temp files:Operating system temporary directory:/tmp (Linux)c:\windows\temp (Windows)
How can these files be cleaned up? | - | true | [] |
TRAIN_Q437 | Is WAS TE v7.0.0.41 available for RAD?
Is WebSphere Application Server 7.0 Test Environment Extension (WTE) v 7.0.0.41 available for Rational Application Developer for WebSphere Software (RAD) ? | This download includes the following update to the WebSphere Application Server v7.0 Test Environment extension included with Rational Software Delivery Platform products:
* IBM WebSphere Application Server Version 7 Fix Pack 41 also known as version 7.0.0.41. | false | [
{
"filename": "swg24042177.txt",
"text": "Title: IBM WebSphere Application Server 7.0 Test Environment Extension 7.0.0.41 - United States\n\nText:\nifix; interim fix; i-fix; fix; patch; update; fixes; upgrade DOWNLOADABLE FILES\n\nABSTRACT\n IBM WebSphere Application Server 7 Fix Pack 41 (7.0.0.41) is available as an installed test environment extension \n\nDOWNLOAD DESCRIPTION\nThis download includes the following update to the WebSphere Application Server v7.0 Test Environment extension included with Rational Software Delivery Platform products:\n\n\n * IBM WebSphere Application Server Version 7 Fix Pack 41 also known as version 7.0.0.41. For more information, see the WebSphere Application Server readme [http://www-01.ibm.com/support/docview.wss?uid=swg27004980#ver70]. \n * WebSphere Application Server Feature Pack for Web 2.0 1.0.1.1 \n * WebSphere Application Server Feature Pack for Mobile 1.1.0.1 (Note: This feature pack is available only when installing with version 8.0 or newer.) \n * WebSphere Application Server Feature Pack for Communications Enabled Applications 1.0.0.13 \n * WebSphere Application Server Feature Pack for Service Component Architecture 1.0.1.17 \n * WebSphere Application Server Feature Pack for XML 1.0.0.15 \n * WebSphere Application Server Feature Pack for OSGi Applications and Java Persistence API (JPA) 2.0 v1.0.0.9 (Note: This feature pack is available only when installing with version 8.0 or newer.) \n * WebSphere Application Server Feature Pack for Modern Batch 1.0.0.5 (Note: This feature pack is available only when installing with version 8.0 or newer.)\n\n\nFor more information on feature packs for WebSphere Application Server, see http://www.ibm.com/support/docview.wss?uid=swg27008534&wv=1#was70 [http://www.ibm.com/support/docview.wss?uid=swg27008534&wv=1#was70]. PREREQUISITES\nYou must have the WebSphere Application Server 7.0 Test Environment extension installed.\n\nYou need up to 5.18 GB of disk space to install the fix pack. To download and extract the compressed installation files, you need an additional 6 GB of disk space.\n\nINSTALLATION INSTRUCTIONS\nImportant: By default, you do not need to download the compressed files that contain the update; the update is downloaded and installed by IBM Installation Manager directly from the IBM update repository.\n\nFor instructions on installing this update using Installation Manager, see the topic Updating Installed Product Packages in the information center for your product and version: \n\n * Rational Application Developer for WebSphere Software, version 8.5.x [http://www.ibm.com/support/knowledgecenter/SSRTLW_8.5.5/com.ibm.rad.install.doc/topics/t_update.html] \n * Rational Application Developer for WebSphere Software, version 9.0.x [http://www.ibm.com/support/knowledgecenter/SSRTLW_9.0.0/com.ibm.rad.install.doc/topics/t_update.html] \n * Rational Application Developer for WebSphere Software, version 9.1.x [http://www.ibm.com/support/knowledgecenter/SSRTLW_9.1.0/com.ibm.rad.install.doc/topics/t_update.html] \n\n\nTo download and install the update from the compressed files, complete the following steps: \n 1. Download the update files from Fix Central by following the link listed in the download table below\n 2. Extract the compressed files in an appropriate directory. For example, choose to extract to C:\\temp\\update\n 3. Add the update's repository location in IBM Installation Manager: 1. Start IBM Installation Manager.\n 2. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.\n 3. On the Repositories page, click Add Repository.\n 4. In the Add repository window, browse to or enter the file path to the diskTag.inf file, which is located in the disk1 sub-directory in the directory where you extracted the compressed files and then click OK. For example, enter C:\\temp\\updates\\disk1\\diskTag.inf.\n 5. Click OK to close the Preference page.\n \n \n 4. Install the update as described in the the topic \"Updating Installed Product Packages\" in the information center for your product and version\n\nDOWNLOAD PACKAGE\nYou can download the fix pack from Fix Central using either Download Director, HTTP or FTP. \n\n 1. Click the link in the table that follows to access Fix Central. \n 2. On the Select Fixes page, select Fix pack : 9.1.1.2-Rational-RAD-groupfixpack (IBM Rational Application Developer for WebSphere Software Version 9.5.0.2) \n 3. Expand section Show contained fixes. \n 4. From the list of contained fixed, select one of the following options:\n\n * (For 64-bit) 7.0.0.41-Rational-WAS70_64-fixzippack (WebSphere Application Server 70 64bit Extension version 7.0.0.41 update pack) \n * (For 32-bit) 7.0.0.41-Rational-WAS70-fixzippack (WebSphere Application Server 70 Extension version 7.0.0.41 update pack \n 1. Click Continue and follow the prompts to download the update.\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 7.0.0.41-Rational-WAS70-fixzippack 6 May 2016 English 1 FC [https://ibm.biz/Bd48Av] [ ] \nTECHNICAL SUPPORT\n \n\nTAB NAVIGATION\n * General Support Information- selected tab,\n * Support Resources [http://www.ibm.com/support/docview.wss?uid=swg27020747]- selected tab,\n\n\n\n\nIBM Rational Software Support Communities \n\n * Visit the IBM Support Portal [http://www.ibm.com/support/entry/portal/Overview/Software/Rational/product] to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.\n \n \n * Visit developerWorks [http://www.ibm.com/developerworks/rational/] to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community [http://www.ibm.com/developerworks/rfe/].\n \n \n * Visit the Jazz Community [http://jazz.net/] if you use a Rational product created using the Jazz platform to interact directly with the Jazz development team and other community members, download product trials and betas and track developement progress. \n\n\n\n\nHELPFUL HINTS FOR OBTAINING TECHNICAL ASSISTANCE:\nBefore you contact IBM Rational Software Support, gather the background information that you need to describe the problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions: \n\n * What software versions were you running when the problem occurred? \n * Do you have logs, traces, or messages that are related to the problem? \n * Can you reproduce the problem? If so, what steps do you take to reproduce it? \n * Is there a workaround for the problem? If so, be prepared to describe the workaround. \n\nIf you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support [http://www.ibm.com/software/support/exchangeinfo.html]. \n\n \n\nFollow IBM Rational Client Support on Twitter [http://twitter.com/rationalsupport] | Facebook [http://facebook.com/rationalsupport] | YouTube [http://www.youtube.com/ibmrationalsupport] | devWorks Blog [https://www.ibm.com/developerworks/mydeveloperworks/blogs/nfrsblog/?lang=en]\n\n\n\n\n Back to top"
}
] |
TRAIN_Q438 | During action in Rhapsody Statechart
Hi Folks,
I am developing a statechart in Rhapsody and I have a question.
I could not see in Rhapsody where I can insert an action that must occur during the whole time the state is active.
I can only see : Actions on Entry and Actions on Exit.
Where is During Action? | Some of UML features such as deferred event and do-activity are not natively supported today. | false | [
{
"filename": "swg27040251.txt",
"text": "Title: IBM Differences between Rational Rhapsody 8.0 Statecharts and UML 2.4.1 Behavior State Machine - United States\n\nText:\nRestriction; Restrictions; Limitation; Limitations; drawing; graphical; graph; difference; diferences; gap; deffer; feature; features; concept; concepts; error; errors WHITE PAPER\n\nABSTRACT\n This is a white paper that explains the differences between IBM Rational Rhapsody 8.0.x Statecharts and UML 2.4.1 Behavior State Machine. \n\nCONTENT\n \n\nAuthors: Shinji Kanai, Moria Abadi\n\n\nOMG UML and IBM Rational Rhapsody have been evolving in parallel, and some differences were created and expanded over time. Not all graphical notations that are defined in UML specification are supported by Rhapsody. There are certain patterns of transitions you cannot draw due to restrictions imposed deliberately, but not necessarily limited by UML specification. Some of UML features such as deferred event and do-activity are not natively supported today. This document covers such gaps that are found between UML specification and Rhapsody implementation, aiming to help you design statechart more effectively and enable easier interchange of statecharts among UML-based modeling tools.\n\n\n\n\nDisclaimer This documentation is created based on differences that are found between Rhapsody 8.0.x Statechart and OMG UML 2.4.1 Superstructure Specification (UML spec). The content is believed to be accurate at the time of publication. Use this documentation at your own risk as it might contain some incompleteness and imprecision.\n\n\n\nTable: Graphical Notations and Naming comparison \n\nUML2.4.1 Concept: Behavior state machine element or capability as it is named in OMG UML 2.4.1 Superstructure Spec. Section in spec: The section describing the element in UML spec. In Rhapsody: The corresponding name and graphical notation of UML concept that is used in Rhapsody. Note: Additional comments to help understand the specific concept better. \n[/support/docview.wss?uid=swg27040251&aid=1] UML2.4.1 Concept Section in spec In Rhapsody Note 1. Entry Point\n[/support/docview.wss?uid=swg27040251&aid=2] 15.3.1 EnterExitPoint\n[/support/docview.wss?uid=swg27040251&aid=3] (*) Visualization using a rectangular symbol is not supported\n(*) Not supported for composite states (See NO. 36). 2. Exit Point\n[/support/docview.wss?uid=swg27040251&aid=4] 15.3.1 EnterExitPoint\n[/support/docview.wss?uid=swg27040251&aid=5] (*) Visualization using a rectangular symbol is not supported\n(*) Not supported for composite states, only for submachine states 3. Final State\n[/support/docview.wss?uid=swg27040251&aid=6] 15.3.2 Termination State\n[/support/docview.wss?uid=swg27040251&aid=7] [/support/docview.wss?uid=swg27040251&aid=1] 4. Initial Pseudostate\n[/support/docview.wss?uid=swg27040251&aid=8] 15.3.8 Default Connector\n[/support/docview.wss?uid=swg27040251&aid=9] [/support/docview.wss?uid=swg27040251&aid=1] 5. Deep History Pseudostate\n[/support/docview.wss?uid=swg27040251&aid=10] 15.3.8 History Connector\n\n[/support/docview.wss?uid=swg27040251&aid=11] [/support/docview.wss?uid=swg27040251&aid=1] 6. Shallow History Pseudostate\n[/support/docview.wss?uid=swg27040251&aid=12] 15.3.8 Shallow History Connector\n[/support/docview.wss?uid=swg27040251&aid=13] (*) Code Generation is supported in v8.0.6. See technote 1668548 [http://www.ibm.com/support/docview.wss?uid=swg21668548] for more information. 7. Join Pseudostate\n[/support/docview.wss?uid=swg27040251&aid=14] 15.3.8 Join Sync Bar\n[/support/docview.wss?uid=swg27040251&aid=15] [/support/docview.wss?uid=swg27040251&aid=1] 8. Fork Pseudostate\n[/support/docview.wss?uid=swg27040251&aid=16] 15.3.8 Fork Sync Bar\n[/support/docview.wss?uid=swg27040251&aid=17] [/support/docview.wss?uid=swg27040251&aid=1] 9. Junction Pseudostate\n[/support/docview.wss?uid=swg27040251&aid=18] 15.3.8 Junction Connector\n[/support/docview.wss?uid=swg27040251&aid=19] (*) Used only for merge. Only one outgoing transition is permitted 10. Static Conditional Branch\n[/support/docview.wss?uid=swg27040251&aid=20] 15.3.8 Condition Connector\n[/support/docview.wss?uid=swg27040251&aid=21] (*) Only one incoming transition is allowed.\n(*) Realized by way of the condition connector. 11. Terminate Pseudostate\n[/support/docview.wss?uid=swg27040251&aid=22] 15.3.8 termination Connector\n[/support/docview.wss?uid=swg27040251&aid=23] [/support/docview.wss?uid=swg27040251&aid=1] 12. State List\n[/support/docview.wss?uid=swg27040251&aid=24] 15.3.8 [/support/docview.wss?uid=swg27040251&aid=25] (*) This is an additional representation for transition from the junction having a history as target. the regular representation can be used instead. 13. Region\n[/support/docview.wss?uid=swg27040251&aid=26] 15.3.10 Region\n[/support/docview.wss?uid=swg27040251&aid=27] [/support/docview.wss?uid=swg27040251&aid=1] 14. Simple State\n[/support/docview.wss?uid=swg27040251&aid=28] 15.3.11 Simple State\n[/support/docview.wss?uid=swg27040251&aid=29] [/support/docview.wss?uid=swg27040251&aid=1] 15. Composite State\n[/support/docview.wss?uid=swg27040251&aid=30] 15.3.11 Composite State\n[/support/docview.wss?uid=swg27040251&aid=31] [/support/docview.wss?uid=swg27040251&aid=1] 16. Submachine State\n[/support/docview.wss?uid=swg27040251&aid=32] 15.3.11 Sub-statechart\n[/support/docview.wss?uid=swg27040251&aid=33] [/support/docview.wss?uid=swg27040251&aid=1] 17. Entry Behavior\n[/support/docview.wss?uid=swg27040251&aid=34] 15.3.11 Action on Entry\n[/support/docview.wss?uid=swg27040251&aid=35] [/support/docview.wss?uid=swg27040251&aid=1] 18. Exit behavior\n[/support/docview.wss?uid=swg27040251&aid=36] 15.3.11 Action on Exit\n[/support/docview.wss?uid=swg27040251&aid=37] [/support/docview.wss?uid=swg27040251&aid=1] 19. Behavior in state (do-activity)\n[/support/docview.wss?uid=swg27040251&aid=38] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=39] (*) Can be implemented using entry and exit actions. See appendix (*2) for additional information. 20. Deferred events\n[/support/docview.wss?uid=swg27040251&aid=40] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=41] (*) Can be modeled by customizing the framework. See appendix (*3) for additional information. 21. State Redefinition 15.3.11 State Redefinition (*) Class inheritance causes inheritance of statecharts. the inherited statechart can redefine its inherited states. 22. State Machine extension 15.3.12 State machine extension (*) through class inheritance 23. Time event\n[/support/docview.wss?uid=swg27040251&aid=42] 15.3.13 Time event\n[/support/docview.wss?uid=swg27040251&aid=43] (*) First option tm(<expression>), where<expression> is the number of time units. Second option Accept time event. 24. Transition 15.3.14 Transition (*) A transition cannot be associated with more than one trigger. Separate transitions for each trigger need to be used.\n(*) See appendix (*4) for the list of known transaction patterns that are forbidden by Rhapsody. 25. Internal transition\n[/support/docview.wss?uid=swg27040251&aid=44] 15.3.14 Reaction in state\n[/support/docview.wss?uid=swg27040251&aid=45] [/support/docview.wss?uid=swg27040251&aid=1] 26. Completion transition 15.3.14 Null transition [/support/docview.wss?uid=swg27040251&aid=1] 27. Completion event 15.3.14 Null event [/support/docview.wss?uid=swg27040251&aid=1] 28. Transition redefinition 15.3.14 Transition redefinition (*) Class inheritance causes inheritance of statecharts. the inherited statechart can redefine its transitions, except the source state and the trigger. 29. Signal receipt\n[/support/docview.wss?uid=swg27040251&aid=46] 15.3.14 Accept Event Action\n[/support/docview.wss?uid=swg27040251&aid=47] [/support/docview.wss?uid=swg27040251&aid=1] 30. Signal sending\n[/support/docview.wss?uid=swg27040251&aid=48] 15.3.14 Send Action\n[/support/docview.wss?uid=swg27040251&aid=49] [/support/docview.wss?uid=swg27040251&aid=1] 31. Action sequence notation\n[/support/docview.wss?uid=swg27040251&aid=50] 15.3.14 [/support/docview.wss?uid=swg27040251&aid=51] [/support/docview.wss?uid=swg27040251&aid=1] 32. Local transition\n[/support/docview.wss?uid=swg27040251&aid=52] 15.3.15 [/support/docview.wss?uid=swg27040251&aid=53] [/support/docview.wss?uid=swg27040251&aid=1] 33. Choice Pseudostate/Dynamic Conditional Branch\n[/support/docview.wss?uid=swg27040251&aid=54] 15.3.8 [/support/docview.wss?uid=swg27040251&aid=55] (*) Can be simulated for example by using an additional state with guarded outgoing null transitions. See attachment (*1) in appendix. 34. Final Notation\n[/support/docview.wss?uid=swg27040251&aid=56] 15.3.8 [/support/docview.wss?uid=swg27040251&aid=57] (*) {final} means that the state cannot be redefined (such as, extended). 35. Entry/Exit Point as part of submachine state graph\n[/support/docview.wss?uid=swg27040251&aid=58] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=59] [/support/docview.wss?uid=swg27040251&aid=1] 36. Entry/Exit Point on composite state\n[/support/docview.wss?uid=swg27040251&aid=60] 15.3.8 [/support/docview.wss?uid=swg27040251&aid=61] [/support/docview.wss?uid=swg27040251&aid=1] 37. \"Bracket\" Entry/Exit Point notation \n[/support/docview.wss?uid=swg27040251&aid=62] 15.3.1 [/support/docview.wss?uid=swg27040251&aid=63] [/support/docview.wss?uid=swg27040251&aid=1] 38. Referenced/Reused submachine state\n[/support/docview.wss?uid=swg27040251&aid=64] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=65] (*) Creation of submachine is supported, but cannot be reused/referenced elsewhere. 39. Multiple triggers for a transition\n[/support/docview.wss?uid=swg27040251&aid=66] 15.3.14 [/support/docview.wss?uid=swg27040251&aid=67] [/support/docview.wss?uid=swg27040251&aid=1] 40. Extended Notation\n[/support/docview.wss?uid=swg27040251&aid=68] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=69] (*) Similar effect is achievable but need to extend a whole class containing a state machine using generalization. \n\nAppendix: \n\n\nDisclaimer All source code or binaries attached to this document are referred to here as \"the Program\". IBM is not providing program services of any kind for the Program. IBM is providing the Program on an \"AS IS\" basis without warranty of any kind. IBM WILL NOT BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM, OR ITS RESELLER, HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.\n\n\n#tbc \n\n#tbc \n(*1) Dynamic Conditional Branch \n\nDynamicBranch74orHigher.zip [/support/docview.wss?uid=swg27040251&aid=71]DynamicBranch74orHigher.zip [/support/docview.wss?uid=swg27040251&aid=70] \n\n#tbc \n(*2) \nthere is a risk that is involved to support an execution of an action that is being performed while the owning object is in a certain state. For example, there is a state \"WaitForInput\" with Do Action reading an input from the console in the background. Now an event comes to trigger a transition - a need arose to interrupt the operation of reading the input - but there is no generic way to do such things for all operations unless the action is being performed in a different thread and kill this thread. this solution seems risky for embedded systems and considered inefficient. \n\n#tbc \n(*3) \nRhapsody does not support deferred events, but there is an easy way to catch an event, which is not consumed, and process it according to your need. OMReactive class contains handleNotConsumed() virtual function, which can be overridden in your reactive class. This function is always called when event is not consumed. \n\n\n(*4)Transactional Restrictions - List of known transaction patterns that are forbidden by Rhapsody \n\n\n\nMultiple outgoing transitions from Exit Point [/support/docview.wss?uid=swg27040251&aid=72] Transition to Condition Connector from Entry/Exit Point having multiple incoming transitions [/support/docview.wss?uid=swg27040251&aid=73] [/support/docview.wss?uid=swg27040251&aid=73]\n[/support/docview.wss?uid=swg27040251&aid=74] [/support/docview.wss?uid=swg27040251&aid=74] Direct transition from Junction to Condition Connector [/support/docview.wss?uid=swg27040251&aid=75] Indirect transition from Junction to Condition Connector by way of Entry/Exit Point [/support/docview.wss?uid=swg27040251&aid=76] Direct transition from Join Bar to Junction [/support/docview.wss?uid=swg27040251&aid=77] Direct transition from Junction to Fork Bar [/support/docview.wss?uid=swg27040251&aid=78] Multiple incoming transition to Condition Connector [/support/docview.wss?uid=swg27040251&aid=79] Set a trigger on a transition that is originated from Exit Point [/support/docview.wss?uid=swg27040251&aid=80] \nRELATED INFORMATION\n UML 2.4.1 Superstructure [http://www.omg.org/spec/UML/2.4.1/Superstructure/PDF/]\nEnhancement for Do Activity [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=8817]\nEnhancement for Dynamic Condition Connector [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=7832]\nEnhancement for Shallow History Connector [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=5916]\nEnhancement Deferred Event [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=12691]"
}
] |
TRAIN_Q439 | Stored Procedure in WTX
Hi All,
Can anyone please share the example/steps/document link on how to call Stored Procedure in Input Card of a Map? The Stored Procedure will return multiple rows and columns and we need to map those rows in Output as well. Please enlighten if someone has worked on this? | SYS_REFCURSOR is not a valid datatype as a return from an Oracle stored procedure call using the WTX / ITX Oracle adapter. | false | [
{
"filename": "swg21982008.txt",
"text": "Title: IBM Transformation Extender Oracle adapter does not support SYS_REFCURSOR return type in an Oracle stored procedure / function - United States\n\nText:\nOracle Adapter Unsupported datatype SYS_REFCURSOR TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When using the IBM WebSphere Transformation Extender (WTX) / IBM Transformation Extender (ITX) Oracle adapter to call a stored procedure / function with a REF_SYSCURSOR return type, a failure of \"Unsupported datatype returned is being treated as text\" occurs. \n\nSYMPTOM\nThe Oracle database adapter log (.dbl) reports the following error:\n\nUnsupported datatype returned is being treated as text.\n\n\nCAUSE\nSYS_REFCURSOR is not a valid datatype as a return from an Oracle stored procedure call using the WTX / ITX Oracle adapter.\n\nENVIRONMENT\nIBM WebSphere TX / IBM TX Oracle adapter on any valid execution platform\n\nDIAGNOSING THE PROBLEM\nLASTERRORMSG() reports 'Failed to execute the SQL statement' and the database adapter log reports 'Unsupported datatype returned is being treated as text.'\n\nRESOLVING THE PROBLEM\nRedesign the Stored Procedure to NOT return a SYS_REFCURSOR datatype."
}
] |
TRAIN_Q440 | SCM check analyses showing as not reported in the SCA user interface
SCM check analyses showing as <not reported> the SCA user interface.
Check analyses in the SCA interface are showing as in the SCA user interface where at one point they were activated and returning data. Now they are not activated and not returning data.
How do I solve this issue? | To resolve the issue, have an active operator reactivate the check analyses and then run a new import in SCA. As a best practice, it is recommended that you have an operator account dedicated to activating the SCM check analyses in your deployment. This account should never be deleted. | false | [
{
"filename": "swg21983904.txt",
"text": "Title: IBM SCM check analyses are showing as <not activated> the SCA user interface - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The reason why your check analyses are no longer showing activated and returning data in the SCA user interface. \n\nSYMPTOM\nCheck analyses in the SCA interface are showing as <not activated> in the SCA user interface where at one point they were activated and returning data. Now they are not activated and not returning data.\n\n\nCAUSE\nThe operator who activated the analysis has been deleted. The audit trail cleaner tool was run and it removed the operator and de-activated the analysis.\n\nRESOLVING THE PROBLEM\nTo resolve the issue, have an active operator reactivate the check analyses and then run a new import in SCA. As a best practice, it is recommended that you have an operator account dedicated to activating the SCM check analyses in your deployment. This account should never be deleted.\n\n\n\nCross reference information Segment Product Component Platform Version Edition Security IBM BigFix Compliance"
}
] |
TRAIN_Q441 | How to serve static images from our HTTP Server instead of WebSphere 8.5 application?
How to serve static images from our HTTP Server instead of WebSphere 8.5 application? | If you want to serve any static files (JPG, GIF, CSS, JS, etc) from your web application in WAS, you must use fileServingEnabled="true" in the ibm-web-ext.xmi file. That will cause the plug-in to use a wildcard entry for the context-root of your web application. | false | [
{
"filename": "swg21508890.txt",
"text": "Title: IBM How to serve static files from both IBM HTTP Server and an application in WebSphere Application Server - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How can I configure IBM HTTP Server (IHS), and the IBM web server Plug-in, and my web application running in WebSphere Application Server (WAS), to serve some of my static files (JPG, GIF, CSS, JS, etc) from the IHS web server, but serve other static files from my web app running in WAS? \n\nCAUSE\nThe \"fileServingEnabled\" property in the ibm-web-ext.xmi file in the web application, is like an ON / OFF switch.\nA setting of fileServingEnabled=\"true\" means that ALL static files will be served from the web application in WAS only. In this case, the plug-in config will use a wildcard with the application context-root like \"/myapp/*\". That way every URL starting with /myapp/* will be routed to the application in WAS.\n\nOn the other hand, fileServingEnabled=\"false\" means NO static files will be served from the application in WAS. In this case, a wildcard will NOT be used in the plugin-cfg.xml file. Instead, there will be several URI entries matching the URL-Patterns from <servlet-mappings> in the web.xml, like \"/myapp/servlet1\" and \"/myapp/index.jsp\". Requests for dynamic content matching the URI entries in the Plug-in config, will be routed to the application in WAS. But everything else (static content) will be handled by the IHS web server itself.\n\n\nANSWER\nIf you want to serve any static files (JPG, GIF, CSS, JS, etc) from your web application in WAS, you must use fileServingEnabled=\"true\" in the ibm-web-ext.xmi file. That will cause the plug-in to use a wildcard entry for the context-root of your web application. For example, if the context-root is \"myapp\", then there will be a URI entry for \"/myapp/*\" in the plug-in config, and everything starting with \"myapp\" will be routed to the application in WAS. \n\n\nNow, if you also want to be able to serve some of the static files from the IHS web server itself, you will need to do a trick using RewriteRule in the IHS config. Here is how the trick works:\n\n1) Create a subdirectory called \"static\" under the IHS DocumentRoot directory. And put the static files that you want IHS to serve into that directory. For example in the IHS document root directory (HTTPServer/htdocs/) create a subdirectory called \"static\". Something like this:\n/usr/IBM/HTTPServer/htdocs/static/\n\n2) In your web application, you will reference those files using relative references like \"static/picture.jpg\", or \"static/mystyles.css\".\n\nThose relative references will be interpreted as URLs like this:\n/myapp/static/picture.jpg\n/myapp/static/mystyles.css\n\nKeep in mind that there really is NOT any \"static\" subdirectory in the application. But that is ok.\n\n3) Now, in the IHS config, you must use RewriteCond and RewriteRule to watch for these references, and redirect to get them from IHS. For example, look at these directives...\n\n<ifModule mod_rewrite.c>\nRewriteEngine on\nRewriteRule ^/myapp/static/(.*) /static/$1 [PT]\n</ifModule>\n\nIt means, if the URI begins with /myapp/static/* then IHS will rewrite it to just /static/* and \"pass-through\". Since /static/* does NOT match anything in the Plug-in config, the request will be handled by IHS, and the file will be served from the static directory under IHS DocumentRoot.\n\nTo the user looking at the URL in the browser they will see this:\n/hostname/myapp/static/picture.jpg\n\nBut, the file will really be served by IHS from here:\n/hostname/static/picture.jpg\n\nHere is another example:\n\nIf you just want to match and serve *.gif files from IHS, use:\n\nRewriteCond %{REQUEST_URI} \\.(gif)$ [NC]\nRewriteRule ^/myapp/(.*) /static/$1 [PT]\n\nIf you just want to match and serve *.gif, *.css and *.js files from IHS, use:\n\nRewriteCond %{REQUEST_URI} \\.(gif|css|js)$ [NC]\nRewriteRule ^/myapp/(.*) /static/$1 [PT]\n\nWhich assumes the files themselves are placed in [IHS_DOC_ROOT]/static/.\n\n4) For the static files in the application, you will need to put them in some other directory that is NOT called \"static\", for example \"images/sunset.jpg\" would be a directory and file in the myapp application. This URL request, would be handled by the Plug-in and sent to the application in WAS:\nhostname/myapp/images/sunset.jpg\n\n\nSo, by using the trick described above, some static files will be served from IHS, like:\n/hostname/myapp/static/picture.jpg\n\nBut other static files will be served from the web application running in WAS, like:\n/hostname/myapp/images/sunset.jpg"
}
] |
TRAIN_Q442 | Help with Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5 (CVE-2015-4000)
I need to understand details regarding Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5 (CVE-2015-4000). This vulnerability is commonly referred to as "Logjam". Where can I find this information? | CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]
DESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. 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".
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N) | false | [
{
"filename": "swg21959412.txt",
"text": "Title: IBM Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5 (CVE-2015-4000) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]\nDESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as \"Logjam\".\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server version 2.5\n\nREMEDIATION/FIXES\nNone\n\nWORKAROUNDS AND MITIGATIONS\nCustomers should follow the mitigation advice contained in the WebSphere Application Server security bulletin, located at http://www.ibm.com/support/docview.wss?uid=swg21957980 [http://www-01.ibm.com/support/docview.wss?uid=swg21957980] .\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] ACKNOWLEDGEMENT\nReported to IBM by The WeakDH team at https://weakdh.org [https://weakdh.org] \n\nCHANGE HISTORY\n 08 June 2015: Original document published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY."
}
] |
TRAIN_Q443 | How to get debug information when the IBM Content Navigator Installer is failing on the Unix Platform?
How to get debug information when the IBM Content Navigator Installer is failing on the Unix Platform? | To capture the debug output from the UNIX command line, enter one of the following (based on what shell you are using) at the command line prior to executing the installer:
export LAX_DEBUG=true or setenv LAX_DEBUG true or LAX_DEBUG=true or set LAX_DEBUG or whatever would be appropriate for the Unix shell.
Then run the installer. The output that is produced should help debug the installer.
If you would like to redirect output to a file:
1. Set LAX_DEBUG=file as per the instruction above.
2. Run your installer.
3. Once the install is complete a file labeled jx.log will be generated in the same directory as your installer. This file will contain the entire debug output generated by the install. | false | [
{
"filename": "swg21980147.txt",
"text": "Title: IBM How to get debug information when the IBM Content Navigator Installer on the Unix Platform is failling? - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How to get debug information when the IBM Content Navigator Installer on the Unix Platform is failling?\n\n\nANSWER\nTo capture the debug output from the UNIX command line, enter one of the following (based on what shell you are using) at the command line prior to executing the installer:\nexport LAX_DEBUG=true or setenv LAX_DEBUG true or LAX_DEBUG=true or set LAX_DEBUG or whatever would be appropriate for the Unix shell. \n\nThen run the installer. The output that is produced should help debug the installer. \nIf you would like to redirect output to a file:\n1. Set LAX_DEBUG=file as per the instruction above. \n2. Run your installer. \n3. Once the install is complete a file labeled jx.log will be generated in the same directory as your installer. This file will contain the entire debug output generated by the install."
}
] |
TRAIN_Q444 | Licence authorised in SPSS 22, however, same error code of missing license appears
I had SPSS 22 that worked fine until the license ended. It was renewed and when I tried to re-enter the license number it was authorised, however, there was still an error code of missing license and so I can work with my SPSS.
This is the error code:
Error # 7001 There is no license for IBM SPSS Statistics. This could be due to a missing license file or no more network licenses available. For detailed information about this problem, run the 'showlic' utility found in the product installation directory. Execution of this command stops. Specific symptom number: 18
I would appreciate your help! | No, installing IBM SPSS Statistics and AMOS for Windows releases on a Macintosh operating system or hardware using any dual booting or emulation software is not supported and cannot run properly. | false | [
{
"filename": "swg21477587.txt",
"text": "Title: IBM Will current versions of IBM SPSS Statistics or AMOS for Windows run on a Macintosh operating system? - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n I have a Macintosh computer with Intel processor. I am wondering if I can install an IBM SPSS Statistics for Windows or IBM SPSS AMOS for Windows releases on this Mac with emulation or dual-booting software such as Boot Camp, Parallels, Virtual PC, Rosetta? \n\nANSWER\nNo, installing IBM SPSS Statistics and AMOS for Windows releases on a Macintosh operating system or hardware using any dual booting or emulation software is not supported and cannot run properly. \n\nIBM SPSS Statistics is available for Macintosh operating system as a single release. IBM SPSS AMOS is available only for Microsoft Windows operating system.\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]"
}
] |
TRAIN_Q445 | Why does IBM Datacap 8.1 appear to hang
Why does IBM Datacap 8.1 appear to hang, requiring a restart of all components http://ow.ly/yhjCg #ibmecm | The cause is due to a malformed SQL query string. From the client perspective, it was reported to occur during logon via TMWeb, and Thick Client. Another case was from a user that was doing a Thick Client query.
TMServer has an feature where it will retry any command that results in error, based on the settings in the registry. The settings reflect the number of retries to do and the time interval to wait. The default settings have a duration of 16 minutes, which gives the appearance that the TMServer has hung. | false | [
{
"filename": "swg21666402.txt",
"text": "Title: IBM Why does IBM Datacap 8.1 appear to hang, requiring a restart of all components? - United States\n\nText:\nhang; non responsive; timeout; Admin retry; Engine retry TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Why does IBM Datacap appear to hang, requiring a restart of all components? \n\nSYMPTOM\nThe Datacap system appears to become non-responsive, requiring a restart of all components to get it working again.\n\n\nCAUSE\nThe cause is due to a malformed SQL query string. From the client perspective, it was reported to occur during logon via TMWeb, and Thick Client. Another case was from a user that was doing a Thick Client query. \n\nTMServer has an feature where it will retry any command that results in error, based on the settings in the registry. The settings reflect the number of retries to do and the time interval to wait. The default settings have a duration of 16 minutes, which gives the appearance that the TMServer has hung.\n\n\nDIAGNOSING THE PROBLEM\nCollect and examine the TMServer log. Look for multiple instances (6-12) of an ADO error, indicating a bad query was executed. This information can be used to identify the user that is causing the problem\n\n\n\nRESOLVING THE PROBLEM\nWhile bad queries should be avoided, the following will allow TMServer to respond faster, should a bad query happen: \n\n1. Stop all Datacap applications, then stop the TMServer. \n\n2. Change the following registry entries on the TMServer box:\n\n\n * \n * \n * HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Datacap\\TMS\\InterThread (REG_SZ) Admin retries HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Datacap\\TMS\\InterThread (REG_SZ) ADO retries HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Datacap\\TMS\\InterThread (REG_SZ) Engine retries \n * \n * \n * \n * HKEY_LOCAL_MACHINE\\SOFTWARE\\Datacap\\TMS\\InterThread (REG_SZ) Admin retries HKEY_LOCAL_MACHINE\\SOFTWARE\\Datacap\\TMS\\InterThread (REG_SZ) ADO retries HKEY_LOCAL_MACHINE\\SOFTWARE\\Datacap\\TMS\\InterThread (REG_SZ) Engine retries \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n\n\n3. Restart the TMServer, then start the Datacap applications in reverse order. \n\nPlease Note: Since these are considered tuning parameters, you will need to test to see what settings work best for your system. \n\nNote: for Datacap 9.x, the registry entry name is singular, as in 'Admin retry' or 'Engine retry'."
}
] |
TRAIN_Q446 | Is DataPower affected by the bash environment variable vulnerability CVE-2014-6271 or CVE-2014-7169
Is DataPower affected by the recent vulnerability reported through CVE-2014-6271 or CVE-2014-7169? | In particular, DataPower in all editions and all platforms is NOT vulnerable to the Bash vulnerabilities: CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277, and CVE-2014-6278. | false | [
{
"filename": "swg21685435.txt",
"text": "Title: IBM WebSphere DataPower is not affected by the Bash vulnerabilities (CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277, and CVE-2014-6278)\nFlash (Alert) - United States\n\nText:\nCVE-2014-6271 CVE-2014-7169 DataPower Bash FLASH (ALERT)\n\nABSTRACT\n DataPower is not vulnerable to the Bash vulnerabilities that have been referred to as “Bash Bug” or “Shellshock” and the two memory corruption vulnerabilities. \n\nCONTENT\nDataPower does not use Bash anywhere. Hence it is not impacted by any of the Bash vulnerabilities. \n\nIn particular, DataPower in all editions and all platforms is NOT vulnerable to the Bash vulnerabilities: CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277, and CVE-2014-6278. \n\nIBM recommends that you review your entire environment to identify vulnerable releases of Bash and take appropriate mitigation and remediation actions."
}
] |
TRAIN_Q447 | ITCAM Agent for DataPower in TEP view, no data in the "HTTP Mean Transaction Times - Top 10" workspace.
WIth ITCAM Agent for DataPower in TEP view, there is no data in the "HTTP Mean Transaction Times - Top 10" workspace. The problem is that while the KBN agent is displaying some data in the TEP, in the "DataPower Appliances" view, there is no data in the "HTTP Mean Transaction Times - Top 10" workspace. | - | true | [] |
TRAIN_Q448 | export XML results in ASE
Hello everyone, you all know that ASD gives the possibility to export results in XML with File --> Export --> Scan Results as XML (Legacy...) Is there any chance to have the same XML using ASE 9035 ??? | The answer to the question is 'no'.
In AppScan Enterprise Console, there are functions, Export to XML and Export detailed Security issues to PDF, but there is no function Export detailed Security issues to XML. | false | [
{
"filename": "swg21649798.txt",
"text": "Title: IBM How to Export the Scan Results (Detailed Security Issues) into XML format in AppScan Enterprise - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Is there a way to Export the Scan Results (Detailed Security Issues) into XML format in IBM Security AppScan Enterprise? \n\nANSWER\nThe answer to the question is 'no'. \nIn AppScan Enterprise Console, there are functions, Export to XML and Export detailed Security issues to PDF, but there is no function Export detailed Security issues to XML. \n\nWe strongly suggest to submit an enhancement request (RFE) for the AppScan Enterprise products as described in How to submit enhancement requests for IBM Security products [http://www.ibm.com/support/docview.wss?uid=swg21682719]. The requests there are submitted directly to the AppScan management team."
}
] |
TRAIN_Q449 | How do I identify people in scope across Matters in Atlas?
How do I identify people in scope across Matters in Atlas? | REP_PEOPLE_INSCOPE_VW view has information about people in scope. You can create a query by joining the view with REP_MATTER_VW, REP_REQUEST_VW, REP_NOTICES_VW and REP_PERSON_VW views. | false | [
{
"filename": "swg21983912.txt",
"text": "Title: IBM Identifying people in scope across Matters in Atlas - United States\n\nText:\nAtlas People in Scope Views TECHNOTE (FAQ)\n\nQUESTION\n How do I identify people in scope across Matters in Atlas? \n\nCAUSE\nQuery to identify people in scope across matters in Atlas\n\nANSWER\nREP_PEOPLE_INSCOPE_VW view has information about people in scope. You can create a query by joining the view with REP_MATTER_VW, REP_REQUEST_VW, REP_NOTICES_VW and REP_PERSON_VW views. \n\nPlease refer to reporting views documentation at the following link for more details about Matter related views\n\nhttps://www.ibm.com/support/knowledgecenter/SS5JP8_6.0.3/com.ibm.aps.use.doc/apsrv0044.html [https://www.ibm.com/support/knowledgecenter/SS5JP8_6.0.3/com.ibm.aps.use.doc/apsrv0044.html]l"
}
] |
TRAIN_Q450 | MQRC_NOT_AUTHORIZED after migrating from Websphere V7.0 to V8.5.5
After migration from WAS 7 TO WAS 8.5.5.3 ,WAS is unable to communicate with MQ and we see the following errors in the SystemOut.log:
com.ibm.msg.client.jms.DetailedJMSSecurityException: JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager 'XXXQM' with connection mode 'Client' and host name 'ipaddress(port)'.
Please check if the supplied username and password are correct on the QueueManager to which you are connecting. at com.ibm.msg.client.wmq.common.internal.Reason .reasonToException(Reason.j ava:516)
.....
Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED'). at com.ibm.msg.client.wmq.common.internal.Reason.createException (Reason.java:204)
What is causing this? | WebSphere MQ access control is based on user identifiers. There is a deliberate change in the default behaviour between the WebSphere MQ V7.0.1 classes for JMS and the WebSphere MQ V7.1 (and later) classes for JMS regarding the default user identifier flowed to the queue manager. | false | [
{
"filename": "swg21662193.txt",
"text": "Title: IBM Changes in the default user identifier between WebSphere MQ V7.0.1 classes for JMS and WebSphere MQ V7.1 classes for JMS - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n You have configured a WebSphere Application Server WebSphere MQ messaging provider connection factory without an Authentication Alias and do not programmatically supply user identifier information when creating a connection to a queue manager. You notice a change in the default behaviour between WebSphere Application Server versions regarding the user identifier flowed on the MQCONN to the target WebSphere MQ Queue Manager:\n\n- When using WebSphere Application Server v7.0 and v8.0, no user identifier value (blank) is passed to the queue manager. \n\n- When using WebSphere Application Server V8.5, a non-blank user identifier value is passed to the queue manager. \n\nIn the latter case, you receive the following exception when creating a connection to a queue manager:\n\nJMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED') \n\nIs this change in behaviour expected? \n\nANSWER\nWebSphere MQ access control is based on user identifiers. There is a deliberate change in the default behaviour between the WebSphere MQ V7.0.1 classes for JMS and the WebSphere MQ V7.1 (and later) classes for JMS regarding the default user identifier flowed to the queue manager.\nFrom the WebSphere MQ V7.1 classes for JMS onwards, a non-blank user identifier is always flowed to the queue manager when creating a connection to WebSphere MQ. This is true even if no user identifier has been specified, or a blank or null user identifier has been specified; for example by calling:\n\nMQConnectionFactory.createConnection();\n\nor:\n\nMQConnectionFactory.createConnection(“”, “”);\n\nor:\n\nMQConnectionFactory.createConnection(null, null);\n\nIn the case where a null or blank user identifier has been specified, the WebSphere MQ V7.1 and later classes for JMS will query the value of the Java System Property user.name. The value of this property is flowed to the queue manager for authorization.\n\nAs a result, if the user identifier specified by the Java System Property user.name is not authorized to access the queue manager, the queue manager will return an exception to the WebSphere MQ classes for JMS with Reason Code MQRC_NOT_AUTHORIZED and the connection to the queue manager will not be established.\n\nThis change in behaviour could affect topologies that previously relied on the default behaviour in the WebSphere MQ V7.0.1 classes for JMS that flowed a blank user identifier when establishing a CLIENT mode transport connection. The expectation that a blank or null user identifier will be flowed by default, and that the user identifier that started the WebSphere MQ server-connection channel would be used by the queue manager when performing the authorization checks, is no longer valid from the WebSphere MQ V7.1 classes for JMS.\n\nIn the case outlined above, system administrators that are currently relying on the default behaviour of the WebSphere MQ V7.0.1 classes for JMS should review their configurations regarding the use of user identifiers and authorization. This might also help to improve security within their WebSphere MQ topology.\n\n\nIn summary, the change in behaviour will affect users of:\n\n- The WebSphere MQ V7.1 and later classes for JMS.\n\n- The WebSphere MQ V7.1 and later JCA Resource Adapter that includes the classes for JMS.\n\n- Versions of WebSphere Application Server that include the WebSphere MQ V7.1 and later JCA Resource Adapter. Currently this is WebSphere Application Server V8.5.0.0 and later.\n\n\nThe com.ibm.mq.jms.ForceUserID Java System Property\n\nA Java System Property called “com.ibm.mq.jms.ForceUserID” was introduced as part of APAR IZ49302 [http://www.ibm.com/support/docview.wss?uid=swg1IZ49302] and included from WebSphere MQ V6.0.2.8 and WebSphere MQ V7.0.1.\n\nThe changes made as part of this APAR could be used to change the default behaviour in the WebSphere MQ V7.0.1 classes for JMS regarding the user identifier value flowed to the queue manager when creating a connection.\n\nThis property is no longer valid from WebSphere MQ V7.1. Setting this property will have no affect on the WebSphere MQ V7.1 classes for JMS and later.\n\nOther Useful Resources\n\nWebSphere MQ Documentation\n\nThe WebSphere MQ Documentation contains a section on planning user authorization which also includes a description on access control for clients. A link to this section in the WebSphere MQ V7.1 Documentation is as follows:\n\nWebSphere MQ > Security > Planning for your security requirements >> Planning authorization [http://pic.dhe.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.doc/zs14070_.htm]\n\nTechnotes\n\nA Technote is available that explains J2C Authentication Aliases and how they can be used to configure the user identifier flowed to a queue manager when creating a connection: \n\nEnterprise applications, the WebSphere Application Server WebSphere MQ messaging provider connection factories and Authentication Aliases explained [http://www.ibm.com/support/docview.wss?uid=swg21580097]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server"
}
] |
TRAIN_Q451 | How to connect ICC to P8 using SSL?
In the ICC Configuration Manager, http has been changed to https in the P8 URL. But validating the connection to P8 fails. | ICC communicates with P8 in several different components. Depending on the API used for the various components, P8 certificates need to be installed in multiple places. | false | [
{
"filename": "swg21979016.txt",
"text": "Title: IBM Configure IBM Content Collector to use SSL to communicate with IBM FileNet P8. - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How do I configure IBM Content Collector (ICC) to use SSL to communicate with IBM FileNet P8 for all components? \n\nCAUSE\nICC communicates with P8 in several different components. Depending on the API used for the various components, P8 certificates need to be installed in multiple places.\n\nANSWER\nDo the following steps to install P8 certificates. Depending on your business requirements, you may not use all of the components so some steps may not be necessary. \n\n * First obtain a P8 server certificate by accessing the P8 Content Engine ping page using this URL: https://<ce_server>:<ssl_port>/FileNet/Engine \n \n From the browser, view the certificate and copy it to a file. Use it for later steps. \n Do not use the MTOM page as it may not produce the same certificate that ICC requires. \n \n \n \n \n * Perform this step if you are going to run ICC Initial Configuration to create new document classes in P8 object store. * To import the certificate, issue the following command, whereICCInstallDiris the directory of your Content Collector installation andP8CertificatFileis the certificate for the FileNet P8 server: \"ICCInstallDir\\java\\jre\\bin\\keytool.exe\" -import -file P8CertificateFile\n -keystore \"ICCInstallDir\\java\\jre\\lib\\security\\cacerts\" -alias afup8 \n \n \n * At the password prompt, enter the password for the JRE keystore. (The default password is changeit.) \n * Enterywhen asked whether to trust the certificate. \n * Run ICC Initial Configuration and you should then be able to validate the connection with P8 using SSL.\n \n \n\n * Perform this step if you are going to run task route archiving to P8: * Add the P8 certificate into the Windows Trusted Root Certificate Authorities via the Microsoft Management Console. \n * For more details instructions, refer to this document:\n http://www-01.ibm.com/support/docview.wss?uid=swg21610358 [http://www-01.ibm.com/support/docview.wss?uid=swg21610358]\n \n \n\n * Perform this step if you are going to retrieve, restore, or search for documents from P8: * Start ikeyman from ICC-install-directory\\AFUWeb\\ewasfor the ICC embedded web application server. \n * In the ikeyman utility, select Key Database File>Open, and select PKCS12as key database type. \n * In theLocationfield, specify theWAShome\\profiles\\profile name\\config\\cells\\cell name\\nodes\\node name\\trust.p12file.\n ReplaceWAShome,profile name,cell name, andnode namewith the proper values of your web application server installation. \n * Click OK. \n * When prompted for a password, enter the password. ClickOK. The default password is WebAS. \n * Under theSigner certificateslist, clickAddto add the P8 certificate. \n * Exit ikeyman utility and restart IBM Content Collector Web Application service. \n * For more details instructions, refer to this document: http://www.ibm.com/support/knowledgecenter/SSAE9L_4.0.1/com.ibm.content.collector.doc_kc/installing/t_afu_establish_trust_relationship.dita?lang=en [http://www.ibm.com/support/knowledgecenter/SSAE9L_4.0.1/com.ibm.content.collector.doc_kc/installing/t_afu_establish_trust_relationship.dita?lang=en]"
}
] |
TRAIN_Q452 | Cannot start the IBM Content Collector Configuration Store Service
How to resolve when the IBM Content Collector Configuration Store Service cannot be started? | Shutdown the IBM Content Collector Configuration Store Service if it is running.
2. Make a backup copy of all files under the following directory:
C:\ProgramData\IBM\ContentCollector\ConfigurationStore
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.
3. Free up disk space on the drive
4. Delete the following files:
C:\ProgramData\IBM\ContentCollector\ConfigurationStore\logs\*
C:\ProgramData\IBM\ContentCollector\ConfigurationStore\solmsg.out
C:\ProgramData\IBM\ContentCollector\ConfigurationStore\solerror.out
Important:
Delete only the files under C:\ProgramData\IBM\ContentCollector\ConfigurationStore\logs\.
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.
6. Restart IBM Content Collector services. | false | [
{
"filename": "swg21680391.txt",
"text": "Title: IBM Content Collector Configuration Store is corrupted - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM Content Collector Configuration Store Service cannot be started successfully due to database corruption. \n\nSYMPTOM\nCannot start the IBM Content Collector Configuration Store Service\n\n\nCAUSE\nTransaction log gets corrupted when IBM Content Collector server runs out of disk space. \n\nRESOLVING THE PROBLEM\n\n\n\n 1. Shutdown the IBM Content Collector Configuration Store Service if it is running. \n 2. Make a backup copy of all files under the following directory:\n C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\n \n C:\\ProgramData may be hidden by default. Show hidden folders by changing the configuration in Folder and Search options > View tab > Hidden files and folders > Show hidden files, folders, and drives. \n 3. Free up disk space on the drive \n 4. Delete the following files:\n C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\\logs\\*\n C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\\solmsg.out\n C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\\solerror.out\n \n Important: \n Delete only the files under C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\\logs\\. \n Do not delete the folder itself.\n \n 5. If restoring the configuration store to a previously backed up copy is required, run afuConfigStoreTool -backup to restore the backup copy. See production documentation for more information on running this tool. Otherwise, proceed to the next step. \n 6. Restart IBM Content Collector services.\n \n\nRELATED INFORMATION\n IBM Content Collector Information Center [http://pic.dhe.ibm.com/infocenter/email/v4r0m0/index.jsp]"
}
] |
TRAIN_Q453 | ICO's Roadmap of supporting next OpenStack versions
Hello,
ICO 2.5.0.2 is compatible with OpenStack kilo, is there a plan making it work with OpenStack Liberty/Mitika ?
Would you share any information or link about the roadmap, please?
Thanks in advance. | The current release of IBM Cloud Orchestrator will continue to bundle IBM Cloud Manager with OpenStack (ICMO), while future IBM Cloud Orchestrator releases will no longer bundle ICMO, as it has been announced that ICMO is at the end of market (see reference document below). | false | [
{
"filename": "swg2C1000132.txt",
"text": "Title: IBM Cloud Orchestrator (ICO) continues to be a strategic solution for IBM - United States\n\nText:\n FLASH (ALERT)\n\nABSTRACT\n Cloud Orchestrator (ICO) continues to be a strategic solution for IBM \n\nCONTENT\nIBM Cloud Orchestrator continues to be a strategic solution for IBM in Hybrid Cloud management and will continue to be actively developed. Future IBM Cloud Orchestrator releases will enable management of external OpenStack environments which are compliant with the RefStack certification, providing more choices and flexibility to clients to select their preferred OpenStack vendor. The current release of IBM Cloud Orchestrator will continue to bundle IBM Cloud Manager with OpenStack (ICMO), while future IBM Cloud Orchestrator releases will no longer bundle ICMO, as it has been announced that ICMO is at the end of market (see reference document below).\nIBM Cloud Orchestrator (ICO) and IBM Cloud Manager with OpenStack (ICMO) will continue to be supported until Sept 2020.\n\nReference: ICMO End of Market announcement:\nhttp://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS916-062/index.html&lang=en&request_locale=en [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS916-062/index.html&lang=en&request_locale=en]"
}
] |
TRAIN_Q454 | Column Analysis on Informix database using odbc connector fails with error SQLSTATE = HY000: Native Error Code = -256
Column Analysis on Informix database using odbc connector fails with error SQLSTATE = HY000: Native Error Code = -256 | To resolve the above error, set the Transaction handling>Isolation Level from none to Auto-Commit. | false | [
{
"filename": "swg21591143.txt",
"text": "Title: IBM Information Server Informix Wire Protocol driver error \"Transaction not available\" from ODBC Connector Stage - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When using the ODBC Connector Stage to access data in an Informix database, receive the following error:\n\nMessage: ODBC_Connector_0: ODBC function \"SQLPrepare\" reported: SQLSTATE = HY000: Native Error Code = -95: Msg = [IBM(DataDirect OEM)][ODBC Informix Wire Protocol driver][Informix]Unexpected Network Error.\nODBC function \"SQLPrepare\" reported: SQLSTATE = HY000: Native Error Code = -256: Msg = [IBM(DataDirect OEM)][ODBC Informix Wire Protocol driver][Informix]Transaction not available. (CC_OdbcDBStatement::dbsPrepare, file CC_OdbcDBStatement.cpp, line 347)\n\n\nRESOLVING THE PROBLEM\nTo resolve the above error, set the Transaction handling>Isolation Level from none to Auto-Commit."
}
] |
TRAIN_Q455 | How can I query the Derby database in Portal via SQL statements?
I have a Portal system I just installed. I have not yet run database-transfer to copy the data from the Derby database to a DB2, Oracle, or SQL Server database. I don't wish to transfer to an external database and I have a need to run a SQL query against a table or two in the Derby database to troubleshoot an issue.
How can I perform this action? | In order to obtain the data and structure of the WebSphere Portal database, dblook and ij utilities can be used to accomplish such goals. | false | [
{
"filename": "swg21381009.txt",
"text": "Title: IBM Using dblook and ij to work with the embedded Apache Derby in WebSphere Portal - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM WebSphere Portal 6.1 uses an embedded version of Apache Derby out of the box. However, there is no longer a graphical tool such as CloudView (as with Cloudscape 5.x). In order to obtain the data and structure of the WebSphere Portal database, dblook and ij utilities can be used to accomplish such goals. \n\nRESOLVING THE PROBLEM\n\nBefore proceeding with the following, it is strongly recommended that you back up your Derby database. Make a copy of <wp_profile>/PortalServer/derby/wpsdb to a backup directory. Since the version of Derby used in WebSphere Portal is embedded, you must stop the Portal server before you can access the database although you can always work on the backup copy.\n\nNOTE: For simplicity, we will omit the extension of the utilities. You should add \".sh\" or \".bat' depending on the platform.\n\nThere are three primary utility tools that are installed with WebSphere 6.1, \"dblook\", \"ij\", and \"sysinfo\", under the <was_root>/AppServer/derby/bin/embedded directory. The sysinfo utility generates information about the operating system, the Java version and classpath, and the Derby driver files and version information.\n\ndblook utility\nThe dblook utility is used to view the database structure (in DDL - Data Definition Language) for a specific database. \n\nThe usage is dblook -d <databaseURL> [options], where databaseURL is in the \"jdbc:derby:<database>\" format. The <database> should be given as a full path, such as C:\\IBM\\WebSphere\\wp_profile\\derby\\wpsdb. \n\nCommonly used options include: \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * Examples:\n * \n * \n * dblook -d jdbc:derby:C:\\IBM\\WebSphere\\wp_profile\\PortalServer\\wpsdb -o C:\\temp\\wpsdb_ddl.sql\n * \n * \n * \n * \n * dblook -d jdbc:derby:C:\\IBM\\WebSphere\\wp_profile\\PortalServer\\wpsdb -z release -o C:\\temp\\wpsdb_ddl.sql\n * \n * \n * \n * \n * dblook -d jdbc:derby:C:\\IBM\\WebSphere\\wp_profile\\PortalServer\\wpsdb -z release -t user_desc -verbose -o C:\\temp\\user_desc.sql\n * \n * \n\n\nij utility \nThe ij utility is a command line SQL processor. It can be used to run DDL for creating database, tables, indexes, and so on. In a WebSphere Portal environment, it would typically be used for exporting data or making simple changes (when advised by IBM Support). \n\nTo start ij, simply open a command prompt or terminal window, change the directory and enter the command. You should then see the ij shell with prompt \"ij>\". \n\nThe following are some common commands that you may use when reviewing data in the Portal database. * \n * ij> connect 'jdbc:derby:C:\\IBM\\WebSphere\\wp_profile\\derby\\wpsdb';\n * \n * \n * \n * \n * ij> show connections;\n * \n * \n * CONNECTION0* - jdbc:derby:C:\\ibm\\websphere\\wp_profile\\portalserver\\derby\\wpsdb \n * = current connection \n ij> driver \"org.apache.derby.jdbc.EmbeddedDriver'; \n * \n * \n * \n * ij> set schema=release;\n * \n * \n * \n * \n * ij> select * from user_desc where oid=1000;\n * \n * \n * \n * \n * ij> run 'myquery.sql';\n * \n * \n * \n * \n * \n * \n * ij> CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE('RELEASE','USER_DESC','USER_DESC.SQL',';','|',NULL);\n * \n * \n * \n * \n * ij> \n * CALL SYSCS_UTIL.SYSCS_EXPORT_QUERY('SELECT * FROM RELEASE.USER_DESC','user_desc_query.sqlL',null,'|',NULL);\n * \n * \n\nRELATED INFORMATION\n Derby utility from Apache [http://docs.oracle.com/javadb/10.3.3.0/getstart/cgsusingtoolsutils.html]\nDerby SQL references from Apache [http://db.apache.org/derby/docs/10.1/ref/crefsqlj23296.html]\n\n\n \n\nCross reference information Segment Product Component Platform Version Edition Organizational Productivity- Portals & Collaboration WebSphere Portal End of Support Products AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS 7.0, 6.1"
}
] |
TRAIN_Q456 | zonecfg error while starting nodeagent and dmgr
I saw zonecfg error while starting nodeagent and dmgr in solaris server
My env is Oracle Solaris 11.2 SPARC, and WAS is 8558, jave 1.7. [1/22/16 21:31:18:379 AEDT] 00000001 SystemOut O java.lang.Exception: command /usr/sbin/zonecfg failed with 1 at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor.executeCommand(SolarisHypervisor.java:357) at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor.access$100 (SolarisHypervisor.java:30) at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor$Zone.processZoneCfg(SolarisHypervisor.java:570) at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor$Zone.(SolarisHypervisor.java:461) at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor ..... Is that normal behavior and what's the exactly meaning of the error? | When WebSphere Application Server is run as a non-root user it will not be able to run native commands. This limited access causes the exceptions. | false | [
{
"filename": "swg21626683.txt",
"text": "Title: IBM Exceptions starting WAS 8.5 as non root user on Solaris - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You notice the exceptions below at start up. \n\nSYMPTOM\nException: command /usr/sbin/zonecfg failed with 1\nand \nFFDC Exception:java.lang.Exception SourceId:com.ibm.ws.xd.vv.nodedetect.NetworkInterfaceUtil.getMacAddresses ProbeId:2\njava.lang.Exception: dlopen() returned error; rc=128\n\n\nCAUSE\nWhen WebSphere Application Server is run as a non-root user it will not be able to run native commands. This limited access causes the exceptions.\n\nRESOLVING THE PROBLEM\nTo resolve the problem, run WebSphere Application Server under a root user. If the environment is not virtualized, that is if Solaris zones are not being used then the errors can be ignored as these will only occur at start up and will not affect a non-virtualized environment"
}
] |
TRAIN_Q457 | What is the correct number of datasource connections for Portal?
What is the best way to figure out how to configure the maximum number of datasource connections for my Portal server? What factors are involved that I need watch out for? | When tuning WebSphere Portal at version 6.0 and beyond, one of the concerns that arises is how should one tune the maximum number of Portal datasources. Portal can and does make heavy internal use of datasources, so miscalculating this (maximum) value can have a significant impact on system behavior. Out of the box, the default maximum setting is 50. This may or may not be sufficient for any given system.
Each Portal request may make any number of database (DB) requests ranging for none to several.. Further, customized portlets and PPR (Parallel Portlet Rendering) may cause several concurrent DB requests. By default, the maximum number of WebContainer threads is also set to 50. Therefore the ratio between the maximum number of Portal datasource connections to the maximum number of Portal WebContainer threads is 1:1. Support has found that this ratio is often too low for the best performance. In the past, there have been recommendations of this ratio as high as of 2:1 or even 2.5:1.
However, these values caused concern in large deployments where the TOTAL number of maximum datasource connections might start to place a strain on backend resources. Recent analysis suggests that these ratio values may be safely reduced to 1.25: 1 for all Portal datasource, with the exception of the jcrDB when WCM is used extensively. In this case, we recommend a ratio of 1.5:1 | false | [
{
"filename": "swg21509634.txt",
"text": "Title: IBM How to set an appropriate number of Portal Datasource connections in WebSphere Portal - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\nFor a given maximum number of Portal WebContainer threads set, what should I set my maximum Portal datasource connections to? \n\nANSWER\nWhen tuning WebSphere Portal at version 6.0 and beyond, one of the concerns that arises is how should one tune the maximum number of Portal datasources. Portal can and does make heavy internal use of datasources, so miscalculating this (maximum) value can have a significant impact on system behavior. Out of the box, the default maximum setting is 50. This may or may not be sufficient for any given system. \n\nEach Portal request may make any number of database (DB) requests ranging for none to several.. Further, customized portlets and PPR (Parallel Portlet Rendering) may cause several concurrent DB requests. By default, the maximum number of WebContainer threads is also set to 50. Therefore the ratio between the maximum number of Portal datasource connections to the maximum number of Portal WebContainer threads is 1:1. Support has found that this ratio is often too low for the best performance. In the past, there have been recommendations of this ratio as high as of 2:1 or even 2.5:1. \n\nHowever, these values caused concern in large deployments where the TOTAL number of maximum datasource connections might start to place a strain on backend resources. Recent analysis suggests that these ratio values may be safely reduced to 1.25: 1 for all Portal datasource, with the exception of the jcrDB when WCM is used extensively. In this case, we recommend a ratio of 1.5:1 \n\n----------------------------------------------------------------------------------------------------------------- \n\nFor example, if your system's \n\nMaximum number of WebContainer threads is 100 \n\nthen you should set your \n\nMaximum number of Portal datasource connections to 125 \n\nfor each Portal datasource. \n\n----------------------------------------------------------------------------------------------------------------- \n\nIf during Runtime, you should find that your running out of Portal Datasource connections, you may go ahead and increase the ratio up to 2:1. Please be aware of how this might impact your backend resources and be sure to scale your database accordingly. \n\n------------------------------------------------------------------------------------------------------------------ \n\nTo find the number of WebContainer threads that are running in any particular Portal server, use the WebSphere Application Server Admin Console and go to the following location: \n\nServers ---> Application Servers --> WebSphere_Portal (your server) --> Thread Pools --> WebContainer \n\n \n\nTo find the Data Source setting for your Portal datasources, use the WebSphere Application Server Admin Console to go to the following location: \n\nResources ---> Data Sources ---> wpdbDB (for example) --> Connection pools \n\n--------------------------------------------------------------------------------------------------------------------"
}
] |
TRAIN_Q458 | Error TASK001X while upgrading Portal 8.0.0.1 to 8.0.0.1 CF14 during import-nodes sub-task
Error TASK001X while upgrading Portal 8.0.0.1 to 8.0.0.1 CF14 during import-nodes sub-task | Please make the following change in the WAS Admin Console...
Applications > WebSphere enterprise applications >
JavaContentRepository > Target specific application status > Check the
box for the WebSphere_Portal server > Click Enable Auto Start > Save
changes > restart Portal
After making this change please attempt the CF upgrade again. | false | [
{
"filename": "swg21691034.txt",
"text": "Title: IBM Error TASK001X while upgrading Portal 8.0.0.1 to 8.0.0.1 CF14 during import-nodes sub-task - United States\n\nText:\nupgrade; TASK001X; import-nodes; 404 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nWhile attempting to upgrade Portal to CF14 the upgrade fails during the import-nodes sub-task.\n\nSYMPTOM\nThe ConfigTrace.log shows the following...\n\nimport-nodes:\n\n--- Exception Thrown ---\nC:\\Portal8\\PortalServer\\jcr\\wp.content.repository.install\\config\\include\ns\\jcr.install_cfg.xml:826: com.ibm.icm.jcr.task.TaskException:\nTASK001X: Remote task execution failed with response code 404 due to\nexception : Not Found . Please check the server log for more\ninformation.\n\nat\ncom.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:\n840)\n\nat\norg.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)\n\nat org.apache.tools.ant.Task.perform(Task.java:364)\n\nat org.apache.tools.ant.Target.execute(Target.java:341)\n\nat org.apache.tools.ant.Target.performTasks(Target.java:369)\n\nat\norg.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)\n\nat\norg.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleChe\nckExecutor.java:37)\n\n...\n\nCaused by: com.ibm.icm.jcr.task.TaskException: TASK001X: Remote task\nexecution failed with response code 404 due to exception : Not Found .\nPlease check the server log for more information.\n\nat\ncom.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:\n825)\n\n... 75 more\n\n\nCAUSE\nThe customer had previously disabled the autostart on several applications to improve the Portal startup time\n\nENVIRONMENT\nPortal 8.0.0.1\nWindows\n\nDIAGNOSING THE PROBLEM\nfrom ConfigTrace.log...\n\nWed Nov 19 16:49:42 CST 2014\nTarget started: import-nodes\n\nimport-nodes:\n--- Exception Thrown ---\nC:\\Portal8\\PortalServer\\jcr\\wp.content.repository.install\\config\\include\ns\\jcr.install_cfg.xml:826: com.ibm.icm.jcr.task.TaskException:\nTASK001X: Remote task execution failed with response code 404 due to\nexception : Not Found . Please check the server log for more\ninformation.\nat\ncom.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:\n840)\nat\norg.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)\n\n...\n\nCaused by: com.ibm.icm.jcr.task.TaskException: TASK001X: Remote task\nexecution failed with response code 404 due to exception : Not Found .\nPlease check the server log for more information.\nat\ncom.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:\n825)\n... 75 more\n\nFrom here I reviewed the SystemOut.log at the same timestamp and see\nthe following...\n\n[11/19/14 16:49:43:804 CST] 00000042 filter E\ncom.ibm.ws.webcontainer.filter.FilterInstanceWrapper doFilter\nSRVE8109W: Uncaught exception thrown by filter Extensible Filter:\njava.io.FileNotFoundException: SRVE0190E: File not found:\n/jcr/remotetask\nat\ncom.ibm.ws.webcontainer.extension.DefaultExtensionProcessor._processEDR(\nDefaultExtensionProcessor.java:893)\nat\ncom.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.processEDR(D\nefaultExtensionProcessor.java:874)\n\nBoth of these messages seems to indicate a problem with the WCM\nstartup. This code is contained in the following\napplication....JavaContentRepository.ear.\n\nLooking at your last Portal startup I saw this below which occurs\nduring the wcm application startup....\n\n[11/19/14 15:57:54:566 CST] 00000009 ApplicationMg A WSVR0200I:\nStarting application: wcm\n\n....\n\n[11/19/14 16:00:36:812 CST] 00000005 TimeoutManage I WTRN0006W:\nTransaction\n00000149CA10760B000000012830B348BBD991CDC4031D0DFCED27CDD500F13F7FC95B79\n00000149CA10760B000000012830B348BBD991CDC4031D0DFCED27CDD500F13F7FC95B79\n00000001 has timed out after 120 seconds.\n[11/19/14 16:00:36:831 CST] 00000005 TimeoutManage I WTRN0124I: When\nthe timeout occurred the thread with which the transaction is, or was\nmost recently, associated was Thread[server.startup : 0,5,main]. The\nstack trace of this thread when the timeout occurred was:\njava.lang.Thread.blockedOn(Thread.java:1076)\nsun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)\nsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce\nssorImpl.java:37)\njava.lang.reflect.Method.invoke(Method.java:611)\n\nKnowing this I further reviewed the SystemOut.log to see where the JCR\nweb module gets loaded during startup....it should begin like this...\n\nSRVE0169I: Loading Web Module: JCRContentRepository.\n\nYour startup does not have this. This prompted me to review the\ndeployment.xml from the JavaContentRepository application directory at\nthis location...\n\nPortal8/wp_profile/config/cells/C001389391Cell/applications/JavaContentR\nepository.ear/deployments/JavaContentRepository/deployment.xml\n\nThe contents show the following...\n\n<targetMappings xmi:id=\"DeploymentTargetMapping_1335003370698\"\nenable=\"false\" target=\"ServerTarget_1335003370698\"/>\n\nThe enable=false means that you have this application set to not\nautostart. Because of this it is not starting during Portal startup\nand therefore is not available when the config task attempts to\ncommunicate with it during the upgrade...and therefore causes the\nproblem.\n\nRESOLVING THE PROBLEM\nPlease make the following change in the WAS Admin Console...\nApplications > WebSphere enterprise applications >\nJavaContentRepository > Target specific application status > Check the\nbox for the WebSphere_Portal server > Click Enable Auto Start > Save\nchanges > restart Portal\n\nAfter making this change please attempt the CF upgrade again."
}
] |
TRAIN_Q459 | Help with Security Bulletin: IIB is affected by Open Source Apache Tomcat Vulnerabilities (CVE-2017-12617,CVE-2017-12615)
I need to understand details regarding Security Bulletin: IBM Integration Bus is affected by Open Source Apache Tomcat Vulnerabilities (CVE-2017-12617,CVE-2017-12615). Where can I find this information? | - | true | [] |
TRAIN_Q460 | How do I transfer my SPSS 24 license key to a new computer?
I need to transfer my SPSS 24 license key to a new computer. I was able to download IBM® SPSS® Statistics Standard GradPack 24 for Windows (12-Mo Rental) onto the new computer, but every time I put in the activation code, I am met with this error message:
Authorization failed.: You are not allowed to generate any more new licenses.
End Of Transaction.
No additional authorizations are permitted on this code.
What should I do?
This dW Answers question is about an IBM document with the Title:
SPSS Student Version and Graduate Pack Resources | For installation & licensing issues on Student version and Graduate pack, contact your vendor. | false | [
{
"filename": "swg21592093.txt",
"text": "Title: IBM SPSS Student Version and Graduate Pack Resources - United States\n\nText:\nSPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http://www.hearne.software/Software/SPSS-Grad-Packs-for-Students-by-IBM/FAQ] \n * On the Hub [http://onthehub.com/] \n * StudentDiscounts.com [http://studentdiscounts.com/contact-us.aspx] \n * JourneyEd [https://www.journeyed.com/contact] \n * thinkEDU [https://thinkedu.desk.com/] \n * Studica [http://www.studica.com/technical-support]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version"
}
] |
TRAIN_Q461 | How can I configure TIP to clear the ARGUS cache without having to do a system restart?
Argus stores it's role authorizations in memory cache, and is not cleaned out unless the TIP is restarted. The "cacheTime" variable in the configFile.xml configuration file controls this, which is set to -1 by default. If the number of TIP roles is high, it can cause Java OOM errors. | To resolve this issue you need to configure 'cacheTime' to non -1 value. Initially we suggest setting the value to 1200000, which is 20 minutes. After the change you will have to restart the TIP server, normally server1. | false | [
{
"filename": "swg21657452.txt",
"text": "Title: IBM Tivoli Integrated Portal hangs because of Argus java.lang.OutOfMemory. - United States\n\nText:\ncacheTime; config.xml; Argus; TIP cache; TIPL2CONF; TIPL2PERF TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Argus stores it's role authorizations in memory cache, and is not cleaned out unless the TIP is restarted. The \"cacheTime\" variable controls this, which is set to -1 by default. If the number of TIP roles is high, it can cause Java OOM errors. \n\nSYMPTOM\nTIP hangs. SystemOut.log file shows Java.lang.OutOfMemoryError: \n\n[10/2/13 9:27:54:838 CDT] 0000002a webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: \n[Servlet Error]-[/secure/isclite/tiles/nop.jsp]: java.lang.OutOfMemoryError: Java heap space at java.lang.Object.clone(Native Method)\n\n\nCAUSE\nBy default, the ARGUS cache will not get cleaned up unless the TIP server is restarted. This normally will give the system good runtime performance. However, in cases where a large number of user/role mappings are defined, the system may run into Java memory issues causing Java OutOfMemory outages.\n\nThe cacheTime we are talking about here is Argus cache. The is used for the way the role authorizations are stored in memory by Argus and nothing related to LDAP or SSO. The Argus cache time by default we ship with in TIP is -1 which means the cache will not get cleaned up till we re-start the server. \n\nError from the <TIP_HOME>/profiles/TIPProfile/logs/server1/SystemOut.log\n\n[10/2/13 9:27:54:838 CDT] 0000002a webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: \n[Servlet Error]-[/secure/isclite/tiles/nop.jsp]: java.lang.OutOfMemoryError: Java heap space at java.lang.Object.clone(Native Method)\n\n\nENVIRONMENT\nall environments\n\n\n\nDIAGNOSING THE PROBLEM\nJava heapdump files will be created in the <TIP_HOME>/profiles/TIPProfile directory. \n\nheapdump.20131022.144244.20034001.phd \n\nThe Systemout.log will have have errors similar to this: \n\n\n[10/2/13 9:27:54:838 CDT] 0000002a webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: \n[Servlet Error]-[/secure/isclite/tiles/nop.jsp]: java.lang.OutOfMemoryError: Java heap space at java.lang.Object.clone(Native Method) \n\n\nUsing the memory heap dump analysis shows that Argus is the problem, specifically the instance shown inside the red line in the output of the Java memory analyzer below: \n\n \n\n[/support/docview.wss?uid=swg21657452&aid=1] [/support/docview.wss?uid=swg21657452&aid=1]\n\nYou can also check the cacheTime variable in the <TIP_HOME>/profiles/TIPProfile/config/cells/TIPCell/commonauthz/config.xml file to confirm if it's set to \"-1\", which means the Argus cache will not get cleaned up unless the TIP server is restarted.\n\n\nRESOLVING THE PROBLEM\nThe cacheTime value in config.xml is in milliseconds. TIP is shipped with the initial value of -1, which means the Argus cache will not be cleared out unless TIP restart. To resolve this issue you need to configure 'cacheTime' to non -1 value. Initially we suggest setting the value to 1200000, which is 20 minutes. After the change you will have to restart the TIP server, normally server1. \n\nNOTE: The cacheTime variable was added in TIP version 2.2.0.0."
}
] |
TRAIN_Q462 | Security Bulletin: IBM MQ and IBM MQ Appliance Shared memory leak caused by MQ applications using dynamic queues (CVE-2017-1283)
I need to understand details regarding Security Bulletin: IBM MQ and IBM MQ Appliance Shared memory leak caused by MQ applications using dynamic queues (CVE-2017-1283). Where can I find this information? | CVEID: CVE-2017-1283 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1283]
DESCRIPTION: IBM WebSphere MQ could allow an authenticated user to cause a shared memory leak by MQ applications using dynamic queues, which can lead to lack of resources for other MQ applications.
CVSS Base Score: 3.1
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/125144 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125144] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L) | false | [
{
"filename": "swg22003852.txt",
"text": "Title: IBM Security Bulletin: IBM MQ and IBM MQ Appliance Shared memory leak caused by MQ applications using dynamic queues. (CVE-2017-1283) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n Shared memory leak caused by MQ applications using dynamic queues. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-1283 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1283]\nDESCRIPTION: IBM WebSphere MQ could allow an authenticated user to cause a shared memory leak by MQ applications using dynamic queues, which can lead to lack of resources for other MQ applications.\nCVSS Base Score: 3.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/125144 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125144] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ V8\nIBM MQ 8.0.0.0 - 8.0.0.6 maintenance levels\nIBM MQ Appliance V8\nIBM MQ Appliance 8.0.0.0 - 8.0.0.6 maintenance levels\nIBM MQ V9\nIBM MQ 9.0.0.0 - 9.0.0.1 maintenance levels\nIBM MQ V9 CD\nIBM MQ 9.0.1 - 9.0.3 releases\nIBM MQ Appliance V9 CD\nIBM MQ Appliance 9.0.1 - 9.0.3\n\nREMEDIATION/FIXES\nIBM MQ V8 \n\nApply Fix Pack 8.0.0.7 [https://www-01.ibm.com/support/docview.wss?uid=swg22005832]\nIBM MQ Appliance V8\nApply Fix Pack 8.0.0.7 for MQ Appliance [https://www-01.ibm.com/support/docview.wss?uid=swg22005832]\nIBM MQ V9\nApply Fix Pack 9.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24044038]\nIBM MQ V9 CD\nUpgrade to IBM MQ 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348]\nIBM MQ Appliance V9 CD\nUpgrade to IBM MQ Appliance 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348]\n\nWORKAROUNDS AND MITIGATIONS\nNone.\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 14 Nov 2017: Initial Version \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY."
}
] |
TRAIN_Q463 | Can Portal prevent the usage of simultaneous logins with the same userID?
Is it possible for WebSphere Portal to limit the usage of a userID to one authenticated session as a time? In other words, prevent authenticating to Portal as "user1" from one browser and then simultaneously authenticating to Portal again as "user1" from another browser? | WebSphere Portal has no built-in mechanism or configuration setting to limit the number of times a user id may log in. Unexpected behavior may occur if the same id is logged in more than once and this is not supported.
"ConcurrentModificationException" and other errors may be logged.
Most of the related issues were resolved in WebSphere Portal 5.1. However, you may still encounter exceptions or side-effects if you access the Portal in multiple browser windows using the same user id, whether or not the authentication requests take place on separate physical hosts.
It may be possible to prevent multiple logins by writing custom "tracking code." Contact IBM Services for assistance to undertake such a project. WebSphere Portal Development does not have any sample code.
If you wish to write your own code, some of the issues to be aware of are (this is not an inclusive list):
-- Multiple logins may take place on different nodes in a cluster. This means some cluster-wide mechanism would have to be in place to keep track of the logged-in users. Look at the WebSphere Application Server DistributedMap interface.
-- There should be a fail-safe way to track user logout (explicit logout and session timeout). Using a session listener might be a possibility.
-- If a user closes the browser without logging out, that user must wait for a session timeout before logging in again. Otherwise, there should be a "force simultaneous login" option in the login user interface.
For load testing, use unique user ids or virtual users. | false | [
{
"filename": "swg21227799.txt",
"text": "Title: IBM Multiple logins using the same user ID - United States\n\nText:\nConcurrentModificationException; log in; login; multiple; userid; multiple login TECHNOTE (FAQ)\n\nQUESTION\n \"ConcurrentModificationException\" and other errors may occur if the same user id is logged in to IBM WebSphere Portal multiple times.\n\n\nANSWER\nWebSphere Portal has no built-in mechanism or configuration setting to limit the number of times a user id may log in. Unexpected behavior may occur if the same id is logged in more than once and this is not supported. \n\n\"ConcurrentModificationException\" and other errors may be logged.\n\nMost of the related issues were resolved in WebSphere Portal 5.1. However, you may still encounter exceptions or side-effects if you access the Portal in multiple browser windows using the same user id, whether or not the authentication requests take place on separate physical hosts.\n\nIt may be possible to prevent multiple logins by writing custom \"tracking code.\" Contact IBM Services for assistance to undertake such a project. WebSphere Portal Development does not have any sample code.\n\nIf you wish to write your own code, some of the issues to be aware of are (this is not an inclusive list):\n\n-- Multiple logins may take place on different nodes in a cluster. This means some cluster-wide mechanism would have to be in place to keep track of the logged-in users. Look at the WebSphere Application Server DistributedMap interface.\n\n-- There should be a fail-safe way to track user logout (explicit logout and session timeout). Using a session listener might be a possibility. \n\n-- If a user closes the browser without logging out, that user must wait for a session timeout before logging in again. Otherwise, there should be a \"force simultaneous login\" option in the login user interface.\n\nFor load testing, use unique user ids or virtual users.\n\nRELATED INFORMATION\n Portal 6.1/7.0: Authentication Filters [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/index.jsp?topic=/com.ibm.wp.ent.doc_v615/admin/adauthflt.html]\nPortal 6.1: Custom Login Portlet [https://www.ibm.com/support/docview.wss?uid=swg21358508]\nRestricting Multiple Sessions [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Restricting_Multiple_Sessions_in_WebSphere_Portal]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Organizational Productivity- Portals & Collaboration WebSphere Portal End of Support Products General AIX, HP-UX, Linux, Solaris, Windows 7.0, 6.1.5, 6.1, 6.0, 5.1"
}
] |
TRAIN_Q464 | Why is SAP agent user getting locked for V7.1.1 FP1?
We have ITCAM agent for SAP, V 7.1.1 FP1 IF1. Every few weeks, the agent user appears to be getting locked because it starts using wrong password, and SAP basis team has to unlock it, and then it starts to work again. Is there a solution for this problem? | - | true | [] |
TRAIN_Q465 | Why do I get a nullPointerException from the default portal theme? EJCBD0021E
I can see the following nullPointerException in the logs:
EJCBD0021E: The URI [dav:fs-type1/themes/Portal8.0/theme.html] and parameters [['themeURI'=['dav:fs-type1/themes/Portal8.0/theme.html'], 'mime-type'=['text/html']]] could not be processed: [EJCBD0021E: The URI [dav:fs-type1/themes/Portal8.0/nls/theme_en.html] and parameters [['themeURI'=['dav:fs-type1/themes/Portal8.0/theme.html'], 'mime-type'=['text/html']]] could not be processed: [EJCBD0019E: The data source identified by the URI [co:head] and parameters []] could not be processed: [java.lang.NullPointerException]]]
Additional review of the logs shows the entry:
Caused by: java.lang.NullPointerException at com.ibm.wps.resolver.impl.ExtensionTracker.(ExtensionTracker.java: 481) at com.ibm.wps.resolver.impl.ExtensionTracker.(ExtensionTracker.java: 502) at com.ibm.wps.resolver.impl.ExtensionTracker.(ExtensionTracker.java: 518) at com.ibm.wps.resolver.resource.BlackWhiteListFactoryOnExtensionRegistry.< init>(BlackWhiteListFactoryOnExtensionRegistry.java:226) ... 136 more | the temporary directory for extension points has become corrupted. This can happen after a server is upgraded. | false | [
{
"filename": "swg21459952.txt",
"text": "Title: IBM WebSphere Portal startup fails with EJCBC0002E: The service [<serviceName>] could not be located. - United States\n\nText:\nEJCBC0002E; EJPFD0016E; extensionregistry; CORFriendlySelectionServiceHome TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nWhen starting the WebSphere_Portal server, startup throws an exception: EJCBC0002E: The service could not be located. \n\nSYMPTOM\nIn the SystemOut.log, the following exception can be seen at the time the wps.ear application is started:\n===========================\n[1/13/11 11:00:56:875 EST] 00000015 Servlet E com.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of service failed.\ncom.ibm.portal.resolver.exceptions.LocalizedIOException: EJCBC0002E: The service [com.ibm.wps.resolver.friendly.CORFriendlySelectionServiceHome] could not be located.\nat com.ibm.portal.resolver.helper.eclipse.Platform.createInstance(Platform.java:201)\nat com.ibm.portal.resolver.helper.eclipse.Platform.createInstance(Platform.java:128)\nat com.ibm.wps.resolver.friendly.service.PortalFriendlySelectionBootstrapService.init(PortalFriendlySelectionBootstrapService.java:197)\nat com.ibm.wps.services.Service.init(Service.java:107)\nat com.ibm.wps.services.Service.init(Service.java:83)\nat com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:363)\n===========================\n\nThe service name in this case is \"com.ibm.wps.resolver.friendly.CORFriendlySelectionServiceHome\", but the name could vary. \n\nYou may also see warnings for various applications like this:\n\n===========================\n[1/13/11 11:00:54:250 EST] 00000015 RegistryResol W CWXRS0023W: Extension Point (com.ibm.portal.model.skinlistprovider) not available for Extension: com.ibm.wps.engine.standardSkinListProvider\n[1/13/11 11:00:54:252 EST] 00000015 RegistryResol W CWXRS0023W: Extension Point (com.ibm.portal.model.themelistprovider) not available for Extension: com.ibm.wps.engine.standardThemeListProvider\n[1/13/11 11:00:54:269 EST] 00000015 RegistryResol W CWXRS0023W: Extension Point (com.ibm.portal.resolver.model.ContentNodeLinkGenerator) not available for Extension: com.ibm.wps.ai.rest.AIContentNodeLinkGenerator\n[1/13/11 11:00:54:278 EST] 00000015 RegistryResol W CWXRS0023W: Extension Point (com.ibm.portal.resolver.model.NavigationNodeLinkGenerator) not available for Extension: com.ibm.wps.ai.rest.AINavigationNodeLinkGenerator\n===========================\n\n\nCAUSE\nThese messages indicate that the the temporary directory for extension points has become corrupted. This can happen after a server is upgraded.\n\n\nRESOLVING THE PROBLEM\nTo resolve this problem, you can do the following: \n\n\n1. Stop the WebSphere_Portal server\n\n2. Delete the contents of the following directory:\n\n<wp_profile root>/temp/<node name>/WebSphere_Portal/_extensionregistry \n\n3. Start the WebSphere_Portal server."
}
] |
TRAIN_Q466 | What happens if I lost my seed and salt value?
In ISDS, what happens if I lost my seed and salt value?
This dW Answers question is about an IBM document with the Title:
Open Mic Webcast: Configuring SDS 8.0.1 Virtual Appliance with a remote DB2 database - Tuesday, 17 Jan 2017 [presentation slides are attached; includes link to replay] | There is NO way to recover the seed value used during the instance creation if it has been lost. The only workaround is to create a new instance with a new encryption seed value and then use the db2ldif and ldif2db utilities to export and import data respectively. These utilities can be supplied with the new encryption seed and the salt value of the new instance. Thus the data would be preserved(alongwith the passwords) on this new instance. | false | [
{
"filename": "swg21244655.txt",
"text": "Title: IBM Seed value used during the instance creation is lost : Recovery procedure - United States\n\nText:\nseed lost; idsgendirksf; Encryption Seed Value; key stash file TECHNOTE (TROUBLESHOOTING)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n English \n\nPROBLEM(ABSTRACT)\n Generating key stash file if the seed value which was used at the time of instance creation has been lost then there is no way to recover this seed value. \n\nRESOLVING THE PROBLEM\n \n\nThere is NO way to recover the seed value used during the instance creation if it has been lost. The only workaround is to create a new instance with a new encryption seed value and then use the db2ldif and ldif2db utilities to export and import data respectively. These utilities can be supplied with the new encryption seed and the salt value of the new instance. Thus the data would be preserved(alongwith the passwords) on this new instance.\n\nHere are the steps to follow:\n\n1. Set up a new instance says \"newinst\".\n\n$> idsicrt -I newinst -e thisismyencryptionseed -l (/home/newinst) -n\n\n$> idscfgdb -I newinst -w ldap -a newinst -t newinst -l (/home/newinst) -n\n\n$> idscfgsuf -s \"o=ibm,c=us\" -I newinst -n\n\n$> idsdnpw -u cn=root -p root -I newinst -n\n\n2. Note the encryption seed - \"thisismyencryptionseed\". Let us call this new_encryptionseed\n\n3. Once this new instance is setup note down the salt value generated by the new server instance by searching for \"cn=crypto,cn=localhost\".\n\n$> ldapsearch -D <administrator DN> -w <administrator password> -b \"cn=crypto,cn=localhost\" -s base objectclass=* ibm-slapdCryptoSalt\n\nLet us call this value: new_saltvalue\n\n4. Lets assume that the instance name with the forgotten encryption seed is \"oldinst\"\n\n5. Use the db2ldif utility on the instance with the forgotten encryptionseed, oldinst with the following options -\n\n$> db2ldif -o outputfile -I oldinst -k new_encryptionseed -t new_saltvalue\n\n6. Once this step is successfully completed the entire data from \"oldinst\" would be dumped in outputfile.\n\n7. Use the utilities like ldif2db to re-load all the data into the new server instance.\n\n\n\n\n\n\n\nHISTORICAL NUMBER"
}
] |
TRAIN_Q467 | How can we change the password for LDAP bind user?
We need to change our LDAP bind user due to security requirement. Is there any documentation for the procedure? | The Directory Service user account and password are normally used in two product components: FileNet Enterprise Manager (FEM), and the application server. A coordinated update procedure should be followed when there is a need to change the user account and/or password. This procedure applies to FileNet Content Engine 4.x and above. | false | [
{
"filename": "swg21442694.txt",
"text": "Title: IBM Procedure to change the username and/or password for the FileNet Content Engine Directory Service Account, including the bootstrap user - United States\n\nText:\nchange; user; password; fem; directory service; bootstrapconfig; bootstrap user TECHNOTE (FAQ)\n\nQUESTION\n How do you change the user and/or password for Directory Service Account used by the Content Engine? \n\nANSWER\nThe Directory Service user account and password are normally used in two product components: FileNet Enterprise Manager (FEM), and the application server. A coordinated update procedure should be followed when there is a need to change the user account and/or password. This procedure applies to FileNet Content Engine 4.x and above. \n\n * \n * Note: \n * \n * \n\n\nIf the same user account is also used as the CE Bootstrap user, the corresponding user in the BootstrapConfig.properties needs to change as well. For changing the GCD admin user/password in BootstrapConfig.properties specifically, refer to this documentation: \nhttp://publib.boulder.ibm.com/infocenter/p8docs/v4r5m1/index.jsp?topic=/com.ibm.p8.doc/admin/security/sec_how_change_bootstrap_pwd.htm [http://publib.boulder.ibm.com/infocenter/p8docs/v4r5m1/index.jsp?topic=/com.ibm.p8.doc/admin/security/sec_how_change_bootstrap_pwd.htm] \n\n\n1. Launch FEM and the application server's administrative console. \na. Login to FEM using the Directory Service account. \nb. Login to the application server administrative console with an administrator account. \n\nImportant: Do not close above two applications until you have completed step 5 below. \n\n\n2. Make LDAP account changes: \na. Change the password for an existing account on the LDAP server - Using LDAP interface, change the password for the CE Directory Service account. \nOR \nb. Create a new user account on the LDAP server for the CE Directory Service account. \n\n\n3. Add new user (if applicable), to FEM \nIf the bind user is also the CE admin user, then the bind user will need to be added to all the existing objects in the P8 domain. Please read Update object store with new users and groups [http://publib.boulder.ibm.com/infocenter/p8docs/v4r5m1/index.jsp?topic=/com.ibm.p8.doc/admin/security/sec_how_update_os.htm] for instructions \n\n\n4. Change Directory Configuration bind user in FEM \nUsing FEM (step 1a above), go to Domain properties > Directory Configuration > Select Directory Configuration > click on the Modify button > General Tab: \na. Modify the Directory Service User with new user's full distinguish name (DN) \nb. Click on Change password check box > change to a new password > click OK. \n\nAt this point you will be presented a dialog box with following message: \n“These changes require the application server to be restarted. Please restart the application server to incorporate these changes” \n\nclick OK > click OK \n\nImportant: Do not restart the application server until you have completed step 5 below. \n\n\n5. Change the user in the application server's directory configuration \n\n- For Websphere, in the WebSphere Administrative Console, go to Global Security > click on Configure under User Account Repository > Modify Bind Distinguished Name (DN) > Modify Bind Password > click OK and Save changes \n\n- For WebLogic go to Security Realms > myrealm > Providers > ldap provider and click on \"Provider Specific\" tab in WebLogic Admin Console. Change \"Principal\" and \"Credential\". \n\n- For JBoss go to <JBoss Home>\\server\\<CE Server>\\conf directory and edit \"login-config.xml\". \nFind \"FileNet\" application-policy and in login module change bindDN/bindCredential. \n\n\n6. Changing the CE Bootstrap user \n\nFor CE 4.5.x and above: \na. In the Configure Bootstrap Properties task, set the Bootstrap Operation property to Modify Existing. \nb. Confirm that the Bootstrapped EAR file property contains the path to the bootstrap file you need to edit. \nc. Change the Bootstrap user password. Use Configuration Manager's features to save and run the task. \nd. Run Configuration Manager's Deploy Application. \n\nFor CE 4.0: \nNote: This step is needed only if the GCD user name is the same as the Directory Service account. Note that the example below is for a Windows environment. \n\n- For WebSphere \na. Open command prompt window, go to folder where EAR file reside (it differs depending on CE version). For example, in CE 4.5.1, go to \"<CE Home> \\ tools \\ configure \\ profiles \\ <profile> \\ ear\" \nb. Backup Engine-ws.ear \nc. Execute the command below: \n\njava –jar “c:\\program files\\FileNet\\ContentEngine\\lib\\BootStrapConfig.jar” –e Engine-ws.ear --username <username> --password <password> \n\nd. Since the Engine-ws.ear file has been deployed in the WebSphere's installedApps path, the Bootstrap file need to be copied to the path manually. Extract the props.jar file from the ear file by utility such as Winzip, copy the props.jar file to theinstalledApps location - “<WebSphere Home>\\ AppServer\\ profiles \\ <profile name> \\ InstalledApps \\<serverNodecell> \\ FileNetEngine.ear \\ APP-INF \\ lib \\\" \n\nNote that an alternative to copying the props.jar file is to uninstall and re-install the updated ear file in WebSphere. \n\n- For WebLogic \na. Open command prompt window, go to folder - \"<WebLogic home> \\ user_projects \\ domains \\ <domain> \\ servers \" \nb. Backup FileNetEngine.ear \nc. Execute the command below: \n\njava –jar “c:\\program files\\FileNet\\ContentEngine\\lib\\BootStrapConfig.jar” –e Engine-wl.ear --username <username> --password <password> \n\n- For JBoss \na. Open command prompt window, go to folder - \"<JBoss Home> \\ server \\ <server> \\ deploy \\\" \nb. Backup FileNetEngine.ear \nc. Execute the command below: \n\njava –jar “c:\\program files\\FileNet\\ContentEngine\\lib\\BootStrapConfig.jar” –e Engine-jb.ear --username <username> --password <password> \n\n\n7. Remove cached files in the application server \n- Close FileNet Enterprise Manager (Step 1a) \n- Close Administrative Console (Step 1b) \n- Stop the application server \n- Remove the cached FileNetEngine directory in the application server. \nFor example, the default windows path on Websphere 6.0 is \n\"C:\\program files\\Websphere\\AppServer\\profiles\\<profile name>\\temp\\<server node>\\ \n<server>\\FileNetEngine\" \n\n\n8. Restart the application server, and login to FEM using the new user and password. \n\n\n9. Troubleshooting \n\nIf CE fails to start due to mistakes in the above procedures, you may not be able to redo the change through these procedures because FEM will fail to run. \nIn this case, you can do the following: \n\n- Back out the change made to the GCD database in step 3 by deleting the latest row in the FNGCD table. \n- Back out the change made to the application server in step 4 by redoing the procedure with the previous user. \n- Back out the change made to the BootstrapConfig.properties file's GCD user by using the backup EAR file \n- Restart the application server, and login to FEM using the previous user."
}
] |
TRAIN_Q468 | How can I alleviate performance problems with the octigate database?
ITCAM-related question: How can I alleviate performance problems with the octigate database?
| - | true | [] |
TRAIN_Q469 | Help with Multiple vulnerabilities have been identified in WebSphere Application Server shipped with WSRR
I need to understand details regarding Multiple vulnerabilities have been identified in WebSphere Application Server shipped with WebSphere Service Registry and Repository ( CVE-2011-4343). Where can I find this information? | CVEID: CVE-2011-4343 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4343]
DESCRIPTION: Apache MyFaces could allow a remote attacker to obtain sensitive information. An attacker could exploit this vulnerability using specially crafted parameters to inject EL expressions into input fields mapped as view parameters and obtain sensitive information.
CVSS Base Score: 5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/132287 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132287] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N) | false | [
{
"filename": "swg22010993.txt",
"text": "Title: IBM Security Bulletin: Multiple vulnerabilities affect Java Server Faces (JSF) used by WebSphere Application Server shipped with Jazz for Service Management (CVE-2017-1583, CVE-2011-4343) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are two potential information disclosure vulnerabilities that affects the Java Server Faces (JSF) component used by WebSphere Application Server. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-1583 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1583]\nDESCRIPTION: IBM WebSphere Application Server could allow a remote attacker to obtain sensitive information caused by improper error handling by MyFaces in JSF.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/132342 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132342] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) \n\n\nCVEID: CVE-2011-4343 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4343] \nDESCRIPTION: Apache MyFaces could allow a remote attacker to obtain sensitive information. An attacker could exploit this vulnerability using specially crafted parameters to inject EL expressions into input fields mapped as view parameters and obtain sensitive information. \nCVSS Base Score: 5 \nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/132287 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132287] for the current score \nCVSS Environmental Score*: Undefined \nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nJazz for Service Management version 1.1.0 - 1.1.3\n\nREMEDIATION/FIXES\n \n\nPrincipal Product and Version(s) Affected Supporting Product and Version Affected Supporting Product Security Bulletin Jazz for Service Management version 1.1.0 - 1.1.3 Websphere Application Server Full Profile 8.5.5 Security Bulletin: Multiple vulnerabilities affect Java Server Faces (JSF) used by WebSphere Application Server (CVE-2017-1583, CVE-2011-4343) [http://www-01.ibm.com/support/docview.wss?uid=swg22008707] WORKAROUNDS AND MITIGATIONS\nPlease refer to WAS iFix\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 27-November-2017: Original version published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY."
}
] |
TRAIN_Q470 | Does Logout button get disabled in ICM for SSO with Tivoli Access Manager ?
Does Logout button get disabled in ICM for SSO with Tivoli Access Manager ? | IBM Content Navigator disables the Log Out option under SSO environments. However, under some SSO environments or desktop load scenarios, such as SPNEGO/Kerberos on a WebLogic Application Server, IBM Content Navigator enables the Log Out option.
If the Log Out option is enabled but does not work correctly in your SSO environment, you can remove the Log Out option by customizing the banner user session context menu that is used by your desktop configuration. | false | [
{
"filename": "swg27042940.txt",
"text": "Title: IBM Content Navigator known issue: In a SPNEGO/Kerberos Single sign-on environment, IBM Content Navigator the Log Out option is enabled - United States\n\nText:\n PRODUCT DOCUMENTATION\n\nABSTRACT\n In a SPNEGO/Kerberos single sign-on (SSO) environment, your IBM Content Navigator session shows the Log Out option as enabled when you select the drop-down menu on the user name. However, the option should be disabled. \n\nCONTENT\nIBM Content Navigator disables the Log Out option under SSO environments. However, under some SSO environments or desktop load scenarios, such as SPNEGO/Kerberos on a WebLogic Application Server, IBM Content Navigator enables the Log Out option.\n\n\n\n\nIf the Log Out option is enabled but does not work correctly in your SSO environment, you can remove the Log Out option by customizing the banner user session context menu that is used by your desktop configuration. \n\nTo remove the Log Out option: \n\n 1. In the administration tool, select Menus. \n 2. Enter \"User\" in the Name contains filter field. \n 3. Select the Default banner user session context menu and click Copy. \n 4. Enter a name for the new menu such as \"Banner user session context menu - no Log Out option\". \n 5. Remove the Log Out from the Selected list. \n 6. Save the new menu. \n 7. Open the Desktops configuration, then open your desktop configuration. \n 8. Select the Menus tab and scroll to the Feature Context Menus section. \n 9. Select the new menu that you created for the Banner user session context menu menu type. \n 10. Save your desktop. \n\n\nThe change to the menus takes effect when the modified desktop is reloaded. \n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Case Manager AIX, Linux, Linux on System z, Windows 5.2.1.0"
}
] |
TRAIN_Q471 | Why can't I search groups after upgrading to WebSphere Application Server 8.5.5.10?
Why can't I search groups after upgrading to WebSphere Application Server 8.5.5.10? | PI69518 resolves the following problem:
ERROR DESCRIPTION:
After upgrade to 8.5.5.10, there are cases when group
search fails from "Users and Groups" -> "Administrative
Groups" panel. When it happens in GUI, the same issue
happens with AdminTask listRegistryGroups command. | false | [
{
"filename": "swg24042833.txt",
"text": "Title: IBM PI69518:group search fails with a classcast exception after upgrade to 8.5.5.10 - United States\n\nText:\nPI69518; PI69518; PI69518 DOWNLOADABLE FILES\n\nABSTRACT\n group search fails with a classcast exception after upgrade to 8.5.5.10 \n\nDOWNLOAD DESCRIPTION\nPI69518 resolves the following problem:\n\nERROR DESCRIPTION: \nAfter upgrade to 8.5.5.10, there are cases when group \nsearch fails from \"Users and Groups\" -> \"Administrative \nGroups\" panel. When it happens in GUI, the same issue \nhappens with AdminTask listRegistryGroups command. \n\nSeeing the following in systemout.log: \n[9/20/16 15:37:21:077 EDT] 00000076 GroupDetailAc W \nlistRegistryGroups: Command not successful: \njava.lang.ClassCastException: javax.management.ObjectName \nincompatible \nwith javax.management.AttributeList \n\n************************************************** \n\nIn traces we see stack: \n\n[9/20/16 15:36:05:658 EDT] 00000076 SecurityRealm 3 exception \ncaught \njava.lang.ClassCastException: \njavax.management.ObjectName incompatible with \njavax.management.AttributeList \nat \ncom.ibm.ws.security.admintask.securityDomain.SecurityRealmProvid\ner.getLD \nAPProps(SecurityRealmProvider.java:1420) \nat \ncom.ibm.ws.security.admintask.securityDomain.SecurityRealmProvid\ner.getLD \nAPList(SecurityRealmProvider.java:1363) \nat \ncom.ibm.ws.security.admintask.securityDomain.SecurityRealmProvid\ner.listR \negistryGroups(SecurityRealmProvider.java:402) \nat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) \nat \nsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor\nImpl.jav \na:95) \nat \nsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod\nAccessor \nImpl.java:56) \nat java.lang.reflect.Method.invoke(Method.java:620) \nat \ncom.ibm.websphere.management.cmdframework.provider.SimpleCommand\nProvider \n.executeReal(SimpleCommandProvider.java:156) \nat \ncom.ibm.websphere.management.cmdframework.provider.SimpleCommand\nProvider \n.execute(SimpleCommandProvider.java:142) \nat \ncom.ibm.websphere.management.cmdframework.provider.SimpleAdminCo\nmmand.ex \necute(SimpleAdminCommand.java:57) \n\nLOCAL FIX: \nnone \n\nPROBLEM SUMMARY\n\nUSERS AFFECTED:\nAll users of IBM WebSphere Application\nServer\n\nPROBLEM DESCRIPTION:\njava.lang.ClassCastException when\ngroup search is performed.\n\nRECOMMENDATION:\nNone\n\nThere was a bug in the code that uses a registry object that\nmay not contain necessary attributes for the group search and\ncauses ClassCastException.\n\nPROBLEM CONCLUSION: \nThe bug was fixed in the code to correct the exception. \n\nThe fix for this APAR is currently targeted for inclusion in \nfix pack 8.5.5.11. Please refer to the Recommended Updates \npage for delivery information: \nhttp://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nPREREQUISITES\nNone\n\nINSTALLATION INSTRUCTIONS\nPlease review the readme.txt for detailed installation instructions.\n\nURL LANGUAGE SIZE(Bytes) V85 Readme [ftp://public.dhe.ibm.com/software/websphere/appserv/support/fixes/PI69518/8.5.5.10/readme.txt] US English 6584 \nDOWNLOAD PACKAGE\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 8.5.5.10-WS-WAS-IFPI69518 09-28-2016 US English 276737 HTTP [http://www-933.ibm.com/eserver/support/fixes/fixcentral/swgquickorder?fixes=8.5.5.10-WS-WAS-IFPI69518&productid=WebSphere%20Application%20Server&brandid=5] \nTECHNICAL SUPPORT\n Contact IBM Support using SR (http://www.ibm.com/software/support/probsub.html [http://www.ibm.com/software/support/probsub.html]), visit the WebSphere Application Server support web site (http://www.ibm.com/software/webservers/appserv/was/support/ [http://www.ibm.com/software/webservers/appserv/was/support/]), or contact 1-800-IBM-SERV (U.S. only). \n\n [/support/docview.wss?uid=swg24042833&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24042833&aid=2]Problems (APARS) fixed\nPI69518"
}
] |
TRAIN_Q472 | The Ping Probe will not start with SetUID configured
The Netcool OMNIbus Ping Probe will not start with SetUID configured. What should I check? | To enable non-root user to start the probe, you need to change the owner to root and permissions to setuid. And AIX ignores the LIBPATH setting when program runs as setuid root, so you also need to put either a copy of the required libraries, or a symbolic link to the required libraries in one of the trusted paths like /lib or /usr/lib. | false | [
{
"filename": "swg21499280.txt",
"text": "Title: IBM Unable to start Ping Probe by non-root user on AIX - United States\n\nText:\nPing probe; non root; start; permissions TECHNOTE (TROUBLESHOOTING)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n English \n\nPROBLEM(ABSTRACT)\n Ping probe fails to start when the probe is installed and started by non-root user. \n\nSYMPTOM\nThe following error is seen in the probe's log: \n\nError: E-P_P-002-038: Could not change euid: Operation not permitted\nError: E-P_P-002-017: IPv4 socket failed: specified action does not have access permission of the file\nError: E-P_P-002-037: This program can only be run by root, or it must be setuid root.\n\n\nCAUSE\nPing probe needs permissions which allow it to run as root and the LIBPATH setting should be changed.\n\n\nENVIRONMENT\nAIX\n\n\n\nRESOLVING THE PROBLEM\nTo enable non-root user to start the probe, you need to change the owner to root and permissions to setuid. And AIX ignores the LIBPATH setting when program runs as setuid root, so you also need to put either a copy of the required libraries, or a symbolic link to the required libraries in one of the trusted paths like /lib or /usr/lib. \n\n\n1. Change the owner to root and permissions to setuid.\ne.g\n# cd $OMNIHOME/probes/aix5/\n# chown root:root nco_p_ping\n# chmod +s nco_p_poing\n\n2. Put a symbolic link to the required libraries.\ne.g\n# cd /usr/lib\n\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libgsk*\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libPa_r.so\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libnetcool_r.so\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libslclient_r.so\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libOpl_r.so\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libsybct_r.so\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libsybcs_r.so\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libsybtcl_r.so\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libsybcomn_r.so\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libtre.a\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libsybintl_r.so\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libicuuc40.a\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libicui18n40.a\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libicudata40.a\n\n\nNote:\nThe required libraries can be seen by the following command:\n# dump -H $NCHOME/omnibus/platform/aix5/nco_p_ping\n\nNote:\nIf there are newer modules of the required libraries, it's better to create a symbolic link to the newer module.\ne.g\nRun\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libicui18n40.1.a\nrather than,\n# ln -s /opt/IBM/netcool/platform/aix5/lib/libicui18n40.a\n\nBut, please note that it would be better to create the symbolic links again whenever after you apply Fix pack for OMNibus core.\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli Netcool/OMNIbus Ping AIX All Versions"
}
] |
TRAIN_Q473 | Why Summarization and pruning are failing with SQL Error Code = -4220 on AIX_LPAR table?
Summarization and pruning are failing with SQL Error Code = -4220 on AIX_LPAR table. What's the fix?
| Update the invalid data with a valid UTF-8 character string. | false | [
{
"filename": "swg21684365.txt",
"text": "Title: IBM SqlException with message \"Caught java.io.CharConversionException.\" and ERRORCODE=-4220 - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When an application uses the IBM Data Server Driver for JDBC and SQLJ (also known as the JCC driver) and is connected to a database with code set UTF-8 (code page 1208), it throws an\nSqlException with message including \"Caught java.io.CharConversionException\" and ERRORCODE=-4220 if the data in a character column that it queries contains a sequence of bytes that is not a valid UTF-8 string. \n\nSYMPTOM\nAn exception is thrown similar to this: \n\n com.ibm.db2.jcc.am.SqlException: [jcc][t4][1065][12306][XXX.XXX.XXX] Caught java.io.CharConversionException. See attached Throwable for details. ERRORCODE=-4220, SQLSTATE=null\n[...]\nCaused by: java.nio.charset.MalformedInputException: Input length = XXX\n[...]\nCaused by: sun.io.MalformedInputException\nat sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:XXX)\n[...]\n\n\n\nCAUSE\nThe JCC driver throws the exception when data in a character column that it queries is not a valid string in the database code page.\n\nThe invalid data could have been input to the database in the following ways:\n\n\n * By running an SQL statement which writes byte values to the database. For example: INSERT INTO tab1 VALUES (X'C3')\n\n * By running the IMPORT or LOAD commands for files which contain character data that is not in the code page of the client machine, so the appropriate code page conversion was not done. To make sure that the the appropriate code page conversion is done when running IMPORT or LOAD, specify the code page of the input file by including the \"codepage=x\" file type modifier (specifying the code page in place of x).\n\nDIAGNOSING THE PROBLEM\nYou can use the HEX function to find out what are the byte values in a character column. \n\nFor example, to find out the byte values in column COL1 in table TAB1, run: \nSELECT HEX(col1) FROM tab1\n\n\nRESOLVING THE PROBLEM\nUpdate the invalid data with a valid UTF-8 character string. \n\n\nAlternatively, for JCC driver versions that support it you can set the JCC configuration property db2.jcc.charsetDecoderEncoder=3 so that instead of throwing an exception the JCC driver returns the Unicode REPLACEMENT CHARACTER (U+FFFD) in place of a sequence of bytes that is not a valid UTF-8 string. \nThe JCC configuration property db2.jcc.charsetDecoderEncoder is supported in versions of the JCC driver that come with DB2 LUW 9.5 Fix Pack 8 and later (APAR IC74896), DB2 LUW 9.7 Fix Pack 5 and later (APAR IC74895), and all DB2 LUW releases from DB2 10.1 onwards.\n\nFor example, suppose you have a Java program MyApp.java that executes an SQL query of a database column that contains a sequence of bytes that is not a valid string.\nWhen you run:\njava MyApp\nit throws an exception. But when you run:\njava -Ddb2.jcc.charsetDecoderEncoder=3 MyApp\nit returns the string with any invalid sequence of bytes replaced by the Unicode REPLACEMENT CHARACTER. \n\nThe Unicode REPLACEMENT CHARACTER often appears like this \n(a diamond with a question mark inside it) : [/support/docview.wss?uid=swg21684365&aid=1]\n\nRELATED INFORMATION\n APAR IC78495 [https://www-01.ibm.com/support/entdocview.wss?uid=swg1IC74895]\nAPAR IC74896 [https://www-01.ibm.com/support/entdocview.wss?uid=swg1IC74896]\nMaking the setting for IBM Data Studio [http://www.ibm.com/support/docview.wss?uid=swg21612346]\nMaking the setting for IBM Content Collector [http://www-01.ibm.com/support/knowledgecenter/SSAE9L_4.0.0/com.ibm.content.collector.doc_kc/troubleshooting/ts_afu_java_throws_exception.dita]\nUDF to identify invalid data in a UTF-8 character colum [http://www.ibm.com/support/docview.wss?uid=swg21608985]\nHow invalid data can get into a UTF-8 character column [http://www.ibm.com/support/docview.wss?uid=swg21412846]\nLOAD command [http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0008305.html]\nIMPORT command [http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0008304.html]\nHEX function [http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.sql.ref.doc/doc/r0000811.html]"
}
] |
TRAIN_Q474 | CICS Transaction Server for z/OS 4.1 and 4.2 End of Service dates
When will CICS Transaction Server for z/OS (CICS TS) V4.1 and V4.2 be withdrawn from support? I need to make sure that I upgrade to a newer release before the end of support (EOS) date. I would like to know what product replacement information is in the announcement letter. | - | true | [] |
TRAIN_Q475 | How can I fix blank pull down "Console Settings" menu after successful install of JazzSM 1.2.1.1 and WebSphere 8.5.5.9?
WebSphere version 8.5.5.9 didn't include jar files that were available in previous releases of WebSphere that are required by DASH for various tasks. | The missing jar files are included in DASH 3.1.2.1 Cumulative Patch 5, which you can download from this site:
http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli∏uct=ibm/Tivoli/Jazz+for+Service+Management&release=1.1&platform=All&function=all [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=1.1&platform=All&function=all] | false | [
{
"filename": "swg21981870.txt",
"text": "Title: IBM Missing Icon pulldown options in DASH main menu after 3.1.2.1 Install - United States\n\nText:\nDASHL2; Console Settings; missing.; icons; WAS 8.5.5.9; DASH 3.1.2.1; Cumulative patch 5; CP5 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After fresh install of WAS 8.5.5.9 with JazzSM 1.1.2.1/DASH 3.1.2.1, the \"Console Settings\" is missing entries and other expected icons are missing from the DASH main page. \n\nSYMPTOM\nAfter successful installation of JazzSM 1.1.2.1/DASH 3.1.2.1 with WebSphere 8.5.5.9, some of the icons in the main DASH window are missing on the left.\n\n\nCAUSE\nIt was recently discovered that some .jar files were not included in WebSphere 8.5.5.9, that were available in previous WebSphere releases, and are required for several functions in DASH.\n\nENVIRONMENT\nJazzSM 1.1.2.1 / DASH 3.1.2.1 WAS 8.5.5.9\n\nDIAGNOSING THE PROBLEM\nAfter you login to DASH and select \"Console Settings\", the displayed window, which should have several lines, is blank:\n\n\n[/support/docview.wss?uid=swg21981870&aid=1]\n\nAlso, in this case there wasn't any icons in the upper left portion of the main DASH window.\n\n\nRESOLVING THE PROBLEM\nThe missing jar files are included in DASH 3.1.2.1 Cumulative Patch 5, which you can download from this site: \n\n\nhttp://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli∏uct=ibm/Tivoli/Jazz+for+Service+Management&release=1.1&platform=All&function=all [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=1.1&platform=All&function=all] \n\n[/support/docview.wss?uid=swg21981870&aid=2] [/support/docview.wss?uid=swg21981870&aid=2]\nIf you have any questions as to whether DASH 3.1.2.1 Cumulative Patch 5 has been installed, please run this command:\n\n<JazzSM_HOME>/ui/bin/consolecli Version if patch 5 has been installed, it will have output showing the patch number shown in the red square in the screen shot:\n\n[/support/docview.wss?uid=swg21981870&aid=3] [/support/docview.wss?uid=swg21981870&aid=3]\n\nIf installing on a UNIX server, you will see several of these messages, they indicate that the jar files are not currently on the server, but the Patch install will finish successfully.\ncp: \n/opt/IBM/JazzSM/ui/../profile/installedApps/JazzSMNode01Cell//isc.ear/TI \nPChangePasswd.war/js/ibm/tivoli/tip/changepasswd/nls/iw/messages.js: No \nsuch file or directory \n.\n.\nPatch 201603301212 successfully installed."
}
] |
TRAIN_Q476 | How to turn on event debug to troubleshoot Impact Event Processing stopping ?
Impact support has requested a set of recreate logs with event logging turned on. What are the steps to do this?
| - | true | [] |
TRAIN_Q477 | On 30th June, could the Leap Second cause Linux to freeze and impact my MQ?
On 30th June, could the Leap Second cause Linux to freeze and impact my MQ? | In the past, the addition of leap seconds caused some systems running older Linux kernels to fail. IBM MQ and WebSphere MQ queue managers running on these systems generated repeated FDC files showing Probe Id XY348010 or XC272003 from xcsCreateThread, with error code xecP_E_NO_RESOURCE. Other FDCs are also possible. | false | [
{
"filename": "swg21602521.txt",
"text": "Title: IBM Leap Second bug in older Linux kernels may affect IBM MQ and WebSphere MQ - United States\n\nText:\n FLASH (ALERT)\n\nABSTRACT\n Leap seconds are a periodic one-second adjustment of Coordinated Universal Time (UTC) required to keep a system's time of day close to the mean solar time.\n\nA leap second is scheduled for 31 December 2016 at 23h 59m 60s UTC.\n\nIn the past, the addition of leap seconds caused some systems running older Linux kernels to fail. IBM MQ and WebSphere MQ queue managers running on these systems generated repeated FDC files showing Probe Id XY348010 or XC272003 from xcsCreateThread, with error code xecP_E_NO_RESOURCE. Other FDCs are also possible. \n\nCONTENT\nOn 31 December 2016, the Network Time Protocol (NTP) daemon will schedule a leap second [http://en.wikipedia.org/wiki/Leap_second] to occur at midnight, making the final minute of the day 61 seconds long. Prior leap second insertions, including the 30 June 2016 leap second, caused some Linux systems to exhibit unexplained high CPU usage.\n\n\nIBM MQ and WebSphere MQ use the Native POSIX Thread Library (NPTL) which relies on futuxes (\"fast userspace mutexes\") for synchronization between threads. Futexes can exhibit high CPU spins after leap seconds on Linux kernel versions 2.6.22 through 3.5-rc7, inclusive, although some Linux distributions shipped patches for kernels in this range:\n\n\n * \n * Leap Second to be added on December 31st 2016\n * \n * \n * \n * General information on Leap Second 2016\n * \n * Fixes and workarounds to avoid issues caused by Leap Second 2015\n * \n * \n * \n * Addition of leap second causes spuriously high CPU usage and futex lockups\n\n\n\nContact your Linux vendor to check the status of other distributions, or check the Linux kernel version using \"uname -r\" and confirm that your system is older than 2.6.22 or running 3.5 or later. \n\nIf you encounter this problem, the following workaround may resolve the high CPU usage. As root, run: \n * date -s \"$(LC_ALL=C date)\"\n\n \n\nPRODUCT ALIAS/SYNONYM\n IBM MQ WMQ WebSphere MQ MQSeries"
}
] |
TRAIN_Q478 | How to define shared libraries for ODM ruleApps on WAS traditional?
What is the proper way to define a shared lib for RuleApps without giving up the isolated mode of the XU resource adapter? Is it "works as designed" that isolating of the XU prevents the resource adapter from seeing shared lib classes from other classloaders? | 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. | false | [
{
"filename": "swg21634612.txt",
"text": "Title: IBM Use\"isolate the resource provider\" to establish data source connections using a different JDBC driver from the same database vendor - United States\n\nText:\nisolate this resource provider TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Customer has defined 3 Oracle JDBC Providers at cell, node and server\nscope. Client have following configuration in websphere JDBC provider. \n\nIn Cell Scope - C:\\jdbc\\ojdbc5\\ojdbc5.jar \n\nIn Node Scope - C:\\jdbc\\ojdbc6_g\\ojdbc6_g.jar \n\nIn Server Scope- C:\\jdbc\\ojdbc6\\ojdbc6.jar \n\nIn this case value of JDBC driver path in WebSphere variable is identical. Nornally, If JDBC provider configure at server level then server level driver will get load first. But in this case since all three drivers are from same vendor, So we can not control which driver is picking up. In this case \n\"C:\\jdbc\\ojdbc6\\ojdbc6.jar\" should be loaded first but instated, ojdbc5.jar was load first\n\n[13. 4. 5 12:05:15:625 KST] 00000023 CompoundClass < loadClass \n\noracle.jdbc.driver.OracleDriver \n\nloader=com.ibm.ws.bootstrap.ExtClassLoader@5dc95dc9 \n\nsource=file:/C:/jdbc/ojdbc5/ojdbc5.jar Exit \n\n\n\n\n\n\nSYMPTOM\nDue to multiple JDBC drivers from the same vendor were configured in different scopes, the wrong driver class was loaded.\n\n\nCAUSE\nWhen multiple versions of the JDBC driver are configured in WebSphere Application Server, irrespective of the scopes, there is a possibility of a collision of the classes and we cannot predict from which version of the driver jar the class got loaded. \n\nRESOLVING THE PROBLEM\n In order to support the existence of multiple versions of the driver jars, the \"Isolate this resource provider\" configuration helps to ensure there are no conflicts. This needs to be configured on each JDBC Provider. You cannot isolate only one resource provider, all the provider configurations in different scopes will have to be configured with the \"Isolate this resource provider\" setting. In this scenario, the resource provider classes from different versions of the jars are not imported or accessed to verify if the isolation has indeed worked. In order to use the server-scoped resource provider the datasource using the server-scoped jdbc provider will have to be referenced from the application after isolating the resource providers and using a resource reference in the application. \n\n\nGo to the JDBC Provider and enable \"isolate the resource provider\". When \"Isolate this resource provider\" is enabled, it ensures that only the jar that was specified in the classpath will be used for all the datasources under that particular JDBC provider. \n\n \n\nHere are links to Knowledge Center articles which contain further information on the setting: \n\n\nJDBC provider settings [https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.0/com.ibm.websphere.nd.multiplatform.doc/ae/udat_manjdbcprodet.html]\n\nConsiderations for isolated resource providers [https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.0/com.ibm.websphere.nd.multiplatform.doc/ae/rdat_isolatedlimitations.html]"
}
] |
TRAIN_Q479 | Why cant I load and AEL when using IE 11 JRE 8
Application Blocked by Java Security
| - | true | [] |
TRAIN_Q480 | Whether IBM Case Manager is using Apache Struts?
Whether IBM Case Manager is using Apache Struts? If yes, could you let us know which version? | - | true | [] |
TRAIN_Q481 | Connection pooling parameters (unusedTimeout, agedTimeout) won't work as expected on bpm 8.5.5 and oracle 11g RAC
We have set the connection pooling parameters to unusedTimeout=300, agedTimeout=600, minConnections=0 and reapTimeout=180 seconds for all pools. Our expectation is that maximum after 13 minutes any connection shall be renewed (8 minutes for unused ones). However we observe connections issued by CMNuser and PSuser that last for days/weeks. Did anyone face a similar issue? | - | true | [] |
TRAIN_Q482 | Is there a limit to the number of items that can be listed within an "in" list as part of a where clause?
Is there a limit to the number of items that can be listed within an "in" list as part of a where clause? | The short answer is no limit.
By default we create a virtual table for any "in list" with more than 5 values.
The only limitation with large "in list" statements would be the memory needed to compile the query. If the query is too complex, you can potentially run out of memory, but that will not affect other sessions since this happens inside the postgres process assigned to that session. The parameter that is responsible for this behaviour is inlist_threshold and it is safe to increase this value to 100, but not more. | false | [
{
"filename": "swg21698950.txt",
"text": "Title: IBM Is there a limit to the number of items that can be listed within an \"in\" list as part of a where clause? - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Is there a limit to the number of items that can be listed within an \"in\" list as part of a where clause? \n\nCAUSE\nEvery time the query optimizer finds a \"(NOT) IN\" statement in the query, a decision must be made:\nOption A: Evaluate the condition sequentially for every member of the IN-list, or \nOption B: create a temporal virtual table from this list and use JOIN logic for evaluation. \n\nIf the amount of members in the IN-list is smaller than the value of INLIST_THRESHOLD, then option A is used. \nIf the amount of members in the IN-list is equal or bigger than the value of INLIST_THRESHOLD, then option B is used.\n\n\nENVIRONMENT\nAny IBM PureData System for Analytics with any NPS Release\n\n\n\nRESOLVING THE PROBLEM\nThe short answer is no limit.\n\n\nBy default we create a virtual table for any \"in list\" with more than 5 values.\n\nThe only limitation with large \"in list\" statements would be the memory needed to compile the query. If the query is too complex, you can potentially run out of memory, but that will not affect other sessions since this happens inside the postgres process assigned to that session. The parameter that is responsible for this behaviour is inlist_threshold and it is safe to increase this value to 100, but not more.\n\nshow inlist_threshold;\n\nset inlist_threshold=<value>;\n\n \n\nPRODUCT ALIAS/SYNONYM\n pda netezza"
}
] |
TRAIN_Q483 | How do I tell when there are mismatched MQ jars in my application server?
Mismatched jar files can cause strange and unpredictable errors when using the MQ JMS classes. | Finding and eliminating duplicate copies of the MQ jar files can be a difficult task, but the mqjavalist.sh script simplifies that task on Linux and UNIX systems. | false | [
{
"filename": "swg21681142.txt",
"text": "Title: IBM Solving IBM MQ Java code version mismatches using the mqjavalist.sh script - United States\n\nText:\nWebSphere MQ WMQ TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When Java™ SE applications and Java EE application servers such as WebSphere Application Server do not use a consistent set of MQ Java archives, applications can fail in unpredictable ways. If WebSphere Application Server notices a mismatch, it issues this message: \"MQJCA1008 The WebSphere MQ classes for JMS were found in the class path but were not the correct version. This error can occur if the application server finds an earlier version of the WebSphere MQ classes for JMS in the class path. The error can also occur if you do not configure WebSphere Application Server to use the correct version of the WebSphere MQ classes for JMS.\" \n\nENVIRONMENT\nThe mqjavalist.sh script runs on Linux and UNIX systems and can identify Java archives and classes from MQ V5.3 and later versions. Although the mqjavalist.sh script does not run on Windows systems, it is possible to zip up a directory structure on Windows in order to examine it with mqjavalist.sh on a different system. To use the mqjavalist.sh script, download it from the bottom of this page, copy it to the target system, and make the script executable. Make sure that either the unzip command or the Java jar command is available in your PATH before running mqjavalist.sh. For example:\n\n\n\n 1. Preparing to run mqjavalist.sh\n 2. \n 3. sh> chmod +x mqjavalist.sh \n sh> PATH=$PATH:/opt/java7/bin \n \n\n\n\n\nDIAGNOSING THE PROBLEM\nIBM MQ ships a number of Java archives (jar files) that applications use to connect to MQ and work with messages. For Java EE environments, MQ provides a Resource Adapter called wmq.jmsra.rar which contains the jar files required by JMS applications. Java SE and Java EE applications must use a consistent set of MQ jar files at the same maintenance level, or else they might experience a wide variety of problems including intermittent errors, performance problems, and other failures.\n\nIt is common to find multiple versions of the MQ jar files in the Java CLASSPATH, or invalidly bundled in Java applications (.ear, .war, and .jar files). Finding and eliminating duplicate copies of the MQ jar files can be a difficult task, but the mqjavalist.sh script simplifies that task on Linux and UNIX systems.\n\n\n\n * Syntax\n * Examples\n * WebSphere Application Server\n * Sample output\n * Resolving problems\n * Download\n\n\n\nSYNTAX\n\n 1. mqjavalist.sh -? | -h \n 2. \n 3. mqjavalist.sh [-v] [-r] [-f File] -d Directory ...\n 4. \n 5. \n 6. \n 7. -?:\n 8. \n 9. \n 10. -h:\n 11. \n 12. \n 13. -v:\n 14. \n 15. \n 16. -r:\n 17. \n 18. \n 19. -f File:\n 20. \n 21. \n 22. -d Directory:\n 23. \n 24. \n 25. \n 26. \n 27. \n 28. The mqjavalist.sh script can take several minutes to complete, depending on the number of Java archives to search and whether you perform a recursive examination of archive files. While running, the script regularly prints its status and the percentage of work completed.\n\n\nBack to top\n\n\n\nEXAMPLES\n\n 1. Search for MQ files under /usr/IBM/WebSphere and save the results to the file mqlist.txt:\n \n mqjavalist.sh -f mqlist.txt -d /usr/IBM/WebSphere\n 2. \n 3. \n 4. Perform a recursive search of archives under /opt/IBM:\n \n mqjavalist.sh -r -d /opt/IBM\n 5. \n 6. \n 7. Recursively search archive files under the /opt/IBM/IIB and /opt/mqm directories and enable verbose output to ~/output.txt:\n \n mqjavalist.sh -vrf ~/output.txt -d /opt/IBM/IIB -d /opt/mqm\n 8. \n\n\nBack to top\n\n\n\nWEBSPHERE APPLICATION SERVER\n\nWebSphere Application Server and other IBM products built on WebSphere Application Server normally show the MQ jar files in more than one location. Except as noted below, the copies of the MQ jar files should match the versions listed on this page [https://www.ibm.com/support/docview.wss?uid=swg21248089]. Any copies of the MQ jar files other than those listed below might represent a problem: \n\n\n 1. WebSphere Application Server V8.5.5, V8.5 and V8.0\n 2. \n 3. \n\n\n\n 1. WebSphere Application Server V7.0\n 2. \n 3. \n 4. \n 5. \n 6. If you created a WebSphere Application Server V7.0 profile before applying fix pack 7.0.0.1 or later, you must update the profile to use the correct MQ Resource Adapter path [https://www.ibm.com/support/knowledgecenter/SSAW57_7.0.0/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tmj_wmqra_restoredefault.html]. Otherwise, the application servers in that profile will use the old MQ Resource Adapter jars under the profile installedConnectors/wmq.jmsra.rar directory rather than the MQ jars in the main installedConnectors/wmq.jmsra.rar directory, which are kept up to date by WebSphere Application Server fix packs.\n\n\n 1. WebSphere Application Server V6.1\n 2. \n 3. \n\n\n\nBack to top\n\n\n\nSAMPLE OUTPUT\n\n 1. sh> \n 2. ./mqjavalist.sh -r -f mqlist.txt -d /opt/IBM/WebSphere/AppServer\n 3. \n 4. Running mqjavalist.sh V1.4 on SUSE Linux Enterprise Server 10 (ppc) with arguments: -r -f mqlist.txt -d /opt/IBM/WebSphere/AppServer\n \n mqjavalist.sh: Searching directory /opt/IBM/WebSphere/AppServer\n mqjavalist.sh: 2180 possible Java archives found\n 1. Found 80 MQ classes in classes.jar in WMQHTTP.war in /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/aemtux1Cell01/applications/WMQHTTP_war.ear/WMQHTTP_war.ear:\n root root 145600 2014-07-16 13:56 /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/aemtux1Cell01/applications/WMQHTTP_war.ear/WMQHTTP_war.ear\n 2. Found 80 MQ classes in /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/aemtux1Cell01/WMQHTTP_war.ear/WMQHTTP.war/WEB-INF/lib/classes.jar:\n root root 156845 2013-09-25 18:02 /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/aemtux1Cell01/WMQHTTP_war.ear/WMQHTTP.war/WEB-INF/lib/classes.jar\n 3. Found 80 MQ classes in classes.jar in WMQHTTP.war in /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/aemtux1Cell01/applications/WMQHTTP_war.ear/WMQHTTP_war.ear:\n root root 145600 2014-07-16 13:57 /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/aemtux1Cell01/applications/WMQHTTP_war.ear/WMQHTTP_war.ear\n 4. Found com.ibm.mq.commonservices.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ Common Service\n Implementation-Version: ${version.number} - ${build.level}\n Implementation-Vendor: IBM Corporation\n 5. Found com.ibm.mq.connector.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ J2EE Connector Architecture\n Implementation-Version: 7.1.0.0-k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 6. Found com.ibm.mq.headers.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 /wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 7. Found com.ibm.mq.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 8. Found com.ibm.mq.jmqi.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 9. Found com.ibm.mq.jmqi.local.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 10. Found com.ibm.mq.jmqi.remote.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 11. Found com.ibm.mq.jmqi.system.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 12. Found com.ibm.mq.jms.admin.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: JMS Common Client API/SPI\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 13. Found com.ibm.mq.pcf.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 14. Found com.ibm.mqjms.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: JMS Client Common Facade\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 15. Found dhbcore.jar in /opt/IBM/WebSphere/AppServer/lib/WMQ/ra/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Version: \"DH610-GOLD\"\n Implementation-Title: \"Webscale Distribution Hub Core\"\n Implementation-Vendor: \"IBM Corporation\"\n 16. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.jar:\n root root 1115668 2012-10-15 12:56 com.ibm.mq.jmqi.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 17. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.commonservices.jar:\n root root 728387 2012-10-15 12:56 com.ibm.mq.commonservices.jar\n Implementation-Title: WebSphere MQ Common Service\n Implementation-Version: ${version.number} - ${build.level}\n Implementation-Vendor: IBM Corporation\n 18. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.remote.jar:\n root root 546407 2012-10-15 12:56 com.ibm.mq.jmqi.remote.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 19. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jar:\n root root 448745 2012-10-15 12:56 com.ibm.mq.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 20. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jms.admin.jar:\n root root 358016 2012-10-15 12:56 com.ibm.mq.jms.admin.jar\n Implementation-Title: JMS Common Client API/SPI\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 21. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mqjms.jar:\n root root 352254 Aug 01 11:49 com.ibm.mqjms.jar\n Implementation-Title: JMS Common Client facade\n Implementation-Version: 7.0.1.5 - k701-105-110419\n Implementation-Vendor: IBM Corporation\n 22. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.connector.jar:\n root root 339396 2012-10-15 12:56 com.ibm.mq.connector.jar\n Implementation-Title: WebSphere MQ J2EE Connector Architecture\n Implementation-Version: 7.1.0.0-k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 23. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.headers.jar:\n root root 338572 2012-10-15 12:56 com.ibm.mq.headers.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 24. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.local.jar:\n root root 224747 2012-10-15 12:56 com.ibm.mq.jmqi.local.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 25. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.system.jar:\n root root 209738 2012-10-15 12:56 com.ibm.mq.jmqi.system.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 26. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/com.ibm.mq.pcf.jar:\n root root 125200 2012-10-15 12:56 com.ibm.mq.pcf.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 27. Found /opt/IBM/WebSphere/AppServer/installedConnectors/wmq.jmsra.rar/dhbcore.jar:\n root root 2011835 2012-10-15 12:56 dhbcore.jar\n Implementation-Version: \"DH610-GOLD\"\n Implementation-Title: \"Webscale Distribution Hub Core\"\n Implementation-Vendor: \"IBM Corporation\"\n mqjavalist.sh: 27 jar files with MQ code found in /opt/IBM/WebSphere/AppServer\n \n mqjavalist.sh: 27 total jar files with MQ code found\n mqjavalist.sh: Results saved to mqlist.txt\n \n \n \n 5. \n 6. Back to top\n\nRESOLVING THE PROBLEM\n\nReview the output from mqjavalist.sh to determine where copies of the MQ jar files have been found. Not all duplicates represent a problem, unless they are being loaded by your Java SE application or Java EE application server at runtime. If the com.ibm.mq.commonservices.jar file shows an implementation version of ${version.number} - ${build.level} just ignore it.\n\nIn the sample output above, entries #16 through #27 represent the jar files for the installed MQ Resource Adapter. They all show an implementation version of 7.1.0.0 - k000-L111005.1 except for #21, com.ibm.mqjms.jar, which shows an implementation version of 7.0.1.5 - k701-105-110419. Because the jar file versions are not in sync, MQ JMS will not function as expected.\n\nIn cases like this, the wmq.jmsra.rar file should contain a copy of the MQ jar at the right level for the application server. Entry #14 in the mqjavalist.sh output shows the com.ibm.mqjms.jar file with an implementation version of 7.1.0.0 - k000-L111005.1, which is what we need. Use the jar program to extract the com.ibm.mqjms.jar file from the wmq.jmsra.rar archive, then copy it over the back-level version of the jar. Use chown and chmod to ensure the permissions on the file are correct.\n\nIn other cases, you might find that the classpath for the application server, or for your Java SE application, is picking up extra copies of the MQ jar files. Eliminating unnecessary classpath entries can resolve the problem.\n\nIf your Java EE application (.ear or .war) bundles a copy of any MQ jar files, you should remove them and rely on the ones from the installed MQ Resource Adapter instead.\n\nBack to top\n\n\nAdditional Keywords: \ntroubleshoot troubleshooting trouble shoot classloader classpath configuration scripts\n\n\n\nDOWNLOAD\n 1. \n 2. mqjavalist.sh [/support/docview.wss?uid=swg21681142&aid=2]mqjavalist.sh\n\n\n\n\nDISCLAIMER: All source code and/or binaries attached to this document are referred to here as \"the Program\". IBM is not providing program services of any kind for the Program. IBM is providing the Program on an \"AS IS\" basis without warranty of any kind. IBM WILL NOT BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM, OR ITS RESELLER, HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Back to top"
}
] |
TRAIN_Q484 | Stale / old content on one cluster node but content up-to-date on other nodes.Why?
Stale / old content on one cluster node but content up-to-date on other nodes. | - | true | [] |
TRAIN_Q485 | Security Bulletin: XXE injection vulnerability in IBM API Connect (CVE-2017-1322)
I need to understand details regarding Security Bulletin: XXE injection vulnerability in IBM API Connect (CVE-2017-1322). Where can I find this information? | - | true | [] |
TRAIN_Q486 | Why Summarization and pruning are failing with SQL Error Code = -4220 on AIX_LPAR table?
Why Summarization and pruning are failing with SQL Error Code = -4220 on AIX_LPAR table?
| - | true | [] |
TRAIN_Q487 | Security Bulletin: API Connect Portal is affected by multiple Drupal vulnerabilities
I need to understand details regarding Security Bulletin: API Connect Portal is affected by multiple Drupal vulnerabilities (CVE-2017-6924, CVE-2017-6923, CVE-2015-7875, CVE-2017-6925). Where can I find this information? | - | true | [] |
TRAIN_Q488 | Does DB2 DBMS implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures?
V-58159 - SV-72589r1_rule says "The DBMS must implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures."
Does DB2 UDB version 8 implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures? | DB2 uses encryption modules which are FIPS 140-2 certified. | false | [
{
"filename": "swg21237078.txt",
"text": "Title: IBM DB2 UDB Version 8, v10.5 compliance with FIPS 140-2 standard - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Is DB2 v8, v10.5 compliant to FIPS 140-2 ?. \n\nANSWER\n\nIs DB2 v10.5 compliant with FIPS 140-2?\n\nQ: Is DB2 vulnerable to the problem described below?\n\nV-58165 DBMS main in the middle attack [https://www.stigviewer.com/stig/database_security_requirements_guide/2015-06-23/finding/V-58165]\n\n\"One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers based on patterns in identifiers already known. The preferred technique for thwarting guesses at Session IDs is the generation of unique session identifiers using a FIPS 140-2 approved random number generator. However, it is recognized that available DBMS products do not all implement the preferred technique yet may have other protections against session hijacking. Therefore, other techniques are acceptable, provided they are demonstrated to be effective. \"\n\nA: No because DB2 does not use session ids for authentication and thus not vulnerable to the attack described above. DB2 uses encryption modules which are FIPS 140-2 certified.\n\nDB2 v8.x compliancy to FIPS 140-2\n\nDB2 v8.x went out of support in April 2009.\n\nWhat is ICC?\n\nICC (IBM Crypto for C) is a set of libraries from Tivoli® for performing encryption. As of DB2® Universal Database™ (DB2 UDB) Version 8 fixpak 7 (equivalent to DB2 UDB Version 8.2), DB2 is using ICC on most platforms.\n\nCustomers who need to operate in an environment that is compliant with FIPS 140-2 federal standard should take into account the releases of ICC that are shipped by DB2 on different platforms and the compliance status of those releases with FIPS 140.2.\n\nFollowing is a list of platforms on which DB2 is using ICC for encryption of data flowing between clients and servers:\n\nDB2 V8 Fixpak 7 through DB2 Fixpak 11: \nICC Version 1.2.2 on platforms:\nAIX 32 bit\nHP-UX PA-RISC 32 bit\nICC Version 1.2.1 on platforms: \nAIX 64 bit\nHP-UX PA-RISC 64 bit\nHP-UX IA64\nLinux x86, Linux x86-64, Linux IA64\nLinux for zSeries\nLinux for POWER\nWindows x86 and IA64\nSolaris SPARC 64 bit\nICC Version 1.3.9 on platforms:\nSolaris x86-64 (DB2 V8.2 GA)\n\nDB2 V8 Fixpak 12 and later: \nICC Version 1.4.1 on platforms \nAIX\nHP-UX PA-RISC\nLinux x86 and x86-64\nLinux for zSeries\nLinux for POWER\nWindows x86 and x86-64\nSolaris SPARC\nICC Version 1.3.9 on platforms \nHP-UX IA64\nLinux IA64\nWindows IA64\n\nSummary of known problems encountered in ICC 1.2.1/1.2.2:\nThere are a number of issues with DB2 and the ICC encryption libraries at levels prior to 1.3.9. The known problems are: \n\n\n 1. Severe performance problems where processes seem to hang, or take several minutes to run. \n 2. A bug in ICC code causes it to communicate with the OpenSSL EGD (Entropy Gathering Daemon) which under certain circumstances could hang \n 3. ICC symbols have not been namespaced and DB2 can end up with symbol collisions with OpenSSL code. This can also happen when multiple versions of ICC are used within the same process.\n\n\nDB2 Version 8 Fixpak 12 and later incorporates IBM Crypto for C (ICC) version 1.3.9 or 1.4.1 cryptographic module which fixes these problems. \n\n \n\nNote: The latest status of ICC conformance with FIPS 140-2 standard can be obtained by referring to http://www.ibm.com/security/standards/st_evaluations.shtml [http://www.ibm.com/security/standards/st_evaluations.shtml]\n\nRELATED INFORMATION\n FIPS PUB 140-2 [http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf]"
}
] |
TRAIN_Q489 | Recurrent RES StaleConnectionException
How to prevent rule execution failing because of recurrent StaleConnectionException on ODM 8.8 Rule Execution Server? | Configure the WebSphere Application Server data source connection pool [http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/udat_conpoolset.html] so as to eliminate occurrences of StaleConnectionException :
* Set the Minimum connections to 0 to avoid situations where a connection is kept in the pool to meet the minimum requirement, even though it may have been idle for longer than Unused timeout
* Set the values for Unused timeout and Reap timeout so that the sum does not exceed any network level idle connection timeout | false | [
{
"filename": "swg21496354.txt",
"text": "Title: IBM JRules or ODM module fails to access database with StaleConnectionException - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n JRules and ODM modules such as Rule Execution Server (RES) and Rule Team Server (RTS) / Decision Center (DC) may fail to access their data source with the following type of exception present in the log:\n\ncom.ibm.websphere.ce.cm.StaleConnectionException: Io exception: Connection timed out \n\nSYMPTOM\nThe problem may occur when a JRules or ODM module accesses its data source after a period of database access inactivity. For example: \n\n * The first user accessing a RTS / DC server that remained idle overnight experiences a failure upon logging and the server log shows an com.ibm.websphere.ce.cm.StaleConnectionException occurred at that time. \n * After a RES server has been processing execution requests normally for some time, an attempt to deploy a ruleset update fails and the server log shows an com.ibm.websphere.ce.cm.StaleConnectionException occurred upon an attempt to invalidate a ruleset or to retrieve its definition.\n\n\nCAUSE\nThe underlying network connection for a data source is no longer valid although the data source itself remains considered active from the WebSphere Application Server data source connection pool management perspective. An attempt by a JRules module to try and access its data base through one such data source connection provided by the Application Server may then fail. \nThe network connection of a data source may become invalid for a number of reasons, one typical example is that a firewall between the Application Server and the Database has a policy to discard network connections that remain idle for some time.\n\n\nENVIRONMENT\nThe exception com.ibm.websphere.ce.cm.StaleConnectionException is specific to WebSphere Application Server environments. But a similar issue can be experienced with Weblogic, see: Rule Execution Server on WebLogic unable to load ruleset after period of inactivity [http://www-01.ibm.com/support/docview.wss?uid=swg21615801]\n\n\n\nRESOLVING THE PROBLEM\nConfigure the WebSphere Application Server data source connection pool [http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/udat_conpoolset.html] so as to eliminate occurrences of StaleConnectionException : \n\n * Set the Minimum connections to 0 to avoid situations where a connection is kept in the pool to meet the minimum requirement, even though it may have been idle for longer than Unused timeout \n * Set the values for Unused timeout and Reap timeout so that the sum does not exceed any network level idle connection timeout\n\n\nThe document Troubleshooting stale connection problems [http://www-01.ibm.com/support/docview.wss?uid=swg21247168#SCETroubleshooting] provides further information. RELATED INFORMATION\n#RES unable to load ruleset after period of inactivity [http://www-01.ibm.com/support/docview.wss?uid=swg21615801]\nTroubleshooting stale connection problems [http://www-01.ibm.com/support/docview.wss?uid=swg21247168#SCETroubleshooting]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Platform Independent 8.5, 8.0.1, 8.0, 7.5 Enterprise"
}
] |
TRAIN_Q490 | TWS / DWC and WebSphere 8.5.5.4+
WebSphere for TWS & DWC were upgraded to 8.5.5.4 on most servers in a particular environment. However, any TWS servers that still had 8.5.5.2, could no longer be seen by the new DWC / WAS 8.5.5.4 servers. Those lower WAS version engines could not be added to the DWC.
Errors seen are:
AWSUI0833E The operation could not be completed. There has been a communication failure.
The internal message is: AWSJCO005E WebSphere Application Server has given the following error: Error getting WsnNameService properties. | You can solve this problem by configuring your TWS engines to use TLS instead of SSL : | false | [
{
"filename": "swg21964202.txt",
"text": "Title: IBM How Connect TDWC 9.3 to TWS Engine lower level release - United States\n\nText:\ndwc 93; connect; SSL ; TLS TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n DWC 9.3 users cannot connect to TWS Engine lower level releases (8.5.1 until 9.2) \n\nSYMPTOM\nUnable to connect to TWS 8.5.1 ,8.6 or 9.1/9.2 from DWC 9.3. \n\nCheck the WAS SystemOut.log for error :\n\nSSL0080E: javax.net.ssl.SSLHandshakeException - The client and server could not negotiate the desired level of security. Reason: Server chose SSLv3, \nbut that protocol version is not enabled or not supported by the client. javax.net.ssl.SSLHandshakeException: Server chose SSLv3, but that protocol version is not enabled or not supported by the client.\n\n\nCAUSE\nDWC 9.3 is packaged with WAS 8.5.5.4 and due to known vulnerabilities has SSLV3 disabled. However TWS 9.2 and earlier versions use SSLv3 by default and so the DWC 9.3 cannot connect\n\n\nRESOLVING THE PROBLEM\nYou can solve this problem by configuring your TWS engines to use TLS instead of SSL :\n\n\nBackup and edit : \n\nTWA_HOME/WAS/TWSProfile/config/cells/TWSNodeCell/security.xml \n\nFind sslProtocol and change \"SSL_TLS\" to \"TLS\" \n\nFind ssl.protocol and change value=\"SSL\" to value=\"TLS\" \n\nBackup and edit : \n\nTWA_HOME/WAS/TWSProfile/properties/ssl.client.props \n\nFind com.ibm.ssl.protocol=SSL and change to com.ibm.ssl.protocol=TLS \n\nBackup and edit : \n\nTWA_HOME/WAS/TWSProfile/temp/ssl.client.props \n\nFind com.ibm.ssl.protocol=SSL and change to com.ibm.ssl.protocol=TLS \n\nStop and restart WAS. \n\n*Be aware that your Engines are now using TLS and so you must also reconfigure any DWC 9.2 or 9.1 installations that need to connect to those engines. You would change them to use TLS in the same way as above but also by the same changes in these copies of security.xml and ssl.client.props : \n\nTWA_HOME/JazzSM/profile/config/cells/JazzSMNode01Cell/security.xml \n\nTWA_HOME/JazzSM/profile/properties/ssl.client.props \n\nTWA_HOME/JazzSM/profile/temp/ssl.client.props \n\nPlease consider that since you configure with TLS the WAS of TWS Engine also the Dynamic Agent can be impacted. \n\nSee technote 1689332."
}
] |
TRAIN_Q491 | Security Bulletin: MQ Explorer directory created with owner '555' on Linux x86-64 vulnerability affects IBM MQ (CVE-2016-6089)
I need to understand details regarding Security Bulletin: MQ Explorer directory created with owner '555' on Linux x86-64 vulnerability affects IBM MQ (CVE-2016-6089). | - | true | [] |
TRAIN_Q492 | Help with Security Bulletin: Malformed client flows abend MQTT channel (CVE-2015-4943, CVE-2015-4941, CVE-2015-4942)
I need to understand details regarding Security Bulletin: Malformed client flows abend MQTT channel (CVE-2015-4943, CVE-2015-4941, CVE-2015-4942). Where can I find this information? | CVEID: CVE-2015-4943 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4943]
DESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service using a sequence of connect and disconnects which will have to be restarted.
CVSS Base Score: 5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/104516 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104516] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)
CVEID: CVE-2015-4941 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4941]
DESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service due to incorrect handling of abbreviated TLS handshake.
CVSS Base Score: 5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/104514 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104514] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)
CVEID: CVE-2015-4942 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4942]
DESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service using a sequence of connect and disconnects which will have to be restarted.
CVSS Base Score: 5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/104515 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104515] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P) | false | [
{
"filename": "swg21972012.txt",
"text": "Title: IBM Security Bulletin: Malformed client flows abend MQTT channel (CVE-2015-4943, CVE-2015-4941, CVE-2015-4942) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n A number of malformed MQTT client flows could be issued by a malicious user to cause the MQXR service to abend and require manual restart. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-4943 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4943]\nDESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service using a sequence of connect and disconnects which will have to be restarted.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/104516 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104516] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)\nCVEID: CVE-2015-4941 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4941]\nDESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service due to incorrect handling of abbreviated TLS handshake.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/104514 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104514] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P) \n\nCVEID: CVE-2015-4942 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4942]\nDESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service using a sequence of connect and disconnects which will have to be restarted.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/104515 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104515] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM WebSphere MQ 8.0 \n\n - IBM WebSphere MQ 8.0.0.3 and earlier maintenance levels \n\nIBM WebSphere MQ 7.5 \n\n - IBM WebSphere MQ 7.5.0.5 and earlier maintenance levels \n\nIBM WebSphere MQ 7.1 \n\n - IBM WebSphere MQ 7.1.0.6 and earlier maintenance levels\n\nREMEDIATION/FIXES\nWebSphere MQ 8.0 \n\n - Apply fixpack 8.0.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg21969244] \n\nWebSphere MQ 7.5 \n\n - Apply interim ifix IT09866 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+MQ&release=7.5.0.5&platform=All&function=aparId&apars=IT09866] \n\nWebSphere MQ 7.1 \n\n - Apply fixpack 7.1.0.7 [http://www-01.ibm.com/support/docview.wss?uid=swg21965293]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nACKNOWLEDGEMENT\nReported to IBM by Codenomicon at http://www.codenomicon.com/ [http://www.codenomicon.com/] \n\nCHANGE HISTORY\n 01 February 2016: Original version published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. \n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21977182]"
}
] |
TRAIN_Q493 | Help with Security Bulletin: A security vulnerability has been identified in IBM WebSphere Application Server, which is shipped with, or a required product for, IBM Tivoli Network Manager IP Edition (CVE-2017-1741).
I need to understand details regarding Security Bulletin: A security vulnerability has been identified in IBM WebSphere Application Server, which is shipped with, or a required product for, IBM Tivoli Network Manager IP Edition (CVE-2017-1741) Where can I find this information? | CVEID: CVE-2017-1741 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1741]
DESCRIPTION: IBM WebSphere Application Server could allow a remote attacker to obtain sensitive information caused by improper handling of Administrative Console panel fields. When exploited an attacker could read files on the file system.
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/134931 [https://exchange.xforce.ibmcloud.com/vulnerabilities/134931] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) | false | [
{
"filename": "swg22012342.txt",
"text": "Title: IBM Security Bulletin: Information disclosure in WebSphere Application Server Admin Console (CVE-2017-1741) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There is a potential information disclosure in the WebSphere Application Server Admin Console. \n\nVULNERABILITY DETAILS\n\nCVEID: CVE-2017-1741 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1741]\nDESCRIPTION: IBM WebSphere Application Server could allow a remote attacker to obtain sensitive information caused by improper handling of Administrative Console panel fields. When exploited an attacker could read files on the file system.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/134931 [https://exchange.xforce.ibmcloud.com/vulnerabilities/134931] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nThis vulnerability affects the following versions and releases of IBM WebSphere Application Server: \n\n * Version 9.0 \n * Version 8.5 \n * Version 8.0 \n * Version 7.0\n\nREMEDIATION/FIXES\n The recommended solution is to apply the interim fix, Fix Pack or PTF containing APARs PI90042 for each named product as soon as practical.\n\nFor WebSphere Application Server traditional and WebSphere Application Server Hypervisor Edition: \n\nFor V9.0.0.0 through 9.0.0.6: \n· Upgrade to minimal fix pack levels as required by interim fixes and then apply Interim Fix PI90042 [http://www-01.ibm.com/support/docview.wss?uid=swg24044616] [http://www-01.ibm.com/support/docview.wss?uid=swg24044155] [http://www-01.ibm.com/support/docview.wss?uid=swg24043596] [http://www-01.ibm.com/support/docview.wss?uid=swg24042712] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24042513] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24044155] [http://www-01.ibm.com/support/docview.wss?uid=swg24044154]\n--OR-- \n· Apply Fix Pack 9.0.0.7 or later. \n\nFor V8.5.0.0 through 8.5.5.13: \n· Upgrade to minimal fix pack levels as required by interim fixes and then apply Interim Fix PI90042 [http://www-01.ibm.com/support/docview.wss?uid=swg24044616] [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 PI90042 [http://www-01.ibm.com/support/docview.wss?uid=swg24044616] [http://www-01.ibm.com/support/docview.wss?uid=swg24044445] [http://www-01.ibm.com/support/docview.wss?uid=swg24043596] [http://www-01.ibm.com/support/docview.wss?uid=swg24042712] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24042513] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394]\n--OR-- \n· Apply Fix Pack 8.0.0.15 or later. \n\nFor V7.0.0.0 through 7.0.0.43: \n· Upgrade to a minimal fix pack levels as required by interim fix and then apply Interim Fix PI90042 [http://www-01.ibm.com/support/docview.wss?uid=swg24044616] [http://www-01.ibm.com/support/docview.wss?uid=swg24044445] [http://www-01.ibm.com/support/docview.wss?uid=swg24043596] [http://www-01.ibm.com/support/docview.wss?uid=swg24042712] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24042513] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394]\n--OR-- \n· Apply Fix Pack 7.0.0.45 or later. \n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 06 March 2018: original document published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. \n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg22014402]"
}
] |
TRAIN_Q494 | Why do we observe the transaction rollback errors J2CA0024E and DSRA0080E with Oracle 12c and how can we fix it?
We are using BPM Advanced v8.5.6 in connection with the Oracle JDBC Driver 12.1.0.1.0. We observe many database transaction rollback exceptions:
J2CA0024E: Method rollback, within transaction branch ID <null> of resource pool jdbc/BPEDB, caught com.ibm.ws.exception.WsException: DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: Could not rollback with auto-commit set on. with SQL State : 99999 SQL Code : 17274
Due to the technote "Advanced database support for IBM BPM Standard, IBM BPM Advanced, and IBM Business Monitor on distributed platforms" this is a supported configuration.
Why do we observe these errors and how can we fix it? | To use Oracle 12c with IBM Business Monitor V8.5.5, a new JVM property must be defined. Add the following JVM property to the Monitor server JVM:
oracle.jdbc.autoCommitSpecCompliant=false | false | [
{
"filename": "swg21690673.txt",
"text": "Title: IBM Upgrading default JDBC drivers to Oracle 12c requires the definition of an additional JVM property in IBM Business Monitor - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n In IBM Business Monitor V8.5.5, the Monitor server fails if the default JDBC driver included in the product is upgraded to an Oracle 12c JDBC driver. \n\nRESOLVING THE PROBLEM\nTo use Oracle 12c with IBM Business Monitor V8.5.5, a new JVM property must be defined. Add the following JVM property to the Monitor server JVM:\n\noracle.jdbc.autoCommitSpecCompliant=false"
}
] |
TRAIN_Q495 | Is there a way to separate the application logging from WebSphere Application Server logging?
Currently the WebSphere error logs as well as the application error logs are printed in same file. The same case with system out logs. Our goal is to separate the application system error and out logs from WebSphere system logs.
If we are use log4j in the application for separating the logs what is the best way to do this? | In WAS V8.5, we added the application name to log and trace records stored using HPEL (High Performance Extensible Logging). Since HPEL lets you format and filter your log content after it has been persisted to the HPEL log/trace repository, this lets you decide if you want to see your application content on its own (helpful for uncluttered debug of an application), or together with the application server log/trace content (helpful to see impact of server on applications, and vice versa). | false | [
{
"filename": "swg21995397.txt",
"text": "Title: IBM Troubleshoot: Logging Problems in IBM WebSphere Application Server - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Trace analysis information for the logging component in the WebSphere® Application Server. \n\nSYMPTOM\nDoes not display.\n\n\nRESOLVING THE PROBLEM\n \n\nThis document contains troubleshooting information for logging problems in the WebSphere® Application Server. This can help address common issues with this component before calling IBM support and save you time.\n\nTAB NAVIGATION\n * \n * \n * Troubleshoot- selected tab,\n * \n * Collect data [http://www.ibm.com/support/docview.wss?uid=swg21321060]\n\nOverview \nYou will find common questions in this section that may help resolve your logging problems.\n\n1. How do I use JCL with WebSphere® Application Server?\n\nFor information on how to use JCL, see The Support Authority: Using Jakarta Commons Logging (JCL) with WebSphere Application Server [https://www.ibm.com/developerworks/websphere/techjournal/0901_supauth/0901_supauth.html]\n\n2. What are IBM recommendations regarding SLF4J and Logback? \n\nIn general, we recommend that customers use JUL when possible/practical (as mentioned in The Support Authority: A developer's guide to WebSphere Application Server logging [http://www.ibm.com/developerworks/websphere/techjournal/0802_supauth/0802_supauth.html]). JUL provides a good, ubiquitous logging infrastructure, which is suitable for most applications, and integrates with WebSphere Application Server log and trace. Using JUL directly also avoids extra log/trace API \"hops\" that are introduced by using other log/trace frameworks that map to JUL. The WAS logs are generated using JUL Handlers connected to the root JUL Logger.\n\nIn case you don't want to use JUL, or you have code that is already instrumented with another logging package, SLF4J or Logback can be helpful. For example, you may have code already written with Log4J. Log4J log/trace is not routed to WAS log/trace files, and Log4J loggers don't show up in the WAS tree of loggers you can control from the admin console. Further, trace spec settings you make in WAS do not control Log4J logger settings. This is where SLF4J or Logback can come in handy, as you can use them to intercept Log4J calls and forward them to the logging implementation of your choice. In order to integrate well with WAS logs/trace, we would recommend you bind your SLF4J/Logback API to map your log/trace content to JUL -- this will give you the ability to see your logs/trace in the WAS log/trace files, and enable you to have easy admin console control over all of your loggers.\n\n3. How can I get WAS logs to go to syslog or the Windows EventLog?\n\nThere are a number of places that users have asked to be able to direct logs to in the past. Most notably, a number of customers have asked for the ability to send logs to syslog.\n\nWebSphere Application Server sends all of its logs to java.util.logging (JUL), and customers can customize what happens to the log/trace events by way of using JUL Handlers. Once content is sent to JUL, it can be handled in a variety of flexible ways:\n\n1) By default, we store the content in our log files, such as SystemOut.log, trace.log, or the newer log and trace repositories of the High Performance Extensible Logging framework we added in WebSphere Application Server V8.0. We also send the log content over JMX notifications, which allows for remote access.\n\n2) If customers want to send content to places like SMTP, syslog, event log, or a few other places, they can use SLF4J to route WAS logs to Log4J, and use the corresponding Log4J Appenders. In this configuration, WAS logging routes to java.util.logging, SLF4J's Handler routes the request to Log4J, and Log4J can be configured to write log records to a syslog Appender. \n\n3) If users want to do something even more custom, they can write their own JUL Handlers and plug them into WebSphere Application Server. \n\n4. I am unable to turn on WebSphere Application Server trace. The trace state sets to *=off?\n\nThe systemOut.log shows: \n\n\n\n[5/26/15 14:10:44:746 EDT] 000000d9 ManagerAdmin I TRAS0018I: The trace state has changed. The new trace state is *=off. \nThe problem is related to the below two JVM arguments: \n\n-Djava.util.logging.configureByLoggingPropertiesFile=TRUE\n-Djava.util.logging.config.file=<path>/logging.properties \nVerify if the above 2 JVM arguments are configured. If yes, temporary disable it so WAS trace can be enabled. \n\n5. The WebSphere Application Server logging has stopped, what may have caused this? \n\nThe user might have disabled the trace by setting trace output to none. \n\nSetting runtime trace output to none impacts the JVM logs. To do that, the runtime trace spec will be set to *=off, which means to turn off all log levels. If customers just want to disable the trace for debug information only, we recommend setting the runtime trace spec, accordingly, instead of setting runtime trace output to none. For example, set to *=info, which is the default. \n\nVerify if the commons-logging.jar and commons-logging.properties exist in the JVM classpath. If yes, suggest to remove it and put them inside the application (with parent_last setting) or put them in the isolated shared library. \n\n6. How can I separate my logs into separate files for each application? \n\nIn WAS V8.5, we added the application name to log and trace records stored using HPEL (High Performance Extensible Logging). Since HPEL lets you format and filter your log content after it has been persisted to the HPEL log/trace repository, this lets you decide if you want to see your application content on its own (helpful for uncluttered debug of an application), or together with the application server log/trace content (helpful to see impact of server on applications, and vice versa). \n\nFor example, if you had 3 applications called app1, app2, and app3, you could create app specific logs as follows: WAS_INSTALL_ROOT\\bin> logViewer -includeExtensions appName=app1 > app1.log\nWAS_INSTALL_ROOT\\bin> logViewer -includeExtensions appName=app2 > app2.log\nWAS_INSTALL_ROOT\\bin> logViewer -includeExtensions appName=app3 > app3.log \nor see everything in one file as follows: \n\nWAS_INSTALL_ROOT\\bin> logViewer > all.log \n7. How can I add my own java.util.logging.Handler to WAS? \n\nTo create a Handler you need to extend the java.util.logging.Handler class as follows (this example also shows how to filter for only the most severe messages): \n\nimport java.util.logging.Handler;\nimport java.util.logging.Level;\nimport java.util.logging.LogRecord;\npublic class MyHandler extends Handler {\npublic void close() {\n}\npublic void flush() {\n}\npublic void publish(LogRecord record) {\nif (record.getLevel().intValue() >= Level.SEVERE.intValue()) {\n// do something...\n}\n}\n}\nIn your application you can add that Handler to the root logger as follows:\nimport java.util.logging.Handler;\nimport java.util.logging.Logger;\n...\nHandler myHandler = new MyHandler();\nLogger logger = Logger.getLogger(\"\");\nlogger.addHandler(myHandler);\n... \n8. Why can't I set my own log levels using the Logger setLevel method? \n\nThe application server can run in two modes. \n\nBy default, the logger levels are managed, and we expect any changes to logger levels to be done only through wsadmin or through the admin console. When the trace spec update is applied, we explicitly set each logger to the level specified in the trace spec -- we do not leave any named loggers at level set to null. So, while you can change a logger's level using the setLevel method, that change only lasts until you apply your next trace spec update from wsadmin or the admin console. Basically, changes you make via logger.setLevel are temporary at best, and do not apply automatically to children since the children won't have a null level. \n\nAlternately, you can have the server to be configured by the JRE's logging.properties file by setting the java.util.logging.configureByLoggingPropertiesFile property. In this mode, the application server will not touch the logger levels -- you cannot update the levels through the admin console, nor through wsadmin. See Java virtual machine custom properties [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-base-dist&topic=xrun_jvm] for more information on this setting. In this mode, you can specify anything you would normally specify in your logging.properties file. Be careful not to use a console handler though, as that will lead to an infinite loop, since we take data sent to System.out, turn it into LogRecords, and send it to the root logger. \n9. How can I get java.util.logging to initialize from a jre/bin/logging.properties file in the application server? \n\nYou can do this via system property: java.util.logging.configureByLoggingPropertiesFile=true\n\nNote that if you do set up your server in this mode, we will not manage your logger levels via the admin console.\n\nNote also that we will ignore any console handler entries found in the logging.properties file, since we route System.out to the root logger, which would mean that a console handler would cause an infinite recursion. \n\nIf you do use this system property, and you want to change logger levels, you have two choices:\n\n\n * \n * 2) Set the Logger levels programatically using the Logger.setLevel method\n \n\n10. How can I get the full logger name from log and trace records? \n\nThe full logger name can be handy to know for enabling trace. How you get to it depends on what log and trace mode you use: \n\nBasic log and trace mode: \n\nThe basic log format (not to be confused with basic log and trace mode), which is the default format for SystemOut.log / SystemErr.log / trace.log has a truncated version of the logger name: \n\n[4/14/11 9:41:45:218 EDT] 00000021 QuickLogTest W hello fine 54857 \nThere is no way to get the full logger name from basic formatted logs. You need to switch to advanced format for your logs/trace if you want to see the full logger name. Once in advanced format, log contents appear as follows: \n\n[4/14/11 9:41:45:218 EDT] 00000021 W UOW= source=com.ibm.somelogger.QuickLogTest org= prod= component= thread=[WebContainer : 4]\nhello fine 54857 \nHPEL log and trace mode: \n\nYou can use the HPEL LogViewer command line tool to output the log/trace content in either basic or advanced format. \n\n> logviewer -format basic \n\n....\n[4/14/11 9:41:45:218 EDT] 00000021 QuickLogTest W hello fine 54857\n.... \n> logviewer -format advanced \n\n....\n[4/14/11 9:41:45:218 EDT] 00000021 W UOW= source=com.ibm.somelogger.QuickLogTest org= prod= component= thread=[WebContainer : 4]\nhello fine 54857\n... \n11. How can I write HPEL content to a database? \n\nIf you want to write to a Database, any of the following options will work: \n\n1) Write your own log handler (that writes to a database) and plug it into JSR47. (see the Java doc for java.util.logging.Handler) \n\n2) Write an HPEL reading Java application to read the content from an HPEL log repository and write it to a database \n\n3) Write an HPEL reading Java application to read the content from an HPEL log repository and write it out in .csv format, then just use the common database commands to load the .csv content into the database. \n\n12. How do you tune HPEL for optimal performance in tWAS? \n\nIn the server.xml, jvmEntries element: \n- Ensure debugMode is set to false \n- Ensure RAS JMX notifications are disabled by including -Dcom.ibm.ejs.ras.disablerasnotifications=true in genericJvmArguments \n- Ensure -Xquickstart is not in the list of genericJvmArguments \n\n<jvmEntries xmi:id=\"JavaVirtualMachine_1183122130078\" verboseModeClass=\"false\" verboseModeGarbageCollection=\"false\" verboseModeJNI=\"false\" runHProf=\"false\" hprofArguments=\"\" debugMode=\"false\" debugArgs=\"-Dcom.ibm.ws.classloader.j9enabled=true -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=7777\" genericJvmArguments=\"-Dcom.ibm.ejs.ras.disablerasnotifications=true\"> \nIn hpelModel.xml: \n- Ensure textLog is disabled. \n\n<hpelTextLog xmi:id=\"HPELTextLog_1\" enabled=\"false\" dataDirectory=\"${SERVER_LOG_ROOT}\"/> \n13. How can I tell who is writing to System.err / System.out ? \n\nAdd the following to your genericJvmArgument s : \n\n-Xtrace:print=mt,trigger=method{com/ibm/ejs/ras/System*.*,jstacktrace} \n14. How can I identify what code is writing to System.out.println? \n\nAdd the following to your genericJvmArguments and restart the server to see a stack trace for each call to System.out.println: \n\n-Xtrace:print=mt,trigger=method{java/io/PrintStream.println,jstacktrace} \nA snippet of the stack trace for a sample application, which calls System.out.println(), with the above JVM argument set, which identifies that the Hello.printHello (Hello.java:15) writes to System.out. \n\n03:41:01.245*0x3277900 mt.0 > java/io/PrintStream.println(Ljava/lang/String;)V Bytecode method, This = 7fffff49f98\n03:41:01.247 0x3277900 j9trc_aux.0 - jstacktrace:\n03:41:01.248 0x3277900 j9trc_aux.1 - [1] java.io.PrintStream.println (PrintStream.java:829)\n03:41:01.248 0x3277900 j9trc_aux.1 - [2] com.ibm.jvm.io.ConsolePrintStream.println (ConsolePrintStream.java:311)\n03:41:01.250 0x3277900 j9trc_aux.1 - [3] Hello.printHello (Hello.java:15)\n03:41:01.251 0x3277900 j9trc_aux.1 - [4] Hello.main (Hello.java:9)Hello World\n03:41:01.253 0x3277900 mt.6 < java/io/PrintStream.println(Ljava/lang/String;)V Bytecode method \n15. How can I see who called a particular method? \n\nAdd the following to your genericJvmArguments: \n\n-Xtrace:print=mt,trigger=method{java/util/logging/Logger.setLevel,jstacktrace} \n16. What are the .owner files for in the log directory? \n\nThe server creates a .owner file for each of the log files. The file content indicates which cell/node/server is the rightful user of the similarly named log file. This is used as a sort of locking mechanism to make sure that users don't improperly configure their systems. If two or more servers are configured to use the same log directory and file name, we can detect it using the .owner file and we will print a warning in the log file. \n\nFor more information, see Java virtual machine (JVM) log settings [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=JVMLogs_description] \n\n17. How can I correlate information from thread stacks in the javacore with information in my SystemOut.log file? \n\nThere are a few ways to correlate content in WAS logs/trace with content in javacore thread dumps: \n\nBest option, if you are using WebSphere Application Server 8.0 / 8.5: \n\nApplies to: \nWAS 8.0.0.4 and above running with Java 626 SR4 and above \nWAS 8.5.0.2 and above running with Java 7 SR3 and above or Java 626 SR4 and above \n\nIn recent releases, we have made it possible to have the thread id used in the WebSphere Application Server log/trace match with the thread id used in javacores. In WAS 8.0.0.4 and above, you can use a system property to make the thread id in the logs/trace match the Java thread id. In WAS 8.5.0.2 and above, the thread id used in the logs/trace matches with the Java thread id by default. For more information, see PM60913: Introduce ability to use Java Thread ID in Logs instead of LogRecord Thread ID [http://www-01.ibm.com/support/docview.wss?uid=swg1PM60913] and JVM log interpretation [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=rtrb_readmsglogs] \n\nAnother option if you are using High Performance Extensible Logging (HPEL) / Binary Logging: \n\nApplies to: \nFull profile WAS 8.0.0.0 and above \nLiberty profile WAS 8.5.5.0 and above \n\nFull Profile: \nUse the HPEL logViewer command to output the logs in advanced format so you can see the full thread name: \n> logViewer -format advanced (basic is the default format) \n\nLiberty Profile: \nUse the binaryLog command line tool to output the logs in advanced format so you can see the full thread name: \n> binaryLog view --format=advanced \n\nYou will get output that looks like the following: \n\n[4/14/11 9:41:45:218 EDT] 00000021 W UOW= source=com.ibm.somelogger.QuickLogTest org= prod= component= thread=[WebContainer : 4] \nThe javacore contains the same thread name: \n\n3XMTHREADINFO \"WebContainer : 4\" J9VMThread:0x1578D700, j9thread_t:0x150D0D04, java/lang/Thread:0x02517CE0, state:R, prio=5\n3XMTHREADINFO1 (native thread ID:0x15B0, native priority:0x5, native policy:UNKNOWN)\n3XMTHREADINFO3 Java callstack:\n4XESTACKTRACE at com/ibm/io/async/AsyncLibrary.aio_getioev2(Native Method) \nAnother option if you are using Advanced format for your SystemOut.log / trace.log: \n\nApplies to: \nAll currently supported WebSphere Application Server releases. \n\nChange your log/trace format to Advanced. The Advanced format contains the full thread name, as does the javacore. \n\nAdvanced format Log: \n\n[4/14/11 9:41:45:218 EDT] 00000021 W UOW= source=com.ibm.somelogger.QuickLogTest org= prod= component= thread=[WebContainer : 4] \nThe javacore contains the same thread name: \n\n3XMTHREADINFO \"WebContainer : 4\" J9VMThread:0x1578D700, j9thread_t:0x150D0D04, java/lang/Thread:0x02517CE0, state:R, prio=5\n3XMTHREADINFO1 (native thread ID:0x15B0, native priority:0x5, native policy:UNKNOWN)\n3XMTHREADINFO3 Java callstack:\n4XESTACKTRACE at com/ibm/io/async/AsyncLibrary.aio_getioev2(Native Method) \nWhat to do next \nIf the preceding troubleshooting did not help solve your problem, see the Mustgather [http://www-01.ibm.com/support/docview.wss?uid=swg21321060]for logging problems to continue investigation."
}
] |
TRAIN_Q496 | Why am I getting an SSL Key Exception (RSA premaster secret error) when trying to create a syndication pair?
When trying to create the syndication pair for a virtual portal, I am getting the following exception:
"IWKWC0016E: The remote service can not be retrieved. Either the URL you entered is incorrect, the server you indicated does not contain IBM Web Content Manager or the web service has been incorrectly configured and could not be located. Check the log for more details https://1.23.456.789 <-- your ip address or hostname will be shown here
/wps/wcm/vpname/basicauth/SyndicationServlet?reqlocale=en_US& javax.net.ssl.SSLKeyException: RSA premaster secret error" | The default restricted policy file has a 2048 key size limit. If the RSA key size exceeds this limit then this error is expected. | false | [
{
"filename": "swg21663373.txt",
"text": "Title: IBM SSLKeyException: RSA premaster secret error Caused by InvalidKeyException - United States\n\nText:\nJDBC JCC SSL SSLKeyException .InvalidKeyException TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n My java application using the Data Server Driver for JDBC (JCC) is failing to establish SSL connection with following error:\n\nSSLKeyException: RSA premaster secret error. Caused by: java.security.InvalidKeyException: Illegal key size or default parameters. \n\nSYMPTOM\njavax.net.ssl.SSLKeyException: RSA premaster secret error. Caused by: java.security.InvalidKeyException: Illegal key size or default parameters \n\n\nCAUSE\nThe default restricted policy file has a 2048 key size limit. If the RSA key size exceeds this limit then this error is expected.\n\nRESOLVING THE PROBLEM\nThis issue can be resolved by upgrading to the unrestricted policy files, replacing the security policy files with the IBM unlimited cryptography files. Replace the local_policy.jar with the Unrestricted JCE policy File. [https://www14.software.ibm.com/webapp/iwm/web/reg/pick.do?source=jcesdk&lang=en_US]"
}
] |
TRAIN_Q497 | Login to DASH returned "Page cannot be displayed" error
Login to DASH returned "Page cannot be displayed" error | Run the log collector program:
1. Change the directory to <JazzSM Home>/ui/bin
2. Run the following command:
./consoleLogCollector.sh or .bat
Send us the console_logs.zip file located in <JazzSM Home>/ui directory
and attach them to the associated Problem Management Record (PMR). Please include the time the issue was reproduced in the PMR update. Please also provide the DASH version info:
<JazzSM Home>/ui/bin/consolecli.sh Version
Upload the resulting output file to the PMR | false | [
{
"filename": "swg21632844.txt",
"text": "Title: IBM Enabling tracing for the DASH service in Jazz for Service Management - United States\n\nText:\nDASHL2; DASHL2FAQ; DASHL2MUSTG; enable tracing TECHNOTE (FAQ)\n\nQUESTION\n What is the procedure to enable trace logging to troubleshoot DASH runtime issues/errors? \n\nCAUSE\nYou can use trace logging to assist in monitoring system performance and diagnosing problems. Since trace logs can be quite verbose and include many unrelated errors, resetting the logs and then reproducing the problem issue can reduce the time required for log analysis for specific issues.\n\nANSWER\nSteps to enable tracing: \n\n\nEnable trace logging. \n\n 1. Log into the DASH. After logging in navigate to Console Settings [/support/docview.wss?uid=swg21632844&aid=1] > Websphere Administrative Console. \n 2. Navigate to Troubleshooting -> Logs & Trace \n 3. Click on the Server1 -> Select Diagnostic Trace Service. Increase the Maximum Number of Historical Files from 1 to 10. \n 4. Click Apply, then select Change Log Detail Levels. \n 5. Click on Runtime tab to enable tracing for the DASH process that is currently running. Enabling tracing from the Runtime tab will keep tracing active until the next time the DASH server process is stopped. To make tracing persistent even after stopping and restarting the DASH server process click the Configuration tab instead. \n 6. Clear the trace string in the Groups box and replace it with the following:\n \n *=info: com.ibm.isc.*=all: com.ibm.isclite.*=all: com.ibm.iscportal.*=all: com.ibm.isclite.service.datastore.consoleproperties.*=INFO\n \n For the Connection manager (data provider related issues) you will want to enable all for the following components:\n \n *=info: com.ibm.isclite.rest.*=all:com.ibm.tivoli.conmgr.*=all \n 7. Click on the Apply button. \n 8. If you enabled tracing from the Configuration tab in step 4, then click the \"Save\" link that appears at the top of the page. (\"Save to master configuration\")\n\n\nOnce tracing is enabled, reproduce the DASH runtime issue. Note the time that the issue was reproduced so that the issue can be easily correlated with the trace log entries. \n\nRun the log collector program:\n\n\n 1. Change the directory to <JazzSM Home>/ui/bin \n 2. Run the following command:\n \n ./consoleLogCollector.sh or .bat\n \n Send us the console_logs.zip file located in <JazzSM Home>/ui directory\n\n\nand attach them to the associated Problem Management Record (PMR). Please include the time the issue was reproduced in the PMR update. Please also provide the DASH version info:\n<JazzSM Home>/ui/bin/consolecli.sh Version\n\nUpload the resulting output file to the PMR"
}
] |
TRAIN_Q498 | How do I reduce the amount of CPU being consumed by Just In Time (JIT) compilation?
My Portal system is experiencing period bursts of high CPU. After reviewing some data, I've determined the primarily culprit behind these CPU bursts are Just In Time (JIT) compilation threads, similar to the following:
3XMTHREADINFO "JIT Compilation Thread-0"
J9VMThread:0x0000000040004F00, j9thread_t:0x0000010010122040,
java/lang/Thread:0x00000007011CAA58, state:CW, prio=10
3XMJAVALTHREAD (java/lang/Thread getId:0x4, isDaemon:true)
3XMTHREADINFO1 (native thread ID:0x39100EF, native priority:0xB, native policy:UNKNOWN)
Why is this happening and how can I reduce the amount of CPU that JIT is using?
| - | true | [] |
TRAIN_Q499 | Security Bulletin: IBM MQ Appliance is affected by a GNU C library (glibc) vulnerability (CVE-2017-8804)
I need to understand details regarding Security Bulletin: IBM MQ Appliance is affected by a GNU C library (glibc) vulnerability (CVE-2017-8804). Where can I find this information? | CVEID:CVE-2017-8804 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8804]
DESCRIPTION:glibc is vulnerable to a denial of service, caused by improper handling of buffer deserialization in the xdr_bytes and xdr_string functions. By sending a specially-crafted UDP packet, a remote attacker could exploit this vulnerability to cause virtual memory allocation, or memory consumption on the system.
CVSS Base Score: 7.5
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/125760 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125760]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) | false | [
{
"filename": "swg22009796.txt",
"text": "Title: IBM Security Bulletin: IBM MQ Appliance is affected by a GNU C library (glibc) vulnerability (CVE-2017-8804) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM MQ Appliance has addressed a vulnerability in GNU C library (glibc). \n\nVULNERABILITY DETAILS\nCVEID:CVE-2017-8804 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8804]\nDESCRIPTION:glibc is vulnerable to a denial of service, caused by improper handling of buffer deserialization in the xdr_bytes and xdr_string functions. By sending a specially-crafted UDP packet, a remote attacker could exploit this vulnerability to cause virtual memory allocation, or memory consumption on the system.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/125760 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125760]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ Appliance 8.0 \n\nMaintenance levels between 8.0.0.0 and 8.0.0.7\nIBM MQ Appliance 9.0.x Continuous Delivery (CD) Release \n\nContinuous delivery updates between 9.0.1 and 9.0.3\n\nREMEDIATION/FIXES\nIBM MQ Appliance 8.0 \n\nApply fixpack 8.0.0.8 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&function=textSearch&text=8.0.0.8]\nIBM MQ Appliance 9.0.x Continuous Delivery (CD) Release \n\nApply Continuous Delivery Release 9.0.4 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&function=textSearch&text=9.0.4]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 04 December 2017 Original version published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY."
}
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.