[ { "doc_id": "techqa_DEV_Q243", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The COBOL Copybook importer option no longer appears in the list of available importers.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q243", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Some files are not correctly overwritten / modified during the upgrade.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q243", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "IBM WebSphere Transformation Extender 8.4.1.1 Design Studio on Windows", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q243", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Install WTX Design Studio 8.4.1.1 in an empty directory, and then perform any installation customization.\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q243", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "IBM Developer for z systems 14.1.1 can't download copybooks when\n Bidi setting is enable and the Property Group have a COBOL\n SYSLIB defined with more than 1 PDSE.\n\nSteps to recreate:\n 1) Windows->Preferences->Bidirectional Development->Enable\n Bidirectional development capabilities\n 2) Define a Property Group and a COBOL Syslib with 2 PDSE\n 3) Associate the Property group to a Cobol member defined\n with copybooks\n 4) Open the cobol member\n The copybooks are not downloading.\n From the bottom task bar , Downloading copybook for program:\n (0%) is shown and never progress.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q243", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "COBOL copybooks fail to download when BIDI options are enabled\n and the Property Group contains a COBOL SYSLIB with two or more\n PDSEs.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q243", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "BIDI option processing for copybooks has been updated in the\n client\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q243", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI93890\nREPORTED COMPONENT NAME\n EXP FOR Z/OS CL\nREPORTED COMPONENT ID\n 5655EXP00\nREPORTED RELEASE\n 311\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2018-02-16\nCLOSED DATE\n 2018-03-26\nLAST MODIFIED DATE\n 2018-03-26\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q243", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n EXP FOR Z/OS CL\nFIXED COMPONENT ID\n 5655EXP00", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q243", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "A FIX IS AVAILABLE\nRational Developer for System z Fix Pack 1 (8.5.1.1) for 8.5.1, 8.5.0.1, and 8.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24034596]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q243", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Rational Developer for System z Software Analyzer hangs when\n analyzing a program with many copybooks.\n\n There are two scenarios:\n Common is that the default COBOL rules are selected. The use\n of custom rules is not significant.\n 1) Start Software Analyzer while the copybooks were\n downloading - hang with the large number (e.g. 2147483647%)\n at the (bottom right) status area.\n 2) Wait until all the status message are done (copybook\n downloads and COBOL syntax parser) in the status area\n (bottom right) and then start Software Analyzer - hang\n with the Running Software Analyzer 100% status at the\n bottom right.\n\n Cause:\n This problem is caused by a deadlock that occurs when\n Software Analyzer is running while the copybooks are being\n loaded", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q243", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "The locking of copybook resources collided with resource locking\n of concurrent jobs.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q243", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Modified code to avoid resource-locking collisions with\n concurrent jobs.\n\nThe problem listed in this APAR has been resolved with\n IBM Rational Developer for System z V8.5.1.1 Fix Pack which\n is available from the Recommended Fixes support download page:\n http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335 [http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335]\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q243", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM80999\nREPORTED COMPONENT NAME\n RATL DEV FOR SY\nREPORTED COMPONENT ID\n 5724T0700\nREPORTED RELEASE\n 850\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-01-21\nCLOSED DATE\n 2013-03-21\nLAST MODIFIED DATE\n 2013-03-21\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q243", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n RATL DEV FOR SY\nFIXED COMPONENT ID\n 5724T0700", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q243", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R850 PSY\n UP\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q243", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Correct copyright statement in COBOL version of DFHTCTTE the\n cobol version of DFHTCTTE is currently coded as a PL/I style\n comment which results in compiler error when any cobol program\n including it is compiled. Ditto for DFHJCADS.\n Build process has added invalid COPYRIGHT statement to DFHTCTTE\n and DFHJCADS COBOL copybooks.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q243", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: CICS/VSE R230 users of the Cobol versions *\nof copybooks DFHTCTTE and DFHJCADS. *\n\nPROBLEM DESCRIPTION: Compiler errors result when compiling *\nthe Cobol versions of copybooks *\nDFHTCTTE and DFHJCADS. *\n\nRECOMMENDATION: *\n\nThe COBOL versions of copybooks DFHTCTTE and DFHJCADS are\n currently coded with PL/1 style comments for the COPYRIGHT\n header statements. Any COBOL program including these Cobol\n copybooks will therefore compile with errors.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q243", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "DFHTCTTE and DFHJCADS have had their COPYRIGHT header\n changed from PL/I style to Cobol style comments.\n\nKeywords: PTM 74316 PTM74316 PL1 PLI\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q243", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PN70961\nREPORTED COMPONENT NAME\n CICS/VSE\nREPORTED COMPONENT ID\n 568602601\nREPORTED RELEASE\n 14X\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 1995-05-03\nCLOSED DATE\n 1995-05-09\nLAST MODIFIED DATE\n 1995-06-16\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n UN76709\n\nMODULES/MACROS\nDFHJCADS DFHTCTTE", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q243", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n CICS/VSE\nFIXED COMPONENT ID\n 568602601", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q243", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R14X PSY UN76709\n UP95/05/10 P E140\n\nz/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q243", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "You are running DFHWS2LS and the resulting cobol copybooks\n contain level 88 fields with names that are longer than 30\n characters. This will result in errors at compile time because\n 30 characters is the max length a cobol field can have. This\n problem will occur even if you have specified\n NAME-TRUNCATION=RIGHT in DFHWS2LS.\n Additional Keywords:\n KIXREVSCB", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q243", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All CICS users. *\n\nPROBLEM DESCRIPTION: DFHWS2LS generates level88 cobol fields *\nwith names over 30 characters in length *\nresulting in errors at compile time. *\n\nRECOMMENDATION: *\n\n DFHWS2LS is called to generate language structure in COBOL from\n a WSDL file. There are names over 30 characters in length in\n the WSDL file. These names are used in Level88 fields in the\n language structure and are not truncated. It results in errors\n at compile time as COBOL cannot handle names that are longer\n than 30 characters.", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q243", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "DFHWS2LS has been changed to generate valid COBOL level 88 field\n names.\n\nTEMPORARY FIX\nFIX AVAILABLE BY PTF ONLY", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q243", "section_id": 4, "heading": "COMMENTS", "parent": null, "text": "\u017e**** PE11/09/13 FIX IN ERROR. SEE APAR PM47550 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM47550] FOR DESCRIPTION\n \u017e**** PE12/07/03 FIX IN ERROR. SEE APAR PM65436 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM65436] FOR DESCRIPTION", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q243", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM43503\nREPORTED COMPONENT NAME\n CICS TS Z/OS V4\nREPORTED COMPONENT ID\n 5655S9700\nREPORTED RELEASE\n 700\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2011-07-12\nCLOSED DATE\n 2011-07-28\nLAST MODIFIED DATE\n 2012-07-12\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n PM37166 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM37166]\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n UK70146\n\nMODULES/MACROS\nDFJ@H176", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q243", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n CICS TS Z/OS V4\nFIXED COMPONENT ID\n 5655S9700", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q243", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R70D PSY UK70146 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK70146]\n UP11/08/09 P F108\n\nFIX IS AVAILABLE\nSELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL. YOU WILL BE REQUIRED TO SIGN IN. DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES.", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q280", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "The WebSphere Transformation Extender for Integration Servers install process cannot locate a keyword in the .nifregistry file", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q280", "section_id": 1, "heading": "ENVIRONMENT", "parent": null, "text": "During the installation of WebSphere Transformation Extender for Integration Servers v8.2.0.x", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q280", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "An error message, \"Setup has detected that you are trying to install a product that requires an IBM WebSphere Integration Server as a prerequisite.\" will be displayed.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q280", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The following steps can be taken to edit the .nifregistry file to resolve this installation issue:\n\nOperating System root installed .nifregistry location Windows %SystemRoot% AIX /usr/.ibm/.nif Solaris, Linux, HP-UX /opt/.ibm/.nif Operating System non-root installed .nifregistry location AIX, Solaris, Linux, HP-UX ~/.nif\n\n1) Open the .nifregistry file with a file editor of your choice. The .nifregistry file is located in the directory depicted in the table listed above.\n\n2) Look for a line similar to the following that contains \"WebSphere/ESB/\":\n\n\n\n3) Change the productid to be WBI.\n\n4) After editing the .nifregistry file, the line should now look like:\n", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q280", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Your version of WBI may be different, but as long as it is a 6.1.0.x release, it is relative to this Technote.\n\n5) Install the WebSphere Transformation Extender for Integration Server software.\n\n6) After the install is complete, restore the productid to \"ND\" in the .nifregistry file.\n\nThe .nifregistry file may have slightly different values in it, the key is to modify just the productid.\n\nPRODUCT ALIAS/SYNONYM\n WTX Integration Server\nAscential DataStage TX", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q280", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What directories does the WTX Map Primitive use in IBM\u00ae WebSphere\u00ae Transformation Extender for WebSphere Enterprise Service Bus?", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q280", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "For maps that are\nSpecified by Use map from project setting\nSet in the service message object (SMO) mapServerLocation property\nSet in the SMO and overridden at runtime\n\nThe home directory is:\n\n< WESBserver >/temp/WTX/< flowName >/< mediationName >\n\nwhere < WESBserver> is the server name under the profiles directory in the WebSphere Enterprise Service Bus or WebSphere Process Server installation location.\n\nThe directory of the WebSphere Transformation Extender map's default audit log, trace log, and workspace is\n\n< WESBserver >/logs/WTX/< flowName >/< mediationName >\n\nWebSphere Transformation Extender; WebSphere TX; WTX; ITX; application programming DOWNLOADABLE FILES", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q280", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This document describes how to download IBM\u00ae WebSphere\u00ae Transformation Extender for Application Programming V8.4.1.4.", "logical_doc_id": 3, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q280", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "WebSphere Transformation Extender for Application Programming provides the core transformation engine, callable by its programming interface. C, Java, Enterprise JavaBeans (EJB), Cobol, and .Net application programming interfaces (APIs) are available to engage the transformation engine to process a prebuilt transformation.\n\nPREREQUISITES\nSee the system requirements for the supported hardware and software:\n\nURL LANGUAGE SIZE(Bytes) IBM Transformation Extender system requirements [http://www.ibm.com/support/docview.wss?uid=swg27045341] English 10\nINSTALLATION INSTRUCTIONS\nAfter you download the code package, follow the instructions in the release notes to install the product:\n\nURL LANGUAGE SIZE(Bytes) IBM Transformation Extender release notes [http://www.ibm.com/support/docview.wss?&uid=swg27008337#841] English 10\nDOWNLOAD PACKAGE\nEntitled customers can download the code package from Fix Central:\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options Fix Central 11 Mar 2016 English 172000 HTTP [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Other%2Bsoftware&product=ibm/WebSphere/WebSphere+Transformation+Extender&release=8.4.1.4&platform=All&function=all&useReleaseAsTarget=true]\nTECHNICAL SUPPORT\n Get online support through the following links:\n\nFix Central support: http://www.ibm.com/systems/support/fixes/en/fixcentral/help/index.html [http://www.ibm.com/systems/support/fixes/en/fixcentral/help/index.html]\n\nTransformation Extender support: http://www.ibm.com/software/integration/wdatastagetx/support [http://www.ibm.com/software/integration/wdatastagetx/support]\n\n8.4.0.2; WTX 8.4.0.2; 8.3.2; HIPAA 4.3.2.2; 8.2.1.6 NEWS", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q280", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "April 27, 2012\n\nIBM WebSphere\u00ae Transformation Extender V8.4.0.2 and Q2 Industry Packs are now available through Passport Advantage.\n\nBuild ID: 8.4.0.2(12)\n\nIndustry Pack releases:\n\nPack for HIPAA EDI 4.3.2.2\nTrading Manager 8.2.1.6\nPack for SAP R/3 8.3.2", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q280", "section_id": 3, "heading": "CONTENT", "parent": null, "text": "Fix List WebSphere Transformation Extender V8.4.0.2 Fix List [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg27024860]\nWTX 8.4.0.2 Core Release Notes Release Notes for IBM WebSphere Transformation Extender V8.4.0.2 [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg27019258] Release Notes for IBM WebSphere Transformation Extender with Launcher Hypervisor Edition [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg27022312]\nWTX 8.4.0.2 Core Download Documents WebSphere Transformation Extender with Command Server [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg24032141] WebSphere Transformation Extender Design Studio [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg24032142] WebSphere Transformation Extender Online Library [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg24027668] WebSphere Transformation Extender with Launcher Hypervisor Edition [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg24032144] WebSphere Transformation Extender with Launcher [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg24032143] WebSphere Transformation Extender Launcher Agent [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg24032145] WebSphere Transformation Extender for Application Programming [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg24032140] WebSphere Transformation Extender Secure Adapter Collection [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg24032147] WebSphere Transformation Extender for Integration Servers [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg24032146]\n\nWTX Pack Release Notes Release Notes for WebSphere Transformation Extender Pack for HIPAA EDI 4.3.2.2 [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg27024259] Release Notes for WebSphere Transformation Extender Trading Manager 8.2.1.6 [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg27023979] Release Notes for WebSphere Transformation Extender Pack for SAP R/3 8.3.2 [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg27024492]\nWTX Pack Download Documents WebSphere Transformation Extender Pack for HIPAA EDI 4.3.2.2 [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg24032514] WebSphere Transformation Extender Trading Manager 8.2.1.6 [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg24032513] WebSphere Transformation Extender Pack for SAP R/3 8.3.2 [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg24032512]\nWTX Pack Fix Lists WebSphere Transformation Extender Pack for HIPAA EDI 4.3.2.2 Fix List [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg27024912] WebSphere Transformation Extender Trading Manager 8.2.1.6 Fix List [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg27024913] WebSphere Transformation Extender Pack for SAP R/3 8.3.2 Fix List [http://www.ibm.com/support/docview.wss?rs=2320&uid=swg27024914]\n\nIBM PassPort Advantage Online [http://www-01.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\n\nPRODUCT ALIAS/SYNONYM\n Ascential DataStage TX Mercator", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q280", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Error 'DTXPlugin cannot be located' is shown if you \"move over\" the ITX Plugin-Node after installing IBM Transformation Extender (ITX) with IBM Integration Bus (IIB) Toolkit.", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q280", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Two installations of IBM Transformation Extender (ITX) installed on the same system with IBM Integration Bus (IIB) Toolkit.", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q280", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "Using ITX V9.0.0.x with IIB10.0.0.x and two versions of ITX are installed on the same system.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q280", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "The TX Map node plugin displays an error in a new installation when you \"move over\" the ITX Plugin-Node.", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q280", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Use a new Work Space.", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q253", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This document details the system requirements for IBM Content Collector Version 4.0.1.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Always 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\nAll versions [http://www.ibm.com/support/docview.wss?uid=swg27040212]\nVersion 4.0.1- selected tab,\nHARDWARE REQUIREMENTS\nContent Collector server\nClient workstations\nSOFTWARE PREREQUISITES\nOperating system and software\nWeb application server\nCOLLECTION SOURCE SYSTEMS\nLotus Domino\nMicrosoft Exchange\nSMTP email\nMicrosoft SharePoint\nIBM Connections\nFile system\nARCHIVE SYSTEMS\nIBM Content Manager\nIBM FileNet P8\nLEGACY RESTORE\nLegacy restore\nRETENTION POLICY DISTRIBUTION SUPPORT\nRetention Policy Distribution Support\nOPTIONAL SOFTWARE\nOptional software\n\nIBM CONTENT COLLECTOR PRODUCTS\nContent Collector for Email\nContent Collector for File Systems\nContent Collector for IBM Connections\nContent Collector for Microsoft SharePoint\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\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", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "If 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:\nLotus Notes or Lotus iNotes\nMicrosoft 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\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\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\nEnterprise Edition\n32-bit (x86)\n64-bit (x86-64)\n\nService Pack 2 Windows Server 2008 R2 * Standard Edition\nEnterprise Edition\n64-bit (x86-64)\n\nService Pack 1 Windows Server 2012 * Datacenter Edition\nStandard Edition\n64-bit (x86-64)\n\n[/support/docview.wss?uid=swg27042658&aid=1] Windows Server 2012 R2 * Datacenter Edition\nStandard Edition\n64-bit (x86-64)\n\n[/support/docview.wss?uid=swg27042658&aid=1] Windows Server 2016 * Datacenter Edition\nStandard Edition\n64-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.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "REQUIRED SOFTWARE\nThe following software must be installed on the server where IBM Content Collector is installed.\nImportant:\nOn 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.\nFor 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", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "WEB 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:\n8.0.0.13\n8.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:\nMicrosoft Visual C++ 2008 Service Pack 1 Redistributable Package\nMicrosoft Visual C++ 2008 Service Pack 1 Redistributable Package ATL Security Update\nMicrosoft 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\n17 or 24 Extended Support Release (ESR)\n24\n28\n31 Extended Support Release (ESR)\n32\n33\n34\n35\n\nMicrosoft Internet Explorer * 8\n9\n10\n11\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\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:", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Server software Client software Other software requirements Notes * Lotus Domino 8.5.0\nLotus Domino 8.5.1\nLotus Domino 8.5.2\nLotus Domino 8.5.3 FP6\nDomino 9.0\nDomino 9.0.1 FP2\nDomino 9.0.1 FP4\nDomino 9.0.1 FP5\nDomino 9.0.1 FP6\nDomino 9.0.1 FP7\nDomino 9.0.1 FP8\nLotus Notes 8.5.0\nLotus Notes 8.5.1\nLotus Notes 8.5.2\nLotus Notes 8.5.3 FP6\nNotes 9.0 (along with the Browser plug-in)\nNotes 9.0.1 (along with the Browser plug-in)\nNotes 9.0.1 FP2\nNotes 9.0.1 FP4\nNotes 9.0.1 FP5\nNotes 9.0.1 FP6\nNotes 9.0.1 FP7\nNotes 9.0.1 FP8\nWindows 7 Service Pack 1 (32-bit and 64-bit)\nWindows 8 Professional Edition\nWindows 8.1 Professional Edition\nMac OS X 10.8.x (32-bit and 64-bit)\nMac OS X 10.9.x (32-bit and 64-bit)\nWindows 10 Professional Edition\nWindows 10 Enterprise Edition\nMozilla Firefox 14\nMozilla Firefox 17 or 24 Extended Support Release (ESR)\nMozilla Firefox 24\nMozilla Firefox 28\nMozilla Firefox 31 Extended Support Release (ESR)\nMozilla Firefox 32\nMozilla Firefox 33\nMozilla Firefox 34\nMozilla Firefox 35\nMicrosoft Internet Explorer 8\nMicrosoft Internet Explorer 9\nMicrosoft Internet Explorer 10\nMicrosoft Internet Explorer 11\nMicrosoft 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\nSettings\nHelp\nLotus iNotes 8.5.0\nLotus iNotes 8.5.1\nLotus iNotes 8.5.2\nLotus iNotes 8.5.3 FP6\niNotes 9.0\niNotes 9.0.1 FP2\niNotes 9.0.1 FP4\niNotes 9.0.1 FP5\niNotes 9.0.1 FP6\niNotes 9.0.1 FP7\niNotes 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\nStarting 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.", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "If 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:\nMicrosoft Visual C++ 2010 Redistributable Package [http://www.microsoft.com/downloads/details.aspx?FamilyID=A7B7A05E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en&displaylang=en]\nMicrosoft Security Advisory: Insecure library loading could allow remote code execution [http://support.microsoft.com/kb/2533623]\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\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:\nAutomatic client document retrieval does not work in the standard configuration of Notes client version 8.5, 8.5.3, or 9.\n\nBack to top\n\nMICROSOFT EXCHANGE\nSERVER\nThe following table describes the supported versions of Microsoft Exchange Server:", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Server software Notes * Microsoft Exchange Server 2007 Standard and Enterprise Edition with Service Pack 3 Update Rollup 11\nMicrosoft Exchange Server 2010 Standard and Enterprise Edition with Service Pack 2 Update Rollup 4 or Service Pack 3\nMicrosoft Exchange Server 2013 Standard and Enterprise Edition with Service Pack 1 (KB2860242 [http://support.microsoft.com/kb/2860242])\nMicrosoft 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\nWindows 7 Ultimate Service Pack 1\nWindows 7 Enterprise Service Pack 1\nWindows 8 Professional Edition\nWindows 8.1 Professional Edition\nWindows 10 Professional Edition\nWindows 10 Enterprise Edition\nMicrosoft Outlook 2007 Service Pack 3\nMicrosoft Outlook 2010 Service Pack 2\nMicrosoft Outlook 2013\nMicrosoft Outlook 2016\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\nMicrosoft Internet Explorer 8, 9, 10, or 11\nMicrosoft Edge\nChrome 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:", "logical_doc_id": 0, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Virtualization 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\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)\nMicrosoft Exchange Server 2010 SP2\nMicrosoft Exchange Server 2013 SP1\nMicrosoft 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\nExchange Server version Operating system for the Outlook Web App Service (required) Other software requirements * Microsoft Exchange Server 2007 Service Pack 3 (or later)\nMicrosoft Exchange Server 2010 SP2\nWindows Server 2008 Service Pack 2\nWindows Server 2008 R2 Service Pack 1\nMicrosoft IIS Server 6 or 7\n.NET Framework 4.5\nMicrosoft Exchange Server 2013 SP1\nWindows Server 2008 R2 Service Pack 1\nWindows Server 2012 R2\nMicrosoft IIS Server 7.5 (or later)\nMicrosoft Exchange Server 2016\nWindows Server 2012\nWindows Server 2012 R2\n.NET Framework 4.5.2\n\nIn the Internet Information Service (IIS) Manager:\nSet the Web Service Extension ASP.NET V4.5 to Allowed.\nSet the identity of the application pool where the OWA service resides to NetworkService.\nSet the .NET Framework version to v4.5\nDisable 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\nHow to get:", "logical_doc_id": 0, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "You can purchase Microsoft IIS Server and .NET Framework from www.microsoft.com [http://www.microsoft.com].\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\nExchange Server version Software prerequisites for OWA clients * Microsoft Exchange Server 2007 Service Pack 3 (or later)\nMicrosoft Exchange Server 2010 SP2\n.NET Framework 2.0 (or later)\nMicrosoft Internet Explorer 8, 9, or 10\nMicrosoft Exchange Server 2013 SP1\nMicrosoft Internet Explorer 9, 10 or 11\nGoogle Chrome 13\nMicrosoft Edge\nMicrosoft Exchange Server 2016\nMicrosoft Internet Explorer 10 or 11\nMicrosoft Edge\n\nThe following restrictions apply:\nIBM Content Collector OWA support does not work with if the option \"Use the blind and low vision experience\" in the OWA settings is used.\nIBM Content Collector OWA support works only with OWA Premium Mode.\nIBM 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.\nIBM 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)\nMicrosoft Edge is supported starting with IBM Content Collector 4.0.1 Fix Pack 2\nIBM Content Collector OWA support on Exchange 2016 is supported starting from IBM Content Collector 4.0.1 Fix Pack 3 Back to top\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:", "logical_doc_id": 0, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q253", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Mail 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\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\nIBM Connections IBM Connections 4.5 Documents from IBM Connections can be archived in the following archive systems:\nIBM Content Manager Enterprise Edition (all supported versions)\nIBM 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.", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q253", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "The File System Repository Connector also allows for archiving to cloud file systems.\n\nBack to top\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\nLinux\nWindows\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.", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q253", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Support 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\nLinux\nWindows\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\nLinux\nWindows\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\nz/OS", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q253", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "IBM 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:\nContent Manager Enterprise Edition [http://www.ibm.com/support/docview.wss?uid=swg24035460]\nContent 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\nThe 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", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q253", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "IC58821\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:\nContent Manager fix packs [http://www.ibm.com/support/docview.wss?uid=swg27009038]\nNet 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\nLinux\nSolaris\nWindows\n\n.NET Clients The .NET Clients component is provided through the FileNet P8 Content Engine installer. Java Clients (Other Applications) The Java Clients component is provided through the FileNet P8 Content Engine Client installer. [/support/docview.wss?uid=swg27042658&aid=1] Important: For IBM FileNet P8 Content Engine 5.1 and 5.2, apply the fix that is described in Security Bulletin: IBM FileNet Content Manager and IBM Content Foundation \u2013 Oracle Outside In Technology security vulnerabilities (CVE-2013-5791, CVE-2013-5763) [http://www.ibm.com/support/docview.wss?uid=swg21660219]. IBM Content Foundation V5.2 or V5.2.1\n\nFor the required level of the database management system, see the IBM Content Foundation system requirements [http://www.ibm.com/support/docview.wss?uid=swg27038265]. * AIX\nLinux\nSolaris\nWindows", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q253", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": ".NET Clients The .NET Clients component is provided through the IBM Content Foundation Content Platform Engine installer. Java Clients (Other Applications) The Java Clients component is provided through the IBM Content Foundation Content Platform Engine installer. [/support/docview.wss?uid=swg27042658&aid=1] Important: For IBM Content Foundation V5.2.0, apply the fix that is described in Security Bulletin: IBM FileNet Content Manager and IBM Content Foundation \u2013 Oracle Outside In Technology security vulnerabilities (CVE-2013-5791, CVE-2013-5763) [http://www.ibm.com/support/docview.wss?uid=swg21660219]. IBM FileNet Image Services 4.1.2 or 4.2 * AIX\nHP-UX\nSolaris\nWindows\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:\nFileNet Content Manager [http://www.ibm.com/support/docview.wss?uid=swg24034227]\nContent Foundation [http://www.ibm.com/support/docview.wss?uid=swg24034868]\nFileNet 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\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\nLinux\nSolaris\nWindows\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].", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q253", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "The 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\nLinux\nSolaris\nWindows\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\nLinux\nWindows\n\nInterim Fixes are available on Fix Central [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=FileNet+Product+Family&product=ibm/Information+Management/FileNet+Content+Search+Services&release=5.1.0.0&platform=All&function=all].\n\nImportant: For IBM FileNet P8 Content Search Services 5.1 and 5.2, apply the fix that is described in Security Bulletin: IBM FileNet Content Manager and IBM Content Foundation \u2013 Oracle Outside In Technology security vulnerabilities (CVE-2013-5791, CVE-2013-5763) [http://www.ibm.com/support/docview.wss?uid=swg21660219]. Java Clients (Other Applications) 5.1 Fix Pack 2 or 5.2 * Content Search Services server\nIBM Content Collector server\nAIX\nLinux\nSolaris\nWindows\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\nLinux\nSolaris\nWindows\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\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.", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q253", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "There are some limitations when using IBM Content Collector Legacy Restore instead of the CommonStore products, including the following restrictions:\nIBM Content Collector Legacy Restore provides read-only access to documents, but no write access.\nFor documents that are stored in Content Manager OnDemand or Content Manager for z/OS, search is not supported.\nFor 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\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\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\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:\nIBM eDiscovery Manager [http://www.ibm.com/support/docview.wss?uid=swg24035931]\nIBM Content Classification [http://www.ibm.com/support/docview.wss?uid=swg24029115]\nIBM Enterprise Records [http://www.ibm.com/support/docview.wss?uid=swg24035858]\nIBM Content Navigator [http://www.ibm.com/support/docview.wss?uid=swg24034327]\n\nBack to top\n\nIBM CONTENT COLLECTOR PRODUCT REPORTS\nCONTENT COLLECTOR FOR EMAIL\nREQUIREMENTS\nBY PLATFORM\nMac OS [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&osPlatforms=Mac OS]\nWindows [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&osPlatforms=Windows]\nSupported Hypervisors [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/vesForProduct?deliverableId=1385722855736]\n\nREQUIREMENTS\nBY COMPONENT\nFileNet P8 Content Search Services Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_862A48C058E511E3A11D923472D26C14]\nLegacy Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_8626C65058E511E3A11D923472D26C14]\nNotes Client Extension [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Desktop_862AE50058E511E3A11D923472D26C14]\nOutlook Extension [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Desktop_862BA85058E511E3A11D923472D26C14]\nOutlook Web App Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_862789A058E511E3A11D923472D26C14]\nServer [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_862825E058E511E3A11D923472D26C14]\nSharePoint Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_8628E93058E511E3A11D923472D26C14]\nText Search Support for Content Manager [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_8629857058E511E3A11D923472D26C14]\n\nRELATED REQUIREMENTS\nNo related requirements.\n\nBack to top\n\nCONTENT COLLECTOR FOR FILE SYSTEMS\nREQUIREMENTS\nBY PLATFORM\nWindows [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&osPlatforms=Windows]\nSupported Hypervisors [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/vesForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A]", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q253", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "REQUIREMENTS\nBY COMPONENT\nFileNet P8 Content Search Services Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&duComponentIds=Server_F6D064B0C7E811E4A93F4F818B63D91A]\nServer [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&duComponentIds=Server_F6C89C80C7E811E4A93F4F818B63D91A]\nText Search Support for Content Manager [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&duComponentIds=Server_F6C9D500C7E811E4A93F4F818B63D91A]\n\nRELATED REQUIREMENTS\nNo related requirements.\n\nBack to top\n\nCONTENT COLLECTOR FOR IBM CONNECTIONS\nREQUIREMENTS\nBY PLATFORM\nWindows [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&osPlatforms=Windows]\nSupported Hypervisors [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/vesForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A]\n\nREQUIREMENTS\nBY COMPONENT\nFileNet P8 Content Search Services Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&duComponentIds=Server_1CE258D0C7ED11E4A93F4F818B63D91A]\nServer [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&duComponentIds=Server_1CE035F0C7ED11E4A93F4F818B63D91A]\nText Search Support for Content Manager [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&duComponentIds=Server_1CE1BC90C7ED11E4A93F4F818B63D91A]\n\nRELATED REQUIREMENTS\nNo related requirements.\n\nBack to top\n\nCONTENT COLLECTOR FOR MICROSOFT SHAREPOINT\nREQUIREMENTS\nBY PLATFORM\nWindows [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&osPlatforms=Windows]\nSupported Hypervisors [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/vesForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A]\n\nREQUIREMENTS\nBY COMPONENT\nFileNet P8 Content Search Services Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E3176240C7EB11E4A93F4F818B63D91A]\nServer [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E3151850C7EB11E4A93F4F818B63D91A]\nSharePoint Support [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E315DBA0C7EB11E4A93F4F818B63D91A]\nText Search Support for Content Manager [http://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E3169EF0C7EB11E4A93F4F818B63D91A]\n\nRELATED REQUIREMENTS\nNo related requirements.\n\nBack to top", "logical_doc_id": 2, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q253", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "2017-06-14T11:23:22Z Error 0x1838 Microsoft hotfix KB2732673 for Windows 2008 R2 is not installed. Without this hotfix, the Win32 API function DeleteFile might fail silently. Therefore, the file system connector will ignore any task route service requests. To ensure that the hotfix is installed, Windows 2008 R2 Service Pack 1 or later must be installed and the version of \\drivers\\rdbss.sys must be equal to or greater than 6.1.7601.22377. ibm::ctms::filesystem_connector::IsValidOSInstall (validatewindows2008r2.cpp:221)", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Missing some Microsoft Windows Server 2008 R2 Hotfixes needed by ICC for FileSystem", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q253", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "Windows Server 2008 R2 Enterprise 64 bit Operating System. Service Pack1\nTarget Repository: FileNet Content manager 5.1.0.3 dap 501.003.019\nICC Version : Upgraded to ICC 4.0.1", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q253", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The mentioned Microsoft hotfix KB2732673 is part of ICC 4.0.1 prerequisites.\n\nhttp://www-01.ibm.com/support/docview.wss?uid=swg27042658 [http://www-01.ibm.com/support/docview.wss?uid=swg27042658]\ncheck the Required Software section under ICC Server software prerequisites.\nEspecially the following ones listed for File System connector:\nMicrosoft Windows Server 2008 R2 SP1 hotfix KB 2732673 - http://support.microsoft.com/kb/2732673 [http://support.microsoft.com/kb/2732673]\nMicrosoft Windows Server 2008 R2 SP1 hotfix KB 2728738 - http://support.microsoft.com/kb/2728738 [http://support.microsoft.com/kb/2728738]\nMicrosoft Windows Server 2008 R2 SP1 hotfix KB 2831013 - http://support.microsoft.com/kb/2831013 [http://support.microsoft.com/kb/2831013]\nMicrosoft Windows Server 2008 R2 hotfix KB 2831154 - http://support.microsoft.com/kb/2831154 [http://support.microsoft.com/kb/2831154]\n\nAlong with the one-KB2732673 in question, the other listed hot-fixes are also required for file system connector.\n\nDIRECT LINKS TO FIXES\n4.0.1.6-IBM-ICC-FP006 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FInformation+Management%2FContent+Collector&fixids=4.0.1.6-IBM-ICC-FP006&source=SAR]\nIBM Content Collector V4.0.1 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24043989]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q253", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "IBM_Content_Collector_Outlook_Extension V4.0.1.5 failed in\n silent installation while using Windows 10 Build 1703\n\nGetting following error -\n Please check your registration: Schluessel: HKEY_LOCAL_MACHINE\n \\ SOFTWARE \\ Microsoft \\ .NET Framework Setup \\ NDP \\ v4 \\ Full\n Value Name: Version\n Status: Successful\n .Net Framework 4.5.1 is not installed.\n Status: Error\n Additional notes: Error - Going to abort installation", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Contact IBM Support for local fix", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q253", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "IBM_Content_Collector_Outlook_Extension V4.0.1.5 failed in\n silent installation while using Windows 10 Build 1703\n\nGetting following error -\n Please check your registration: Schluessel: HKEY_LOCAL_MACHINE\n \\ SOFTWARE \\ Microsoft \\ .NET Framework Setup \\ NDP \\ v4 \\ Full\n Value Name: Version\n Status: Successful\n .Net Framework 4.5.1 is not installed.\n Status: Error\n Additional notes: Error - Going to abort installation\n\nAs per ICC prerequisites .NET Framework 4.5 or later is\n supported. With latest Windows 10 build, .NET Framework 4.7 is\n shipped.\n Outlook Extension silent/console installation is currently\n unable to detect the .NET framework version 4.7.", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q253", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The same issue with GUI installation has been already handled in\n APAR HE12666 [http://www-01.ibm.com/support/docview.wss?uid=swg1HE12666] (fixed with IBM Content Collector 4.0.1 FP5\n release).\n Starting with IBM Content Collector 4.0.1 FP6 release, the\n Outlook Extension silent and console installation has been also\n fixed and it will detect the .Net Framework 4.7 pre-requisite.\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q253", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n HE12698\nREPORTED COMPONENT NAME\n ICC FOR EMAIL\nREPORTED COMPONENT ID\n 5724V5700\nREPORTED RELEASE\n 401\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2017-07-18\nCLOSED DATE\n 2017-08-29\nLAST MODIFIED DATE\n 2017-08-29\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q253", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n ICC FOR EMAIL\nFIXED COMPONENT ID\n 5724V5700", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q253", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R401 PSY\n UP\n\nPRODUCT DOCUMENTATION", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q253", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "The PDF attached to this techdoc contains the documentation for the Watson Explorer Community Edition, including installation instructions. The content of this techdoc also serves as the release notes for Watson Explorer Community Edition.", "logical_doc_id": 5, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "wex_ce.pdf [/support/docview.wss?uid=swg27050410&aid=2]wex_ce.pdf [/support/docview.wss?uid=swg27050410&aid=1]\n\nIBM Watson Explorer Community Edition [https://www.ibm.com/us-en/marketplace/content-analytics] application can be downloaded from https://www.ibm.com/us-en/marketplace/content-analytics [https://www.ibm.com/us-en/marketplace/content-analytics]. Before you install the IBM Watson Explorer Community Edition [https://www.ibm.com/us-en/marketplace/content-analytics] application, get familiar with the most important information related to the installation process.\n\nFeedback / Suggestions / Questions\n\nYou are welcome to provide any feedback in the community.\n\nPlease post to the dWAnswers Community with the watson-explorer tag at the following URLs:\nhttps://developer.ibm.com/answers/topics/watson-explorer/ [https://developer.ibm.com/answers/topics/watson-explorer/]\n\nSupported platforms\nWindows * Windows 10 Education\nWindows 10 Enterprise\nWindows 10 Pro\nMacOS * Mac OS X 10.10.3 or later\n\nSupported browsers\nGoogle Chrome Version 60 or later\nMozilla FireFox Version 52 (ESR) or later\nMicrosoft Edge on Windows\nMicrosoft Internet Explorer 11 on Windows\n\nNote: 'Supported platforms/browsers' here means those are confirmed to work with Watson Explorer Community Edition [https://www.ibm.com/us-en/marketplace/content-analytics]. Watson Explorer Community Edition [https://www.ibm.com/us-en/marketplace/content-analytics] is provided under Evaluation/Trial license, thus no support will be provided via Passport Advantage/IBM Support channel.", "logical_doc_id": 5, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Known Issues and Limitations\nInstalling the application\nIf you use an older toolbox-based version of Docker, uninstall it before you install the application. If you have other containers that run on your computer, stop them before you start the installation process of the application because your computer might have resource constraints. The application pulls a Docker Image during the installation process. The installation takes about 10-15 minutes on a standard network speed of about 15-20 Mbps. A typical corporate VPN is likely to limit the download speed. Consider it while you wait for the installation to finish. If you already have the application installed and want to upgrade to a new version, from the 'More info' menu in the upper-right corner on the Result page select Uninstall. This will remove the older version of Docker Image and container. Finally relaunch the application to pull most recent Image. *\nLaunching the application\nIf you are a Mac user, the following security warning is displayed when you launch the application: \"IBM Watson Explorer Community Edition [https://www.ibm.com/us-en/marketplace/content-analytics] can't be opened because it is from an unidentified developer\" In this case, from the Apply menu, choose System Preferences, click Security & Privacy, then click General. In the General pane, click Open Anyway button. For details, see https://support.apple.com/kb/PH25088?locale=en_US [https://support.apple.com/kb/PH25088?locale=en_US]. *\nOther Known Issues / Limitations\nMultiple dictionary annotators do not work with a single collection. If you want to apply multiple dictionaries, create a dictionary annotator that includes multiple dictionaries. When creating a new model for a classifier and cancelling the creation during Creating datasets status in either Content Miner or Admin Console, the status may not be changed although the process has been actually cancelled in the system. Facet highlighting is partially supported. The text will be highlighted when the exact same facet value string is specified as the facet refinement query. For example, query 'facet:\"positive expression\"' does not highlight 'good product' in the document text. Facet counting for numeric or date facets in the custom analysis view is not supported in Content Miner. On Windows 10 OS while the application is downloading the docker image. If there is internet disconnection. The Application has to be restarted.", "logical_doc_id": 5, "chunk_id": 32 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "If a native field name in a crawler data source is id or ID, the dataset field name is changed to id_ or ID_. *\nBrowser specific issues - please use Chrome or any other tested browsers\nSafari on Mac is not a supported browser. Pop-up error with \"ReferenceError: 'URLSearchParms' is undefined\" appears on Microsoft Internet Explorer 11 and Microsoft Edge when trying to create a new classifier in Admin Console. Some UI elements are not correctly rendered in Admin Console with Microsoft Internet Explorer 11.", "logical_doc_id": 5, "chunk_id": 33 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "FAQ * On Windows installation, the window to input the username/password for mounting the volume may not appear in front.\nYou may need to search if the screen is found behind the installer. (Installation itself will be succeeded once you input the user name/password, but may be confusing.)\nWhile installation, if there is an interruption in internet connection. The Application waits till the connection is back, and continues after. But there are cases when the percentage may go beyond 100% because of the interruption. In this case, close the application, restart the Docker Daemon and relaunch the application.\nIf the Application redirects to error page right after installation, after multiple tries. In this case check run the command docker ps -a on the terminal and check to see if the status of the container is in 'Created' state. If it is in Created state then run docker rm -f wex-d-g to remove the container. Finally relaunch the Application.\nFor users who would like to look at the mounts on the terminal. Run the command docker exec -it wex-d-g ls /mnt.\nFor users using windows machine with AsureAD. When trying to mount a folder, the docker prompts for user credentials. Even after the user enters the password, as the password stored for the AzureAD account is not local, it will not succeed. This is an issue from Docker and Windows with Azure AD. For details, see \"Installing Watson Explorer Community Edition on a computer with Azure Active Directory [http://www.ibm.com/support/docview.wss?uid=swg22010048]\" .\n\nORIGINAL PUBLICATION DATE\n 2017/10/27", "logical_doc_id": 5, "chunk_id": 34 }, { "doc_id": "techqa_DEV_Q253", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Why are IBM BigFix security patches not yet available even though Microsoft has already announced them?", "logical_doc_id": 6, "chunk_id": 35 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Each month Microsoft releases security bulletins, including operating system and product application patches. Various other hardware and software vendors release patches periodically. However, patches can be released any time. The Microsoft monthly patch release is known as Patch Tuesday because it typically occurs every second Tuesday of the month.\n\nWithin 24 hours of Microsoft's release, the BigFix team typically creates and releases English-language Fixlets to match specific Microsoft patch bulletins. Each Fixlet targets the specific components that are listed by the Microsoft patch. While patches are released by Microsoft, they are typically not available in the BigFix console until about 24 hours after Microsoft has released them.\n\nTherefore you may not be seeing them in your BigFix console because 24 hours have not passed yet.\n\nCustomers can check Microsoft's site to see if the patch has been released at:\nhttp://www.catalog.update.microsoft.com/Home.aspx [http://www.catalog.update.microsoft.com/Home.aspx]\nThis url is the most comprehensive list of Microsoft patches and is available online.\nNote that customers might not see a patch because it has been \"superseded\" or \"replaced\" by a\nlater patch. What you can do is put in the KB into the box and then do a search for the KB in the page. Click on the patch you want to see information about -> then click on the Package Details tab.\nThe tab will state if the patch has been replaced by a later patch (a later KB).\nScroll down to the bottom to see the latest KB.\n\nNote that there are some patches IBM does not support. While IBM does support security updates for Microsoft Windows it does not cover older versions of Windows or of Windows software. See our most recent documentation regarding this which will explain which type of patch we do support:http://www.ibm.com/support/knowledgecenter/SS6MER_9.5.0/com.ibm.bigfix.patch.doc/Patch/Patch_Windows/c_system_requirements.html?view=embed [http://www.ibm.com/support/knowledgecenter/SS6MER_9.5.0/com.ibm.bigfix.patch.doc/Patch/Patch_Windows/c_system_requirements.html?view=embed]\n\nYou can also view this information at:\nhttps://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/Supported%20OS [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/Supported%20OS]", "logical_doc_id": 6, "chunk_id": 36 }, { "doc_id": "techqa_DEV_Q253", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "It is also possible that the user's Patches for Windows site is simply out of date. What customers can do is go to this link:\nhttp://sync.bigfix.com/cgi-bin/bfgather/bessecurity [http://sync.bigfix.com/cgi-bin/bfgather/bessecurity]\nThis is the link for our Patches for Windows site.\nDo a search for the term MODIFIED and look at each of the modified dates. You will then be able to tell how your old site is. As we release content monthly for the Patches for Windows site, on the second Tuesday of the month, your site should not be more than a couple of weeks old. If it is, then you may have some blockage preventing your main BigFix server to go out to the internet, preventing it from getting the latest content (fixlets) for the patch you are looking at.\nOn this point, you can sign up for the BigFix newsletter to tell you when we release a new site.\nSign up details at:\nhttp://bigmail.bigfix.com/mailman/listinfo/ [http://bigmail.bigfix.com/mailman/listinfo/]\n\nIf customers do find a patch that is not covered by our Patches for Windows solution customers can develop their own BigFix content. Technical support cannot create content for customers nor advise on custom content creation however customers can engage IBM Professional Services who can create custom content for customers for a fee. Contact your IBM sales representative if you are interested in this option.", "logical_doc_id": 6, "chunk_id": 37 }, { "doc_id": "techqa_DEV_Q253", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "Understanding BigFix Patches for Windows Solution [http://www.ibm.com/support/docview.wss?uid=swg21505562]", "logical_doc_id": 6, "chunk_id": 38 }, { "doc_id": "techqa_DEV_Q231", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Vulnerability in Apache Commons FileUpload affects IBM WebSphere Service Registry and Repository (CVE-2016-1000031)", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q231", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-1000031 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031]\nDESCRIPTION: Apache Commons FileUpload, as used in certain products, could allow a remote attacker to execute arbitrary code on the system, caused by deserialization of untrusted data in DiskFileItem class of the FileUpload library. A remote attacker could exploit this vulnerability to execute arbitrary code under the context of the current process.\nCVSS Base Score: 9.8\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117957 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117957] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q231", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "WebSphere Service Registry and Repository V8.5\nWebSphere Service Registry and Repository V8.0\n\nFor unsupported versions IBM recommends upgrading to a fixed, supported version of the product", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q231", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "To remediate CVE-2016-1000031 you need to apply fixes for both IBM WebSphere Application Server and IBM WebSphere Service Registry and Repository.\n\nFor WebSphere Application Server updates refer to this bulletin:\nSecurity Bulletin: Security vulnerability in Apache Commons FileUpload used by WebSphere Application Server (CVE-2016-1000031) [http://www.ibm.com/support/docview.wss?uid=swg22011428]\n\nFor WebSphere Service Registry and Repository, this vulnerability has been fixed under APAR IJ01131. Fixes containing IJ01131 have been published and are available from Fix Central.\n\nFor WSRR V8.5\nApply V8.5.6.1_IJ01131 [https://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FWebSphere+Service+Registry+and+Repository&fixids=8.5.6.1-WS-WSRR-MultiOS-IFIJ01131]\n\nFor WSRR V8.0 * Apply [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+Service+Registry+and+Repository&function=fixId&fixids=8.0.0.3-WS-WSRR-MultiOS-IFIV65487_IV79085]V8.0.0.3_IV65487_IV79085_IV87422_IV87429_IV89477_IJ01131 [https://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FWebSphere+Service+Registry+and+Repository&fixids=8.0.0.3-WS-WSRR-MultiOS-IFIV65487_IV79085_IV87422_IV87429_IV89477_IJ01131]", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q231", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q231", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q231", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 04 January 2018: Original version published\nThe 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\nsecurity SECURITY BULLETIN", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q231", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Apache Commons FileUpload used by IBM Maximo Asset Management could allow a remote attacker to execute arbitrary code on the system, caused by deserialization of untrusted data in DiskFileItem class of the FileUpload library. A remote attacker could exploit this vulnerability to execute arbitrary code under the context of the current process.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q231", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-1000031 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031]\nDESCRIPTION: Apache Commons FileUpload, as used in Novell NetIQ Sentinel and other products, could allow a remote attacker to execute arbitrary code on the system, caused by deserialization of untrusted data in DiskFileItem class of the FileUpload library. A remote attacker could exploit this vulnerability to execute arbitrary code under the context of the current process.\nCVSS Base Score: 9.8\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117957 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117957] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q231", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "The following Apache Commons FileUpload version is affected:\nApache Commons FileUpload 1.3.2\n\nIBM supplied Apache Commons FileUpload with the following:\n\nThe 7.5.0.x and 7.6.0.x versions of Maximo Asset Management bundled Apache Commons FileUpload 1.3.2\n\nThis vulnerability affects the following versions of the IBM Maximo Asset Management core product, and all other IBM Maximo Industry Solution and IBM Control Desk products, regardless of their own version, if they are currently installed on top of an affected IBM Maximo Asset Management. *\n\nMaximo Asset Management core product affected versions:\nMaximo Asset Management 7.6, 7.5\nMaximo Asset Management Essentials 7.5\n\nIndustry Solutions products affected if using an affected core version:\nMaximo for Aviation\nMaximo for Government\nMaximo for Life Sciences\nMaximo for Nuclear Power\nMaximo for Oil and Gas\nMaximo for Transportation\nMaximo for Utilities\n\nIBM Control Desk products affected if using an affected core version:\nSmartCloud Control Desk\nIBM Control Desk\nTivoli Integration Composer\nTo determine the core product version, log in and view System Information. The core product version is the \"Tivoli's process automation engine\" version. Please consult the Product Coexistence Matrix [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Maximo%20Asset%20Management/page/Product%20compatibility] for a list of supported product combinations. REMEDIATION/FIXES\nThe recommended solution is to download the appropriate Interim Fix or Fix Pack from Fix Central (What is Fix Central? [http://www.ibm.com/systems/support/fixes/en/fixcentral/help/faq_sw.html]) and apply for each affected product as soon as possible. Please see below for information on the fixes available for each product, version, and release. Follow the installation instructions in the \u2018readme\u2019 documentation provided with each fix pack or interim fix.\n\nFor Maximo Asset Management 7.6, 7.5:\n\nVRM Fix Pack, Feature Pack, or Interim Fix Download 7.6.0 Maximo 7.6.0.9 Interim Fix:\n7.6.0.9-TIV-MBS-IFIX004 or latest Interim Fix available FixCentral [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/IBM+Maximo+Asset+Management&release=7.6.0.9&platform=All&function=all] 7.5.0 Maximo 7.5.0.11 Interim Fix:\n7.5.0.11-TIV-MBS-IFIX013 FixCentral [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/IBM+Maximo+Asset+Management&release=7.5.0.11&platform=All&function=all] WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q231", "section_id": 3, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q231", "section_id": 4, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q231", "section_id": 5, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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 April 2018: Original version published\nThe 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\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Control Desk 7.5, 7.5.1, 7.5.1.1, 7.5.1.2, 7.5.3, 7.6.0, 7.6.0.1 Systems and Asset Management Maximo for Life Sciences 7.5, 7.6 Systems and Asset Management Maximo for Nuclear Power 7.5, 7.5.1, 7.6.0 Systems and Asset Management Maximo for Oil and Gas 7.5, 7.5.1, 7.6.0 Systems and Asset Management Maximo for Transportation 7.5, 7.5.1, 7.6.1, 7.6.2, 7.6.2.1, 7.6.2.2, 7.6.2.3, 7.6.2.4 Systems and Asset Management Maximo for Utilities 7.5, 7.6 Systems and Asset Management Tivoli Integration Composer 7.5 Systems and Asset Management IBM Maximo for Aviation 7.6, 7.6.1, 7.6.2, 7.6.2.1, 7.6.3 Systems and Asset Management Maximo for Government 7.5 Systems and Asset Management Maximo Asset Management Essentials 7.5\n\nPSIRT SECURITY BULLETIN", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q231", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM Security Identity Manager (ISIM) has addressed the following vulnerability. Apache Commons FileUpload could allow a remote attacker to execute arbitrary code on the system.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q231", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID:CVE-2016-1000031 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031]\nDESCRIPTION: Apache Commons FileUpload, as used in Novell NetIQ Sentinel and other products, could allow a remote attacker to execute arbitrary code on the system, caused by deserialization of untrusted data in DiskFileItem class of the FileUpload library. A remote attacker could exploit this vulnerability to execute arbitrary code under the context of the current process.\nCVSS Base Score: 9.8\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/117957 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117957]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q231", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Product Version ISIM 6.0 REMEDIATION/FIXES\n\nProduct VRMF Remediation ISIM 6.0 6.0.0-ISS-SIM-FP0020 [https://www-945.ibm.com/support/fixcentral/swg/doSelectFixes?options.selectedFixes=6.0.0-ISS-SIM-FP0020&continue=1] GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n\nSubscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.\n\nREFERENCE\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q231", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nThe 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.", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q231", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Fix is available for vulnerability in Apache Commons FileUpload affecting Tivoli Netcool/OMNIbus WebGUI (CVE-2016-1000031).", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q231", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID:CVE-2016-1000031 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031]\nDESCRIPTION:Apache Commons FileUpload, as used in Novell NetIQ Sentinel and other products, could allow a remote attacker to execute arbitrary code on the system, caused by deserialization of untrusted data in DiskFileItem class of the FileUpload library. A remote attacker could exploit this vulnerability to execute arbitrary code under the context of the current process.\nCVSS Base Score: 9.8\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/117957 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117957]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q231", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Tivoli Netcool/OMNIbus WebGUI 8.1.0\nTivoli Netcool/OMNIbus WebGUI 7.4.0", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q231", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Product VRMF APAR Remediation/Fix Tivoli Netcool/OMNIbus WebGUI 8.1.0 IJ04482 Apply Fix Pack 13\n(Fix Pack for WebGUI 8.1.0 Fix Pack 13 [http://www.ibm.com/support/docview.wss?uid=swg24044415]) Tivoli Netcool/OMNIbus WebGUI 7.4.0 IJ04482 Upgrade to WebGUI 8.1.0 and then apply Fix Pack 13\n(Fix Pack for WebGUI 8.1.0 Fix Pack 13 [http://www.ibm.com/support/docview.wss?uid=swg24044415])\nPlease also note the end of support announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS917-138/index.html&lang=en&request_locale=en] from 12 September 2017 for selected Netcool product versions. You can find detailed information on whether the product version you have installed in your environment is affected by this end of service announcement by following the Netcool End of Support Knowledge Collection [https://www-01.ibm.com/support/entdocview.wss?uid=swg22009231] . If your product version is affected, IBM recommend to upgrade your product version to the latest supported version of your product. Please contact your IBM account manager for any question you might have or for any assistance you may require for upgrading an end of service announced offering. GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q231", "section_id": 4, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q231", "section_id": 5, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 18 May 2018: Original version published\nThe 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\nDOWNLOADABLE FILES", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q231", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This interim Fix address Open Source Commons FileUpload Apache Vulnerabilities: CVE-2016-1000031 in Tivoli Business Service Manager V6.1", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q231", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Date:\n----\nMarch 23, 2018\n\nCopyright Notice:\n\n\u00a9 Copyright IBM Corp. 2018 All Rights Reserved.\n\nUS Government Users Restricted Rights - Use, duplication or\ndisclosure restricted by GSA ADP Schedule Contract with\nIBM Corp.\n\nIBM\u00ae Tivoli\u00ae Business Service Manager V6.1.0 Interim Fix Version 6.1.0.4-TIV-BSM-IF0007\n\nContents:\n\nFiles that are included in this Interim Fix:\nThis README file - 6.1.0.4-TIV-BSM-IF0007.README\nInterim Fix content - 6.1.0.4-TIV-BSM-IF0007.zip\n\nAbout this Interim Fix:\n\nThis Interim Fix addresses problems reported in IBM Tivoli Business Service Manager V6.1.0\n\nThis IF contains fixes that are only applicable when using IBM Tivoli Business Service Manager 6.1.0 Fix Pack\n\n04.\nFixes that are included in Interim Fix", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q231", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "07.\nOpen Source Commons FileUpload Apache Vulnerabilities: CVE-2016-1000031\n\nPREREQUISITES\nIBM Tivoli Business Service Manager V6.1.0 Fix Pack 4(6.1.0-TIV-BSM-FP0004)\n\nURL LANGUAGE SIZE(Bytes) 6.1.0-TIV-BSM-FP0004-aix.tar [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.0-TIV-BSM-FP0004-aix&source=SAR] English 1342259200 6.1.0-TIV-BSM-FP0004-linux.tar [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.0-TIV-BSM-FP0004-linux&source=SAR] English 1240391680 6.1.0-TIV-BSM-FP0004-solaris.tar [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.0-TIV-BSM-FP0004-solaris&source=SAR] English 1278269440 6.1.0-TIV-BSM-FP0004-windows.zip [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.0-TIV-BSM-FP0004-windows&source=SAR] English 1271825734 6.1.0-TIV-BSM-FP0004-zlinux.tar [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.0-TIV-BSM-FP0004-zlinux&source=SAR] English 1229219840\nINSTALLATION INSTRUCTIONS\n\nInstallation, migration, upgrade and configuration information:\n\nHardware and software requirements:\n\nRefer to the Tivoli Business Service Manager 6.1.0 Release Notes for a full\ndescription of all the hardware and software requirements.\nDependencies:\n\nThis Interim Fix must be installed on each server(s) that is\nrunning the Tivoli Business Service Manager server.\n\nThis Interim Fix requires Tivoli Business Service Manager 6.1.0 FP0004\nto be already installed.\nSpecial considerations:\n\n1) The Tivoli Business Service Manager server(s) need to be stopped, prior to\ninstalling this Interim Fix.\nExtracting this Interim Fix:\nWindows and Non-Windows\n\n1. Copy the file 6.1.0.4-TIV-BSM-IF0007.zip to a\ntemporary location on your Tivoli Business Service Manager server.", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q231", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "2. Unzip the file on each server that you need to install on.\nInstalling this Interim Fix:\n\n[Interim Fix] Refers to the directory where this Interim Fix\nresides (after you have extracted it from the zip file).\n\nfor example: /tmp/6.1.0.4-TIV-BSM-IF0007\n\nOn the Tivoli Business Service Manager server system:\n\nNavigate to the [Interim Fix] directory where the files\nwere extracted.\n\nInstall the Interim Fix with the same user that was used to\ninstall Tivoli Business Service Manager 6.1.0 Base release.\n\nAll Tivoli Business Service Manager servers\n\n1.) Stop the Tivoli Business Service Manager server(s)\n2.) Open a command prompt and change to the unzip directory\n3.) Set the NC_HOME environment variable to locate the Tivoli Business Service Manager\n6.1.0 installation:\nfor example: /opt/IBM/tivoli\n\n4.) Backup and move all commons-fileupload*.jar under following directory to other place\n$NC_HOME/tbsm/lib3p\n$NC_HOME/impact/guiserver/stageAdmin/WEB-INF/lib\n$NC_HOME/tipv2/profiles/TBSMProfile/installedApps/TBSMCell/TBSM.ear\n$NC_HOME/tipv2/profiles/TIPProfile/installedApps/TIPCell/isc.ear/impactAdmin.war/WEB-INF/lib\n$NC_HOME/tipv2/profiles/TIPProfile/installedApps/TIPCell/isc.ear/sla.war/WEB-INF/lib\n$NC_HOME/tipv2/systemApps/isclite.ear\n$NC_HOME/tipv2/profiles/TIPProfile/installedApps/TIPCell/isc.ear\n$NC_HOME/tipv2/profiles/TIPProfile/installedApps/TIPCell/authnsvc_ctges.ear\n\n5.) Copy extracted commons-fileupload-1.3.3.jar and commons-io-2.4.jar file to same place as Step 4.)\n\n6.) Start the Tivoli Business Service Manager server(s)\n\nDOWNLOAD PACKAGE\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options 6.1.0.4-TIV-BSM-IF0007-Aix 23 Mar 2018 English 231029 HTTP [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.0.4-TIV-BSM-IF0007&source=SAR] 6.1.0.4-TIV-BSM-IF0007-Linux 23 Mar 2018 English 231029 HTTP [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.0.4-TIV-BSM-IF0007&source=SAR] 6.1.0.4-TIV-BSM-IF0007-Windows 23 Mar 2018 English 231029 HTTP [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.0.4-TIV-BSM-IF0007&source=SAR] 6.1.0.4-TIV-BSM-IF0007-Solaris 23 Mar 2018 English 231029 HTTP [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.0.4-TIV-BSM-IF0007&source=SAR] 6.1.0.4-TIV-BSM-IF0007-zLinux 23 Mar 2018 English 231029 HTTP [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.0.4-TIV-BSM-IF0007]", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q196", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Having a 64-bit install of Modeler and a 32-bit installation of Statistics is not a supported configuration by IBM SPSS. In order to use the SPSS Statistics nodes from within Modeler, you will need to install the 64-bit version of Statistics.\n\nThis is because the 32-bit API's of SPSS Statistics cannot be loaded by the 64-bit installation of SPSS Modeler.\n\nThis limitation is expected to be documented in future releases of IBM SPSS Modeler.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q196", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Modeler forum is Live! [https://developer.ibm.com/answers/topics/modeler/?smartspace=predictive-analytics]\n\nHISTORICAL NUMBER\n 93142", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q196", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "After extracting the MSI from the product installer (.EXE file) there is no SMS file found as was indicated by the product documentation. This file is needed for some types of silent/push installation methods.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q196", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "The contents of the SMS file are between the asterix lines below:\n\n[PDF]\nVersion = 2.0\n\n[Package Definition]\nName = IBM SPSS Statistics 21\nVersion = 21.0.0.0\nPublisher = IBM Corp.\nLanguage = English, French, German, Spanish, Italian, Polish, Korean, Japanese, Russian, Chinese (Simplified), Chinese (Traditional), Portuguese (Brazil)\nPrograms = Setup\nMifFileName = IBM SPSS Statistics 21.mif\nMifName = IBM SPSS Statistics 21\nMifVersion = 21.0.0.0\nMifPublisher = IBM Corp.\n\n[Setup]\nName = Automated Minimum Installation\nCommandLine English (United States) = msiexec /qn /I \"IBM SPSS Statistics 21.msi\" TRANSFORMS=1033.mst\nCommandLine French (France) = msiexec /qn /I \"IBM SPSS Statistics 21.msi\" TRANSFORMS=1036.mst\nCommandLine German (Germany) = msiexec /qn /I \"IBM SPSS Statistics 21.msi\" TRANSFORMS=1031.mst\nCommandLine Spanish (Traditional-Spain) = msiexec /qn /I \"IBM SPSS Statistics 21.msi\" TRANSFORMS=1034.mst\nCommandLine Italian (Italy) = msiexec /qn /I \"IBM SPSS Statistics 21.msi\" TRANSFORMS=1040.mst\nCommandLine Japanese (Japan) = msiexec /qn /I \"IBM SPSS Statistics 21.msi\" TRANSFORMS=1041.mst\nCommandLine Polish (Poland) = msiexec /qn /I \"IBM SPSS Statistics 21.msi\" TRANSFORMS=1045.mst\nCommandLine Russian (Russia) = msiexec /qn /I \"IBM SPSS Statistics 21.msi\" TRANSFORMS=1049.mst\nCommandLine Korean (Korea) = msiexec /qn /I \"IBM SPSS Statistics 21.msi\" TRANSFORMS=1042.mst\nCommandLine Chinese (Simplified) = msiexec /qn /I \"IBM SPSS Statistics 21.msi\" TRANSFORMS=2052.mst\nCommandLine Chinese (Traditional) = msiexec /qn /I \"IBM SPSS Statistics 21.msi\" TRANSFORMS=1028.mst\nCommandLine Portuguese (Brazil) = msiexec /qn /I \"IBM SPSS Statistics 21.msi\" TRANSFORMS=1046.mst\nSupportedClients = Win 9x, Win NT (i386)\nUserInputRequired = False\nRemoveProgram = True\nUnInstallKey = {1E26B9C2-ED08-4EEA-83C8-A786502B41E5}\n****\n\nSimply copy the above lines into a normal text file with the SMS extension and use it normally.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q196", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q196", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What causes an 1152 error during extraction of Modeler self extracting executable?", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q196", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "When an IBM SPSS compressed image is launched, files compressed within it are extracted to the temporary location assigned to the signed in user i.e. /Documents and settings/... or /users.\nThe possibility of these files downloaded improperly exists. You can use a tool such\nas MD5 to verify the file content or simply attempt downloading a second time and test.\n\nOther possible causes of this error:\nAvailable space within the temporary location noted by the installer.\nAbility to write in the temporary location noted by the installer.", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q196", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Transfer the files again, resolved the issue.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q196", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Modeler forum is Live! [https://developer.ibm.com/answers/topics/modeler/?smartspace=predictive-analytics]", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q196", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Where is the Microsoft Installer (*.msi) file required for unattended/silent/push installations the IBM SPSS Statistics application?", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q196", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "The Microsoft Installer (*.msi) file for IBM SPSS Statistics applications is not available as a separate download. Accessing the.msi file for IBM SPSS Statistics is dependent upon the installation media you have received.\nUsing the Software Download:\n1. Download and save the installer executable (e.g. 'SPSS_Statistics_24_win64.exe') to a known, accessible location on the computer hard drive.\n2. Next, you will need to use the /b switch from your command prompt to extract the .msi file.\nIn the example below the SPSS_Statistics_24_win64.exe was downloaded to the C: drive.\nProvide the file location for the extraction. This example uses the directory \"MSItest\" on the C: drive:\n\nC:\\>SPSS_Statistics_24_win64.exe /b\"C:\\MSItest\"\n\n3. Notice that running this command will launch the InstallShield Wizard. Let this run until the .msi has been extracted. You will see \"Extracting: IBM SPSS Statistics 24.msi\" message from the installer. You do not need to proceed with the full installation.\n\nUsing Installation Media (CD/DVD)\n1. Insert the disk.\n2. IF prompted to install the software, select 'Cancel'.\n3. Browse to the media location.\n4. Open the 'SPSSStatistics' folder.\n\nThe 32-bit MSI file will be located in the 'win32'. folder.\nThe 64-bit MSI file will be located in the 'win64' folder.\n\nUsing a compressed (.zip) file\n1. Extract (decompress) the contents of the ZIP file into a designated folder.\n2. The MSI folder will located in the designated folder.\n\nFor documentation on IBM SPSS-specific commands for use with MSI files, see 'Administrator's Guide' appropriate to your license type (e.g. 'Site', 'Concurrent' Users Guide').", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q196", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Statistics", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q196", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How can I push out an install or patch for the IBM SPSS Modeler Client application?", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q196", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "A Modeler install or patch can be pushed out to the clients with the following steps.\n\nStep 1: Harvest the .msi and accompanying files required for silent install. To do this:\nGo to: Start > Run and type '%temp%' to navigate to the temporary path for Windows Installer programs. Delete all contents within this folder.\nRun the installer executable (SPSS_Modeler_141_win64.exe) as normal. When it finishes extracting and decompressing the .msi file and the end-user is required to click 'Continue', minimise this window.\nSwitch to the %temp% folder and locate the folder with the 'ModelerClient64.msi' file. Copy ALL contents within this folder and paste it to a local folder (e.g. C:\\Temp\\Modeler\\ClientInstall).\nOnce copied, switch back to the installation wizard and hit 'Cancel'.\n\nStep 2: Use the command prompt to execute the 'MsiExec' command:\nOpen a command prompt window as an Administrator and run the following command: (substitute with the location of your .msi file)\n\nMsiExec.exe /i \"\\ModelerClient.msi\" /qn /L*v logfile.txt INSTALLDIR=\"C:\\Program Files\\IBM\\SPSS\\Modeler\\14\" LICENSETYPE=\"Network\" LSHOST=\"mylicserver\"\nFor a full list of Silent Install options, please refer to the 'NetworkLicenseAdministratorsGuide.pdf' > 'Installaing the Product on the Local Desktop Computers > Pushing an Installation to Windows Computers.\n\nOnce that you have confirmed that Modeler Client is operational, repeat the steps to extract the .msi file for Modeler Client Fix Pack\n\n1. Please note that it is highly recommended to delete the contents of the temporary folder as the Fix Pack and Client installations use the same file names. This is to prevent the accidental copying of the Client installation instead of the Fix Pack install.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q196", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Modeler forum is Live! [https://developer.ibm.com/answers/topics/modeler/?smartspace=predictive-analytics]", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q062", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "The WebSphere Message Broker V6.0 Client for WebSphere Service Registry and Repository provides a means of querying the service registry.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q062", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "PLEASE NOTE:\nThis SupportPac has been superseded by IA9Q. Please use the link in the download table to access the webpage and code.\n\nThe WebSphere Service Registry and Repository (WSRR) is the repository of record for the services meta-data for the ESB. This SupportPac provides WMB standard interfaces (nodes) for accessing WSRR, provides three levels of caching, and WSRR synchronized cache update.\n\nThe IA9L SupportPac (WMB Client for WSRR) has been largely superseded by a product extension SupportPac, IA9Q. The IA9Q is a Category 3 SupportPac and will be merged into the product base in the WMB 6.1 timeframe. The IA9Q SupportPac is the recommended WMB Client for WSRR, to access it click on the link below in the downloads table.\n\nThe IA9L SupportPac will be updated in the near future, as most of its functionality became IA9Q. Once updated IA9L will contain only the pattern of use nodes, SRxxxxVirtualService nodes.\n\nPOSSIBLE USES\nImplementation of a services registry, as part of a Service Oriented Architecture, where WebSphere Message Broker has been selected as the Enterprise Services Bus.\n\nSKILL LEVEL REQUIRED\nNormal WebSphere Message Broker development skills.\n\nDELIVERY\nThis SupportPac has been superseded by IA9Q. Please use the link in the download table to access the web page and code.\n\nNEW IN THIS RELEASE\n1. Documentation updates relating to installation.\n2. Update to scripts and readme files making it easier to install sample data.\n\nDETAILS\nAuthors: IBM China Software Development Laboratory, IBM Enterprise Integration Solutions\nCategory: 1\nReleased: 29Sep06\nLast updated: 31Oct06\nCurrent Version: 1.0.1\n\u00bbPlease note that the version number shown in the right-hand pane is the version of the MQ or WBI product that this SupportPac applies to. The date is the last web page refresh.\n\nTo view the complete portfolio of WebSphere MQ SupportPacs please visit the WebSphere MQ SupportPacs homepage:\nhttp://www-306.ibm.com/software/integration/support/supportpacs [http://www-306.ibm.com/software/integration/support/supportpacs]\n\nPREREQUISITES\nWebSphere Service Registry and Repository Version 1.0\nWebSphere Message Broker Version 6.0 Fix Pack 2 or later.\n\nINSTALLATION INSTRUCTIONS\nNot applicable.\n\nDOWNLOAD PACKAGE\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options About Category 1 SupportPacs 31/10/2006 US English 111 HTTP [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27007195&loc=en_US&cs=utf-8&lang=en] SupportPac IA9Q 19/01/2007 US English 1540803 HTTP [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg24014652&loc=en_US&cs=utf-8&lang=en]\nTECHNICAL SUPPORT\n This SupportPac is supplied under the standard terms and conditions provided by the International Program License Agreement (IPLA) and thus, carry program defect service.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q062", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "If you encounter what you believe to be a defect with the SupportPac you may request Program Services, by reporting the problem via the same defect reporting channel you use for the WebSphere MQ or WebSphere Business Integration product/s with which you are using the SupportPac. These products must themselves have service support.\n\nPlease read the license file that accompanies it, to determine if you want to use it. No proof of Entitlement or License Information is required to use this SupportPac.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q062", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "No errors are thrown, nor can any be seen in a service level trace of the execution group. A service trace will show that the node has started:\n\nBIP3904I: Invoking the evaluate() method of node (class='SRRetrieveEntityNode', name='').\n\nBIP3685I: The following details will be used to query WebSphere Service Registry and Repository (WSRR) from node 'RegistryLookup':", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q062", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "On Solaris and HP platforms, WMB uses the vendor base JDK rather than an IBM supplied JDK.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q062", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "You need to alter the JVM to use a different, poll-based selector provider. This can be done via the mqsichangeproperties command:\n\nmqsichangeproperties -e -o ComIbmJVMManager -n jvmSystemProperty -v \"-Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider\"\n\nA broker restart is required to pick up these changes. This should allow WMB to properly connect to WSRR.\n\nHISTORICAL NUMBER\n 47153 442 000\n\nPRODUCT ALIAS/SYNONYM\n WMB MB Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI WSRR\n\n SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q062", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "6.1.0.12 for WebSphere Message Broker V6.1 on Multiplatforms\n provides fixes for the problems described in this APAR.", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q062", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n All users of WebSphere Message Broker Version 6.1.\n\nPlatforms affected:\n MultiPlatform\n\nPROBLEM SUMMARY:\n 6.1.0.12 for WebSphere Message Broker V6.1 on Multiplatforms.\n This APAR does not represent any actual code change, instead\n is used to represent the whole fix pack.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q062", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "6.1.0.12 for WebSphere Message Broker V6.1 on Multiplatforms\n is now available.\n For details refer to 'WebSphere Message Broker V6.1 - Fix Pack\n 6.1.0.12'\n http://www-01.ibm.com/support/docview.wss?uid=swg24036648 [http://www-01.ibm.com/support/docview.wss?uid=swg24036648]\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q062", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC96183\nREPORTED COMPONENT NAME\n WMB WINDOWS V6\nREPORTED COMPONENT ID\n 5724J0500\nREPORTED RELEASE\n 610\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-09-24\nCLOSED DATE\n 2014-01-24\nLAST MODIFIED DATE\n 2014-01-24\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q062", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMB WINDOWS V6\nFIXED COMPONENT ID\n 5724J0500", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q062", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R610 PSY\n UP\n\nA FIX IS AVAILABLE\nWebSphere Message Broker V6.1 - Fix Pack 6.1.0.7 [http://www-01.ibm.com/support/docview.wss?uid=swg24026355]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q062", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Creating a new userid and adding it to the Broker results in a\n BIP7017W unknown user error. Restarting the Broker will allow\n the new userid to be recognized.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q062", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of WebSphere Message Broker and *\nthe UserNameServer. *\n\nPROBLEM DESCRIPTION: If a user was added to the *\nUserNameServer, a subscription by *\nthat user would result in a BIP7017 *\nerror message from the non-default *\nexecution groups. *\nIf the execution groups are restarted, *\nthe subscription was processed without *\nan error from the non-default execution *\ngroups. *\n\nRECOMMENDATION: *\n\nThe UserNameServer will forward new and deleted users and\n groups to the default execution group and they should be\n passed onto the non-default execution groups.\n The messages were not being correctly passed on which meant\n that the non-default execution groups did not know about\n the new user.\n If a subscription was issued for that user, the non-default\n execution groups would reject the subscription where as the\n default execution group would accept the subscription.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q062", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The default execution group was changed to pass on the\n the changes to the users to the non-default execution\n groups.\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q062", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IZ38636\nREPORTED COMPONENT NAME\n WMB SOL SPARC\nREPORTED COMPONENT ID\n 5724J0502\nREPORTED RELEASE\n 100\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2008-11-25\nCLOSED DATE\n 2008-12-18\nLAST MODIFIED DATE\n 2009-01-22\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q062", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMB SOL SPARC\nFIXED COMPONENT ID\n 5724J0502", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q062", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R100 PSY\n UP\n\nA FIX IS AVAILABLE\nWebSphere Message Broker V6.1 - Fix Pack 6.1.0.11 [http://www-01.ibm.com/support/docview.wss?uid=swg24033879]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q062", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "6.1.0.11 for WebSphere Message Broker V6.1 on Multiplatforms.\n This APAR does not represent any actual code change, instead\n is used to represent the whole fix pack.", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q062", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n All users of WebSphere Message Broker Version 6.1.\n\nPROBLEM SUMMARY:\n 6.1.0.11 for WebSphere Message Broker V6.1 on Multiplatforms.\n This APAR does not represent any actual code change, instead\n is used to represent the whole fix pack.", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q062", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "6.1.0.11 for WebSphere Message Broker V6.1 on Multiplatforms\n is now available.\n For details refer to 'WebSphere Message Broker V6.1 - Fix Pack\n 6.1.0.11'\n http://www-01.ibm.com/support/docview.wss?uid=swg24033879 [http://www-01.ibm.com/support/docview.wss?uid=swg24033879]\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q062", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC87011\nREPORTED COMPONENT NAME\n WMB WINDOWS V6\nREPORTED COMPONENT ID\n 5724J0500\nREPORTED RELEASE\n 610\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2012-10-05\nCLOSED DATE\n 2012-12-18\nLAST MODIFIED DATE\n 2014-01-24\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q062", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMB WINDOWS V6\nFIXED COMPONENT ID\n 5724J0500", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q062", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R610 PSY\n UP", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q252", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "You might see the following exception in SystemOut.log:\n\njava.sql.SQLException: ORA-01000: maximum open cursors exceeded\nat oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)\nat oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395)\nat oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802)\nat oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)\nat oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)\nat oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)\nat oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:205)\nat oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1008)\nat oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307)\nat oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3449)\nat oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3550)\nat oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1374)\nat com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecute(WSJdbcPreparedStatement.java:958)\nat com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.execute(WSJdbcPreparedStatement.java:625)\nat teamworks.sql.SQLClient.executePreparedStatement(SQLClient.java:443)\nat teamworks.sql.SQLClient.execute(SQLClient.java:216)\nat teamworks.SQLConnector$5.execute(SQLConnector.java:232)\nat teamworks.SQLConnector$5.execute(SQLConnector.java:228)\nat teamworks.sql.SQLExecutor.doExecute(SQLExecutor.java:134)\nat teamworks.sql.SQLExecutor.execute(SQLExecutor.java:79)\nat teamworks.SQLConnector.execute(SQLConnector.java:227)", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q252", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The Oracle ORA-01000 error occurs because the statement cache size property for the data source is set to a value higher than the maximum number of open cursors in the Oracle database. But, in this case, it is not good to simply increase the maximum number of open cursors in the Oracle database.\n\nThe root cause is that bind variable is not used in your SQL integration service. The SQL string that is passed to the SQL integration service contains literal values. Because most of the SQL statements for one SQL integration service have different literal values, a matching statement cannot be found in statement cache (shared pool). The cache hit ratio is very low and the execution plan is generated for each SQL statement every time.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q252", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To resolve this issue, use a bind variable in your SQL integration service.\n\nFor information on how to use the bind variable in the IBM Business Process Manager SQL integration service, see the following developerWorks article: Using the SQL integration service with WebSphere Lombardi Edition V7.2 and WebSphere Application Server V7 [http://www.ibm.com/developerworks/websphere/tutorials/1110_phi/].\n\nTo learn more about the Oracle ORA-01000 error and its corresponding solution, see the \"ORA-01000: maximum open cursors exceeded\" connecting to an Oracle database from WebSphere Application Server [http://www.ibm.com/support/docview.wss?uid=swg21218727] document.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Databases AIX, Linux, Linux zSeries, Solaris, Windows 8.5, 8.0.1, 8.0, 7.5.1, 7.5 Business Integration IBM Business Process Manager Express Databases Linux, Windows 8.5, 8.0.1, 8.0, 7.5.1, 7.5\nPRODUCT ALIAS/SYNONYM\n BPM", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q252", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The errors about missing tables (SQL0204N or ORA-00942) will be logged in the default.log file when using the history manager feature or running old version reports from the Report console. This file is located in the $TOP/logs/ directory.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q252", "section_id": 1, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "The following DB2 or Oracle error will be logged depending on your back-end database:\n\nSQL0204N is an undefined name\n\nORA-00942: table or view does not exist\n\nThe following tables will be reported as missing:\n\n 1. taud_smp_simple_object\n 2. taud_ssm_simple_simple_map\n 3. taud_shi_simple_hierarchy\n\nThe error messages in various files in the $TOP/logs directory will be similar to the error messages given below:\n\n[sch_worker_0] ERROR WPCIBMMDMPIMEstimateOldVersionsScript13189499965190 JOB_ID:28602- CWPCM0002E:Generic error / Exception: Exception:Could not execute query\nCould not execute query\nat com.ibm.ccd.common.interpreter.operation.generated.GenExecuteQueryOperation.execute(Unknown Source)\nat WPCIBMMDMPIMEstimateOldVersionsScript13189499965190.ScriptFunction__estimateOldVersions(WPCIBMMDMPIMEstimateOldVersionsScript13189499965190.java:787)\nat WPCIBMMDMPIMEstimateOldVersionsScript13189499965190.run(WPCIBMMDMPIMEstimateOldVersionsScript13189499965190.java:1752)\nat com.ibm.ccd.common.interpreter.engine.Script.runFunction(Unknown Source)\nat com.ibm.ccd.common.interpreter.engine.Script.execute(Unknown Source)\nat com.ibm.ccd.common.interpreter.engine.Script.run(Unknown Source)\nat com.ibm.ccd.report.common.Report.generate(Unknown Source)\nat com.ibm.ccd.report.common.ReportExe.execute(Unknown Source)\nat com.ibm.ccd.scheduler.threads.SchedulerThread.fuzaoRun(Unknown Source)\nat com.ibm.ccd.common.util.FuzaoRunnableAdapter.run(Unknown Source)\nat com.ibm.ccd.common.util.FuzaoThread.run(Unknown Source)\nCaused by: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist\n\nat oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440)\nat oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)\nat oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:837)\nat oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:290)\nat oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191)\nat oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:523)\nat oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193)\nat oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:852)\nat oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1153)\nat oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1275)\nat oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1477)\nat oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:392)\nat org.apache.commons.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:188)\n... 11 more", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q252", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Follow the steps mentioned below to resolve the problem:\n\n1. Copy or transfer by FTP one of the attached files to the $TOP directory of your MDM Server for PIM installation :\n\nWhen using DB2 as the back-end database transfer the db2_create_missing_tables.sql file.\n\ndb2_create_missing_tables.sql [/support/docview.wss?uid=swg21575279&aid=2] [/support/docview.wss?uid=swg21575279&aid=1]\n\nWhen using Oracle as the back-end database transfer the oracle_create_missing_tables.sql file.\n\noracle_create_missing_tables.sql [/support/docview.wss?uid=swg21575279&aid=4] [/support/docview.wss?uid=swg21575279&aid=3]\n\n2. Run the runSQL.pl script using the following command from within the $TOP directory:\n\nperl $PERL5LIB/runSQL.pl --sql_file=\n\nReplace with db2_create_missing_tables.sql or oracle_create_missing_tables.sql depending on your back-end database.\n\nAn APAR (JR40709) has been created and will be resolved in the upcoming fix pack.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q252", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "HTTP Server Adapter returning 404 responses and throwing exceptions when processing incoming requests.\n\nSymptom: Incoming HTTP requests my results in errors such as the following in the wf.log file: [2007-06-25 17:04:43.84] ERROR Chained Exception: [2007-06-25 17:04:43.84] ERROR SQL Error Code: 1 [2007-06-25 17:04:43.84] ERROR SQL State: 23000 java.sql.SQLException: ORA-00001: unique constraint (APPGIS.SCI_PK_26) violated at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java(Compiled Code)) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java(Compiled Code)) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java(Inlined Compiled Code)) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java(Compiled Code)) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java(Compiled Code)) at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java(Compiled Code)) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java(Compiled Code)) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java(Compiled Code)) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java(Compiled Code)) at com.sterlingcommerce.woodstock.util.frame.jdbc.JDBCService.executeUpdate(JDBCService.java(Compiled Code)) at com.sterlingcommerce.woodstock.workflow.Document.saveExtensions(Document.java(Compiled Code)) at com.sterlingcommerce.woodstock.workflow.Document.saveExtensions(Document.java(Inlined Compiled Code)) at com.sterlingcommerce.woodstock.workflow.Document.persist(Document.java(Compiled Code)) at com.sterlingcommerce.woodstock.workflow.WorkFlowContext.persist(WorkFlowContext.java(Compiled Code)) at com.sterlingcommerce.woodstock.workflow.WorkFlowContext.persist(WorkFlowContext.java(Inlined Compiled Code)) at com.sterlingcommerce.woodstock.workflow.engine.WEHelper.dispatch(WEHelper.java(Compiled Code)) at com.sterlingcommerce.woodstock.workflow.engine.WorkFlowEngineRMIImpl.dispatch(WorkFlowEngineRMIImpl.java(Compiled Code)) at com.sterlingcommerce.woodstock.workflow.Dispatcher.run(Dispatcher.java(Compiled Code)) at java.lang.Thread.run(Thread.java(Compiled Code))", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q252", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Document persistence code was modified within the HTTP Server Adapter to correct a persistence timing issue.\n\nFor Gentran Integration Suite Release 4.2: Please apply Gentran Integration Suite, Release 4.2 Build 4206 or higher.\n\nFor Gentran Integration Suite Release 4.1.1: Please apply Gentran Integration Suite, Release 4.1.1 Build 1982 or higher.\n\nHISTORICAL NUMBER\n NFX1161\n\nPRODUCT ALIAS/SYNONYM\n\nFunction Area\n\nAdapters - HTTP\n\nEscalation ID\n\n1365813\n\nFix ID\n\n37318\n\nSeverity\n\nCritical\n\nType\n\nNormalFix\n\nBuild\n\n4206\n1982", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q252", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "deadlock TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nOccasionally, customer will see following exception in Metrics WAS SystemOut.log file:\n\nPMGR6022E: Error using adapter to create or execute an Interaction.\n\ncom.ibm.ws.ejbpersistence.utilpm.PersistenceManagerException: PMGR6022E: Error using adapter to create or execute an Interaction.\n\nCaused by: java.sql.SQLException: ORA-00060: deadlock detected while waiting for resource\nDSRA0010E: SQL State = 61000, Error Code = 60\n\nCNTR0019E: EJB threw an unexpected (non-declared) exception during invocation of method \"create\". Exception data: com.ibm.ejs.container.CreateFailureException: ; nested exception is:\ncom.ibm.ws.exception.WsEJBException: nested exception is: com.ibm.ws.ejbpersistence.utilpm.PersistenceManagerException: PMGR6022E: Error using adapter to create or execute an Interaction.\n\nAnd the Oracle Database detected DEADLOCK (ORA-00060 ).\n\nThere is no data lose and no action needed for this case.", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q252", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "GIS 4220\n\nError Message 2009-07-29 17:42:11.35] ERROR 000000000000 GLOBAL_SCOPE Exception occured during transferring data to archive tables\n[2009-07-29 17:42:11.35] ERROR SQL Error Code: 1\n[2009-07-29 17:42:11.35] ERROR SQL State: 23000\njava.sql.SQLException: ORA-00001: unique constraint (GIS.ARCH_INFO_WRK_PK) violated\n\nat oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java(Compiled Code))\nat oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java(Compiled Code))\nat oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java(Inlined Compiled Code))\nat oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java(Compiled Code))\nat oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java(Compil ed Code))\nat oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java (Compiled Code))\nat oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java(Com piled Code))\nat oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStateme nt.java(Compiled Code))\nat oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement .java(Compiled Code))", "logical_doc_id": 4, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q252", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Issue resolved by DBA's, problems was external to GIS.\n\nHISTORICAL NUMBER\n NFX6980", "logical_doc_id": 4, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q199", "section_id": 0, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Recommended Updates for WebSphere Portal and Web Content Management V6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24024380]\n6.0.1.7 Download: WebSphere Portal and Web Content Manager V6.0.1, fix pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24025748]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q199", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Root cause is an IllegalArgumentException from theme code in\n the\n UrlGenerationTag:\n com.ibm.wps.engine.tags.UrlGenerationTag doStartTag EJPEJ0002E:\n An error occurred while executing CreateUrlCommand.\n\n com.ibm.wps.command.CommandException: EJPEJ0013E: Execution of\n CreateUrlCommand failed.\n at\n com.ibm.wps.util.CreateUrlCommand.execute(CreateUrlCommand.java:\n\n 310)\n at\n com.ibm.wps.engine.tags.UrlGenerationTag.doStartTag(UrlGeneratio\n\n Tag.java:245)\n at com.ibm._jsp._Default._jspService(_Default.java:1382)\n Caused by: java.lang.IllegalArgumentException: ObjectID is of\n wrong ResourceType!\n\n This causes a locking issue so that subsequent threads that are\n performing data modification (e.g. page layout changes) are\n hung. This is indicated by WAS warning in log file:\n WSVR0605W: Thread \"WebContainer : 4\" (00000050) has been active\n for 664095 milliseconds and may be hung. There is/are 1\n thread(s) in total in the server that may be hung.\n WSVR0605W: Thread \"WebContainer : 7\" (0000005c) has been active\n for 619985 milliseconds and may be hung. There is/are 2\n thread(s) in total in the server that may be hung.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q199", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Root cause is an IllegalArgumentException from theme code in the\n UrlGenerationTag:\n com.ibm.wps.engine.tags.UrlGenerationTag doStartTag EJPEJ0002E:\n An error occurred while executing CreateUrlCommand.\n Caused by: java.lang.IllegalArgumentException: ObjectID is of\n wrong ResourceType!\n\n This causes a locking issue so that subsequent threads that are\n performing data modification (e.g. page layout changes) are\n hung.\n This is indicated by WAS warning in log file:\n WSVR0605W: Thread \"WebContainer : 7\" (0000005c) has been active\n for 619985 milliseconds and may be hung. There is/are 2\n thread(s) in total in the server that may be hung.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q199", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This APAR corrects the exception handling in model\n synchronization code.\n\n Manual Steps:\n None\n\n Failing Module(s):\n Engine: Tags & Commands\n\n Affected Users:\n All users\n\n Version Information:\n Portal Version(s): 6.0.1.3\n Pre-Requisite(s): PK72523 [http://www-01.ibm.com/support/docview.wss?uid=swg1PK72523] PK72210 [http://www-01.ibm.com/support/docview.wss?uid=swg1PK72210]\n Co-Requisite(s): ---\n\n Portal Version(s): 6.0.1.5\n Pre-Requisite(s):\n Co-Requisite(s): ---\n\n Platform Specific:\n This fix applies to all platforms.\n\n A fix is available from Fix Central:\n\n http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde\n r?apar=PK97946&productid=WebSphere%20Portal&brandid=5 [http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorder?apar=PK97946&productid=WebSphere%20Portal&brandid=5]\n\n You may need to type or paste the complete address into your Web\n browser.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q199", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PK97946\nREPORTED COMPONENT NAME\n WEBSPHERE PORTA\nREPORTED COMPONENT ID\n 5724E7600\nREPORTED RELEASE\n 60G\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2009-10-06\nCLOSED DATE\n 2009-11-03\nLAST MODIFIED DATE\n 2009-11-09\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q199", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBSPHERE PORTA\nFIXED COMPONENT ID\n 5724E7600", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q199", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R60G PSY\n UP\nR60J PSY\n UP", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q199", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24038133]\n7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35 [http://www-01.ibm.com/support/docview.wss?uid=swg24038310]\n8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24038539]\n8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24039242]\n7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37 [http://www-01.ibm.com/support/docview.wss?uid=swg24039338]\n8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24039425]\n8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040035]\n8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24040425]\n8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24040533]\n7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39 [http://www-01.ibm.com/support/docview.wss?uid=swg24041013]\n8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041178]\n8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24041590]\n8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24041819]\n7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41 [http://www-01.ibm.com/support/docview.wss?uid=swg24041931]\n8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]\n8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24043005]\n8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24042746]\n7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43 [http://www-01.ibm.com/support/docview.wss?uid=swg24043400]\n8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]\n8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http://www-01.ibm.com/support/docview.wss?uid=swg24044096]\n8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]\n7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45 [http://www-01.ibm.com/support/docview.wss?uid=swg24044551]\n8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q199", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "A deadlock may occur when stopping an application\n that contains a resource adapter module, which causes two\n threads to hang and the application to fail to stop.\n .\n The SystemOut.log will show the following hung thread detection\n messages:\n .\n WSVR0605W: Thread \"HAManager.thread.pool : 1\" (00000017) has\n been active for 628025 milliseconds and may be hung. There\n is/are 1 thread(s) in total in the server that may be hung.\n at\n com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(C\n onnectionFactoryBuilderImpl.java:436)\n at\n javax.naming.spi.NamingManager.getObjectInstanceByFactoryInRefer\n ence(NamingManager.java:501)\n at\n javax.naming.spi.NamingManager.getObjectInstance(NamingManager.j\n ava:365)\n at\n com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupE\n xt(Helpers.java:927)\n ...\n\n WSVR0605W: Thread \"Default : 4\" (0000003e) has been active for\n 627799 milliseconds and may be hung. There is/are 2 thread(s)\n in total in the server that may be hung.\n at\n com.ibm.ejs.j2c.RALifeCycleManagerImpl.shutdown(RALifeCycleManag\n erImpl.java:1483)\n at\n com.ibm.ejs.j2c.RALifeCycleManagerImpl.stop(RALifeCycleManagerIm\n pl.java:782)\n at\n com.ibm.ws.runtime.component.ApplicationMgrImpl.stop(Application\n MgrImpl.java:1151)\n ...\n\n A Javacore will show that a deadlock has occurred:\n .\n**WARNING*** Deadlock detected in [HAManager.thread.pool : 1]\n [Default : 2]\n\n HAManager.thread.pool : 1\n State\n Deadlock/Blocked\n Monitor\n Owns Monitor Lock on\n com/ibm/ejs/j2c/RAWrapperImpl@0x000000074E493120/0x000000074E493\n 12C\n Waiting for Monitor Lock on\n java/lang/Object@0x00000007443ADCF8/0x00000007443ADD04\n Java Stack\n at\n com/ibm/ejs/j2c/ConnectionFactoryBuilderServerImpl.createCFD_Com\n mon(ConnectionFactoryBuilderServerImpl.java:330)\n at\n com/ibm/ejs/j2c/ConnectionFactoryBuilderServerImpl.processObject\n Instance(ConnectionFactoryBuilderServerImpl.java:1027)\n at\n com/ibm/ejs/j2c/ConnectionFactoryBuilderImpl.getObjectInstance(C\n onnectionFactoryBuilderImpl.java:664)\n at\n javax/naming/spi/NamingManager.getObjectInstanceByFactoryInRefer\n ence(NamingManager.java:501)\n ...\n\n Default : 2\n State\n Deadlock/Blocked\n Monitor\n Owns Monitor Lock on\n java/lang/Object@0x00000007443ADCF8/0x00000007443ADD04\n Waiting for Monitor Lock on\n com/ibm/ejs/j2c/RAWrapperImpl@0x000000074E493120/0x000000074E493\n 12C\n Java Stack\n at\n com/ibm/ejs/j2c/RALifeCycleManagerImpl.shutdown(RALifeCycleManag\n erImpl.java:1483)\n at\n com/ibm/ejs/j2c/RALifeCycleManagerImpl.stop(RALifeCycleManagerIm\n pl.java:782)\n at\n com/ibm/ws/runtime/component/ApplicationMgrImpl.stop(Application\n MgrImpl.java:1151)\n ...\n\n This is a timing/synchronization issue that can occur when\n running WebSphere Application Server with a fix pack level\n that includes apar PM93319 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM93319].", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q199", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of IBM WebSphere Application *\nServer with applications that include a *\nresource adapter. *\n\nPROBLEM DESCRIPTION: Threads hang due to a deadlock when *\nstopping an application that includes *\na resource adapter. *\n\nRECOMMENDATION: *\n\nA deadlock can occur between the application stop thread and\n the j2c resource adapter work thread doing a lookup due to\n synchronization and issues which can prevent stopping the\n application.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q199", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The WebSphere Application Server J2C code has been corrected\n to properly synchronize the locking objects.\n The fix for this APAR is currently targeted for inclusion in\n fix packs 7.0.0.35, 8.0.0.10 and 8.5.5.3. Please refer to the\n Recommended Updates page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q199", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI13428\nREPORTED COMPONENT NAME\n WEBS APP SERV N\nREPORTED COMPONENT ID\n 5724H8800\nREPORTED RELEASE\n 700\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-03-10\nCLOSED DATE\n 2014-07-15\nLAST MODIFIED DATE\n 2014-07-15\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q199", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBS APP SERV N\nFIXED COMPONENT ID\n 5724H8800", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q199", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R700 PSY\n UP\nR800 PSY\n UP\nR850 PSY\n UP", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q199", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere [http://www-01.ibm.com/support/docview.wss?uid=swg24029525]\n7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24029894]\n6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47 [http://www-01.ibm.com/support/docview.wss?uid=swg24035508]\n7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24035324]\n6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24030426]\n6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24031035]\n6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24031963]\n6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24033270]\n6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24035649]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q199", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "This APAR contains a fix to optimize how the workload\n management (WLM) component will compress and decompress data\n being sent betweenprocesses. This is designed to reduce\n compression overhead in large WebSphere Process Server or\n service integration bus (SIBus) topologies, specifically with\n a large number of destinations (more effective at 2,000 or more\n destinations). It addresses scenarios in which many clusters\n have been defined and one or more non-messaging engine (ME)\n clusters are restarted while the messaging engine cluster is\n running. A customer experiencing this may see the following:\n\n ThreadMonitor W WSVR0605W: Thread\n \"server.startup : 0\" (00000038) has been active for 686179\n milliseconds and may be hung. There is/are 1 thread(s) in total\n in the server that may be hung.\n at java.lang.Object.wait(Native Method)\n at java.lang.Object.wait(Object.java:199)\n at\n com.ibm.ws.sib.jfapchannel.impl.ExchangeReceiveListener.waitToCo\n mplete(ExchangeReceiveListener.java:235)\n\n In addition this fixes a rare condition which could result in\n compressed data being lost. This would only occur if a series\n of bytes to be compressed could not actually be compressed\n (every byte was unique). This would then cause a potential loss\n of data due to how WLM handled the uncompressed bytes.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q199", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: IBM WebSphere Process Server users or users *\nof IBM WebSphere Application Server with *\nservice integration bus (SIBus) *\nconfigurations. *\n\nPROBLEM DESCRIPTION: Workload management (WLM) Compressor *\nFix and Enhancements *\n\nRECOMMENDATION: *\n\n In scenarios in which many clusters have been defined\n and one or more non-ME clusters are restarted while the\n messaging engine cluster is running, a customer experiencing\n this may see the following:\n\n ThreadMonitor W WSVR0605W: Thread\n \"server.startup : 0\" (00000038) has been active for 686179\n milliseconds and may be hung. There is/are 1 thread(s) in total\n in the server that may be hung.\n at java.lang.Object.wait(Native Method)\n at java.lang.Object.wait(Object.java:199)\n at\n com.ibm.ws.sib.jfapchannel.impl.ExchangeReceiveListener.waitToCo\n mplete(ExchangeReceiveListener.java:235)", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q199", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This APAR contains a fix to optimize how the WLM component\n will compress and decompress data being sent between\n processes. This is designed to reduce compression overhead in\n large WPS/SIB topologies, specifically with a large number of\n destinations (more effective at 2,000 or more destinations).\n\nIn addition this fixes a rare condition which could result in\n compressed data being lost. This would only occur if a series\n of bytes to be compressed could not actually be compressed\n (every byte was unique). This would then cause a potential loss\n of data due to how WLM handled the uncompressed bytes.\n\nAlthough it is not recommended, the compression optimizations\n can be removed and the code reverted back to the prior code if\n problems are seen by setting a cell level custom property:\n\nIn the administrative console, go to the Custom properties\n page for the cell.\n\nSystem administration > Cell > cell_name, and then, under\n Additional Properties, click Custom Properties\n\nCreate a new custom property with a name of:\n\nIBM_CLUSTER_USE_LEGACY_COMPRESSOR\n\nand a value of true. Save, Synchronize the nodes and restart\n all of the processes in the cell to pick up this change.\n\nThe fix for this APAR is currently targeted for inclusion in\n fix packs 6.1.0.37 and 7.0.0.17. Please refer to the\n Recommended Updates page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q199", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM27960\nREPORTED COMPONENT NAME\n WEBS APP SERV N\nREPORTED COMPONENT ID\n 5724H8800\nREPORTED RELEASE\n 61I\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2010-12-01\nCLOSED DATE\n 2011-03-02\nLAST MODIFIED DATE\n 2011-03-02\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q199", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBS APP SERV N\nFIXED COMPONENT ID\n 5724H8800", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q199", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R61A PSY\n UP\nR61H PSY\n UP\nR61I PSY\n UP\nR61P PSY\n UP\nR61S PSY\n UP\nR61W PSY\n UP\nR61Z PSY\n UP\nR700 PSY\n UP", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q199", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Message processing, that is related to event-sequenced operations, stops. After handling several messages, further messages wait in the Service Component Architecture (SCA) bus queues and event-sequenced es-workmanager hung-thread WSVR0605W warnings are seen in the log files and traces. The entire process of event-sequenced messages in the system is effectively blocked.\n\nThe following code is an example of an es-workmanager hung-thread warning:\n\n[01/01/11 12:00:37:844 CEST] 0000000d ThreadMonitor W WSVR0605W: Thread \"WorkManager.es-workmanager : 9\" (0000012e) has been active for 602495 milliseconds and may be hung. There is/are 5 thread(s) in total in the server that may be hung.\nat java.lang.Object.wait(Native Method)\nat java.lang.Object.wait(Object.java:231)\nat com.ibm.ws.util.BoundedBuffer.waitPut_(BoundedBuffer.java:229)\nat com.ibm.ws.util.BoundedBuffer.put(BoundedBuffer.java:339)\nat com.ibm.ws.util.ThreadPool.execute(ThreadPool.java:1189)\nat com.ibm.ws.util.ThreadPool.execute(ThreadPool.java:1040)\nat com.ibm.ws.asynchbeans.WorkItemImpl$PoolExecuteProxy.run(WorkItemImpl.java:197)\nat com.ibm.ws.asynchbeans.WorkItemImpl.executeOnPool(WorkItemImpl.java:211)\nat com.ibm.ws.asynchbeans.WorkManagerImpl.queueWorkItemForDispatch(WorkManagerImpl.java:425)\nat com.ibm.ws.asynchbeans.WorkManagerImpl.startWork(WorkManagerImpl.java:381)\nat com.ibm.ws.asynchbeans.WorkManagerImpl.startWork(WorkManagerImpl.java:510)\nat com.ibm.ws.asynchbeans.WorkManagerImpl.startWork(WorkManagerImpl.java:525)\nat com.ibm.wbiserver.sequencing.service.BaseEsService.submitWork(BaseEsService.java:417)\n...", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q199", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Event sequencing uses a WebSphere Application Server (WAS) thread pool. This event-sequencing thread pool is named \"es-workmanager,\" by default, and it is configured during the profile creation process. The startWork method behavior is that the method is blocked until the work is placed in the thread pool and then returned. The work is later run asynchronously. If there are not enough threads available in the es-workmanager thread pool, the startWork call to the work manager is blocked indefinitely and the WSVR0605W es-workmanager hung-thread warnings are thrown. With each warning, the number of blocked threads increases.", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q199", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To resolve the problem, you must tune the thread pool size for the es-workmanager thread pool. By default, the es-workmanager thread pool is created with a minimum of 2 threads and a maximum of 20 threads. Also, the Growable option is set to true, which means that the number of threads can go beyond the maximum, if needed. When the defaults are used, this issue should not happen because the thread pool can grow, if necessary. However, in certain situations, it might be necessary to limit and tune the maximum thread pool size. In these situations, individual performance tuning is necessary to prevent blocked threads. You can tune es-workmanager thread-pool properties in a pre-production test environment to avoid performance problems on a production server.\n\nYou can access the configuration for work managers in the administrative console under Resources > Asynchronous beans > Work managers > es-workmanager. The task of configuring work managers is also described in the Configuring work managers [http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/asyncbns/tasks/tasb_workmanager.html] topic within the information center:", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q199", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#WebSphere Process Server V7.0 Information Center [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wps.doc/welcome_wps.html]\n\nPRODUCT ALIAS/SYNONYM\n WPS", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q199", "section_id": 4, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24032315]\n7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23 [http://www-01.ibm.com/support/docview.wss?uid=swg24032493]\n8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24033190]\n7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25 [http://www-01.ibm.com/support/docview.wss?uid=swg24033267]\n8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24033754]\n7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27 [http://www-01.ibm.com/support/docview.wss?uid=swg24033882]\n8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24034673]\n7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29 [http://www-01.ibm.com/support/docview.wss?uid=swg24034966]\n8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24035457]\n8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24036729]\n7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31 [http://www-01.ibm.com/support/docview.wss?uid=swg24036768]\n7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24035324]\n7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33 [http://www-01.ibm.com/support/docview.wss?uid=swg24037573]\n8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24037574]\n7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35 [http://www-01.ibm.com/support/docview.wss?uid=swg24038310]\n8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24039242]\n7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37 [http://www-01.ibm.com/support/docview.wss?uid=swg24039338]\n8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24040425]\n7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39 [http://www-01.ibm.com/support/docview.wss?uid=swg24041013]\n8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24041590]\n7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41 [http://www-01.ibm.com/support/docview.wss?uid=swg24041931]\n8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24042746]\n7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43 [http://www-01.ibm.com/support/docview.wss?uid=swg24043400]\n8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http://www-01.ibm.com/support/docview.wss?uid=swg24044096]\n7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45 [http://www-01.ibm.com/support/docview.wss?uid=swg24044551]\n8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q199", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "An application server JVM can hang if a thread logging an FFDC\n hangs.\n\n The problem can be detected by observing the WSVR0605W hung\n thread notifications in the SystemOut.log.\n\n One thread will be running the FFDCFilter.processException()\n which can be invoked from any WebSphere Application Server\n component. The thread will get stuck doing its work.\n In the following example, the thread which invoked\n FFDCFilter.processException() is stuck waiting on a response to\n the OracleConnectionWrapper.getMetaData() method call:\n\n [05/24/12 12:06:35:286 EST] 00000016 ThreadMonitor W\n WSVR0605W: Thread \"ORB.thread.pool : 32\" (000000d6) has\n been active for 304721 milliseconds and may be hung. There\n is/are 16 thread(s) in total in the server that may be hung.\n at\n oracle.jdbc.OracleConnectionWrapper.getMetaData(OracleConnection\n Wrapper.java:150)\n at\n com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.introspectSe\n lf(WSRdbManagedConnectionImpl.java:1480)\n at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n at\n sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor\n Impl.java:60)\n at\n sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod\n AccessorImpl.java:37)\n at java.lang.reflect.Method.invoke(Method.java:611)\n at\n com.ibm.ws.ffdc.impl.Formatters$IntrospectSelfFormatter$1.run(Fo\n rmatters.java:99)\n at\n com.ibm.ws.ffdc.impl.Formatters$IntrospectSelfFormatter$1.run(Fo\n rmatters.java:96)\n\n ...\n\n at\n com.ibm.ffdc.util.provider.IncidentEntry.log(IncidentEntry.java:\n 96)\n at com.ibm.ffdc.util.provider.Ffdc.log(Ffdc.java:90)\n at\n com.ibm.ws.ffdc.FFDCFilter.processException(FFDCFilter.java:114)\n at\n com.ibm.ejs.j2c.FreePool.createOrWaitForConnection(FreePool.java\n :1671)\n at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2496)\n\n Looking later in the SystemOut.log, there will be more hung\n thread notifications which show that the\n FFDCFilter.processException() method is stuck waiting on an\n Ffdc. call to complete. The stack trace of such a thread\n will look like this:\n\n [05/24/12 12:42:35:914 EST] 00000003 ThreadMonitor W\n WSVR0605W: Thread \"ORB.thread.pool : 29\" (000007f4) has been\n active for 224151 milliseconds and may be hung. There is/are 23\n thread(s) in total in the server that may be hung.\n at com.ibm.ffdc.util.provider.Ffdc.(Ffdc.java:64)\n at\n com.ibm.ffdc.util.provider.FfdcProvider.getFfdc(FfdcProvider.jav\n a:289)\n at com.ibm.ffdc.impl.Ffdc.getFfdc(Ffdc.java:188)\n at\n com.ibm.ws.ffdc.FFDCFilter.processException(FFDCFilter.java:112)\n at\n com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteUpda\n te(WSJdbcPreparedStatement.java:1179)\n at\n com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeUpdate(\n WSJdbcPreparedStatement.java:816)\n\n It is possible that the first FFDC thread which got hung (in\n this example, \"ORB.thread.pool : 32\") will eventually complete.\n If it does complete, the threads will start moving and the hang\n will clear up. However, if it never completes, then it is the\n same as if a true thread deadlock had occurred.\n\n This same type of analysis can be performed using a\n javacore/thread dump, however, javacores are not always\n available.", "logical_doc_id": 5, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q199", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of IBM WebSphere Application *\nServer V7.0 and V8.0 *\n\nPROBLEM DESCRIPTION: Syncrhonization between FFDC *\nincidents can cause a server hang *\nwhen an unrecoverable problem *\noccurs in a given incident. *\n\nRECOMMENDATION: *\n\nSyncrhonization between FFDC incidents can cause a server hang\n when an unrecoverable problem occurs in a given incident.", "logical_doc_id": 5, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q199", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "FFDC has been modified to ensure that incidents can continue\n to be logged from other components when a given component's\n incident-handling hangs a thread. The impact to this is that\n the FFDC summary log may indicate that the incident file of a\n bad thread was created, while the thread may not have returned\n so the incident file will not exist. Therefore, a missing\n incident entry that might have appeared in a summary file is\n an indication that the component logging to FFDC did not\n return control.\n\nThe fix for this APAR is currently targeted for inclusion in\n fix packs 7.0.0.23 and 8.0.0.3. Please refer to the\n Recommended Updates page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q199", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM45011\nREPORTED COMPONENT NAME\n WEBS APP SERV N\nREPORTED COMPONENT ID\n 5724H8800\nREPORTED RELEASE\n 700\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2011-08-03\nCLOSED DATE\n 2011-12-15\nLAST MODIFIED DATE\n 2012-06-01\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q199", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBS APP SERV N\nFIXED COMPONENT ID\n 5724H8800", "logical_doc_id": 5, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q199", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R700 PSY\n UP\nR800 PSY\n UP", "logical_doc_id": 5, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q077", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "A program defect was filed with SPSS Development. Technical Support was unable to replicate the crash. SPSS Development was able to trigger ASSERT_ warnings with program crashes by renaming the spss.err file that was mentioned in the later part of your error messages. They have made program changes to avoid such crashes in the future. However, they were unable to replicate the error in the context of running the customer's MIXED syntax on the customer's data.\n\nThe customer has since reported that all of the computers involved in these crashes had Iolo System Mechanic Professional installed. Subsequent runs of the same analysis on computers without System Mechanic ran without error messages or crashes. Users that experience system crashes with the message:\n\n_ASSERT(qfirst) failed in mxceff\n\nshould examine the computer to see if Iolo System Mechanic is installed. If so, try the analysis on a computer without System Mechanic.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q077", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\n\nHISTORICAL NUMBER\n 91124", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q077", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "There are a number of possible causes for this symptom. The following instructions are designed to guide you through resolving most common causes.\n\nThe two most common types of problems are:\n\n(1) Upon inserting the IBM SPSS product installation CD, no menu appears providing you with the option to install SPSS.\n(2) Upon inserting the IBM SPSS product installation CD, a menu appears allowing you to select the option to install my IBM SPSS product. However, after selecting this option the SPSS program does not install.\n\nIf the problem you are experiencing is more like (1) go to (A1).\nIf the problem you are experiencing is more like (2), select the \"Browse the CD ROM\" option and see instructions in (B1)\n\n(A1)\nIf available, insert the IBM SPSS product installation CD in a different computer.\nIf the same problem occurs, see instructions in (A2).\nIf the problem does not occur, see instructions in (B1).\n\n(A2)\nRemove the IBM SPSS product installation CD.\nIf disk is clean and without cracks, see instructions in (A4).\nIf the IBM SPSS product installation CD is not clean, see instructions in section (A3)\nIf the IBM SPSS product installation CD is cracked, contact your software vendor to request a replacement.\n\n(A3)\nUse soap, warm water and a soft cloth that is not abrasive to clean the surface.\nThoroughly dry with a clean, soft cloth.\nVerify that all foreign material has been removed.\nReinsert the the IBM SPSS product installation CD .\nIf the installation menu still does not appear, see instructions in (A4)\nIf the installation menu appears, select the \"Browse the CD ROM\" option and see instructions in (B1)\n\n(A4)\nOpen My Computer (XP) or Computer (Vista) or Finder (Macintosh).\nBrowse to CD drive.\nIf you can view the files/folders on the CD, see instructions in (B1a) for Microsoft Windows operating systems OR (B1b) for Apple Macintosh operating systems.\nIf you can not view the files or folders on the CD, see instructions in (A5)", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q077", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "(A5)\nRemove the the IBM SPSS product installation CD .\nLocate another program installation CD from another product.\nInsert the CD.\nIf the alternate CD starts normally, contact your vendor for a replacement SPSS installation CD.\nIf the alternative CD does not start normally, you may be experiencing a problem with your drive which may require technical assistance to correct.\n\n(B1a)\nLocate the folder labeled 'SPSS' or 'Statistics' (without quotes).\nRight-click on the folder.\nSelect the Copy menu option.\nMinimize the window where the CD files appear.\nGo to your Windows or Macintosh Desktop (which appears when you boot the computer).\nRight-click on an open area of the Windows Desktop (not on a folder).\nSelect the Paste menu option.\nWait for your computer to complete copying the folder and included files.\nIf the SPSS folder and included files copies successfully, there should be a folder labeled 'SPSS' or 'Statistics' (without quotes) on your Windows Desktop. See instructions in (B2a).\nIf the folder and included files do not copy successfully, contact SPSS Technical Support.\n\n(B1b)\nLocate the folder labeled 'SPSS' or 'Statistics' (without quotes).\nDrag (or copy) the folder to your Macintosh Desktop.\nIf the SPSS folder and included files copies successfully, there should be a folder labeled 'SPSS' or 'Statistics' (without quotes) on your Macintosh Desktop. See instructions in (B2b).\nIf the folder and included files do not copy successfully, contact SPSS Technical Support.\n\n(B2a)\nDouble-click the SPSS folder located on your Windows Desktop.\nVista users: Right-click on the file labeled 'Setup' (without quotes) and select the 'Run as administrator' (without quotes) menu option.\nXP users: Double-click on the file labeled 'Setup' (without quotes).\nInstall the software providing the correct responses when prompted.\nIf SPSS installs normally, proceed to license your product in the normal manner.\nIf SPSS does not install normally, contact SPSS Technical Support.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q077", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "(B2b)\nOpen the 'SPSS' or 'Statistics' folder.\nLocate the file whose label includes 'Installer'.\n(This file should be a 'disk image' file with the file extension of 'dmg'.)\nDouble-click the 'dmg' file.\nAnother file with the name 'Installer' should appear in a separate window.\n(This file should be an 'application' file with the file extension of 'app'.)\nDrag the 'app' file to your Desktop.\nDouble-click this file.\nThe installation process should begin.\nInstall the software providing the correct responses when prompted", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q077", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\n\nHISTORICAL NUMBER\n 79748", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q077", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "I have SPSS AMOS installed on my Windows computer. I do not have SPSS Statistics installed on that computer but I oftern receive SPSS Statistics data files (.sav) to analyze. When I try to view the data, either from the File->Data Files dialog in AMOS or by the View Data choice in the IBM SPSS AMOS section of the Start->All Programs menu, I receive a message that SPSS Base must be installed to view an SPSS data file in AMOS.", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q077", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "The message is correct. When you choose View Data in AMOS and point to an SPSS Statistics data file (.sav), SPSS Statistics is launched with the data viewer forward. If SPSS Statistics is not installed, then the error message will be printed. (Several years ago, the facilities that used to be packaged as the Base module were divided in previo into the Core, which includes the Data Viewer, and the Base Module, which includes procedures such as Frequencies, Correlations and Linear Regression. The core would be enough to launch the Data Viewer from AMOS).", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q077", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our AMOS forum is Live! [https://developer.ibm.com/answers/search.html?f=&type=question&redirect=search%2Fsearch&sort=relevance&q=%2B[amos]]", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q077", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The workaround is to turn off \"Hide extension for known files types\", then rename lservrc to it's correct state.\n\nFor Windows XP - Open \"My Computer\" > \"Tools\" > \"Folder Options\"\nFor Windows Vista - Open \"Computer\" > \"Organise\" > \"Folder and Search Options\".\n\nOnce extensions are viewable, open the Statistics 17 installation directory, default being: C:\\Program Files\\SPSSinc\\Statistics17 or \\PASWStatistics17.\nRight click the file 'lservrc.txt' / 'lservrc.dat' and rename it to just 'lservrc'\nYou should now be able to restart Statistics", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q077", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our AMOS forum is Live! [https://developer.ibm.com/answers/search.html?f=&type=question&redirect=search%2Fsearch&sort=relevance&q=%2B[amos]]\n\nHISTORICAL NUMBER\n 86020", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q077", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Where do I get support for IBM SPSS Student Version or Graduate Pack software?", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q077", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Step 1:\nFor installation & licensing issues on Student version and Graduate pack, contact your vendor.\nHearne [http://www.hearne.software/Software/SPSS-Grad-Packs-for-Students-by-IBM/FAQ]\nOn the Hub [http://onthehub.com/]\nStudentDiscounts.com [http://studentdiscounts.com/contact-us.aspx]\nJourneyEd [https://www.journeyed.com/contact]\nthinkEDU [https://thinkedu.desk.com/]\nStudica [http://www.studica.com/technical-support]\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", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q008", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "A static route forces the DataPower appliance to use a specific interface and a specific set of network hops to access a given set of destinations. The \"default route\" is created by setting the Default Gateway of an interface on a DataPower appliance.\n\nA default route will be used if a known route does not exist for a given destination address. If multiple default routes are configured, the appliance will randomly pick which interface to use for outbound traffic if a more specific route cannot be found.\n\nIf you want your network traffic to follow a specific route, set a static route and NOT rely on the default gateway. As a general rule, the management interface should not have the default gateway set, as you generally want to restrict the connections that can be made through that interface.\n\nA general recommendation is to set specific static routes and only ONE default gateway that will catch all traffic not being directed by the static routes.\n\nConsider the following example after running this command from the CLI:\n\nxs40# show route\n\ndestination interface gateway metric 0.0.0.0/0 eth0 167.91.8.1 0 0.0.0.0/0 eth1 167.91.7.1 0 0.0.0.0/0 mgt0 10.238.77.1 0 10.238.77.0/24 mgt0 [/support/docview.wss?uid=swg21249208&aid=1] 0 167.81.18.0/23 eth0 [/support/docview.wss?uid=swg21249208&aid=1] 0 167.81.18.0/23 eth1 [/support/docview.wss?uid=swg21249208&aid=1] 0\n\nThe output above shows that three default gateways were configured on eth0, eth1, and mgt0 which causes three \"default\" route to be generated (0.0.0.0/0). If the destination address of your service is 166.84.23.4, the device will randomly choose any one of the default routes as no specific route is configured. If, for example, the gateway picked is 10.238.77.1 and the gateway does not know how to route to the needed backend server ip address, this will cause unexpected connection failures. In the case of such failure, a reboot of the device will lead to a different route to be randomly picked, thus temporarily resolving until the next failure.\n\nFirmware 3.7.2 and later\n\nInstructions for setting the default gateway and for setting a static route can be found in the \"Managing the appliance\" section of the Administrators Guide. The command line commands are ip default-gateway and ip route respectively, and more information is available in the CLI Reference Guide.\n\nFirmware earlier than 3.7.2", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q008", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Instructions for setting the default gateway and static routes can be found in the \"Ethernet Interface\" appendix of the WebGUI Guide. The command line commands are ip default-gateway and ip route respectively, and more information is available in the CLI Reference Guide.\n\nTo access product documentation, see these instructions. [http://www.ibm.com/support/docview.wss?rs=2362&uid=swg21377654]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower Integration Appliance XI50 Not Applicable Firmware 3.8.2, 3.8.1, 3.8, 3.7.3 Business Integration WebSphere DataPower B2B Appliance XB60 Not Applicable Firmware 3.7.3 Business Integration WebSphere DataPower Low Latency Appliance XM70 Not Applicable Firmware 3.7.3 Business Integration WebSphere DataPower XML Security Gateway XS40 Not Applicable Firmware 3.8.2, 3.8.1, 3.8, 3.7.3 Business Integration WebSphere DataPower XML Accelerator XA35 Not Applicable Firmware 3.8.2, 3.8.1, 3.8, 3.7.3", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q008", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do I add the Data Integration Module to an IBM WebSphere DataPower Service Gateway XG45 appliance?\n\nThe following document provides assistance on upgrading a DataPower Service Gateway XG45 appliance to add the Data Integration Module.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q008", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "To add the Data Integration Module:\nThe appliance must be a DataPower Service Gateway XG45 running firmware 4.0.2.0 or later.\nYou purchased the Data Integration Module and received a letter that contains the Controlled Access Key to download the firmware image.\n\nPart 1: Accessing the Web site that contains the firmware image.\nUsing your IBM account and Controlled Access Key, access the Web site to download the firmware image that contains the Data Integration Module.\n\n1. Identify the serial number for your appliance * From the WebGUI, click Status -> System -> Version Information.\nFrom the command line, issue the show version command.\n\n2. Follow the instructions in the Authorized Feature Download letter to access the WebSphere DataPower Registered Downloads portal [http://www.ibm.com/services/forms/preLogin.do?lang=en_US&source=swg-datapowerapps].\n\n3. Sign in using your IBM user ID and password. Register, if you do not have an ID.\n\n4. Enter the Controlled Access Key in the letter to access the web page containing the firmware images. Ensure that the first 7-characters of the Controlled Access Key in the letter matches the serial number for the appliance that you obtained in step\n\n1.\n\nYou are now ready to continue to Part 2 to download the firmware image.\n\nPart 2: Downloading the firmware image.\n\n1. Download the image.\n\n2. Do not transfer the image to the appliance at this time. You will install the image in Part 4: Installing the firmware image.\n\nPart 3: Preparing for the firmware upgrade.\nReview the installation instructions and prepare your appliance for the firmware upgrade.\n\n1. Read the upgrade documentation in the version-specific DataPower information center. Instructions for accessing the correct information center is in the [http://www-01.ibm.com/support/docview.wss?rs=2362&uid=swg21377654]IBM WebSphere DataPower Product Documentation Portal [http://www-01.ibm.com/support/docview.wss?rs=2362&uid=swg21377654] technical flash. The steps in this flash provide additional information to use with the upgrade documentation in the information center.\n\n2. Save the current configuration. * From the WebGUI, click Save Config.\nFrom the command line, issue the write memory command.\n\n3. Create a backup of the entire system, and store the configuration in a safe location off of the appliance.\n\n4. Confirm that you have a working admin account and a back up privileged account that can change the password for the admin account, if needed.\n\n5. Make sure that the passwords for both accounts were recently changed.\n\nPart 4: Installing the license image.\nInstall the license image. Each license image uses the serial number of the appliance as the key.\n\n1. Remove appliance from production.\n\n2. Following the instructions upgrade documentation in the information center: * Remove extraneous files\nReboot the appliance to release temporary storage\nTransfer the firmware image to the appliance\nInstall the firmware image", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q008", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "3. Verify that the appliance has the Data Integration Module. * From the WebGUI, click Status -> System -> Device Features. The list includes: * Binary processing support\nPKCS #7 and S/MIME support\nSQL-ODBC support\nDatabase Connectivity Option support\nFrom the command line, issue the show features command. The list includes: * DataGlue\nPKCS7-SMIME\nSQL-ODBC\nDCO\n\nPart 5: Installing the firmware image.\nInstall the firmware image. XG45 firmware images selectively install only the features licensed for the appliance. In order to make the Data Integration Module features available, the firmware must be upgrade after installing the license image.\n\n1. Download the firmware image for your appliance model and licenses from FixCentral\n\n2. Upgrade the appliance firmware following the upgrade documentation in the information center\n\n3. Repeat part 4", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q008", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "step 3 and ensure all of the licenses are both enabled and available.\n\nIf the installation is successful and the list does not include the features for the Data Integration Module, the most likely reason is that the firmware image was for a different appliance. Each firmware image to add the Data Integration Module uses the serial number of the appliance as the key. If you install a downloaded image to a different appliance, you will notice that the firmware is upgraded to that firmware level and that the features for the Data Integration Module are not available.\n\nIf you accessed the download site using the Controlled Access Key and installed the downloaded image to the appliance with the matching serial number and the feature list does not include the features for the Data Integration Module, contact IBM Support [http://www-01.ibm.com/support/docview.wss?uid=swg21236322].\n\nContacting IBM Support\nWhen reporting the problem to IBM Support, the representative will need your Controlled Access Key in addition to the standard information to include. Go to Contacting IBM WebSphere DataPower Appliances Support [http://www-01.ibm.com/support/docview.wss?uid=swg21236322].", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q008", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do I export and import private keys between the same or different Hardware Security Module (HSM) enabled IBM WebSphere DataPower SOA Appliance?", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q008", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "HSM-enabled DataPower appliances support the export of private keys using the crypto-export command. For key export to work, various conditions must be met:\nHSMs must be initialized and in the same key sharing domain on exporting and importing machines\nThe private key in question must be marked exportable at keygen time (see keygen's exportable option)\nHSMs on exporting and importing machines must share internal key-wrapping keys (see hsm-clone-kwk command). A key-wrapping key is a key that encrypts another key.\n\nEach HSM has a special key inside of it, the key-wrapping key, that is used to encrypt exported private keys (and to decrypt imported private keys). If the goal is to restore exported keys to the same appliance, then you don't need to worry about hsm-clone-kwk, red keys, or the hsm-domain parameter. That is because the key-wrapping key at import time will already match the key-wrapping key at export time (since the HSM device is the same). If the goal is to move exported keys from one appliance to another one, then all of the steps in this section must be followed :-\n\nFirst, the two HSMs in question must be both be initialized and in the same key sharing domain. This means that they must both be initialized in the same mode (both in Security Level 2 or both in Security Level 3). In Security Level 2 mode, they must have used the same hsm-domain parameter during hsm-reinit (this parameter has a default value that is the same on all appliances). In Security Level 3 mode, they must have used the same red PED key during hsm-reinit (and the second initialization must not have overwritten the key value from the first initialization).\n\nSecond, the key to be exported must be exportable. The exportability of keys is immutable. It is determined at keygen time, and it is controlled by that command's exportable parameter. If a key was created outside of the appliance (not using keygen), then it is always considered exportable.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q008", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Finally, before the crypto-export crypto-import sequence, the key-wrapping keys must be synchronized using the hsm-clone-kwk command. This command must be run four times: once on the source HSM appliance (with the key-wrapping key you are copying), once on the destination HSM appliance, once again on the source HSM appliance, and once again on the destination HSM appliance. Each time the command is run, it will need the output file from the previous step (as the input to the current step) which must be moved manually (usually with the copy command).\n\nOnce all of this has been done, then private keys may move from system to system with crypto-export and crypto-import.\n\nNote that the non-HSM appliance can export keys immediately at keygen time, but never at a later time.\n\nFor additional information refer to the online Info Center [http://publib.boulder.ibm.com/infocenter/wsdatap/v3r8m2/index.jsp?topic=%2Fxi50%2Fwelcome.htm] and search for \"PIN entry device\".\n\nNote: You will need to sign into the documentation portal with your IBM Registration ID and password.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q008", "section_id": 2, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Fix packs for DataPower XML Security Gateway version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034955]\nFix packs for DataPower B2B Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034956]\nFix packs for DataPower Integration Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034957]\nFix packs for DataPower Low Latency Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034958]\nFix packs for DataPower Service Gateway version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034959]\nFix packs for DataPower Service Gateway version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036407]\nFix packs for DataPower B2B Appliance version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036409]\nFix packs for DataPower Integration Appliance version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036410]\nFix packs for DataPower Service Gateway version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037486]\nFix packs for DataPower B2B Appliance version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037487]\nFix packs for DataPower Integration Appliance version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037488]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q008", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Problem description:\n When attempting to create a checkpoint, the operation might take\n too long and time out. The WebGUI shows \"Permission denied\"\n error. In the error log:\n\n20140610T174011Z [mgmt][error] : tid(1550207): Save Checkpoint -\n Error creating\n 'Checkpoint-test-1'.\n 20140610T174011Z [cli][error] : tid(32307809): Failed saving\n checkpoint -\n Please show logs for details..\n 20140610T174011Z [cli][error] : tid(32307809): === Line 2: save\n chkpoint\n \"Checkpint-test-1\"", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q008", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "User might experience an error when creating a checkpoint in a\n domain when the export takes longer than the allowed time.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q008", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fix is available in 5.0.0.17, 6.0.0.9, 6.0.1.5 and 7.0.0.2.\n\nFor a list of the latest fix packs available, please see:\n http://www-01.ibm.com/support/docview.wss?uid=swg21237631 [http://www-01.ibm.com/support/docview.wss?uid=swg21237631]\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q008", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT02925\nREPORTED COMPONENT NAME\n DATAPOWER\nREPORTED COMPONENT ID\n DP1234567\nREPORTED RELEASE\n 500\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-07-04\nCLOSED DATE\n 2014-09-19\nLAST MODIFIED DATE\n 2014-09-26\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q008", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n DATAPOWER\nFIXED COMPONENT ID\n DP1234567", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q008", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R500 PSY\n UP\nR600 PSY\n UP\nR601 PSY\n UP\nR700 PSY\n UP\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q008", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When a Gateway node is removed from an IBM API Management\n environment, there are some scenarios where the configuration\n of the Gateway node might not be successfully cleaned. If the\n administrator tries to add the same Gateway node back in to\n the environment, the following error is displayed.\n\nerror message key:\n error message text: \"An error ocurred while adding the gateway\n appliance ''${0}'' to the loadbalancer group used for internal\n traffic. The error was: ${1}: ${2}\"", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q008", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "This issue can be resolved by manually removing the load\n balancer configuration from the Gateway node (DataPower\n appliance). To manually remove the load balancer, run the\n following CLI or GUI commands: (where your\n DataPower appliance is configured to use the network interface\n \"eth0\", and the load balancer group is \"123\") By\n using the CLI: * ssh *\n enter your login credentials * co * int eth0 * no\n standby 123 * exit * write mem By using the\n DataPower user interface: Open the Network and\n Interface folders in the navigation tree. * Click \"Ethernet\n Interface\". * Click the relevant interface row in the\n table. * Select the \"Standby Control\" tab. * Click X\n on the relevant table row to delete the load balancing\n group. * Click \"Apply\". * Click \"Save Config\" in the\n page header. Also, to prevent any port conflicts,\n remove all IBM API Management domains from the Gateway node\n (DataPower appliance) too. The IBM API Management related\n domains have the format of \"APIMgmt_<10 alphanumeric\n characters>\". Otherwise, adding the Gateway node appears to\n complete successfully but when APIs that are created by using\n the recreated Management node are accessed, you see 404 errors.", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q008", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "When a Gateway node is removed from an IBM API Management\n environment, there are some scenarios where the configuration of\n the Gateway node might not be successfully cleaned. If the\n administrator tries to add the same Gateway node back in to\n the environment, an error is displayed.\n\nIn particular, this occurs if the Management node(s) of the\n environment is deleted and recreated without first removing\n the Gateway node (the Gateway node was never actually removed\n from the environment).\n\nThe external symptom of this problem is the error message that\n is displayed when adding the gateway node.\n\nerror message key: FAILURE_ADDING_APICALL_LOADBALANCER\n error message text: \"An error ocurred while adding the gateway\n appliance ''${0}'' to the loadbalancer group used for internal\n traffic. The error was: ${1}: ${2}\"", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q008", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The IBM API Management code has been updated to resolve this\n error.\n\nThe update has been addressed in IBM API Management V2.0\n cumulative ifix 002 and will be officially included in IBM API\n Management fixpack V2.0.0.1\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q008", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n LI77490\nREPORTED COMPONENT NAME\n IBM API MANAGEM\nREPORTED COMPONENT ID\n 5725L3000\nREPORTED RELEASE\n 200\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-07-09\nCLOSED DATE\n 2013-07-11\nLAST MODIFIED DATE\n 2013-07-11\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q008", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n IBM API MANAGEM\nFIXED COMPONENT ID\n 5725L3000", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q008", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R200 PSY\n UP", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q215", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "A FIX IS AVAILABLE\nWebSphere MQ V7.0 Fix Pack 7.0.1.12 [http://www-01.ibm.com/support/docview.wss?uid=swg24037169]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q215", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "WebSphere MQ Classes for Java/JMS V7.0.1.5 (or later): Failure\n Data Capture (FDC) files\n with Probe\n ID JO076001 and JO205001 are generated following a remote\n connection to a Queue Manager that has conversation sharing\n disabled:\n\n| Probe Id :- JO076001\n | Component :- RemoteFAP.MQOPEN(Hconn,MQOD,int,Phobj,Pi\n | Probe Type :- INCORROUT\n | Comment1 :- MQOPEN reply expected\n\n| Probe Id :- JO205001\n | Component :- RemoteConnection.removeHconn(RemoteTls,R\n | Probe Type :- INCORROUT\n | Comment1 :- Hconn is not associated with this connection", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q215", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n This issue affects users of the WebSphere MQ V7.0.1.5 Classes\n for Java/JMS (or later) who have established a remote connection\n to a Queue Manager via a channel that has Conversation Sharing\n disabled (SHARECNV=0 or SHARECNV=1).\n\nThis includes users of:\nThe WebSphere MQ V7.0.1 Classes for JMS\nThe WebSphere MQ V7.0.1 Resource Adapter.\nThe WebSphere Application Server V7.0 and V8.0 WebSphere MQ\n messaging provider.\nThe WebSphere Application Server V6.1 WebSphere MQ messaging\n provider who have configured the WebSphere variable\n MQ_INSTALL_ROOT to point to a WebSphere MQ V7.0.1 installation.\n\nPlatforms affected:\n All Distributed (iSeries, all Unix and Windows)\n\nPROBLEM SUMMARY:\n By default in the WebSphere MQ Classes for Java/JMS,\n conversation\n sharing is enabled and set to 10 on the client side. The client\n only discovers that Conversation Sharing is disabled following\n negotiation with a Queue Manager on the completion of a\n connection over a Channel that has SHARECNV=0 or SHARECNV=1.\n\nWhen a WebSphere MQ Classes for Java/JMS application requests a\n remote connection to a Queue Manager the client first attempts\n to find an already established TCP/IP connection which can be\n shared. As part of this process the list of known TCP/IP\n connections are matched for their suitability, this list\n includes connections which are in the process of being\n established (MQCONN reply not received from the Queue Manager).\n\nWhen a WebSphere MQ Classes for Java/JMS application requested a\n remote connection it was matched for sharing with a connection\n that was still in the process of being established. The\n WebSphere MQ Client waited for the connection to complete and\n due to a small timing window began incorrectly sharing the\n connection without confirming the connection's suitability. If\n the connection's suitability had been checked then the\n connection\n would have been marked unsuitable due to the Negotiated Channel\n specifying that Conversation Sharing was disabled (SHARECNV=0 or\n SHARECNV=1).\n As the connection (which did not support conversation sharing)\n was now shared by two threads, packets destined for one thread\n were erroneously received by the other, this led to the client\n being in an inconsistent state and the two FDCs being generated.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q215", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The WebSphere MQ Classes for Java/JMS have been modified to\n correctly restrict conversation sharing when using a connection\n that does not support conversation sharing (SHARECNV=0 or\n SHARECNV=1).\n\nThe fix is targeted for delivery in the following PTFs:\n\nVersion Maintenance Level\n v7.0 7.0.1.12\n\nThe latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\nIf the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q215", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV47785\nREPORTED COMPONENT NAME\n WMQ HP V7\nREPORTED COMPONENT ID\n 5724H7222\nREPORTED RELEASE\n 701\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-09-02\nCLOSED DATE\n 2013-09-26\nLAST MODIFIED DATE\n 2014-01-13\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q215", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ HP V7\nFIXED COMPONENT ID\n 5724H7222", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q215", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R701 PSY\n UP", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q215", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "IBM WebSphere MQ server version 7.0 and later releases provide sharing conversations (SHARECNV) attribute on SVRCONN channel that specifies the maximum number of conversations that can share each TCP/IP channel instance. This feature can be configured in DataPower as it uses client connection with queue manager SVRCONN channel.\nThe default setting of sharing conversations (SHARECNV) value is zero in DataPower mq-qm object. The same default value for MQ SVRCONN channel is 10. The sharing conversations value is\nnegotiated between MQ server and DataPower and the lower value takes effect. However, in current versions of the DataPower firmware, the sharing conversations setting of 1 is treated as 0 when negotiating with MQ server.\n\nThere are three use cases to configure Sharing Conversations in DataPower mq-qm object:\n\nCase #1 : The negotiated sharing conversations value is 0 - The channel runs in a mode similar to WebSphere MQ V6 and does not uses features such as\n\n\u00b7 Administrator stop-quiesce\n\u00b7 Heartbeating\n\u00b7 Read ahead\n\u00b7 Client asynchronous consume\n\nSet a value of 0 or 1 on the Sharing Conversations attribute of the mq-qm object in DataPower to disable sharing conversations regardless of the IBM WebSphere MQ SVRCONN setting.\n\nCase #2: The negotiated sharing conversations value is 1 - The channel supports IBM WebSphere MQ V7 and later release features as outlined in case #1, but each TCP/IP channel instance has a single conversation.\n\nSet a value of 1 on the Sharing Conversations attribute and select \"on\" in Share Single Conversation attribute of the mq-qm object in DataPower as shown in the following picture and a value of 1 on IBM WebSphere MQ SVRCONN setting.\n\nThe Share Single Conversation attribute is only visible when \"Sharing Conversations\" is configured with value of \"1\" and then key is entered. For values greater than 1, the \"Share Single Conversation\" attribute is hidden in the mq-qm object.\n[/support/docview.wss?uid=swg21647231&aid=1] [/support/docview.wss?uid=swg21647231&aid=1]\n\nCase #3: The negotiated sharing conversations value is 2 or more - The channel supports IBM WebSphere MQ 7 and later release features and each TCP/IP channel instance supports 2 or more conversations.\n\nSet a value of 2 or more on the Sharing Conversations attribute of the mq-qm object in DataPower and on the MQ SVRCONN channel.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q215", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "On average, processing of messages from client applications is 15 percent slower when using SHARECNV(10) as compared to SHARECNV(0). Please refer to Performance Implications of Sharing [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.csqzaf.doc/mi12240_.htm]\nConversations on Client-connection Channels. [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.csqzaf.doc/mi12240_.htm].\n\nSince DataPower uses a connection pool in processing MQ messages, there are no additional benefits of using sharing conversations with the mq-qm object. However, in situations when mixed message sizes are used by the same mq-qm object, using case #2 will benefit mq-qm object as it will use new buffer management feature of IBM WebSphere MQ Version 7 when making MQGET API call.\n\nWhen using a negotiated shared conversations value of 0 as in case #1, mq-qm object uses maximum message size as the buffer pool for the MQGET API call. However, when mixed message sizes are processed by the same MQ Front Side Handler (FSH), it requests buffer pool based on maximum message size configured in the mq-qm object. The use of fixed buffer pool for small and large messages can deplete MQ server's allocated buffer and contribute to unexpected termination of MQ SVRCONN channel instance and may terminate the queue manager. In such a situation, using a negotiated sharing conversations value of 1 as in case #2 will benefit DataPower mq-qm object as it will use IBM WebSphere MQ Version 7 Read Ahead feature and the new buffer management feature for MQGET API call. IBM WebSphere MQ V8 release provides enhanced performance for case #2, when the negotiated sharing conversations value is 1.\n\nFor DataPower firmware releases 7.0.0.x, 7.1.0.x, 7.2.0.x and earlier, one should follow case #1 and use a negotiated sharing conversations value of 0. If you configure these firmware versions with case #2 or case #3, DataPower device may reload or hang due to connection instability and generate many MQ errors with Reason Code - 2009 and 2059.\n\nCases #2 and #3 can be used in firmware releases 7.5.0.x, 7.5.1.x and later. We suggest to use a value of 10 or less in Sharing Conversations attribute of the mq-qm object and verify the configuration empirically to make sure that IBM WebSphere MQ server can sustain load from DataPower with the negotiated Sharing Conversations of 10.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q215", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Note: In order to use sharing conversations, make sure you have applied APAR IV24821 [http://www.ibm.com/support/docview.wss?uid=swg1IV24821] (\"Client C application process hangs after cancelling thread\") to the IBM WebSphere MQ server. IV24821 is included in IBM WebSphere MQ V7.0.1.10 and later, IBM WebSphere MQ V7.1.0.3 and later, IBM WebSphere MQ V7.5.0.1 and later, and IBM WebSphere MQ V8.\n\nIn order to identify the negotiated Sharing Conversations status, the following MQ commands are used in the distributed platform.\n\nrunmqsc \ndisplay chs(CHANNEL3) maxshcnv curshcnv\n\ndisplay chs(CHANNEL3) maxshcnv curshcnv\n1 : display chs(CHANNEL3) maxshcnv curshcnv\nAMQ8417: Display Channel Status details.\nCHANNEL(CHANNEL3) CHLTYPE(SVRCONN)\nCONNAME(9.x1.x2.x3) CURRENT\nSTATUS(RUNNING) SUBSTATE(RECEIVE)\nCURSHCNV(1) MAXSHCNV(1) <---- Negotiated Sharing Conversations value of 1\nAMQ8417: Display Channel Status details.\nCHANNEL(CHANNEL3) CHLTYPE(SVRCONN)\nCONNAME(9.y1.y2.y31) CURRENT\nSTATUS(RUNNING) SUBSTATE(RECEIVE)\nCURSHCNV(0) MAXSHCNV(0) <---- Negotiated Sharing Conversations value of 0\n\nend\n\nIn order to identify the negotiated Sharing Conversations status, the following MQ commands are used in the z/OS System.\n\nconnect to \nOn z/OS system, options for issuing the commands are described at http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ref.adm.doc/q085120_.htm [http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ref.adm.doc/q085120_.htm].\n/+RTP8 DIS CHSTATUS(channel_name) MAXSHCNV CURSHCNV\nwhere \"+RTP8\" is the command prefix.\n\nz/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q215", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "You are running JOB CSQ45CTB with DB2 V12.\n JOB CSQ45CTB\n CREATE TYPE 2 INDEX CSQ.CLUS_INDEX\n ON CSQ.ADMIN_B_MESSAGES\n (BASEPART ASC)\n USING STOGROUP MQ2\n PRIQTY 16384\n SECQTY 16384\n CLUSTER\n (PART 1 VALUES(X'3FFF'),\n PART 2 VALUES(X'7FFF'),\n PART 3 VALUES(X'BFFF'),\n PART 4 VALUES(X'FFFF'))\n CLOSE NO\n SQL ERROR DURING EXECUTE IMMEDIATE\n DSNT408I SQLCODE = -876, ERROR: INDEX CANNOT BE CREATED OR\n ALTERED, REASON 6\n DSNT418I SQLSTATE = 53092 SQLSTATE RETURN CODE\n DSNT415I SQLERRP = DSNXICIX SQL PROCEDURE DETECTING ERROR\n DSNT416I SQLERRD = 77 0 0 -1 0 0 SQL DIAGNOSTIC\n INFORMATION\n DSNT416I SQLERRD = X'0000004D' X'00000000' X'00000000'\n X'FFFFFFFF' X'00000000' X'00000000' SQL DIAGNOSTIC\n INFORMATION\n .\n CREATE TYPE 2 INDEX CSQ.CLUS_INDEX, TYPE 2 incorrect syntax for\n CREATE INDEX at DB2 V12.\n .\n https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/sqlref\n /src/tpc/db2z_sql_createindex.html [https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/sqlref/src/tpc/db2z_sql_createindex.html]\n .\n\nJOB CSQ45CTB includes other references for \"CREATE TYPE 2 INDEX\"\n and \"CREATE TYPE 2 UNIQUE INDEX ...\" which complete without\n error. DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION\n .\n The only one with an error is\n CREATE TYPE 2 INDEX CSQ.CLUS_INDEX\n ON CSQ.ADMIN_B_MESSAGES\n .", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q215", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Changing PREVENT_NEW_IXCTRL_PART in macro DSN6SPRM to be \"NO\"\n should allow the Db2 indexes to be created.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q215", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of IBM MQ for z/OS Version 8 *\nRelease 0 Modification 0 using DB2 V12. *\n\nPROBLEM DESCRIPTION: Sample job CSQ45CTB to create DB2 *\ntables for a new QSG fails with message *\nDSNT408I SQLCODE = -876, ERROR: INDEX *\nCANNOT BE CREATED OR ALTERED, REASON 6 *\nSQLSTATE = 53092 when run against DB2 *\nV12. *\n\nIn DB2 V12 the PREVENT_NEW_IXCTRL_PART subsystem parameter has\n changed to a default value of YES which disallows the creation\n of new index-controlled partitioned tables. The sample JCL in\n CSQ45CTB attempts to create table CSQ.ADMIN_B_MESSAGES of this\n type, which leads to the error seen.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q215", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "New sample JCL, with prefix CSQ4X, is provided for use with DB2\n V12.\n\n The following pages in the IBM MQ 8.0.0 Knowledge Center are\n updated:\n IBM MQ\n Configuring\n Configuring queue managers on z/OS\n Customizing IBM MQ for z/OS\n Set up the Db2 environment\n\n https://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm\n .mq.con.doc/q019210_.htm [https://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.con.doc/q019210_.htm]\n\n IBM\u00ae MQ provides two equivalent sets of jobs. Those with the\n CSQ45 prefix are for compatibility with earlier versions of IBM\n MQ and for use with Db2 version 11 and earlier. If you are\n setting up a new data-sharing group with Db2 V12 or later, the\n jobs with CSQ4X prefix must be used. These jobs exploit more\n recent Db2 capabilities for dynamic sizing and Universal Table\n Spaces.\n\n 1. Customize and execute sample JCL CSQ45CSG (or CSQ4XCSG) to\n create the storage group that is to be used for the IBM MQ\n database, table spaces, and tables.\n 2. Customize and execute sample JCL CSQ45CDB (or CSQ4XCDB) to\n create the database to be used by all queue managers that are\n connecting to this Db2 data-sharing group.\n 3. Customize and execute sample JCL CSQ45CTS (or CSQ4XCTS) to\n create the table spaces that contain the queue manager and\n channel initiator tables used for queue-sharing groups (to be\n created in step 1 ).\n 4. Customize and execute sample JCL CSQ45CTB (or CSQ4XCTB) to\n create the 12 Db2 tables and associated indexes. Do not change\n any of the row names or attributes.\n\n In the event of a failure during Db2 setup, the following jobs\n can be customized and executed:\n CSQ45DTB to drop the tables and indexes.\n CSQ45DTS (or CSQ4XDTS) to drop the table spaces.\n CSQ45DDB (or CSQ4XDDB) to drop the database.\n CSQ45DSG (or CSQ4XDSG) to drop the storage group.\n\n IBM MQ\n Planning\n Planning your IBM MQ environment on z/OS\n Planning your Db2 environment\n\n https://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm\n .mq.pla.doc/q006030_.htm [https://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.pla.doc/q006030_.htm]\n\n IBM MQ provides sample jobs for defining the Db2 tablespaces,\n tables, and indexes. Two sets of sample jobs are provided:\n One for compatibility with earlier versions of IBM MQ\n (CSQ45CDB,CSQ45CSG,CSQ45CTB & CSQ45CTS)\n One for use with Db2 V12 and later, which exploits\n Universal Table Spaces (UTS) (CSQ4XCDB,CSQ4XCSG,\n CSQ4XCTB & CSQ4XCTS)\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q215", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI95423\nREPORTED COMPONENT NAME\n IBM MQ Z/OS V8\nREPORTED COMPONENT ID\n 5655W9700\nREPORTED RELEASE\n 000\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2018-03-20\nCLOSED DATE\n 2018-03-29\nLAST MODIFIED DATE\n 2018-05-01\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n PI88274 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI88274]\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n UI54835\n\nMODULES/MACROS\nCSQ4XCDB CSQ4XCSG CSQ4XCTB CSQ4XCTS CSQ4XDDB CSQ4XDSG CSQ4XDTS", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q215", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n IBM MQ Z/OS V8\nFIXED COMPONENT ID\n 5655W9700", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q215", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R000 PSY UI54835 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI54835]\n UP18/04/24 P F804\n\nFIX IS AVAILABLE\nSELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL. YOU WILL BE REQUIRED TO SIGN IN. DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q215", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Clarifications are needed in the manuals for the sequence of\n security exit calls in a channel instance sharing conversations.", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q215", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n Users with security exits defined in client channels that will\n use sharing conversations.\n\nPlatforms affected:\n All Distributed (iSeries, all Unix and Windows)\n\nPROBLEM SUMMARY:\n When a client channel instance is shared by more than one\n conversation, the pattern of calls to the security exit is\n restricted on the second and subsequent conversations.\n\nThese restrictions should be documented in the WebSphere MQ\n product manuals.", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q215", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The following description will be added to the\n Intercommunication manual on the page that describes Channel\n security exit programs.\n\nWhen a client channel instance is shared by more than one\n conversation, the pattern of calls to the security exit is\n restricted on the second and subsequent conversations.\n\nFor the first conversation, the pattern is the same as if the\n channel were not sharing conversations. For the second and\n subsequent conversations, the security exit is never called with\n MQXR_INIT, MQXR_INIT_SEC, or MQXR_SEC_MSG. It is called with\n MQXR_SEC_PARMS.\n\nIn a channel that is sharing conversations, MQXR_TERM is called\n only for the last conversation running.\n\nEach conversation has the opportunity in the MQXR_SEC_PARMS\n invocation of the exit to alter the MQCD; on the\n server-connection end of the channel this can be useful to vary,\n for example, the MCAUserIdentifier or LongMCAUserIdPtr values\n before the connection is made to the queue manager.\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q215", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IZ33379\nREPORTED COMPONENT NAME\n WMQ AIX V7\nREPORTED COMPONENT ID\n 5724H7221\nREPORTED RELEASE\n 700\nSTATUS\n CLOSED DOC\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2008-09-25\nCLOSED DATE\n 2008-10-31\nLAST MODIFIED DATE\n 2008-10-31\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q215", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Fix packs for DataPower Gateway version 7.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24038524]\nFix packs for DataPower Gateway version 7.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24041543]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q215", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Unexpected appliance restart may occur during MQ traffic with MQ\n Sharing Conversation.", "logical_doc_id": 5, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q215", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Affected is use of MQ Sharing Conversation.\n\nCustomers who use MQ Sharing Conversation get high CPU.", "logical_doc_id": 5, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q215", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fix is available in 7.1.0.7\n\nFor a list of the latest fix packs available, please see:\n http://www-01.ibm.com/support/docview.wss?uid=swg21237631 [http://www-01.ibm.com/support/docview.wss?uid=swg21237631]\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q215", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT10498\nREPORTED COMPONENT NAME\n DATAPOWER\nREPORTED COMPONENT ID\n DP1234567\nREPORTED RELEASE\n 710\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2015-08-10\nCLOSED DATE\n 2015-10-19\nLAST MODIFIED DATE\n 2015-11-06\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q215", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n DATAPOWER\nFIXED COMPONENT ID\n DP1234567", "logical_doc_id": 5, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q215", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R710 PSY\n UP", "logical_doc_id": 5, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q249", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Jazz Team Server is shipped as a component of Jazz Reporting Service (JRS). Information about multiple security vulnerabilities affecting Jazz Team Server and Jazz-based products has been published in a security bulletin.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q249", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID:CVE-2017-3511 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3511]\nDESCRIPTION:An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit JCE component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 7.7\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/124890 [https://exchange.xforce.ibmcloud.com/vulnerabilities/124890]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H)\n\nCVEID:CVE-2016-9840 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9840]\nDESCRIPTION:zlib is vulnerable to a denial of service, caused by an out-of-bounds pointer arithmetic in inftrees.c. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/120508 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120508]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L)\n\nCVEID:CVE-2016-9841 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9841]\nDESCRIPTION:zlib is vulnerable to a denial of service, caused by an out-of-bounds pointer arithmetic in inftrees.c. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/120509 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120509]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L)\n\nCVEID:CVE-2016-9842 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9842]\nDESCRIPTION:zlib is vulnerable to a denial of service, caused by an undefined left shift of negative number. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/120510 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120510]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L)\n\nCVEID:CVE-2016-9843 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9843]\nDESCRIPTION:zlib is vulnerable to a denial of service, caused by a big-endian out-of-bounds pointer. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/120511 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120511]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q249", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Principal Product and Version(s) Affected Supporting Product(s) and Version(s) JRS 5.0, 5.0.1, 5.0.2 Jazz Foundation 5.0, 5.0.1, 5.0.2 JRS 6.0, 6.0.1, 6.0.2, 6.0.3 Jazz Foundation 6.0, 6.0.1, 6.0.2, 6.0.3 * Both JRS and Jazz Foundation are part of Rational Collaborative Lifecycle Management. REMEDIATION/FIXES\nConsult the security bulletin Security Bulletin: Vulnerability in IBM\u00ae Java SDK affects multiple IBM Rational products based on IBM Jazz technology [http://www-01.ibm.com/support/docview.wss?uid=swg22004599] for vulnerability details and information about fixes.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q249", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q249", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q249", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 22 June 2017: Initial Publication\nThe 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.", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q249", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "OpenSSL\u306e\u8106\u5f31\u6027\u306fOpenSSL Project\u306b\u3088\u3063\u30662015\u5e743\u670819\u65e5\u306b\u958b\u793a\u3055\u308c\u307e\u3057\u305f\u3002 OpenSSL\u306f\u3001IBM WebSphere MQ Advanced Message Security for the IBM i\u30d7\u30e9\u30c3\u30c8\u30d5\u30a9\u30fc\u30e0\u3001 IBM WebSphere MQ HP-NSS\u3068IBM WebSphere MQ Paho MQTT \u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u3067\u4f7f\u7528\u3055\u308c\u307e\u3059\u3002\nIBM WebSphere MQ Advanced Message Security for the IBM i \u3068IBM WebSphere MQ HP-NSS \u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u306f\u3001\u8a72\u5f53\u306eCVE\u306b\u5bfe\u51e6\u3057\u307e\u3057\u305f\u3002", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q249", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "\u8106\u5f31\u6027\u306e\u8a73\u7d30\uff1a\n\nCVEID: CVE-2015-0209 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0209]\nDESCRIPTION: OpenSSL could allow a remote attacker to execute arbitrary code on the system, caused by a use-after-free error in the d2i_ECPrivateKey or EVP_PKCS82PKEY function. An attacker could exploit this vulnerability to corrupt memory and execute arbitrary code on the system and cause a denial of service.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101674 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101674] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:P/A:P)\n\nCVEID: CVE-2015-0286 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0286]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an error in the ASN1_TYPE_cmp function when attempting to compare ASN.1 boolean types. An attacker could exploit this vulnerability to crash any certificate verification operation and cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101666 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101666] 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-0289 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0289]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by the failure to properly handle missing outer ContentInfo by the PKCS#7 parsing code. An attacker could exploit this vulnerability using a malformed ASN.1-encoded PKCS#7 blob to trigger a NULL pointer dereference.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101669 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101669] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q249", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "\u5f71\u97ff\u306e\u3042\u308b\u88fd\u54c1\u30fb\u30d0\u30fc\u30b8\u30e7\u30f3\uff1a\n\n\u6b21\u306e\u88fd\u54c1\u306b\u5f71\u97ff\u304c\u3042\u308a\u307e\u3059\u3002\n\n\u30fbIBM WebSphere MQ Advanced Message Security for IBM i platform - V8.0.0.2 \u672a\u6e80\u306e\u30ea\u30ea\u30fc \u30b9\n\n\u30fbIBM WebSphere MQ Client for HP Integrity NonStop Server - V8.0.0.2 \u672a\u6e80\u306e\u30ea\u30ea\u30fc \u30b9\n\n\u30fbIBM Mobile Messaging and M2M Client Pack - Eclipse Paho MQTT C Client libraries for Linux & Windows platforms only", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q249", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "\u4fee\u6b63\u7b56\uff1a\n\nIBM WebSphere MQ Advanced Message Security for IBM i platform\n\nFix Pack 8.0.0.3 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.2&platform=IBM+i&function=all] \u4ee5\u964d\u3092\u5c0e\u5165\u3057\u3066\u304f\u3060\u3055\u3044\u3002\n\nIBM WebSphere MQ HP-NSS client\n\nFix Pack 8.0.0.3 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.2&platform=HP+NonStop&function=all] \u4ee5\u964d\u3092\u5c0e\u5165\u3057\u3066\u304f\u3060\u3055\u3044\u3002", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q249", "section_id": 4, "heading": "WORKAROUNDS AND MITIGATIONS", "parent": null, "text": "\u56de\u907f\u7b56/\u8efd\u6e1b\u7b56\uff1a\n\nEclipse Paho MQTT C Client (Linux & Windows)\nMA9B\u30b5\u30dd\u30fc\u30c8\u30d1\u30c3\u30af MA9B \u304c\u63d0\u4f9b\u3059\u308bC\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u30e9\u30a4\u30d6\u30e9\u30ea\u306f\u3001\u30bd\u30fc\u30b9\u304b\u3089\u30ea\u30d3\u30eb\u30c9\u3068OpenSSL 1.0.1.m \u4ee5\u964d\u306b\u30ea\u30f3\u30af\u3067\u304d\u307e\u3059\u3002\u624b\u9806\u306f\u3001instructions [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mm.tc.doc/tc10155_.htm]\u3092\u53c2\u7167\u304f\u3060\u3055\u3044\u3002", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q249", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q249", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\n. \u53c2\u7167\u60c5\u5831\uff1a\n\nOpenSSL Project vulnerability website [http://www.openssl.org/news/vulnerabilities.html] (for detail on what versions are affected)\n\nOpenSSL Advisory on above listed CVEs [https://www.openssl.org/news/secadv_20150319.txt]\n\n[IBM\u30b5\u30a4\u30c8]\n\u3053\u306e\u6587\u66f8\u306f\u3001\u7c73\u56fd IBM \u793e\u306e\u8cc7\u6599\u3092\u7ffb\u8a33\u3057\u305f\u53c2\u8003\u6587\u66f8\u3067\u3059\u3002\u7ffb\u8a33\u5143\u306e\u6587\u66f8\u306f\u3001\u4ee5\u4e0b\u306e\u30ea\u30f3\u30af\u3088\u308a\u3054\u53c2\u7167\u304f\u3060\u3055\u3044\u3002\nSecurity Bulletin: Vulnerabilities in OpenSSL affect IBM WebSphere MQ Advanced Message Security for IBM i, IBM WebSphere MQ Client for HP-NSS [http://www.ibm.com/support/docview.wss?uid=swg21902519]\n\n\u516c\u958b\u6e08\u307f\u306e\u30d5\u30a3\u30c3\u30af\u30b9\u30d1\u30c3\u30af\u306b\u3064\u3044\u3066\u306f\u3001\u4ee5\u4e0b\u306e\u30b5\u30a4\u30c8\u3088\u308a\u3054\u5229\u7528\u3044\u305f\u3060\u3051\u307e\u3059\u3002\nRecommended fixes for WebSphere MQ [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\n\u30d5\u30a3\u30c3\u30af\u30b9\u30fb\u30d1\u30c3\u30af\u306e\u516c\u958b\u4e88\u5b9a\u306b\u3064\u3044\u3066\u306f\u3001\u4ee5\u4e0b\u306e\u30b5\u30a4\u30c8\u3088\u308a\u3054\u78ba\u8a8d\u3044\u305f\u3060\u3051\u307e\u3059\u3002\nWebSphere MQ planned maintenance release dates [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n[CVSS\u60c5\u5831]\n\u72ec\u7acb\u884c\u653f\u6cd5\u4eba \u60c5\u5831\u51e6\u7406\u63a8\u9032\u6a5f\u69cb: \u5171\u901a\u8106\u5f31\u6027\u8a55\u4fa1\u30b7\u30b9\u30c6\u30e0CVSS\u6982\u8aac [http://www.ipa.go.jp/security/vuln/CVSS.html]\nJVN iPedia: CVSS\u8a08\u7b97\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u65e5\u672c\u8a9e\u7248 [http://jvndb.jvn.jp/cvss/ja.html]", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q249", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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] . \u95a2\u9023\u60c5\u5831\uff1a\n.\n[\u304a\u554f\u5408\u305b\u5148]\n\u6280\u8853\u7684\u306a\u5185\u5bb9\u306b\u95a2\u3057\u3066\u3001\u30b5\u30fc\u30d3\u30b9\u5951\u7d04\u306e\u3042\u308b\u304a\u5ba2\u69d8\u306fIBM\u30b5\u30fc\u30d3\u30b9\u30fb\u30e9\u30a4\u30f3\u306b\u304a\u554f\u3044\u5408\u308f\u305b\u304f\u3060\u3055\u3044\u3002\nIBM \u30b5\u30fc\u30d3\u30b9\u30fb\u30e9\u30a4\u30f3 [http://www.ibm.com/jp/news/20070420001.html]\nThe 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\u95a2\u9023\u60c5\u5831\n An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21902519]", "logical_doc_id": 1, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q249", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "An administration command can cause IBM MQ to access an invalid memory address, leading to a segmentation failure and causing the queue manager to become unresponsive.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q249", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-8971 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8971]\nDESCRIPTION: IBM MQ could allow an authenticated user with queue manager permissions to cause a segmentation fault. This would result in the machine needing to be rebooted to resume normal operations.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118862 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118862] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H)", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q249", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM MQ V9.0 Long Term Support Release\n\nIBM MQ V9.0.0.0 only.\n\nIBM MQ V8.0\n\nIBM MQ V8.0.0.0 - V8.0.0.5 maintenance levels.", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q249", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "IBM MQ V9.0 Long Term Support Release\n\nApply 9.0.0.1 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=9.0.0.1&platform=All&function=all&useReleaseAsTarget=true] maintenance level.\n\nIBM MQ V8.0\n\nApply 8.0.0.6 [http://www-01.ibm.com/support/docview.wss?uid=swg21995100] maintenance level.", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q249", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 2, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q249", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 2, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q249", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 20 February 2017: Original version published.\n23 February 2017: Minor corrections to wording.\n21 June 2017: Add 9.0 LTS applicability\nThe 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.", "logical_doc_id": 2, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q249", "section_id": 8, "heading": "RELATED INFORMATION", "parent": null, "text": "A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21999232]", "logical_doc_id": 2, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q249", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "zlib is vulnerable to a denial of service, caused by an out-of-bounds pointer arithmetic in inftrees.c. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q249", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVE IDs: CVE-2016-9840 CVE-2016-9841 CVE-2016-9842 CVE-2016-9843\nCVEID:CVE-2016-9840 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9840]\nDESCRIPTION:zlib is vulnerable to a denial of service, caused by an out-of-bounds pointer arithmetic in inftrees.c. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/120508 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120508]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L)\n\nCVEID:CVE-2016-9841 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9841]\nDESCRIPTION:zlib is vulnerable to a denial of service, caused by an out-of-bounds pointer arithmetic in inftrees.c. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/120509 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120509]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L)\n\nCVEID:CVE-2016-9842 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9842]\nDESCRIPTION:zlib is vulnerable to a denial of service, caused by an undefined left shift of negative number. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/120510 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120510]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L)\n\nCVEID:CVE-2016-9843 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9843]\nDESCRIPTION:zlib is vulnerable to a denial of service, caused by a big-endian out-of-bounds pointer. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/120511 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120511]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L)", "logical_doc_id": 3, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q249", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM SPSS Analytic Server 2.0.1.0\nIBM SPSS Analytic Server 2.0.0.0", "logical_doc_id": 3, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q249", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "The fixes for these vulnerabilities are included in IBM SDK, Java Technology Edition, Version 7R1 Service Refresh 3 Fix Pack 50 and subsequent releases.", "logical_doc_id": 3, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q249", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 3, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q249", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 3, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q249", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nThe 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.", "logical_doc_id": 3, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q249", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There is a potential bypass security restriction vulnerability in IBM WebSphere Application Server. This will only occur in environments that have the webcontainer custom property HttpSessionIdReuse enabled. There is a potential denial of service with IBM WebSphere Application Server when using SIP services. IBM WebSphere Application Server Liberty could allow a remote attacker to conduct phishing attacks, caused by an open redirect vulnerability. An attacker could exploit this vulnerability to redirect a victim to arbitrary Web sites. IBM WebSphere Application Server Liberty is vulnerable to cross-site scripting in OpenID Connect clients caused by improper validation of input. A remote attacker could exploit this vulnerability using a specially-crafted URL to execute script in a victim's Web browser within the security context of the hosting Web site, once the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials. There is an Information Disclosure Vulnerability in IBM WebSphere Application Server Liberty. Apache Commons Fileupload vulnerability affects WebSphere Application Server. There is a potential information disclosure in WebSphere Application Server.", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q249", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-0385 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0385]\nDESCRIPTION: IBM WebSphere Application Server could allow a remote attacker to bypass security restrictions caused by a buffer overflow. This could allow the attacker to view unauthorized data.\nCVSS Base Score: 3.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112359 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112359] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N)\n\nCVEID: CVE-2016-2960 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2960]\nDESCRIPTION: IBM WebSphere Application Server could be vulnerable to a denial of service when using SIP services. A remote attacker could cause a denial of service with specially-crafted SIP messages.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113805 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113805] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L)\n\nCVEID: CVE-2016-3040 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3040]\nDESCRIPTION: IBM WebSphere Application Server Liberty could allow a remote attacker to conduct phishing attacks, caused by an open redirect vulnerability. An attacker could exploit this vulnerability to redirect a victim to arbitrary Web sites.\nCVSS Base Score: 6.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/114636 [https://exchange.xforce.ibmcloud.com/vulnerabilities/114636] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N)\n\nCVEID: CVE-2016-3042 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3042]\nDESCRIPTION: IBM WebSphere Application Server - Liberty is vulnerable to cross-site scripting in OpenID Connect clients. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.\nCVSS Base Score: 5.4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/114638 [https://exchange.xforce.ibmcloud.com/vulnerabilities/114638] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N)\n\nCVEID: CVE-2016-0378 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0378]\nDESCRIPTION: IBM WebSphere Application Server Liberty could allow a remote attacker to obtain sensitive information caused by improper handling of exceptions when a default error page does not exist.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112240 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112240] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\nCVEID: CVE-2016-3092 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092]\nDESCRIPTION: Apache Tomcat is vulnerable to a denial of service, caused by an error in the Apache Commons FileUpload component. By sending file upload requests, an attacker could exploit this vulnerability to cause the server to become unresponsive.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/114336 [https://exchange.xforce.ibmcloud.com/vulnerabilities/114336] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)", "logical_doc_id": 4, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q249", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-5986 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5986]\nDESCRIPTION: IBM WebSphere Application Server and IBM WebSphere Application Server Liberty could allow a remote attacker to obtain sensitive information, caused by the improper handling of responses under certain conditions. An attacker could exploit this vulnerability to gain server identification information.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116556 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116556] 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)", "logical_doc_id": 4, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q249", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "This vulnerability affects all versions of Liberty for Java in IBM Bluemix up to and including v3.2.", "logical_doc_id": 4, "chunk_id": 32 }, { "doc_id": "techqa_DEV_Q249", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "To upgrade to Liberty for Java v3.3-20160912-1729 or higher, you must re-stage or re-push your application. To check which version of the Liberty for Java runtime your Bluemix application is using, navigate to the \"Files\" menu item for your application through the Bluemix UI. In the \"logs\" directory, check the \"staging_task.log\".\n\nYou can also find this file through the command-line Cloud Foundry client by running the following command:\n\ncf files logs/staging_task.log\n\nYou can see\n----> Liberty Buildpack Version: _________\n\nTo re-stage your application using the command-line Cloud Foundry client, use the following command:\n\ncf restage \n\nTo re-push your application using the command-line Cloud Foundry client, use the following command:\n\ncf push ", "logical_doc_id": 4, "chunk_id": 33 }, { "doc_id": "techqa_DEV_Q249", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 4, "chunk_id": 34 }, { "doc_id": "techqa_DEV_Q249", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] CHANGE HISTORY\n 16 September 2016: original document published\nThe 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.", "logical_doc_id": 4, "chunk_id": 35 }, { "doc_id": "techqa_DEV_Q250", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "OpenSSL vulnerabilities were disclosed on December 7, 2017 by the OpenSSL Project. OpenSSL is used by IBM SDK for Node.js. IBM SDK for Node.js has addressed the applicable CVEs.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q250", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID:CVE-2017-3737 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3737]\nDESCRIPTION:OpenSSL could allow a remote attacker to bypass security restrictions, caused by a flaw in the \\\"error state\\\" mechanism when directly calling SSL_read() or SSL_write() for an SSL object after receiving a fatal error. An attacker could exploit this vulnerability to bypass the decryption or encryption process and perform unauthorized actions.\nCVSS Base Score: 5.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/136077 [https://exchange.xforce.ibmcloud.com/vulnerabilities/136077]for more information\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)\n\nCVEID: CVE-2017-3738 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3738]\nDESCRIPTION:OpenSSL could allow a remote attacker to obtain sensitive information, caused by an overflow bug in the AVX2 Montgomery multiplication procedure used in exponentiation with 1024-bit moduli. An attacker could exploit this vulnerability to obtain information about the private key. Note: In order to exploit this vulnerability, the server would have to share the DH1024 private key among multiple clients, which is no longer an option since CVE-2016-0701.\nCVSS Base Score: 3.1\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/136078 [https://exchange.xforce.ibmcloud.com/vulnerabilities/136078]for more information\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q250", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "These vulnerabilities affect IBM SDK for Node.js v4.8.6.0 and earlier releases.\nThese vulnerabilities affect IBM SDK for Node.js v6.12.0.0 and earlier releases.\nThese vulnerabilities affect IBM SDK for Node.js v8.9.0.0 and earlier releases.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q250", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "The fixes for these vulnerabilities are included in IBM SDK for Node.js v4.8.7.0 and subsequent releases.\nThe fixes for these vulnerabilities are included in IBM SDK for Node.js v6.12.2.0 and subsequent releases.\nThe fixes for these vulnerabilities are included in IBM SDK for Node.js v8.9.3.0 and subsequent releases.\n\nIBM SDK for Node.js can be downloaded, subject to the terms of the developerWorks license, fromhere [http://www.ibm.com/developerworks/web/nodesdk/].\n\nIBM customers requiring an update for an SDK shipped with an IBM product should contactIBM support [http://www.ibm.com/support/], and/or refer to the appropriate product security bulletin.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q250", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q250", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q250", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nNode.js 4.8.7 [https://nodejs.org/en/blog/release/v4.8.7/] Node.js 6.12.2 [https://nodejs.org/en/blog/release/v6.12.2/]\n\nNode.js 8.9.3 [https://nodejs.org/en/blog/release/v8.9.3/]\n\nCHANGE HISTORY\n December 22 2017: Original version published\nJanuary 30 2018: Corrected CVSS reference\nThe 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.", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q250", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "This bulletin describes CVE-2015-3197 that was reported on January 26, 2015 by the OpenSSL Project, plus two additional vulnerabilities.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q250", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID:CVE-2015-3197 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3197]\nDESCRIPTION:OpenSSL could allow a remote attacker to conduct man-in-the-middle attacks, caused by the use of weak Diffie-Hellman parameters based on unsafe primes that are generated and stored in X9.42-style parameter files. By performing multiple handshakes using the same private DH exponent, an attacker could exploit this vulnerability to conduct man-in-the-middle attacks.\nCVSS Base Score: 5.4\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/110235 [https://exchange.xforce.ibmcloud.com/vulnerabilities/110235] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N)\n\nCVE-ID: CVE-2016-2086 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2086]\nDESCRIPTION: Node.js is vulnerable to HTTP request smuggling, caused by the improper handling of the Content-Length header. A remote attacker could send a specially-crafted request in a malformed chunked header to the Web server to cause multiple processing conflicts on the servers. An attacker could exploit this vulnerability to poison the web cache, bypass web application firewall protection, and conduct XSS attacks.\nCVSS Base Score: 6.100\nCVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/110530 [https://exchange.xforce.ibmcloud.com/vulnerabilities/110530] for more information\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N)\n\nCVE-ID: CVE-2016-2216 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2216]\nDESCRIPTION: Node.js is vulnerable to HTTP response splitting attacks, caused by improper validation of user-supplied input when processing malicious requests. A remote attacker could exploit this vulnerability to inject arbitrary HTTP headers containing unicode charactesr and cause the server to return a split response, once the URL is clicked. This would allow the attacker to perform further attacks, such as Web cache poisoning or cross-site scripting, and possibly obtain sensitive information.\nCVSS Base Score: 6.100\nCVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/110529 [https://exchange.xforce.ibmcloud.com/vulnerabilities/110529] for more information\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N)", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q250", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "These vulnerabilities affect IBM SDK for Node.js v1.1.0.18 and earlier releases.\n\nThese vulnerabilities affect IBM SDK for Node.js v1.2.0.8 and earlier releases.\nA subset of these vulnerabilities affect IBM SDK for Node.js v4.2.6.0 and earlier releases. See Remediation/Fixes section for details.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q250", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "CVE ID Fixed IBM SDK for Node.js releases 1.1.x 1.2.x 4.x CVE-2015-3197 1.1.0.19 1.2.0.9 N/A CVE-2016-2086 1.1.0.19 1.2.0.9 4.3.0.0 CVE-2016-2216 1.1.0.19 1.2.0.9 4.3.0.0\nIBM SDK for Node.js can be downloaded, subject to the terms of the developerWorks license, from here [http://www.ibm.com/developerworks/web/nodesdk/].\n\nIBM customers requiring an update for an SDK shipped with an IBM product should contact IBM support [http://www.ibm.com/support/], and/or refer to the appropriate product security bulletin. WORKAROUNDS AND MITIGATIONS\nCVE-2015-3197 only applies to IBM SDK for Node.js v1.1.x and 1.2.x if the --enable-ssl2 command line argument is being used. This option is not enabled by default.", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q250", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q250", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] Node.js 0.10.42 [https://nodejs.org/en/blog/release/v0.10.42/]\nNode.js 0.12.10 [https://nodejs.org/en/blog/release/v0.12.10/]\nNode.js 4.3.0 [https://nodejs.org/en/blog/release/v4.3.0/]\nNode.js February 2016 Security Release [https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/] CHANGE HISTORY\n February 16 2016: Original version published\nThe 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.", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q250", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "OpenSSL vulnerabilities were disclosed on November 2, 2017 by the OpenSSL Project. OpenSSL is used by IBM SDK for Node.js. IBM SDK for Node.js has addressed the applicable CVEs.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q250", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID:CVE-2017-3735 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3735]\nDescription:OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAdressFamily extension in an X.509 certificate. An attacker could exploit this vulnerability to trigger an out-of-bounds read, resulting in an incorrect text display of the certificate.\nCVSS Base Score: 4.3\nCVSS Temporal Score:https://exchange.xforce.ibmcloud.com/vulnerabilities/131047 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131047] for more information\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N)\n\nCVEID: CVE-2017-3736 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3736]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by a carry propagation flaw in the the x86_64 Montgomery squaring function bn_sqrx8x_internal(). An attacker with online access to an unpatched system could exploit this vulnerability to obtain information about the private key.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/134397 [https://exchange.xforce.ibmcloud.com/vulnerabilities/134397] for more information\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N)", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q250", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "These vulnerabilities affect IBM SDK for Node.js v4.8.5.0 and earlier releases.\nThese vulnerabilities affect IBM SDK for Node.js v6.11.5.0 and earlier releases.\nThese vulnerabilities affect IBM SDK for Node.js v8.9.0.0 and earlier releases.", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q250", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "The fixes for these vulnerabilities are included in IBM SDK for Node.js v4.8.6.0 and subsequent releases.\nThe fixes for these vulnerabilities are included in IBM SDK for Node.js v6.12.0.0 and subsequent releases.\nThe fixes for these vulnerabilities are included in IBM SDK for Node.js v8.9.3.0 and subsequent releases.\n\nIBM SDK for Node.js can be downloaded, subject to the terms of the developerWorks license, fromhere [http://www.ibm.com/developerworks/web/nodesdk/].\n\nIBM customers requiring an update for an SDK shipped with an IBM product should contactIBM support [http://www.ibm.com/support/], and/or refer to the appropriate product security bulletin.", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q250", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q250", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 2, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q250", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nNode.js 4.8.6 [https://nodejs.org/en/blog/release/v4.8.6/] Node.js 6.12.0 [https://nodejs.org/en/blog/release/v6.12.0/]\n\nNode.js 8.9.1 [https://nodejs.org/en/blog/release/v8.9.1/]\n\nCHANGE HISTORY\n December 22 2017: Original version published\nThe 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.", "logical_doc_id": 2, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q250", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Vulnerabilities in .NET Core, ASP.NET Core Could Allow Elevation of Privilege. Vulnerabilities in Node.js and the c-ares library were disclosed on July 11 2017 by the Node.js Foundation. IBM SDK for Node.js has addressed the applicable CVEs.", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q250", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2017-0256 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0256]\nDESCRIPTION: Microsoft ASP.NET Core could allow a remote attacker to conduct spoofing attacks, caused by improper validation of user supplied input.\nCVSS Base Score: 6.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/125327 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125327] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N)\n\nCVEID: CVE-2017-0249 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0249]\nDESCRIPTION: Microsoft ASP.NET Core could allow a remote attacker to gain elevated privileges on the system, caused by improper validation of user supplied input.\nCVSS Base Score: 8.4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/125299 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125299] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)\n\nCVEID: CVE-2017-0247 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0247]\nDESCRIPTION: Microsoft ASP.NET Core is vulnerable to a denial of service, caused by improper validation of web requests in the TextEncoder.EncodeCore function. By inserting specially-crafted content into any system using the function to encode content, a remote attacker could exploit this vulnerability to prevent any page delivering the content from loading.\nCVSS Base Score: 3.6\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/125297 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125297] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:L)\n\nCVEID: CVE-2017-1000381 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000381]\nDESCRIPTION: c-ares could allow a remote attacker to obtain sensitive information, caused by an out-of-bounds read in the ares_parse_naptr_reply() function when parsing NAPTR responses. By sending specially crafted DNS response packet, an attacker could exploit this vulnerability to read memory outside of the given input buffer and cause a denial of service.\nCVSS Base Score: 6.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/128625 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128625] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L)\n\nCVEID: CVE-2017-11499 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11499]\nDESCRIPTION: Node.js is vulnerable to a denial of service, caused by a flaw related to constant HashTable seeds. A remote attacker could exploit this vulnerability to flood the hash and cause a denial of service.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/129465 [https://exchange.xforce.ibmcloud.com/vulnerabilities/129465] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q250", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "These vulnerabilities affect ASP.NET Core in IBM Bluemix v1.0.20 and earlier releases.\n\nYou can also find this file through the command-line Cloud Foundry client by running the following command:\n\ncf ssh -c cat staging_info.yml\n\nLook for the following lines:\n{\"detected_buildpack\":\"ASP.NET Core (buildpack-v1.xxx)\",\"start_command\":\"cd . \\u0026\\u0026 dotnet dotnetstarter.dll --server.urls http://0.0.0.0:${PORT}\" [http://0.0.0.0:$%7Bport%7D'/]}\n\nIf the buildpack version is not at least v1.0.22 your application may be vulnerable.", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q250", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "You will need to restage (or re-push) your application using the ASP.NET Core Buildpack v1.0.22.", "logical_doc_id": 3, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q250", "section_id": 4, "heading": "WORKAROUNDS AND MITIGATIONS", "parent": null, "text": "None.\n\nADDITIONAL BLUEMIX ALERT INFORMATION\nMonitor the Bluemix console (https://console.ng.bluemix.net/status/ [https://console.ng.bluemix.net/status/]) for additional important product alerts.", "logical_doc_id": 3, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q250", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 3, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q250", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n August 17 2017: Original version published\nThe 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\nnode.js; nodejs; vulnerable; vulnerability; cordova SECURITY BULLETIN", "logical_doc_id": 3, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q250", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Portions of IBM Rational Application Developer for WebSphere Software are shipped as a component of Rational Developer for i (RPG and COBOL + Modernization Tools, Java and EGL editions), and Rational Developer for AIX and Linux. Information about a security vulnerability affecting Rational Application Developer has been published in a security bulletin.", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q250", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Subscribe to My Notifications to be notified of important product support alerts like this. * Follow this link [https://www.ibm.com/systems/support/myview/subscription/css.wss/subscriptions?methodName=startSearchToSubscribe&uctug_rational_dcfsbblurb_2013-11-05_myn_adoption_promo] for more information (requires login with your IBM ID)\n\nReview Security Bulletin: Multiple vulnerabilities affecting the IBM SDK for Node.js used by the Cordova platform packaged with Rational Application Developer (CVE-2014-3508 CVE-2014-5139 CVE-2014-3509 CVE-2014-3505 CVE-2014-3506 CVE-2014-3507 CVE-2014-3510 CVE-2014-3511 CVE-2014-3512 CVE-2014-5256) [http://www.ibm.com/support/docview.wss?uid=swg21685467] for vulnerability details. AFFECTED PRODUCTS AND VERSIONS\n\nAffected Product and Version(s) Product and Version shipped as a component IBM Rational Developer for i v9.1, RPG and COBOL + Modernization Tools, Java Edition Rational Application Developer 9.1 IBM Rational Developer for i v9.1, RPG and COBOL + Modernization Tools, EGL Edition Rational Application Developer 9.1 IBM Rational Developer for AIX and Linux v9.1, AIX COBOL Edition Rational Application Developer 9.1 IBM Rational Developer for AIX and Linux v9.1, C/C++ Edition Rational Application Developer 9.1 REMEDIATION/FIXES\nReview the Remediation/Fixes section of Security Bulletin: Multiple vulnerabilities affecting the IBM SDK for Node.js used by the Cordova platform packaged with Rational Application Developer (CVE-2014-3508 CVE-2014-5139 CVE-2014-3509 CVE-2014-3505 CVE-2014-3506 CVE-2014-3507 CVE-2014-3510 CVE-2014-3511 CVE-2014-3512 CVE-2014-5256) [http://www.ibm.com/support/docview.wss?uid=swg21685467] for instructions on obtaining the fix for this issue.", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q250", "section_id": 3, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q250", "section_id": 4, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] OpenSSL Project vulnerability website [http://www.openssl.org/news/vulnerabilities.html] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] ACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n21 October 2014: Original copy published\nThe 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\nCross reference information Segment Product Component Platform Version Edition Software Development Rational Developer for AIX and Linux", "logical_doc_id": 4, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q129", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition Version 6 and 7 that are used by IBM OS Images for Red Hat Linux Systems and AIX. These issues were disclosed as part of the IBM Java SDK updates in January 2015.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q129", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2015-0410 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0410]\nDESCRIPTION: An unspecified vulnerability related to the Security component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100151 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100151] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)\n\nCVEID: CVE-2014-6593 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6593]\nDESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100153 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100153] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q129", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM OS Image for Red Hat Linux Systems 2.0.0.1 and earlier.\nIBM OS Image for AIX 2.0.0.1 and earlier.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q129", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "The deployed Red Hat Linux-based and AIX virtual machines on IBM PureApplication Systems types are affected. The solution is to apply the following IBM PureApplication System fix to the deployed virtual machines.\n\nJava Update for Linux\nhttp://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=+Java_Update_Linux_2++&includeSupersedes=0 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=+Java_Update_Linux_2++&includeSupersedes=0]\n\nJava Update for AIX\nhttp://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=+Java_Update_AIX_2++&includeSupersedes=0 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=+Java_Update_AIX_2++&includeSupersedes=0]\n\n1. Import the fix into the Emergency Fix catalogue.\n 2. For deployed instances, apply this emergency fix on the VM. The IBM Java SDKwill be upgraded to IBM Java JDK 7.0 SR8 FP10 interim fix and IBM Java JDK 6.0 SR16 FP3 interim fix\n 3. Restart the deployed instance after the fix is applied.\n\nYou should verify applying this fix does not cause any compatibility issues. WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q129", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q129", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q129", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 23 July 2015: Original Version Published\nThe 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.", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q129", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "InfoSphere Streams Version 3.2.1 Fix Pack 6 InfoSphere Streams Version 3.2.1 Fix Pack 5 IT12710 [https://www.ibm.com/support/docview.wss?uid=swg1IT12710] Tuples not sent to consistent parallel channel using @parallel with partitionBy with bounded string attribute CVE-2015-1819 [http://www-01.ibm.com/support/docview.wss?uid=swg21981066] A vulnerability in XML processing affects IBM InfoSphere Streams CVE-2015-8317 [http://www-01.ibm.com/support/docview.wss?uid=swg21983370] Vulnerability in libxml2 affects IBM InfoSphere Streams CVE-2016-0466, CVE-2016-0448 [http://www-01.ibm.com/support/docview.wss?uid=swg21983436] Multiple vulnerabilities in IBM Java SDK affect IBM InfoSphere Streams CVE-2015-8710 [http://www-01.ibm.com/support/docview.wss?uid=swg21983371] Vulnerability in libxml2 affects IBM InfoSphere Streams CVE-2016-0363, CVE-2016-0376 [http://www-01.ibm.com/support/docview.wss?uid=swg21983367] IBM InfoSphere Streams update of IBM\u00ae SDK Java\u2122 Technology Edition InfoSphere Streams Version 3.2.1 Fix Pack 4 IT11451 [https://www.ibm.com/support/docview.wss?uid=swg1IT11451] Unbalanced zookeeper host pool connections IT11454 [https://www.ibm.com/support/docview.wss?uid=swg1IT11454] Collection directory for getlog is not configurable IT10196 [https://www.ibm.com/support/docview.wss?uid=swg1IT10196] Streams encounters an \"All the servers are dead for this entry\" error IT10362 [https://www.ibm.com/support/docview.wss?uid=swg1IT10362] The isContains native function at times returns true for points outside of the specified polygon, when it should return false CVE-2015-4000 [http://www.ibm.com/support/docview.wss?uid=swg21959676] Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects InfoSphere Streams CVE-2015-0488, CVE-2015-0478, CVE-2015-2808 [http://www.ibm.com/support/docview.wss?uid=swg21960981] Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect InfoSphere Streams InfoSphere Streams Version 3.2.1 Fix Pack 3 IT08234 [https://www.ibm.com/support/docview.wss?uid=swg1IT08234] The Streams application manager with tracing level INFO or higher causes SIGSEGV CVE-2014-6457, CVE-2014-3566, CVE-2014-3065 [http://www.ibm.com/support/docview.wss?uid=swg21698046] Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect InfoSphere Streams (CVE-2014-6457, CVE-2014-3566, CVE-2014-3065) CVE-2014-6593, CVE-2015-0138, CVE-2015-0410 [http://www.ibm.com/support/docview.wss?uid=swg21700697] Security Bulletin: Multiple vulnerabilities in IBM Java SDK and DB2 client affect InfoSphere Streams (CVE-2014-6593, CVE-2015-0138, CVE-2015-0410) CVE-2015-2808 [http://www.ibm.com/support/docview.wss?uid=swg21702155] Security Bulletin: Vulnerability in RC4 stream cipher affects InfoSphere Streams (CVE-2015-2808) InfoSphere Streams Version 3.2.1 Fix Pack 2 IT05394 [https://www.ibm.com/support/docview.wss?uid=swg1IT05394] NetezzaPrepareLoad operator loses precision with FLOAT64 and FLOAT32 values IT05330 [https://www.ibm.com/support/docview.wss?uid=swg1IT05330] Tokenize function fails for USTRINGS that contain surrogate pairs IT04952 [https://www.ibm.com/support/docview.wss?uid=swg1IT04952] Some streamtool properties are not dynamically updated IT05327 [https://www.ibm.com/support/docview.wss?uid=swg1IT05327] Streams Studio fails to start due to permission denied CVE-2014-4244 [http://www.ibm.com/support/docview.wss?uid=swg21681184] InfoSphere Streams is affected by a vulnerability in the IBM\u00ae SDK, Java\u2122 Technology Edition CVE-2014-0191 [http://www.ibm.com/support/docview.wss?uid=swg21681183] InfoSphere Streams is affected by libxml2 vulnerability InfoSphere Streams Version 3.2.1 Fix Pack 1 IT02036 [https://www.ibm.com/support/docview.wss?uid=swg1IT02036] SECURITY APAR CVE-2014-0411, CVE-2014-0453 AND CVE-2014-0460 IT02012 [https://www.ibm.com/support/docview.wss?uid=swg1IT02012] SPL-MAKE-DOC faile when operator contains IT02071 [https://www.ibm.com/support/docview.wss?uid=swg1IT02071] JMSSINK operator does not respect the DELIVERY_MODE attribute IT02072 [https://www.ibm.com/support/docview.wss?uid=swg1IT02072] JMSSINK and JMSSOURCE operators cannot connect to ACTIVEMQ if security is enabled IT01905 [https://www.ibm.com/support/docview.wss?uid=swg1IT01905] POWER() and MAGNITUDE() functions always return the result of the first input tuple IT01906 [https://www.ibm.com/support/docview.wss?uid=swg1IT01906] First two results output by an FFT operator with a sliding window might be identical IT01907 [https://www.ibm.com/support/docview.wss?uid=swg1IT01907] When using the FFT operator, the input list is being padded with zeros when REALCEPTRUM or REALDFT algorithm is used", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q129", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM\u00ae Runtime Environment Java\u2122 Technology Edition, Version 5.0 Service Refresh 16 Fix Pack 7 and Version 6 Service Refresh 16 Fix Pack 1 and earlier releases, that is used by IBM Tivoli Provisioning Manager. This also includes a fix for the Padding Oracle On Downgraded Legacy Encryption (POODLE) SSLv3 vulnerability (CVE-2014-3566). These were disclosed as part of the IBM Java SDK updates in October 2014 and January 2015.\nIBM WebSphere Application Server is shipped as a component of IBM Tivoli Provisioning Manager. Information about multiple vulnerabilities in IBM Java SDK affecting IBM WebSphere Application Server has been published in a security bulletin.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q129", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVE-ID: CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566]\nDESCRIPTION: Product could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plaintext of encrypted connections.\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\nCVEID:CVE-2014-6593 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6593]\nDESCRIPTION:An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 4\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/100153 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100153]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N)\n\nCVEID:CVE-2015-0410 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0410]\nDESCRIPTION:An unspecified vulnerability related to the Security component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/100151 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100151]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)\n\nCVEID: CVE-2015-0383 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0383]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE and JRockit related to the Hotspot component has no confidentiality impact, partial integrity impact, and complete availability impact.\nCVSS Base Score: 5.4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100148 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100148] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:L/AC:M/Au:N/C:N/I:P/A:C)", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q129", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Tivoli Provisioning Manager 7.2 and earlier", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q129", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "The recommended solution is to apply the remediation fix indicated below:\n\nProduct VRMF APAR Remediation/First Fix Tivoli Provisioning Manager 7.1 7.1.1-TIV-TPM-IF00007 none 7.1.1-TIV-TPM-IF00013 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Provisioning+Manager&release=7.1.1&platform=All&function=fixId&fixids=7.1.1-TIV*IF00013*&includeSupersedes=0] Tivoli Provisioning Manager 7.2 7.2.2.0-TIV-TPM-IF00003 none 7.2.2.0-TIV-TPM-JRE60SR16FP3 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Provisioning+Manager&release=7.2.2.0&platform=All&function=fixId&fixids=7.2.2.0-TIV-TPM-*JRE60SR16FP3]\nFor out of support versions, contact IBM customer support for assistance.\n\nTo remediate IBM WebSphere Application Server, please consult the security bulletin Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect WebSphere Application Server January 2015 CPU [http://www.ibm.com/support/docview.wss?uid=swg21695362] for vulnerability details and information about fixes.\n\nIBM recommends that you review your entire environment to identify areas that enable the SSLv3 protocol and take appropriate mitigation and remediation actions. The most immediate mitigation action that can be taken is disabling SSLv3. You should verify disabling SSLv3 does not cause any compatibility issues. WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q129", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q129", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\nIBM Java SDK Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg21688283]", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q129", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 30 April 2015: Original Version Published\nThe 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.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q129", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM\u00ae Runtime Environments Java\u2122 Technology Edition, Versions 5 and 6, that are used by Web Experience Factory. These issues were disclosed as part of the IBM Java SDK updates in January 2015. The \u201cFREAK: Factoring Attack on RSA-EXPORT keys\" TLS/SSL client and server vulnerability (CVE-2015-0138) may affect some configurations of products bundled with Web Experience Factory.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q129", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2015-0410 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0410]\nDESCRIPTION: An unspecified vulnerability related to the Security component could allow a remote attacker to cause a denial of service.\n\nCVSS Base Score: 5\nCVSS Temporal Score: See http://xforce.iss.net/xforce/xfdb/100151 [http://xforce.iss.net/xforce/xfdb/100151] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)\n\nCVEID:CVE-2014-6593 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6593]\nDESCRIPTION:An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.\n\nCVSS Base Score: 4\nCVSS Temporal Score: Seehttp://xforce.iss.net/xforce/xfdb/100153 [http://xforce.iss.net/xforce/xfdb/100153]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N)\n\nCVEID: CVE-2015-0138 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0138]\nDESCRIPTION: A vulnerability in various IBM SSL/TLS implementations could allow a remote attacker to downgrade the security of certain SSL/TLS connections. An IBM SSL/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers.\n\nThis vulnerability is also known as the FREAK attack.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691 [http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q129", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "All versions of Web Experience Factory 8.5, 8.0, 7.0.1, 7.0, and 6.1.5.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q129", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Obtain the JRE appropriate for you product from Fix Central [http://www-933.ibm.com/support/fixcentral/] [http://www-933.ibm.com/support/fixcentral/]. Note however that these updated JREs are only appropriate for customers that have installed the copy of Eclipse, WASCE, or Liberty bundled with Web Experience Factory.\n\nWeb Experience Factory (WEF) on Windows:\nLO83576\n*\nLO83577\n*\nLO83578\n*\n\nWeb Experience Factory (WEF) on Linux:\nLO83580\n*\nLO83581\n*\nLO83582", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q129", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.\n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www-03.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q129", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] [http://www-01.ibm.com/support/docview.wss?uid=swg21695474] IBM Java SDK Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg21695474] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] CHANGE HISTORY\n 27 March 2015 - Original Version Published\nThe 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\nCVE-2015-0138; CVE-2015-0410; CVE-2014-6593 SECURITY BULLETIN", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q129", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition, Versions 6 and 7 that is used by Rational Developer for System z. These issues were disclosed as part of the IBM Java SDK updates in January 2015. This bulletin also addresses the \u201cFREAK: Factoring Attack on RSA-EXPORT keys\" TLS/SSL client and server vulnerability..", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q129", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Subscribe to My Notifications to be notified of important product support alerts like this. * Follow this link [https://www.ibm.com/systems/support/myview/subscription/css.wss/subscriptions?methodName=startSearchToSubscribe&uctug_rational_dcfsbblurb_2013-11-05_myn_adoption_promo] for more information (requires login with your IBM ID)\n\nCVEID: CVE-2015-0138 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0138]\nDESCRIPTION: A vulnerability in various IBM SSL/TLS implementations could allow a remote attacker to downgrade the security of certain SSL/TLS connections. An IBM SSL/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers.\n\nThis vulnerability is also known as the FREAK attack.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691 [http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)\n\nCVEID: CVE-2015-0410 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0410]\nDESCRIPTION: An unspecified vulnerability related to the Security component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100151 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100151] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)\nCVEID: CVE-2014-6593 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6593]\nDESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100153 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100153] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N)", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q129", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Principal Product and Version(s) Affected Supporting Product and Version Rational Developer for System z, versions 9.1.x, 9.0.x, 8.5.x * IBM SDK, Java Technology Edition, Version 6 Service Refresh 16 FP3 and earlier\nIBM SDK, Java Technology Edition, Version 7 Service Refresh 8 FP10 and earlier", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q129", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "IBM has provided patches for all affected versions.\n\nFollow the installation instructions in the README files included with the patch.\n\nThe fix can be obtained at the following locations:\nRational Developer for System z Interim Fix 3 for 8.5.x [http://www-01.ibm.com/support/docview.wss?uid=swg24039791]\nRational Developer for System z Interim Fix 3 for 9.0.x [http://www-01.ibm.com/support/docview.wss?uid=swg24039792]\nRational Developer for System z Interim Fix 3 for 9.1.x [http://www-01.ibm.com/support/docview.wss?uid=swg24039793]", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q129", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q129", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q129", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nThe 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.", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q294", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Ensure the IBM SPSS Modeler client license used has 'Server enablement' imbedded.\n\nThis will require contacting IBM BA SPSS Client Care.\n\nThe authorization code that you have applied to the Modeler Client installation does not have the \"Server Enablement\" option checked.\n\nIf you have purchased Modeler Server, please contact IBM SPSS customer services and obtain a Modeler Client code that has the server enablement option checked and apply that code to your Modeler Client installation. After doing this, the server login option should be enabled after you restart the client application.\n\nDetails of how to contact customer services can be found here:\n\nhttp://www.ibm.com/software/analytics/spss/ [http://www.ibm.com/software/analytics/spss/]", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q294", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Modeler forum is Live! [https://developer.ibm.com/answers/topics/modeler/?smartspace=predictive-analytics]\n\nHISTORICAL NUMBER\n 77301", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q294", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "I am an IT administrator for an organization. My IBM SPSS Statistics 23.0 client licenses are expiring. I have purchased IBM SPSS Statistics 24.0 client software and licenses, but I am afraid my version 23.0 licenses will expire before I complete my client migrations to Statistics 24.0. How can I keep my end users up and running throughout the migration?", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q294", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "License for version N expires before all clients can be upgraded to client software version N+1", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q294", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Starting in IBM SPSS Statistics 22.0 we have added what we colloquially call \"N+1 Licensing\" for this exact problem. Simply put, your Statistics version \"N\" will use client licenses for Statistics version \"N+1\".\n\nImagine the above scenario. You have IBM SPSS Statistics 23.0 clients deployed and the license period is coming to an end. Your licenses for Statistics 23.0 will expire long before you complete the upgrade of all clients to Statistics 24.0. The solution is to go ahead and deploy your Statistics 24.0 licenses. Statistics 23.0 (version \"N\") will use a Statistics 24.0 (version \"N+1\") license.\n\nThis is true for Authorized User licensing.\n\nThis is true for Concurrent User licensing - though as a solution, it really is more suited to this method.\n\nCAVEATS:\n\n1) If you are deploying multiple license strings (e.g. A 'base' license plus one or more add-on licenses) the 'base' and 'add-on' license versions must match.\n\nFor example: You have IBM SPSS Statistics 23.0 client installed.\n\nYou CAN add a version 23.0 IBM SPSS Statistics Advanced Statistics module to your version 23.0 \"IBM SPSS Statistics Base\" installation\nYou CANNOT add a version 24.0 IBM SPSS Statistics Advanced Statistics module to your version 23.0 \"IBM SPSS Statistics Base\" installation license.\n\nYou CAN add a version 24.0 IBM SPSS Statistics Advanced Statistics module to your version 24.0 \"IBM SPSS Statistics Base\" installation license.\n\n2) \"N+1 Licensing\" will not work with Commuter License tokens. IBM SPSS Statistics version \"N\" can use an IBM SPSS Statistics \"N+1\" Concurrent User license token. However, it cannot use the same as a Commuter license token.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q294", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\nNeed more help? Our Licensing forum is Live! [https://developer.ibm.com/answers/topics/spsslicensing.html]", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q294", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "IF the product presenting the error 7003/symptom 213 is licensed via the Sentinel RMS License Manager, THEN refer to KnowledgeBase resolution 91720.\nIF the product presenting error 7003/symptom 213 is licensed with a Single-User or Site license authorization code, THEN go to (A).\n\n(A)\nIF your was working normally for more than 14 days prior to presenting error 7003/symptom 213, THEN go to (B)\nIF your product has been working for no more than 14 days prior to presenting error 7003/symptom 213, THEN go to (E)\n\n(B)\nConfirm the date and time on the computer are correct.\n\nIF date/time is NOT correct, THEN got to (C)\nIF date/time is correct, THEN go to (D).\n\n(C)\n1) Reset the date/time on the computer.\n2) Start the IBM SPSS product.\n\nIF the error message persists, THEN go to (D)\nIF the error not longer presents, then the problem has been resolved.\n\n(D)\n1) Delete (or rename) the file named 'lservrc' found in program installation directory of the IBM SPSS product.\n2) License the IBM SPSS product using the License Authorization Wizard and your product authorization code.\n\n(E)\n1) Please contact IBM SPSS Customer Service via email at spsscs@us.ibm.com or via phone at 800-521-1337.\n2) Provide IBM SPSS Customer Service with the license authorization code used to license your IBM SPSS product.\n3) Request confirmation that the license authorization code is for the correct product.\n4) Request confirmation that the license authorization code includes the 'base' module (if applicable).\n5) Request confirmation that the license authorization code is not expired", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q294", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our AMOS forum is Live! [https://developer.ibm.com/answers/search.html?f=&type=question&redirect=search%2Fsearch&sort=relevance&q=%2B[amos]]\n\nHISTORICAL NUMBER\n 52068", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q294", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "The authorization code product and/or version does not match that of your installed product.", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q294", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Please check that your authorization code matches the version and software product you are trying to license. The product and version of the authorization code must match that of the installed product. For assistance with your authorization codes, please visit the Predictive Analytics Community Get Help page https://developer.ibm.com/predictiveanalytics/get-help/ [https://developer.ibm.com/predictiveanalytics/get-help/], for direct links to the License Key Center and information about your Support options.", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q294", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Visualization Designer Platform Independent 1.0.3, 1.0.2, 1.0\nHISTORICAL NUMBER\n 93088\n\nPRODUCT LIFECYCLE", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q294", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM is pleased to announce a new support option available to you when your software reaches End of Service (EOS). IBM will offer Continuing Support for select Master Data Management (MDM) products and releases. This offering will provide you with continued access to the same knowledgeable global Support team you are working with today.", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q294", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM is pleased to announce a new support option available to you when your software reaches End of Service (EOS). IBM will offer Continuing Support for MDM Version 10.0 and MDM 10.1, for all editions (part ID 5725-E59). This offering will provide you with continued access to the same knowledgeable global Support team you are working with today.\nWorld-Class Software Support\n\nUnder your IBM Passport Advantage agreement's (International Passport Advantage Agreement or International Passport Advantage Express Agreement) Software Subscription and Support (S&S) terms, you receive comprehensive cross-platform technical assistance from a team of highly skilled Support experts. Additionally, you get flexible upgrade protection, access to the latest software versions and releases, remote technical support, 24x7 support for business-critical outages, online self-help resources, and unlimited electronic and voice access (where available) to world-class global IBM Software Support Centers.\n\nContinuing Support Option\n\nContinuing Support extends support for your software beyond its EOS date. When your software versions reach their End of Service date and support is no longer available through standard Software S&S, you now have the option for Continuing Support and no longer need to tackle support issues on your own.\n\nContinuing Support Program Benefits\n\nThis exciting offering allows you to enjoy many of the S&S benefits that you have told us matter most to you, including:\n\n\u00b7 7 days, 24-hour support for mission critical emergencies (Severity 1)\n\u00b7 Provided by voice in most countries.\n\u00b7 Provided in English, with the local language accommodated when possible.\n\u00b7 Remote problem analysis and assistance during normal country business hours in your time zone.\n\u00b7 Support for routine, short duration installation and usage questions.\n\u00b7 Response time objective of two hours during prime shift for voice and electronic problem submissions.\n\u00b7 Response objective for critical/emergency problems during off-shift hours is two hours.\n\u00b7 Unlimited number of technical support incidents.", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q294", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "\u00b7 Access to documentation, technotes and other online product material.\n\u00b7 Access to existing available fixes created before the product's EOS date to correct known defects.\n\nThe Continuing Support offering does not include:\n\n\u00b7 Voice and electronic access support for code-related problems.\n\u00b7 Development analysis of new defects.\n\u00b7 Development of or packaging fixes that are not already available.\n\u00b7 Support for Supporting Programs and third party components.\n\u00b7 Infrastructure that are not included in the software version\u2019s Hardware and Software Requirement page.\n\nProgram Participation\n\nTo receive Continuing Support, you only need to maintain active S&S for licenses deployed for the software. If you are not current on S&S, please contact us (askCS@us.ibm.com) to discuss reinstatement options.\n\nComplete Coverage for Mission Critical Installations\n\nIn addition to Continuing Support, IBM still provides the option for Service Extension (SE). Customers will have the choice between Continuing Support and Service Extension. For mission critical installations, it is highly recommended that you continue to pro-actively purchase a Service Extension to receive full defect and development support assistance. By adding this offering, you will be maintaining the same full defect support coverage you received before the End of Service date, further protecting your installation. If you require development or defect support assistance after the End of Service for any version, including during the life of Continuing Support or with an active Upgrade Bridge contract, you will be required to purchase a Service Extension at that time at IBM's specified charge in order to receive such support. Contact your IBM sales representative for more information, or to purchase these options.\n\nFAQs\n\n1. Why should I take advantage of Continuing Support?\nContinuing Support provides flexibility for you to remain up and running on your software version with non-defect Support until you are able to upgrade to the latest version. Continuing Support provides uninterrupted access to many of the benefits of S&S and is more affordable than other options, such as a Service Extension.\n\n2. What is the cost of Continuing Support and how do I buy it?\nContinuing Support is available when you maintain active S&S. To avoid possible delays in receiving Support, you are encouraged to email askcs@us.ibm.com or your Sales contact.", "logical_doc_id": 5, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q294", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "3. I am on a software version which is out of support, and would like to benefit from this offering.\nContinuing Support is now available to clients running Master Data Management V10.0 and V10.1, for all editions. To learn more about Continuing Support for your installations, please contact your local sales representative or email inquiries to askcs@us.ibm.com\n\n4. Are special builds included with Continuing Support?\nContinuing Support assistance provides you with access to pre-existing and available fixes. Special builds will NOT be created as part of this offering. If a special build is required, you will need first to purchase and sign a contract for a Service Extension.\n\n5. Should I purchase a Service Extension (SE) instead of relying on Continuing Support assistance?\nIf your business requires the same comprehensive full-defect coverage it relied on before the EOS date, you will want to purchase a SE, if available. A SE is recommended for maximum coverage for your mission critical installations.\n\n6. What if I have already purchased a Service Extension (SE) for my software licenses?\nYou should evaluate your true business need. If you require maximum Support coverage, you should maintain the SE for optimum coverage (this is recommended). If the Support offerings available through Continuing Support for non-defect support are sufficient, you may cancel your SE agreement. By cancelling your SE agreement, you will remove coverage for defect assistance and will be required to pay an increased fee if defect correction is required.\n\nFor more information\nTo get more information about the Continuing Support offering, email us at askcs@us.ibm.com [askcs@us.ibm.com]", "logical_doc_id": 5, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q043", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This document describes how to download and install IBM Netcool Network Management V9.2 using the Passport Advantage website.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q043", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Netcool Network Management provides network discovery and event and network management, including identification and resolution of root-causes and system, network, and service failures, and configuration management capabilities for network devices. Inventory and connectivity data is integrated with IBM Tivoli Netcool/OMNIbus event data. Network management staff can visualize and understand the layout of complex networks and the impact of network events and failures, and work with events to locate, diagnose, and solve network problems in real time.\n\nNetcool Network Management consists of the following products: IBM Tivoli Netcool/OMNIbus V7.4, IBM Tivoli Network Manager IP Edition V3.9, and IBM Tivoli Netcool Configuration Manager V6.4.\n\nMore information\n\nThe libraries of publications for the products in Netcool Network Management are available from this website: IBM Tivoli Network Management Information Center [http://www.ibm.com/support/knowledgecenter/SSNFET].\n\nDownloading and assembling the product\n\n1. Navigate your browser to the Find Downloads and Media [http://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/sdma/SDMA?PO=DOWNLOAD_FIND_BY_PART_NUMBER] page on the IBM Passport Advantage Online website. You must log on to continue.\n 2. Select the Find by part number search option under Download finder options.\n 3. Search for each downloadable image by part number (parts are listed and described by operating system in the tabbed section of this document).\n 4. Download all of the parts that you need.\n 5. Unpack each of the parts into a single temporary directory on your system. If you want to install Tivoli Netcool/OMNIbus as part of the Network Manager installation process, you must download the Tivoli Netcool/OMNIbus installation package to a specific location and point the Network Manager installer to that location. Do not extract or rename the Tivoli Netcool/OMNIbus installation package.\n 6. Open the Quick Start image and follow the instructions in the Quick Start Guide to install the base product.\n\n[http://www.ibm.com/i/c.gif] [http://www.ibm.com/i/c.gif] AIX [http://www.ibm.com/support/docview.wss?rs=3120&uid=swg24033496] [http://www.ibm.com/i/c.gif] HP-UX [http://www.ibm.com/support/docview.wss?rs=3120&uid=swg24033919] [http://www.ibm.com/i/c.gif] Linux [http://www.ibm.com/support/docview.wss?rs=3120&uid=swg24033491] [http://www.ibm.com/i/c.gif] Linux zSeries [http://www.ibm.com/support/docview.wss?rs=3120&uid=swg24033488] [http://www.ibm.com/i/c.gif] Solaris [http://www.ibm.com/support/docview.wss?rs=3120&uid=swg24033487] [http://www.ibm.com/i/c.gif] Windows [http://www.ibm.com/support/docview.wss?rs=3120&uid=swg24033493] [http://www.ibm.com/i/c.gif] [http://www.ibm.com/i/c.gif] Supported operating systems\n\nNetwork Manager IP Edition V3.9 and Netcool Configuration Manager V6.4 are not supported on HP-UX operating systems. Tivoli Netcool/OMNIbus is supported on HP-UX.\n\nThe base product and all required and optional parts are supported on HP-UX on Itanium. Certain parts, not including the base product, are supported on HP-UX PA-RISC.\n\nSee the Software Product Compatibility Reports [http://pic.dhe.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1311792011350&osPlatform=HP ] website for the HP-UX on Itanium operating systems on which Tivoli Netcool/OMNIbus is supported.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q043", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Downloadable parts\n\nThere are downloadable parts for the base products and components. Refer to the links below for details about what each part contains. These parts are contained in the eAssembly CRL04ML.\n\nParts for Tivoli Netcool/OMNIbus V7.4\n\nFor the downloadable parts for Tivoli Netcool/OMNIbus V7.4 on HP-UX operating systems, see www.ibm.com/support/docview.wss?rs=3120&uid=swg24033294 [http://www.ibm.com/support/docview.wss?rs=3120&uid=swg24033294].\n\nQuick Start Guide\n\nThe Quick Start Guide is available for download in the eAssembly CRG6HML, which contains the following part.\n\nAssembly # Description CIE7QML\n\nIBM Netcool Network Management Quick Start Guide\n\nChange history\nNovember 30, 2012: First release of this document.\n\nURL LANGUAGE SIZE(Bytes) Netcool Network Management V9.2 [http://www.ibm.com/support/knowledgecenter/SSNFET_9.2.0/com.ibm.omnnmip.doc_9.2.0/tivnetnetwelcome.html] English 1 Tivoli Netcool/OMNIbus V7.4 [http://www.ibm.com/support/knowledgecenter/en/SSSHTQ_7.4.0/com.ibm.netcool_OMNIbus.doc_7.4.0/omnibus/wip/kc_welcome.html] English 1 Tivoli Netcool Configuration Manager V6.4 [http://www.ibm.com/support/knowledgecenter/en/SSSHRK_3.9.0/com.ibm.networkmanagerip.doc_3.9/itnm/ip/wip/common/networkmanageripeditionv390.html] English 1 Tivoli Network Manager IP Edition V3.9 [http://www.ibm.com/support/knowledgecenter/en/SS7UH9_6.4.0/ncm/wip/welcome/kc_welcome-444.html] English 1\nINSTALLATION INSTRUCTIONS\n\nFollow the instructions in the Quick Start Guide to install the product. You can find the Quick Start Guide at www.ibm.com/support/docview.wss?rs=3120&uid=swg27036638 [http://www.ibm.com/support/docview.wss?rs=3120&uid=swg27036638].\n\nDOWNLOAD PACKAGE\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options IBM Passport Advantage Online 30 Nov 2012 English 1 HTTP [http://www-01.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli Netcool Configuration Manager Linux, Solaris, AIX 6.4 All Editions Systems and Asset Management Tivoli Network Manager IP Edition AIX, Linux, Solaris, Windows 3.9\n\nPAODownloadDocument; download Network Manager IP Edition; download ITNM; download Network Manager v3.9; download Network Manager 3.9; Network Manager DOWNLOADABLE FILES", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q043", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "This document describes how to download IBM Tivoli Network Manager IP Edition version 3.9 from the IBM Passport Advantage Online Web site.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q043", "section_id": 3, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "[http://www.ibm.com/i/c.gif] IBM Tivoli Network Manager IP Edition discovers networks, including layer 2 and 3 network devices, interfaces and connectivity. Network Manager also integrates topology and alert data with IBM Tivoli Netcool/OMNIbus so that operators can visualize and understand the layout of complex networks, and diagnose and solve network problems in real time.\n\nAfter logging into IBM's Passport Advantage Online [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm] Web site, click Software download & media access, then click Download finder, then select Find by product description and type in Tivoli Network Manager. Expand the Tivoli Software eAssembly, and select the images you wish to download from that list. All Tivoli Network Manager IP Edition download images are described below.\n\nDownloading and assembling the product\n\n1. Download all of the parts that you need, both required and optional. The parts are listed by operating system in the tabs below.\n 2. Unpack each of the parts into a single temporary directory on your system. If you want Network Manager to install IBM Tivoli Netcool/OMNIbus, do not rename the Tivoli Netcool/OMNIbus package.\n 3. Follow the instructions in the Quick Start Guide to install the product.\n\nTo see the part numbers for your platform, click the appropriate link below.\n\n[http://www.ibm.com/i/c.gif] [http://www.ibm.com/i/c.gif] AIX [http://www.ibm.com/support/docview.wss?rs=3118&uid=swg24028958] [http://www.ibm.com/i/c.gif] Linux [http://www.ibm.com/support/docview.wss?rs=3118&uid=swg24028957] [http://www.ibm.com/i/c.gif] Linux zSeries [http://www.ibm.com/support/docview.wss?rs=3118&uid=swg24028956] 3 [http://www.ibm.com/i/c.gif] Solaris [http://www.ibm.com/support/docview.wss?rs=3118&uid=swg24028955] [http://www.ibm.com/i/c.gif] Windows [http://www.ibm.com/i/c.gif] [http://www.ibm.com/i/c.gif] Supported operating systems\n\nOn Intel x86 processor and chipset-based platforms, these versions are supported:\nWindows Server 2008 Enterprise Edition (x86-32 and x86-64)\nWindows Server 2008 Standard Edition\nWindows Server 2008 Datacenter Edition\n\nDownloadable parts\n\nThere are downloadable parts for each supported platform upon which IBM Tivoli Network Manager IP Edition can be installed. Refer to the tables below for details about what each part contains. At a minimum, you must download the required parts.\n\nRequired parts\n\nTo install IBM Tivoli Network Manager IP Edition V3.9 Multilingual on Windows, you need to download the following parts:\n\nPart # Description CI7F2ML IBM Tivoli Network Manager IP Edition V3.9 For Windows Multilingual Includes the base product including the Tivoli Integrated Portal, Tivoli Common Reporting, Topoviz Web application, Tivoli Netcool/OMNIbus Web GUI, and IBM Java Runtime Environment (JRE) 1.6.\n\n(English, Brazilian Portuguese, French, German, Italian, Spanish, Japanese, Korean, Hungarian, Polish, Russian, Simplified Chinese, and Traditional Chinese)", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q043", "section_id": 3, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "CI7EYML.pdf IBM Tivoli Network Manager IP Edition V3.9 Quick Start Guide.\nAdditional parts\n\nIn addition to the required parts, you must also have or download the following software which is not provided in this eAssembly:\n\nPart # Description CI3JCML IBM Tivoli Netcool/OMNIbus Version 7.3.1\n\nRefer to the Network Manager Quick Start Guide for instructions about installing Tivoli Netcool/OMNIbus with Network Manager.\n\nOptional parts\n\nThese optional parts are included in this eAssembly.", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q043", "section_id": 3, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Part # Description CZ6V2EN Informix Workgroup Edition V11.50.UC6 Sun SolS 32 bit CZ6V3EN Informix Workgroup Edition V11.50.FC6 Sun SolS 64 bit CZ6V8EN Informix Workgroup Edition V11.50.UC6 AIX 32 bit CZ6V9EN Informix Workgroup Edition V11.50.FC6 AIX 64 bit CD CZ6VCEN Informix Workgroup Edition V11.50..UC6 Linux x86 CD CZ6VGEN Informix Workgroup Edition V11.50.FC6 Linux x86 64 CD CZ6VEEN Informix Workgroup Edition V11.50.FC6 zSeries 64bit CD CZ6VAEN Informix Workgroup Edition V11.50.TC6 Windows CD CZ6VBEN Informix Workgroup Edition V11.50.FC6 Windows 64 bit CD CI8GKML Informix Growth Edition 11.70 UC5 Linux x86 Multilingual CI8GLML Informix Growth Edition 11.70 FC5 Linux x86 64 Multilingual CI8GNML Informix Growth Edition 11.70 FC5 Linx zSeries 64 bit Multilingual CI8GRML Informix Growth Edition 11.70 FC5 AIX 64 bit Multilingual CI8GUML Informix Growth Edition 11.70 FC5 Sun Solaris/SPARC 64 bit Multilingual CI8GWML Informix Growth Edition 11.70 FC5 Windows x86 64 bit Multilingual CI8GXML Informix Growth Edition 11.70 TC5 Windows x86 32 bit Multilingual CZ1HMEN IBM DB2 9.7 for AIX, English CZ1HPEN IBM DB2 for Linux, UNIX and Windows V9.7 - Limited Use for Solaris on Ultra SPARC CZ1HQEN IBM DB2 for Linux, UNIX and Windows V9.7 - Limited Use for Solaris on x64 CZ1HREN IBM DB2 for Linux, UNIX and Windows V9.7 - Limited Use for Linux(R) on 32-bit CZ1HSEN IBM DB2 for Linux, UNIX and Windows V9.7 - Limited Use for Linux(R) on AMD64 CZ1HKML IBM DB2 for Linux, UNIX and Windows V9.7 - Limited Use for Windows(R) on 32 bit CZ1HLML IBM DB2 for Linux, UNIX and Windows V9.7 - Limited Use for Windows(R) on AMD64&INTEL(R) EM64T SYS (X64) CZ1HNEN IBM DB2 for Linux, UNIX and Windows V9.7 - Limited Use for HP-UX on HP Integrity CZ1HTEN IBM DB2 for Linux, UNIX and Windows V9.7 - Limited Use for Linux(R) on POWER CZ1HUEN IBM DB2 for Linux On zSeries - Limited Use for Linux on zSeries CZ1H8ML IBM DB2 National Language Pack V9.7 for AIX, Multilingual CZ1HAML IBM DB2 National Language Pack V9.7 for Solaris on UltraSPARC systems CZ1HBML IBM DB2 National Language Pack V9.7 for Solaris on x64 systems CZ1HCML IBM DB2 National Language Pack V9.7 for Linux(R) on 32-bit AMD and Intel systems CZ1HDML IBM DB2 National Language Pack V9.7 for Linux(R) on AMD64 and Intel(R) EM64 CZ1H9ML IBM DB2 National Language Pack V9.7 for HP-UX on HP Integrity Itanium-based CZ1HEML IBM DB2 National Language Pack V9.7 for Linux(R) on POWER(TM) (IBM i and System p) CZ1HFML IBM DB2 National Language Pack V9.7 for Linux On zSeries CZZM7ML IBM Tivoli Common Reporting V2.1.1 Windows 32 bit Multilingual - part 1 CI01GML IBM Tivoli Common Reporting V2.1.1 Windows 32 bit Multilingual - part 2 CI01HML IBM Tivoli Common Reporting V2.1.1 Windows 64 bit Multilingual - part 1 CI01IML IBM Tivoli Common Reporting V2.1.1 Windows 64 bit Multilingual - part 2 CZZM8ML IBM Tivoli Common Reporting V2.1.1 Linux 32 bit Multilingual CI01JML IBM Tivoli Common Reporting V2.1.1 Linux 64 bit Multilingual CZZM9ML IBM Tivoli Common Reporting V2.1.1 AIX 32 bit Multilingual CI01KML IBM Tivoli Common Reporting V2.1.1 AIX 64 bit Multilingual CZZN0ML IBM Tivoli Common Reporting V2.1.1 HP-UX 32 bit Multilingual CI01NML IBM Tivoli Common Reporting V2.1.1 HP-UX 64 bit Multilingual CZZN1ML IBM Tivoli Common Reporting V2.1.1 Solaris 32 bit Multilingual CI01LML IBM Tivoli Common Reporting V2.1.1 Solaris 64 bit Multilingual CZZN2ML IBM Tivoli Common Reporting V2.1.1 Linux on z 32 bit Multilingual CI01MML IBM Tivoli Common Reporting V2.1.1 Linux on z 64 bit Multilingual CZZN3ML IBM Tivoli Common Reporting V2.1.1 Cognos Framework Manager Windows Multilingual CZF7REN IBM Tivoli Monitoring V6.2.2 FP2 Base, Windows - English CZF7SEN IBM Tivoli Monitoring V6.2.2 FP2 Base, UNIX - English CZF7TEN IBM Tivoli Monitoring V6.2.2 FP2 Base, Linux - English CZH9FML IBM Tivoli Monitoring V6.2.2 Language Support\n[http://www.ibm.com/i/c.gif] PREREQUISITES\nFor software and hardware prerequisites, see the Planning sections in the documentation.", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q043", "section_id": 3, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "URL LANGUAGE SIZE(Bytes) Planning information [http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.networkmanagerip.doc_3.9/itnm/ip/wip/install/task/nmip_pln_planninginst.html] English 1\nINSTALLATION INSTRUCTIONS\nTo install the product, follow the instructions in the IBM Tivoli Network Manager 3.9 Quick Start Guide.\n\nURL LANGUAGE SIZE(Bytes) Quick Start Guide (Multilingual) [http://www.ibm.com/support/docview.wss?rs=3121&uid=swg27020740] English 1\nDOWNLOAD PACKAGE\nDownload IBM Tivoli Network Manager IP Edition V3.9 from the Passport Advantage Online Web site.\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options Passport Advantage Online 25/02/2011 US English 1 HTTP [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\nTECHNICAL SUPPORT\n\nYou can access IBM Tivoli Product support at http://www-01.ibm.com/software/sysmgmt/products/support/IBMTivoliNetworkManagerIPEdition.html [http://www-01.ibm.com/software/sysmgmt/products/support/IBMTivoliNetworkManagerIPEdition.html]\n\nYou can access Passport Advantage Online support at www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html [http://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html]\n\nDOWNLOADABLE FILES", "logical_doc_id": 0, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q043", "section_id": 4, "heading": "ABSTRACT", "parent": null, "text": "This document describes how to download and install IBM Tivoli Network Manager IP Edition Version 4.2 Fix Pack 1 using the Passport Advantage Web site.", "logical_doc_id": 0, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q043", "section_id": 5, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "IBM\u00ae Tivoli\u00ae Network Manager IP Edition discovers networks, including layer 1 optical networks, and layer 2 and 3 IP networks. Network Manager also discovers mobile networks (including LTE). In addition, Network Manager integrates network topology information with alert data from IBM Tivoli Netcool/OMNIbus so that operators can visualize and understand the layout of complex networks, and diagnose and solve network problems in real time.\n\nAfter logging into IBM's Passport Advantage Online Web site at https://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm], click Software download & media access, then click Download finder, then select Find by product description and type in Tivoli Network Manager. Expand the Tivoli Software eAssembly, and select the images you wish to download from that list. All Tivoli Network Manager IP Edition download images are described below.\n\nMore information\nThe IBM Tivoli Network Manager IP Edition V4.2 library of publications are available from IBM Knowledge Center at https://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/common/welcome.html [https://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/common/welcome.html]\n\nDownloading and installing the product\n\n1. Download all of the parts that you need, both required and optional. The parts are listed in the sections below.\n 2. Unpack each of the parts into a single temporary directory on your system.\n 3. Follow the instructions in the Installing [https://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/install/task/ins_installing.html] section of the IBM Knowledge Center to install the product.\n\nSupported operating systems\n\nOn IBM\u00ae PowerPC-based systems, the following versions are supported:\nAIX\u00ae 6.1 iSeries and pSeries\nAIX 7.1 iSeries and pSeries\n\nOn Intel and Advanced Micro Devices (AMD) x86 processors, the following versions are supported:\nRed Hat Enterprise Linux 6 (x86-64)\nRed Hat Enterprise Linux 7 (x86-64)\nSuSE Linux Enterprise Server (SLES) 11.0 (x86-64) SP2 and SP3\n\nDownloadable parts\n\nThere are downloadable parts for each supported platform upon which IBM Tivoli Network Manager IP Edition can be installed. Refer to the tables below for details about what each part contains. At a minimum, you must download the required parts.\n\nRequired parts\n\nTo install IBM Tivoli Network Manager IP Edition V4.2.0.1 Multilingual, you need to download the following parts:\n\nPart # Description CNE9VEN IBM Tivoli Network Manager IP Edition 4.2.0.1 for Linux Includes the base product including the core components, the GUI components, and the topology database scripts.\n\n(English, Brazilian Portuguese, French, German, Italian, Spanish, Japanese, Korean, Hungarian, Polish, Russian, Simplified Chinese, and Traditional Chinese)", "logical_doc_id": 0, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q043", "section_id": 5, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "CNE9WEN IBM Tivoli Network Manager IP Edition 4.2.0.1 for AIX Includes the base product including the core components, the GUI components, and the topology database scripts.\n\n(English, Brazilian Portuguese, French, German, Italian, Spanish, Japanese, Korean, Hungarian, Polish, Russian, Simplified Chinese, and Traditional Chinese)\n\nCNE9UML IBM Tivoli Network Manager IP Edition V4.2.0.1 Quick Start Guide.\nDB2 is the default topology database in Network Manager 4.2. Network Manager 4.2 also supports Oracle Database version 12c Enterprise Edition with Partitioning option.\n\nPart # Description CRYY2ML IBM DB2 10.5 Enterprise Server Edition for Tivoli Netcool/OMNIbus, Network Manager, and Netcool Configuration Manager\n\nOptional parts\n\nThese optional parts are included in this eAssembly.\n\nPart # Description CRYY6ML IBM Tivoli Monitoring V6.3.0.2 and Monitoring Agent for Network Manager IP Edition V4.2 CN933EN IBM Tivoli Monitoring Agent for Network Manager V4.2 for Linux CN934EN IBM Tivoli Monitoring Agent for Network Manager V4.2 for AIX CN935EN IBM Tivoli Monitoring Agent for Network Manager V4.2 for Windows CJ0R8ML Jazz for Service Management v1.1.3 for Tivoli Netcool/OMNIbus, Network Manager, Netcool Configuration Manager, and Network Performance Insight CJ0S1ML Websphere Application Server 8.5.5.9 and SDK Java 7 for Tivoli Netcool/OMNIbus, Network Manager, and Netcool Configuration Manager\nPREREQUISITES\nFor software and hardware prerequisites, see the Planning for installation section in the Network Manager 4.2 documentation on the IBM Knowledge Center.\n\nURL LANGUAGE SIZE(Bytes) Planning for installation [https://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/install/task/pln_planninginst.html] English 1\nINSTALLATION INSTRUCTIONS\nTo install the product, follow the instructions in the IBM Tivoli Network Manager IP Edition V4.2 Quick Start Guide. The Quick Start Guide is in multiple languages.\n\nURL LANGUAGE SIZE(Bytes) Quick Start Guide [https://www-01.ibm.com/support/docview.wss?uid=swg27048605] English 1\nDOWNLOAD PACKAGE\nDownload IBM Tivoli Network Manager IP Edition V4.2.0.1 from the Passport Advantage Online Web site.\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options Download Network Manager 4.2.0.1 for AIX and Linux 22 Sep 2016 English 1 HTTPS [https://www-01.ibm.com/software/how-to-buy/passportadvantage/pao_customers.htm]\nTECHNICAL SUPPORT\n\nYou can access IBM Tivoli Product support at https://www.ibm.com/software/sysmgmt/products/support/IBMTivoliNetworkManagerIPEdition.html [https://www.ibm.com/software/sysmgmt/products/support/IBMTivoliNetworkManagerIPEdition.html]\n\nYou can access Passport Advantage Online support at https://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html [https://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html]\n\nWindows HSM; 6.4; 6.4.0 DOWNLOADABLE FILES", "logical_doc_id": 0, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q043", "section_id": 6, "heading": "ABSTRACT", "parent": null, "text": "This document describes how to download and install IBM Tivoli Storage Manager HSM for Windows Version 6.4 from the Passport Advantage Online Web Site", "logical_doc_id": 0, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q043", "section_id": 7, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "This document describes how to download IBM Tivoli Storage Manager Version 6.4 installation images using the Passport Advantage Online Web site [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm].\n\nThe Version 6.4 IBM Tivoli Storage Manager HSM for Windows client migrates files from your local file system to storage and recalls them either automatically or selectively. Migrating files to a distributed storage device frees space for new data on your local file system, and takes advantage of lower-cost storage resources that are available in your network environment.\n\nMore information\nTo access a wide variety of technical resources for this product, see the Tivoli Storage Manager V6.4 product information [https://www.ibm.com/support/knowledgecenter/SSATMW_6.4.0/com.ibm.itsm.hsmwin.doc/t_tsmhsmw.html].\n\nSpace requirements\n68 MB of disk space to download the part, plus\n67 MB of disk space to unpack the part.\n32 MB of disk space for the installed product, plus 23 MB for Microsoft redistributables.\n\nDownloading and assembling the product: 1. Download the part. The part number is listed in the \"Downloadable parts\" section of this document.\n 2. Unpack the downloaded part.\n 3. Follow the instructions in the IBM Tivoli Storage Manager HSM for Windows Quick Start Guide [http://www.ibm.com/support/docview.wss?&uid=swg27035889] to install the product.\n\nSupported platforms: * Windows 2008 Server\nWindows 2012 Server\n\nDownloadable parts: * CB8LEML.iso\n\nPREREQUISITES\nThe hardware and software requirements are explained in the following documents.\n\nURL LANGUAGE SIZE(Bytes) HW/SW requirements [http://www.ibm.com/support/docview.wss?&uid=swg21319299] English 1\nINSTALLATION INSTRUCTIONS\nRetrieve a copy of the IBM Tivoli Storage Manager HSM for Windows Quick Start Guide. The Quick Start Guide is available with the product and included on the Quick Start CD. The Quick Start Guide is also available for download in PDF format in all supported languages at the Web site listed below. Follow the instructions in the IBM Tivoli Storage Manager HSM for Windows Quick Start Guide to install the product.\n\nURL LANGUAGE SIZE(Bytes) TSM HSM for Windows 6.4 Quick Start Guide [http://www.ibm.com/support/docview.wss?&uid=swg27035889] English 1\nDOWNLOAD PACKAGE\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options Log on to Passport Advantage online 16 Nov 2012 English 16000 HTTP [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\nTECHNICAL SUPPORT\n\nSee the Passport Advantage Online support at eCustomer Care contact information [http://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html].\n\nFor additional information, go to the following Web sites:\nIBM Tivoli Storage Manager Support [http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager]\nHSM for Windows Support [http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManagerHSMforWindows.html]\n\n DOWNLOADABLE FILES", "logical_doc_id": 0, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q043", "section_id": 8, "heading": "ABSTRACT", "parent": null, "text": "This document describes how to download the installation images for the IBM\u00ae Tivoli\u00ae Storage Productivity Center Standard Edition V4.2 using the Passport Advantage\u00ae Online Web site", "logical_doc_id": 0, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q043", "section_id": 9, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "This document describes how to download IBM Tivoli Storage Productivity Center Standard Edition V4.2 for Linux\u00ae installation images from the IBM Passport Advantage Online Web site.\n\nTivoli Storage Productivity Center is a suite of storage infrastructure management software that can centralize, automate, and simplify complex and heterogeneous storage environments.\n\nMore information\n\nTo access a wide variety of technical resources for this product, see Support for Tivoli Storage Productivity Center [http://www.ibm.com/software/sysmgmt/products/support/IBMTotalStorageProductivityCenterStandardEdition.html].\n\nHardware requirements for Tivoli Storage Productivity Center servers:\n\nFor Linux on Dual Intel\u00ae:\nMachine: Dual Intel class P4/Xeon 3.2 GHz processors.\nMinimum memory: 8 GB of RAM.\nDisk space: Approximately 80 GB of hard disk space. For installation, you need you need 10 GB of available disk space, 500 MB in the /tmp directory, and 1.3 GB in the /opt directory.\n\nHardware requirements for Tivoli Storage Productivity Center Storage Resource agents:\n\nFor Linux on Intel (x86Series):\nMachine: Pentium\u00ae 400 MHz processor or later.\nMinimum memory and space requirements to run:\n256 MB of RAM. Approximately 100 MB of hard disk space.\n\nFor Linux IBM System i\u00ae and IBM System p\u00ae:\nMachine: Minimum 400 MHz processor or later.\nMinimum memory and space requirements to run: * 256 MB of RAM.\nApproximately 100 MB of hard disk space.\n\nDownloading and assembling the product\n\n1. Log on to Passport Advantage [http://www-01.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm].\n 2. Click Customer sign in.\n 3. Enter your IBM ID and password, and click Sign in.\n 4. Click Software download and media access.\n 5. Click Download finder, and then click View all my downloads.\n 6. Navigate to find the Tivoli Storage Productivity Center download parts.\n 7. Select the Tivoli Storage Productivity Center parts that you require. The parts are described by platform in the tabbed sections of this document.\n 8. Click I Agree followed by Download Now.\n 9. When the download is complete, unpack Tivoli Storage Productivity Center Disk 1 images part 1, part 2, and part 3 to the same single temporary directory. Unpack all other parts into a separate temporary directory for each part.\n 10. Follow the instructions in the Quick Start Guide to install the product.\n\n[http://www.ibm.com/i/c.gif] [http://www.ibm.com/i/c.gif] AIX [http://www.ibm.com/support/docview.wss?&uid=swg24027303] [http://www.ibm.com/i/c.gif] HP-UX [http://www.ibm.com/support/docview.wss?&uid=swg24027349] [http://www.ibm.com/i/c.gif] Linux [http://www.ibm.com/support/docview.wss?&uid=swg24027350] [http://www.ibm.com/i/c.gif] Solaris [http://www.ibm.com/support/docview.wss?&uid=swg24027351] [http://www.ibm.com/i/c.gif] Windows [http://www.ibm.com/support/docview.wss?&uid=swg24027352] [http://www.ibm.com/i/c.gif] [http://www.ibm.com/i/c.gif] Supported platform\nLinux", "logical_doc_id": 0, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q043", "section_id": 9, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Downloadable parts This section provides the downloadable parts in the Tivoli Storage Productivity Center Standard Edition V4.2 eAssembly for Linux platforms. Refer to the following tables for details about what each part contains.\n\nRequired parts To install Tivoli Storage Productivity Center Standard Edition V4.2 on the Linux platform, you need to download the following parts in the order that they appear.\n\nThe Tivoli Storage Productivity Center Disk 1 images part 1, part 2, and part 3 must be downloaded to the same directory.\n\nCZK4KML.tar\n\nTivoli Storage Productivity Center, Disk 1 Part 1\n\nCZL02ML.tar\n\nTivoli Storage Productivity Center, Disk 1 Part 2\n\nCZL03ML.tar\n\nTivoli Storage Productivity Center, Disk 1 Part 3\n\nCZL04ML.tar\n\nTivoli Storage Productivity Center, Disk 1 Part 4\n\nCZK4EML.tar\n\nTivoli Storage Productivity Center, Storage Resource Agents for Windows\n\nCZM8PML.tar\n\nTivoli Storage Productivity Center, Storage Resource Agents for UNIX\n\nCZK4FML.tar\n\nTivoli Storage Productivity Center, National Language Support for Windows\n\nCZM8QML.tar\n\nTivoli Storage Productivity Center, National Language Support for UNIX\n\nCZ19NEN.tar\n\nDB2 Enterprise Server Edition, Version 9.7, AMD64 and Intel EM64T (x64)\n\nCZF7TEN.tar\n\nIBM Tivoli Monitoring Version 6.2.2 Fix Pack 2 Base, Linux, English\n\nCZF7VEN.tar\n\nIBM Tivoli Monitoring Version 6.2.2 Fix Pack 2 Agent, Multiplatform, English\n\nCZKX5ML.tar\n\nTivoli Storage Productivity Center National Language Support for IBM Tivoli Monitoring Version 6.2.2 Fix Pack 2\n\nCZ8MRML\n\nTivoli Storage Productivity Center for Replication Two Site License Key\n\nCZ8SBML\n\nTivoli Storage Productivity Center for Replication Two Site and Three Site License Key\n\n[http://www.ibm.com/i/c.gif] PREREQUISITES\n\nFor supported products and platforms, see Help to Find the Supported Products and Platforms: Interoperability Matrix Links [http://www.ibm.com/support/docview.wss?rs=40&context=SSBSEX&context=SSMN28&context=SSMMUP&context=SS8JB5&context=SS8JFM&q1=Help+to+Find+the+Supported+Products+and+Platforms+Interoperability+Matrix+Links&uid=swg21386446&loc=en_US&cs=utf-8&lang=en].\n\nINSTALLATION INSTRUCTIONS\nRetrieve a copy of the IBM Tivoli Storage Productivity Center Standard Edition Version 4 Release 2 Quick Start Guide. The Quick Start Guide is available with the product and is included on the Quick Start CD. Follow the instructions in the Quick Start Guide to install the product.\n\nURL LANGUAGE SIZE(Bytes) Tivoli Storage Productivity Center Quick Start [http://publib.boulder.ibm.com/infocenter/tivihelp/v4r1/topic/com.ibm.tpc_V42.doc/qstrtsed.pdf] US English 118753\nDOWNLOAD PACKAGE\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options Log on to Passport Advantage online 8/20/2010 US English 12081 HTTP [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\nTECHNICAL SUPPORT\n\nSee the Passport Advantage Online support at eCustomer Care contact information [http://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html].\n\nSee the Tivoli Productivity Center support site at IBM Tivoli Storage Productivity Center Standard Edition product support [http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Productivity_Center_Standard_Edition].", "logical_doc_id": 0, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q037", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This document describes how to download IBM WebSphere Message Broker Hypervisor Edition V8.0 eAssembly images from the Passport Advantage website.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q037", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "This document was created during November 2011 for V8.0 and updated during September 2012.\n\nTerminology\n\nWebSphere Message Broker Hypervisor Edition V8.0 is supplied in two eAssemblies: refer to the table below to identify the appropriate eAssembly image for your environment.\n\nRelated product documentation\n\nWebSphere Message Broker Hypervisor Edition contains WebSphere Message Broker and WebSphere MQ. The most up-to-date information about WebSphere Message Broker can be found in the US English WebSphere Message Broker V8.0 readme file at http://www.ibm.com/support/docview.wss?&uid=swg27006913 [http://www.ibm.com/support/docview.wss?&uid=swg27006913] [http://www-01.ibm.com/support/docview.wss?&uid=swg27006913]. Translated versions of the WebSphere Message Broker V8.0 readme file are available at: ftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/V8.0/ [ftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/V8.0/]. For specific documentation about Websphere Message Broker Hypervisor Edition V8.0, refer to the User's Guide and Reference (which is available for download in several languages). It can be accessed via the IBM Publications Center as follows: 1. Go to the IBM Publications Center [http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss] home page.\n 2. Select \"country/region/language to begin\" and click Go.\n 3. Click on \"Search for publications\" on the Navigation panel.\n 4. Type \"message broker hypervisor\" into the Search on field and click Go.\n 5. Click on the required language publication number or Online button to display the Download screen.\n\nDownloading the relevant eAssembly images from the Passport Advantage website\n\n1. From the eAssemblies table below, decide which of the eAssemblies you want to download.\n 2. Go to the Download package table below and follow the link to the Passport Advantage website.\n 3. Sign in to download all of the images that you need.\n 4. Unpack each of the images onto your system. Documentation is included in every image except for the Quick Start Guide.\n\neAssemblies table\n\neAssembly or eImage part number eAssembly or eImage Description CI9F5ML WebSphere Message Broker Hypervisor Edition V8.0.0.1 Quickstart Guide CRGY4ML WebSphere Message Broker Hypervisor Edition V8.0 Red Hat Enterprise Linux Server for x86 Multilingual eAssembly\n\nThis Assembly contains the following eImages:\u200b\u200b CI7TXML WebSphere Message Broker Hypervisor Edition V8.0.0.1 Red Hat Enterprise Linux Server for x86 VMWare Multilingual CI7TYML WebSphere Message Broker Hypervisor Edition V8.0.0.1 Red Hat Enterprise Linux Server for x86 IBM Workload Deployer and IBM Pure Application System Multilingual [/support/docview.wss?uid=swg24031059&aid=1] [/support/docview.wss?uid=swg24031059&aid=1] CRGY5ML WebSphere Message Broker Hypervisor Edition V8.0 for AIX Multilingual eAssembly", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q037", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "This Assembly contains the following eImages:\u200b\u200b CI7TKML WebSphere Message Broker Hypervisor Edition V8.0.0.1 for AIX IBM Workload Deployer Multilingual - AIX License Required CI7TMML WebSphere Message Broker Hypervisor Edition V8.0.0.1 for AIX mksysb Multilingual - AIX License required\n\nDOWNLOAD PACKAGE\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is Fix Central (FC)? [http://www-304.ibm.com/systems/support/fixes/en/fixcentral/help/faq_sw.html] IBM Passport Advantage Online 09 Dec 2011 English 1 FC [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm] [ ]\nPRODUCT ALIAS/SYNONYM\n WMB MB Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI\n\nFLASH (ALERT)", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q037", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q037", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2011-5320 CVE-2017-15670 CVE-2017-15671 CVE-2017-15804\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\nPRODUCT ALIAS/SYNONYM\n WMB HVE IIB HVE\n\n\u30d5\u30e9\u30c3\u30b7\u30e5(ALERTS)\n\n\u6982\u8981\n IIBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0 and WebSphere Message Broker Hypervisor Edition V7.0 \u3067\u63d0\u4f9b\u3055\u308c\u3066\u3044\u308b Red Hat Enterprise Linux (RHEL) \u306e GNU C library (glibc) \u306b\u8106\u5f31\u6027\u304c\u5b58\u5728\u3057\u307e\u3059\u3002(CVE-2015-0235).\n\n\u672c\u6587\nIIBM Integration Bus Hypervisor Edition V9.0, WebSphere Message Broker Hypervisor Edition V8.0 and WebSphere Message Broker Hypervisor Edition V7.0 \u3067\u63d0\u4f9b\u3055\u308c\u3066\u3044\u308b Red Hat Enterprise Linux (RHEL) \u306e GNU C library (glibc) \u306b\u8106\u5f31\u6027\u304c\u5b58\u5728\u3057\u307e\u3059\u3002(CVE-2015-0235).\nGNU C Library (glibc)\u306e__nss_hostname_digits_dots() \u95a2\u6570\u306b\u30d0\u30c3\u30d5\u30a1\u30aa\u30fc\u30d0\u30d5\u30ed\u30fc\u306e\u8106\u5f31\u6027\u304c\u767a\u898b\u3055\u308c\u307e\u3057\u305f\u3002(GHOST\u3068\u547c\u3070\u308c\u307e\u3059)\n\u3053\u308c\u306b\u3088\u308a\u3001\u9060\u9694\u306e\u7b2c\u4e09\u8005\u306b\u3088\u308b\u4efb\u610f\u306e\u30b3\u30fc\u30c9\u5b9f\u884c\u304c\u53ef\u80fd\u306b\u306a\u308b\u5834\u5408\u304c\u3042\u308a\u307e\u3059\u3002\n\n\u3010\u5bfe\u8c61\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u3011\n\n\u30fbIBM Integration Bus Hypervisor Edition V9.0\n\n\u30fbWebSphere Message Broker Hypervisor Edition V7.0/8.0\n\nIBM Integration Bus Hypervisor Edition V9.0 \u3068 WebSphere Message Broker Hypervisor Edition V8.0 \u306f\u3001Red Hat Enterprise Linux (RHEL) Server 6.2\u3092\u540c\u68b1\u3057\u3066\u3044\u307e\u3059\u3002\nWebSphere Message Broker Hypervisor Edition V7.0\u306f\u3001 Red Hat Enterprise Linux (RHEL) Server 5.5\u3092\u540c\u68b1\u3057\u3066\u3044\u307e\u3059\u3002\nHypervisor Edition \u3067\u306f\u306a\u304f\u3001IBM Integration Bus\u3082\u3057\u304fWebSphere Message Broker\u3092\u4f7f\u7528\u3055\u308c\u3066\u3044\u308b\u5834\u5408\u3001\u8a72\u5f53\u3044\u305f\u3057\u307e\u305b\u3093\u3002\n\n\u3010\u5bfe\u5fdc\u7b56/\u8efd\u6e1b\u7b56\u3011\nRed Hat Enterprise Linux (RHEL)\u306e\u4fee\u6b63\u3092\u5165\u624b\u3057\u3001\u5c0e\u5165\u3057\u3066\u304f\u3060\u3055\u3044\u3002\n\n\u3010\u53c2\u8003\u60c5\u5831\u3011\nRed Hat Customer Portal - GHOST vulnerability [https://access.redhat.com/articles/1332213]\n\n[IBM\u30b5\u30a4\u30c8]\n\u3053\u306e\u6587\u66f8\u306f\u3001\u7c73\u56fd IBM \u793e\u306e\u8cc7\u6599\u3092\u7ffb\u8a33\u3057\u305f\u53c2\u8003\u6587\u66f8\u3067\u3059\u3002\u7ffb\u8a33\u5143\u306e\u6587\u66f8\u306f\u3001\u4ee5\u4e0b\u306e\u30ea\u30f3\u30af\u3088\u308a\u3054\u53c2\u7167\u304f\u3060\u3055\u3044\u3002\nAction required for IBM WebSphere MQ Hypervisor Edition for Red Hat Enterprise Linux Server for the GNU C library (glibc) vulnerability (CVE-2015-0235) [http://www.ibm.com/support/docview.wss?uid=swg21695676]\n\n[CVSS\u60c5\u5831]\n\u72ec\u7acb\u884c\u653f\u6cd5\u4eba \u60c5\u5831\u51e6\u7406\u63a8\u9032\u6a5f\u69cb: \u5171\u901a\u8106\u5f31\u6027\u8a55\u4fa1\u30b7\u30b9\u30c6\u30e0CVSS\u6982\u8aac [http://www.ipa.go.jp/security/vuln/CVSS.html]\nJVN iPedia: CVSS\u8a08\u7b97\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u65e5\u672c\u8a9e\u7248 [http://jvndb.jvn.jp/cvss/ja.html]\nglibc \u306e\u8106\u5f31\u6027\u5bfe\u7b56\u306b\u3064\u3044\u3066(CVE-2015-0235)\uff1aIPA \u72ec\u7acb\u884c\u653f\u6cd5\u4eba \u60c5\u5831\u51e6\u7406\u63a8\u9032\u6a5f\u69cb [http://www.ipa.go.jp/security/announce/20150129-glibc.html]\n\n\u3010\u304a\u554f\u5408\u305b\u5148\u3011\n\u6280\u8853\u7684\u306a\u5185\u5bb9\u306b\u95a2\u3057\u3066\u3001\u30b5\u30fc\u30d3\u30b9\u5951\u7d04\u306e\u3042\u308b\u304a\u5ba2\u69d8\u306fIBM\u30b5\u30fc\u30d3\u30b9\u30fb\u30e9\u30a4\u30f3\u306b\u304a\u554f\u3044\u5408\u308f\u305b\u304f\u3060\u3055\u3044\u3002\nIBM \u30b5\u30fc\u30d3\u30b9\u30fb\u30e9\u30a4\u30f3 [http://www.ibm.com/jp/news/20070420001.html]\n\n\u95a2\u9023\u60c5\u5831\n An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21695798 ]\n\nIIB WMB FLASH (ALERT)", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q037", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q037", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2 which is vulnerable to\nCVE-2017-16546\n\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\n\nFLASH (ALERT)", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q037", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q037", "section_id": 3, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2015-8982, CVE-2015-8983, CVE-2015-8984, CVE-2015-8985, CVE-2017-10995, CVE-2017-10928, CVE-2017-11141, CVE-2017-11166, CVE-2017-11170, CVE-2017-11188, CVE-2017-11310, CVE-2017-11352, CVE-2017-11360, CVE-2017-11446, CVE-2017-11447, CVE-2017-11448, CVE-2017-11449, CVE-2017-11450, CVE-2017-11478, CVE-2017-11505, CVE-2017-11522, CVE-2017-11523, CVE-2017-11524, CVE-2017-11525, CVE-2017-11526, CVE-2017-11527, CVE-2017-11528, CVE-2017-11529, CVE-2017-11530, CVE-2017-11531, CVE-2017-11532, CVE-2017-11533, CVE-2017-11534, CVE-2017-11535, CVE-2017-11536, CVE-2017-11537, CVE-2017-11538, CVE-2017-11539, CVE-2017-11540, CVE-2017-11639, CVE-2017-11640 and CVE-2017-11644\n\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2.\n\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\nPRODUCT ALIAS/SYNONYM\n WMB HVE IIB HVE", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q139", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Websphere Application Server (WAS) is shipped as a component of Tivoli Netcool/OMNIbus WebGUI. Information about a security vulnerability affecting WAS has been published in a security bulletin.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q139", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Please consult the security bulletin Potential Privilege Escalation in WebSphere Application Server Admin Console (CVE-2017-1731) [http://www.ibm.com/support/docview.wss?uid=swg22012345] for vulnerability details and information about fixes.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q139", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Principal Product and Version(s) Affected Supporting Product and Version WebGUI 7.4.0 GA and FP embedded Websphere Application Server 7.0 WebGUI 8.1.0 GA and FP Websphere Application Server 8.5\nPlease also note the end of support announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS917-138/index.html&lang=en&request_locale=en] from 12 September 2017 for selected Netcool product versions. You can find detailed information on whether the product version you have installed in your environment is affected by this end of service announcement by following the Netcool End of Support Knowledge Collection [https://www-01.ibm.com/support/entdocview.wss?uid=swg22009231] . If your product version is affected, IBM recommend to upgrade your product version to the latest supported version of your product. Please contact your IBM account manager for any question you might have or for any assistance you may require for upgrading an end of service announced offering. GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q139", "section_id": 3, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q139", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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 6 February 2018: Original version published\nThe 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\nPSIRT SECURITY BULLETIN", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q139", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere Application Server (WAS) is shipped as a component of IBM Security Identity Manager (ISIM). Information about a security vulnerability affecting IBM WebSphere Application Server has been published in a security bulletin.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q139", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Please consult the security bulletinSecurity Bulletin: Privilege Escalation Vulnerability in WebSphere Application Server (CVE-2017-1151) [http://www-01.ibm.com/support/docview.wss?uid=swg21999293]for vulnerability details and information about fixes.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q139", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Product Version WebSphere version ISIM 6.0 WAS v7.0, v8.5, v8.5.5 GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q139", "section_id": 3, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q139", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nThe 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.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q139", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere Application Server is shipped as a component of IBM PureApplication System. Information about a security vulnerability affecting IBM WebSphere Application Server has been published in a security bulletin.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q139", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Consult the security bulletin Privilege Escalation Vulnerability in WebSphere Application Server (CVE-2017-1151) [http://www-01.ibm.com/support/docview.wss?uid=swg21999293].\nThe WebSphere fixes can be installed using the IBM PureApplication System\u2019s Installation Manager Repository feature.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q139", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Principal Product and Version(s) Affected Supporting Product and Version PureApplication System versions 2.1, and 2.2 IBM WebSphere Application Server 8.0.0.0\nIBM WebSphere Application Server 8.5.0.0\nIBM WebSphere Application Server 8.5.5.0\nIBM WebSphere Application Server 9.0.0.0 GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q139", "section_id": 3, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q139", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 20 March 2017: Original Version Published\nThe 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\nCVE-2017-1731 SECURITY BULLETIN", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q139", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere Application Server (WAS) is shipped as a component of IBM Rational ClearCase. Information about a security vulnerability affecting WAS has been published in a security bulletin.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q139", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Refer to the security bulletin(s) listed in the Remediation/Fixes section.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q139", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Rational ClearCase, ClearCase Remote Client (CCRC) WAN server/CM Server component.\n\nVersions 8.0.0.x, 8.0.1.x, 9.0.0.x, 9.0.1.x:\n*", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q139", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Refer to the following security bulletins for vulnerability details and information about fixes addressed by IBM WebSphere Application Server (WAS) which is shipped with IBM Rational ClearCase.\n\nPrincipal Product and Version(s) Affected Supporting Product and Version Affected Supporting Product Security Bulletin IBM Rational ClearCase, versions 8.0.0.x, 8.0.1.x, 9.0.0.x, 9.0.1.x IBM WebSphere Application Server 7.0, 8.0, 8.5 and 9.0. Security Bulletin: Potential Privilege Escalation in WebSphere Application Server Admin Console (CVE-2017-1731) [http://www.ibm.com/support/docview.wss?uid=swg22012345]\nClearCase Versions Applying the fix 8.0.0.x, 8.0.1.x, 9.0.0.x, 9.0.1.x 1. Determine the WAS version used by your CCRC WAN server. Navigate to the CCRC profile directory (either the profile you specified when installing ClearCase, or /common/ccrcprofile), then execute the script: bin/versionInfo.sh (UNIX) or bin\\versionInfo.bat (Windows). The output includes a section \"IBM WebSphere Application Server\". Make note of the version listed in this section.\n 2. Identify the latest available fix (per the bulletin listed above) for the version of WAS used for CCRC WAN server.\n 3. Apply the appropriate WebSphere Application Server fix directly to your CCRC WAN server host. No ClearCase-specific steps are necessary.\n\nFor 7.0.x, 7.1.x and earlier releases, IBM recommends upgrading to a fixed, supported version/release/platform of the product. WORKAROUNDS AND MITIGATIONS\nNone.", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q139", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q139", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q139", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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\n1 February 2018: Original version published\nThe 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.", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q139", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere Application Server is shipped with BM Integrated Information Core. Information about a security vulnerability affecting IBM WebSphere Application Server has been published in a security bulletin.", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q139", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Consult the security bulletin, Security Bulletin: Privilege Escalation Vulnerability in WebSphere Application Server (CVE-2017-1151) [http://www.ibm.com/support/docview.wss?uid=swg21999293], [http://www.ibm.com/support/docview.wss?uid=swg21991469] for vulnerability details and information about fixes.", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q139", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Principal Product and Version(s) Affected Supporting Product IBM Integrated Information Core V1.5, V1.5.0.1, and V1.5.0.2 IBM WebSphere Application Server REMEDIATION/FIXES\nDownload the correct version of the fix from the following link: Security Bulletin: Privilege Escalation Vulnerability in WebSphere Application Server (CVE-2017-1151) [http://www.ibm.com/support/docview.wss?uid=swg21999293]. Installation instructions for the fix are included in the readme document that is in the fix package.", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q139", "section_id": 3, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q139", "section_id": 4, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q139", "section_id": 5, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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 17 March 2017: Original Version Published\nThe 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.", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q172", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "When creating a new Filing report or rolling forward an existing one, the Reference Dates available in the CDM User Interface are newer than the required value.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q172", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Reference Dates in version 10.2.4 are based on the current CDM server date.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q172", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "IBM Cognos Disclosure Management 10.2.4 IF16", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q172", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "1. Create a new Filing report or roll forward an existing one.\n2. In the wizard, check if the required Reference Date is displayed.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q172", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "This issue is solved in CDM version 10.2.5 by the addition of a \"Custom\" option field. Any Reference Date can be inputted by the user, as required.\n\nIf upgrading to 10.2.5 is not possible at this time, please contact CDM support for further assistance.\n\nDOWNLOADABLE FILES", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q172", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This page describes how to download IBM Cognos Disclosure Management.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q172", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "IBM Cognos Disclosure Management is a unified financial governance solution that focuses on improving financial processes and controls, particularly in the final stages before disclosure.\n\nDownloading and assembling the product\n\nDownload all of the parts that you need, both required and optional.\n\n1. Access the IBM Passport Advantage\u00ae website [http://www.ibm.com/software/passportadvantage] (www.ibm.com/software/passportadvantage). [http://%20www.google.com/]\n Tip: If you get an error, try using a different web browser to access Passport Advantage.\n 2. Sign in and navigate to the software downloads page.\n 3. Find the eAssembly or eAssemblies for your product.\n The eAssembly part numbers to search for are listed in this document. An eAssembly groups individual product parts (eImages) together.\n 4. Download all parts in an eAssembly by selecting the check box beside the name of the eAssembly or download individual parts of an eAssembly by expanding the eAssembly and selecting the check box for a part.\n When the download finishes, a Download Complete message displays. The location of the downloaded files displays in the message window.\n 5. Unpack each of the parts into a single, temporary directory on your system.\n 6. Follow the instructions in the IBM Cognos Disclosure Management Version 10.2.5 Installation Guide to install the product.\n\nIf you need help with downloading a product, contact eCustomer Care. There are links to eCustomer Care on the IBM Passport Advantage website.\n\nClick or double-click the arrow preceding the product name to see the product parts to install.\n- [http://www.ibm.com/i/c.gif] IBM Cognos Disclosure Management 10.2.5 Microsoft Windows Multilingual eAssembly\n\nParts and Platforms Details eAssembly IBM Cognos Disclosure Management 10.2.5 Microsoft Windows Multilingual eAssembly [/support/docview.wss?uid=swg24041034&aid=1] CRY1GML Parts and Platforms Details eImage IBM Cognos Disclosure Management 10.2.5 Microsoft Windows Multilingual Required CN7MBML\n- [http://www.ibm.com/i/c.gif] IBM Cognos Disclosure Management with Data Aggregation 10.2.5 Microsoft Windows Multilingual eAssembly", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q172", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Parts and Platforms Details eAssembly IBM Cognos Disclosure Management with Data Aggregation 10.2.5 Microsoft Windows Multilingual eAssembly [/support/docview.wss?uid=swg24041034&aid=1] CRY1HML Parts and Platforms Details eImage IBM Cognos Disclosure Management with Data Aggregation 10.2.5 Microsoft Windows Multilingual Required CN7MCML IBM Cognos TM1 32-bit 10.2.2 Microsoft Windows Multilingual Required CIYF6ML IBM Cognos TM1 64-bit 10.2.2 Microsoft Windows Multilingual Required CIYF7ML IBM Cognos TM1 Client 32-bit 10.2.2 Microsoft Windows Multilingual Required CIYF8ML IBM Cognos TM1 Client 64-bit 10.2.2 Microsoft Windows Multilingual Required CIYF9ML IBM Cognos TM1 10.2.2 AIX Multilingual Required CIYF3ML IBM Cognos TM1 10.2.2 Linux x86-64 Multilingual Required CIYF4ML IBM Cognos TM1 10.2.2 Linux on System z Multilingual Required CIYF5ML\n- [http://www.ibm.com/i/c.gif] IBM Cognos Disclosure Management 10.2: Cognos Financial Statement Reporting (FSR) 6.6.1 Microsoft Windows Multilingual eAssembly\n\nParts and Platforms Details eAssembly IBM Cognos Disclosure Management 10.2: Cognos Financial Statement Reporting (FSR) 6.6.1 Microsoft Windows Multilingual eAssembly [/support/docview.wss?uid=swg24041034&aid=1] CRY1IML Parts and Platforms Details eImage IBM Cognos Financial Statement Reporting (FSR) 6.6.1 Microsoft Windows Multilingual Required CI8PYML\n- [http://www.ibm.com/i/c.gif] IBM Cognos Disclosure Management EDGAR Engine 10.2 eAssembly\n\nParts and Platforms Details eAssembly IBM Cognos Disclosure Management EDGAR Engine 10.2 eAssembly [/support/docview.wss?uid=swg24041034&aid=1] CRK8DML Parts and Platforms Details eImage IBM Cognos Disclosure Management EDGAR Engine Enablement Key 10.2 Required CIL3DZZ IBM Cognos Financial Statement Reporting (FSR) EDGAR Enablement Script 6.6.1 Microsoft Windows English Required CI8PXEN\n- [http://www.ibm.com/i/c.gif] IBM Cognos Disclosure Management XBRL User 10.2 eAssembly\n\nParts and Platforms Details eAssembly IBM Cognos Disclosure Management XBRL User 10.2 eAssembly [/support/docview.wss?uid=swg24041034&aid=1] CRK8CML Parts and Platforms Details eImage IBM Cognos Disclosure Management XBRL Enablement Key 10.2 Required CIL3CZZ IBM Cognos Financial Statement Reporting (FSR) XBRL Enablement Script 6.6.1 Microsoft Windows English Required CI8PWEN\n\nDOWNLOADABLE FILES", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q172", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "This page describes how to download IBM\u00ae Cognos\u00ae Disclosure Management.", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q172", "section_id": 3, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "IBM Cognos Disclosure Management is a unified financial governance solution that focuses on improving financial processes and controls, particularly in the final stages before disclosure.\n\nTo download a product, go to the IBM Passport Advantage\u00ae Web Site [http://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/sdma/SDMA?PO=DOWNLOAD_FIND_BY_PART_NUMBER] and then:\n\n1. Do one of the following:\n If you are a returning customer, sign in.\n If you are a new customer, register.\n 2. Under Find it fast, click Download software.\n 3. If the Software download & media access window appears, click I agree.\n 4. In the Find downloads & media window, select the download you want and click Continue.\n 5. Under Select criteria, select a language and one or more platforms.\n 6. Under Download options, select the options you want, and click Continue.\n 7. Under Review \u201cCurrent version\u201d downloads, expand Current version and under Description, select the download you want, expand it and select the items you want.\n 8. If applicable, under Select optional downloads, expand and select the items you want.\n 9. Under Review downloading specifics, update the Download method or the Download location, if you want, and then click I agree, and click Download now.\n 10. In the Initial Setup window, change the Default download location, if you want.\n 11. If you are prompted, click OK to create the directory where you want the downloaded items to be stored.\n 12. Click OK to begin the download.\n\nWhen the download has finished, Download complete appears in the Download Director window. The required and optional parts for each product are listed and described in detail. There is an option to download each licensed eAssembly. Each eAssembly contains all of the required and optional downloads needed for a particular product and platform combination.\n\nDownloading and assembling the product *\n\n1. Download all of the parts that you need, both required and optional.\n2. Unpack each of the parts into a single temporary directory on your system.\n3. Follow the instructions in the Quick Start Guide to install the product. [/support/docview.wss?uid=swg24033377&aid=1] [/support/docview.wss?uid=swg24033377&aid=1] The following tables list all parts available for IBM Cognos Disclosure Management 10.2.0.0.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q172", "section_id": 3, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "The following parts are applicable to IBM Cognos Disclosure Management 10.2.0 Microsoft Windows Multilingual: Parts and Platforms Details eImage IBM Cognos Disclosure Management 10.2.0 Microsoft Windows Multilingual Required CIC75ML\nThe following parts are applicable to IBM Cognos Disclosure Management Advanced 10.2.0 Microsoft Windows Multilingual:\n\nParts and Platforms Details eImage IBM Cognos Disclosure Management Quick Start Guide 10.2.0 Multilingual Required CIC74ML IBM Cognos Disclosure Management 10.2.0 Microsoft Windows Multilingual Required CIC75ML IBM Cognos TM1 32-bit 10.1.0 Microsoft Windows Multilingual Required CI5TAML IBM Cognos TM1 64-bit 10.1.0 Microsoft Windows Multilingual Required CI5TBML IBM Cognos TM1 Client 10.1.0 Microsoft Windows Multilingual Required CI5TCML IBM Cognos TM1 64-bit 10.1.0 AIX Multilingual Required CI5T7ML IBM Cognos TM1 64-bit 10.1.0 Linux x86 Multilingual Required CI5T8ML\nThe following parts are applicable to IBM Cognos Financial Statement Reporting (FSR) EDGAR Engine for IBM Cognos Disclosure Management 10.2.0 Microsoft Windows Multilingual:\n\nParts and Platforms Details eImage IBM Cognos Financial Statement Reporting (FSR) 6.6.1 for IBM Cognos Disclosure Management 10.2.0 Microsoft Windows Multilingual Required CIC76ML IBM Cognos Financial Statement Reporting (FSR) EDGAR Enablement Script 6.6.1 Microsoft Windows English Required CI8PXEN\nThe following parts are applicable to IBM Cognos Financial Statement Reporting (FSR) XBRL User for IBM Cognos Disclosure Management 10.2.0 Microsoft Windows English:\n\nParts and Platforms Details eImage IBM Cognos Financial Statement Reporting (FSR) 6.6.1 for IBM Cognos Disclosure Management 10.2.0 Microsoft Windows Multilingual Required CIC76ML IBM Cognos Financial Statement Reporting (FSR) XBRL Enablement Script 6.6.1 Microsoft Windows English Required CI8PWEN\n\nDOWNLOADABLE FILES", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q172", "section_id": 4, "heading": "ABSTRACT", "parent": null, "text": "This page describes how to download IBM Cognos Disclosure Management.", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q172", "section_id": 5, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "IBM Cognos Disclosure Management is a unified financial governance solution that focuses on improving financial processes and controls, particularly in the final stages before disclosure.\n\nDownloading and assembling the product\n\nDownload all of the parts that you need, both required and optional.\n\n1. Access the IBM Passport Advantage\u00ae website [http://www.ibm.com/software/passportadvantage] (www.ibm.com/software/passportadvantage). [http://%20www.google.com/]\n Tip: If you get an error, try using a different web browser to access Passport Advantage.\n 2. Sign in and navigate to the software downloads page.\n 3. Find the eAssembly or eAssemblies for your product.\n The eAssembly part numbers to search for are listed in this document. An eAssembly groups individual product parts (eImages) together.\n 4. Download all parts in an eAssembly by selecting the check box beside the name of the eAssembly or download individual parts of an eAssembly by expanding the eAssembly and selecting the check box for a part.\n When the download finishes, a Download Complete message displays. The location of the downloaded files displays in the message window.\n 5. Unpack each of the parts into a single, temporary directory on your system.\n 6. Follow the instructions in the IBM Cognos Disclosure Management Version 10.2.3 Installation Guide to install the product.\n\nIf you need help with downloading a product, contact eCustomer Care. There are links to eCustomer Care on the IBM Passport Advantage website.\n\nClick or double-click the arrow preceding the product name to see the product parts to install.\n- [http://www.ibm.com/i/c.gif] IBM Cognos Disclosure Management 10.2.3 Microsoft Windows Multilingual eAssembly\n\nParts and Platforms Details eAssembly IBM Cognos Disclosure Management 10.2.3 Microsoft Windows Multilingual eAssembly [/support/docview.wss?uid=swg24037296&aid=1] CRRH0ML Parts and Platforms Details eImage IBM Cognos Disclosure Management Quick Start Guide 10.2.3 Multilingual Optional CIYL4ML IBM Cognos Disclosure Management 10.2.3 Microsoft Windows Multilingual Required CIYL5ML IBM Cognos Disclosure Management Samples 10.2.3 Microsoft Windows Multilingual Required CIYL3ML IBM Cognos Financial Statement Reporting (FSR) 6.6.1 Microsoft Windows Multilingual Required CIPY8ML\n- [http://www.ibm.com/i/c.gif] IBM Cognos Disclosure Management with Data Aggregation 10.2.3 Microsoft Windows Multilingual eAssembly", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q172", "section_id": 5, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Parts and Platforms Details eAssembly IBM Cognos Disclosure Management with Data Aggregation 10.2.3 Microsoft Windows Multilingual eAssembly [/support/docview.wss?uid=swg24037296&aid=1] CRRH1ML Parts and Platforms Details eImage IBM Cognos Disclosure Management Quick Start Guide 10.2.3 Multilingual Optional CIYL4ML IBM Cognos Disclosure Management with Data Aggregation 10.2.3 Microsoft Windows Multilingual Required CIYL6ML IBM Cognos Disclosure Management Samples 10.2.3 Microsoft Windows Multilingual Required CIYL3ML IBM Cognos Financial Statement Reporting (FSR) 6.6.1 Microsoft Windows Multilingual Required CIPY8ML IBM Cognos TM1 32-bit 10.2.2 Microsoft Windows Multilingual Required CIYF6ML IBM Cognos TM1 64-bit 10.2.2 Microsoft Windows Multilingual Required CIYF7ML IBM Cognos TM1 Client 32-bit 10.2.2 Microsoft Windows Multilingual Required CIYF8ML IBM Cognos TM1 Client 64-bit 10.2.2 Microsoft Windows Multilingual Required CIYF9ML IBM Cognos TM1 10.2.2 AIX Multilingual Required CIYF3ML IBM Cognos TM1 10.2.2 Linux x86-64 Multilingual Required CIYF4ML IBM Cognos TM1 10.2.2 Linux on System z Multilingual Required CIYF5ML\n- [http://www.ibm.com/i/c.gif] IBM Cognos Disclosure Management XBRL User 10.2 eAssembly\n\nParts and Platforms Details eAssembly IBM Cognos Disclosure Management XBRL User 10.2 eAssembly [/support/docview.wss?uid=swg24037296&aid=1] CRK8CML Parts and Platforms Details eImage IBM Cognos Disclosure Management XBRL Enablement Key 10.2 Required CIL3CZZ IBM Cognos Financial Statement Reporting (FSR) XBRL Enablement Script 6.6.1 Microsoft Windows English Required CI8PWEN\n- [http://www.ibm.com/i/c.gif] IBM Cognos Disclosure Management EDGAR Engine 10.2 eAssembly\n\nParts and Platforms Details eAssembly IBM Cognos Disclosure Management EDGAR Engine 10.2 eAssembly [/support/docview.wss?uid=swg24037296&aid=1] CRK8DML Parts and Platforms Details eImage IBM Cognos Disclosure Management EDGAR Engine Enablement Key 10.2 Required CIL3DZZ IBM Cognos Financial Statement Reporting (FSR) EDGAR Enablement Script 6.6.1 Microsoft Windows English Required CI8PXEN", "logical_doc_id": 1, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q172", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "A specific usage scenario of IBM Cognos Disclosure Management could allow an Excel Macro execution on the client machine.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q172", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-6077 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6077]\nDESCRIPTION: IBM Cognos Disclosure Management could allow a remote attacker to insert a specially crafted Macro inside an exported CSV file.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117536 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117536] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L)", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q172", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Cognos Disclosure Management 10.2.0 - 10.2.6", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q172", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Cognos Disclosure Management 10.2.5 Interim Fix 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24042831]\nCognos Disclosure Management 10.2.6 Interim Fix 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24042881]\n\nUsers of Cognos Disclosure Management 10.2.4 and previous are advised to contact Customer Support.", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q172", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q172", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT\nVulnerability reported to IBM by Ary Dobrovolskiy, Penetration Tester & Cyber Security Consultant, Citadel Consulting.\n\nCHANGE HISTORY\n Original Publish Date: October 20, 2016\nThe 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.", "logical_doc_id": 2, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q137", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Multiple security vulnerabilities exist in the IBM\u00ae Runtime Environment Java\u2122 Technology Edition 6.0.16.26 (and earlier) used by WebSphere Message Broker, and the IBM\u00ae Runtime Environment Java\u2122 Technology Edition 7.0.9.40 (and earlier) used by WebSphere Message Broker and IBM Integration Bus, and the IBM\u00ae Runtime Environment Java\u2122 Technology Edition 7.1.3.40 (and earlier) used by IBM Integration Bus. These issues were disclosed as part of the IBM Java SDK updates in July 2016.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q137", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-3485 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3485]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE and Java SE Embedded related to the Networking component has no confidentiality impact, low integrity impact, and no availability impact.\nCVSS Base Score: 2.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/115273 [https://exchange.xforce.ibmcloud.com/vulnerabilities/115273] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q137", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Integration Bus V10, V9\n\nWebSphere Message Broker V8", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q137", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Product VRMF APAR Remediation/Fix IBM Integration Bus V10 IT16743 The APAR is available in fix pack 10.0.0.7\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24043068 [https://www-304.ibm.com/support/docview.wss?uid=swg24043068] IBM Integration Bus V9 IT16743 The APAR is available in fix pack 9.0.0.7\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043227 [http://www-01.ibm.com/support/docview.wss?uid=swg24043227] WebSphere Message Broker V8 IT16743 An interim fix is available from IBM Fix Central for all platforms\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT16743 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=%20IT16743]\n\nIf you are running with a fix pack earlier than 8.0.0.7 and do not have IT03599 applied then you must upgrade your fix pack level to 8.0.0.7 or higher, or request IT16735 via IBM support.\n\nAPAR IT16743 is targeted to be available in fix pack 8.0.0.9\nFor unsupported versions of the product IBM recommends upgrading to a fixed, supported version/release/platform of the product.\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at :\nhttp://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308]", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q137", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q137", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]\nIBM Java SDK Security Bulletin [http://www.ibm.com/support/docview.wss?uid=swg21986642]", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q137", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 30 Mar 2017 - Original version Published\nThe 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.", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q137", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "#\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker 8.0\nPRODUCT ALIAS/SYNONYM\n WMB IIB\n\nFIX README", "logical_doc_id": 0, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q137", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "Readme file for IBM Financial Transaction Manager for z/OS Version 3.0.0.7\nProduct/Component Release: 3.0.0\nPTF number: UI47207", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q137", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Contents:\nDownload location\nPrerequisites and co-requisites\nWhat's new in FTM 3.0.0.7\nKnown issues\nInstallation information\nInstalling FTM v3.0.0.7 to create a new installation\nTo update an existing V3.0.0 runtime installation\nUninstalling if necessary\nList of fixes\n\nDownload location\n\nDownload IBM(R) Financial Transaction Manager for z/OS Version 3.0.0.7 from the following location:\n\nIBM Shopz [https://www14.software.ibm.com/webapp/ShopzSeries/ShopzSeries.jsp?action=orderPTFs&openv=z/OS&ptf=UI40706]\n\nPrerequisites and co-requisites\n\nBefore downloading FTM v3.0.0.7, perform the following steps:\nEnsure that your system meets all of the system requirements: http://www.ibm.com/software/industry/financial-transaction-manager/requirements [http://www.ibm.com/software/industry/financial-transaction-manager/requirements]\nThis action prevents technical problems that might occur after the installation and configuration of the fix.\nReview the Flashes and open Authorized Problem Analysis Reports (APARs) on the Financial Transaction Manager product support Web site: https://support.podc.sl.edst.ibm.com/support/home/product/W823356Z48952D56/IBM_Financial_Transaction_Manager [https://support.podc.sl.edst.ibm.com/support/home/product/W823356Z48952D56/IBM_Financial_Transaction_Manager]\nOpen APARs describe defects that are not yet addressed in a fix, and they might contain workarounds that will impact your use of FTM v3.0.0.7.\nRead the \"Known issues\" section of this readme.\nYou need to have a file system with 200MB of free space to contain the fix files.\nEnsure that you have the free space required to install the fix.\nIf you already have an FTM product installed and have obtained special fixes, contact IBM(R) support to determine whether you need an updated version of the fixes before you install FTM v3.0.0.7.\nThis helps to ensure that your system is in a consistent state and that no special fixes are lost. back to Contents", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q137", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "What's new in FTM 3.0.0.7 * Extended Resend Support Enhancements have been made to the resend capabilities of transactions / transmissions, especially in the context of optimization settings where the logging of some objects may be avoided.\nSupport for Devolved Timeout Alerts Enhancements have been made to the Outbound Transactions FSM to reduce the number of objects in a timed-out alert state.\nRefactoring of the Outbound Transaction FSM The Outbound Transaction FSM diagram has been split into 3 smaller diagrams in the interest of legibility. These diagrams include the Outbound Transaction, Outbound Transaction(Timeout) & Outbound Transaction(Devolved).\nGeneration of Subflow and ESQL templates. Support has been added to the Model Tooling component to enable the generation of ESQL and Subflow files from an FTM model.\nFiner support for control of rollback on an Inbound Mapper abort. Support has been added at the interface(Channel) level to control rollback in the event of an Inbound Mapper abort.\nThe Purge Utility has been enhanced.\n\nSee the \"Financial Transaction Manager -> Financial Transaction Manager overview -> What's new in FTM\" section of the \"FTM for z/OS v3.0.0 Knowledge Center\" available at\nIBM Financial Transaction Manager for z/OS V3.0.0 documentation [https://www.ibm.com/support/knowledgecenter/SSRH32_3.0.0/SSRH32_3.0.0welcome.html]\nback to Contents\n\nKnown issues\nIssue 1 Summary :\n\nCustomers using IBM WebSphere Transformation Extender(WTX) version 8.4.1.2 who use native schema and choice sequence iterations are unable to access iterations of a particular sequence group.\n\nResolution :\n\nThe fix for this issue (APAR PI31636) is available in WTX v8.4.1.3.\n\nIssue 2\n\nSummary :\n\nCustomers using IBM Integration Bus (IIB) version 9.0.0.x may experience the following BIP2930E error when deploying or restarting the broker.\n\nRecoverableException BIP2930E: A function or procedure was called but the value supplied for the ''cAppVer'' parameter was of type ''BOOLEAN'' but the function/procedure expects value of type ''CHARACTER'' Functions and procedures require an exact matching between the data type of values supplied as parameters and the data type in its definition.\n\nResolution :\n\nThe fix for this issue (IIB APAR IT06286) is available in IIB Maintenance Level 9.0.0.4.\n\nIssue 3\n\nSummary :\n\nCustomers using IBM Integration Bus (IIB) version 9.0.0.3 may experience the following BIP2503E when executing customer flows if propagating from a node after exiting a FOR loop acting on a shared variable.", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q137", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "RecoverableException BIP2503E: Propagate with a SHARED variable lock held by FOR statement.\n\nResolution :\n\nThe fix for this issue (IIB APAR IT07974) is available in IIB Maintenance Level 9.0.0.4.\n\nIssue 4\n\nSummary :\n\nCustomers using IBM Integration Bus (IIB) version 9.0.0.5 may experience the following issue:\n\nIf a user has a REFERENCE variable declared at the module or schema level which points at either OutputRoot, OutputLocalEnvironment or OutputExceptionList and performs a PROPAGATE without specifying DELETE NONE in a compute node then it is not defined what the REFERENCE variable will be left pointing at. After the PROPAGATE the Output trees are deleted and the REFERENCE variables should be reset to point at the root of the newly created trees.The module and schema level reference variables are not being reset and are thus left to point at the original syntax element which they were pointing at which will now have been reset leading to unexpected results.\n\nResolution :\n\nThe fix for this issue (IIB APAR IT14426) is available in IIB Maintenance Level 9.0.0.6.\n\nIssue 5\n\nSummary :\n\nCustomers using any Broker level from v7.x may experience inconsistent validation results when using FTM Channel based validation and/or IIB in ESQL parser validation.\n\nResolution :\n\nIIB APAR IT14075 has been raised for this issue.\n\nIssue 6\n\nSummary :\n\nFTM SWIFT SR2016 WTX maps will not work with FTM SWIFT SR2015 WTX maps at a single broker instance together at the same time.\n\nThe reason is that IBM Transformation Extender has changed the JVCWrapper code with the new Financial Payments Pack for SWIFT 9.0.1 release and it is not compatible with the earlier Pack for SWIFT releases.\nTherefore using multiple Pack for SWIFT versions at the same time in a specific instance of a program is not supported.\n\nIssue 8\n\nSummary :\n\nDebulking and Bulking Sample application :\n\nIf the FTM database timezone is set to UTC and the runtime (IIB/Broker) timezone it set to a different timezone then bulking will not occur(ref:55056).\n\nInstallation information\n\nBefore proceeding with the installation process, view the online version of this readme file to check if information has changed since the\nreadme file was downloaded: http://www.ibm.com/support/docview.wss?uid=swg22002334 [http://www.ibm.com/support/docview.wss?uid=swg22002334]\n\nUse the normal SMP/E process to install this PTF.\n\nInstalling FTM v3.0.0.7 to create a new runtime installation", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q137", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Follow the instructions in the \"Financial Transaction Manager -> Installing\" section of the \"FTM for z/OS v3.0.0 Knowledge Center\" available at\nIBM Financial Transaction Manager for z/OS V3.0.0 documentation [https://www.ibm.com/support/knowledgecenter/SSRH32_3.0.0/SSRH32_3.0.0welcome.html] back to Contents To update an existing v3.0.0.x runtime installation\n\nFollow the instructions in the \"Financial Transaction Manager -> Planning -> Migration\" section of the \"FTM for z/OS v3.0.0 Knowledge Center\" available at\nIBM Financial Transaction Manager for z/OS V3.0.0 documentation [https://www.ibm.com/support/knowledgecenter/SSRH32_3.0.0/SSRH32_3.0.0welcome.html] back to Contents\n\nUninstalling if necessary\n\nTo rollback to the previous version of FTM:\nUse the normal SMP/E process to revert to a previous version.\n\nDatabase:\n\nRestore the backup taken during the Database migration step.\n\nApplication Migration:\n\nRevert to the WebSphere Message Broker Toolkit workspace taken during the installation steps.\n\nRe-deploy the application bar files.\n\nOAC Migration:\n\nRe-deploy the OAC ear from the previous version.\n\nRSA Model Tooling:\n\nUse Installation manager to re-install the previous version of the 'FTM Model Tools'. back to Contents\n\nList of fixes\n\nFixes included in FTM for z/OS v3.0.0.7\nhttp://www.ibm.com/support/docview.wss?uid=swg21700249 [http://www.ibm.com/support/docview.wss?uid=swg21700249] back to Contents", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q137", "section_id": 0, "heading": "ENVIRONMENT", "parent": null, "text": "These instructions are for WebSphere Message Broker or IBM Integration Bus on AIX, HP-UX, Linux, and Solaris systems.\nReturn to the WMB / IIB MustGather index [http://www-01.ibm.com/support/docview.wss?uid=swg21209857] for other systems.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q137", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "STEP 1: SELF-GUIDED TROUBLESHOOTING\n\n1. Understand the problem that is occurring. * Consider using the Test Client in trace and debug mode [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/af52260_.htm].\nA user level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#1] is intended to assist users with understanding how their ESQL is processed.\n It will also show a high level view of the message flow behavior.\nThe product documentation contains several suggestions for Monitoring the Global Cache [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bn23786_.htm].\n\n2.\n 3. Locate the errors. * Global Cache interactions are logged in the Global Cache Activity Log [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bj23784_.htm].\nInformational messages and unhandled exceptions are written to the IIB Syslog [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/an04230_.htm]. This will also contain a number of BIP71** messages relating to startup/connection of cache components, and whether any of them have failed.\nSome messages may be written to the 'stderr' and 'stdout' files [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/au14165_.htm], located under the Broker's (Integration Node's) workpath.\n\n4.\n 5. Check for known issues and solutions. * General information regarding the Global Cache [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bc23789_.htm] is available in the product documentation, as well as instructions on how to configure the cache [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bn23780_.htm] via the provided tooling.\nReview how to access the Global Cache from a JavaCompute node [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bc23770_.htm].\nThe IIB development and support teams regularly update the IIB DeveloperWorks Blog with Global Cache solutions [https://developer.ibm.com/integration/blog/].\nYour problem may have been discussed on the IIB dWAnswers forum [https://developer.ibm.com/answers/?community=iib].\n*\nWebSphere Message Broker support site\n\nSTEP 2: COLLECT DATA\n\n1. mqsidc\n See: mqsidc usage instructions [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/bu46012_.htm]\nWhen running the tool, select the option for 'Broker Collector', when prompted.\n\n2.\n 3.\n 4. Global Cache details\n Export a current view of your Global Cache with these commands.\n See: mqsicacheadmin command [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bn23783_.htm] * mqsicacheadmin -c listHosts\nmqsicacheadmin -c showMapSizes\nmqsicacheadmin -c showPlacement\nmqsireportproperties -b cachemanager -o CacheManager -r\nmqsireportproperties -e -o ComIbmCacheManager -r\n\n5.\n 6.\n 7. Traces\n If the problem occurs during a runtime test or with the Toolkit test facility,\n an Execution Group service level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#2] can be used to gain a better understanding of the problem.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q137", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Note: For issues with Global Cache, broker service trace contains WXS trace. However, you may sometimes be advised to set a specific WXS trace string. Moreover, for startup issues, a WXS trace string must be specified, as well as enabling service trace. * For startup issues, run this command prior to tracing:\n mqsichangeproperties -e -o ComIbmCacheManager -n overrideTraceSpec -v ObjectGrid*=fine=enabled\nTo capture all information (very verbose), run this command prior to tracing:\n mqsichangeproperties -e -o ComIbmCacheManager -n overrideTraceSpec -v ObjectGrid*=all=enabled\n\n8.\n 9.\n 10. Project Interchange files for the problematic message flow\nYou can export your Message Flow and Java project(s) into an archive file for easy transmission to IBM Support.\n See: Exporting your message flow projects from the Toolkit [http://www-01.ibm.com/support/docview.wss?uid=swg21418121]\n\n11.\n 12.\n\nATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!\nWhen sending data to IBM, be sure to update your PMR or send a note with the following information:\nTell us what errors you saw, where you saw them, and what time they happened Let us know if you made any changes to WebSphere Message Broker or the system before the problem Share any other observations which you think will help us to better understand the problem\n\nSTEP 3: SUBMIT DATA TO IBM\nUse IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM.\nSend your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis.\n\nPlease see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support.\n\nBack to top\n\nPRODUCT ALIAS/SYNONYM\n IIB WMB WXS GC\n\nSTEwebcastDocument; lste_webcast; Tech Exchange; STEwebcast; openmic call; open microphone call; discussion; conference call; customer call; Citrix; submit; ask the experts; discuss; open mic; questions; answers; questions and answers; q&a; replay; recording; webcast; FAQ; best practice; transcript; IBM Lotus Notes on Citrix environments WEBCAST", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q137", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM hosted an Open Mic Webcast with Lotus Development and Support Engineers on 28 September 2011. The topic was \"IBM Lotus Notes in Citrix XenApp environments.\" Check back for the Q&A transcript.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q137", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "For more information about our Open Mic webcasts, visit the IBM Collaboration Solutions Support Open Mics [http://www.ibm.com/software/lotus/support/lotus-open-mics/] page.\n\nPresentation & Audio Recording\nPresentation\n[/support/docview.wss?uid=swg27022065&aid=2]OpenMic_NotesCitrix_09_28_2011.pdf [/support/docview.wss?uid=swg27022065&aid=1]\n\nAudio recording\nLotus_Notes_on_Citrix_XenApp_OpenMic_Sept282011.mp3 [ftp://public.dhe.ibm.com/software/lotus/info/notes/Lotus_Notes_on_Citrix_XenApp_OpenMic_Sept282011.mp3]\n\nQ&A\nQ. Since ID Vault is not supported in Citrix environments until Notes 8.5.3, does that mean it\u2019s known to not work in prior versions?\nA. The statement about support of 8.5.3 just implies that we tested it formally in 8.5.3 and that no testing has been done on previous releases. It doesn\u2019t mean that if used prior to 8.5.3 you\u2019ll find any issues or that there are functional issues with it.\n\nQ. I\u2019m planning to upgrade a Notes installation on a Presentation Server 4.5 from Notes 7.0.2 to 8.5.2 Fix Pack 1. Any advice or pitfalls or best practices we should be aware of prior to doing that? Is an upgrade preferable or a clean install?\nA . With 7.0.2 you should have had the Single User Install because we didn\u2019t support multi-user until 8.5.1, so I would recommend uninstalling Notes 7.x and then doing an install of Notes 8.5.1 or 8.5.2. Then, any subsequent upgrades you could just do an in-place upgrade without backing out the previous build.\n\nQ.Intermittently, users are not able to log in and we receive an error message that \u201cthe Administration program could not be used while the Domino server is running\u201d.\nA. I\u2019ve found that if users completely terminate their ICA session that will leave Notes running in their session. And when the user tries to launch Notes again the error will occur.\n\nIf you\u2019re publishing it as an application, advise users to do a File > Exit to cleanly close the ICA session and to avoid leaving ghost sessions on the XenApp server. You may also want to check with Citrix to see if they have suggestions on handling cases where ICA sessions are terminated but the processes are still running.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q137", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Q. Regarding the recommendation to leverage file server roaming capability where possible, is Domino roaming preferred for that versus Domino file server roaming? For example we want to implement using Domino server because we think it\u2019s easier and we\u2019ve already got a connection established to the mail server to roam to that server, but in the presentation the recommendation was to leverage file server roaming.\nA. You can use either one. The presentation focused on file server roaming because you can implement it using a policy and you don\u2019t need to have a Domino application installed on that server in order to set it up as a roaming server. From the client side it\u2019s still the same functionality for the most part. For example, some customers don\u2019t want to have that application running on that remote server.\n\nQ.Regarding Notes Shared Login not being supported for Citrix environments, will it work but it just not supported?\nA. Not reliably. It may appear to work but you cannot rely on it working. Note that the technology we\u2019re looking at for supporting Shared Login in the future not only will proivde support in the Citrix environment but also provide support in Mac and Linux as well. So we\u2019ll have a much more comprehensive solution going forward.\nWe\u2019re actively working on that solution. At Lotusphere 2012 you\u2019ll hear a lot more on that solution and its potential availability.\n\nQ. Are there recommendations on how to easily move to a multi-user installation from a single-user installation of Notes 8.5.1 Fix Pack 2 in a XenApp 5.0 environmen?\nA. Run the Multi-user Migration Assistant tool, which is available in the Deployment Toolkit with 8.5.3.\n\nQ. I read in the forum that the Admin client and the Designer client are not supported on Citrix. Is that correct?\nA. Correct, neither the Domino Administrator client nor the Domino Designer clients are supported on Citrix.\n\nORIGINAL PUBLICATION DATE\n 2011/7/1\n\nWMB IIB SECURITY BULLETIN", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q137", "section_id": 2, "heading": "SUMMARY", "parent": null, "text": "WebSphere Message Broker and IBM Integration Bus; web user interface error page returns detailed error information.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q137", "section_id": 3, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVE-ID: CVE-2014-4819\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/95456 [https://exchange.xforce.ibmcloud.com/vulnerabilities/95456] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:S/C:P/I:N/A:N)", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q137", "section_id": 4, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "WebSphere Message Broker V8.0\n\nIBM Integration Bus V9.0", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q137", "section_id": 5, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Apply APAR IT03097\n\nFor IBM Integration Bus V9.0, the APAR is targeted to be available in fix pack 9.0.0.3\nFor WebSphere Message Broker V8.0, the APAR is targeted to be available in fix pack 8.0.0.6\n\nPrior to fix pack availability the APAR can be obtained on request from IBM Support.", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q137", "section_id": 7, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 3, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q137", "section_id": 8, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 3, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q137", "section_id": 9, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 10-September- 2014 - Original version Published\nThe 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.", "logical_doc_id": 3, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q137", "section_id": 10, "heading": "RELATED INFORMATION", "parent": null, "text": "A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21684383]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Web User Interface AIX, HP-UX, Linux, Solaris, Windows 9.0\nPRODUCT ALIAS/SYNONYM\n WMB IIB", "logical_doc_id": 3, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q085", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What fixes are included in 5.2.0.0-ISS-XGS-All-Models-Hotfix-FP0007?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q085", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Abstract:\nNetwork Security Protection (XGS)\nFixpack version: FP0007\nApplicable versions: 5.2\n\nProblems resolved:\nDelivers security fixes to date. Please visit\nhttp://www-947.ibm.com/support/entry/portal/support [http://www-947.ibm.com/support/entry/portal/support] to view security\nbulletins for this product.\n62145: Update time zones to support Eternal Winter Time.\n64019: An invalid \"TCP Reset Interface\" setting in the adapters policy causes\nAll future policy changes to reset links on all connected protection interfaces.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q085", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Previous Fixes:\nFix an issue with LACP Down.\nFix issue with snapshot upload not working for some browser configurations.\nFix adapter configuration for ips event filter rules.\nFix issue for not able to add ICMP into restriction tab for Non-Web Object\nin NAP rules.\nFix issue for not able to save customized schedule security setting policy\nin SP for Windows OS Language that does not support the 12-hour notation\n(AM/PM) conversion.\ne.g Japanese\nNOTE: Patch in SiteProtector-XGS-Schedule-Security-Settings-Fix folder\nFixes an issue where XGS fails to post events to SP.\nFixes an Exception on License and Updates Overview page that doesn't\nload page when all protection interfaces disabled.\nCorrects aplsd crash\nAdd DCA lookup logging\nCorrects pktcapd restart race condition, which prevents NAP rule from being\nchanged.\nFix kernel panic\nQuarantine rules are not added in response to non-sequitur events (Network\nsweeps, scans, and flood events) that have quarantine responses that are enabled.\nQuarantine rules are added in response to events that are detected in\nMonitoring mode (IDS mode), even though quarantine responses are not\nApplicable in Monitoring mode.\nImprovements to hardware bypass to prevent a crash on exit under certain\nconditions.\nPAM XPU 34.070 (July 2014) breaks in Domain Certificate Object matching\nNetwork Access and SSL Inspection rules.\nUpdate to hardware bypass to allow for continued operation of the bypass\nmodules if an internal error occurs.\nFixes the command line interface to display DHCP acquired management IP\naddresses.\nFixes Inbound SSL decryption failures that are related to error message \"No Error\nSet.\"\nFixes an internal error that can occur while processing TLS/SSL traffic.\nOptimizations to decrease packet latency.\nFixes an internal error that can occur when processing TLS or SSL traffic.\nFixes an intermittent issue that displays Top 10 Applications as Unknown\nwhen the application is known.\nReplaces application database recovery files that were not migrated when\nUpdating from 5.1.2 to 5.2.\nFixes the status of the Application Control license.\nFix to preserve the IP Reputation license when the Application License is\nremoved\n\nModules impacted:\nPktcapd, SSL, Kernel, LACP, MSL, LMI, SiteProtector\n\nNotes:\nIf the Event Id GLGSY0038W appears in your System Events Event Log, then\nThe operating system is experiencing a temporary failure. However, the\nAppliance is still protecting your network. Contact IBM Support for\nassistance.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q085", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "[/support/docview.wss?uid=swg21696054&aid=1] [https://ibm.biz/BdHdZx] [/support/docview.wss?uid=swg21696054&aid=2] [http://ibm.biz/InfraSecForumTechnote] [/support/docview.wss?uid=swg21696054&aid=3] [http://ibm.biz/SecSuptUTube] [/support/docview.wss?uid=swg21696054&aid=4] [http://ibm.biz/InfraSecFixes] [/support/docview.wss?uid=swg21696054&aid=5] [http://ibm.biz/FlexLicLogin] [/support/docview.wss?uid=swg21696054&aid=6] [http://ibm.biz/MyNotification] [/support/docview.wss?uid=swg21696054&aid=7] [http://ibm.biz/ContactSecSupport]", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q085", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Step to reproduce:\n\n1. Log into DASH and open the Health Dashboard\n2. Ensure that the event list shown is the Event Viewer, not the AEL\n3. Ensure that the active view is the Self Monitoring view\n5. Click on a selection of gauges.\n\nExpected result: The event list is updated to show the events which match the related filter (if any such events exist).\n\nActual result: No update from the Event Viewer. The same events are showing.", "logical_doc_id": 2, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q085", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "This third party API:\n\nvar xmlDoc = new ActiveXObject( \"Microsoft.XMLDOM\" );\n\nin /ibm/console/webtop/scripts/ajax.js causes an exception with some IE9/IE10 browsers.\nStepping over the above line throws the following exception:\neventTransformer: Exception caught while attempting to read payload. Error was:Automation server can't create object\n\nThe issue is caused by configuration changes on some Windows machines and is not a defect in OMNIbus Web GUI.", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q085", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Go to:\n\n\" IE9/10 > Internet Options > Security > Custom Level\" and set\n1. \"Run ActiveX controls and plug-ins\" to Enable\n2. \"Script ActiveX controls marked safe for scripting\" to Enable", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q085", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Is it possible to display an event list directly on a mobile device, without drilling down from an Event Dashboard or Gauge?", "logical_doc_id": 3, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q085", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Yes, it is. The URL can be entered in this format to display an event list in the Event Viewer on a mobile device:\n[https]://:/ibm/console/webtop/m/eventviewer?filtername=Escalated&filtertype=global\n\nNote: it is not possible to use a transient filter in the URL under these circumstances. The filter specified must be pre-defined via the Filter Builder.", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q085", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "When changing the width of one column in the Table widget e.g. Alert Group, close the page and open it again. The column Alert Group keeps the size.\n\nAfter adding a wire to the page from List > NodeClickedOn to Table widget and clicking on one line in List widget, you will see that columns in Table widget are reorganizing. The column Alert Group has switched to its old width.", "logical_doc_id": 4, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q085", "section_id": 1, "heading": "ENVIRONMENT", "parent": null, "text": "WAS v8.5.0.1\nDASH v3.1.0.3\nWebGUI 8.1.0.0", "logical_doc_id": 4, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q085", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "See this document for recreation steps:WebGUI_8.1_List_Widget_does_not_save_column_width_after_receiving_wire_event.docx [/support/docview.wss?uid=swg21959612&aid=2]WebGUI_8.1_List_Widget_does_not_save_column_width_after_receiving_wire_event.docx [/support/docview.wss?uid=swg21959612&aid=1]", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q085", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Upgrade to JazzSM 1.1.2 Refresh Pack from Fix Central:\n\nDownload link\nhttp://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%2FTivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=All&platform=All&function=fixId&fixids=1.1.2.0-TIV-JazzSM-multi&includeSupersedes=0&source=fc [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%2FTivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=All&platform=All&function=fixId&fixids=1.1.2.0-TIV-JazzSM-multi&includeSupersedes=0&source=fc]\n\nReadme instructions:\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24039724 [http://www-01.ibm.com/support/docview.wss?uid=swg24039724]", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q085", "section_id": 4, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Version 8.0.1 Fix Pack 2 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24035701]\nVersion 8.5.0 Fix Pack 1 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24035702]\nVersion 8.5 Refresh Pack 5 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24037683]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q085", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "If user is using a Non-English locale (e.g. ja_JP) for their\n browsers, in Process Portal the Dashboards do not display the\n Pie-Chart and Task lists.", "logical_doc_id": 5, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q085", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "set locale of the user to English, access dashboard, and then\n change it back to real locale, like Japanese, the problem will\n be workarounded", "logical_doc_id": 5, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q085", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Users of BPM Express, BPM Standard, and *\nBPM Advanced on 8.0.1.0. *\n\nPROBLEM DESCRIPTION: Issues with resolving an unsupported *\nlanguage-country browser locale into *\na Portal-supported locale. *\n\nRECOMMENDATION: *\n\nMy Performance and My Team Performance Pie\n Charts and Task List do not load until\n user changes their Language preference in\n the User Profile.", "logical_doc_id": 5, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q085", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Added a configurable flag that will resolve the user's browser\n locale to a Portal-supported locale, and properly set the\n language as their User Preference. If the user's browser locale\n is not a Portal-supported locale, then the user's locale will\n default to English.\n\nFix is available on FixCentral.\n\nInstall/Dependency information is available in the readme.txt on\n FixCentral. When the user goes to the download files page in\n FixCentral, the readme will be available with the fix package as\n a separate download.\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q085", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR46703\nREPORTED COMPONENT NAME\n BPM ADVANCED\nREPORTED COMPONENT ID\n 5725C9400\nREPORTED RELEASE\n 801\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-05-21\nCLOSED DATE\n 2014-04-11\nLAST MODIFIED DATE\n 2014-04-11\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q085", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM ADVANCED\nFIXED COMPONENT ID\n 5725C9400", "logical_doc_id": 5, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q085", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R800 PSY\n UP", "logical_doc_id": 5, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q180", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere Application Server is shipped as a component of IBM WebSphere Portal. Information about security vulnerabilities affecting IBM WebSphere Application Server has been published in security bulletins.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q180", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Please consult the security bulletins for IBM WebSphere Application Server published at\nSecurity Bulletin: Security Vulnerability in IBM WebSphere Application Server (CVE-2015-1920) [http://www-01.ibm.com/support/docview.wss?uid=swg21883573]\nSecurity Bulletin: Vulnerability in RC4 stream cipher affects WebSphere Application Server (CVE-2015-2808) [http://www-01.ibm.com/support/docview.wss?uid=swg21701503]\nSecurity Bulletin: Multiple vulnerabilities in IBM\u00ae Java SDK affect WebSphere Application Server April 2015 CPU [http://www-01.ibm.com/support/docview.wss?uid=swg21902260]\nSecurity Bulletin: Vulnerability in RC4 stream cipher affects IBM HTTP Server and Caching Proxy (CVE-2015-2808) [http://www-01.ibm.com/support/docview.wss?uid=swg21701072]\nSecurity Bulletin: Vulnerability with RSA Export Keys may affect IBM HTTP Server and WebSphere EDGE Caching Proxy (CVE-2015-0138) [http://www-01.ibm.com/support/docview.wss?uid=swg21698959]\nSecurity Bulletin: Vulnerability in Dojo Toolkit affect WebSphere Application Server (CVE-2014-8917) [http://www-01.ibm.com/support/docview.wss?uid=swg21697284]\n\nfor vulnerability details. AFFECTED PRODUCTS AND VERSIONS\n\nPrincipal Product and Version(s) Affected Supporting Product and Version IBM WebSphere Portal version 6.1, 7.0, 8.0, and 8.5 IBM WebSphere Application Server version 6.1, 7.0, 8.0, 8.5 GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.\n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www-03.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q180", "section_id": 2, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] CHANGE HISTORY\n 21 May 2015: Original Version Published\nThe 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.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q180", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Log viewer vulnerability affects IBM PureApplication System.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q180", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2014-6190 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6190]\nDESCRIPTION:\nDefined system users without proper permissions can access the log viewer functionality by entering the log page URLs in their browser.\n\nCVSS Base Score: 5.0\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/98561 [https://exchange.xforce.ibmcloud.com/vulnerabilities/98561] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q180", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM PureApplication System V1.0\nIBM PureApplication System V1.1\nIBM PureApplication System V2.0", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q180", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "The solution is to apply the following IBM PureApplication System version fixes.\nThe PureSystems Managers on all IBM PureApplication Systems types are affected. Upgrade the IBM PureApplication System to the following interim fix levels:\nIBM PureApplication System V1.0\n Upgrade to IBM PureApplication System V1.0.0.4 Interim Fix 11\nIBM PureApplication System V1.1\n Upgrade to IBM PureApplication System V1.1.0.5 Interim Fix1\nIBM PureApplication System V2.0\n Upgrade to IBM PureApplication System V2.0.0.1", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q180", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q180", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q180", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 25 March 2015: Original version published\nThe 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.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q180", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM PureApplication System contains IBM WebSphere Application Server, which has a security vulnerability that could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q180", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2015-1920 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1920]\nDESCRIPTION: WebSphere Application Server could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions.\nCVSS Base Score: 9.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/102404 [https://exchange.xforce.ibmcloud.com/vulnerabilities/102404] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:C/I:C/A:C)\n\nPlease consult the security bulletin: Security Vulnerability in IBM WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg21883573]for additional vulnerability details and information", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q180", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM PureApplication Server bundles WebSphere Application Server in its Web Application Pattern.\n\nIBM PureApplication System V2.1\nIBM PureApplication System V2.0\nIBM PureApplication System V1.1", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q180", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "The solution is to apply an update to the Web Application pattern type included in IBM PureApplication System:\n\nIBM PureApplication System V2.1\n\u00b7 Web Application Pattern Type V2.0.4.2\nhttp://www.ibm.com/support/fixcentral/swg/quickorder?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-2.0.4.2-sys&includeSupersedes=0&source=fc [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-2.0.4.2-sys&includeSupersedes=0&source=fc]\n\n\u00b7 Web Application Pattern Type V1.0.4.2\nhttp://www.ibm.com/support/fixcentral/swg/quickorder?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-1.0.4.2-sys&includeSupersedes=0&source=f [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-1.0.4.2-sys&includeSupersedes=0&source=f]\n\nIBM PureApplication System V2.0\nThe solution is to upgrade to IBM PureApplication System V2.0.0.1 Interim Fix 5\n\nIBM PureApplication System V1.1 and earlier:\nContact IBM customer support for upgrade options.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q180", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q180", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q180", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 19 August 2015: Original Version Published\n11 September 2015 Updated for IBM PureApplication System v2.0\nThe 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\nsecurity; CVE-2014-6593; CVE-2015-0410; CVE-2015-0138; CVE-2014-3566; CVE-2014-6468; CVE-2014-6457; CVE-2015-2808; CVE-2014-0453; CVE-2015-1920; CVE-2015-0488; CVE-2015-0478; CVE-2015-2808; CVE-2015-1916; CVE-2015-1914; CVE-2015-0204; CVE-2015-4000; CVE-2015-4000; CVE-2015-2613; CVE-2015-2601; CVE-2015-2625; CVE-2015-1931; CVE-2015-4749; CVE-2015-3183; CVE-2015-2017; CVE-2015-4872; CVE-2015-4911; CVE-2015-4893; CVE-2015-4803; CVE-2015-4734; CVE-2015-5006 SECURITY BULLETIN", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q180", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM Tivoli System Automation for Multiplatforms is shipped as a component of IBM Cloud Orchestrator, IBM Cloud Orchestrator Enterprise, IBM SmartCloud Orchestrator, and IBM SmartCloud Orchestrator Enterprise. Information about security vulnerabilities affecting IBM Tivoli System Automation for Multiplatforms has been published in security bulletins.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q180", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Consult the security bulletins for IBM Tivoli System Automation for Multiplatforms for vulnerability details and information about fixes.\nSecurity Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Tivoli System Automation for Multiplatforms (CVE-2016-0466, CVE-2015-7575) [http://www-01.ibm.com/support/docview.wss?uid=swg21977127]\nSecurity Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Tivoli System Automation for Multiplatforms (CVE-2015-4872, CVE-2015-4911, CVE-2015-4893, CVE-2015-4803, CVE-2015-4734, CVE-2015-5006) [http://www.ibm.com/support/docview.wss?uid=swg21971479&myns=swgtiv&mynp=OCSSRM2X&mync=E&cm_sp=swgtiv-_-OCSSRM2X-_-E]\nSecurity Bulletin: A security vulnerability has been identified in WebSphere Application Server shipped with IBM Tivoli System Automation for Multiplatforms (CVE-2015-2017) [http://www.ibm.com/support/docview.wss?uid=swg21970548]\n\n[http://www-01.ibm.com/support/docview.wss?uid=swg21967199]\nSecurity Bulletin: A security vulnerability has been identified in WebSphere Application Server shipped with IBM Tivoli System Automation for Multiplatforms (CVE-2015-1283) [http://www-01.ibm.com/support/docview.wss?uid=swg21967199]\nSecurity Bulletin: A security vulnerability has been identified in WebSphere Application Server shipped with IBM Tivoli System Automation for Multiplatforms (CVE-2015-3183) [http://www-01.ibm.com/support/docview.wss?uid=swg21967197]\nSecurity Bulletin: Multiple vulnerabilities in IBM Java SDK including Logjam affect IBM Tivoli System Automation for Multiplatforms (CVE-2015-4000, CVE-2015-2613, CVE-2015-2601, CVE-2015-2625, CVE-2015-1931, CVE-2015-4749) [http://www.ibm.com/support/docview.wss?uid=swg21963330]\nSecurity Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM Tivoli System Automation for Multiplatforms (CVE-2015-4000) [www.ibm.com/support/docview.wss?uid=swg21960862]\nSecurity Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Tivoli System Automation for Multiplatforms (CVE-2015-0488, CVE-2015-0478, CVE-2015-2808, CVE-2015-1916, CVE-2015-1914, CVE-2015-0204) [http://www.ibm.com/support/docview.wss?uid=swg21957951]\nSecurity Bulletin: Vulnerability in WebSphere Application Server affects IBM Tivoli System Automation for Multiplatforms (CVE-2015-1920) [http://www.ibm.com/support/docview.wss?uid=swg21957952]\nSecurity Bulletin: Vulnerability in IBM Tivoli System Automation for Multiplatforms (CVE-2014-0453) [http://www-01.ibm.com/support/docview.wss?uid=swg21680562]\nSecurity Bulletin: Vulnerability in RC4 stream cipher affects IBM Tivoli System Automation for Multiplatforms (CVE-2015-2808) [http://www.ibm.com/support/docview.wss?uid=swg21882749].\nSecurity Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Tivoli System Automation for Multiplatforms (CVE-2014-3566, CVE-2014-6468, CVE-2014-6457)\nSecurity Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Tivoli System Automation for Multiplatforms (CVE-2014-6593, CVE-2015-0410, CVE-2015-0138) [http://www.ibm.com/support/docview.wss?uid=swg21698239]", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q180", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Principal Product and Version Affected Supporting Product and Version IBM Cloud Orchestrator 2.5, 2.5.0.1, 2.5.0.1 Interim Fix1, 2.4, 2.4.0.1, 2.4.0.2 and 2.4.0.3 IBM Cloud Orchestrator Enterprise 2.5.0.1, 2.5.0.1 Interim Fix1, 2.4, 2.4.0.1, 2.4.0.2 and 2.4.0.3\n\nIBM Tivoli System Automation for Multiplatforms 4.1 IBM SmartCloud Orchestrator 2.3, 2.3.0.1 IBM SmartCloud Orchestrator Enterprise 2.3 and 2.3.0.1\n\nIBM Tivoli System Automation for Multiplatforms 3.2.2 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.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q180", "section_id": 3, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q180", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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\n20 May 2016: Last update new bulletins\n30 April 2015: Original copy published\nThe 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\nCVE-2015-0138; CVE-2014-3566; CVE-2014-8730; CVE-2015-2808; CVE-2015-4000; CVE-2014-6593; CVE-2015-0410; CVE-2015-1920; CVE-2015-0488; CVE-2015-0478; CVE-2015-1916; CVE-2015-5003; CVE-2015-2017; CVE-2015-1829; CVE-2015-3183; CVE-2015-1283; CVE-2015-4947; CVE-2015-2808; CVE-2015-7450; CVE-2015-2017; CVE-2015-4938; CVE-2015-1932; CVE-2015-1927; CVE-2015-2017; CVE-2015-7417; CVE-2015-4872; CVE-2015-4911; CVE-2015-4893; CVE-2015-4803; CVE-2015-4734; CVE-2015-5006; CVE-2015-7450; CVE-2016-0201; CVE-2015-7411 SECURITY BULLETIN", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q180", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM Tivoli Monitoring is shipped as a component of IBM Cloud Orchestrator Enterprise and IBM SmartCloud Orchestrator Enterprise. Information about security vulnerabilities affecting IBM Tivoli Monitoring has been published in the security bulletins below.", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q180", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Consult the following security bulletins for IBM Tivoli Monitoring for vulnerability details and information about fixes.\nSecurity Bulletin: Vulnerability in IBM Java SDK affect IBM Tivoli Monitoring (CVE-2015-7575)\nSecurity Bulletin: Vulnerability in RC4 stream cipher affects IBM Tivoli Monitoring (CVE-2015-2808) [http://www-01.ibm.com/support/docview.wss?uid=swg21883223]\nSecurity Bulletin: Vulnerability in IBM Java Runtime affects IBM Tivoli Monitoring (CVE-2015-0138) [http://www-01.ibm.com/support/docview.wss?uid=swg21701519]\nSecurity Bulletin: A security vulnerabilities has been identified in Websphere Application Server shipped with Jazz for Service Management (CVE-2016-0306) [http://www-01.ibm.com/support/docview.wss?uid=swg21981087]\nSecurity Bulletin: IBM Tivoli Monitoring Privileges Escalation through Authorization Bypass (CVE-2015-7411) [http://www-01.ibm.com/support/docview.wss?uid=swg21973559]\nSecurity Bulletin: A vulnerability in the GSKit component of IBM Tivoli Monitoring (CVE-2016-0201) [http://www-01.ibm.com/support/docview.wss?uid=swg21976125]\nSecurity Bulletin: IBM Tivoli Monitoring Remote Code Execution (CVE-2015-5003) [http://www-01.ibm.com/support/docview.wss?uid=swg21970361]\nSecurity Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IBM Tivoli Monitoring clients (CVE-2015-2590 plus additional CVEs) [http://www.ibm.com/support/docview.wss?uid=swg21964027]\nSecurity Bulletin IBM Tivoli Monitoring embedded WebSphere Application Server (CVE-2015-7450, CVE-2015-2017, CVE-2015-4938, CVE-2015-1932, CVE-2015-1927)\nSecurity Bulletin: Multiple security vulnerabilities has been identified in WebSphere Application Server shipped with Jazz for Service Management (CVE-2015-7450) (CVE-2015-2017) [http://www-01.ibm.com/support/docview.wss?uid=swg21971097]\nSecurity Bulletin: Multiple security vulnerabilities has been identified in IBM HTTP Server shipped with Jazz for Service Management / Websphere Application Server (CVE-2015-1283,CVE-2015-3183) [http://www-01.ibm.com/support/docview.wss?uid=swg21968301]\nSecurity Bulletin: IBM Tivoli Monitoring (CVE-2015-1829, CVE-2015-3183, CVE-2015-1283, CVE-2015-4947, CVE-2015-2808) [http://www.ibm.com/support/docview.wss?uid=swg21970056]\nSecurity Bulletin: IBM Tivoli Monitoring embedded WebSphere Application Server (CVE-2015-1920) [http://www-01.ibm.com/support/docview.wss?uid=swg21963474]\n[http://www-01.ibm.com/support/docview.wss?uid=swg21963473]Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM Tivoli Monitoring (CVE-2015-4000) [http://www.ibm.com/support/docview.wss?uid=swg21962739]\nSecurity Bulletin: Vulnerability in Diffie-Hellman ciphers affects the Enterprise Common Collector component of the IBM Tivoli zEnterprise Monitoring Agent (CVE-2015-4000) [http://www-01.ibm.com/support/docview.wss?uid=swg21960019]\nSecurity Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Tivoli Monitoring (CVE-2014-6593, CVE-2015-0410) [http://www-01.ibm.com/support/docview.wss?uid=swg21963473]\nSecurity Bulletin: Multiple vulnerabilities in IBM Java Runtime affect the Enterprise Common Collector component of the IBM Tivoli zEnterprise Monitoring Agent (CVE-2015-0488, CVE-2015-0478, CVE-2015-1916) [http://www-01.ibm.com/support/docview.wss?uid=swg21902886]\nSecurity Bulletin: Vulnerability in IBM Java Runtime affects IBM Tivoli Monitoring (CVE-2015-0138) [http://www.ibm.com/support/docview.wss?uid=swg21701519]\nSecurity Bulletin: Multiple vulnerabilities in IBM Java Runtime affecting IBM Tivoli Monitoring clients [http://www.ibm.com/support/docview.wss?uid=swg21695592]\nSecurity Bulletin: Vulnerability in TLS affects IBM Tivoli Monitoring (CVE-2014-8730) [http://www.ibm.com/support/docview.wss?uid=swg21694339]\nSecurity Bulletin: Vulnerability in RC4 stream cipher affects the Enterprise Common Collector component of the IBM Tivoli zEnterprise Monitoring Agent (CVE-2015-2808) [http://www.ibm.com/support/docview.wss?uid=swg21713608]", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q180", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Principal Product and Versions Affected Supporting Product and Version IBM Cloud Orchestrator Enterprise 2.5, 2.5.0.1, 2.5.0.1 Interim Fix1, 2.4, 2.4.0.1, 2.4.0.2 and 2.4.0.3 IBM Tivoli Monitoring 6.3.0.2 IBM SmartCloud Orchestrator Enterprise 2.3 and 2.3.0.1 IBM Tivoli Monitoring 6.3.0.1 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.", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q180", "section_id": 3, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q180", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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\n20 May 2016:Last Update new bulletins\n30 April 2015: Original copy published\nThe 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.", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q205", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Why does the \"Terminate\" action provided by WebSphere Application Server debugger not allow you to terminate WebSphere Application Server v6.x when started in debug mode?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q205", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "There has been a behavior change in terms of debugging WebSphere Application Server v5.x and v6.x:\n\nWhen debugging WebSphere Application Server v5.x you can select any suspended thread, and invoke the \"Terminate\" action to terminate the server JVM.\n\nHowever, when debugging WebSphere Application Server 6.x the \"Terminate\" action will only terminate or disconnect the WebSphere Application Server debugger. It will not terminate the WebSphere Application Server 6.x JVM process.\n\nCross Reference information Segment Product Component Platform Version Edition Software Development Rational Software Architect Debugging Applications Linux, Windows 6.0, 6.0.0.1, 6.0.1, 6.0.1.1, 6.0.1.2, 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4, 7.0.0.5 Edition Independent", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q205", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "You connected a Rational Team Concert server to Rational Business Developer and you perform actions on the server. Then the Eclipse workbench, java.exe, stops with the following error message.\n\nJava was started but returned exit code=8096\n\n[/support/docview.wss?uid=swg21502684&aid=1] [/support/docview.wss?uid=swg21502684&aid=1]\n\nExamples of actions you can do are: creating a work item and creating a user.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q205", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "One known cause is due to the video driver and when two different versions of drivers are installed on the machine (i.e 6.14.10.5284 and 6.14.10.5303)\n\nNote: Other causes are also possible but have not been reported.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q205", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "This problem has been seen with ThinkPad laptops", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q205", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Look at the java core. The following entries support the hypothesis of the faulty video drivers.\n\n1. The last call before the problem relates to the Microsoft gdiplus.dll graphics library.\n\n2. The correct values passes correctly to the Standard Widget Toolkit (SWT) before the error occurs.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q205", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Update the video driver to the newest version\n\nLink: Intel Download Center [http://downloadcenter.intel.com/]", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q205", "section_id": 5, "heading": "RELATED INFORMATION", "parent": null, "text": "#JVM terminated. Exit code=8096 [https://www.ibm.com/support/docview.wss?uid=swg21303648]\nInternet Explorer v9 or higher is required if the produ [http://www-01.ibm.com/support/docview.wss?uid=swg21502701]", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q205", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "exit; code; 8096; crash; crashes; RTC; RSA; java virtual machine; Work item 166607 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q205", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Rational Team Concert crashes with the following JVM terminated error message:\n\nJVM terminated. Exit code=8096\n\n[/support/docview.wss?uid=swg21501371&aid=1]", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q205", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "There are many possible factors that could contribute to the crash the JVM exit code=8096 error message.\n\nOne of possible causes might be a bug in the Intel Graphic Card driver for Windows XP Service Pack 3", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q205", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "Rational Team Concert version 3.0 and 3.0.1 integrated with Rational Software Architect\nIntel(R) Q45/Q43 Express Chipset\nWindows XP Service Pack 3", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q205", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Upgrade your graphic card driver to the latest one. If upgrading the driver does not fix the issue, contact Rational support..\n\nCross reference information Segment Product Component Platform Version Edition Software Development Rational Software Architect Not Applicable Windows 8.0, 8.0.1, 8.0.2, 8.0.3", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q205", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Steps to reproduce:\n\n1. Try to link a CQ record to an RTC work item through the RTC Eclipse client.\n\n2. Bring up the CQ dialog window.\n\n3. Observe that Eclipse halts with the error.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q205", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "You use 64-bit Eclipse. 64-bit Eclipse cannot fulfil this task.", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q205", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "Windows 7, RTC 4.0.x", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q205", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "You can see a text in the javacore file that is similar to:\n\nWindows_ExceptionCode: C0000005 (access violation)\nModule: C:\\Windows\\System32\\mshtml.dll\n\nCurrent thread:\n\"main\" J9VMThread:0x0000000002868500, j9thread_t:0x00000000007397B0,\njava/lang/Thread:0x000007FFBE6F1B60, state:R, prio=6\n(java/lang/Thread getId:0x1, isDaemon:false)\n(native thread ID:0xDC0, native priority:0x6, native policy:UNKNOWN)\nJava callstack:\nat org/eclipse/swt/internal/win32/OS.DispatchMessageW(Native Method)", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q205", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "WORKAROUND:\n\nUse a 32-bit Eclipse instance.", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q205", "section_id": 5, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Rational Software Architect 9.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034297]\nRational Software Architect for WebSphere Software 9.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034298]\nRational Software Architect RealTime Edition 9.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034299]\nRational Software Architect 8.5.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24035434]\nRational Software Architect for WebSphere Software 8.5.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24035436]\nRational Software Architect Fix Pack 1 (8.5.5.1) for 8.5.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24036832]\nRational Software Architect for WebSphere Software Fix Pack 1 (8.5.5.1) for 8.5.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24036833]\nRational Software Architect Fix Pack 2 (8.5.5.2) for 8.5.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24038307]\nRational Software Architect for WebSphere Software Fix Pack 2 (8.5.5.2) for 8.5.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24038308]\nRational Software Architect Fix Pack 3 (8.5.5.3) for 8.5.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24039397]\nRational Software Architect for WebSphere Software Fix Pack 3 (8.5.5.3) for 8.5.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24039398]\nRational Software Architect Fix Pack 4 (8.5.5.4) for 8.5.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24041240]\nRational Software Architect for WebSphere Software Fix Pack 4 (8.5.5.4) for 8.5.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24041241]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q205", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Environment:\nMicrosoft Windows\nProduct: RSA 8.5\n\n Reproducible: Y\n\n Description of problem:\n\n The fix of PM73705 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM73705] that was introduced in RSA 8.5.1 has adverse\n consequence for UML to Java Transformation.\n After this defect fix, every space is represented by ?nbsp;\n This is fine for the documentation itself, but the ?nbsp; is\n then emitted in the Javadocs by the UML to Java transformation.\n\n Steps to reproduce\n\n With Rich text option enabled by default, if you add this text\n as documentation of a new UML Class:\n\n This is one line\n\n This is another line\n\n and yet another one.\n\n (where you pressed ENTER between lines) and then run a UML to\n Java transformation, it gets transformed to:\n /**\n?!-- begin-UML-doc --?\n?p?This?nbsp;is?nbsp;one?nbsp;line?/p??p?This?nbsp;is?nbsp;anoth\n er?nbsp;\n line?/p??p?and?nbsp;yet?nbsp;another?nbsp;one.?/p?\n?!-- end-UML-doc --?\n@author 098561\n@generated 'UML to Java\n\n (com.ibm.xtools.transform.uml2.java5.internal.UML2JavaTransform)\n '\n/\n\n public class Class1 {\n\n }", "logical_doc_id": 5, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q205", "section_id": 1, "heading": "Workaround", "parent": null, "text": "No known workaround.", "logical_doc_id": 5, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q205", "section_id": 3, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\n\nPROBLEM DESCRIPTION: *\n\nRECOMMENDATION: *\n\nUML to Java transformation replaced all spaces in UML\n documentation with ?nbsp in the generated Java code.", "logical_doc_id": 5, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q205", "section_id": 4, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "UML to Java transformation no longer replace all spaces in\n UML documentation with ?nbsp in the generated Java code.\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q205", "section_id": 6, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM88777\nREPORTED COMPONENT NAME\n RATL SW ARCHITE\nREPORTED COMPONENT ID\n 5725A3000\nREPORTED RELEASE\n 851\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-05-10\nCLOSED DATE\n 2013-06-17\nLAST MODIFIED DATE\n 2013-06-17\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q205", "section_id": 7, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n RATL SW ARCHITE\nFIXED COMPONENT ID\n 5725A3000", "logical_doc_id": 5, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q205", "section_id": 8, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R851 PSN\n UP", "logical_doc_id": 5, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q305", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q305", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "After migratrating working reports to V 10.2.2 images with\n relative URL addressing will not be displayed in HTML reports", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q305", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "change the way the images are addressed wihtin the report", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q305", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nAll Users *\n\nPROBLEM DESCRIPTION: *\nSee error description. *\n\nRECOMMENDATION: *\nUpgrade to IBM Cognos Business Intelligence 10.2.2 Fix Pack *\n4 *", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q305", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Code Fix\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q305", "section_id": 4, "heading": "COMMENTS", "parent": null, "text": "A fix for this APAR is targeted for IBM COGNOS 10.2.2 BI Fix\n Pack 4\n\nThe Fix Pack Release Schedule can be found at\n http://www.ibm.com/software/analytics/support/fixes/pbi_schedule\n .html [http://www.ibm.com/software/analytics/support/fixes/pbi_schedule.html]", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q305", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI35387\nREPORTED COMPONENT NAME\n COG REPORT STUD\nREPORTED COMPONENT ID\n 5724W12RS\nREPORTED RELEASE\n A22\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2015-02-19\nCLOSED DATE\n 2015-12-17\nLAST MODIFIED DATE\n 2015-12-17\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n PI41576 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI41576]", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q305", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n COG REPORT STUD\nFIXED COMPONENT ID\n 5724W12RS", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q305", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "RA22 PSN\n UP", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q305", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Does IBM Cognos Analysis for Microsoft Excel, Planning Analytics for Microsoft Excel, or TM1 Perspectives support Microsoft Office 365?", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q305", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "You can check the supported environments for all versions of Cognos Analysis for Microsoft Excel, Planning Analytics for Microsoft Excel, or Perspectives on the IBM website:\nhttps://www.ibm.com/software/reports/compatibility/clarity/index.html [https://www.ibm.com/software/reports/compatibility/clarity/index.html]\n\nHowever, MS Office 365 is not a 'traditional' single product. Instead, it is a subscription plan which allows users to download/run the very latest version of Office. In other words, customers who own Office 365 licenses will probably be upgrading their Excel versions (over time) as new MS Excel versions are released.\n=> This makes it impossible to give a simple 'yes/no' answer to the question to whether Cognos Analysis for Microsoft Excel or Planning Analytics for Microsoft Excel supports MS Office 365.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q305", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Microsoft Office 365 is supported so long as all of the following are true:\nThe version of Office installed (for example Office 2016) as part of Office 365, is supported by that version of Cognos Analysis for Microsoft Excel or Planning Analytics for Microsoft Excel. For example: * Cognos Analysis for Microsoft Excel 10.2.2 FP6 is the first release in that line that supports Excel 2016. All earlier versions of CAFE 10.2.2 (FP5 and earlier) support a maximum of Office 2013.\nPlanning Analytics for Microsoft Excel has supported Excel 2016 since its release.\nUsing desktop-installed (downloaded) Office 365 (not the cloud version of Office 365), which has been installed via the traditional installation method or if you have installed via click to run.\n\nFor the avoidance of doubt, Office 365 is not supported when running directly in the Cloud (instead of running on the desktop/laptop directly).\n\nQ1 - What are the different methods to install Microsoft Office 365?\nMicrosoft Office 365 can be installed in two different ways:\n\n(1) Traditional method\nThis is sometimes called the 'MSI' or 'Windows Installer' method\nIt is also sometimes known as the 'Volume License' method\nThe application is installed (and runs) natively/directly on the users client device\n\n(2) Click-to-run * The user \"streams\" the portion of Office that they need (downloading extra portions as and when they need it). The software is running in an isolated 'Sandbox' environment ('virtual bubble') on the computer.\n\nQ2 - What is 'Click to Run' ?\nClick-to-Run is a streaming and virtualization technology that is designed to significantly reduce the time that is required to download and use Office client products. Streaming allows users to begin to use a Click-to-Run product before the complete product is downloaded.\n\nClick-to-Run for Office 365 products are based on core virtualization and streaming Microsoft Application Virtualization ( App-V) technologies. Click-to-Run resources run in an isolated virtual environment on the local operating system.\n\nQ3 - How can I check if my installation is 'traditional' or 'click to run'?\nMethod #1 (recommended)", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q305", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "1. Launch Excel (or Outlook or Word).\n2. Click \"File - Account\" (or Office Account).\n[/support/docview.wss?uid=swg22015168&aid=1] [/support/docview.wss?uid=swg22015168&aid=1]\nIf you see an \" Update Options\" item, you have a Click-to-Run installation\nIf you don't see the \"Update Options\" item, you have an MSI-based install.\nMethod #2 (alternative)\n\nSee where EXCEL.EXE is installed/run from:\n\n(1) Traditional (MSI):\nBy default, EXCEL.EXE is located in the following locations: * Office 2013 (32-bit): C:\\Program Files (x86)\\Microsoft Office\\Office15\\\nOffice 2016 (32-bit): C:\\Program Files (x86)\\Microsoft Office\\root\\Office16\\\n\n(2) Click to Run:\nBy default, EXCEL.EXE is located in the following locations: * Office 2013 (32-bit): C:\\Program Files (x86)\\Microsoft Office 15\\ClientX64\\Root\\Office15\\\nOffice 2016 (32-bit): C:\\Program Files (x86)\\Microsoft Office 16\\ClientX64\\Root\\Office16\\\n\nQ4 - What should I do if I have already installed MS Office 365 as 'click to run', and it is unsupported in my version of Cognos Analysis for Microsoft Excel or Planning Analytics for Microsoft Excel ?\nEither:\n(a) Remove the Click-To-Run installed Office. Then install MS Office via the traditional (MSI) method instead\nor (b) Upgrade to a later version of Cognos Analysis for Microsoft Excel or Planning Analytics for Microsoft Excel which supports click to run (see above for caveats).", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q305", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "TECHNOTE(\u30c8\u30e9\u30d6\u30eb\u30b7\u30e5\u30fc\u30c6\u30a3\u30f3\u30b0)\n\n\u554f\u984c(\u6982\u8981)\n \u30ec\u30dd\u30fc\u30c8\u306b\u753b\u50cf\u3092\u8868\u793a\u3059\u308b\u3088\u3046\u306b\u3057\u3066\u3044\u308b\u304c\u3001HTML\u5f62\u5f0f\u3067\u306f\u8868\u793a\u3055\u308c\u308b\u306e\u306bExcel/PDF\u5f62\u5f0f\u3067\u306f\u8868\u793a\u3055\u308c\u306a\u3044\u3002\n\n\u539f\u56e0\n\u753b\u50cf\u306eURL\u3067\u6307\u5b9a\u3055\u308c\u305f\u30d1\u30b9\u306f\u3001\u30d5\u30a1\u30a4\u30eb\u306e\u7269\u7406\u7684\u306a\u5834\u6240\u3092\u53c2\u7167\u3057\u307e\u3059\u3002\n\n\u753b\u50cf\u30d5\u30a1\u30a4\u30eb\u304cWeb\u30b5\u30fc\u30d0\u30fc\u306b\u3057\u304b\u5b58\u5728\u3057\u306a\u3044\u5834\u5408\u3001\u30c7\u30a3\u30b9\u30d1\u30c3\u30c1\u30e3\u306fWeb\u30b5\u30fc\u30d0\u30fc\u306e\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u4e0a\u3067\u753b\u50cf\u30d5\u30a1\u30a4\u30eb\u3092\u63a2\u305d\u3046\u3068\u3057\u307e\u3059\u304c\u3001\u30a2\u30af\u30bb\u30b9\u304c\u51fa\u6765\u306a\u3044\u7b49\u3067\u30d5\u30a1\u30a4\u30eb\u304c\u898b\u3064\u304b\u3089\u306a\u3044\u5834\u5408\u3001\u753b\u50cf\u304cExcel/PDF\u5f62\u5f0f\u306e\u30ec\u30dd\u30fc\u30c8\u306b\u8868\u793a\u3055\u308c\u307e\u305b\u3093\u3002\n\n\u89e3\u6c7a\u65b9\u6cd5\n\u753b\u50cf\u306eURL\u306f\u4ee5\u4e0b\u306e\u30d1\u30bf\u30fc\u30f3\u3067\u7269\u7406\u7684\u306a\u5834\u6240\u306b\u30de\u30c3\u30d4\u30f3\u30b0\u3055\u308c\u307e\u3059\u3002\n\n\u4f7f\u7528\u3059\u308bURL\u306e\u30d1\u30bf\u30fc\u30f3\u306b\u5fdc\u3058\u3066\u3001\u30d5\u30a1\u30a4\u30eb\u3092\u30c7\u30a3\u30b9\u30d1\u30c3\u30c1\u30e3\u304c\u7a3c\u50cd\u3057\u3066\u3044\u308b\u30b5\u30fc\u30d0\u30fc\u306e\u30d5\u30a9\u30eb\u30c0\u30fc\u306b\u3082\u914d\u7f6e\u3057\u307e\u3059\u3002\n\u76f8\u5bfe\u30d1\u30b9\u304c\u4f7f\u7528\u3055\u308c\u3066\u3044\u308b\u5834\u5408 * ../samples/images/pic.jpg \uff08\"..\"\u3067\u59cb\u307e\u308b\u5834\u5408\uff09\n\n\u30c7\u30a3\u30b9\u30d1\u30c3\u30c1\u30e3\u306f\u4ee5\u4e0b\u306e\u30d5\u30a9\u30eb\u30c0\u30fc\u3092\u53c2\u7167\u3057\u307e\u3059\u3002\n\n/webcontent/samples/images/pic.jpg\n./samples/images/pic.jpg (\".\"\u3067\u59cb\u307e\u308b\u5834\u5408)\n*\n*\n*\n*\n\u7d76\u5bfe\u30d1\u30b9\u304c\u4f7f\u7528\u3055\u308c\u3066\u3044\u308b\u5834\u5408\n\n/pictures/company_logo.gif\u3001C:\\\\images\\company_logo.gif\u3001\\\\NAS\\ci\\company_logo.gif\u7b49\n\n\u6307\u5b9a\u3057\u305f\u7d76\u5bfe\u30d1\u30b9\u304c\u4f7f\u7528\u3055\u308c\u307e\u3059\u3002 \u95a2\u9023\u60c5\u5831\n Images Don't Render in PDF/Excel [http://www.ibm.com/support/docview.wss?uid=swg21622751]\nResolution of images in Cognos 8 and ReportNet [http://www.ibm.com/developerworks/data/library/cognos/page57.html]\nImages in IBM Cognos BI Reports and Analyses [http://www.ibm.com/developerworks/library/ba-pp-infrastructure-cognos_specific_page665/]", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q305", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Unable to view images in reports in PDF/Excel output when using Report Studio/Workspace.\nHowever images are visible in HTML format when reports are run actively.\n\nThe PDF/Excel outputs will have a placeholder image. This will be in the form of an empty black box (PDF) or will be a missing pictures icon (Excel).", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q305", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "There are a few common causes for this issue:\n\n1. The permissions of the folder which contains the image, have not been configured correctly\n 2. The image is not within the directory which is specified\n 3. The directory where the image is meant to be stored, does not exist in the specified location", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q305", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "To find out the root cause of this problem, you will need to use tools that monitor and record all actions attempted against the Operating System Registry.\n\nIn THIS scenario the tool used was Process Monitor and the Web Server was IIS 7.5.\n\n1. Download Process Monitor tool (Make sure you run it from the same machine Cognos is installed on)\n 2. Open up the report in Cognos Workspace\n 3. Load up Process Monitor\n 4. You will notice the current processes immediately being captured and displaying in the window. Press the Capture / Ctrl+E Icon (Magnifying Glass) to stop the capture of events.\n 5. Press the Clear / Ctrl+X icon (Eraser) to remove all the recorded entries.\n 6. Press the capture icon in process monitor\n 7. Export the report to Excel 2007/PDF\n 8. Save the file anywhere\n 9. Press the Capture icon again in process monitor to stop the capturing of events.\n 10. Press the Find Icon / Ctrl+F and type \"[Image Name]\" to make sure the filter image event was captured.\n 11. You should be able to see the reason why the image could not be saved under the 'Result' column.", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q305", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "If the image is found but cannot be accessed due to permission configuration issue:\n\n1. Open up IIS 7.5\n 2. Click on the root folder of your Cognos installation (E.g. C1021GA) in the navigation pane on the left side\n 3. When the root folder is selected, double-click 'Authentication'\n 4. Ensure that anonymous access is enabled\n 5. Repeat steps 3 and 4 for the image folder and it's parent folder.\n 6. If the user is concerned about security, they may want to restrict the child-folders (E.g. cgi-bin) and change the authentication settings accordingly\n 7. Run the report in export as Excel 2007 and PDF\n\nIf the image/ directory is not located:\n\nPlace the image/directory in the specified location\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics Cognos Business Intelligence Cognos Workspace Windows 10.2.1, 10.2", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q305", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "Incomplete or missing Chain of Trust for SSL within the IBM Cognos Keystore", "logical_doc_id": 5, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q305", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "There are two options available:\n\n1. Place the images on the application tier in the Cognos installation directory in the same path they exist on the gateway server. This way the Application Tier can access the image on disk, removing the need to connect to HTTPS\n\nExample: /webcontent/samples/images/pic.jpg\n 2.\n 3. Import the SSL certificate Chain of Trust on the Application Tier.\n\nSteps to import the SSL Chain of Trust:\n 1. Obtain the CA certificate and any Intermediate certificates which is in the chain of the trust that has signed the Web site certificate.\n\n2. Import the certificate(s) in the IBM Cognos CA keystore by typing the following command (from a command window in the /bin directory) where ca.cer is the name of the certificate file:\nThirdPartyCertificateTool.bat -T -i -r ca.cer -k ../configuration/signkeypair/jCAKeystore -p \n\nThe default password for the KeyStore is NoPassWordSet. For example:\nThirdPartyCertificateTool.bat -T -i -r ca.cer -k ../configuration/signkeypair/jCAKeystore -p NoPassWordSet\n\nNote: Ensure that the correct gateway URL with \"https\" at the beginning has been saved in Cognos Configuration for all dispatchers.", "logical_doc_id": 5, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q269", "section_id": 0, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24037250]\n8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24038133]\n8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24038539]\n8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24039425]\n8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040035]\n8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24040533]\n8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041178]\n8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24041819]\n8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]\n8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24043005]\n8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]\n8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q269", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Fail to login to an application with exception:]\n javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.j:\n PKIX path building failed:\n java.security.cert.CertPathBuilderException: unable to find\n valid certification path to requested target.\n\n The application relies on the fact that the Liberty profile\n server sets a SSLContext created with the default SSL\n configuration as the process's default. When running in just\n a Liberty Profile server all is okay. When they run in a\n collective a cert path error is hit. This happens because the\n default SSL Configuration is being used when the app make it's\n httpsURLConnection call.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q269", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of IBM WebSphere Application *\nServer Liberty Profile version 8.5.5 *\nCollective Members. *\n\nPROBLEM DESCRIPTION: Fail to login to an application with *\nSSLHandshakeException on a *\nserver with collectiveMember-1.0 *\nfeature. *\n\nRECOMMENDATION: *\n\n This problem was caused because the code setting the\n SSLSocketFactory for the entire JVM which resulted in\n failure to login to an application with the following\n exception:\n javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.j:\n PKIX path building failed:\n java.security.cert.CertPathBuilderException: unable to find\n valid certification path to requested target.\n This can also be caused by application code doing the same\n thing.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q269", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "We now have instance base setting of the SSL Socket factory on\n the JMXConnector.\n The fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.5.2. Please refer to the Recommended Updates\n page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q269", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI05059\nREPORTED COMPONENT NAME\n LIBERTY PROFILE\nREPORTED COMPONENT ID\n 5724J0814\nREPORTED RELEASE\n 850\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-10-30\nCLOSED DATE\n 2013-11-05\nLAST MODIFIED DATE\n 2014-03-24\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q269", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n LIBERTY PROFILE\nFIXED COMPONENT ID\n 5724J0814", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q269", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R850 PSY\n UP", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q269", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How to generate Common Event Infrastructure events from the rule executions ?\nHow to monitor rule executions with WebSphere Business Monitor ?", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q269", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "The decision trace captured for JRules Decision Warehouse (DW) can be customized so that Common Event Infrastructure (CEI) events are emitted whenever a ruleset, a task or a rule is executed. Based on the rule execution CEI event format, a business rule monitoring model can be defined with the WebSphere Business Monitor Development Toolkit 7.0 in WebSphere Integration Developer 7.0.\nA dashboard can then present the information in Business Space., with graphs such as:\n\n[/support/docview.wss?uid=swg21440000&aid=1] [/support/docview.wss?uid=swg21440000&aid=1]\n\nInstructions to generate CEI events from rule execution events:\njrules-ceitrace.zip [/support/docview.wss?uid=swg21440000&aid=3] [/support/docview.wss?uid=swg21440000&aid=2]\n\n1. Unzip the attached sample jrules-ceitrace.zip to a local folder\n 2. Edit the file jrules-ceitrace/build.xml and modify properties to reflect your environment : jrules.home should point to the base folder of your JRules installation and wps.home to WebSphere Process Server ( or corresponding WebSphere Integration Developer test environment )\n 3. By default this sample generates CEI events without saving the decision trace in DW. If you want to have both DW persistence and CEI events emitted, replace the content of the file jrules-ceitrace/src/dvs-dw.properties with the file jrules-ceitrace/src/dvs-dw-both-dw-and-cei.properties\n 4. From a command line execute : ant build\n 5. Bundle the library jrules-ceitrace/build/jrules-ceitrace.jar with the application executing rules: * If you are using JRules Hosted Transparent Decision Service (HTDS), in jrules-res-htds-.ear/jrules-res-htds-.war/WEB-INF/lib\nIf you are using JRules Scenario Service Provider (SSP) in jrules-ssp-.ear/jrules-ssp-server.war/WEB-INF/lib\nIf you are executing rules from your application, the sample should be packaged alongside the RES session library that your application already bundles\n\n6. On the ruleset(s) that you wish to monitor set the properties: * monitoring.enabled =true\nruleset.trace.sequential.enabled = true (if you are using sequential rule tasks)", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q269", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Instructions to monitor rule CEI events with WebSphere Business Monitor 7:\nwbm-jrules.zip [/support/docview.wss?uid=swg21440000&aid=5] [/support/docview.wss?uid=swg21440000&aid=4] 1. Import the attached sample wbm-jrules.zip in \"WebSphere Integration Developer 7 .0 with WebSphere Business Monitor Development Toolkit 7.0\"\n 2. Right-click on BusinessRulesMonitoring.mm monitoring model, and select Generate Monitor JEE Projects\n 3. Deploy the generated BusinessRuleMonitoringApplication\n 4. Launch Business Space, create a new page named \"Business Rules\" and add an \"Instances\" and a \"Dimensions\" widget\n 5. Configure the widgets to use \"Business Rule Monitoring\" as the monitoring model and choose the \"Rule MC\" monitoring context. Choose to display information such as \"Rule Name\" and \"Execution Date\".\n 6. The CEI events generated with the jrules-ceitrace sample above can then be monitored through these widgets in Business Space. A simple setup is presented here:\n\nwbm-jrules.png [/support/docview.wss?uid=swg21440000&aid=7] [/support/docview.wss?uid=swg21440000&aid=6]\n\nNotes: * Because of issue JR35504 an installation of WebSphere Business Monitor v7.0.0.0 should be upgraded to fix pack 2, for more information see: WebSphere Business Monitor V7.0 Fix Pack 2 (7.0.0.2) [http://www-01.ibm.com/support/docview.wss?uid=swg24026057]\nThe creation of CEI events may require eventCreator credentials, for which either option below can be used : * the thread invoking ruleset executions (and generating CEI events) is authenticated and has an eventCreator role\nthe invocation of ruleset executions happens through an EJB ( or a servlet ) with a runAs configuration to grant an eventCreator role\nthrough the WebSphere Administration console, allow everyone to create CEI events by going in Service integration > Common Event Infrastructure > Event service > Security role to user/group mapping then select eventCreator role and map special subject Everyone\n\n,\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Platform Independent 8.6, 8.5, 8.0, 7.5", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q269", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The following exception is received:\n\n[2/10/14 19:15:16:814 CST] 00000111 wle E CWLLG0594E: An exception occurred while initializing the runnable thread. Error:com.lombardisoftware.component.common.workflow.WorkflowProcessItemException: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.j: PKIX path building failed:java.security.cert.CertPathBuilderException: unable to find valid certification path to requested target in\ncom.ibm.orchestrator.restcall.GenericREST\n\nat com.lombardisoftware.component.common.workflow.ExecutionJob.doJob(ExecutionJob.java:421)\nat com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.doResumeWorkflowEngine(EJBWorkflowManagerBean.java:1287)\nat com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.resumeProcess(EJBWorkflowManagerBean.java:407)\nat com.lombardisoftware.server.ejb.workflow.EJSRemoteStatefulEJBWorkflowManager_82478d70.resumeProcess(Unknown Source)\nat com.lombardisoftware.server.ejb.workflow._EJBWorkflowManagerInterface_St\nub.resumeProcess(_EJBWorkflowManagerInterface_Stub.java:518)\nat com.lombardisoftware.component.common.workflow.EJBWorkflowManagerDelegat\neDefault.resumeProcess(EJBWorkflowManagerDelegateDefault.java:144)\nat com.lombardisoftware.component.common.workflow.EJBWorkflowManagerDelegat\neWebSphere$6.run(EJBWorkflowManagerDelegateWebSphere.java:84)\nat java.security.AccessController.doPrivileged(AccessController.java:280)", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q269", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To resolve the problem, complete the following steps:\n\n1. Restart IBM Business Process Manager from the administrative console. To restart it, click Servers > All servers > SingleClusterServer1.\n\n2. Stop the Deployment Manager by running the /opt/ibm/BPM/v8.5/profiles/DmgrProfile/bin/stopManager.sh command.\n\n3. Restart the Deployment Manager by running the /opt/ibm/BPM/v8.5/profiles/DmgrProfile/bin/startManager.sh command.\n\nYou can access the Administrative Console for IBM Business Process Manager using the following URL syntax: https://:9043/ibm/console\nReplace the variable with the address of the Center Server 4 in your environment.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q269", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do I increase the heap size of the JVM used to run Decision Validation Services (DVS) tests in Rule Studio?", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q269", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "When running DVS tests from Rule Studio against a local Scenario Service Provider (SSP) service, the environment is subject to the memory limitations of the running Eclipse JVM.\n\nYou may encounter the following error:\n\nilog.rules.dvs.util.IlrDVSLogger error\nSEVERE: scenario provider or scenario execution threw exception !\nadding an error to the report java.lang.OutOfMemoryError: Java heap space", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q269", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Use Java options, -Xms (initial heap size) and -Xmx (maximum heap size), to increase the heap size of the JVM used to launch the DVS test.\n\nAs you will be changing the default heap configuration of the JVM, we recommend that you designate a separate JRE for the DVS tests to avoid modifying the workspace default JVM options, which may impact other run configurations.\n\nFollow the steps below:\n\n1. In the DVS run configuration, under the JRE tab, select Alternate JRE. Click Installed JREs\n [/support/docview.wss?uid=swg21427125&aid=1] [/support/docview.wss?uid=swg21427125&aid=1]\n\n2. Select a jdk of your choice and click Duplicate\n [/support/docview.wss?uid=swg21427125&aid=2] [/support/docview.wss?uid=swg21427125&aid=2]\n\n3. Set Default VM arguments: use Java options, -Xms and -Xmx, to tune the JVM heap size. Name the new JRE. Click Finish.\n [/support/docview.wss?uid=swg21427125&aid=3] [/support/docview.wss?uid=swg21427125&aid=3]\n\n4. Click OK in the Preferences window.\n 5. In the Run Configuration window, select the newly added JRE. Click Apply and Run.\n [/support/docview.wss?uid=swg21427125&aid=4] [/support/docview.wss?uid=swg21427125&aid=4]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere ILOG JRules Modules:Rule Studio (Eclipse) Business Integration IBM Operational Decision Manager Modules:Rule Studio Platform Independent 7.5 Enterprise Business Integration IBM Operational Decision Manager Modules:Rule Studio Platform Independent 8.0 Enterprise\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q269", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When assimilating one appliance into another to form a\n two-appliance collective, the assimilation task might fail. The\n following error is displayed in the \"Tasks\" view of the web\n console at the end of the page:\n\ninfo Feb 20, 2013 11:33:21 AM Placed task into queue.\n info Feb 20, 2013 11:33:21 AM Task has begun running.\n info Feb 20, 2013 11:33:21 AM Start the assimilation process\n with the appliance 10.1.1.136.\n info Feb 20, 2013 11:33:22 AM Verify the secret key of\n 10.1.1.136 is valid.\n info Feb 20, 2013 11:33:23 AM Request was validated, now\n requesting the appliance 10.1.1.136 to restart.\n info Feb 20, 2013 11:34:26 AM Stopping the servers on\n appliance 10.1.1.136.\n info Feb 20, 2013 11:35:36 AM Notify appliance 10.1.1.135 of\n new catalog servers.\n info Feb 20, 2013 11:36:03 AM Stopping the servers on\n appliance 10.1.1.135.\n info Feb 20, 2013 11:36:03 AM All appliances have restarted\n with new catalog servers. Restarting 10.1.1.136 now.\n info Feb 20, 2013 11:36:11 AM Restarting appliance\n 10.1.1.135 with the catalog servers [10.1.1.135:2809,\n 10.1.1.136:2809].\n info Feb 20, 2013 11:37:06 AM The appliance 10.1.1.136 has\n successfully restarted with the new catalog servers.\n info Feb 20, 2013 11:37:06 AM The appliance 10.1.1.135 has\n successfully restarted with the new catalog servers.\n error Feb 20, 2013 12:06:11 PM The appliance 10.1.1.135 did\n not restart in the allotted time.", "logical_doc_id": 5, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q269", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Administrators of the IBM WebSphere *\nDataPower XC10 Appliance using appliance *\ncollectives Version 2.1 and higher. *\n\nPROBLEM DESCRIPTION: The appliance assimilation task fails *\nwith an error. *\n\nRECOMMENDATION: Install a firmware version that contains *\nthis APAR. *\n\n During assimilation, the appliance that you assimilate into the\n new appliance (the source appliance), does not restart\n correctly.\n The StartHandler process for the xsa.admin command does not\n have the system SSL properties set early enough during\n processing, which results in the following exceptions that are\n displayed in the xsa.admin log files:\n [2013-03-19 19:17:11:848 EDT] 00000001 XSMBeanHelper W\n com.ibm.ws.xsa.server.mbean.XSMBeanHelper\n getCatalogServerConnection Failed to create connection to\n service:jmx:rmi:///jndi/rmi://10.1.1.137:109\n java.rmi.ConnectIOException: error during JRMP connection\n establishment; nested exception is:\n javax.net.ssl.SSLHandshakeException:\n com.ibm.jsse2.util.h: PKIX path building failed:\n java.security.cert.CertPathBuilderException: unable to find\n valid certification path to requested target\n at\n sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.jav\n a:298)\n at\n sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:1\n 96)\n at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)\n at\n javax.management.remote.rmi.RMIServerImpl_Stub.newClient(RMIServ\n erImpl_Stub.java:53)\n at\n javax.management.remote.rmi.RMIConnector.getConnection(RMIConnec\n tor.java:2338)\n at\n javax.management.remote.rmi.RMIConnector.connect(RMIConnector.ja\n va:288)\n at\n com.ibm.ws.xsa.server.mbean.XSMBeanHelper.getCatalogServerConnec\n tion(XSMBeanHelper.java:282)\n at\n com.ibm.ws.xsa.server.mbean.XSMBeanHelper.getCatalogServerConnec\n tionFromCatalogServers(XSMBeanHelper.java:137)\n at\n com.ibm.ws.xsa.server.mbean.XSMBeanHelper.getPlacementServiceMBe\n an(XSMBeanHelper.java:454)\n at\n com.ibm.websphere.xsa.admin.StartHandler.waitForPlacementConnect\n ion(StartHandler.java:1649)\n at\n com.ibm.websphere.xsa.admin.StartHandler.startCatalogServer(Star\n tHandler.java:1464)\n at\n com.ibm.websphere.xsa.admin.StartHandler.startSequence(StartHand\n ler.java:281)\n at\n com.ibm.websphere.xsa.admin.StartHandler.onStartDaemon(StartHand\n ler.java:128)\n at sun.reflect.NativeMethodAccessorImpl.invoke0(Native\n Method)\n at\n sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor\n Impl.java:60)\n at\n sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod\n AccessorImpl.java:37)\n at java.lang.reflect.Method.invoke(Method.java:611)\n at\n zero.core.interpreter.JavaInterpreter.invoke(JavaInterpreter.jav\n a:64)\n at\n zero.core.events.EventEngine.dispatch(EventEngine.java:305)\n at\n zero.core.events.EventEngine.fire(EventEngine.java:135)\n at zero.core.DaemonManager.start(DaemonManager.java:90)\n at zero.core.tasks.Run.onCliTask(Run.java:44)\n at sun.reflect.NativeMethodAccessorImpl.invoke0(Native\n Method)\n at\n sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor\n Impl.java:60)\n at\n sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod\n AccessorImpl.java:37)\n at java.lang.reflect.Method.invoke(Method.java:611)\n at\n zero.core.interpreter.JavaInterpreter.invoke(JavaInterpreter.jav\n a:64)\n at\n zero.core.events.dispatcher.EventDispatcher.invoke(EventDispatch\n er.java:73)\n at\n zero.core.events.dispatcher.OneDispatcher.invoke(OneDispatcher.j\n ava:43)\n at\n zero.core.events.EventEngine.dispatch(EventEngine.java:305)\n at\n zero.core.events.EventEngine.fire(EventEngine.java:135)\n at zero.core.Main.fireCliTask(Main.java:368)\n at zero.core.Main.invoke(Main.java:345)\n at zero.core.Main.main(Main.java:113)\n Caused by: javax.net.ssl.SSLHandshakeException:\n com.ibm.jsse2.util.h: PKIX path building failed:\n java.security.cert.CertPathBuilderException: unable to find\n valid certification path to requested target\n at com.ibm.jsse2.o.a(o.java:33)\n at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:649)\n at com.ibm.jsse2.kb.a(kb.java:56)\n at com.ibm.jsse2.kb.a(kb.java:502)\n at com.ibm.jsse2.lb.a(lb.java:107)\n at com.ibm.jsse2.lb.a(lb.java:570)\n at com.ibm.jsse2.kb.s(kb.java:327)\n at com.ibm.jsse2.kb.a(kb.java:529)\n at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:300)\n at com.ibm.jsse2.SSLSocketImpl.h(SSLSocketImpl.java:403)\n at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:774)\n at com.ibm.jsse2.k.write(k.java:7)\n at\n java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.ja\n va:76)\n at\n java.io.BufferedOutputStream.flush(BufferedOutputStream.java:134\n )\n at\n java.io.DataOutputStream.flush(DataOutputStream.java:117)\n at\n sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.jav\n a:223)\n ... 34 more\n Caused by: com.ibm.jsse2.util.h: PKIX path building failed:\n java.security.cert.CertPathBuilderException: unable to find\n valid certification path to requested target\n at com.ibm.jsse2.util.f.b(f.java:37)\n at com.ibm.jsse2.util.f.b(f.java:15)\n at com.ibm.jsse2.util.e.a(e.java:19)\n at com.ibm.jsse2.pc.a(pc.java:17)\n at com.ibm.jsse2.pc.checkServerTrusted(pc.java:85)\n at com.ibm.jsse2.pc.b(pc.java:31)\n at com.ibm.jsse2.lb.a(lb.java:49)\n ... 45 more\n Caused by: java.security.cert.CertPathBuilderException: unable\n to find valid certification path to requested target\n at\n com.ibm.security.cert.PKIXCertPathBuilderImpl.buildCertPath(PKIX\n CertPathBuilderImpl.java:642)\n at\n com.ibm.security.cert.PKIXCertPathBuilderImpl.engineBuild(PKIXCe\n rtPathBuilderImpl.java:357)\n at\n java.security.cert.CertPathBuilder.build(CertPathBuilder.java:25\n 8)\n at com.ibm.jsse2.util.f.b(f.java:11)\n ... 51 more\n The assimilation task never finishes in time, which causes the\n error that is displayed in the \"Tasks\" view, and assimilation\n fails.", "logical_doc_id": 5, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q269", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The StartHandler has been corrected to set the SSL properties\n early enough during processing to prevent the error from\n occurring.\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q269", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC91195\nREPORTED COMPONENT NAME\n WSDATAPOWER XC1\nREPORTED COMPONENT ID\n 5765H4200\nREPORTED RELEASE\n 210\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-04-02\nCLOSED DATE\n 2013-04-08\nLAST MODIFIED DATE\n 2013-04-08\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q269", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WSDATAPOWER XC1\nFIXED COMPONENT ID\n 5765H4200", "logical_doc_id": 5, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q269", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R210 PSY\n UP", "logical_doc_id": 5, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q266", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "What is this document:\nThis document has the abstract of a technical article that is available to authorized users after you have logged on. Please use the link to actual document below to access the full document. You will be asked to log on if you are not already logged in. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.\n\nabstract text\nSTEPS TO REPRODUCE:\n\nlink to actual document\nhttp://www.ibm.com/support/docview.wss?uid=swg1PI85964 [http://www.ibm.com/support/docview.wss?uid=swg1PI85964]", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q266", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "You receive one of the following errors:\nFrom the graphical user interface:\nFailed to find all installation files.\n\nMessage ID: CRIMA1161E\n\nInstallation Manager was unable to find all artifacts from input repository. A package has an issue that cannot be resolved by Installation Manager.\n\nCheck the package repository for consistency. Otherwise, identify the package that has the issue by looking at the installation history. In Installation Manager, click File > Installation History. In console mode, enter S: View Installation History. Contact IBM customer support.\n\n'jar file ' not found in .\n\n'zip file ' not found in .\n*\nFrom the command line or console mode:\nCRIMA1154E ERROR: Error installing.\n\nERROR: 'jar file ' not found in .\n\nERROR: 'zip file ' not found in .", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q266", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Packaging Utility deletes additional files when you delete a package or fix from a repository.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q266", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "This issue has been fixed in Packaging Utility version 1.6.\n\nTo work around this issue, use Packaging Utility to recopy the affected package or fix from the original source to the repository that is missing files.\n\nIBM Packaging Utility; Version 1005 fix pack; Packaging Utility; v1005; fix pack 1005; 1005; fix pack DOWNLOADABLE FILES", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q266", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This document describes how to download and install this fix pack to IBM Packaging Utility, Version 1.0.", "logical_doc_id": 2, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q266", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "IMPORTANT: This update has been superseded and is no longer available for download from ibm.com. You should update your product with the most recent version available. See http://www.ibm.com/support/docview.wss?uid=swg27025142 [http://www.ibm.com/support/docview.wss?uid=swg27025142] [http://www-01.ibm.com/support/docview.wss?rs=2042&uid=swg27007823] for the most recent version.\n\nThis fix pack contains fixes to the version 1.0 release of IBM Packaging Utility.\n\nThe IBM\u00ae Packaging Utility is a program used to generate a new repository for packages, copy packages to a new repository, and delete packages that are no longer needed.\n\nPREREQUISITES\nBefore you can install this fix pack, you must install IBM Installation Manager, Version 1.0.0.5; by default, it is automatically installed when you attempt to update or install packages by using an earlier version.\n\nFor more information, refer to the version 1.0.0.5 readme file.\n\nURL LANGUAGE SIZE(Bytes) IBM Packaging Utility v1.0.0.5 Readme [http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/pu/1005/docs/readme/readme.html] English 26000\nINSTALLATION INSTRUCTIONS\nTo download and install the fix pack:\n\n1.\n 2. Download the fix pack from the download URL below.\n 3.\n 4. Extract the compressed file in an appropriate directory. For example, choose to extract to C:\\temp.\n 5.\n 6. Add the fix pack's repository location in IBM Installation Manager:\n 1.\n 2. Start IBM Installation Manager.\n 3.\n 4. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.\n 5.\n 6. On the Repositories page, click Add Repository.\n 7.\n 8. On the Add repository window, browse to and enter the file path to the C:\\temp\\pu\\updates directory. For example, enter C:\\temp\\pu\\updates\\repository.config and then click OK.\n 9.\n 10. Click OK to close the Preference page.\n\n7.\n\nIf IBM Packaging Utility is currently installed, you can perform an update to install this version by completing the following steps:\n\n1. On the Start page of Installation Manager, click Update Packages.\n 2.\n 3. Select IBM Packaging Utility and follow the wizard pages to update it.\n\nIf IBM Packaging Utility is not currently installed, install it by completing the following steps:\n\n1. On the Start page of Installation Manager, click Install Packages\n 2.\n 3. Select IBM Packaging Utility and follow the wizard pages to install it.\n 4.\n\nDOWNLOAD PACKAGE\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] pu-1.0.0.5.zip 7/13/2007 English 156511190 HTTP [http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/pu/1005/zips/pu-1.0.0.5.zip]\nTECHNICAL SUPPORT\n IBM Rational Software Support provides you with technical assistance.", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q266", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "For contact information and guidelines or reference materials that you will need when you require support, read the IBM Software Support Handbook at: http://techsupport.services.ibm.com/guides/handbook.html [http://techsupport.services.ibm.com/guides/handbook.html]\n\nBefore you contact IBM Rational Software Support, gather the background information that you will need to describe your problem. When describing 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* 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* Are you using a workaround for the problem? If so, be prepared to describe the workaround.\nCross reference information Segment Product Component Platform Version Edition Software Development Rational Application Developer for WebSphere Software Packaging Utility Windows, Linux 7.0.0.3 Software Development Rational Software Architect Packaging Utility Linux, Windows 7.0.0.3 Software Development Rational Software Modeler Packaging Utility Windows, Linux 7.0.0.3 Software Development Rational Systems Developer Packaging Utility Linux, Windows 7.0.0.3 Software Development Rational Modeling Extension for Microsoft .NET Packaging Utility Linux, Windows 7.0.0.3 Software Development Rational Business Developer Extension Linux, Windows 7.0.0.3 Software Development Rational Functional Tester Packaging Utility 7.0.0.2\n\nservice release; modpack; mod pack; upgrade; refresh; refresh pack DOWNLOADABLE FILES", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q266", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "IBM Packaging Utility 1.8 has been made generally available and contains any fixes for client-reported and internally found defects.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q266", "section_id": 3, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Table of Contents Sections Description * What's new\n\nThe Change history section provides an overview on what is new in this release with a description of any new functions or enhancements when applicable.\nImpact assessment\n\nThe How critical is this fix section provides information related to the impact of this release to allow you to assess how your environment may be affected.\nPrerequisites\n\nThe Prerequisites section provides important information to review prior to the installation of this release.\nDownload package\n\nThe Download package section provides the direct link to obtain the download package for installation in your environment.\nInstallation instructions\n\nThe Installation instructions section provides the installation instructions necessary to apply this release into your environment.\nKnown problems\n\nThe Known side effects section contains a link to the known problems (open defects) identified at the time of this release.\n\nSupporting Documentation Document Description * Detailed System Requirements [http://www.ibm.com/support/docview.wss?uid=swg27036456]\n\nClick to review the detailed system requirements information for a complete list of hardware requirements, supported operating systems, prerequisites and optional supported software, with component-level details and operating system restrictions.\nIBM Knowledge Center [http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.0/com.ibm.cic.auth.ui.doc/helpindex_pu.html]\n\nIBM Knowledge Center provides an entry point to product documentation. You can view, browse, and search online information related to the product.\nFix List [http://www.ibm.com/support/docview.wss?uid=swg27036454#tab_1.8]\n\nClick to review a complete list of the defects (APARs) resolved in this release including a list of resolved defects for the entire version family.\n\nPREREQUISITES\n\nPrerequisites include: Review the Detailed System Requirements [http://www.ibm.com/support/docview.wss?uid=swg27036456] for any prerequisites required for this release.\n\nBack to top\n\nINSTALLATION INSTRUCTIONS\n\nUse Installation Manager to install and update Packaging Utility. If Installation Manager is installed, you can use the Packaging Utility repository on www.ibm.com to install or update Packaging Utility without downloading files. If Installation Manager is not installed, you must download the Packaging Utility files. Installation Manager is included in the Packaging Utility download packages.\n\nThe installer package for Packaging Utility is pu.offering.disk.platform_version.zip where platform indicates the operating system and version indicates the version of Packaging Utility. The installer package contains files for only one platform. Using this package, you can install Packaging Utility and Installation Manager by running the install command. You can also add this package as a repository in Installation Manager and use the package to update Packaging Utility.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q266", "section_id": 3, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "The fix pack package for Packaging Utility is pu.update_version.zip. The fix pack contains files for all supported platforms. You can add this fix pack as a repository to update Packaging Utility. You cannot install Packaging Utility or Installation Manager with this fix pack.\n\nPackaging Utility is available in 64-bit mode. Review information information about bit mode for installation or updates: Packaging Utility bit mode information [https://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.0/com.ibm.cic.auth.ui.doc/topics/r_pu_bit_mode.html].\n\nFor more information about Packaging Utility and Installation Manager, Review the Installation Manager Knowledge Center [http://www.ibm.com/support/knowledgecenter/SSDV2W/im_family_welcome.html].\n\nINSTALL OR UPDATE PACKAGING UTILITY WITHOUT DOWNLOADING FILES\nYou must have Internet access and Installation Manager must be installed to install or update Packaging Utility without downloading files. The Packaging Utility repository located on www.ibm.com contains the latest version of Packaging Utility.\n\nYou must have an IBM user name and password to access the repository. To register for these credentials, go to: http://www.ibm.com/account/profile.\n\nIBM Knowledge Center topics that are specified by operating system for installing and updating Packaging Utility. The installation topics contain information about downloading the Installation Manager installation files.\n\nOperating System Action Packaging Utility topic located in the IBM Installation Manager Knowledge Center Windows\nLinux\nUNIX\nMac OS X operating system Installation Installing Packaging Utility in wizard mode [http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.0/com.ibm.cic.auth.ui.doc/topics/r_pu_wm.html] Installing Packaging Utility by using console mode [http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.0/com.ibm.cic.commandline.doc/topics/t_pu_console_install.html] Installing or updating Packaging Utility by using imcl commands [http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.0/com.ibm.cic.commandline.doc/topics/t_pu_install_imcl.html] Update Updating Packaging Utility in wizard mode [http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.0/com.ibm.cic.auth.ui.doc/topics/t_pu_update.html] Updating Packaging Utility by using console mode [http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.0/com.ibm.cic.commandline.doc/topics/t_pu_console_update.html] Installing or updating Packaging Utility by using imcl commands [http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.0/com.ibm.cic.commandline.doc/topics/t_pu_install_imcl.html] IBM z/OS Installation Installing Packaging Utility by using console mode [http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.0/com.ibm.cic.commandline.doc/topics/t_pu_console_install.html] Installing or updating Packaging Utility by using imcl commands [http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.0/com.ibm.cic.commandline.doc/topics/t_pu_install_imcl.html] Update Updating Packaging Utility by using console mode [http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.0/com.ibm.cic.commandline.doc/topics/t_pu_console_update.html] Installing or updating Packaging Utility by using imcl commands [http://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.0/com.ibm.cic.commandline.doc/topics/t_pu_install_imcl.html]\nBack to top\n\nDOWNLOAD PACKAGE\n\nThe following sections provide detailed information related to this release.\n\nClick the FC link below to obtain the release from Fix Central.\n\nHOW CRITICAL IS THIS FIX?\n\nImpact Assessment Impact Description Recommended This is a service release. It contains new features as well as fixes for client-reported and internally found defects.\n\nTest Results\n\nClose [x]", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q266", "section_id": 3, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "DEFINITIONS\nRegression: An error in the Maintenance Delivery Vehicle [http://www.ibm.com/support/docview.wss?uid=swg27008656] (MDV) that produces incorrect or unexpected behavior causing a supported feature to stop functioning as designed.\nThis includes:\nCoding errors that cause a regression\nDocumentation or packaging problems that cause a regression\nErrors reported in a new function delivered in a MDV that cause a regression\n\nIncomplete: An error in the MDV has not regressed, but does not work as designed.\nThis includes:\nFixed APARs which did not solve the original problem but did not break anything new\nAPARs reporting documentation errors, such as readme errors, that cause problems applying an MDV but do not lead to a regression\n\nNotes: * Regression and incomplete APARs are considered fix-in-error or MDV-in-error\nDefinitions above apply only to valid APARs that result in product fixes (APARs returned as working-as-designed are not assessed for being fix-in-error)\nIssues in major releases due to new functionality do not apply in this definition\n\nThere are no known regressions to report.\n\nBack to top\n\nPROBLEMS SOLVED\n\nDefects resolved Click the Fix List link in the table of contents above to review a list of the problems solved in this release.\n\nKNOWN SIDE EFFECTS\n\nReview the following list of known issues and open defects: There are no known issues report.\n\nOPEN DEFECTS\nReview the following list of open defects for IBM Installation Manager and Packaging Utility [https://www-947.ibm.com/support/entry/myportal/search_results/rational/ibm_installation_manager?sn=spe&q=%22APAR%20status%22%20OPEN&prod=N340276G72802P18&filter=language:en&productContext=864296863#q%3D%22APAR%20status%22%20OPEN%26filter%3DDC.Type%3ACT748%2Blanguage%3Aen%26prod%3DN340276G72802P18] on the IBM Support Portal.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q266", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Review technote 1461170: Open APARs for Rational products available on the Web [http://www.ibm.com/support/docview.wss?uid=swg21461170] for information on how to configure your MyNotifications subscription account and subscribe to the APARs you are interested in following.\n\nBack to top\n\nCHANGE HISTORY\n\nWhat's new No new features or functions.\n\nBack to top\n\nClick the link in the Download Options column:\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] Packaging Utility downloads (1.8) 11 Sep 2014 English 1 FC [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7ERational&product=ibm/Rational/IBM+Packaging+Utility&release=All&platform=All&function=all&source=fc] [ ]\nTECHNICAL SUPPORT\n\nTAB NAVIGATION\nGeneral Support Information- selected tab,\nSupport Resources [http://www.ibm.com/support/docview.wss?uid=swg27020747]- selected tab,\n\nIBM Rational Software Support Communities\nVisit 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.\nVisit 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/].\nVisit 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\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:\nWhat software versions were you running when the problem occurred?\nDo you have logs, traces, or messages that are related to the problem?\nCan you reproduce the problem? If so, what steps do you take to reproduce it?\nIs 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\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\nBack to top", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q266", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Different symptoms occur depending on the version of Linux and shells that you use.\nNo feedback when you start Packaging Utility.\n\nYou start Packaging Utility from a Terminal window running a shell, and change the directory to the installation location of the IBMPU executable. You execute IBMPU. The command returns without providing feedback:\n$ cd /opt/IBM/PackgingUtility\n$ ./IBMPU\n$\nYou receive the message: \"no such file or directory\"\n\n$ ./IBMPU\nbash ./IBMPU no such file or directory\n$\nYou receive the message: \"bad ELF interpreter\"\n\n$./IBMPU\n./IBMPU bash: ./install: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory\nCheck if Packaging Utility is 32-bit\n\nUse the file command to identify a 32-bit executable:\n\n$ file ./IBMPU\n./IBMPU: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.2.5, not stripped\nTest the 32-bit Java Runtime Environment (JRE)\n\nThe IBMPU executable invokes a program written in Java. Verify that the 32-bit JRE does not run by changing to the jre folder and executing the java command with the -version parameter. Similar results as executing the ./IBMPU are shown:\n$ cd /opt/IBM/PackgingUtility/jre/bin\n$ ./java\nbash: ./java no such file or directory\n$ file ./java\n./java: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.2.5, not stripped", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q266", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The required 32-bit libraries are not installed on the computer.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q266", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To work around this issue, take one of the following actions:\nInstall a new instance of Packaging Utility version 1.6 and select the 64-bit package group.\nInstall the 32-bit libraries that are required to support a 32-bit program", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q266", "section_id": 0, "heading": "RELATED INFORMATION", "parent": null, "text": "#Issues starting or running Installation Manager [http://www-01.ibm.com/support/docview.wss?uid=swg21438776]", "logical_doc_id": 5, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q188", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "IBM Java ORB : What happened to Visibroker?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q188", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Visibroker was replaced by the IBM Java ORB in 2012", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q188", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "The Visibroker CORBA software is being phased out of the integrations product line. New probes will use the ORB provided with the IBM JRE included within the base installation of Netcool/OMNIbus. Ensure the probes readme or description files are read before installation to ensure that the necessary dependencies are installed first.\n\nThe dumpnameservice.sh utility uses Visibroker [not Visibroker8] and Visibroker needs to be installed to use it.\n\nIts replacement is dumpns, as provided with the latest CORBA framework package [probe-corba-framework 3_0 or above]. The command is located in the $NCHOME/omnibus/probes/java/corba directory and takes the host port as arguments.\n\nYou can also use the standard jacorb.jar to dump the name service contents using this syntax:\njava -cp /tmp/jacorb.jar org.jacorb.naming.ContextLister -url corbaloc:iiop::/NameService\n\nListing output:\nTMF_MTNM.Class/\nTejasNetworks.Vendor/\nTejasNetworks\\/NORTH-CDG.EmsInstance/\n3\\.5.Version/\nTejasNetworks\\/NORTH-CDG.EmsSessionFactory_I\n\nExample probe property:\nNamingContextPath: \"TMF_MTNM.Class/TejasNetworks.Vendor/TejasNetworks\\\\/NORTH-CDG.EmsInstance/3\\\\.5.Version/TejasNetworks\\\\/NORTH-CDG.EmsSessionFactory_I\"\n\nNote : jacorb.jar is available from the JACORB JAR download link.\n\nDebugging the Java ORB:\n\nThe latest CORBA framework allows probes to use the ORB debugging properties:\n\ne.g.\nORBDebug : 'true'\nORBDebugFile : '/tmp/orb_debug.log'\n\nUse the -dumpprops option on the probe to see if these properties are available or not.\n\nTo manually debug the IBM Java ORB the probe specific environment file needs to be modified as described below:\n\nEdit or create the $OMNIHOME/probes/java/nco_p_.env file and add the following line to enable IBM ORB trace logging.\n\nNCO_JPROBE_JAVA_FLAGS=\"-Dcom.ibm.CORBA.Debug=true -Dcom.ibm.CORBA.CommTrace=true -Dcom.ibm.CORBA.Debug.Output=$OMNIHOME/log/ibm_orb_trace.log $NCO_JPROBE_JAVA_FLAGS\"\n\nNotes:\nThe ORB debugging should not be enabled unless required and not left running in a production environment unless requested by IBM Tivoli Netcool support.\n\nIf the property ORB debugging is available in the probe, the manual java option method does not work.\n\nIf the probe reports encoding issues when used with the IBM Java ORB set the probe properties as shown below before contacting support;\nORBWCharDefault : \"UTF16\"\nORBCharEncoding : \"ISO8859_1\"", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q188", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#JACORB JAR download [http://www.jacorb.org/download.html]", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q188", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "MTTrapd probe : How can you troubleshoot configuration issues?", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q188", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "The MTTrapd (SNMP) probe is a Generic probe used to process SNMP traps.\nIt is a multi-threaded probe and supports both UDP and TCP traps/informs.\n\nThe attached Support's guide to the SNMP probe provides details on how best to configure the probe, troubleshoot issues and how to use third party products to test the probes behaviour.\n\nThe latest probe version is:\nRelease ID: 20.0.2\nOr higher.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q188", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "Where to locate the latest MTTrapd probe release 20.0.2 [https://developer.ibm.com/answers/questions/414820/where-do-you-download-the-mttrapd-probe-release-20/]\n\nSNMP_MTTRAPDProbe_SupportsGuide_22.pdf [/support/docview.wss?uid=swg21607690&aid=2]SNMP_MTTRAPDProbe_SupportsGuide_22.pdf [/support/docview.wss?uid=swg21607690&aid=1]", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q188", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Support Guides : Which Support Guides are available?", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q188", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Users find it useful to have a list of all available guides", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q188", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "A list of the available Support Guides is given in the links below.\n\nThe Support Guides documentation is mostly a collection of technical documentation that supplements the main user reference guides for specific integrations.\n\nWithin these guides there are worked examples for at least one UNIX platform, and recommended configurations.\n\nThe rest of the documentation provides examples of specific tasks, such as event replication and the controlled re-synchronisation of events.\n\nNOTE: You can use the search text \"Support's Guide [product]\" to see if anything is available if you find you need to get to the link outside of this FAQ.\n\nFor example, \"Support's Guide\" will list all of the guides when entered into the Netcool/OMNIbus search portal.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q188", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "Support's Guide to the JDBC Gateway [http://www-01.ibm.com/support/docview.wss?uid=swg21608681]\nSupport's Guide to the ODBC Gateway [http://www-01.ibm.com/support/docview.wss?uid=swg21607700]\nSupport's Guide to the Oracle Gateway [http://www-01.ibm.com/support/docview.wss?uid=swg21588025]\nSupport's Guide to Historical Reporting gateways [http://www-01.ibm.com/support/docview.wss?uid=swg21637022]\nSupport's Guide to the SNMP Gateway [http://www-01.ibm.com/support/docview.wss?uid=swg21622160]\nSupport's Guide to the Message Bus Integration [http://www-01.ibm.com/support/docview.wss?uid=swg21622274]\nSupport's Guide to production triggers [http://www-01.ibm.com/support/docview.wss?uid=swg21615136]\nSupport's Guide to sub-second triggers [http://www-01.ibm.com/support/docview.wss?uid=swg21591539]\nSupport's Guide to Probe Event Replication [http://www-01.ibm.com/support/docview.wss?uid=swg21607694]\nSupport's Guide to the SNMP [MTTrapd] probe [http://www-01.ibm.com/support/docview.wss?uid=swg21607690]\nSupport's Guide to the Nortel IEMS Probe [http://www-01.ibm.com/support/docview.wss?uid=swg21607701]\nSupport's Guide to the Multi-Headed NT Log File Probe [http://www-01.ibm.com/support/docview.wss?uid=swg21607710]\nSupport's guide to the ODBC Probe [http://www-01.ibm.com/support/docview.wss?uid=swg21607732]\nSupport's guide to the Tivoli EIF Probe [http://www-01.ibm.com/support/docview.wss?uid=swg21622152]\nSupport's guide to the SCOM 2007 R1 Probe on Windows [http://www-01.ibm.com/support/docview.wss?uid=swg21618671]\nSupport's Guide to the Alcatel 5620 SAM Probe [http://www-01.ibm.com/support/docview.wss?uid=swg21614211]\nSupport's Guide to IBM CORBA probes [http://www-01.ibm.com/support/docview.wss?uid=swg21614208]\nSupport's Guide to Sub-second Events in a Multitier Env [http://www-01.ibm.com/support/docview.wss?uid=swg21967283]\nSupport's Guide to the EIF MUX [http://www-01.ibm.com/support/docview.wss?uid=swg21957943]\nSupport's Guide to the Ping Probe [http://www-01.ibm.com/support/docview.wss?uid=swg21682130]\nSupport's Guide to Q3 Probes [http://www-01.ibm.com/support/docview.wss?uid=swg21697361]\nSupport's guide to Netcool/OMNIbus performance tuning [http://www-01.ibm.com/support/docview.wss?uid=swg21978376]\nSupport's Guide to the Tivoli EIF Gateway [http://www-01.ibm.com/support/docview.wss?uid=swg21994650]\nNetcool Support's Guide to Object Server Backup and Rec [http://www-01.ibm.com/support/docview.wss?uid=swg22002788]\nSupport's Guide to rules file processing [http://www-01.ibm.com/support/docview.wss?uid=swg21903536]\nSupport's Guide to the SOCKET Probe and Gateway [http://www-01.ibm.com/support/docview.wss?uid=swg21971139]\nSupport's Guide to the Syslog probe [http://www-01.ibm.com/support/docview.wss?uid=swg21987143]", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q188", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "SCOM 2007 probe : Where is the probe documentation?", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q188", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The SCOM 2007 Probe was replaced with the SCOM 2007 R2 probe", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q188", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "The SCOM 2007 probe for UNIX has been withdrawn, as has the Windows version. The Windows version was replaced with the SCOM 2007 R2 probe. The two version's of the SCOM 2007 probes are configured differently.\n\nIt is recommend that the SCOM 2007 probe is upgraded to the SCOM 2007 R2 probe.\nPlease review the probes documentation and plan the upgrade.\n\nnco_p_scom2007_r2\nMicrosoft SCOM 2007 R2\nMicrosoft SCOM 2007 Service Pack 1\nMicrosoft SCOM 2007\n\nFor completeness, and to provide limited documentation, Support's guide to the SCOM 2007 R1 probe is provided.\n\nNote: There is a probe specifically for SCOM 2012:\nnco_p_scom2012 * Microsoft SCOM 2012\n\nAdditionally : The Microsoft Operations Manager Probe was withdrawn in August 2014, with software support ending on 30th June 2015.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q188", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "SCOM R2 GA Link [http://www-01.ibm.com/support/docview.wss?uid=swg21569004]\n\nSCOM2007R1WindowsONLYTechDoc.pdf [/support/docview.wss?uid=swg21618671&aid=2]SCOM2007R1WindowsONLYTechDoc.pdf [/support/docview.wss?uid=swg21618671&aid=1]", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q188", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "IBM CORBA probe : What happened to the visibroker patches?", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q188", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Visibroker was replaced by the IBM CORBA integration", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q188", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "The Visibroker software is a third party product, and was replaced in 2012 by the IBM CORBA software.\n\nPlease review Support's Guide to IBM CORBA probes [attached] to understand the integration, alongside the probe's specific documentation.\n\nGENERIC_CORBA_SupportsGuide_20.pdf [/support/docview.wss?uid=swg21614208&aid=2]GENERIC_CORBA_SupportsGuide_20.pdf [/support/docview.wss?uid=swg21614208&aid=1]", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q092", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What versions of Tivoli Workload Scheduler (TWS) are supported with Oracle 12c?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q092", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Oracle 12c is supported with IBM Workload Scheduler (IWS) v9.1, v9.2, and v9.3.\n\nNOTE: You can check the compatibility of TWS with various components by using the Software Product Compatibility Reports (SPCR) website:\nhttp://www.ibm.com/software/reports/compatibility/clarity/index.html [http://www.ibm.com/software/reports/compatibility/clarity/index.html]\n\nPRODUCT ALIAS/SYNONYM\n Maestro\nTWS\nIWS\nTWA", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q092", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Is it possible to use Oracle 12c with IBM Enterprise Integrator for Domino 9.0.1?", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q092", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Yes, IBM Enterprise Integrator for Domino 9.0.1 supports Oracle 12c on platforms Windows 2008 / R2 / 2012, RHEL 6, SLES 11 and AIX 7.1 as native client and ODBC. You should install the Oracle 12c client as per Oracle documentation on the machine for using as native client. You can use Oracle 12c similarly as with earlier versions of Oracle.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q092", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "VA and unsupported patch detected for Oracle 12.1.0.2.0\n\nGuardium VA and Oracle 12c datapatch", "logical_doc_id": 2, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q092", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Based on Oracle documentation, it is always recommended to apply post-upgrade step after applying database patch. If you are using Oracle 12c or newer, it is recommended to run datapatch. If you are using Oracle 10 and 11, then you should do the @catbundle.sql psu apply. For more information on these post-upgrade step, please refer to Oracle support portal for more instruction.\n\nIf customer database does not show anything in the DBA_REGISTRY_SQLPATCH view, then it is likely that the DBA never applied the post database patch step.\n\nSee these Oracle references and make sure datapatch is run to make sure the database is upgraded.\n\nhttps://blogs.oracle.com/UPGRADE/entry/dbua_and_datapatch_some_things [https://blogs.oracle.com/UPGRADE/entry/dbua_and_datapatch_some_things]", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q092", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "VA and unsupported patch detected for Oracle 12.1.0.2.0", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q092", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The post-upgrade datapatch execution in Oracle 12.1.0.2 is not completed.\n\nThe solution is to apply the SQL changes manually after the DBA has completed the database upgrade to Oracle Database 12c:\n\ncd $ORACLE_HOME/OPatch\n\n./datapatch -verbose\n\nhttps://www.pythian.com/blog/oracle-database-12c-patching-dbms_qopatch-opatch_xml_inv-and-datapatch/ [https://www.pythian.com/blog/oracle-database-12c-patching-dbms_qopatch-opatch_xml_inv-and-datapatch/]\n\nWith Oracle 11g the latest patch is applied within the database using:\n\nSQL> @catbundle.sql psu apply", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q092", "section_id": 0, "heading": "Summary", "parent": null, "text": "Oracle 12c introduced a new utility called datapatch which replaces the need to run the 11g command shown above.\n\nAs with Oracle 11g, you first install the patch into the Oracle Home with all services & databases down. But with Oracle Database 12c, after restarting the database, simply run datapatch from the OPatch directory:\n\ncd $ORACLE_HOME/OPatch\n\n./datapatch -verbose\n\nNow, the customer is saying that they installed a fresh new Oracle 12c and then patched the server. Then they created the database and ran select * from dba_registry_sqlpatch and no record was found. That because they did not run the datapatch step. The customer then questioned whether they need to run datapatch or not since this database is created after the server patch. That is a good question.\n\nLet's look at the possible scenario.\n\nIf you don't run datapatch, then dba_registry_sqlpatch will have 0 row. There is no way for Guardium's Vulnerability Assessment to know if you really did patch the database or not as there is no other way to find this information by doing a JDBC connection. That is why when the Guardium test ran, it showed \"Unsupported CVE database patch detected\" as Guardium found nothing or potentially something that Guardium does not recognize and would not be able to parse it. Guardium cannot simply fail the test as failing it may or may not be the desired result. One can argue that I don't need to run datapatch because this database is created after the server was patched. This assumption may or may not be correct depending on how the database is created.\n\nTherefore, Guardium recommends running the datapatch step regardless. Also this is an abnormal case where it would only happen during the first few months of your database creation. After that, you would need to patch your database on a quarterly basis to satisfy Oracle security, so you will have to run datapatch each time.\n\nIn an Oracle database, when the server is patched and a new database is created, here is what happens in dba_registry_sqlpatch\n\nSELECT VERSION, FLAGS, DESCRIPTION, BUNDLE_ID, BUNDLE_SERIES\n\nFROM DBA_REGISTRY_SQLPATCH\n\nWHERE ACTION = 'APPLY'\n\nAND STATUS = 'SUCCESS'\n\nAND VERSION = (SELECT SUBSTR(VERSION,1,LENGTH(VERSION) -2) FROM V$INSTANCE)\n\nAND FLAGS LIKE '%B%'\n\nAND ACTION_TIME = (SELECT MAX(ACTION_TIME)\n\nFROM DBA_REGISTRY_SQLPATCH\n\nWHERE ACTION = 'APPLY'", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q092", "section_id": 0, "heading": "Summary", "parent": null, "text": "AND STATUS = 'SUCCESS'\n\nAND VERSION = (SELECT SUBSTR(VERSION,1,LENGTH(VERSION) -2) FROM V$INSTANCE)\n\nAND FLAGS LIKE '%B%');\n\nSELECT VERSION, FLAGS, DESCRIPTION, BUNDLE_ID, BUNDLE_SERIES\n\nFROM DBA_REGISTRY_SQLPATCH\n\nWHERE ACTION = 'APPLY'\n\nAND STATUS = 'SUCCESS'\n\nAND VERSION = (SELECT SUBSTR(VERSION,1,LENGTH(VERSION) -2) FROM V$INSTANCE)\n\nAND FLAGS LIKE '%J%'\n\nAND ACTION_TIME = (SELECT MAX(ACTION_TIME)\n\nFROM DBA_REGISTRY_SQLPATCH\n\nWHERE ACTION = 'APPLY'\n\nAND STATUS = 'SUCCESS'\n\nAND VERSION = (SELECT SUBSTR(VERSION,1,LENGTH(VERSION) -2) FROM V$INSTANCE)\n\nAND FLAGS LIKE '%J%');\n\nVERSION FLAGS DESCRIPTION BUNDLE_ID BUNDLE_SERIES\n--------- -------- -------------- ------------ ----------------\n\n0 record(s) selected [Fetch MetaData: 0ms] [Fetch Data: 0ms]\n\n[Executed: 7/12/2016 12:55:47 PM] [Execution: 25ms]\n\nVERSION FLAGS DESCRIPTION BUNDLE_ID BUNDLE_SERIES\n--------- -------- -------------- ------------ ----------------\n\n0 record(s) selected [Fetch MetaData: 0ms] [Fetch Data: 0ms]\n\nAfter running datapatch.\n\nSELECT VERSION, FLAGS, DESCRIPTION, BUNDLE_ID, BUNDLE_SERIES\n\nFROM DBA_REGISTRY_SQLPATCH\n\nWHERE ACTION = 'APPLY'\n\nAND STATUS = 'SUCCESS'\n\nAND VERSION = (SELECT SUBSTR(VERSION,1,LENGTH(VERSION) -2) FROM V$INSTANCE)\n\nAND FLAGS LIKE '%B%'\n\nAND ACTION_TIME = (SELECT MAX(ACTION_TIME)\n\nFROM DBA_REGISTRY_SQLPATCH\n\nWHERE ACTION = 'APPLY'\n\nAND STATUS = 'SUCCESS'\n\nAND VERSION = (SELECT SUBSTR(VERSION,1,LENGTH(VERSION) -2) FROM V$INSTANCE)\n\nAND FLAGS LIKE '%B%');\n\nSELECT VERSION, FLAGS, DESCRIPTION, BUNDLE_ID, BUNDLE_SERIES\n\nFROM DBA_REGISTRY_SQLPATCH\n\nWHERE ACTION = 'APPLY'\n\nAND STATUS = 'SUCCESS'\n\nAND VERSION = (SELECT SUBSTR(VERSION,1,LENGTH(VERSION) -2) FROM V$INSTANCE)\n\nAND FLAGS LIKE '%J%'\n\nAND ACTION_TIME = (SELECT MAX(ACTION_TIME)\n\nFROM DBA_REGISTRY_SQLPATCH\n\nWHERE ACTION = 'APPLY'\n\nAND STATUS = 'SUCCESS'\n\nAND VERSION = (SELECT SUBSTR(VERSION,1,LENGTH(VERSION) -2) FROM V$INSTANCE)\n\nAND FLAGS LIKE '%J%');\n\nVERSION FLAGS DESCRIPTION BUNDLE_ID BUNDLE_SERIES\n--------- -------- ------------------------------------------------------- ------------ ----------------\n\n12.1.0.2 NB WINDOWS DB BUNDLE PATCH 12.1.0.2.160119(64bit):22310559 160119 PSU\n\n1 record(s) selected [Fetch MetaData: 0ms] [Fetch Data: 0ms]\n\nVERSION FLAGS DESCRIPTION BUNDLE_ID BUNDLE_SERIES\n-------------------------------------------------------------------- ------------ ----------------\n\n12.1.0.2 UJJ WINDOWS ORACLE JAVAVM COMPONENT BUNDLE PATCH 12.1.0.2.160119(64bit):22311086 (null) (null)\n\n1 record(s) selected [Fetch MetaData: 0ms] [Fetch Data: 1ms]", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q092", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "The IBM Emptoris Strategic Supply Management Suite, IBM Emptoris Rivermine Telecom Expense Management and IBM Emptoris Services Procurement products are affected by multiple security vulnerabilities that exist in the IBM SDK Java Technology Edition that is shipped with IBM WebSphere Application Server. The issues are disclosed in the Oracle Oct 2014 Java SE Critical Patch Update.", "logical_doc_id": 4, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q092", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566]\n\nDESCRIPTION: Product could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plaintext of encrypted connections.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/97013 [https://exchange.xforce.ibmcloud.com/vulnerabilities/97013] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)\n\nCVEID: CVE-2014-6457 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6457]\n\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE and JRockit related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.\n\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/97148 [https://exchange.xforce.ibmcloud.com/vulnerabilities/97148] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N)", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q092", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Emptoris Contract Management 9.5 through 10.0.2.5\nIBM Emptoris Program Management 10.0.0 through 10.0.2.5\nIBM Emptoris Sourcing 10.0.0 through 10.0.2.5\nIBM Emptoris Spend Analysis 10.0.0 through 10.0.2.5\nIBM Emptoris Supplier Lifecycle Management 9.5 through 10.0.2.5\nIBM Emptoris Strategic Supply Management 10.0.0 through 10.0.2.5\nIBM Emptoris Rivermine Telecom Expense Management 6.5.x through 7.0.1\nIBM Emptoris Services Procurement 10.0.0", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q092", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "An interim fix has been issued for the IBM WebSphere Application Server which will upgrade the IBM Java Development Kit to a version which is not susceptible to this vulnerability. Customers running any of the IBM Emptoris products listed above should apply the interim fix to all IBM WebSphere Application Server installations that are used to run IBM Emptoris applications. See Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect WebSphere Application Server Oct 2014 CPU [https://www-304.ibm.com/support/docview.wss?uid=swg21687740] [http://www-01.ibm.com/support/docview.wss?uid=swg21663938] for more details on upgrade versions.\n\nSelect the appropriate WebSphere application server fix based on the version being used for IBM Emptoris product version. The following table lists the IBM Emptoris application versions along with the corresponding required version of IBM WebSphere Application Server and a link to the corresponding fix version where further installation instructions are provided.\n\nEmptoris Product Version WebSphere Version Interim Fix 9.5.x.x 8.0.0.x PI27100: SHIP JAVA 6/26 SR8 FP2 FOR WSAS V8.0.0.X [https://www-304.ibm.com/support/docview.wss?uid=swg24038812] 10.0.0.x, 10.0.1.x 8.5.0.x PI27099: SHIP JAVA 6/26 SR8 FP2 FOR WSAS V8.5.0.X AND V8.5.5.X [https://www-304.ibm.com/support/docview.wss?uid=swg24038811] 10.0.2.x 8.5.5.x PI27099: SHIP JAVA 6/26 SR8 FP2 FOR WSAS V8.5.0.X AND V8.5.5.X [https://www-304.ibm.com/support/docview.wss?uid=swg24038811] 6.5, 6.5.1 8.0.0.x PI20798: SHIP JAVA 6/26 SR8 FP1 FOR WSAS V8.0.0.X [http://www-01.ibm.com/support/docview.wss?uid=swg24038093] 6.5.1.1 8.5.0.x JRE 6\nPI27099: SHIP JAVA 6/26 SR8 FP2 FOR WSAS V8.5.0.X AND V8.5.5.X [https://www-304.ibm.com/support/docview.wss?uid=swg24038811]\n\nJRE 7\nPI27097: SHIP JAVA 7.1 SR2 FOR WSAS V8.4.4.2 and higher [https://www-304.ibm.com/support/docview.wss?uid=swg24038809]\nOR\nPI27098: SHIP JAVA 7 SR8 FOR WSAS V8.5.0.X AND V8.5.5.X [https://www-304.ibm.com/support/docview.wss?uid=swg24038810] 6.5.1.2, 7.0.0.x, 7.0.1.x 8.5.5.x JRE 6\nPI27099: SHIP JAVA 6/26 SR8 FP2 FOR WSAS V8.5.0.X AND V8.5.5.X [https://www-304.ibm.com/support/docview.wss?uid=swg24038811]\n\nJRE 7\nPI27097: SHIP JAVA 7.1 SR2 FOR WSAS V8.4.4.2 and higher [https://www-304.ibm.com/support/docview.wss?uid=swg24038809]\nOR\n[https://www-304.ibm.com/support/docview.wss?uid=swg24038810]PI27098: SHIP JAVA 7 SR8 FOR WSAS V8.5.0.X AND V8.5.5.X [https://www-304.ibm.com/support/docview.wss?uid=swg24038810] WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q092", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q092", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\nSecurity Bulletin: Multiple vulnerabilities in current releases of the IBM\u00ae SDK, Java\u2122 Technology Edition [http://www-01.ibm.com/support/docview.wss?uid=swg21688283]", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q092", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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 23rd, January 2015 - Original version published\nThe 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\nCross reference information Segment Product Component Platform Version Edition Commerce Emptoris Contract Management Commerce Emptoris Program Management Commerce Emptoris Services Procurement Commerce Emptoris Sourcing Commerce Emptoris Spend Analysis Commerce Emptoris Supplier Lifecycle Management\n\nA FIX IS AVAILABLE\nRational Insight Fix Pack 7 (1.1.1.7) for 1.1.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24039168]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q092", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The Jazz Reporting Service (JRS) gives an error if Oracle 12c is\n used as the database, and fails to connect with the following\n error message:\n\n \"Data source connection test failed: CRRGW5548E An\n com.ibm.team.integration.reporting.db.exception.DbAccessExceptio\n n error occurred when validating the database connection, caused\n by !CRRGW6011E Database version detected is \"Oracle Database 12c\n Enterprise Edition Release 12.1.0.2.0 - 64bit Production With\n the Partitioning, OLAP, Advanced Analytics and Real Application\n Testing options\" but Oracle 10.2.0.0 or 11.2.0.2 or later is\n required\"\n\n The workaround is to ignore the version check by adding\n com.ibm.team.datawarehouse.db.override.versioncheck=true to the\n app.properties file to ignore the version check.\n\n Refer to the following defect work item for details:\n\n https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.Wo [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.Wo]\n rkItem/339475", "logical_doc_id": 5, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q092", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nUsers using version prior to 6.0 *\n\nPROBLEM DESCRIPTION: *\nVersion check fails for Oracle 12c data warehouse *\n\nRECOMMENDATION: *", "logical_doc_id": 5, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q092", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Solution:\n The Oracle driver code in JRS was only supporting versions 10g\n and 11g of the database. Support for a 12c database was added.\n In addition, the JRS driver now allows versions 11.2+ and 12.1+\n of the Oracle JDBC driver.\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q092", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI42042\nREPORTED COMPONENT NAME\n JAZZ REPT SERVI\nREPORTED COMPONENT ID\n RATLJRS00\nREPORTED RELEASE\n 600\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2015-05-29\nCLOSED DATE\n 2015-06-26\nLAST MODIFIED DATE\n 2015-06-26\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n PI41944\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q092", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n JAZZ REPT SERVI\nFIXED COMPONENT ID\n RATLJRS00", "logical_doc_id": 5, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q092", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R600 PSY\n UP", "logical_doc_id": 5, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q147", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What are the steps needed or recommendations available, in order to upgrade an ISM agent from v7.3 to v7.4, while SDA is already configured ?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q147", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "not enough details in docs", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q147", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "A) use/check configuration of the SDA (Self-Describing Agents) mechanism on the TEMS/TEPS, so the ISM new application support is deployed automatically on TEMS, TEPS.\nYou can refer to :\n\nISM agent and SDA\nhttp://www-01.ibm.com/support/knowledgecenter/SS5MD2_7.4.0.1/com.ibm.itcamt.doc/common/sda.html?cp=SS5MD2_7.4.0.1%2F6-1-4-0&lang=en [http://www-01.ibm.com/support/knowledgecenter/SS5MD2_7.4.0.1/com.ibm.itcamt.doc/common/sda.html?cp=SS5MD2_7.4.0.1%2F6-1-4-0&lang=en]\n\nITM 6.3 self-describing monitoring agents\nhttp://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/adminuse/agentadmin_sda_intro.htm?lang=en [http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/adminuse/agentadmin_sda_intro.htm?lang=en]\n\nB) if you are planning to install new fresh ISM 7.4 agent as well as upgrading old ISM 7.3 agent, install new ISM 7.4 fresh agent first.\n\nYou can refer to :\n\nISM 7.4 agent installation\nhttp://www-01.ibm.com/support/knowledgecenter/SS5MD2_7.4.0.1/com.ibm.itcamt.doc/ism/dita/ag/topic/ISM_install_chapter.html?lang=en [http://www-01.ibm.com/support/knowledgecenter/SS5MD2_7.4.0.1/com.ibm.itcamt.doc/ism/dita/ag/topic/ISM_install_chapter.html?lang=en]\n\nC) upgrade your existing ISM 7.3 agent to v7.4\nyou can refer to :\n\nISM agent upgrade\nhttp://www-01.ibm.com/support/knowledgecenter/SS5MD2_7.4.0.1/com.ibm.itcamt.doc/ism/dita/ag/task/ISM_in_upgrade.html?lang=en [http://www-01.ibm.com/support/knowledgecenter/SS5MD2_7.4.0.1/com.ibm.itcamt.doc/ism/dita/ag/task/ISM_in_upgrade.html?lang=en]\n\nRemarks :\nif you are planning to use recent OS version for your new ISM agent, like for example Windows 2012 R2, you need to install and use ISM 7.4.0.1 (not ISM 7.4.0.0);\n\nsee prerequisites web site report for ISM :\nhttp://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1364203661236&duComponent=Miscellaneous_3F551130952E11E290021D5C0925FE1B [http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1364203661236&duComponent=Miscellaneous_3F551130952E11E290021D5C0925FE1B]\nDon't forget to install ISM 7401 application support on all your TEP client systems as well. Application support is not automatically applied to the Tivoli Enterprise Portal clients.\nyou can refer to :\n\nhttp://www-01.ibm.com/support/knowledgecenter/SS5MD2_7.4.0.1/com.ibm.itcamt.doc/ism/dita/ag/topic/ISM_install_elements.html?lang=en [http://www-01.ibm.com/support/knowledgecenter/SS5MD2_7.4.0.1/com.ibm.itcamt.doc/ism/dita/ag/topic/ISM_install_elements.html?lang=en]\nAn Application support event - new indicator is displayed on these clients to tell the user that they need to recycle their client to apply new or modified application support.\nIf you are using the Tivoli Enterprise Portal desktop client, you must use the monitoring agent's installation images to install the Tivoli Enterprise Portal application support on each of the desktop clients.\nIf you are using the Tivoli Enterprise Portal browser client or Java\u2122 WebStart client and you have the required user permissions to view the updated application, after the indicator is displayed, you can choose to close and restart these clients to see the new updates.\nClear the java cache on your TEP client systems before accessing the TEP GUI after your upgrade is complete.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q147", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "(possibly useful technote for this :\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21631843 [http://www-01.ibm.com/support/docview.wss?uid=swg21631843]\nGenerally speaking after the ISM application support has been deployed on all TEMS (hub and remote) and TEPS, it's safer to restart all these components (TEMS/TEPS), but not mandatory with SDA.\nSDA function is only supported on ITM IBM Tivoli Monitoring V6.2.3 and later. So make sure that your ITM (TEMS/TEPS) environment is already at right level, or upgrade it.\nISM 74 prereqs ITM 6.23. fp3 at minimum, or ITM 6.30 fp1, see the 'prerequisites' tab of this web page :\nhttp://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1364203661236&duComponent=Miscellaneous_3F551130952E11E290021D5C0925FE1B [http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1364203661236&duComponent=Miscellaneous_3F551130952E11E290021D5C0925FE1B]\nIf you have a ISM agent 7.3 co-resident on TEMS or TEPS system, and upgrade it to ISM v7.4, the installation process will attempt to stop automatically the co-resident ITM components like TEMS or TEPS, prior to running the upgrade; so you should be aware of that stop that is needed; so you can plan such upgrade at a time that is convenient for you, in order not to impact your environment and administrators or the monitoring solution currently in use.\nWe did identify however a possible issue AFTER the ISM 7.3 to 7.4 upgrade was done, if DNS monitor was in use :\n\nwhen redeploying the existing DNS profile to the new ISM agent, specifically one of the profiles was causing instant \"out of sync\" errors. For some reason it was identified that the DNS host field was using actual hostname values, and not IPs.\n\nThis clearly was allowed in the older ISM versions (pre 7.3.0.1), however ISM 7.4's data validation would only allow IPs in that field. Once change of those host values to the IP addresses was done, this resolved the issue with the profile and allowed it to be deployed against the systems without causing them to go out of sync.\n\nThe check for the DNS server being an IP address was not in some early ISM v7.3 code, so if using ISM version pre v7.3.0.1, the DNS server could set as a hostname.\n\nPRODUCT ALIAS/SYNONYM\n itcam itcam4tx itcam4trans itcamfortrans itcamfortx internet services monitoring", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q147", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The execution fails with the following errors :\n\ncom.sun.deploy.net.FailedDownloadException: Unable to load resource:\n\n http://host.xxx.dev.yyy:15200/commons-discovery-0.2.jar.jnlp\n\nat com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)\nat com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source)\nat com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source)\n..\n..\n..\nWrapped Exception\n\njava.net.ConnectException: Connection refused: connect\nat java.net.PlainSocketImpl.socketConnect(Native Method)\nat java.net.PlainSocketImpl.doConnect(Unknown Source)\nat java.net.PlainSocketImpl.connectToAddress(Unknown Source)\nat java.net.PlainSocketImpl.connect(Unknown Source)", "logical_doc_id": 2, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q147", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Possible explanations for this failure are :\n\n1) IHS not running on TEPS system\n2) Firewall preventing communication with port 15200\n3) Corrupted or invalid local files on workstation machine where TEP client is launched\n\nNothing explicitly related with Windows 7, unless specific firewall rules have been applied with the new\noperating system", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q147", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "1) Check if port 15200 is in LISTENING on the TEPS server.If not, likely the IHS is not running and you need to investigate about failures on TEPS side, considering that IHS should be started and stopped automatically with TEPS service.\n\n2) If port 15200 is available and in LISTENING on TEPS, verify if any firewall (locally to the workstation that is trying to launch TEP or the network boundary firewall) is preventing communication with that specific port. You may need to change firewall rules to allow access on port 15200.\n\nIf the first two options are fine, communication works normally so it is possible that the problem is with the application or JNLP file locally stored on the Windows workstation.\n\n3) On the workstation where TEP client runs, from Windows Control Panel, open the Java Control Panel and clear the Java cache.Then download TEP application again using the following URL from a web browser:\n\nhttp://TEPS_host_name:1920///cnp/kdh/lib/tep.jnlp\n\nIn this way you will get rid of any inconsistency of the TEP client application previously downloaded.\n\nPRODUCT ALIAS/SYNONYM\n IBM Tivoli Monitoring V6.2.3 Tivoli Enterprise Portal Client\n\nA FIX IS AVAILABLE\nIBM Tivoli Monitoring 6.3.0 Fix Pack 5 (6.3.0-TIV-ITM-FP0005) [http://www-01.ibm.com/support/docview.wss?uid=swg24039236]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q147", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Tivoli portal client changes need to be made to recognize Java\n 8 is installed can be set as the default java used.", "logical_doc_id": 3, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q147", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Add support for the Tivoli Portal client to run with Java\n version 8.", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q147", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Added necessary code to the Tivoli Portal clients startup files\n including java script to support Java version 8.\n\nKnown Issues:\n Problem Summary 1:\n Using Java 8 64-bit with Internet Explorer version 11 fails with\n the message:\n\nThis content cannot be displayed in a frame\n To help protect the security of information you enter into this\n website, the publisher of this content does not allow it to be\n displayed in a frame.\n What you can try:\n Open this content in a new windows\n\nWorkaround:\n Internet Explorer verison 11 does not support running 64-bit\n plugins. Use Java 8 32-bit with Internet Explorer version 11\n or use the WebStart client.\n\nProblem Summary 2:\n Java 8 fails with Firefox; the client does not fully initialize\n giving a blank screen.\n\nWorkaround:\n Use Internet Explorer or the WebStart client.\n This defect will be fixed in Oracle Java 8 u60, targeted for\n August 2015.\n\nNote: Recent Java updates have caused connection problems when\n logging into the portal server via the Tivoli Enterprise Portal", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q147", "section_id": 1, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV67716\nREPORTED COMPONENT NAME\n TEP\nREPORTED COMPONENT ID\n 5724C04EP\nREPORTED RELEASE\n 630\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-12-10\nCLOSED DATE\n 2015-02-09\nLAST MODIFIED DATE\n 2015-06-29\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q147", "section_id": 2, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n TEP\nFIXED COMPONENT ID\n 5724C04EP", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q147", "section_id": 3, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R630 PSY\n UP\n\nJava Security U51 DOWNLOADABLE FILES", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q147", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "4.2.0-TIV-KIP-FP0009 This is a cumulative fix pack for Tivoli OMEGAMON XE for IMS on z/OS V420", "logical_doc_id": 5, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q147", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Tivoli OMEGAMON XE for IMS on z/OS V420 fix pack 9 consists of the following files:\n\nFix pack file name Description 4.2.0-TIV-KIP-FP0009.README Contains the README for Tivoli OMEGAMON XE for IMS on z/OS V420 Fixpack 9. 4.2.0-TIV-KIP-FP0009.tar.gz Contains the Fix Pack 9 updates to Tivoli OMEGAMON XE for IMS on z/OS V420 application support for TEMS, TEPS, or TEP deployed on the AIX, Linux, HP-UX, and Solaris platforms. 4.2.0-TIV-KIP-FP0009.zip Contains the Fix Pack 9 updates to Tivoli OMEGAMON XE for IMS on z/OS V420 application support for TEMS, TEPS, or TEP deployed on Windows platforms. PREREQUISITES\nThis fixpack requires IBM Tivoli Monitoring Version 6.2.1 (at a minimum level) which was a prerequisite for OMEGAMON XE for IMS V420.\n\nIf 4.2.0-TIV-KIP-FP0008 was not installed, ensure z/OS PTF UA68726 has also been installed with this Fix Pack. The need for the updated language pack 4.2.0-TIV-KIP-LP0002 with FP0008 should also be verified.\n\nINSTALLATION INSTRUCTIONS\nPlease consult the readme file 4.2.0-TIV-KIP-FP0009_readme.txt (download below via Fix Central) for detailed installation instructions.", "logical_doc_id": 5, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q147", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "[http://publib.boulder.ibm.com/infocenter/tivihelp/v42r1/index.jsp?topic=%2Fcom.ibm.itm.doc_6.2.2fp1%2Flangpack.htm] [http://www-01.ibm.com/support/docview.wss?uid=swg21290883]Refer to the \"Recommended Maintenance\" Technote #1290883 to locate the full list of IBM Tivoli OMEGAMON product maintenance deliverables which contain the renewed Java certificate: http://www-01.ibm.com/support/docview.wss?uid=swg21290883 [http://www-01.ibm.com/support/docview.wss?uid=swg21290883]\n\nDOWNLOAD PACKAGE\n4.2.0-TIV-KIP-FP0009.README\n4.2.0-TIV-KIP-FP0009.zip\n4.2.0-TIV-KIP-FP0009.tar.gz\n\nHOW CRITICAL IS THIS FIX?\nRecommended\n\nPROBLEMS SOLVED\nSupports security update U51 in Java V7\n\nKNOWN SIDE EFFECTS\nNone Known\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is Fix Central(FC)? [http://www.ibm.com/systems/support/fixes/en/fixcentral/help/faq_sw.html]\nWhat is DD? [http://www6.software.ibm.com/dldirector/doc/DDfaq_en.html] 4.2.0-TIV-KIP-FP0009 on Fix Central 6 Jun 2014 English 11905443 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+OMEGAMON+XE+for+IMS+on+zOS&release=4.2.0&platform=All&function=all] [ ] DD\nPRODUCT ALIAS/SYNONYM\n I5420 I5 XE\n\n [/support/docview.wss?uid=swg24037685&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24037685&aid=2]Problems (APARS) fixed\nOA45300\n\n SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 6, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q147", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Environment:\n Occurs only when using the browser to access TEPS.\n\nProblem Description:\n Each time you logon to TEPS jar file is downloaded though you\n have\n caching enabled.\n\nThis is not an issue with 6.2", "logical_doc_id": 7, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q147", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "An additional 6m of byte code was being dowmloaded to the tep\n client even though all of the necessary jar files were already\n in the local java plugin cache.", "logical_doc_id": 7, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q147", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The fix for this APAR is included in the following maintenance\n vehicle:\n\n| interim fix | 6.1.0.7-TIV-ITM-IF0001\n\nNote: Search the IBM technical support web site for maintenance\n package availability.\n\nTEMPORARY FIX", "logical_doc_id": 7, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q147", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IZ17689\nREPORTED COMPONENT NAME\n TEP\nREPORTED COMPONENT ID\n 5724C04EP\nREPORTED RELEASE\n 610\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2008-03-13\nCLOSED DATE\n 2008-06-27\nLAST MODIFIED DATE\n 2008-06-27\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 7, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q147", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n TEP\nFIXED COMPONENT ID\n 5724C04EP", "logical_doc_id": 7, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q147", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R610 PSY\n UP", "logical_doc_id": 7, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q143", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Downloading and installing the Tomcat Apache server in preparation for ITCAM monitoring.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q143", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "So you want to download, install and monitor the Apache Tomcat server on your Windows system but don't quite know where to start?\n\nWell, start here...\n\nA. How to download the Apache Tomcat Server:\nv5.5 is here: https://archive.apache.org/dist/tomcat/tomcat-5/v5.5.26/bin/ [https://archive.apache.org/dist/tomcat/tomcat-5/v5.5.26/bin/]\nv6.0, v7.0, v8.0 is here: http://tomcat.apache.org/whichversion.html [http://tomcat.apache.org/whichversion.html]-\nclick on the version on the left and download the zip file to your C:\\temp directory\n(Note: We don't support the actual Apache Tomcat server itself. For help with that, consult one of the many online forums.)\n\nB. How to install the Apache Tomcat Server:\nInstalling is super easy, there's no GUI to run, there's no silent install, nothing.. Simply extract the zip file to your C:\\Program Files(x86)\\ dir. (Or any dir you want.) See my example here.. extracted to C:\\Program Files(x86) directory. You will find a sub-directory under this directory called apache-tomcat-5.5.26 (or whatever version you install.)\n\n[/support/docview.wss?uid=swg21682163&aid=1] [/support/docview.wss?uid=swg21682163&aid=1]\n\nC. How to stop / start up the Apache Tomcat Server:\nIn this example, am using Apache Tomcat v7.0.55.\nSet the JRE_HOME and check your java version. Then run the startup.bat script which will start the Tomcat Server.\n[/support/docview.wss?uid=swg21682163&aid=2] [/support/docview.wss?uid=swg21682163&aid=2]\n(To stop the Apache Tomcat Server, simply run the shutdown.bat script from the same bin dir.)\n\nD. How to login to the Apache Tomcat server admin console:\nBring up your browser, and simply point to your server on port 8080 (default) like this:\nhttp://:8080\n\nE. How to monitor Apache Tomcat server:\ndownload and install the latest version of ITCAM for J2EE v7.1.1.x\nconfigured the ITCAM agent and DC\nrestart your Server, login to your TEPS and observe data\n\nPRODUCT ALIAS/SYNONYM\n ITCAM for J2EE\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q143", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "DC/TEMA: ITCAM for J2EE v6.1.0.4\n OS Information: Win XP\n App Server: Weblogic Portal 10\n\n Steps to reproduce :\n Step 1: instal & configure FP4 DC, TEMA\n Step 2: start the server and TEMA\n check the BEA Weblogic App Server-portalServer workspace,\n the Process CPU utilizationis null in Application Servers\n Summary table.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q143", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Customers using ITCAM for J2EE v6.1.0.4\n WebLogic DC/TEMA\n\n ERROR DESCRIPTION:\n DC/TEMA: ITCAM for J2EE v6.1.0.4\n OS Information: Win XP\n App Server: Weblogic Portal 10\n\n Steps to reproduce :\n Step 1: instal & configure FP4 DC, TEMA\n Step 2: start the server and TEMA\n check the BEA Weblogic App Server-portalServer workspace,\n the Process CPU utilizationis null in Application Servers\n Summary table.\n\nRECOMMENDATION: apply ITCAM for J2EE V6.2, TEMA Fix Pack 5\n when\navailable\n\n When using ITCAM for J2EE v6.1.0.4 WebLogic DC/TEMA to monitor a\n Weblogic Portal 10 server, in the BEA Weblogic App\n Server-portalServer workspace, the Process CPU utilization is\n null in Application Servers Summary table.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q143", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The fix for this APAR is contained in the following maintenance\n packages:\n | fix pack | 6.2.0-TIV-ITCAM_J2EE_TEMA-FP005\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q143", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM17754\nREPORTED COMPONENT NAME\n ITCAM WAS DIS T\nREPORTED COMPONENT ID\n 5724L62TM\nREPORTED RELEASE\n 610\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2010-07-01\nCLOSED DATE\n 2010-07-15\nLAST MODIFIED DATE\n 2010-07-15\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q143", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n ITCAM WAS DIS T\nFIXED COMPONENT ID\n 5724L62TM", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q143", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R610 PSY\n UP\nR620 PSY\n UP\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q143", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "DC/TEMA: ITCAM for J2EE v6.1.0.4\n OS Information: Win XP\n App Server: Weblogic Portal 10\n\n Steps to reproduce :\n Step 1: instal & configure FP4 DC, TEMA\n Step 2: start the server and TEMA\n Step 3: check the BEA WebLogic App Server - portalServer work\n space. In the Application Server Summary table, the CPU Usage is\n more than 100%", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q143", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Customers using ITCAM for J2EE v6.1.0.4\n Weblogic DC/TEMA\n\n ERROR DESCRIPTION:\n DC/TEMA: ITCAM for J2EE v6.1.0.4\n OS Information: Win XP\n App Server: Weblogic Portal 10\n\n Steps to reproduce :\n Step 1: instal & configure FP4 DC, TEMA\n Step 2: start the server and TEMA\n Step 3: check the BEA WebLogic App Server - portalServer work\n space. In the Application Server Summary table, the CPU Usage is\n more than 100%\n\nRECOMMENDATION: apply ITCAM for J2EE V6.2, TEMA Fix Pack 5\n when\navailable\n\n When using ITCAM for J2EE v6.1.0.4 DC/TEMA to monitor a Weblogic\n Portal 10 server, in the Application Server Summary table, the\n CPU Usage is more than 100%.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q143", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The fix for this APAR is contained in the following maintenance\n packages:\n | fix pack | 6.2.0-TIV-ITCAM_J2EE_TEMA-FP005\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q143", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM17799\nREPORTED COMPONENT NAME\n ITCAM WAS DIS T\nREPORTED COMPONENT ID\n 5724L62TM\nREPORTED RELEASE\n 610\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2010-07-04\nCLOSED DATE\n 2010-07-15\nLAST MODIFIED DATE\n 2010-07-15\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q143", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n ITCAM WAS DIS T\nFIXED COMPONENT ID\n 5724L62TM", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q143", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R610 PSY\n UP\nR620 PSY\n UP", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q143", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "You need to set permissions for the Data Collector installation directory.", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q143", "section_id": 1, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "The following messages might be present in the configuration log file:\n\nUser that runs NetWeaver application server can not access the ITCAM DC home directory, or the user is not the member of the user group of ITCAM DC.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q143", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The admin users for every SAP NetWeaver instance must belong to the same group (for example, sapsys).\n\nWhen installing the Data Collector, run the installation program as a user belonging to the same group. Alternatively, change the group of the Data Collector installation tree (DC_home) to this group, for example:\n\nchgrp -R sapsys /opt/IBM/itcam/J2EE/DC\n\nFor all files and directories in the tree, the group must have at least the same permissions as the owner. To achieve this in the simplest way, grant the group read, write, and execute permissions for all files in the tree, for example:\n\nchown -R g+rwx /opt/IBM/itcam/J2EE/DC\n\nAlso, make sure that the group has read and write permissions for the Tivoli logging directory (by default, /var/ibm/tivoli/common),\n\nTo configure each SAP NetWeaver instance that you need to monitor, run the Data Collector configuration tool using the admin user for the instance.\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli Composite Application Manager for J2EE ITCAM J2EE NETWEAVER Solaris, AIX, HP-UX, Linux 6.1", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q143", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do I collect the J2EE DC and TEMA logs?", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q143", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "1. Please Collect \"yj\" and/or \"ht\" version from TEMS, TEPS, TEMA, and send the output.\n\nCommand on Windows : \\bin\\kincinfo -i\non UNIX/Linux : /bin/cinfo -i\n2. Collect MS, DC, TEMA data using following instruction and send the ouptut.\n** Collecting J2EE 7.1.1 Data\nNote : Since the J2EE agent is composed by two parts, Data Collector and TEMA, you can separately collect data from them by invoking the two following scripts as \" root\":\n\n=====> Data Collector (DC) Location Windows: \\TMAITM6\\j2eedc\\7.1.1.0.0\\itcamdc\\bin\\cyn_collector.cmd\nUnix : //yj/j2eedc/7.1.1.0.0/itcamdc/bin/cyn_collector.sh\nexample:\nWindows platform :\nC:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\itcamdc\\bin\\cyn_collector.cmd\nLinux 64 bit platform :\nopt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/itcamdc/bin/cyn_collector.sh Usage/\nOutput Windows : %TEMP%\\CYN\\*.zip\nUnix : /tmp/CYN/-CYNenv.jar\n=====> TEMA Location Windows : \\TMAITM6\\kyjcollect.cmd\nUnix : //yj/bin/kyjcollect.sh\nexample:\nWindows platform : C:\\IBM\\ITM\\TMAITM6\\kyjcollect.cmd\nLinux 64 bit platform : opt/IBM/ITM/lx8266/yj/bin/kyjcollect.sh Usage/\nOutput Windows : %TEMP%\\kyj\\*.jar\nUnix : $HOME/tmp/kyj/kyjcollect-$HOSTNAME.tar.gz\nexample:\nLinux : /root/tmp/kyj/kyjcollect-.tar.gz\nAIX, Solaris, HPUX : /tmp/kyj/kyjcollect-.tar.gz\n** Collecting J2EE 6.1 FP4 or higher version using script\n=============> Managing Server (MS) Location on Window/Unix/Linux : /bin/MS_Gather_Data.sh\n\nNote: On Windows, the user must run the script in a Korn Shell environment. Usage/\nOutput on Windows/Unix/Linux :\n/bin/MS_Gather_Data.sh [pmr][was_home][appServer]\n\nNote: [was_home] = directory where the MS Visualization Engine is installed\n=============> Data Collector (DC) Location on Windows : \\itcamdc\\bin\\cyn_collector_j2.cmd\non Unix/Linux : /itcamdc/bin/cyn_collector_J2.sh Output on Windows : \\collect.jar\non Unix/Linux : /collect.tar.gz =============> TEMA Location on Windows : \\TMAITM6\\kyjcollect.cmd\non Unix/Linux : //yj/bin/kyjcollect.sh\nwhere = location that indicates the platforms\n(ex: sol283 for Solaris, aix513 for AIX, and hp11 for HP-UX).\nUsage on Windows : \\TMAITM6\\kyjcollect.cmd\non Unix/Linux : //yj/bin/kyjcollect.sh Output on Windows : %TEMP%\\kyj\\*.jar\non Unix/Linux : $HOME/tmp/kyj/kyjcollect-.tar.gz\n\nBack to top\n** MANUAL J2EE 6.1 Data Collection ***\nManaging Server (MS) Data - manual\nWindow and Unix Location /logs/am_stderr.log\n/logs/am_stdout.log\n/msg-.log\n/trace-.log\n/audit-ms.log\n\nData Collector (DC) Data - manual\nWindows and Unix\n\nFor the version lower than ITCAM for J2EE 6.1 FixPack 4 Here are the logs required for each application server. The logs are from the following directory: /nodename.instancename\n\nApplication Server Logs to Collect WebLogic, WASCE, J2SE msg-dc.log, trace-dc.log, msg-dc-native.log, trace-dc-native.log NetWeaver msg-dc-sap.log, trace-dc-sap.log, msg-dc-native.log, trace-dc-native.log Tomcat msg-dc-Standard.log, trace-dc-Standard.log, msg-dc-native.log, trace-dc-native.log Oracle msg-dc.log, trace-dc.log, trace-dc-bcm.log, msg-dc-native.log, trace-dc-native.log JBoss msg-dc-Unified.log, trace-dc-Unified.log, trace-dc-bcm.log, msg-dc-native.log, trace-dc-native.log", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q143", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "For the version ITCAM for J2EE 6.1 FixPack 4 or higher Here are the logs required for each application server. The logs are from the following directory: /nodename.instancename\n\nApplication Server Logs to Collect WebLogic msg-dc-ParentLast.log, trace-dc-ParentLast.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log WASCE, J2SE msg-dc.log, trace-dc.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log NetWeaver msg-dc-sap.log, trace-dc-sap.log, msg-dc-native.log, trace-dc-native.log ,msg-dc-bcm.log, trace-dc-bcm.log Tomcat msg-dc-tomcat.log, trace-dc-tomcat.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log Oracle msg-dc.log, trace-dc.log, trace-dc-bcm.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log JBoss msg-dc-jboss.log, trace-dc-jboss.log, msg-dc-native.log, trace-dc-native.log, msg-dc-bcm.log, trace-dc-bcm.log\n\nAgent (TEMA) Data - manual\nWindows Location /logs/kyj-tema-trace.log,\n/logs/kyj-tema-msg.log,\n/logs/KYJ.Primary.*.*JVM.log\nUnix Location //logs/kyj-tema-trace.log,\n//logs/kyj-tema-msg.log,\n/logs/KYJ.Primary.*.*JVM.log\n\nBack to top\n******J2EE Installation Error Logs (for all version) *******\nManaging Server (MS) Data - install error log\n\nManaging Server Installation Error Logs (for all version)\nComponents Logs to Collect Managing Server specific logs * Windows : C:\\Program Files\\ibm\\tivoli\\common\\CYN\\logs\nUnix : /var/ibm/tivoli/common/CYN/logs Embedded DB2 logs * Windows : \\DB2LOG\nUnix : /tmp/db2setup.* Embedded WebSphere Application Server ** Windows and Unix :\n/temp\n/logs Embedded WebSphere Application Server Refresh Pack ** Windows and Unix :\n/logs/update\n\nData Collector (DC) Data - install error log\nWindow and Unix Location /trace-install.log\n/launchContainer/\n/platformUtils/\nIf you use NetWeaver, /config.log\nBack to top\n\nPRODUCT ALIAS/SYNONYM\n ITCAM for J2EE", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q285", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "DIRECT LINKS TO FIXES\nbpm.8570.cf2016.12.delta.repository [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8570.cf2016.12.delta.repository&source=SAR]\nDownloading IBM Business Process Manager V8.5.7 Cumulative Fix 2016.12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043062]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q285", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Process instances or tasks are not retrieved when you search by\n using Microsoft SQL Server as the IBM Business Process Manager\n (BPM) database and a JavaScript object of type TWSearch that\n specifies the date value or date values as a search parameter,\n even though the value or values match existing process instances\n or tasks.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q285", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "If you store time values in process variables that are marked as\n visible in IBM Process Portal, the time values include\n fractions of a second, you use Microsoft SQL Server as the IBM\n BPM database, and you run a search specifying an exact match\n filter with a time value that includes fractions of a second, an\n empty result might be returned.\n\nOn Microsoft SQL Server, IBM BPM stores searchable variables of\n type \"time\" in columns of type DATETIME. During insertion, the\n value is rounded to increments of .000, .003, or .007 seconds.\n If the search value has fractions of a second that do not\n exactly match the rounded value, the comparison fails. As a\n result, corresponding process instances or tasks cannot be\n retrieved.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q285", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A fix will be available in IBM BPM V8.5.7 cumulative fix 2016.12\n that casts the search value to DATETIME before the comparison\n is done.\n\nTo determine whether the cumulative fix is available, complete\n the following steps on Fix Central\n (http://www.ibm.com/support/fixcentral):\n\n1. On the Select product tab, select WebSphere as the product\n group, IBM Business Process Manager with your edition from the\n WebSphere options, All as the installed version, and All as the\n platform, and then click Continue.\n 2. In the Text field, enter \"cumulative fix\", and click\n Continue.\n\nIf cumulative fix 2016.12 is available, download and install it.\n When you download fix packages, ensure that you also download\n the readme file for each fix. Review each readme file for\n additional installation instructions and information about the\n fix.\n\nPRODUCTS AFFECTED\n IBM BPM Advanced\n IBM BPM Standard\n IBM BPM Express\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q285", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR57068\nREPORTED COMPONENT NAME\n BPM STANDARD\nREPORTED COMPONENT ID\n 5725C9500\nREPORTED RELEASE\n 857\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-11-28\nCLOSED DATE\n 2016-12-09\nLAST MODIFIED DATE\n 2016-12-09\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q285", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM STANDARD\nFIXED COMPONENT ID\n 5725C9500", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q285", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R857 PSY\n UP\n\nPRODUCT README", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q285", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "The following new feature and fixes are included in IBM Business Process Manager (BPM) V8.5.7 cumulative fix 2016.12.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q285", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "TAB NAVIGATION\nFix list [http://www.ibm.com/support/docview.wss?uid=swg27049215]\nWhat's new [http://www.ibm.com/support/docview.wss?uid=swg27048992]- selected tab,\nDownloading the cumulative fix [http://www.ibm.com/support/docview.wss?uid=swg24043062]\nInstalling the cumulative fix [http://www.ibm.com/support/docview.wss?uid=swg27048950]\nUpgrading profiles from V8.5.x [http://www.ibm.com/support/docview.wss?uid=swg27048949]\nPost-upgrade tasks [http://www.ibm.com/support/docview.wss?uid=swg27049143]\n\nWith this update, you can\nOptimize your business operations by using the leading Business Process Management platform at a low-cost entry point. For more information, see IBM Business Process Manager on Cloud Express offers a new opportunity to start automating business operations [http://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/5/897/ENUS216-365/index.html&lang=en&request_locale=en].\nExperience a new responsive IBM BPM on Cloud login page.\nCreate much more when you use the web IBM Process Designer, including service flows and events.\nUse new REST APIs that replace and extend heritage BPD REST APIs.\nUse new self-service capabilities to delete snapshots of process applications or toolkits.\nCollaborate on tasks directly from the IBM Process Portal by using IBM Sametime and IBM Connections.\nSelect which search results to display and define display names.\nEnsure you have sufficient permissions before you run the command to upgrade the database.\nIntegrate Watson cognitive services into your IBM BPM solutions by using the latest REST integration enhancements.\nPerform log analysis in the cloud for your existing IBM BPM on-premise deployment. For more information, see the blog [https://developer.ibm.com/bpm/2016/11/perform-log-analysis-in-the-cloud-for-your-existing-ibm-bpm-on-premise-deployment].\nUse the IBM BPM default theme to style coaches created by using the Salient Process SPARK UI toolkit.\nMigrate deployment environments with custom password encryption more easily.\n\nIBM BPM V8.5.7 Cumulative Fix 2016.12 also offers new supported environments:\nIBM WebSphere Application Server Liberty 16.0.0.4 is now supported for IBM Process Federation Server.\nDojo 1.10.5 - When you upgrade to IBM BPMV8.5.7 Cumulative Fix 2016.12, your Dojo version is automatically upgraded to Dojo 1.10.5 if your coach or system toolkit is V8.5.7.\nSafari on Apple iOS 10 for iPad and iPhone (Process Portal and coaches)\nSafari 9.1 for Mac OS (Process Portal and coaches)\nMicrosoft Edge (now supported for web Process Designer)\nIBM DB2 11.1 Advanced Workgroup Server Edition (AWSE) is now available to be downloaded from Passport Advantage\u00ae for IBM BPM Standard and IBM BPM Advanced.\nIBM Security Directory Suite 8.0.1 is now available to be downloaded from Passport Advantage for IBM BPM Advanced, IBM BPM Standard, and IBM BPM Express.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q285", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "For more information about supported configurations, see the IBM BPM support site:\nIBM BPM Advanced [http://ibm.biz/BPMAdvSysReqs]\nIBM BPM Standard [http://ibm.biz/BPMStdSysReqs]\nIBM BPM Express [http://ibm.biz/BPMExpSysReqs]\n\nNotes:\nYou can also find out [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.7/com.ibm.wbpm.admin.doc/topics/cbpm_whatsnew-cf2016.06.html]what was new [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.7/com.ibm.wbpm.admin.doc/topics/cbpm_whatsnew-cf2016.09.html] in IBM Business Process Manager (BPM) V8.5.7 cumulative fix 2016.09 and what was new [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.7/com.ibm.wbpm.admin.doc/topics/cbpm_whatsnew-cf2016.06.html] in IBM Business Process Manager (BPM) V8.5.7 cumulative fix 2016.06.\nThe functions that are deprecations and removals in IBM BPM V8.5.7 cumulative fix 2016.12 are flagged in Deprecated and removed features of IBM Business Process Manager V8.5.7 [https://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.7/com.ibm.wbpm.main.doc/topics/gbpm_deprecationlist.html].\n\nFor more information, see What's new in IBM Business Process Manager V8.5.7 Cumulative Fix 2016.12 [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.7/com.ibm.wbpm.admin.doc/topics/cbpm_whatsnew-cf2016.12.html].\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Express Installation / Configuration Linux, Windows 8.5.7.CF201612, 8.5.7 Business Integration IBM Business Process Manager Standard Installation / Configuration AIX, Linux, Solaris, Windows 8.5.7.CF201612, 8.5.7 PRODUCT ALIAS/SYNONYM\n BPM\n\nDIRECT LINKS TO FIXES\nbpm.8570.cf2016.12.delta.repository [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8570.cf2016.12.delta.repository&source=SAR]\nDownloading IBM Business Process Manager V8.5.7 Cumulative Fix 2016.12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043062]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q285", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When you run the BPMExport command to export a .twx file, a copy\n of the .twx file remains in the \\TMP folder.\n\nPRODUCTS AFFECTED\n IBM Business Process Manager (BPM) Advanced\n IBM BPM Standard\n IBM BPM Express", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q285", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Stop the IBM Process Center server and delete the files from the\n \\TMP folder manually or by using a scheduled task.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q285", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "No additional information is available.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q285", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A fix will be included in IBM BPM V8.5.7 cumulative fix 2016.12\n that deletes the copy of the .twx file from the \\TMP folder\n after the BPMExport command finishes.\n\nTo determine whether the cumulative fix is available and\n download it if it is, complete the following steps on Fix\n Central:\n\n1. On the Select product tab, select WebSphere as the product\n group, IBM Business Process Manager with your edition from the\n WebSphere options, All as the installed version, and All as the\n platform, and then click Continue.\n 2. In the Text field, enter \"cumulative fix?, and click\n Continue.\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q285", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR56622\nREPORTED COMPONENT NAME\n BPM STANDARD\nREPORTED COMPONENT ID\n 5725C9500\nREPORTED RELEASE\n 856\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-09-18\nCLOSED DATE\n 2016-10-24\nLAST MODIFIED DATE\n 2016-10-24\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q285", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM STANDARD\nFIXED COMPONENT ID\n 5725C9500", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q285", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R857 PSY\n UP\n\nDIRECT LINKS TO FIXES\nbpm.8570.cf2016.12.delta.repository [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8570.cf2016.12.delta.repository&source=SAR]\nDownloading IBM Business Process Manager V8.5.7 Cumulative Fix 2016.12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043062]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q285", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "If you run a process with a user task that is defined to run as\n a multi-instance or simple loop, and this task has a timer\n boundary event with a trigger specified relative to the task's\n due date, the process fails with an exception similar to the\n following exception, which you see in the SystemOut.log file of\n the server:\n\n [8/30/16 15:17:11:482 BRT] 00000158 wle E\n CWLLG0326E: A deliverException has occurred.\n java.lang.NullPointerException\n at\n com.lombardisoftware.bpd.component.flowcomponent.event.worker.Ti\n merEventWorkerHelper.getSentTaskId(TimerEventWorkerHelper.java:4\n 33)\n at\n com.lombardisoftware.bpd.component.flowcomponent.event.worker.Ti\n merEventWorkerHelper.calculateRelativeToDueDate(TimerEventWorker\n Helper.java:410)\n at\n com.lombardisoftware.bpd.component.flowcomponent.event.worker.Ti\n merEventWorkerHelper.calculateTargetTime(TimerEventWorkerHelper.\n java:352)\n at\n com.lombardisoftware.bpd.component.flowcomponent.event.worker.Ti\n merEventWorkerHelper.processIntermediateAction(TimerEventWorkerH\n elper.java:130)\n at\n com.lombardisoftware.bpd.component.flowcomponent.event.worker.Ev\n entWorker.doWork(EventWorker.java:144)\n at\n com.lombardisoftware.bpd.runtime.engine.FlowObjectExecutionTreeN\n ode.doWork(FlowObjectExecutionTreeNode.java:373)\n at\n com.lombardisoftware.bpd.runtime.engine.FlowObjectExecutionTreeN\n ode.executeAttachedEvents(FlowObjectExecutionTreeNode.java:633)\n at\n com.lombardisoftware.bpd.runtime.engine.FlowObjectExecutionTreeN\n ode.doWork(FlowObjectExecutionTreeNode.java:380)\n at\n com.lombardisoftware.bpd.runtime.engine.BPDEngine.executeTreeNod\n e(BPDEngine.java:337)\n at\n com.lombardisoftware.bpd.runtime.engine.BPDEngine.resume(BPDEngi\n ne.java:180)\n ...", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q285", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Change the process model and define the timer boundary event in\n a different way. There are several options other than relative\n to due date, for example, you could define the timer boundary\n event relative to the start of the step or a custom date that is\n hardcoded or is from a process variable.", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q285", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "If a user task runs in a loop, each task instance has its own\n due date. A timer boundary event on an activity is a timer for\n the overall activity, not a timer for each instance of the loop.\n There is only one timer and that one timer cannot be calculated\n relative to multiple different due dates of several task\n instances. It is, therefore, not possible to run a process in\n such a combination.", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q285", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A fix will be included in IBM BPM V8.5.7 cumulative fix 2016.12\n that shows a validation error for processes that contain such a\n non-executable definition. If a user still models and runs this\n task, an improved failure message is provided.\n\nTo determine whether the IBM BPM V8.5.7 cumulative fix 2016.12\n is available and download it if it is, complete the following\n steps on Fix Central:\n\n1. On the Select product tab, select WebSphere as the product\n group, IBM Business Process Manager with your edition from the\n WebSphere options, All as the installed version, and All as the\n platform, and then click Continue.\n 2. In the Text field, enter \"cumulative fix\", and click\n Continue.\n\nPRODUCTS AFFECTED\n IBM Business Process Manager (BPM) Advanced\n IBM BPM Standard\n IBM BPM Express\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q285", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR56707\nREPORTED COMPONENT NAME\n BPM ADVANCED\nREPORTED COMPONENT ID\n 5725C9400\nREPORTED RELEASE\n 857\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-09-21\nCLOSED DATE\n 2016-12-07\nLAST MODIFIED DATE\n 2016-12-07\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q285", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM STANDARD\nFIXED COMPONENT ID\n 5725C9500", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q285", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R857 PSY\n UP\n\nDIRECT LINKS TO FIXES\nbpm.8570.cf2016.12.delta.repository [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8570.cf2016.12.delta.repository&source=SAR]\nDownloading IBM Business Process Manager V8.5.7 Cumulative Fix 2016.12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043062]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q285", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "In IBM Process Designer, the SQL Connector panel displays the\n following information:\n\nStandard JDBC Types: ARRAY, BIGINT, BINARY, BIT, BLOB, BOOLEAN,\n CHAR, CLOB, DATALINK, DATE, DECIMAL, DISTINCT, DOUBLE, FLOAT,\n INTEGER, AVA_OBJECT, LONGVARBINARY....\n\nHowever, even though all these types are technically available,\n IBM Business Process Manager (BPM) does not transform complex\n IBM BPM types (such as TWObjects) to standard JDBC types that\n the database can process. Therefore, the SQL Connector code can\n handle only simple types.\n\nThe limitation information is missing from the documentation.", "logical_doc_id": 5, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q285", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Use the Java integration feature to invoke custom Java code\n using JDBC java interfaces to call stored procedures.", "logical_doc_id": 5, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q285", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "No additional information is available.\n\nPRODUCTS AFFECTED\n IBM Business Process Manager (BPM) Advanced\n IBM BPM Standard\n IBM BPM Express", "logical_doc_id": 5, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q285", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Information about this limitation will be added to the\n SQLParameter variable types description in an upcoming IBM BPM\n V8.5.7 cumulative fix.\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q285", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR56769\nREPORTED COMPONENT NAME\n BPM STANDARD\nREPORTED COMPONENT ID\n 5725C9500\nREPORTED RELEASE\n 856\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-10-04\nCLOSED DATE\n 2016-10-19\nLAST MODIFIED DATE\n 2016-10-19\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q285", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM STANDARD\nFIXED COMPONENT ID\n 5725C9500", "logical_doc_id": 5, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q285", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R857 PSY\n UP", "logical_doc_id": 5, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q237", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "How you set up cross-certification for this depends on what you would be using it for. If you are setting this up strictly for user access, one-way cross-certification would work great. If you want to be able to replicate, it is more complicated.\n\nFor example, you have two domains, Domain A and Domain B, and the goal is to allow Domain A access to Domain B, but not allow Domain B access to Domain A.\n\nTo use this for user access:\nTo also replicate:\n*\n\n2. On your Domain A server create a cross certificate for your Domain A organization to your Domain B organization.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q237", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "3. On your Domain A server in the Server Document -> Security tab ->Access Server field, list your Domain A organization (for example, if your Domain A organization was /notes, the entry in this field would be */notes) . Also list the Domain B server's name (for example, if this is Server1/notes2, the entry in this field is Server1/notes2).\n\nStep 3 will allow server-to-server replication, but will not allow any users in Domain B to access the Domain A server.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q237", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "A simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21602845]", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q237", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The Change home page URL is formatted as follows:\n\nhttps://changeserver:port/webapps/change\n\n(replace changeserver and port with your Rational Change server and port)", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q237", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The web server underlying to Change is Jetty. This forces you to include the \"Jetty context\" (/webapps/change\") in the URL, and to explicitly include the protocol \"https\" when you have configured Change that way.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q237", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "The question dealt with by this Technote is literally \"how can I redirect the traffic from a port to another port in Jetty?\", or \"how can I redirect the traffic from https to http?\".\n\nThe answer relies entirely on a customization of Jetty and/or OS administration. This question is not directly about Change.\n\nIMPORTANT NOTE: All tips below are only meant as leads, they are not definitive answers. Also, they have not been tested. To achieve these goals you require knowledge of Jetty and OS administration.", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q237", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Therefore, the contents of this Technote are not supported. Rational support provides help only with defects in Change.\n\n1. Lead 1: UNIX ipchains\n* http://wiki.eclipse.org/Jetty/Howto/Port80\n\n2. Lead 2: Using Jetty's \"Connectors\"\n* jetty:// Configuring SSL [http://www.eclipse.org/jetty/documentation/current/configuring-ssl.html]\n*\n*\n*\n* http://changeserver:port/webapps/change/\nhttps://changeserver:port/webapps/change\nhttps://changeserver:port/webapps/change/\nThe port in this example is 443. It has a value under 1024. This can cause issues on the UNIX systems, as only root can use those. However you don't want to run Change as root!\n\n\n \n \n \n 30000\n 1\n false\n 443\n 1000\n 500\n \n \n \n\nThe section below describes the SSL connector:\n\n\n \n \n 443\n 30000\n[THE KEYSTORE SETTINGS MUST BE INSERTED HERE]\n\n \n \nAbout the keystore settings\n*\nALL\n*\n*\n\n \n Secured area\n /*\n \n \n \nCONFIDENTIAL\n\n \n \n*\nThis solution relies on the fact that Change knows its own https port (see the \"CONFIDENTIAL\" bit above) from its configuration files.", "logical_doc_id": 3, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q237", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "See also : Technote 1452679: \"Configuring Rational Change 5.2 to allow the omission of the context from the login URL\" [https://www.ibm.com/support/docview.wss?uid=swg21452679]", "logical_doc_id": 4, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q237", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Procedure\n\nRun the following commands to disable SSLv2 and SSLv3 in Data ONTAP operating in 7-Mode and clustered Data ONTAP, as recommended by these security advisories:\nCVE-2014-3566 SSL v3.0 Nondeterministic CBC Padding Vulnerability in Multiple IBM N Series Products.\nCVE-2016-0800 SSLv2 Vulnerability in Multiple IBM N Series Products\n\nNOTE: Disabling the SSLv2 and SSLv3 protocols in supported versions of IBM N Series products should not cause any adverse impact to their operation.\n\nFor Data ONTAP operating in 7-Mode, perform the following steps:\nTLS is disabled by default and must be enabled prior to disabling SSL to ensure uninterrupted secure communication.\n1. Enable TLS using the Data ONTAP command line interface:\ncontroller1> options tls.enable\ntls.enable off\n\ncontroller1> options tls.enable on\n\ncontroller1> options tls.enable\ntls.enable on\n\nNote: If the error Could not set option for https/ftps traffic. Try again is reported while enabling TLS, run the secureadmin setup -f ssl command and then attempt to enable TLS again.\n2. Disable only SSLv2 and v3 using the Data ONTAP command line interface:\ncontroller1> options ssl\nssl.enable on\nssl.v2.enable on\nssl.v3.enable on\n\ncontroller1> options ssl.v3.enable off\ncontroller1> options ssl.v2.enable off\n\ncontroller1> options ssl\nssl.enable on <<<< THIS MUST REMAIN ON FOR TLS TO WORK\nssl.v2.enable off\nssl.v3.enable off\n\nNote: Even though the httpd and ldap options mention SSL, they will use TLS when the SSLv2 and SSLv3 options are disabled. For clustered Data ONTAP, perform the following steps:\n1. Upgrade monitoring applications as needed to support TLS-based communication. For example, OnCommand Unified Manager must be version 6.2 or later.\n2. Display the current Web service options by running the following command:\n::>system services web show\nOutput similar to the following is displayed:\nExternal Web Services: true\nStatus: online\nHTTP Protocol Port: 80\nHTTPs Protocol Port: 443\nTLSv1 Enabled: true\nSSLv3 Enabled: true\nSSLv2 Enabled: false\n3. Disable SSLv3:\n::>system services web modify -external true -sslv3-enabled false\n4. If SSLv2 was enabled (it is disabled by default in all versions & not available in version 8.3) disable it:\n::>system services web modify -external true \u2013sslv2-enabled false\n5. Run the following command to confirm the settings:\n::>system services web show\nExternal Web Services: true\nStatus: online\nHTTP Protocol Port: 80\nHTTPs Protocol Port: 443\nTLSv1 Enabled: true\nSSLv3 Enabled: false\nSSLv2 Enabled: false\n\nNote: Only these versions of clustered Data ONTAP 8.2.3 and 8.2.4 have the ability to disable SSLv2 with LDAP.", "logical_doc_id": 5, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q237", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Domino Administrator client still connects to servers although the option \"Refresh Server Bookmarks\" is disabled", "logical_doc_id": 6, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q237", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "This problem was previously reported to Quality Engineering in SPR MROE6HHP8T, and was later fixed in 7.0. However, the problem has returned in Domino Administrator builds 8.5.1 and 8.5.2.\n\nThe cause was determined to be the bookmark.nsf. Both the bookmark.nsf and the domadmin.nsf contained their own list of servers. The error dialog, which contains the server name, is actually the servers that do not exist in the domadmin.nsf, but do exist in the bookmark.nsf.", "logical_doc_id": 6, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q237", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "Domino Administrator Client 8.5.1 and 8.5.2\n\nWindows XP/Vista/7", "logical_doc_id": 6, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q237", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "This problem has been reported again to Quality Engineering in SPR TMDS8CBVY4 and is currently under investigation.\n\nAs a workaround, you can recreate the local bookmark.nsf to resolve the issue.", "logical_doc_id": 6, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q237", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "When replying to an e-mail in Notes, you notice that the Notes Internet domain is added unexpectedly to the Send To address.\n\nFor example, when replying to an e-mail message from johndoe@us.widgets.com, the SendTo is addressed to johndoe@us.widgets.com@uswidgets.\n\nThis occurs in cases where multiple Notes domains are in use and inbound mail comes in via SMTP, with NRPC being used to route to the domains.\n\nExample:\nYou use multiple Notes domains with incoming and outgoing SMTP servers in different domains:\n*\n1. You send an Internet e-mail to a user in domain B from test@test.com:\n*\n*\n\n2. You open the received message and click Reply or Reply To All:\n*\n*\n\nThe address in the Send To field still contains the Notes domain. This should be stripped off since it is an e-mail address. The address in the cc: field is processed correctly.\n\nIf inbound and outbound SMTP traffic is separate and the servers are in two different domains, this is very problematic.", "logical_doc_id": 7, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q237", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Notes/Domino is working as designed. It can be critical that the domain information be appended since without it, sometimes mail may not route as expected.\n\nEnhancement requests to enhance the logic in this area have been made to Quality Engineering as SPR# NGRT4M7H67 and SPR# MCHT4LYK85.\n\nIf you want multiple domain information to remain in e-mail:\nAdd the following variable to the notes.ini file in the Notes client, \"NoOptimizeLocalRouting=1\", and restart Notes.\n\nUnsupported workaround\nThe following workaround will prevent the Notes Internet domain from being added to Internet addresses but may result in delivery failures under some scenarios.\n\nNOTE: The code below is a sample script, provided to illustrate one way to approach this issue and is used at your own risk. In order for this example to perform as intended, the script must be laid out exactly as indicated below. Product Support cannot customize this script for specific environments or applications.\nModify the formulas in the InheritedFrom and InheritedAltFrom fields in the Reply and Reply With History forms as follows:\n\nWho := @If\n(@IsAvailable(Principal) & Principal != \"\"; *\n\n@IsAvailable(From); *\n\n@Author *\n\n@If * (@IsAvailable(FromDomain) & (@Middle(who; \"@\";\".\")=\"\"); *\nWho", "logical_doc_id": 7, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q237", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "#A simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21602218]", "logical_doc_id": 7, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q095", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "How will I know if the OIDC certificate has expired?\n\nWhen the OIDC certificate has expired, users will receive a \"Secure Connection Failed\" message in their browser instead of the APM 8.1.3 Login Page.\n\nHow will I know if the APMUI certificate has expired?\n\nWhen the APMUI certificate has expired, users will receive a \"Your connection is not secure\" message that indicates the APM UI certificate has expired when navigating to APM server port 9443.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q095", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "To maintain valid UI certificates for installations that are still using the default out-of-the-box certificates, the existing keystore files must be replaced with the keystore files that are attached at the end of this technote.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q095", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "The following new keystore files that are attached to this technote contain certificates that expire in 2028.\n\n1. updated.8.1.3.oidc.key.jks (password: ccmR0cKs!)\n2. updated.8.1.3.apmui.key.jks (password: apmpass)\n3. updated.8.1.3.trust.jks (password: ccmR0cKs!)\n\nHow will I know if I need to update my existing keystore files?\n\n1. Identify the default self-signed oidc certificate by verifying the following:\nThe password is ccmR0cKs!\nThere's only a single certificate listed.\nAlias is \"default\".\nValid for a two year period.\nSignature Algorithm is SHA256withRSA.\nOwner: CN=localhost, O=IBM, OU=oidc, C=US and Issuer: CN=localhost, O=IBM, OU=oidc, C=US\n\n1.1. Navigate to the OIDC keystore directory by issuing the following command:\n\n# cd /opt/ibm/wlp/usr/servers/oidc/resources/security\n\n1.2. List the certificates in the key store by issuing the following command:\n\n# /opt/ibm/java/jre/bin/keytool -v -list -keystore ./key.jks\n\nEnter the keystore password: ccmR0cKs!\n\n1.3. Verify the output:\n\nKeystore type: jks\nKeystore provider: IBMJCE\nYour keystore contains 1 entry\nAlias name: default\nCreation date: Mar 12, 2018\nCertificate chain length: 1\nCertificate[1]:\nOwner: CN=localhost, O=IBM, OU=oidc, C=US\nIssuer: CN=localhost, O=IBM, OU=oidc, C=US\nSerial number: 59c006a2\nValid from: 3/12/18 7:07 AM until: 3/11/20 7:07 AM\nCertificate fingerprints:\nMD5: 3C:A8:D9:B5:6C:4E:32:44:4B:07:6C:21:0E:52:4A:0A\nSHA1: BD:C5:2F:F3:78:8C:D7:FC:0C:60:92:A9:33:3D:E4:75:90:C5:33:E6\nSHA256: EF:78:14:56:9D:99:86:C1:69:B8:AC:ED:E1:EC:30:AA:07:60:6B:76:D4:B1:5B:8E:E2:7B:17:23:5D:E8:3C:28\nSignature algorithm name: SHA256withRSA\nVersion: 3\nExtensions:\n#1: ObjectId: 2.5.29.14 Criticality=false\nSubjectKeyIdentifier [\nKeyIdentifier [\n0000: a2 dc 5d 96 22 55 ae 63 e1 43 0e d0 2c 96 17 63 .....U.c.C.....c\n0010: 9c fd 9d e8\n]\n]\n\n2. Identify the default shared trust.jks by verifying the following:\nThe password is ccmR0cKs!\nThere is only a single certificate listed.\nAlias is \"default\".\nValid for a 2 year period.\nSignature Algorithm is SHA256withRSA.\nOwner: CN=localhost, O=IBM, OU=oidc, C=US and Issuer: CN=localhost, O=IBM, OU=oidc, C=US\nSame serial # as the certificate in the above key.jks file\n\n2.1. Navigate to the shared trust store directory by issuing the following command:\n\n# cd /opt/ibm/wlp/usr/shared/resources/security\n\n2.2 List the certificates in the trust store by issuing the following command:\n\n# /opt/ibm/java/jre/bin/keytool -v -list -keystore ./trust.jks\n\nEnter the keystore password: ccmR0cKs!\n\n2.3. Verify the output:", "logical_doc_id": 2, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q095", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Keystore type: jks\nKeystore provider: IBMJCE\nYour keystore contains 1 entry\nAlias name: oidc\nCreation date: Mar 12, 2018\nEntry type: trustedCertEntry\nOwner: CN=localhost, O=IBM, OU=oidc, C=US\nIssuer: CN=localhost, O=IBM, OU=oidc, C=US\nSerial number: 59c006a2\nValid from: 3/12/18 7:07 AM until: 3/11/20 7:07 AM\nCertificate fingerprints:\nMD5: 3C:A8:D9:B5:6C:4E:32:44:4B:07:6C:21:0E:52:4A:0A\nSHA1: BD:C5:2F:F3:78:8C:D7:FC:0C:60:92:A9:33:3D:E4:75:90:C5:33:E6\nSHA256: EF:78:14:56:9D:99:86:C1:69:B8:AC:ED:E1:EC:30:AA:07:60:6B:76:D4:B1:5B:8E:E2:7B:17:23:5D:E8:3C:28\nSignature algorithm name: SHA256withRSA\nVersion: 3\nExtensions:\n#1: ObjectId: 2.5.29.14 Criticality=false\nSubjectKeyIdentifier [\nKeyIdentifier [\n0000: a2 dc 5d 96 22 55 ae 63 e1 43 0e d0 2c 96 17 63 .....U.c.C.....c\n0010: 9c fd 9d e8 ....\n]\n]\n\n3. Identify the default APMUI keystore by verifying the following:\nThe password is apmpass\nThere's only a single certificate listed\nAlias is \"default\"\nExpires 4/21/19\nSignature Algorithm is SHA256withRSA\nOwner: CN=liberty, O=IBM, C=US and Issuer: CN=liberty, O=IBM, C=US\n\n3.1. Navigate to the shared trust store directory by issuing the following command:\n\n# cd /opt/ibm/wlp/usr/servers/apmui/resources/security\n\n3.2. List the certificates in the trust store by issuing the following command:\n\n# /opt/ibm/java/jre/bin/keytool -v -list -keystore ./key.jks\n\nEnter keystore password: apmaas\n\n3.3 Verify the output:\n\nKeystore type: jks\nKeystore provider: IBMJCE\nYour keystore contains 1 entry\nAlias name: default\nCreation date: Apr 21, 2016\nEntry type: keyEntry\nCertificate chain length: 1\nCertificate[1]:\nOwner: CN=liberty, O=IBM, C=US\nIssuer: CN=liberty, O=IBM, C=US\nSerial number: 191bd82a\nValid from: 4/21/16 1:09 PM until: 4/21/19 1:09 PM\nCertificate fingerprints:\nMD5: 06:FB:FA:F0:68:49:65:38:6D:FB:B3:2D:8A:24:5D:2B\nSHA1: A2:39:41:40:F8:D5:3A:6D:80:62:D5:D5:6A:27:EB:9B:3A:35:B2:DA\nSHA256: 85:B9:FB:97:98:69:B8:DF:2A:B0:38:C6:3B:C7:87:CA:71:21:CA:CE:DE:D0:09:57:FF:AF:B7:EB:E8:77:FD:6D\nSignature algorithm name: SHA256withRSA\nVersion: 3\nExtensions:\n#1: ObjectId: 2.5.29.14 Criticality=false\nSubjectKeyIdentifier [\nKeyIdentifier [\n0000: 1b 97 38 19 52 43 34 f6 2a 0e 7f a4 22 db 07 80 ..8.RC4.........\n0010: 41 6e 47 a5 AnG.\n]\n]\n\nProcedures\n\nInstallation procedure (using /opt/ibm as the install directory)", "logical_doc_id": 2, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q095", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "1. Download the new keystore files attached at the end of this technote into a temporary directory (/ tmp) on the APM server.\n\n2. Stop APM by issuing the following command:\n\napm stop_all\n\n3. Back up the existing OIDC keystore by issuing the following command:\n\ncp /opt/ibm/wlp/usr/servers/oidc/resources/security/key.jks /opt/ibm/wlp/usr/servers/oidc/resources/security/key.jks.BAK\n\n4. Install the new OIDC keystore (replace the existing file) by issuing the following command:\n\ncp /tmp/updated.8.1.3.oidc.key.jks /opt/ibm/wlp/usr/servers/oidc/resources/security/key.jks\n\n5. Back up the existing APMUI keystore by issuing the following command:\n\ncp /opt/ibm/wlp/usr/servers/apmui/resources/security/key.jks /opt/ibm/wlp/usr/servers/apmui/resources/security/key.jks.BAK\n\n6. Install the new APMUI keystore (replace the exiting file) by issuing the following command:\n\ncp /tmp/updated.8.1.3.apmui.key.jks /opt/ibm/wlp/usr/servers/apmui/resources/security/key.jks\n\n7. Back up the existing UI truststore by issuing the following command:\n\ncp /opt/ibm/wlp/usr/shared/resources/security/trust.jks /opt/ibm/wlp/usr/shared/resources/security/trust.jks.BAK\n\n8. Install the new UI truststore (replace the existing file) by issuing the following command:\n\ncp /tmp/updated.8.1.3.trust.jks /opt/ibm/wlp/usr/shared/resources/security/trust.jks\n\n9. Restart APM by issuing the following command:\n\napm start_all\n\nVerification procedure - verifying the installation of the new keystore files\n\n1. After APM is restarted, navigate to the APMUI at https://:9443 [https://apm_server_hostname:9443/]\n\nwhere is the hostname of your V8.1.3 APM server.\n\n2. Verify that the APM Log in page appears and log in.\n\n3. Verify that agent data is shown on the APM dashboard. Note: The passwords for the keystores and truststore are the same as the passwords that were shipped in APM V8.1.3, therefore, you don't need to update theserver.xml and serverVariables.xml files.\n\nKeystore files:\n\nupdated.8.1.3.trust.jks [/support/docview.wss?uid=swg22016064&aid=2]updated.8.1.3.trust.jks [/support/docview.wss?uid=swg22016064&aid=1] updated.8.1.3.oidc.key.jks [/support/docview.wss?uid=swg22016064&aid=4]updated.8.1.3.oidc.key.jks [/support/docview.wss?uid=swg22016064&aid=3] updated.8.1.3.apmui.key.jks [/support/docview.wss?uid=swg22016064&aid=6]updated.8.1.3.apmui.key.jks [/support/docview.wss?uid=swg22016064&aid=5]", "logical_doc_id": 3, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q095", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "console.log in APMUI_HOME//usr/servers/apmui/logs has following messages:\n[AUDIT ] CWWKG0028A: Processing included configuration resource: /usr/Tivoli/APMUI/usr/shared/config/ldapRegistry.xml\n....\n[AUDIT ] CWWKS1100A: Authentication did not succeed for user ID apmadmin. An invalid user ID or password was specified.", "logical_doc_id": 4, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q095", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "LDAP properties in ldapRegistry.xml are not correct.", "logical_doc_id": 4, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q095", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Section \"Configuring an LDAP user registry for Liberty profile\" of Application Performance Management User Interface (APMUI) User Guide has a sample ldapRegistry.xml. The properties in this sample are only examples, the settings in this file are dependent on the specific LDAP setup in your environment.\n\n1) Contact LDAP administrator to determine LDAP Server settings for APMUI users. Validate what filters must be used, as well as values for the bindDN and bindPassword etc, based on how the LDAP Directory Information Tree (DIT) is configured.\n\nThe meaning of various properties in the ldapRegistry.xml are as follows:\n\nbaseDN: specifies the starting point in the LDAP (DIT) for all LDAP searches\nbindDN: specifies the distinguished name for the application server to use when it attempts to bind to the LDAP server\nbindPwd: specifies the password for the application server to user when binding to LDAP\n\nThe filters:\n\nuserFilter: defines the filter is used to search LDAP for users\ngroupFilter: defines the filter used to search LDAP for groups\nuserIdMap: specifies the LDAP filter that maps the short name of a user to an LDAP entry\ngroupIdMap: specifies the LDAP filter that maps the short name of a group to an LDAP entry\ngroupMemberIdMap: specifies the LDAP filter that identifies user-to-group relationships. It specifies which property of an objectclass stores the list of members belonging to the group represented by the objectclass.\n\nThe filters do not need to be specified. If they are not specified they contain default values depending on the LDAP server type (IBM Directory Server, Microsoft Active Directory etc). So these are always required, but if the default values match with the LDAP tree's configuration, then they do no need to be explicitly specified in the server.xml file.\n\nFor Active Directory, if no filters are specified, the default values for the filters are as follows:\n\n// Active Directory LDAP\n\nfilters.put(LdapConfig.USER_FILTER, \"(&(sAMAccountName=%v)(objectcategory=user))\");\nfilters.put(LdapConfig.GROUP_FILTER, \"(&(cn=%v)(objectcategory=group))\");\nfilters.put(LdapConfig.USER_ID_MAP, \"user:sAMAccountName\");\nfilters.put(LdapConfig.GROUP_ID_MAP, \"*:cn\");\nfilters.put(LdapConfig.GROUP_MEMBER_ID_MAP, \"memberof:member\");\n\nAgain, these should match with how the LDAP server is actually set up in terms of objectclasses, and attributes on the LDAP entries. The LDAP admin can confirm the same.\n\n2) Use ldapsearch utility to verify the settings in ldapRegistry.xml.\n\nNote: If you have IBM Lotus Notes installed, ldapsearch utility can be found under \"notes\" directory.", "logical_doc_id": 4, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q095", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "For example, if the ldapRegistry is setup as follows:\n\n\n\n\n\nThe following command matches what the APMUI Liberty Profile server does at runtime to authenticate user apmadmin based on above ldapRegistry.xml settings:\nldapSearch -h apmldap.sc.us.ibm.com -p 389 -b cn=users,dc=sc,dc=us,DC=ibm,DC=com -D cn=apmadmin,cn=users,dc=sc,dc=us,dc=ibm,dc=com -w testpassword uid=apmadmin\n\nHere the parameters to ldapsearch tool are as follows:\nh host ldap server [server.acme.com]\np port port on ldap server [389]\nb baseDN base dn for search [\"\"]\nD bindDN bind dn for simple authentication [NULL i.e. anonymous]\n\nIf the ldapsearch command does not execute successfully, then this confirms that the issue is with the\nldapRegistry.xml settings.\n\nA FIX IS AVAILABLE\nIBM SmartCloud Application Performance Management UI V7.7 Interim Fix 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24042494]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q095", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Approver: Hua Ming Zhong/China/IBM\n Compid: 5724G70UI\n Release: APMUI v7.7\n Environment: APMUI v7.7 IF02\n OS: Linux\n\n PROBLEM\n\n APMUI Overview -> CPU Overview -> CPU Detail -> Processor widget\n shows \"Dataprovider error\".\n\n Detailed Recreation Procedure:\n\n 1) Apply for APMUI v7.7 IF02\n 2) create application with Windows OS agent dashboard\n 3) In CPU detail page, you see no data, and may see data\n provider error in groupwidget \"Processor\".\n\n Related Files and Output:\n\n APM_UI.log shows:\n Cause: java.io.IOException: Server returned HTTP response code:\n 400 for URL\n http://hostname:15200/ibm/tivoli/rest/providers/hostname/datasou [http://hostname:15200/ibm/tivoli/rest/providers/hostname/datasou]\n rces/TMSAgent%25IBM.STATIC021/datasets/MetricGroup.NTPROCSSR/ite\n msproperties=TIMESTAMP,USERTIME,PRIVTIME,DPCTIME,INTERRTIME,INST\n CNAME&start=0¶m_providerVersion=06.30.05.00¶m_Limit=1000\n &condition=INSTCNAME%20=%201,10¶m_SourceToken=Primary:hostna\n me:NT¶m_Time...\n\n ITM data provider returned:\n ATKRST101E The parameter 'condition' with a value of 'INSTCNAME\n = 1,10' is not formatted correctly.\n\n Code change needed in APMUI to use condition clause like\n \"&condition=INSTCNAME='1,10' \"", "logical_doc_id": 5, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q095", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: APMUI users\n\nPROBLEM DESCRIPTION: APMUI Overview -> CPU Overview -> CPU\nDetail -> Processor widget shows \"Dataprovider error\".\n\nRECOMMENDATION: Apply APMUI 7.7 IF0003 when it is available", "logical_doc_id": 5, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q095", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The fix for this APAR is contained in the following maintenance\n packages:\n | interim fix | 7.7-TIV-APM_UI-IF0003\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q095", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV78320\nREPORTED COMPONENT NAME\n SMARTCLOUD APM\nREPORTED COMPONENT ID\n 5724G70UI\nREPORTED RELEASE\n 770\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2015-10-26\nCLOSED DATE\n 2017-08-08\nLAST MODIFIED DATE\n 2017-08-08\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q095", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n SMARTCLOUD APM\nFIXED COMPONENT ID\n 5724G70UI", "logical_doc_id": 5, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q095", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R770 PSY\n UP", "logical_doc_id": 5, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q095", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Which roles must a user have to integrate APMUI console in DASH?", "logical_doc_id": 6, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q095", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The DASH admin user may be defined on a different user repository from the APMUI user registry. For APMUI console integration to succeed, the DASH admin user must be defined in a common user repository for both APMUI and DASH servers.", "logical_doc_id": 6, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q095", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Below steps can be used to give administrative roles to a user from the APMUI user registry, and then log into DASH as this user to perform the console integration steps.\n\n1) Define user repository of APMUI in DASH.\n2) Identify a user from APMUI user repository to be granted admin role in DASH (the example below uses apmadmin user)\n3) Follow these steps to assign admin roles to the user:\n\n3.1 Log into DASH as a user with administrator privileges, select Console Settings->User Roles option.\n\n[/support/docview.wss?uid=swg21903489&aid=1] [/support/docview.wss?uid=swg21903489&aid=1]\n\n3.2 On the User Roles page, type the ID of APMUI user (for example, apmadmin) and then click the \"Search\" button. Click the link for the user in returned search results.\n\n[/support/docview.wss?uid=swg21903489&aid=2] [/support/docview.wss?uid=swg21903489&aid=2]\n\n3.3 Select the \"administrator\" and \"iscadmins\" roles and then click \"Save\".\n\n[/support/docview.wss?uid=swg21903489&aid=3] [/support/docview.wss?uid=swg21903489&aid=3]\n\n4) Use this administrative user to perform console integration steps.", "logical_doc_id": 6, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q095", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "Integrating APMUI with DASH [http://www-01.ibm.com/support/knowledgecenter/SSATHD_7.7.0/com.ibm.apm.doc_77/apm_ui_docs/apmui_77/integrate_APMUI_with_DASH.html]\nDASH - Adding the LDAP user registry as a federated rep [http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/config/psc_t_config_add_ldap_rep.html]\nDASH - Configuring the LDAP federated repository [http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/config/psc_t_config_fed_rep.html?lang=en]", "logical_doc_id": 6, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q095", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "When launching the OpenPages reporting framework generation process, it is completing with errors. When clicking on 'Cognos Framework Generation' sub operation, why is the log showing: ERROR! java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server?", "logical_doc_id": 7, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q095", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The OpenPages application is unable to connect to URL and port utilized by the OpenPages Framework Model Service.", "logical_doc_id": 7, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q095", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "When an OpenPages 5.x administrator reviews the Cognos Framework Generation sub operation task, the log records:\n\nCognos Framework Generation [OPENPAGES_DEFAULT]: ERROR! java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'myreportingserver.ibm.com', port: '9080'\n\nwhere myreportingserver.ibm.com is name of the reporting server and the OpenPages Framework Model Service is listening on port 9080.\n\nWhen an OpenPages 6.x administrator reviews the Reporting Framework Subprocess sub operation task, the log records:\n\nGenerating Framework Model, Facts and Dimensions, Custom Query Subjects. [DEFAULT]: ERROR! java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'myreportingserver.ibm.com', port: '8080'\n\nwhere myreportingserver.ibm.com is name of the reporting server and the OpenPages Framework Model Service is listening on port 8080.\n\nIn most instances, the OpenPages administrator does not have the OpenPages Framework Model Service up and running on the reporting server. If the issue is occurring for a new installation, there could be a firewall blocking the connection.\n\nTo resolve the issue, an administrator should start the service and verify that the application server can make a valid connection.", "logical_doc_id": 7, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q095", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#Reporting Framework Troubleshooting Steps [http://www.ibm.com/support/docview.wss?uid=swg21514115]\nIntegration Between OpenPages and Cognos [http://www.ibm.com/support/docview.wss?uid=swg21628148]", "logical_doc_id": 7, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q044", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Managed File Transfer process controller\u6a5f\u80fd\u306e\u305f\u3081\u306bWebSphere MQ\u304c\u540c\u68b1\u3057\u3066\u3044\u308bICU4C\u3067\u306f\u3001_canonicalize \u95a2\u6570\u306b\u30b9\u30bf\u30c3\u30af\u30d9\u30fc\u30b9\u306e\u30d0\u30c3\u30d5\u30a1\u30aa\u30fc\u30d0\u30fc\u30d5\u30ed\u30fc\u306e\u8106\u5f31\u6027\u304c\u5b58\u5728\u3057\u307e\u3059\u3002", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q044", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "\u8106\u5f31\u6027\u306e\u8a73\u7d30\uff1a\n\nCVEID: CVE-2011-4599 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4599]\nDESCRIPTION: International Components for Unicode is vulnerable to a stack-based buffer overflow, caused by improper bounds checking by the _canonicalize( ) function. By supplying a negative len value, a remote attacker could overflow a buffer and execute arbitrary code on the system or cause the application to crash.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/71726 [https://exchange.xforce.ibmcloud.com/vulnerabilities/71726] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:P/A:P)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q044", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "\u5f71\u97ff\u306e\u3042\u308b\u88fd\u54c1\u30fb\u30d0\u30fc\u30b8\u30e7\u30f3\uff1a\n\nIBM WebSphere MQ \u306e\u4ee5\u4e0b\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u306b\u5f71\u97ff\u304c\u3042\u308a\u307e\u3059\u3002\nV8.0.0.3 \u304a\u3088\u3073\u305d\u308c\u4ee5\u524d\u306e\u4fdd\u5b88\u30ec\u30d9\u30eb\nV7.5.0.5 \u304a\u3088\u3073\u305d\u308c\u4ee5\u524d\u306e\u4fdd\u5b88\u30ec\u30d9\u30eb", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q044", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "\u4fee\u6b63\u7b56\uff1a\n\nIBM WebSphere MQ 8.0\nFixPack 8.0.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg21969244] \u4ee5\u964d\u3092\u9069\u7528\u3057\u3066\u304f\u3060\u3055\u3044\n\nIBM WebSphere MQ 7.5\nFixPack 7.5.0.6 [http://www-01.ibm.com/support/docview.wss?uid=swg21975660] \u4ee5\u964d\u3092\u9069\u7528\u3057\u3066\u304f\u3060\u3055\u3044", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q044", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q044", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\n[IBM\u30b5\u30a4\u30c8]\n\u3053\u306e\u6587\u66f8\u306f\u3001\u7c73\u56fd IBM \u793e\u306e\u8cc7\u6599\u3092\u7ffb\u8a33\u3057\u305f\u53c2\u8003\u6587\u66f8\u3067\u3059\u3002\u7ffb\u8a33\u5143\u306e\u6587\u66f8\u306f\u3001\u4ee5\u4e0b\u306e\u30ea\u30f3\u30af\u3088\u308a\u3054\u53c2\u7167\u304f\u3060\u3055\u3044\u3002\nSecurity Bulletin: ICU4C overflow vulnerability affects IBM WebSphere MQ (CVE-2011-4599) [http://www.ibm.com/support/docview.wss?uid=swg21975091&myns=swgws&mynp=OCSSFKSJ&mync=E&cm_sp=swgws-_-OCSSFKSJ-_-E]\n\n\u516c\u958b\u6e08\u307f\u306e\u30d5\u30a3\u30c3\u30af\u30b9\u30d1\u30c3\u30af\u306b\u3064\u3044\u3066\u306f\u3001\u4ee5\u4e0b\u306e\u30b5\u30a4\u30c8\u3088\u308a\u3054\u5229\u7528\u3044\u305f\u3060\u3051\u307e\u3059\u3002\nRecommended fixes for WebSphere MQ [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\n\u30d5\u30a3\u30c3\u30af\u30b9\u30fb\u30d1\u30c3\u30af\u306e\u516c\u958b\u4e88\u5b9a\u306b\u3064\u3044\u3066\u306f\u3001\u4ee5\u4e0b\u306e\u30b5\u30a4\u30c8\u3088\u308a\u3054\u78ba\u8a8d\u3044\u305f\u3060\u3051\u307e\u3059\u3002\nWebSphere MQ planned maintenance release dates [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n[CVSS\u60c5\u5831]\n\u72ec\u7acb\u884c\u653f\u6cd5\u4eba \u60c5\u5831\u51e6\u7406\u63a8\u9032\u6a5f\u69cb: \u5171\u901a\u8106\u5f31\u6027\u8a55\u4fa1\u30b7\u30b9\u30c6\u30e0CVSS\u6982\u8aac [http://www.ipa.go.jp/security/vuln/CVSS.html]\nJVN iPedia: CVSS\u8a08\u7b97\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u65e5\u672c\u8a9e\u7248 [http://jvndb.jvn.jp/cvss/ja.html] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT]\n\u95a2\u9023\u60c5\u5831\uff1a\n.\n[\u304a\u554f\u5408\u305b\u5148]\n\u6280\u8853\u7684\u306a\u5185\u5bb9\u306b\u95a2\u3057\u3066\u3001\u30b5\u30fc\u30d3\u30b9\u5951\u7d04\u306e\u3042\u308b\u304a\u5ba2\u69d8\u306fIBM\u30b5\u30fc\u30d3\u30b9\u30fb\u30e9\u30a4\u30f3\u306b\u304a\u554f\u3044\u5408\u308f\u305b\u304f\u3060\u3055\u3044\u3002\nIBM \u30b5\u30fc\u30d3\u30b9\u30fb\u30e9\u30a4\u30f3 [http://www.ibm.com/jp/news/20070420001.html] *The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.\n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q044", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere MQ Managed File Transfer\u304c\u4f7f\u7528\u3059\u308bApache Commons FileUpload \u306b\u306f\u3001\u30ed\u30fc\u30ab\u30eb\u30e6\u30fc\u30b6\u306b\u3088\u308b\u4e0d\u7279\u5b9a\u306e\u30b7\u30f3\u30dc\u30ea\u30c3\u30af\u30ea\u30f3\u30af\u653b\u6483 (symlink attack) \u304c\u30d5\u30a1\u30a4\u30eb\u3092\u4e0a\u66f8\u3059\u308b\u53ef\u80fd\u6027\u304c\u3042\u308a\u307e\u3059\u3002", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q044", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "\u8106\u5f31\u6027\u306e\u8a73\u7d30\uff1a\nCVEID: CVE-2013-0248 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0248]\nDESCRIPTION: Apache Commons FileUpload could allow a local attacker to launch a symlink attack. Temporary files are created insecurely. A local attacker could exploit this vulnerability by creating a symbolic link from a temporary file to various files on the system, which could allow the attacker to overwrite arbitrary files on the system with elevated privileges.\nCVSS Base Score: 3.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/82618 [https://exchange.xforce.ibmcloud.com/vulnerabilities/82618] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:L/AC:M/Au:N/C:N/I:P/A:P)", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q044", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "\u5f71\u97ff\u306e\u3042\u308b\u88fd\u54c1\u30fb\u30d0\u30fc\u30b8\u30e7\u30f3\uff1a\n\nIBM WebSphere MQ \u306e\u4ee5\u4e0b\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u306b\u5f71\u97ff\u304c\u3042\u308a\u307e\u3059\u3002\nV8.0.0.3 \u304a\u3088\u3073\u305d\u308c\u4ee5\u524d\u306e\u4fdd\u5b88\u30ec\u30d9\u30eb\nV7.5.0.5 \u304a\u3088\u3073\u305d\u308c\u4ee5\u524d\u306e\u4fdd\u5b88\u30ec\u30d9\u30eb", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q044", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "\u4fee\u6b63\u7b56\uff1a\n\nIBM WebSphere MQ 8.0\nFixPack 8.0.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg21969244] \u4ee5\u964d\u3092\u9069\u7528\u3057\u3066\u304f\u3060\u3055\u3044\n\nIBM WebSphere MQ 7.5\nFixPack 7.5.0.6 [http://www-01.ibm.com/support/docview.wss?uid=swg21975660] \u4ee5\u964d\u3092\u9069\u7528\u3057\u3066\u304f\u3060\u3055\u3044", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q044", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q044", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\n\n[IBM\u30b5\u30a4\u30c8]\n\u3053\u306e\u6587\u66f8\u306f\u3001\u7c73\u56fd IBM \u793e\u306e\u8cc7\u6599\u3092\u7ffb\u8a33\u3057\u305f\u53c2\u8003\u6587\u66f8\u3067\u3059\u3002\u7ffb\u8a33\u5143\u306e\u6587\u66f8\u306f\u3001\u4ee5\u4e0b\u306e\u30ea\u30f3\u30af\u3088\u308a\u3054\u53c2\u7167\u304f\u3060\u3055\u3044\u3002\nSecurity Bulletin: Apache Commons FileUpload vulnerability affects IBM WebSphere MQ Managed File Transfer (CVE-2013-0248) [http://www.ibm.com/support/docview.wss?uid=swg21975093&myns=swgws&mynp=OCSSFKSJ&mync=E&cm_sp=swgws-_-OCSSFKSJ-_-E]\n\n\u516c\u958b\u6e08\u307f\u306e\u30d5\u30a3\u30c3\u30af\u30b9\u30d1\u30c3\u30af\u306b\u3064\u3044\u3066\u306f\u3001\u4ee5\u4e0b\u306e\u30b5\u30a4\u30c8\u3088\u308a\u3054\u5229\u7528\u3044\u305f\u3060\u3051\u307e\u3059\u3002\nRecommended fixes for WebSphere MQ [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\n\u30d5\u30a3\u30c3\u30af\u30b9\u30fb\u30d1\u30c3\u30af\u306e\u516c\u958b\u4e88\u5b9a\u306b\u3064\u3044\u3066\u306f\u3001\u4ee5\u4e0b\u306e\u30b5\u30a4\u30c8\u3088\u308a\u3054\u78ba\u8a8d\u3044\u305f\u3060\u3051\u307e\u3059\u3002\nWebSphere MQ planned maintenance release dates [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\n[CVSS\u60c5\u5831]\n\u72ec\u7acb\u884c\u653f\u6cd5\u4eba \u60c5\u5831\u51e6\u7406\u63a8\u9032\u6a5f\u69cb: \u5171\u901a\u8106\u5f31\u6027\u8a55\u4fa1\u30b7\u30b9\u30c6\u30e0CVSS\u6982\u8aac [http://www.ipa.go.jp/security/vuln/CVSS.html]\nJVN iPedia: CVSS\u8a08\u7b97\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u65e5\u672c\u8a9e\u7248 [http://jvndb.jvn.jp/cvss/ja.html] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT]\n\u95a2\u9023\u60c5\u5831\uff1a\n.\n[\u304a\u554f\u5408\u305b\u5148]\n\u6280\u8853\u7684\u306a\u5185\u5bb9\u306b\u95a2\u3057\u3066\u3001\u30b5\u30fc\u30d3\u30b9\u5951\u7d04\u306e\u3042\u308b\u304a\u5ba2\u69d8\u306fIBM\u30b5\u30fc\u30d3\u30b9\u30fb\u30e9\u30a4\u30f3\u306b\u304a\u554f\u3044\u5408\u308f\u305b\u304f\u3060\u3055\u3044\u3002\nIBM \u30b5\u30fc\u30d3\u30b9\u30fb\u30e9\u30a4\u30f3 [http://www.ibm.com/jp/news/20070420001.html] *The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.\n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q044", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "OpenSSL vulnerabilities were disclosed on March 19, 2015 by the OpenSSL Project. OpenSSL is used by IBM WebSphere MQ Advanced Message Security for the IBM i platform, IBM WebSphere MQ HP-NSS and IBM WebSphere MQ Paho MQTT clients. IBM WebSphere MQ Advanced Message Security for the IBM i platform and IBM WebSphere MQ HP-NSS client have addressed the applicable CVEs.", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q044", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2015-0209 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0209]\nDESCRIPTION: OpenSSL could allow a remote attacker to execute arbitrary code on the system, caused by a use-after-free error in the d2i_ECPrivateKey or EVP_PKCS82PKEY function. An attacker could exploit this vulnerability to corrupt memory and execute arbitrary code on the system and cause a denial of service.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101674 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101674] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:P/A:P)\n\nCVEID: CVE-2015-0286 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0286]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an error in the ASN1_TYPE_cmp function when attempting to compare ASN.1 boolean types. An attacker could exploit this vulnerability to crash any certificate verification operation and cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101666 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101666] 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-0289 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0289]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by the failure to properly handle missing outer ContentInfo by the PKCS#7 parsing code. An attacker could exploit this vulnerability using a malformed ASN.1-encoded PKCS#7 blob to trigger a NULL pointer dereference.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101669 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101669] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q044", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM WebSphere MQ Advanced Message Security for IBM i platform - V8.0.0.2 and earlier\n\nIBM WebSphere MQ Client for HP Integrity NonStop Server - V8.0.0.2 and earlier\n\nIBM Mobile Messaging and M2M Client Pack - Eclipse Paho MQTT C Client libraries for Linux & Windows platforms only", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q044", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "IBM WebSphere MQ Advanced Message Security for IBM i platform\n\nThe fix is provided in fix pack 8.0.0.3 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.2&platform=IBM+i&function=all]. or later.\n\nIBM WebSphere MQ HP-NSS client\n\nThe fix is provided in fix pack 8.0.0.3 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.2&platform=HP+NonStop&function=all] or later.", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q044", "section_id": 4, "heading": "WORKAROUNDS AND MITIGATIONS", "parent": null, "text": "Eclipse Paho MQTT C Client (Linux & Windows)\n\nThe C client libraries provided by the MA9B SupportPac can also be rebuilt from source and linked against OpenSSL 1.0.1m or later using the following instructions [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mm.tc.doc/tc10155_.htm].", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q044", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q044", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\nOpenSSL Project vulnerability website [http://www.openssl.org/news/vulnerabilities.html] (for detail on what versions are affected)\nOpenSSL Advisory on above listed CVEs [https://www.openssl.org/news/secadv_20150319.txt] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT\nNone.\n\nCHANGE HISTORY\n 22 June 2015 - Original Version Published.\nThe 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.", "logical_doc_id": 2, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q044", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21962359]", "logical_doc_id": 2, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q044", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "A security vulnerability has been discovered in OpenSSL.", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q044", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVE ID: CVE-2014-0160 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0160]\nDESCRIPTION:\nOpenSSL could allow a remote attacker to obtain sensitive information, caused by an error in the TLS/DTLS heartbeat functionality. An attacker could exploit this vulnerability to expose 64k of private memory and retrieve secret keys. An attacker can repeatedly expose additional 64k chunks of memory. This vulnerability can be remotely exploited, authentication is not required and the exploit is not complex. An exploit can only partially affect the confidentially, but not integrity or availability.\n\nCVSS:\nCVSS Base Score: 5\nCVSS Temporal Score: See http://xforce.iss.net/xforce/xfdb/92322 [http://xforce.iss.net/xforce/xfdb/92322] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)\n\nWarning: We strongly encourage you to take action as soon as possible as potential implications to your environment may be more serious than indicated by the CVSS score.", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q044", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "This vulnerability is known to affect the following offerings;\nSupport Pac MAT1 - WebSphere MQ client for HP Integrity NonStop Server\nSupport Pac MA9B - IBM Mobile Messaging and M2M Client Pack - Eclipse Paho MQTT C Client libraries for Linux & Windows platforms only\n\nNote that the Paho MQTT C client libraries provided for Linux and Windows platforms in IBM WebSphere MQ 7.1 and IBM WebSphere MQ 7.5 are also affected.\n\nThis vulnerability does NOT affect any version or release of the following on any other platforms: * IBM WebSphere MQ Client\nIBM WebSphere MQ Server\nIBM WebSphere MQ Managed File Transfer\nIBM WebSphere MQ Advanced Message Security\n\nNote that IBM Java JSSE does not use OpenSSL and so it is NOT affected by this vulnerability. REMEDIATION/FIXES\nBoth the HP Integrity NonStop Server MQ client and Paho MQTT C clients for Linux and Windows platforms have been updated to use OpenSSL 1.0.1g, which contains a fix for the heartbleed vulnerability.\nA refreshed install image for the HP Integrity NonStop Server MQ client can be downloaded from Fix Central here [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?product=ibm/WebSphere/WebSphere+MQ&release=7.1&platform=All&function=fixId&fixids=MQ-7100-hpns-ia64-OpenSSL101g&includeSupersedes=0].\nA refreshed zip file containg the Paho MQTT C client can be downloaded from Fix Central here [http://www-933.ibm.com/support/fixcentral/swg/quickorder?product=ibm/WebSphere/WebSphere+MQ&release=7.5&platform=All&function=fixId&fixids=1.0.0.3-WS-MQCP-MA9B-OpenSSL101g&includeSupersedes=0].\n\nAfter applying the fix(es), additional steps are recommended for CVE-2014-0160 *\n*\n*\n*\n*\n\nWarning: Your environment may require additional fixes for other products, including non-IBM products. Please replace the SSL certificates and reset the user credentials after applying the necessary fixes to your environment. WORKAROUNDS AND MITIGATIONS\nThe C client libraries provided by the MA9B Support Pac can also be rebuilt from source and linked against OpenSSL 1.0.1g using the following instructions [http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/topic/com.ibm.mm.tc.doc/tc10155_.htm].", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q044", "section_id": 3, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS Guide [http://www.first.org/cvss/cvss-guide.html]\nOn-line Calculator V2 [http://nvd.nist.gov/cvss.cfm?calculator&adv&version=2] [https://www-304.ibm.com/support/docview.wss?uid=swg21496117&wv=1] OpenSSL Project vulnerability website [http://www.openssl.org/news/vulnerabilities.html]\nHeartbleed [http://heartbleed.com/] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] ACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 9th April 2014 - Original Copy Published\n11th April 2014 - Links to fix central added, CVSS score updated\n12th April 2014 - Updated description to indicate an attacker can repeated use exploit\nThe 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.", "logical_doc_id": 3, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q044", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "#A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21669903]\n\nPRODUCT ALIAS/SYNONYM\n WMQ MQ", "logical_doc_id": 3, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q044", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Shared memory leak caused by MQ applications using dynamic queues.", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q044", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2017-1283 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1283]\nDESCRIPTION: IBM WebSphere MQ could allow an authenticated user to cause a shared memory leak by MQ applications using dynamic queues, which can lead to lack of resources for other MQ applications.\nCVSS Base Score: 3.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/125144 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125144] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L)", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q044", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM 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", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q044", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "IBM 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]", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q044", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q044", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 4, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q044", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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\nThe 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.", "logical_doc_id": 4, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q013", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How to resolve \"ZeroGur: Windows DLL failed to load\" error when installing IBM Decision Optimization Center 3.9 on Windows 10?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q013", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "IBM Decision Optimization Center 3.9 is not officially supported on Windows 10.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q013", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "This error occurs when installing the JViews component in IBM Decision Optimization Center 3.9 on Windows 10.\n\nThere are two ways to get around this:\n\n1. Install IBM Decision Optimization Center 3.9 without checking the JViews component, the installation will go through.\n\nThen install JViews manually:\nlaunch \\Developer\\redist\\JViews\\jviewsenterprise-8.8.exe,\nthen install JViews fixpack:\nin \\Developer\\redist\\JViews run the following 3 commands (run as admin):\nset PATH=%PATH%;\"\\Developer\\sdk\\bin\"\ncd /D \\Developer\\redist\\JViews\n\"\\Developer\\sdk\\bin\\java.exe\" -jar \"\\Developer\\redist\\JViews\\jviewsenterprise-8.8_11.jar\".\n\n2. Install IBM Decision Optimization Center 3.9 by launching the executable file \"odme_developer.exe\" in Windows 7 compatible mode:\nin DOC_Developer_V3.9_Win_x86-64\\Disk1\\InstData\\VM\\ right click on odme_developer.exe and go to \"Properties\",\nin \"Compatibility\" tab, check \"Run this program in compatibility mode for:\" and select \"Windows 7\" (cannot change compatibility mode if .bat),\nthen launch odme_developer.exe (check JViews install check box).", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q013", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "When and how should I apply a modification or fix pack to my JRules or Operational Decision Management (WODM/ODM) installation?", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q013", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The Operational Decision Manager version numbers use the standard IBM formatV.R.M.Fwhich stands for Version.Release.Modification.Fixpack. See the V.R.M.F Maintenance Stream Delivery Vehicle terminology explanation [http://www.ibm.com/support/docview.wss?uid=swg27008656] for more details.\n\nModification and fix pack numbers are the third and fourth digits in the IBM product version number, for example: 8.5.M.F.\n\nModification and fix packs include only bug fixes, so they do not affect the product functionality or your data.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q013", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "See the following technotes to find out which update your installation need:\nFinding the version of ODM product and fixes [http://www.ibm.com/support/docview.wss?uid=swg21627850] to determine the exact product versions that are installed on your machine.\nFind the version of ODM components [http://www.ibm.com/support/docview.wss?uid=swg21400738] to determine the exact module or library versions that are deployed on your servers.\nOperational Decision Manager Download document [http://www.ibm.com/support/docview.wss?uid=swg24031636] to learn about the latest modification or fix pack that is available for your product version.\nIBM Operational Decision Manager detailed system requirements [http://www.ibm.com/support/docview.wss?uid=swg27023067] to verify that your configuration is supported with your current product version.\nIBM Support Lifecycle [http://www.ibm.com/software/websphere/support/lifecycle/] to verify that your current version does not reach end of support in the near future.", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q013", "section_id": 0, "heading": "ANSWER", "parent": null, "text": "As with any software product, even if you do not have any issues with running your current configuration, you should apply the latest modification or fix pack to take advantage of these benefits:\nAnticipate and avoid the risk of encountering defects already fixed.\nApply the latest product improvements that are available (performance, for example).\nMaintain a serviceable system and be able to install an interim fix when required.\n\nWHEN TO UPDATE\nThe latest modification or fix pack should be installed as soon as it is available.\n\nYou can subscribe to the IBM Support My Notifications [https://www.ibm.com/support/mynotifications] to be notified of any fix pack releases, and you can also bookmark the Operational Decision Manager Download document [http://www.ibm.com/support/docview.wss?uid=swg24031636] page, which lists the latest modifications or fix packs.", "logical_doc_id": 3, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q013", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "See the technote Fix pack release notification for Operational Decision Manager [http://www.ibm.com/support/docview.wss?uid=swg21665593] to find out when a modification or fix pack will be available.\n\nBEFORE UPDATING\n\nThe databases used in the sample server are deleted and recreated during the update. If you are using those databases and want to save the existing content, perform the following steps before updating:\nStop the sample server. In the folder /shared/data/derby, create an archive file containing the resdb and rtsdb folders. Save the archive file, such as zip file, in the data folder. After installation, unzip the archive file in the folder /shared/data/derby to restore your databases before restarting the sample server.\n\nA new profile is also created for the sample server, at the first server start following the installation of a modification or fix pack.\n\nIf you want to continue using the same ports, you must delete the existing profile prior. In the /shared/bin folder, from the command line, run the command ../tools/ant/bin/ant forcedestroyprofile.\n\nNote: The sample server is not designed to be used in a production system. For a production system, you must create a dedicated profile and database that you update using the following steps.\n\nUPDATING\n\nEach modification or fix pack page provides instructions on how to download and run the installer, in addition to providing a list of corrections that are included in the update.\n\nThe fix pack installation updates the following files and folders: * JAR libraries in the installation directories, including \\\\lib.\nEAR and WAR applications in the \\\\applicationservers\\ folders.\n\nOnce this is done, you perform these tasks: * Repackage your client applications with the up-to-date libraries.\nReapply product customizations to the up-to-date Java EE modules (EARs and WARs).\n\nNote that all customizations you developed before the update, for example modifications of the descriptors, must be reapplied to the new, up-to-date EARs and WARs. It is a good idea to document and automate those customizations using scripts to make the process easier and error-proof.\n\nFinally, you must update the client applications and ODM modules on your server or servers with the same settings as you deployed previously. If you redeploy the application, follow again the documentation instructions to deploy all ODM modules to your servers [http://pic.dhe.ibm.com/infocenter/dmanager/v8r5m1/topic/com.ibm.odm.distrib.config/topics/odm_distrib_config.html].", "logical_doc_id": 4, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q013", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Keep in mind that applying a modification or a fix pack does not require any data migration, so your projects and database remain the same.\n\nUPDATING RULE EXECUTION SERVER\n\nUpdate the following applications in the application server: * jrules-res-xu-.rar jrules-res-management-.ear jrules-ssp-.ear jrules-res-htds-ear\n\nMake sure you do not change the class loading policies for applications and modules ( parent last for all ODM modules).\n\nNote: Updating the eXecution Unit RAR file requires a restart of the server.\n\nUPDATE DECISION CENTER\n\nUpdate the following application in your application server:\njrules-teamserver-.ear\n\nMake sure you do not change the class loading policies for applications and modules ( parent last for all ODM modules).\n\nUPDATE THE EVENTS RUNTIME\n\n1. Stop the event runtime application, wberuntimeear.\n 2. Uninstall the following applications, if they exist: * wbefileconnector\nwbehttpconnector\nwbejdbcconnector\nwbejmsconnector\nwbesoapconnector\n\n3. Update the application wberuntimeear.\n 4. Start the application wberuntimeear.\n\nMake sure you do not change the class loading policies for applications and modules ( parent last for all ODM modules).\n\nADDITIONAL CONSIDERATIONS", "logical_doc_id": 4, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q013", "section_id": 0, "heading": "RELATED INFORMATION", "parent": null, "text": "Fix pack release notification for ODM [http://www.ibm.com/support/docview.wss?uid=swg21665593 ]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere ILOG JRules Maintenance Platform Independent 7.1, 7.0\n\nDOWNLOADABLE FILES", "logical_doc_id": 5, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q013", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This cumulative fix pack updates Operational Decision Manager V8.5.1 to V8.5.1.1.", "logical_doc_id": 6, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q013", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "This fix pack is entitled. Only customers who have purchased Operational Decision Manager V8.5.1 can use this fix pack.\n\nHow to install the fix pack\nIf you are not installing both components, skip the instructions regarding Decision Center or Decision Server.\n\n1. For Decision Center, download 8.5.1-WS-ODM_DC--FP001.zip, and extract its files. (Change to match your platform: AIX, HPUX, LINUX, OS400, SOLARIS, ZOS, or WIN32.)\n 2. Extract the archive to a new folder, named WDC.\n 3. For Decision Server, Download 8.5.1-WS-ODM_DS--FP001.zip, and extract its files. (Change to match your platform: AIX, HPUX, LINUX, OS400, SOLARIS, ZOS, or WIN32.)\n 4. Extract the archive to a new folder, named WDS.\n\nInstalling by using IBM Installation Manager: 1. Launch IBM Installation Manager.\n 2. In the toolbar menu, open File > Preferences and do the following:\n 3. Select repositories. 1. For Decision Center, click Add Repository.\n 2. Browse to the extracted folder WDC\\updates.\n 3. Select the file repository.config.\n 4. For Decision Server, click Add Repository.\n 5. Browse to the extracted folder WDS\\updates.\n 6. Select the file repository.config.\n 7. Make sure the repositories are selected in the Repositories list.\n\n4. Click Apply to save your changes, and click OK to close the Repositories list.\n 5. Click Update to update your installation.\n 6. Follow the instructions in the installation manager to complete the installation.\n\nInstalling by using the Installation Manager command line: 1. Locate the imcl command under /eclipse/tools.\n 2. Run the commandimcl updateAll -repositories WDC/updates,WDS/updates -acceptLicense.\nUse the option -installDirectory to update a specific installation.\nIf you update only Decision Server or Decision Center, specify the repository accordingly.\n\nApplying the fix pack\nAfter you install the fix pack, you might have to do additional steps to apply the fix pack in your environment. To complete the update, see When and how to apply a modification or fix pack [http://www-01.ibm.com/support/docview.wss?uid=swg21665766].", "logical_doc_id": 6, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q013", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Warning:\nIf you have installed interim fixes for Operational Decision Manager V8.5.1, you must uninstall the fixes before you can install this fix pack. You must also stop the Operational Decision Manager sample server for this installation. If you do not uninstall the fixes and stop the server, the installation of the fix pack will fail. If you attempt to install the fix pack without uninstalling the interim fixes, the installer will uninstall the interim fixes before it fails. In this case, stop the sample server and restart the installation. INSTALLATION INSTRUCTIONS\nFollow the instructions provided in the following resources:\n\nURL LANGUAGE SIZE(Bytes) ODM 8.5.1.1 AIX [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.1&platform=AIX&function=all] Language Independent 4000000000 ODM 8.5.1.1 HPUX [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.1platform=HPUX&function=all] Language Independent 4000000000 ODM 8.5.1.1 Linux PPC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.1&platform=Linux+PPC&function=all] Language Independent 4000000000 ODM 8.5.1.1 Linux x86 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.1&platform=Linux+x86&function=all] Language Independent 4000000000 ODM 8.5.1.1 Linux zSeries [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.1&platform=Linux+zSeries&function=all] Language Independent 4000000000 ODM 8.5.1.1 OS/400 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.1&platform=OS/400&function=all] Language Independent 4000000000 ODM 8.5.1.1 Solaris 32-bit SPARC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.1&platform=Solaris+32-bit,SPARC&function=all] Language Independent 4000000000 ODM 8.5.1.1 Solaris 64-bit SPARC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.1&platform=Solaris+64-bit,SPARC&function=all] Language Independent 4000000000 ODM 8.5.1.1 Solaris 32-bit x86 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.1&platform=Solaris+32-bit,x86&function=all] Language Independent 4000000000 ODM 8.5.1.1 Solaris 64-bit x86 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.1&platform=Solaris+64-bit,x86&function=all] Language Independent 4000000000 ODM 8.5.1.1 Windows [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.1&platform=Windows&function=all] Language Independent 4000000000\nDOWNLOAD PACKAGE\n\nPROBLEMS SOLVED\n Fix List for IBM Operational Decision Manager [http://www.ibm.com/support/docview.wss?uid=swg27023767]\n\n[/support/docview.wss?uid=swg24037905&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24037905&aid=2]Problems (APARS) fixed\nPI15995, PI16188, RS01057, RS01350, RS01407, RS01429, RS01430, RS01451, RS01452, RS01453, RS01456, RS01462, RS01464, RS01465, RS01466, RS01467, RS01468, RS01469, RS01471, RS01472, RS01473, RS01474, RS01475, RS01476, RS01478, RS01479, RS01483, RS01484, RS01485, RS01487, RS01488, RS01491, RS01492, RS01496, RS01498, RS01499, RS01502, RS01503, RS01506, RS01508, RS01511, RS01512, RS01513, RS01520, RS01521, RS01522, RS01523, RS01525, RS01529, RS01532, RS01533, RS01534, RS01535, RS01536, RS01537, RS01538, RS01539, RS01540, RS01543, RS01545, RS01549, RS01553, RS01556, RS01558, RS01561, RS01562, RS01564, RS01569, RS01586, RS01598, RS01607, RS01611, RS01612, RS01614, RS01622, RS01627, RS01650, RS01651, RS01656, RS01665, RS01666", "logical_doc_id": 6, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q013", "section_id": 2, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Operational Decison Manager z/OS 8.8.1.2 Fix Pack [http://www-01.ibm.com/support/docview.wss?uid=swg24043654]\nOperational Decision Manager V8.8.1.2 Fix Pack [http://www-01.ibm.com/support/docview.wss?uid=swg24043530]\nOperational Decision Manager V8.9.0.1 Fix Pack [http://www-01.ibm.com/support/docview.wss?uid=swg24043671]\nOperational Decison Manager z/OS 8.9.0.1 Fix Pack [http://www-01.ibm.com/support/docview.wss?uid=swg24043670]\nOperational Decision Manager V8.9.1 Download Document [http://www-01.ibm.com/support/docview.wss?uid=swg24044122]\nOperational Decision Manager V8.9.1 Mod Pack [http://www-01.ibm.com/support/docview.wss?uid=swg24044253]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 6, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q013", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "ODM 8.8.1\n In Rule Designer, suppose a new rule project is added to an\n existing decision service with dependancies, this rule project\n is published to decision center first and then the decision\n service is synced to decision center. This rule project has to\n stay connected to Decision Center while synchronizing the\n decision service.\n If you disconnect the rule project after publish it to DC (keep\n connection entries), there will be various errors afterwards in\n Decision Center while extracting project state, and pulling the\n projects from DC into a new workspace.\n To reproduce with loan validation service sample:\n 1. import Loan Validation Service sample to workspace A, and\n publish \"Loan Validation Service\" to DC.\n 2. open a new workspace B, import Loan Validation Service\n sample, and add a new rule project \"Loan Test\" with the\n following dependancies:\n Loan Validation Service > Loan Test > Loan Validation Base\n 3. right click \"Loan Test\" and publish this rule project to DC,\n it publishes to main branch by default.\n 4. right click \"Loan Test\" > Decision Center > Disconnect and\n select keep connection entries.\n 5. create a new branch based on main in business console for\n Loan Validation Service \"newBranch\"\n 6. in Rule Designer, right click \"Loan Validation Service\" and\n synchronize it to newBranch, publish the changes in Sync view.\n 7. login to DCEC, select Loan Validation Service > newBranch,\n Export Current Project State will throw the following error. (\n attached)\n 8. create a new workspace C, and create rule project from\n Decision Center from Loan Validation Service, the rule projects\n are created in the workspace with empty folders. Errors in\n workspace log:\n !MESSAGE Caught exception processing: class ilog.rules.\n synchronization.endpoint.remote.server.CollectChangesHandler\n !STACK 0\n ilog.rules.synchronization.SyncException: Caught exception\n processing: class ilog.rules.synchronization.endpoint.remote.\n server.CollectChangesHandler\n at ilog.rules.synchronization.subscriber.\n DataAccessSignatureVariantTree.collectChanges(\n DataAccessSignatureVariantTree.java:68)\n at ilog.rules.synchronization.subscriber.\n SignatureVariantTree.refresh(SignatureVariantTree.java:139)\n at ilog.rules.synchronization.subscriber.Subscriber.\n refresh(Subscriber.java:349)\n at ilog.rules.synchronization.subscriber.Subscriber.\n refresh(Subscriber.java:305)\n at ilog.rules.synchronization.subscriber.service.\n SynchronizationService.collectSyncInfos(SynchronizationService.\n java:126)\n at ilog.rules.synchronization.eclipseui.subscriber.\n EclipseWrapperSubscriber.configureFromRuleTeamServer(\n EclipseWrapperSubscriber.java:1197)\n at ilog.rules.synchronization.eclipseui.wizards.\n NewRuleProjectFromRTServerWizard$ConfigureJob.runInWorkspace(\n NewRuleProjectFromRTServerWizard.java:145)\n at org.eclipse.core.internal.resources.\n InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)\n at org.eclipse.core.internal.jobs.Worker.run(Worker.\n java:54)\n Caused by: ilog.rules.model.dataaccess.DataAccessException:\n Caught exception processing: class ilog.rules.synchronization.\n endpoint.remote.server.CollectChangesHandler\n at ilog.rules.synchronization.endpoint.remote.client.\n RemoteRuleModelDataAccess.collectChanges(\n RemoteRuleModelDataAccess.java:373)\n at ilog.rules.synchronization.subscriber.\n DataAccessSignatureVariantTree.collectChanges(\n DataAccessSignatureVariantTree.java:66)\n Note that there will be no errors in step 7 and 8 if the new\n rule project is not disconnected from DC in step 4.\n Connection is not required for classic rule project with\n dependancies in similar scenario.", "logical_doc_id": 7, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q013", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "stay connected during sync. or restore the connection for the\n dependent projects.", "logical_doc_id": 7, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q013", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "We got a NullPointerException during synchronization with newly\n added dependent projects because If the sync branch is null\n this causes an NPE later on in ProjectBranch\n This can happen if the project was disconnected from DC in RD.", "logical_doc_id": 7, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q013", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The code is fixed\n\nTEMPORARY FIX", "logical_doc_id": 7, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q013", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n RS02629\nREPORTED COMPONENT NAME\n WS DECISION CTR\nREPORTED COMPONENT ID\n 5725B6900\nREPORTED RELEASE\n 881\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2017-01-31\nCLOSED DATE\n 2017-02-17\nLAST MODIFIED DATE\n 2017-02-17\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\n999", "logical_doc_id": 7, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q013", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WS DECISION CTR\nFIXED COMPONENT ID\n 5725B6900", "logical_doc_id": 7, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q013", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R881 PSY\n UP", "logical_doc_id": 7, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q013", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Operational Decison Manager z/OS 8.8.1.2 Fix Pack [http://www-01.ibm.com/support/docview.wss?uid=swg24043654]\nOperational Decision Manager V8.8.1.2 Fix Pack [http://www-01.ibm.com/support/docview.wss?uid=swg24043530]\nOperational Decision Manager V8.9.0.1 Fix Pack [http://www-01.ibm.com/support/docview.wss?uid=swg24043671]\nOperational Decison Manager z/OS 8.9.0.1 Fix Pack [http://www-01.ibm.com/support/docview.wss?uid=swg24043670]\nOperational Decision Manager V8.9.1 Download Document [http://www-01.ibm.com/support/docview.wss?uid=swg24044122]\nOperational Decision Manager V8.9.1 Mod Pack [http://www-01.ibm.com/support/docview.wss?uid=swg24044253]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 7, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q013", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "For a new rule project that is added to an existing decision\n service with dependancies, it has to stay connected to Decision\n Center while synchronizing the decision service.\n Disconnecting the rule project after publish it to Decision\n Center (keep connection entries) will introduce various errors\n afterwards in Decision Center while extracting project state,\n and pulling the projects from Decision Center into a new\n workspace.", "logical_doc_id": 8, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q013", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Make sure the rule project is connected to Decision Center\n during the synchronization.", "logical_doc_id": 8, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q013", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "We have a NullPointerException during synchronization with\n newly added dependent projects\n because if the sync branch is null this causes an NPE later on\n in ProjectBranch\n This can happen if the project was disconnected from Decision\n Center in RuleDesigner\n We need to retrieve the sync from the server project infos\n based on the main project.", "logical_doc_id": 8, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q013", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The code is fixed\n\nTEMPORARY FIX", "logical_doc_id": 8, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q013", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n RS02491\nREPORTED COMPONENT NAME\n WS DECISION CTR\nREPORTED COMPONENT ID\n 5725B6900\nREPORTED RELEASE\n 881\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-09-06\nCLOSED DATE\n 2017-02-16\nLAST MODIFIED DATE\n 2017-02-16\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\n999", "logical_doc_id": 8, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q013", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WS DECISION CTR\nFIXED COMPONENT ID\n 5725B6900", "logical_doc_id": 8, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q013", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R881 PSY\n UP", "logical_doc_id": 8, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q014", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What is the Java\u2122 SDK upgrade policy for the IBM\u00ae WebSphere\u00ae Application Server?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q014", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Updating to the latest compatible Java SDK could help you resolve problems more quickly.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q014", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "The IBM WebSphere Application Server Java SDK can be upgraded to the latest service release for the same Java SDK version.\n\nList of WebSphere Application Server fix packs and the corresponding Java SDK versions [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27005002]\n\nPolicy Summary by WebSphere Application Server release:\n\nWebSphere Application Server V8.0, V8.5, V8.5.5\nStarting with V8.0 and applicable to all subsequent releases and fixpacks, there is one install package that contains updates for both WebSphere Application Server and Java SDK. Applying fixpacks of WebSphere Application Server also upgrades the SDK that is packaged and bundled within the fixpack. Additionally, separate Java SDK fixpacks are also available that contain just the SDK updates which can be applied to upgrade the SDK.\n\nWebSphere Application Server V7.0\nAny V7.0 fix pack can upgrade to the latest Java SDK 1.6.0 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V6.1\nAny V6.1 fix pack can upgrade to the latest Java SDK 1.5.0 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V6.0\nAny V6.0 fix pack can upgrade to the latest Java SDK 1.4.2 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V5.1\nAny V5.1 fix pack can upgrade to the latest Java SDK 1.4.1 and any V5.1.1 can be upgraded to the latest Java SDK 1.4.2 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V5.0\nAny V5.0 fix pack can upgrade to the latest Java SDK 1.3.1 service release packaged for WebSphere Application Server.\n\nDetails of Java SDK Upgrade Policy\n\nWebSphere Application Server leverages the Java SDK as a base component. This results in unique support issues, including:\nMatching Java SDK service releases to Application Server releases and fix packs\nDelivering updates and fixes associated with the Java SDK on any given Application Server release.\n\nIn an effort to resolve customer Java SDK situations as quickly as possible, WebSphere Application Server Support has done a quickest-path-to-resolution analysis, determining the most direct way to collect problem information.\n\nIn some cases, problem resolution might include finding shortcuts to resolve symptoms. One shortcut is an immediate upgrade to a newer compatible Java SDK service release, before gathering detailed problem determination data.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q014", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "There are multiple advantages to performing an immediate Java SDK upgrade as a quicker path to resolution over a full Problem Determination (PD) process:\n 1. There is a continuous stream of fixes going into the Java SDK. Many problems encountered by customers are resolved by these fixes.\n\n2. When a new problem is encountered, applying the latest Java SDK is a quick way to determine if related fixes change the symptoms or correct the problem.\n\n3. Many documented Java SDK fixes have common symptoms. Frequently, limited PD data does not isolate the problem to a single root cause.\n\nThese factors highlight the advantage of applying a newer Java SDK before working through a full PD cycle.\n\nJava SDK and WebSphere Application Server software are updated frequently. To avoid compatibility issues for customers, WebSphere Application Server Support maintains this Java SDK Upgrade Policy.\n\nWebSphere Application Server Support details:\nhttp://www.ibm.com/software/webservers/appserv/support.html [http://www.ibm.com/software/webservers/appserv/support.html]\n\nIdentifying compatibility limitations between WebSphere Application Server releases and Java SDK service releases that have not been tested together reduces risk.\n\nImportant: Using a Java SDK not specifically packaged with WebSphere Application Server and supplied by IBM, or in violation of the Java SDK Upgrade Policy, is not supported by IBM WebSphere Application Server Support for Java SDK problems. RELATED INFORMATION\n Verify Java SDK version shipped with WebSphere fix pack [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27005002]\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK\n\nSCA; Feature Pack for SCA; SCA Feature Pack Fix Pack 1.0.1.19 DOWNLOADABLE FILES", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q014", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM WebSphere Application Server V7 Feature Pack for Service Component Architecture (SCA) Fix Pack 19 for distributed platforms, also known as SCA Feature Pack Fix Pack 1.0.1.19", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q014", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "SCA Feature Pack Fix Pack 1.0.1.19 is now available for your download through FTP and DD links by going to the Download Package section of this document. The ZIP files in the download package section below can be used for setting up local repository to install SCA Fix Pack 1.0.1.19 using IBM Installation Manager.\n\nWebSphere Application Server feature packs are a mechanism for providing major new application server function between product releases. By delivering new functions and support for industry standards between product releases, you can more quickly explore and implement new technologies within your business applications in today's rapidly changing business environments.\n\nIBM WebSphere Application Server V7 Feature Pack for SCA [http://www.ibm.com/software/webservers/appserv/was/featurepacks/sca/] delivers critical technology that enables adoption of key Service-Oriented Architecture (SOA) principles. As part of the larger SOA Foundation, which straddles all of IBM software brands, this offering delivers an integrated, open implementation of Service Component Architecture (SCA), a technology specified by IBM and other industry leaders through the Open SOA Collaboration (OSOA). For More details, visit the Information Center for SCA Feature Pack. [http://publib.boulder.ibm.com/infocenter/wasinfo/fep/index.jsp?topic=/com.ibm.websphere.soafep.multiplatform.doc/info/ae/ae/csca_overview.html]\n\nDownload Package\n\nDownload Language Download options SCA V1.0.1.19 local repository US English FTP [ftp://public.dhe.ibm.com/software/websphere/downloads/sca/service/1.0/fixpacks/sca.1.0.1.19.fp.zip] WAS 7.0 local import repository US English FTP [ftp://public.dhe.ibm.com/software/websphere/downloads/was/import/was.7.0.import.zip] SCA V1.0 local import repository US English FTP [ftp://public.dhe.ibm.com/software/websphere/downloads/sca/import/sca.1.0.import.zip]\nKnown Issues * OSGi Application Blueprint Service registrations fail. For details visit this Link [http://www-01.ibm.com/support/docview.wss?uid=swg24033832].\n\nChange History * Nov 2, 2015: Published for SCA Fix Pack 19 (1.0.1.19)\n\nPREREQUISITES\n\n1. If you are going to use IBM Installation Manager to import an existing WebSphere Application Server Version 7.0 installation that contains Version 1.0.0.x of the Feature Pack for SCA and then update it to Version 1.0.1.0, first use the Update Installer to remove any fixes that have been applied to the 1.0.0.x level using the Update Installer.\n\n2. Install WebSphere Application Server Version 7.0.0.7 or later.\n\n3. Install IBM Installation Manager. You can download and unpack a compressed file containing the IBM Installation Manager appropriate for your operating system from the IBM Installation Manager Web site [http://www.ibm.com/support/docview.wss?uid=swg24023498]. You can then install IBM Installation Manager on your local system and use it to import WebSphere Application Server Version 7.0 as well as to install the feature pack from the Web-based repositories.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q014", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "4. If you are using local repository for your installation, IBM Installation Manager must point to SCA local import repository in order to apply any future maintenance. It is available for download from the Download package section of this document.\n\n5. The operating system requirements for a feature pack are the same as for the application server installation. However, you need to ensure that you have enough free disk space to install the feature pack onto the application server installation.\n\nURL LANGUAGE SIZE(Bytes) Detailed System Requirements [http://www.ibm.com/support/docview.wss?uid=swg27006921] US English 100 IBM Installation Manager [http://www.ibm.com/support/docview.wss?uid=swg24023498] US English 100\nINSTALLATION INSTRUCTIONS\nPerform the following tasks to install Feature Pack for SCA Version 1.0.1.19 on WebSphere Application Server Version 7.0.0.7 or later:\n\n1. Install WebSphere Application Server V7.0.\n\n2. Install WebSphere Application Server Fix Pack 7.0.0.7 [http://www.ibm.com/support/docview.wss?uid=swg24024582] or later using the Update Installer [http://www.ibm.com/support/docview.wss?uid=swg24020212].\n\n3. Install IBM Installation Manager. You can download and unpack a compressed file containing the IBM Installation Manager appropriate for your operating system from the IBM Installation Manager Web site [http://www.ibm.com/support/docview.wss?uid=swg24023498]. Start IBM Installation Manager.\n\n4. Import WebSphere Application Server into Installation Manager. Make sure to stop all servers and applications on the WebSphere Application Server installation that is being imported.\n\n5. Install Feature Pack for SCA Version 1.0.1 using IBM Installation Manager. This can be done by using either Web-based Repository or Local Repository. Whenever possible, you should use the remote Web-based repositories so that you are accessing the most up-to-date WebSphere Application Server base-product import and feature pack installation files. The feature-pack version of Installation Manager is preconfigured to use both the local repositories (if they are set up) and the remote repositories.\n\n6. Install SCA Fix Pack 1.0.1.19 using Update option on IBM Installation Manager main page. This can also be done by using either Web-based Repository or Local Repository.\n\nFor detailed instructions on installing the feature pack on distributed operating systems using the GUI as well as instructions on using remote Web-based repositories and local repositories, you can visit Installing the feature pack on distributed operating systems using the GUI [http://publib.boulder.ibm.com/infocenter/wasinfo/fep/index.jsp?topic=/com.ibm.websphere.installation.soafepnd.doc/info/ae/ae/tins_installfp.html] Link.\n\nRelated Links\nDownload location for WebSphere Application Server Fix Pack 7.0.0.7 [http://www.ibm.com/support/docview.wss?uid=swg24024582]\nDownload location for IBM Installation Manager [http://www.ibm.com/support/docview.wss?uid=swg24023498]\nDownload location for IBM Update Installer 7.0 for WebSphere [http://www.ibm.com/support/docview.wss?uid=swg24020212]", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q014", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Installing the SDO feature\nThe Feature Pack for SCA Version 1.0.1.0 and later has an optional feature--the Service Data Objects (SDO) feature. You can use IBM Installation Manager to install this feature.\n\nBefore you can install the SDO feature, you must have the Feature Pack for SCA Version 1.0.1.0 or later and the Feature Pack for XML [http://www.ibm.com/software/webservers/appserv/was/featurepacks/xml/] installed on your system. Make sure that your Installation Manager preferences are pointing to the appropriate Web-based or local repositories containing the Feature Pack for SCA Version 1.0.1.0 or later product.\nPerform this procedure to use IBM Installation Manager to install SDO feature: 1. Stop all servers and applications on the WebSphere Application Server installation that is being modified.\n\n2. Start IBM Installation Manager.\n\n3. Click Modify.\n\n4. Select the package group to modify.\n\n5. Click Next. Note: If you are prompted to authenticate, use the IBM ID and password that you registered with on the program Web site.\n\n6. Expand IBM WebSphere Application Server V7 Feature Pack for Service Component Architecture (SCA).\n\n7. Check the Service Data Objects checkbox to install the SDO feature. Note: This feature is optional, but it is selected by default. If you leave the SDO feature selected, you are required to install IBM WebSphere Application Server Version 7.0 Feature Pack for XML if it is not already installed.\n\nIf you continue the installation with the SDO feature selected and the Feature Pack for XML is not installed, you will receive an error message. If you install the SDO feature, you must use the manageProfiles command or the Profile Management Tool to augment an existing profile or create a new profile when this modification is finished to enable the functionality provided by the feature.\n\nFor details on problems fixed in Fix Pack 17, refer to the Fix list for SCA Feature Pack 1.0.1 [http://www.ibm.com/support/docview.wss?uid=swg27017704]document.\n\nURL LANGUAGE SIZE(Bytes) Fix List for SCA Feature Pack 1.0.1 [http://www.ibm.com/support/docview.wss?uid=swg27017704] US English 100\n\nTECHNICAL SUPPORT\n Contact 1-800-IBM-SERV (U.S. only) or visit the WebSphere Application Server Support site [http://www.ibm.com/software/webservers/appserv/was/support/].\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server AIX, HP-UX, Linux, Solaris, Windows 7.0", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q014", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do we install maintenance for the embedded WebSphere Application Server and the IBM HTTP Server provided by IBM Tivoli Monitoring V6.2.3?", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q014", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "IBM Tivoli Monitoring (ITM) provides embedded WebSphere Application Server (eWAS) and IBM HTTP Server (IHS) for use with Tivoli Enterprise Portal Sever (TEPS). For maintenance purposes it may be necessary to install fix packs and/or interim fixes for eWAS and IHS.\nYou can use this procedure to install fix packs and interim fixes for a given eWAS and IHS version, but not to upgrade to a new eWAS or IHS version. For example, you can use it to install eWAS 7.0.0.43 on top of eWAS 7.0.0.29, but you cannot use it to install eWAS version 8.0 on top of eWAS version 7.0.\nThe following table shows the different levels of eWAS and IHS that are provided by 6.2.3:\n\nITM version eWAS version IHS version 6.23.05.00 7.0.0.29 7.0.0.00 6.23.03.00 - 6.23.04.00 7.0.0.25 7.0.0.00 6.23.01.00 - 6.23.02.00 7.0.0.19 7.0.0.00 6.23.00.00 7.0.0.15 7.0.0.00", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q014", "section_id": 0, "heading": "ANSWER", "parent": null, "text": "Follow these steps to install a new eWAS fix pack into your ITM environment:\n\nStep\n\n1. Back up your ITM environment.\nBack up your ITM environment using your local procedures.\n\nStep\n\n2. Download the maintenance installation scripts.\nDownload the appropriate eWAS/IHS maintenance installation script to the system where your TEPS resides.\nUnix/Linux: Download ewasihsv7update.sh attached below. Ensure that the script has execute permission after it has been downloaded.\nls -l ./ewasihsv7update.sh\nchmod a+rx ./ewasihsv7update.sh\nWindows: Download ewasihsv7update.cmd attached below.\n\nStep", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q014", "section_id": 0, "heading": "ANSWER", "parent": null, "text": "3. Generate the list of files that need to be downloaded.\nRun ewasihsv7update.sh or ewasihsv7update.cmd to generate the list of files that need to be downloaded and to create the temporary directory to hold them.\nWhen the prompt beginning with \"Have all required files been downloaded to\" is displayed,\nrespond with n to exit the script so that you can download the required files.\n\nThe usage information for the command follows:\nUnix:\n ewasihsv7update.sh [-h candle_directory] [-w working_directory] [-u updateinstaller directory]\nh Fully qualified path of the ITM installation directory.\nw Fully qualified path of the temporary working directory for file downloads.\nu Fully qualified path of the UpdateInstaller installation directory.\n If ewasihsv7update.sh was downloaded to CANDLEHOME/bin/, then the -h option is not needed.\n The working directory default value is: /tmp/ewasihsv7. You can specify a different location using the -w option.\n The -u option should only be used when installation of the UpdateInstaller to the documented default directory is not permitted. * AIX Default Location:\n /usr/IBM/WebSphere/UpdateInstaller Linux Default Location:\n /opt/IBM/WebSphere/UpdateInstaller\nWindows:\n ewasihsv7update.cmd [-h candle_directory] [-w working_directory] [-u updateinstaller directory]\nh Fully qualified path of the ITM installation directory.\nw Fully qualified path of the temporary working directory for file downloads.\nu Fully qualified path of the UpdateInstaller installation directory.\n The ITM installation directory default value is the %CANDLE_HOME% value retrieved from the shell environment. Normally the -h option is not needed.\n The working directory default value is: %TEMP%\\ewasihsv7. You can specify a different location using the -w option.\n The -u option should only be used when installation of the UpdateInstaller to the documented default directory is not permitted. * Windows Default Location:\n \"C:\\Program Files\\IBM\\WebSphere\\UpdateInstaller\"\n\nStep 4: Download the files listed in the output from\n\nstep 3 between the two delimiter lines starting with:\n<><><><><><><><><><>\nThere are a number of ways to download the files:", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q014", "section_id": 0, "heading": "ANSWER", "parent": null, "text": "1. If a browser is available on the TEPS system: * For each file listed between the two delimiter lines in the output from step 3; * Copy and paste the full line, one at a time, into the browser address bar and then hit enter.\nSave the file to the working directory displayed after the second delimiter line in the output from step\n\n3.\n\n2. If the wget utility is available, in a command prompt on the TEPS system: * Change directory to the working directory displayed after the second delimiter line in the output from step\n\n3.\nFor each file listed between the two delimiter lines in the output from step 3; * Enter the wget command followed by the copy and paste of the full line, and then hit enter.\n\n3. If the ftp utility is available, in a command prompt on the TEPS system: * Change directory to the working directory displayed after the second delimiter line in the output from step\n\n3.\nRun the ftp command and connect to public.dhe.ibm.com as anonymous.\nFor each file listed between the two delimiter lines in the output from step 3; * Change the remote directory to parent directory of the file (starting with /software/websphere/appserv/support)\nGet the file.\n\n4. Use any other method available to you to download the files.\n\nStep\n\n5. Install the UpdateInstaller and eWAS and IHS maintenance\nRun ewasihsv7update.sh or ewasihsv7update.cmd again\nWhen the prompt starting with \"Have all required files been downloaded to\" is displayed,\nrespond with y to allow the script to continue and perform the UpdateInstaller and maintenance installation actions.\n\nStep\n\n6. Cleanup\nRemove the temporary working directory displayed after the second delimiter line in the output from step\n\n3.\n\nStep", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q014", "section_id": 0, "heading": "ANSWER", "parent": null, "text": "7. Verify the update\nRun run the cinfo/kincinfo command with the -i -z options, which should print out the following messages:\n\nOn a UNIX/Linux system,\nwhere $CANDLEHOME is the IBM Tivoli Monitoring installation directory.\n$CANDLEHOME/bin/cinfo -i -z\nwill print the following iu and iw entries depending on the platform:\n\niu IBM HTTP Server\naix536 Version: 07.00.43.00\nPatch: 7.0.0.43-WS-WASIHS-AixPPC32 APARs: IFPI82481\n\niw IBM Tivoli Enterprise Portal Server Extensions\naix536 Version: 07.00.43.00\nPatch: 7.0.0.19-WS-WAS APARs: IFPI79343\nPatch: 7.0.0.0-WS-WASJavaSDK-AixPPC64 APARs: IFPI84269\n\niu IBM HTTP Server\nli6263 Version: 07.00.43.00\nPatch: 7.0.0.43-WS-WASIHS-LinuxX32 APARs: IFPI82481\n\niw IBM Tivoli Enterprise Portal Server Extensions\nli6263 Version: 07.00.43.00\nPatch: 7.0.0.19-WS-WAS APARs: IFPI79343\nPatch: 7.0.0.0-WS-WASJavaSDK-LinuxX32 APARs: IFPI84269\n\niu IBM HTTP Server\nls3266 Version: 07.00.43.00\nPatch: 7.0.0.43-WS-WASIHS-LinuxS390 APARs: IFPI82481\n\niw IBM Tivoli Enterprise Portal Server Extensions\nls3266 Version: 07.00.43.00\nPatch: 7.0.0.19-WS-WAS APARs: IFPI79343\nPatch: 7.0.0.0-WS-WASJavaSDK-LinuxS39064 APARs: IFPI84269\n\nOn a Windows system.\nkincinfo -i -z\nwill print the following IU and IW entries:\n\nIU TEPS App Support/IBM HTTP Server\nWINNT Version: 07.00.43.00 Build: d4029a\nPatch: 7.0.0.0-WS-WASJavaSDK-WinX32 APARs: IFPI84269\nPatch: 7.0.0.43-WS-WASIHS-WinX32 APARs: IFPI82481\n\nIW TEPS App Support/Tivoli Enterprise Portal Server Extensions\nWINNT Version: 07.00.43.00 Build: d4029a\nPatch: 7.0.0.0-WS-WASJavaSDK-WinX32 APARs: IFPI84269\nPatch: 7.0.0.19-WS-WAS APARs: IFPI79343\n\nKnown Issues / Workarounds\nNone.\nAttachments:\newasihsv7update.sh [/support/docview.wss?uid=swg21633720&aid=2]ewasihsv7update.sh [/support/docview.wss?uid=swg21633720&aid=1] ewasihsv7update.cmd [/support/docview.wss?uid=swg21633720&aid=4]ewasihsv7update.cmd [/support/docview.wss?uid=swg21633720&aid=3]\n\nwste_webcast; WSTE; Support Technical Exchange; education; presentation; webcast; STEwebcastDocument; Install Manager questions to install ; uninstall ; modify ; update. WEBCAST", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q014", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Ask the Experts discussion about WebSphere Application Server installation/uninstall/update/modify using Install Manager on 12 December 2013.\nThis session covers install / uninstall / update / modify operations using Installation Manager on WebSphere Application Server V8.X This also covers any questions related to Install /Uninstall or applying fixpacks using Update Installer in v7.x", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q014", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Ask the Experts sessions are conducted in a question and answer format.\n\nThe table below provides a time index (minutes:seconds) to the recording and describes the questions or topics discussed.\nYou can to fast forward to any question using the time index. A table containing the panel of experts is also included.\n\nTo play or download the audio of this Ask the Experts session, see the Audio Section of this document (audio not available until after the webcast).\n\nSee the Related Information Section of this document for a list of documents referenced during the presentation.\n\nAsk the Experts session\n12 December 2013 - 11:00 a.m. - 12:00 p.m. EST", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q014", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Time Questions asked 00:00 General introduction 02:40 Technical introduction 03:38 How can I use command line options to find what is installed and what offerings are available in the repository? 06:05 What option can I use to uninstall ifix and fixpack? 07:43 IMShared directory is using a lot of space, is there an option to delete files from this directory? 11:27 Is it possible to change AppData agent directory from default after WebSphere Application Server and other offerings are installed? 15:24 What options do I have to install Liberty 8.5.5? 17:00 Open lines for live question and answer period 17:03 On a non-administrator install, does it have to be the user_home? Can it be directed to a shared (NFS) space? 17:40 What is the difference between WAS installation through IM and Silent mode installation? 19:21 How to import license from RAD 7.0 to 8.5.5 (trial version)? 19:51 Can you please give an overview of using IM to install ifix? 20:38 I have WAS ND 8.5.5 32-bit installed on a 32-bit linux server, and I have a new linux 64bit server that we want only the 64bit 8.5.5 WAS, and use the DMGR on the 32-bit server, how do we do this? 22:14 Why is IBM only providing Installation of WebSphere Application Server through Installation Mananger? 23:01 When we go for Ifix and when we go for fixpack, what is basic difference between those? 23:50 Can you pleasee give information about what is the use of Liberty profile and its advantages? 24:57 What do you recommend if there is a need to duplicate the WebSphere environment? 26:54 What are the basic pre-req checks for installation of Installation Manager? 28:19 Do you have a link for how to federate the 64-bit WAS ND APPSERVER to 32-bit DMGR, instructions/step (jython scripting) so it can be automated? 29:20 With WebSphere products changing the method of installation, is there a white paper, or recommended practices, for setting up a central repository? 30:33 Is there any way make a WAS back-up through Installation Manager? 30:52 Do we have to uninstall previous ifix before installing latest fix pack? 32:09 We are planning to migrate from WAS 6.1 to WAS8.5.5, can I install 8.5.5 on top of the existing 6.1 profile?", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q014", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Or does it have to be a fresh installation? 33:10 I have an NFS share on 3 servers and IIM is installed there. Can I utilize IIM to install/uninstall with 2 different users without any issues on all 3 servers? 34:44 Is there a document for migrating WebSphere 7 to WAS 8.7 entire cell, say node-by-node? 35:11 What provisions does WebSphere Application Server provide to prevent denial of service attacks? 35:40 If we have 32-bit 8.5.5 DMGR and 1 APPSRVR 32-bit 8.5.5 and a 2nd APPSRVR 64-bit 8.5.5, does the DMGR have to be updated first or can we update the APPServers first? That is, does the order matter for fixes? 36:58 Is it a good idea to create any dependency on the dmgr for runtime? For example, Adobe Life Cycle installed on top of WAS uses some cache mechanism called gds, gemfire, etc. 37:42 I noticed on IM with 8.5 that when you choose to install the updates, it always goes through your IBM PA account to get the updates and the latest. But with Maximo application for instance, you only want to go to 8.5.0.1 for instance, so the only way I found is run the update pointing to the repository for fix 1, and choose update and keep clicking cancel to look online to continue and install the fix 1. Is this the only way to install a fix on V8 or V8.5? 39:40 When migrating WAS from 6.1 to 8.5, do you guys recommend using the migration tool or create configurations using scripts? 40:44 To upgrade websphere from 6.1 to 8.5, What path do you suggest: fresh install or migration proces?. If you suggest migration process where can I get the documentation? 42:34 To get to WAS 8.0 from WAS 8.1, is this a migration process only? 42:57 What is the latest fix pack available on top of 8.5.5.0 base (and location to down load from Passport Advantage)? 43:37 Is there a fixed release scheduled for FixPacks? I hear that it's every 3 months or so. 44:24 If I have 1000 servers to apply FP, whats the recommended method to apply fixes to large number of servers in minimum time; any tools available? 47:01 I have IIM, WASND, WAS installed and configured per application's requirement.", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q014", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Now, I want to install another instance of WAS. Does IIM have an option to take the existing WAS as a template so that I can get the configuration also? 47:49 We are planning to upgrade from 6.1 to 8.5.5.0. What's the stable version (already being used by companies)? 48:45 Closing remarks 50:05 End of Call\nPanel of Experts: Jeanette Daly WebSphere Application Server L2 Support Mike Hill WebSphere Application Server L2 Support Vishavpal Shergill WebSphere Application Server L2 Support Vikram Thommandru WebSphere Application Server L2 Support", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q014", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "PRESENTATION\n[http://www.ibm.com/i/v16/icons/weblecture.gif]WSTE-12122013-AskTheExperts-WebSphere_Application_Server_installation_update_uninstall.pdf [/support/docview.wss?uid=swg27040108&aid=2]WSTE-12122013-AskTheExperts-WebSphere_Application_Server_installation_update_uninstall.pdf [/support/docview.wss?uid=swg27040108&aid=1]\n\nGet Adobe Reader [http://www.adobe.com/products/acrobat/readstep2.html] to view PDF\n\nAUDIO\n[http://www.ibm.com/i/v16/icons/aud.gif]To replay the recording of this conference call, click on Download Audio [http://public.dhe.ibm.com/software/websphere/techexchange/December-12-2013-Daly-Hill-Shergill-Thommandru.mp3](audio in MP3 format). Right-click and select Save As to store the file on your local computer for later playback. Remember that you can fast forward to any question using the time index.", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q014", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "WebSphere Support Technical Exchange [http://www.ibm.com/software/websphere/webcast]", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q014", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "admin.passwd; index.html TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Use of Installation Manager (IM) to install IBM HTTP Server (IHS webserver) starts with IHS version 8.0.0.0. Prior to use of IM, the fixpacks for IHS (V7 and V6.x) did not include files expected to be customized such as default static content files like index.html and other HTML, GIF, and ICO files installed by IHS to its /htdocs directory. More importantly the admin.passwd file (that holds the user/passsword for the IHS Admin Service) is usually configured right after install when using the Plugin Configration Tool (PCT).\n\nPrior to use of IM you could not install directly to a fixpack level. You had to install the base GA code (i.e. 7.0.0.0 or 6.1.0.0) and then use the Update Installer to apply fixpacks. IM supports installation directly to a fixpack level therefore all install files included with the base GA code 8.0.0.0 are applied with the fixpack. Any files that should not be overwritten must be listed in a exception list (of non-serviceable files) that the IM installer can reference. This list of non-serviceable files was ommitted or incomplete for IHS V8.0.0.0 and 8.5.0.0 so the install of the first fixpack (regardless of fixpack level) may overwrite files such as admin.passwd and index.html.\n\nThere are two APAR related to the same event:\n.\nPM71612: ADDITIONAL NON-SERVICEABLE FILES ADDED FOR IBM HTTP SERVER.\nhttp://www-01.ibm.com/support/docview.wss?uid=swg1PM71612 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM71612]\n.\nPM63634: IHS CONFIG ADMIN.PASSWD FILE WAS RESET AFTER INSTALLING\nFIXPACK 3 ON WAS 8.0.0.2 or 7.0.0.25 on Windows.\nhttp://www-01.ibm.com/support/docview.wss?uid=swg1PM63634 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM63634]\n\n.", "logical_doc_id": 5, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q014", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "The technote about PM63634: IHS CONFIG ADMIN.PASSWD FILE WAS RESET advises a resolution in reseting the admin.passwd file:\n\nInstallation of IBM HTTP Server 7.0.0.25, 8.0.0.1, 8.0.0.2, 8.0.0.3 will overlay admin.passwd:\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21593118 [http://www-01.ibm.com/support/docview.wss?uid=swg21593118]\n\nThe main impact is that the IHS admin.passwd file gets overwritten which means the IHS Admin User/PW must be reset with the htpasswd utility in the IHS bin directory. Some customers customize the IHS splash page (index.html) or other default pages provided by IHS install so apply of first fixpack can overwrite these files and the customer's customization.\n\nThe list of these non-serviceable files where included in 8.0.0.5 and 8.5.0.1 per the APAR links above so once that fixpack level is applied then any future fixpacks will not overwrite these files. There is no way to avoid the event if GA 8.0.0.0/8.5.0.0 IHS is installed first. The first fixpack applied (of any fixpack) could replace the files.", "logical_doc_id": 6, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q014", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The admin.passwd is a zero byte file after apply of fixpack\nAny content installed under /htdocs by IHS install (default static content files) that have been customized are replaced by their default originals after apply of fixpack", "logical_doc_id": 7, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q014", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Files not marked as non-serviceable files for IM install of fixpacks for IHS per APAR PM71612", "logical_doc_id": 7, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q014", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "WebSphere environments that use IHS v8.x to run the WSAS plugin for Webservers to act as proxy front to WSAS appservers.", "logical_doc_id": 7, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q014", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Support suggests one of three recommendations to avoid the problem:\n\n1. Use IM to install IHS at fixpack 8.0.0.5/8.5.0.1 or higher bypassing the install of 8.0.0.0/8.5.0.0\n\n2. Do not use PCT, configure IHS Admin or use htpasswd (or other customization/config) until after fixpack has been applied.\n\n3. If you have already installed 8.0.0.0 or 8.5.0.0 then before you apply your first IHS fixpack backup these files:\nadmin.passwd\nall content under /htdocs\n\nPRODUCT ALIAS/SYNONYM\n IHS", "logical_doc_id": 7, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q072", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM Integration Bus and WebSphere Message Broker SOAP FLOWS are vulnerable to XML external entity attack.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q072", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-9706 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9706]\nDESCRIPTION: IBM Integration Bus and WebSphere Message Broker SOAP FLOWS are vulnerable to a denial of service attack, caused by an XML External Entity Injection (XXE) error when processing XML data. A remote attacker could exploit this vulnerability to expose highly sensitive information or consume all available memory resources.\nCVSS Base Score: 8.2\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/119580 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119580] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q072", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Integration Bus V10.0 & V9.0\n\nWebSphere Message Broker V8.0", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q072", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Product VRMF APAR Remediation/Fix IBM Integration Bus V10 IT14799 The APAR is available in fix pack 10.0.0.5 http://www-01.ibm.com/support/docview.wss?uid=swg24042299 [http://www-01.ibm.com/support/docview.wss?uid=swg24042299]\n\nIBM Integration Bus V9 IT14799 The APAR is available in fix pack 9.0.0.6 http://www-01.ibm.com/support/docview.wss?uid=swg24042598 [http://www-01.ibm.com/support/docview.wss?uid=swg24042598]\n\nWebSphere Message Broker V8 IT14799 The APAR is available in fix pack 8.0.0.8\n\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24042925 [http://www-01.ibm.com/support/docview.wss?uid=swg24042925]\nFor unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product.\n\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at :\nhttp://www.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006308]", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q072", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q072", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q072", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 10 Feb 2017 - Original version Published\nThe 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\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker AIX, HP-UX, Linux, Solaris, Windows 8.0\nPRODUCT ALIAS/SYNONYM\n WMB IIB", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q072", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "WebSphere Message Broker\u3067\u4f7f\u7528\u3055\u308c\u308bIBM\u00ae\u30e9\u30f3\u30bf\u30a4\u30e0\u74b0\u5883Java\u2122Technology Edition 6.0.16.26\uff08\u304a\u3088\u3073\u305d\u308c\u4ee5\u524d\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\uff09\u3001WebSphere Message Broker\u304a\u3088\u3073IBM Integration Bus\u3067\u4f7f\u7528\u3055\u308c\u308bIBM\u00aeRuntime Environment Java\u2122Technology Edition 7.0.9.40\uff08\u304a\u3088\u3073\u305d\u308c\u4ee5\u524d\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\uff09\u3001\u304a\u3088\u3073IBM Integration Bus\u3067\u4f7f\u7528\u3055\u308c\u308bIBM\u00ae\u30e9\u30f3\u30bf\u30a4\u30e0\u74b0\u5883Java\u2122Technology Edition 7.1.3.40\uff08\u304a\u3088\u3073\u305d\u308c\u4ee5\u524d\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\uff09\u306b\u8907\u6570\u306e\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30fc\u8106\u5f31\u6027\u304c\u5b58\u5728\u3057\u307e\u3059\u3002\u3053\u308c\u3089\u306e\u554f\u984c\u306f\u30012016\u5e747\u6708\u306bIBM Java SDK\u30a2\u30c3\u30d7\u30c7\u30fc\u30c8\u306e\u4e00\u90e8\u3068\u3057\u3066\u516c\u958b\u3055\u308c\u307e\u3057\u305f\u3002", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q072", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "\u6700\u65b0\u306e\u60c5\u5831\u306b\u3064\u3044\u3066\u306f\u3001\u4e0b\u8a18URL\u306e\u6587\u66f8\uff08\u82f1\u8a9e\uff09\u3092\u3054\u53c2\u7167\u304f\u3060\u3055\u3044\u3002\nSecurity Bulletin: Multiple vulnerabilities in IBM Java Runtime affect WebSphere Message Broker and IBM Integration Bus (CVE-2016-3485)\nhttp://www.ibm.com/support/docview.wss?uid=swg21994213 [http://www.ibm.com/support/docview.wss?uid=swg21994213]\n\nCVEID: CVE-2016-3485 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3485]\n\u8106\u5f31\u6027\u306e\u8a73\u7d30:\n\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30b3\u30f3\u30dd\u30fc\u30cd\u30f3\u30c8\u306b\u95a2\u9023\u3059\u308b Oracle Java SE \u304a\u3088\u3073 Java SE Embedded \u306e\u7279\u5b9a\u3055\u308c\u3066\u3044\u306a\u3044\u8106\u5f31\u6027\u306f\u3001\u6a5f\u5bc6\u6027\u3078\u306e\u5f71\u97ff\u306f\u3042\u308a\u307e\u305b\u3093\u3002\u6574\u5408\u6027\u3078\u306e\u5f71\u97ff\u306f\u4f4e\u304f\u3001\u53ef\u7528\u6027\u3078\u306e\u5f71\u97ff\u306f\u3042\u308a\u307e\u305b\u3093\u3002\nCVSS Base Score: 2.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/115273 [https://exchange.xforce.ibmcloud.com/vulnerabilities/115273] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N) AFFECTED PRODUCTS AND VERSIONS\n IBM Integration Bus V10, V9\n\nWebSphere Message Broker V8", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q072", "section_id": 2, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Product VRMF APAR Remediation/Fix IBM Integration Bus V10 IT16743 APAR \u306f\u3001Fix pack 10.0.0.7 \u306b\u542b\u307e\u308c\u3066\u3044\u307e\u3059\u3002\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24043068 [https://www-304.ibm.com/support/docview.wss?uid=swg24043068] IBM Integration Bus V9 IT16743 APAR\u306f\u3001Fix pack 9.0.0.7 \u306b\u542b\u307e\u308c\u3066\u3044\u307e\u3059\u3002\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043227 [http://www-01.ibm.com/support/docview.wss?uid=swg24043227] WebSphere Message Broker V8 IT16743 Interim fix \u306f\u3001\u5168\u3066\u306e\u30d7\u30e9\u30c3\u30c8\u30d5\u30a9\u30fc\u30e0\u306b\u5bfe\u3057\u3066 IBM Fix Central \u304b\u3089\u5165\u624b\u3067\u304d\u307e\u3059\u3002\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT16743 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=%20IT16743]\n\n8.0.0.7 \u3088\u308a\u524d\u306e Fix pack \u3092\u3054\u4f7f\u7528\u3055\u308c\u3066\u3044\u3066\u3001IT03599\u304c\u9069\u7528\u3055\u308c\u3066\u3044\u306a\u3044\u5834\u5408\u306f\u3001Fix pack 8.0.0.7 \u4ee5\u4e0a\u306b\u30a2\u30c3\u30d7\u30b0\u30ec\u30fc\u30c9\u3059\u308b\u304b\u3001IBM\u30b5\u30dd\u30fc\u30c8\u3078 IT16735 \u3092\u4f9d\u983c\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002\n\nAPAR IT16743 \u306f\u3001Fix pack 8.0.0.9 \u306b\u542b\u307e\u308c\u3066\u3044\u307e\u3059\u3002\nFor unsupported versions of the product IBM recommends upgrading to a fixed, supported version/release/platform of the product. WORKAROUNDS AND MITIGATIONS\n\u56de\u907f\u7b56\u306f\u3054\u3056\u3044\u307e\u305b\u3093\u3002", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q072", "section_id": 3, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q072", "section_id": 4, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]\nIBM Java SDK Security Bulletin [http://www.ibm.com/support/docview.wss?uid=swg21986642]", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q072", "section_id": 5, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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\u516c\u958b\u6e08\u307f\u306e\u30d5\u30a3\u30c3\u30af\u30b9\u30d1\u30c3\u30af\u306b\u3064\u3044\u3066\u306f\u3001\u4ee5\u4e0b\u306e\u30b5\u30a4\u30c8\u3088\u308a\u3054\u5229\u7528\u3044\u305f\u3060\u3051\u307e\u3059\u3002\nRecommended fixes for IBM Integration Bus and WebSphere Message Broker\nhttp://www.ibm.com/support/docview.wss?uid=swg27006041 [http://www.ibm.com/support/docview.wss?uid=swg27006041]\n\n\u30d5\u30a3\u30c3\u30af\u30b9\u30fb\u30d1\u30c3\u30af\u306e\u516c\u958b\u4e88\u5b9a\u306b\u3064\u3044\u3066\u306f\u3001\u4ee5\u4e0b\u306e\u30b5\u30a4\u30c8\u3088\u308a\u3054\u78ba\u8a8d\u3044\u305f\u3060\u3051\u307e\u3059\u3002\nIntegration Bus and WebSphere Message Broker planned maintenance release dates\nhttp://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308]\nThe 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\u95a2\u9023\u60c5\u5831\n An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21994213]\n\n\u30af\u30ed\u30b9\u30ea\u30d5\u30a1\u30ec\u30f3\u30b9\u60c5\u5831 \u533a\u5206 \u88fd\u54c1 \u30b3\u30f3\u30dd\u30fc\u30cd\u30f3\u30c8 \u30d7\u30e9\u30c3\u30c8\u30d5\u30a9\u30fc\u30e0 \u30d0\u30fc\u30b8\u30e7\u30f3 \u30a8\u30c7\u30a3\u30b7\u30e7\u30f3 Business Integration WebSphere Message Broker 8.0", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q072", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "WebSphere Message Broker is shipped as a component of WebSphere Remote Server. Information about multiple security vulnerabilities affecting WebSphere Message Broker has been published in a security bulletin.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q072", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "For vulnerabilities details, see the security bulletin Multiple vulnerabilities in IBM Java Runtime affect IBM Integration Bus and WebSphere Message Broker [http://www.ibm.com/support/docview.wss?uid=swg21697107].", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q072", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Principal Product and Version(s) Affected Supporting Product and Version WebSphere Remote Server\nV7.1, 7.1.1, 7.1.2, 8.5 WebSphere Message Broker\nV7.0, 8.0 GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q072", "section_id": 3, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q072", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] CHANGE HISTORY\n 7 April 2015: Original Version Published\nThe 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.", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q072", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition that is shipped with IBM Cloud Orchestrator. These issues were disclosed as part of the IBM Java SDK updates in October 2016. These may affect some configurations of IBM WebSphere Application Server, IBM Business Process Manager, and IBM Tivoli System Automation Application Manager, which are shipped with IBM Cloud Orchestrator and Cloud Orchestrator Enterprise.\nAdditionally, it affects Jazz for Service Management and IBM Tivoli Monitoring, which are shipped with Cloud Orchestrator Enterprise.", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q072", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-5573 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5573]\nDESCRIPTION: An unspecified vulnerability related to the VM component has high confidentiality impact, high integrity impact, and high availability impact.\nCVSS Base Score: 8.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118070 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118070] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H)\n\nCVEID: CVE-2016-5597 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5597]\nDESCRIPTION: An unspecified vulnerability related to the Networking component could allow a remote attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118071 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118071] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N)", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q072", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Principal Product and Version(s)\nAffected Supporting Product and Version\n* WebSphere Application Server V8.5.5 through V8.5.5.7\nIBM Business Process Manager Standard V8.5.5 - V8.5.6.2\nIBM Tivoli System Automation Application Manager 4.1\n* WebSphere Application Server V8.5.0.1 through V8.5.5.7\nIBM Business Process Manager Standard V8.5.0.1\nIBM Tivoli System Automation Application Manager 4.1\n* IBM WebSphere Application Server V8.0, V8.0.11\nIBM Business Process Manager Standard V8.5.0.1\n* WebSphere Application Server V8.5.5 through V8.5.5.7\nIBM Business Process Manager Standard V8.5.5 - V8.5.6.2\nIBM Tivoli System Automation Application Manager 4.1\nIBM Tivoli Monitoring 6.3.0.2\nJazz for Service Management 1.1.0.1\n* WebSphere Application Server V8.5.0.1 through V8.5.5.7\nIBM Business Process Manager Standard V8.5.0.1\nIBM Tivoli System Automation Application Manager 4.1\nIBM Tivoli Monitoring 6.3.0.1\nJazz for Service Management 1.1.0.1\n* IBM WebSphere Application Server V8.0, V8.0.11\nIBM Business Process Manager Standard V8.5.0.1\nIBM Tivoli Monitoring V6.3.0.1\nJazz\u2122 for Service Management V1.1.0.1", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q072", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "These issues were addressed by IBM Cloud Orchestrator and IBM Cloud Orchestrator Enterprise through the bundled products IBM WebSphere Application Server, IBM Business Process Manager, and IBM Tivoli System Automation Application Manager, which are shipped with IBM Cloud Orchestrator and IBM Cloud Orchestrator Enterprise.\nAdditionally, these issues were also addressed by IBM Tivoli Monitoring that is shipped with IBM Cloud Orchestrator Enterprise.\n\nRefer to the following security bulletins for information about fixes for IBM Cloud Orchestrator and Cloud Orchestrator Enterprise:\nProduct\nVRMF\nRemediation/First Fix\n*\nUpgrade to IBM Cloud Orchestrator Fix Pack 3 (2.5.0.3) for 2.5\n* http://www-01.ibm.com/support/docview.wss?uid=swg27045667\n*\n*\nUpgrade to IBM Cloud Orchestrator Fix Pack 4 (2.4.0.4) for 2.4:\n* http://www-01.ibm.com/support/docview.wss?uid=swg27045667\n*\n*\n* IBM Support\n\nRefer to the following security bulletins for vulnerability details and information about fixes addressed by IBM WebSphere Application Server, Tivoli System Automation Application Manager, and Business Process Manager that are shipped with IBM Cloud Orchestrator.\nPrincipal Product and Version(s)\nAffected Supporting Product and Version\nRemediation/First Fix/ Affected Supporting Product Security Bulletin\n*\n* Security Bulletin: Multiple vulnerabilities in IBM\u00ae Java SDK affects WebSphere Application Server October 2016 CPU (CVE-2016-5573, CVE-2016-5597)\n* Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Tivoli System Automation Application Manager (CVE-2016-5597)\n* Security Bulletin: Multiple vulnerabilities in WebSphere Application Server affect IBM Business Process Manager, WebSphere Process Server and WebSphere Lombardi Edition (Java CPU October 2016)\n* Security Bulletin: Security vulnerability has been identified in Jazz Team Server shipped with Jazz Reporting Service (CVE-2016-5597)", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q072", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Refer to the following security bulletins for vulnerability details and information about fixes addressed by IBM WebSphere Application Server, Tivoli System Automation Application Manager, Business Process Manager, and Tivoli Monitoring, which are shipped with IBM Cloud Orchestrator Enterprise Edition:\nPrincipal Product and Version(s)\nAffected Supporting Product and Version\nRemediation/First Fix/ Affected Supporting Product Security Bulletin\n*\nSecurity Bulletin: Multiple vulnerabilities in IBM\u00ae Java SDK affects WebSphere Application Server October 2016 CPU (CVE-2016-5573, CVE-2016-5597)\n* Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Tivoli System Automation Application Manager (CVE-2016-5597)\n* Security Bulletin: Multiple vulnerabilities in WebSphere Application Server affect IBM Business Process Manager, WebSphere Process Server and WebSphere Lombardi Edition (Java CPU October 2016)\n* Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Tivoli Monitoring\n* Security Bulletin: Security vulnerability has been identified in Jazz Team Server shipped with Jazz Reporting Service (CVE-2016-5597)", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q072", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 3, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q072", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]\nIBM Java SDK Security Bulletin with link http://www-01.ibm.com/support/docview.wss?uid=swg21985393 [http://www-01.ibm.com/support/docview.wss?uid=swg21985393]", "logical_doc_id": 3, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q072", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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 Apr 2017: Original version published\nThe 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\nWMB IIB SECURITY BULLETIN", "logical_doc_id": 3, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q072", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Multiple security vulnerabilities exist in the IBM\u00ae Runtime Environment Java\u2122 Technology Edition Version 6 Service Refresh 16 Fix Pack 41 and earlier releases used by WebSphere Message Broker, and the IBM\u00ae Runtime Environment Java\u2122 Technology Edition Version 7 Service Refresh 10 Fix Pack 1 and earlier releases used by WebSphere Message Broker and IBM Integration Bus, and the IBM\u00ae Runtime Environment Java\u2122 Technology Edition Version 7R1 Service Refresh 4 Fix Pack 1 and earlier releases used by IBM Integration Bus. These issues were disclosed as part of the IBM Java SDK updates in April 2017. WebSphere Message Broker and IBM Integration Bus have addressed the applicable CVEs", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q072", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "If you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities, refer to the \u201cIBM Java SDK Security Bulletin\u201d, located in the References section for more information.\n\nCVEID: CVE-2017-3511 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3511]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit JCE component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 7.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/124890 [https://exchange.xforce.ibmcloud.com/vulnerabilities/124890] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H)\n\nCVEID: CVE-2017-1289 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1289]\nDESCRIPTION: IBM SDK, Java Technology Edition is vulnerable XML External Entity Injection (XXE) error when processing XML data. A remote attacker could exploit this vulnerability to expose highly sensitive information or consume memory resources.\nCVSS Base Score: 8.2\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/125150 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125150] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L)\n\nCVEID: CVE-2016-9840 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9840]\nDESCRIPTION: zlib is vulnerable to a denial of service, caused by an out-of-bounds pointer arithmetic in inftrees.c. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/120508 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120508] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L)\n\nCVEID: CVE-2016-9841 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9841]\nDESCRIPTION: zlib is vulnerable to a denial of service, caused by an out-of-bounds pointer arithmetic in inftrees.c. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/120509 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120509] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L)\n\nCVEID: CVE-2016-9842 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9842]\nDESCRIPTION: zlib is vulnerable to a denial of service, caused by an undefined left shift of negative number. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/120510 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120510] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L)", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q072", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-9843 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9843]\nDESCRIPTION: zlib is vulnerable to a denial of service, caused by a big-endian out-of-bounds pointer. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/120511 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120511] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L)", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q072", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Integration Bus V10.0.0.0- 10.0.0.8\n\nIBM Integration Bus V9.0.0.0- 9.0.0.7\n\nWebSphere Message Broker V8.0.0.0 - 8.0.0.8", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q072", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Product VRMF APAR Remediation/Fix IBM Integration Bus V10.0.0.0- 10.0.0.8 IT20410 The APAR is available in fix pack 10.0.0.9 (on all platforms except HP) http://www-01.ibm.com/support/docview.wss?uid=swg24043686 [http://www-01.ibm.com/support/docview.wss?uid=swg24043686]\n\nIBM Integration Bus V9.0.0.0- 9.0.0.7 IT20410 The APAR is available in fix pack 9.0.0.8 (on all platforms except HP) http://www-01.ibm.com/support/docview.wss?uid=swg24043751 [http://www-01.ibm.com/support/docview.wss?uid=swg24043751]\n\nWebSphere Message Broker V8.0.0.0 - 8.0.0.8 IT20410 The APAR is available in fix pack 8.0.0.9 (on all platforms except HP) https://www.ibm.com/support/docview.wss?uid=swg24043806 [https://www.ibm.com/support/docview.wss?uid=swg24043806]\n\nFor unsupported versions of the product IBM recommends upgrading to a fixed, supported version/release/platform of the product.\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at :\nhttp://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308]", "logical_doc_id": 4, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q072", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 4, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q072", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]\nIBM Java SDK Security Bulletin [http://www.ibm.com/support/docview.wss?uid=swg22002169]", "logical_doc_id": 4, "chunk_id": 32 }, { "doc_id": "techqa_DEV_Q072", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 30 Jun 2017 - Original version Published\nThe 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.", "logical_doc_id": 4, "chunk_id": 33 }, { "doc_id": "techqa_DEV_Q072", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "#\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker 8.0\nPRODUCT ALIAS/SYNONYM\n WMB IIB", "logical_doc_id": 4, "chunk_id": 34 }, { "doc_id": "techqa_DEV_Q036", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "This document will answer the question, \"How to create an IBM WebSphere Application Server (WAS) profile using the IBM Web Administration for i console?\"", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q036", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Pre-requisites\nA currently supported version of the IBM WebSphere Application Server software product must already be installed and updated to a recent Fix Pack version. Refer to the following hyperlink for the list of currently supported IBM WebSphere Application Server products at specific IBM i OS VRMs.\n\nOfficial Support Statement for the IBM WebSphere Application Server Product on the IBM i OS [http://www.ibm.com/support/docview.wss?uid=nas8N1020185]\n\n1) Open a web browser and go to the URL, http://:2001/HTTPAdmin, to display the IBM Web Administration for i console web application.\n\nIf you are not prompted for a userID and password or receive an error in the browser, ensure the ADMIN jobs are started in the QHTTPSVR subsystem using the WRKACTJOB SBS(QHTTPSVR) CL command. If the ADMIN jobs are not started, execute the following CL command to start the ADMIN server:\n\nSTRTCPSVR *HTTP HTTPSVR(*ADMIN)\n\nIf you continue to experience issues accessing the IBM Web Administration for i console, please open a Service Request (PMR) with IBM here [http://www-01.ibm.com/software/support/servicerequest/quick_start.html] or call 1-800-IBM-SERV. 2) Click on the \"Setup\" tab in the top,left-hand corner of the IBM Web Administration for i GUI.\n\n[/support/docview.wss?uid=nas8N1021317&aid=1] 3) Click on the link \"Create a New Application Sever\" in the main window.\n\n[/support/docview.wss?uid=nas8N1021317&aid=2] [/support/docview.wss?uid=nas8N1021317&aid=2] 4) The \"Create Application Server\" welcome screen will be displayed. Click on the \"Next\" button to begin the application server creation process. 5) You will then be presented with a screen to select the IBM WebSphere Application Server installation version you would like to create an application server under. Select the radio button next to the WAS version and edition you wish to create an application server profile under and then click the \"Next\" button.\n\nIn the screen shot below, the WAS v8.5.5.9 Express installation was chosen.\n\n[/support/docview.wss?uid=nas8N1021317&aid=3] [/support/docview.wss?uid=nas8N1021317&aid=3] 6) Configure the WAS Profile name and description. Then, click on the \"Next\" button to continue the WAS Profile creation process.\n\n[/support/docview.wss?uid=nas8N1021317&aid=4] 7) You are not presented with the option of either creating a new IBM HTTP Server to associate with your WAS Profile, selecting an existing IBM HTTP Server instance to associate with your WAS Profile, or not to associate an IBM HTTP Server with your WAS Profile. IBM recommends you select either the \"Create a new HTTP server\" or \"Select an existing HTTP server\" option.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q036", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "In the example below, we have selected the \"Create a new HTTP server\" option.\n\n[/support/docview.wss?uid=nas8N1021317&aid=5] [/support/docview.wss?uid=nas8N1021317&aid=5] 8) You will be presented with the following screen based on the option you selected in the previous step.\n\nCreate a new HTTP server (powered by Apache)\nWhen this option is selected, you will be prompted to enter the name and description for your new HTTP Server as well as the IP address and port you would like the HTTP Server to listen on. After you have configured this information, click the \"Next\" button.\n\n[/support/docview.wss?uid=nas8N1021317&aid=6] [/support/docview.wss?uid=nas8N1021317&aid=6]\n\nSelect an existing HTTP server (powered by Apache)\nWhen this option is selected, you will be prompted to select an existing HTTP Server to associate and use with your new WAS Profile. Select the exist HTTP Server you would like to associate with your WAS Profile and then click on the \"Next\" button.\n\n[/support/docview.wss?uid=nas8N1021317&aid=7] [/support/docview.wss?uid=nas8N1021317&aid=7]\n\nDo not associate an external HTTP server with this application server\nProceed to the next step to continue the WAS Profile creation process. 9) Enter the starting port for your WAS profile application server and then click the \"Next\" button.\n\nNOTE: A port block of 21 ports from the starting port specified will be allocated to the WAS Profile. This port block (starting port + 20) cannot be in use by another application or IBM i job. You can use the NETSTAT *CNN command to verify whether any of the ports in the port block are in use. If you find any of the ports in the port block (starting port + 20) are in use, you should specify a different starting port for a port block that is not currently in use to prevent application server start up issues due to port conflicts.\n\nIn the example below, we have specified port 10000 as the application server starting port, which means the port block will be 10000-10020 for this application server. We have verified that all\n\n[/support/docview.wss?uid=nas8N1021317&aid=8] [/support/docview.wss?uid=nas8N1021317&aid=8]", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q036", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "NOTE: If you get an error stating, \"Error:A port in the range xxx to xxx is already configured by another application. Specify a new port range. \"; change the \"First port in range\" field to a port number and port block that is not currently is use by another application. 10) The next screen shown will ask if you want to install the Default and Sample applications. By default, only the Default Applications are selected. Check the boxes next to the applications you wish to install into your new application server. IBM recommends checking only the Default Applications. Then, click the \"Next\" button to proceed.\n\n[/support/docview.wss?uid=nas8N1021317&aid=9] [/support/docview.wss?uid=nas8N1021317&aid=9] 11) Click the \"Next\" button to continue if you don't want to configure Kerberos/Single Sign-on for your WebSphere Application Server at this time. If you do wish to configure your WebSphere Application Server for Kerberos/Single Sign-on, click on the \"Configure Identity Tokens\" radio button and then click on the \"Next\" button to continue. IBM recommends you select \"Do no configure Identity Tokens\".\n\n[/support/docview.wss?uid=nas8N1021317&aid=10] [/support/docview.wss?uid=nas8N1021317&aid=10] 12) Finally, you will be presented with a WAS profile creation summary screen. This screen identifies the creation properties you configured (including the port range required to be available for the application server to start successfully) and the URLs to the sample applications you installed (if you installed any). Click on the \"Finish\" button to complete the WAS Profile and/or HTTP Server creation/association process.\n\nIBM recommends you write down the sample application URLs listed on this Summary screen to use for testing your new application server environment in later steps.\n\n[/support/docview.wss?uid=nas8N1021317&aid=11] [/support/docview.wss?uid=nas8N1021317&aid=11] 13) After clicking on the \"Finish\" button, you will be presented with a similar screen while the WAS Profile is being created. You can click on the [/support/docview.wss?uid=nas8N1021317&aid=12] button to refresh the status as indicated below.\n\n[/support/docview.wss?uid=nas8N1021317&aid=13] [/support/docview.wss?uid=nas8N1021317&aid=13] 14) Once the WAS Profile creation process has completed, the status on the left will change from \"Creating\", [/support/docview.wss?uid=nas8N1021317&aid=14], to \"Stopped\", [/support/docview.wss?uid=nas8N1021317&aid=15].\n\nIf you experience issues creating your WAS profile, please open a Service Request (PMR) with IBM here [http://www-01.ibm.com/software/support/servicerequest/quick_start.html] or call 1-800-IBM-SERV.\n\n[/support/docview.wss?uid=nas8N1021317&aid=16] [/support/docview.wss?uid=nas8N1021317&aid=16] 14) Click on the green start button, [/support/docview.wss?uid=nas8N1021317&aid=17], and then the \"Start\" button at the bottom of the page to start your WAS Profile and/or HTTP Server.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q036", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "NOTE: In the example below, an IBM HTTP Server is NOT currently associated with the WAS Profile.\n\n[/support/docview.wss?uid=nas8N1021317&aid=18] [/support/docview.wss?uid=nas8N1021317&aid=18] 15) You will noticed the status next to the WebSphere Application Server is now \"Starting\", You can click on the [/support/docview.wss?uid=nas8N1021317&aid=19] button to refresh the status.\n\n[/support/docview.wss?uid=nas8N1021317&aid=20] [/support/docview.wss?uid=nas8N1021317&aid=20]\n\nOnce the WebSphere Application Server has started, the status will change to \"Started\".\n\n[/support/docview.wss?uid=nas8N1021317&aid=21] [/support/docview.wss?uid=nas8N1021317&aid=21] 16) Finally, open a web browser and execute one of the URLs listed on the previous summary screen. If the web page is displayed successfully, this tells you your IBM WebSphere Application Server environment was created and is functioning normally.\n\nExample:\n\n[/support/docview.wss?uid=nas8N1021317&aid=22] [/support/docview.wss?uid=nas8N1021317&aid=22] 17) Congratulations! You have successfully created a new IBM WebSphere Application Server Profile using the IBM Web Administration for i Console.\n\nCross reference information Segment Product Component Platform Version Edition Operating System IBM i 7.3 Operating System IBM i 7.2 Operating System IBM i 7.1 Operating System IBM i 6.1", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q036", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "TAB NAVIGATION\nLearn more [http://www.ibm.com/support/docview.wss?uid=swg21405260]\nTroubleshoot [http://www.ibm.com/support/docview.wss?uid=swg21405299]- selected tab,\nCollect data [http://www.ibm.com/support/docview.wss?uid=swg21268195]\n\nTable of contents\nTroubleshooting Messaging bindings problems\n\n1 . What traces are required for troubleshooting bindings problems?\n2. Where can I find the changes made in my WebSphere MQ header fields in Service Message Objects(SMO) reflected in the outbound WebSphere MQ message?\n\n3. I am receiving the exception below, what custom properties do I need to define?\ncom.ibm.websphere.sca.ServiceRuntimeException: MQ channel exit has not been invoked, ensure Connection Factory has Custom Properties set for exits.\n\n4. Can two WebSphere MQ exports or imports point to the same queue?\n\n5. If the WebSphere MQ goes down, would the listener port re-connect to the WebSphere MQ automatically when it is available again?\n\n6. How can I dynamically change the JNDI resources for a WebSphere MQ import without the need to re-deploy the application?\n\n7. I am seeing the exception below, what does this mean?\ncom.ibm.websphere.sca.ServiceRuntimeException: No message is received from callback queue with selector=callbackID='CALLBACKMESSAGE_ID:....\n\n8. Even though I have received a response for a request that was sent out, I see the error message below. Why am I seeing this error and what are the possible solutions?\ncom.ibm.websphere.sca.ServiceRuntimeException: No message is received from callback queue with selector=callbackID='CALLBACKMESSAGE_ID:...\n\n9. My listener port is stopping due to an invalid or \u201cbad\u201d message and further processing does not take place. How do I configure the listener port to not stop and continue processing?\n\nWebSphere Process Server Messaging Bindings Questions and Answers\n1. What traces are required for troubleshooting bindings?\nFor all messaging bindings, use the following trace setting: SCA.JMS=all\n\nBack to top\n\n2. Where can I find the changes made in some of the WebSphere MQ headers fields in SMO reflected in the outbound WebSphere MQ message?\n\nNot all fields are propagated in the outbound message. You can find a list of the fields that are not passed on in the Using WebSphere MQ bindings in WebSphere ESB, Part 1: Manipulating MQ headers in WebSphere ESB using the XSL transformation primitive and WebSphere Integration Developer [http://www.ibm.com/developerworks/websphere/library/techarticles/0901_norton1/0901_norton1.html] developerWorks article.\n\nBack to top\n\n3. I am receiving the exception below, what custom properties do I need to define?\ncom.ibm.websphere.sca.ServiceRuntimeException: MQ channel exit has not been invoked, ensure Connection Factory has Custom Properties set for exits.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q036", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Refer to the Service Component Architecture modules and WebSphere MQ [http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp?topic=/com.ibm.websphere.soacore.612.doc/doc/cadm_scaandwmq.html] information center topic, which discusses the custom properties that you need to set. [http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp?topic=/com.ibm.websphere.soacore.612.doc/doc/cadm_scaandwmq.html]\n\nYou can find information on channel exits in the Using the WebSphere MQ messaging provider in WebSphere Application Server V7, Part 2: Using channel exits [http://www.ibm.com/developerworks/websphere/techjournal/0906_leming/0906_leming.html] developerWorks article. [http://www.ibm.com/developerworks/websphere/techjournal/0906_leming/0906_leming.html]\n\nBack to top\n\n4. Can two WebSphere MQ exports or imports point to the same queue?\n\nMultiple imports or exports (or applications) using the same queue is not supported. It cannot be guaranteed which one would receive the response. There should be separate queues for each import and export.\n\nOne Import/Export per MQ queue configuration is required. This configuration is also true in a golden or silver topology cluster environment. In this environment, the callback queue for the Import is remote from the application and all cluster members have visibility of the callback information.\n\nBack to top\n\n5. If WebSphere MQ goes down, would the listener port re-connect to WebSphere MQ automatically when it is available again?\n\nIf a WebSphere MQ resource goes down within the retry limits (the default is 5 times) then the listeners will reconnect. For example, if you try to put a message once and WebSphere MQ has gone down but then comes up on the 2nd, 3rd or 4th retry, it should reconnect. However, if the retry limit has been reached then after the listeners finish retrying, they are stopped and need to be started again manually.\nBack to top\n\n6. How can I dynamically change the JNDI resources for a WebSphere MQ import without the need to re-deploy the application?\n\nFollow the below steps:\n\n1. Log into the administrative console.\n\n2. Expand the Applications section.\n\n3. Select SCA modules.\n\n4. Select your module in question.\n\n5. On the right side of the page, expand imports, find the import you are referring to and select it.\n\n6. Expand 'Bindings'.\n\n7. Click MQ.\n\n8. Make changes to the JNDI and click apply.\n\n9. Save.\n Back to top\n\n7. I am seeing the below exception, what does it mean?\ncom.ibm.websphere.sca.ServiceRuntimeException: No message is received from callback queue with\nselector=callbackID='CALLBACKMESSAGE_ID:....", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q036", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The previous exception means that an MQ import is receiving a response message for a request that it did not send a request message for.\nBack to top\n\n8. Even though I have received a response for a request that was sent out, I see the error message below. Why am I seeing this error and what are the possible solutions?\ncom.ibm.websphere.sca.ServiceRuntimeException: No message is received from callback queue with selector=callbackID='CALLBACKMESSAGE_ID:....\n\nSee the following process that explains how the MQ/JMS Import works:\n\n1. MQ/JMS Import sends the MQ/JMS Request message and in the same transaction it also puts a correlation message to a Service Integration Bus (SIBus) Queue.\n\n2. MQ/JMS Import response listener receives the MQ/JMS response message off the response queue and, at this point, it attempts to get the correlation message off the SIBus queue.\n\n3. The response listener waits for a maximum of 6 seconds for the correlation message to become available before throwing the exception that you see.\n\n4. The MQ/JMS response message is then subject to the MQ retry and backout configuration as you have defined.\n\nTherefore, a possible cause for this error is a delay in the SIBus message being committed and becoming available. This scenario might be caused by performance issues of the underlying database used by SIBus.\n\nTo handle such situations you have the following options:\n 1. For the MQ/JMS Import, JMS callback destination has the default of persistence (Application). The MQ/JMS Import sends the correlation message as PERSISTENT; therefore, the message is persistent.\n\nMQ/JMS Callback Connection Factory uses the default Quality of Service for persistent, so it maps persistent to \"Reliable Persistence\" for SIBus.\n\nYou can try changing this to \"Assured Persistent,\" which drives the persistence of the message on the same thread as the commit call.\n\n2. Increase the retry values on the WebSphere MQ backout threshold and listener port to optimum values. In this case, the message is tried more than once before being sent to the backout queue.\n\n3. Tune the database used by SIBus to avoid any performance issue.\n Back to top\n\n9. My listener port is stopping due to an invalid or \u201cbad\u201d message and further processing does not take place. How do I configure the listener port to not stop and continue processing?", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q036", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "These messages are known as poison messages. Refer to the How WebSphere Application Server V6 handles poison messages [http://www.ibm.com/developerworks/websphere/library/techarticles/0803_titheridge/0803_titheridge.html] developerWorks article, which discusses how to handle these messages [http://www.ibm.com/developerworks/websphere/library/techarticles/0803_titheridge/0803_titheridge.html].\nBack to top", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q036", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "I have a working CICS\u00ae listener and a working TCP/IP connection to IWPM/NT. But when I start an IODM DISP transaction, why do I get error message: \"EKC0305A Unable to initialize workstation WRKSTTST\"?", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q036", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "This can happen when the definitions for the workstation are not correct in the IDWKCFTB table. It can be caused by the Port number being wrong, the IPADDR being wrong, it can even be wrong if the AMODATE is wrong as well. It has also been known to fail if the RTOUTor STOUT values are to small.\nIf running with dynamic TCP/IP (protocol set to 3), it can happen if you are not using DDNS or DHCP.\n\nIt can also fail if the IP address of the workstation has changed since the last time IODM had connected to the workstation and IODM has not be refreshed. The use of the OINT command or OSET command can resolve this problem.\n\nPlease refer to the IODM Systems Programmers Guide Appendix F. It covers installing and setting up TCP/IP support for IODM. Also, make sure your values in the IDWKCFTB are correct.\n\nLast do an OSET command with the DNSCLEAR option against the workstation followed by an OINT. This will ensure we have the correct IP address for the workstation. If none of this works, you will need to do a TSO PING of the host name of the workstation from a TSO session on the MVS\u00ae system running IODM's CICS region. If this fails, then the problem is the host name server does not have the definitions for the workstation defined. Please fix that to resolve the problem.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q036", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "EIF probe log at debug shows;\n\n2014-05-07T12:51:13: Information: I-UNK-000-000: Probewatch: Running ...\n2014-05-07T12:51:13: Information: I-UNK-000-000: ::::\n2014-05-07T12:51:13: Error: E-JPR-000-000: Error:Unable to bind to\nsocket transportTransportList=t1\nt1Type=SOCKET\nt1Channels=c1\nc1Port=5529\nc1PortMapper=true\nc1PortMapperNumber=100033057\nc1ServerLocation=localhost\neifHBID=5529\n\n2014-05-07T12:51:13: Information: I-UNK-000-000: Probewatch: Unable to\nget events; Caused by: null\n2014-05-07T12:51:13: Error: E-JPR-000-000: Unable to get events\nCaused by: null\n2014-05-07T12:51:13: Information: I-UNK-000-000: ::::\n2014-05-07T12:51:13: Information: I-UNK-000-000: Probewatch: Going Down\n...\n2014-05-07T12:51:13: Information: I-UNK-000-000: ::::", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q036", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "At SUSE11 rpcbind is used instead of portmap leading to no portmap as default, it has to be sourced and installed,", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q036", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "SUSE11, Omnibus 7.4 and EIF probe V13", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q036", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Apart from the EIF not starting, and a receiving EIF application showing an example of a .conf file commonly seen in a sending EIF product in the debug log, doing a rpm -q portmap will not show the product as being installed, ps aux | grep portmap will not show a running portmap process.", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q036", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Installed portmap which for my SUSE11 64bit system came in portmap-6.0+git20070716-31.16.x86_64.rpm\n\nThen had problems starting portmap by service portmap start, kept saying 111/udp address already in use, finally grep 111/udp /etc/services showed rpcbind against it, did service rpcbind stop and then service portmap start worked fine, service rpcbind start restarted rpcbind OK.\n\nps aux | grep portmap showed /sbin/portmap running, the eif probe would now start while having PortMapper='true' set.\n\nA confirm test for this would be to send an event with no port specified, the following will do that;\n\nposteifmsg -S sles11-64 -m \"Random text\" -r CRITICAL EVENT EVENT and seeing that event in the eif debug log.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q036", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "WebSphere 8.5 port collision during the creation of a second\n WebSphere cell despite having APAR PI51435 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI51435] applied.\n This APAR describes the issues that customers encountered with\n IBM WebSphere Application Server Version 8.5. These issues were\n resolved as information center updates in March, 2016.", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q036", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: This APAR provides a cumulative list of *\nthe documentation issues for month_year *\nthat affect users of IBM WebSphere *\nApplication Server Version 8.5. *\n\nPROBLEM DESCRIPTION: The Knowledge Centers for WebSphere *\nApplication Server Version 8.5 need *\nto reflect customer enhancement *\nrequests received in problem *\nmanagement records (PMRs). These *\nenhancements can include fixing *\ntechnical inaccuracies or clarifying *\nvague information. *\n\nRECOMMENDATION: *\n\nSee the Problem conclusion section for a description of the\n issues, which are described in customer PMRs, and the\n documentation change or changes that will address these issues.", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q036", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Note: We update our knowledge centers monthly. The following\n Version 8.5 modifications will be available in the month_year\n update to the Knowledge Centers. To access the latest\n on-line documentation, go to the product library page at\n http://www.ibm.com/software/webservers/appserv/library and\n select the version and product that is appropriate for your\n WebSphere Application Server environment.\n\nID: PI58314\n Problem: To avoid fewer pmrs where customers using 3rd party\n JPA jars and getting the problems. Need to add a statement in\n knowledge center so that we can also avoid sending these pmrs .\n\nResolution: Topic, Using third-party persistence providers, is\n updated as follows:\n Add an AVOID TROUBLE note that says:\n Avoid trouble: Even though IBM supports the enablement of\n third party JPA run times to run on WebSphere Application\n Server, and ensures the successful deployment of applications\n that use such run times,IBM does not provide support for\n resolving JAR file conflict problems, or any problem that a\n stack trace indicates is in the third party code.\n\nThe update also applies to V9.0\n\nID: 772810\n Problem: Calling getResource that begin with a forward slash\n (/) may return NULL if the JVM custom property\n com.ibm.ws.classloader.strict is set to true. This condition\n needs to be pointed out in the knowledge\n center.\n\nResolution: Topic, Java virtual machine custom properties, is\n updated for the com.ibm.ws.classloader.strict property with an\n Important note that reads:\n\nImportant: Ensure that you use the resources that don't begin\n with a forward slash (/). The WebSphere Application Server\n class loader behaves consistently with the Java Underclassman\n by using this property, which prohibits getResource calls that\n begin with a forward slash (/).\n\nThe update also applies to V7.0, V8.0, and, V9.0\n\nID: 772705\n Problem: In the following WAS 8.5.5 documentation we read\n about \"Memory overload protection\" that should be disabled by\n default:\n Topic: Configuring memory overload protection\n During a test a javacore was produced in which it seems the\n libHeapDetect64.so is loaded despite the fact no \"-agentlib\"\n parameter was specified. The documentation needs to clarify\n this condition.", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q036", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Resolution: Topic, Configuring memory overload protection, is\n updated as follows:\n (1)AVOID TROUBLE note before the procedure now reads:\n Avoid trouble: To ensure that the memory overload protection\n is configured properly, the -agentlib parameter needs to be\n set in the Generic JVM arguments field. Specifying the\nagentlib parameter is only required in WebSphere ??Applicatio\n Server Version 8.5.5.2 and earlier. For a version of WebSphere\n Application Server after version 8.5.5.2, the -agentlib\n parameter is always loaded and does not need to be set, even\n if the autonomic request flow manager (ARFM) is disabled.\n\n(2) the sentence just before this AVOID TROUBLE note is\n rewritten to read:\n Memory overload protection is disabled by default. Memory\n overload protection is enabled when the memory overload\n protection (MOP) value is set to less than 100.\n\nThe update also applies to V9.0\n\n209287 (RTC)\n Problem: Client had issue setting the startup wait time.\n PM91596 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM91596] added a new bootstrap.properties parameter:\n server.start.wait.time\n This bootstrap.properties parameter is not\n documented in the Knowledge Center and should be\n\nResolution: Topic, Specifying Liberty bootstrap properties, is\n updated to read:\n Use custom properties to configure server start wait time.\n\nYou can increase the server start wait time beyond the product\n default setting by adding the server.start.wait.time property\n to the boostrap.properties file. The server.start.wait.time is\n specified in seconds.\n\nSpecify the server.start.wait.time property in the\n bootstrap.properties file. The following example sets the\n server start time to 25 seconds.\n\nserver.start.wait.time = 25\n\nThis setting means that as the server starts, the\n reporting mechanism for the server attempts to report on the\n completed stages of the start. If the reporting mechanism for\n the server cannot perform its function within 25 seconds, an\n error 22 occurs.\n\nIf you do not add the server.start.wait.time property to\n the bootstrap.properties file, the default server start wait\n time is internally set to 30 seconds.\n\nThis update also applies to V9.0\n\nID: 772734\n Problem:Topic, Configuring port settings, is missing\n information about configuring to set port numbers in a\n different port range so that they cannot conflict.\n Resolution: Topic, Configuring port settings, is update to add\n a third optional step that reads:\n Optional: Set port numbers in a different port range so that\n they cannot conflict.", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q036", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "WebSphere Application Server cannot always detect port\n conflicts when multiple installations are present on multiple\n hosts. To set port numbers in this situation so that you avoid\n port conflicts, adjust the starting port numbers of each\n installation to be in a different range from the other\n installations.\n\nFor example, in a system with two installations, you can\n configure one installation to use the default port number\n settings, and manually assign a different port range in the\n second installation.\n\nCreate the deployment manager of the second installation\n by using the manageprofiles command. On the -startingPort\n option, set a starting port number that is out of range of any\n ports that other installations use.\n\nbin/manageprofiles.sh -create -profileName Dmgr03\nprofilePath\n /opt/IBM/WebSphere/AppServer_2/profiles/Dmgr03 -templatePath\n /opt/IBM/WebSphere/AppServer_2/profileTemplates/management\nstartingPort 15000\n\nCreate the application server or custom profiles on each\n target machine.\n Federate the profiles to the deployment manager by running\n the addNode command.\n Create clusters and cluster members from the deployment\n manager.\n\nNew servers that you create inherit the higher starting\n port number from the deployment manager.\n Note: Node agents do not inherit the starting port number\n from the deployment manager. If needed, manually change the\n port number settings.\n\nTip: You can use the Profile Port Checker tool to check for\n conflicts without needing to start the servers. Note that the\n tool checks only for conflicts on the machine where it runs.\n For information about using the Profile Port Checker, see\n Using the Profile Port Checker.\n\nThis update also applies to V9.0\n\nID:\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q036", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI58314\nREPORTED COMPONENT NAME\n WEBSPHERE APP S\nREPORTED COMPONENT ID\n 5724J0800\nREPORTED RELEASE\n 850\nSTATUS\n CLOSED DOC\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-03-02\nCLOSED DATE\n 2016-07-21\nLAST MODIFIED DATE\n 2018-04-11\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q060", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "There is a mismatch in z/OS levels between Language Environment modules, CEECCICS and CEEPLPKA.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q060", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Ensure that there is only one instance of CEEPLPKA and CEECCICS in your library concatenations, and that they are at the correct z/OS level.\n\nPRODUCT ALIAS/SYNONYM\n CICS/TS CICS TS CICS Transaction Server", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q060", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "DFHSR0622 [http://publib.boulder.ibm.com/infocenter/cicsts/v3r2/index.jsp?topic=/com.ibm.cics.ts.messages.doc/cics_mc/dfhsr/SR0622.html] An attempt to overwrite the ERDSA has caused the abend which follows\nDFHSR0601 [http://publib.boulder.ibm.com/infocenter/cicsts/v3r2/index.jsp?topic=/com.ibm.cics.ts.messages.doc/cics_mc/dfhsr/SR0601.html] Program interrupt occurred with system task TCP in control\nDFHKE1800 [http://publib.boulder.ibm.com/infocenter/cicsts/v3r2/index.jsp?topic=/com.ibm.cics.ts.messages.doc/cics_mc/dfhke/KE1800.html] ABNORMAL TERMINATION OF CICS IS COMPLETE", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q060", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Program check in Compuware module DBUGPCPA. CICS ends since the program check occurs in a module that is running under the main CICS terminal control task.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q060", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "You examine a system dump on the DFHSR0601 [http://publibfi.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/dfhg4c00/1.87?ACTION=MATCHES&REQUEST=dfhsr0601&TYPE=FUZZY&SHELF=dfhasj00&DT=20070614214024&CASE=&searchTopic=TOPIC&searchText=TEXT&searchIndex=INDEX&rank=RANK&ScrollTOP=FIRSTHIT#FIRSTHIT] message and find that the running task is TCP CSTP.\n\nThe ABEND0C4 occurs in Compuware module DBUGPCPA on a STM instruction: 90ECD00C. This is because register 13 is pointing to \"read only\" or key 0 storage. In this case, it is pointing to module EYU9NA01.\n\nYou back up in the CICS trace and find that the TCP task was in the middle of processing a losterm error for a terminal attached to CICS.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q060", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "[/support/docview.wss?uid=swg21272740&aid=1]Compuware [http://www.compuware.com/] has provided fix XDPF265.\n\nPRODUCT ALIAS/SYNONYM\n CICS/TS CICS TS CICS Transaction Server", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q060", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Following are the messages you receive:\nDFHSI1517 Control is being given to CICS.\nDFHAP0001 An abend (code 0C4/AKEA) has occurred at offset X'FFFF' in module DHSUWT.\nDFHDU0201 ABOUT TO TAKE SDUMP. DUMPCODE: AP0001 , DUMPID: 1/0001.", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q060", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Analysis of the dump shows that some non IBM code is attempting to access the TCA of the current task by using CSAQRTCA. In CICS TS V3.2 and higher, this field contains the address of fetch protected storage. An attempt to access the storage at the address results in a program check (abend0C4 abendAKEA).", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q060", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Determine who is accessing the CSA by Locating the PSW for the program check in a CICS system dump [http://www.ibm.com/support/docview.wss?uid=swg21176381]. Then change the code so it no longer uses CSAQRTCA. Your code should also no longer use CSACDTA which is also being loaded with fetch protected storage.\n\nIf you find that CA module CAS9XS41 or CAS9560 is causing the abend, then this problem is being caused by the CA ENF program product. The official CA fix is QO88406 (from 2007). However, to immediately solve your problem you can enter the following MVS modify command and then restart your CICS region:\n\nF ENF,MODE(CICS,NONE)\n\nContact [/support/docview.wss?uid=swg21244931&aid=1]CA support [http://www.ca.com/] to get the fix or if you have additional questions.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q060", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#ASRD abend when using CICS TS V3.2 or higher [http://www.ibm.com/support/docview.wss?uid=swg21264616]\n\nPRODUCT ALIAS/SYNONYM\n CICS/TS CICS TS CICS Transaction Server\n\nz/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q060", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Immediately after an EXCI program purges some transactions, the\n region receives:\n DFHLD0002 A severe error (code X'1927') has occurred in module\n DFHLDLD1\n followed by:\n DFHPC0401 CICST20 Abend AEXZ issued by TCP task.\n After issuing DFHPC0401, the CICS asid hangs and had to be\n canceled.\n An abend0c4 occurs in program DFHZACT at offset x'1FA' on a\n TM instruction 9180 80B4 with reg8 invalid. Reg8 contains\n x'40404040' and has been loaded from regA +x'230'. Register\n 10 does not point to a valid TCTTE.\n The problem is that the CATD task was purged while in the middle\n of SYNCPOINTing the deletion of the terminal. The abend was\n deferred until after returning from DFHSPP. At that point, the\n TCTTE has been successfully committed. DFHAPLI then abends the\n task. This drives the handle abend exit of DFHZATD which calls\n DELETE_TERMINAL_ERROR. A SYNCPOINT ROLLBACK is issued but the\n TCTTE is not re-instated because deletion of the TCTTE has been\n successfully committed.\n The code assumed that it has a TCTTE now and put it back on the\n activate scan queue to retry the terminal delete.\n When DFHZACT runs, it finds the TCTTE that is not valid\n resulting in an ABEND0C4 in DFHZACT.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q060", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All. *\n\nPROBLEM DESCRIPTION: Abend0C4 in DFHZACT at X'1FE' following *\nabend of CATD task. CICS abends with *\nDFHSR0601 Program interrupt occurred *\nwith system task TCP in control. *\n\nRECOMMENDATION: *\n\nWhile deleting an autoinstalled terminal, CATD gets forcepurged\n during SYNCPOINT of the deleted terminal. The AKC3 abend is\n deferred and on return to DFHZATD control passes to the abend\n handler routine ZATDDTEE.\n Routine DELETE_TERMINAL_ERROR is called to perform a SYNCPOINT\n ROLLBACK to restore the terminal and to place the TCTTE back on\n activate scan queue so that the delete can be retried.\n However, in this case the terminal had already been\n deleted successfully and the TCTTE storage freed and reused.\n When TCP ran subsequently and processed the activate scan queue\n this reused TCTTE storage caused an abend0C4 in DFHZACT. This\n led to message DFHSR0601 'Program interrupt occurred with system\n task TCP in control' being issued and CICS being terminated.\n However other unpredictable results could occur.\n Additional keywords: AbendAKC3 DFHZATD ZACT Abends0C4 S0C4 0C4\n AKC3", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q060", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "DFHZATD has been altered to check if the terminal still\n exists before rescheduling for deletion.\n\nTEMPORARY FIX\nFIX AVAILABLE BY PTF ONLY", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q060", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PK47140\nREPORTED COMPONENT NAME\n CICSTS V3 Z/OS\nREPORTED COMPONENT ID\n 5655M1500\nREPORTED RELEASE\n 400\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2007-06-14\nCLOSED DATE\n 2007-10-26\nLAST MODIFIED DATE\n 2007-11-02\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n UK30680 UK30681\n\nMODULES/MACROS\nDFHZATD", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q060", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n CICSTS V3 Z/OS\nFIXED COMPONENT ID\n 5655M1500", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q060", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R400 PSY UK30680 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK30680]\n UP07/11/01 P F710\nR500 PSY UK30681 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK30681]\n UP07/10/31 P F710\n\nFIX IS AVAILABLE\nSELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL. YOU WILL BE REQUIRED TO SIGN IN. DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q060", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "If you have a system dump from a CICS TS V4.2 or V5.1 region, see locating the PSW for a program check in a CICS TS V5.3, V5.2, V5.1 or V4.2 system dump [http://www.ibm.com/support/docview.wss?uid=swg21610631].\n\nIf you have a system dump from a CICS TS V3.2 or lower region, see locating the PSW for a program check in a CICS TS V3 system dump [http://www.ibm.com/support/docview.wss?uid=swg21176381].\n\nIf you have a system dump that contains your CICS TS V4.1 address space, you can do the following to locate the PSW and the registers for the program check:\n\n1. Enter option 0 from the IPCS primary option menu to display the IPCS default values panel.\n 2. Enter DSNAME('xxxxx.xxxxx.xxxx') to the right of Source where xxxxx.xxxxx.xxxx is the dump dataset name. Then enter Enter and F3 to return to the IPCS primary option menu.\n 3. Enter option 6 from the IPCS primary option menu to display the IPCS Subcommand Entry panel.\n 4. Enter IPCS command verbx dfhpdxxx 'ke' where xxx is the version and release for the CICS dump. The value of xxx is 660 for CICS TS V4.1. This command will format the dump and display to the Kernel Domain KE_TASK Summary.\n 5. Enter f *YES* to get to the running task that had the program check. There may be more than one. In the example below, there is one task with *YES* under ERROR (KE_NUM 008E). Figure 1.1\n [/support/docview.wss?uid=swg21424768&aid=1] [/support/docview.wss?uid=swg21424768&aid=1]\n\n6. Make a note of the KE_NUM, TCA_ADDR and the TRANSID of the tasks in error.\n 7. Enter f table to find the KE Domain Error Table Summary. This is a summary containing the last 50 abends in the region since it was started. Figure 1.2\n [/support/docview.wss?uid=swg21424768&aid=2] [/support/docview.wss?uid=swg21424768&aid=2]", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q060", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "8. Enter ip st sys on the command line to determine the local time and date that the dump was taken.\n 9. Make a note of the ERR_NUM associated with the program check that has an ERR_TIME matching the time the dump was taken and a KE_NUM matching the KE_NUM found in the Kernel Domain KE_TASK Summary. If there is more than one program check for the same ERR_TIME and KE_NUM, focus on the first program check. The other program checks are probably a result of the first program check.\n 10. Enter f 'Number: xxxxxxxx' where xxxxxxxx is the ERR_NUM of the program check (from Figure 1.2) you have decided to focus on. This will find the entry in the KE Domain Error table for the error number you specify.\n\nFigure 1.3\n [/support/docview.wss?uid=swg21424768&aid=3] [/support/docview.wss?uid=swg21424768&aid=3]\n 11. For CICS TS V4.1 compare the addresses at offset X'34' and offset X'10C' in the KERNEL ERROR DATA. The addresses are the second word of the CICS PSW and the MVS PSW, respectively. If the addresses are different, use the MVS PSW and registers. Otherwise, use the CICS PSW and registers.\n\nThe CICS PSW starts at offset x'30' and is 3 words in length. The CICS registers, 0 through 15, start at offset X'48' and each register is 2 words in length.\n The MVS PSW starts at offset x'108' and is 3 words in length. The MVS registers, 0 through 15, start at offset x'120' and each register is 2 words in length.\n\n12. Use F8 to scroll down to see the formatted CICS PSW and registers as shown in Figure 1.4 below. IPCS CICS VERBX will format the MVS PSW and registers if the MVS PSW is different from the CICS PSW. If the PSWs are the same as in this example, then CICS VERBX does not duplicate the information.\n\nFigure 1.4\n [/support/docview.wss?uid=swg21424768&aid=4] [/support/docview.wss?uid=swg21424768&aid=4]\n\nCICS VERBX will attempt to determine the failing module from the PSW and will display the module name and offset if possible. The offline dump formatter uses more information than the original failure message, and so often, when the original failure message is unhelpful (offset FFFFFFFF in module) the dump formatter will be more informative.", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q060", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "By scrolling down from the panel in Figure 1.4, you will often get the failing module printed from the start to the interrupt address plus 256 bytes. CICS VERBX will also assume the values in the general registers are addresses and print the storage before and after these addresses, using both 31 bit and 24 bit addresses.\n\nOnce you know the PSW, you can do the following to determine the module that the failure is occurring in: 1. Enter option 1 from the IPCS primary option menu to Browse the dump data set.\n 2. Enter nnnnnnnn into the Pointer Address field where nnnnnnnn is the second word of the PSW. If the first digit of the PSW address is greater than 8, subtract 8 from it. In the example above, the PSW address is AE500B86. Therefore, you would use 2E500B86.\n 3. If the storage displays, enter F7 to scroll up until you see an eye catcher for a load module. Load module names are usually followed by a date and time stamp. Calculate an offset within the module by subtracting the load point from the PSW address. This is the offset where the abend occurred.\n 4. If \"storage not available\" displays, enter ip where nnnnnnnn. If the module has been loaded by the operating system from the LPA or Nucleus, this will display the module name and the offset within the module.\n\nNow that you know the module name and the offset, search for a known problem on the CICS Support page [http://www.ibm.com/support/entry/portal/Overview/Software/Other_Software/CICS_Transaction_Server]. Use keywords such as the following for a search argument: 'DFHAP0001 DFHAPDM 0C4'.", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q060", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "Finding where a program check occurred [http://www.ibm.com/support/knowledgecenter/SSGMCP_4.1.0/com.ibm.cics.ts.doc/dfhs1/topics/dfhs1l8.html]\n\nPRODUCT ALIAS/SYNONYM\n CICS/TS CICS TS CICS Transaction Server", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q051", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Error Stack Trace extracted from the J2EE Application Server error log:\n\njava.lang.NullPointerException\n\n at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:421)\n\n at com.filenet.wcm.apps.server.ui.info.prefs.PrefAccessRolesInfoPage.renderRoleMembers(PrefAccessRolesInfoPage.java:254)\n\n at com.filenet.wcm.apps.server.ui.info.prefs.PrefAccessRolesInfoPage.renderRole(PrefAccessRolesInfoPage.java:220)\n\n at com.filenet.wcm.apps.server.ui.info.prefs.PrefBootstrapInfoPage.renderAdminRole(PrefBootstrapInfoPage.java:131)\n\n at com.filenet.wcm.apps.server.ui.info.prefs.PrefBootstrapInfoPage.render(PrefBootstrapInfoPage.java:303)", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q051", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "This behavior may occur if an invalid entry has been specified in the User Display Name Attribute or Group Display Name Attribute setting in the Directory Services Configuration in FileNet Enterprise Manager (FEM).\n\nWorkplace XT attempts to resolve the user names and groups defined within the Access Roles based on the Directory Service configuration defined in FEM. If the user name query resolves to null or if there is an invalid entry a NullPointerException error may occur.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q051", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "In FEM, change the User Display Name Attribute or Group Display Name Attribute to a valid LDAP entry such as cn, displayName or uid and restart the FileNet Content Engine and Workplace XT instances.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q051", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The following message may be displayed instead of the logon screen in FileNet Application Engine (Workplace) :\n\nError Message:\nnull\n\nException Class:\njava.lang.NullPointerException\n\nStack Trace:\njava.lang.NullPointerException\nat java.io.File. (File.java:194)\nat org.apache.log4j.helpers.FileWatchdog. (FileWatchdog.java:47)\nat org.apache.log4j.PropertyWatchdog. (PropertyConfigurator.java:665)\nat org.apache.log4j.PropertyConfigurator.configureAndWatch (PropertyConfigurator.java:373)\nat org.apache.log4j.PropertyConfigurator.configureAndWatch (PropertyConfigurator.java:355)\nat com.filenet.util.logging.LoggingConfigLoader.loadConfig (LoggingConfigLoader.java:44)\nat com.filenet.wcm.apps.server.controller.WcmWorkplaceController.initializeStaticClasses (WcmWorkplaceController.java:370)\nat com.filenet.wcm.toolkit.server.base.WcmController.configurePage (WcmController.java:2580)\nat com.filenet.wcm.toolkit.server.base.ConfigurableController.configurePage (ConfigurableController.java:115)\nat com.filenet.wcm.toolkit.server.base.WcmController.configurePage (WcmController.java:2476)\nat com.filenet.wcm.toolkit.server.base.WcmController.configurePage (WcmController.java:2339)\nat org.apache.jsp.WcmDefault_jsp._jspService (WcmDefault_jsp.java:59) ....", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q051", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "This message may be displayed when the Application Engine (Workplace) is unable to access the configuration files directory.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q051", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Inspect the contents of the deployed web.xml for the Workplace application ( typically under the J2EE application server deployed directory ...\\Workplace\\WEB-INF\\web.xml).\n\nThe configurationDirectory parameter indicates the location of the AE configuration files directory, for example on Microsoft Windows, it may indicate :\n\n\nconfigurationDirectory\nC:\\\\Program Files\\\\FileNet\\\\Config\\\\AE\n", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q051", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The Operating System user starting the J2EE application server needs to be able to read / write to the location identified as the \"configurationDirectory\" in web.xml, otherwise a NullPointerException may be displayed. Adjust file system / network share permissions as to allow access to this directory.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q051", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Error:\n\ncom.filenet.api.exception.EngineRuntimeException;Property not defined: RoleName. [Code=null] ... Object Reference [ANY:0] ID \"{00000000-0000-0000-0000-000000000000}\" in ObjectStore \"null\"; OMFC/Search/ExecuteXML//RETRIEVE_PROPERTY_NOT_DEFINED", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q051", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "During Object Store creation, the Access Role not created", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q051", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "During Object Store creation, the Access Role not created", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q051", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Solution:\nWhen using Wizard to create an Object Store, need to select the full set of addon extensions. RoleName (Access Roles) will be created with the install of the Workplace Addon Extensions.\nOr if no addon extensions are selected during the object store creation, you can add the set of addoon extentions to the object store after its creation.\n\nPRODUCT ALIAS/SYNONYM\n FileNet", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q051", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Getting prompted to logon twice when adding a document through Application Integration for WorkplaceXT/Microsoft Outlook and getting a NullPointerException when logging on at second time.\n\nAfter the first logon, user was promoted to logon again. When logging on at the second time, the following error occurred:\n\n\"IBM FileNet Workplace XT Add: Unable to Perform Add Operation\"\n\nOperation: SelectedAddProfile\nError Name: E_SVRCMDXMLPARSERFAILED\nHRESULT: 0x8004042b\nDescription: Unable to parse command XML:null\nDetails: java.lang.NullPointerException\n\nAfter the error message dialog box was dismissed, adding a document from Outlook did not prompt for logon again for the current Outlook session. After starting a new Outlook session, the symptom repeated again.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q051", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Since the WorkplaceXT was not configured for Single Sign On (SSO), the first logon was expected for each Outlook session. The unexpected second logon was due to the Application Integration error (see above).\n\nThis error was caused by the jar files in /IBM/WebShpere/AppServer/lib/ext directory of the WebShpere Applicaton Server (WAS) hosting the WorkplaceXT.\n\nIn reference to the following page at P8 Knowledge Center\n\n\"Configuring WebSphere Application Server to support user tokens and WebDAV connections for Workplace XT\"\n\nhttp://www-01.ibm.com/support/knowledgecenter/SSNW2F_5.2.1/com.ibm.p8.installingxt.doc/wxtip018.htm [http://www-01.ibm.com/support/knowledgecenter/SSNW2F_5.2.1/com.ibm.p8.installingxt.doc/wxtip018.htm]\n\nthere should be only two jar files in the following directory in WAS hosting the WorkplaceXT:\n/IBM/WebShpere/AppServer/lib/ext", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q051", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Steps to resolve the problem:\n\n1. Stopped WAS hosting the WorkplaceXT\n2. Removed any additional jar files from the /IBM/WebShpere/AppServer/lib/ext directory so that the directory contained only two jar files:\nauthentication-websphere.jar\nlog4j_1.2.13.jar\n\n3. Deleted WorkplaceXT folder from the WAS wstemp folder, and clear the browser cache\n4. Started WebSphere Application Server\n\nAfter implementing the above procedure, the problem was resolved. User started to get a logon prompt only once as expected.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q051", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Below error displayed after logging in:\n\njava.lang.NullPointerException at com.filenet.wcm.apps.server.util.prefs.LabelConfiguration.getConfiguredLabelResource (LabelConfiguration.java:106)\nat com.filenet.wcm.apps.server.ui.info.prefs.PrefBootstrapInfoPage.render (PrefBootstrapInfoPage.java:263)\nat com.filenet.wcm.toolkit.server.base.WcmUiModule.renderJSP (WcmUiModule.java:676)\nat com.filenet.wcm.toolkit.server.util.ui.WcmLayout.renderRegion (WcmLayout.java:68)\nat com.filenet.wcm.apps.server.presentation.util.WorkplaceLayout.render (WorkplaceLayout.java:221)\nat com.filenet.wcm.apps.server.ui.WcmInfoModule.render (WcmInfoModule.java:399)\nat com.filenet.wcm.toolkit.server.base.WcmUiModule.renderJSP (WcmUiModule.java:676)\nat com.filenet.wcm.toolkit.server.util.WcmUi.render (WcmUi.java:90)\nat com.filenet.wcm.toolkit.server.util.WcmUi.render (WcmUi.java:82)\nat com.ibm._jsp._WcmBootstrap._jspService (_WcmBootstrap.java:131)\nat com.ibm.ws.jsp.runtime.HttpJspBase.service (HttpJspBase.java:99)\nat javax.servlet.http.HttpServlet.service (HttpServlet.java:831)\nat com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied (ServletWrapper.java:307)\nat com.ibm.ws.cache.servlet.CacheHook.handleFragment (CacheHook.java:576)\nat com.ibm.ws.cache.servlet.CacheHook.handleServlet (CacheHook.java:250)\nat com.ibm.ws.cache.servlet.ServletWrapper.service (ServletWrapper.java:259)\nat com.ibm.ws.webcontainer.servlet.ServletWrapper.service (ServletWrapper.java:1661)\nat com.ibm.ws.webcontainer.servlet.ServletWrapper.service (ServletWrapper.java:1602)\nat com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter (WebAppFilterChain.java:113)\nat com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter (WebAppFilterChain.java:80)\nat com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter (WebAppFilterManager.java:908)\nat com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest (ServletWrapper.java:939)\nat com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest (ServletWrapper.java:507)\nat com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest (ServletWrapperImpl.java:181)\nat com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest (GenericServletWrapper.java:121)\nat com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest (AbstractJSPExtensionServletWrapper.java:259)\nat com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionProcessor.handleRequest (AbstractJSPExtensionProcessor.java:353)\nat com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include (WebAppRequestDispatcher.java:732)\nat com.filenet.wcm.toolkit.server.base.WcmController.serverSideInclude (WcmController.java:5503)\nat com.filenet.wcm.toolkit.server.base.WcmController.handleEvent (WcmController.java:3155)\nat com.ibm._jsp._WcmBootstrap._jspService (_WcmBootstrap.java:141)", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q051", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "PrimaryViews.xml file has encoding that's set incorrectly to ANSI. By default, this file should be set to UCS-2 Big Endian after XT installation.", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q051", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "1. Open the FileNet/Config/WebClient/PrimaryViews.xml into Notepad ++.\n 2. Select Encoding menu.\n 3. Select Convert to UCS-2 Big Endian then save the change.\n 4. Stop and restart the Workplace XT application server", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q296", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "DB transactions are rolled back due to SQL timeout.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q296", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "When multiple DB2 pureScale members are active during FileNet CM addon creation, excessive SQL locking may occur, resulting in a potential lock timeout. This can result in transactions being rolled back, thereby resulting in the addon installation failing.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q296", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Examine both the P8 error log and the DB2 diagnostic logs for each active member for lock timeout error messages similar to the following:\n\nDB2 (db2diag.log):\nFUNCTION: DB2 UDB, lock manager, sqlplWaitOnWP, probe:999\n\n MESSAGE : ZRC=0x80100044=-2146435004=SQLP_LTIMEOUT\n\"LockTimeOut - tran rollback Reason code 68\n\nP8 (p8_server_error.log):\ncom.filenet.api.exception.EngineRuntimeException: FNRCE0019E: E_DEADLOCK_ERROR: The operation could not be completed due to a deadlock error. A retry might be appropriate.\nCaused by: com.ibm.db2.jcc.am.SqlTransactionRollbackException: DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68, DRIVER=4.15.82\n\nNote: The SQLERRMC=68 suggests that the root cause is a SQL lock timeout even though the P8 error message and SQLCODE suggest a deadlock occurred.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q296", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The lock timeouts can be avoided by only having a single DB2 pureScale member active during FileNet CM addon installation. Once addon installation has completed successfully, the other members can be brought back online.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q296", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "I have setup multipath devices to work with Spectrum Scale (GPFS) replication in my pureScale cluster.\nHowever, the pureScale system is hanging if one of the storage device goes offline.\n\nWhy does this happen, and how can I setup the devices for GPFS failover to take place as expected?", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q296", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The multipath devices might be configured as features= \"1 queue_if_no_path\" by default like as below:.\n*\ndefaults {\n user_friendly_names yes\n find_multipaths yes\n }\n blacklist {\n }\n*\nmpathe (360050768028488816800000000000024) dm-8 IBM ,2145\n* size=100G\nfeatures='1 queue_if_no_path'\nhwhandler='0' wp=rw\n*\n\nThe I/O would stop in a storage failure due to the settings, then it causes a hang issue on pureScale cluster. Please see the Linux manual page for more information on the queue_if_no_path settings.\n\nIssues with queue_if_no_path feature [https://access.redhat.com/documentation/ja-JP/Red_Hat_Enterprise_Linux/7/html/DM_Multipath/queueifnopath_issues.html]\nIf a multipath device is configured with features \"1 queue_if_no_path\", then any process that issues I/O will hang until one or more paths are restored.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q296", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Please setup multipath devices as below:\n\n1. Make sure of Device Mapper Multipathing (DM-MP) settings in your multipath device manuals, then follow the instructions.\n\nFor instance, if you use IBM Storwize V7000, please see:\nMultipath support for hosts running the Linux operating system [https://www.ibm.com/support/knowledgecenter/ST3FR7_7.8.0/com.ibm.storwize.v7000.780.doc/svc_linmultipathovr_21bb33.html]\nSettings for Linux hosts [https://www.ibm.com/support/knowledgecenter/ST3FR7_7.8.0/com.ibm.storwize.v7000.780.doc/svc_linux_settings.html]\n\n2. Update /etc/multipath.conf so that GPFS failover can take place accordingly.\n\nIBM Spectrum Scale\u2122 Frequently Asked Questions and Answers [https://www.ibm.com/support/knowledgecenter/SSFKCN/com.ibm.cluster.gpfs.doc/gpfs_faqs/gpfsclustersfaq.html#dmmp]\nQ4.6: What considerations are there when setting up DM-MP multipath service?\n*\n*\nfeatures \"0\"\n* failback immediate\n* no_path_retry fail\n\nFigure 1.sample multipath.conf with V7000 in RHEL 7.2:\n\ndefaults {\nuser_friendly_names yes\nfind_multipaths yes\npolling_interval 30\n}\ndevices {\ndevice {\nvendor \"IBM\"\nproduct \"2145\"\npath_grouping_policy \"group_by_prio\"\npath_selector \"service-time 0\" # Used by Red Hat 7.x\nprio \"alua\"\npath_checker \"tur\"\nfailback \"immediate\"\nno_path_retry fail\nrr_weight uniform\nrr_min_io_rq \"1\"\ndev_loss_tmo 120\nfeatures \"0\"\n}\n}\nblacklist {\n}\nFigure 2. sample multipath -l on the same setup as figure 1.\n\nmpathe (360050768028488816800000000000024) dm-7 IBM ,2145\nsize=100G features='0'hwhandler='0' wp=rw\n|-+- policy='service-time 0' prio=0 status=active\n| |- 5:0:2:0 sdn 8:208 active undef running\n| |- 5:0:3:0 sdt 65:48 active undef running\n| |- 6:0:2:0 sdbn 68:16 active undef running\n| `- 6:0:3:0 sdbt 68:112 active undef running\n`-+- policy='service-time 0' prio=0 status=enabled\n|- 5:0:1:0 sdh 8:112 active undef running\n|- 5:0:0:0 sdb 8:16 active undef running\n|- 6:0:0:0 sdbb 67:80 active undef running\n`- 6:0:1:0 sdbh 67:176 active undef running", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q296", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#\n\nA FIX IS AVAILABLE\nVersion 8.5 Refresh Pack 7 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24041575]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q296", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Adding members to or removing members from an internal group\n fails on a system where you use process attachments or case\n folders. In the log, you see an error similar to this error:\n com.lombardisoftware.core.TeamWorksException: Error updating\n teams. Details: CWTDS0000E: An unexpected failure occurred.\n Details: 'FNRCE0004: E_BAD_INDEX: The index specified does not\n reference a valid property or list element.'\n Explanation: An exception was thrown.\n Action: Check the server log files.\n at com.lombardisoftware.bpd.runtime.engine.CaseHelper.\n updateContentEngineTeams(CaseHelper.java:1415)\n at com.lombardisoftware.bpd.runtime.engine.CaseHelper.\n updateContentEngineTeams(CaseHelper.java:1367)\n at com.lombardisoftware.server.ejb.security.InternalGroupsCore.\n removeUserFromInternalGroup(InternalGroupsCore.java:260)\n at com.lombardisoftware.server.ejb.security.InternalGroupsCore.\n removeUserFromInternalGroup(InternalGroupsCore.java:230)\n ...", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q296", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "When you update the membership of an internal group, your\n updates must be propagated to the IBM BPM document store to also\n update the authorization of process attachments and case\n folders. This operation is done in bulk on all teams that\n contain the internal group. If this operation affects a team as\n well as its manager team, the operation might fail.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q296", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A fix that ensures permission updates do not fail will be\n included in an IBM BPM V8.5.6.0 cumulative fix.\n\nTEMPORARY FIX\nNot applicable", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q296", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR54725\nREPORTED COMPONENT NAME\n BPM ADVANCED\nREPORTED COMPONENT ID\n 5725C9400\nREPORTED RELEASE\n 856\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2015-11-12\nCLOSED DATE\n 2016-01-14\nLAST MODIFIED DATE\n 2016-01-14\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q296", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM STANDARD\nFIXED COMPONENT ID\n 5725C9500", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q296", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R856 PSY\n UP", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q296", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How can I configure the DB2 JCC properties for DB2 pureScale affinity on Tomcat ?", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q296", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "For Java applications including stand alone or web applications in the Web Application Server (WAS), the necessary DB2 JDBC properties for DB2 pureScale affinity configuration are same.\nFor the detail of the JDBC properties, refer to the link in this page below.\nFollowing steps are an example configuration of the client affinity on Tomcat.\n\n1. Set pureScale member host names to the /etc/hosts of the operating system where Tomcat will be running.\nAs pureScale java client refers the serverlist which is received from pureScale server,\nit's necessary to set the hosts and the pureScale member IP to the /etc/hosts file.\n\n$ cat /etc/hosts\n.....\n### example\n### pureScale client\n192.168.153.65 db2ps1.au.ibm.com db2ps1\n### pureScale server\n192.168.153.64 db2ps2.au.ibm.com db2ps2 # pureScale member 0\n192.168.153.68 db2ps3.au.ibm.com db2ps3 # pureScale member 1\n\n2. Add JNDI resource information to the web application environment file /conf/web.xml.\n\n........\n\n\njdbc/sample\njavax.sql.DataSource\nContainer\n\n\n\n\n3. Add JNDI data source information to tomcat configuration file /conf/context.xml\n\ntomcat@db2ps1:~/tomcat7054/conf> cat context.xml\n\n\nWEB-INF/web.xml\n\n\n\n\n\n\n4. Sample application code to get connection from the datasource name.\n\n.....\nConnection conn = null;\nStatement stmt = null;\nResultSet rs = null;\ntry {\nContext c = new InitialContext();\nDataSource ds =(DataSource)c.lookup(\"java:comp/env/jdbc/sample\");\nconn = ds.getConnection();\n......\n5. During client affinity test, following message will be recorded in the Tomcat log file /logs/catalina.out\n\ncom.ibm.db2.jcc.am.ClientRerouteException:\n[jcc][t4][2027][11212][3.63.123] A connection failed but has been\nre-established. The host name or IP address is \"db2ps2.au.ibm.com\" and\nthe service name or port number is 61,118. RELATED INFORMATION\n JDBC properties for client affinities [http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.apdv.java.doc/src/tpc/imjcc_c0056257.html]\nApache Tomcat JNDI Datasource HOW-TO [http://tomcat.apache.org/tomcat-7.0-doc/jndi-datasource-examples-howto.html]", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q296", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How can you access user attributes other than user name and display name in an LDAP store from the IBM Business Process Manager products?", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q296", "section_id": 0, "heading": "ANSWER", "parent": null, "text": "To resolve this issue, you can use one of the following approaches:\nUse the LDAP Connector toolkit to query LDAP for specific user attributes. Then, store these values in custom Business Process Manager user attributes so that task user assignment can be selected based on these Business Process Manager user attributes.\nUse code that queries the Virtual Member Manager to retrieve any supported user attributes from the underlying security repository and stash the value in a Business Process Manager user custom attribute.\n\nYou must implement either solution as custom code.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM BPM Advanced Pattern on Red Hat Enterprise Linux Server Security Linux Red Hat - xSeries 8.0 Business Integration IBM Business Process Manager Standard Security AIX, Linux, Linux zSeries, Solaris, Windows 8.5.5, 8.5, 8.0, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration IBM Business Process Manager Express Security Linux, Linux zSeries, Windows 8.5.5, 8.5, 8.0, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5\nPRODUCT ALIAS/SYNONYM\n BPM", "logical_doc_id": 5, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q197", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM Cognos Business Intelligence, IBM DB2, IBM SPSS Modeler, IBM SPSS Collaboration and Deployment Services, IBM WebSphere Application Server, WebSphere Message Broker and IBM Integration Bus are shipped as components of IBM Predictive Maintenance and Quality. Information about a security vulnerability affecting IBM Cognos Business Intelligence, IBM DB2, IBM SPSS Modeler, IBM SPSS Collaboration and Deployment Services, IBM WebSphere Application Server, WebSphere Message Broker and IBM Integration Bus has been published in their respective security bulletins.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q197", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Please consult the Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM Cognos Business Intelligence [http://www-01.ibm.com/support/docview.wss?uid=swg21959671] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM DB2 [http://www-01.ibm.com/support/docview.wss?uid=swg21967893] for vulnerability details and information about fixes.\nPlease consult the Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM SPSS Modeler [https://www-304.ibm.com/support/docview.wss?uid=swg21960194] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM SPSS Collaboration and Deployment Services [http://www-01.ibm.com/support/docview.wss?uid=swg21960528] for vulnerability details and information about fixes\n\nPlease consult the Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg21957980] details and information about fixes\n\nPlease consult the Security Bulletin: Multiple vulnerabilities in IBM Java Runtime including Logjam affect WebSphere Message Broker and IBM Integration Bus. This bulletin also addresses vulnerabilities in OpenSSL including Logjam and alternate chains certificate forgery [http://www-01.ibm.com/support/docview.wss?uid=swg21958955] details and information about fixes", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q197", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Principal Product and Version(s) Affected Supporting Product and Version IBM Predictive Maintenance and Quality 2.0\n\nIBM Predictive Maintenance and Quality 2.5\n\nIBM Predictive Maintenance and Quality 2.5.1 IBM Cognos Business Intelligence 10.2.1.1\nIBM DB2 10.1.0.3\nIBM SPSS Modeler 16.0\nIBM SPSS Collaboration and Deployment Services 6.0\nIBM WebSphere Application Server ND 8.5.5.0\nWebSphere Message Broker 7.5.0.2\nIBM Integration Bus 9.0.0.1\n\nIBM Cognos Business Intelligence 10.2.2\nIBM DB2 10.5.0.4\nIBM SPSS Modeler 16.0.0.1\nIBM SPSS Collaboration and Deployment Services 6.0.0.1\nIBM WebSphere Application Server ND 8.5.5.3\nWebSphere Message Broker 7.5.0.4\nIBM Integration Bus 9.0.0.2\n\nIBM Cognos Business Intelligence 10.2.2\nIBM DB2 10.5.0.4\nIBM SPSS Modeler 17.0\nIBM SPSS Collaboration and Deployment Services 7.0\nIBM WebSphere Application Server ND 8.5.5.3\nWebSphere Message Broker 7.5.0.4\nIBM Integration Bus 9.0.0.2 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.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q197", "section_id": 3, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] CHANGE HISTORY\n November 11, 2015: Original Version Published\nThe 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.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q197", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere Application Server is shipped as a component of IBM WebSphere Commerce. Information about a potential security vulnerability affecting the WebSphere Application Server was published in a security bulletin.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q197", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Consult the security bulletin Information Disclosure in WebSphere Application Server (CVE-2017-1743) [http://www-01.ibm.com/support/docview.wss?uid=swg22013601]for vulnerability details and information about fixes.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q197", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "WebSphere Commerce versions 7.0.0.0 or higher fix pack\nWebSphere Commerce versions 8.0.0.0 or higher fix pack or higher mod pack", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q197", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Principal Product and Version(s) Affected Supporting Product and Version Affected Supporting Product Security Bulletin WebSphere Commerce V7.0 WebSphere Application Server 7.0.0\nWebSphere Application Server 8.5.5 Information Disclosure in WebSphere Application Server (CVE-2017-1743) WebSphere Commerce V8.0 WebSphere Application Server 8.5.5 Information Disclosure in WebSphere Application Server (CVE-2017-1743) WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q197", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q197", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q197", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 24 May 2018: Original Version Published\nThe 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\nCross reference information Segment Product Component Platform Version Edition Commerce WebSphere Commerce - Express Security IBM i, Linux, Windows 7.0 Express Commerce WebSphere Commerce Developer Enterprise Security Windows 8.0, 7.0 All Editions Commerce WebSphere Commerce Professional Security AIX, IBM i, Linux, Solaris, Windows 8.0, 7.0 Professional Edition\n\nWMB IIB SECURITY BULLETIN", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q197", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "WebSphere Message Broker and IBM Integration Bus are affected by Open Source Apache Tomcat vulnerability.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q197", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-3092 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092]\nDESCRIPTION: Apache Tomcat is vulnerable to a denial of service, caused by an error in the Apache Commons FileUpload component. By sending file upload requests, an attacker could exploit this vulnerability to cause the server to become unresponsive.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/114336 [https://exchange.xforce.ibmcloud.com/vulnerabilities/114336] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q197", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Integration Bus V10.0 & V9.0\n\nWebSphere Message Broker V8.0", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q197", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Product VRMF APAR Remediation/Fix IBM Integration Bus V10\nIT15719 An interim fix is available from IBM Fix Central for all platforms.\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719]\n\nThe APAR is targeted to be available in fix pack 10.0.0.7 IBM Integration Bus V9\nIT15719 An interim fix is available from IBM Fix Central for all platforms.\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719]\n\nThe APAR is targeted to be available in fix pack 9.0.0.7 WebSphere Message Broker\nV8\nIT15719 An interim fix is available from IBM Fix Central for all platforms.\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibms~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT15719 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibms~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT15719]\n\nThe APAR is targeted to be available in fix pack 8.0.0.8\nFor unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product.\n\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at :\nhttp://www.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006308]", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q197", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q197", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 27 Oct 2016 - Original version Published\nThe 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\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker AIX, HP-UX, Linux, Solaris, Windows 8.0\nPRODUCT ALIAS/SYNONYM\n WMB IIB", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q197", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere Application Server is shipped as a component of IBM WebSphere Commerce. Information about a potential security vulnerability affecting the WebSphere Application Server was published in a security bulletin.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q197", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Consult the security bulletin Information disclosure in WebSphere Application Server (CVE-2017-1681) [http://www-01.ibm.com/support/docview.wss?uid=swg22010419] for vulnerability details and information about fixes.", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q197", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "WebSphere Commerce versions 7.0.0.0 or higher fix pack\nWebSphere Commerce versions 8.0.0.0 or higher fix pack or higher mod pack", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q197", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Principal Product and Version(s) Affected Supporting Product and Version Affected Supporting Product Security Bulletin WebSphere Commerce V7.0 WebSphere Application Server 7.0.0\nWebSphere Application Server 8.5.5 Information disclosure in WebSphere Application Server (CVE-2017-1681) [http://www-01.ibm.com/support/docview.wss?uid=swg22010419] WebSphere Commerce V8.0 WebSphere Application Server 8.5.5 Information disclosure in WebSphere Application Server (CVE-2017-1681) [http://www-01.ibm.com/support/docview.wss?uid=swg22010419] WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q197", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q197", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q197", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 16 May 2018: Original Version Published\nThe 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\nCross reference information Segment Product Component Platform Version Edition Commerce WebSphere Commerce Developer Enterprise Security Windows 8.0, 7.0 All Editions Commerce WebSphere Commerce Professional Security AIX, IBM i, Linux, Solaris, Windows 8.0, 7.0 Professional Edition Commerce WebSphere Commerce - Express Security IBM i, Linux, Windows 7.0 Express", "logical_doc_id": 3, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q197", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere Application Server is shipped as a component of WebSphere Commerce. Information about a security vulnerability affecting IBM WebSphere Application Server was published in a security bulletin.", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q197", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Consult the security bulletin Information disclosure in WebSphere Application Server (CVE-2017-1381) [http://www-01.ibm.com/support/docview.wss?uid=swg22004792] for vulnerability details and information about fixes.", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q197", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "WebSphere Commerce versions 8.0.0.0 or higher fix pack or higher mod pack\nWebSphere Commerce versions 7.0.0.0 - 7.0.0.9", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q197", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Principal Product and Version(s) Affected Supporting Product and Version Affected Supporting Product Security Bulletin WebSphere Commerce V7.0 IBM WebSphere Application Server 7.0 Information disclosure in WebSphere Application Server (CVE-2017-1381) [http://www-01.ibm.com/support/docview.wss?uid=swg22004792] WebSphere Commerce V8.0 IBM WebSphere Application Server 8.5.5 Information disclosure in WebSphere Application Server (CVE-2017-1381) [http://www-01.ibm.com/support/docview.wss?uid=swg22004792] WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q197", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q197", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q197", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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 17 August 2017: Original Version Published\nThe 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\nCross reference information Segment Product Component Platform Version Edition Commerce WebSphere Commerce - Express Security IBM i, Linux, Windows 7.0 Express Commerce WebSphere Commerce Developer Enterprise Security Windows 8.0, 7.0 All Editions Commerce WebSphere Commerce Professional Security AIX, IBM i, Linux, Solaris, Windows 8.0, 7.0 Professional Edition", "logical_doc_id": 4, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q277", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Portal page is blank\nSystemOut.log contains the following error at the time of the problem occurrence:\n\ncom.ibm.websphere.wim.exception.InvalidUniqueNameException: CWWIM1011E\nThe '' unique name is not valid.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q277", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "SAML TAI parameter sso_.sp.idMap = is configured to use \"idAssertion\" which results in the userid instead of the fully distinguished name of the user to be set in the JAAS subject. Portal then uses this value to query Virtual Member Manager (VMM) via findUserByIdentifier() and the failure occurs since the value is not formatted as a distinguished name.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q277", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Collect Portal Login troubleshooting data [http://www-01.ibm.com/support/docview.wss?uid=swg21592791]\nLook for the following in security.xml:\n\" interceptorClassName=\"com.ibm.ws.security.web.saml.ACSTrustAssociationInterceptor\">\n...\n\" name=\"sso_1.sp.idMap\" value=\"idAssertion\"/>\n\nNote: There may be more than one sso_.sp.idMap property (for example, sso_1.sp.idMap, sso_2.sp.idMap, etc).", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q277", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Option #1:\n\nThe idAssertion value means that no entry is necessary for the user in the user registry, which is not supported in WebSphere Portal by default. Update the sso_.sp.idMap property via the Integrated Solutions Console to use the value \"localRealm\" instead of \"idAssertion.\"\n\nThe localRealm value ensures that WebSphere Application Server will complete the JAAS Subject with the full distinguished name for the user by querying the user registry and thus Portal will pass the correct format to VMM.\n\nOption #2:\n\nTransient user support [http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/overview/new_cf08.dita?lang=en] has been introduced for SAML TAI [http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/wcm/wcm_secure_int_tai_auth.dita?lang=en] starting with Cumulative Fix (CF) #8 for 8.5. Refer to the WebSphere Portal Security blog [https://www.ibm.com/developerworks/community/blogs/8f2bc166-3bdc-4a9d-bad4-3620dbb3e46c/entry/portal_transient_user_support_with_was_saml_tai_business_case_clarification?lang=en] for more details regarding the business case and implementation details.\n\nNote: WebSphere Portal also provides transient user support when configured with OpenId authentication [http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/security/use_openid.dita?lang=en].", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q277", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "Understanding the SAML Trust Association Interceptor [http://www.ibm.com/developerworks/websphere/techjournal/1307_lansche/1307_lansche.html]\nWebSphere Portal Support Statement [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/WebSphere_Portal_Support_Statement_wp8]", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q277", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "The WebSphere MQ (WMQ) Support Portal page has been replaced by the IBM MQ Support Portal page.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q277", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "The WebSphere MQ product name was changed to IBM MQ starting with v8. Now that v9 has been available for a while, we have renamed the IBM Support Portal page for MQ from WebSphere MQ to IBM MQ. You will find content for all versions of MQ on the new IBM MQ Support Portal page [https://www.ibm.com/support/entry/portal/product/websphere/ibm_mq].\n\nIf you have bookmarks or links to the old WebSphere MQ Support Portal page, you should update them to point to the new IBM MQ Support Portal page. We have put redirects in place to handle most forms of the old WebSphere MQ URL, but there are some variants that might not properly redirect to the new IBM MQ page. To avoid any problems with the URL redirect process, we recommend that you update your bookmarks and links to the new IBM MQ Support Portal page:https://www.ibm.com/support/entry/portal/product/websphere/ibm_mq [https://www.ibm.com/support/entry/portal/product/websphere/ibm_mq]\n\nYou can search for MQ, IBM MQ, or WebSphere MQ from the main IBM Support Portal page [https://www.ibm.com/support/entry/portal/support]. You will see the choice to select IBM MQ. You will not see \"WebSphere MQ\" in the search results since it has been replaced by the IBM MQ Support Portal page.\n\nTo receive notifications for MQ content, make sure your My Notifications subscriptions also include IBM MQ. Keep WebSphere MQ active as well, since the transition phase for our documents will take some time and you will want to receive notifications for both IBM MQ and WebSphere MQ documents. To manage your My Notifications subscriptions, go to the My Notifications site [https://www.ibm.com/support/mynotifications].", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q277", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM MQ and WebSphere MQ Support Portal changes [https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/IBM_MQ_and_WebSphere_MQ_Support_Portal_Changes]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere MQ AIX, Platform Independent, HP-UX, IBM i, Linux, OpenVMS, Solaris, z/VSE, Windows, z/OS 9.0, 8.0, 7.5, 7.1, 7.0, 6.0, 5.3.1, 5.3, 3.0\nPRODUCT ALIAS/SYNONYM\n IBMMQ MQ WMQ", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q277", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Top Content for WebSphere Portal Security and Administration, all topics.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q277", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "1. What steps should I follow to change Portal-related passwords?\nThe WebSphere Portal documentation contains instructions for both Version 6.1 [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/topic/com.ibm.wp.ent.doc_v615/security/sec_pswds.html] and [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Updating_user_ID_and_passwords_wp7]Version 7 [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Updating_user_ID_and_passwords_wp7].\n\n2. How can I configure LDAP failover in WebSphere Portal?\n\nSee Implementing LDAP failover [http://www-01.ibm.com/support/docview.wss?uid=swg21382720].\n\n3. Login fails for a single user or a small number of users and only on specific workstations. What might cause this?\n\nClient add-ons could prevent successful login [http://www-01.ibm.com/support/docview.wss?uid=swg21441915]\n\n4. After login a single image file is shown in the browser and nothing else, how can I resolve this?\n\nApply APAR PM25450 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM25450] then perform the manual configuration steps listed in the APAR text.\n\n5. Should I configure the Portal for standalone or federated LDAP security?\n\nFederated security is the out-of-the-box configuration. The configuration task wp-modify-ldap-security \"converts\" the configuration to standalone with a single LDAP. Use standalone if you: (1) Will not require more than one LDAP or another type user repository (for example, a database), (2) Will not need to configure multiple virtual portals, each with its own realm.\n\n6. Is my current security configuration is standalone or federated?\n\nDetermining whether WebSphere Portal security configuration is standalone or federated [http://www-01.ibm.com/support/docview.wss?uid=swg21386736]\n\n7. Configuration changes in our environment have caused access to Portal artifacts to be lost. How can I restore access?\n\nSee How to fix Portal Access Control settings after user/group external identifiers have changed [http://www-01.ibm.com/support/docview.wss?uid=swg21377025]\n\n8. In our environment, updates are made to LDAP directly outside Portal. The changes are not immediately visible in the Portal or in our custom portlet. Why is this?\n\nBoth the Portal User Management Architecture (PUMA) and WebSphere Application Server Virtual Member Manager (VMM) component maintain caches that are automatically updated only if user, group or attribute changes are made using the Portal UI.\n\nYou can adjust the cache time [http://www-01.ibm.com/support/docview.wss?uid=swg21413947] out periods, disable the caches [http://www-01.ibm.com/support/docview.wss?uid=swg21379992] (this is to be avoided due to its effect on performance), or, if you have custom code that calls or can be modified to call the PUMA reload() method, apply APAR PM16430 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM16430] and add the associated new properties.\n\n9. Is there a document that summarizes the ReleaseBuilder tool?\n\nYes. See Using ReleaseBuilder effectively [http://www-01.ibm.com/support/docview.wss?uid=swg21243005]\n\n10. How do I collect log files or trace for a WebSphere Portal security issue?", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q277", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Follow the appropriate Collecting Data [http://www.ibm.com/support/docview.wss?uid=swg21312740] document for the version of Portal in use.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q277", "section_id": 2, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24044067]\n8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http://www-01.ibm.com/support/docview.wss?uid=swg24044096]\n9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24044242]\n8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]\n9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24044620]\n7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45 [http://www-01.ibm.com/support/docview.wss?uid=swg24044551]\n8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q277", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "In SAML Web SSO, when the redirect target is null,\n \"INTERNAL ERROR: Please contact your support.\" is displayed\n in the browser. There is no information in the FFDC or\n SystemOut.log for problem diagnosis.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q277", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: IBM WebSphere Application Server users of *\nSAML Web SSO *\n\nPROBLEM DESCRIPTION: Additional diagnostics are required *\nwhen the SAML Web SSO redirect URL is *\nnull *\n\nRECOMMENDATION: Install a fix pack that contains this *\nAPAR. *\n\nIn SAML Web SSO, when the redirect target is null, the runtime\n sets the redirect target to NO_TARGET. This results in\n \"INTERNAL ERROR: Please contact your support.\" being displayed\n in the browser.\n .\n There should be some indication in the SystemOut.log that this\n condition has happened so that the administrator can attempt\n to address the issue.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q277", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The SAML Web SSO TAI is updated to redirect to the configured\n error page when the redirect target is null. . When the redirect target is null, the following error message\n will appear in the SystemOut.log file:\n . CWSML7035E: The SAML Web Single Sign-on (SSO) Trust\n Association Interceptor (TAI) is unable to determine a\n redirect target URL. The redirect URL can come from the\n sso_.sp.targetUrl SAML TAI custom property, the RelayState\n parameter in the SAMLResponse or the WasSamlSpReqUrl cookie. If you do not intend to have a value for the\n sso_.sp.targetUrl SAML TAI custom property or have your\n IdP send a RelayState parameter in the SAMLResponse, then\n check earlier in the log to see if you have a CWSML7036W\n warning that indicates that the request URL host name is not\n the same as the ACS URL host name. If you see that warning,\n then that condition must be corrected to fix this error. The\n value for the relayState parameter on the SAMLResponse is [{0}]. . EXPLANATION: The SAML Web SSO TAI cannot find a redirect URL\n for the current request. The redirect URL can come from three\n places: 1) the sso_.sp.targetUrl SAML TAI custom property,\n 2) the RelayState parameter in the SAMLResponse and 3) the\n WasSamlSpReqUrl cookie. At least one of these three things\n must be present in order for the SAML TAI to be able to\n determine the redirect URL. In this case, none of these three\n things are present, therefore, the SAML TAI can not determine\n the redirect URL. Note that the SAML TAI may have set a\n WasSamlSpReqUrl cookie earlier in the process, but the browser\n did not make the cookie available to the SAML TAI. Also, the\n RelayState parameter must be a URL that uses the http or https\n protocol. . USER ACTION: Ensure at least one of the following is true: 1)\n the sso_.sp.targetUrl SAML TAI custom property is\n configured for the current SP, 2) the IdP sets the RelayState\n parameter on the SAMLResponse with a valid URL that uses the\n http or https protocol or 3) the WasSamlSpReqUrl cookie is\n made available to the SAML TAI.", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q277", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "In order for the\n WasSamlSpReqUrl to be available to the SAML TAI, the original\n request URL must have the same host name as the ACS URL that\n is configured on the sso_.sp.acsUrl TAI custom property. . . The SAML TAI is also updated to check for duplicate acsUrl\n entries at load time. If any are found, the following warning\n will be emitted:\n . CWSML7038W: The SAML Web Single Single Sign-on (SSO) Trust\n Association Interceptor (TAI) has two assertion consumer\n service URL custom properties configured that have the same\n URL path: [{0}] and [{1}]. This condition can cause\n unexpected behavior at run time. To prevent further issues,\n all text after : must be unique for each\n [sso_.sp.acsUrl] custom property value. . EXPLANATION: The value for each SAML [sso_.sp.acsUrl]\n custom property must have a unique URL path. A URL path does\n not include the protocol and : parts of a URL\n string. For example, although the URL strings for\n https://somewhere.ibm.com/samlsps/hello/app and\n https://elsewhere.ibm.com/samlsps/hello/app are different, the\n URL paths are the same. If two acsUrl entries have the same\n URL path, when a SAMLResponse is sent to one of the URLs that\n has a duplicate path, the service provider that is chosen to\n handle the request will be indeterminate. . USER ACTION: Ensure that the URL configured for each of the\n [so_.sp.acsUrl] custom properties have unique URL paths,\n meaning that they have unique text after the :\n part of the URL string.\n\nThe fix for this APAR is currently targeted for inclusion in\n fix pack 7.0.0.45, 8.0.0.14, 8.5.5.13 and 9.0.0.5. Please\n refer to the Recommended Updates page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q277", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI61915\nREPORTED COMPONENT NAME\n WEBS APP SERV N\nREPORTED COMPONENT ID\n 5724H8800\nREPORTED RELEASE\n 700\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-05-05\nCLOSED DATE\n 2017-08-16\nLAST MODIFIED DATE\n 2017-08-16\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q277", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBS APP SERV N\nFIXED COMPONENT ID\n 5724H8800", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q277", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R700 PSY\n UP\nR800 PSY\n UP\nR850 PSY\n UP\nR900 PSY\n UP", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q277", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "IBM WebSphere Portal is successfully installed and configured. Without logging in, end-users occasionally mistype a URL which does not exist. Then users are redirected to either the Portal login page or the Portal home page. How can Portal be configured to throw a 404 error message rather than issuing a 302 redirect?", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q277", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The default behavior of WebSphere Portal is to send an HTTP 302 redirect to the end user. A modification to the Portal configuration is required to throw an HTTP 404 instead.", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q277", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Throwing a 404 error\n\nTo configure WebSphere Portal to throw 404 errors for nonexistent URLs, perform the following steps:\n\n1) Login to the WAS Console / Deployment Manager.\n\n2) Navigate to Resources > Resource Environment > Resource Environment Providers > WP ConfigService > Custom Properties\n\n3) Create a new custom property\n\nName: friendly.pathinfo.enabled\nValue: false\nType: java.lang.String\n\n4) Create a new custom property\n\nName: friendly.pathinfo.invalid\nValue: true\nType: java.lang.String\n\n5) Create a new custom property\n\nName: friendly.redirect.enabled\nValue: false\nType: java.lang.String\n\n6) Create a new custom property\n\nName: state.decoding.fallback\nValue: false\nType: java.lang.String\n\n7) Create a new custom property\n\nName: wps.mappingurl.invalid\nValue: true\nType: java.lang.String\nNote: The end result of steps #3-#7 should look like the following:\n[/support/docview.wss?uid=swg21674823&aid=1]\n\n8) Save changes. If clustered sync nodes.\n\n9) Restart the Portal server(s).\n\nFor a description of what each of these properties does see the related URL below.\n\nServlet Level 404 Handling", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q277", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Note - the configuration changes noted in the previous section will account for use cases where WebSphere Portal is processing the URLs - such as /wps/portal/nonexistentURL, /wps/myportal/nonexistentURL, etc. If you wish to expand you use cases to cover /wps/nonexistentURL and more generally /wps/* URLs which do not exist, see the Technote below for how to update wps.ear to handle 404 errors on a servlet level:\nhttp://www.ibm.com/support/docview.wss?uid=swg21411195 [http://www.ibm.com/support/docview.wss?uid=swg21411195]\n\nWCM Friendly URLs", "logical_doc_id": 5, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q277", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "If you are on Portal 8.5 and leverage WCM Friendly URLs - upgrade to Portal 8.5 Cumulative Fix 03 or later and implement additional configuration settings as noted in the Portal 8.5 Infocenter [http://www.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/wcm/configure_validate_friendly_urls.dita?lang=en]. This Technote will be updated in the near future with further details of how to implement these settings.", "logical_doc_id": 6, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q277", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "WARNING: If you are on Portal 7.0 or 8.0 and you have WCM Friendly URLs configured - those Friendly URLs will no longer work correctly if the settings in this Technote are implemented. Friendly URLs on Portal pages will continue to function correctly but resolution of the WCM Friendly URLs will fail. WCM URLs that utilize the urile query parameter will continue to work but WCM Friendly URLs will fail. Unfortunately - there are no plans at present to backport WCM Friendly URL functionality to Portal 7.0 or 8.0. Open a feature request [https://www.ibm.com/developerworks/rfe/] if you would like to see this functionality backported.\n\nUpdated Behavior for Access Control", "logical_doc_id": 7, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q277", "section_id": 0, "heading": "RELATED INFORMATION", "parent": null, "text": "Configuration Service properties [http://www.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/admin-system/srvcfgref_config.dita?lang=en]\nCan WebSphere Portal be configured to send a specific 3 [http://www.ibm.com/support/docview.wss?uid=swg21411109]\n\nCross reference information Segment Product Component Platform Version Edition Organizational Productivity- Portals & Collaboration WebSphere Portal AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS 7.0, 6.1", "logical_doc_id": 8, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q230", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "z/os DIRECT LINKS TO FIXES\n7.2.0-ISS-SDI-FP0005 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FSecurity+Directory+Integrator&fixids=7.2.0-ISS-SDI-FP0005&source=SAR]\n7.2.0-ISS-SDI-FP0004 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FSecurity+Directory+Integrator&fixids=7.2.0-ISS-SDI-FP0004&source=SAR]\n7.2.0-ISS-SDI-FP0003 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FSecurity+Directory+Integrator&fixids=7.2.0-ISS-SDI-FP0003&source=SAR]\n7.2.0-ISS-SDI-FP0002 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FSecurity+Directory+Integrator&fixids=7.2.0-ISS-SDI-FP0002&source=SAR]\n7.2.0-ISS-SDI-FP0001 [http://www-01.ibm.com/support/docview.wss?uid=swg24037895]\n7.2.0-ISS-SDI-FP0002 [http://www-01.ibm.com/support/docview.wss?uid=swg24039085]\n7.2.0-ISS-SDI-FP0003 [http://www-01.ibm.com/support/docview.wss?uid=swg24040694]\n7.2.0-ISS-SDI-FP0004 [http://www-01.ibm.com/support/docview.wss?uid=swg24044400]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q230", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Short description: tdisrvctl fails with CTGDJB125E\n\n Problem description:\n When my customer issues the following command:\n\n /app/IBM/TDI/V7.1.1/bin/tdisrvctl -h localhost -v -op status -c\n\n He receives the following error message frequently (but not\n every time) in tdisrvctl.log:\n\n 2014-02-03 17:48:46,671 ERROR [tdisrvctl] - CTGDJB125E Unable to\n get list of all running Configs.\n 2014-02-03 17:48:46,673 ERROR [tdisrvctl] - error unmarshalling\n return;\n nested exception is:\n java.io.WriteAbortedException: writing aborted;\n java.io.NotSerializableException: java.io.ByteArrayInputStream\n sun.rmi.server.UnicastRef.invoke(UnicastRef.java:185)\n com.ibm.di.api.remote.impl.ConfigInstanceImpl_Stub.getConfigura\n tion(Con\n figInstanceImpl_Stub.java:386)\n com.ibm.di.cli.RemoteServerCommand.getRunningConfig(RemoteServe\n rCommand\n .java:3017)\n com.ibm.di.cli.RemoteServerCommand.viewStatus(RemoteServerComma\n nd.java:\n 2330)\n com.ibm.di.cli.RemoteServerCommand.execStatus(RemoteServerComma\n nd.java:\n 1598)\n com.ibm.di.cli.RemoteServerCommand.serverControlCommand(RemoteS\n erverCom\n mand.java:294)\n com.ibm.di.cli.RemoteServerCommand.main(RemoteServerCommand.jav\n a:230)\n Caused by: java.io.WriteAbortedException: writing aborted;\n java.io.NotSerializableException:\n java.io.ByteArrayInputStreamwriting\n aborted; java.io.NotSerializableException:\n java.io.ByteArrayInputStream\n java.io.ObjectInputStream.readObject0(ObjectInputStream.java:13\n 50)\n java.io.ObjectInputStream.readObject(ObjectInputStream.java:365\n )\n java.util.Hashtable.readObject(Hashtable.java:1005)\n sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)\n sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMetho\n dAccesso\n rImpl.java:37)\n java.lang.reflect.Method.invoke(Method.java:611)\n ...\n\n The issue has been addressed in WI DI02000\n\n L3 provided file mmconfig.jar on Feb 7 and advised to use this\n file along with previous miserver.jar & miconfig.jar from 4th\n Feb update.\n\n This fixed the issue.\n\n Cust's environment:\n ITDI 7.1.1.3\n AIX 7.1", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q230", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Workaround: use files mmconfig.jar from the Feb 7 and files\n miserver.jar & miconfig.jar from Feb 4 update of WI DI02000\n\nAccording to L3, official fix would be made available in next\n fixpack for 7.1.1 i.e. 7.1.1-TIV-TDI-FP0004 (No plan yet in Q1)", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q230", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Problem with TDI tdisrvctl utility.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q230", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This is bug in TDI code and has been fixed. formal fix will be\n made available in 7.2.0-TIV-TDI-FP0001.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q230", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IO20596\nREPORTED COMPONENT NAME\n ITDI MULTIPLATF\nREPORTED COMPONENT ID\n 5724D9960\nREPORTED RELEASE\n 720\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2014-02-18\nCLOSED DATE\n 2014-02-18\nLAST MODIFIED DATE\n 2014-02-18\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n IO20582 [http://www-01.ibm.com/support/docview.wss?uid=swg1IO20582]\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q230", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n ITDI MULTIPLATF\nFIXED COMPONENT ID\n 5724D9960", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q230", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "8.0.0.3: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24035488]\n8.0.0.4: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24037623]\n8.0.0.5: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24040426]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q230", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Customer noticed following exception during Transaction\n rollback.\n\n com.ibm.ws.gridcontainer.exceptions.PersistTLJInternalContextExc\n eption:\n java.io.NotSerializableException:\n com.cmb.businessengine.common.computegrid.fileimport.message.Imp\n ortRun", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q230", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of WebSphere Compute Grid *\nVersion 8. *\n\nPROBLEM DESCRIPTION: A PersistTLJInternalContextException: *\njava.io.NotSerializableException is *\nthrown during a transaction rollback. *\n\nRECOMMENDATION: *\n\n Job context is persisted during a\n transaction rollback even if\n persistence was not requested. This\n may result in a PersistTLJInternalContextException.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q230", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The job context is not persisted during a transaction rollback\n if persistence was not requested.\n The fix for this APAR is currently targeted for inclusion in\n fixpack 8.0.0.3.\n Please refer to the Recommended Updates page for delivery\n information:\n http://www.ibm.com/support/docview.wss?uid=swg27022998 [http://www.ibm.com/support/docview.wss?uid=swg27022998]\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q230", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM90226\nREPORTED COMPONENT NAME\n WXD COMPUTE GRI\nREPORTED COMPONENT ID\n 5725C9301\nREPORTED RELEASE\n 800\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-05-31\nCLOSED DATE\n 2013-08-13\nLAST MODIFIED DATE\n 2013-08-13\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n PM93368 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM93368]", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q230", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WXD COMPUTE GRI\nFIXED COMPONENT ID\n 5725C9301", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q230", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R800 PSY\n UP", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q230", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Solaris [http://www-01.ibm.com/support/docview.wss?uid=swg24014824]\n6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for HP-UX [http://www-01.ibm.com/support/docview.wss?uid=swg24014827]\n6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Linux [http://www-01.ibm.com/support/docview.wss?uid=swg24014826]\n6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for Linux [http://www-01.ibm.com/support/docview.wss?uid=swg24014331]\n6.1.0.3: WebSphere Application Server V6.1.0 Fix Pack 3 for Linux [http://www-01.ibm.com/support/docview.wss?uid=swg24013772]\n6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24014825]\n6.1.0.3: WebSphere Application Server V6.1.0 Fix Pack 3 for Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24013830]\n6.1.0.7 WebSphere Application Server V6.1 Fix Pack 7 for AIX [http://www-01.ibm.com/support/docview.wss?uid=swg24014799]\n6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for AIX [http://www-01.ibm.com/support/docview.wss?uid=swg24014327]\nPK29441; 6.1.0.1: Repeated admc0001e messages into log files [http://www-01.ibm.com/support/docview.wss?uid=swg24013152]\n6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for i5/OS [http://www-01.ibm.com/support/docview.wss?uid=swg24014332]\n6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for i5/OS [http://www-01.ibm.com/support/docview.wss?uid=swg24014873]\n6.1.0.3: WebSphere Application Server V6.1.0 Fix Pack 3 for HP-UX [http://www-01.ibm.com/support/docview.wss?uid=swg24013747]\n6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for HP-UX [http://www-01.ibm.com/support/docview.wss?uid=swg24014328]\n6.1.0.3: WebSphere Application Server V6.1.0 Fix Pack 3 for i5/OS [http://www-01.ibm.com/support/docview.wss?uid=swg24013794]\n6.1.0.3: WebSphere Application Server V6.1.0 Fix Pack 3 for AIX [http://www-01.ibm.com/support/docview.wss?uid=swg24013746]\n6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24014336]\nJava SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24020073]\nJava SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24021203]\nJava SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24024201]\n6.1.0.31: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24026453]\n6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere [http://www-01.ibm.com/support/docview.wss?uid=swg24027786]\n6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24025191]\n6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere [http://www-01.ibm.com/support/docview.wss?uid=swg24028574]\n6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere [http://www-01.ibm.com/support/docview.wss?uid=swg24029525]\n6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24030426]\n6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24031035]\n6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24031963]\n6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24033270]\n6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47 [http://www-01.ibm.com/support/docview.wss?uid=swg24035508]\n6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24035649]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q230", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The following exception is filling up log files in websphere\n V6.0.2.9 ND/Base environment :\n\n [6/19/06 9:34:19:216 PDT] 0000003e JMXObjectOutp E ADMC0001E:\n Unable to serialize object: com.sun.jndi.ldap.LdapCtx@2bbf257a\n\n [6/19/06 9:34:19:366 PDT] 0000003e GenericSerial E ADMC0008E:\n The system failed to marshall the object of type\n\n [Ljava.lang.Object;: com.sun.jndi.ldap.LdapCtx\n\n These errors are logged several times per second.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q230", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Ignore messages and increase file system space.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q230", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: WebSphere Application Server version 6 *\nusers. *\n\nPROBLEM DESCRIPTION: java.io.NotSerializableException *\nrepeatedly written to server log. *\n\nRECOMMENDATION: *\n\n Notification code receives a java.io.NotSerializableException\n while attempting to send a message. It then queues the message\n to try and send again.\n This results in repeated java.io.NotSerializableException\n entries in the server log:\n\n java.io.NotSerializableException: com.sun.jndi.ldap.LdapCtx\n at java.io.ObjectOutputStream.writeObject0(ObjectOutpu\n tStream.java(Compiled Code))\n at java.io.ObjectOutputStream.defaultWriteFields(Object\n OutputStream.java(Inlined Compiled Code))\n at java.io.ObjectOutputStream.writeSerialData(ObjectOutput\n Stream.java(Compiled Code))\n at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOu\n tputStream.java(Compiled Code))\n at java.io.ObjectOutputStream.writeObject0(ObjectOutputStre\n am.java(Compiled Code))\n at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutp\n utStream.java(Compiled Code))\n at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutp\n utStream.java(Compiled Code))\n at java.lang.Throwable.writeObject(Throwable.java:679)\n ....", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q230", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The notification code has been updated to not retry sending the\n message if it results in a\n java.io.NotSerializableException exception.\n\n The fix for this APAR is currently targeted for inclusion\n in fixpacks 6.0.2.15 and 6.1.0.3.\n Please refer to the recommended updates page for delivery\n information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q230", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PK29441\nREPORTED COMPONENT NAME\n WEBSPH APP SERV\nREPORTED COMPONENT ID\n 5724J0800\nREPORTED RELEASE\n 60I\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2006-08-07\nCLOSED DATE\n 2006-08-14\nLAST MODIFIED DATE\n 2006-10-18\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\nADMIN JMX", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q230", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBSPH APP SERV\nFIXED COMPONENT ID\n 5724J0800", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q230", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R60A PSY\n UP\nR60H PSY\n UP\nR60I PSY\n UP\nR60P PSY\n UP\nR60S PSY\n UP\nR60W PSY\n UP\nR61A PSY\n UP\nR61H PSY\n UP\nR61I PSY\n UP\nR61P PSY\n UP\nR61S PSY\n UP\nR61W PSY\n UP\n\nz/os DIRECT LINKS TO FIXES\n7.1.1-TIV-TDI-FP0008 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Directory+Integrator&fixids=7.1.1-TIV-TDI-FP0008&source=SAR]\n7.1.1-TIV-TDI-FP0004 [http://www-01.ibm.com/support/docview.wss?uid=swg24038511]\n7.1.1-TIV-TDI-FP0005 [http://www-01.ibm.com/support/docview.wss?uid=swg24040693]\n7.1.1-TIV-TDI-FP0006 [http://www-01.ibm.com/support/docview.wss?uid=swg24043146]\n7.1.1-TIV-TDI-FP0007 [http://www-01.ibm.com/support/docview.wss?uid=swg24044377]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q230", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "PROBLEM: \"tdisrvctl -op status\" not showing Config name, only\n Assembly Lines\n\n # tdisrvctl -op status\n-- Configs ---\n\n None\n-- AssemblyLines ---\n\n ...\n\n tdisrvctl.log shows error:\n\n 2013-09-18 13:55:24,848 ERROR [tdisrvctl] - CTGDJB125E Unable to\n get list of all running Configs.\n 2013-09-18 13:55:24,850 ERROR [tdisrvctl] - error unmarshalling\n return; nested exception is:\n java.io.WriteAbortedException: writing aborted;\n java.io.NotSerializableException:\n com.ibm.di.config.xml.MetamergeConfigXML$LazyConfigProtector\n sun.rmi.server.UnicastRef.invoke(UnicastRef.java:185)\n com.ibm.di.api.remote.impl.ConfigInstanceImpl_Stub.getConfigura\n tion(ConfigInstanceImpl_Stub.java:386)\n com.ibm.di.cli.RemoteServerCommand.getRunningConfig(RemoteServe\n rCommand.java:3016)\n com.ibm.di.cli.RemoteServerCommand.viewStatus(RemoteServerComma\n nd.java:2329)\n com.ibm.di.cli.RemoteServerCommand.execStatus(RemoteServerComma\n nd.java:1597)\n com.ibm.di.cli.RemoteServerCommand.serverControlCommand(RemoteS\n erverCommand.java:294)\n com.ibm.di.cli.RemoteServerCommand.main(RemoteServerCommand.jav\n a:230)\n Caused by: java.io.WriteAbortedException: writing aborted;\n java.io.NotSerializableException:\n com.ibm.di.config.xml.MetamergeConfigXML$LazyConfigProtectorwrit\n ing aborted; java.io.NotSerializableException:\n com.ibm.di.config.xml.MetamergeConfigXML$LazyConfigProtector\n java.io.ObjectInputStream.readObject0(ObjectInputStream.java:13\n 50)\n java.io.ObjectInputStream.readObject(ObjectInputStream.java:365\n )\n java.util.HashMap.readObject(HashMap.java:875)\n ...\n\n STEPS TO DUPLICATE: See above\n\n DESIRED BEHAVIOR: Show name of Config", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q230", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "PATCH available from ITDI L2 Support", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q230", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Problem with tdisrvctl", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q230", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This is bug in TDI code and has been fixed, formal fix will be\n made available in 7.1.1-TIV-TDI-FP0004.\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q230", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IO20121\nREPORTED COMPONENT NAME\n ITDI MULTIPLATF\nREPORTED COMPONENT ID\n 5724D9960\nREPORTED RELEASE\n 711\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2013-11-28\nCLOSED DATE\n 2013-12-03\nLAST MODIFIED DATE\n 2013-12-03\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q230", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n ITDI MULTIPLATF\nFIXED COMPONENT ID\n 5724D9960", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q230", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "The class name at the end of the exception is the object that does not implement the java.io.Serializable or java.io.Externalizable interface. In most instances, this object is the attribute that was put into the session object; however, sometimes this object is referenced by an attribute of the session object.\n\n To determine which attribute of the session object references this non-serializable object, access the SessionInspectServlet.", "logical_doc_id": 5, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q230", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Implement the Java.io.Serializable or Java.io.Externalizable interface\n\nWith persistent sessions enabled, any object that is put into the HTTPSession must implement the serializable interface in order for session manager to store the session data outside of JVM.\n\nWhen PMI is enabled, there is a counter for session data size. In order to evaluate this counter, the session data must be serialized into a byte array stream. Any object that is put into the HTTPSession must implement the serializable interface in order for session manager to convert the session data objects into byte array stream.\n\nFor example:\n\npublic classMyObject implementsSerializable{\n}//end of class MyObject\n\nCheck that all objects placed in the HTTPSession implement the java.io.Serializable or java.io.Externalizable interface.\n\n1. Acess the SessionInspectServlet\n\nIf the class name printed in the exception is not an object that is explicitly placed into the HTTPSession, use the SessionInspectServlet to determine the attribute in the HTTPSession that references a non-serializable object.\n\nSessionInspectServlet helps application writers to determine if application is written to support session persistence. SessionInspectServlet helps to:\nDetermine attributes present in the session\nDetermine serializable and non-serializable attributes in the session\nDetermine the size of each serializable attribute in session\nDetermine if serializable attribute is implemented properly (if serializable attribute and all its internals are serializable)\n\nServlet serializes and deserializes attributes into memory to simulate session persistence; therefore, application writers need not turn on session persistence to run this servlet. However, you can run it with persistent sessions enabled.\n\nHow to Access the SessionInspectServlet:\n 1. com.ibm.ws.webcontainer.httpsession.SessionInspectServlet is shipped with WebSphere Application Server. It is already in the classpath and does not need to be added to the application.\n\nDefine a servlet/uri entry for class SessionInspectServlet. If ServeServletsByClassnameEnabled is set to true (check the ibm-web-ext.xmi file in the WEB-INF directory of your webModule) in your webModule, servlet/uri definition is not needed.\n\n2. Restart your Web module.\n\n3. Open a browser and access your Web module from the browser, then navigate the application in the browser to populate the session.", "logical_doc_id": 5, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q230", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "4. Press Crtl+N to open a new browser, then access the SessionInspectServlet in the new browser by calling the URI that you defined in step 2. If you are using ServeServletsbyClassname, the URI will be \"webapp_context_root\\servlet\\com.ibm.ws.webcontainer.httpsession.SessionInspectServlet\". This displays the session details at that moment. You can access the servlet as you navigate your application to determine the session contents as you go along. Note: The servlet does not support attributes in the session that are outside the WebSphere Application Server scope. That is, session contents need to be accessed by the server class loader scope.\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK", "logical_doc_id": 5, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q061", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q061", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "You are running CICS 5.2 and have a CICS IPIC connection\n stuck in Freeing state. It never goes into Released state, and\n the region must be recycled to clear.\n A dump at the time the connection was in freeing state, shows\n a Tran number associated with an IPIC session, but this task is\n no longer in the system. It issued the following message:\n DFHIS1025 APPLID Failed to attach mirror transaction xxxx on\n IPCONN IPIC. Error code is X'0619'\n This task tried to send an error response back to the client,\n but\n fails due to the connection being closed.\n There is a problem in this scenario, where we do not\n free up the session control block- ISSB. This leaves it on the\n active chain, preventing the IPCONN from ever getting to\n RELEASED\n state.\n Additional Symptom(s) Search Keyword(s): KIXREVEPH", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q061", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nAll CICS users. *\n\nPROBLEM DESCRIPTION: *\nIPCONN remain in FREEing state after a *\nmirror transaction failed to attach *\nbecause it was disable. *\n\nRECOMMENDATION: *\n. *\n\nCICS region A and region B are connected via IPIC. The IPCONN is\n in ACQUIRE status. Region A send a DPL request to region B.\n The mirror transaction in region B is disabled. Transaction CSAC\n get attached instead of the mirror transaction. DFHACP attempt\n to send an IS7 with sense code 084C0000 with message DFHIS1025\n to region A. The send failed because the IPIC socket has been\n closed. The CSAC transaction terminates without FREEing the\n receive ISSB that was allocated to the task.\n .\n The SOCKET closed causes transaction CIST to be attached to\n release the IPCONN. During the IPCONN termination the orphan\n ISSB is found causing the IPCONN to remain in FREEing state.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q061", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "DFHISZA and DFHISIS have been changed to ensure that the receive\n ISSB used to send an IS7 response to the client region is FREE\n when socket domain returned an exception.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q061", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI70623\nREPORTED COMPONENT NAME\n CICS TS Z/OS V5\nREPORTED COMPONENT ID\n 5655Y0400\nREPORTED RELEASE\n 000\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-10-13\nCLOSED DATE\n 2016-11-02\nLAST MODIFIED DATE\n 2016-12-01\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n PI67167 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI67167]\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n UI42228\n\nMODULES/MACROS\nDFHISIS DFHISZA", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q061", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n CICS TS Z/OS V5\nFIXED COMPONENT ID\n 5655Y0400", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q061", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R000 PSY UI42228 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI42228]\n UP16/11/15 P F611\n\nFIX IS AVAILABLE\nSELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL. YOU WILL BE REQUIRED TO SIGN IN. DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q061", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "An incident occurred that caused a transaction not to finish in the SFS. The incident could be a CICS region crash or a batch program abend.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q061", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "In my experience, the problem with the log volume becoming full\n\nand causing the (SFS and RQS) server to crash always has the root cause\nof the presence of a transaction being in the commitcomplete state.\nA transaction is in the commitcomplete state when all participants\nhave agreed to commit, and then one of the participants has failed to\nactually perform its commit. I will now explain why even one such\ntransaction can cause the log to fill up.\n\nAs log records are written to the log, the log will continue to become\nmore full. The log regularly checks itself to see how much free space it has.\nWhen the percent of free space is sufficiently small, say 25%, it will check\nto see if it can throw away old records. When you see the log go from 75% full\nto 1% full, that's because the oldest record for any transaction that is still alive\nis quite recent, and virtually all of the records in the log can be thrown away and their\nspace reclaimed. When a transaction is in the commitcomplete state, as far as the\nlog is concerned, that transaction is still alive. Therefore none of the log records\nput in the log since that transaction can be thrown away, and the log will fill up\nuntil the server crashes.\n\nIn other words, the log filling up is not really caused by too much work being\ndone now, but rather because there is an old unfinished transaction clogging up the log.\n\nThe normal method of handling the log filling up to a dangerous level is 2 steps:\n1) tkadmin list transaction\n\nThen examine the output and see if there are any transactions in the commitcomplete state.\nIf there are any, then for all of them, perform", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q061", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "step 2\n\n2) tkadmin force transaction -finish\n\nIf this command succeeds, then the transaction which was stuck is now dead.\nThe next time the log tries to throw away old records and reclaim space,\nit will detect that this oldest record for the stuck transaction is dead, and reclaim\nall the space for all records until a live transaction record is reached, Usually the log\nwill now have most of its space free.\n\nHowever, the force tran -finish does not explicitly reclaim space, so the log may\nstill appear to be full.\n\nIn some cases bringing down the CICS region may help to determine which transactions to perform the force on.\n\n3) tkadmin force checkpoint\n\nNow the log checks its oldest record, sees that the tran for that record is dead, and\nreclaims space as discussed above.\n\nOther DCF documents to review -\nResolving a Stuck Transaction:\nhttp://www.ibm.com/support/docview.wss?uid=swg21045910 [http://www-01.ibm.com/support/docview.wss?uid=swg21045910]\n\nExpanding CICS volumes on UNIX systems\nhttp://www.ibm.com/support/docview.wss?uid=swg21616731 [http://www-01.ibm.com/support/docview.wss?uid=swg21616731]\n\nExpanding CICS volumes - Windows Edition\nhttps://developer.ibm.com/answers/questions/165307/how-can-i-expand-the-txseries-sfs-volumes-on-windo.html [https://developer.ibm.com/answers/questions/165307/how-can-i-expand-the-txseries-sfs-volumes-on-windo.html]", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q061", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "NEWCOPY and PHASEIN are not valid for Java programs, and are ignored if specified. The command returns NORMAL because it completed without error. This is documented as follows in the CICS TS V4.2 information center under CEMT SET PROGRAM [http://publib.boulder.ibm.com/infocenter/cicsts/v4r2/topic/com.ibm.cics.ts.systemprogramming.doc/transactions/cemt/dfha7ai.html]:\n\nYou cannot specify NEWCOPY for a program specified with the HOLD option or for a Java program that runs in a JVM. Use the PERFORM JVMPOOL PHASEOUT command to refresh Java programs that run in a pooled JVM. Disable and enable the JVMSERVER resource to refresh a Java program that runs in a JVM server.\n\nYou cannot specify PHASEIN for a program specified with the HOLD option or for a Java program that runs in a JVM. Use the PERFORM JVMPOOL PHASEOUT command to refresh Java programs that run in a pooled JVM. Disable and enable the JVMSERVER resource to refresh a Java program that runs in a JVM server", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q061", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "If using CICS Transaction Server for z/OS (CICS TS) V3.1, use CEMT SET JVMPOOL PHASEOUT [http://publib.boulder.ibm.com/infocenter/cicsts/v3r2/topic/com.ibm.cics.ts.doc/dfha7/transactions/cemt/dfha7ng.html] to pull in the newest version of your Java program. This will also delete the Java Virtual Machines (JVM) when the task using each JVM is no longer dependent on it. The next time you enter your transaction, a new JVM will be built and it will use the new version of your program.\n\nIf using CICS TS 3.2 and above with pooled JVMs, enter CEMT PERFORM JVMPOOL PHASEOUT [http://publib.boulder.ibm.com/infocenter/cicsts/v4r2/topic/com.ibm.cics.ts.systemprogramming.doc/transactions/cemt/dfha7_performjvmpool.html]. Afterwards, when new JVMs are started they will run the new version of the program.\n\nIf using CICS TS 4.2 with JVM servers, enter CEMT SET JVMSERVER(jvmserver) DISABLED [http://publib.boulder.ibm.com/infocenter/cicsts/v4r2/topic/com.ibm.cics.ts.systemprogramming.doc/commands/dfha8_setjvmserver.html] then ENABLED to disable and enable the JVMSERVER [http://publib.boulder.ibm.com/infocenter/cicsts/v4r2/topic/com.ibm.cics.ts.resourcedefinition.doc/resources/jvmserver/dfha4_overview.html] resource that the Java program uses.\n\nCEMT SET JVMPOOL Phaseout, Purge, and Forcepurge functions are deprecated in CICS TS V3.2. That is why you should use the corresponding functions of the PERFORM JVMPOOL command when using CICS TS V3.2 and above.\n\nNote that CICS TS V3.2 supports Java V5. If using the shared class cache [http://publib.boulder.ibm.com/infocenter/cicsts/v4r2/topic/com.ibm.cics.ts.java.doc/topics/dfhpjd3.html], a PHASEOUT is not needed with Java V5 onwards. Any changed classes are automatically phased in to the cache as they are used.\n\nPRODUCT ALIAS/SYNONYM\n CICS/TS CICS TS CICS Transaction Server", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q061", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Why am I receiving ABEND AKEA in IODM module EKCCMTOM at offset x'1A68' when trying to run in a CICS Version 3.3.0 region? The error occurs shortly after restarting IODM without the cycling region.\n\nIn the CICS system initialization table (SIT), STGPROT is set to \"No\" and RENTPGM is set to NOPROTECT. System modifications (sysmods), UN54096 and UN60897, have been applied.", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q061", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Refer to authorized program analysis report (APAR) PN56650 for information about IODM module EKCCMTOM and program DFHZNEP. Set both programs to the EXECKEY parameter of CICS\u00ae and give them a datalocation value of \"Any.\" Also, change the queue status field (QUESTAT) of the IDPARMTB table from 'E' to 'D'. The IDPARMTB table defines system-wide Object Distribution Manager parameters vital to the system's operation. Making this change frees you from relying on the use of the send queue processing operator commands, OAQM and OAQC, that are between OID1 and OID2. OID1 is the ImagePlus Object Distribution Manager first-stage, and OID2 the second-stage, shutdown CICS transaction. OID2 completes the Object Distribution Manager shutdown.\n\nThe mode settings for program DFHZNEP state that DFHZNEP must be RMODE=any, AMODE=31. Relink your DFHZNEP as 31 bit so that DFHZNAC can link to ZNEP.\n\nWhen you relink DFHZNEP as 31 bit, expect to receive error message: IEW2646 for modules DFHZNEP, EKCCVECT, and EKCCFMSG. Error message: IEW2646I is issued when an RMODE value that is specified in the PARM statement is different than the one in the electrostatic discharge (ESD) record. Included is a binder message, which warns of a conflict. As a result, the RMODE value in the PARM statement will be used, based on the hierarchy specified in the Program Management Manual.\n\nYou might get intermittent failures in OID1 in IODM module EKCCMTOM. Continue to try the failing transaction until you receive a normal completion.\n\nAnother element to this error was revealed during its testing. The abend appears after cycling ODM but without cycling the CICS region. For example, you might first start the CICS region, then OIUP, OID1, OID2, OIUP, OID1 (which fails), OID2 (which also fails). By cycling the CICS region, the first OID1 and OID2 will function normally.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q061", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "In this situation, the second OIUP, which initializes the Object Distribution Manager, and all other functions (DISP and so on), function without incident.\nIf you use the LMODs from EKCPSTLK with the CICS330 libraries (instead of with the CICS211 libraries), OID1 and OID2 fail after the first shutdown of ODM.\nIf you cycle the whole region, OID1 and OID2 work the first time after an OIUP.\nIf you bring ODM up and then try to shut it down again, you will get the abends.\nWith the CICS330 links, the failure is consistent.\nWith the CICS211 links, the failure is intermittent.\nAdditionally, with the CICS330 modules:\nDFHECI links clean\nerror message: IEW2646I is not produced\nthe offset of the abend moves about 8 bytes\n\nNote: The error described in this document was accompanied by error message: EKC0304A return code 8 reason code 00070017 after restarting IODM without a cycling region. If you have an earlier release of IODM, see APAR PN14003 regarding the error message: EKC0304A 00070017.\n\nHISTORICAL NUMBER\n APAR PN56650", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q061", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "DFHSJ0215 [http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic/com.ibm.cics.ts.messages.doc/DFHSJ/DFHSJ0215.html] The JVM Server jvmserver failed to initialize the OSGi framework. The JVM will be terminated.\n\nDFHSJ0914 [http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic/com.ibm.cics.ts.messages.doc/DFHSJ/DFHSJ0914E.html] JVMSERVER jvmserver is DISABLED because the Language Environment Enclave was not created.", "logical_doc_id": 5, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q061", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "zFS files not propagated to target environment(s)", "logical_doc_id": 5, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q061", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "When you applied the maintenance, the zFS files were updated. However, due to a procedural error, these updated files were not rolled out to the target environments. Now that you are running JVM Servers, this has more of an impact.", "logical_doc_id": 5, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q061", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Ensure that the updated zFS files are propagated to the target environments when maintenance is applied to CICS.\n\nPRODUCT ALIAS/SYNONYM\n CICS/TS CICS TS CICS Transaction Server", "logical_doc_id": 5, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q058", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q058", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2 which is vulnerable to:\nCVE-2018-5357 CVE-2018-5358 CVE-2018-5246 CVE-2018-5247 CVE-2018-5248 CVE-2017-1000476 CVE-2017-18008 CVE-2017-17914 CVE-2017-17934 CVE-2017-18022 CVE-2017-17882 CVE-2017-17884 CVE-2017-17887 CVE-2017-17886 CVE-2017-17880 CVE-2017-17883 CVE-2017-17885 CVE-2017-17879 CVE-2017-17881 CVE-2017-17499 CVE-2017-17504\n\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\n\nFLASH (ALERT)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q058", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q058", "section_id": 3, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2017-2619, CVE-2017-5509, CVE-2017-5510, CVE-2017-7275, CVE-2016-10228.\n\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2.\n\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\nPRODUCT ALIAS/SYNONYM\n WMB HVE IIB HVE\n\nFLASH (ALERT)", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q058", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q058", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2016-5010, CVE-2016-7906, CVE-2017-4606, CVE-2017-7606, CVE-2017-7619, CVE-2017-794, CVE-2017-7942, CVE-2017-7943, CVE-2017-8343, CVE-2017-8344, CVE-2017-8345, CVE-2017-8346, CVE-2017-8347, CVE-2017-8348, CVE-2017-8349, CVE-2017-8350, CVE-2017-8351, CVE-2017-8352, CVE-2017-8353, CVE-2017-8354, CVE-2017-8355, CVE-2017-8356, CVE-2017-8357, CVE-2017-8765, CVE-2017-8830\n\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2.\n\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\nPRODUCT ALIAS/SYNONYM\n WMB HVE IIB HVE\n\nFLASH (ALERT)", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q058", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux .", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q058", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with a version of Red Hat Enterprise Linux (RHEL) Server vulnerable to CVE-2017-15217,CVE-2017-15218\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as needed.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\nPRODUCT ALIAS/SYNONYM\n WMB HVE IIB HVE\n\nFLASH (ALERT)", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q058", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat (CVE-2015-7547)", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q058", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to GNU C Library (glibc) - stack-based buffer overflow (CVE-2015-7547)\n\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2.\n\nRemediation:\n\nIBM strongly recommends that you contact Red Hat provider to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2 as applicable", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q058", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "google [https://googleonlinesecurity.blogspot.com/2016/02/cve-2015-7547-glibc-getaddrinfo-stack.html]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\nPRODUCT ALIAS/SYNONYM\n WebSphere Message Broker WMB IBM Integration Bus IIB", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q220", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Transport Layer Security (TLS) padding vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) like attack affects TPF Toolkit.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q220", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVE-ID: CVE-2014-8730 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8730]\n\nDESCRIPTION: Product could allow a remote attacker to obtain sensitive information, caused by the failure to check the contents of the padding bytes when using CBC cipher suites of some TLS implementations. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) like attack to decrypt sensitive information and calculate the plaintext of secure connections.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/99216 [https://exchange.xforce.ibmcloud.com/vulnerabilities/99216] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q220", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "TPF Toolkit 3.6.x, 4.0.x, and 4.2.x", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q220", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "All current versions of TPF Toolkit ship JREs that are not impacted by this vulnerability. However, TPF Toolkit provides a Remote System Explorer (RSE) daemon that runs on Linux for System z. This daemon relies on the Java that is installed on that system. Ensure that the Java level currently installed on your Linux for System z system is up to date. The minimum level of Java that is required includes the fix for vulnerability CVE-2013-0169 [http://www.ibm.com/support/docview.wss?uid=swg1IV37656].", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q220", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q220", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q220", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 19 December 2014: Original version published\nThe 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\nCVE-2014-8730 SECURITY BULLETIN", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q220", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM Security Access Manager version 8.0.0.5 for DataPower is affected by a TLS padding vulnerability, which could allow a remote attacker to obtain sensitive information.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q220", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "The following vulnerability affects IBM Security Access Manager version 8.0.0.5 for DataPower.\nCVEID: CVE-2014-8730 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8730]\n\nDESCRIPTION: IBM Security Access Manager for DataPower could allow a remote attacker to obtain sensitive information, caused by the failure to check the contents of the padding bytes when using CBC cipher suites of some TLS implementations. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) like attack to decrypt sensitive information and calculate the plaintext of secure connections.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See http://xforce.iss.net/xforce/xfdb/99216 [http://xforce.iss.net/xforce/xfdb/99216] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q220", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Security Access Manager version 8.0.0.5 for DataPower in all WebSphere DataPower Gateway appliances version 7.1.0.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q220", "section_id": 4, "heading": "WORKAROUNDS AND MITIGATIONS", "parent": null, "text": "The following steps describe how to mitigate this vulnerability for the affected releases. You should verify applying this configuration change does not cause any compatibility issues.\n\nMitigation for IBM Security Access Manager for DataPower 8.0.0.5\n\n1. Select Objects > Security Access Manager > Access Manager Reverse Proxy from the WebGUI navigation panel.\n 2. Select the Reverse Proxy instance.\n 3. Select the Manage Files tab and then the Edit button for the Configuration File property.\n 4. In the [ssl] stanza, add the bold lines below to the following two sections.\n # Specify any additional GSKit attributes which should be used when\n # initializing an SSL connection with the client. A complete list of\n # the available attributes is included in the GSKit SSL API\n # documentation.\n #\n # The configuration entry may be specified multiple times, one for each\n # GSKit attribute. The entry should be of the format:\n # gsk-attr-name = ::\n #\n # - where is one of 'enum', 'string', 'number'\n # and corresponds to the identity associated with a GSKit attribute\n # (e.g., GSK_HTTP_PROXY_SERVER_NAME = 225)\n #\n # An example configuration could be:\n # gsk-attr-name = string:225:proxy.ibm.com\n\ngsk-attr-name = enum:471:1\n\n# Specify any additional GSKit attributes which should be used when\n # initializing an SSL connection with a junctioned server. A complete\n # list of the available attributes is included in the GSKit SSL API\n # documentation.\n #\n # The configuration entry may be specified multiple times, one for each\n # GSKit attribute. The entry should be of the format:\n # jct-gsk-attr-name = ::\n #\n # - where is one of 'enum', 'string', 'number'\n # and corresponds to the identity associated with a GSKit attribute\n # (e.g., GSK_HTTP_PROXY_SERVER_NAME = 225)\n #\n # An example configuration could be:\n # jct-gsk-attr-name = string:225:proxy.ibm.com\n\njct-gsk-attr-name = enum:471:1\n 5. Click Apply to deploy the changes.", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q220", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q220", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete 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] Security Access Manager for Web Security Bulletin (CVE-2014-8730) [http://www-01.ibm.com/support/docview.wss?uid=swg21692802] ACKNOWLEDGEMENT\nNone\nThe 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.", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q220", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Transport Layer Security (TLS) padding vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) like attack affects IBM PureApplication System.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q220", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2014-8730 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8730]\nDESCRIPTION: IBM PureApplication Server bundles IBM HTTP Server, which could allow a remote attacker to obtain sensitive information, caused by the failure to check the contents of the padding bytes when using CBC cipher suites of some TLS implementations. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) like attack to decrypt sensitive information and calculate the plain text of secure connections.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/99216 [https://exchange.xforce.ibmcloud.com/vulnerabilities/99216] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q220", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "This vulnerability affects all versions and releases of IBM HTTP Server (powered by Apache) component in all editions of WebSphere Application Server and bundling products. IBM PureApplication Server bundles WebSphere Application Server in its Web Application Pattern.\n\nIBM PureApplication System V1.1\nIBM PureApplication System V2.0\nIBM PureApplication System V2.1", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q220", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "The solution is to apply an update to the Web Application pattern type included in IBM PureApplication System:\n\nIBM PureApplication System V2.1\n*\nhttp://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=2.1.0.1&platform=All&function=fixId&fixids=webapp-2.0.4.1-sys&includeSupersedes=0\n*\n*\nhttp://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=2.1.0.1&platform=All&function=fixId&fixids=webapp-1.0.4.1-sys&includeSupersedes=0\n\nIBM PureApplication System V2.0\n*\nhttp://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=2.0.0.1&platform=All&function=fixId&fixids=webapp-2.0.2.1-vaea-20150610&includeSupersedes=0\n\nIBM PureApplication System V1.1 and earlier:\n*\nYou should verify applying this fix does not cause any compatibility issues. WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q220", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q220", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 2, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q220", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 19 June 2015: Original Version Published\nThe 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\nCVE-2014-8730 SECURITY BULLETIN", "logical_doc_id": 2, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q220", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Transport Layer Security (TLS) padding vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) like attack affects IBM Rational ClearCase.", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q220", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVE-ID: CVE-2014-8730 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8730]\nDescription: IBM Rational ClearCase could allow a remote attacker to obtain sensitive information, caused by the failure to check the contents of the padding bytes when using CBC cipher suites of some TLS implementations. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) like attack to decrypt sensitive information and calculate the plaintext of secure connections.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/99216 [https://exchange.xforce.ibmcloud.com/vulnerabilities/99216] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q220", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "CMI and OSLC integrations (Windows platform)\nThe vulnerable component is used when ClearCase on Windows platforms is configured to integrate with IBM Rational ClearQuest or Rational Team Concert with communication over SSL (https). This applies to Base CC/CQ integrations using Change Management Interface (CMI) and to UCM-enabled CQ integration via OSLC. The UCM-enabled CQ integration without using OSLC (SQUID) is not sensitive to this attack.\nThe integrations may be used by Windows clients directly, or by a Windows CCRC WAN server/CM Server.\n\nClearCase Windows Client or CCRC WAN Server/CM Server Version Status 8.0.1.x Affected if you use CMI or OSLC integrations 8.0.0.5 and higher Affected if you use CMI or OSLC integrations 7.1.2.9 and higher Affected if you use CMI or OSLC integrations 7.0.x, 7.1.0.x, 7.1.1.x Not affected\nNote: Linux/UNIX clients using CMI or OSLC integrations are not affected. Linux/UNIX WAN servers are not affected by this vulnerability in CMI/OSLC, but are affected by a vulnerability in IBM HTTP Server (IHS).\nCCRC WAN Server (All platforms)\n\nThe vulnerable component is also used by CCRC WAN server (all platforms) and CM Server for ClearCase (all platforms) when supporting SSL connections with IBM HTTP Server.\n\nClearCase server version Status of IHS vulnerability 8.0.1.x (CCRC WAN server) Affected (all platforms) if you use SSL 8.0.0.x (CCRC WAN server) Affected (all platforms) if you use SSL 7.1.2.x (CM Server) Affected (all platforms) if you use SSL 7.1.1.x (CM Server) Affected (all platforms) if you use SSL 7.1.0.x (CM Server) Affected (all platforms) if you use SSL REMEDIATION/FIXES\nInstall the appropriate fix pack on your Windows systems running the vulnerable integration code (clients and servers):\n\nAffected Versions Applying the fix to Windows clients using an integration 8.0.1.x Install Rational ClearCase Fix Pack 7 (8.0.1.7) for 8.0.1 [http://www.ibm.com/support/docview.wss?uid=swg24039409] 8.0.0.x Install Rational ClearCase Fix Pack 14 (8.0.0.14) for 8.0 [http://www.ibm.com/support/docview.wss?uid=swg24039407] 7.1.2.x\n7.1.1.x\n7.1.0.x Customers on extended support contracts should install Rational ClearCase Fix Pack 17 (7.1.2.17) for 7.1.2 [http://www.ibm.com/support/docview.wss?uid=swg24039405] You should verify applying this fix does not cause any compatibility issues.", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q220", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "In addition to the above fix pack, you should install a fix for IBM HTTP server on your CCRC WAN server/CM Server host(s). Apply the fixes listed in Security Bulletin: TLS padding vulnerability affects IBM HTTP Server (CVE-2014-8730) [http://www.ibm.com/support/docview.wss?uid=swg21692502]. To install a fixpack or interim fix for IHS as referenced in that bulletin, follow the guidance in this table:\n\nAffected ClearCase Versions Applying an IHS Fix 8.0.0.x, 8.0.1.x Install the IHS fixes to your installation, following the instructions from the IHS security bulletin. (IHS is installed and maintained separately for ClearCase 8.0.x.) 7.1.0.x\n7.1.1.x\n7.1.2.x Document 1390803 [http://www.ibm.com/support/docview.wss?uid=swg21390803] explains how to update IHS for ClearCase CM Servers at release 7.1.x. Consult those instructions when applying the fix. Install the IHS fixes listed in the IHS security bulletin referenced above.\n\nYou should verify applying this configuration change does not cause any compatibility issues. GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.\n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.", "logical_doc_id": 3, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q220", "section_id": 3, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 3, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q220", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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\n22 December 2014: Original copy published\n19 January 2015: revised to refer to fixes for IBM HTTP Server\n18 March 2015: revised to refer to fix packs with final fixes\nThe 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.", "logical_doc_id": 3, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q220", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM Tivoli/Security Directory Server (ITDS/ISDS) as a component of IBM Tivoli Network Performance Manager Wireless Platform are affected by a TLS padding vulnerability, which could allow a remote attacker to obtain sensitive information", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q220", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "The following vulnerability affects IBM Security Directory Server as a component of IBM Tivoli Network Performance Manager Wireless Platform\n\nCVEID: CVE-2014-8730 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8730]\n\nDESCRIPTION: IBM Security Directory Server could allow a remote attacker to obtain sensitive information, caused by the failure to check the contents of the padding bytes when using CBC cipher suites of some TLS implementations. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) like attack to decrypt sensitive information and calculate the plaintext of secure connections.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/99216 [https://exchange.xforce.ibmcloud.com/vulnerabilities/99216] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q220", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Affected Product and Version(s) Product and Version shipped as component Tivoli Network Performance Manager 1.4 ITDS 6.3 Tivoli Network Performance Manager 1.3.2 ITDS 6.3 Tivoli Network Performance Manager 1.3.1 ITDS 6.2 REMEDIATION/FIXES\nApply an interim fix based on the impacted version from URL below:- http://www-01.ibm.com/support/docview.wss?uid=swg21692906 [http://www-01.ibm.com/support/docview.wss?uid=swg21692906]", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q220", "section_id": 3, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q220", "section_id": 4, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 4, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q220", "section_id": 5, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 18 December 2014: original version\nThe 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.", "logical_doc_id": 4, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q081", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q081", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Error Message: Files in the /tmp/.com_ibm_tools_attach\n directory, such as _attachlock, _master, and _notifier, have\n unnecessary execute permissions.\n Only owner, group, and world read and write permissions are\n required.\n .\n Stack Trace: N/A\n .", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q081", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Run:\n chmod 666 /tmp/.com_ibm_tools_attach/_*\n Do not change permissions on directories.\n Do not remove any read or write permissions on _attachlock,\n _master, and _notifier as this will delay VM shutdown.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q081", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "The Java VM was creating files with unnecessarily broad\n permissions, creating security concerns. It was also not\n handling the case where certain files had incorrect permissions.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q081", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This defect will be fixed in:\n 6.0.1 SR2\n 7.0.0 SR1\n 6.0.0 SR11\n .\n The default permissions for the attach API common files have\n been changed.? The recovery algorithm was fixed to handle files\n with insufficient permissions.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q081", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV20654\nREPORTED COMPONENT NAME\n J9 COMMON CODE\nREPORTED COMPONENT ID\n 620700127\nREPORTED RELEASE\n 260\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2012-05-04\nCLOSED DATE\n 2012-05-08\nLAST MODIFIED DATE\n 2012-05-08\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q081", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n J9 COMMON CODE\nFIXED COMPONENT ID\n 620700127", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q081", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R260 PSY\n UP\nR600 PSY\n UP", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q081", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "CIWEB Error: com.ibm.ecm.beans.viewer.DocServicesSessionBean$ICNStreamingDocServices.\n_loadDocument java.io.IOException: No such file or directory", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q081", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "ICN creates a subdirectory under UNIX: /tmp or Windows:\\temp for temporary file storage. On some systems, automated housecleaning procedures at OS level delete the contents of /tmp and its subdirectories, resulting in the error.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q081", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "On startup, ICN sets the variable ENGINE_TEMPDIR which defines a temporary directory, for example:\n'/tmp/ECMClient.IBMWebSphereApplicationServer80.navigator.tmpdir' .\nVerify the directory path and check whether the directory exists or has been deleted.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q081", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "There are two ways to resolve the problem:\n\n1) Disable the automation which deletes the contents of /tmp. Some Linux systems for example use a 'tmpwatch' process which deletes files in /tmp. For tmpwatch, an 'EXCLUDE' job parameter can be defined, causing the process to skip the named subdirectory.\n2) ICN uses the Java Virtual Machine (JVM) default temp file directory, which can be overridden at JVM level by adding the Java system property java.io.tmpdir. For example, specify \"-Djava.io.tmpdir=/var/temp\" in the application server startup configuration. Note that this setting is JVM-wide and will affect all applications running on the application server.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q081", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Resource tracker files are accumulating in /tmp or %TEMP%. What are the steps for disabling the Resource Tracker or moving the output files to a different directory?", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q081", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The Resource Tracker logs the processor, memory, and I/O usage on each computer that runs parallel jobs. The machine log files are created by the DataStage Resource Tracker program.\n\nThere will be machine log files in /tmp or %TEMP%\n\nThe Resource Tracker uses a lot of memory and a lot of swap space, therefore you may want to consider disabling it or moving the logs it generates to a different directory", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q081", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "The resource_tracker is controlled by a file located in PXEngine/etc named restrack_settings. The format is shown in the following example:\n\nLOGGING_INTERVAL=4\nRUN_TIMEOUT=0\nLOG_INCREMENT_INTERVAL=86400\nCLEANUP_INTERVAL=432000\nHANDLE_DIRECTORY=/tmp\nLOG_DIRECTORY=/tmp\n\nHere the logging interval is set to 4 or every 4 seconds write to the active log. The log increment interval is 86400 seconds or every 24 hours close the current log and start a new log. The cleanup interval is set to 432000 seconds or every 5 days delete logs greater than 5 days old. Lastly, the handle and log directory is set to /tmp or where the pid and logs are written.\n\nFiles in /tmp:\n\nresource_tracker.8001.log - activity log file\napt_resource_track.8001.wb-machine - current settings in effect and resource_tracker process pid\nmachineLog.8001.wb-machine.20080508100536 - machine log data file(s)\n\nThe file that contains the activity for the resource_tracker is named resource_tracker.8001.log. In this log, you can see how the log manager rolls over the log files after the defined time of 86400 seconds or 24 hours and deletes log files older than 432000 seconds or 5 days. Below is a snapshot of a resource_tracker log file:\n\n##IIIS-DSEE-TRES-0000310:05:37(000)Resource Tracker Log\n##IIIS-DSEE-TRES-0000810:05:37(001)Opening log file: /tmp/machineLog.8001.hawkcewin01.20080508100536.\n##IIIS-DSEE-TRES-0000910:05:37(000)Closing log file.\n##IIIS-DSEE-TRES-0000810:05:37(001)Opening log file: /tmp/machineLog.8001.hawkcewin01.20080509100537.\n##IIIS-DSEE-TRES-0001010:05:37(002)Removing old log: machineLog.8001.hawkcewin01.20080502061733.\n##IIIS-DSEE-TRES-0001010:05:37(003)Removing old log: machineLog.8001.hawkcewin01.20080503061735.\n##IIIS-DSEE-TRES-0001010:05:37(004)Removing old log: machineLog.8001.hawkcewin01.20080504061737.\n##IIIS-DSEE-TRES-0000910:05:38(000)Closing log file.\n##IIIS-DSEE-TRES-0000810:05:38(001)Opening log file: /tmp/machineLog.8001.hawkcewin01.20080510100538.\n##IIIS-DSEE-TRES-0001010:05:38(002)Removing old log: machineLog.8001.hawkcewin01.20080505061739.\n##IIIS-DSEE-TRES-0000910:05:42(000)Closing log file.\n##IIIS-DSEE-TRES-0000810:05:42(001)Opening log file: /tmp/machineLog.8001.hawkcewin01.20080511100542.\n\nYou can either move the location of the files or disable the resource_tracker from starting.\nIn order to move the location to which the files are generated, edit the restrack_settings file in PXEngine/etc directory.\n\nThen, restart the DataStage Engine for the settings to take affect.\nTo disable the resource_tracker from starting:\n\nUnix/Linux Platforms\n\nAdd the following to the dsenv file:\n\nAPT_DISABLE_TRACKER_STARTUP=1; export APT_DISABLE_TRACKER_STARTUP\n\nThen, restart the DataStage Engine for the settings to take affect.\n\nor\n\nAdd the following to the System Environment variables:\n\nAPT_DISABLE_TRACKER_STARTUP=1\n\nThen, restart the DataStage Engine for the settings to take effect.\n\nWindows Platforms\n\nAdd the following to the System Environment variables:\n\nAPT_DISABLE_TRACKER_STARTUP=1\n\nReboot the machine.\n\nThe resource_tracker is started by the same script that starts the JobMonApp. The script is located in the PXEngine/java directory and it is named jobmoninit. In the jobmoninit script there is a bit of code that looks like this:\n\n# startup resource tracker", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q081", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "if [ \"$APT_DISABLE_TRACKER_STARTUP\"X = \"X\" ] ; then\nif [ -z \"$rtlist\" ] ; then\n\nSo, if APT_DISABLE_TRACKER_STARTUP is set, it will not start the resource_tracker here either.\n\nOn Unix (but NOT Windows) it is possible to have two instances for DataStage installed and running on the same Engine tier machine. However, multiple instances for of the Resource Tracker will interfere with each other unless some adjustments are made. Users can either:\n 1. Disable on instance of the resource tracker by setting APT_DISABLE_TRACKER_STARTUP in the dsenv file for one of the Datastage instances\n\n2. Edit the the PXengine/bin/restrack_settings file for one of the instances and change the following values in one of the instances:\n\nHANDLE_DIRECTORY=/tmp\n LOG_DIRECTORY=/tmp\n\nso that they point to a different directory than the values for the other instance. Be sure that the directories exist and have the right permissions.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q081", "section_id": 0, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Reviewing BAR files, by using the mqsireadbar command, shows that the contents of BAR files created with the Toolkit and command line are not exactly the same.\nThe resources in the BAR file created in the Toolkit are not compiled by default, so it includes all resources (.msgflows and .esql files) in the library or application. This indicates that you did not select the build option \"Compile and in-line resources\" when creating the BAR file.\n\nThe resources in the BAR file created with the mqsi command are compiled (.cmf) files, so the compiled message flows already have the ESQL code embedded in the .cmf, and some .esql files are not added as individual resources.", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q081", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To correct the issue, add the parameter -deployAsSource when building the BAR file using the mqsi command. By using this parameter, the source .esql and .msgflow files are included explicitly in the BAR file, instead of the .cmf.\n\nThe default options used to build both BAR files are not exactly the same for the Toolkit and mqsicreatebar command. When the BAR file is built using the Toolkit, the option \"Compile and in-line resources\" is not selected by default, but this option is enabled by default in the mqsicreatebar command.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Linux, Windows 9.0 All Editions\nPRODUCT ALIAS/SYNONYM\n WMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q081", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "tmp; temp; agent; AgentReadError; error 0 creating; .retag encountered an error during variable expansion; value 'Check_${BF_SERVER}_${BF_BID}' expanded to 'AgentReadError'; 1306611; PK67083; RATLC01066091; ifix03; ifix3; ifix 3; ifix 03; 7.0.2-ifix3; 7.0.2-ifix03 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)", "logical_doc_id": 5, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q081", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "After a project run that performs a .bset or .retag, a number of 0-length files are left in the %TEMP% directory on the agent host.\n\nDirectory of C:\\DOCUME~1\\user\\LOCALS~1\\Temp\n\n06/03/2008 03:04 PM 0 bf2A0.tmp\n06/03/2008 03:04 PM 0 bf2A2.tmp\n06/03/2008 03:05 PM 0 bf2A4.tmp\n06/03/2008 03:05 PM 0 bf2A6.tmp\n06/03/2008 03:05 PM 0 bf2AA.tmp\n06/03/2008 03:05 PM 0 bf2AC.tmp\n06/03/2008 03:05 PM 0 bf2AE.tmp\n06/03/2008 03:05 PM 0 bf2B1.tmp\n06/03/2008 03:06 PM 0 bf2B3.tmp\n\nIf these files build up for a while, they can lead to more severe agent failures due to Windows OS limitations, such as the following Agent error:\n\n\".retag encountered an error during variable expansion, value 'Check_${BF_SERVER}_${BF_BID}' expanded to 'AgentReadError'.\"\ncommand line error = \"error 0 creating/accessing temporary file\"", "logical_doc_id": 6, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q081", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "This is a resolved defect against the Build Forge Agent, APAR PK67083.", "logical_doc_id": 6, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q081", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "This defect, APAR PK67083 [http://www.ibm.com/support/docview.wss?uid=swg1PK67083], has been resolved in Build Forge iFix3 for version 7.0.2 [http://www.ibm.com/support/docview.wss?&rs=3099&uid=swg21254846]. The functionality now cleans up the files that are created in %TEMP%, but if this issue has already occurred, you will need to delete the files as detailed in the workaround.\n\nWORKAROUND:\n\nThe upgrade prevents the problem from occurring, but it does not clean up files that have already been left in the %TEMP, and you will need to remove the files as detailed by this workaround.\n\nDelete all bf*.tmp files from %TEMP% on a regular basis. You may want to code a script to clear the %TEMP% directory on the agent host before or after each project run.", "logical_doc_id": 6, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q304", "section_id": 0, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Fix packs for DataPower XML Security Gateway version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034955]\nFix packs for DataPower B2B Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034956]\nFix packs for DataPower Integration Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034957]\nFix packs for DataPower Low Latency Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034958]\nFix packs for DataPower Service Gateway version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034959]\nFix packs for DataPower Service Gateway version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036407]\nFix packs for DataPower B2B Appliance version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036409]\nFix packs for DataPower Integration Appliance version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036410]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q304", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Using SFTP to query for file that does not exist (STAT command),\n DataPower returns error code 4 (Failure) instead of 2 (Not\n Found).", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q304", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Affected is the use of a Multi-Protocol Gateway with a\n SFTP Server Front Side Handler as a proxy to a SFTP backend.\n\nAfter a query for file that doesn't exist (STAT command)\n DataPower returns error code 4 (Failure) instead of 2 (Not\n Found).", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q304", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fix is available in 6.0.0.6 and 6.0.1.2.\n\nFor a list of the latest fix packs available, please see:\n http://www-01.ibm.com/support/docview.wss?uid=swg21237631 [http://www-01.ibm.com/support/docview.wss?uid=swg21237631]\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q304", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT00246\nREPORTED COMPONENT NAME\n DATAPOWER\nREPORTED COMPONENT ID\n DP1234567\nREPORTED RELEASE\n 600\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-03-14\nCLOSED DATE\n 2014-04-24\nLAST MODIFIED DATE\n 2014-05-26\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q304", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n DATAPOWER\nFIXED COMPONENT ID\n DP1234567", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q304", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R600 PSN\n UP\nR601 PSN\n UP", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q304", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM API Connect V5.0.3.0 is available which addresses several APARs, and includes product enhancements.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q304", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM API Connect V5.0.3.0 is now available, which provides important development and APAR fixes, and includes product enhancements as well as a more consistent user experience.\n\nFor information on new features that have been included in V5.0.3.0, see What's new for this release [https://www.ibm.com/support/knowledgecenter/SSMNED_5.0.0/com.ibm.apic.overview.doc/overview_whatsnew.html].\n\nWe advise all users of IBM API Connect V5.0 to install this update to take advantage of the fixes.\n\nAPAR FIXES\n\nTHE FOLLOWING APAR WERE ADDRESSED BY IBM API CONNECT V5.0.3.0, ALONG WITH OTHER INTERNALLY RAISED QUALITY FIXES:\nAPAR Summary LI79190 API CONNECT: OAUTH SCOPES ARE NOT UPDATED CORRECTLY IN SWAGGER LI79180 AFTER THE UPGRADE EXISTING APIS HAVE MULTIPLE OPERATION IDS. LI79063 API CONNECT: THE LITERAL STRING OF A QUERY PARAMETER IN A TARGET URL IS SENT TO THE BACKEND AS IS LI79144 API CONNECT ANALYTICS: API INVOKES REQUESTS ARE NOT ALL RECORDED LI79137 API CONNECT: /WIP DISK SPACE IS RAPIDLY CONSUMED LI79135 RUNTIME ON MANAGEMENT SERVER CANNOT START AFTER DELETION OF ANOTHER MANAGEMENT SERVER AND REBOOT LI79134 IBM API MANAGEMENT AND API CONNECT: PROBLEM WITH DOWNLOADING PM LOGS FROM CMC GUI LI79133 API MANAGEMENT: THE UI HANGS AND ALL MANAGEMENT SERVERS ARE DOWN LI79130 DEVELOPER PORTAL: PERFORMANCE ISSUE WITH A LARGE USER LIST LI79113 DEVELOPER PORTAL FIXPACK DOES NOT CHECK IF .SSH/AUTHORIZED_KEYS FILE EXISTS. LI79047 QUERY PARAMETERS BEING DECODED INCORRECTLY LI79192 UNABLE TO EXECUTE A REQUEST TO A CATALOG, 404 URL NOT FOUND, ERRORS RETURNED UPGRADE PATHS FOR API CONNECT:\nFor more information of details on IBM API Connect upgrade paths, see Supported Upgrade Paths. [http://www-01.ibm.com/support/docview.wss?uid=swg21984408]\n\nThere are specific validated upgrade paths between IBM\u00ae API Management Version 4.0 or later and IBM API Connect Version 5.0 or later. For more information, see Validated upgrade paths for API Connect [http://www.ibm.com/support/knowledgecenter/SSMNED_5.0.0/com.ibm.apic.overview.doc/overview_apic_upgrade_path.html]\n\nIn addition to the specific validated upgrade paths for the API Management appliance, you must upgrade your IBM DataPower Gateway appliance. For more information, see Upgrading DataPower for Gateway servers [http://www.ibm.com/support/knowledgecenter/SSMNED_5.0.0/com.ibm.apic.overview.doc/apply_main_gateway.html?lang=en-us].\n\nUpgrading the gateway to firmware level 7.5.0.1 is strongly recommended for the best experience.\n\nDOWNLOADS:\n\nFull installation and upgrade files for IBM API Connect Version 5.0.3.0 (Enterprise, Professional & Essentials) can be downloaded from Fix Central: IBM API Connect Version 5.0.3.0 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.3.0&platform=All&function=all]\n\nEnsure that you have read and understood the above Important installation instructions before downloading and using the installation or upgrade files.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q304", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "What is Fix Central (FC)? [http://www.ibm.com/systems/support/fixes/en/fixcentral/help/faq_sw.html]", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q304", "section_id": 2, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Fix packs for DataPower XML Security Gateway version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034955]\nFix packs for DataPower B2B Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034956]\nFix packs for DataPower Integration Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034957]\nFix packs for DataPower Low Latency Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034958]\nFix packs for DataPower Service Gateway version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034959]\nFix packs for DataPower Service Gateway version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036407]\nFix packs for DataPower B2B Appliance version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036409]\nFix packs for DataPower Integration Appliance version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036410]\nFix packs for DataPower Service Gateway version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037486]\nFix packs for DataPower B2B Appliance version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037487]\nFix packs for DataPower Integration Appliance version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037488]\nFix packs for DataPower Gateway version 7.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24038524]\nFix packs for DataPower Gateway version 7.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24039783]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q304", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Affected are customers sending HTTP GET requests to the\n multiprotocol gateway, web service proxy or web application\n firewall service.\n\nWith the present implementation, users may end up in a state\n with indefinite retries for HTTP GET requests as long as\n DataPower has at least one live persistent connection to the\n backend server. After timeout interval for active connection it\n will terminate the connection and retry using remaining\n persistent connections to the backend. (If a new connection is\n opened because of half-dead backend this can continue\n indefinitely or until the request is served).", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q304", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "This behavior cannot be turned off however it can be mitigated.\n For some relief out of this, the admin can lower the Back\n Persistent Timeout and/or User Agent's default Timeout. This\n should result in less persistent connections to the backend and\n thus less possible timeout hops\n\nDropping the backend persistent connections option is also a\n possible workaround, but the consequences should be weighed\n carefully before making this decision. Not using persistent\n connections comes with a performance penalty, but it very much\n depends on the size/type of the transferred data and the\n speed/ping of the network.\n\nSLM is also strongly encouraged to prevent the backend from\n getting more load than it can handle.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q304", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Affected are all customers using the Multi-Protocol Gateway,\n Web Service Proxy or Web Application Firewall with persistent\n connection to the backend side.\n\nIn case the backend server stops responding to HTTP GET\n requests while there are already some established TCP\n connections from the time the server worked OK, DataPower will\n automatically retry those GET requests after a timeout period.\n This will be retried until there are no established connections\n to the server.\n\nDuring a high load window, these unwanted retries might\n eventually keep flooding an already congested backend,\n especially if it is still able to establish some new\n connections.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q304", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fix is available in 6.0.0.16, 6.0.1.12, 7.0.0.9, 7.1.0.6 and\n 7.2.0.2.\n\nFor a list of the latest fix packs available, please see:\n http://www-01.ibm.com/support/docview.wss?uid=swg21237631 [http://www-01.ibm.com/support/docview.wss?uid=swg21237631]\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q304", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT08971\nREPORTED COMPONENT NAME\n DATAPOWER\nREPORTED COMPONENT ID\n DP1234567\nREPORTED RELEASE\n 600\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2015-05-18\nCLOSED DATE\n 2015-08-12\nLAST MODIFIED DATE\n 2015-09-02\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q304", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n DATAPOWER\nFIXED COMPONENT ID\n DP1234567", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q304", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R600 PSN\n UP\nR601 PSN\n UP\nR602 PSN\n UP\nR700 PSN\n UP\nR710 PSN\n UP\nR720 PSN\n UP", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q304", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Fix packs for DataPower Service Gateway version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037486]\nFix packs for DataPower B2B Appliance version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037487]\nFix packs for DataPower Integration Appliance version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037488]\nFix packs for DataPower Gateway version 7.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24038524]\nFix packs for DataPower Gateway version 7.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24039783]\nFix packs for DataPower Gateway version 7.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24041543]\nFix packs for DataPower Gateway version 7.5.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24042194]\nFix packs for DataPower Gateway version 7.5.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24042699]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q304", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Datapower service (i.e MPGW, WSP, etc) is configured to connect\n to backend server through an HTTP Proxy server (as configured\n in the Proxy Policy of the user agent) using the HTTP CONNECT\n method.\n However, if the HTTP CONNECT request to the proxy server,\n receives a 5xx response, Datapower might issue the following SSL\n error:\n 20160711T163325.760Z [0x8120002f][ssl][error]\n ssl-client(PMYClientProfile): tid(11573565)[10.x.x.x]\n gtid(11573565): SSL library error: error:1408F10B:SSL\n routines:SSL3_GET_RECORD:wrong version number", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q304", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "With the fix the device will now log the actual HTTP response\n code received if there is an error.", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q304", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The fix is available in 7.0.0.16, 7.1.0.13, 7.2.0.10, 7.5.0.4,\n 7.5.1.3 and 7.5.2.1\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q304", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT16244\nREPORTED COMPONENT NAME\n DATAPOWER\nREPORTED COMPONENT ID\n DP1234567\nREPORTED RELEASE\n 720\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-07-21\nCLOSED DATE\n 2016-10-11\nLAST MODIFIED DATE\n 2016-11-18\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\n0", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q304", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n DATAPOWER\nFIXED COMPONENT ID\n DP1234567", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q304", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R752 PSY\n UP", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q304", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "Many common forward proxy servers expect requests in different formats depending on if they are proxying non-SSL or SSL requests.\n\nFor example, a non-SSL request to be proxied may come in the form of GET hostname:port/URI.\n\nFor SSL requests to be proxied, remote proxy servers are commonly configured to tunnel the request from the client to the backend server.\n\nIn the SSL request scenario, remote proxy servers will typically expect a CONNECT request and then tunnel the SSL request from the client to the backend server.\n\nUsers configuring DataPower may need a way to implement this CONNECT method for SSL tunneling to a remote Proxy Server.", "logical_doc_id": 5, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q304", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Non-SSL Proxy requests will work using either:\n\na) an XML Firewall when configuring in the HTTP Options tab, where the user can configure the Proxy Host and Port\n\nb) a Multi-Protocol Gateway when configuring an HTTP Proxy Policy in the User Agent\n\nSSL Proxy requests will work using the CONNECT method for SSL Tunneling when using a Multi-Protocol Gateway when configuring in a User Agent's HTTP Proxy Policy.\n\nThe XML Firewall service is not designed to use the CONNECT method for SSL Tunneling.", "logical_doc_id": 5, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q174", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Is there a setting that can disable or suppress web error messages in the Datacap Taskmaster Capture thin client?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q174", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "No, there is currently no setting that would allow web error messages to be suppressed or disabled. IBM Lab Services [http://www.ibm.com/software/ecm/services/] does have the ability to customize Datacap Taskmaster to do this, but the customization is not supported by IBM Support.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q174", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "This addresses customers that have already been using Citrix and have their data stored in the previously configured folder, for example H:\\username, and who wish to maintain this folder structure for both existing users and new users.\n\n1. Run an install using the configurable data option. Use command line parameters to install the Notes client with a configured data directory folder; for example H:\\username, as follows:\n\n\"SETMULTIUSER=1 CITRIX=1 MULTIUSERBASEDIR=h:\\!USER NAME! MULTIUSERCOMMONDIR=C:\\notes\"\n\nThis causes the Notes shared files (templates, help files, icons) to be installed under C:\\notes\\Lotus\\Notes\\Data and each new user's data to be stored under H:\\username\\Lotus\\Notes\\Data.\n\nThe Notes Binaries are installed under C:\\Program Files (x86)\\IBM\\Lotus\\Notes.\n\n2. Create a registry key to point to the user's existing or newly created stub NOTES.INI file as follows:\n\nHKCU\\Software\\Lotus\\Notes\\8.0\\NotesIniPath = H:\\username\\notes.ini\n\nThis instructs the Notes setup code to use this file when setting up the Notes client for the first time. If the user already exists, Notes will use all the current data files for this user. For new users, you must create a new stub NOTES.INI with the following contents:\n\n[Notes]\nDirectory=h:\\newusername\n\nResult: The existing user's data directories will be intact and new users will have the same structure under their username.\n\n3. [Standard Installs Only]: To update the path of the .\\data\\workspace directory, open the C:\\Program Files\\IBM\\Lotus\\Notes\\framework\\rcp\\rcplauncher.properties. Modify the path to the \\workspace directory by updating the rcp.data parameter.\n\nExample:\nrcp.data=H\\:/", "logical_doc_id": 2, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q174", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "- Technote 1447060 -- Using MULTIUSERBASEDIR with network drive destination requires an existing directory [http://www-01.ibm.com/support/docview.wss?uid=swg21447060]", "logical_doc_id": 3, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q174", "section_id": 0, "heading": "RELATED INFORMATION", "parent": null, "text": "Wiki - Notes and Domino community posts and related doc [http://www-10.lotus.com/ldd/dominowiki.nsf/]\nInformation Center - Notes and Domino product documenta [http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp]\n\nFIX README", "logical_doc_id": 4, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q174", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This readme file provides instructions on applying updated Taskmaster server modules on Datacap 9.1.3.0 Interim Fix 005 systems to address the following issue:\n\"Under certain situation, Datacap system allows users to be authenticated with incorrect password.\"", "logical_doc_id": 5, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q174", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Install 9.1.3.0-Datacap-WIN-IF005-HF001 on all machines that includes Taskmaster server and all Taskmaster clients. To install this fix, replace files. Registration is not necessary.\n\nTo apply 9.1.3.0-Datacap-WIN-IF005-HF001 during a maintenance window, complete the following steps:\n\n1. Stop Taskmaster Server services and other background Datacap services, such as RuleRunner services, and close all the Datacap Applications.\n 2. Back up the following modules that are found in \\Datacap\\Taskmaster folder to a temp folder.(Ensure that you do not remove or rename the module from this folder): * atm.dll\natms.dll\ntmcore.afx.dll\ntmnetcore.afx.dll\ntms.exe\n\n3. Drop the following attached updated Taskmaster Server modules into Datacap\\Taskmaster folder: * atm.dll (9.1.3.0.97)\natms.dll (9.1.3.0.101)\ntmcore.afx.dll (9.1.3.0.181)\ntmnetcore.afx.dll (9.1.3.0.134)\ntms.exe (9.1.3.0.73)\n\n4. Restart Datacap Server services and then launch Datacap Applications.\n\nThis issue has been tracked according to APAR IO26396 and work item number 181907.\n\nImportant notes:\n9.1.3.0-Datacap-WIN-IF005-HF001 fix can only be installed on a 9.1.3.0-iFix-005 Datacap system.\nInstalling 9.1.3.0-iFix-006 Fix Pack on current Datacap System that previously had 9.1.3.0-Datacap-WIN-IF005-HF001 will override existing Taskmaster Server modules with newer updated Taskmaster modules included in 9.1.3.0 Interim Fix 006 since all Interim Fixes are cumulative.\nIf you do not wish to install 9.1.3.0-Datacap-WIN-IF005-HF001 fix on your current Datacap 9.1.3.0 System, then you may install 9.1.3.0- Interim Fix - 006 fix when it is available on IBM Fix Central as it will include 9.1.3.0-Datacap-WIN-IF005-HF001 fix.\n\nTo view IBM Datacap Version 9.1.3 Interim Fix 005 readme file, click here [http://www-01.ibm.com/support/docview.wss?uid=swg27051104].\n\niNotes Web Access; IWA; DWA; systemrequirementsdocument; sysreqs; system requirements; hardware requirements; software requirements; minimum; maximum; workstation; systemrequirementsdocument; supports; supported with; DSRdoc; ND8; 8.0.1; Domino Off-Line Service; Domino Off Line Service; Domino Offline Service; DOLS PRODUCT DOCUMENTATION", "logical_doc_id": 5, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q174", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "This document contains the detailed system requirements for IBM\u00ae Lotus\u00ae Domino\u00ae Web Access 8.0.1.", "logical_doc_id": 5, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q174", "section_id": 3, "heading": "CONTENT", "parent": null, "text": "See below for a list of detailed system requirements for Lotus\u00ae Domino\u00ae Web Access.\n\nFor additional information, see the IBM Lotus Notes\u00ae and Domino 8.0.1 Release Notes, referenced below.\n\nClient Hardware Requirements\nRecommended for better performance:\nWindows -- Pentium IV 1.5 GHz with 512 MB of memory\nLinux -- Pentium IV 1.5 GHz with 512 MB of memory\nMacintosh -- G4 1.5 GHz with 512 MB of memory\nMinimum requirements:\nWindows -- Pentium III 800 MHz with 256 MB of memory\nLinux -- Pentium III 800 MHz with 256 MB of memory\nMacintosh -- G4 1 GHz 256 MB of memory\n\nClient Operating Systems and Supported Browsers\nDomino Web Access runs on the following client operating systems: Windows XP and Vista using the following browsers:\nInternet Explorer 6 and 7\nMozilla Firefox 2.0.x\n\nNovell Linux Desktop (NLD) 10 using the following browsers: * Mozilla Firefox 2.0.x\n\nRedHat Enterprise Linux Desktop 5.0 using the following browsers: * Mozilla Firefox 2.0.x\n\nMacintosh OS 10.4.x and 10.5 using the following browsers: * Mozilla Firefox 2.0.x -- Note: Does not support Domino Off-Line Services (DOLS), local archiving, and Lotus Sametime awareness\n\nCitrix Presentation Server 4.5 on Windows 2003 * Clients using the Citrix Presentation Server 4.5 on Windows 2003 server, using ICA. Citrix ICA stands for Citrix\u00ae Independent Computing Architecture. It is the \"thin\" protocol that enables Citrix to separate screen updates and user input processing from the rest of the application\u2019s logic. When using a Citrix ICA client, all application logic executes on the server and only screen updates, mouse movements and keystrokes are transmitted via the Citrix ICA session. Note: Does not support Domino Off-Line Services (DOLS).", "logical_doc_id": 5, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q174", "section_id": 3, "heading": "CONTENT", "parent": null, "text": "Browser Support Notes * Mozilla Firefox is supported by the DWA7 and MAIL8 mail templates only, it is not supported by iNotes6 templates.\nAttempting to access Domino Web Access through unsupported browsers results in the display of an unsupported browser notice. Netscape 4.x users may see hangs and/or crashes when encountering the Domino Web Access unsupported browser page. If you are a Netscape 4.x user and you encounter these problems, you should open your mail file using the WebMail UI directly through the &ui=webmail switch. This is documented in the topic \"Switching to WebMail\" in the Domino Web Access help.\nDomino Web Access will not work if JavaScript is disabled or if session cookies are disabled.\n\nServer Requirements\nSee the IBM Lotus Notes and Domino 8.0.1 Release Notes, referenced below, for a complete list of server operating systems and requirements.\n\nCertified Proxy Servers * SunOne Portal Server 6.2\nIBM WebSphere Edge Server 2.0.2 efix 49\nTivoli Access Manager 6.0\n\nAdobe Acrobat\nAdobe Acrobat Reader, Version 4.0 or higher to print calendars.", "logical_doc_id": 5, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q174", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Lotus Domino Web Access product page [http://www.ibm.com/software/lotus/products/domino-web-access/]\nIBM Lotus Notes and Domino 8.0.1 Release Notes [http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss?CTY=US&FNC=SRX&PBL=GC23597601]", "logical_doc_id": 5, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q174", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What are the best practices for deploying Datacap servers and clients on a wide area network (WAN)?", "logical_doc_id": 6, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q174", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Remote users that access Datacap over a WAN can use Taskmaster Web-based \"thin clients\", or FastDoc Capture operating in offline mode. Datacap thick clients (DotScan, DotEdit) and utilities (NENU, Fingerprint Maintenance Tool) require LAN communication speeds and low latency for responsive performance.\n\nConnect all Datacap Taskmaster Servers, Rulerunner Servers, Web Servers, file servers and databases to a single high performance LAN for best results. Network delays between Taskmaster Server, shared files and databases causes degraded performance of Job Monitor and data intensive operations.\n\nSome customers successfully operate Datacap thick clients in remote sites using Citrix or other remote access technology. IBM has not tested or sought certification with Citrix, and does not provide support for Citrix. If you deploy Datacap clients on Citrix and encounter issues, IBM may require you to reproduce the issues outside of Citrix as part of the investigation.\n\nConsult the IBM Redbooks titled \"Implementing Imaging Solutions with IBM Production Imaging Edition and IBM Datacap Capture\", section 2.5, for deployment recommendations and diagrams.", "logical_doc_id": 6, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q174", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Redbooks Production Imaging Edition [http://www.redbooks.ibm.com/abstracts/sg247969.html?Open]", "logical_doc_id": 6, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q149", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Errors on connection with \"No matching cipher found\", or \"No matching MAC algorithm found\", or occasionally \"No matching kex algorithm found\".", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q149", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The following PTFs, or their supersedes, upgrade OpenSSH on the IBM i from an earlier release to 6.9p1:\n\no R610 - SI57920 (1000)\no R710 - SI57762 (5317)\no R720 - SI57771 (5310)\n\nImportant Note: The R710 and R720 PTFs are on a cumulative package; therefore, applying that package will also upgrade OpenSSH.\n\nThe previous release of OpenSSH on these releases was 6.6p1. In OpenSSH 6.7 and subsequent releases, changes were made to the default set of ciphers. The release notes at http://www.openssh.com/txt/release-6.7 [http://www.openssh.com/txt/release-6.7] state the following:\n\nChanges since OpenSSH 6.6\n\nPotentially-incompatible changes\nsshd(8): The default set of ciphers and MACs has been altered to\nremove unsafe algorithms. In particular, CBC ciphers and arcfour*\nare disabled by default.\n\nThe full set of algorithms remains available if configured\nexplicitly via the Ciphers and MACs sshd_config options.\n\nIf the SSH client/SSH server is older and does not yet support the safer ciphers and MACs, and wants to use one of the unsafe ciphers/MACs disabled by default, the connection will fail.\n\nIssues have also been seen with Key Exchange Algorithms (kex) failing on a connection attempt.\n\nNOTE : The upgrade to OpenSSH 6.9p1 was necessary in order to fix several published CVE vulnerabilities in the OpenSSH code and ensure PCI compliance.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q149", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "OpenSSH 6.9p1 has the following algorithms available as default. This information is taken from the OpenSSH manual page [http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man5/sshd_config.5?query=sshd_config&sec=5] for sshd_config:\n\nCiphers\n\nchacha20-poly1305@openssh.com,\naes128-ctr,aes192-ctr,aes256-ctr,\naes128-gcm@openssh.com,aes256-gcm@openssh.com\n\nMACs\n\numac-64-etm@openssh.com,umac-128-etm@openssh.com,\nhmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,\numac-64@openssh.com,umac-128@openssh.com,\nhmac-sha2-256,hmac-sha2-512\n\nKexAlgorithms\n\ncurve25519-sha256@libssh.org,\necdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,\ndiffie-hellman-group-exchange-sha256,\ndiffie-hellman-group14-sha1", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q149", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "There are two potential solutions to this issue. From a security viewpoint, Option 1 must be preferred as it uses the secure algorithms and does not introduce back in unsafe algorithms. Unsafe means that security vulnerabilities have been found in the algorithms being used. Option 2 is recommended only as a stop-gap to allow time to upgrade the client or server software, and then you should remove the changes from the configuration file:\n\n1. Upgrade the SSH client/server to a version where it uses the safe algorithms in the default lists above. Refer to your SSH client/server provider for information on how to do this, and which version you will need.\n\n2. Modify the appropriate OpenSSH configuration file on the IBM i to add back in the unsafe algorithms required to have the client connect.\n\nIf the IBM i is the SSH Server, modify the sshd_config file\n\nIf the IBM i is the SSH Client, modify the ssh_config file\n\nThe configuration file will be found in the following locations per release:\n\nV6R1 - /QOpenSys/QIBM/UserData/SC1/OpenSSH/openssh-3.8.1p1/etc/\nV7R1 - /QOpenSys/QIBM/UserData/SC1/OpenSSH/openssh-4.7p1/etc/\nV7R2+ - /QOpenSys/QIBM/UserData/SC1/OpenSSH/etc/\n\nUsing WRKLNK, locate the file, and select Option 2 (=Edit) against it. You will need to add in the appropriate keyword, specify the default algorithms that you still need it to use, and then add one or more of the unsafe algorithms (comma separated) to the end of the defaults.\n\nFor example:\n[/support/docview.wss?uid=nas8N1021014&aid=1] [/support/docview.wss?uid=nas8N1021014&aid=1]\n\nTake similar action if you need to add the MACs or KexAlgorithms keywords to the file.\n\nThe algorithm you add will still need to be one of the algorithms that the system supports. To get a list of all the supported algorithms, you can run the following from QSH or CALL QP2TERM:\n\nssh -Q cipher\nssh -Q mac\nssh -Q kex\n\nIf you want to create a comma separated list of all the supported algorithms to use with the appropriate keyword, you can run the following from QSH or CALL QP2TERM command line:\n\nssh -Q cipher | xargs echo | sed 's| |,|g'\n\nNote this example is for ciphers; you should adjust accordingly for MAC or KexAlgorithms.\n\nCross reference information Segment Product Component Platform Version Edition Operating System IBM i 7.2 Operating System IBM i 7.1 Operating System IBM i 6.1", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q149", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How to review AMM reporting power source issues.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q149", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Message log is showing is showing the following output:\nWarning: Got error from DevMgr task:/nz/kit.7.2.0.6/bin/adm/ibm_amm --loc=spa1.mm --status, RetCode:5,\n\nListing out ssh mm001 list -l 2 showed the power connections where not\nlisted. I saw no power issues..\n\nssh mm001 list -l2\n\nstem> list -l 2\nsystem\nblade[1] SN#Y010UF47P0DW\nblade[3] SN#Y010UF47P0C0\nblade[5] SN#Y010UN47T03Z\nblade[7] SN#Y010UN47N0H9\nblade[9] SN#Y010UF47P0F8\nblade[11] SN#Y010UF47P0F9\nblade[13] SN#Y010UF47P0B6\nblower[1]\nblower[2]\nmm[1] primary\nmm[2] standby\nswitch[7]\nswitch[9]\nmt[1]\n\nssh mm001 fuelg - to check the power domains:\n\nsystem> fuelg\nNote: All power values are displayed in Watts.\n\nTotal DC Power Available: 5760\nTotal AC Power In Use: 1593\nTotal Thermal Output: 5435 BTU/hour\n\nPower Domain 1\n\nStatus: Power domain status is good.\nModules:\nBay 1: 2880\nBay 2: 2880\nPower Management Policy: Basic Power Management\nPower in Use: 807\nTotal Power: 2880\nAllocated Power (Max): 2634\nRemaining Power: 246\n\nIssuing a force restart of the AMM cleared the condition:\nssh mm00x reset -T mm[x]\n\nThis cleared the issue and stopped the sysmgr log reporting the power issue.\n\na ssh mm001 list -l2 showed all connections.\n\nIf this does not work I would suggest a fail over of the AMM.\nFollowed by a site visit by a field tech to reseat the AMM.\nThe followed by a replacement if necessary.\n\nAdditional commands to use in problem determination.\n\nTo get AMM FRU:\nssh mm001 info -T mm[1]\n\nfail over Amm1 to Amm2\nssh mm001 reset -T mm[1] -f\n\nsnmp walk on amm\nsnmpwalk -c public -v1 mm010 system\n\nAIX SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q149", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Adapter firmware upgrade could fail with FCA_ERR6\n and sense data 518\n------------Cut-------------------------\n LABEL: FCA_ERR6\n ..\n ..\n ..\n\n Detail Data\n SENSE DATA\n 0000 0020 0000 0518 0000 0005 0000 0000 0000 00AC 0000\n 0000 1000 0090 FAA0 5444\n ^^^\n------------Cut-------------------------\n\n This could happen under the following sequence of events:\n\n 1) Firmware upgrade is performed on an unused fcs\n instance\n 2) a monitoring application like fcstat opens the same\n adapter\n at the same time", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q149", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "1) retry adapter microcode upgrade\n or\n 2) perform microcode upgrade on actively used fcs\n instances\n or\n 3) stop monitoring applications from polling the adapter\n or\n 4) If all adapters fcs instances are unused, place\n protocol driver associated with\n the firmware upgrade in a defined state with the\n following command:\n\nExample: Assuming your upgrading firmware on fcs0\n rmdev -Rl fscsi0\n\nThe above will place fscsi0 in a defined state", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q149", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Adapter microcode update might fail with FCA_ERR6 and sense\n code 518", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q149", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "code modified to return error to the open thread, if adapter\n microcode update is already in progress\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q149", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IJ08641\nREPORTED COMPONENT NAME\n AIX V7.2\nREPORTED COMPONENT ID\n 5765CD200\nREPORTED RELEASE\n 720\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSUBMITTED DATE\n 2018-08-20\nCLOSED DATE\n 2018-08-20\nLAST MODIFIED DATE\n 2018-08-20\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n IJ06644 [http://www-01.ibm.com/support/docview.wss?uid=isg1IJ06644]\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q149", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n AIX V7.2\nFIXED COMPONENT ID\n 5765CD200", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q149", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "The version 7.5 documentation for IBM DataPower Gateway is not the latest available information. This document covers late breaking updates that are not in IBM Knowledge Center.\n\nLast updated, October 2017.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q149", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "The late breaking updates in this document apply to DataPower Gateway version 7.5 documentation.\n\nTo access specific updates, click the appropriate link: * Upgrade\n* Installation\n* GatewayScript\n* File management\n* Monitors\n\nTo view the change history of this document, see Change history\n\nThe corrections in the following sections apply to DataPower Gateway version 7.5 in IBM Knowledge Center.\n\nUpgrade *\nDisabled diffie-hellman-group-exchange-sha1 and diffie-hellman-group1-sha1 algorithms by default. Disabled MD5-based MAC algorithms. Limited DH-GEX to 4096 bits for Cisco devices.\n*\nenable-legacy-kex yes\n* The enable-legacy-kex command for the SSH server profile in available in 7.5.2.0. The enable-legacy-kex command for the SSH client profile is available in 7.5.2.7.\n*\nDefault cipher suites * chacha20-poly1305@openssh.com (CHACHA20-POLY1305_AT_OPENSSH.COM)\n* aes128-ctr (AES128-CTR)\n* aes192-ctr (AES192-CTR)\n* aes256-ctr (AES256-CTR)\n* aes128-gcm@openssh.com (AES128-GCM_AT_OPENSSH.COM)\n* aes256-gcm@openssh.com (AES256-GCM_AT_OPENSSH.COM)\n* arcfour256 (ARCFOUR256)\n* arcfour128 (ARCFOUR128)\n* aes128-cbc (AES128-CBC)\n* 3des-cbc (3DES-CBC)\n* blowfish-cbc (BLOWFISH-CBC)\n* cast128-cbc (CAST128-CBC)\n* aes192-cbc (AES192-CBC)\n* aes256-cbc (AES256-CBC)\n* arcfour (ARCFOUR)\n* rijndael-cbc@lysator.liu.se (RIJNDAEL-CBC_AT_LYSATOR.LIU.SE)\n\nDefault KEX algorithms * curve25519-sha256@libssh.org\n* ecdh-sha2-nistp256\n* ecdh-sha2-nistp384\n* ecdh-sha2-nistp521\n* diffie-hellman-group-exchange-sha256\n* diffie-hellman-group14-sha1\n\nDefault MAC algorithms * umac-64-etm@openssh.com\n* umac-128-etm@openssh.com\n* hmac-sha2-256-etm@openssh.com\n* hmac-sha2-512-etm@openssh.com\n* hmac-sha1-etm@openssh.com\n* umac-64@openssh.com\n* umac-128@openssh.com\n* hmac-sha2-256\n* hmac-sha2-512\n* hmac-sha1\n*\nThe SSH client always initiates the banner exchange. During the SSH2 banner exchange, use CR+LF termination for the banner. The SSH client ignores any message from the SSH server until the banner exchange.\n\nBack to top\n\nInstallation *\nshow other-sensors\n* show sensors-other\nBack to top\n\nGatewayScript *\nclear gatewayscript-cache path\nBack to top\n\nFile management *\nisamwebroot local policyframework\n\nBack to top\n\nMonitors *\ntype\n* block\n* shape\n* type command\nBack to top\n\nChange history\nLast modified: 30 October 2017. * 30 October 2017: Added information about nonexisting block keyword for Message Filter Action type command.\n19 October 2017: Added information about which directories you can create and remove subdirectories.\n19 July 2016: Added data about the wrong command troubleshooting command in the installation documentation.\n17 June 2016: Added data about the undocumented Global command.\n22 March 2016: Created for 7.5.\n\nBack to top", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q149", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "After configuring McAfee VSES Version 1.0 with IBM Connections Files to scan uploaded files for virus, no one is able to upload files to the system. Why does this fail?", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q149", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "IBM Connections works with ICAP 1.0 protocol. McAfee VSES, however, does not currently support the ICAP 1.0 protocol, and will not currently work with IBM Connections", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q149", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Select an ICAP 1.0 compliant anti virus solution.\n\nEnsure that the virus detection product used in your enterprise supports the ICAP 1.0 protocol.\nIBM Connections is currently certified to work with Symantec AntiVirus Scan Engine 5.1 and McAfee web Security Appliance (3400) and (3300).", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q221", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The following error message is showed in either the message prompt while opening a project in WebStart Studio or the Cast Iron Live Web Start Studio error.log:\n\nError:\nMessage:\njavax.xml.soap.SOAPException: Connection timed out: connect\nLevel:\nSEVERE\nStack Trace: Connection timed out: connect com.approuter.module.session.WSDispatch.dispatch(WSDispatch.java: 324)\ncom.approuter.studio.module.cloud.impl.DefaultCloudProjectsManager.fetchProject(DefaultCloudProjectsManager.java:121)\ncom.approuter.studio.module.cloud.OpenRemoteProjectTask.run (OpenRemoteProjectTask.java:83)\nThe log file could be stored at the following path:\nC:\\Users\\\\AppData\\Roaming\\castiron", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q221", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The error message means Web Start Studio has problem accessing the project data that resides on Cast Iron Live. Take one of the following steps to solve the issue:\nRestart Web Start Studio and try again.\nCheck the network in which the Web Start Studio is running by accessing the Cast Iron Live login page via browser.\nIf proxy is used in the network in which the Web Start Studio is running, go to Web Start Studio Menu > Edit > Preferences > Session Login and check the proxy settings.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q221", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "The error message can be received because the Cast Iron orchestration did not get the acknowledgement from the Web server. The web service Invoke is considered complete once the Invoke activity receives the acknowledgement from the server. If it does not get the acknowledgement, the activity errors with a \"time out exception\"", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q221", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Increase the 'Connection time out value' for the 'Invoke service' activity. Invoke the web service using a third party tool to assess the time-out value.\n\nHISTORICAL NUMBER\n 00000383\n\nPRODUCT ALIAS/SYNONYM\n Cast Iron Solution\nCast Iron Operating System\nCast Iron Studio\n\nRELEASE NOTES", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q221", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "APARs resolved in WebSphere Cast Iron Cloud integration 6.4.0.1 fix pack.", "logical_doc_id": 2, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q221", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "TAB NAVIGATION\nOverview [http://www.ibm.com/support/docview.wss?uid=swg21647655]- selected tab,\nIncluded Fixes [http://www.ibm.com/support/docview.wss?uid=swg27039418]\nKnown Issues [http://www.ibm.com/support/docview.wss?uid=swg27039417]\nDownload Links [http://www.ibm.com/support/docview.wss?uid=swg24035612]\n\nThe following table details the APARs that are addressed in WebSphere Cast Iron Cloud integration 6.4.0.1 fix pack.\n\nAPAR Summary LI77263 [http://www.ibm.com/support/docview.wss?uid=swg1LI77263] MAPPINGS MAY DISAPPEAR FROM VIEW IN ACTIVITIES UNTIL THE MAPPINGTREE IS MINIMIZED OR MAXIMIZED IN CAST IRON STUDIO LI77265 [http://www.ibm.com/support/docview.wss?uid=swg1LI77265] NOT SPECIFYING \"LISTEN AT URL\" IN HTTP RECEIVE REQUEST ACTIVITY CAUSES ORCHESTRATION FAILURE LI77431 [http://www.ibm.com/support/docview.wss?uid=swg1LI77431] SAP ADAPTER RECEIVES COMPLEX TYPE ELEMENT, BUT IS PROCESSING ONLY THE FIRST VALUE AND IGNORING THE OTHERS. LI77432 [http://www.ibm.com/support/docview.wss?uid=swg1LI77432] UNABLE TO SET PARAMETRIZED HTTP LISTENER URL AS A CONFIGURATION PROPERTY IN 6.3.0.1 VERSION OF STUDIO LI77470 [http://www.ibm.com/support/docview.wss?uid=swg1LI77470] THE \"NET ADD ETCHOST\"ERROR MESSAGE DOES NOT CLEARLY INDICATE IF HOSTNAME/IP ADDRESS MAPPING WAS A SUCCESS OR A FAILURE. LI77472 [http://www.ibm.com/support/docview.wss?uid=swg1LI77472] REPUBLISHING THE SAME PROJECT WITH SAME NAME INTO WMC REMOVES THE PUBLISHER PRIVILEGES ON THE PROJECT. LI77478 [http://www.ibm.com/support/docview.wss?uid=swg1LI77478] LAUNCHING WEBSPHERE CAST IRON V6.4 STUDIO DISPLAYS V6.3 ON THE SPLASH PANEL LI77484 [http://www.ibm.com/support/docview.wss?uid=swg1LI77484] DOWNLOAD OF CAST IRON REPOSITORY ON WMC DOES NOT COMPLETE AFTER USER CLICK ON THE \"DOWNLOAD NOW\" LINK LI77487 [http://www.ibm.com/support/docview.wss?uid=swg1LI77487] NPE WHILE ADDING A WSDL WHICH CONTAINS EMPTY PORTTYPE ELEMENT LI77492 [http://www.ibm.com/support/docview.wss?uid=swg1LI77492] ROLL UP OF SERVICEABILITY IMPROVEMENTS FOR CAST IRON LI77522 [http://www.ibm.com/support/docview.wss?uid=swg1LI77522] SAP ENDPOINT TEST CONNECTION MESSAGE IS NOT SHOWN UNTIL PROJECT IS CLOSED Back to top", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q221", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Best Practices to optimize performance on the App Connect Professional Live environment:\n\n 1. Set logging level to \"ErrorValue\" for production jobs.\n Orchestrations with Logging level set to \"All\" (which records each and every interaction onto the database) greatly reduces execution time and is unnecessary. Please check the logging level on your orchestrations and if it is set to \"All\" then please change it to \"ErrorValue\".\n\n 2. Turn off the \"Persistence\" setting where possible.\n Persistence allows for restarting jobs in an exception scenario. Where your solution includes retry logic or where restarting the orchestration has little overall cost, the persistence setting can be safely disabled thus reducing unnecessary database access and increasing the performance of jobs. This is a simple update that requires changing the persistence setting and redeploying your orchestrations.\n\n 3. Shared Variables:\n If you are using shared variables please note that the value of this variable will reset whenever the cloud runtime restarts. Therefore if your orchestration logic relies on using such variables across a restart boundary, please change it appropriately for using values that are stored rather than kept in temporary memory.\n\nPRODUCT ALIAS/SYNONYM\n App Connect Professional", "logical_doc_id": 3, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q221", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do I increase the size of the heap memory allocated to the Cast Iron Studio?", "logical_doc_id": 4, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q221", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Start the Studio through the command line interface using the following command:\n\nCastIronStudio.exe -J-Xmx1024m\n\nIn this command, \"1024\" is the new memory size that will be allocated to the Studio instead of the default value of 512. This numeric value is in MB.\n\nNote: There are no benchmark figures on the max value for a given machine configuration that is supported as max memory by Studio. Use garbage collection from Studio to free up unused space, Also, try XML Schema preference settings and see if the use of memory is within the default value of 520 MB or a permissible increased value.\n\nFor additional questions related to Increasing heap memory size, open a service request with IBM Cast Iron Support. More information about using the IBM Service Request tool is available here [http://www-01.ibm.com/software/support/servicerequest/quick_start.html].\n\nHISTORICAL NUMBER\n 00001529\n\nPRODUCT ALIAS/SYNONYM\n Cast Iron Solution\nCast Iron Operating System\nCast Iron Studio", "logical_doc_id": 4, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q251", "section_id": 0, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "WebSphere MQ V7.0 Fix Pack 7.0.1.6 [http://www-01.ibm.com/support/docview.wss?uid=swg24030108]\nWebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.6 [http://www-01.ibm.com/support/docview.wss?uid=swg24030534]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q251", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Upon change of system hostname, WebSphere MQ will continue to\n operate successfully, but will lose some of its fault-tolerance\n in relation to semaphore ID clashes.\n\nAfter a hostname change, WebSphere MQ code will use another\n scheme for allocating semaphore IDs, but if there is a clash\n with a semaphore ID in use by other software on the machine,\n then WebSphere MQ trace functionality can become disabled.\n\nThe semaphore IDs in question are only those used in relation\n to WebSphere MQ trace. It is only the functionality of MQ\n trace that is potentially affected by this issue.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q251", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n Systems on which the hostname has changed since installing\n WebSphere MQ.\n\nPlatforms affected:\n All Distributed (iSeries, all Unix and Windows)\n\nPROBLEM SUMMARY:\n The path /var/mqm/sockets/@SYSTEM/qmgrlocl should contain a\n directory named after the hostname of the local machine.\n\nThe said directory was checked and created only at the time\n WebSphere MQ was installed on the machine. But during strmqm,\n there was no check that the directory existed.\n\nIf the system hostname does not change, there is no problem at\n all. But if the system hostname is changed, WebSphere MQ code\n will not check the path containing the new hostname directory\n or attempt to create it.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q251", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The WebSphere MQ code has been changed. During strmqm, there\n is now a check for the existence of the directory named above.\n If the directory does not exist, an attempt will be made to\n create it.\n\nThe fix is targeted for delivery in the following PTFs:\n\nv7.0\n Platform Fix Pack 7.0.1.6\n------- --------------------\n Windows U200328\n AIX U840698\n HP-UX (PA-RISC) U841555\n HP-UX (Itanium) U841560\n Solaris (SPARC) U841556\n Solaris (x86-64) U841562\n iSeries tbc_p700_0_1_6\n Linux (x86) U841557\n Linux (x86-64) U841561\n Linux (zSeries) U841558\n Linux (Power) U841559\n\nThe latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\nIf the maintenance level is not yet available, information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q251", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IZ96837\nREPORTED COMPONENT NAME\n WMQ SOL SPARC\nREPORTED COMPONENT ID\n 5724H7223\nREPORTED RELEASE\n 701\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2011-03-16\nCLOSED DATE\n 2011-04-14\nLAST MODIFIED DATE\n 2011-04-14\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q251", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ SOL SPARC\nFIXED COMPONENT ID\n 5724H7223", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q251", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R701 PSY\n UP", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q251", "section_id": 0, "heading": "ENVIRONMENT", "parent": null, "text": "Any IBM i system with an IASP", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q251", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "In today's IBM i environments, many users are leveraging IASPs (Independent Auxiliary Storage Pools) for various reasons. Most common use cases include PowerHA to have the ability to switch an IASP between sites or to perform flashcopies.\n\nCurrently there are no hard requirements when getting ready to IPL a system that currently has an IASP.\n\nThe purpose of this document is to provide some high level Best Practices to prepare a system with an IASP for an IPL.\n\n1. Plan the IPL window\n\n2. Start bringing down jobs and applications as desired\n\n3. Ensure there are no jobs active in the IASP by using the WRKASPJOB command\n\n a. May need to run command SETASPGRP *NONE\n\n4. Vary off the IASP\n\n5. If the system is a member of a cluster, properly end cluster components as needed.\n\n a. If a Production node, use commands ENDCRG, ENDCAD and ENDCLUNOD\n\n b. If some other node role, use command ENDCLUNOD\n\n6. Bring the system to a restricted state by using commands: ENDHOSTSVR *ALL and ENDTCPSVR *ALL, delay 5 minutes, ENDTCP, delay 5 minutes, and then ENDSBS *ALL *IMMED\n\n7. IPL the system\nNOTES:\n\n1. In some rare cases, if an IASP vary off should hang that would be the only exception where a partition could be forced to shut down before successfully varying off the IASP. This would result in an ABNORMAL IPL and should probably be followed with a Normal IPL before varying the IASP back on.\n\n2. In R720 with SI60255 and R730 with SI60256 applied, the IASP process will wait up to 10 minutes for system jobs to end and will post CPF9898 once a minute to QSYSOPR during this time if that's the case.\n\nCross reference information Segment Product Component Platform Version Edition Operating System IBM i 7.3 Operating System IBM i 7.2 Operating System IBM i 7.1\n\nz/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q251", "section_id": 1, "heading": "Error Description", "parent": null, "text": "The reported environment was:\n All the LPARs in a Queue Sharing Group (QSG) were IPL'd.\n Afterwards, the MSTR and CHIN jobs all started and appeared to\n be working. However, shared inbound channels had problems. Any\n connection coming in using the QSG VIPA name hung if it was\n sent to the first queue manager up. If it was sent to one of\n the other QSG members first, it worked. In the hang scenario,\n if the others queue managers then tried to start the shared\n channel, they got\n CSQX478E CSQXRCTL Channel , connection tag in use\n .\n Once the first queue manager up was stopped, everything worked\n fine. The queue manager was then restarted and worked fine also.\n .\n The channel hang was due to a deadlock. A channel was\n waiting for the XSCS semaphore as requested by routine\n rriInitSess. The DPRO that was holding the XSCS semaphore was\n waiting for the XSTA semaphore, requested by routine\n rriAddStatusEntry. The XSTA semaphore was held by a DPRO that\n was waiting to be dispatched on a particular dispatcher TCB.\n The DPRO running on that dispatcher TCB was currently in a\n WAIT, in CSQXLOCT, waiting for a conversion table to be loaded\n by the CSQXSUPR TCB. However, the CSQXSUPR TCB was in routine\n riiCheckChannels waiting for the XSTA semaphore. So, there was\n a deadly embrace.", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q251", "section_id": 3, "heading": "Local Fix", "parent": null, "text": "Restart the channel initiator or entire queue manager that is\n suffering the deadlock.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q251", "section_id": 4, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *\nRelease 0 Modification 1. *\n\nPROBLEM DESCRIPTION: Deadlock occurs between supervisor TCB *\nand dispatcher TCB. Channel initiator *\ncommands are not processed and channels *\non the affected dispatcher will hang. *\n\nRECOMMENDATION: *\n\nA timing window exists where it's possible for a channel to\n obtain the XSTA channel status table semaphore and yield control\n to another channel process on the same dispatcher TCB, which\n then requests a load of a data conversion table be performed by\n the supervisor TCB. The supervisor TCB is unable to process this\n load request as it is attempting to obtain the XSTA semaphore\n held by the first channel in order to process any channels in\n retry.\n\nBecause the channel requesting the load of the conversion table\n does not correctly yield control back to the dispatcher code,\n the first channel is not given an opportunity to execute and\n therefore is unable to release its semaphore. This results in a\n deadly embrace between the dispatcher and supervisor TCBs.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q251", "section_id": 5, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "When waiting for a data conversion table to be loaded, a channel\n process will now correctly issue a dispatcher wait rather than\n an MVS wait to ensure that other channels running on the same\n dispatcher TCB are able to release any semaphores they are\n holding.\n 010Y\n CSQDLOCT\n CSQXCNVT\n CSQXLOCT\n CSQXSPRT\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q251", "section_id": 6, "heading": "COMMENTS", "parent": null, "text": "**** PE12/07/25 FIX IN ERROR. SEE APAR PM69566 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM69566] FOR DESCRIPTION\n*** PE13/05/07 FIX IN ERROR. SEE APAR PM81886 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM81886] FOR DESCRIPTION", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q251", "section_id": 7, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM53107\nREPORTED COMPONENT NAME\n WMQ Z/OS V7\nREPORTED COMPONENT ID\n 5655R3600\nREPORTED RELEASE\n 010\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n YesHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2011-11-29\nCLOSED DATE\n 2012-02-28\nLAST MODIFIED DATE\n 2013-06-17\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n PM58956 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM58956] UK76598\n\nMODULES/MACROS\nCSQDLOCT CSQXCNVT CSQXLOCT CSQXSPRT", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q251", "section_id": 8, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ Z/OS V7\nFIXED COMPONENT ID\n 5655R3600", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q251", "section_id": 9, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R010 PSY UK76598 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK76598]\n UP12/04/11 P F204\n\nFIX IS AVAILABLE\nSELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL. YOU WILL BE REQUIRED TO SIGN IN. DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q251", "section_id": 10, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "WebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 12 (CSD12) [http://www-01.ibm.com/support/docview.wss?uid=swg24011423]\nWebSphere MQ V6.0 for iSeries Refresh Pack 6.0.1.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24010895]\nWebSphere MQ V6.0 Refresh Pack 6.0.2.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24013482]\nWebSphere MQ V5.3 for iSeries - Fix Pack 12 (CSD12) [http://www-01.ibm.com/support/docview.wss?uid=swg24011422]\nWebSphere MQ V6.0 Refresh Pack 6.0.1.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24010812]\nWebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 13 (CSD13) [http://www-01.ibm.com/support/docview.wss?uid=swg24014128]\nWebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 14 (CSD14) [http://www-01.ibm.com/support/docview.wss?uid=swg24017668]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q251", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "MQ channels go into a Retrying/Binding state after a network\n outage and do not recover.\n The receiver AMQCRSTA job does not show a start channel message\n id in it's job log(AMQ9002).\n The AMQCRSTA jobs get SIGKILLS which can be seen in the job\n logs. These end but then new AMQCRSTA jobs startup which\n experience the same problem i.e. they fail to start and are\n eventually killed (SIGKILL). New jobs then start and the whole\n process repeats over and over again.\n\nTo recover one has to end the AMQCRSTA job, and stop and start\n the sender on the Windows server.\n\nThe Trace shows the following characteristic function\n calls/trace statements:\n 005 .....> rriAdoptMCA\n 006 ......> rrxStopChannel\n 007 Stop Phase:1 Pass:0\n 007 Stop Phase:2 Pass:1 and so on until...\n 007 Stop Phase:5 Pass:0\n 007 .......> rriStopChannel\n 008 ........> cccJobKill\n 009 .........> xcsKillProgram\n 008 ........< cccJobKill rc=OK\n 007 .......< rriStopChannel rc=OK and finally out of AdoptMCA\n 005 .....< rriAdoptMCA rc=OK and then into ccxSend\n 004 ....> ccxSend\n 005 .....> cciTcpSend\n 006 ......> send and then into a loop in xcsSleep\n 005 .....< cciTcpSend rc=OK\n 005 Waiting to be killed\n 005 .....> xcsSleep\n 005 .....< xcsSleep rc=OK\n 005 Waiting to be killed", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q251", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Restart channels manaually.", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q251", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n User's using non-threaded receiver channels(AMQCRSTA) with\n AdoptNewMCA tuning parameters.\n\nPlatforms affected:\n All Distributed (iSeries, all Unix and Windows)\n\nPROBLEM SUMMARY:\n The problem was caused because of the KillPending flag in the\n status table being set when case SP_KILL_CHANNEL && Running.\n This flag was not being cleared after the channel was killed.\n Thus new receiver jobs starting had this flag set and were\n waiting to be killed.", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q251", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The Flag initialization and clearing of the flag and some\n additional checking have been introduced to prevent this\n problem.\n\nThe fix is targeted for delivery in the following PTFs:\n\nv5.3\n Platform Fix Pack 11\n------- --------------------\n Windows U200236\n AIX U802047\n HP-UX (PA-RISC) U802131\n Solaris (SPARC) U802142\n iSeries SI18375\n Linux (x86) U802143\n Linux (zSeries) U802146\n Linux (Power) Not applicable\n\nv6.0\n Platform Refresh Pack 6.0.1.0\n------- --------------------\n Windows U200243\n AIX U803805\n HP-UX (PA-RISC) U803943\n Solaris (SPARC) U803944\n iSeries SI17318\n Linux (x86) U803945\n Linux (zSeries) U803946\n Linux (Power) U803947\n\nThe latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\nIf the maintenance level is not yet available, information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q251", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n SE19791\nREPORTED COMPONENT NAME\n WEB MQ FOR ISER\nREPORTED COMPONENT ID\n 5724B4106\nREPORTED RELEASE\n 530\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2005-04-05\nCLOSED DATE\n 2005-04-12\nLAST MODIFIED DATE\n 2007-08-02\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q251", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEB MQ FOR ISER\nFIXED COMPONENT ID\n 5724B4106", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q251", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R530 PSY SI18375\n UP05/09/01 I 1000\n\nz/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q251", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The z/OS system hung, and an IPL was required. A standalone dump\n showed that many jobs, including *MASTER*, DMPSRV, CONSOLE,\n OMVS, JES2, and user jobs such as brokers, were in an ENQ wait\n for resource NAME=MAJOR=NETMAGDB (a resource for a 3rd party\n product). The ENQ was held by a broker job that was going\n through MEMTERM processing due to an ABENDS40D.\n .\n The dump of the *MASTER* address space showed that the TCB for\n memterm processing for the ENQ owner was waiting in MQ. SYSTRACE\n of the *MASTER* address space showed that the MEMTERM TCB was in\n a loop of WAIT, STORAGE RELEASE, and STORAGE OBTAIN every\n second. The WAIT PSW was in CSQ3RRSX+x'185C' (UK94940) in\n routine SETDIE. It was called from EBACTL_RETRY2 to wait for 1\n second at a time for EBACTL to be turned on for a thread for the\n broker job. The TCB for that thread was alrady gone.\n .\n The MQ change team found that the code added by PM75418 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM75418] can\n cause memterm processing to hang indefinitely. Presumably the\n fact that memterm processing hung prevented subsequent memterm\n processing by z/OS from releasing the NETMAGDB ENQ.\n .\n Additional Symptom(s) Search Keyword(s):\n hang MQ NETMAGDB looping ABEND40D S40D ABEND 40D SAD", "logical_doc_id": 5, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q251", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *\nRelease 0 Modification 1 and Release 1 *\nModification 0. *\n\nPROBLEM DESCRIPTION: After applying the PTF for PM75418 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM75418], *\nUK91873 / UK91874, MEMTERM processing *\nfor an address space connected to MQ is *\nhanging. *\nThe LPAR may potentially become *\nunresponsive. *\n\nRECOMMENDATION: *\n\nThe connected address space has experienced abends, and has then\n been MEMTERM'ed with S40D. During MEMTERM processing, context\n services has invoked CSQ3RRSX for END_CONTEXT processing. The\n ACE associated with the context has EBACTL set off, indicating\n that it is in MQ code. CSQ3RRSX therefore waits for EBACTL to be\n set back on.\n However, EBACTL will never get set back on as the address space\n that it was running under has been MEMTERM'ed.", "logical_doc_id": 5, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q251", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The code was changed to not wait for EBACTL to be turned back on\n if the connected address space has been MEMTERM'ed, preventing\n the hang from occurring.\n 010Y\n 100Y\n CSQARIB\n CSQMCLMT\n CSQMCTXE\n CSQMCTXS\n CSQ3AAES\n CSQ3AMT3\n CSQ3RRSF\n CSQ3RRSI\n CSQ3RRSM\n CSQ3RRSR\n CSQ3RRSX\n CSQ3RRXF\n CSQ5CONN\n CSQ5MONR\n\nTEMPORARY FIX\n\nHIPER *", "logical_doc_id": 5, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q251", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI20391\nREPORTED COMPONENT NAME\n WMQ Z/OS V7\nREPORTED COMPONENT ID\n 5655R3600\nREPORTED RELEASE\n 010\nSTATUS\n CLOSED PER\nPE\n YesPE\nHIPER\n YesHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-06-19\nCLOSED DATE\n 2014-07-10\nLAST MODIFIED DATE\n 2014-08-04\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n UI19493 UI19494\n\nMODULES/MACROS\nCSQARIB CSQMCLMT CSQMCTXE CSQMCTXS CSQ3AAES\n CSQ3AMT3 CSQ3RRSF CSQ3RRSI CSQ3RRSM CSQ3RRSR CSQ3RRSX CSQ3RRXF\n CSQ5CONN CSQ5MONR", "logical_doc_id": 5, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q251", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ Z/OS V7\nFIXED COMPONENT ID\n 5655R3600", "logical_doc_id": 5, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q251", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R010 PSY UI19493 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI19493]\n UP14/07/22 P F407 \u00ae\nR100 PSY UI19494 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI19494]\n UP14/07/22 P F407 \u00ae\n\nFIX IS AVAILABLE\nSELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL. YOU WILL BE REQUIRED TO SIGN IN. DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES.", "logical_doc_id": 5, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q022", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "The Edge Caching Proxy component of WebSphere Application Server may be vulnerable to an HTTP response splitting attack. This is a separate install from WebSphere Application Server. You only need to apply this if you use the Edge Caching Proxy.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q022", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2017-1503 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1503]\nDESCRIPTION: IBM WebSphere Application Server is vulnerable to HTTP response splitting attacks. A remote attacker could exploit this vulnerability using specially-crafted URL to cause the server to return a split response, once the URL is clicked. This would allow the attacker to perform further attacks, such as Web cache poisoning, cross-site scripting, and possibly obtain sensitive information.\nCVSS Base Score: 6.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/129578 [https://exchange.xforce.ibmcloud.com/vulnerabilities/129578] for the current score", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q022", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM WebSphere Application Server Edge Caching Proxy Version 7.0, 8.0, 8.5, & 9.0", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q022", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "The recommended solution is to apply the Fix Pack or PTF for each named product as soon as practical.\n\nFix:\nApply an Interim Fix, Fix Pack or PTF containing APAR PI82587 if you use the Edge Caching Proxy component (separate install from WebSphere Application Server) as noted below: [https://www-304.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nFor IBM WebSphere Application Server\nFor V9.0.0.0 through 9.0.0.4:\nUpgrade to 9.0.0.3 fix pack level then apply Interim Fix PI82587 [http://www-01.ibm.com/support/docview.wss?uid=swg24044131]\n- OR * Upgrade to 9.0.0.4 fix pack level then apply Interim Fix PI82587 [http://www-01.ibm.com/support/docview.wss?uid=swg24044131]\n- OR * Apply Fix Pack 5 (9.0.0.5), or later.\n\nFor V8.5.0.0 through 8.5.5.12: * Upgrade to 8.5.5.11 fix pack level then apply Interim Fix PI82587 [http://www-01.ibm.com/support/docview.wss?uid=swg24044131]\n- OR * Upgrade to 8.5.5.12 fix pack level then apply Interim Fix PI82587 [http://www-01.ibm.com/support/docview.wss?uid=swg24044131]\n- OR * Apply Fix Pack 13 (8.5.5.13), or later (targeted availability 5 February 2018).\n\nFor V8.0.0.0 through 8.0.0.1 3: * Apply Fix Pack 14 (8.0.0.14), or later.\n\nFor V7.0.0.0 through 7.0.0.43: * Upgrade to a minimum of 7.0.0.41 fix pack level then apply Interim Fix [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%2FWebSphere&product=ibm/WebSphere/WebSphere+Application+Server&release=All&platform=All&function=fixId&fixids=8.5.5-WS-EDGECP-FP00000071&includeSupersedes=0]PI82587 [http://www-01.ibm.com/support/docview.wss?uid=swg24044131]\n- OR * Apply Fix Pack 45 (7.0.0.45), or later (targeted availability 2Q 2018).\n\nFor more details about WAS fixpack refer to link http://www-01.ibm.com/support/docview.wss?uid=swg22006815 [http://www-01.ibm.com/support/docview.wss?uid=swg22006815] WORKAROUNDS AND MITIGATIONS\nMitigation is to apply relevant WAS fixpack. For more detail refer to link http://www-01.ibm.com/support/docview.wss?uid=swg22006815 [http://www-01.ibm.com/support/docview.wss?uid=swg22006815]", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q022", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q022", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q022", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nThe 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\nPRODUCT ALIAS/SYNONYM\n Leads\n\nPAODownloadDocument; Passport advantage; 7.5.0; Windows DOWNLOADABLE FILES", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q022", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This document provides the eAssembly part numbers that are required to download IBM Business Process Manager Advanced - Process Server V7.5 files from Passport Advantage.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q022", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Note: You cannot create a Process Center profile with this image. If you want to create a Process Center profile, see Download IBM Business Process Manager Advanced V7.5 for Windows platforms [http://www.ibm.com/support/docview.wss?uid=swg24029288].\n\nIBM Business Process Manager is a comprehensive and consumable business process management platform that provides visibility and management of business processes. It includes tools and a runtime environment, for process design, execution, monitoring, and optimization. It is specifically designed to enable process owners and business users to engage directly in the improvement of their business processes.\n\nThis document provides the eAssembly part numbers required for download of the IBM Business Process Manager Advanced - Process Server V7.5 product from the Passport Advantage website [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm].\n\nMore information\nSee the Latest information and critical fixes for Business Process Manager Advanced [http://www.ibm.com/support/search.wss?q=ibpma75relnotes], Release notes [http://www.ibm.com/support/docview.wss?uid=swg27021575], and IBM Business Process Manager Advanced product package [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5mx/topic/com.ibm.wbpm.imuc.ebpm.doc/topics/cins_bpm_pc_ps_package.html].\n\nSpace requirements\nRefer to the Hardware and software requirements [http://www.ibm.com/support/docview.wss?uid=swg27023005] page for this platform for space requirements.\n\nDownloading and assembling the product\n\n1. Ensure that your workstation has sufficient space to store both the files you must download from IBM Passport Advantage and the extracted installation image.\n\n2. Navigate to the Passport Advantage website [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm] and download all of the parts that you need. The parts are listed by platform in the tabbed sections of this document.\n (For information about how to access Passport Advantage, see the Passport Advantage Quick reference guide in the Learn more section on the Passport Advantage website [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm].)\n\n3. Download all required parts for the product installation image from IBM Passport Advantage to a temporary directory.\n\n4. Extract the downloaded files to one directory.\n\n5. Open the Quick Start Guide located in the Quick Start image to access documentation to help with product installation.\n\nTAB NAVIGATION\nAIX [http://www.ibm.com/support/docview.wss?uid=swg24029617]- selected tab,\nLinux [http://www.ibm.com/support/docview.wss?uid=swg24029619]\nSolaris [http://www.ibm.com/support/docview.wss?uid=swg24029852]\nWindows [http://www.ibm.com/support/docview.wss?uid=swg24029620]- selected tab,\n\nSupported platforms\n\nFor supported platforms, including required version levels, refer to Hardware and software requirements [http://www.ibm.com/support/docview.wss?uid=swg27023005].\n\nDownloadable parts\n\nTo install IBM Business Process Manager Advanced-Process Server on a Windows platform, download the following images.", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q022", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Required and optional parts are labeled in the tables. Your need for parts depends on your usage and configuration choices. Components that you might want to use in your topology, but which run on another platform, can be found on the tabbed page that corresponds to that platform.\n\nRequired software\neAssembly Image Description CREX6ML\n\n[/support/docview.wss?uid=swg24029620&aid=1] CI0KCML IBM Business Process Manager Advanced-Process Server V7.5 Quick Start Guide CI0BKML\nCI0BLML\nCI0BMML IBM Process Server Advanced Version 7.5 For Windows 32-bit and 64-bit\n\nMake sure to download all 3 images and extract all 3 images to the same location.\n\nIncludes: * IBM Business Process Manager Advanced-Process Server V7.5\nIBM WebSphere Application Server Network Deployment V7.0.0 Fix Pack 17\nIBM WebSphere Application Server Feature Pack for XML V1.0.0 Fix Pack 9\nIBM WebSphere Application Server Feature Pack for SCA V1.0.1 Fix Pack 11\nIBM DB2 Express V9.7.4\n\nOptional software\nIBM WebSphere Application Server Network Deployment V7.0 supplements\nUse the following supplemental software if you are using a separate HTTP server or need to do load balancing.\n\neAssembly Image Description CREX6ML\nC1G2HML\nC1G2IML IBM WebSphere Application Server Network Deployment V7.0 Supplements for Windows on Intel, 32-bit\n\nMake sure to download both images and extract both images to the same location. C1G2KML\nC1G2LML IBM WebSphere Application Server Network Deployment V7.0 Supplements for Windows on AMD, 64-bit\n\nMake sure to download both images and extract both images to the same location.\nIBM DMZ Secure Proxy Server\n\neAssembly Image Description CREX6ML\nC1G1EML IBM DMZ Secure Proxy Server V7.0 for Windows 32-bit CZB5EML IBM DMZ Secure Proxy Server V7.0 for Windows 64-bit\nIBM WebSphere Application Server Network Deployment Edge Components\n\neAssembly Image Description CREX6ML C1I4YML IBM WebSphere Application Server Network Deployment Edge Component for Windows 32-bit ESD only C1I50ML IBM WebSphere Application Server Network Deployment Edge Component for Windows 64-bit ESD only C1I4ZML IBM WebSphere Application Server Network Deployment Edge Component for IPv6 V7.0 for Windows on x86 32-bit ESD only C1I51ML IBM WebSphere Application Server Network Deployment Edge Component for IPv6 V7.0 for Windows on x86 64-bit ESD only\n\nIBM Tivoli software", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q022", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "eAssembly Image Description CREX6ML C1HN9ML IBM Tivoli Access Manager for e-business V6.1 for Windows 32-bit/64-bit CZKC3ML IBM Tivoli Directory Server V6.3 Client-Server with entitlement (compressed file) for Windows, 32-bit, Multilingual CZKG4ML IBM Tivoli Directory Server V6.3 Client-Server with entitlement (compressed file) for Windows on x86, 64-bit, Multilingual C1HW2ML IBM Tivoli Composite Application Manager for WebSphere Application Server V7.0 for Windows on Intel, 32-bit / 64-bit C1LY4ML IBM Rational Agent Controller for Windows on Intel, 32-bit and Linux on Intel 32-bit\nIBM DB2 Enterprise Server Edition V9.7\nUse the following supplemental software if you do not already have a database to use with Business Process Manager and want to use DB2.\n\neAssembly Image Description CREX6ML CZL3UML IBM DB2 Enterprise Server Edition V9.7 Restricted Use Quick Start and Activation CZ19HML IBM DB2 Enterprise Server Edition V9.7 for Windows on 32-bit AMD and Intel systems (x86) Multilingual CZ19IML IBM DB2 Enterprise Server Edition V9.7 for Windows on 64-bit AMD and Intel EM64Tsystems (x86) Multilingual\nRational Application Developer V7.5\n\neAssembly Image Description CREW9ML C1KJ4ML IBM Rational Application Developer AD V7.5 Setup\nfor 32-bit and 64-bit and for Linux on System z 31-bit C1KJ5ML\nC1KJ6ML\nC1KJ7ML\nC1KJ8ML\nC1KJ9ML IBM Rational Application Developer AD V7.5\nfor 32-bit and 64-bit and for Linux on System z 31-bit\n\nMake sure to download all 5 images and extract all 5 images to the same location.\n\nMultilingual Fonts for IBM WebSphere Application Server Network Deployment\n\neAssembly Image Description CREW9ML C1G24ML WorldType Fonts for Multiplatform, Multilingual for IBM WebSphere Application Server Network Deployment V7.0, 32-bit and 64-bit\n\nPREREQUISITES\nSee the following website for the prerequisites for Business Process Manager Advanced for Windows:\n\nURL LANGUAGE SIZE(Bytes) Detailed hardware and software requirements [http://www.ibm.com/support/docview.wss?uid=swg27023005] English 200000\nINSTALLATION INSTRUCTIONS\nMake sure to download the Quick Start Guide from your product eAssembly. Open the PDF file, and follow the instructions to install the product.\n\nDetailed installation instructions for your product are available on the Business Process Management information center [http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5mx/index.jsp].\n\nDOWNLOAD PACKAGE\nDownload IBM Business Process Manager Advanced - Process Server V7.5 for Windows platforms from IBM Passport Advantage Online at http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm].\n\nTECHNICAL SUPPORT\n See Passport Advantage Online support at:\nhttp://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html [http://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html].\n\nSee Business Process Manager Advanced support at:\nhttp://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_Business_Process_Manager_Advanced [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_Business_Process_Manager_Advanced].\n\nFeature Pack; EJB FLASH (ALERT)", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q022", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "IBM\u00ae WebSphere\u00ae Application Server Feature Packs are optionally installable product extensions that offer targeted, incremental new features.", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q022", "section_id": 3, "heading": "CONTENT", "parent": null, "text": "WebSphere Application Server V6.1 Feature Pack for EJB 3.0 delivers several new technologies, including EJB 3.0 and Java\u2122 Persistence API (JPA), which are key technologies of Java Platform, Enterprise Edition 5 (Java EE 5). This feature pack includes production support with Application Server V6.1.\n\nEasy to Develop\nThe EJB 3.0 specification simplifies the development of business logic for enterprise applications. EJB 3.0 simplifies development by allowing developers to program EJB components as POJOs with Java business interfaces.\n\nAnnotations now provide component metadata, so it is no longer necessary to create XML deployment descriptors.\n\nAssociated with the EJB 3.0 specification is the JPA specification. The Feature Pack for EJB 3.0 includes an implementation of this as well. JPA simplifies the entity persistence model by leveraging many of the features in open-source persistence frameworks. JPA uses a simple, yet robust, object relational mapping layer over the top of typical Java Database Connectivity (JDBC) resource usage patterns. This architecture uses simple JavaBeans classes (POJO) to represent relational database content, which enables developers to use basic resource access patterns to fetch and store state in the database.\n\nEasy to Test\nIt is also now possible to easily test outside the container using typical JUnit test patterns. This increases the rapid development productivity by reducing the time for the edit-compile-deploy-debug cycles currently associated with Java Enterprise Edition applications.\n\nPersistence testing has also been simplified. It is now possible to test outside of the container environment either without the database (using just simple POJO classes that represent state) or with the database (for example, allowing testing of queries, relationships, and inheritance).\n\nConfigurable and Extensible\nJPA persistence support can be configured and extended to meet a variety of needs including, but not limited to:\nPessimistic or optimistic locking\nLarge query result sets\nCaching\nXML type mapping\nBatch updates\n\nHardware Prerequisites\nAny hardware that supports Application Server V6.1 or higher Software Prerequisites\nWebSphere Application Server V6.1\n\nFeature Pack for EJB 3.0 version 6.1\nWebSphere Application Server Feature Pack for EJB 3.0 [https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?&source=swg-wasfpejb3]\n\nMandatory ++APAR for IBM WebSphere Application Server V6.1 Feature Pack for EJB 3.0 on z/OS [http://www.ibm.com/support/docview.wss?rs=404&uid=swg21288940]\n\nPK56653; 6.1.0.13: Enable application update via RAD to EJB 3.0 Feature pack [http://www.ibm.com/support/docview.wss?rs=180&uid=swg24017666]\n\nInformation Center\nWebSphere Application Server Feature Pack for EJB 3.0 [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v610ejb&product=was-base-dist]\n\nFeature Packs by Version\nAccess Feature Packs by version [http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27008534]as they become available\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server for z/OS z/OS 6.1 Feature Pack for EJB 3.0 Application Servers WebSphere Application Server for z/OS z/OS 6.1", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q022", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "New WAS packaged in RAD:\n\nRational Application Developer for WebSphere packages WebSphere Application Server for development and test purposes. WAS recently renamed WAS for Developers (WAS4D) to WAS ILAN (see here [https://developer.ibm.com/wasdev/downloads/#asset/WAS_traditional_for_Developers]). In response to this change, RAD 9.6 now packages WAS ILAN available in the RAD_WS_9.6_WASTE_9.0.zip file. It has the same capabilities and updates that RAD users expect.\n\nSupport for this new WAS packaged in RAD:\nNew message during installation has worried users, however, users with an active support contract for their production WebSphere Application Server are entitled for support on the developer machine as long as an active support contract is in place for the production server.\nEvaluation software page: https://www.ibm.com/developerworks/downloads/ws/wasdevelopers/index.html [https://www.ibm.com/developerworks/downloads/ws/wasdevelopers/index.html]\nFAQ: https://www.ibm.com/developerworks/downloads/ws/wasdevelopers/faq-wasdevelopers.html [https://www.ibm.com/developerworks/downloads/ws/wasdevelopers/faq-wasdevelopers.html]", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q022", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To change/upgrade RAD 9.6 WAS4D to WAS ILAN.\n\nAdd the following repository to Installation Manager: https://www.ibm.com/software/repositorymanager/com.ibm.websphere.ILAN.v90/ [https://www.ibm.com/software/repositorymanager/com.ibm.websphere.ILAN.v90/]\n\nV7Rnotes PRODUCT DOCUMENTATION", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q022", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This document describes how to download IBM WebSphere Application Server for Developers Version 7.0 for Windows installation images from the IBM Passport Advantage Online Web site.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q022", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM WebSphere Application Server is the premier Java\u2122 Platform, Enterprise Edition (Java EE) and Web services-based application server. WebSphere Application Server is built on open standards and helps you deploy and manage applications ranging from simple Web sites to powerful on-demand solutions.\n\nMore information\nTo access a wide variety of technical resources for this product, see the Information Centers for WebSphere Application Server Version 7.0 [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-base-dist&].\n\nSpace requirements\n800 MB of disk space to store the required downloadable parts plus 900 MB of disk space to unpack the parts.\n1 GB (1000 MB) of disk space to install the product without profiles and 1.25 GB (1250 MB) for a cell installation.\n30 MB of space in the tmp directory to run the installation program.\nFor more detailed information, see the WebSphere Application Server detailed system requirements [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27006921] document.\n\nDownloading and assembling the product 1. Navigate your browser to the Find Downloads and Media [http://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/sdma/SDMA?PO=DOWNLOAD_FIND_BY_PART_NUMBER] Web page on the IBM Passport Advantage Online Web site.\n 2. Select the Find by part number search option under Download finder options.\n 3. Search for each downloadable image by part number.\n 4. Download all of the required parts.\n 5. Use a file extracting utility that supports large file extractions to unpack each of the parts into a single, temporary directory on your system.\n 6. Open the Quick Start Guide, which is located on the Quick Start CD. Follow step three through step nine of the Quick Start Guide to access the documentation to help with product installation.\n\nTAB NAVIGATION\nAIX [http://www.ibm.com/support/docview.wss?uid=swg27012952]\nHP-UX [http://www.ibm.com/support/docview.wss?uid=swg27012951]\nIBM i [http://www.ibm.com/support/docview.wss?uid=swg27013249]\nLinux [http://www.ibm.com/support/docview.wss?uid=swg27012950]\nSolaris [http://www.ibm.com/support/docview.wss?uid=swg27012948]\nWindows- selected tab,\n\nSupported operating systems * Microsoft Windows on x86-32 bit architecture\n\nDownloadable parts\nThere are ten downloadable parts for the Windows operating systems. Refer to the following tables for details about what each part contains. At a minimum, you must download the required parts.\n\nRequired parts\nTo install WebSphere Application Server for Developers Version 7.0 on the Windows operating system, download the following parts:\n\nPart Description File name (part number.extension) Download 1 of 12: WebSphere Application Server for Developers V7.0 Quick Start, Multilingual CZ0KFML.zip Download 2 of 12: WebSphere Application Server for Developers V7.0 for Windows C1T3TML.zip\nOptional parts", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q022", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Part Description File name (part number.extension) Download 3 of 12: WebSphere Application Server for Developers V7.0 Supplements for Windows (1 of 2) C1FV5ML.zip WebSphere Application Server for Developers V7.0 Supplements for Windows (2 of 2) C1FV6ML.zip Download 4 of 12: IBM WebSphere Installation Factory V7.0 C1F8XML.zip Download 5 of 12: WebSphere Application Server V7.0.0 Feature Pack for Web 2.0 for Windows, Multilingual C1P3SML.zip Download 6 of 12: IBM Rational Application Developer Assembly and Deployment Features for WebSphere Software V7.5 for Multiplatforms Setup Disk, Multilingual C1KJ4ML.zip Rational Application Developer Assembly and Deployment Features for WebSphere Software V7.5 for Multiplatforms (1 of 5) C1KJ5ML.zip Rational Application Developer Assembly and Deployment Features for WebSphere Software V7.5 for Multiplatforms (2 of 5) C1KJ6ML.zip Rational Application Developer Assembly and Deployment Features for WebSphere Software V7.5 for Multiplatforms (3 of 5) C1KJ7ML.zip Rational Application Developer Assembly and Deployment Features for WebSphere Software V7.5 for Multiplatforms (4 of 5) C1KJ8ML.zip Rational Application Developer Assembly and Deployment Features for WebSphere Software V7.5 for Multiplatforms (5 of 5) C1KJ9ML.zip Download 7 of 12: IBM Support Assistant Workbench V4.0.2 for Windows on x86 C1G27ML.zip Download 8 of 12: IBM Support Assistant V4.0 Agent for Window on x86-32 bit, Multilingual C1G28ML.zip Download 9 of 12: IBM Tivoli Access Manager for e-Business V6.1 for Windows 32 bit /64 bit, Multlingual C1HN9ML.zip Download 10 of 12: IBM Tivoli Directory Server 6.1 Client-Server with entitlement, GSKit 7.0.3.30 for Windows 32bit, Multilingual C12X6ML.zip IBM Tivoli Directory Server 6.1, DB2 v9.1 Fix Pack 02 for Windows 32bit, Multilingual C12X8ML.zip IBM Tivoli Directory Server 6.1 eWebSphere 6.1.0.7, Tivoli Directory Integrator 6.1.1 for Windows 32bit, Multilingual C12X9ML.zip Download 11 of 12: IBM Tivoli Composite Application Manager for IBM WebSphere Application Server V7.0 C1HW2ML.zip Download 12 of 12: IBM DB2 for Linux, UNIX and Windows V9.5 - Limited Use for Linux on x86-64 bit and Linux EMT64 systems (x64), English C1HQ8ML.zip", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q022", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "Interim Fixes for Application Server V7.0.0.0 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg24020613]\n\nORIGINAL PUBLICATION DATE\n 2008/9/26", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q170", "section_id": 0, "heading": "ENVIRONMENT", "parent": null, "text": "IBM Connections 5.0.0.0 CR1", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q170", "section_id": 1, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "The SystemOut.log on node is reporting the below OutOfMemoryErrors\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n\nJavacore and heapdump files are produced when this issue occurs. The javacore shows it was generated due to OOM caused by heap exhaustion, although heap was not fully expanded, there were many consecutive very large allocation requests. After analyzing the heapdump logs you can see that the java.lang.string is suspected mostly as the memory leak.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q170", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "IBM Connections Quality engineering is aware of the issue and it has been addressed in APAR# LO83405, which is included in Connections 5.0 CR3.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q170", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "LO83405: OUTOFMEMORYERROR ON BLOGS WITH SPECIFIC CONTEN [http://www-01.ibm.com/support/docview.wss?uid=swg1LO83405]", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q170", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "The reason for the 404 error can be determined by recreating and tracing the ODR server and application server.\nTracing the application server using the following trace string:\n\nServlet_Engine=all=enabled\nTracing the ODR server using the following trace string:\n\ncom.ibm.ws.proxy.*=all=enabled\nThe following outlines two scenarios causing the 404 error: * Scenario 1 - User Error\n This scenario reviews a common problem where the user types an invalid URL for their application. Reviewing the ODR server trace.log we can see the request arrive and the error message returned from the application server:\n\n [11/2/04 20:46:47:297 EST] 67f1de90 HttpProxyServ < requestArrived - Received request; method=GET uri=/FinancialAdvice/CpuAndSleepBound service context=HttpProxyServiceContextImpl@4fb0de9d connection link=HttpProxyConnectionLink@3c415e9d\n ...\n [11/2/04 20:46:47:906 EST] 4f655e93 HttpProxyServ < responseArrived\n [11/2/04 20:46:47:906 EST] 4f655e93 HttpProxyConn d Status code=Status code: 404 response body allowed; service context=HttpProxyServiceContextImpl@4fb0de9d, connection link=HttpProxyConnectionLink@3c415e9d\n Reviewing the application server trace.log we can see the message arrive and the error message returned:\n [11/2/04 20:46:47:359 EST] 12d9f3a ServletReques > dispatchByURI\n /FinancialAdvice/CpuAndSleepBound\n ...\n [11/2/04 20:46:47:875 EST] 12d9f3a WebApp d Exception message=File not found: /CpuAndSleepBound\nScenario 2 - ODR Configuration\n This scenario reviews an ODR server configuration problem where an ODR server proxy port is not mapped to the appropriate virtual host. Reviewing the ODR server trace.log we can see the request arrive and then a 404 error because the ODR cannot properly map the request to an enterprise application:\n\n [11/2/04 21:42:40:156 EST] 6982e513 HttpProxyServ < requestArrived - Received request; method=GET uri=/FinancialAdvice/CpuAndSleepBound service context=HttpProxyServiceContextImpl@5d426517 connection link=HttpProxyConnectionLink@5cd52517\n ...\n [11/2/04 21:42:40:156 EST] 6982e513 MapRequestFil d failed to map request to application: com.ibm.ws.http.channel.impl.HttpRequestMessageImpl@4a56515\n ...\n [11/2/04 21:42:40:172 EST] 6982e513 HttpFilterCha d Filter=HTTP Mapper generated error status code=Status code: 404 for service context=HttpProxyServiceContextImpl@5d426517. Generating error response and breaking request chaining.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q170", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The following are the two solutions to the preceding scenarios.\nScenario 1 - User Error Solution\n Review the EAR file to determine the correct urls and if the url used above is valid. From the application.xml you can find the context root for the Web modules. Find the Web module, FinancialAdvice.war, that corresponds to the FinancialAdvice context root, shown below:\n\nFinancialAdvice.war\n /FinancialAdvice\n From the web.xml file for the FinancialAdvice.war we can find all valid url patterns for the application. You should find the following if this was a valid URL:\n /CpuAndSleepBound\n But for this scenario, you would not find the preceeding xml entry in the web.xml because the Web page URL was invalid.\nScenario 2 - ODR Configuration Solution\n The proxy port setting for the ODR is not mapped to the appropriate virtual host group. This can be done using the administrative console: 1. Find the ODR proxy http 1. Expand the Servers topology\n 2. Select the On Demand Routers entry.\n 3. Under Additional Properties select the End Points.\n 4. Select the PROXY_HTTP_ADDRESS entry to find the ODR host/port settings\n\n2. Add a new alias for the ODR proxy http port in the interested virtual host group: 1. Expand the Environment topology.\n 2. Choose the Virtual Hosts entry.\n 3. Choose appropriate virtual host group (for example: \"default_host\")\n 4. Under Additional Properties select the Host Aliases.\n 5. Click New to create a new alias\n 6. Fill out the correct host/port entry (for example: the ODR proxy http port information).\n 7. Click OK.\n 8. Save and synchronize the change.\n\n3. Recycle the ODR and application servers to pick up the new virtual host alias. The configuration information can be seen below. From the serverindex.xml file you can find the http proxy address used by the ODR. This port was used in the url by the user to hit the ODR so it can route the request to the running server.\n\n\n \" port=\"83\"/>\n \n Review the web module information to determine the virtual host mapping located in the ibm-web-bnb.xmi file, search for \"virtualHostName\" entry. This mapping will show the actual virtual host requiring the http proxy port alias. For this example we will assume it is the \"default_host\" group.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q170", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The virtualhost.xml file will show the list of port aliases for the interested virtual host group where we should find under the interested virtual host the ODR proxy http port, port 83 for this example.\n \n ...\n \n \n Note: If the port is 80, then the following entry in the virtualhost.xml file will show the following:\n \n\nPK59793; PK59793; PK59793 DOWNLOADABLE FILES", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q170", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "java.lang.NullPointerException is seen on the On-Demand Router (ODR) when HTTP requests are flowing.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q170", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "PK59793 resolves the following problem:\n\nERROR DESCRIPTION:\nIBM\u00ae WebSphere\u00ae Extended Deployment V6.1 maintenance mode feature does not work as expected. After placing a server into maintenance mode, intermittent HTTP 1.1 500 responses are returned when attempting to establish a session.\n\nThe server state was not being initialized. The following exception is thrown:\n\nHttpFilterCha E PROX0050E: Caught unhandled exception from doFilter in filter=XD load balance filter.; exception=java.lang.NullPointerException at\ncom.ibm.ws.xd.dwlm.client.XDTargetServerImpl.isUp(XDTargetServerImpl.java:234) at\ncom.ibm.ws.dwlm.client.TargetServerImpl.isAvailable(TargetServerImpl.java:178) at\ncom.ibm.ws.xd.dwlm.client.XDTargetServerImpl.isAvailable(XDTargetServerImpl.java:226)\n\nLOCAL FIX:\nN/A", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q170", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\nAll users of WebSphere Extended Deployment V6.1 using the On Demand Router.\n\nPROBLEM DESCRIPTION:\njava.lang.NullPointerException is seen on the On-Demand Router (ODR) when HTTP requests are flowing.\n\nRECOMMENDATION:\nNone\n\nThe following exception is seen in the ODR logs during traffic:\n\n[1/21/08 9:59:58:095 PST] 00000018 HttpFilterCha E PROX0050E: Caught unhandled exception from doFilter in filter=XD load balance filter.; exception=java.lang.NullPointerException at com.ibm.ws.xd.dwlm.client.XDTargetServerImpl.isUp(XDTargetServerImpl.java:234) at\ncom.ibm.ws.dwlm.client.TargetServerImpl.isAvailable(TargetServerImpl.java:178) at\ncom.ibm.ws.xd.dwlm.client.XDTargetServerImpl.isAvailable(XDTargetServerImpl.java:226)\n\nPROBLEM CONCLUSION:\nThe code was fixed to avoid the exception and the fix was made available for the 6.1.0.0 release. The fix will be included in Service Pack 6.1.0.1 for WebSphere Extended Deployment.\n\nPREREQUISITES\nPlease download the UpdateInstaller below to install this fix.\n\nURL LANGUAGE SIZE(Bytes) UpdateInstaller [http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24012718] US English 7250000\nINSTALLATION INSTRUCTIONS\nPlease review the readme.txt for detailed installation instructions.\n\nURL LANGUAGE SIZE(Bytes) Readme [ftp://public.dhe.ibm.com/software/websphere/extended/support/fixes/PK59793/readme.txt] US English 5683\nDOWNLOAD PACKAGE\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is DD? [http://www6.software.ibm.com/dldirector/doc/DDfaq_en.html] 6.1.0.0-WS-WXD-IFPK59793 01-25-2008 US English 189966 FTP [ftp://public.dhe.ibm.com/software/websphere/extended/support/fixes/PK59793/6.1.0.0-WS-WXD-IFPK59793.pak] DD\nTECHNICAL SUPPORT\n Contact IBM Support using SR (http://www-306.ibm.com/software/support/probsub.html [http://www-306.ibm.com/software/support/probsub.html]), visit the WebSphere Extended Deployment Support Web site (http://www.ibm.com/software/webservers/appserv/extend/support/ [http://www.ibm.com/software/webservers/appserv/extend/support/]), or contact 1-800-IBM-SERV (U.S. only).\n\n [/support/docview.wss?uid=swg24018242&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24018242&aid=2]Problems (APARS) fixed\nPK59216, PK59793\n\n SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q170", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The GenPluginCfg utility creates default URIs as:\n \n \n \n \n \n \n\nWhile in the plugin--cfg.xml that the ODR generates it adds\n extra slash (/).\n\n\n \n \n \n \n \n \n\nOnly the name attribute is of interest from a consistently\n viewpoint.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q170", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Users with WepSphere Application Server *\nNetwork Deployment 6.0.2 who need to *\ninstall WebSphere Application Server *\nExtended Deployment 6.0 *\n\nPROBLEM DESCRIPTION: The plugin-cfg.xml file generated by *\nthe ODR had an extra leading forward *\nslash (/) in it causing HTTP plugin *\nload failure. *\n\nRECOMMENDATION: *\n\nODR malformed URI causes HTTP plugin load failure", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q170", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The problem was resolved by changing code to ensure that the\n generated URI that goes into the plugin-cfg.xml file does not\n contain an extra forward slash (/).\n\nThe fix for this APAR is currently targeted for inclusion\n in fixpack 6.0.2.1.\n Please refer to the recommended updates page for delivery\n information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q170", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PK08425\nREPORTED COMPONENT NAME\n WEBS APP SERV N\nREPORTED COMPONENT ID\n 5724H8800\nREPORTED RELEASE\n 60W\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2005-07-06\nCLOSED DATE\n 2005-08-24\nLAST MODIFIED DATE\n 2005-08-24\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\nPLUGIN", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q170", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBS APP SERV N\nFIXED COMPONENT ID\n 5724H8800", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q170", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R60A PSY\n UP\nR60H PSY\n UP\nR60I PSY\n UP\nR60P PSY\n UP\nR60S PSY\n UP\nR60W PSY\n UP\nR60Z PSY\n UP", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q170", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The original load of classification attributes for the authorized CIs\n\nhad misspellings in the attribute names. These \"bad\" attributes have\nbeen removed and the correct ones added using the CI Space Loader tool.\nThe problem is that the correct attributes are not being added to the\nCIs when they are promoted with the update and copy attributes options\nchecked.\n\nOnce the attribute names were fixed I tried to recreate the CIs from the Select Action menu. After the operation completed there was no change to the CI in the authorized space.", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q170", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The key problem is that the CI Space Loader tool is not compatible\nwith the Update Promotion eFeature in certain scenarios. In particular,\nif you use the CI Space Loader tool to add CI Attributes to a CI Type\nafter CI instances have been created with promotion, the Update\nPromotion eFeature will not work correctly. The problem is that the CI\nSpace Loader tool does not use the MBO interface and thus it bypasses\nnew logic that has updated the classification MBO with the eFeature. The\nsupported use case is to add an attribute in the classification\napplication. This will go through all CI instances of that CI Type and\nadd a blank attribute. You can even choose to copy the value for the\nactual CI attribute if you desire. However, there is a known performance\nissue with this function that has been corrected in 7.2. If you have\nmore than 5000 CIs of one CI Type, you may experience OOM exceptions.\nThe work around is to increase the JVM Memory for this operation.\n\nThere are 3 options to correct this:\n\n1) Try the classification \"add attribute\" function and consider increasing JVM memory if needed. This is the officially supported way to handle your use case. Note, delete the attribute before trying to add it again.\n\n2) Delete all of your authorized CIs and then promote again. Do not use\nthe CI Space Loader tool to load new attributes and you will not have\nthis issue again.\n\n3) Use a custom written script to add a blank attribute to each CI\ninstance. Then update promotion will bring the values over from the\nactual Side.", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q097", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "An OpenSSL denial of service vulnerability disclosed by the OpenSSL Project affects GSKit. IBM WebSphere MQ uses GSKit and addressed the applicable CVE.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q097", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2015-1788 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1788]\n\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an error when processing an ECParameters structure over a specially crafted binary polynomial field. A remote attacker could exploit this vulnerability to cause the application to enter into an infinite loop.\n\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103778 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103778] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q097", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM WebSphere MQ 8.0\nFixpack 8.0.0.3 and previous maintenance levels\n\nIBM WebSphere MQ 7.5\nFixpack 7.5.0.5 and previous maintenance levels\n\nIBM WebSphere MQ 7.1\nFixpack 7.1.0.6 and previous maintenance levels\n\nIBM WebSphere MQ 7.0.1\nFIxpack 7.0.1.13 and previous maintenance levels", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q097", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "IBM WebSphere MQ 8.0\nApply Fixpack 8.0.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg21969244]\n\nIBM WebSphere MQ 7.5\nApply Fixpack 7.5.0.6 [http://www-01.ibm.com/support/docview.wss?uid=swg21975660]\n\nIBM WebSphere MQ 7.1\nApply Fixpack 7.1.0.7 [http://www-01.ibm.com/support/docview.wss?uid=swg21965293]\n\nIBM WebSphere MQ 7.0.1\nApply Fixpack 7.0.1.14 (when available), in the interim apply APAR IV77604 [www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=7.0&platform=All&function=aparId&apars=IV77604&source=fc]", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q097", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q097", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q097", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] CHANGE HISTORY\n 11 March 2016: Original version published\n18 March 2016: Updated with details of 7.0.1 interim fix\nThe 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.", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q097", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "OpenSSL vulnerabilities were disclosed on March 1, 2016 by the OpenSSL Project. OpenSSL is used by HP SSL 1.4 on HP OpenVMS. IBM WebSphere MQ on OpenVMS Alpha & Itanium uses HP SSL and has addressed the applicable CVE ( CVE-2016-0800 ) the \u201cDROWN: Decrypting RSA with Obsolete and Weakened eNcryption\" vulnerability.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q097", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-0800 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0800]\n\nDESCRIPTION: OpenSSL could allow a remote attacker to bypass security restrictions. By using a server that supports SSLv2 and EXPORT cipher suites as a Bleichenbacher RSA padding oracle, an attacker could exploit this vulnerability to decrypt TLS sessions between clients and non-vulnerable servers. This vulnerability is also known as the DROWN attack.\nCVSS Base Score: 7.4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/111139 [https://exchange.xforce.ibmcloud.com/vulnerabilities/111139] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N)", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q097", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "The vulnerability affects versions 6.0 of IBM WebSphere MQ on OpenVMS Alpha & Itanium.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q097", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Product VRMF APAR Fix IBM WebSphere MQ on OpenVMS Alpha & Itanium. 6.0.2.12 ,\n6.0.2.13 IT14528 Download the fix from Fix Central [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%2FWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=All&platform=All&function=aparId&apars=IT14528&source=fc]\n\nOn HP OpenVMS, IBM recommends upgrading to WMQ version 6.0.2.12 / 6.0.2.13 and applying the fix and also update HP OpenSSL V1.4 kit to latest HP OpenSSL V1.4 kit supplied by HPE ( Supported environment for MQ V6.0 on OpenVMS can be found here [http://www-01.ibm.com/support/docview.wss?uid=swg27013058] ). After applying the fix, server blocks the use of SSLv2 protocol and \u201cSSLv2 client hello\u201d messages for SSL handshake.\n\nIBM recommends that the same certificate should ONLY be shared with identical server configuration and software.\nIf the same certificate were shared with different server(s) configuration or software, IBM recommends replacing the different server(s) with unique certificates to protect against the DROWN exposure. WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q097", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q097", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 31 March 2016 Original version published\nThe 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.", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q097", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Various IBM WebSphere MQ graphical user interface installers are susceptible to a DLL-planting vulnerability where a malicious DLL, that is present in the Windows search path, could be loaded by the operating system in place of the genuine file.\n\nThe vulnerability affects Windows executable installers downloaded from IBM before 2nd June 2016.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q097", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-2542 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2542]\nDESCRIPTION: Flexera InstallShield could allow a remote attacker to execute arbitrary code on the system. The application does not directly specify the fully qualified path to a dynamic-linked library (schannel.dll) when running on Microsoft Windows. By persuading a victim to open a specially-crafted file from a WebDAV or SMB share using a vulnerable application, a remote attacker could exploit this vulnerability via a specially-crafted library to execute arbitrary code on the system.\nCVSS Base Score: 7.8\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/110914 [https://exchange.xforce.ibmcloud.com/vulnerabilities/110914] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)\n\nCVEID: CVE-2016-4560 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4560]\nDESCRIPTION: Flexera InstallAnywhere could allow a remote attacker to execute arbitrary code on the system. The application does not directly specify the fully qualified path to a dynamic-linked library when running on Microsoft Windows. By persuading a victim to open a specially-crafted file from a WebDAV or SMB share using a vulnerable application, a remote attacker could exploit this vulnerability via a specially-crafted library to execute arbitrary code on the system.\nCVSS Base Score: 7.8\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113016 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113016] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q097", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "The vulnerability affects the executable (.exe file extension) installers, fixpacks and SupportPacs;\nIBM WebSphere MQ for Windows (5.3 - All versions)\nIBM WebSphere MQ for Windows (6.0 - All versions)\nIBM WebSphere MQ for Windows (7.0.0.0 - 7.0.1.13)\nIBM WebSphere MQ for Windows (7.1.0.0 - 7.1.0.7)\nIBM WebSphere MQ for Windows (7.5.0.0 - 7.5.0.6)\nIBM WebSphere MQ for Windows (8.0.0.0 - 8.0.0.4)\nIBM WebSphere MQ Evaluation (8.0.0.0 - 8.0.0.4)\nIBM WebSphere MQ Evaluation (7.5.0.0 - 7.5.0.6)\nIBM WebSphere MQ Evaluation (7.1.0.0 - 7.1.0.7)\nIBM WebSphere MQ File Transfer Edition for Windows (V7.0.0.0 - V7.0.4.4)\nIBM WebSphere MQ File Transfer Edition Trial for Windows (V7.0.0.0 - V7.0.4.4)\nIBM WebSphere MQ Advanced Message Security for Windows (V7.0.1.0 - V7.0.1.3)\nIBM WebSphere MQ Advanced Message Security Trial for Windows (V7.0.1.0 - V7.0.1.3)\nIBM WebSphere MQ for HP NonStop Server V5.3 (Windows Installer V5.3.1.0)\nIBM WebSphere MQ Advanced for Developers (7.5.0.0 - 8.0.0.4)\nMS0T IBM WebSphere MQ Explorer (7.0.1.0 - 8.0.0.4)\nMQC7 IBM WebSphere MQ V7 Clients (All versions)\nMQC71 IBM WebSphere MQ V7.1 Clients (7.1.0.0 - 7.1.0.7)\nMQC75 IBM WebSphere MQ V7.5 Clients (7.5.0.0 - 7.5.0.6)\nMQC8 IBM WebSphere MQ V8 Clients (8.0.0.0 - 8.0.0.4)\n\nWhere fixes are available (see below), you should discard any Windows installation images that were downloaded from IBM before 2nd June 2016 and download new images from Fix Central or Passport Advantage.", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q097", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "The executable installers for the following offerings now contain safeguards to prevent being started in an environment where a malicious DLL could be loaded by the operating system.\n\nThe following offerings, and all subsequent levels of maintenance, have the installer fix applied:\nIBM WebSphere MQ for Windows (6.0.2.12) [http://www.ibm.com/support/fixcentral/quickorder?source=dbluesearch&product=ibm%2FWebSphere%2FWebSphere+MQ&release=6.0&platform=Windows&fixids=6.0.2-WS-MQ-Windows-FP0012]\nIBM WebSphere MQ for Windows (7.0.1.13) [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=7.0.1&platform=All&function=fixId&fixids=7.0.1-WS-MQ-Windows-FP0013]\nIBM WebSphere MQ for Windows (7.1.0.7) [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=7.1&platform=All&function=fixId&fixids=7.1.0-WS-MQ-Windows-FP0007]\nIBM WebSphere MQ for Windows (7.5.0.6) [http://www.ibm.com/support/fixcentral/swg/quickorder?product=ibm/WebSphere/WebSphere+MQ&release=7.5&platform=All&function=fixId&fixids=7.5.0-WS-MQ-Windows-FP0006]\nIBM WebSphere MQ for Windows (8.0.0.5) [http://www.ibm.com/support/fixcentral/swg/quickorder?product=ibm/WebSphere/WebSphere+MQ&release=All&platform=All&function=fixId&fixids=8.0.0-WS-MQ-Windows-FP0005]\nIBM WebSphere MQ File Transfer Edition for Windows (V7.0.4.5) [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+MQ+File+Transfer+Edition&release=7.0.4.4&platform=Windows&function=all]\nIBM WebSphere MQ Advanced Message Security for Windows (V7.0.1.3) [http://www-933.ibm.com/eserver/support/fixes/fixcentral/swg/quickorder?brandid=5&productid=WebSphere+MQ+Advanced+Message+Security&vrmf=7.0.1&platform=Windows&searchtype=browse]\nIBM WebSphere MQ for HP NonStop Server V5.3 (V5.3.1.0 Manufacturing Refresh)\nMS0T IBM WebSphere MQ Explorer (8.0.0.4) [http://www-01.ibm.com/support/docview.wss?uid=swg24021041]\nMQC71 IBM WebSphere MQ V7.1 Clients (7.1.0.7) [http://www-01.ibm.com/support/docview.wss?uid=swg24031412]\nMQC75 IBM WebSphere MQ V7.5 Clients (7.5.0.6) [http://www-01.ibm.com/support/docview.wss?uid=swg24032744]\nMQC8 IBM WebSphere MQ V8 Clients (8.0.0.5) [http://www-01.ibm.com/support/docview.wss?uid=swg24037500]\n\nYou should download these new install images from Fix Central or Passport Advantage where possible, however if older installers must be used, please refer to the workarounds and mitigations detailed below.", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q097", "section_id": 4, "heading": "WORKAROUNDS AND MITIGATIONS", "parent": null, "text": "The DLL-planting vulnerability only impacts IBM WebSphere MQ for Windows when an interactive installation is attempted via the graphical user interface via executable installer (.exe file extension).\n\nThe advanced installation method of IBM WebSphere MQ that uses msiexec offers both an interactive graphical interface, and a command line driven non-interactive installation that is not affected by this vulnerability. To install using msiexec, at the command line, enter the msiexec command in the following format:\n\nmsiexec parameters [USEINI=\" response-file \"] [TRANSFORMS=\" transform_file \"]\n\nThis installation method should be used in preference to running setup.exe. See the links below for detailed information on using this installation method.", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q097", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q097", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] IBM WebSphere MQ 7.1 Advanced Installation [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/wq10640_.htm]\nIBM WebSphere MQ V7.5 Advanced Installation [http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.ins.doc/q008690_.htm]\nIBM WebSphere MQ V8 Advanced Installation [http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ins.doc/q008690_.htm]\nIBM MQ Advanced for Developers [http://www-03.ibm.com/software/products/en/ibm-mq-advanced-for-developers]\nIBM MQ SupportPacs by Product [http://www-01.ibm.com/support/docview.wss?uid=swg27007197#1]\nRecommended Fixes for WebSphere MQ [http://www-01.ibm.com/support/docview.wss?uid=swg27006037]\nIBM WebSphere MQ Evaluation [https://www-01.ibm.com/marketing/iwm/iwm/web/pick.do?source=ESD-WSMQ-EVAL]\nIBM WebSphere MQ Advanced Message Security Evalution [https://www-01.ibm.com/marketing/iwm/iwm/web/preLogin.do?source=ESD-MQAMS-EVAL]\nIBM WebSphere MQ File Transfer Edition Evaluation [https://www-01.ibm.com/marketing/iwm/iwm/web/preLogin.do?source=ESD-MQFTE-EVAL] CHANGE HISTORY\n 2 June 2016: Original version published\n7 June 2016: Corrected spelling of SupportPac\n9 June 2016: Remove link to MQC7 SupportPac\nThe 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.", "logical_doc_id": 2, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q097", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21984649]", "logical_doc_id": 2, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q097", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere Application Server, IBM DB2, IBM SPSS Modeler, IBM Cognos Business Intelligence Server, IBM SPSS Collaboration and Deployment Services,IBM Integration Bus, IBM Analytic Server, IBM ILOG CPLEX Optimization Studio, IBM SPSS Statistics, IBM SPSS Modeler and IBM WebSphere MQ are shipped as components of IBM Predictive Maintenance and Quality. Information about a security vulnerability affecting : IBM WebSphere Application Server, IBM DB2, IBM SPSS Modeler, IBM Cognos Business Intelligence Server, IBM SPSS Collaboration and Deployment Services,IBM Integration Bus, IBM Analytic Server, IBM ILOG CPLEX Optimization Studio, IBM SPSS Statistics, IBM SPSS Modeler and IBM WebSphere MQ has been published in their respective security bulletins.", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q097", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Please consult the Security Bulletin: Vulnerability in IBM Java Runtime affect WebSphere Message Broker and IBM Integration Bus (CVE-2015-7575) [http://www-01.ibm.com/support/docview.wss?uid=swg21976779] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Vulnerability in IBM Java Runtime affect IBM ILOG CPLEX Optimization Studio and IBM ILOG CPLEX Enterprise Server (CVE-2015-7575) [http://www-01.ibm.com/support/docview.wss?uid=swg21975929] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Please consult the Security Bulletin: Vulnerability in IBM Java SDK affects IBM\u00ae DB2\u00ae LUW (CVE-2015-7575) [http://www-01.ibm.com/support/docview.wss?uid=swg21976363] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Vulnerability in IBM Java Runtime affect IBM SPSS Analytic Server (CVE-2015-7575) [http://www-01.ibm.com/support/docview.wss?uid=swg21977135] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Vulnerability in IBM Java Runtime affect IBM SPSS Statistics (CVE-2015-7575) [http://www-01.ibm.com/support/docview.wss?uid=swg21976835] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Vulnerability in IBM Java affect IBM SPSS Modeler (CVE-2015-7575) [http://www-01.ibm.com/support/docview.wss?uid=swg21977518] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Vulnerability in IBM Java SDK affect IBM SPSS Collaboration and Deployment Services (CVE-2015-7575) [Link%20:%20http:/www-01.ibm.com/support/docview.wss?uid=swg21976265] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: vulnerabilities in IBM\u00ae Java SDK affect WebSphere Application Server January 2016 CPU (CVE-2015-7575) [http://www-01.ibm.com/support/docview.wss?uid=swg21975424] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Vulnerability in IBM Java Runtime affects IBM WebSphere MQ (CVE-2015-7575) [http://www-01.ibm.com/support/docview.wss?uid=swg21977523] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects WebSphere Message Broker and IBM Integration Bus (CVE-2015-7575) [http://www-01.ibm.com/support/docview.wss?uid=swg21975233] for vulnerability details and information about fixes.", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q097", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Principal Product and Version(s) Affected Supporting Product and Version IBM Predictive Maintenance and Quality 2.0\n\nIBM Integration Bus V9.0.0.1\nIBM DB2 Enterprise Server Edition V10.1.0.3\nIBM SPSS Modeler V16.0.0.0\nIBM Websphere Application Server V8.5.5.0\nIBM WebSphere MQ V7.5.0.2 IBM Predictive Maintenance and Quality 2.5.0 IBM Integration Bus V9.0.0.2\nIBM ILOG CPLEX Optimization Studio V12.6.0.1\nIBM DB2 Enterprise Server Edition V10.5.0.4\nSPSS Analytic Server V1.0.1.0\nIBM SPSS Modeler V16.0.0.1\nIBM SPSS Collaboration and Deployment Services V6.0.0.0\nIBM Websphere Application Server V8.5.5.3\nIBM WebSphere MQ V7.5.0.4 IBM Predictive Maintenance and Quality 2.5.1 IBM Integration Bus V9.0.0.2\nIBM ILOG CPLEX Optimization Studio V12.6.0.1\nIBM DB2 Enterprise Server Edition V10.5.0.4\nSPSS Analytic Server V2.0\nIBM SPSS Modeler V17.0.0.0\nIBM SPSS Collaboration and Deployment Services V7.0.0.0\nIBM Websphere Application Server V8.5.5.3\nIBM WebSphere MQ V7.5.0.4 IBM Predictive Maintenance and Quality 2.5.2 IBM Integration Bus V9.0.0.2\nIBM ILOG CPLEX Optimization Studio V12.6.0.2\nIBM DB2 Enterprise Server Edition V10.5.0.5\nSPSS Analytic Server V2.0\nIBM SPSS Modeler V17.0.0.0\nIBM SPSS Collaboration and Deployment Services V7.0.0.1\nIBM Websphere Application Server V8.5.5.6\nIBM WebSphere MQ V7.5.0.4 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.", "logical_doc_id": 3, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q097", "section_id": 3, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 3, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q097", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] *The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.\n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 3, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q097", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "You can successfully connect to remote queue managers using\n your Windows MQ Explorer V7.1.0 configured with a C based\n security exit.\n However, after upgrading the MQ Explorer to V7.5, the following\n error occurs:\n\nAMQ4582: Queue Manager is not available for client\n connection.\n\nIf the MQ Explorer is started from the shell where the\n environment is set using the setmqenv command, the MQ Explorer\n connects successfully.\n However, if the the installation is configured as the primary,\n using the setmqinst command, the same error is incurred.", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q097", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Set the java.library.path variable to the location of the java\n libraries for the MQ Explorer. For Example:\n\n 1. From a command prompt start the MQ Explorer using the\n following command:\n\n MQExplorer.exe -vmargs \"-Djava.library.path=\"\n\n The \"path name\" is the install location of the MQ java/lib\n directory, for example if the MQ Explorer was installed to the\n \"default\" location run the following command:\n\n MQExplorer.exe -vmargs \"C:\\Program Files (x86)\\IBM\\WebSphere\n MQ\\java\\lib\"\n\n 2. As an alternative, the WebSphere MQ Explorer shortcut can\n also be updated to pass these arguments into the MQ Explorer\n program. In order to do this, implement the following steps:\n\n A. Right click on the WebSphere MQ Explorer shortcut in the\n Windows Start\n Menu, and select Properties from the pop up menu.\n\n B. When the WebSphere MQ Explorer properties window appears,\n click on\n the Shortcut tab.\n\n C. In the Target field, add the following arguments to the end:\nvmargs \"-Djava.library.path=C:\\Program Files\n (x86)\\IBM\\WebSphere MQ\\java\\lib\"\n\n D Click OK to apply the changes.\n\n NOTE:\n The installation and uninstallation mechanism does not affect\n the shortcut. This means that the additional arguments will not\n be removed from the shortcut when Fix Packs are installed or\n uninstalled.", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q097", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n This issue affects two categories of users:\n\n Category 1:\n\n Users of:\nThe WebSphere MQ V7.5 Explorer\nThe IBM MQ V8.0 Explorer\n\n on Linux who have installed a number of components that include:\nMQSeriesExplorer\nMQSeriesJava\n\n and do not include:\nMQSeriesServer\n\n and have configured their MQ Explorer to use a Client Channel\n Definition Table (CCDT) when accessing remote queue managers,\n where one or more entries in the CCDT uses a native exit written\n in C.\n\n Category 2:\n\n Users of:\nThe WebSphere MQ V7.5 Explorer\nThe IBM MQ V8.0 Explorer\n\n on Windows who have installed a number of components that\n include:\nMQ Explorer\nJava and .Net Messaging and Web Services (also known as\n JavaMsg)\n\n and do not include:\nServer\n\n and have configured their MQ Explorer to use a Client Channel\n Definition Table (CCDT) when accessing remote queue managers,\n where one or more entries in the CCDT uses a native exit written\n in C.\n\n Platforms affected:\n Windows, Linux on x86-64, Linux on x86\n\n PROBLEM DESCRIPTION:\n In order to load a native exit, the MQ Explorer requires access\n to the WebSphere MQ Java native library mqjexitstub02. This\n native library is part of the MQSeriesJava component on Linux,\n and the JavaMsg component on Windows. For 32-bit installations,\n the library is installed into the directory:\n\n \\java\\lib\n\n while on 64-bit installations, the library is installed into:\n\n \\java\\lib64\n\n When an MQ installation includes the following components:\n\n Linux\n\nMQSeriesExplorer\nMQSeriesJava\nMQSeriesServer\n\n Windows\n\nJavaMsg\nMQ Explorer\nServer\n\n then the MQ Explorer sets the Java system property\n java.library.path to be:\n\n \\java\\lib;\\bin\n\n for 32-bit installation, and:\n\n \\java\\lib64;\\bin64\n\n for 64-bit installations. This allows the MQ Explorer to load\n the Java native library mqjexitstub02, which means that it can\n successfully use native exits.\n\n However, if the MQ Explorer was installed as part of an MQ\n installation which included the JavaMsg component (on Windows)\n or the MQSeriesJava component (on Linux) and did not include the\n Server component, then the user interface did not modify the\n java.library.path. As a result, whenever the user interface was\n required to load and use a native exit, it was unable to find\n the mqjexitstub02 native library and so reported the following\n error:\n\n AMQ4582: Queue Manager is not available for client\n connection.", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q097", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The MQ Explorer has been modified so that if it has been\n installed as part of an installation which includes the JavaMsg\n component (on Windows) or the MQSeriesJava component (on Linux),\n and does not include the Server component, it will modify the\n Java system property java.library.path and append the following\n entries to the end:\n\n For 32-bit installations:\n\n \\java\\lib\n \\bin\n\n For 64-bit installations:\n\n \\java\\lib64\n \\bin64\n\n This ensures that the MQ Explorer can access the Java native\n library mqjexitstub02, which is required when using native\n exits.\n\n The fix is targeted for delivery in the following PTFs:\n\n Version Maintenance Level\n v7.5 7.5.0.7\n v8.0 8.0.0.5\n\n The latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\n If the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q097", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT13226\nREPORTED COMPONENT NAME\n WMQ BASE MULTIP\nREPORTED COMPONENT ID\n 5724H7241\nREPORTED RELEASE\n 750\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-01-18\nCLOSED DATE\n 2016-02-26\nLAST MODIFIED DATE\n 2016-02-26\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q097", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ BASE MULTIP\nFIXED COMPONENT ID\n 5724H7241", "logical_doc_id": 4, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q097", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R750 PSY\n UP", "logical_doc_id": 4, "chunk_id": 32 }, { "doc_id": "techqa_DEV_Q146", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "Update 1 of IBM\u00ae WebSphere\u00ae Application Server Version 7 Fix Pack 7, also known as Version 7.0.0.7, for an installed test environment extension.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q146", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "This download includes the following updates to the WebSphere Application Server v7.0 Test Environment extension included with Rational Software Delivery Platform products:\nIBM WebSphere Application Server Version 7 Fix Pack 7, also known as Version 7.0.0.7. For details about this update, such as known issues, view the WebSphere Application Server 7.0.0.7 readme at http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27017010 [http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27017010].\nXML Feature Pack Fix Pack V1.0.0.1 for WebSphere Application Server V7. For details about the fix pack, see http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27017703 [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27017703].\nSCA Feature Pack Fix Pack V1.0.1.1 for WebSphere Application Server V7. For details about the fix pack, see http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27017704 [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27017704].\n\nPREREQUISITES\nYou must have the WebSphere Application Server v7.0 Test Environment extension installed with one of the following products:\n\nIBM Rational Application Developer for WebSphere Software, v7.5.x IBM Rational Software Architect for WebSphere Software, v7.5.x\nYou need up to 3.35 GB of disk space to install the fix pack. To download and extract the compressed installation files, you need an additional 3.25 GB of disk space. INSTALLATION INSTRUCTIONS\n\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 Rational Application Developer for WebSphere Software [http://publib.boulder.ibm.com/infocenter/radhelp/v7r5/topic/com.ibm.rad.install.doc/topics/t_update.html] or Rational Software Architect for WebSphere Software [http://publib.boulder.ibm.com/infocenter/rsawshlp/v7r5m0/topic/com.ibm.xtools.installation.rsaws.doc/topics/t_update.html].\n\nTo download and install the update from the compressed files, complete the following steps:\n\n1.\n 2. Download the update files listed in the download table below.\n 3.\n 4. Extract the compressed files in an appropriate directory. For example, choose to extract to C:\\temp\\update\n 5.\n 6.\n 7. Add the update's repository location in IBM Installation Manager:\n 1.\n 2. Start IBM Installation Manager.\n 3.\n 4. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.\n 5.\n 6. On the Repositories page, click Add Repository.\n 7.\n 8. 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 9.\n 10. Click OK to close the Preference page.\n 11.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q146", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "8. Install the update as described in the the topic \"Updating Installed Product Packages\" in the information center for Rational Application Developer for WebSphere Software [http://publib.boulder.ibm.com/infocenter/radhelp/v7r5/topic/com.ibm.rad.install.doc/topics/t_update.html] or Rational Software Architect for WebSphere Software [http://publib.boulder.ibm.com/infocenter/rsawshlp/v7r5m0/topic/com.ibm.xtools.installation.rsaws.doc/topics/t_update.html].\n 9.\n\nDOWNLOAD PACKAGE\nYou can download the fix pack using either Download Director or FTP from the table below. If you are unable to use either of these methods, you can download the fix pack using HTTP from the following URL:\nhttp://public.dhe.ibm.com/software/rationalsdp/v75/was70/7007u1/zips/ [http://public.dhe.ibm.com/software/rationalsdp/v75/was70/7007u1/zips/]\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is DD? [http://www6.software.ibm.com/dldirector/doc/DDfaq_en.html] was7007u1.update.disk1.zip 1/18/2010 English 217194871 FTP [ftp://public.dhe.ibm.com/software/rationalsdp/v75/was70/7007u1/zips/was7007u1.update.disk1.zip] DD was7007u1.update.disk2.zip 1/18/2010 English 626688030 FTP [ftp://public.dhe.ibm.com/software/rationalsdp/v75/was70/7007u1/zips/was7007u1.update.disk2.zip] DD was7007u1.update.disk3.zip 1/18/2010 English 93002573 FTP [ftp://public.dhe.ibm.com/software/rationalsdp/v75/was70/7007u1/zips/was7007u1.update.disk3.zip] DD was7007u1.update.disk4.zip 1/18/2010 English 626884389 FTP [ftp://public.dhe.ibm.com/software/rationalsdp/v75/was70/7007u1/zips/was7007u1.update.disk4.zip] DD was7007u1.update.disk5.zip 1/18/2010 English 673705696 FTP [ftp://public.dhe.ibm.com/software/rationalsdp/v75/was70/7007u1/zips/was7007u1.update.disk5.zip] DD\nCross reference information Segment Product Component Platform Version Edition Software Development Rational Software Architect for WebSphere Software Integrated Test Environment Linux, Windows 7.5, 7.5.1, 7.5.2, 7.5.3, 7.5.4, 7.5.5 Software Development Rational Business Developer General Information Linux, Windows 7.5, 7.5.1, 7.5.1.1, 7.5.1.2, 7.5.1.3, 7.5.1.4, 7.5.1.5", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q146", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Where can IBM Business Process Manager V7.5.x, WebSphere Process Server v7, WebSphere Enterprise Service Bus V7 and V7.5.x, IBM Business Monitor V7.5.x, and WebSphere Business Monitor V7 customers download the Websphere Application Server version 7.0 fix pack repository images to upgrade their WebSphere Application Server installations using IBM Installation Manager?", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q146", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "WebSphere Process Server Version 7.0, IBM Business Process Manager Version 7.5.x, WebSphere Enterprise Service Bus Version 7.0 and 7.5.x, IBM Business Monitor Version 7.5.x, and WebSphere Business Monitor Version 7.0 products use IBM Installation Manager to install their binaries. To upgrade the WebSphere Application Server to a later version you will need the WebSphere Application Server fix pack as an IBM Installation Manager repository.\n\nIf you have internet access you will be able to upgrade your WebSphere Application Server using the IBM Installation Manager live repository. If you do not have internet access then the following FTP site has the collection of all the WebSphere Application Server Version 7.0 fix pack repositories which can be used with IBM Installation Manager.\n\nftp://public.dhe.ibm.com/software/websphere/bpm/repositories/downloads/was/ [ftp://public.dhe.ibm.com/software/websphere/bpm/repositories/downloads/was/]\n\nEach subdirectory contains downloadable .zip files of the IBM Installation Manager repositories for the WebSphere Application Server specific fix pack.\n\nYou can download the PART1 and PART2 fix pack repository which is for all supported systems and architectures, or you can download the sliced repositories for specific operating systems and architectures that you need.\n\nExample :\n\nDirectory name \"70033 [ftp://public.dhe.ibm.com/software/websphere/bpm/repositories/downloads/was/70033/]\" contain the following images .\nFix pack image for all operating systems and platforms:\n\nwas.7.0.0.33.fp.all_Part1of2.zip ---- 2,073,768,159 bytes\n was.7.0.0.33.fp.all_Part2of2.zip ---- 2,078,505,024 bytes\n\nExtract both parts under the same directory, which includes all WebSphere Application Server offerings for all supported operating systems and architectures.\nFix pack image for a specific operating system:\n\nwas.nd.7.0.0.33.fp.win.zip ----------- 1,083,512,033 bytes - contains both 32bit and 64bit for Windows\n was.nd.7.0.0.33.fp.linux.x86.zip ---- 1,050,139,800 bytes - contains both 32bit and 64bit for Linux x86 and x86-64\n\nSliced for specific operating system is much smaller in size compared to the image for all operating system. It will be faster to download and require less hard drive space to extract and upgrade the product.\n\nReview the product documentation link in the reference document for additional instructions for updating the IBM Business Process Manager. RELATED INFORMATION\n Infocenter: Updating IBM Business Process Manager [http://pic.dhe.ibm.com/infocenter/dmndhelp/v7r5m1/index.jsp?topic=/com.ibm.wbpm.imuc.doc/topics/tins_updating.html]\nUpdate Instructions for V7.5.1 Refresh Pack [http://www.ibm.com/support/docview.wss?uid=swg27023410]", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q146", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Upgrade AIX, Linux, Linux zSeries, Solaris, Windows 7.5.1, 7.5 Business Integration IBM Business Process Manager Express Upgrade Linux, Linux zSeries, Windows 7.5.1, 7.5 Business Integration WebSphere Process Server Upgrade AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows 7.0 Business Integration IBM Business Monitor Upgrade AIX, Linux, Linux zSeries, Solaris, Windows 7.5.1, 7.5 Business Integration WebSphere Enterprise Service Bus Not Applicable AIX, HP-UX, Linux, Linux pSeries, Linux zSeries, Solaris, Windows 7.5.1, 7.5, 7.0 Business Integration WebSphere Business Monitor Upgrade AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows 7.0\nPRODUCT ALIAS/SYNONYM\n WAS\nWPS\nBPM\nWESB\n\nLaunchpad Hang Business Progress Management DOWNLOADABLE FILES", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q146", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "The Launchpad hangs at 41% when you install an IBM Business Process Manager (BPM) product using the typical installation method in some Microsoft Windows environments.", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q146", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "The attached compressed file (.zip) contains four files. These files are replacement files for the Launchpad, which will fix this problem.\n\nFor more information on this issue, see Launchpad hangs at 41% during a typical installation for the IBM Business Process Server (BPM) products [http://www.ibm.com/support/docview.wss?uid=swg21588515].\n\nINSTALLATION INSTRUCTIONS\nStep1: Backup the following four files in your launchpad image.\n\n/launchpad/content/scripts/runIM.bat\n/launchpad/content/global.properties\n/launchpad/content/installation/utils/InstallUtils.js\n/launchpad/content/installation/widgets/InstallingPane.js\n\nWhere extract_directory is the directory where the product image is unzipped\n\nStep2: Place the patch file (zip file) at folder\nStep3: unzip zip file (Right click -> extract_directory All\nStep4: Accept the default path listed by unzip utility ( Make sure you see \"launchpad\" folder at the end of default path)\nStep4: extract_directory ( Accept YES TO ALL to the the Confirm File Replace Dialog)\nStep5(optional): Make sure the following file are replaced\n\n/launchpad/content/scripts/runIM.bat\n/launchpad/content/global.properties\n/launchpad/content/installation/utils/InstallUtils.js\n/launchpad/content/installation/widgets/InstallingPane.js\n\nlaunchpad.zip [/support/docview.wss?uid=swg24032300&aid=2]launchpad.zip [/support/docview.wss?uid=swg24032300&aid=1]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Express Installation / Configuration Windows 7.5.1 Business Integration IBM Business Process Manager Advanced Installation / Configuration Windows 7.5.1\nPRODUCT ALIAS/SYNONYM\n BPM\n\n[/support/docview.wss?uid=swg24032300&aid=3]Problems (APARS) fixed [/support/docview.wss?uid=swg24032300&aid=4]Problems (APARS) fixed\nJR42324\n\nRAD; RADWS; RSAS; RSAWS; RBD; WAS; 61025; 6.1.0.25 DOWNLOADABLE FILES", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q146", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM\u00ae WebSphere\u00ae Application Server Version 6.1, Web Services Feature Pack and EJB 3.0 Feature Pack Fix Pack 25 (v6.1.0.25) for an installed test environment extension.", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q146", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "This update applies IBM WebSphere Application Server Version 6.1, Web Services Feature Pack and EJB 3.0 Feature Pack Fix Pack 25, also known as Version 6.1.0.25, to the WebSphere Application Server v6.1 Test Environment extension included with Rational Software Delivery Platform products.\n\nFor details about this update, such as known issues, view the WebSphere Application Server 6.1.0.25 readme at http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27015918 [http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27015918].\n\nPREREQUISITES\nPrerequisites *\nYou must have the WebSphere Application Server v6.1 Test Environment extension installed with one of the following products:\nIBM Rational Application Developer for WebSphere Software, v7.5.x\nIBM Rational Software Architect for WebSphere Software, v7.5.x\nIBM Rational Business Developer, v7.5.1.x\n\nYou need up to 2.31 GB of disk space to install the fix pack. To download and extract the compressed installation files, you need an additional 3.29 GB of disk space. INSTALLATION INSTRUCTIONS\n\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 Rational Application Developer for WebSphere Software [http://publib.boulder.ibm.com/infocenter/radhelp/v7r5/topic/com.ibm.rad.install.doc/topics/t_update.html] or Rational Software Architect for WebSphere Software [http://publib.boulder.ibm.com/infocenter/rsawshlp/v7r5m0/topic/com.ibm.xtools.installation.rsaws.doc/topics/t_update.html].\n\nTo download and install the update from the compressed files, complete the following steps:\n\n1.\n 2. Download the update files listed in the download table below.\n 3.\n 4. Extract the compressed files in an appropriate directory. For example, choose to extract to C:\\temp\\update\n 5.\n 6.\n 7. Add the update's repository location in IBM Installation Manager:\n 1.\n 2. Start IBM Installation Manager.\n 3.\n 4. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.\n 5.\n 6. On the Repositories page, click Add Repository.\n 7.\n 8. 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 9.\n 10. Click OK to close the Preference page.\n 11.", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q146", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "8. Install the update as described in the the topic \"Updating Installed Product Packages\" in the information center for Rational Application Developer for WebSphere Software [http://publib.boulder.ibm.com/infocenter/radhelp/v7r5/topic/com.ibm.rad.install.doc/topics/t_update.html] or Rational Software Architect for WebSphere Software [http://publib.boulder.ibm.com/infocenter/rsawshlp/v7r5m0/topic/com.ibm.xtools.installation.rsaws.doc/topics/t_update.html].\n 9.\n\nDOWNLOAD PACKAGE\nYou can download the fix pack using either Download Director or FTP from the table below. If you are unable to use either of these methods, you can download the fix pack using HTTP from the following URL:\nhttp://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v75/was61/61025/zips/ [http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v75/was61/61025/zips/]\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is DD? [http://www6.software.ibm.com/dldirector/doc/DDfaq_en.html] was61025.update.disk1.zip 6/30/2009 English 238747647 FTP [ftp://public.dhe.ibm.com/software/rationalsdp/v75/was61/61025/zips/was61025.update.disk1.zip] DD was61025.update.disk2.zip 6/30/2009 English 558340693 FTP [ftp://public.dhe.ibm.com/software/rationalsdp/v75/was61/61025/zips/was61025.update.disk2.zip] DD was61025.update.disk3.zip 6/30/2009 English 582829953 FTP [ftp://public.dhe.ibm.com/software/rationalsdp/v75/was61/61025/zips/was61025.update.disk3.zip] DD\nCross reference information Segment Product Component Platform Version Edition Software Development Rational Software Architect for WebSphere Software Integrated Test Environment Linux, Windows 7.5, 7.5.1, 7.5.2, 7.5.3 Software Development Rational Business Developer General Information Linux, Windows 7.5.1, 7.5.1.1, 7.5.1.2, 7.5.1.3", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q146", "section_id": 2, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Rational Developer for System z 9.1.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24039079]\nRational Developer for System z Interim Fix 1 for 9.1.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24039177]\nRational Developer for System z Interim Fix 2 for 9.1.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24039625]\nRational Developer for System z Fix Pack 1 (9.1.1.1) for 9.1.1. [http://www-01.ibm.com/support/docview.wss?uid=swg24039635]\nRational Developer for System z Interim Fix 1 for 9.1.1.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24040387]\nRational Developer for System z Interim Fix 2 for 9.1.1.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24040483]\nRational Developer for System z Fix Pack 1 (9.1.1.2) for 9.1.1. [http://www-01.ibm.com/support/docview.wss?uid=swg24040962]\nRational Developer for System z Interim Fix 1 for 9.1.1.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24041307]\nRational Developer for System z Interim Fix 2 for 9.1.1.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24041657]\nRational Developer for System z Fix Pack 1 (9.1.1.3) for 9.1.1. [http://www-01.ibm.com/support/docview.wss?uid=swg24041789]\nRational Developer for System z Interim Fix 1 for 9.1.1.3 [http://www-01.ibm.com/support/docview.wss?uid=swg24042181]\nRational Developer for System z Fix Pack 1 (9.1.1.4) for 9.1.1. [http://www-01.ibm.com/support/docview.wss?uid=swg24042820]\nRational Developer for System z Fix Pack 1 (9.1.1.5) for 9.1.1. [http://www-01.ibm.com/support/docview.wss?uid=swg24043244]\nRational Developer for System z Fix Pack 1 (9.1.1.6) for 9.1.1. [http://www-01.ibm.com/support/docview.wss?uid=swg24044103]\nRational Developer for System z Fix Pack 1 (9.1.1.7) for 9.1.1. [http://www-01.ibm.com/support/docview.wss?uid=swg24044796]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q146", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Errors prevent installation of Rational Developer for System z\n (RDz) 9.1 and Data Studio 4.1.1 on Windows in the same package\n group. During the install using the IBM Installation Manager,\n the following error messages would occur and installing RDZ 9.1\n in the same package group as Data Studio 4.1.1 is not allowed:\n\n CRIMA1161E: Failed to find required installation files.\n CRIMC1020E: feature\n com.ibm.datatools.base.linux_2.1.200.v20131217_2357 not found\n CRIMC1020E: feature\n com.ibm.datatools.base.linux64_1.0.0.v20131217_2357 not found", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q146", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "1)Install Data Studio version 4.1.0.1 instead of 4.1.1 with RDz\n 9.1.\n 2) Download Data Studio 4.1.1 for Linux\n (http://www-01.ibm.com/support/docview.wss?uid=swg24037681),\n unzip and add the following to the IBM Installation Manager\n repository before attempting to install Data Studio 4.1.1 and\n RDz 9.1 in the same install package group:\n \\disk1\\diskTag.inf", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q146", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Windows and Linux only features were always being installed\n instead of installing based on the operating system.", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q146", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Windows and Linux specific features were not being installed\n based on the operating system.\n\nThe problem listed in this APAR has been resolved with\n IBM Rational Developer for System z V9.1.1.0 Refresh Pack which\n is available from the Recommended Fixes support download page:\n http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335 [http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335]\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q146", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI26466\nREPORTED COMPONENT NAME\n RATL DEV FOR SY\nREPORTED COMPONENT ID\n 5724T0700\nREPORTED RELEASE\n 910\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-09-25\nCLOSED DATE\n 2014-12-11\nLAST MODIFIED DATE\n 2014-12-11\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q146", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n RATL DEV FOR SY\nFIXED COMPONENT ID\n 5724T0700", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q146", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R911 PSY\n UP", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q206", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q206", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "ERPRISE PL/I WITH DEBUG TOOL, NON-DESCRIPTIVE ERROR MSG FOR\n \"LIST BASED_VARIABLE\" WITH BAD BASING PTR.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q206", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Users running Enterprise PL/I programs *\nunder Debug Tool, who receive message *\n\"EQA1750E An error occurred during *\nexpression evaluation\" when trying to list *\nthe value of a variable that is based on *\nan invalid pointer. *\n*\n\nPROBLEM DESCRIPTION: When running Enterprise PL/I programs *\nwith Debug Tool, a LIST command that *\nreferences a based variable with a bad *\nbasing pointer receives message *\nEQA11750E. This message is not helpful *\nin determining why the expression *\nevaluation failed. *\n*\n\nRECOMMENDATION: *\n\nThe same message is issued for different types of errors that\n occur during expression evaluation. The message is not helpful\n to the user in determining why expression evaluation failed.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q206", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The PL/I runtime library routines can provide a return code\n to Debug Tool that will indicate that an invalid basing pointer\n has been detected. This will allow Debug Tool to issue a more\n descriptive error message.\n\nIf a basing pointer is found to be invalid, either because it\n contains x'00000000' or is pointing to inaccessible storage, a\n new return code will be returned to Debug Tool from Enterprise\n PL/I.\n\nDebug Tool will issue message \"EQA2296E Unable to display the\n variable based on an invalid pointer.\" when this new return\n code is received.\n\nSupport for this new message requires applying co-requisite\n Debug Tool fixes for the appropriate Debug Tool version.\n\nCO-REQUISITE APARS\n\nDebug Tool 4.1: PQ99203 and PQ95624\n Debug Tool 5.1: PK00675 and PQ94401 [http://www-01.ibm.com/support/docview.wss?uid=swg1PQ94401]\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q206", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PQ96959\nREPORTED COMPONENT NAME\n ENT PL/I FOR Z/\nREPORTED COMPONENT ID\n 5655H3100\nREPORTED RELEASE\n 707\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2004-11-09\nCLOSED DATE\n 2005-03-14\nLAST MODIFIED DATE\n 2005-04-01\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n UK01479 UK01480 UK01481\n\nMODULES/MACROS\nIBMPXPL1 IBMQEXP IBMRRTV", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q206", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n LE VA PL/I\nFIXED COMPONENT ID\n 568819806", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q206", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R707 PSY UK01479 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK01479]\n UP05/03/17 P F503\nR708 PSY UK01480 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK01480]\n UP05/03/17 P F503\nR709 PSY UK01481 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK01481]\n UP05/03/17 P F503\n\nFIX IS AVAILABLE\nSELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL. YOU WILL BE REQUIRED TO SIGN IN. DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q206", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The IP forwarding option is on. I edited the hosts file and tried to restart the LIM. This is the error message I got :\n\n[lsfadmin@acsrocks1 conf]$ lsadmin limrestart all\n\nChecking configuration files ...\nNo errors found.\nls_gethostinfo: Failed in sending/receiving a message: Permission denied\nOperation aborted\n\nWith the original hosts file, I can restart LIM. But after I modify it, I get the error message above.\n\nProblem identified: the user put a wrong ip address for the external interface on the master node, so that the packet are routed to external network.\n\nCross reference information Segment Product Component Platform Version Edition IBM Spectrum Computing IBM Spectrum LSF", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q206", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Installing C:E z/OS 1.3 on a test LPAR that probably never had C:E on it before. Customized the LIBDEF clist (just for our dataset names) and when I EXEC it, I get a \"IKJ56500I COMMAND MZMCP001 NOT FOUND\" message. All the ISPEXEC LIBDEF commands finished with LASTCC=0 (I added a debug statement after each one). I also created a MZICMDS table entry in ISPF option 3.9.\n\nError Message IKJ56500I COMMAND MZMCP001 NOT FOUND", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q206", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "In C:E 1.0.00, the LIBDEF example member contained the following, using PGM:\n\nISPEXEC SELECT PGM(MZMCP001) NEWAPPL(MZI) PASSLIB\n\nIn C:E 1.1.00 and above, the LIBDEF example member was updated and PGM was delibrately changed to CMD:\n\nISPEXEC SELECT CMD(MZMCP001) NEWAPPL(MZI) PASSLIB\n\nWhy the update: We found that CMD was needed for the dialog to function properly. CMD allows us to do LINK/LOAD/XCTL and find modules in the LIBDEF concatenation. With PGM, all programs must be called using the ISPF SELECT service.\n\nThis customer was using ACF2 and C:E 1.3.00. They noticed in their C:E 1.2.00 LIBDEF, they defined PGM(MZMCP001) and in their C:E 1.3.00 libdef, they'd defined CMD(MZMCP001). Per ACF2 support, this is why the ACF2 Command-Limiting table needed to be updated for C:E 1.3.00, you must add Program MZMCP001 to give access to these TSO users, but this was unnecessry for C:E 1.2.00. FYI: The TSO CMDS can be defined per TSO user id or it can be defined globally in TSO GSO CMDLIST command. If NULL is defined in the list, that means there is no checking/verifying.\n\nHISTORICAL NUMBER\n NFX2072\n\nPRODUCT ALIAS/SYNONYM\n\nSeverity\n\nNormal\n\nType\n\nNormalFix", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q206", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What causes the error: \"Duplicate menu path: MapPageOVMenu\" when using nco_confpack to export or import object server data?", "logical_doc_id": 4, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q206", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Due to having 2 menus with the same name in the tools menu.", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q206", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "The solution is to rename or delete away (if no not needed) one of the duplicate menus.\n\nThe object server is able to allow for duplicate menu item names because it tracks them by a numeric identifier in the database tables. For nco_confpack to be able to export and then import , it can't rely upon those numeric identifiers, because they will be different from one host to another, so we have to use the name.\n\nThe menus and menu items are tracked by constructing a menu tree, starting from the root. Then the complete path is then used as the key. This allows for the menu and menu items to be unique, based upon a name. This is where the duplicate menu path comes into the picture.\n\nSolution : Make sure the names are unique. For example, append them with a sequential number (ie: by appending a 1, 2, 3....).", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q206", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The command fails and the following error is received: Tool in menu but not found, menu: AlertsMenu, tool: CLEAR_LWY.", "logical_doc_id": 5, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q206", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The menu AlertsMenu has a tool in it called CLEAR_LWY, however the tool no longer exists.", "logical_doc_id": 5, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q206", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Recreate the tool and associate it with the menu and try to run the command again.", "logical_doc_id": 5, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q292", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "There may be a number of different errors depending on the client application. For example:\n\nThe Repository is not available.\n\nfailed to establish connection using iiop://:port/FileNet/Engine\n\nCORBA.NO_RESPONSE\n\nWebSphere may report ORB thread starvation or multiple ORB hung threads, for example:-\n\nWSVR0606W: Thread \"ORB.thread.pool : 90\" (000000e0) was previously reported to be hung but has completed. It was active for approximately 1626228 milliseconds. There is/are 4 thread(s) in total in the server that still may be hung.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q292", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Excessive load balancer health monitor calls against the default WebSphere EJB port may use all available ORB threads and may leave TCP connections in the CLOSE_WAIT state, resulting in connection failures from other clients.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q292", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "High availability IBM FileNet P8 Content Engine load balanced farm.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q292", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Check the WebSphere systemout.log for messages relating to hung threads or thread starvation.\nUse netstat to collect information about port usage and remote connections.\nCollect the load balancer health monitor configurations for all target P8 CE ports.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q292", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Review the following points in order to prevent this problem from occurring:\nAvoid using a health monitor against the EJB/bootstrap port.\nThe preferred load balancer health monitor for P8 Content Engine is to use the CE start-up context page, also known as the CE ping page. This should be configured against the HTTP port:\n http://<>:<>/FileNet/Engine\nA typical load balancer HTTP health monitor configuration will only require the context path string:\n /FileNet/Engine\nThe monitor interval should be set to the largest practical time interval, typically greater than 5 seconds. and a time-out value of not less than 15 seconds.\nThe Content Engine application server instance will need to be re-started to close the accumulated open connections.\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q292", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When a storage area becomes offline or unavailable, ingested\n documents are created unfiled and with minor version number.\n\nThis is occurring because the Content Engine (CE) Client\n (WorkplaceXT (WPXT), etc) is not able\n to delete or remove the document after an unsuccessful call to\n the document.setContent(...) method due to no storage area being\n available.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q292", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nUsing ICC or WorkplaceXT for document ingestion with *\n5.0.0.2-P8CE-FP002 or prior. *\n\nPROBLEM DESCRIPTION: *\nWhen using ICC or WorkplaceXT for document ingestion, if the *\ntarget storage area happens to be unavailable (due to *\nhardware, network issues, etc) the applications would create *\nminor versions of documents without content, not the *\nexpected major versions with content. These minor versions *\ncould not be deleted until the storage area was back online, *\nmaking it impossible for the ingestion applications to *\ncorrectly clean up their incomplete work. *\n\nRECOMMENDATION: *\nUpgrade to Content Engine 5.0.0.3-P8CE-FP003 or later, and *\nupgrade the ingestion application to a version that *\nimplements cleanup of incomplete documents. *", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q292", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Code fix in Content Engine 5.0.0.3-P8CE-FP003 or later will\n allow the ingestion applications to clean up incomplete\n ingestion in this case.\n Note that the ingestion applications me require modification to\n actually perform the cleanup.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q292", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PJ40525\nREPORTED COMPONENT NAME\n CONTENT ENGINE\nREPORTED COMPONENT ID\n 5724R8101\nREPORTED RELEASE\n 500\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2012-08-21\nCLOSED DATE\n 2015-05-21\nLAST MODIFIED DATE\n 2015-05-21\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n PJ40497 [http://www-01.ibm.com/support/docview.wss?uid=swg1PJ40497]\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q292", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n CONTENT ENGINE\nFIXED COMPONENT ID\n 5724R8101", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q292", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R500 PSY\n UP", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q292", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Red icons are displayed next to the Fixed Content Devices and Storage Areas even though users can add and access content.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q292", "section_id": 1, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "The p8_server_error log may contain the following E_ACCESS_DENIED error:\n\nyyyy-mm-ddThh:mm:ss nnnnnn ENG FNRCE0241E - ERROR method name: postLoadSecurity principal name: Global Transaction: false User Transaction: false Exception Info: The requester has insufficient access rights to perform the requested operation.\ncom.filenet.api.exception.EngineRuntimeException: E_ACCESS_DENIED: The requester has insufficient access rights to perform the requested operation.\nat com.filenet.engine.retrieve.IndependentClassRetriever.postLoadSecurity(IndependentClassRetriever.java:1390)\nat com.filenet.engine.retrieve.RetrieverClassBase.loadNonScalarProperties(RetrieverClassBase.java:633)\nat com.filenet.engine.retrieve.IndependentClassRetriever.loadNonScalarProperties(IndependentClassRetriever.java:1298)\nat com.filenet.engine.retrieve.IndependentClassRetriever.loadObject(IndependentClassRetriever.java:1119)\n...", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q292", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "1. Verify the Content Engine Bootstrap User has Full Control on the Object Store and all associated Storage Areas.\n\n2. Inspect Storage Area security by right-clicking on the Object Store\n\n3. Choose Properties\n\n4. Select the All Properties radio button and view the Storage Area property name\n\n5. Click on the drop down list to select the Storage Area.\n\n6. The Storage Area properties screen will appear.\n\n7. Verify the Security tab allows the Content Engine Bootstrap User has Full Control.\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q292", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When using Administrative Console for Content Engine (ACCE) to\n create a new Object Store, ACCE asks details on the Storage Area\n that it should create for storing the documents. When a Customer\n chooses to have a Fixed Content Area created, that uses a Tivoli\n Storage Manager Fixed Content Device, this choice is accepted by\n ACCE. When the Create Object Store wizard completes, it has\n created a Database Storage Area instead.", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q292", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Create a Fixed Content Area separately, and substitute the Fixed\n Content Area in the Storage Policy that ACCE has created for the\n Database Storage Area. Then rename the Database Storage Policy\n to reflect this change.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q292", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nAdministrative Console for Content Engine (ACCE) on *\n5.2.1.0-P8CPE and prior versions. *\n\nPROBLEM DESCRIPTION: *\nWhen using Administrative Console for Content Engine (ACCE) *\nto *\ncreate a new Object Store, ACCE asks details on the Storage *\nArea *\nthat it should create for storing the documents. When a *\nCustomer *\nchooses to have a Fixed Content Area created, that uses a *\nTivoli *\nStorage Manager Fixed Content Device, this choice is *\naccepted by *\nACCE. When the Create Object Store wizard completes, it has *\ncreated a Database Storage Area instead. *\n\nRECOMMENDATION: *\nUpgrade to 5.2.1.2-P8CPE-FP002 and higher. *", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q292", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fixed in 5.2.1.2-P8CPE-FP002 and higher. Now Object Store\n creation wizard creates Tivoli Storage Manager Fixed store and\n policy.\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q292", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PJ42919\nREPORTED COMPONENT NAME\n CONTENT ENGINE\nREPORTED COMPONENT ID\n 5724R8101\nREPORTED RELEASE\n 521\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2015-01-27\nCLOSED DATE\n 2015-06-11\nLAST MODIFIED DATE\n 2015-06-11\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q292", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n CONTENT ENGINE\nFIXED COMPONENT ID\n 5724R8101", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q292", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R521 PSY\n UP", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q292", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "This is necessary if for example the storage device currently hosting the index-area is running out of space.", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q292", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Moving an IBM Content Search Services (CSS) index-area. This procedure assumes basic knowledge of IBM Content Search Services and the use of either FileNet Enterprise Manager (FEM) or Administration Console Content Engine (ACCE). This procedure was written with ACCE in mind.\n\n 1. Execute the following object store database query and save the results prior to starting this procedure. You can re-run this when done with this procedure to ensure the object store database was correctly updated;\n\n select create_date,modify_date,display_name,description,root_directory_path from IndexArea\n\n 2. Stop all CSS services configured as Indexing or Index and Search.\n\n 3. Backup the text collection(s) in the current index-area location.\n\n 4. Create a new index-area directory. Note that all CSS services requires access to this new location.\n\n 5. Move the text collection(s) located in the current index-area, to the new index-area location as defined in step 4.\n\n 6. Using FEM or ACCE update the object store index-area Root Directory value to reflect the new index-area location as defined in step 4. Press Save then refresh the object store.\n\n 7. Start all CSS services you stopped in step 2.\n\n 8. Re-run the database query defined in step 1 and ensure the root_directory_path was updated to the newly defined index-area location.\n\n 9. Test by adding 1 or a few text documents which will after a few minutes show an increased count for the currently open text collection.\n\n Note If using Content Engine and IBM Content Search Services (CSS) 5.1 and each text collection directory contains a 'collection.xml' file, access the following Product Documentation [http://www.ibm.com/support/knowledgecenter/SSNW2F_5.1.0/com.ibm.p8toc.doc/ic-homepage.html] link.", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q098", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM\u00ae Runtime Environment Java\u2122 Version 7.0.10.10 used by IBM MQ Internet Pass Thru. These issues were disclosed as part of the IBM Java SDK updates in January 2018.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q098", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "If you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities please refer to the link for \u201cIBM Java SDK Security Bulletin\" located in the \u201cReferences\u201d section for more information.\n\nCVEID: CVE-2018-2579 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2579]\nDESCRIPTION: An unspecified vulnerability related to the Java SE Libraries component could allow an unauthenticated attacker to obtain sensitive information resulting in a low confidentiality impact using unknown attack vectors.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/137833 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137833] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\nCVEID: CVE-2018-2602 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2602]\nDESCRIPTION: An unspecified vulnerability related to the Java SE I18n component could allow an unauthenticated attacker to cause low confidentiality impact, low integrity impact, and low availability impact.\nCVSS Base Score: 4.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/137854 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137854] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L)\n\nCVEID: CVE-2018-2603 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2603]\nDESCRIPTION: An unspecified vulnerability related to the Java SE Libraries component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/137855 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137855] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)\n\nCVEID: CVE-2018-2633 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2633]\nDESCRIPTION: An unspecified vulnerability related to the Java SE JNDI component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/137885 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137885] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q098", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM SDK, Java Technology Edition, Version 7 Service Refresh 10 Fix Pack 10 and earlier releases provided by WebSphere MQIPT 2.1 on all platforms.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q098", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "A JRE update for MQIPT 2.1.0.4 contains fixes for these vulnerabilities and can be downloaded from the MS81: WebSphere MQ Internet Pass-Thru [http://www.ibm.com/support/docview.wss?uid=swg24006386] SupportPac page, via the Download package link.\n\nUsers can follow the instructions contained in Instructions for manually updating the JRE within an MQIPT V2.1 Installation [http://www.ibm.com/support/docview.wss?uid=swg21678663].\n\nPlease note: Users of MQIPT v2.1 on the HP-UX platform are advised that patches for these issues have not been released by the manufacturer for this JRE level (7.0) at this time. These updates will be published by IBM when they are available.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q098", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q098", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q098", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nIBM Java SDK Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg22012965]\nACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 05 June 2018: Published\n23 May 2018: Updated security bulletin link\nThe 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.", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q098", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition, Version 6 used by WebSphere Service Registry and Repository and WebSphere Service Registry and Repository Studio. These issues were disclosed as part of the IBM Java SDK updates in January 2018.\n\nThese issues are also addressed by WebSphere Application Server Network Deployment shipped with WebSphere Service Registry and Repository.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q098", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID:CVE-2018-2633 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2633]\nDESCRIPTION:An unspecified vulnerability related to the Java SE JNDI component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/137885 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137885]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H)\nCVEID:CVE-2018-2603 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2603]\nDESCRIPTION:An unspecified vulnerability related to the Java SE Libraries component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.\nCVSS Base Score: 5.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/137855 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137855]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)\n\nCVEID:CVE-2018-2579 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2579]\nDESCRIPTION:An unspecified vulnerability related to the Java SE Libraries component could allow an unauthenticated attacker to obtain sensitive information resulting in a low confidentiality impact using unknown attack vectors.\nCVSS Base Score: 3.7\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/137833 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137833]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\nCVEID:CVE-2018-2602 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2602]\nDESCRIPTION:An unspecified vulnerability related to the Java SE I18n component could allow an unauthenticated attacker to cause low confidentiality impact, low integrity impact, and low availability impact.\nCVSS Base Score: 4.5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/137854 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137854]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L)", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q098", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "WebSphere Service Registry and Repository V8.5 and V8.0 and WebSphere Service Registry and Repository Studio V8.5 are affected.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q098", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "For all releases of WebSphere Service Registry and Repository Studio, upgrade to WebSphere Service Registry and Repository Studio V8.5.6.1_IJ04332 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FWebSphere+Service+Registry+and+Repository&fixids=8.5.6.1-WS-WSRR-Studio-MultiOS-IFIJ04332]\n\nFor WebSphere Service Registry and Repository the issues are addressed by WebSphere Application Server.\n\nPrincipal Product and Version(s) Affected Supporting Product and Version WebSphere Service Registry and Repository V8.5 WebSphere Application Server V8.5.5 WebSphere Service Registry and Repository V8.0 WebSphere Application Server V8.0\nRefer to the following security bulletin for vulnerability details and information about fixes addressed by WebSphere Application Server shipped with WebSphere Service Registry and Repository:\n\nSecurity Bulletin: Multiple Vulnerabilities in IBM\u00ae Java SDK affects WebSphere Application Server January 2018 CPU [http://www.ibm.com/support/docview.wss?uid=swg22013818] GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q098", "section_id": 4, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q098", "section_id": 5, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 14 March 2018: Original version published\nThe 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.", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q098", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition that is shipped with IBM WebSphere Application Server which is shipped with IBM WebSphere Portal. These issues were disclosed as part of the IBM Java SDK updates in April 2018.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q098", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Multiple vulnerabilities in IBM\u00ae Java SDK affect IBM WebSphere Portal.\nNote: If you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities please refer to the link for \"IBM Java SDK Security Bulletin\" located in the \u201cReferences\u201d section for more information.\n\nCVEID:CVE-2018-2783 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2783]\nDESCRIPTION:An unspecified vulnerability related to the Java SE Security component could allow an unauthenticated attacker to cause high confidentiality impact, high integrity impact, and no availability impact.\nCVSS Base Score: 7.4\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/141939 [https://exchange.xforce.ibmcloud.com/vulnerabilities/141939]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N)\n\nCVEID:CVE-2018-2800 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2800]\nDESCRIPTION:An unspecified vulnerability related to the Java SE RMI component could allow an unauthenticated attacker to cause low confidentiality impact, low integrity impact, and no availability impact.\nCVSS Base Score: 4.2\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/141956 [https://exchange.xforce.ibmcloud.com/vulnerabilities/141956]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N)", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q098", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Affected Product Affected Versions IBM WebSphere Portal 9.0 IBM WebSphere Portal 8.5 IBM WebSphere Portal 8.0 IBM WebSphere Portal 7.0\nFor unsupported versions IBM recommends upgrading to a fixed, supported version of the product.", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q098", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Upgrade the SDK per WebSphere Application Server \"Security Bulletin: Multiple Vulnerabilities in IBM\u00ae Java SDK affects WebSphere Application Server April 2018 CPU [https://www-01.ibm.com/support/docview.wss?uid=swg22016282]\".\n\nFor V9.0\nUpgrade the SDK.\n\nFor V8.5\nUpgrade the SDK.\n\nFor V8.0\nUpgrade the SDK.\n\nFor V7.0\nUpgrade the SDK.", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q098", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q098", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]\nIBM Java SDK Security Bulletin [https://www-01.ibm.com/support/docview.wss?uid=swg22015806]", "logical_doc_id": 2, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q098", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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 6 June 2018: Original Version Published\nThe 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.", "logical_doc_id": 2, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q098", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Vulnerability in Apache Struts and Apache Commons FileUpload affects IBM WebSphere Service Registry and Repository (CVE-2016-1181, CVE-2016-1182, CVE-2016-3092)", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q098", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-1181 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1181]\nDESCRIPTION: Apache Struts could allow a remote attacker to execute arbitrary code on the system, caused by the failure to protect against unintended remote operations against components on server memory by the ActionForm instance. An attacker could exploit this vulnerability to execute arbitrary code on the system.\nCVSS Base Score: 8.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113852 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113852] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)\n\nCVEID: CVE-2016-1182 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1182]\nDESCRIPTION: Apache Struts could allow a remote attacker to bypass security restrictions, caused by the improper validation of input by the Validator. An attacker could exploit this vulnerability to modify validation rules and error messages.\nCVSS Base Score: 4.8\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113853 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113853] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L)\n\nCVEID:CVE-2016-3092 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092]\nDESCRIPTION:Apache Tomcat is vulnerable to a denial of service, caused by an error in the Apache Commons FileUpload component. By sending file upload requests, an attacker could exploit this vulnerability to cause the server to become unresponsive.\nCVSS Base Score: 5.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/114336 [https://exchange.xforce.ibmcloud.com/vulnerabilities/114336]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q098", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "WebSphere Service Registry and Repository V8.5\nWebSphere Service Registry and Repository V8.0\n\nFor unsupported versions IBM recommends upgrading to a fixed, supported version of the product", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q098", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "To remediate CVE-2016-1181, CVE-2016-1182 and CVE-2016-3092 you need to apply fixes for both IBM WebSphere Application Server and IBM WebSphere Service Registry and Repository.\n\nFor WebSphere Application Server updates refer to this bulletin regarding CVE-2016-1181 and CVE-2016-1182\nSecurity Bulletin: Vulnerability in Apache Commons affects IBM WebSphere Application Server (CVE-2016-1181 and CVE-2016-1182) [http://www.ibm.com/support/docview.wss?uid=swg21985995]\n\nFor CVE-2016-3092, please refer to this to this bulletin:\nSecurity Bulletin: Apache Commons FileUpload Vulnerability affects WebSphere Application Server (CVE-2016-3092) [http://www.ibm.com/support/docview.wss?uid=swg21987864]\n\nFor WebSphere Service Registry and Repository, all three vulnerabilities have been fixed under APARs IV87422 and IV87429\n\nFixes containing IV87422 and IV87429 have been published and are available from Fix Central.\n\nFor WSRR V8.5\nApply V8.5.6.0_IV79085_IV87422_IV87429_IV89477 [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+Service+Registry+and+Repository&function=fixId&fixids=8.5.6.0-WS-WSRR-MultiOS-IFIV79085_IV87422_IV87429_IV89477]\n\nFor WSRR V8.0 * Apply [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+Service+Registry+and+Repository&function=fixId&fixids=8.0.0.3-WS-WSRR-MultiOS-IFIV65487_IV79085]V8.0.0.3_IV65487_IV79085_IV87422_IV87429_IV89477 [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+Service+Registry+and+Repository&function=fixId&fixids=8.0.0.3-WS-WSRR-MultiOS-IFIV65487_IV79085_IV87422_IV87429_IV89477]\n\nIBM recommends that you review your entire environment to identify vulnerable releases of the open-source Apache Commons Collections and take appropriate mitigation and remediation actions. GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.\n\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.", "logical_doc_id": 3, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q098", "section_id": 4, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] CHANGE HISTORY\n 12 September 2016: Original version published\nThe 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.", "logical_doc_id": 3, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q098", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabiltities in the IBM\u00ae SDK Java\u2122 Technology Edition that is shipped with IBM WebSphere Application Server. These issues were disclosed as part of the IBM Java SDK updates in April 2018. These may affect some configurations of IBM WebSphere Application Server Traditional, IBM WebSphere Application Server Liberty and IBM WebSphere Application Server Hypervisor Edition.", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q098", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "If you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities please refer to the link for \u201cIBM Java SDK Security Bulletin\" located in the References section for more information.\n\nCVEID:CVE-2018-2783 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2783]\nDESCRIPTION: An unspecified vulnerability related to the Java SE Security component could allow an unauthenticated attacker to cause high confidentiality impact, high integrity impact, and no availability impact.\nCVSS Base Score: 7.4\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/141939 [https://exchange.xforce.ibmcloud.com/vulnerabilities/141939]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N)\n\nCVEID:CVE-2018-2800 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2800]\nDESCRIPTION: An unspecified vulnerability related to the Java SE RMI component could allow an unauthenticated attacker to cause low confidentiality impact, low integrity impact, and no availability impact.\nCVSS Base Score: 4.2\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/141956 [https://exchange.xforce.ibmcloud.com/vulnerabilities/141956]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N)", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q098", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "This vulnerability affects the following versions and releases of IBM WebSphere Application Server:\nLiberty\nVersion 9.0\nVersion 8.5", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q098", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "To patch an existing service instance refer to the IBM WebSphere Application Server bulletin listed below:\n\nSECURITY BULLETIN: MULTIPLE VULNERABILITIES IN IBM\u00ae JAVA SDK AFFECTS WEBSPHERE APPLICATION SERVER APRIL 2018 CPU [HTTP://WWW-01.IBM.COM/SUPPORT/DOCVIEW.WSS?UID=SWG22016282]\nAlternatively, delete the vulnerable service instance and create a new instance.", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q098", "section_id": 4, "heading": "WORKAROUNDS AND MITIGATIONS", "parent": null, "text": "None\n\nADDITIONAL BLUEMIX ALERT INFORMATION\nMonitor the Bluemix console (https://console.ng.bluemix.net/status/ [https://console.ng.bluemix.net/status/]) for additional important product alerts.\n\nREFERENCE\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q098", "section_id": 5, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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\n20 July 2018: original document published\nThe 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.", "logical_doc_id": 4, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q039", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Which WebSphere DataPower virtual edition fix pack can I upgrade to and downgrade from?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q039", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Not all scrypt4 fix packs are compatible with the 5.0.0.0 OVA files that were released in November 2012 and March 2013. If you upgrade or downgrade with an incompatible fix pack, unexpected errors might occur.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q039", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Use the following links to determine which fix packs are compatible with your virtual deployment.\n5.0.0.0 from 30 November 2012 (build 220750)\n5.0.0.0 from 29 March 2013 (build 227007)\n5.0.0.5\n5.0.0.6\n5.0.0.8 or later\n6.0.0.0 or later\n\n5.0.0.0 from 30 November 2012 (build 220750)\nWhen your virtual deployment is the OVA file from 30 November 2012, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013.\n\nBack to top\n\n5.0.0.0 from 29 March 2013 (build 227007)\nWhen your virtual deployment is the OVA file from 29 March 2013, you can install only the 5.0.0.0 fix pack and 5.0.0.8 or later fix packs from Fix Central. On Fix Central, the 5.0.0.5 and 5.0.0.6 fix packs are for the 5.0.0.0 OVA release from 30 November 2013.\n\nBack to top\n\n5.0.0.5\nWhen your virtual deployment is 5.0.0.5, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013.\n\nBack to top\n\n5.0.0.6\nWhen your virtual deployment is 5.0.0.6, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013.\n\nBack to top\n\n5.0.0.8 or later\nWhen your virtual deployment is 5.0.0.8 or later, do not install any fix pack from Fix Cental that is earlier than the 5.0.0.8 fix pack. The 5.0.0.8 fix pack has critical fixes. For more information, see Critical Updates [http://www-01.ibm.com/support/docview.wss?uid=swg21390112#part2].\n\nNote: You must install the 5.0.0.8 or later fix pack to upgrade to 6.0.0.0 or later. The 5.0.0.8 fix pack contains a required fix to allow the larger sized firmware image to fit.\n\nBack to top\n\n6.0.0.0 or later\nWhen your virtual deployment is the 6.0.0.0 OVA file or a firmware upgrade through a 6.0.0.0 or later fix pack, do not install any fix pack from Fix Cental that is earlier than the 5.0.0.8 fix pack. The 5.0.0.8 fix pack has critical fixes. For more information, see Critical Updates [http://www-01.ibm.com/support/docview.wss?uid=swg21390112#part2].\n\nBack to top\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower Service Gateway XG45 Virtual Edition VMware ESXi, VMware ESX 5.0.0, 6.0.0 Edition Independent", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q039", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "NOTE: DataPower highly recommends upgrading to a version containing the fix for APAR IC80983\n\nA DataPower 9235 appliance may be restarted without a back trace by its hardware watchdog due to a Baseboard Management Controller (BMC) communications loss.\n\nThis also rarely causes a failure to restart successfully.\n\nIf a failure to restart occurs, the appliance needs to be manually power cycled by removing and then replacing the power cords.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q039", "section_id": 1, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Due to the potential impact of this problem, DataPower highly recommends upgrading to a version containing the fix for APAR IC80983.\n\nTo check if your system may be susceptible to this issue check the output of these commands:\n*\nIf the BMC version listed is below 0.29 we highly recommend upgrading [http://www-01.ibm.com/support/docview.wss?uid=swg21237631]to install the fix for this issue as outlined below.\n\nThe fix was first included in the 3.8.1.20, 3.8.2.11, 4.0.1.8, and 4.0.2.4 fixpacks. Please install [http://www-01.ibm.com/support/docview.wss?uid=swg21237631]this fixpack level or higher.\n\nNote: Due to the nature of this issue the upgraded BMC level will remain installed even if downgraded to levels of the 3.8.1, 3.8.2, 4.0.1,and 4.0.2 firmware below the 3.8.1.20, 3.8.2.11, 4.0.1.8, and 4.0.2.4 fixpacks.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q039", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Follow these steps to upgrade the 9235 appliance to a firmware level containing the new BMC firmware level to resolve this issue.\n\n1. Stop traffic to the appliance and gather the output of the following CLI commands:\n*\nNote the \"BMC Firmware Version\"", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q039", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "2. If the BMC level is displayed perform a reboot of the appliance to free resources and proceed to the next step (step 3).\n\nIf the BMC version is not displayed, power off and unplug the power cords for 30 to 60 seconds then connect the power and boot the appliance. When the appliance boots, check the output again to ensure the BMC version is displayed if not repeat the power off and unplug.\n\n3. Upload the firmware image to the appliance and perform the \"Boot Image\". For questions on upgrading firmware see our Upgrade Knowledge Collection [http://www.ibm.com/support/docview.wss?uid=swg27015333&loc=en_US&cs=utf-8&lang=en]\n\n4. When the automatic reboot is complete collect the outputs for the same commands from step one. Note the BMC version should now be 0.29 or higher", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q039", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "5. To clear the old impi entries from the logs issue the following:\n*\n*\n*\n*\n*Note: The commands \"clear-ipmi-sel\" and \"show ipmi\" are not present in version 3.8.1.20 firmware.\n\nIf there are any issues contact DataPower Support [http://www.ibm.com/support/docview.wss?uid=swg21236322] and include the following information: *\n*\nshow clock\n show ipmi\n show filesystem\n config\n service show component-firmware\n\nNote: As stated above, due to the nature of this issue the upgraded BMC level will remain installed even if downgraded to levels of the 3.8.1, 3.8.2, 4.0.1,and 4.0.2 firmware below the 3.8.1.20, 3.8.2.11, 4.0.1.8, and 4.0.2.4 fixpacks.\n\nThe document \"Supported firmware versions and recommended upgrade levels for IBM WebSphere DataPower SOA Appliances\" [http://www-01.ibm.com/support/docview.wss?uid=swg21237631] contains links to the latest firmware releases.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower B2B Appliance XB60 4.0.2, 4.0.1, 4.0, 3.8.2, 3.8.1, 3.8 All Editions Business Integration WebSphere DataPower Low Latency Appliance XM70 3.8, 3.8.1, 3.8.2, 4.0, 4.0.1, 4.0.2 All Editions Business Integration WebSphere DataPower XML Security Gateway XS40 4.0.2, 4.0.1, 4.0, 3.8.2, 3.8.1, 3.8 All Editions Business Integration WebSphere DataPower XML Accelerator XA35 4.0.2, 4.0.1, 4.0, 3.8.2, 3.8.1, 3.8\n\nv25xc10rnotes; v86xsrnotes DOWNLOADABLE FILES", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q039", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "Download IBM WebSphere DataPower XC10 Appliance Version 2.5 Fix Pack 4, also known as V2.5.0.4.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q039", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "This firmware release includes improved capability and usability enhancements for the appliance. For more information, see the WebSphere DataPower XC10 Appliance V2.5 product documentation [http://www.ibm.com/support/knowledgecenter/SSS8GR_2.5.0/com.ibm.websphere.datapower.xc.doc/whatsnew.html?lang=en]. For a list of fixes and improvements that are included in this fix pack, see the IBM WebSphere eXtreme Scale and WebSphere DataPower XC10 Appliance Releases and Updates [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W30b21440b0d9_432c_8e75_b16bac9c5427/page/IBM%20WebSphere%20eXtreme%20Scale%20and%20DataPower%20XC10%20Appliance%20Releases%20and%20Updates] web page.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q039", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Note: For certain levels of installed firmware, a rolling upgrade of a collective of appliances might lead to a corrupted configuration. Before you attempt a rolling upgrade from V2.5 Fix Pack 3 to this fix pack level, see the technote about this firmware upgrade problem [http://www.ibm.com/support/docview.wss?uid=swg21692158].\n\nIBM WebSphere DataPower XC10 Virtual Appliance for Developers:Download the IBM WebSphere DataPower XC10 Virtual Appliance for Developers [http://www.ibm.com/developerworks/downloads/ws/wsdvad/index.html], which is an open virtual appliance (OVA) package that you can import into your virtualization environment. With this image, you can test and develop with the XC10 software before you create your data grid on the physical appliance.\n\nPREREQUISITES\nTwo firmware upgrades exist for this release. See the following descriptions to determine which firmware upgrade to download:\n\nRun the show ssd-version command from a command prompt. If this command does not exist on your system, then, the SSD driver installed in the appliance is level 3.1.1. If the command exists on your system, then the output indicates whether the appliance is at SSD driver level 3.1.1 or 3.2.6; for example:\n\nCommand output from a virtual appliance where there is no SSD card.\nConsole> show ssd-version\nNo version reported. By default, use a firmware not tagged for VSL 3.2.6.\n\nCommand output from a virtual appliance where there is an old SSD card.\nConsole> show ssd-version\nVersion: 3.1.1 build 172. By default, use a firmware not tagged for VSL 3.2.6.\n\nCommand output from an appliance where there is a newer SSD driver:\nConsole> show ssd-version\nVersion: 3.2.6 build 1212. Use a firmware tagged for VSL 3.2.6\n\nAlternatively, in the monitoring console, click Collective > Members. Select a collective member. If the line SSD Version is present, then determine whether the level is 3.2.6 or higher. If so, you have the new driver. If not, then you have the old driver.\n\nFirmware and driver 9005.rel.xc10.scrypt3", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q039", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "This firmware image contains the VSL 3.1.1 SSD driver. This image includes a firmware driver that is intended for appliances that already contain the VSL 3.1.1 or lower SSD driver. When you install this image, you also upgrade the SSD driver. After you have upgraded, the appliance firmware cannot be rolled back to the previous 2.1.0.0 version. However, you can roll back to the VSL 3.1.1 firmware version that you had before you applied the VSL 3.1.1 SSD driver upgrade.\n\nFirmware and driver 9005.rel.xc10.vsl.3.2.6.scrypt3\n\nThis firmware image contains the latest VSL 3.2.6 SSD driver. This image includes a firmware driver that is intended for appliances that contain the VSL 3.2.6 or lower version. After you upgrade with this firmware image, the appliance firmware cannot be rolled back to the previous firmware version that you installed for V2.5 Fix Pack 3. Likewise, if you upgrade to this VSL 3.2.6 SSD driver from an existing VSL 3.1.1 SSD driver, then you cannot roll back to the VSL 3.1.1 SSD driver version. However, if you upgrade to a firmware that contains the VSL 3.2.6 SSD driver from an appliance that already contains the VSL 3.2.6 SSD driver, the you can roll back to the previous VSL 3.2.6 firmware version.\n\nAlternatively, use the following table to determine the rollback scenarios for each firmware and driver image:\n\nBegin with SSD driver Upgrade the firmware using driver Rollback available VSL 3.1.1 VSL 3.1.1 Yes VSL 3.1.1 VSL 3.2.6 No VSL 3.2.6 VSL 3.1.1 You must roll back because this scenario causes the system to fail. VSL 3.2.6 VSL 3.2.6 Yes INSTALLATION INSTRUCTIONS\nComplete the following instructions to download the firmware and client images.\n\n1. Initialize and configure the appliance.\n The firmware upgrades for the 7199-92x (2426-92X) appliances are available in this document. See Inihtializing and configuring WebSphere DataPower XC10 Appliance [http://pic.dhe.ibm.com/infocenter/wdpxc/v2r5/topic/com.ibm.websphere.datapower.xc.doc/tinitappl.html] in the product information center for more information about the initialization and firmware upgrade process.\n\nNote: The type 7199 appliances can have one of two machine types depending on when they were ordered. Type 2426, listed in parentheses, is the machine type model (MTM) if the appliance is ordered from Passport Advantage.\n\nDOWNLOAD PACKAGE", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q039", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] Virtual appliance upgrade 8 Dec 2014 Language Independent 290118034 FC [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+DataPower+XC10+Appliance&release=All&platform=All&function=fixId&fixids=2.5.0-WS-DPXC10-VIRT-FP0000004&includeSupersedes=0] [ ] 2426-92X Firmware 9005.rel.xc10.vsl.3.2.6.scrypt3 8 Dec 2014 Language Independent 298881400 FC [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+DataPower+XC10+Appliance&release=All&platform=All&function=fixId&fixids=2.5.0-WS-DPXC10-7199-VSL-3.2.6-FP0000004&includeSupersedes=0] [ ] 2426-92x Firmware 9005.rel.xc10.scrypt3 8 Dec 2014 Language Independent 282992068 FC [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+DataPower+XC10+Appliance&release=All&platform=All&function=fixId&fixids=2.5.0-WS-DPXC10-7199-FP0000004&includeSupersedes=0] [ ]\nTECHNICAL SUPPORT", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q039", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "Effective 19 June 2016, IBM will withdraw support for the WebSphere DataPower SOA Appliances 6.0 and 6.0.1 firmware levels.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q039", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Effective 19 June 2016, IBM will withdraw support for the WebSphere DataPower SOA Appliances 6.0 and 6.0.1 firmware levels. See software withdrawal and discontinuance of service announcement letters:\n\nUS 915-085 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/5/897/ENUS915-085/index.html&lang=en&request_locale=en] Canada A15-0304 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/649/ENUSA15-0304/index.html&lang=en&request_locale=en] EMEA ZP15-0207 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/877/ENUSZP15-0207/index.html&lang=en&request_locale=en] AP WP15-0057 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/872/ENUSWP15-0057/index.html&lang=en&request_locale=en] Japan JP15-0206 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/6/760/ENUSJP15-0206/index.html&lang=en&request_locale=en] LA LP15-0206 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/6/899/ENUSLP15-0206/index.html&lang=en&request_locale=en]\n\nEffective 19 June 2016, IBM will withdraw support for firmware level 6.0 and 6.0.1 on the following WebSphere DataPower SOA Appliances:\nXG45 (7198-32X, 2426-32X/33X)\nXG45 Virtual Edition\nXI52 (7199-42X, 2426-42X/43X)\nXI52 Virtual Edition\nXB62 (7199-62X, 2426-62X/63X)\n\nNote: Standard firmware support (all releases) for the XI50 Blade (MTM 4195-4BX) ends 4/30/2015. See IBM WebSphere DataPower Appliance Support Lifecycle [http://www.ibm.com/support/docview.wss?rs=2362&uid=swg21246298] and announcement letter [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/6/897/ENUS913-076/index.html&lang=en&request_locale=en] 914-067 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/897/ENUS914-067/index.html&lang=en&request_locale=en] for more information.\n\nCustomers running firmware level 6.0 or 6.0.1 (or any earlier level) are advised to plan to upgrade to the latest supported releases of WebSphere DataPower firmware in order to continue receiving technical support, as well as proactively avoiding problems that are already resolved. Refer to Supported Firmware versions and recommended upgrade levels [http://www-01.ibm.com/support/docview.wss?uid=swg21237631] for more information.\n\nIBM recommends that users consider applying the 7.0 or 7.1 latest fixpack version (or later) of the firmware. Of course, in the case of upgrading firmware for any critical embedded system, IBM recommends that users test their configurations and surrounding applications before moving into production. To easily find the latest fixpack levels, please use this link: http://www-01.ibm.com/support/docview.wss?uid=swg21237631 [http://www-01.ibm.com/support/docview.wss?uid=swg21237631] .\n\nIn addition, refer to the following documents:\nIBM WebSphere DataPower Appliance Support Lifecycle [http://www.ibm.com/support/docview.wss?rs=2362&uid=swg21246298]\nCritical updates for IBM WebSphere DataPower SOA appliances [http://www-01.ibm.com/support/docview.wss?rs=2362&uid=swg21390112] (for guidance when migration to a later firmware level)", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q039", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What are some guidelines with respect to managing expired third-party public CA certificates in the pubcert: directory on the IBM WebSphere DataPower SOA appliance?", "logical_doc_id": 5, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q039", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "While the IBM WebSphere DataPower SOA appliance provides some standard public CA certificates in pubcert: for convenience, you may encounter missing certificate file errors after firmware upgrades across major release boundaries.\n\nWhat would cause a certificate file to be removed from pubcert:?\nAt the beginning of any major firmware release (3.7.1.0 or 3.7.2.0 or 3.7.3.0 or 3.8.0.0), all expired public CA certificates are removed from the pubcert: directory in the firmware packaging. Expired public CA certificates are not removed in minor firmware releases. This means that upgrading within a release series will not cause a certificate file to be removed from pubcert: but upgrading across a major release boundary might.\n\nWill a firmware upgrade fix the missing certificate file error?\nA firmware upgrade will not fix the missing certificate file error since firmware upgrades do not include replacement public certificates to update expired certificates. Replacement certificates for expired public certificates must be obtained from the vendor's public site and uploaded to the DataPower appliance.\n\nHow can I fix my configuration when a certificate file is removed from pubcert:?\nIf the CA in question is not needed by the customer, then the configuration can be repaired by removing references to the removed certificate file. This can be accomplished by first finding any Crypto Certificate objects that refer to the removed file (they will be in a down state), then by removing references to that Crypto Certificate from any configuration objects that refer to it (such as Validation Credentials objects), and finally by deleting the Crypto Certificate object in question.\n\nIf the CA in question is needed by the customer, then the user must obtain an updated copy from the CA's public site, upload the new certificate to the DataPower appliance, and then reconfigure the down Crypto Certificate object to refer to the new certificate file.", "logical_doc_id": 5, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q039", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "How can I monitor for certificate expiration?\nCustomers have the option of defining a Certificate Monitor, a configurable periodic task used to check and report on expiration dates of Crypto Certificate objects. Refer to the Administrator's Guide for details on configuring the monitor. Note that the Certificate Monitor only checks certificates for which a Crypto Object is configured in that it scans the list of configured objects rather than scanning all files in a given directory. Refer to the WebSphere DataPower product documentation portal [http://www.ibm.com/support/docview.wss?rs=2362&uid=swg21377654] to access the Administrator's Guide. You will need to sign into the portal with your IBM registration ID.\n\nFor example, the terminology as logged by the error log might contain errors like these\n\n1,20140225T064505Z,default,audit,error,,,95,,0x8240001b,,,\"(SYSTEM:default:*:*): certificate 'ABC-Global-CA-pem' - File is unreadable\"\n\n1,20140225T064506Z,default,crypto,error,certificate,GTE-CyberTrust-Root-4-pem,95,,0x80600086,,,\"*certificate file 'pubcert:ABC-CyberTrust-Root-4.pem' unreadable*\"\n\nThe files are listed as unreadable. If a user goes into the file system and views one of these certificates, they will see the validity date has passed.", "logical_doc_id": 5, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q029", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How can I improve the performance of Operational Decision Management (ODM) Decision Center and WebSphere ILOG Rule Team Server (RTS)?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q029", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "This document addresses how to improve the performance when working with ODM Decision Center or Rule Team Server (RTS) . For the purposes of this document, we will use RTS to refer to both entities, unless explicitly stated otherwise.\n\nYou can incorporate the following recommendations, if applicable to your environment:\n\nInstallation * Separate your installations of Rule Execution Server (RES) and RTS. A high RES execution load will negatively impact RTS performance. Check if you been seeing heavier than normal RES execution loads during the period of poor RTS performance.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q029", "section_id": 0, "heading": "RELATED INFORMATION", "parent": null, "text": "Improve Performance of Rules Execution [http://www.ibm.com/support/docview.wss?uid=swg21589513]\nImprove Performance of Rule Studio and Rule Designer [http://www.ibm.com/support/docview.wss?uid=swg21589514]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere ILOG Rule Team Server Performance Platform Independent 7.1, 7.0, 6.7, 6.6", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q029", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "For example, I get the following error when I execute a DVS test:\n\nThe version of the application which has generated the ruleset archive /prodra1387398245412_8e4f8b7e_7933_4a17_bd7e_a13543042794/1.0/prodrs1387398245412_8e4f8b7e_7933_4a17_bd7e_a13543042794/1.0 is 8.0.\nIlrExcel2003S E Throwable caught while invoking test ruleset factory\njava.lang.VerifyError:\nilog/rules/archive/IlrRulesetArchiveBuilderBase.generate()Lilog/rules/archive/IlrRulesetArchive;\nat ilog.rules.dvs.rbtesting.rules.IlrTestRulesetFactory.createTestRulesetArchive(IlrTestRulesetFactory.java:449)", "logical_doc_id": 2, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q029", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The presence of the Rule Execution Server libraries in the system or server class path, or in the shared lib folder might explain the issue.", "logical_doc_id": 2, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q029", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Verify the following points:\nAll Rule Execution Server modules are deployed as indicated in the documentation: the class loading policy should be parent last for all EAR files (see the links further below).\nAll client applications are packaged as indicated in the documentation (see the links further below).\nNo Rule Execution Server libraries are present in the system or server class path.\n\nFor example, the following client library JAR files for Rule Execution Server rule sessions must be packaged only inside the client EAR files and not be present anywhere else in the class path:\njrules-res-session-java.jar for POJO,\njrules-res-session-ejb3-.jar for EJB3.\njrules-res-mdb-.jar for MDB.\n\nFor DVS tests and hosted transparent decision services (HTDS), all you need to do is deploy the SSP application and the HTDS EAR.\n\nThe execution of the rules requested by all those Rule Execution Server clients is then handled by the Rule Execution Server XU resource adapter. You do not need anything else in the server class path.", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q029", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#Configuring Rule Execution Server on WAS [http://pic.dhe.ibm.com/infocenter/dmanager/v8r5m1/topic/com.ibm.odm.distrib.config.was/config_ds_res_was8/con_res_was.html]\nCreating a client for Rule Execution Server [http://pic.dhe.ibm.com/infocenter/dmanager/v8r5m1/topic/com.ibm.odm.dserver.rules.res.developing/topics/tpc_res_client_intro.html]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere ILOG JRules Modules:Execution Server (BRES / RES) Platform Independent 7.1, 7.0", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q029", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do I set the JNDI properties through the Rule Execution Server EJB3 client API?", "logical_doc_id": 3, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q029", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The new EJB3 Rule Execution Server remote client API does not provide a way to set JNDI properties programmatically, as the EJB2 API (now deprecated) does (see the IlrRuleSessionProviderFactory API documentation [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.doc/html/api/html/ilog/rules/bres/session/IlrRuleSessionProviderFactory.Builder.html]).\nThe alternative is to use a JNDI property file. However, even when the JNDI properties are correct, errors such as the following one can occur when the client application is running from a server (whether from the same vendor or not) remote to Rule Execution Server:\n\nSystemErr R ilog.rules.res.session.IlrSessionCreationException: An error occurred while the rule session was created.:\njavax.naming.NameNotFoundException: Context: TestNode01Cell/nodes/TestNode01/servers/server1, name: ilog.rules.res.session.impl.ejb3.IlrStatelessSessionRemote: First component in name ilog.rules.res.session.impl.ejb3.IlrStatelessSessionRemote not found.\norg.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0\n\nMoreover, it is not recommended to use JNDI property files in a Java EE container as this could be picked up by other applications and affect their behavior.", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q029", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "The solution is to bypass the EJB3 IlrSessionFactory API and use the Java EJB API to look up rule sessions directly:\n* Properties props = new Properties();\n props.setProperty(Context.PROVIDER_URL, \"...\");\n props.setProperty(Context.INITIAL_CONTEXT_FACTORY, \"...\");\n InitialContext context = new InitialContext(props);\n IlrStatelessSession session = (IlrStatelessSession)context.lookup(jndiName);\n ...\n\nAfter the IlrStatelessSession object is retrieved, use the Rule Execution Server client API as documented.\n\nStarting in the V7.5 version of the product, it is possible again to set JNDI properties through the Rule Execution Server remote client API (see V7.5 IlrEJB3SessionFactory API documentation [http://publib.boulder.ibm.com/infocenter/dmanager/v7r5/topic/com.ibm.dserver.reference.res/html/api/html/ilog/rules/res/session/IlrEJB3SessionFactory.html]). Therefore, it is ultimately recommended to upgrade to the latest version (see download document below).", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q029", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#WODM/ODM Download document [http://www.ibm.com/support/docview.wss?uid=swg24031636]\n\"Hello World\" EJB3 remote client for RES V7 on WAS V7 [http://www.ibm.com/support/docview.wss?uid=swg21461685]\nAssembling and packaging a RES EJB application [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.doc/Content/Business_Rules/Documentation/_pubskel/JRules/ps_JRules_Global967.html]", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q029", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The problem may occur when a JRules or ODM module accesses its data source after a period of database access inactivity. For example:\nThe 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.\nAfter 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.", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q029", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The 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.", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q029", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "The 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]", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q029", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "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 :\nSet 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\nSet the values for Unused timeout and Reap timeout so that the sum does not exceed any network level idle connection timeout\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\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", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q029", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Which RES execution component should I package in my application if I use IlrPOJOSessionFactory?", "logical_doc_id": 5, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q029", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "In JRules 7, there are several rules session factories (IlrEJB3SessionFactory, IlrJ2SESessionFactory, IlrPOJOSessionFactory, IlrExtendedJ2SESessionFactory, IlrExtendedPOJOSessionFactory) for client application to connect to RES for rule invocations.\n\nIn a JEE environment, if you prefer to have a simple and non-ejb approach (web application or decision service), you can make use of IlrPOJOSessionFactory APIs for rule session creation. The execution component that is required to package together with the application will be simply jrules-res-session-java.jar. This jar file can be found at \\executionserver\\lib folder.\n\nFor JRules version 7.0.X, refer to JRules documentation at:\nWebSphere ILOG JRules V7.0 > Rule Studio online help > Executing rules > Tasks > Assembling and packaging a Rule Execution Server application > Packaging Java rule sessions [http://publib.boulder.ibm.com/infocenter/brjrules/v7r0/index.jsp?topic=/ilog.rules.jrules.doc/Content/Business_Rules/Documentation/_pubskel/JRules/ps_JRules_Global854.html]\n\nFor JRules version 7.1.X, refer to JRules documentation at:\nWebSphere ILOG JRules BRMS V7.1 > Rule Execution Server > Introducing Rule Execution Server > Assembling and packaging a Rule Execution Server application > Packaging Java rule sessions [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/index.jsp?topic=/com.ibm.websphere.ilog.jrules.doc/Content/Business_Rules/Documentation/_pubskel/JRules/ps_JRules_Global966.html]", "logical_doc_id": 5, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q029", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "#Choose a rule session to call RES on JEE server [http://www-01.ibm.com/support/docview.wss?uid=swg21400825]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Platform Independent 7.5 Enterprise", "logical_doc_id": 5, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q032", "section_id": 0, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Run the NMO install interactively [http://www-01.ibm.com/support/knowledgecenter/SSEUEX_2.0.3/com.ibm.installingeuc.doc/eucco044.htm?lang=en].\nIf the installation works as expected, the problem is with the deployment tool being used.\nNote: Do not use the NMO .msi file to perform the installation as this is not supported.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q032", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "1. Verify NMO pre-requisites [http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1379371439042&osPlatforms=AIX%7CLinux%7CMac%20OS%7CWindows&duComponentIds=D009&mandatoryCapIds=30%7C126%7C9%7C140%7C61%7C26&optionalCapIds=12%7C63%7C35] are met.\n 2. Run the NMO install interactively. * If this works as expected, the issue is with the deployment tool.\nIf there is an issue with manual execution of the installation exe, then open a problem management record (PMR) with IBM Support.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q032", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "Pre-requisites for IBM Content Navigator for Microsoft [http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1379371439042&osPlatforms=AIX|Linux|Mac%20OS|Windows&duComponentIds=D009&mandatoryCapIds=30|126|9|140|61|26&optionalCapIds=12|63|35]\nIBM Content Navigator v2.0.3 Download [http://www.ibm.com/support/docview.wss?uid=swg24038160]\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Content Navigator\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q032", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "File extension is not provided when downloading a report.After\n selecting a report in Browse/Personal documents, one can perform\n several actions. If one chooses Download CSV or Download to\n Excel, the application does not provide for a file extenstion.\n This way the operating system doesn't seems to know in what\n format to save the file or which applicaiton to use to open the\n file in.\n\nPlease refer to the following snapshot on steps to reproduce the\n problem reported:-\n\n1) Login to TNMPW page----->Browse---->personal\n documents----->Select Action--->Download in Excel\n\n2) The save button will just save the file as CAEJSBFS, with no\n file extension type as xls\n\n3) If you choose the option \"Option\", windows present you with\n the \"Open with\" screen.\n\n4) Had to manually choose the application in Excel.\n\n5) When saving a report as a CSV-file, it doesnt show the\n extension.\n\n6) Therefore,it likes to save it as an HTML document.Once can\n do two things:\n a) Save the report without extension:the OS writes the file down\n as an HTML-document.\n b) Put the CSV extension in place; the file will be saved as a\n CSV-file.\n\n7) If one did not specify the extension as html or csv(as for\n the CAO1A5XC example), 2 files will be saved to the directory.\n The CAO1A5ZC.file are also created with 0 kb size.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q032", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "The problem had been fix in IE7, but customer require for the\n function to work on IE6.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q032", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "*\nUSERS AFFECTED: 9.1.2 Users *\n*\n\nRECOMMENDATION: Apply the following fix when available *\n*\nThe fix for this APAR is to be contained in the following *\nmaintenance package(s): *\n*\n| fixpack | 9.1.2.26-TIV-TNPMW-FP0003 *\n*\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q032", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IZ41786\nREPORTED COMPONENT NAME\n NETCOOL PM WIRE\nREPORTED COMPONENT ID\n 5724T0100\nREPORTED RELEASE\n 912\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2009-01-15\nCLOSED DATE\n 2009-01-31\nLAST MODIFIED DATE\n 2009-01-31\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q032", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n NETCOOL PM WIRE\nFIXED COMPONENT ID\n 5724T0100", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q032", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R912 PSN\n UP\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\nDIRECT LINKS TO FIXES\n3.0.1-ICN-WIN [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FContent+Navigator&fixids=3.0.1-ICN-WIN&source=SAR]\n3.0.1-ICN-zLINUX [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FContent+Navigator&fixids=3.0.1-ICN-zLINUX&source=SAR]\n3.0.1-ICN-LINUX [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FContent+Navigator&fixids=3.0.1-ICN-LINUX&source=SAR]\n3.0.1-ICN-AIX [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FContent+Navigator&fixids=3.0.1-ICN-AIX&source=SAR]", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q032", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "IBM Content Navigator is downloading XSN files stored in a\n Content Manager Repository with a .dat extension", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q032", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "When a user downloads a Microsoft InfoPath file, IBM Content\n Navigator appends the .dat file extension.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q032", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This issue has been addressed in IBM Content Navigator V2.0.3\n Fix Pack 8 LA008.\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q032", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IO25185\nREPORTED COMPONENT NAME\n CONTENT NAVIGAT\nREPORTED COMPONENT ID\n ISCONTNAV\nREPORTED RELEASE\n 203\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2017-03-19\nCLOSED DATE\n 2017-04-26\nLAST MODIFIED DATE\n 2017-04-26\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q032", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n CONTENT NAVIGAT\nFIXED COMPONENT ID\n ISCONTNAV", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q032", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R203 PSY\n UP\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q032", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Unable to view MS Office documents ingested as\n 'application/octate-stream' after upgrading ICN to V2.0.3.8.\n When downloading, ICN associates these documents with .bin. The\n same documents can be opened using ICN V2.0.3.6", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q032", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "When a user downloads a document as original, the file is\n downloaded with a .bin or .dat file extension or without the\n expected extension.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q032", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This has been addressed in IBM Content Navigator V2.0.3.8\n LA013, V3.0 LA010, V3.0.1 LA003, and V3.0.2.\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q032", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IO25586\nREPORTED COMPONENT NAME\n CONTENT NAVIGAT\nREPORTED COMPONENT ID\n ISCONTNAV\nREPORTED RELEASE\n 203\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2017-08-23\nCLOSED DATE\n 2017-10-16\nLAST MODIFIED DATE\n 2017-10-16\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q032", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n CONTENT NAVIGAT\nFIXED COMPONENT ID\n ISCONTNAV", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q032", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R203 PSY\n UP", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q032", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "A .dat extension is added to the CSV document upon download.", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q032", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "A CSV document is basically a plain text file. If the mime type of the document as shown in system properties in ICN is not text/csv, then Navigator cannot recognize the document and a .dat extension will be added upon download. The correct mime type for a CSV file is text/csv.", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q032", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "If there are CSV document already in the content repository with a mime type that is not text/csv, then in order to view them in a text editor (ex. Notepad), you may use the following workaround:\nsave the document to the local machine with .dat extension\nright click on the .dat file and click Open With...\nclick 'Choose your default program...'\nthen select Notepad or another text editor of your choice\nselect the checkbox 'Always use the selected program to open this type of file'\n\nThe other alternative is to change the mimetype of the document in the content repository using a custom solution written using the repository's client APIs.", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q246", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Viewing the log using 'cmureport' produces 'Error: The Log File is not a version 2.0 Log File' at the end of the log.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q246", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "corrupted log file logacct.dat", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q246", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "stop Connect:Enterprise ( ceushutdown ) - delete corrupted logfile - restart Connect:Enterprise ( ceustartup )\n\nHISTORICAL NUMBER\n PRI5952\n\nPRODUCT ALIAS/SYNONYM\n\nFact\n\nConnect:Enterprise UNIX\nRelease 2.2.00\nSCI73578\n\nA FIX IS AVAILABLE\nTivoli Log File Agent, Version 6.2.3.2 Interim Fix 07 6.2.3.2-TIV-ITM_LFA-IF0007 [http://www-01.ibm.com/support/docview.wss?uid=swg24038012]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q246", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The Log File Agent is monitoring a file on a mounted file\n system. Once a day the file system is unmounted and copied.\n The file system is remounted and the log is created when a new\n entry is created. There is a timing condition that happens\n where a return code 26, file busy is returned while the file\n system is unmounted and remounted. The log file is no longer\n monitored after the error code is returned. The log shows this:\n .\n\n(50F6C071.0001-14:kraaevst.cpp,678,\"listSitStat\") *STAT-INFO:\n\n(50F811F1.0000-14:kraaevst.cpp,664,\"listSitStat\") *STAT-INFO:\n************** Situation Statistics Fri Jan 18 00:00:01 2013\n (50F811F1.0001-14:kraaevst.cpp,678,\"listSitStat\") *STAT-INFO:\n\n(50F8956B.0000-E:kumpwfrm.c,270,\"KUMP_WaitFileReadyForMonitor\")\n Opening file /s01az03p06/p/BAXX/log/latest/BAXX.log\n FILEEXISTWAIT=Y size 0\n (50F8956B.0001-E:kumpwfrm.c,321,\"KUMP_WaitFileReadyForMonitor\")\n** Unable to open file /s01az03p06/p/BAXX/log/latest/BAXX.log,\n Errno: 26, ErrorText: Text file busy, NO retry. Exiting\n (50F8956B.0002-E:kumpfdp5.c,342,\"CheckFileExistAndReady\") ***\n File /s01az03p06/p/BAXX/log/latest/BAXX.log -- initial\n monitoring setup\n failed(50F8956B.0003-E:kumpfile.c,1113,\"KUMP_FileServer\") >>>>>\n DP file server process ended for file\n /s01az03p06/p/BAXX/log/latest/BAXX.log last position 175\n current/last EOF 175/175. ThreadID: E\n .\n RECREATE INSTRUCTIONS:\n Attempted to recreate with a mounted file system. This is a\n timing issue, and I was not able to recreate the problem.\n .\n Approver Initials: JW", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q246", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "The workaround for this problem is to create the monitored\n file after remounting the file system.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q246", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "When monitoring a file on a mounted file system, there is a\n timing condition when opening the file where a return code 26,\n file busy is returned while the file system is un-mounted and\n remounted. The log file is no longer monitored after the error\n code is returned.\n\nThis problem was found on Log File Agent 6.2.3 FP1, but existed\n in prior releases.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q246", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "If a return code 26 (file busy) is returned when opening the\n file, the agent now wait and tries to open the file again.\n\nThe fix for this APAR is included in the following maintenance\n vehicle:\n\n| interim fix | 6.2.3.2-TIV-ITM_LFA-IF0003\n\navailable at\n http://www.ibm.com/support/docview.wss?uid=swg24034607 [http://www.ibm.com/support/docview.wss?uid=swg24034607]\n\nIt is also included in Log File Agent, v6.3 (CIGM5ML).\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q246", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV36678\nREPORTED COMPONENT NAME\n ITM LOG FILE AG\nREPORTED COMPONENT ID\n 5724C04LF\nREPORTED RELEASE\n 623\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-02-12\nCLOSED DATE\n 2013-03-28\nLAST MODIFIED DATE\n 2013-03-28\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q246", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n ITM LOG FILE AG\nFIXED COMPONENT ID\n 5724C04LF", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q246", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R623 PSY\n UP\nR630 PSY\n UP\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q246", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Additional Fixes Installed:\n\nV5R19SP4 HF27\n\nEnvironment:\n\nClient OS and level: Windows XP SP2\n\nServer OS and level: Windows Server 2003 SP2\n\nDatabase and level: Oracle 10g2\n Scenario:\n\n1 - Log on to SmarTeam Editor with a user who has full\n authorizations (for example joe);\n\n2 - Checkout an assembly with one part inside of it;\n\n3 - Delete this part form the assembly in SolidWorks;\n\n4 - Add another part (already saved in SmarTeam) in the\n assembly;\n You can use any Checked In or Released SW Part, Copied into\n work directory\n 5 - Use the reload latest function in the DMT;\n> the DMT is up to date\n Mandatory for reproduction: Do SW Save for the Assembly\n (Local Save)\n 6 - Check in or Release the assembly.\n> the Life Cycle window still shows the deleted part and the\n assembly is not updated in SmarTeam", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q246", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Additional Fixes Installed:\n\nV5R19SP4 HF27\n\nEnvironment:\n\nClient OS and level: Windows XP SP2\n\nServer OS and level: Windows Server 2003 SP2\n\nDatabase and level: Oracle 10g2\n Scenario:\n\n1 - Log on to SmarTeam Editor with a user who has full\n authorizations (for example joe);\n\n2 - Checkout an assembly with one part inside of it;\n\n3 - Delete this part form the assembly in SolidWorks;\n\n4 - Add another part (already saved in SmarTeam) in the\n assembly;\n You can use any Checked In or Released SW Part, Copied into\n work directory\n 5 - Use the reload latest function in the DMT;\n> the DMT is up to date\n Mandatory for reproduction: Do SW Save for the Assembly\n (Local Save)\n 6 - Check in or Release the assembly.\n> the Life Cycle window still shows the deleted part and the\n assembly is not updated in SmarTeam", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q246", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "NOTE THAT THIS PROBLEM WILL ALSO BE FIXED ON V5R19 SP7.\n NOTE THAT THIS PROBLEM WILL ALSO BE FIXED ON V5R20 SP1.\n Additional Closure Information:\n N/A\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q246", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n HD92035\nREPORTED COMPONENT NAME\n SMARTEAM NT>XP\nREPORTED COMPONENT ID\n 569199970\nREPORTED RELEASE\n 519\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2009-12-17\nCLOSED DATE\n 2010-04-08\nLAST MODIFIED DATE\n 2010-04-08\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q246", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n SMARTEAM NT>XP\nFIXED COMPONENT ID\n 569199970", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q246", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R519 PSN\n UP", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q246", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How to see the Sterling Connect:Direct File Agent version?", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q246", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "To display the version of Sterling Connect:Direct File Agent, issue a 'cdfa -p' command from a command prompt.\n\n2016-04-19 16:09:56,423 INFO - Connect:Direct File Agent, Version 1.4.0.0_iFix20\n(c) Copyright IBM Corp. 2002, 2014,\nAll rights reserved.\nBuild 0, Date 2015/02/18\n\nThe version shown in this example is 1.4.0.0_iFix20.\n\nSterling Connect:Direct File Agent will also write this version information into the log file at every startup.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q246", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What are some possible causes and resolutions for issues in which a PatternRunTargetException occurs in IBM Rational Integration Tester (RIT) Agent?", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q246", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "When is this issue known to occur?\nThis issue may be seen in the Agent log files when:\nan attempt to publish and launch a stub is made on a Test Engine which is already running that stub,\nand the version numbers of the stub being deployed and the stub currently running are identical.\n\nDoes the software version matter?\n\nYes.\n\nIBM Rational Integration Tester (RIT) 8.6 and IBM Rational Integration Tester Agent (RIT-Agent) 8.6 and IBM Rational Test Control Panel (RTCP) 8.6 always publish at a new version number and so this problem cannot occur for the above reason.\n\nThe preferred solution should ordinarily be to upgrade to version 8.6.\n\nWhat are the typical steps which cause this problem?\n\nThis issue may typically occur when these actions are undertaken (in versions of the software prior to 8.6):\nCreate a project and within it Stub A.\nPublish project at version 1 (i.e. publish Stub A)\nStart Stub A on the Agent\nStop Stub A\n (N.B. Stopping a stub does NOT unload the project from the test engine.)\nCreate Stub B in the same project.\nPublish project at version 1 again (i.e. publish Stub A and Stub B)\nRun Stub B on the Agent\n\nRTCP doesn't send the new project to the test engine the second time the project is published. The then Agent gets told to run Stub B and fails because Stub B does not exist in the version of the project on the Agent.\n\nWhat solutions exist without upgrading?\n\nHere are the alternate solutions available\nAlways publish stubs at a new version number\n or\nStop all stubs before republishing or if this problem occurs. (This forces the shutdown of all test engines which means RTCP has to send them new projects.)\n or\nUnload the project from the agent manually. (See instructions below.)\n\nHow can a project be unloaded from the Agent manually?", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q246", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "To unload a project manually in RTCP: * Go to the Agents and click the Magnifying Glass for the agent running the stub.\nYou will see a finer grained break down of how many instances are running per agents. (Each instance corresponds to an execution of the RunTests binary.)\nWhere an instance shown has the appropriate domain, environment and version deployed, there will be an 'X' symbol.\nClicking the 'X' will cause the running instance of the RunTests binary associated with the display to shutdown. (This will force RTCP to send the updated project to the Agent when the stub is next deployed.)\n\nWhat will the entry in the log file look like?\n\nHere is the text which will be found in the log file if this issue occurs:\ncom.ghc.ghTester.commandline.PatternRunTargetException:\n* no resources were found that matched the pattern:\n* ########:###########:-####\nThe number at the end of the message, hashed above is the UUID of the resource.\n\nWhat else could cause this error?\n\nThe entry in the log file is indicating that there is a resource missing. In these terms each file within a Rational Integration Tester Project is considered to be a resource. Each resource is identified by a UUID.\n\nThe project files are XML files and the UUID of each can be found at XPath location: * /*/@uuid\n\nIf the Rational Integration Tester project is damaged then there may be a resource reference in the project which contains a UUID which is not fulfilled by any resource within the project.\n\nThis can occur, for example, where a project is shared using a version control system, and a new resource is added to a project locally and then a resource containing the reference to the new resource is checked into the version control system, but the resource itself is not added to the version control repository. The problem would then occur when the stub was deployed from a computer other than the one which created the new resource.", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q065", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q065", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Short description:\n RPMPROD6126:'Update Project Health Status'\n I am not able to access \"Update Project Health Status\" from My\n Portal Page. I can see all the options except this one. I can\n access this from the Investment Map when I access it from the\n normal Portfolio Viewer.\n Action Taken:\n I sent the following e-mail to the customer on March 14:\n Hello Preeti,\n Regarding PMR 77370 49R 000 ('Update Proj Health Status' not\n available in My Portal):\n This is a defect. After some research, I have discovered that\n access to the \"Update Project Health Status\" option in the 'My\n Portal' page is controlled by the \"Access Asset Portfolio\n Dashboard\" security option. This is not correct. I have opened a\n defect on the requirements server and notified the Development\n Team.\n As a workaround, in order to make the \"Update Project Health\n Status\" option visible from the 'My Portal' page, please follows\n the steps below:\n 1. Log on as the resource administrator who has access to the\n user's resource record.\n 2. Navigate to the \"Resource Management\" view and locate the\n resource record.\n 3. Double-click on the resource record to open its \"Description\n View\".\n 4. Check out the resource record.\n 5. Maximize the \"System Security Rights\" portlet.\n 6. Expand the \"Asset Management\" node.\n 7. Put a check mark in the box next to the \"Access Asset\n Portfolio Dashboard\" security option.\n 8. Check in the resource record.\n 9. Log on as this resource.\n 10. Confirm that the user now has the \"Update Project Health\n Status\" option in the 'My Portal' page.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q065", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "No option to update Project health in My Portal Page", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q065", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fixed in 7.1.0.0\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q065", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PK22421\nREPORTED COMPONENT NAME\n RATL PORT MGR V\nREPORTED COMPONENT ID\n 5724J4001\nREPORTED RELEASE\n 610\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2006-03-29\nCLOSED DATE\n 2007-06-28\nLAST MODIFIED DATE\n 2007-06-28\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q065", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n RATL PORT MGR V\nFIXED COMPONENT ID\n 5724J4001", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q065", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R610 PSN\n UP", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q065", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do I change the width of the left column on my Maximo Start Center (Go To Applications)?", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q065", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "The width of the column that contains the \"Go To Applications\" on the Start Center in Maximo 7.6 is determined by a value in the\n\nLibrary.xml file. By default the column width is longer than any of the standard application names and looks like this:\n\n[/support/docview.wss?uid=swg22012791&aid=1] [/support/docview.wss?uid=swg22012791&aid=1]\n\nSome clients would like the left column to be narrower and look more like this:\n\n[/support/docview.wss?uid=swg22012791&aid=2] [/support/docview.wss?uid=swg22012791&aid=2]\n\nYou can modify the width of the left hand column by modifying a value in your Library.xml file. Please try the following on\na test environment to change the width of your left column on the Start Center.\n\nFirst in Application Designer, click on Select Action / Export System XML and then select the Library xml.\n\nAfter the Library xml opens in a browser,save the page to your\nhard drive as LIBRARY.xml. Then make a backup of the LIBRARY.xml in case you need to restore the original version.\n\nThen open LIBRARY.xml in a text editor such as Wordpad or Notepad and look for the following code:\n\n
\n\n\n\n\nThen change the width value from 190 to a smaller value such as 100 and save your file. You will end up with the code below. You may have to\nexperiment with the exact width you would like but the process is the same.\n\n
\n\n\n\n\nAfter saving your changes go back into Application Designer and click on \"Import Application Definition\" and browse for your modified LIBRARY.xml\nfile and import your changed file. Then logout and back in and see if the left column is now at the desired width like the one shown above.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q065", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do I troubleshoot potential database-related problems or enable verbose logging for SQL queries for IBM Collaborative Lifecycle Management (CLM)?", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q065", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "There are a few different ways to approach database performance from the application perspective. The methods that are described are most useful when an application administrator does not have direct access to vendor utilities that can perform similar, if not more verbose, database analysis. Note these are not direct replacements for things like Oracle's Automated Workload Repository (AWR) but can certainly help narrow in on database-related problems so that you can provide your DBA with database metrics from the applications perspective, if not resolve the problem on your own.\n\n1. Database diagnostics\n\nThere are three database diagnostics available from the applications /admin -> Diagnostics page. Verify that these diagnostics are all green after running all diagnostics. * Database Performance - This diagnostic performs queries against the database for 60 seconds to ensure that the performance is within the expected limits. If needed, export the diagnostics by using the Export Results button on the diagnostics page and look at the file that is called com.ibm.team.repository.service.diagnostics.database.internal.databaseStatisticsDiagnostic.html contained within the Diagnostics.zip file.\u02d8 Database - Reports the database and JDBC versions along with a performance measurement. If the performance measurement is exceeds 2500 ms, an error is reported and the network latency between the application server and database should be investigated. Also, consider performing a health check on the database by using the vendor-specific DMBS tools available. Consult a DBA if needed. Database Indices - Ensures that the out-of-the-box database indices are in place on the database. If indices are missing, you can run repotools- -rebuildIndices [https://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.4/com.ibm.jazz.install.doc/topics/r_repotools_rebuildindices.html] to re-create them. This is a fairly quick operation (usually under 10 minutes), not to be confused with repotools -reindex all which is a much more time consuming task that can take hours or possibly days to complete.\n\n2. Performance widget - Provides a high-level performance overview from an applications dashboard. See the Performance Health Check [https://jazz.net/blog/index.php/2012/05/15/performance-health-check/]wiki article on jazz.net for more information.\n\n[/support/docview.wss?uid=swg22010123&aid=1] 3. Repodebug \"Querystats\" - Provides statistics on SQL queries run on the database by a given application. Enabling RepoDebug along with a more detailed description of its capabilities is available here [https://jazz.net/wiki/bin/view/Main/RepoDebug]. To access querystats, enable repodebug on the application you are investigating and access https://://repodebug/database/queryStats, or navigate to the /repodebug page and click Database -> Querystats.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q065", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Note: While some features of Repodebug require access control and restarting the server, Querystats can be enabled and run without restarting the server.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q065", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Below are some helpful tips when running and analyzing output from repodebug querystats:\nStart repodebug just before reproducing a performance-related use case and stop it just after the problem has been reproduced. This allows for a more simplified analysis, as leaving querystats that are enabled over a longer period will often skew the results or provide more detail than needed. Keep in mind that there are likely other users in the system doing work, which will also be rolled in to your output. Note that the READ queries are displayed in the top section, the WRITE queries are displayed in the middle, and the OTHER section (ROLLBACK/COMMIT/CONNECT/CLOSE) are shown at the bottom of the output. Make sure to review all sections when analyzing the output. Do not be alarmed when you see multiple ROLLBACKs in the OTHER section, as ROLLBACK is just how the application terminates read queries. Ensure the average time of the ROLLBACKs is in the low/single digit ms range (ideally closer to zero ms). The numbers that are shown are in milliseconds and are a true measurement of how long a query took to run on the database side (does not account for latency between the application server and the database server). When looking at output from repodebug, pay special attention to the number, totalTime and avgTime columns. The queries are sorted by totalTime, which means the query that ran the longest, whether it is one or many executions, are shown at the top of the output for each section. Sometimes it might be necessary to determine what code was responsible for running a given query. This can be accomplished by clicking on the hash value of a query in the output and selecting ENABLESTACKS. Once stacks have been enabled, the associated stack trace is shown in the statistics for the query when clicking the hash value again, or by refreshing the page if you are already in the statistics for a given query that has stacks enabled. You will notice that the parameters of queries are not printed in the output from querystats. If it is necessary to see queries containing parameters, use vendor-specific database tracing tools or enable the logging that is described below. For example, if a query shows SELECT * FROM VVCMODEL.VERSION WHERE URL IN (?, ?, ?) and you need to know the value of the ?'s, use the logging below. This is helpful to capture in the event you want to generate an EXPLAIN plan on the query.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q065", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "4. Verbose SQL logging - Enable this for a given application when you want to see all SQL queries in the application log file. This can be done either in the applications log4j.properties file, or by using repodebug. There are two loggers available:\n\nlog4j.logger.sqlTxLogger - Will output all SQL to the application log file\nlog4j.logger.com.ibm.team.repository.service.internal.ExecuteDataQuery - To be used with sqlTxLogger, will print the parameters from the SQL statements.\nTo enable using repodebug\n*\n* https://clmweb.ibm.com/rm/repodebug [https://clmweb.ibm.com/rm/repodebug]\n*\n* sqlTxLogger\n*\n*\nEdit Level\n* DEBUG\n* submit.\n* com.ibm.team.repository.service.internal.ExecuteDataQuery\n*\n* To enable using log4j\n*\n*\n*\n* log4j.logger.sqlTxLogger\n=DEBUG\n* log4j.logger.com.ibm.team.repository.service.internal.ExecuteDataQuery\n=DEBUG (\nNote\n* )\n*\n* Reload Log Settings option\n* Reload Log Settings\n*\n5. Mbeans - For 6.0.3 and higher, an Mbean exists that will allow you to consume a wide variety of metrics from the server, one of them being an SQL activity metric, which will display the top 25 slowest SQL queries. An extensive article on mbeans is forthcoming on jazz.net, however if you are already familiar with consuming Mbeans, you can enable com.ibm.team.repository.service.internal.serviceability.SQLActivityMetricsTask from the applications /admin -> Advanced Properties page by setting Enable SQL Activity Metrics MBean to True. Mbeans can be consumed by a java client or performance monitoring tool, but can also visualized from repodebug using /repodebug -> mxBeans.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q065", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How to use JNDI clean up Scripts in 7.11?", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q065", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Purpose of using JNDI clean up Scripts MCF v7.11 supports JNDI clean up Script. Higher versions of the Sterling Application do not support this script. The JNDI registry records an entry for each Application server (Weblogic or JBoss) and each Sterling Supply Chain Applications (SSCA) Agent/Integration (A/I) server that starts up. When the SSCA A/I server shuts down, then the Application server removes the corresponding entry from the JNDI registry. However when the SSCA A/I server ends abruptly (or whenever the application server ends), then the corresponding entry remains in the JNDI registry, even though it no longer points to a valid running server. These pointers to servers that are no longer running are known as \"stale entries.\" Stale entries may cause significant slowdown when managing servers through the System Administration Console and when broadcasting cache updates of configuration changes from the Sterling Configurator. To eliminate stale entries from the JNDI tree, the SSCA attempts to remove them during the initialization phase of any server start up. On JBoss, this process can remove active entries as well as stale entries. This behavior may result in conditions ranging from benign (such as the inability to see a server in the System Administration Console) to potentially serious data integrity issues resulting from failed cache updates. SSCA supplies a script that enables to maintain an accurate JNDI registry. This script is extremely lightweight and does not require significant resources or separate sizing estimates. To maintain accurate entries in the JNDI registry and to remove stale entries do the following: 1. Modify the /Applications/Foundation/resources/management.properties file and set the value of the jndi.nocleanup property to \"false\". For example, jndi.nocleanup=false or comment #jndi.nocleanup=true. 2. Ensure that the CLASSPATH environment variable includes the jnpserver.jar and jboss-common.jar files. 3. Schedule and run the /Applications/Foundation/bin/jndicleanup.sh script. The above steps clean up the stale entries in JNDI. As a workaround, one can also run Health Monitor script. This will also clean the JNDI entries.\n\nHISTORICAL NUMBER\n HTG2262\n\nproduct notifications; My notifications; subscribes NEWS", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q065", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This is a My notifications Question and Answer document and step-by-step guide on how to subscribe to valuable product information notifications.", "logical_doc_id": 5, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q065", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Q: Can you explain what My notifications can do for me?\n\nA: My notifications will pro-actively notify you of new and important technical support content regarding the products you purchased and are currently using. Considering recent vulnerabilities that were announced in 2014, it is important for our clients to stay updated on both product-level and industry-specific situations.\n\nQ: How important?\n\nA: Security issues, Critical fix packs, operational warnings, good practices, and troubleshooting tips are some of the document types you can enable for these notifications.\n\nQ: How will I be notified?\n\nA: You can choose by email or RSS, ATOM feeds.\n\nQ: What types of notifications can I receive?\n\nA: You can have emails sent directly to your inbox. You can configure feeds to report the notifications. Or, you can have information listed on the Notifications page by clicking the View link. The notifications you receive are based on the document types you select.\n\nQ: How do I get started?\n\nA: You must have an IBM ID to access My notifications. The ID is free (no charge) and allows you to access these services. If you do not have an IBM ID, you can create one using the IBM Id [https://www-947.ibm.com/account/userservices/jsp/login.jsp?persistPage=true&page=/systems/support/myview/subscription/css.wss/folders%3FmethodName%3DlistMyFolders%26navBar%3D0%26tabInd%3D0&PD-REFERER=none&error=] Registration page. There is a Create id button that will ask you for some information. Once you have an IBM ID, you will be able to log in using that ID to access the My notifications tool.\n\nQ: Once I have an IBM ID, how can I get notified about my products?\n\nA: You can access the My notifications [http://www-01.ibm.com/software/support/einfo.html] tool. Browse for a product or type-in the product name to search for a product. Click the Subscribe button next to the product name. It's that simple.\n\nQ: Once I have found my product(s), how do I create the notification?\n\nA: Click the Subscribe link to the right of the product name. A green checkmark will appear to show you that the subscription is completed. The Edit button allows you to change the types of notifications for the subscription.\n\nQ: What types of notification document types can I enable?\n\nA: Notifications are based on the document types you select. Based on the products you select, the list of document types will change. Document types include:\nSecurity bulletins\nFlashes", "logical_doc_id": 5, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q065", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "News\nDownloads and drivers\nFixes * Recommended\nHigh-Impact / Pervasive (HIPER)\nSecurity Vulnerability (Sec/Int)", "logical_doc_id": 6, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q065", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Troubleshooting * Technotes\nFrequently Asked Questions (FAQs)\nAuthorized Program Analysis reports (APARs)\nFix readmes\nPreventative Service Planning\nProgram Temporary Fixes\nProduct information and publications\nWebcasts\n\nAgain, the list varies by product. You can enable as many document types as you want. You will be notified based on your selections. Q: It seems complicated and I am a new user to IBM. Is there any documentation that can walk me through the sign up process?\n\nA: Yes! We have created a step-by-step tutorial: Stay Informed by Receiving Product and Lifecycle Notifications [http://www.ibm.com/support/docview.wss?uid=swg21674106] to help you enable notifications for each of your products. Once you have enabled the notifications, you will immediately start receiving important information regarding those products!\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Case Manager Enterprise Content Management Case Foundation Enterprise Content Management Atlas Policy Suite Enterprise Content Management Daeja ViewONE Enterprise Content Management Datacap Taskmaster Capture Enterprise Content Management StoredIQ Enterprise Content Management Content Manager Enterprise Content Management Content Manager OnDemand Enterprise Content Management Enterprise Content Management System Monitor Enterprise Content Management FileNet Image Services Enterprise Content Management FileNet P8 Platform Enterprise Content Management FileNet IDM Desktop/WEB Services/Open Client", "logical_doc_id": 7, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q015", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "DFHAP0001 Abend AKEA reported in DFHAPDM", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q015", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Running with CA Technologies ENF active and missing a fix.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q015", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "You receive the following message:\n\nDFHAP0001 [http://publib.boulder.ibm.com/infocenter/cicsts31/index.jsp?I=dfhg4ap] An abend (code ---/AKEA) has occurred at offset x'FFFFFFFF' in module DFHAPDM.\n\nThe ---/AKEA indicates this is a percolate and the original abend happened somewhere prior to this.\n\nFrom reviewing the dump, you see the running task has program checked twice. The first 0C1 is occurring in DFHPASY (base) around offset x'8E', in the middle of the copyright eyecatcher for this module.\n\nThe second program check is an 0C4 abend occurring in DFHPASY (base) + x'4438'. The PSW is pointing to a MVI instruction: 9202 101B and abends because Reg1 is EBCDIC. Reg1 was loaded from Reg3+160 and Reg3 points to the DFHLDLD modhead. However, according to LD=3, the load point for DFHLDLD is 16A1DBE0. In browse you see the following where Reg3 points:\n\nStorage at 16BEA300:\n01406ED4 D6C4C8C5 C1C403D7 80F6F3F0 |. >MODHEAD.P.630|\nC4C6C8D3 C4D3C440 F1F161F1 F361F0F3 |DFHLDLD 11/13/03|\n7CF2F34B F0F70001 96A1DF18 C8C3C9F6 |@23.07..o~..HCI6|\nF3F0F040 1F3001C8 00000002 00001F60 |300 ...H.......-|\n00000300 00000000 90ECD00C BFFFF054 |..........}...0.|\n07FF0000 00C8CB58 96A1DBE0 00000000 |.....H..o~.\\....|\n16BEA360 -16BEA3AF. LENGTH(X'50')--All bytes contain X'00'\n00000000 00000000 01406ED4 D6C4C8C5 |......... >MODHE|\nC1C403C1 80F6F3F0 C4C6C8D7 C1E2E840 |AD.A.630DFHPASY |\nF1F161F1 F461F0F3 7CF0F24B F5F30001 |11/14/03@02.53..|\n00000000 C8C3C9F6 F3F0F040 FFFFFFFF |....HCI6300 ....|\n00000001 00005C48 00008080 00000008 |......*.........|\nC3C9C3E2 40F5F6F9 F760C5F9 F3404DC3 |CICS 5697-E93 (C|\n5D40C3D6 D7E8D9C9 C7C8E340 C9C2D440 |) COPYRIGHT IBM |\nC3D6D9D7 D6D9C1E3 C9D6D56B 40F1F9F7 |CORPORATION, 197|\nF46B40F2 F0F0F36B 40C1D3D3 40D9C9C7 |4, 2003, ALL RIG|\n\nIn the trace you see that CICS has just returned from a DELETE_GATE request issued out of DFHAPSIP (base) at offset x'1914' when DFHLDLD is called to load the base registers. CA-ENF has a hook in this module so they are getting control (instead of the CICS DFHLDLD module) and program checks for some reason.\n\nWhether you request it or not, CA gets hooks in unless you disable this feature by issuing an ENF command. ENF is brought up with MODE(CICS,ON). In order to disable it, issue the operator command: F ENF,MODE(CICS,NONE). Once CA-ENF has been successfully disabled, CICS will come up. Note, this command affects all CICS regions in the LPAR.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q015", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Apply APAR QO49462 for ENF/CICS from [/support/docview.wss?uid=swg21169266&aid=1]CA Technologies [http://www.ca.com/]. This fix is early in the ENF code prior to checking the CICS release. This fix will work for both CICS TS 2.3 and 3.1.\n\nAs a workaround, you can deactivate CA90 (ENF) by issuing 'F ENF,MODE(CICS,NONE)' to eliminate ENF from the CICS regions in the LPAR. The CICS TS region should then come up. Note, this command will affect all CICS regions in the LPAR, so ENF will be removed from all regions, which might not be what you want.\n\nPRODUCT ALIAS/SYNONYM\n CICS TS CICS/TS CICS Transaction Server", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q015", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "DFHAP0001 An abend (code 0C4/AKEA) has occurred at offset X'00002200' in module DBUGDBXX.\n\nThe symptoms of the problem are similar to the one described in APAR OA42454 [http://www-01.ibm.com/support/docview.wss?uid=swg1OA42454]. However, the problem occurs with or without OMEGAMON active in the region.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q015", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "You are missing a CA-ENF fix. Your current level of CA-ENF is making a similar mistake that the pre OA42454 version of OMEGAMON made. This causes the problem when CA-ENF intercepts control.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q015", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "From the dump, the 0C4 is at offset x'00002200' in program DBUGDBXX. The failing instruction is BF6F 2074 and register 2 (R2) has an address that is not valid: 0000000_40C55368. R2 is supposed to address DBUG's CPE at address 00000048_40C55368 (64bit).\n\nPrior to the 0C4, DBUGDBXX loaded R2 with the CPE address 00000048_40C55368 and then issued an EXEC CICS RELEASE command to release program DBUG. On completion of the RELEASE command, DBUGDBXX was attempting to reference CPE field CPE_CURRENT_USERS (R2+74), but the top half of R2 was cleared, causing the 0C4.\n\nIt appears that R2 was updated during the RELEASE command processing.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q015", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Apply CA-ENF fix RO66173. Contact [/support/docview.wss?uid=swg21669828&aid=1]CA Technologies [http://www.ca.com/] if you need further assistance.\n\nPRODUCT ALIAS/SYNONYM\n CICS/TS CICS TS CICS Transaction Server", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q015", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "DFHSO0001 An abend (code 0C4/AKEA) has occurred at offset X'FFFF' in module DFHSOIS", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q015", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "All transactions used by Web Support are not defined within the BSM.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q015", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Add transactions CWBG CSOL and CSOX to the BSM with SEC LEVEL 1.\n\nIn this case, CSOL and CWBG were defined, but CSOX was completely missing in BSM. Adding CSOX with Sec Level 1 to BSM solved the problem.\n\nPRODUCT ALIAS/SYNONYM\n CICS/VSE CICS VSE CICS/TS CICS TS CICS Transaction Server", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q015", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "DFHTD0101I [http://publib.boulder.ibm.com/infocenter/cicsts/v3r2/index.jsp?topic=/com.ibm.cics.ts.messages.doc/cics_mc/dfhtd/TD0101I.html] Transient Data initialization has ended.\nDFHAP0001 [http://publib.boulder.ibm.com/infocenter/cicsts/v3r2/index.jsp?topic=/com.ibm.cics.ts.messages.doc/cics_mc/dfhap/AP0001.html] An abend (code 0C4/AKEA [http://publib.boulder.ibm.com/infocenter/cicsts/v3r2/index.jsp?topic=/com.ibm.cics.ts.messages.doc/cics_mc/AKxx_abend_codes/AKEA.html]) has occurred at offset X'FFFFFFFF' in module DFHRCEX.\nDFHAP0002 [http://publib.boulder.ibm.com/infocenter/cicsts/v3r2/index.jsp?topic=/com.ibm.cics.ts.messages.doc/cics_mc/dfhap/AP0002.html] A severe error (code X'0516') has occurred in module DFHAPAC.\nDFHSI1521 [http://publib.boulder.ibm.com/infocenter/cicsts/v3r2/index.jsp?topic=/com.ibm.cics.ts.messages.doc/cics_mc/dfhsi/SI1521.html] CICS unable to continue for reasons given above.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q015", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "You are running with an old version of the ASG-TMON for CICS TS for z/OS startup program.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q015", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Reviewing the dump taken on the DFHSI152 message, you find that the abend 0C4 actually occurred in TMON module TM8N960 at offset x'3992'. The module header looked like:\n\n| ..>MODHEAD.A.620 |\n| TM8N960 03/29/07 |\n| @11.30..NEO}TH02 |\n| 802 ............ |\n| ...}......}..-1. |\n| ...U...Y.0..TM8N |\n| 960 ........ASM |\n| 03/29/07 11.30 V |\n| ERSION 031 MOD L |\n| EVEL 0000-020 LI |\n| CENSED MATERIALS |\n| COPYRIGHT 1990, |\n| 2006 BY ALLEN S |\n| YSTEMS GROUP, IN |\n| C. TH02802 |", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q015", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Ensure you have the correct version of TMON in the startup PLTPI. You can also remove TMON from the PLTPI until you can find the correct version.\n\nIn this particular case, ASG (TMON) support confirmed the problem was due to having an old version of the TMON startup (PLTPI) program. TM8N680 was being used and caused the error, but TM2N680 should have been used instead.\n\nContact [/support/docview.wss?uid=swg21407141&aid=1]ASG Software Solutions [http://www.asg.com/] if you need further assistance.\n\nPRODUCT ALIAS/SYNONYM\n CICS/TS CICS TS CICS Transaction Server", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q015", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "The startup GRPLIST contains a duplicate definition for program DFHECID with specification EXECKEY(USER).", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q015", "section_id": 1, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "The failure occurs in program DFHEIN01 on the LM instruction (98F0 2030) at offset x'AE2' with an invalid Reg2. DFHEIN01 is the main program within module DFHECID. At the time of the abend 0C4, DFHEIN01 is about to call trace program. The instruction fails because DFHEIN01 is running in USER key instead of CICS key. The PPT entry for DFHECID shows USER (see field PPTE_CICS_EXEC_KEY).\n\nIn the startup GRPLIST, there was a second definition for program DFHECID with EXECKEY specified as USER. The definition for DFHECID is shipped with EXECKEY(CICS).\n\nYou can use the CEDA transaction to display any groups that contain definitions for DFHECID with the following command:\n\nCEDA EXP G(*) PROG(DFHECID)", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q015", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Ensure that your program definition for DFHECID specifies EXECKEY(CICS).\n\nPRODUCT ALIAS/SYNONYM\n CICS/TS CICS TS CICS Transaction Server", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q126", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "SSL configuration problem.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q126", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Once the client-server connection is setup to work without SSL, perform the following steps to make it SSL enabled.\n\nOn the server, using IBM Key Management utility:\n\n1. Create a key database say key.kdb (if not already existing) under \\WebSphere MQ\\qmgrs\\qmgrname\\ssl by choosing the key database type as CMS.\n 2. Enter and confirm password and opt to stash the password to a file.\n 3. Create a new self signed certificate. Ensure that the Key Label exactly as follows: ibmwebspheremqxx for a queue manager (where xx is the qmgr name folded to lower case).\n 4. Extract the self signed certificate, cert.arm to a local folder.\n 5. Copy cert.arm to client machine to a temporary directory.\n 6. Alter the svrconn and clntconn channel definitions to add the SSL Cipherspec (example: NULL_MD5) and copy the client channel table file AMQCLCHL.TAB to the client machine.\n\nOn Client Side, using IBM Key Management utility:\n\n1. Create a key database(kdb) file as mentioned above and stash the password.\n 2. Select signer certificate from the Key database content drop down and use Add to add the .arm file copied from the server machine. Use the same label as used on the server side.\n 3. Set the MQCHLLIB and MQCHLTAB environment variables appropriately and unset MQSERVER if it exists.\n 4. Set MQSSLKEYR to point to the directory where the key database resides.\n\nAdditional information\n\nFDC:\n\nDate/Time :- Tue June 21 11:12:30 Eastern Standard Time 2005\nHost Name :- DOSxxxIN6XP (Windows XP Build 2600: Service Pack\nPIDS :- 5724H7200\nLVLS :- 6.0.0.0\nProduct Long Name :- WebSphere MQ for Windows\nVendor :- IBM\nProbe Id :- JC062003\nApplication Name :- MQM\nComponent :- NativeCalls.getCommandServesStatus\nSCCS Info :- eclipse/common/amqjxtra.c, 1.13\nLine Number :- 609\nBuild Date :- May 19 2005\nCMVC level :- p000-L050519\nBuild Type :- IKAP - (Production)\nUserID :- cdoconn\nProcess Name :- C:\\IBM\\Eclipse SDK30\\eclipse\\jre\\bin\\javaw.exe\nProcess :- 00001772\nThread :- 00000001\nMajor Errorcode :- OK\nMinor Errorcode :- OK\nProbe Type :- INCORROUT\nProbe Severity :- 4\nProbe Description :- AMQ6125: An internal WebSphere MQ error has occur\nFDCSequenceNumber :- 0\nComment1 :-\ncom/ibm/mq/commonservices/internal/utils/NativeCalls.wmq_native\n\nHISTORICAL NUMBER\n66509 442\n\nPRODUCT ALIAS/SYNONYM\nWebSphere MQ WMQ MQSeries\n\nz/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q126", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The customer defined a channel with SSL and they are using\n SSLPEER.\n They receive the following message:\n CSQX636E distinguished name does not match peername.\n For V6, the following fails C=US or C=U* both fail.\n What is happening is that CSQXCCIS routines cciSslFindDNAttr\n and cciSslCompareDNAttr are doing a strstr find for \"C=\"\n and they find the \"C=07310\" in CERTN and C=US in SSLPEER which\n do not match.\n Additional symptom:\n CSQX636E is also issued when L= attribute doesn't match.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q126", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of WebSphere MQ for z/OS V6 *\n\nPROBLEM DESCRIPTION: Failure to match information in SSLPEER *\nfield on a channel definition with the *\ninformation in the distinguished name *\nfrom the certificate in some cases. *\nChannel fails to start,CSQX636E message *\nissued. *\n\nRECOMMENDATION: *\n\nWhen matching SSLPEER information with information passed\n in a certificates distinguished name, an error can occur\n if you have specified PC= and C= in your certificate\n distinguished name field and C= in your SSLPEER.\n The channel fails to start resulting in a CSQX636E message\n distinguished name does not match peer name.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q126", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This problem occured in V6 and not previous releases as the way\n the SSL distinguised name information was obtained and\n processed changed in V6. In previous release we only obtained\n and processed fields we were interested in. In V6 we obtained\n the whole DN from System SSL and processed it, but the\n processing didn't allow for some of the extra information in\n the DN partially matching what we were trying to match against.\n For example PC=xxxx matching against C=abcd , it matched the\n 'C=' part and then said xxxx doesn't match abcd therefore\n this is and error. This caused the channel to fail to start.\n The code was changed to perform a more thorough check of the\n strings we are trying to match, and to skip over those that\n we are not interested in.\n 000Y\n CSQXCCIS\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q126", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PK29806\nREPORTED COMPONENT NAME\n WMQ Z/OS V6\nREPORTED COMPONENT ID\n 5655L8200\nREPORTED RELEASE\n 000\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2006-08-11\nCLOSED DATE\n 2006-12-04\nLAST MODIFIED DATE\n 2007-02-02\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n UK20232\n\nMODULES/MACROS\nCSQXCCIS", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q126", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ Z/OS V6\nFIXED COMPONENT ID\n 5655L8200", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q126", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R000 PSY UK20232 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK20232]\n UP07/01/04 P F701\n\nFIX IS AVAILABLE\nSELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL. YOU WILL BE REQUIRED TO SIGN IN. DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES.\n\nA FIX IS AVAILABLE\nWebSphere MQ for HP NonStop Server V5.3.1 fix pack 5.3.1.9 [http://www-01.ibm.com/support/docview.wss?uid=swg24033520]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q126", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Using slashes in the Distinguished Name name fields such as CN,\n O, OU, L, will fail SSLPEER value verification, and as such SSL\n Handshake, due to an MQ parsing error. MQ uses slashes (/) to\n delimit the distinguished name values when matching the SSLPEER\n value with the information contained in the certificate.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q126", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "The only workaround is to generate certificates with\n Distinguished Name values that do not contain a slash.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q126", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "CERTIFICATES CONTAINING SLASHES IN THE\n DISTINGUISHED NAME (DN) FIELDS FAIL WEBSPHERE\n MQ VERIFICATION, THEREFORE SSL HANDSHAKE.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q126", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Using slashes in the Distinguished Name name\n fields such as CN, O, OU, L, will fail\n SSLPEER value verification, and as such SSL\n Handshake, due to an MQ parsing error. WMQ\n uses slashes (/) to delimit the\n distinguished name values when matching the\n SSLPEER value with the information contained\n in the certificate.\n\nTEMPORARY FIX\nThe only workaround is to generate certificates\n with\n Distinguished Name values that do not contain a\n slash.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q126", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC74903\nREPORTED COMPONENT NAME\n WEBS MQ NSS ITA\nREPORTED COMPONENT ID\n 5724A3902\nREPORTED RELEASE\n 531\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2011-03-09\nCLOSED DATE\n 2011-03-29\nLAST MODIFIED DATE\n 2011-03-29\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q126", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBS MQ NSS ITA\nFIXED COMPONENT ID\n 5724A3902", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q126", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R530 PSY\n UP\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q126", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "A WebSphere MQ classes for Java Message Service (JMS) or\n WebSphere MQ classes for Java client application using WebSphere\n MQ Version 7.0.1.11 jar files, tries to make a connection to a\n queue manager secured with SSL/TLS. This fails with a\n JMSException, with reason code MQRC_SSL_PEER_NAME_ERROR.\n The exception is similar to:\n .\n com.ibm.mq.jmqi.JmqiException: CC=2;RC=2399;AMQ9640: SSL invalid\n peer name, channel '?', attribute 'DC (x2)'. [5=DC (x2)]\n .\n The same application works fine when using the WebSphere MQ\n Version 7.0.1.10 jar files.\n .\n Below is an extract of a JMS trace showing the error:\n\n @1a2f02e c.i.m.j.r.internal.system.RemotePeerName(RemotePeerNam\n e) ----+----+--- X parseDN(String)\n CC=2;RC=2399;AMQ9640: SSL invalid peer name, channel '?', attrib\n ute 'DC (x2)'. [5=DC (x2)] [com.ibm.mq.jmqi.JmqiException] at:\n com.ibm.mq.jmqi.remote.internal.system.RemotePeerName.setValue\n (RemotePeerName.java:387)\n com.ibm.mq.jmqi.remote.internal.system.RemotePeerName.parseDN(\n RemotePeerName.java:205)\n com.ibm.mq.jmqi.remote.internal.system.RemotePeerName.(R\n emotePeerName.java:93)\n com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection.protocolCo\n nnect(RemoteTCPConnection.java:1105)\n com.ibm.mq.jmqi.remote.internal.system.RemoteConnection.connec\n t(RemoteConnection.java:1283)\n com.ibm.mq.jmqi.remote.internal.system.RemoteConnectionPool.ge\n tConnection(RemoteConnectionPool.java:355)\n com.ibm.mq.jmqi.remote.internal.RemoteFAP.jmqiConnect(RemoteFA\n P.java:1716)\n com.ibm.mq.jmqi.remote.internal.RemoteFAP.jmqiConnect(RemoteFA\n P.java:1305)\n com.ibm.msg.client.wmq.internal.WMQSession.connect(WMQSession.\n java:372)\n com.ibm.msg.client.wmq.internal.WMQSession.(WMQSession.j\n ava:316)\n com.ibm.msg.client.wmq.internal.WMQConnection.createSession(WM\n QConnection.java:980)\n com.ibm.msg.client.jms.internal.JmsConnectionImpl.createSessio\n n(JmsConnectionImpl.java:573)\n com.ibm.mq.jms.MQConnection.createSession(MQConnection.java:33\n 9)\n Jms11Sample.run(Jms11Sample.java:49)\n Object ClassLoader = sun.misc.Launcher$AppClassLoader@1ea2dfe\n CurrentThread ClassLoader = sun.misc.Launcher$AppClassLoader@1\n ea2dfe\n\n .", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q126", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n This issue affects users of the WebSphere MQ Classes for JMS\n V7.0.1 who are attempting an SSL Connection to a Queue Manager\n\nPlatforms affected:\n MultiPlatform\n\nPROBLEM SUMMARY:\n A WebSphere MQ Classes for JMS application established an SSL\n connection to a Queue Manager. The application then attempted to\n create a JMS Session from the connection, on the JMS Session\n connect the SSLPEERNAME property was erroneously set on the\n client side from the distinguished name of the certificate. This\n resulted in the MQRC_SSL_PEER_NAME_ERROR error being returned to\n the application.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q126", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The WebSphere MQ Classes for JMS have been altered to not set\n the SSLPEERNAME property from the distinguished name of the\n certificate when attempting the JMS Session connect.\n\nThe fix is targeted for delivery in the following PTFs:\n\nVersion Maintenance Level\n v7.0 7.0.1.13\n\nThe latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\nIf the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q126", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV53739\nREPORTED COMPONENT NAME\n WMQ SOL SPARC\nREPORTED COMPONENT ID\n 5724H7223\nREPORTED RELEASE\n 701\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-01-08\nCLOSED DATE\n 2014-01-31\nLAST MODIFIED DATE\n 2014-01-31\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q126", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ SOL SPARC\nFIXED COMPONENT ID\n 5724H7223", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q126", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R701 PSY\n UP\n\nAIX FIXES ARE AVAILABLE\nWebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 12 (CSD12) [http://www-01.ibm.com/support/docview.wss?uid=swg24011423]\nWebSphere MQ V5.3 & WebSphere MQ Express V5.3 - Fix Pack 10 (CSD10) [http://www-01.ibm.com/support/docview.wss?uid=swg24009688]\nWebSphere MQ V5.3 & WebSphere MQ Express V5.3 - Fix Pack 8 (CSD08) [http://www-01.ibm.com/support/docview.wss?uid=swg24007905]\nWebSphere MQ V5.3 for iSeries - Fix Pack 12 (CSD12) [http://www-01.ibm.com/support/docview.wss?uid=swg24011422]\nWebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 13 (CSD13) [http://www-01.ibm.com/support/docview.wss?uid=swg24014128]\nWebSphere MQ V5.3 and WebSphere MQ Express V5.3 - Fix Pack 14 (CSD14) [http://www-01.ibm.com/support/docview.wss?uid=swg24017668]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q126", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "We have identified a discrepancy regarding the storing of\n the repository information in its cache. The stored\n information may contain a stale pointer to the SSLPeerName,\n and this is something we need to fix. It is, however, not\n clear why this would give rise to a SEGV when the SSLPeerName\n is copied, since we would expect that even if the pointer is\n stale, it is still a valid memory address for the purpose of\n copying. But this is a complicated area.", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q126", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n Users of SSL with WMQ clustering.\n\nPROBLEM SUMMARY:\n Code path existed that could result in non-refreshing of cache\n information which holds a pointer to the SSL peer name.", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q126", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Ensured the SSL peer name cache pointer is maintained correctly.\n\nThe fix will be included in the following PTFs:\n WebSphere MQ v5.3 CSD09\n Windows U200223\n AIX U498401\n HP-UX U498684\n Linux on Intel U498687\n Linux on zSeries U498689\n Sun Solaris U498686\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q126", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IY58921\nREPORTED COMPONENT NAME\n WEB MQ FOR AIX\nREPORTED COMPONENT ID\n 5724B4101\nREPORTED RELEASE\n 530\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2004-07-14\nCLOSED DATE\n 2004-07-27\nLAST MODIFIED DATE\n 2004-07-27\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q126", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R530 PSY\n UP", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q182", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Multiple security vulnerabilities exist in the IBM\u00ae Runtime Environment Java\u2122 Technology Edition 6.0.16.26 (and earlier) used by WebSphere Message Broker, and the IBM\u00ae Runtime Environment Java\u2122 Technology Edition 7.0.9.40 (and earlier) used by WebSphere Message Broker and IBM Integration Bus, and the IBM\u00ae Runtime Environment Java\u2122 Technology Edition 7.1.3.40 (and earlier) used by IBM Integration Bus. These issues were disclosed as part of the IBM Java SDK updates in July 2016.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q182", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-3485 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3485]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE and Java SE Embedded related to the Networking component has no confidentiality impact, low integrity impact, and no availability impact.\nCVSS Base Score: 2.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/115273 [https://exchange.xforce.ibmcloud.com/vulnerabilities/115273] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q182", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Integration Bus V10, V9\n\nWebSphere Message Broker V8", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q182", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Product VRMF APAR Remediation/Fix IBM Integration Bus V10 IT16743 The APAR is available in fix pack 10.0.0.7\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24043068 [https://www-304.ibm.com/support/docview.wss?uid=swg24043068] IBM Integration Bus V9 IT16743 The APAR is available in fix pack 9.0.0.7\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043227 [http://www-01.ibm.com/support/docview.wss?uid=swg24043227] WebSphere Message Broker V8 IT16743 An interim fix is available from IBM Fix Central for all platforms\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT16743 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=%20IT16743]\n\nIf you are running with a fix pack earlier than 8.0.0.7 and do not have IT03599 applied then you must upgrade your fix pack level to 8.0.0.7 or higher, or request IT16735 via IBM support.\n\nAPAR IT16743 is targeted to be available in fix pack 8.0.0.9\nFor unsupported versions of the product IBM recommends upgrading to a fixed, supported version/release/platform of the product.\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at :\nhttp://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308]", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q182", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q182", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]\nIBM Java SDK Security Bulletin [http://www.ibm.com/support/docview.wss?uid=swg21986642]", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q182", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 30 Mar 2017 - Original version Published\nThe 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.", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q182", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "#\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker 8.0\nPRODUCT ALIAS/SYNONYM\n WMB IIB", "logical_doc_id": 0, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q182", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabiltities in the IBM\u00ae SDK Java\u2122 Technology Edition that is shipped with IBM WebSphere Application Server. These issues were disclosed as part of the IBM Java SDK updates in July 2017. These may affect some configurations of IBM WebSphere Application Server Traditional, IBM WebSphere Application Server Liberty and IBM WebSphere Application Server Hypervisor Edition.", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q182", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "If you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities please refer to the link for \u201cIBM Java SDK Security Bulletin\" located in the References section for more information.\nHP fixes are on a delayed schedule.\nCVEID:CVE-2017-10116 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10116]\nDESCRIPTION:An unspecified vulnerability related to the Java SE, Java SE Embedded, JRockit Security component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/128877 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128877]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H)\n\nCVEID:CVE-2017-10115 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10115]\nDESCRIPTION:An unspecified vulnerability related to the Java SE, Java SE Embedded, JRockit JCE component could allow an unauthenticated attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/128876 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128876]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q182", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "This vulnerability affects all versions of Liberty for Java in IBM Bluemix up to and including v3.11.", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q182", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "To upgrade to Liberty for Java v3.12-20170814-1322 [https://cf-jenkins.rtp.raleigh.ibm.com/files/OERuntimeMileStone/LibertyBuildpack/v3.9/20170419-1403/bluemix_files/] or higher, you must re-stage or re-push your application.\n\nTo find the current version of Liberty for Java in IBM Bluemix being used, from the command-line Cloud Foundry client by running the following commands:\n\ncf ssh -c cat \"staging_info.yml\"\n\nLook for the following lines:\n\n{\"detected_buildpack\":\"Liberty for Java(TM) (WAR, liberty-17.0.0_2, buildpack-v3.12-20170814-1322, ibmjdk-1.8.0_20170727, env)\",\"start_command\":\".liberty/initial_startup.rb\"}\n\nTo re-stage your application using the command-line Cloud Foundry client, use the following command:\n\ncf restage \n\nTo re-push your application using the command-line Cloud Foundry client, use the following command:\n\ncf push ", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q182", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q182", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]\nIBM Java SDK Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg22006695]\nIBM Java SDK Version 8 bundled with WebSphere Application Server [https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/covr_javase6_eos.html]\nIBM Java SDKs for WebSphere Liberty [http://www-01.ibm.com/support/docview.wss?uid=swg27049903]\nIBM SDK Java Technology Edition Version 8.0 for WebSphere Liberty using archives [http://www-01.ibm.com/support/docview.wss?uid=swg24043502]", "logical_doc_id": 1, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q182", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 18 August 2017: original document published\nThe 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\nIIB; WMB SECURITY BULLETIN", "logical_doc_id": 1, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q182", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition, Version 7.1.4.10 and IBM\u00ae Runtime Environment Java\u2122 Versions 7.0.10.10 and 7.1.4.10 used by IBM Integration Bus and WebSphere Message Broker. These issues were disclosed as part of the IBM Java SDK updates in Jul 2017.", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q182", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "If you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities please refer to the link for \u201cIBM Java SDK Security Bulletin\" located in the \u201cReferences\u201d section for more information.\n\nCVEID:CVE-2017-10115 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10115]\nDESCRIPTION:An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit JCE component could allow an unauthenticated attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/128876 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128876]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)\n\nCVEID:CVE-2017-10116 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10116]\nDESCRIPTION:An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit Security component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/128877 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128877]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H)\n\nCVEID:CVE-2017-10108 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10108]\nDESCRIPTION:An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit Serialization component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.\nCVSS Base Score: 5.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/128869 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128869]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)\n\nCVEID:CVE-2017-10109 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10109]\nDESCRIPTION:An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit Serialization component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.\nCVSS Base Score: 5.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/128870 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128870]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q182", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Integration Bus V9.0.0.0 - V9.0.0.8 and V10.0.0.0 - V10.0.0.9\n\nWebSphere Message Broker V8.0.0.0 - V8.0.0.9\nWebSphere Message Broker V7.0.0.0 - V7.0.0.8", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q182", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Product VRMF APAR Remediation / Fix IBM Integration Bus V10.0.0.0 - V10.0.0.9 IT21764 The APAR is available in fix pack 10.0.0.10 [http://www-01.ibm.com/support/docview.wss?uid=swg24043943]\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043943 [http://www-01.ibm.com/support/docview.wss?uid=swg24043943] IBM Integration Bus V9.0.0.0 - V9.0.0.8 IT21764 The APAR is available in fix pack 9.0.0.9\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043947 [http://www-01.ibm.com/support/docview.wss?uid=swg24043947] WebSphere Message Broker V8.0.0.0 - V8.0.0.9 IT21764 Contact IBM support to request a fix for APAR IT21764 WebSphere Message Broker V7.0.0.0 - V7.0.0.8 IT21764 Contact IBM support to request a fix for APAR IT21764\n\nWebsphere Message Broker V7 and V8 are no longer in full support; IBM recommends upgrading to a fixed, supported version/release/platform of the product.\n\nIf you are a customer with extended support and require a fix, contact IBM support.", "logical_doc_id": 2, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q182", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 2, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q182", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]\nIBM Java SDK Security Bulletin [http://www.ibm.com/support/docview.wss?uid=swg22006695]", "logical_doc_id": 2, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q182", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 15th November 2017 : Original version published\nThe 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.", "logical_doc_id": 2, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q182", "section_id": 8, "heading": "RELATED INFORMATION", "parent": null, "text": "#\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker AIX, HP-UX, Linux, Solaris, Windows 7.0, 8.0\nPRODUCT ALIAS/SYNONYM\n IIB\nWMB\n\nTROUBLESHOOTING\n\nPROBLEM\nIBM Planning Analytics and Cognos TM1 Security Bulletins and Alerts.", "logical_doc_id": 2, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q182", "section_id": 9, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "TAB NAVIGATION\nPA 2.0.x\nTM1 10.2.x\nInsight 10.2.x\nConcert 4.0.2", "logical_doc_id": 2, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q182", "section_id": 9, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Security bulletins and Alerts for IBM Planning Analytics 2.0.x. Published / Updated Title July 2018 Security Bulletin: Multiple vulnerabilities exist in IBM Planning Analytics Local [http://www.ibm.com/support/docview.wss?uid=swg22016372] February 2018 Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IBM Planning Analytics [http://www.ibm.com/support/docview.wss?uid=swg22007463] October 2017 Inconsistent results when using Refresh Workbook vs. Refresh Page [http://www.ibm.com/support/docview.wss?uid=swg22009899] October 2017 Security Bulletin: Multiple Security Vulnerabilities exist in IBM Planning Analytics Express and IBM Cognos Express [http://www.ibm.com/support/docview.wss?uid=swg22009518] September 2017 Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IBM Planning Analytics Local [http://www.ibm.com/support/docview.wss?uid=swg22008584] Security bulletins and Alerts for Cognos TM1 10.2 and 10.2.2. Published / Updated Title July 2018 Multiple Security Vulnerabilities exist in IBM Cognos TM1 [http://www.ibm.com/support/docview.wss?uid=ibm10716285] April 2018 A vulnerability in IBM Java Runtime affects IBM Cognos TM1 [http://www.ibm.com/support/docview.wss?uid=swg22015269] October 2017 Database structure change affects Cognos TM1 and Planning Analytics [http://www.ibm.com/support/docview.wss?uid=swg22008561] September 2017 Cognos TM1 \u53ca\u3073 Planning Analytics\u306b\u65bc\u3051\u308b\u30c7\u30fc\u30bf\u30d9\u30fc\u30b9\u69cb\u9020\u306e\u5909\u66f4 [http://www.ibm.com/support/docview.wss?uid=swg22008727] November 2016 URGENT Message to all on premises Cognos TM1 and Cognos Express Customers: You must refresh your SSL Certificate or your TM1 System will Stop Working on November 25, 2016 [http://www.ibm.com/support/docview.wss?uid=swg21990869] May 2015 Updated: Cognos TM1 10.2.2 FP3 Interim Fix 1 [http://www.ibm.com/support/docview.wss?uid=swg21903242] February 2014 Cognos TM1 10.2 - TM1 Web input issues with non-US numeric values and copy/paste from external sources [http://www.ibm.com/support/docview.wss?uid=swg21664460] February 2014 Cognos TM1 10.2 Multi-threaded Query calculation fix [http://www.ibm.com/support/docview.wss?uid=swg21664467] Security bulletins for Cognos Insight 10.2, 10.2.1 and 10.2.2.", "logical_doc_id": 2, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q182", "section_id": 9, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Published / Updated Title July 2018 Multiple Security Vulnerabilities exist in IBM Cognos Insight [http://www.ibm.com/support/docview.wss?uid=ibm10716289] April 2018 A vulnerability in IBM Java Runtime affects IBM Cognos Insight [http://www.ibm.com/support/docview.wss?uid=swg22015268] January 2018 Multiple vulnerabilities in IBM Java Runtime affect IBM Cognos Insight [http://www-01.ibm.com/support/docview.wss?uid=swg22012627] April 2017 Multiple Security Vulnerabilities exist in IBM Cognos Insight [http://www-01.ibm.com/support/docview.wss?uid=swg21999652] February 2017 Multiple Security Vulnerabilities affect IBM Cognos Insight [http://www-01.ibm.com/support/docview.wss?uid=swg21966780] July 2016 Multiple Security Vulnerabilities exist in IBM Cognos Insight [http://www-01.ibm.com/support/docview.wss?uid=swg21987175] May 2016 Multiple Security Vulnerabilities exist in IBM Cognos Insight [http://www-01.ibm.com/support/docview.wss?uid=swg21979761] May 2015 Vulnerability in RC4 stream cipher affects IBM Cognos Insight (CVE-2015-2808) [http://www-01.ibm.com/support/docview.wss?uid=swg21902669] May 2015 Multiple vulnerabilities in IBM Java Runtime affect Cognos Insight (CVE-2015-0410, CVE-2014-3566, CVE-2014-6593) [http://www-01.ibm.com/support/docview.wss?uid=swg21902637] May 2015 Vulnerabilities in OpenSSL affect Cognos Insight (CVE-2015-0204) [http://www-01.ibm.com/support/docview.wss?uid=swg21902635] March 2015 Multiple vulnerabilities in OpenSSL affect IBM Cognos Insight (CVE-2014-3567, CVE-2014-3513, CVE-2014-3568) [http://www-01.ibm.com/support/docview.wss?uid=swg21697995] September 2014 Cognos Insight is affected by the following OpenSSL vulnerabilities: CVE-2014-0224 [http://www-01.ibm.com/support/docview.wss?uid=swg21682840] Security bulletins and Alerts for IBM Concert on Cloud 4.0.2. Published / Updated Title July 2014 Security Bulletin: Security exposure in IBM Concert (CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-0198, CVE-2010-5298, CVE-2014-3470) [http://www-01.ibm.com/support/docview.wss?uid=swg21678893] -->\nCross reference information Product Component Platform Version Edition Cognos TM1 10.2, 10.2.2 IBM Planning Analytics Advanced 2.0.4, 2.0.3, 2.0.2, 2.0.1, 2.0 IBM Planning Analytics Express 2.0.4, 2.0.3, 2.0.2, 2.0.1, 2.0 IBM Planning Analytics Local 2.0.4, 2.0.3, 2.0.2, 2.0.1, 2.0 IBM Concert on Cloud 4.0.2 Cognos Insight 10.2.2, 10.2.1, 10.2", "logical_doc_id": 2, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q182", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition, Version 6 and IBM\u00ae Runtime Environment Java\u2122 Version 6 used by IBM Web Experience Factory. These issues were disclosed as part of the IBM Java SDK updates in Jul 2017.", "logical_doc_id": 3, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q182", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "If you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities please refer to the link for \u201cIBM Java SDK Security Bulletin\" located in the \u201cReferences\u201d section for more information.\n\nCVEID: CVE-2017-10116 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10116]\nDESCRIPTION: An unspecified vulnerability related to the Java SE Security component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/128877 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128877] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H)\n\nCVEID: CVE-2017-10115 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10115]\nDESCRIPTION: An unspecified vulnerability related to the Java SE JCE component could allow an unauthenticated attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/128876 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128876] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)\n\nCVEID: CVE-2017-10067 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10067]\nDESCRIPTION: An unspecified vulnerability related to the Java SE Security component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/128831 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128831] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H)\n\nCVEID: CVE-2017-10243 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10243]\nDESCRIPTION: Microsoft Office software could allow a remote attacker to execute arbitrary code on the system, caused by improper handling of objects in memory. By persuading a victim to open specially-crafted content, an attacker could exploit this vulnerability to execute arbitrary code on the system with privileges of the victim.\nCVSS Base Score: 7.8\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/125293 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125293] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H)\n\nCVEID: CVE-2017-10109 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10109]\nDESCRIPTION: An unspecified vulnerability related to the Java SE Serialization component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/128870 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128870] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)", "logical_doc_id": 3, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q182", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2017-10108 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10108]\nDESCRIPTION: An unspecified vulnerability related to the Java SE Serialization component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/128869 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128869] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)\n\nCVEID: CVE-2017-10053 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10053]\nDESCRIPTION: An unspecified vulnerability related to the Java SE 2D component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/128822 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128822] 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)", "logical_doc_id": 3, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q182", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Web Experience Factory 8.0\n\nIBM Web Experience Factory 8.5", "logical_doc_id": 3, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q182", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Product VRMF APAR Remediation/First Fix IBM Web Experience Factory (Windows) 8.0 LO92930 Download fix here [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FLotus%2FWeb+Experience+Factory&fixids=LO92930_WEF80&source=SAR] IBM Web Experience Factory (Linux) 8.0 LO92931 Download fix here [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FLotus%2FWeb+Experience+Factory&fixids=LO92931_WEF80&source=SAR] IBM Web Experience Factory (Windows) 8.5 LO92932 Download fix here [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FLotus%2FWeb+Experience+Factory&fixids=LO92932_WEF85&source=SAR] IBM Web Experience Factory (Linux) 8.5 LO92933 Download fix here [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FLotus%2FWeb+Experience+Factory&fixids=LO92933_WEF85&source=SAR] WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 3, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q182", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 3, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q182", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 3, "chunk_id": 32 }, { "doc_id": "techqa_DEV_Q182", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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 Sep 2017 - Original version published\nThe 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.", "logical_doc_id": 3, "chunk_id": 33 }, { "doc_id": "techqa_DEV_Q099", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q099", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "* Problem Description -\n (configtemplate.sh fails on DMGR)\n Creating server templates with ITCAM v7.2-IF010 fails in\n main routine with following error message:\n\nCFG2056E Unexpected exception detected in\n configtemplatexd.py\n\n\".../opt/IBM/ITM/dchome/7.2.0.0.10/bin/configtemplatexd.py\"\n\nRecreating Senario -\n Following the installation steps under 7.2.0.0.10:\n\nexport JAVA_HOME=/sims110/WebSphere/AppServer/java_1.7.1_64\n wasadm@sims110:/sims110/opt/IBM/ITM/dchome/7.2.0.0.10/bin\n # ./configtemplate.sh\n\nITCAM Data Collector for WebSphere XD Template Creation\n Utility -\n- The utility guides you through the steps involved in\ncreating a XD template\n- At each prompt, enter 'q' to quit the utility or enter '?'\n for help.-\n\nEnvironment Variables:\n ITCAM_CONFIGHOME=/sims110/opt/IBM/ITM/dchome/7.2.0.0.10\n\nLog file name:\n /sims110/opt/IBM/ITM/dchome/7.2.0.0.10/data/configtemplate-trac\n e.log.\n\nList of WebSphere Application Server home directories\n discovered:\n 1. /sims110/WebSphere/AppServer\n Enter a number or enter the full path to a home directory\n [default is:\n 1]:\n 1\n\nList of WebSphere profiles discovered:\n 1. JobMgr01\n 2. BDmgr\n 3. FDmgr\n 4. MDmgr\n 5. SDmgr\n 6. DBDmgr\n 7. DFDmgr\n 8. DMDmgr\n 9. DSDmgr\n 10. DBSCCDDmgr\n 11. DFSCCDDmgr\n Enter a number [default is: 1]:\n 11\n\nSpecify the Data Collector home directory:\n /opt/IBM/ITM/dchome/currentVersion\n List of Operating Systems supported\n 1. linux-ppc\n 2. linux-ppc64\n 3. linux-s390\n 4. linux-s390-64\n 5. hpux10\n 6. hpux-64\n 7. hpux-ia64n\n 8. hpux-ia64\n 9. aix4-r1\n 10. aix-64\n 11. solaris2\n 12. solaris-64\n 13. solaris2-ix86\n 14. solaris2-ix86-64\n 15. linux-ix86\n 16. linux-ix64\n 17. win32-ix86\n 18. win64-x64\n 19. zos\n Enter a number:\n 10\n List of JDK versions supported\n 1. 15\n 2. 16\n Enter a number:\n 2\n\n[Optional] integration with ITCAM for SOA Agent\n\nDo you want to integrate with an ITCAM for SOA Agent? [1 - YES,\n 2 - NO]\n [default is: 2]:\n 1\n\n[Optional] integration with ITCAM Agent for WebSphere\n Applications -\n\nDo you want to integrate with an ITCAM Agent for WebSphere\n Applications?\n [1 - YES, 2 - NO] [default is: 2]:\n 1\n\n+--------------------------------------------------------------+\n | [Optional] For full monitoring capabilities and for\n | integration with other monitoring components, configure the\n | data collector within the application server. This\n | configuration requires an application server restart.\n +---------------------------------------------------------------\n+\n Do you want to configure a data collector within the application\n server?\n [1 - YES, 2 - NO] [default is: 1]:\n 1\n\nEnter the host name or IP address of the ITCAM Agent for\n WebSphere\n Applications TEMA: [default is: 127.0.0.1]:\n\nEnter the port number of the ITCAM Agent for WebSphere\n Applications\n TEMA: [default is: 63335]:\n\nCFG2056E Unexpected exception detected in configtemplatexd.py", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q099", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Traceback (most recent call last):\n File\n \"/sims110/opt/IBM/ITM/dchome/7.2.0.0.10/bin/configtemplatexd.py\"\n ,line 181, in \n configtema.config_tema(pdl)\n File\n \"/sims110/opt/IBM/ITM/dchome/7.2.0.0.10/bin/lib/configtema.py\",\n line 182, in config_tema\n for fullserveri in xrange(len(fullservers)):\n TypeError: object of type 'NoneType' has no len()\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nApprover :\n L2- JH, IS", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q099", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Creating server templates with ITCAM v7.2-IF010 fails in\n configtemplte.sh.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q099", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The fix for this APAR is contained in the following maintenance\n release:\n\n| Interim Fix | 7.2.0.0-TIV-ITCAM_DC-IF0012\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q099", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI35893\nREPORTED COMPONENT NAME\n TCAM AD WAS TEM\nREPORTED COMPONENT ID\n 5724Y92WD\nREPORTED RELEASE\n 720\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2015-02-26\nCLOSED DATE\n 2015-11-11\nLAST MODIFIED DATE\n 2015-11-11\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q099", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n TCAM AD WAS TEM\nFIXED COMPONENT ID\n 5724Y92WD", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q099", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R720 PSY\n UP", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q099", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Are there any TCR reports for ITCAM for AD v7.1 and what kind of reporting is available?", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q099", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "This package of Tivoli Common Reports (TCR) is based on data collected by the ITCAM Agent for WebSphere Applications, which is packaged with ITCAM for Application Diagnostics and ITCAM for Applications.\n\nThe package depends on IBM Tivoli Monitoring (ITM), which includes Tivoli Common Reporting and the Tivoli Data Warehouse.\n\nThe reports are installed on Tivoli Common Reporting. The user interface for Tivoli Common Reporting is the Tivoli Integrated Portal; the data source is Tivoli Data Warehouse. Historical data collection must be enabled for the ITCAM Agent for WebSphere Applications, so that historical data is stored in Tivoli Data Warehouse.\n\nThe following predefined reports are available in this package:\nApplication Request Performance\nDB Connection Pools\nEJB Performance\nGC Usage of Application Server\nJVM Usage of Application Server\nRequest Performance for an Application\nServlet-JSP Performance for an Application\nThreadpools\nWeb Application Performance\nApplication Request Performance for Clusters\nJVM and GC Usage for Clusters\n\nThe following software prerequisites are required for these reports: * Tivoli Monitoring 6.2.2 fix pack 3 or higher\nTivoli Common Reporting 2.1 or higher\nITCAM Agent for WebSphere Applications 7.1 Fix Pack 2, interim fix 3, or higher\nTivoli Data Warehouse (including Summarization and Pruning agent [S&P])\nTCR wiki page [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W22ac5f3ebabf_4ff4_bd55_1a897c9a443e]\n\nPRODUCT ALIAS/SYNONYM\n ITCAM ITCAM4AD ITCAMfAD ITCAM for App Diagnostics", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q099", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What types of data are collected by ITCAM for WAS TEMA (YN agent) and displayed on TEP and how are they obtained? What monitoring data available on ITCAM for Websphere Web UI are unavailable on TEP?", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q099", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "There are four types of data collected by YN TEMA:\nResource Data: obtained from Performance Monitoring Infrastructure (PMI) modules provided by WAS. They consist of aggregated data of how different resources in the system are being used.\nThey populate following TEP workspaces: Pool Analysis, Web Applications, EJB Containers, DB Connection Pools, J2C connection Pool, Thread Pools, Cache Analysis, Workload Management, Scheduler, Web Services, Platform Messaging.\n\nRequest Data: obtained from the Byte Code Injection (BCI) of WebSphere and application classes by the ITCAM Data Collector. They mainly track individual user transactions and the elapsed time to perform various operations.\nThey populate following TEP workspaces: Application Health, Request Analysis, Datasources and JMS Summary.\n\nGarbage Collection Data: obtained from parsing verbose GC file (on WAS/DC server). They are displayed in Garbage Collection Analysis workspace.\n\nWebSphere Log Entries: obtained from parsing WAS Logs (on TEMA server). They are displayed in Log Analysis workspace.\n\nData is always \u201cpulled\u201d by TEMA from Data Collector and can be obtained either at Fixed Interval or On-demand, depending on TEMA configuration.\nEither Resource Data Monitoring, or Request Data Monitoring, or Garbage Collection Data Monitoring can be enabled or disabled.\n\nThere are monitored data from ITCAM for WAS Managing Server (MS) Web UI that are not available on TEMA (can't be displayed on TEP). Those mainly are Deep-dive diagnostics like:\nLevel 3 monitoring data.\nApplication profiling (Method/Component tracing, Memory leaks, Lock analysis).\nIn-flight requests, misbehaving transactions.\nThread dumps, Thread cancellation.\nMemory management .\nHeap dumps, memory leaks.\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli Composite Application Manager for Application Diagnostics", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q099", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "WebSphere Application Server version 8.5.5 on SuSe Enterprise Linux Server 11 in hypervisor mode is not supported by ITCAM Agent for WebSphere Applications.", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q099", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Use another application server version, for example, WebSphere Application Server 8.5. Alternatively, use another Linux distribution, for example, RedHat version 6.\n\nFIX README", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q099", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Tivoli Composite Application Manager Agent for WebSphere Applications V7.2 fixes", "logical_doc_id": 5, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q099", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Installation Instructions\n\nRefer to the README file located in Fix Central for additional information\n\nDownload\nWhat is Fix Central? [http://www.ibm.com/systems/support/fixes/en/fixcentral/help/faq_sw.html] Embedded DC RELEASE DATE APAR numbers 7.2.0.0.8 [http://www.ibm.com/support/fixcentral/swg/quickorder?product=ibm/Tivoli/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0008&includeSupersedes=0&source=fc] 7.2.0.0.15 April 17, 2018 PI84591 7.2.0.0.7 [http://www.ibm.com/support/fixcentral/swg/quickorder?product=ibm/Tivoli/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0007&includeSupersedes=0&source=fc] 7.2.0.0.14 March 9, 2017 IV85603 PI05433 PI67994 PI52132 PI52407 PI71243 PI22174 PI71124 PI22832 PI77911 7.2.0.0.6 [http://www.ibm.com/support/fixcentral/swg/quickorder?product=ibm/Tivoli/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0006&includeSupersedes=0&source=fc] 7.2.0.0.13 May 6, 2016 PM92340 PI33522 PI47001 PI53858 PI00024 PI50832 PI48106 PI53964 PI41634 PI53691 PI52367 PI51119 PI57148 PI59839 PI42952 PI39907 PI42603 PI30133 PI35027 PI35893 PI34945 PI39525 PI43321 PI48106 PI53964 PI41634 PI53691 PI11450 PI16745 PI18682 PI21062 PI24319 PI25035 PI25663 PI27187 PI33891 PI34061 PI35680 PI36215 PI37162 PM70256 PM74078 PM75193 PM75581 PM87883 PM93570 IV47342 IV69645 7.2.0.0.5 [http://www.ibm.com/support/fixcentral/swg/quickorder?product=ibm/Tivoli/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0005&includeSupersedes=0&source=fc] 7.2.0.0.10 Oct 8, 2014 PM98778 PI06311 PI07084 PI22743 PI08200 PM88373 PM99070 PM94101 IV47342 PI06761 PI08473 PI08257 7.2.0.0.4 7.2.0.0.9 This is Limited Availability Interim Fix. Please contact Customer Support to obtain this fix . 7.2.0.0.3 [http://www.ibm.com/support/fixcentral/swg/quickorder?product=ibm/Tivoli/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0003&includeSupersedes=0&source=fc] 7.2.0.0.8 Oct 10, 2013 PM93570 7.2.0.0.2 [http://www.ibm.com/support/fixcentral/swg/quickorder?product=ibm/Tivoli/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0002&includeSupersedes=0&source=fc] 7.2.0.0.7 Aug 23, 2013 7.2.0.0.1 [http://www.ibm.com/support/fixcentral/swg/quickorder?product=ibm/Tivoli/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0001&includeSupersedes=0&source=fc] 7.2.0.0.5 Jul 17, 2013 PM81890; PM77662; PM79101; PM82318; PM80120; PM88932; PM76203", "logical_doc_id": 5, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q084", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What application servers are supported by ITCAM for J2EE agent v7.1.1? What has changed if compared to the previous version of this product?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q084", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "These application servers and J2SE applications are supported:\nApache Tomcat 4.x, 5.x, 6.x, 7.x\nJBoss 3.x, 4.x, and 5.x\nOracle WebLogic Server 9.x, 10.x, and 12.x; Oracle WebLogic Portal Server 9.x and 10.x\nSAP NetWeaver 7.0 (2004s), 7.1, 7.3, and 7.4\nJ2SE applications\n\nJBoss EAP versions 6.1.0, 6.2.0, 6.3.0, and 6.4.0 support has been introduced starting from 7.1.1.0-TIV-ITCAM_J2EE-IF0003\n\nSupport for versions highlighted in boldface is new in release 7.1.1\n\nSupport for versions highlighted in italics had already been introduced starting from 6.1 FP6 and later interim-fixes (typically 6.1.0.6-TIV-ITCAMfJ2EE_MP-IF000x, see their readmes for details).\nIn fact J2EE v6.x has gone out of support at this point, so you will have to upgrade to v7.1.1.0.x to use a supported version.\n\nJava 7 support has been officially introduced in version 7.1.1.\nJava 8 support has been introduced starting from 7.1.1.0-TIV-ITCAM_J2EE-IF0003\n\nThe following application servers are not supported anymore in the J2EE agent 7.1.1:\nOracle/BEA Application Server\nSun JSAS\nWebSphere Application Server Community Edition\n\nCSILandingPage \"landing page\" itcam j2ee PREVENTIVE SERVICE PLANNING", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q084", "section_id": 0, "heading": "CONTENT", "parent": null, "text": "TAB NAVIGATION\nHome [http://www.ibm.com/support/docview.wss?uid=swg21663653]\nManaging Server [http://www.ibm.com/support/docview.wss?uid=swg21661409]\nWebSphere Agent (yn) [http://www.ibm.com/support/docview.wss?uid=swg21660979]\nJ2EE Agent (yj)\nHTTP Servers Agent (ht) [http://www.ibm.com/support/docview.wss?uid=swg21661410]\nITCAMforApps [http://www.ibm.com/support/docview.wss?uid=swg21568133]\nMore [http://www.ibm.com/support/docview.wss?uid=swg21663842]\n\nINFRASTRUCTURE\n To see what is supported for the J2EE Agent (Operating Systems, Application Servers, etc.), click on the button to the left.\n\nProblem determination issues related to connectivity between a Data Collector and the Managing Server or ITM via the TEMA can be found by clicking the button to the left.\n\nProduct integration related items can be found by clicking the button to the left.\n\nUSER INTERFACE\n Information related to missing or incorrect data on the ITCAM Managing Server can be found by clicking the button to the left.\n\nInformation related to missing or incorrect data on the ITM Tivoli Enterprise Portal (TEP) can be found by clicking the button to the left.\n\nInformation related to missing or incorrect data on the Application Performance Management(APM) UI can be found by clicking the button to the left.\n\nHelp with usage of the product can be found by clicking the button to the left.\n\nInformation related to Monitoring on Demand settings and usage can be found by clicking the button to the left.\n\nSYSTEM CONFIGURATION AND ADMINISTRATION\n Items related to the J2EE Agent (TEMA or Data Collector) installation and configuration can be found by clicking the button to the left.\n\nItems related to SSL / Certificates / Security of the J2EE Agent can be found by clicking the button to the left.\n\nRecommended tuning and performance related items can be found by clicking the button to the left. The ITCAM Performance and Tuning Guide can be found by clicking here [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Composite%20Application%20Manager/page/ITCAM%20for%20AD%20Performance%20and%20Tuning%20Guide].\n\nItems related to the Transaction Tracking API can be found by clicking the button to the left.\n\nItems related to the Port Consolidator can be found by clicking the button to the left.\n\nItems related to the Request Mapper can be found by clicking the button to the left.\n\nItems related to reports generated from the Managing Server or Data Warehouse can be found by clicking the button to the left.\n\nAGENT AND DATA COLLECTORS\nFIXES AND GATHERING DOCUMENTATION FOR PROBLEMS\n Currently recommended fixes can be found by clicking the button to the left.", "logical_doc_id": 2, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q084", "section_id": 0, "heading": "CONTENT", "parent": null, "text": "All fixes for the Agent for J2EE can be found by clicking the button to the left.\n\nInformation related to tracing and logging settings can be found by clicking the button to the left.\n\nIf you have researched the problem you are experiencing and have not found a solution, please gather the documentation requested by going to this link and then open a PMR.", "logical_doc_id": 2, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q084", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "ALL TECHNOTES\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli Composite Application Manager for Application Diagnostics ITCAM for APPLICATION DIAGNOSTICS Agent for J2EE Systems and Asset Management Tivoli Composite Application Manager for Applications ITCAM for Web Resources v620 5724-S32\nPRODUCT ALIAS/SYNONYM\n ITCAM", "logical_doc_id": 3, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q084", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Commonly used APM / IBM Monitoring V8.1.2 part numbers.", "logical_doc_id": 4, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q084", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Here are the commonly used part numbers to search for when downloading the new IBM Monitoring / APM V8.1.2 components. The Agents package here will contain the WebSphere and other J2EE agents to be used for monitoring the WAS / J2EE servers.\nNote these are the upgrade part numbers, so you will need to use the base code parts [http://www-01.ibm.com/support/docview.wss?uid=swg21961194] first. You can choose to download the eAssembly or the individual packages that you need.\n\nThese images are en_US, and multilingual, multiplatform where applicable. If you are looking for non-US English images, please do your search on Passport Advantage for the right image to download for your specific language, if available.\n\nNot sure which package to download? Check this table [http://www-01.ibm.com/support/knowledgecenter/SSHLNR_8.1.1/com.ibm.pm.doc/install/saas_agent_capabilities.htm] to see what agent you want to monitor and then download the right package.\n\nIBM Monitoring V8.1.2 for Multiplatform Multilingual eAssembly (CRW7XML)\n\nComponent Part Number (approx. size) IBM Monitoring Agents Install V8.1.2 Windows 64-bit Multilingual CN7D3ML (649 MB) IBM Monitoring Agents Install V8.1.2 Windows 32-bit Multilingual CN7D4ML (158 MB) IBM Monitoring Agents Install V8.1.2 Linux 64-bit Multilingual CN7D5ML (594 MB) IBM Monitoring Agents Install V8.1.2 AIX Multilingual CN7D6ML (422 MB) IBM Agent Builder V8.1.2 Multiplatform, Multilingual CN7D7ML (636 MB) IBM Agent Builder Language Pack V8.1.2 Multiplatform Multilingual CN7D8ML (191 MB) IBM Monitoring TCR Reports V8.1.2 Multiplatform Multilingual CN7D9ML (7 MB) IBM Monitoring Server Install V8.1.2 RHEL6 64-bit Multilingual CN7DAML (2.9 GB) IBM Hybrid Gateway V8.1.2 Multiplatform Multilingual CN7DBML (230 MB)\nIBM Application Diagnostics V8.1.2 for Multiplatform Multilingual eAssembly (CRW71ML)\n\nComponent Part Number (approx. size) IBM Performance Management Application Diagnostics Server Install V8.1.2 Linux Multilingual CN7DIML (2.9 GB) IBM Performance Management Application Diagnostics Agents Install V8.1.2 Linux for System x86 Series Multilingual CN7DJML (230 MB) IBM Performance Management Application Diagnostics Agents Install V8.1.2 Windows 64-bit Multilingual CN7DKML (365 MB) IBM Performance Management Application Diagnostics Agents Install V8.1.2 AIX Multilingual CN7DLML (210 MB) IBM Performance Management Application Diagnostics Agents Install V8.1.2 Windows 32-bit Multilingual CN7DMML (85 MB) IBM Performance Management Application Diagnostics Reports V8.1.2 Multilingual CN7DNML (7 MB)\nIBM Application Performance Management (APM) V8.1.2 Multiplatform Multilingual eAssembly (CRW61ML)", "logical_doc_id": 4, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q084", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Component Part Number (approx. size) IBM APM Agents Install V8.1.2 Windows 64-bit Multilingual CN7F9ML (752 MB) IBM APM Agents Install V8.1.2 Windows 32-bit Multilingual CN7FAML (158 MB) IBM APM Agents Install V8.1.2 Linux x86 64-bit Multilingual CN7FBML (617 MB) IBM APM Agents Install V8.1.2 AIX Multilingual CN7FCML (457 MB) IBM APM Agent Builder V8.1.2 Multiplatform Multilingual CN7D7ML (636 MB) IBM APM Agent Builder Language Pack V8.1.2 Multiplatform Multilingual CN7D8ML (191 MB) IBM APM TCR Reports V8.1.2 Multiplatform Multilingual CN7FDML (7 MB) IBM APM Server Install V8.1.2 RHEL6 64-bit Multilingual CN7FEML (2.9 GB)\nIBM Application Performance Management Advanced (APM) V8.1.2 Multiplatform Multilingual eAssembly (CRW73ML)\n\nComponent Part Number (approx. size) IBM APM Advanced Server Install V8.1.2 Linux for System x86 SeriesMultilingual CN7FFML (2.9 GB) IBM APM Advanced Agents Install V8.1.2 Linux for System x86 SeriesMultilingual CN7FGML (617 MB) IBM APM Advanced Agents Install V8.1.2 Windows 64-bit Multilingual CN7FHML (752 MB) IBM APM Advanced Agents Install V8.1.2 AIX Multilingual CN7FIML (457 MB) IBM APM Advanced Agent Builder V8.1.2 Windows 32-bit Multilingual CN7FJML (158 MB) IBM APM Advanced Reports V8.1.2 Linux for System x86 Series Multilingual CN7FKML (7 MB)\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli Composite Application Manager for Application Diagnostics ITCAM for APPLICATION DIAGNOSTICS Agent for WebSphere AIX, Linux, Windows 7.1 Advanced, All Editions\nPRODUCT ALIAS/SYNONYM\n ITCAM APM IBM Performance Monitoring", "logical_doc_id": 4, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q084", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What are the names, part numbers, sizes and posting dates for ITCAM for J2EE v7.1.1.0 installation images on all supported platforms?", "logical_doc_id": 5, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q084", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "IBM Tivoli Composite Application Manager Agent for J2EE V7.1.1.0, Windows, English\nPart Number: CN0PIEN\nSize: 214Mb\nDate posted: 18 Jul 2014\n\nIBM Tivoli Composite Application Manager Agent for J2EE V7.1.1.0, AIX, English\nPart Number: CN0PJEN\nSize: 434Mb\nDate posted: 18 Jul 2014\n\nIBM Tivoli Composite Application Manager Agent for J2EE V7.1.1.0, Linux on x86, English\nPart Number: CN0PKEN\nSize: 384Mb\nDate posted: 18 Jul 2014\n\nIBM Tivoli Composite Application Manager Agent for J2EE V7.1.1.0, Linux on pSeries, English\nPart Number: CN0PLEN\nSize: 227Mb\nDate posted: 18 Jul 2014\n\nIBM Tivoli Composite Application Manager Agent for J2EE V7.1.1.0, Linux on zSeries, English\nPart Number: CN0PMEN\nSize: 314Mb\nDate posted: 18 Jul 2014\n\nIBM Tivoli Composite Application Manager Agent for J2EE V7.1.1.0, Solaris, English\nPart Number: CN0PNEN\nSize: 415Mb\nDate posted: 18 Jul 2014\n\nIBM Tivoli Composite Application Manager Agent for J2EE V7.1.1.0, HP Itanium, English\nPart Number: CN0PPEN\nSize: 752Mb\nDate posted: 18 Jul 2014\n\nIBM Tivoli Composite Application Manager Agent for J2EE V7.1.1.0, Support Files English\nPart Number: CN0PQEN\nSize: 152Mb\nDate posted: 18 Jul 2014", "logical_doc_id": 5, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q084", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Using the ITCAM for J2EE agent v7.1.1.0 with RHEL7.1 Linux Operating System.", "logical_doc_id": 6, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q084", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "As of 4Q2015, RHEL7 64-bit has now been certified for use with ITCAM for J2EE v7.1.1.0.1 and higher. Also, please be aware of this APAR for a known ITM problem:\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21960089 [http://www-01.ibm.com/support/docview.wss?uid=swg21960089]", "logical_doc_id": 6, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q084", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "In addition, you will also need this updated cienv.tar file (attached here in this technote) that goes in the /unix directory.\n\ncienv.tar [/support/docview.wss?uid=swg21972181&aid=2]cienv.tar [/support/docview.wss?uid=swg21972181&aid=1]\n\nPRODUCT ALIAS/SYNONYM\n ITCAM for J2EE", "logical_doc_id": 7, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q101", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "WebSphere Message Broker and IBM Integraton Bus have addressed the following vulnerabilities", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q101", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2017-12617 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12617]\nDESCRIPTION: Apache Tomcat could allow a remote attacker to execute arbitrary code on the system, caused by an incomplete fix related to an error when running on Windows with HTTP PUTs enabled. By sending a specially crafted request, an attacker could exploit this vulnerability to upload a JSP file and execute arbitrary code on the system.\nCVSS Base Score: 8.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/132484 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132484] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)\n\nCVEID: CVE-2017-12615 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12615]\nDESCRIPTION: Apache Tomcat could allow a remote attacker to execute arbitrary code on the system, caused by an error when running on Windows with HTTP PUTs enabled. By sending a specially crafted request, an attacker could exploit this vulnerability to upload a JSP file and execute arbitrary code on the system.\nCVSS Base Score: 8.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/132277 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132277] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q101", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Integration Bus V9.0.0.0 - V9.0.0.9\n\nIBM Integration Bus V10.0.0.0 - V10.0.0.10.\n\nWebSphere Message Broker V7.0.0.0 - V7.0.0.8\n\nWebSphere Message Broker V8.0.0.0 - V8.0.0.9", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q101", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Product VRMF APAR Remediation/Fix IBM Integration Bus V9.0.0.0 - V9.0.0.9 IT22679 The APAR is available in fix pack 9.0.0.10\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24044363 [http://www-01.ibm.com/support/docview.wss?uid=swg24044363] IBM Integration Bus V10.0.0.0 - V10.0.0.10 IT22679 The APAR is available in fix pack 10.0.0.11\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24044326 [http://www-01.ibm.com/support/docview.wss?uid=swg24044326] WebSphere Message Broker V7.0.0.0 - V7.0.0.8 IT22679 For APAR IT22679, please contact IBM support WebSphere Message Broker V8.0.0.0 - V8.0.0.9 IT22679 For APAR IT22679, please contact IBM support\nWebsphere Message Broker V7 and V8 is no longer in full support; IBM recommends upgrading to a fixed, supported version/release/platform of the product. If you are an extended support customer and require a fix, this is available only for the latest fixpack (8.0.0.9) and (7.0.0.8). To obtain the fix contact IBM support. GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.\n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q101", "section_id": 4, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q101", "section_id": 5, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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 December 2017: Original version published\nThe 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.", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q101", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg22011680]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker AIX, HP-UX, Linux, Solaris, Windows 7.0, 8.0\nPRODUCT ALIAS/SYNONYM\n WMB IIB", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q101", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "1. Launch the Adapter Connection Wizard in WMB/IIB Toolkit\n 2. Go to the 'Service Generation and Deployment Configuration' window.\n 3. In the SAP RFC trace configuration section:\n a. Set the RFCTraceOn property to 'true'\n b. Set the RFC Trace Level property to '8'. This outputs verbose debug messages, full execution path, info messages, errors and warnings.\n c. Set the Folder for RFC trace files property to the directory location where the RFC Traces will be created.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q101", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "#Troubleshooting data for WebSphere Adapter for SAP [http://www.ibm.com/support/docview.wss?uid=swg21438193#wmb]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker with Rules and Formatter Extension for Multiplatforms Linux, Windows All Editions Business Integration WebSphere Message Broker Documentation Linux, Windows 7.0, 8.0\nPRODUCT ALIAS/SYNONYM\n WMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI\n\nWMB IIB SECURITY BULLETIN", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q101", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "WebSphere Message Broker and IBM Integration Bus using the IBM Dojo Toolkit and providing the dojox/form/resources/fileuploader.swf, dojox/form/resources/uploader.swf, dojox/av/resources/audio.swf or dojox/av/resources/video.swf files are subjected to a cross-site scripting (XSS) vulnerability.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q101", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID:CVE-2014-8917 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8917]\nDESCRIPTION: IBM Dojo Toolkit is vulnerable to cross-site scripting, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability using a specially-crafted URL to execute scripts in a victim's Web browser within the security context of the hosting Web site, when the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials\nCVSS Base Score: 4.3\nCVSS Temporal Score: Seehttp://xforce.iss.net/xforce/xfdb/99303 [http://xforce.iss.net/xforce/xfdb/99303] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: AV:N/AC:M/Au:N/C:N/I:P/A:N", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q101", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM WebSphere Message Broker V8\n\nIBM Integration Bus V9", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q101", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Follow the steps outlined in the workarounds and mitigations section.\nAPAR IT06833 is targeted for availability in WebSphere Message Broker V8.0.0.6 and IBM Integration Bus V9.0.0.4 which will remove the affected files.", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q101", "section_id": 4, "heading": "WORKAROUNDS AND MITIGATIONS", "parent": null, "text": "The files affected by this vulnerability are not used by the WebSphere Message Broker or IBM Integration Bus web user interface (web UI) and can be deleted.\n\nThe product users are requested to delete the following files to address this vulnerability.\n*\n*\n*\nNote: WebSphere Message Broker V8.0.0.0 does not contain the file fileuploader.swf GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.\n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www-03.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q101", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] [http://www.first.org/cvss/cvss-guide.html] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] ACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 15 May 2015 - Original version Published\nThe 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.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q101", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21903287]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Web User Interface Linux, Windows 9.0\nPRODUCT ALIAS/SYNONYM\n WMB IIB\n\nWMB IIB PSIRT SECURITY BULLETIN", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q101", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Security vulnerabilities have been discovered in OpenSSL that were reported on June 5, 2014 by the OpenSSL Project.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q101", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "OpenSSL Security Vulnerability in DataDirect Drivers shipped with WebSphere Message Broker 8.0 and IBM Integration Bus 9.0. (CVE-2014-0224) . This only affects users of DataDirect ODBC SSL connectivity.\nLinks to latest fix packs\nWebSphere Message Broker 8.0.0.4 [http://www.ibm.com/support/docview.wss?uid=swg24037264]\nIBM Integration Bus 9.0.0.2 [http://www.ibm.com/support/docview.wss?uid=swg24037877] [http://www-01.ibm.com/support/docview.wss?uid=swg24037877]\n\nCVE-ID: CVE-2014-0224 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0224]\n\nDESCRIPTION: OpenSSL is vulnerable to a man-in-the-middle attack, caused by the use of weak keying material in SSL/TLS clients and servers. A remote attacker could exploit this vulnerability using a specially-crafted handshake to conduct man-in-the-middle attacks to decrypt and modify traffic.\n\nCVSS Base Score: 5.8\nCVSS Temporal Score: See http://xforce.iss.net/xforce/xfdb/93586 [http://xforce.iss.net/xforce/xfdb/93586] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:P/A:N)", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q101", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Websphere Message Broker V8.0\n\nIBM Integration Bus V9.0", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q101", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "For all affected products and versions this requires configuring Websphere Message Broker and IBM Integration Bus to pick up the DataDirect drivers available from IBM Fix Central (APAR IT02892)\n\nFor IBM WebSphere Message Broker V8,0 an interim fix for APAR IT02892 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT02892] is available from IBM Fix Central.\n\nFor IBM Integration Bus V9.0 an interim fix for APAR IT02892 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT02892] available from IBM Fix Central.\n\nFor IBM WebSphere Message Broker V8.0, this fix is targeted to be available in fix pack 8.0.0.6\n\nFor IBM Integration Bus V9.0, this fix is targeted to be available in fix pack 9.0.0.3", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q101", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q101", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\n[http://www.first.org/cvss/cvss-guide.html] OpenSSL Project vulnerability website [http://www.openssl.org/news/vulnerabilities.html] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] ACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 10 July 2014 - Original version Published\nThe 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.", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q101", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21679967]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Web User Interface AIX, HP-UX, Linux, Solaris, Windows 9.0\nPRODUCT ALIAS/SYNONYM\n WMB IIB\n\nWMB IIB SECURITY BULLETIN", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q101", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "WebSphere Message Broker / IBM Integration Bus WEBUI does not set X-FRAME-OPTIONS", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q101", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-9010 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9010]\nDESCRIPTION: IBM WebSphere Message Broker could allow a remote attacker to hijack the clicking action of the victim. By persuading a victim to visit a malicious web site, a remote attacker could exploit this vulnerability to hijack the victim's click actions and possibly launch further attacks against the victim.\nCVSS Base Score: 6.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/119398 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119398] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N)", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q101", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Integration Bus V10 and V9\n\nWebSphere Message Broker V8", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q101", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Product VRMF APAR Remediation/Fix IBM Integration Bus V10\nIT14670 The fix is available in Fix Pack 10.0.0.7\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24043068 [https://www-304.ibm.com/support/docview.wss?uid=swg24043068] IBM Integration Bus V9\nIT14670 The fix is available in Fix Pack 9.0.0.7\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043227 [http://www-01.ibm.com/support/docview.wss?uid=swg24043227] WebSphere Message Broker\nV8\nIT14670 The fix is available in Fix Pack 8.0.0.8\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24042925 [https://www-304.ibm.com/support/docview.wss?uid=swg24042925]\nFor unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product.\n\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at :\nhttp://www.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006308]", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q101", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q101", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q101", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 10 Feb 2017 - Original version Published\nThe 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\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker AIX, HP-UX, Linux, Solaris, Windows 8.0\nPRODUCT ALIAS/SYNONYM\n WMB IIB", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q016", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do I deploy Rule Execution Server EJB rule sessions more than once, for each application that uses them on the same server, and call them remotely?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q016", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "An EJB module can be shared among several applications on the same server or cell. However, you will find it more convenient for maintainability to bundle Rule Execution Server EJB rule sessions within each application that calls Rule Execution Server through EJBs because doing so, you can redeploy the application EAR when necessary (for an application code or XOM modification, for example) without affecting the availability of other applications. You can also have those applications call different versions of Rule Execution Server.\n\nWhen you deploy the same EJB on the same server or cell more than once, you must give each instance a unique global JNDI name to avoid conflict errors, because those names need to uniquely identify a bean in a given context. See section \"Rule Execution Server > Introducing Rule Execution Server > Rule Execution Server basics > JNDI bindings > Reference bindings for Rule Execution Server modules\" of the JRules 7.1 documentation [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.doc/Content/Business_Rules/Documentation/_pubskel/JRules/ps_JRules_Global941.html].\n\nHere is an example of the error you might get in WebSphere Application Server 7:\n\nUnable to start EJB jar, IlrStatelessRuleSessionEJB: The ilog.rules.bres.session.ejb.IlrStatelessRuleSessionHome interface of the IlrStatelessRuleSessionEJB bean in the jrules-res-session-WAS7.jar module of the jrules-res-session-WAS7_jar_2 application cannot be bound to the ejb/IlrStatelessRuleSessionEJB name location. The ilog.rules.bres.session.ejb.IlrStatelessRuleSessionHome interface of the IlrStatelessRuleSessionEJB bean in the jrules-res-session-WAS7.jar module of the jrules-res-session-WAS7_jar application has already been bound to the ejb/IlrStatelessRuleSessionEJB name location.\n\nFor EJB3, you can set your own unique names for the EJB business interfaces at deployment time (see the documentation of your application server) or you can have them generated by the server automatically. For example, WebSphere AS 7 generates the following JNDI name for the remote business interface of Rule Execution Server stateless rule sessions:\n\nejb/My RES application/jrules-res-session-ejb3-WAS7.jar/IlrStatelessSessionEJB3#ilog.rules.res.session.impl.ejb3.IlrStatelessSessionRemote\n\n(See \"Network Deployment (All operating systems), Version 7.0 > Developing and deploying applications > EJB applications > Assembling EJB 3.x enterprise beans > EJB 3.0 application bindings overview > Default bindings for EJB business interfaces and homes\" in the WebSphere AS 7 documentation [http://publib.boulder.ibm.com/infocenter/wasinfo/fep/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/cejb_bindingsejbfp.html#cejbbindingsejbfp__ejb30defaultbindings])\n\nIn that case, you must adjust the JNDI name in the Rule Execution Server client code by using the method IlrEJB3SessionFactory.setStatelessRemoteJndiName(String jndiName).", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q016", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "For EJB2, you add a prefix to the JNDI names that are specified in the application-server-specific deployment descriptors and deployment scripts, or by using the console of your application server at deployment. For example:\n\nmyApplication/ejb/IlrStatefulRuleSessionEJB\n\nand add that prefix at the end of the provider URL (java.naming.provider.url) on the client side through the rule session client API or in the jndi.properties file. For example, for WebSphere AS 7:\n\ncorbaname:iiop::#myApplication\nNote: Default JNDI names and provider URL formats vary from one application server to another. Refer to the corresponding documentation to know what is appropriate in your configuration.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q016", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "#JNDI bindings for RES V7.5 [http://pic.dhe.ibm.com/infocenter/dmanager/v7r5/topic/com.ibm.dserver.res/Content/Business_Rules/_pubskel/Infocenter_Primary/ps_DS_Rule_Execution_Server1556.html]\nJNDI bindings for RES V8.0 [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tpc_res_devclient_jndibind_intro.html]\nJNDI bindings for RES V8.5 [http://pic.dhe.ibm.com/infocenter/dmanager/v8r5/topic/com.ibm.wodm.dserver.rules.res.developing/topics/tpc_res_devclient_jndibind_intro.html]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Platform Independent 8.5, 8.0, 7.5", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q016", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "This might be due to user errors in configuration. For example, you could have set the URL of the Rule Execution Server to be 'http://:/testing' instead of 'http://:/res\" in the RTS configuration.\n\n. When you add a new server to the RTS configuration ( Websphere ILOG Rule Team Server online help > Configure: Manage your project configuration > Managing servers [http://publib.boulder.ibm.com/infocenter/brdotnet/v7r0m2/index.jsp?topic=/com.ibm.websphere.ilog.brdotnet.doc/Content/Business_Rules/Documentation/_pubskel/Rules_for_DotNET/ps_RFDN_Global716.html]), make sure you specify the URL of the Rule Execution Server (e.g.: http://localhost:8080/res).\n\nA common mistake is to specify the URL of the SSP server (e.g.: http://localhost:8080/testing), which leads to the error above.\n\nThis error could also indicate that the SSP is not correctly deployed or configured.\n\nPlease check that the SSP is correctly deployed and configured.\n\nExamine the application server logs for error messages which indicate the root of the problem. For example, you could have multiple SSPs deployed and different XOMs integrated into different SSPs. In that case, make sure that you have one SSP deployed and active, and all the XOMs are integrated within it.\n\nAlso note that the SSP and the RES management console are expected to be deployed on the same server outside the cluster, and no other SSP should be deployed inside the cluster, See Clustering Decision Validation Services [http://www.ibm.com/support/docview.wss?uid=swg21425487] for more details.\n\nIf these recommendations do not help, please contact IBM support with a description of your set up and the server logs.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Platform Independent 8.6, 8.5, 8.0, 7.5 Enterprise", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q016", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Can I configure Rules Team Server to distribute the Decision Validation Service tests to multiple application servers?", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q016", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "With a Rule Execution Server environment defined on a domain with multiple servers it is possible to define which Rule Execution Server instances will be used to execute the Rule Team Server Decision Services", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q016", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "First remember to pack all your XOMs (eXecutable Object Model) into the ssp.war following the documentation [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.doc/Content/Business_Rules/Documentation/_pubskel/JRules/ps_JRules_Global720.html].\n\nThen make sure the SSP (ssp.war) is deployed on each server along with a XU connection factory and the appropriate datasource definition.\n\nThen create your own SSP resolver, add it to the teamserver.war and set the teamserver.defaultSSPResolver.class property to this class following this specification [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/index.jsp?topic=/com.ibm.websphere.ilog.jrules.doc/html/api/html/ilog/rules/teamserver/model/testing/IlrSSPResolver.html].\n\nBy implementing your own method IlrSSPResolver.getSSPURL(String serverName,URL url), you will be able to point to something else than the default provider.\n\nThe default provider uses the url of the Rule Execution Server passed in parameter and replaces the application name with testing.\n\nA simple implementation can use the server name to return a specific server URL.\n\nfor example you can have 2 servers defined in RTS:\ntestingServer1 http://host1:9080/res\ntestingServer2 http://host1:9080/res\n\nAnd your SSP provider can evaluate the SSP URL as follow :\nif ( serverName.equals(\"testingServer1\") )\n{\nreturn ( new URL( \"http://server1:9080/testing\" ) );\n}\nelse if ( serverName.equals(\"testingServer2\") )\n{\nreturn ( new URL( \"http://server2:9080/testing\" );\n}\nelse\nreturn( new URL( \"http://host1:9080/testing\" ));\n\nThen when running a DVS test the execution will be dispatched according to the server you choose.\n\nFor a more elaborate implementation you can have a dependency with the project being tested so that you can distribute the DVS execution based on a project:\n\nManagerBean bean = ManagerBean.getInstance() ;\nIlrSession session = bean.getSession();\nIlrRuleProject project = session.getWorkingBaseline().getProject();\nString pname = project.getName();\n\n.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q016", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#Repackaging the XOM for remote testing [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.doc/Content/Business_Rules/Documentation/_pubskel/JRules/ps_JRules_Global720.html]\nIlrSSPResolver [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/index.jsp?topic=/com.ibm.websphere.ilog.jrules.doc/html/api/html/ilog/rules/teamserver/model/testing/IlrSSPResolver.html]", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q016", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "1. From the application server console, check if the application EAR files for the Decision Center and the RES Management are deployed and have been started.\n\n2. From the application server administration console, check the HTTP port number. Make sure you use this port number to access the console. For example, by default, the HTTP port number for WebSphere Application Server is 9080, but it might be configured to 9081 for the profile on which the ODM application is installed.\n\n3. Check that the HTTP port is not being used [http://www.ibm.com/support/docview.wss?uid=swg21264632] by another process. If it is, stop the other process and try to access the console again.\n\n4. Examine the server logs. If they contain the following exception:\n\ncom.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E:\n[Servlet Error]-[/moduleVersion/versioninfo.jsp]:\ncom.ibm.ws.jsp.translator.JspTranslationException: JSPG0227E: Exception\ncaught while translating /moduleVersion/versioninfo.jsp:\njava.lang.reflect.InvocationTargetException at\ncom.ibm.ws.jsp.translator.JspTranslator.processVisitors(JspTranslator.java:139) at\ncom.ibm.ws.jsp.translator.utils.JspTranslatorUtil.translateJsp(JspTranslatorUtil.java:254) at\ncom.ibm.ws.jsp.translator.utils.JspTranslatorUtil.translateJspAndCompile(JspTranslatorUtil.java:121) at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.translateJsp(AbstractJSPExtensionServletWrapper.java:548)\n\nEnsure that the /temp and /temp directories have sufficient read and write privileges for the non-root user. If possible, grant the user full access to the entire application server installation directory. Note that on Windows, you can check if you have the required privileges by right-clicking on the folder, choosing Properties, and going to the Security tab.\n\nAlso ensure there are no JSP files which were compiled by another user in the above-mentioned directories.\n\nThis error could also be due to the APAR PI09545 [http://www.ibm.com/support/docview.wss?uid=swg1PI09545], in which case apply the appropriate fix.\n\n5. Ensure there are no firewall settings which are preventing access to the Decision Center or Rule Execution Server consoles.\n\n6. Ensure that the Class loader order property is set to Classes loaded with local class loader first (parent last), for the ILOG Rule Execution Server Console module of the Rule Execution Server EAR. See Step 17 of the documentation at\nOperational Decision Manager V8.5.1 > Configuring > Configuring Operational Decision Manager on WebSphere Application Server > Configuring Rule Execution Server on WebSphere Application Server [http://pic.dhe.ibm.com/infocenter/dmanager/v8r5m1/index.jsp?topic=%2Fcom.ibm.odm.distrib.config.was%2Fconfig_ds_res_was8%2Ftsk_was_deploy_mgmt_ear.html]", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q016", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "7. Ensure that the Class loader order property is set to Classes loaded with local class loader first (parent last), for the teamserver module of the Decision Center EAR. See Step 5 of the documentation at\nOperational Decision Manager V8.5.1 > Configuring > Configuring Operational Decision Manager on WebSphere Application Server > Configuring the Decision Center consoles on WebSphere Application Server > Configuring the Decision Center consoles on WebSphere Application Server for distributed platforms > Step 4: Deploying the Decision Center EAR file [http://pic.dhe.ibm.com/infocenter/dmanager/v8r5m1/index.jsp?topic=%2Fcom.ibm.odm.distrib.config.was%2Fconfig_dc_websphere%2Ftsk_zlinux_change_class_load_seq.html]\n\n8. Examine the server logs (including FFDC logs if working with WebSphere Application Server) and address any additional errors such as authentication errors [http://www.ibm.com/support/docview.wss?uid=swg21578192].\n\n9. After making the above changes, restart the server and try to access the console for the Decision Center and/or the Rule Execution Server again.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q016", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How can I improve the performance of Decision Validation Services (DVS) and Decision Warehouse?", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q016", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Improving the performance of DVS testing and the Decision Warehouse involves reducing the size of the execution trace data generated during tests, and also some architectural and environmental configurations that might be suited to your use case. The following are recommendations you can consider incorporating:\n\nReduce the size of the execution data:\nFilter data [http://www.ibm.com/support/docview.wss?uid=swg21586717] using the ruleset properties: monitoring.filters and monitoring.inout.filters.\nReduce the BOM serialization overhead: * Override the toString() method for the ruleset parameters to return minimal information\nSet the ruleset property ruleset.bom.enabled to \"false\" to remove support for BOM based serialization. This property is set to \"true\" by default when extracting rulesets from Rule Team Server (RTS) and Decision Center, and needs to be explicitly set to \"false\" in order to deactivate it. (You should set it to \"true\" if you need to generate an Excel report from a Test Suite/Simulation in RTS.)\n\nRefer to the documentation Optimizing Decision Warehouse for v7.1.x or earlier [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/index.jsp?topic=%2Fcom.ibm.websphere.ilog.jrules.doc%2FContent%2FBusiness_Rules%2FDocumentation%2F_pubskel%2FJRules%2Fps_JRules_Global733.html] and WODM [http://publib.boulder.ibm.com/infocenter/dmanager/v7r5/index.jsp?topic=%2Fcom.ibm.dserver.res%2FContent%2FBusiness_Rules%2F_pubskel%2FInfocenter_Primary%2Fps_DS_Rule_Execution_Server1571.html].\nReduce the number of columns in the Excel files by using the Ignore for DVS flag for the arguments in the DVS constructor, in Rule Studio [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/index.jsp?topic=%2Fcom.ibm.websphere.ilog.jrules.doc%2FContent%2FBusiness_Rules%2FDocumentation%2F_pubskel%2FJRules%2Fps_JRules_Global715.html] or Rule Designer [http://publib.boulder.ibm.com/infocenter/dmanager/v7r5/index.jsp?topic=%2Fcom.ibm.dserver.rulestudio%2FContent%2FBusiness_Rules%2F_pubskel%2FInfocenter_Primary%2Fps_DS_Rule_Designer1303.html&resultof=%22Adding%22%20%22ad%22%20%22removing%22%20%22remov%22%20%22columns%22%20%22column%22%20%22from%22%20%22Excel%22%20%22excel%22%20%22file%22%20].\nYou can also choose to not write the traces to a database (Decision Warehouse) as shown in this sample [http://www.ibm.com/support/docview.wss?uid=swg21441394].\n\nConfigure Decision Warehouse: * Manage the production and test environments separately [http://publib.boulder.ibm.com/infocenter/dmanager/v7r5/index.jsp?topic=%2Fcom.ibm.dserver.overview%2FContent%2FBusiness_Rules%2F_pubskel%2FInfocenter_Primary%2Fps_DS_Overview83.html], and use a different Decision Warehouse instance for each environment.\nWrite asynchronously to Decision Warehouse: * Using a JMS provider, such as WebSphere MQ or OpenJMS.\nUsing MDBs or in batch using a ETL tool, such as Clover.ETL or Cognos ETL.\nPerform an asynchronous update to Decision Warehouse, as shown in this sample [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/index.jsp?topic=%2Fcom.ibm.websphere.ilog.jrules.doc%2FContent%2FBusiness_Rules%2FDocumentation%2F_pubskel%2FJRules%2Fps_JRules_Global1781.html] for v7.1.x and earlier (and this sample [http://publib.boulder.ibm.com/infocenter/dmanager/v7r5/index.jsp?topic=%2Fcom.ibm.dserver.samples%2FContent%2FBusiness_Rules%2F_pubskel%2FInfocenter_Primary%2Fps_DS_Samples588.html] for WODM).\nCapture the Decision Warehouse trace as an asynchronous operation in application servers supporting thecommonj WorkManager API, as shown in this sample [http://www.ibm.com/support/docview.wss?uid=swg21433167].\nEstimate the database capacity [http://www.ibm.com/support/docview.wss?uid=swg21430461] that should be allocated.\n\nRefer to the documentation at Auditing executed decisions [http://publib.boulder.ibm.com/infocenter/dmanager/v7r5/index.jsp?topic=%2Fcom.ibm.dserver.overview%2FContent%2FBusiness_Rules%2F_pubskel%2FInfocenter_Primary%2Fps_DS_Overview83.html] for detailed recommendations for configuring Decision Warehouse.", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q016", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Configure Rule Execution Server (RES): * Do not use a production RES for your tests and simulations. Instead dedicate a separate RES instance for testing.\nSet the optimal XU and SSP pool sizes (in v7.1.x or earlier [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/index.jsp?topic=%2Fcom.ibm.websphere.ilog.jrules.doc%2FContent%2FBusiness_Rules%2FDocumentation%2F_pubskel%2FJRules%2Fps_JRules_Global206.html] and WODM [http://publib.boulder.ibm.com/infocenter/dmanager/v7r5/index.jsp?topic=%2Fcom.ibm.dcenter.overview%2FContent%2FBusiness_Rules%2F_pubskel%2FInfocenter_Primary%2Fps_DC_Overview2884.html]).\nIncrease the size of the database connection pool for the RES data source.\nDedicate more processing resources to the handling of DVS tests: * Deploy the SSP along with the RES console on a dedicated server. (By default tests are run on a single SSP, see Clustering Decision Validation Services [http://www.ibm.com/support/docview.wss?uid=swg21425487]).\nOtherwise, distribute the DVS tests [http://www.ibm.com/support/docview.wss?uid=swg21502095] on different RES instances.\nImprove RES performance [http://www.ibm.com/support/docview.wss?uid=swg21589513].\n\nConfigure Rule Team Server (RTS) or Decision Center: * Install RTS and RES on separate computers.\nReduce the size of the Decision Warehouse trace when running scenario suites from RTS, as shown in this sample [http://www.ibm.com/support/docview.wss?uid=swg21438208].\nImprove RTS performance [http://www.ibm.com/support/docview.wss?uid=swg21584855].\n\nConfigure Rule Studio or Rule Designer: * Increase the heap size for DVS testing [http://www.ibm.com/support/docview.wss?uid=swg21427125].\nImprove Rule Studio or Rule Designer performance [http://www.ibm.com/support/docview.wss?uid=swg21589514].\n\nIn addition, refer to the sections Enhancing the performance of Decision Warehouse and Enhancing the performance of Decision Validation Services in the IBM Redpaper: Proven Practices for Enhancing Performance: A Q&A for IBM WebSphere ILOG BRMS 7.1 [http://www.redbooks.ibm.com/redpapers/pdfs/redp4775.pdf]. RELATED INFORMATION\n#Improving the performance of Decision Center [http://publib.boulder.ibm.com/infocenter/dmanager/v7r5/index.jsp?topic=%2Fcom.ibm.dcenter.overview%2FContent%2FBusiness_Rules%2F_pubskel%2FInfocenter_Primary%2Fps_DC_Overview2884.html]\nImproving Decision Validation Services performance [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/index.jsp?topic=%2Fcom.ibm.websphere.ilog.jrules.doc%2FContent%2FBusiness_Rules%2FDocumentation%2F_pubskel%2FJRules%2Fps_JRules_Global206.html]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere ILOG Decision Validation Services Performance Platform Independent 7.1, 7.0", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q056", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To resolve this issue, complete the following steps:\n\nNote: Change instances of the cell_name, cluster_name, node_name, server_name variables with the information for your environment.\n\n1. Enter the following command on a command line to launch the wsadmin tool and use the Jython programming language:\n\n wsadmin -lang jython\n\n2. Enter the following command to save the deployment targets:\n\n modules = AdminApp.listModules('commsvc',['-server'])\n\n The results should contain a list of targets that you will use in steps 3 through\n\n5. For example:\n\n 'commsvc#commsvc.rest.war+WEB-INF/web.xml#\n WebSphere:cell=wt0cell,cluster=wt0clust+WebSphere:\n cell=wt0cell,node=wt0node5,server=wt0pbx1+WebSphere:\n cell=wt0cell,node=wt0node4,server=wt0svt+WebSphere:\n cell=wt0cell,node=wt0node4,server=wt0s000+WebSphere:\n cell=wt0cell,node=wt0node4,server=wt0x000+WebSphere:\n cell=wt0cell,node=wt0node5,server=wt0s002+WebSphere:\n cell=wt0cell,node=wt0node4,server=wt0s001+WebSphere:\n cell=wt0cell,node=wt0node5,server=wt0s003'.\n\n In this example your potential targets are cell=wt0cell, cluster=wt0clust, node=wt0node5, node=wt0node4, server=wt0pbx1, and so on.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q056", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "3. Enter the following command for the first cluster target:\n\n Note: This step replaces the existing targets with one new target.\n\n AdminApp.edit('commsvc', '[ -MapModulesToServers [[ \"commsvc\"\n commsvc.rest.war,WEB-INF/sip.xml WebSphere:cell=cell_name,\n cluster=cluster_name]]]' )\n\n From the example in step 2, this command replaces the existing targets with one new target: cell=wt0cell,cluster=wt0clust:\n\n AdminApp.edit('commsvc', '[ -MapModulesToServers [[ \"commsvc\"\n commsvc.rest.war,WEB-INF/sip.xml WebSphere:cell=wt0cell,\n cluster=wt0clust]]]' )\n\n4. Enter the following command for each additional cluster target:\n\n Note: This step adds to the existing targets.\n\n AdminApp.edit('commsvc', '[ -MapModulesToServers [[ \"commsvc\"\n commsvc.rest.war,WEB-INF/sip.xml+WebSphere:cell=cell_name,\n cluster=cluster_name]]]' )\n\n From the example in step 2, this command adds to existing cluster=wt0clust target:\n\n AdminApp.edit('commsvc', '[ -MapModulesToServers [[ \"commsvc\"\n commsvc.rest.war,WEB-INF/sip.xml +WebSphere:cell=wt0cell,\n cluster=wt0clust]]]' )", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q056", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "5. Enter the following command for each server target that is not a cluster member:\n\n Note: This step adds to the existing targets.\n\n AdminApp.edit('commsvc', '[ -MapModulesToServers [[ \"commsvc\"\n commsvc.rest.war,WEB-INF/sip.xml+WebSphere:cell=cell_name,\n node=node_name,server=server_name]]]' )\n\n From the example in step 2, this command adds to the existing wt0svt target server from wt0node4 node , wt0cell cell:\n\n AdminApp.edit('commsvc', '[ -MapModulesToServers [[ \"commsvc\"\n commsvc.rest.war,WEB-INF/sip.xml +WebSphere:cell=wt0cell,\n node=wt0node4,server=wt0svt]]]' )\n\n6. Enter the following command to save the configuration:\n\n AdminConfig.save()\n\n7. Synchronize the affected nodes with the deployment manager.\n\n8. Restart the cluster or clusters.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q056", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "Feature Pack for CEA Release Notes [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v700cea&product=was-nd-mp&topic=relnotes]\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Install AIX, HP-UX, Linux, Solaris, Windows 7.0.0.7 Base, Express, Network Deployment Application Servers WebSphere Application Server for z/OS Install z/OS 7.0.0.7", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q056", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The following error is displayed: CRRAM703I: Database - CRRAM701E: Database \u2013 Error. This message indicates that Rational Team Concert is missing the repotools.bat file. The system might contain the repotools.sh file instead.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q056", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "This error occurs if the deployment manager for IBM WebSphere Application Server is on a different operating system from the WebSphere Application Server instance host.\n\nNetwork deployment environments include a deployment manager server. The deployment manager manages multiple application servers and clusters. A cluster consists of multiple application servers. When Rational Asset Manager is deployed in a network deployment environment, it is usually deployed on a cluster.\n\nInstalling a deployment manager and a Rational Asset Manager cluster in a mixed operating system environment is not supported. However, if you are installing Rational Asset Manager on a network deployment of WebSphere Application Server that runs different operating systems, you can use the following guidelines.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q056", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Case 1: Run the environment on one operating system\n\nThe preferred installation configuration is to run the deployment manager and the Rational Asset Manager cluster on the same operating system. Running the entire environment on the same operating system simplifies the installation process and the management of the application server.\n\nIn this case, you can install Rational Asset Manager by following the procedures in the product documentation.\n\nCase 2: Run the deployment manager and cluster on different operating systems\n\nIf the deployment manager and Rational Asset Manager cluster are running on different operating systems, perform a manual installation. For example, if the deployment manager is running on AIX and the Rational Asset Manager cluster is running on a Windows system, follow these steps:\n\n1. Install the Rational Asset Manager server setup application on the cluster by using the WebSphere Application Server administration console or the wsadmin scripts.\n 2. Run the setup application by entering this URL in a web browser: http://appServer/ram.setup\n 3. In the server setup application, when you are prompted to specify the installation files, select the Windows version of the files to access the application server that runs on a Windows system.\n 4. Follow the instructions in the server setup application to finish the installation process.\n\nCase 3: Run the deployment manager and a few application servers on the same operating system, and run other application servers on another operating system\n\nIf the deployment manager and a few of the application servers in the Rational Asset Manager cluster are running on the same system and a few other application servers are running on a different operating system, issues might occur. A cluster of this type is not ideal, and this deployment of Rational Asset Manager has not been tested.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q056", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "For example, the deployment manager might run on AIX while the Rational Asset Manager cluster consists of application servers on AIX and a Windows system. In this case, these issues might occur:\nRunning repotools issue - file not found: You can resolve this issue by running the correct version of the repotool files. If you deployed the Windows version of the files, run the repotools.bat file from an application server that is running the Windows system.\nLicense client issue: The license client is a shared library in WebSphere Application Server that was created at the application server scope.\n If the license client that is running on an application server does not match the operating system, download the matching operating system .jar files to the server and point the variable of the license client shared library to the new .jar files. The variable is named rlsibmratl811_*.\nIndexer issue: The indexer code is at com.ibm.ram.repository.web_runtime.ear\\com.ibm.ram.repository.web.war\\WEB-INF\\classes\\oiexport\n The code varies by operating system. You must change the oiexport classes with the matching operating system classes that can be found in the EAR file for that operating system.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q056", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "A Data Services Scheduler erroneously gets created at the cell level for the deployment manager and federated server profiles. These servers then try to run the scheduler upon startup, but they cannot find a local IBM_WBM_DATA_SERVICES EAR file and therefore return the error. In ND, the Data Services Scheduler should get created after profiles are created at the cluster or server scope, using the WebSphere Business Monitor configuration tool in the administrative console (Servers > WebSphere Business Monitor configuration). The WebSphere Business Monitor configuration tool will create both the Data Services Scheduler resource and the IBM_WBM_DATA_SERVICES EAR file at the same cluster or server scope.\n[/support/docview.wss?uid=swg21329981&aid=1]", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q056", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "No action is required.\n\nHowever, the errors can be confusing, and so can the duplicate Data Services Scheduler resource at the cell level. It is recommended that you remove the duplicate cell-level scheduler resource.\n\nTo remove the resource, open the administrative console and select Resources > Schedulers. Select the cell scope. Select the DataServicesScheduler resource at the cell scope and click Delete.\n[/support/docview.wss?uid=swg21329981&aid=2]", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q056", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "Existing Security Domain associated with IBM Content Navigator Node or Cluster is a possible cause of the failure.\n\nIBM WebSphere Application Server has the ability to define additional Security Domains that can override a subset of the global security settings. These domains can be used to provide customized security settings for applications and service integration buses. A Security Domain has a scope that defines where its settings are applicable. Settings that are not defined in the domain default to the global security settings.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q056", "section_id": 1, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Check the security domain listed IBM WebSphere Application Server and its association.\nSecurity->Security Domains\nOpen security domain and check if it is associated with IBM Content Navigator Node or Cluster.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q056", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "A Security Domain can be scoped to an entire cell, or to a specific set of servers, clusters, or service integration buses. Therefore, multiple security domains can be used to allow security settings to vary from one application to another application. Security settings that apply to an application will be defined by the following scope:\n\n1. If the application is running on a server or cluster that is within the scope of a security domain, those settings will be used. Security settings that are not defined in this domain will be taken from the global security settings (not a cell-level domain).\n\n2. If the application is running on a server or cluster that is not within the scope of a security domain, but a security domain has been defined at the cell scope, that domain will be used. Security settings that are not defined in this domain will be taken from the global security settings.\n\n3. If the previous conditions do not apply, the global domain settings will be used. Note that you can enable or disable application security at the domain and global level, so just falling within a domain does not necessarily mean that application security is enabled. Also, note that naming operations always use the global security configuration.\n\nFollow the instructions below to successfully deploy IBM Content Navigator on WebSphere Application Server with Security Domains.\nUsing WebSphere Administration Console go to Security->Security Domains.\nOpen security domain and check if it is associated with IBM Content Navigator Node or Cluster.\nIf the IBM Content Navigator Node or Cluster is associated with the Security Domain, uncheck the check box for the Node or Cluster and save the changes.\nRerun the deployment of IBM Content Navigator.\nRestart WebSphere Application Server(full restart).\nRe-associate the IBM Content Navigator Node or Cluster with the security domain.\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server AIX, HP-UX, Mac OS, Solaris, Windows 8.5 Base, Network Deployment", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q056", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "The cause of the problem is that the WebSphere Application Server Java\u2122 virtual machine (JVM) could not find the JDBC JAR file, in this example the DB2 JAR, in its classpath that contains the implementation class. The most likely cause is that the classpath of the JDBC Provider configuration has used a WebSphere Application Server variable, for example, DB2_JDBC_DRIVER_PATH, which has not been set for the corresponding WebSphere Application Server jvm process. This could also be caused on Unix based servers by the userID not having permission to access the jar that contains the class.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q056", "section_id": 1, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Check the database provider and data source configuration to see if the WebSphere Application Server JDBC driver path system variable is used in the classpath in the JDBC Provider and ensure the variable is set for the correct scope; the scope could be cell, node, cluster, or server. To determine which scope the resource is defined, one can use the Administrative Console. This can also be determined by which SystemOut.log file contains the J2CA0036E and DSRA0023E errors.\n\nIf the J2CA0036E and DSRA0023E are logged in the application server's SystemOut.log, then check the JDBC Provider configuration to see if it uses WebSphere variables for its classpath setting. From the Administrative Console select Resources > JDBC Provider > DB_Provider_Used_By_DataSource, and inspect the classpath. For this example, one would check to see if the JDBC Provider configuration uses the Application Server's DB2_INSTALL_ROOT and DB2_JDBC_DRIVER_PATH variable.\n\nThen confirm that variable points to the correct location of the driver. To do this, from the Administrative Console, select Resources > WebSphere Variables. View the location specified in the DB driver path variable and confirm that the driver is installed in that location.\n\nSimilarly, if the JDBC provider is defined at the node scope, the JDBC driver path system variable must be defined at the node scope. And if the JDBC provider is defined at the cell scope, then the Deployment Manager's (DMgr's) JDBC provider configuration must be checked.", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q056", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Check the JDBC Provider's configuration to see if the variable is used and confirm that variable points to the correct location for the driver and correct it if it does not. Also, for Unix based servers, confirm the userID that is used to run the Application Server jvm process has correct permission to use the driver.", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q056", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "A simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21660862]\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q069", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This SupportPac contains all the IBM MQ V9 client components.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q069", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Click here to go straight to the download table.\n\nAn IBM MQ client is part of the product that can be installed on its own, on a separate machine from the base product and server. You can run an IBM MQ application on an IBM MQ client and it can interact, by means of a communications protocol, with one or more IBM MQ servers and connect to their queue managers. The servers to which the client connects may or may not be part of a cluster.\n\nIBM MQ Family Platforms provides a list of which platforms are supported as IBM MQ Clients and/or Servers.\n\nAn application that you want to run in the IBM MQ client environment must first be linked with the relevant client library. When the application issues an MQI call, the IBM MQ client code directs the request to a queue manager, where it is processed and from where a reply is sent back to the client. The link between the application and the client code is established dynamically at run time. The MQI is available to applications running on the client platform; the queues and other IBM MQ objects are held on a queue manager that you have installed on a server machine.\n\nClick here to go straight to the download table.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q069", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Possible Uses\nWhy use IBM MQ clients?\n\u00bb Using IBM MQ clients is an efficient way of implementing IBM MQ messaging and queuing.\n\u00bb You can have an application that uses the MQI running on one machine and the queue manager running on a different machine, either physical or virtual. The benefits of doing this are:\nThere is no need for a full IBM MQ implementation on the client machine.\nHardware requirements on the client system are reduced.\nSystem administration requirements are reduced.\nAn IBM MQ application, running on a client, can connect to multiple queue managers on different systems.\nAlternative channels using different transmission protocols can be used.\nWhat applications run on an IBM MQ client?\n\u00bb The full MQI is supported in the client environment and this enables almost any IBM MQ application to be relinked to run on an IBM MQ client. Link the application on the IBM MQ client to the MQIC library, rather than to the MQI library. The exceptions are:\nAn application that uses global transactions; that is, it requires sync point coordination with resource managers other than the queue manager.\nGet(signal) on z/OS.\n\u00bb Applications which are built using various programming languages including C, C++, .NET (Windows systems only), COBOL, Java and JMS.\n\u00bb Applications running within application servers that are certified as having passed the JEE 7 Compatibility Test Suite can use the IBM MQ resource adapter provided in the SupportPac. For more information see IBM MQ resource adapter v9.0 statement of support [http://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.dev.doc/q128150_.htm].\n\nNote: An application running on an IBM MQ client can connect to more than one queue manager concurrently, or use a queue manager name with an asterisk (*) on an MQCONN or MQCONNX call. If you want to link to the queue manager libraries instead of the client libraries, you have to modify the application to enable this.\n\nRELATED MESSAGE SERVICE CLIENTS\nThe IBM Message Service Client offers C/C++ users an Application Programming Interface (API) that is consistent with the Java Message Service (JMS) API. Applications created using this client can be used to exchange messages between other XMS applications, JMS applications or native IBM MQ applications.\n\nFor more information and to download the client, go here:\nIBM Message Service Client for C/C++ (SupportPac IA94) [http://www.ibm.com/support/docview.wss?rs=0&q1=ia94&uid=swg24007092&loc=en_US&cs=utf-8&cc=us&lang=en]", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q069", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Skill Level Required\nUsers should be familiar with the IBM MQ product family in general and have particular skills on the platform for which this client is intended.\n\nNew in this Release\nIBM MQ V9.0.0.4 added.\n\nDetails\nAuthor: IBM MQ Development, Hursley\nCategory: 3\nReleased: 02Jun16\nLast updated: 17May18\nCurrent Version: 9.0.0.4\n\u00bbPlease note that the version number shown in the right-hand pane is the version of the IBM MQ product that this SupportPac applies to. The date is the last web page refresh.\n\nTo view the complete portfolio of IBM MQ SupportPacs please visit the IBM MQ SupportPacs homepage. [http://www-306.ibm.com/software/integration/support/supportpacs]\n\nPREREQUISITES\nThis client will inter operate with all the currently supported WebSphere MQ server products, provided the functions used are common to the release of server and client.\n\nNotes:\nManaged File Transfer (MFT) code is not provided in this SupportPac.\n\nIBM has withdrawn the download of the MQ Client for HP NonStop Server. As IBM has stated in a Statement of Direction ( https://ibm.biz/MQ-SoD-Nov2014 [https://ibm.biz/MQ-SoD-Nov2014]) there is an intent to deliver an updated version of IBM MQ for the HP NonStop Server platform as this should be a better solution to meet the MQ connectivity needs for most of the customers on the HP NonStop Server platform. In common with other IBM MQ platforms, MQ Clients that run on other platforms will continue to provide connectivity to IBM MQ Servers on the HP NonStop platform and other MQ Server supported platforms.\n\nTo gain an early look at the intended release of IBM MQ V8 for HP NonStop Server please join the beta program by contacting your IBM sales representative.\n\nINSTALLATION INSTRUCTIONS\nTo install a Unix Client:\n1. Logon as root, create an empty directory (with sufficient space to receive the download file) and make it current.\n2. Download 9.0.0.x-IBM-MQC- to this directory. (Where 'platform' is replaced with a specific platform name e.g. AIX, Linux-x86)\n3. Uncompress 9.0.0.x-IBM-MQC- .\n4. Execute tar -xvf 9.0.0.x-IBM-MQC-.\n5. Execute rm 9.0.0.x-IBM-MQC-.\n6. To complete the installation of the client, follow the instructions provided for IBM MQ V9 in Knowledge Center.\n\nTo install the client on a Windows machine, download the zip file and extract the content. From the Windows subdirectory that has been created, run the setup.exe program.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q069", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Redistributable clients\nPlease note any files named '9.0.0.x-IBM-MQC-Redist-' can be redistributed as per the terms of the MQ license.\n\nDOWNLOAD PACKAGE\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options IBM MQ V9.0.0.4 LTS Clients 17 May 2018 US English 111 HTTP [http://ibm.biz/mq9004clients] IBM MQ V9.0.5 CD Clients 16 Mar 2018 US English 111 HTTP [http://ibm.biz/mq905clients] IBM MQ V9.0.0.3 LTS Clients 08 Mar 2018 US English 111 HTTP [http://ibm.biz/mq9003clients] IBM MQ V9.0.4 CD Clients 06 Nov 2017 US English 111 HTTP [http://ibm.biz/mq904clients] IBM MQ V9.0.0.2 LTS Clients 05 Oct 2017 US English 111 HTTP [http://ibm.biz/mq9002clients] IBM MQ V9.0.0.1 LTS Clients 11 May 2017 US English 111 HTTP [http://ibm.biz/mq9001clients] IBM MQ V9.0 LTS Clients 02 Jun 2016 US English 111 HTTP [http://ibm.biz/mq9000clients]\nTECHNICAL SUPPORT\n Category 3 IBM MQ SupportPacs are supplied under the standard terms and conditions provided by the International Program License Agreement (IPLA) and thus, carry program defect service for IBM MQ customers. Please read the IPLA and LI files that accompany the SupportPac, to ensure you understand the conditions under which the SupportPac is provided.\n\nIf you encounter what you believe to be a defect with the SupportPac, and you have a current license for an IBM MQ server product, you may request Program Services by reporting the problem through the same defect reporting channel you employ for the IBM MQ server products on which you are using the SupportPac. No proof of entitlement is required to use this SupportPac.\n\nService is available for the V9 version of this SupportPac for as long as the IBM MQ V9 server product is supported by service. Refer to the WebSphere product lifecycle pages for the relevant service information. This SupportPac is only supported with IBM MQ platforms that are themselves supported.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q069", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When using the WebSphere MQ v7.5 classes for JMS or classes for\n Java to connect to an IBM MQ v8 queue manager that has the\n Advanced Message Security component installed, opening a queue\n on a queue manager results in the following exception being\n thrown to the application:\n\n MQJE001: Completion Code '2', Reason '6114'.\n com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ2008: Failed\n to open MQ queue 'QUEUE1'.\n JMS attempted to perform an MQOPEN, but WebSphere MQ reported an\n error.\n Use the linked exception to determine the cause of this error.\n Check that the specified queue and queue manager are defined\n correctly.\n at\n com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(\n Reason.java:585)\n at\n com.ibm.msg.client.wmq.common.internal.Reason.createException(Re\n ason.java:221)\n at\n com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCall\n Success(WMQMessageConsumer.java:129)\n at\n com.ibm.msg.client.wmq.internal.WMQConsumerShadow.initialize(WMQ\n ConsumerShadow.java:988)\n at\n com.ibm.msg.client.wmq.internal.WMQSyncConsumerShadow.initialize\n (WMQSyncConsumerShadow.java:139)\n at\n com.ibm.msg.client.wmq.internal.WMQMessageConsumer.(WMQMessageCo\n nsumer.java:257)\n ...\n Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call\n failed with compcode '2' ('MQCC_FAILED') reason '6114'\n ('MQRC_INSUFFICIENT_DATA').\n at\n com.ibm.msg.client.wmq.common.internal.Reason.createException(Re\n ason.java:209)\n ... 9 more\n Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=6114\n at\n com.ibm.mq.ese.intercept.JmqiOpenInterceptorImpl.processExceptio\n nAfterOpen(JmqiOpenInterceptorImpl.java:712)\n at\n com.ibm.mq.ese.intercept.JmqiOpenInterceptorImpl.afterSpiOpen(Jm\n qiOpenInterceptorImpl.java:212)\n at\n com.ibm.mq.ese.jmqi.InterceptedJmqiImpl.spiOpen(InterceptedJmqiI\n mpl.java:411)\n at com.ibm.mq.ese.jmqi.ESEJMQI.spiOpen(ESEJMQI.java:513)\n at\n com.ibm.msg.client.wmq.internal.WMQConsumerShadow.initialize(WMQ\n ConsumerShadow.java:961)\n ... 7 more\n Caused by: The IBM WebSphere MQ Advanced Message Security Java\n interceptor failed to obtain the security policy. Reason Code:\n '6114'\n The IBM WebSphere MQ Advanced Message Security Java interceptor\n was not able to obtain the security policy.\n See subsequent messages in the exception for more details about\n the cause of the error.\n at\n com.ibm.mq.ese.service.PolicyServiceImpl.failedToObtainPolicyExc\n eption(PolicyServiceImpl.java:407)\n at\n com.ibm.mq.ese.service.PolicyServiceImpl.policyFromPcf(PolicySer\n viceImpl.java:613)\n ...\n Caused by: com.ibm.mq.headers.MQDataException: MQJE001:\n Completion Code '2', Reason '6114'.\n at\n com.ibm.mq.headers.MQDataException.getMQDataException(MQDataExce\n ption.java:314)\n at com.ibm.mq.headers.internal.Header.read(Header.java:620)\n at com.ibm.mq.headers.pcf.MQCFST.(MQCFST.java:138)\n at\n com.ibm.mq.headers.pcf.PCFParameter.nextParameter(PCFParameter.j\n ava:73)\n ...\n Caused by: java.io.EOFException\n at java.io.DataInputStream.readFully(DataInputStream.java:209)\n at\n com.ibm.mq.headers.internal.DataInputWrapper.readFully(MessageWr\n apper.java:247)\n at\n com.ibm.mq.headers.internal.store.ByteStore.readFrom(ByteStore.j\n ava:303)\n ...\n\n The above exception would be thrown even when the queue that the\n application attempted to open is not AMS protected.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q069", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "1. Use IBM MQ V8 classes for JMS/Java\n\n 2. Use WMQ V7.5.0.4 classes for JMS, then disable the AMS\n function. Please refer to following page in the Knowledge\n Center that describes how to do this:\n\n https://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm\n .mq.sec.doc/q127080_.htm#q127080 [https://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.sec.doc/q127080_.htm#q127080]\n\n 3. Remove the AMS component from the queue manager installation\n if this is not required by the connecting applications.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q069", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n This issue affects all users of the:\nWebSphere MQ v7.5 classes for JMS\nWebSphere MQ v7.5 classes for Java\n\n who run their applications in a JVM with a file encoding scheme\n which does not guarantee a one-to-one mapping of byte to String\n conversion. An example of such a file encoding scheme is UTF-8,\n where a single character may be represented by one or more\n bytes, as opposed to Cp1252 where each character is represented\n by exactly one byte.\n\n It is also required that the queue manager installation includes\n the Advanced Message Security (AMS) component, although it does\n not need to be in active use.\n\n Platforms affected:\n MultiPlatform\n\n PROBLEM DESCRIPTION:\n Advanced Message Security (AMS) capability is included in the\n WebSphere MQ v7.5 (and later) classes for JMS and classes for\n Java. As such, when an application using this version of the\n Java client attempts to open a queue on a queue manager, a check\n is made to determine whether an AMS policy has been defined for\n that queue.\n\n The WebSphere MQ v7.5 classes for JMS client was incorrectly\n treating the policy information it received from the queue\n manager as character data and internally constructed a\n \"java.lang.String\" object from the received data bytes. When\n this data was subsequently parsed to determine whether a policy\n existed on the queue, the \"java.lang.String\" object was\n converted back into a sequence of bytes.\n\n Due to the use of the JVM's default character encoding (which\n varies by platform), during this byte to string and back to byte\n conversion, the final byte sequence was not necessarily the same\n as the bytes which were returned by the queue manager.\n\n For example, the byte '0x80' can be returned as part of the byte\n sequence when a policy for a queue does not exist. When using\n UTF-8 as the default JVM charset, such is the case on the Linux\n platform, performing the conversion operations described above\n can result in this byte being replaced by the sequence of bytes,\n '0xEF', '0xBF' and '0xBD', resulting in being two bytes longer\n than the original byte sequence.\n\n This results in a failure to parse the byte sequence as the\n length is not as expected, resulting in the MQRC 6114\n 'MQRC_INSUFFICIENT_DATA' exception code.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q069", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The WebSphere MQ v7.5 classes for JMS and classes for Java have\n been updated such that the byte sequence that describes Advanced\n Message Security (AMS) policy information for a particular queue\n is stored internally as a byte sequence, and not converted to a\n Java String.\n\nThe fix is targeted for delivery in the following PTFs:\n\nVersion Maintenance Level\n v7.5 7.5.0.6\n\nThe latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\nIf the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q069", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT08610\nREPORTED COMPONENT NAME\n WMQ BASE MULTIP\nREPORTED COMPONENT ID\n 5724H7241\nREPORTED RELEASE\n 750\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2015-04-28\nCLOSED DATE\n 2015-08-28\nLAST MODIFIED DATE\n 2018-02-06\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q069", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ BASE MULTIP\nFIXED COMPONENT ID\n 5724H7241", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q069", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "MQRC 2035 2035 MQRC_NOT_AUTHORIZED", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q069", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Starting with MQ V6, changes were done to the MQ JMS client code to provide to the MQ server the userid of the process (application) that is connecting to the MQ server using the MQ JMS client.\n\nIn this case, the MQ queue manager has received a username which either:\nDoes not exist in the host of the MQ queue manager.\nDoes exist, but it does not have the proper authority to access the MQ queue manager.", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q069", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Trace the failure to find the userid that is being sent by the MQ client to the MQ queue manager, it is necessary to capture the concurrent trace. This section provides more details.\n\nFrom the JMS Trace (trace.log) you can see the userid that is sent by the MQ Client\n\nFor example, the trace.log for the JMS client may have strings such as these:\n\ncom.ibm.mq.jms.MQQueueConnectionFactory connecting as user: JohnDoe\ncom.ibm.mq.jms.MQQueueConnection Setting username = JohnDoe\ncom.ibm.mq.MQv6InternalCommunications userID = 'JohnDoe '\ncom.ibm.mq.MQv6InternalCommunications UID :JOHNDOE\n\nFrom the MQ server trace you can see the userid that is received by the queue manager\n\nIt is very likely that one of the MQ trace files (*.FMT) will have the following string indicating that the value (username) is not a user ID in the system (unknown principal). Search for the string: UnknownPrincipal\n\nUnknownPrincipal(johndoe)\n\nAlso, in case that the userid does exist, another possible cause is that the user does not have all the proper authorizations, thus, check for the following phrase in the trace:\n\nThe following requested permissions are unauthorized\n\nObtaining traces:\n\nFor information on how to gather the traces:\n\nMQ: WebSphere MQ Queue Manager Trace (Example for Linux)\nhttp://www.ibm.com/support/docview.wss?&uid=swg21174924#UNIXlt [http://www.ibm.com/support/docview.wss?&uid=swg21174924#UNIXlt]\n\nWAS JMS: Enabling JMS trace for releases of WebSphere Application Server V5.1, V6.0, V6.1, and V7.0\nhttp://www.ibm.com/support/docview.wss?&uid=swg21199176 [http://www.ibm.com/support/docview.wss?&uid=swg21199176]", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q069", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Check which user ID the application is being run under and then check to see if that user ID either is in the \"mqm\" group (if the user is going to be an MQ Administrator) or in some other group with sufficient authority.\n\nAfter adding the userid to the group with sufficient authority, issue a runmqsc command:\nREFRESH SECURITY(*)\n\nThe user ID associated with the program when it runs must have authority to access certain resources of the queue manager. Grant the following authorities to the user ID:\nThe authority to connect to the queue manager, and the authority to inquire on the attributes of the queue manager object.\nThe authority to put and get messages on the desired queue.\n\nFor information about how to grant authorities, see the following book from the MQ online information center:\n\nMQ V7 Information Center [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp]\n\nWebSphere MQ System Administration Guide [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.amqzag.doc/fa10120_.htm]\n\nPRODUCT ALIAS/SYNONYM\n MQ WMQ MQSeries\n\nmqc8 websphere mq v8 DOWNLOADABLE FILES", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q069", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This SupportPac contains all the IBM MQ V8 client components.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q069", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Click here to skip straight to download table.\n\nA IBM MQ client is part of the product that can be installed on its own, on a separate machine from the base product and server. You can run an IBM MQ application on an IBM MQ client and it can interact, by means of a communications protocol, with one or more IBM MQ servers and connect to their queue managers. The servers to which the client connects might be part of a cluster.\n\nIBM MQ Family Platforms provides a list of which platforms are supported as IBM MQ Clients and/or Servers.\n\nAn application that you want to run in the IBM MQ client environment must first be linked with the relevant client library. When the application issues an MQI call, the IBM MQ client code directs the request to a queue manager, where it is processed and from where a reply is sent back to the client. The link between the application and the client code is established dynamically at runtime. The MQI is available to applications running on the client platform. The queues and other IBM MQ objects are held on a queue manager that you have installed on a server machine.\n\nClick here to skip straight to download table", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q069", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Possible Uses\nWhy use IBM MQ clients?\n\u00bb Using IBM MQ clients is an efficient way of implementing IBM MQ messaging and queuing.\n\u00bb You can have an application that uses the MQI running on one machine and the queue manager running on a different machine, either physical or virtual. The benefits of doing this are:\nThere is no need for a full IBM MQ implementation on the client machine.\nHardware requirements on the client system are reduced.\nSystem administration requirements are reduced.\nAn IBM MQ application, running on a client, can connect to multiple queue managers on different systems.\nAlternative channels using different transmission protocols may be used.\nWhat applications run on an IBM MQ client?\n\u00bb The full MQI is supported in the client environment and this enables almost any IBM MQ application to be relinked to run on an IBM MQ client. Link the application on the IBM MQ client to the MQIC library, rather than to the MQI library. The exceptions are:\nAn application that uses global transactions; that is, it requires sync point coordination with resource managers other than the queue manager.\nGet(signal) on z/OS.\n\u00bb Applications which are built using various programming languages including C, C++, .NET (Windows systems only), COBOL, Java and JMS.\n\u00bb Applications running within application servers that are certified as having passed the JEE 7 Compatibility Test Suite can use the IBM MQ resource adapter provided in the SupportPac. For more information see IBM MQ resource adapter v8.0 statement of support [http://www.ibm.com/support/docview.wss?uid=swg27041968]\n\nNote: An application running on an IBM MQ client can connect to more than one queue manager concurrently, or use a queue manager name with an asterisk (*) on an MQCONN or MQCONNX call. The application will have to be changed if you want to link to the queue manager libraries instead of the client libraries, because this function is not available.\n\nRELATED MESSAGE SERVICE CLIENTS\nThe IBM Message Service Client offers C/C++ users an Application Programming Interface (API) that is consistent with the Java Message Service (JMS) API. Applications created using this client can be used to exchange messages between other XMS applications, JMS applications, or native IBM MQ applications.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q069", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Please click here for more information and to download the SupportPac:\nIBM Message Service Client for C/C++ (SupportPac IA94) [http://www.ibm.com/support/docview.wss?rs=0&q1=ia94&uid=swg24007092&loc=en_US&cs=utf-8&cc=us&lang=en]\n\nSkill Level Required\nUsers should be familiar with the IBM MQ product family in general and have particular skills on the platform for which this client is intended.\n\nNew in this Release\nUpdated for IBM MQ V8.0.0.9.\n\nDetails\nAuthor: IBM MQ Development, Hursley\nCategory: 3\nReleased: 23May14\nLast updated: 12Apr18\nCurrent Version: 8.0.0.9\n\u00bbPlease note that the version number shown in the right-hand pane is the version of the IBM MQ product that this SupportPac applies to. The date is the last web page refresh.\n\nTo view the complete portfolio of IBM MQ SupportPacs please visit the IBM MQ SupportPacs homepage. [http://www-306.ibm.com/software/integration/support/supportpacs]\n\nPREREQUISITES\nThis client will interoperate with all the currently supported IBM MQ server products, provided the functions used are common to the release of server and client.\n\nNotes:\nManaged File Transfer (MFT) code is not provided in this SupportPac.\n\nIBM has withdrawn the download of the MQ Client for HP NonStop Server. As IBM has stated in a Statement of Direction ( https://ibm.biz/MQ-SoD-Nov2014 [https://ibm.biz/MQ-SoD-Nov2014]) there is an intent to deliver an updated version of IBM MQ for the HP NonStop Server platform as this should be a better solution to meet the MQ connectivity needs for most customers on the HP NonStop Server platform. In common with other IBM MQ platforms, MQ Clients that run on other platforms will continue to provide connectivity to IBM MQ Servers on the HP NonStop platform and other MQ Server supported platforms.\n\nTo gain an early look at the intended release of IBM MQ V8 for HP NonStop Server please join the beta program by contacting your IBM sales representative.\n\nINSTALLATION INSTRUCTIONS\nTo install a Unix Client:\n1. Logon as root, create an empty directory (with sufficient space to receive the download file) and make it current.\n2. Download mqc8_platform to this directory. (Where 'platform' is replaced with a specific platform name e.g. AIX, Linux-x86)\n3. Uncompress mqc8_platform.\n4. Execute tar -xvf mqc8_platform.\n5. Execute rm mqc8_platform.\n6. Follow the instructions provided in the IBM MQ V8 Knowledge Center to complete the installation of the client.", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q069", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "To install the client on a Windows machine download the zip file and extract the content. From the Windows subdirectory created run the setup.exe program.\n\nURL LANGUAGE SIZE(Bytes) IBM MQ 8.0: Installing and Uninstalling [http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ins.doc/q008250_.htm] US English 111\nDOWNLOAD PACKAGE\n** ATTENTION : 8.0.0.4 and earlier packages: Install image vulnerability alert - see http://www.ibm.com/support/docview.wss?uid=swg21978363 [http://www.ibm.com/support/docview.wss?uid=swg21978363] for mitigation steps. Contact IBM Support with questions. ***\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 8.0.0.9 Client 12 Apr 2018 US English 111 FC [http://ibm.biz/mq8009clients] [ ] 8.0.0.8 Client 30 Nov 2017 US English 111 FC [http://ibm.biz/mq8008clients] [ ] 8.0.0.7 Client 10 Jul 2017 US English 111 FC [http://ibm.biz/mq8007clients] [ ] 8.0.0.6 Client 31 Jan 2017 US English 111 FC [http://ibm.biz/FixPackMQ8006 ] [ ] 8.0.0.5 Client 25 May 2016 US English 111 FC [http://ibm.biz/mq8005aclients] [ ] 8.0.0.4 Client 23 Oct 2015 US English 111 FC [https://ibm.biz/mq8004clients] [ ] 8.0.0.3 Client 18 Jun 2015 US English 111 FC [https://ibm.biz/mq8003clients] [ ] 8.0.0.2 Client 27 Feb 2015 US English 111 FC [https://ibm.biz/mq8002clients] [ ] 8.0.0.1 Client 16 Sep 2014 US English 111 FC [http://ibm.biz/mq8001clients] [ ] 8.0.0.0 Client 23 May 2014 US English 111 FC [https://ibm.biz/mq8000clients] [ ]\nTECHNICAL SUPPORT\n Category 3 IBM MQ SupportPacs are supplied under the standard terms and conditions provided by the International Program License Agreement (IPLA) and thus, carry program defect service for IBM MQ customers. Please read the IPLA and LI files that accompany the SupportPac, to ensure you understand the conditions under which the SupportPac is provided.\n\nIf you encounter what you believe to be a defect with the SupportPac, and you have a current license for a IBM MQ server product, you may request Program Services by reporting the problem via the same defect reporting channel you employ for the IBM MQ server product(s) on which you are using the SupportPac. No proof of entitlement is required to use this SupportPac.\n\nService is available for the v8 version of this SupportPac for as long as the IBM MQ V8 server product is supported by service. Refer to the IBM MQ product lifecycle pages for the relevant service information. It is only supported with MQ platforms which are themselves supported.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q069", "section_id": 2, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "WebSphere MQ V7.0 Fix Pack 7.0.1.10 [http://www-01.ibm.com/support/docview.wss?uid=swg24034145]\nWebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.10 [http://www-01.ibm.com/support/docview.wss?uid=swg24034909]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q069", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "An application using the WebSphere MQ V7.0.1 classes for JMS is\n connected to a WebSphere MQ V7.0.1 queue manager using the\n CLIENT transport.\n\nWhen the runmqsc command:\n\nDISPLAY CHSTATUS(channel name)\n\nis run on the queue manager for the channel that the\n application has used to connect to the queue manager, the\n following output is displayed:\n\nRVERSION(00000000)\n RPRODUCT(MQJM)", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q069", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n This issue affects two categories of user:\n\n 1. Users of the WebSphere MQ command runmqsc who run:\n\n DISPLAY CHSTATUS(channel name)\n\n to display the status of a channel.\n\n 2. Users of the WebSphere MQ Explorer who display the status of\n a Channel by highlighting a Channel in the Channels pane, right\n clicking and selecting Status->Channel Status... from the pop-\n up menu.\n\n Platforms affected:\n All Distributed (iSeries, all Unix and Windows)\n\n PROBLEM SUMMARY:\n Applications that connect to WebSphere MQ using the CLIENT\n transport provide version information to the queue manager\n about the level of WebSphere MQ Client code that the\n application is running. This version information is in the\n format:\n\n VVRRMMFF\n\n where:\nVV = Version\nRR = Release\nMM = Maintenance level\nFF = Fix level\n\n The runmqsc command:\n\n DISPLAY CHSTATUS(channel name)\n\n will report this version information in the RVERSION attribute.\n\n The WebSphere MQ Explorer shows the version information in the:\n\n Remote Version\n\n column in the Channel Status window.\n\n In order to determine the version information to pass to a\n queue manager, the WebSphere MQ V7.0.1 classes for Java and\n classes for JMS, and the WebSphere MQ V7.0.1 Resource Adapter,\n looked inside the MANIFEST.MF file contained within the file:\n\n com.ibm.mq.jmqi.jar\n\n for the property:\n\n version\n\n However, the MANIFEST.MF file did not contain an entry for this\n property. This caused the WebSphere MQ classes for Java and\n classes for JMS, and the WebSphere MQ Resource Adapter,to\n specify:\n\n 00000000\n\n as the version number being used.", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q069", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The WebSphere MQ V7.0.1 classes for Java and classes for JMS,\n and the WebSphere MQ V7.0.1 Resource Adapter, have been updated\n to use the information in the property:\n\n com.ibm.mq.jmqi\n\n within the MANIFEST.MF file contained within the JAR file:\n\n com.ibm.mq.jmqi.jar\n\n to determine what version information to pass to the queue\n manager.\n\n Applications using the WebSphere MQ Resource Adapter or Java\n and JMS clients which have this APAR applied will report\n their version information correctly to the queue manager,\n which will be reflected in the information returned by\n runmqsc and the MQ Explorer.\n\n The fix is targeted for delivery in the following PTFs:\n\n v7.0\n Platform Fix Pack 7.0.1.10\n------- --------------------\n Windows U200352\n AIX U853055\n HP-UX (PA-RISC) U853082\n HP-UX (Itanium) U853087\n Solaris (SPARC) U853083\n Solaris (x86-64) U853089\n iSeries 7.0.1.10\n Linux (x86) U853084\n Linux (x86-64) U853088\n Linux (zSeries) U853085\n Linux (Power) U853086\n\n The latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\n If the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q069", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC89770\nREPORTED COMPONENT NAME\n WMQ WINDOWS V7\nREPORTED COMPONENT ID\n 5724H7220\nREPORTED RELEASE\n 701\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-01-23\nCLOSED DATE\n 2013-01-24\nLAST MODIFIED DATE\n 2013-02-13\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q069", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ WINDOWS V7\nFIXED COMPONENT ID\n 5724H7220", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q069", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R701 PSY\n UP", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q163", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q163", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Pri Key generation with autotracking can cause a the server to\n stop processing the BPD processes. Symptoms in the logs are\n repeated lock wait timeout such as the following:\n\n CWLLG2068E: An unexpected exception occurred during an attempt\n to generate the next primary key. Error:\n org.springframework.jdbc.BadSqlGrammarException:\n PreparedStatementCallback; bad SQL grammar [select high_key from\n lsw_pri_key where table_id=? for update]; nested exception is\n java.sql.\n SQLSyntaxErrorException: ORA-02049: timeout: distributed\n transaction waiting for lock\n\n One DB2, the exception would look like this:\n [3/15/16 6:59:34:055 EDT] 0001ca7f wle E CWLLG2068E:\n An unexpected exception occurred during an attempt to generate\n the next primary key. Error:\n com.lombardisoftware.core.TeamWorksRuntimeException:\n [jcc][t4][2041][11392][4.11.69] Error executing\n XAResource.start(). Server returned XAER_PROTO.\n ERRORCODE=-4203, SQLSTATE=null\n\n com.lombardisoftware.core.TeamWorksRuntimeException:\n [jcc][t4][2041][11392][4.11.69] Error executing\n XAResource.start(). Server returned XAER_PROTO.\n ERRORCODE=-4203, SQLSTATE=null\n at\n com.lombardisoftware.server.ejb.pk.PKGeneratorCore.getNextHighIn\n ternal(PKGeneratorCore.java:156)\n at\n com.lombardisoftware.server.ejb.pk.PKGeneratorCore.access$000(PK\n GeneratorCore.java:42)\n at\n com.lombardisoftware.server.ejb.pk.PKGeneratorCore$1.call(PKGene\n ratorCore.java:95)\n at\n com.lombardisoftware.server.ejb.pk.PKGeneratorCore$1.call(PKGene\n ratorCore.java:93)\n at\n com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo\n rt$1.doInTransaction(ProgrammaticTransactionSupport.java:436)\n at\n org.springframework.transaction.jta.WebSphereUowTransactionManag\n er$UOWActionAdapter.run(WebSphereUowTransactionManager.java:306)\n at\n com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.runUnderNewUO\n W(EmbeddableUOWManagerImpl.java:790)\n at\n com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.runUnderUOW(E\n mbeddableUOWManagerImpl.java:369)\n at\n org.springframework.transaction.jta.WebSphereUowTransactionManag\n er.execute(WebSphereUowTransactionManager.java:252)\n at\n com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo\n rt.executeInNewTransaction(ProgrammaticTransactionSupport.java:4\n 31)\n at\n com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo\n rt.execute(ProgrammaticTransactionSupport.java:294)\n at\n com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo\n rt.execute(ProgrammaticTransactionSupport.java:225)\n at\n com.lombardisoftware.server.ejb.pk.PKGeneratorCore.getNextHigh(P\n KGeneratorCore.java:91)", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q163", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Pri Key generation with autotracking can cause the server to\n stop processing the BPD processes.\n Symptoms in the logs are repeated lock wait timeout such as the\n following:\n\n CWLLG2068E: An unexpected exception occurred during an attempt\n to generate the next primary key.\n Error: org.springframework.jdbc.BadSqlGrammarException:\n PreparedStatementCallback; bad SQL grammar\n [select high_key from lsw_pri_key where table_id=? for update];\n nested exception is\n java.sql.SQLSyntaxErrorException: ORA-02049: timeout:\n distributed transaction waiting for lock", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q163", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Problem fixed\n iFix available on top of V7501\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q163", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR42463\nREPORTED COMPONENT NAME\n BPM STANDARD\nREPORTED COMPONENT ID\n 5725C9500\nREPORTED RELEASE\n 750\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2012-04-05\nCLOSED DATE\n 2012-07-09\nLAST MODIFIED DATE\n 2016-03-15\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q163", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM STANDARD\nFIXED COMPONENT ID\n 5725C9500", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q163", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R750 PSY\n UP\n\nz/os SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q163", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "A xa_start was failed with XAER_RMFAIL, If you implemented XA\n transactions as below.\n\nGlobal transaction\n Local transaction\n Global transaction\n\nFor example.\n 1st global transaction was failed SQL0911N with RC=68\n (Locktimeout).\n There is no diaglog messages.\n\n2nd global transaction was failed in xa_start with XAER_RMFAIL\n and recorded the following entry in db2diag.log.\n 2013-05-28-10.14.57.234656+540 I8893830A527 LEVEL: Error\n PID : 8126774 TID : 10309 PROC :\n db2sysc 0\n INSTANCE: db2inst1 NODE : 000 DB :\n SAMPLE\n APPHDL : 0-54 APPID:\n 192.168.1.1.64777.130528011455\n AUTHID : DB2INST1 HOSTNAME: host1\n EDUID : 10309 EDUNAME: db2agent (SAMPLE) 0\n FUNCTION: DB2 UDB, relation data serv, sqlrxreg, probe:1\n RETCODE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT\n \"SQLCA has already been built\"\n\nHere is a scenario that 2nd global transaction was fail.\n\n1st global transaction was failed with -911.\n Then xa_end and xa_rollback was executed.\n Usually, we need to switch out of the xa_tranasction.\n However, we do not do switch out of the xa_transaction.\n So, 1st transaction is still xa transaction mode.\n\nLocal transaction which is not in xa transaction.\n Because local transaction is not needed with xa_start.\n When local transaction was completed, the xa_commit was executed\n in the local transaction.\n In this time, xa_commit was returned XAER_RMFAIL.\n\n[jcc][t4][2041][11392][3.63.123] Error executing\n XAResource.commit(). Server returned XAER_RMFAIL.\n ERRORCODE=-4203, SQLSTATE=null\n\n2nd global transaction was executing xa_start.\n The xa_start was failed XAER_RMFAIL.\n Because 1st transaction is in the xa_transaction.\n And local transaction was executed xa_commit, evenif this is a\n local transaction.\n\nThe fix is to switch out of the xa transaction during xa_failure\n when the transaction is due to -911 error.\n\nAfter fixed, transaction was executed as below.\n\n1st global transaction was failed with -911.\n 1st global transaction is switched out of the xa_transaction.\n Now, xa_transaction was completed.\n\nThe local transaction was executed.\n No xa_commit was executed.\n Because 1st global transaction was completed,\n and this is not a xa_transaction.\n\n2nd global transaction was not failed in xa_start.\n 2nd xa_transaction was successfully without xa error.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q163", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nALL *\n\nPROBLEM DESCRIPTION: *\nSee Error Description *\n\nRECOMMENDATION: *\nUpgrade to DB2 UDB to version 10.1 fix pack 2. *", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q163", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Problem was first fixed in DB2 UDB Version 10.1 FixPack 2\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q163", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC92643\nREPORTED COMPONENT NAME\n DB2 FOR LUW\nREPORTED COMPONENT ID\n DB2FORLUW\nREPORTED RELEASE\n A10\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-05-28\nCLOSED DATE\n 2013-06-25\nLAST MODIFIED DATE\n 2013-06-25\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q163", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n DB2 FOR LUW\nFIXED COMPONENT ID\n DB2FORLUW", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q163", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "RA10 PSN\n UP\n\nz/os FIXES ARE AVAILABLE\nDB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24032754]\nDB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24031181]\nDB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24033685]\nDB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24034634]\nDB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24036646]\nDB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24037559]\nDB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24038641]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q163", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The JCC driver retries a batch statement if all the following\n conditions are met when the client re-route kicked in\nthe connection is not in a transaction , the failure occurs\n when the first SQL statement in the transaction is executed.\nthere are no open, held cursors after commit\nthere is no input stream associated with the prepared\n statement", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q163", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Even if all the previous conditions are met, the JCC driver\n doesn't retry the batch statement after a client re-route.\n Instead, you will see in your JCC traces, an error message like\n the following :\n [jcc][t4]\n [time:2011-04-30-11:50:52.617][Thread:Application_Thread[impl:3]\n _1][tracepoint:400]Client Re-route to client affinities\n server[0]: HOST1 - 5036\n [jcc][t4]\n [time:2011-04-30-11:50:52.617][Thread:Application_Thread[impl:3]\n _1][tracepoint:100]Client Re-route: Trying connection to HOST1\n at port 5036\n ....\n [jcc] BEGIN TRACE_DIAGNOSTICS\n [jcc][Thread:Application_Thread[impl:3]_1][SQLException@74205d55\n ] java.sql.SQLException\n [jcc][Thread:Application_Thread[impl:3]_1][SQLException@74205d55\n ] SQL state = 08506\n [jcc][Thread:Application_Thread[impl:3]_1][SQLException@74205d55\n ] Error code = -4498\n [jcc][Thread:Application_Thread[impl:3]_1][SQLException@74205d55\n ] Message = [jcc][t4][2027][11212][3.61.75] A connection\n failed but has been re-established. The host name or IP address\n is \"HOST1\" and the service name or port number is 5,036.\n Special registers may or may not be re-attempted (Reason code =\n 2). ERRORCODE=-4498, SQLSTATE=08506\n [jcc][Thread:Application_Thread[impl:3]_1][SQLException@74205d55\n ] Stack trace follows\n com.ibm.db2.jcc.am.ClientRerouteException:\n [jcc][t4][2027][11212][3.61.75] A connection failed but has been\n re-established. The host name or IP address is \"HOST1\" and the\n service name or port number is 5,036.\n Special registers may or may not be re-attempted (Reason code =\n 2). ERRORCODE=-4498, SQLSTATE=08506\n at com.ibm.db2.jcc.am.ed.a(ed.java:304)\n at com.ibm.db2.jcc.am.ed.a(ed.java:356)\n at com.ibm.db2.jcc.t4.a.a(a.java:476)\n at com.ibm.db2.jcc.t4.a.L(a.java:1039)\n at com.ibm.db2.jcc.t4.a.a(a.java:913)\n at com.ibm.db2.jcc.t4.z.b(z.java:231)\n at com.ibm.db2.jcc.t4.z.c(z.java:259)\n at com.ibm.db2.jcc.t4.z.c(z.java:372)\n at com.ibm.db2.jcc.t4.z.v(z.java:1147)\n at com.ibm.db2.jcc.t4.cb.a(cb.java:60)\n at com.ibm.db2.jcc.t4.q.a(q.java:50)\n at com.ibm.db2.jcc.t4.sb.b(sb.java:228)\n at com.ibm.db2.jcc.am.hn.mc(hn.java:2924)\n at com.ibm.db2.jcc.am.hn.a(hn.java:4929)\n at com.ibm.db2.jcc.am.hn.a(hn.java:4271)\n at com.ibm.db2.jcc.am.hn.c(hn.java:4130)\n at com.ibm.db2.jcc.t4.l.c(l.java:78)\n at com.ibm.db2.jcc.am.hn.executeBatch(hn.java:2447)\n ....\n [jcc] BEGIN TRACE_DIAGNOSTICS\n [jcc][Thread:Application_Thread[impl:3]_1][SQLException@78cfb302\n ] java.sql.SQLException\n [jcc][Thread:Application_Thread[impl:3]_1][SQLException@78cfb302\n ] SQL state = null\n [jcc][Thread:Application_Thread[impl:3]_1][SQLException@78cfb302\n ] Error code = -4225\n [jcc][Thread:Application_Thread[impl:3]_1][SQLException@78cfb302\n ] Message = [jcc][t4][103][10843][3.61.75] Non-recoverable\n chain-breaking exception occurred during batch processing. The\n batch is terminated non-atomically. ERRORCODE=-4225,\n SQLSTATE=null\n [jcc][Thread:Application_Thread[impl:3]_1][SQLException@78cfb302\n ] Stack trace follows\n com.ibm.db2.jcc.am.SqlException: [jcc][t4][103][10843][3.61.75]\n Non-recoverable chain-breaking exception occurred during batch\n processing. The batch is terminated non-atomically.\n ERRORCODE=-4225, SQLSTATE=null\n at com.ibm.db2.jcc.am.ed.a(ed.java:660)\n at com.ibm.db2.jcc.am.ed.a(ed.java:60)\n at com.ibm.db2.jcc.am.ed.a(ed.java:120)\n at com.ibm.db2.jcc.am.hn.a(hn.java:4310)\n at com.ibm.db2.jcc.am.hn.c(hn.java:4130)\n at com.ibm.db2.jcc.t4.l.c(l.java:78)\n at com.ibm.db2.jcc.am.hn.executeBatch(hn.java:2447)\n ....\n [jcc] END TRACE_DIAGNOSTICS\n [jcc] BEGIN TRACE_DIAGNOSTICS\n [jcc][Thread:Application_Thread[impl:3]_1][BatchUpdateException@\n bf18645] java.sql.BatchUpdateException\n [jcc][Thread:Application_Thread[impl:3]_1][BatchUpdateException@\n bf18645] SQL state = null\n [jcc][Thread:Application_Thread[impl:3]_1][BatchUpdateException@\n bf18645] Error code = -4229\n [jcc][Thread:Application_Thread[impl:3]_1][BatchUpdateException@\n bf18645] Message = [jcc][t4][102][10040][3.61.75] Batch\n failure. The batch was submitted, but at least one exception\n occurred on an individual member of the batch.\n Use getNextException() to retrieve the exceptions for specific\n batched elements. ERRORCODE=-4229, SQLSTATE=null\n [jcc][Thread:Application_Thread[impl:3]_1][BatchUpdateException@\n bf18645] Update counts = { -3, -3 }\n [jcc][Thread:Application_Thread[impl:3]_1][BatchUpdateException@\n bf18645] Stack trace follows\n com.ibm.db2.jcc.am.BatchUpdateException:\n [jcc][t4][102][10040][3.61.75] Batch failure. The batch was\n submitted, but at least one exception occurred on an individual\n member of the batch.\n Use getNextException() to retrieve the exceptions for specific\n batched elements. ERRORCODE=-4229, SQLSTATE=null\n at com.ibm.db2.jcc.am.ed.a(ed.java:404)\n at com.ibm.db2.jcc.am.o.a(o.java:365)\n at com.ibm.db2.jcc.am.hn.a(hn.java:4347)\n at com.ibm.db2.jcc.am.hn.c(hn.java:4130)\n at com.ibm.db2.jcc.t4.l.c(l.java:78)\n at com.ibm.db2.jcc.am.hn.executeBatch(hn.java:2447)\n ....\n [jcc] END TRACE_DIAGNOSTICS", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q163", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Fixed in IBM Data server driver for JDBC& SQLJ for DB2 on LUW\n V9.7 Fix Pack 7.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q163", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Upgrade IBM Data server driver for JDBC& SQLJ for DB2 on LUW\n V9.7 Fix Pack 7 or above.\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q163", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC77293\nREPORTED COMPONENT NAME\n DB2 CONNECT\nREPORTED COMPONENT ID\n DB2CONNCT\nREPORTED RELEASE\n 970\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2011-07-01\nCLOSED DATE\n 2014-04-04\nLAST MODIFIED DATE\n 2014-04-04\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n IC77895", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q163", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n DB2 CONNECT\nFIXED COMPONENT ID\n DB2CONNCT", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q163", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R970 PSY\n UP\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q163", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Activation of locking even monitor can fail with SQL204 and\n SQL1619 if OPM objects were not cleared from the monitored\n database, if case the OPM server was killed or abnormally\n terminated during locking event monitoring initialization.\n The lock events are not collected anymore.\n .\n Fix: Locking monitoring component will do the necessary cleaning\n during initialization.\n .\n Possible errors in OPM Server traces:\n EXCPMon-1 LockMonInst.\n com.ibm.db2pm.server.lockmon.LockMonitorInternalException: Error\n during unit of work monitor activation on db db name\n Caused by: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL\n Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=OPMNORBH4J2,\n DRIVER=3.59.81\n .\n Internall error during monitor creation. Monitor was not\n created.\n .\n EXCPMon-1 LockMonitor com.ibm.db2.jcc.am.SqlException:\n DB2 SQL Error: SQLCODE=-1619, SQLSTATE=55034, SQLERRMC=null,\n DRIVER=3.59.81", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q163", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Connect to the monitored database and drop the event monitors\n created by OPM, with names matching OPMN*.\n Drop unformatted event tables which names matching OPMN* created\n by event monitors, which belong to schema \"OPM\".", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q163", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "OPTIM PERFORMANCE MANAGER - LOCK EVENT MONITORING START FAILS\n WITH SQL -204 AFTER ABNORMAL TERMINATION.\n .\n Activation of locking even monitor can fail with SQL204 and\n SQL1619 if OPM objects were not cleared from the monitored\n database, if case the OPM server was killed or abnormally\n terminated during locking event monitoring initialization.\n The lock events are not collected anymore.\n .\n Fix: Locking monitoring component will do the necessary cleaning\n during initialization.\n .\n Possible errors in OPM Server traces:\n EXCPMon-1 LockMonInst.\n com.ibm.db2pm.server.lockmon.LockMonitorInternalException: Error\n during unit of work monitor activation on db db name\n Caused by: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL\n Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=OPMNORBH4J2,\n DRIVER=3.59.81\n .\n Internall error during monitor creation. Monitor was not\n created.\n .\n EXCPMon-1 LockMonitor com.ibm.db2.jcc.am.SqlException:\n DB2 SQL Error: SQLCODE=-1619, SQLSTATE=55034, SQLERRMC=null,\n DRIVER=3.59.81", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q163", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Install Optim Performance Manager release 4.1.1.0\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q163", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PK99960\nREPORTED COMPONENT NAME\n OPT PER MGR DB2\nREPORTED COMPONENT ID\n 5724Y9400\nREPORTED RELEASE\n 410\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2011-03-30\nCLOSED DATE\n 2011-07-11\nLAST MODIFIED DATE\n 2011-07-11\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q163", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n OPT PER MGR DB2\nFIXED COMPONENT ID\n 5724Y9400", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q163", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R410 PSY\n UP\n\nz/os SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q163", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Following frequent error messages may be observed with a\n multithreaded DB2 client application\n that uses JCC:T4 JDBC driver.\n\n .\n\n Exception in thread \"Thread-3\" java.lang.RuntimeException:\n com.ibm.db2. jcc.am.SqlException Caught\n java.io.CharConversionException. ERRORCODE=-4220\n\n The programs fails with the following error :\n\n Exception in thread \"Thread-1\" Exception in thread \"Thread-0\"\n java.lang.RuntimeE\n xception: com.ibm.db2.jcc.am.\n\n SqlException: [jcc][t4][1065][12547][3.63.75] Caugh\n t java.io.CharConversionException. See attached Throwable for\n details. ERRORCOD\n E=-4220, SQLSTATE=null\n at ThreadingDB2v9$1.run(ThreadingDB2v9.java:48)\n Caused by: com.ibm.db2.jcc.am.SqlException:\n [jcc][t4][1065][12547][3.63.75] Caug\n ht java.io.CharConversionException. See attached Throwable for\n details. ERRORCO\n DE=-4220, SQLSTATE=null\n at com.ibm.db2.jcc.am.fd.a(fd.java:663)\n at com.ibm.db2.jcc.am.fd.a(fd.java:60)\n at com.ibm.db2.jcc.am.fd.a(fd.java:112)\n at com.ibm.db2.jcc.am.ic.a(ic.java:2318)\n at com.ibm.db2.jcc.am.ic.p(ic.java:521)\n at com.ibm.db2.jcc.am.ic.X(ic.java:2193)\n at com.ibm.db2.jcc.am.nn.f(nn.java:1438)\n at com.ibm.db2.jcc.am.nn.getObject(nn.java:1413)\n at ThreadingDB2v9$1.run(ThreadingDB2v9.java:40)\n Caused by: java.nio.BufferOverflowException\n at com.ibm.db2.jcc.am.t.a(t.java:24)\n at com.ibm.db2.jcc.am.ic.a(ic.java:2310)\n ... 5 more\n Caused by: sun.io.ConversionBufferFullException\n at sun.io.ByteToCharUTF8.convert(Unknown Source)\n at com.ibm.db2.jcc.am.t.a(t.java:16)\n ... 6 more\n java.lang.RuntimeException: com.ibm.db2.jcc.am.SqlException:\n [jcc][t4][1065][125\n 47][3.63.75] Caught java.io.CharConversionException. See\n attached Throwable for\n details. ERRORCODE=-4220, SQLSTATE=null\n at ThreadingDB2v9$1.run(ThreadingDB2v9.java:48)\n Caused by: com.ibm.db2.jcc.am.SqlException:\n [jcc][t4][1065][12547][3.63.75] Caught\n java.io.CharConversionException. See attached Throwable for\n details. ERRORCODE=-4220, SQLSTATE=null\n at com.ibm.db2.jcc.am.fd.a(fd.java:663)\n at com.ibm.db2.jcc.am.fd.a(fd.java:60)\n at com.ibm.db2.jcc.am.fd.a(fd.java:112)\n at com.ibm.db2.jcc.am.ic.a(ic.java:2318)\n at com.ibm.db2.jcc.am.ic.p(ic.java:521)\n at com.ibm.db2.jcc.am.ic.X(ic.java:2193)\n at com.ibm.db2.jcc.am.nn.f(nn.java:1438)\n at com.ibm.db2.jcc.am.nn.getObject(nn.java:1413)\n at ThreadingDB2v9$1.run(ThreadingDB2v9.java:40)\n Caused by: java.nio.BufferOverflowException\n at com.ibm.db2.jcc.am.t.a(t.java:24)\n at com.ibm.db2.jcc.am.ic.a(ic.java:2310)\n ... 5 more\n Caused by: sun.io.ConversionBufferFullException\n at sun.io.ByteToCharUTF8.convert(Unknown Source)\n at com.ibm.db2.jcc.am.t.a(t.java:16)\n ... 6 more\n\n NOTE:\n This issue happens with only Oracle Java and not with IBM java.", "logical_doc_id": 5, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q163", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nUser prior for v9.7 fp 9 version *\n\nPROBLEM DESCRIPTION: *\nSee Error Description *\n\nRECOMMENDATION: *\nPlease upgrade to latest fix pack v9.7 fix pack 7 *", "logical_doc_id": 5, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q163", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC82934\nREPORTED COMPONENT NAME\n DB2 FOR LUW\nREPORTED COMPONENT ID\n DB2FORLUW\nREPORTED RELEASE\n 970\nSTATUS\n CLOSED FIN\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2012-04-26\nCLOSED DATE\n 2012-12-03\nLAST MODIFIED DATE\n 2012-12-03\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q163", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R970 PSY\n UP", "logical_doc_id": 5, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q033", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "datapower; 7993; machine type 7993; logging; off device; off device logging; log target; off-device; syslog; debug log level; debug; log level TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q033", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "The DataPower device has a finite amount of space to hold larger than average log files or long term logging needs in production environment.\n\nIt should be noted that if used while debugging at load or in a capacity issue, log events may be dropped. There is a prioritization of events within the device and client traffic always comes first. Log events dropped can be confirmed or counted from the Status>Log Targets menu in the WebGUI.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q033", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Configure a server daemon to listen and capture the DataPower devices events. First, this example shows how to create the log target sending events to a syslog destination. The other examples listed below will have their own strong points to be considered depending on the problem scenario.\n\nSyslog:\nThe syslog protocol operates over UDP which has no guarantee on packet delivery - a fast fire and forget method.\n\nTo create the new log target, go into the default domain: Objects > Log Targets\n\nConfigure the log target with settings as follows from the WebGUI:\n\n1. Name the log target\n 2. Select Target Type of syslog\n 3. Fill in the Local Identifier with a descriptive string that may be used by a remote recipient to identify this specific log target\n 4. Enter the Remote Host Address and the Remote IP Port as in the screen shot wherex.x.x.x is the IP address of the remote syslog server that listens on port 514\n 5. Take all other defaults\n\n[/support/docview.wss?uid=swg21269136&aid=1] [/support/docview.wss?uid=swg21269136&aid=1]\n\nUnder the Event Subscriptions tab, you can select all and debug as indicated here:\n\n[/support/docview.wss?uid=swg21269136&aid=2] [/support/docview.wss?uid=swg21269136&aid=2]\n* 6. Generate log events in the DataPower by using some transactions, for example by saving the configuration from the WebGUI or running some test load into a domain.\n\nSyslog-ng, will simply work over the TCP protocol to ensure the packet is delivered to the destination. The same consideration should be applied to a device under high load in that a log event could be dropped if not able to be wrote out to the network within time.\n\nNFS:\nAll NFS limitations apply from file size and permission settings. This is a more common approach using an NFS static mount to capture a log target and can allow for slightly more reliable messages to be logged. The limiting factor again is the speed of the network and NFS server response time.\n\nFile type:", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q033", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Using a file type log target with a backup method as seen here:\n[/support/docview.wss?uid=swg21269136&aid=3] [/support/docview.wss?uid=swg21269136&aid=3]\nThis will allow log events to quickly be written to a local file on the device's file system. Once the file reaches its set size a connection to the destination will upload the file from the device. This will upload with a unique time and date stamp on the uploaded file.\n\nThis is a useful method to capture sporadic problems. This is also useful for long running transactions that may span more than one file depending on device load.\n\nHTTP service:\nFinally a clever method that may be used in some senarios would be an HTTP service on the device.\nUsing an HTTP service configured in the following way,\n[/support/docview.wss?uid=swg21269136&aid=4] [/support/docview.wss?uid=swg21269136&aid=4]\n\nOnce the file type log is created in the logtemp:/// directory, a client browser or wget type client can easily retrieve the file from the device.\n\nThis is very useful when there is no local or accessible remote log storage location to the device, due to firewall or network restrictions.\n\nThis is also removing the limitation of the device dropping the log event should it not be able to write the log event to the network.\n\nEach of the above methods are very useful and work better in some scenarios than others depending on the network, load, problem, and information needed. This is intended to be a guide to help you decide which method would be best for your scenario.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q033", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What timeout values are used in specific configuration examples for WebSphere DataPower SOA Appliances?", "logical_doc_id": 2, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q033", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Specific connection methods may use different timeout values:\n\nHTTP\n\nThe HTTP protocol through services such as Web Service Proxy, Multi-Protocol Gateway, etc. The url-open() and the Results Action have the same timeout behavior:\n\nTimeout Behavior Response The User Agent timeout takes precedence even with a lower Back Side Timeout, when waiting on a response from the back side server. Persistent The persistent connection timeout is controlled by a 15-second timer that is not user accessible. Even with a lower Back Persistent Timeout, the 15-second timeout will take precedence.\nNote:\n* The var://service/routing-url and Static Backend have the same timeout behavior.\n\nTimeout Behavior Response Uses the Back Side Timeout Persistent Uses the Back Persistent Timeout.\n\nSQL\n\nFor the SQL Data Source, the User Agent timeout will fail the transaction only and a log event will be thrown. This has no direct control or change in the TCP connections between the DataPower device and database server. The actual connections from the device to the database server have no user-configurable timeouts.\n\nMQ\n\nThe MQ protocol will use the following options for response timeout.\n* Note:\nThe url-open() and Results Action have the same timeout behavior. The var://service/routing-url and Static Backend URL have the same timeout behavior.\n\nTimeout Behavior Response When the Timeout option is set on the url string, it will take precedence over the User Agent Timeout even if the User Agent is set to a lower Timeout value. The User Agent Timeout will be used if no Timeout option is set. Persistent Also known as the connection reuse timeout. This timeout is determined by the Cache Timeout value in the MQ Queue Manager.\nLog Target\n\nLog target connections have no timeout options for the TCP-based methods such as SOAP and Syslog-ng. To limit total connections from the log target, the Rate Limit setting must be tuned.", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q033", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "I forwarded my Syslog events to QRadar, but I do not see any events on the Log Activity tab. How can I use the command-line to troubleshoot event issues?", "logical_doc_id": 3, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q033", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Administrators can troubleshoot if syslog events are being received by QRadar using several tools built in to the QRadar appliance. A common technique used to prove data is being received by the appliance interface is to use a utility called tcpdump. This utility allows the administrator to define the interface, port, source or destination IP addresses for the syslog data being sent and writes the packet data on-screen to help users determine if events are received by QRadar.\n\nBEFORE YOU BEGIN\nBefore you can troubleshoot if the events are sent to QRadar, you need to review the event source sending Syslog events and verify the IP address. The Syslog destination configured on your device is where you need to troubleshoot. The tcpcump command must be run on the appliance receiving the events from your device.\n\nNote: By default, QRadar appliances are always configured to listen for Syslog events on TCP and UDP port 514. There is no need to touch the firewall on your QRadar appliance.\n\nTROUBLESHOOTING EVENTS WITH TCPDUMP\nThe following command allows administrators to review the full Syslog header for events coming from a remote Syslog source.\n\n1. Using SSH, log in to your QRadar Console as root.\n 2. Optional. If the Syslog destination is another appliance, such as an Event Collector appliance, SSH to the event collector.\n 3. Type one of the following command: 1. For TCP Syslog, type: tcpdump -s 0 -A host Device_Address and port 514\n 2. For UDP Syslog, type: tcpdump -s 0 -A host Device_Address and udp port 514\n\nNote: Device_Address must be an IPv4 address or a host name.\n For example, tcpdump -s 0 -A host 8.8.8.8 and port 514.\n\nPOSSIBLE RESULTS\n\n1. I do not see any events\n\nIf you do not see any events in the command line, then is is likely that either the device is not sending Syslog events or there is a firewall blocking communication.\nVerify with your firewall administrator or operations group if any firewalls are blocking communication between the QRadar appliance and the device sending Syslog events.", "logical_doc_id": 3, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q033", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Typically, an easy method to verify if a TCP port is open is to telnet from QRadar to the device. From the QRadar command line, type telnet Device_IPAddress 514.\n Review the Syslog configuration of your remote device to ensure that it is configured to send events to the appropriate QRadar appliance.\n If the remote appliance is Linux/UNIX-based, administrators can verify the event source is sending data to the QRadar appliance with the following command: tcpdump dst QRadar_Appliance_IPAddress\n\n2. The command line is listing events from my device\n\nThe tcpdump command displays results with the full Syslog header and event payloads, which is why we recommend to use the -A flag when troubleshooting events.\n\n1. Review your system notifications.\n\nWhen QRadar cannot automatically discover a log source, then a system notification is created. Administrators can review the hostname or IP address outlined in the system notification to determine what address QRadar thinks is the source address for the log source. Manually creating a log source is typically required. The Log Source Identifier field might need to be updated with the either a host name or IP address depending on what the System Notification indicates.\n\n2. Verify if the device supports automatic discovery in QRadar.\n\nThe DSM Configuration Guide has an appendix that lists what Device Support Modules (DSMs) allow automatic log source creation. For more information, see the DSM Configuration Guide: Master documentation link list on the QRadar Customer Forum [https://www.ibm.com/developerworks/community/forums/html/topic?id=72952d0f-54dd-4539-ba42-a9110567987a&ps=25].\n\n3. The Syslog header might include an unexpected IP address or the log source is misconfigured.", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q033", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "When reviewing the tcpdump results, administrators should note the hostname in the Syslog header. If there is no hostname in the syslog header then note the packet IP address. From the Admin tab of your QRadar Console, open the Log Sources window and search for the hostname or IP address from the event payload. If you do not find the expected address of your device in the search, then the log source might have been created with an unexpected address. Your event payload should indicate what value is the source address. This can occur when the event source handles events from multiple devices or substitutes in an unexpected value in to the Syslog header. This is uncommon, but does happen on certain devices. Your device might have an option to preserve the original event IP before sending the Syslog event.\n\nRead more: How QRadar determines a hostname or IP from an event [http://www-01.ibm.com/support/docview.wss?uid=swg21622450]\n\n4. Search for a unique payload value in the Log Activity tab.\n\nReview the raw payloads from tcpdump and select a key word you think is unique to your event source. Perform a search to look for the unique value.\nClick the Log Activity tab. Select the Quick Filter search option.\n\nNOTE: For more information on using the Quick Filter for searches, see: Searching Your QRadar Data Efficiently: Part 1 - Quick Filters [http://www.ibm.com/support/docview.wss?uid=swg21689800].\n In the search bar, type any unique value that would appear in your payload. Review the search results.\n\nResults\n The search will locate any values entered in the quick filter that are part of the event payload. The administrator can review these events as they may show up as a different log source which would indicate a false positive in auto detection or an issue with an extension. In this case, you can go to the Admin tab > Log sources > Delete the log source which was not auto detected properly. If the log source discovers incorrectly, you should verify that your Console is installed with the latest DSM version. Administrators can compare their RPM version against IBM Fix Central [http://www-933.ibm.com/support/fixcentral/], then let the log source rediscover.\n*\nWhere do you find more information?\n\n[/support/docview.wss?uid=swg21674902&aid=1] [http://ibm.biz/QRadar-KC] [/support/docview.wss?uid=swg21674902&aid=2] [https://ibm.biz/qradarforums] [/support/docview.wss?uid=swg21674902&aid=3] [http://ibm.biz/qradarknowledge] [/support/docview.wss?uid=swg21674902&aid=4] [http://ibm.biz/SecSuptUTube] [/support/docview.wss?uid=swg21674902&aid=5] [http://ibm.biz/qradarsoftware] [/support/docview.wss?uid=swg21674902&aid=6] [http://ibm.biz/MyNotification] [/support/docview.wss?uid=swg21674902&aid=7] [http://ibm.biz/SuptRegQuikStart]", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q033", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "How do I find error logs on my unix system? Error messages of LSF servers are logged in either the syslog(3) or specified files. This is determined by the LSF_LOGDIR definition in the lsf.conf file.\n\nIf you configure LSF to log daemon messages using syslog, the destination file is determined by the syslog configuration. On most systems, you can find out which file the LSF messages are logged in with the command:\n\ngrep daemon /etc/syslog.conf\n\nOnce you have found the syslog file, you can select the LSF error messages with the command:\n\negrep 'lim|res|batchd' syslog_file\n\nLook at the /etc/syslog.conf file and the manual page for syslog or syslogd for help in finding the system logs.\n\nWhen searching for log messages from LSF servers, you are more likely to find them on the remote machine where LSF put the task than on your local machine where the command was given.\n\nLIM problems are usually logged on the master host. Run lsid to find the master host, and check syslog or the lim.log.hostname file on the master host. The res.log.hostname file contains messages about RES problems, execution problems and setup problems for LSF. Most problems with interactive applications are logged in the remote machine's log files.\n\nErrors from LSF Batch are logged either in the mbatchd.log.hostname file on the master host, or the sbatchd.log.hostname file on the execution host. The bjobs or bhist command tells you the execution host for a specific job.\n\nMost LSF log messages include the name of an internal LSF function to help the developers locate problems. Many error messages can be generated in more than one place, so it is important to report the entire error message when you ask for technical support.\n\nCross reference information Segment Product Component Platform Version Edition IBM Spectrum Computing IBM Spectrum LSF\n\nDOWNLOAD", "logical_doc_id": 4, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q033", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "Lists of fixes in fix packs for IBM DataPower Gateway version 7.7.", "logical_doc_id": 5, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q033", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Fix packs and firmware images are located in Fix Central.\nIn IBM Knowledge Center you can find information about new and changed features, limitations, and restrictions.\nFor new features, see What's new [http://www.ibm.com/support/knowledgecenter/SS9H2Y_7.7.0/com.ibm.dp.doc/whats_new.html].\nFor changes, see What's changed [http://www.ibm.com/support/knowledgecenter/SS9H2Y_7.7.0/com.ibm.dp.doc/whats_changed.html].\nFor limitations and restrictions, see the Release notes [http://www.ibm.com/support/knowledgecenter/SS9H2Y_7.7.0/com.ibm.dp.doc/releasenotes.html].\nTo download fix packs, go to the Fix Central website [http://www.ibm.com/support/fixcentral/].\n\nImportant:\nBefore you install any fix pack or firmware image, review the DataPower Knowledge Collection on firmware updates. [http://www.ibm.com/support/docview.wss?uid=swg27015333]", "logical_doc_id": 5, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q033", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "For information about how to download DataPower fix packs from Fix Central, see the Fix download method [http://www.ibm.com/support/docview.wss?uid=swg21376557] technote.\n7.7.1.2 Replacement CD image for 7.7.1.1\n7.7.1.1 Replacement CD image for 7.7.1.0\n7.7.1.0 Replacement CD image for 7.7.0.x and includes all APARs in the 7.6.0.7 fix pack\n7.7.0.2 Fix pack for 7.7.0.x\n7.7.0.1 Fix pack for 7.7.0.x\n7.7.0.0 Initial CD image for 7.7.0.x and Includes all APARs in the 7.6.0.6 fix pack.\n\n7.7.1.2\n\nRelease date: 27 July 2018\nLast modified : 27 July 2018\nStatus: Available\n\nAPAR Description IT24329 [http://www.ibm.com/support/docview.wss?uid=swg1IT24329] QUIESCE CAN PREVENT OBJECTS FROM BEING DELETED IT24375 [http://www.ibm.com/support/docview.wss?uid=swg1IT24375] DATAPOWER SCHEMA COMPILER MIGHT INCORRECTLY GENERATE COMPILE ERROR RELATED TO XS:RESTRICTION IT25130 [http://www.ibm.com/support/docview.wss?uid=swg1IT25130] DATAPOWER DNS ROUND ROBIN ALGORITHM DOES NOT HONOR TCP BASED DNSRESPONSE IT25176 [http://www.ibm.com/support/docview.wss?uid=swg1IT25176] B2B TRANSACTION VIEWER PROVIDES EMPTY DOCUMENTS IT25289 [http://www.ibm.com/support/docview.wss?uid=swg1IT25289] DATAPOWER RESTARTS MIGHT OCCUR WHEN CALLING AN API WITH INCORRECT SOAPACTION HEADER IT25539 [http://www.ibm.com/support/docview.wss?uid=swg1IT25539] DATAPOWER MIGHT RESTART WHILE VALIDATING CREDENTIALS DURING AN SSL HANDSHAKE Back to top\n\n7.7.1.1\n\nRelease date: 29 June 2018\nLast modified : 29 June 2018\nStatus: Available", "logical_doc_id": 6, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q033", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "APAR Description IT21452 [http://www.ibm.com/support/docview.wss?uid=swg1IT21452] DATAPOWER CANNOT PARSE UTF8 BOM PREFIXED XML IF BOM IS SPLIT ON DIFFERENT TCP PACKETS IT21491 [http://www.ibm.com/support/docview.wss?uid=swg1IT21491] GATEWAYSCRIPT FILE WITH TRANSFORM.XSLT() MISSES XSLT CLEANUP THAT MIGHT LEAK MEMORY IT21452 [http://www.ibm.com/support/docview.wss?uid=swg1IT21452] DATAPOWER CANNOT PARSE UTF8 BOM PREFIXED XML IF BOM IS SPLIT ON DIFFERENT TCP PACKETS IT24052 [http://www.ibm.com/support/docview.wss?uid=swg1IT24052] UNEXPECTED RESTART OF ISAM REVERSE PROXY IT24359 [http://www.ibm.com/support/docview.wss?uid=swg1IT24359] RBM LDAP SETTINGS REQUIRE HOST AND PORT VALUES IN GUI, AFTER LOAD BALANCER GROUP IS SET IT24651 [http://www.ibm.com/support/docview.wss?uid=swg1IT24651] DATAPOWER LOAD BALANCER GROUP UNABLE TO HANDLE MULTIPLE SETCOOKIE IT24731 [http://www.ibm.com/support/docview.wss?uid=swg1IT24731] SECURE RESTORE MIGHT FAIL FOR LARGE FILE SIZES IT24896 [http://www.ibm.com/support/docview.wss?uid=swg1IT24896] SOME OBJECTS MIGHT BE ENABLED BUT DOWN EVEN THOUGH THE FEATURE IS NOT ACTIVATED IT24906 [http://www.ibm.com/support/docview.wss?uid=swg1IT24906] DOMAIN CLEANUP MIGHT NOT COMPLETE SUCCESSFULLY LEAVING OLD OBJECTS THAT MIGHT LEAD TO INSTABILITY IT24941 [http://www.ibm.com/support/docview.wss?uid=swg1IT24941] A LOG TARGET STATUS MEMORY VALUE IS NOT CORRECT, ALWAYS BEING TOO LOW IT24998 [http://www.ibm.com/support/docview.wss?uid=swg1IT24998] AAA DYNAMIC CONFIGURATION CANNOT HANDLE MULTIPLE LTPA ATTRIBUTES IT25078 [http://www.ibm.com/support/docview.wss?uid=swg1IT25078] CONSOLE MODULE IN GATEWAYSCRIPT ACTION RESTART ISSUE WHEN PASSING SOME ESCAPED CHARACTER IT25198 [http://www.ibm.com/support/docview.wss?uid=swg1IT25198] JSON STRINGS MIGHT FAIL TO PARSE IN AAA POLICY WHEN IT CONTAINS RESERVED XML CHARACTERS IT25303 [http://www.ibm.com/support/docview.wss?uid=swg1IT25303] AAA CUSTOM PASSWORD RETRIEVAL FOR DERIVED-KEY IDENTITY EXTRACTION MIGHT FAIL IT25410 [http://www.ibm.com/support/docview.wss?uid=swg1IT25410] URLOPEN.OPEN() API IN GATEWAYSCRIPT ACTION SUPPORTS GET/DELETE/HEAD WITH DATA IT25469 DATAPOWER GUI AND SOME NETWORK INTERFACES MIGHT FAIL TO START WHEN THE ENCRYPTED SPACE IS LOW Back to top\n\n7.7.1.0\n\nRelease date:8 June 2018\nLast modified : 8 June 2018\nStatus: Available\n\nAPAR Description IT24970 [http://www-01.ibm.com/support/docview.wss?uid=swg1IT24970] ERROR MESSAGE: REQUIRED PROPERTY GATEWAY-PEERING IS MISSING WHEN NOT CONFIGURING API CONNECT Back to top\n\n7.7.0.2\n\nRelease date: 20 April 2018\nLast modified : 20 April 2018\nStatus: Available\n\nAPAR Description IT24787 [http://www-01.ibm.com/support/docview.wss?uid=swg1IT24787] ADDRESS PROBLEMS WITH API CONNECT INTEGRATION Back to top\n\n7.7.0.1\n\nRelease date: 5 April 2018\nLast modified : 5 April 2018\nStatus: Available\n\nAPAR Description IT24621 [http://www-01.ibm.com/support/docview.wss?uid=swg1IT24621] ADDRESS PROBLEMS WITH API CONNECT INTEGRATION Back to top\n\n7.7.0.0\n\nRelease date:30 March 2018\nLast modified : 30 March 2018\nStatus: Available", "logical_doc_id": 6, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q033", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "APAR Description IT19401 [http://www.ibm.com/support/docview.wss?uid=swg1IT19401] DATAPOWER MAY INACCURATELY LOG BACKEND RESPONSE AS CONNECTION FAILURE IT20862 [http://www.ibm.com/support/docview.wss?uid=swg1IT20862] LATENCY AND EXTLATENCY LOG MESSAGES MAY CONTAIN INCORRECT INFORMATION WHEN REQUEST IS HTTP GET IT22019 [http://www.ibm.com/support/docview.wss?uid=swg1IT22019] CHANGE TO LOG MESSAGES RELATED TO MIME IT24076 [http://www.ibm.com/support/docview.wss?uid=swg1IT24076] URL-OPEN MAY PROCESS BACKEND ERRORS DIFFERENTLY WHEN FOLLOWING A REDIRECT IT24130 [http://www.ibm.com/support/docview.wss?uid=swg1IT24130] NON-MAIN TASK MAY EXHIBIT UNEXPECTED BEHAVIOR IF IT IS STOPPED AND THEN LATER STARTED IT24881 [http://www.ibm.com/support/docview.wss?uid=swg1IT24881] POTENTIAL VULNERABILITY IN THE SSL COMPONENT OF IBM DATAPOWER GATEWAYS IT25182 QUOTA ENFORCEMENT SERVER USES DES-CBC3-SHA CIPHER FOR INTERNAL COMMUNICATION Back to top\n\nChange history\nLast modified: 27 July 2018\n27 July 2018: Added fix list for 7.7.1.2.\n29 June 2018: Added fix list for 7.7.1.1.\n8 June 2018: Added fix list for 7.7.1.0.\n20 April 2018: Added fix list for 7.7.0.2.\n5 April 2018: Added fix list for 7.7.0.1.\n30 March 2018: Created fix list for 7.7.0.0.\n\n[data:image/gif;base64,R0lGODlhEAAQAPcAAAAAAP///zQYGVVMVMzEzNzU3NTM1Pz0/PTs9OTc5ExETby0vcS8xSQcKQQEDAwMHCwsPEREXDQ0REREVCQkLExMXHx8jIyMnKSktAwMDUxMUMTEzLS0vNTU3PT0/CAkPC80TDc8VBQcPCw0VNrc5EVMZFVcdKesvDxEXExUbMnM1Ons9Q0UJB0kNAQKFiw0RDxEVERMXExUZFRcamRsehUcJ0xbdCUsNzQ8SVxfZKestLe8xAwcNERUbFxshHV8hoWMlhwjLDxDTJyntJWcpZSjtAREhAQUJAwcLESExBQkNBwsPCQ0RCw8TDREVDxMXERUZExcbFxsfERMVGx4hExUXHyIlIyYpDQ1NldYWWdoaefo6VtodHuMnDxTZJukqwQcLAwkNBQsPDRMXERcbExkdHmEjIqUm29ydJeanCc0PGd0fKy0uQYUHDxBRAwcJBQkLBwsNCw8RDRETDxMVERUXExcZFVkbLzEyKWpq4iKiwSk5MzU1wQcJAwkLBQsNBw0PCQ8RCxETDRMVDxUXERcZKS0uev093d6e0xka9zk5lx0eYykqBQsLBQkJBwsLDRMTERcXDRERBwkJDxMTCo0NERUVCQsLExcXHKEhExUVLO8vBQVFcPMzERHR/P8/NTc3BscHDo8PISUkwQNDHyEgwwUESo1LD5NQTtEPPP89BgmGbK+swQOBCQsJEtVS1xlXGt1a+v06zZ+M1zZUyZVI1RdU6u2qlKkRMzUytTd0cTOwIyXg5yflLzIkdDdmsjYdzU3K3d5aVVWS2VmWqanmg0NBL+/srW1qszMw/z889zc1MTEwpWVlOTjuZiXienYOCwpDPX06ujm2aeSJtjVymVUGi0qJIWDgbSrpera0c3DvtbKxnRsapWLiUQ+Pffs6iALCGRcW6Scm18FBdAUFDYHB4QUFJYwLncnJgwEBFAhIeVwcKZTU+yWlsCMi/O6ulRMTN3U1Ly0tPz09N3c3L28vPz8/PT09NTU1MzMzLS0tCwsLCQkJAQEBP///yH5BAEAAP8ALAAAAAAQABAARwg7AP8JHEiwoMEkCJPsMWKQYMKGBhdmg1gwCcWDCS1eRLhw3sWPIDdqBJmRZMY9IhUa8UhRJcuLK0OCDAgAOw==]Problems (APARS) fixed [data:image/gif;base64,R0lGODlhEAAQAPcAAAAAAP///zQYGVVMVMzEzNzU3NTM1Pz0/PTs9OTc5ExETby0vcS8xSQcKQQEDAwMHCwsPEREXDQ0REREVCQkLExMXHx8jIyMnKSktAwMDUxMUMTEzLS0vNTU3PT0/CAkPC80TDc8VBQcPCw0VNrc5EVMZFVcdKesvDxEXExUbMnM1Ons9Q0UJB0kNAQKFiw0RDxEVERMXExUZFRcamRsehUcJ0xbdCUsNzQ8SVxfZKestLe8xAwcNERUbFxshHV8hoWMlhwjLDxDTJyntJWcpZSjtAREhAQUJAwcLESExBQkNBwsPCQ0RCw8TDREVDxMXERUZExcbFxsfERMVGx4hExUXHyIlIyYpDQ1NldYWWdoaefo6VtodHuMnDxTZJukqwQcLAwkNBQsPDRMXERcbExkdHmEjIqUm29ydJeanCc0PGd0fKy0uQYUHDxBRAwcJBQkLBwsNCw8RDRETDxMVERUXExcZFVkbLzEyKWpq4iKiwSk5MzU1wQcJAwkLBQsNBw0PCQ8RCxETDRMVDxUXERcZKS0uev093d6e0xka9zk5lx0eYykqBQsLBQkJBwsLDRMTERcXDRERBwkJDxMTCo0NERUVCQsLExcXHKEhExUVLO8vBQVFcPMzERHR/P8/NTc3BscHDo8PISUkwQNDHyEgwwUESo1LD5NQTtEPPP89BgmGbK+swQOBCQsJEtVS1xlXGt1a+v06zZ+M1zZUyZVI1RdU6u2qlKkRMzUytTd0cTOwIyXg5yflLzIkdDdmsjYdzU3K3d5aVVWS2VmWqanmg0NBL+/srW1qszMw/z889zc1MTEwpWVlOTjuZiXienYOCwpDPX06ujm2aeSJtjVymVUGi0qJIWDgbSrpera0c3DvtbKxnRsapWLiUQ+Pffs6iALCGRcW6Scm18FBdAUFDYHB4QUFJYwLncnJgwEBFAhIeVwcKZTU+yWlsCMi/O6ulRMTN3U1Ly0tPz09N3c3L28vPz8/PT09NTU1MzMzLS0tCwsLCQkJAQEBP///yH5BAEAAP8ALAAAAAAQABAARwg4AP8JHEiwoMEkCJPsMYLMoMOHECNKJJiwokIj9iAuxDOxo8ePAi1aXHhwJEaICPeI2AGypUuBAQEAOw==]Problems (APARS) fixed\nIT19401, IT20862, IT22019, IT24076, IT24130, IT24881, IT24621, IT24787, IT24970, IT21452, IT21491, IT21452, IT24052, IT24359, IT24651, IT24731, IT24896, IT24906, IT24941, IT24998, IT25078, IT25198, IT25303, IT25410, IT25469, IT24329, IT24375, IT25130, IT25176, IT25289, IT25539", "logical_doc_id": 6, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q007", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "A new version of the Netcool/OMNIbus Probe for Socket will be available to download from September 11, 2014.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q007", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "The Netcool/OMNIbus V8.1 version of this probe has been repackaged to support additional Operating Systems. The probe now supports the following Operating Systems:\n\nAIX, Linux, Solaris, Windows and zLinux.\n\nYou can download the installation package from the IBM Passport Advantage website:\nwww.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\n\nYou can access the latest version of the guide written for this probe on the IBM Knowledge Center:\n\nwww-01.ibm.com/support/knowledgecenter/#!/SSSHTQ/omnibus/probes/socket/wip/concept/socket_intro_c.html [http://www-01.ibm.com/support/knowledgecenter/#!/SSSHTQ/omnibus/probes/socket/wip/concept/socket_intro_c.html]\n\nNetcool/OMNIbus V8.1\n\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the probe for all supported Operating Systems. To obtain this new package, use the Find by part number field to search for part number: CN1I0EN\n\nNetcool/OMNIbus V7.3.0, 7.3.1 or 7.4.0\n\nIf you are running Netcool/OMNIbus V7.3.0, 7.3.1 or 7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.\n\nPart number Operating System CICP0EN AIX CICP4EN HP-UX PA-RISC CICR2EN HP-UX on Itanium CICR3EN Linux CICR6EN Linux for zSeries CICN8EN Solaris CICS0EN Windows Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.\n\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:\n\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html]\n\nrelease notice; downloads; nco-p-socket-java; Socket Java Probe NEWS", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q007", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "The Netcool/OMNIbus Socket Java Probe will be available to download from December 10, 2015.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q007", "section_id": 3, "heading": "CONTENT", "parent": null, "text": "This is a new socket probe that can be configured to work in either Client mode or Server mode. In Server mode, the probe is a multiheaded probe that acts as a single process concurrent server which accepts multiple client connections. In Client mode, the probe connects to a socket to which a device writes its events.\n\nThis probe has been created to address the following enhancement requests:\nRFE 43179, RFE 50920, RFE 61527: A secure connection can be established using the new Secure Sockets Layer (SSL) feature. This probe supports TLSv1 protocol.\nRFE 36469: The ParserElementDelimiter property now accepts Java Regular Expression, allowing users to specify multiple characters as delimiters. This enhancement is also applicable to the new ParserNVPDelimiter property to tokenize name-value pairs.\nRFE 53841: The probe can now be configured to receive heartbeat messages to avoid entering into the Inactivity state.\n\nYou can download the installation package from the IBM Passport Advantage website:\nwww.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\n\nYou can access the latest version of the guide written for this probe on the IBM Knowledge Center:\n\nwww.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/socket_java/wip/concept/socket_java_intro.html [https://www.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/socket_java/wip/concept/socket_java_intro.html]\n\nNetcool/OMNIbus V8.1\n\nThis probe is only supported on Netcool/OMNIbus V8.1. It is provided as a single package which contains versions of the probe for all supported Operating Systems. To obtain this new package, use the Find by part number field to search for part number: CN8BAEN\n\nNetcool/OMNIbus V7.4.0\n\nIf you are running Netcool/OMNIbus V7.4.0, you must use the legacy Socket Probe (nco-p-socket-10_0). For details see\nwww-01.ibm.com/support/docview.wss?uid=swg21613418 [http://www-01.ibm.com/support/docview.wss?uid=swg21613418]\n\nNote: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.\n\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:\n\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html]\n\nrelease note; downloads; nco-g-socket-java; Java Gateway for Socket NEWS", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q007", "section_id": 4, "heading": "ABSTRACT", "parent": null, "text": "A new version of the Netcool/OMNIbus Socket Gateway will be available to download from August 6, 2015.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q007", "section_id": 5, "heading": "CONTENT", "parent": null, "text": "You can access the latest version of the guide written for this gateway on the IBM Knowledge Center:\n\nwww.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/gateways/socketjavagw/wip/concept/socketjavagw_instl_cnfgr_gateway.html [http://www.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/gateways/socketjavagw/wip/concept/socketjavagw_instl_cnfgr_gateway.html]\n\nYou can download the installation package from the IBM Passport Advantage website:\nwww.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\n\nNetcool/OMNIbus V8.1\n\nThe Netcool/OMNIbus V8.1 version of this gateway supports the following Operating Systems:\n\nAIX, Linux, Solaris, Windows and zLinux.\n\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the gateway for all supported Operating Systems. To obtain this package, use the Find by part number field to search for part number: CN6I1EN\n\nNetcool/OMNIbus V7.4.0\n\nIf you are running Netcool/OMNIbus V7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.\n\nPart number Operating System CN6GZEN AIX CN6H1EN HPUX on Itanium CN6H2EN Linux CN6H3EN Linux for zSeries CN6H4EN Solaris CN6H5EN Windows Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.\n\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:\n\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q007", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Specific Binary:\n Last-modified-by:\n Product: Netcool/OMNIBUS\n Component:\n Priority: High\n Severity: High\n Version N.n:\n Product Group:", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q007", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Users of nco_gate as an ObjectServer gateway *\nfor OMNIbus v3.6 ObjectServers. *\n\nPROBLEM DESCRIPTION: Log file messages sometimes clash *\nrather than get written discreetly. *\n\nRECOMMENDATION: *\n*\n\nLog file messages sometimes clash rather than get written\n discreetly.\n\nIt appears that different threads are simultaneously writing\n log messages.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q007", "section_id": 4, "heading": "COMMENTS", "parent": null, "text": "The nco_gate ObjectServer gateway product will be replaced by a\n new product called gateway-nco-g-objserv-36\n\nDate of Release: Fix Pack Name: gateway-nco-g-objserv-36", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q007", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IY88332\nREPORTED COMPONENT NAME\n NC/OMNI GTWY (B\nREPORTED COMPONENT ID\n 5724O73OS\nREPORTED RELEASE\n 100\nSTATUS\n CLOSED FIN\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2006-08-16\nCLOSED DATE\n 2006-11-30\nLAST MODIFIED DATE\n 2006-11-30\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\nNETCOOL", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q007", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R100 PSY\n UP", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q007", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "\"No new features to install\" window is displayed with message \"You haven't selected any new features to install as the selected features already exist on the system.\"", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q007", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The output of listIU is still showing the JDBC Gateway as installed.", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q007", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "1. Back up existing DE by zipping/tarring the entire DE directory\n\ne.g. for root install, tar up \"/usr/ibm/common/acsi\" directory and keep it in another location. Alternatively, use de_backupdb.sh script to create the backup.\n\n2. Run de_lsrootiu.sh script and review the output to determine the discriminant information.\n\ne.g. /opt/IBM/tivoli/netcool\n\nThe discriminant would be /opt/IBM/tivoli/netcool\n\n3. Run listIU.cmd or listIU.sh and in the output look for a line which has \"RootIU UUID:\" and the component name and version\n\ne.g. IU RootIU UUID: 060A90E184C84B7A98E25EC426B44288 Name: gateway-nco-g-jdbc Version: 1.5.1.0\n\n4. Remove the uninstalled component from the listIU, by running\n\nmanageIU.sh -o delete -r -d RootIUTypeID ,\n\nBased on the example above, for root install with discriminant of \"/opt/IBM/tivoli/netcool\" the command to run would be:\n/usr/ibm/common/acsi/bin/manageIU.sh -o delete -r /opt/IBM/tivoli/netcool -d RootIUTypeID[060A90E184C84B7A98E25EC426B44288, 1.5.1.0]\n\n5. Run listIU.sh again and make sure that JDBC gateway is no longer listed.\n\nThe reinstallation of JDBC gateway should now work. If the problem with reinstallation persists, please contact IBM Support.\n\nPRODUCT ALIAS/SYNONYM\n OMNIbus gateway", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q119", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What debug logs should I send to support to help troubleshoot why my adapter request failed?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q119", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The following settings and procedure will assist in capturing debug data from both\nITIM server and ITIM adapter", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q119", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "a.) Enable debug on the ITIM server, by editing /data/enRoleLogging.properties\nfrom:\n# logger.trace.com.ibm.itim.remoteservices.level=DEBUG_MIN\nto:\nlogger.trace.com.ibm.itim.remoteservices.level=DEBUG_MAX\n\nIf the problem is during a reconciliation request, increase the size, and # of logs to:\n\n# The maximum number of trace log files\nhandler.file.trace.maxFiles=20\n\n# The maximum log file size in KB\nhandler.file.maxFileSize=10240\n\nYou will need to wait 5 minutes for the above change to take effect.\n(as that is default value for refreshInterval, in enRoleLogging.properties)\n\n# Logging properties refresh interval in milliseconds\nlogger.refreshInterval=300000\n\nor stop/start ITIM application in WebSphere, or stop/start WebSphere. On Windows, you must restart WebSphere itself or the logs will not roll correctly.\n\nb.) To enable debug in an ADK adapter, please use the 'agentCfg' utility located in /bin/ directory.\n\nagentCfg.exe -a \n(password by default is 'agent', and the would be the folder name where it's installed.\nOnce in agentCfg:\nA. Configuration Settings.\nB. Protocol Configuration.\nC. Event Notification.\nD. Change Configuration Key.\nE. Activity Logging.\nF. Registry Settings.\nG. Advanced Settings.\nH. Statistics.\nI. Codepage Support.\n\nX. Done\n\nDo: E (Activity Logging), and enable all:\n\nF. Debug Logging (Enabled).\nG. Detail Logging (Enabled).\nH. Base Logging (Enabled).\nI. Thread Logging (Enabled).\n\nRrestart adapter after,\n\nc.) Test the ADK based adapter service in ITIM.\n\nd.) Recreate the problem by submitting the request that is failing.\n\ne.) After failure, send to IBM support:\nmsg.log, and trace*.log from ITIM server.\n(from the location configured for \"handler.file.fileDir\", in enRoleLogging.properties)\n\nadapter log from ADK adapter server.\n(from /logs/ location)\n\nPRODUCT ALIAS/SYNONYM\n TIM ITIM Identity Manager enRole isim sim", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q119", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Why does the Dataserver service change from healthy to Vulnerable after logging into appstack?", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q119", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Memory allocated was not the supported number", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q119", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "This could be due to amount of Memory allocated to the dataserver.\n\n1. Login to the Dataserver\n 2. Click on Administration > Dashboard tab\n 3. Review the Application status and make sure it is green\n 4. Click on Controller Link\n 5. Review and confirm that all services are running fine\n 6. If needed, make changes to memory", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q119", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "After configuring the StoredIQ for Legal environment to use the company LDAP and imported users. Why the imported users are not able authenticate ?", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q119", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Incorrect LDAP port could cause this issue.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q119", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Configure LDAP server port correctly in StoredIQ for Legal LDAP configuration. If LDAP accepts SSL then use port 636 , if not then use default port 389.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q119", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Any statements in the cognos.ini are separated by entries in square brackets [ ].\nFor example, if you were to add the following:\n\n[PowerPlay DataServer]\nReadCacheSize=4096\nWriteCacheSize=16384\n\ninto the cognos.ini file, it should be included either at the very end or the very beginning or at a line preceding a [ ... ] entry.\nTo make the following three examples functional, settings need to be saved. If Transformer is open, close the application and restart it for the new settings to take effect.\n\n1.\n[PowerPlay DataServer]\nReadCacheSize=4096\nWriteCacheSize=16384\n[ServicesK]\nCOGN LSTAB=coglang.tab\nSRVCMSGS=SRVCMSGS.MSG\nWSK=pgwsckk\n[Services]\nTempo rary=C:\\TEMP\nSortMemory=512\n\n2.\n[ServicesK]\nCOGNLSTAB=coglang.tab\nSRVCMSGS=SRVCMSGS.MSG\nWSK=pgwsckk\n[Services]\nTemporary=C:\\TEMP\nSortMemory=512\n[PowerPlay DataServer]\nReadCacheSize=4096\nWriteCacheSize=16384\n\n3.\n[Services K]\nCOGNLSTAB=coglang.tab\nSRVCMSGS=SRVCMSGS.MSG\nWSK=pgwsckk\n[PowerPla y DataServer]\nReadCacheSize=4096\nWriteCacheSize=16384\n[Services]\nTempo rary=C:\\TEMP\nSortMemory=512\nBob Mango\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics CognosReportNet CognosReportNet Business Analytics Cognos Series 7 Transformer\nHISTORICAL NUMBER\n 88911", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q119", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do we view Policy Execution Reports in StoredIQ?", "logical_doc_id": 4, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q119", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Unable to find the location to view generated Policy Execution Reports", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q119", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "1. Login to StoredIQ Dataserver\n 2. Navigate to the Inbox link located next to help icon on the top right corner\n 3. Clicking the link brings up a list with links to the reports\n 4. Clicking on one of the report links will allow you to download the report", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q020", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q020", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When attempting to issue a long-running command scheduler\n command using lrcmd.[bat|sh] through the On-Demand Router (ODR),\n an IOException will be returned as follows:\n\n C:\\IBM\\WebSphere\\AppServer\\bin>lrcmd -cmd=submit\nxJCL=C:\\SimpleCIxJCL.xml -port= -host=\n\n CWLRB4940I: com.ibm.ws.batch.wsbatch : -cmd=submit\nxJCL=C:\\SimpleCIxJCL.xml -port= -host=\n\n CWLRB4880E: -cmd=submit -xJCL=C:\\SimpleCIxJCL.xml -port=\nhost= failed:\n com.ibm.ws.batch.wsbatch: java.io.IOException:\n Connection\n close: Read failed. Possible end of stream encountered.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q020", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of WebSphere Extended Deployment *\nversion 6.0.1.1. *\n\nPROBLEM DESCRIPTION: When attempting to issue a *\nlong-running scheduler command using *\nlrcmd.[bat|sh] through the On-Demand *\nRouter (ODR), an IOException will be *\nreturned as follows: *\n*\nC:\\IBM\\WebSphere\\AppServer\\bin>lrcmd *\n-cmd=submit -xJCL=C:\\SimpleCIxJCL.xml *\n-port= -host= *\n*\nCWLRB4940I: com.ibm.ws.batch.wsbatch : *\n-cmd=submit -xJCL=C:\\SimpleCIxJCL.xml *\n-port= -host= *\n*\nCWLRB4880E: -cmd=submit -xJCL=C:\\Simple *\nCIxJCL.xml -port= *\n-host= failed: *\ncom.ibm.ws.batch.wsbatch: java.io. *\nIOException:Connection close: Read *\nfailed. Possible end of stream *\nencountered. *\n\nRECOMMENDATION: *\n\n The problem was caused by assuming in the code the every SOAP\n request will have a web module with web service and operation\n node defined. Therefore for the cases where web service and\n operation nodes do not exist, trying to use the operation map\n to get a key results in a null pointer exception. To the\n caller this wrapped up exception shows up as an IO Exception.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q020", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "For each SOAP over HTTP request, check for the definition of\n web service and web service operation nodes, if they exist use\n them to fetch the workclasses and perform further request\n classification as necessary, otherwise, use the original\n request mapping to route request.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q020", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PK21207\nREPORTED COMPONENT NAME\n WEBS EXTENDED D\nREPORTED COMPONENT ID\n 5724J3400\nREPORTED RELEASE\n 60A\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2006-03-09\nCLOSED DATE\n 2006-05-22\nLAST MODIFIED DATE\n 2006-05-22\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\nODR", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q020", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBS EXTENDED D\nFIXED COMPONENT ID\n 5724J3400", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q020", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R60A PSY\n UP\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q020", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "They got the message \"Cannot invoke method toInteger( ) on null\n object\"\n once dropping the ODR part on the pattern editor.\n It is an error only WCA which upgraded WCA from v1.1.1.0 GA code\n to v2.0.0.0 GA.\n When they use WCA 2.0 GA code with reset, this error does not\n occur.\n .\n Here is the steps taken during the migration from 1.1.1 GA.\n 1. replace the firmware from v1.1.1.0 GA to v2.0.0.0 GA\n 2. upload WAS HV 7.0.0.11 (RHEL) to WCA via\n CLI(cloudburst.virtualimage.create('local path of ova') )and\n Enabled IMP\n 3. upload WAS HV 7.0.0.11(SLES) to WCA via CLI and Enabled IMP\n 4. tried to create new pattern with ODR part, but failed with\n both RHEL and SLES ODR parts.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q020", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "reset the GA 2.0 firmware", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q020", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Title\n\nThe On-Demand Router part is not usable in user interface when a\n WebSphere Cloudburst Appliance is upgraded to 2.0.0.0 and the\n WebSphere Hypervisor Edition with Intelligent Management Pack\n image is imported", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q020", "section_id": 3, "heading": "Error description", "parent": null, "text": "The problematic scenario is when:\n (1) WebSphere Cloudburst Appliance is upgraded to version\n 2.0.0.0\n (2) Then the new WebSphere Hypervisor Edition with the\n Intelligent Management Pack virtual image is imported, the\n license is accepted, and the Intelligent Management pack support\n is enabled.\n (3) Then when you attempt to drag and drop a On demand router\n part onto the pattern. The pattern no longer can be displayed\n and a \"Cannot invoke method toInteger( ) on null object\"\n message is displayed.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q020", "section_id": 4, "heading": "Local fix", "parent": null, "text": "There is no workaround for this issue.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q020", "section_id": 5, "heading": "Problem summary", "parent": null, "text": "USERS AFFECTED:\n Users upgrading a WebSphere CloudBurst Appliance from releases\n prior to 2.0.0.0 to 2.0.0.0, who then import a new WebSphere\n Hypervisor Edition virtual image.\n\nPROBLEM DESCRIPTION:\n In previous releases of WebSphere CloudBurst appliance, the On\n Demand Router part is no included. This is actually two parts,\n an abstract conceptual part, and a specific concrete\"part\n associated with a particular WebSphere Hypervisor Edition\n virtual image. The upgrade from WebSphere CloudBurst 2.0.0.0\n does not add the conceptual part to the WebSphere CloudBurst\n Appliance. WebSphere CloudBurst Appliance is unable to construct\n a consistent pattern model, and the message \"Cannot invoke\n method toInteger( ) on null object\" is the result.", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q020", "section_id": 6, "heading": "Problem conclusion", "parent": null, "text": "The WebSphere CloudBurst Appliance 2.0.0.1 upgrade includes the\n addition of the On Demand Router conceptual part to the\n WebSphere Cloudburst appliance.\n If this upgrade is applied, the problem is resolved.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q020", "section_id": 9, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC69795\nREPORTED COMPONENT NAME\n CLOUDBURST APPL\nREPORTED COMPONENT ID\n 5765H1600\nREPORTED RELEASE\n 110\nSTATUS\n CLOSED FIN\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2010-07-09\nCLOSED DATE\n 2010-07-30\nLAST MODIFIED DATE\n 2010-07-30\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q020", "section_id": 11, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R200 PSY\n UP\nR100 PSN\n UP\nR110 PSN\n UP\nR111 PSN\n UP\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q020", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Entries for ODR Traffic appear twice in RM panels", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q020", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: WebSphere Application Server Extended *\nDeployment users *\n\nPROBLEM DESCRIPTION: ODR Entries were showing up twice in *\nthe RM panel. *\n\nRECOMMENDATION: Applying this fix is recommended. *\n\nODR Entries were showing up twice in the RM panel.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q020", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Corrected the problem so that ODR entries only appear once.\n\nThe fix for this APAR is currently targeted for inclusion\n in fixpack 6.0.2.1.\n Please refer to the recommended updates page for delivery\n information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q020", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PK08419\nREPORTED COMPONENT NAME\n WEBS APP SERV N\nREPORTED COMPONENT ID\n 5724H8800\nREPORTED RELEASE\n 60W\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2005-07-06\nCLOSED DATE\n 2005-07-28\nLAST MODIFIED DATE\n 2005-07-28\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\nWEBUI", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q020", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBS APP SERV N\nFIXED COMPONENT ID\n 5724H8800", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q020", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R60A PSY\n UP\nR60H PSY\n UP\nR60I PSY\n UP\nR60P PSY\n UP\nR60S PSY\n UP\nR60W PSY\n UP\nR60Z PSY\n UP", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q020", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Seen in place of viewer and loaded document:\n\n[/support/docview.wss?uid=swg22008878&aid=1] [/support/docview.wss?uid=swg22008878&aid=1]", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q020", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Caching is enabled in the Websphere OnDemand Router (WAS ODR) and this causes WAS ODR to add its own cache control headers. These cache-control headers prevent the client PC from making the required callbacks to the back end webserver to obtain the resources it needs to start.", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q020", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "Any load balanced environment using Webshere OnDemand Router (ODR)", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q020", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "To diagnose this issue, the developer tools in the browser need to be used to analyse the network requests.\n\nIn the console log for the success case, you should see a call for \"getViewoneBootstrap\" - this call does not appear anywhere in the console in the failure case.\n\nFrom the network traces, the following differences can be seen:\n\nRequest via Loadbalancer\\ODR:\n\nHTTP/1.1 200 OK\nX-Powered-By: Servlet/3.0\nContent-Type: text/css; charset=UTF-8\nCache-Control: max-age=86400\nLast-Modified: Tue, XX Sep XXXX 18:35:44 GMT\nContent-Language: en-GB\nDate: Wed, XX Sep XXXX 10:32:55 GMT\nAge: 13378\nTransfer-Encoding: chunked\nContent-Encoding: gzip\n\nRequest to App server direct:\n\nHTTP/1.1 200 OK\nX-Powered-By: Servlet/3.0\nDate: Wed, XX Sep XXXX 14:15:27 GMT\nContent-Type: text/plain\nLast-Modified: Wed, XX Jul XXXX 14:33:38 GMT\nContent-Length: 9131\nContent-Language: en-GB", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q020", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Disable the WAS ODR caching completely form the Admin console:\n\nServers -> On Demand Routers -> -> On Demand Router Settings -> On Demand Router Properties -> On Demand Router settings\n> Caching\nFrom here, uncheck the \"Enable caching\" tick box.\n\nRestart the application in full for the setting to take effect.", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q020", "section_id": 5, "heading": "RELATED INFORMATION", "parent": null, "text": "WAS ODR Caching Configuration [https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tjpx_cachestatdyn.html]", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q020", "section_id": 6, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "IBM WebSphere Virtual Enterprise Version 7.0 Fix Pack 4, also known as Version 7.0.0.4 is available for download. [http://www-01.ibm.com/support/docview.wss?uid=swg24035621]\nIBM WebSphere Virtual Enterprise Version 7.0 Fix Pack 5, also known as Version 7.0.0.5 is available for download. [http://www-01.ibm.com/support/docview.wss?uid=swg24037897]\nIBM WebSphere Virtual Enterprise Version 7.0 Fix Pack 6, also known as Version 7.0.0.6 is available for download. [http://www-01.ibm.com/support/docview.wss?uid=swg24039270]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q020", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "In star topologies, the P2P/SON bootstrap process can significan", "logical_doc_id": 5, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q020", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Users of IBM WebSphere Virtual Enterprise *\nleveraging multi-cell star topology *\nconfigurations. *\n\nPROBLEM DESCRIPTION: Immediately after start-up, the on *\ndemand router (ODR) incorrectly *\nreturns 404 error codes for certain *\nrequests. *\n\nRECOMMENDATION: *\n\nIn multi-cell star topology configurations, the service overlay\n network (P2P/SON) components bootstrap process can\n significantly slow the receipt of on demand configuration\n (ODC) data residing in linked remote cells. The delay in\n receiving ODC data can result in ODR processes incorrectly\n returning 404 error codes for some requests immediately\n after start-up.", "logical_doc_id": 5, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q020", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The bootstrap process used by P2P/SON has been altered; the\n window which caused the delay in ODC data propagation is\n alleviated.\n\nThis fix will be included in the next available fix pack for\n IBM WebSphere Virtual Enterprise.\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q020", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM88669\nREPORTED COMPONENT NAME\n WAS VIRTUAL ENT\nREPORTED COMPONENT ID\n 5725C9203\nREPORTED RELEASE\n 700\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-05-08\nCLOSED DATE\n 2013-06-13\nLAST MODIFIED DATE\n 2013-06-13\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 32 }, { "doc_id": "techqa_DEV_Q020", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WAS VIRTUAL ENT\nFIXED COMPONENT ID\n 5725C9203", "logical_doc_id": 5, "chunk_id": 33 }, { "doc_id": "techqa_DEV_Q020", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R700 PSY\n UP", "logical_doc_id": 5, "chunk_id": 34 }, { "doc_id": "techqa_DEV_Q181", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What would be the equivalent of MSSQL getdate() function for Maximo running on DB2 or Oracle?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q181", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "The getdate() MSSQL function can be replaced by value from DB2 CURRENT DATE special register. On Oracle, sysdate is used to retrieve the current date.\n\nEXAMPLE : MSSQL and transdate <= ( getdate() - 35)\n\nDB2 and transdate <= ( CURRENT DATE - 35 DAYS)\n\nOracle and transdate <= ( sysdate - 35)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q181", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "URL [http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp]\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q181", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When new mail received, inbox unread count changes but inbox\n view does not\n display newly arrived mail. To reproduce you have to set all\n settings mentioned\n above, no new mail received today and lotus notes\n client reopened. Issue can not be reproduced when File -\n Preferences - Mail -\n Sending and Receiving - Alerts has different setting.\n Also to reproduce the issue you must be at least two group by\n date like\n Yesterday and Rest of Week. There should be no messages received\n today.\n Yesterday group should be closed and Rest of Week or any next\n group\n expanded/open. Rest of Week group must contain messages that it\n will not fit\n into screen and scroll bar should be seen. After sending message\n from different\n client or window unread count for inbox view\n updated and scroll bar position changed. Today is not shown and\n I was unable to\n scroll up to see new message. Refresh view also does not help.\n Just selecting\n different view/folder and going back to inbox view\n showed new message and Today group.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q181", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "New Mail not shown in Today Categoryin Grop By Date", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q181", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "New Mail not shown in Today Categoryin Grop By Date\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q181", "section_id": 4, "heading": "COMMENTS", "parent": null, "text": "This APAR is associated with SPR# PBAO9EGN7B.\n New Mail not shown in Today Categoryin Grop By Date", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q181", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n LO78391\nREPORTED COMPONENT NAME\n NOTES CLIENT\nREPORTED COMPONENT ID\n 5724E6255\nREPORTED RELEASE\n 853\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-12-17\nCLOSED DATE\n 2014-09-11\nLAST MODIFIED DATE\n 2014-09-11\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q181", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n NOTES CLIENT\nFIXED COMPONENT ID\n 5724E6255", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q181", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R853 PSN\n UP", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q181", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The Preventive Maintenance, Based Frequency Tab shows the Earliest Next Due Date (PM.ERLSTWOGENDATE) value as today. If you then look at the same record a day later, the date would have also changed and yet no new meter readings records have been entered.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q181", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Today we use the reading history to calculate an average and use that average to project an earliest next due date from today. We assume that if there are no readings between the last reading and today, then there are no readings, and as such 0 units were consumed during that time.\n\nToday If you project an earliest next due date in 6 days, then you go in tomorrow and NO new readings are entered, then the earliest next due date would be pushed out by another day (since 0 readings were entered, yesterday).\n\nThere is a case to be made that the earliest next due date should use the last date of the meter reading instead of today (ie. assume that units that are not yet entered will be entered at some point). There are user requests for this, as well as other models to calculate next due date, but currently, that is not how it is designed.\n\nIt is designed to assume that if no readings are entered, then there are 0 units consumed.\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Control Desk on Cloud", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q181", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Tested on 7.5.0.5-IFIX20140108-2152\n\nSteps to replicate:\n\nCreate a PM Record\n Fill in the Work Type and Location\n On the Frequency Tab enter 1 Day and the Estimated Due Date for\n today\n 02/12/14\n Save\n On the Seasonal Dates tab\n I have 12:00 AM for the PM.TARGSTARTTIME ( default in the\n Database)\n Change status to Active\n Generate Workorder\n Go to the Workorder Application\n Go to Advanced Search Dialog and fill in\n Target Start field and Target Finish\n 2/12/14 12:00 AM for both FROM and TO and click Find\n\nYou will get the following System Message\n\nBMXAA4186E - No records were found that match the specified\n query.\n Check that the value you are searching for was entered correctly\n\nIn the Where Clause:\n\n(targcompdate >= { ts '2014-02-12 00:00:00.000' } and\n targstartdate <=\n { ts '2014-02-12 00:00:00.000' } and siteid = 'BEDFORD' and\n targstartdate >= { ts '2014-02-12 00:00:00.000' } and\n targcompdate <= {\n ts '2014-02-12 00:00:00.000' } and wonum like '%1205%')\n\nBecause Target Start on the PM is set to midnight (without any\n milliseconds), the PM WOGEN process shouldn't include\n millseconds when\n it sets the target start/target finish otherwise searches like\n this\n will fail.\n\nRun a query on the Database and you will notice that there are\n Miliseconds\n\nselect targstartdate, targcompdate from workorder where\n wonum='xxx' and\n siteid='yyy';\n\nThe following will be specified on the Database ( we cannot see\n the\n miliseconds in Maximo, example below;\n\n2014-02-12 00:00:00.817\n\nThis has been the same since 71XX and i can reproduce on 7505\n and 7506", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q181", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nMaximo users of PM work order generation *\n\nPROBLEM DESCRIPTION: *\nPMs are generating with milliseconds on the targstartdate *\nand targcompdate fields on Work Orders. This causes a *\nproblem searching using the calendar control in Work Order *\nTracking. *\n\nRECOMMENDATION: *\nApply latest fix pack. *\n\nSteps to replicate:\n\n1 Create a PM Record\n 2 Fill in the Work Type and Location\n 3 On the Frequency Tab enter 1 Day and the Estimated Due Date\n for today 02/12/14\n 4 Save\n 5 On the Seasonal Dates tab I have 12:00 AM for the\n PM.TARGSTARTTIME ( default in the Database)\n 6 Change status to Active\n 7 Generate Workorder\n 8 Go to the Workorder Application\n 9 Go to Advanced Search Dialog and fill in Target Start field\n and Target Finish 2/12/14 12:00 AM for both FROM and TO.\n 10 Click Find\n\nYou will get the following System Message:\n BMXAA4186E - No records were found that match the specified\n query. Check that the value you are searching for was entered\n correctly\n\n11 Note the Where Clause accessed by the dropdown arrow to the\n right of the Advanced Search button:\n (targcompdate >= { ts '2014-02-12 00:00:00.000' } and\n targstartdate <={ ts '2014-02-12 00:00:00.000' } and siteid =\n 'BEDFORD' and\n targstartdate >= { ts '2014-02-12 00:00:00.000' } and\n targcompdate <= {ts '2014-02-12 00:00:00.000' } and wonum like\n '%1205%')\n\nBecause Target Start on the PM is set to midnight (without any\n milliseconds), the PM WOGEN process shouldn't include\n millseconds when it sets\n the target start/target finish otherwise searches like this will\n fail.\n\nIf you run the following query on the Database and you will\n notice that there are non-zero milliseconds:\n\nselect targstartdate, targcompdate from workorder where\n wonum='xxx' and siteid='yyy';\n\nThe resulting dates include non-zero milliseconds ==>\n 2014-02-12 00:00:00.817\n\nThis has been the same since 71X and still occurs on 7505.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q181", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The millisecond portion of targstartdate and targcompdate on\n work orders generated from PMs will be zero.\n\nThe fix for this APAR is contained in the following maintenance\n package:\n | release\\fix pack\\interim fix for Release 7.1.1.13 of Base\n Services and Release 7.5.0.6 of Base Services\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q181", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV55714\nREPORTED COMPONENT NAME\n WORK & MTRL APP\nREPORTED COMPONENT ID\n TIVOWRKMM\nREPORTED RELEASE\n 750\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2014-02-20\nCLOSED DATE\n 2014-03-07\nLAST MODIFIED DATE\n 2014-03-07\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\nMAXIMO", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q181", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WORK & MTRL APP\nFIXED COMPONENT ID\n TIVOWRKMM", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q181", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R750 PSY\n UP\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q181", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The Add user dialog should be removed so that we are presented\n with the\n \"Select Names\" dialog directly instead. I know noone that uses\n the \"Add\n user\" dialog anymore. It might have been great back when we\n didn't use\n hierarchical names and didn't have the little \"man\"-icon next to\n the\n input field, but now that we can click the \"man\"-icon and open\n up the\n \"Select Names\" dialog it's much easier to find and add names...\n and\n less\n error-prone.\n\nHope this can be created as a design request or something like\n that.\n Maybe we could have a preference option to by-pass the \"Add\n user\"\n dialog which would make the UI back-compatible and make the rest\n of us\n add names even faster that what is possible today.", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q181", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "use standard acl seetings dialog box", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q181", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "The problem will be fixed in the next release of the product.", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q181", "section_id": 4, "heading": "COMMENTS", "parent": null, "text": "This APAR is associated with SPR# HSCR7TJD8D.\n The problem will be fixed in the next release of the product.", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q181", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n LO42018\nREPORTED COMPONENT NAME\n DOMINO SERVER\nREPORTED COMPONENT ID\n 5724E6200\nREPORTED RELEASE\n 801\nSTATUS\n CLOSED FIN\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2009-07-01\nCLOSED DATE\n 2009-07-10\nLAST MODIFIED DATE\n 2009-07-10\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\nNA", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q181", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R801 PSN\n UP", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q283", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "*****INTERNAL********\nAs of version 11.1, Clementine has been modularized. In order for a standalone Clementine Batch installation to connect to a Clementine Server and run a stream, option 1 for server enablement must be licensed as part of the 8800 Clementine Batch authorization code. Please contact SPSS Customer Service for an updated authorization code with this option enabled.\n\nPlease note: Even if you are executing clemb from the client (not server), you still need to have option 1 marked on the Clementine Client license key. Also verify that all other modules(add ons) that the customer is entitled to is enabled as well", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q283", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Modeler forum is Live! [https://developer.ibm.com/answers/topics/modeler/?smartspace=predictive-analytics]\n\nHISTORICAL NUMBER\n 71838", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q283", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Please check to make sure the Sentinel RMS License Manager is running in your Windows Services. If you cannot find the Sentinel RMS License Manager Service under services, please make sure you have installed the correct License Manager Package. The correct install should be located on D:\\Sentinel\\LicenseManager\\Windows\\setup.exe. Where D: is your CD ROM drive", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q283", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\nNeed more help? Our Licensing forum is Live! [https://developer.ibm.com/answers/topics/spsslicensing.html]\n\nHISTORICAL NUMBER\n 80271", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q283", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "My organization has a network license for SPSS for Windows. I know in version 14.0 and beyond it's possible to reserve licenses at the license manager for specific users or groups of users and further that individual users have the ability to \"check out\" licenses for use as commuters -- i.e., they can then disconnect from the network and continue to use the SPSS license for some set period of time.\n\nMy question is this: must license reservations and commuter licenses be configured separately? I want the ability to reserve a certain number of licenses for commuter use ideally without have to specify explicitly who those commuters are. Right now it appears that there is no way to designate a license as \"commuter\" at the license manager level. A license becomes a \"commuter\" license simply by virtue of it being checked out by a user.\n\nHow can I make sure that a certain number of licenses are always available for a group of users who a) have to have a license available when they need one, and b) need that license to be \"commutable\"?", "logical_doc_id": 2, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q283", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "I'm afraid there's no such thing as a \"reserved commuter\" license at present -- in other words, yes, they are configured completely separately. We have filed a feature request with SPSS Development to permit some cross-linkage between the two, but until that functionality is added, here's a hypothetical situation that describes a workaround:\n\nLet's say I've got a 100-user network license. When I set up commuter licensing, I set the license server to allow no more than 30% commuter licenses -- so up to 30 separate users can request to \"check out\" a license. The 31st commuter check out request will be denied.\n\nAny user with the SPSS Commute utility (which is installed automatically with a Network license option installation) will be able to make a check out request. Currently the only way to restrict Commuting at the individual user level is to delete the shortcut and/or the utility post-installation.\n\nLet's say I've got 20 users who I want to guarantee access to a \"commutable\" license. So first I have to reserve 20 licenses for their use only, whether they are commuting or not, and then I would have to delete or hide the SPSS 14 Commuter License program menu shortcut and the SPSSCommute.exe and WCommute.exe files from the SPSS installation directory for all users who I do not want to be able to commute ever.\n\nRight now the rule of thumb is to set the commutability percentage to at least the number of people who have to have the ability to commute, and then you have to reserve licenses for those people.\n\nPlease see Resolutions 59826 and 56447 for detailed instructions on configuring commuter licenses and license reservation files.\n\nWe apologize for the inconvenience", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q283", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Modeler forum is Live! [https://developer.ibm.com/answers/topics/modeler/?smartspace=predictive-analytics]\n\nHISTORICAL NUMBER\n 66306", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q283", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Where do I get support for IBM SPSS Student Version or Graduate Pack software?", "logical_doc_id": 3, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q283", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Step 1:\nFor installation & licensing issues on Student version and Graduate pack, contact your vendor.\nHearne [http://www.hearne.software/Software/SPSS-Grad-Packs-for-Students-by-IBM/FAQ]\nOn the Hub [http://onthehub.com/]\nStudentDiscounts.com [http://studentdiscounts.com/contact-us.aspx]\nJourneyEd [https://www.journeyed.com/contact]\nthinkEDU [https://thinkedu.desk.com/]\nStudica [http://www.studica.com/technical-support]\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", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q283", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "IBM SPSS has not included the option for remotely setting up commuter licenses within its products using wrcommute. To set up a commuter license for your network version product, please view Resolution #59826\n\nHISTORICAL NUMBER\n 71999", "logical_doc_id": 4, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q288", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "WebSphere Application Server java.security file may need manual updates", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q288", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "The java.security file shipped with WebSphere Application Server is a customizable file. WebSphere Application Server does not update this file when fix packs or i-fixes are applied, to avoid overwriting customizations.\n\nWebSphere Application Server Liberty using the Installation Manager (IM) install method, and the WebSphere Application Server Classic may be affected.\n\nThe java.security file may need manual updates to comply with both security and performance upgrades.\n\nSee the following, organized by Java major version, to determine if your java.security file needs to be manually updated.\n\nJava 8\n\nJava 8 release start point Description CVE Common name java.security property Java 8 GA Vulnerability in SSLv3 CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566] POODLE jdk.tls.disabledAlgorithms=SSLv3 Java 8 SR1 Vulnerability in RC4 CVE-2015-2808 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2808] Bar Mitzvah jdk.tls.disabledAlgorithms=SSLv3, RC4 Java 8 SR1 FP1 Vulnerability with Diffie-Hellman ciphers CVE-2015-4000 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000] Logjam jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize <768 Java 8 SR2 Performance degradation due to secure random source n/a n/a securerandom.source=file:/dev/urandom Java 8 SR2 FP10 Vulnerability in MD5 CVE-2015-7575 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575] SLOTH jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 1024\nand-\njdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize <768, MD5withRSA\n\nJava 7 and 7.1\n\nJava 7/7.1 release start point Description CVE Common name java.security property Java 7.1 SR2\n---\nJava 7 SR8 FP10 Vulnerability in SSLv3 CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566] POODLE jdk.tls.disabledAlgorithms=SSLv3 Java 7.1 SR 3\n----\nJava 7 SR9 Vulnerability in RC4 CVE-2015-2808 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2808] Bar Mitzvah jdk.tls.disabledAlgorithms=SSLv3, RC4 Java 7.1 SR3 FP10\n----\nJava 7 SR9 FP10 Vulnerability with Diffie-Hellman ciphers CVE-2015-4000 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000] Logjam jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize <768 Java 7.1 SR3 FP30\n----\nJava 7 SR9 FP30\nVulnerability in MD5 CVE-2015-7575 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575] SLOTH jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 1024\nand-\njdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize <768, MD5withRSA\n\nJava 6 and 6.1\n\nMinimum Java 6/6.1 Description CVE Common name java.security property Java 6.1 SR8 FP2\n----\nJava 6 SR16 FP3 Vulnerability in SSLv3 CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566] POODLE jdk.tls.disabledAlgorithms=SSLv3 Java 6.1 SR8 FP7\n----\nJava 6 SR16 FP7 Vulnerability in RC4 CVE-2015-2808 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2808] Bar Mitzvah jdk.tls.disabledAlgorithms=SSLv3, RC4 Java 6.1 SR8 FP5\n----\nJava 6 SR16 FP5 Vulnerability with Diffie-Hellman ciphers CVE-2015-4000 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000] Logjam jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize <768 Java 6.1 SR8 FP20\n----\nJava 6 SR16 FP20 Vulnerability in MD5 CVE-2015-7575 [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575] SLOTH jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 1024\nand-\njdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize <768, MD5withRSA", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q288", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "WebSphere Java Versions [http://www-01.ibm.com/support/docview.wss?rs=404&uid=swg27005002]\nWebSphere Java Non-serviceable files [http://www-01.ibm.com/support/docview.wss?uid=swg27046880]\nIBM SDK Java Technology Edition Version 8 fixes [http://www.ibm.com/developerworks/java/jdk/fixes/8/]\nIBM SDK Java Technology Edition Version 7 Release 1 fix [http://www.ibm.com/developerworks/java/jdk/fixes/71/]\nIBM SDK Java Technology Edition Version 7 fixes [http://www.ibm.com/developerworks/java/jdk/fixes/7/]\nIBM SDK for Java 6 with an IBM J9 2.6 virtual machine f [http://www.ibm.com/developerworks/java/jdk/fixes/601/]\nIBM SDK Java Technology Edition Version 6 fixes [http://www.ibm.com/developerworks/java/jdk/fixes/6/]\n\nDOWNLOADABLE FILES", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q288", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "Ship Java 8 SR5 FP5 for WebSphere Application Server traditional bundled Java 8", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q288", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "ERROR DESCRIPTION:\n\nShip Java 8 SR5 FP5 for WebSphere Application Server traditional bundled Java 8\n\nLOCAL FIX:\nNone\n\nPROBLEM SUMMARY:\nShip Java 8 SR5 FP5 for WebSphere Application Server traditional bundled Java 8 .\nNote* - Java 8 SR5 FP5 i-fix for z/OS has been replaced by Java 8 SR5 FP6 PI90903 [http://www-01.ibm.com/support/docview.wss?uid=swg24044350].\n\nUSERS AFFECTED:\nShip Java 8 SR5 FP5 for WebSphere Application Server traditional bundled Java 8\nThis combination of WebSphere Application Server and Java is available with fix pack 855.11 and later.\n\nLinux PPC64 LE does not support embedded Java 8 at this time, since the existing embedded Java on that platform is Java 7.1, and it is not going out of service yet. Please continue to use the Java 8 extension offering for your Java 8 needs on this platform.\n\nPROBLEM DESCRIPTION:\nShip Java 8 SR5 FP5 for WebSphere Application Server traditional bundled Java 8\n\nRECOMMENDATION:\nApply this i-fix to your SDK to upgrade your SDK 8 to SDK8 SR5 FP5.\nNOTE:\nThis iFix can ONLY be applied on:\na) WebSphere Application Server traditional bundled Java 8 V855.11 and above with bundled Java 8 installed\n\nPROBLEM CONCLUSION:\nApplying this apar will upgrade your SDK 8 to SDK8 SR5 FP5 (Oracle 1.8.0_u151 ).\n\nThe fixes in this Java SDK are found here:\nhttps://www.ibm.com/developerworks/java/jdk/fixes/8/#SR5FP5 [https://www.ibm.com/developerworks/java/jdk/fixes/8/#SR5FP5]\n\nWhen downloading the fix from fix central, please also download the readme.txt with instructions for installation.\n\nThis Java SDK level was minimally tested with WebSphere 8.5.5.12.\n\nDOWNLOAD PACKAGE", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q288", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] AIX 32-bit Power PC Java SDK 20 Nov 2017 English 142159504 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-AixPPC32-IFPI89658&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] AIX 64-bit Power PC Java SDK 20 Nov 2017 English 156709931 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-AixPPC64-IFPI89658&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Linux 32-bit i/p Series Java SDK 20 Nov 2017 English 140296333 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-LinuxPPC32-IFPI89658&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Linux 64-bit i/p Series Java SDK 20 Nov 2017 English 157938373 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-LinuxPPC64-IFPI89658&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Linux 31-bit S/390 Java SDK 20 Nov 2017 English 131071830 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-LinuxS39031-IFPI89658&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Linux 64-bit S/390 Java SDK 20 Nov 2017 English 144174090 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-LinuxS39064-IFPI89658&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Linux 32-bit x86 AMD/Intel Java SDK 20 Nov 2017 English 133560258 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-LinuxX32-IFPI89658&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Linux 64-bit x86 AMD/Intel Java SDK 20 Nov 2017 English 144466890 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-LinuxX64-IFPI89658&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Solaris 64-bit SPARC Java SDK 20 Nov 2017 English 98169419 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-SolarisSparc64-IFPI89658&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Solaris 64-bit x86 AMD/Intel Java SDK 20 Nov 2017 English 95600514 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-SolarisX64-IFPI89658&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Win 32-bit x86 AMD/Intel Java SDK 20 Nov 2017 English 161812486 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-WinX32-IFPI89658&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Win 64-bit x86 AMD/Intel Java SDK 20 Nov 2017 English 188624008 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-WinX64-IFPI89658&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] HPUX 64-bit Itanium SDK 5 Jan 2018 English 140536992 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-HpuxIA64-IFPI89658&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ]\n [/support/docview.wss?uid=swg24044233&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24044233&aid=2]Problems (APARS) fixed\nPI89658, PI90903\n\nDOWNLOADABLE FILES", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q288", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "Ship Java 8 SR5 FP10 for WebSphere Application Server traditional bundled Java 8", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q288", "section_id": 3, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "ERROR DESCRIPTION:\n\nShip Java 8 SR5 FP10 for WebSphere Application Server traditional bundled Java 8\n\nLOCAL FIX:\nNone\n\nPROBLEM SUMMARY:\nShip Java 8 SR5 FP10 for WebSphere Application Server traditional bundled Java 8 .\n\nUSERS AFFECTED:\nShip Java 8 SR5 FP10 for WebSphere Application Server traditional bundled Java 8\nThis combination of WebSphere Application Server and Java is available with fix pack 855.11 and later.\n\nLinux PPC64 LE does not support embedded Java 8 at this time, since the existing embedded Java on that platform is Java 7.1, and it is not going out of service yet. Please continue to use the Java 8 extension offering for your Java 8 needs on this platform.\n\nPROBLEM DESCRIPTION:\nShip Java 8 SR5 FP10 for WebSphere Application Server traditional bundled Java 8\n\nRECOMMENDATION:\nApply this i-fix to your SDK to upgrade your SDK 8 to SDK8 SR5 FP10.\nNOTE:\nThis iFix can ONLY be applied on:\na) WebSphere Application Server traditional bundled Java 8 V855.11 and above with bundled Java 8 installed\n\nPROBLEM CONCLUSION:\nApplying this apar will upgrade your SDK 8 to SDK8 SR5 FP10 (Oracle 1.8.0_u161 ).\n\nThe fixes in this Java SDK are found here:\nhttps://www.ibm.com/developerworks/java/jdk/fixes/8/#SR5FP10 [https://www.ibm.com/developerworks/java/jdk/fixes/8/#SR5FP10]\n\nWhen downloading the fix from fix central, please also download the readme.txt with instructions for installation.\n\nDOWNLOAD PACKAGE", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q288", "section_id": 3, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] AIX 32-bit Power PC Java SDK 19 Feb 2018 English 144842120 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-AixPPC32-IFPI93094&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] AIX 64-bit Power PC Java SDK 19 Feb 2018 English 159743263 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-AixPPC64-IFPI93094&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Linux 32-bit i/p Series Java SDK 19 Feb 2018 English 142816434 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-LinuxPPC32-IFPI93094&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Linux 64-bit i/p Series Java SDK 19 Feb 2018 English 160903485 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-LinuxPPC64-IFPI93094&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Linux 31-bit S/390 Java SDK 19 Feb 2018 English 133564206 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-LinuxS39031-IFPI93094&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Linux 64-bit S/390 Java SDK 19 Feb 2018 English 147033157 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-LinuxS39064-IFPI93094&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Linux 32-bit x86 AMD/Intel Java SDK 19 Feb 2018 English 136066661 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-LinuxX32-IFPI93094&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Linux 64-bit x86 AMD/Intel Java SDK 19 Feb 2018 English 147399450 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-LinuxX64-IFPI93094&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Solaris 64-bit SPARC Java SDK 19 Feb 2018 English 98578489 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-SolarisSparc64-IFPI93094&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Solaris 64-bit x86 AMD/Intel Java SDK 19 Feb 2018 English 96044369 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-SolarisX64-IFPI93094&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Win 32-bit x86 AMD/Intel Java SDK 19 Feb 2018 English 164860755 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-WinX32-IFPI93094&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] Win 64-bit x86 AMD/Intel Java SDK 19 Feb 2018 English 192241154 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-WinX64-IFPI93094&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] z/OS 31-bit and 64-bit Java SDK 19 Feb 2018 English 843399750 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-OS390-IFPI93094&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ] HPUX 64-bit Itanium SDK 12 Jun 2018 English 141068099 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=8.5.5.11-WS-WASBundledSDK8-HpuxIA64-IFPI93094&product=ibm%2FWebSphere%2FWebSphere%20Application%20Server&source=dbluesearch] [ ]\n [/support/docview.wss?uid=swg24044576&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24044576&aid=2]Problems (APARS) fixed\nPI93094", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q288", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "When starting WebSphere Application Server in profiling mode performing execution time analysis, the JVM might crash resulting in WebSphere Application Server being stopped and no profiling data being collected. You might see a dialog indicating that the C++ runtime library has a runtime error.\n\nIn the WebSphere Application Server native_stderr.log for the server, you might see the following error:\n\n[Error: EC JPIAgent received message (FATAL ERROR): Internal error (see log file).]\n\nThe server's native_stderr.log can be found in the WebSphere Application Server installation directory in a location such as:\n\n[WAS install directory]\\profiles\\AppSrv01\\logs\\server1\\native_stderr.log", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q288", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The January Java 6, Java 7 and Java 8 JDK driver contains a security vulnerability fix that reports error when running code instrumented for execution time analysis profiling", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q288", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "For scenarios where the server is local to the workbench, refer to the following document for installing a fix to the workbench:\n\nhttp://www.ibm.com/support/docview.wss?uid=swg22001889 [http://www.ibm.com/support/docview.wss?uid=swg22001889]\n\nFor scenarios where the server is remote, install Rational Agent Controller v9.6.1 or newer on the same machine as the server before trying execution time analysis profiling again.\n\nContact IBM Support [https://www.ibm.com/contact] if you require further assistance.\n\nCross reference information Segment Product Component Platform Version Edition Software Development Rational Software Architect for WebSphere Software 9.1.2.2, 9.5.0.2, 9.6 Software Development Rational Developer for i 9.0.1, 9.1, 9.1.1, 9.1.1.1, 9.5, 9.5.0.1, 9.5.0.2, 9.5.0.3, 9.5.1, 9.5.1.1, 9.5.1.2 Software Development Rational Developer for Power Systems Software 8.5.1 Software Development Rational Developer for AIX and Linux 9.0.1, 9.1, 9.1.1, 9.1.1.1, 9.1.1.2, 9.1.1.3, 9.1.1.4 Business Integration IBM Integration Designer 8.5.7, 8.5.6, 8.5.5, 8.5.1.2, 8.5.1.1, 8.5.0.1", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q288", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Use the appropriate Java version for the version of IBM BPM or IBM Business Monitor you are using:\n\nProduct version Supported Java version IBM BPM V8.6 Java 8* IBM BPM V8.5.7.0 Java 6 or Java 7* IBM BPM V8.5.6.0 Java 6 or Java 7* IBM BPM V8.5.5.0 Java 6 IBM BPM V8.5.0.x Java 6 [/support/docview.wss?uid=swg21639640&aid=1] [/support/docview.wss?uid=swg21639640&aid=1] IBM Business Monitor V8.5.7.0 Java 6 or Java 7* Business Monitor V8.5.6.0 Java 6 or Java 7* Business Monitor V8.5.5.0 Java 6 [/support/docview.wss?uid=swg21639640&aid=1] [/support/docview.wss?uid=swg21639640&aid=1] *Java snippets, Java conditions, and Java expressions in BPEL processes must use Java 6 constructs instead of Java 7 or Java 8 constructs.\nFor more information, see the following resources:\nVerify Java SDK version shipped with IBM WebSphere Application Server fix packs [http://www.ibm.com/support/docview.wss?uid=swg27005002]\nSupport for Java 6 with Business Process Manager and Business Monitor ending April 2018 [http://www.ibm.com/support/docview.wss?uid=swg21999583]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Installation / Configuration AIX, Linux, Solaris, Windows 8.5.7, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5 Business Integration IBM Business Process Manager Express Installation / Configuration Linux, Windows 8.5.7, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5 Business Integration IBM Business Monitor Installation AIX, Linux, Solaris, Windows, z/OS 8.5.7, 8.5.6, 8.5.5 Business Integration IBM Business Process Manager Advanced Installation / Configuration AIX, Linux, Solaris, Windows, z/OS 8.5.7, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5 Business Integration IBM Business Process Manager Family Installation / Configuration AIX, Linux, Windows 8.6.0.0 IBM Business Process Manager Server Express\nPRODUCT ALIAS/SYNONYM\n BPM\nMonitor", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q236", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM\u00ae Runtime Environment Java\u2122 Version 8 used by IBM Security Directory Suite (SDS). These issues were disclosed as part of the IBM Java SDK updates for Jan 2017.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q236", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID:CVE-2016-5546 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5546]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE Java SE Embedded and Jrockit related to the Libraries component has no confidentiality impact, high integrity impact, and no availability impact.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps://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 in Oracle Java SE and Java SE Embedded 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: Seehttps://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 in Oracle Java SE and Java SE Embedded 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: Seehttps://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 in Oracle Java SE Java SE Embedded and Jrockit 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: Seehttps://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: Seehttps://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)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q236", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Product Version IBM Security Directory Suite 8.0 IBM Security Directory Suite 8.0.1.0 - 8.0.1.1 REMEDIATION/FIXES\n\nProduct VRMF Remediation IBM Security Directory Suite 8.0 Contact IBM Support\n\nIBM Security Directory Suite 8.0.1.0 - 8.0.1.1 8.0.1.2-ISS-ISDS [https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=IBM%20Security&product=ibm/Tivoli/IBM+Security+Directory+Suite&release=8.0.1.2&platform=Linux+64-bit,x86_64&function=fixId&fixids=8.0.1.2-ISS-ISDS-IF0004.fixpack&includeRequisites=1&includeSupersedes=0&downloadMethod=http]", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q236", "section_id": 3, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.\n\nREFERENCE\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q236", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nThe 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.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q236", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition, Version 8.0, which is used by IBM Development Package for Apache Spark. These issues are disclosed as part of the IBM Java SDK updates in January 2017.\n\nIf you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities please refer to the link for \"IBM Java SDK Security Bulletin\" located in the \"References\" section for more information.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q236", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-2183 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2183]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error in the DES/3DES cipher, used as a part of the SSL/TLS protocol. By capturing large amounts of encrypted traffic between the SSL/TLS server and the client, a remote attacker able to conduct a man-in-the-middle attack could exploit this vulnerability to recover the plaintext data and obtain sensitive information. This vulnerability is known as the SWEET32 Birthday attack.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116337 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116337] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\nCVEID: CVE-2016-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-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-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-5552 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-]\nDESCRIPTION: An unspecified vulnerability related to the Networking component has no confidentiality impact, low integrity impact, and no availability impact.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/120872 [https://exchange.xforce.ibmcloud.com/vulnerabilities/120872] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q236", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Development Package for Apache Spark, v1.6.3.0, and earlier versions; or\nIBM Development Package for Apache Spark, v2.1.0.0, and earlier versions", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q236", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Principal Product and Version(s) Remediated IBM Java SDK Version IBM Development Package for Apache Spark [https://www.ibm.com/developerworks/java/jdk/spark/] 1.6.3.1 IBM SDK, Java Technology Edition, Version 8.0 Service Refresh 4 Fix Pack 1 and subsequent releases IBM Development Package for Apache Spark [https://www.ibm.com/developerworks/java/jdk/spark/] 2.1.0.1 and subsequent releases IBM SDK, Java Technology Edition, Version 8.0 Service Refresh 4 Fix Pack 1 and subsequent releases WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q236", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q236", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]\nIBM Java SDK Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg21997194]", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q236", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 9th June 2017 : Correcting the Fix Pack name released having changed the naming basis of issuing Fix Packs within the SR 4 context relative to SR3.\n28th February 2017: Original version published\nThe 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\nCVE-2016-2183; CVE-2016-5546; CVE-2016-5547; CVE-2016-5548; CVE-2016-5549 SECURITY BULLETIN", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q236", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM\u00ae Runtime Environment Java\u2122 Versions 6, 7, and 8, which are used by IBM Rational ClearQuest. These issues were disclosed as part of the IBM Java SDK updates in January 2017.", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q236", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: 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)\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)", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q236", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Rational ClearQuest, versions 7.1, 7.1.1, 7.1.2, 8.0, 8.0.1 and 9.0 in the following components:\nClearQuest Web/CQ OSLC server/CM Server component, when configured to use SSL.\nClearQuest Eclipse clients that use Report Designer, run remote reports on servers using secure connections, or use the embedded browser to connect to secure web sites. If you do not use the ClearQuest Eclipse client in this way, then you are not affected.\n\nClearQuest version Status 9.0.1, 9.0.1.1 Not Affected 9.0 through 9.0.0.4 Affected 8.0.1 through 8.0.1.14 Affected 8.0 through 8.0.0.21 Affected 7.1.2 through 7.1.2.19 (all fix packs) Affected REMEDIATION/FIXES\nThe solution is to install a fix that includes an updated Java\u2122 Virtual Machine with fixes for the issues, and to apply fixes for WebSphere Application Server (WAS).\n\nClearQuest Web/CQ OSLC Server/CM Server Component\n\n1. Determine the WAS version used by your CM server. Navigate to the CM profile directory (either the profile you specified when installing ClearQuest, or /cqweb/cqwebprofile), then execute the script: bin/versionInfo.sh (UNIX) or bin\\versionInfo.bat (Windows). The output includes a section \"IBM WebSphere Application Server\". Make note of the version listed in this section.\n 2. Review the following WAS security bulletin:\n\nSecurity Bulletin: Multiple vulnerabilities in IBM\u00ae Java SDK affects WebSphere Application Server January 2017 CPU [http://www.ibm.com/support/docview.wss?uid=swg21998379]\n\n[http://www.ibm.com/support/docview.wss?uid=swg21982223]and apply the latest available fix for the version of WAS used for CM server.\n\nNote: there may be newer security fixes for WebSphere Application Server. Follow the link below (in the section \"Get Notified about Future Security Bulletins\") to subscribe to WebSphere product support alerts for additional Java SDK fixes.\n\nAffected Versions Applying the fix 8.0.0.x\n8.0.1.x\n9.0.0.x Apply the appropriate WebSphere Application Server fix directly to your CM server host. No ClearQuest-specific steps are necessary. 7.1.2.x (all fix packs)\n7.1.1.x (all fix packs)\n7.1.0.x (all fix packs) Customers should upgrade to a fixed, supported version/release of the product.\n\nClearQuest Eclipse Clients\nApply the relevant fixes as listed in the table below.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q236", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Affected Versions Applying the fix 9.0 through 9.0.0.4 Install Rational ClearQuest Fix Pack 5 (9.0.0.5) for 9.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24043919] or install Rational ClearQuest release 9.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24043586] 8.0.1 through 8.0.1.14\n8.0 through 8.0.0.21 Install Rational ClearQuest Fix Pack 15 (8.0.1.15) for 8.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24043917] 7.1.2 through 7.1.2.19 (all fix packs) Customers should upgrade to a fixed, supported version/release of the product. For 7.0, 7.1, 7.1.1 and earlier releases, IBM recommends upgrading to a fixed, supported version/release/platform of the product. WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q236", "section_id": 3, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q236", "section_id": 4, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]\nIBM Java SDK Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg21997194]", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q236", "section_id": 5, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 13 September 2017: Originally published\nThe 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\nJava Vulnerabilities SECURITY BULLETIN", "logical_doc_id": 2, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q236", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM Runtime Environment Java Technology Edition Version 6.0 and Version 7.0 that is used by Security Directory Integrator. These issues were disclosed as part of the IBM Java SDK updates in January 2017.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q236", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: 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)", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q236", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Tivoli Directory Integrator 7.1.1\n\nIBM Security Directory Integrator 7.2.0", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q236", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Affected Products and Versions Fix availability TDI 7.1.1 and TDI 7.1 7.1.1-TIV-TDI-LA0034 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Directory+Integrator&fixids=7.1.1-TIV-TDI-LA0034-60SR16FP41&source=SAR] SDI 7.2 7.2.0-ISS-SDI-LA0012 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FSecurity+Directory+Integrator&fixids=7.2.0-ISS-SDI-LA12-70SR10FP1&source=SAR] 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.", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q236", "section_id": 4, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 3, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q236", "section_id": 5, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nThe 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\nTSAAM; saam; tsa; psirt; WAS; websphere application server SECURITY BULLETIN", "logical_doc_id": 3, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q236", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition, Version 7 used by IBM Tivoli System Automation Application Manager. IBM Tivoli System Automation Application Manager has addressed the applicable CVEs.\n\nThese issues were also addressed by WebSphere Application Server shipped with IBM Tivoli System Automation Application Manager.", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q236", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: 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)", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q236", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Tivoli System Automation Application Manager 4.1.0.0 \u2013 4.1.0.1", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q236", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "The recommended solution is to apply the corresponding fix to IBM Tivoli System Automation Application Manager. To select the fix you need to apply in your environment, click on 'Download link' in the table below.\nIf you are running IBM Tivoli System Automation Application Manager 4.1, please apply interim fix \u201c4.1.0.1-TIV-SAAMR--IF0004\u201d where represents the operating system for which you want to install the interim fix of this product version. You can apply this interim fix on top of any fixpack of version 4.1.\n\nProduct VRMF APAR IBM Tivoli System Automation Application Manager 4.1 Download link [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+System+Automation+Application+Manager&release=All&platform=All&function=all]\nRefer to the following security bulletin for vulnerability details and information about fixes addressed by WebSphere Application Server shipped with IBM Tivoli System Automation Application Manager.\n\nPrincipal Product and Version(s) Affected Supporting Product and Version Affected Supporting Product Security Bulletin IBM Tivoli System Automation Application Manager 4.1 WebSphere Application Server 8.5 Security Bulletin: Multiple vulnerabilities in IBM\u00ae Java SDK affects WebSphere Application Server January 2017 CPU [http://www-01.ibm.com/support/docview.wss?uid=swg21998379] WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q236", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q236", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]\nIBM Java SDK Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg21997194]", "logical_doc_id": 4, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q236", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 5 July 2017: Original version published\nThe 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.", "logical_doc_id": 4, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q063", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "In the DotEdit logs the client system receives generic error \"CConnection::Couldn't secure parameters\".", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q063", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Either the encryption keys are not valid or a roaming Windows profile is being used.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q063", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Copy from Taskmaster server C:\\Datacap\\Taskmaster\\dc_KTF.xml to your local system C:\\Datacap\\Taskmaster\n\n1. On client system open a Command Prompt window\n 2. Type\n cd c:\\Datacap\\Taskmaster\n 3. Then type\n dcskey.exe -i\n 4. If you are still unable to connect then Remove the client system from the domain\n 5. On the client delete the local folder of the domain user\n 6. Reconnect the client to the domain\n 7. Log into client with domain user\n 8. Repeat steps 1 through 4 and connect with DotEdit and DotScan\n\nPRODUCT README", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q063", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This readme file contains information about installation of the interim fix and about known problems, restrictions, and solutions in support of IBM\u00ae Datacap Version 9.1.3.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q063", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Note: To view other versions of IBM Datacap 9.1.3 Interim Fixes readme files, click the respective tab:\n\nLINKS TO IBM DATACAP 9.1.3 INTERIM FIXES LIBRARY DOCUMENTS\nVersion 9.1.3 Interim Fix 1 [http://www-01.ibm.com/support/docview.wss?uid=swg27050718] - selected tab,\n*\nVersion 9.1.3 Interim Fix 2 [http://www-01.ibm.com/support/docview.wss?uid=swg27050766]\nVersion 9.1.3 Interim Fix 3 [http://www-01.ibm.com/support/docview.wss?uid=swg27050863]\nVersion 9.1.3 Interim Fix 4 [http://www-01.ibm.com/support/docview.wss?uid=swg27050951]\nVersion 9.1.3 Interim Fix 5 [http://www-01.ibm.com/support/docview.wss?uid=swg27051104]\n\nReadme file for: IBM\u00ae Datacap\nProduct or component release:\nIBM\u00ae Datacap\nUpdate name:\nInterim fix pack 002\nFix ID:\n9.1.3.0-Datacap-WIN-IF002\nPublication date:\n15 February 2018\nLast modified date:\n15 February 2018\n\nDownload location\n\nDownload the fix from the following location: https://www-945.ibm.com/support/fixcentral/fixes [https://www-945.ibm.com/support/fixcentral/fixes] or access the fix from the following table.\n\nProduct or Component Name Platform File Name IBM\u00ae Datacap Windows 9.1.3.0-Datacap-WIN-IF002.zip\nKnown problems, restrictions, and solutions Known problems, restrictions, and solutions that affect administration and usage of interim fixes are documented as techdocs in the product support knowledge base. To review all known problems, restrictions, and solutions that affect Version 9.1.3 interim fixes, use the following link to query the product support knowledge base: https://www.ibm.com/support/home/product/Z865301M54010G81/Datacap [https://www.ibm.com/support/home/product/Z865301M54010G81/Datacap].\n\nThe techdoc links are also provided here:\n\nViewer problems when using IBM Content Navigator V3.0.3 with IBM Datacap Version 9.1.3, or later [http://www-01.ibm.com/support/docview.wss?uid=swg22013382] Scan task does not show image when the first scan or hold on Chrome V62 [http://www.ibm.com/support/docview.wss?uid=swg22013455] Datacap Navigator problem about detecting scanner flatbed [http://www-01.ibm.com/support/docview.wss?uid=swg22013503] To review all known problems, restrictions, and solutions that affect Version 9.1.3, see IBM Datacap Version 9.1.3 Release Notes [http://www-01.ibm.com/support/docview.wss?uid=swg27050507]. Prerequisites for IBM\u00ae Datacap Version 9.1.3 Interim Fix 002\n\nThe official statements for hardware and software support for IBM\u00ae Datacap are provided as part of the hardware and software requirements for IBM\u00ae Datacap Version 9.1.3.\n\nBefore you install this fix, ensure that you installed IBM\u00ae Datacap Version 9.1.3. For more information about installing IBM\u00ae Datacap, see Installing IBM Datacap [https://www.ibm.com/support/knowledgecenter/SSZRWV_9.1.3/com.ibm.dc.install.doc/dc_inst.htm].\n\nFor complete details about the hardware and software requirements for IBM\u00ae Datacap, see System requirements [https://www.ibm.com/support/knowledgecenter/SSZRWV_9.1.3/com.ibm.dc.install.doc/sw_comp_reports.htm] .\n\nInstalling IBM\u00ae Datacap interim fix 002\n\nTo install the IBM\u00ae Datacap interim fix 002, use the following procedure:\n\nProcedure\n1. Download the 913 iFix 002 package from Fix Central [https://www-945.ibm.com/support/fixcentral/fixes].\n2. Extract the 913 iFix 002 package, and run the \"Update.exe\" file.\nFeature enhancements", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q063", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "As part of this interim fix, the following new enhancements have been added in Datacap Navigator:\nYou can hide snippets in the default panel. An option has been added in the task setting to show or hide the snippet above each field with the default panel under Field Details of Datacap Navigator (NVerify).\nYou can see the text content in multiple line format in the default panel of the verify page. An option has been added in the task setting that you can configure to use multiple line text area to display captured text in Datacap Navigator.\nYou can use the field variable to control the behavior of default fields panel, such as the ShowSnippet, EditorClass, FieldWidth, and FieldOrder variables.\nYou can now manage default user settings administratively. For more information see, Managing user settings administratively in IBM Datacap, Version 9.1.3, Interim Fix 2 [http://www-01.ibm.com/support/docview.wss?uid=swg27050803].", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q063", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Fixed issues\nThe following issues are fixed in IBM Datacap 9.1.3, Interim Fix 2: Datacap application/component Description Datacap Navigator Spaces contained in variable value get trimmed after the variable value is saved page file. On the Settings page, under the Job Monitor tab, the \"Sort by\" feature does not remain consistent. Asynchronous upload progress bar and batch status does not map. When you rotate or move an image with single page mode, and click undo, the image does not come to its original position. The Zoom In feature does not work for the thumbnail and viewer modes. On the Internet Explorer browser, when you set scan task to upload immediately, scan some images, and submit, does not delete the local batch folder. Validation fails on empty Date fields on the Chrome browser. When you open two clients, for example, first open Fixup client, and the open Scan client, and close the Fixup client, the Scan client gets closed instead of Fixup client. Index, Verify document, and page labels are not displayed correctly when document and page labels are defined in PageID. The Batch preparation client does not open after launching web scan client. Improved page movement performance in scan page. The Filter list is not displayed. Disable rotation if the file type is PDF or MS Office file. Job Monitor does not display any entries. When you close task quickly, a \"Missing JavaScript Event handler\" error might occur. Datacap Web Services (wTM) wTM hangs while creating a thumbnail in the document information pane of the Job Monitor for a batch with a 0 byte page file. Services Operation error has been recorded in the \"tms.log\" file of the Datacap Server. Datacap Desktop The Merge Document feature for fails in Datacap Desktop. Datacap Desktop unexpectedly terminates on batch load. DotEdit, DotScan and FastDoc do not report proper elapsed time in the statistics table. The Verify panel throws an \"Object Reference\" error when a required page is missing from the document, and when validation occurs on the Main_Page. Multiselect drag and drop in thumbnail view does not highlight the thumbnail that is target of drop. Additional Task Profile, created in tmweb, is disabled, and does not work in Datacap Desktop. IBM Datacap Insight Edition (Document Analytics) Most of the pages that are classified using the VisualRecog action have an empty type associated with them. Datacap Web Client For operational shortcut in the tmweb for the \"Manual for hold\" mode, after clicking the select pending Datacap, does not process the oldest batch first. TMweb Verify task using the Verifine panel fails to load child fields in the Lookup script if they reference a standard field. In TmWeb > Admin > Group tab, the \"Run Task\" check box does not work. Datacap Studio When user tries to unlock the DCO in Datacap Studio on a DCO file that contains over 5,000 DCO objects, DCO fails to lock successfully, and fails to load fingerprints in the Zones tab. Using Barcode Byte Mode shuts down Rulerunner. Content Classification The ClassifyCC action throws the ABORT error when KnowledgeBase is not found. The ClassifyCC action gets an error: Unknown Knowledgebase or Decision Plan name. The CC Actions need option to specify txt or xml file for CC submission. [/support/docview.wss?uid=swg27050766&aid=1] Convert.WordDocumentToImage() returns the \"Memory stream is not expandable\" error when you try to extract tiff image from the Word document.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q063", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "z/os A FIX IS AVAILABLE\nDB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24044110]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q063", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "DB2 Versions 10.1 Fix Pack 5 (APAR IT05851 [http://www-01.ibm.com/support/docview.wss?uid=swg1IT05851]), 10.5 Fix Pack 7\n (IT06005 [http://www-01.ibm.com/support/docview.wss?uid=swg1IT06005]), and 11.1 GA introduced a behavior change in the way\n asynchronous write time is accumulated. Asynchronous writes are\n submitted in large batches using asynchronous I/O services/APIs\n provided by an operating system. The approximate previous\n behavior apportioned a pagecleaner EDU's I/O wait time evenly\n across all pages in a batch. For example, if a batch of 10 I/O\n requests took 10ms to complete, each I/O request/page write\n would be assigned 1ms of the overall 10ms time.\n\nIn many cases the apportionment approach masks underlying\n response time issues, and a change was made in the\n above-mentioned DB2 levels to stop splitting a pagecleaner's\n wait time across all pages written, and instead assign the\n entire batch time to each page write request. In the case where\n a batch of 10 I/O requests took 10ms to complete each \"page\n write\" would be assigned the full 10ms. While there is some\n value in providing this information, as it may more accurately\n reflect I/O response time in some storage configurations, it can\n also cause unnecessary concern. This is due to the much higher\n calculated average asynchronous page write time, which bubbles\n up to overall average page write time. It is reasonable that a\n large batch of I/Os may incur some overhead and take longer than\n a single I/O, thus the higher reported time may not be a good\n indicator of underlying I/O performance. In addition, the wait\n time for pagecleaner write activity does not typically impact\n the time a db2agent EDU spends servicing application requests.\n As such, this APAR fix will revert to the former behaviour of\n splitting pagecleaner I/O wait time across the pages involved in\n a batch of asynchronous I/O requests.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q063", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nALL *\n\nPROBLEM DESCRIPTION: *\nSee Error Description *\n\nRECOMMENDATION: *\nUpgrade to DB2 10.5 Fix Pack 8 *", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q063", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "First fixed in DB2 10.5 Fix Pack 8\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q063", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT15748\nREPORTED COMPONENT NAME\n DB2 FOR LUW\nREPORTED COMPONENT ID\n DB2FORLUW\nREPORTED RELEASE\n A50\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-06-15\nCLOSED DATE\n 2017-03-13\nLAST MODIFIED DATE\n 2017-03-13\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n IT15750 [http://www-01.ibm.com/support/docview.wss?uid=swg1IT15750] IT15752 [http://www-01.ibm.com/support/docview.wss?uid=swg1IT15752]", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q063", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n DB2 FOR LUW\nFIXED COMPONENT ID\n DB2FORLUW", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q063", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "RA50 PSN\n UP", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q063", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "All fields pass validations, but Verify indicates that there is still a problem on the page.\n\nExample: In reviewing the batch, the page file indicates a problem status on the page but the RRS log for Validate does not show any rules failing against any field", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q063", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "1. Ensure that the page level rule calls Status_Preserve_OFF\n 2. Ensure that the page level rules do not return false\n 3. If the problem persists, review the page file (Verify.xml), datafile (e.g. tm000001.xml) and RRS logs in order to troubleshoot the issue.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q063", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Note: this issue is separate from the batch indicating there are still problem pages to be verified. If you get a prompt that there are still problem pages within the batch, review the following IBM Technote:\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21507344 [http://www-01.ibm.com/support/docview.wss?uid=swg21507344]\n\nIn addition when using Taskmaster Web, review the [iCap] settings, specifically the DOF.", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q063", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do I delete a document hierarchy node, such as a blank page, so that it no longer processes rules or appears in a batchview listing?", "logical_doc_id": 5, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q063", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "It is sometimes desired to remove pages or documents from a batch, as they are no longer needed or to simplify processing for a Verify operator.", "logical_doc_id": 5, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q063", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "The DeleteChildType from the Validations library can be used by running it from the parent of the object to be deleted and specifying the specific child.\n\nFor example, to remove blank pages from a batch:\n\n1. Create a special page type attached at the batch level called something like DeleteMe.\n 2. Use an action like BlankPagesIDBySize to identify the blank page: * BlankPagesIDBySize (1000,DeleteMe)\n\n3. Create a rule with the action DeleteChildType(DeleteMe) and attach it at the batch level to have it remove all pages with page type DeleteMe.\n\nIf building a custom action, the DeleteChild API method is invoked from the parent object.\n*", "logical_doc_id": 5, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q134", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "Air-freight safety requirements mean that uninterruptible power supply batteries must be disconnected when shipped by air.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q134", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "When installing new SAN Volume Controller uninterruptible power supplies or replacing failed uninterruptible power supplies, the batteries must be reconnected before use. When returning failed uninterruptible power supplies the batteries must be disconnected.\n\nUse the procedure below to reconnect the batteries on uninterruptible power supplies that you are installing. Reverse the procedure if you are returning failed uninterruptible power supplies to IBM.\n\nUninterruptible power supply 2145 UPS\n\n1. Verify that the UPS is off and unplugged.\n2. Remove the UPS front panel.\n3. Align the battery cables.\n\n[/support/docview.wss?uid=ssg1S1002587&aid=1]\n\n4. Push the plug firmly into the socket.\n\n[/support/docview.wss?uid=ssg1S1002587&aid=2]\n\n5. Reinstall the UPS front panel.\n6. If the UPS requires any type of transportation in\nthe future, disconnect the UPS internal battery\nconnector using the above steps in reverse order.\n\nUninterruptible power supply 2145 UPS-1U\n\n1. Verify that the UPS is off and unplugged.\n2. Remove the UPS front panel.\n\n[/support/docview.wss?uid=ssg1S1002587&aid=3]\n\n3. Remove the protective label from the internal battery connector.\n\n[/support/docview.wss?uid=ssg1S1002587&aid=4]\n\n4. Connect the internal battery connector. Each end of the keyed connector has two wires: one red (+) and one black (\u2212). Align the connector so that the two red wires are joined together and the two black wires are joined together. Note: A small amount of arcing may occur when connecting the batteries. This is normal and does not damage the unit or present any safety concern.\n\n[/support/docview.wss?uid=ssg1S1002587&aid=5]\n\n5. Reinstall the UPS front panel.\n\n[/support/docview.wss?uid=ssg1S1002587&aid=6]\n\n6. If the UPS requires any type of transportation in the future, disconnect the UPS internal battery connector using the above steps in reverse order.\n\nCross reference information Segment Product Component Platform Version Edition Storage Virtualization SAN Volume Controller V4.2.x Platform Independent Version Independent Storage Virtualization SAN Volume Controller V4.3.x Platform Independent Version Independent", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q134", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "[nz@nps123 ~]$ nzhw -issues\nDescription HW ID Location Role State\n---------- ----- ----------------- -------- -----\nPowerSupply 1178 rack7.ethsw1.pwr2 Inactive Down\nPowerSupply 1186 rack7.ethsw2.pwr2 Inactive Down", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q134", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "SPAs were power-cycled 8 days ago, the error began after power cycle was complete.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q134", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "Twinfin, Striper, RPC", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q134", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Obtain the fabric switch locations by running 'nzhw | more'.\nThis appliance has 2 fabric switches in racks 2, 6, and 7.\nRun sys_rev_check to get the names of the fabric switches.\n----------------------------RACK SWITCH FAB CHECK-----------------------------\nnetswfab01a [PASS]\nnetswfab01b [PASS]\nnetswfab02a [PASS]\nnetswfab02b [PASS]\nnetswfab03a [PASS]\nnetswfab03b [PASS]", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q134", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Telnet to the fabric switches to confirm the issue.\nTELNET/SSH From host 10.0.128.1\nHardware ASIC Info: Family FM4000, Model FM4224, Version FM4224_A3\n\nTemperature Sensors Information\nThreshold: Warning at 85C and Failure at 100C\nTemperature Sensor 1: 39.0 C\nTemperature Sensor 2: 28.5 C\nTemperature Sensor 3: 28.50 C\n\nFans Information\nFan Air Flow: Forward\nSpeed of Fan #1: 16666 RPM at 255 PWM\nSpeed of Fan #2: 16615 RPM at 255 PWM\nSpeed of Fan #3: 16666 RPM at 255 PWM\nSpeed of Fan #4: 17197 RPM at 255 PWM\nSpeed of Fan #5: 17197 RPM at 255 PWM\nSpeed of Fan #6: 16927 RPM at 255 PWM\n\nState of Power Supply 1: On\nState of Power Supply 2: Off\n\nTemperature Sensors Information\nThreshold: Warning at 85C and Failure at 100C\nTemperature Sensor 1: 38.0 C\nTemperature Sensor 2: 26.5 C\nTemperature Sensor 3: 26.75 C\n\nFans Information\nFan Air Flow: Forward\nSpeed of Fan #1: 16513 RPM at 255 PWM\nSpeed of Fan #2: 16513 RPM at 255 PWM\nSpeed of Fan #3: 16718 RPM at 255 PWM\nSpeed of Fan #4: 16463 RPM at 255 PWM\nSpeed of Fan #5: 16363 RPM at 255 PWM\nSpeed of Fan #6: 16770 RPM at 255 PWM\n\nState of Power Supply 1: On\nState of Power Supply 2: Off\n\nLogged in to rpc7ll\n\nSwitched Rack PDU: Communication Established\n------ Control Console -------------------------------------------------------\n\n1- Device Manager\n2- Network\n3- System\n4- Logout\n\n- Main Menu, - Refresh, - Event Log\n> 1\n------ Device Manager --------------------------------------------------------\n\n1- Phase Management\n2- Outlet Management\n3- Power Supply Status\n\n- Back, - Refresh, - Event Log\n> 2\n------ Outlet Management -----------------------------------------------------\n\n1- Outlet Control/Configuration\n2- Outlet Restriction\n\n- Back, - Refresh, - Event Log\n> 1\n------ Outlet Control/Configuration ------------------------------------------\n\n1- SPA14 SPA-DE03 left ps ON\n2- SPA14 SPA-DE04 left ps ON\n3- NETSWFAB03A left ps OFF\n4- NETSWFAB03B left ps OFF\n5- unused5 ON\n6- unused6 ON\n7- unused7 ON\n8- unused8 ON\n9- Master Control/Configuration\n\n- Back, - Refresh, - Event Log\n> 3\n------ NZ80684-H1 ------------------------------------------------------------\n\nName : NETSWFAB03A left ps\nOutlet : 3\nState : OFF\n\n1- Control Outlet\n2- Configure Outlet\n\n?- Help, - Back, - Refresh, - Event Log\n> 1\n------ Control Outlet --------------------------------------------------------", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q134", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Name : NETSWFAB03A left ps\nOutlet : 3\nState : OFF\n\n1- Immediate On\n2- Immediate Off\n3- Immediate Reboot\n4- Delayed On\n5- Delayed Off\n6- Delayed Reboot\n7- Cancel\n\n?- Help, - Back, - Refresh, - Event Log\n> 1\n\nTurned both outlet 3 and 4 on.\n------ Outlet Control/Configuration ------------------------------------------\n\n1- SPA14 SPA-DE03 left ps ON\n2- SPA14 SPA-DE04 left ps ON\n3- NETSWFAB03A left ps ON\n4- NETSWFAB03B left ps ON\n5- unused5 ON\n6- unused6 ON\n7- unused7 ON\n8- unused8 ON\n9- Master Control/Configuration\n\n- Back, - Refresh, - Event Log\n\nConfirm settings. 'nzhw -issues' should no longer report fabric switch power supply failure.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q134", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What are the system specifications for the SiteProtector appliances?", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q134", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "IBM Security SiteProtector SP4001\nForm factor 1U, rack mountable Dimensions (mm/in.) [/support/docview.wss?uid=swg21961505&aid=1] Weight (kg/lb) [/support/docview.wss?uid=swg21961505&aid=1] Power Supply 2x Acbel Model FSA021 CPU 1x Quad Core Intel i7-2600 3.40 GHz Memory 32 GB DDR3 DRAM Video port 1x VGA, front panel Operating System Windows Server 2012 R2 (for Embedded Systems Standard) Database Embedded SQL Svr Std Runtime 2014 (Standard) Storage 800 GB Micron M500DC SSD, 2.5\u201d form factor Network ports 6x 1 GbE copper ports General availability 30 January 2015 End of Support 30 December 2022 IBM Security SiteProtector SP3001 Form factor 2U, rack mountable Dimensions (mm/in.) 89/ 3.5 (H) x 483/ 19 (W) x 610/ 24 (D) Weight (kg/lb) 27/ 59.5 Power Supply 2x 3Y Power Technology : Ym-2721A (720W) CPU 1x Quad Core Intel Xeon E5540 2.53 GHz Memory 12 GB DDR3 DRAM, ECC- REG Video port VGA, front panel Operating System Microsoft Windows Server 2008 R2 Standard Database Microsoft SQL Server 2008 R2 Enterprise Storage 4x 600 GB hard disk drive (HDD) removable 10K rpm, 2.5\" form factor Network ports 2x 1 GbE copper ports USB ports 3x ports, front panel General availability 08 December 2011 End of Support 09 July 2019 Proventia Management SiteProtector SP2001 Form factor 2U, rack mountable Dimensions (mm/ in.) 88/ 3.5 (H) x 429/ 16.9 (W) x 520/ 20.5 (D) Weight (kg/ lb) 18/ 39.68 Power Supply 2x internal power supply, hot-plug, AC 120/230 V CPU 2x Xeon 2.8 GHz Memory 4 GB of Ram Video port 1x VGA, rear panel Operating System Microsoft Windows Server 2003 Database Microsoft SQL Server 2005 Storage 2x 74 GB Network ports 1x Management RJ45, rear panel\n1x Unused port, rear panel USB ports 2x ports, rear panel General availability 29 June 2009 End of Support 31 December 2016\nProventia Management SiteProtector SP1001 Form factor 2U, rack mountable Dimensions (mm/in.) 88/ 3.5 (H) x 429/ 16.9 (W) x 520/ 20.5 (D) Weight (kg/lb) 18 / 40 Power Supply 2x internal power supply, hot-plug, AC 120/230 V CPU 2x Xeon 2.8 GHz Memory 4 GB of RAM Video port 1x DVI-D, rear panel\n1x VGA, rear panel Operating System Microsoft Windows Server 2003 Database Microsoft SQL Server 2005 Storage 2x 74 GB hard disk drive (HDD) hot-swap Network ports 1x Management RJ45, front panel USB ports 2x USB 2.0 - Type A, front panel General availability 17 June 2008 End of Support 30 November 2014", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q134", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "[/support/docview.wss?uid=swg21961505&aid=2] [https://ibm.biz/BdHdjw] [/support/docview.wss?uid=swg21961505&aid=3] [http://ibm.biz/InfraSecForumTechnote] [/support/docview.wss?uid=swg21961505&aid=4] [http://ibm.biz/SecSuptUTube] [/support/docview.wss?uid=swg21961505&aid=5] [http://ibm.biz/InfraSecFixes] [/support/docview.wss?uid=swg21961505&aid=6] [http://ibm.biz/FlexLicLogin] [/support/docview.wss?uid=swg21961505&aid=7] [http://ibm.biz/MyNotification] [/support/docview.wss?uid=swg21961505&aid=8] [http://ibm.biz/ContactSecSupport]", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q134", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "The IBM WebSphere DataPower M/T 9235 appliance might incorrectly report the failure of both power supplies. This message is not reported on all appliances and can occur rarely in the field.", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q134", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "The following message would be present in the DataPower logs:\n\nSystem power supply #2 has failed.\n\nor logging event code:\n\n0x80400022 System power supply #2\n\nThe problem can be confirmed by issuing the following commands on the appliance CLI:\n\nco\ntest hardware\nexit\n\nThe following output from the test hardware command confirms this problem:\n\n[failure] Power supply '1' has no AC input power, or is not present.\n[failure] Power supply '2' has no AC input power, or is not present.\n\nOther results in the test hardware command might also show incorrect values.\n\nThis problem does not affect the operation of the appliance other than the continuous reporting power supply failure message.\n\nTo confirm the power supplies are working normally you may check the LED status on the power supplies. If the LED's are green the power supplies are working normally.\n\nTo recover from the false errors perform a reboot of the appliance:\n\nFrom the WebGUI:\n\nControl Panel \u2192 System Control \u2192 In the \u201cShutdown\u201d section choose \u201cReboot System\u201d then click \u201cShutdown\u201d\n\nFrom the CLI:\n\ntop\n\nshutdown reboot\n\ny\n\nThis problem is caused by a highly intermittent error that may allow the sensor reading mechanism to get into a bad state. This bad state then generates the false error messages. In most cases, a reboot of the appliance will reset the sensors and no additional errors are logged. The highly intermittent error rarely occurs again on the same appliance\n\nIf the issue reoccurs on the same appliance contact IBM DataPower support [http://www.ibm.com/support/docview.wss?uid=swg21236322] with the following information:\n\n1) How many times have you seen the issue on the same appliance?\n\n2) Gather the outputs for the following CLI commands:\nshow clock\nshow version\nshow ipmi\nshow sensors-other\nconfig\nservice show\ntest hardware\n\n\u30de\u30cb\u30e5\u30a2\u30eb\n\n\u6982\u8981\n This guide is intended for system administrators or systems services representatives who use and diagnose problems with the SAN Volume Controller, the redundant ac-power switch, and the uninterruptible power supply.\n\nSVC V710 Troubleshooting Guide_JPN.pdf [/support/docview.wss?uid=ssg1S7004466&aid=2]SVC V710 Troubleshooting Guide_JPN.pdf [/support/docview.wss?uid=ssg1S7004466&aid=1]\n\n\u521d\u7248\u30ea\u30ea\u30fc\u30b9\u65e5\n 2013/7/25", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q049", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Validating database support. Please wait...\n\nIBM InfoSphere Change Data Capture supports Oracle 10g and above.\n\nPress ENTER to go to the Main menu...", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q049", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The CDC Oracle database user has insufficient privileges.\nIf CDC can't query v$instance we are unable to validate the Oracle version and fail", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q049", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "InfoSphere Data Replication for Oracle", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q049", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Execute the command\nsqlplus /@ select version from v$instance\n\nThe should be the same CDC Oracle database user specified when trying to create the instance", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q049", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Grant CDC database user v$instance privileges.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q049", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Errors like the following are logged:\n\nJ2CA0036E: An exception occurred while invoking method setDataSourceProperties on com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jdbc/afuConfigurationDatabase : com.ibm.ws.exception.WsException: DSRA0023E: The DataSource implementation class \"oracle.jdbc.xa.client.OracleXADataSource\" could not be found.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q049", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "You can specify the directory of the JDBC driver in the IBM InfoSphere Content Collector Configuration Manager. However, you cannot specify a specific JDBC driver file.\n\nIf you connect to an Oracle data store, Content Collector uses the value of the WebSphere environment variable ORACLE_JDBC_DRIVER_PATH to locate the Oracle JDBC driver and assumes that the driver file name is ojdbc6.jar. If ojdbc6.jar is not found, the Content Collector WebApplications service cannot connect to the Oracle data store. Various connectivity errors are logged.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q049", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Check the resources.xmlfile in the directory\n\n\\AFUWeb\\profiles\\\\config\\cells\\\\nodes\\\n\nResolve the problem as mentioned below if it contains the following class path element:\n${ORACLE_JDBC_DRIVER_PATH}/ojdbc6.jar\nDo not modify the resources.xml file.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q049", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To resolve the problem:\n\n1. Create a copy of the Oracle JDBC driver that is installed on the IBM InfoSphere Content Collector system in the same location where the current driver resides (for example, copy ojdbc14.jar for Oracle 10g).\n 2. Rename the copy as ojdbc6.jar.\n 3. Restart the IBM InfoSphere Content Collector WebApplications service.", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q049", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The following exception is written to the logs:\n\njava.sql.SQLException: ORA-01483: invalid length for DATE or NUMBER bind variable\nDSRA0010E: SQL State = 72000, Error Code = 1,483", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q049", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The Oracle 9i Thin Driver limits the size of data to no more than 4 KB for VARCHAR2, NVARCHAR2, BLOB, and CLOB types.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q049", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Use either of the following solutions to solve the problem:\nUse the Oracle 10g driver file. 1. Log on to the administrative console and navigate to Environment > WebSphere Variables.\n\n2. Select the variable ORACLE_JDBC_DRIVER_PATH.\n\n3. Change the variable value to the folder that contains the Oracle 10g driver (ojdbc14.jar).\n\n4. Save the configuration.\n\n5. Restart the server.\n\nNote: In a network deployment environment, change the variable value at the cell level and in all of the nodes scopes, and restart all of the servers and deployment manager processes.\nIf the Oracle server or client is installed and configured correctly on the same system as WebSphere Process Server, change the data source to use the Oracle 9i OCI driver. 1. Log on to the administrative console and navigate to Resources > JDBC > Data sources.\n\n2. Select the data source with the JNDI name jdbc/WPSDB.\n\n3. Change the URL format from Thin to OCI. For example, if the original URL is jdbc:oracle:thin:@localhost:1521:WPRCSDB, change it to jdbc:oracle:oci:@WPRCSDB.\n\n4. Save the configuration.\n\n5. Restart the server.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q049", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "Oracle requires that you have special permissions to attempt to perform the recovery.\nIf there is a system crash during a distributed transaction, the WebSphere Application Server transaction manager will attempt to clean up any failed transactions which it finds in the transaction logs.\nWhen the recovery involves an Oracle XAResource, the Oracle JDBC driver\noracle.jdbc.xa.OracleXAResource.recover function will make a call to DIST_TXN_SYNC.\n\nThe above error occurs when the user trying to execute the .recover method does not have sufficient privileges to make a call to DIST_TXN_SYNC.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q049", "section_id": 1, "heading": "ENVIRONMENT", "parent": null, "text": "This problem can occur with all versions of Oracle: 10g, 11g, and 12g.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q049", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Run the following commands as user SYS:\n\ngrant select on pending_trans$ to ;\ngrant select on dba_2pc_pending to ;\ngrant select on dba_pending_transactions to ;\ngrant execute on dbms_system to ; (If using Oracle 10.2.0.3 or lower JDBC driver)\ngrant execute on dbms_xa to ; (If using Oracle 10.2.0.4 or higher JDBC driver)\n\nWhere is the username configured in the Oracle datasource's authentication alias.\n\nThis problem is mentioned under Oracle bug: 3979190. Running the preceding commands solve the problem.\n\nUpdate: Since the SYS.DBMS_SYSTEM package contains many procedures, granting execute privileges to that package gives access to all of them. In Oracle patch 5892995 (JDBC driver) and 5945463 (server), Oracle has moved the DIST_TXN_SYNC procedure to a new package called DBMS_XA. These patches are available in 10.2.0.4 and higher. By using the new DBMS_XA package, it will reduce the security risk which DBMS_SYSTEM might cause.\n\nIf the recovery of the inflight transactions is not important, then one possible workaround to this problem is to remove the transaction logs. (Does NOT apply to WebSphere Process Server and IBM Business Process Manager, please see note below for details)\n\nThe transaction logs are stored in the following folder:\n\\profiles\\\\tranlog\\\\\\\\transaction\n\nTo remove the transaction logs, do the following:\n(1) Stop the server.\n(2) Delete the '\\transaction' folder and all subdirectories.\n(3) Restart the server.\nThe above exceptions will no longer occur.\n\nNOTE: Transaction logs should NOT be deleted if running in a WebSphere Process Server or IBM Business Process Manager environment.\nThe WebSphere Process Server and IBM Business Process Manager systems can get into an inconsistent state because the logs are tightly coupled with information in other places like BPEDB, WPSDB, SIB messages and MQ, if it is configured.\n\nIf WebSphere Process Server or IBM Business Process Manager is being used, follow the information in this document:\n\nHow to resolve Transaction- and Partnerlog recovery issues in WebSphere Process Server (WPS) and IBM Business Process Manager (BPM)\nhttps://developer.ibm.com/answers/questions/168157/how-to-resolve-transaction-and-partnerlog-recovery.html [https://developer.ibm.com/answers/questions/168157/how-to-resolve-transaction-and-partnerlog-recovery.html]", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q049", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "A simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21621220]\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server for z/OS DB Connections/Connection Pooling Application Servers Runtimes for Java Technology Java SDK z/OS Application Servers Runtimes for Java Technology Java SDK", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q049", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "In the Import Data Wizard, I do the following:\n\nStep 1: I select ODBC Compliant Database\n\nStep 2: I select Driver: IBM DB2 ODBC DRIVER\n\nStep 3: I define my connection information.\n\nStep 4: I press Preview\n\nThe Error message received is:\n\n'An error occurred reading the data source.'\n\nError details are:\n\nERROR [08001] [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: \"TCP/IP\". Communication API being used: \"SOCKETS\". Location where the error was detected: \"xxx.xxx.xxx.xxx\". Communication function detecting the error: \"connect\". Protocol specific error code(s): \"10060\", \"*\", \"*\". SQLSTATE=08001\n\nERROR [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed\n\nError Type:\n\nSystem.Data.Odbc.OdbcException", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q049", "section_id": 1, "heading": "ENVIRONMENT", "parent": null, "text": "IBM Cognos ICM Admin Client using Oracle database and importing from DB2 database", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q049", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To resolve the connection issue, use an ODBC DSN as a middle-step to achieve connectivity.\n\nCreate a System DSN on the server that uses the Oracle ODBC driver, then set Cognos ICM connection string manually to use this DSN. To do this, In Import Data Wizard - Step 3, press the \"Advanced\" button and replace the existing connection string with one that uses the following format:\n\ndsn=;;pwd=\n\nPRODUCT ALIAS/SYNONYM\n Varicent\nCognos ICM", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q066", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q066", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to\nCVE-2017-14746 CVE-2017-15085 CVE-2017-15086 CVE-2017-15087 CVE-2017-15275\n\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2\n\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\n\nFLASH (ALERT)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q066", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q066", "section_id": 3, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2016-8677, CVE-2016-8678 CVE-2016-9298, CVE-2014-9915, CVE-2016-10046, CVE-2016-10047, CVE-2016-10048, CVE-2016-10049, CVE-2016-10050, CVE-2016-10051, CVE-2016-10052, CVE-2016-10053, CVE-2016-10054, CVE-2016-10055, CVE-2016-10056, CVE-2016-10057, CVE-2016-10058, CVE-2016-10059, CVE-2016-10060, CVE-2016-10061, CVE-2016-10062, CVE-2016-10063, CVE-2016-10064, CVE-2016-10065, CVE-2016-10066, CVE-2016-10067, CVE-2016-10068, CVE-2016-10069, CVE-2016-10070, CVE-2016-10071, CVE-2016-10144, CVE-2016-10145, CVE-2016-10146, CVE-2017-5506, CVE-2017-5507, CVE-2017-5508, CVE-2017-5511, CVE-2017-6498, CVE-2017-6499, CVE-2017-6500, CVE-2017-6501, CVE-2017-6502, CVE-2016-10252 and CVE-2017-6497\n\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2.\n\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\nPRODUCT ALIAS/SYNONYM\n WMB HVE IIB HVE\n\nFLASH (ALERT)", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q066", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q066", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2015-5180, CVE-2014-9984,CVE-2017-12133,CVE-2014-9804 CVE-2014-9821 CVE-2014-9825 CVE-2014-9827 CVE-2014-9832 CVE-2014-9841 CVE-2014-9843 CVE-2014-9848 CVE-2014-9850 CVE-2014-9852 CVE-2017-14172 CVE-2017-14173 CVE-2017-14174 CVE-2017-14175 CVE-2017-14248 and CVE-2017-14249\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\nPRODUCT ALIAS/SYNONYM\n WMB HVE IIB HVE\n\nIIB WMB FLASH (ALERT)", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q066", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q066", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to\nCVE-2014-8716 CVE-2017-14224 CVE-2017-14324 CVE-2017-14325 CVE-2017-14326 CVE-2017-14341 CVE-2017-14342 CVE-2017-14343 CVE-2017-14400 CVE-2017-14505 CVE-2017-14528 CVE-2017-14531 CVE-2017-14532 CVE-2017-14533 CVE-2017-14607 CVE-2017-14625 CVE-2017-14626 CVE-2017-14682 CVE-2017-14684\n\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2\n\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\n\nIIB WMB FLASH (ALERT)", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q066", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q066", "section_id": 3, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2 which is vulnerable to:\nCVE-2018-1057 , CVE-2018-1050\n\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q001", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How to diagnose 'TOO MANY OPEN FILES' issues?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q001", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Applications or servers can sometimes fail with an error indicating that\nthere are too many open files for the current process. Most of the time\nthe problem is due to a configuration too small for the current needs.\nSometimes as well it might be that the process is 'leaking' file descriptors.\nIn other words, the process is opening files but does not close them leading\nto exhaustion of the available file descriptors.\n\nIf you face the 'too many open files' error here are a few things you can\ntry to identify the source of the problem.\n1 - Check the current limits.\n2 - Check the limits of a running process.\n3 - Tracking a possible file descriptors leak.\n4 - Tracking open files in real time.\n5 - Specific to DB2.\n6 - Extra notes.\n1 - Check the current limits.\n\nThe 'ulimit -a' command will print the list of current limitations for\nthe current session. The interesting one here will be 'nofile(s)'. Any process\nstarted by your current shell will by default inherit the limits. So before\nstarting a program, check with 'ulimit -a', for example:\n\nAIX:\n\n# ulimit -a\nfile(blocks) unlimited\ndata(kbytes) unlimited\nstack(kbytes) 32768\nmemory(kbytes) 32768\ncoredump(blocks) 2097151\nnofiles(descriptors) 2000\nthreads(per process) unlimited\nprocesses(per user) unlimited\n\nSOLARIS:\n\n# ulimit -a\ntime(seconds) unlimited\nfile(blocks) unlimited\ndata(kbytes) unlimited\nstack(kbytes) 8192\ncoredump(blocks) unlimited\nnofiles(descriptors) 256\nvmemory(kbytes) unlimited\n\nLINUX:\n\n# ulimit -a\naddress space limit (kbytes) (-M) unlimited\ncore file size (blocks) (-c) 0\ncpu time (seconds) (-t) unlimited\ndata size (kbytes) (-d) unlimited\nfile size (blocks) (-f) unlimited\nlocks (-x) unlimited\nlocked address space (kbytes) (-l) 32\nmessage queue size (kbytes) (-q) 800\nnice (-e) 0\nnofile (-n) 65536\nnproc (-u) 192837\npipe buffer size (bytes) (-p) 4096\nmax memory size (kbytes) (-m) unlimited\nrtprio (-r) 0\nsocket buffer size (bytes) (-b) 4096\nsigpend (-i) 192837\nstack size (kbytes) (-s) 8192\nswap size (kbytes) (-w) not supported\nthreads (-T) not supported\nprocess size (kbytes) (-v) unlimited\n\nIf the limit is too small, you might want to increase it.\n\nAIX:\n\n# ulimit -n 8192\n\nSOLARIS:\n\n# ulimit -n 8192\n\nLINUX:\n\n# ulimit -n 8192\n2 - Check the limits of a running process.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q001", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "There are some system calls that allow you to change the current limits of a\nprocess while it is running. Therefore the values might be different from the\ndefault ones inherited from the shell. To check the current settings for a\nrunning process you can use the '/proc' API that is now available on most\nUnix flavors. For example:\n\nAIX:\n\n# procfiles \n\nLimit of file descriptors will show as 'Current rlimit'\n\nSOLARIS:\n\n# plimit \n\nLimit of file descriptors will show as 'nofiles(descriptors)'\n\nLINUX:\n\n# cat /proc//limits\n\nLimit of file descriptors will show as 'Max open files'\n3 - Tracking a possible file descriptors leak.\n\nBy checking regularly you would see the number growing on and on in case of\na leak. Keep in mind that the number of files descriptors growing does not ALWAYS\nindicate a leak. It might simply be that the process needs to open a lot of files.\n\nYou have multiple ways to do this. The first one, the easiest one, is to simply\nuse as well the '/proc' API to check how many files are opened by the process.\nThe following examples will show the file descriptors currently in use.\n\nAIX:\n\n# ls /proc//fd\nor\n# procfiles \n\nSOLARIS:\n\n# ls /proc//fd\nor\n# pfiles \n\nLINUX:\n\n# ls /proc//fd\n\nThe methods provided above are fast but they do not tell you which files are\nactually opened. It might be convenient sometimes to have the names of the files.\nFinding the list of open files with their names for a running process can be\ndone using the following commands:\n\nAIX:\n\n# procfiles -n \n\nSOLARIS:\n\n# pfiles \n\nLINUX:\n\n# lsof -p \n\nNote that this might take longer to execute as extra work has to be done to\naccess the name of the files starting from the process file descriptor.\n4 - Tracking open files in real time.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q001", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "This is a bit more advanced than the previous solutions but will provide\nmost likely the most interesting results. Tracking in real time the usage\nof file descriptors means that you have to monitor both the open() and close()\nsystem calls. To be more accurate you can use the same method to also track\nsystem calls like 'dup()' and others like 'socket()' that would create a new\nfile descriptor.\n\nTo track in real time the usage of file descriptors you can use a debugger\nlike dbx (AIX. SOLARIS) or gdb (LINUX). You can as well use system tools\nlike probevue (AIX), dtrace (SOLARIS) or systemtap (LINUX). Finally you can\nuse system traces if available. The preferred choice would be system tools\nas the ones mentioned above are actually executing within the Kernel avoiding\nthe long delays caused by debuggers.\n5 - Specific to DB2.\n\nAny of the methods described above will work for db2. Additionally DB2\nprovides you already with a few extra things. For example, you can check the\nfile descriptors limit for DB2 by looking at the db2diag.log file. You will find\nsomething like this:\n\nCur core size (bytes) = 0x000000003FFFFE00\nCur memory size (bytes) = 0x7FFFFFFFFFFFFFFF\nnofiles (descriptors) = 0x7FFFFFFFFFFFFFFF\n\nAs well DB2 has it's own set of traces that will allow you to catch the files\nopened and closed by the DB2 internal API. Note that this might not be as complete\nas tracing the regular 'open()' and 'close()' system calls at the process level.\nFor example you can do the following:\n\n# db2trc on -f trc.raw -Madd sqloopenp -Madd sqloclose\n6 - Extra notes.\n\nSome other restrictions might also apply when dealing with files like for\nexamples quotas being defined for the current user or file system. It can\nbe quotas for size, number of inodes etc... Usually when a system call is\nfailing it provides an error number (errno) that you can use to check\nthe reason for the failure in the man page for that system call.\n\nAIX SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q001", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "On an HP system, when the total number of open files reaches\n the value of nfile, TSM HP server crashes when it fails to\n open dsmameng.txt", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q001", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All IBM TSM HP server users *\n\nPROBLEM DESCRIPTION: On an HP system, when the value of *\nnfile or maxfiles is reached, TSM HP *\nserver crashes when it fails to open *\ndsmameng.txt. The error messages *\nlook like this: *\nANR2017I Administrator SERVER_CONSOLE *\nissued command: HELP anr88888 *\nANR9999D Mutex previously acquired *\nby output.c(4830). *\nANR9999D Mutex acquisition failure, *\nrc=45 (Lockf deadlock detection), *\nOUTV->mutex; thread 45 (tid 84). *\nANR7824S Server operation terminated *\nby thread 45 (SmLocalConsoleSession, *\ntid 84). *\nANR9999D Trace-back of called *\nFunctions: *\nU_STACK_TRACE: Too many open files *\nCan't open executable file ./dsmserv *\nU_STACK_TRACE: Too many open files *\nCan't open executable file ./dsmserv *\nU_STACK_TRACE: Too many open files *\nCan't open executable file ./dsmserv *\nU_STACK_TRACE: Too many open files *\nCan't open executable file ./dsmserv *\nU_STACK_TRACE: Too many open files *\nCan't open executable file ./dsmserv *\nU_STACK_TRACE: Too many open files *\nCan't open executable file ./dsmserv *\n\nRECOMMENDATION: Apply fixing level when available. *\nThis problem is currently projected to be *\nfixed in levels 5.2.5, and 5.3.1. Note *\nthat this is subject to change at the *\ndiscretion of IBM. *\n\nThe server crashes when it fails to open dsmameng.txt due to\n the system limit.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q001", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The server code has been modified to handle this situation\n properly. The server will issue messages to explain the\n problem and also provide steps to resolve it.\n The following messages will be displayed:\n \"ANR9999D psmsgnls.c(1352) Error 24 There are too many files\n open. The server cannot open language file dsmameng.txt\n\nANR8224W The Tivoli Storage Manager server has reached the\n system limit for open files. Use the System Administrator\n Manager program (SAM) to change the value of the maxfiles\n parameter. Increasing this value will increase the maximum\n number of files a process is allowed to open.\"\n\nHP customers should increase the default value of the\n maxfiles parameter. The HP Installation Guide will be updated\n with the following text:\n \"The maxfiles parameter specifies the number of files a\n process is allowed to open at any given time. The default\n value for HP is 60. However, this value is very low\n and can cause server problems. To ensure proper server\n operation, increase the maxfiles value to at least 512.\"\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q001", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC42942\nREPORTED COMPONENT NAME\n TSM SERVER 510\nREPORTED COMPONENT ID\n 5698ISMSV\nREPORTED RELEASE\n 52H\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2004-12-16\nCLOSED DATE\n 2005-02-22\nLAST MODIFIED DATE\n 2005-02-22\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q001", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R52H PSY\n UP\nR53H PSY\n UP", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q001", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Version 8.5 Refresh Pack 6 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24039185]\nVersion 8.5.0 Fix Pack 2 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24040683]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q001", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When you use IBM Business Process Manager (BPM), you might\n receive the following error messages in the log files:\n\n java.net.SocketException: Too many open files\n\n java.io.IOException: Signals that an I/O exception of some sort\n has occurred. Reason: Too many open files\n\n Java? virtual machine (JVM) is trying to get a handle on the\n ?IBM/BPM/profiles//searchIndex/artifact/\\bpm.lock file.\n\n Depending on what IBM BPM was trying to do at the time, various\n other error messages might occur that are related to too many\n files being open in the JVM.\n\n PRODUCTS AFFECTED:\n IBM Business Process Manager (BPM) Advanced\n IBM BPM Standard\n IBM BPM Express", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q001", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "File descriptor leaks on the bpm.lock file causes an error about\n there being too many files open.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q001", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A fix is available for IBM BPM V8.5.0.1 and V8.5.5.0 that\n ensures only one cluster member has write access to the index\n directory at a time.\n\nOn Fix Central (http://www.ibm.com/support/fixcentral), search\n for JR51223:\n\n1. Select IBM Business Process Manager with your edition from\n the product selector, the installed version to the fix pack\n level, and your platform, and then click Continue.\n 2. Select APAR or SPR, enter JR51223, and click Continue.\n\nWhen you download fix packages, ensure that you also download\n the readme file for each fix. Review each readme file for\n additional installation instructions and information about the\n fix.\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q001", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR51223\nREPORTED COMPONENT NAME\n BPM ADVANCED\nREPORTED COMPONENT ID\n 5725C9400\nREPORTED RELEASE\n 850\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-09-09\nCLOSED DATE\n 2014-10-08\nLAST MODIFIED DATE\n 2014-10-08\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q001", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM ADVANCED\nFIXED COMPONENT ID\n 5725C9400", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q001", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R850 PSY\n UP\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\nDIRECT LINKS TO FIXES\n3.4.2.0-SterlingSecureProxy-AIX-if0004 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FSterling+Secure+Proxy&fixids=3.4.2.0-SterlingSecureProxy-AIX-if0004&source=SAR]\n3.4.2.0-SterlingSecureProxy-HP-IA-if0004 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FSterling+Secure+Proxy&fixids=3.4.2.0-SterlingSecureProxy-HP-IA-if0004&source=SAR]\n3.4.2.0-SterlingSecureProxy-Linux_s390-if0004 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FSterling+Secure+Proxy&fixids=3.4.2.0-SterlingSecureProxy-Linux_s390-if0004&source=SAR]\n3.4.2.0-SterlingSecureProxy-Linux-if0004 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FSterling+Secure+Proxy&fixids=3.4.2.0-SterlingSecureProxy-Linux-if0004&source=SAR]\n3.4.2.0-SterlingSecureProxy-SolarisSPARC-if0004 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FSterling+Secure+Proxy&fixids=3.4.2.0-SterlingSecureProxy-SolarisSPARC-if0004&source=SAR]\n3.4.2.0-SterlingSecureProxy-Windows-if0004 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FSterling+Secure+Proxy&fixids=3.4.2.0-SterlingSecureProxy-Windows-if0004&source=SAR]\n3.4.2.0-SterlingSecureProxy-AIX-if0005 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FSterling+Secure+Proxy&fixids=3.4.2.0-SterlingSecureProxy-AIX-if0005&source=SAR]\n3.4.2.0-SterlingSecureProxy-HP-IA-if0005 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FSterling+Secure+Proxy&fixids=3.4.2.0-SterlingSecureProxy-HP-IA-if0005&source=SAR]\n3.4.2.0-SterlingSecureProxy-Linux_s390-if0005 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FSterling+Secure+Proxy&fixids=3.4.2.0-SterlingSecureProxy-Linux_s390-if0005&source=SAR]\n3.4.2.0-SterlingSecureProxy-Linux-if0005 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FSterling+Secure+Proxy&fixids=3.4.2.0-SterlingSecureProxy-Linux-if0005&source=SAR]\n3.4.2.0-SterlingSecureProxy-SolarisSPARC-if0005 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FSterling+Secure+Proxy&fixids=3.4.2.0-SterlingSecureProxy-SolarisSPARC-if0005&source=SAR]\n3.4.2.0-SterlingSecureProxy-Windows-if0005 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FSterling+Secure+Proxy&fixids=3.4.2.0-SterlingSecureProxy-Windows-if0005&source=SAR]", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q001", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "CD Adapter is receiving an error \"Too Many Open Files\"", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q001", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "STRRTC - 468626\n RJ/RJ\n Circumvention:\n Update to latest SSP Build", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q001", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "SSP3420 Customers running many simultaneous C:D transfers\n through SSP getting a java.net.SocketException: Too many open\n files error. These open files are sockets which have not been\n closed.", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q001", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Now close every used socket at the end of a\n C:D transfer.\n\nTEMPORARY FIX\nSupplied SSP3420 iFix 4 to Customer which contained fix for\n RTC468626.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q001", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT09823\nREPORTED COMPONENT NAME\n STR SECURE PROX\nREPORTED COMPONENT ID\n 5725D0300\nREPORTED RELEASE\n 342\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2015-07-02\nCLOSED DATE\n 2015-09-01\nLAST MODIFIED DATE\n 2015-09-01\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q001", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n STR SECURE PROX\nFIXED COMPONENT ID\n 5725D0300", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q001", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R342 PSY\n UP", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q001", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "mbatchd cannot start up with the message \"mbatchd: createThreadedChild: socketpair() failed, Too many open files.\"\n\nThis occurs because mbatchd has reached the threashold of the open file limit and cannot open any new files.\n\nTo resolve this issue, increase the open file limit for the mbatchd process. Because mbatchd is started by sbatchd, this must be done for sbatchd as well.\n\n1. Run \"badmin hshutdown\" on the master machine to shutdown the sbatchd daemon.\n2. Run \"badmin mbatchdrestart\" to shutdown the mbatchd daemon.\n3. Change to the root user and check the limit. If the limit is too small, use the system command limit or ulimit to increase it first.\n4. Run \"badmin hstartup\" to start the sbatchd and mbatchd daemons again.\n5. Monitor the cluster and see whether the problem still happens.\n\nCross reference information Segment Product Component Platform Version Edition IBM Spectrum Computing IBM Spectrum LSF", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q073", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "MSSQL Server:\nWhen there are many sync activities occurring on the ICN/Sync server, the SQL database server may encounter deadlock issue on the SyncItems table inside the Sync database. A deadlock message of \"Transaction (Process ID) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim.\" will be logged in the ICN server log.\n\nOracle Server:\nWhen the sync server is under load for a long period of time, the disk read queue on the Oracle database server may increase and the Oracle AWR reports may show indications of increasing disk read waits accessing the SyncItems table and index. Users may notice slower response times.\n\nIBM DB2 Server:\nWhen the sync server is under load for a long period of time, end user may experience longer than expected response time for any Sync activities. System vitals, such as CPU and memory may look normal at the time of the slowness.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q073", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To help resolve these symptoms, consider performing the following:\n\u00b7 Add a composite non-clustered index on the OBJECTID and USERID columns (in that order) on the SyncItems table. Name the index I_SI_OID_UID, since future fix pack upgrades will not add the index I_SI_OID_UID if it already exists.\n\u00b7 Collect table and index statistic after the index is created to ensure all the statistics are up to date.\n\nWhat is this document:\nThis document has the abstract of a technical article that is available to authorized users after you have logged on. Please use the link to actual document below to access the full document. You will be asked to log on if you are not already logged in. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.\n\nabstract text\nASD / GHOST LINKS / OPEN MENU SHOWS GHOST LINKS WHICH CANNOT BE CLEANED BY CATDUA.\n\nlink to actual document\nhttp://www.ibm.com/support/docview.wss?uid=swg1HD46358 [http://www.ibm.com/support/docview.wss?uid=swg1HD46358]", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q073", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "This document provides troubleshooting information regarding the QHST message queue.\n\nQHST\n\nThe history (QHST) log consists of a message queue and a physical file known as a log-version. Messages sent to the log message queue are written by the system to the current log-version physical file. It is the role of the SCPF job to move messages from the QHST message queue to the log-version physical file. There are numerous errors that can cause the logging to QHST to stop. If the SCPF job has errors or is not getting enough time to run, the messages will not be removed from QHST. This can cause the QHST message queue to extend and eventually fill to the point where no more messages are allowed to be posted to the QHST message queue.\n\nCommand DSPOBJD OBJ(QSYS/QHST) OBJTYPE(*MSGQ) will show the current size of the QHST message queue. QHST, as well as all message queues, can reach a maximum size of 16 MB. When the QHST message queue has been extended the maximum number of times, message CPF2460 will appear that says it has been extended the maximum number of 488 times. This limit is based on the 16 MB maximum size of the message queue.\n\nUnder normal conditions, the amount of messages put to the QHST message queue will vary throughout the day. When the queue is at certain thresholds, the QMHLOGER code in the SCPF job is run to move the messages from the QHST message queue to the QHST physical file. If the system determines it is getting too far behind, it will change the priority of the SCPF job to 0. When this happens, message CPI2413 is logged (run priority for SCPF has been changed to 0.). When the SCPF job catches up, message CPI2414 is logged (original run priority for SCPF has been reinstated), and the priority is returned to normal.\n\nSystem value QHSTLOGSIZ plays a part in how often a new history log version needs to be created. If that is larger, the system does not have to create a physical file as often.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q073", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Some of the common reasons that messages stop logging to QHST are as follows: 1. Excessive messages. A job or a large number of jobs generate messages faster than the system can move them from the QHST message queue to the log-file. 2. The QHST message queue is corrupted. No messages are able to be logged to QHST. 3. There is a problem with the SCPF job that is preventing it from removing messages from the QHST message queue. What are some potential messages that indicate a problem with QHST? 1. CPF2469 - Error occurred when sending message&1. 2. CPF2460 - Message queue QHST could not be extended. 3. CPF4167 - Job cannot create any more spooled files. If this is in SCPF job, then it may not be able to remove messages from the QHST message queue due to some corruption. 4. CPF2503 - Message queue for system log QHST damaged. 5. CPF2477 - Message queue QHST currently in use. Seen by issuing the DSPLOG command or sending a message to QHST. 6. CPD2537 - All messages have not been logged to the history log. Seen by issuing the DSPLOG command. 7. CPI2413 \u2013 Run priority for SCPF has been changed to 0. Indicates the system recognized it was falling behind moving messages from QHST message queue to the file log. 8. CPI2414 - Original run priority for SCPF has been reinstated. System determines is has caught up with QHST message logging. 9. CPF2456 - Log version &1 in &2 closed and should be saved. 10. CPF2553 - Message queue &1 extended. 11. CPD2446 - Message queue was extended. You should try the following steps when a QHST problem occurs: 1. Try to send a message to QHST: SNDMSG TEST QHST. What happens? If this fails, send in the job log showing the command and its error messages. 2. Dump QHST message queue (will show IBM if it is corrupted): DMPOBJ QHST *MSGQ 3. What happens with DSPLOG or DSPLOG with a time specified? If it fails, send in the job log showing the command and its error messages. If it is successful, send in the last page from the current date. 4. SCPF job log. Use WRKJOB JOB(000000/QSYS/SCPF) OUTPUT(*PRINT) OPTION(*ALL). 5.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q073", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "QMHLOGER needs to be running in the SCPF job. Get multiple dumps of the SCPF job call stack. Use WRKJOB JOB(000000/QSYS/SCPF) OUTPUT(*PRINT) OPTION(*PGMSTK). 6. If the SCPF job is related to the QHST issue, collect any spooled files created under the SCPF job as this information may be related. 7.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q073", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Is the message queue in use?\n\nAfter all necessary data is collected, if logging has stopped and issuing the DSPLOG command does not cause QMHLOGER to start running in the SCPF job, and you do not mind losing messages that are in the QHST message queue, sometimes deleting QHST (DLTMSGQ QHST) will get logging started again. After the delete, try SNDMSG TEST QHST and then issue the DSPLOG command a couple times to see if the TEST message appears using DSPLOG.\nTo monitor for QHST filling the Start Watch ( STRWCH) command to start a watch and then a user exit program could be created to act on the watch event. For example, it could watch for CPI2413 being sent to QSYSOPR. STRWCH SSNID(WCHCPI2413) WCHPGM(MYLIB/MONQHST) WCHMSG((CPI2413))\n\nWe recommend getting and staying current on the latest PTFs for QMHLOGER and QMHLDISP.\n\nCross reference information Segment Product Component Platform Version Edition Operating System IBM i 7.1 Operating System IBM i 6.1 Operating System IBM i 7.3 Operating System IBM i 7.2\nHISTORICAL NUMBER\n 516471946\n\nWhat is this document:\nThis document has the abstract of a technical article that is available to authorized users after you have logged on. Please use the link to actual document below to access the full document. You will be asked to log on if you are not already logged in. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.\n\nabstract text\nASD: GHOST LINKS / GHOST LINKS NOT CLEANED BY CATDUA.\n\nlink to actual document\nhttp://www.ibm.com/support/docview.wss?uid=swg1HD50749 [http://www.ibm.com/support/docview.wss?uid=swg1HD50749]\n\nAIX SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q073", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "CATALOG : GHOST LINK ARE DISPLAYED WITH\n EXISITING CATALOG FILES.\n .\n Scenario:\n 1. Open the Catalog File in CATIA\n 2. Click on File ? Send to\n .\n OBSERVATION:\n 1. A ghost ling with the other catalog file is\n observed.\n .\n EXPECTED RESULT:\n There should not be any ghost link to the other\n catalog file\n .\n .", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q073", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "CATALOG : GHOST LINK ARE DISPLAYED WITH EXISITING CATALOG FILES\n CATALOG : GHOST LINK ARE DISPLAYED WITH\n EXISITING CATALOG FILES.\n .\n Scenario:\n 1. Open the Catalog File in CATIA\n 2. Click on File ? Send to\n .\n OBSERVATION:\n 1. A ghost ling with the other catalog file is\n observed.\n .\n EXPECTED RESULT:\n There should not be any ghost link to the other\n catalog file\n .\n .", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q073", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "null\n\nTHIS PROBLEM WILL BE FIXED ON CATIA VERSION\n 5 RELEASE 19 GA level.\n NOTE THAT THIS PROBLEM WILL ALSO BE FIXED\n ON V5R18SP01 AND ON V5R17SP07.\n .\n Incident Diagnosis\n GHOST LINK ARE DISPLAYED WITH EXISITING\n CATALOG FILES\n .\n Correction Explanation\n A description instance has a reference in another\n document. A new CATDUA rule CCL_6 cleans the\n existing ghost link.\n .\n Answer and By-Pass\n None\n .\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q073", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n HD64596\nREPORTED COMPONENT NAME\n CATIA V5 NT>XP\nREPORTED COMPONENT ID\n 569151000\nREPORTED RELEASE\n 516\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2007-05-28\nCLOSED DATE\n 2007-06-29\nLAST MODIFIED DATE\n 2007-10-01\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q073", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n CATIA V5 NT>XP\nFIXED COMPONENT ID\n 569151000", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q073", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R518 PSN SP51801\n UP07/10/01 I 1000", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q019", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "The \u201cFREAK: Factoring Attack on RSA-EXPORT keys\" TLS/SSL client and server vulnerability affects IBM WebSphere Application Server Versions 6.1, 7, 8, 8.5, and 8.5.5 that are used by IBM Rational RequisitePro.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q019", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Please consult the Security Bulletin: Vulnerability with RSA Export Keys may affect IBM WebSphere Application Server (CVE-2015-0138) [http://www.ibm.com/support/docview.wss?uid=swg21698613] for vulnerability details and information about fixes.\n\nCVEID: CVE-2015-0138 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0138]\nDESCRIPTION: A vulnerability in various IBM SSL/TLS implementations could allow a remote attacker to downgrade the security of certain SSL/TLS connections. An IBM SSL/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers.\n\nThis vulnerability is also known as the FREAK attack.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691 [http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q019", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Rational RequisitePro, RequisiteWeb Server component.\n\nVersion Status 7.1.3.x, 7.1.4.x This vulnerability only applies to RequisiteWeb component, and it only applies if one of the following conditions exist:\nYou have installed RequisiteWeb server into an existing WAS profile, and that profile supports a non-default set of ciphers.\nYou modified the default set of ciphers in the WAS profile created during the installation of RequisitePro. 7.1.0.x, 7.1.1.x, 7.1.2.x This vulnerability only applies to the RequisiteWeb component, other parts of RequisitePro are not affected. In addition, this vulnerability only applies if you modified the RequisiteWeb WAS profile by changing its set of supported ciphers. REMEDIATION/FIXES\nReview the security bulletin referenced above and apply the relevant fixes to your WAS installation and WAS profiles used for RequisiteWeb.\n\nAffected version Applying the fix 7.1.3.x, 7.1.4.x Apply the appropriate WebSphere Application Server directly to your RequisiteWeb server host. No particular RequisitePro steps are necessary. 7.1.0.x, 7.1.1.x and 7.1.2.x Document 1390803 [http://www-01.ibm.com/support/docview.wss?uid=swg21390803] explains how to update WebSphere Application Server for RequisiteWeb servers for 7.1.0.x, 7.1.1.x and 7.1.2.x releases. WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q019", "section_id": 3, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q019", "section_id": 4, "heading": "REFERENCES", "parent": null, "text": "Complete 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\nThe vulnerability was reported to IBM by Karthikeyan Bhargavan of the PROSECCO team at INRIA\nThe 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.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q019", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition that is used by WebSphere Application Server underneath IBM Business Process Manager and WebSphere Lombardi Edition. These issues were disclosed as part of the IBM SDK Java\u2122 Technology Edition updates in January 2015. This bulletin also addresses the \u201cFREAK: Factoring Attack on RSA-EXPORT keys\" TLS/SSL client and server vulnerability.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q019", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2015-0138 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0138]\nDESCRIPTION: A vulnerability in various IBM SSL/TLS implementations could allow a remote attacker to downgrade the security of certain SSL/TLS connections. An IBM SSL/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers.\n\nThis vulnerability is also known as the FREAK attack.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691 [http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)\n\nCVEID: CVE-2014-6593 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6593]\nDESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100153 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100153] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N)\n\nCVEID: CVE-2015-0400 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0400]\nDESCRIPTION: An unspecified vulnerability related to the Libraries component could allow a remote attacker to obtain sensitive information.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100149 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100149] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)\n\nCVEID: CVE-2015-0410 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0410]\nDESCRIPTION: An unspecified vulnerability related to the Security component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100151 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100151] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q019", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Business Process Manager V7.5.x through V8.5.6.0\nWebSphere Lombardi Edition V7.2.0.x\n\nFor earlier unsupported versions of the products, IBM recommends upgrading to a fixed, supported version of the product. REMEDIATION/FIXES\nIBM SDK Java\u2122 Technology Edition is used in WebSphere Application Server. See the following two security bulletins for vulnerability details and information about fixes.\nSecurity Bulletin: Vulnerability with RSA Export Keys may affect IBM WebSphere Application Server (CVE-2015-0138) [http://www.ibm.com/support/docview.wss?uid=swg21698613]\nSecurity Bulletin: Multiple vulnerabilities in IBM Java SDK affect WebSphere Application Server January 2015 CPU [http://www-01.ibm.com/support/docview.wss?uid=swg21695362]\n\nIBM SDK Java\u2122 Technology Edition is also used in IBM Process Designer. Install the interim fix for APAR IT07386 for your current version of IBM Business Process Manager or WebSphere Lombardi Edition.\nIBM Business Process Manager Express [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Express&release=All&platform=All&function=aparId&apars=IT07386]\nIBM Business Process Manager Standard [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Standard&release=All&platform=All&function=aparId&apars=IT07386]\nIBM Business Process Manager Advanced [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Advanced&release=All&platform=All&function=aparId&apars=IT07386]\nWebSphere Lombardi Edition [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Lombardi+Edition&release=All&platform=All&function=aparId&apars=IT07386]\n\nIf you are on earlier unsupported releases, IBM strongly recommends to upgrade. WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q019", "section_id": 3, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.\n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www-03.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q019", "section_id": 4, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] IBM Java SDK Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg21695474]\nSecurity Bulletin: Vulnerability with RSA Export Keys may affect IBM WebSphere Application Server (CVE-2015-0138) [http://www.ibm.com/support/docview.wss?uid=swg21698613]\nSecurity Bulletin: Multiple vulnerabilities in IBM Java SDK affect WebSphere Application Server January 2015 CPU [http://www-01.ibm.com/support/docview.wss?uid=swg21695362] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] ACKNOWLEDGEMENT\nCVE-2015-0138 was reported to IBM by Karthikeyan Bhargavan of the PROSECCO team at INRIA\n\nCHANGE HISTORY\n 2015-04-03: Original Version Published\nThe 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\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Express Security Linux, Linux zSeries, Windows 8.5.6, 8.5.5, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration IBM Business Process Manager Standard Security AIX, Linux, Linux zSeries, Solaris, Windows 8.5.6, 8.5.5, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration WebSphere Lombardi Edition Security AIX, HP-UX, Linux, Linux zSeries, Linux/x86, Solaris, Windows, Windows Vista, Windows XP 7.2.0.5, 7.2.0.4, 7.2.0.3, 7.2.0.2, 7.2.0.1, 7.2", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q019", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "The \u201cFREAK: Factoring Attack on RSA-EXPORT keys\" TLS/SSL client and server vulnerability (CVE-2015-0138) may affect IBM WebSphere Application Server Community Edition.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q019", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2015-0138\nDESCRIPTION: A vulnerability in various IBM SSL/TLS implementations could allow a remote attacker to downgrade the security of certain SSL/TLS connections. An IBM SSL/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers.\n\nThis vulnerability is also known as the FREAK attack.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691 [http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q019", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM WebSphere Application Server Community Edition 3.0.0.4", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q019", "section_id": 3, "heading": "WORKAROUNDS AND MITIGATIONS", "parent": null, "text": "Upgrade your IBM SDK for Java to an interim fix level as determined below:\nIBM SDK 6.0:\nIBM SDK, Java Technology Edition, Version 6R1 Service Refresh 8 Fix Pack 3 (required) + IV70681 [http://www-01.ibm.com/support/docview.wss?uid=swg24039651]\n\nIBM SDK 7.0:\nIBM SDK, Java Technology Edition, Version 7 Service Refresh 8 FP10 (optional) +IV70681 [http://www-01.ibm.com/support/docview.wss?uid=swg24039665]\nIBM SDK, Java Technology Edition, Version 7R1 Service Refresh 2 FP10 (optional) + IV70681 [http://www-01.ibm.com/support/docview.wss?uid=swg24039687]", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q019", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q019", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS Guide [http://www.first.org/cvss/cvss-guide.html]\nOn-line Calculator V2 [http://nvd.nist.gov/cvss.cfm?calculator&adv&version=2] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] *The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.\n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q019", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "GSKit is an IBM component that is used by IBM Tivoli Network Manager IP Edition. The GSKit that is shipped with IBM Tivoli Network Manager IP Edition contains multiple security vulnerabilities including the \u201cFREAK: Factoring Attack on RSA-EXPORT keys \" TLS/SSL client and server vulnerability. IBM Tivoli Network Manager IP Edition and WebSphere Application Server shipped with IBM Tivoli Network Manager have addressed the applicable CVEs.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q019", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2014-6221 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6221]\nDESCRIPTION: Random Data Generation using GSKit MSCAPI/MSCNG Interface Code does not generate cryptographically random data. An attacker could use this weakness to gain complete confidentially and/or integrity compromise.\nCVSS Base Score: 8.8\nCVSS Temporal Score: See http://exchange.xforce.ibmcloud.com/#/vulnerabilities/98929 [http://exchange.xforce.ibmcloud.com/#/vulnerabilities/98929] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:C/I:C/A:N)\n\nCVEID: CVE-2015-0138 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0138]\nDESCRIPTION: A vulnerability in various IBM SSL/TLS implementations could allow a remote attacker to downgrade the security of certain SSL/TLS connections. An IBM SSL/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers.\n\nThis vulnerability is also known as the FREAK attack.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691 [http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)\n\nCVEID: CVE-2015-0159 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0159]\nDESCRIPTION: An unspecified error in GSKit usage of OpenSSL crypto function related to the production of incorrect results on some platforms by Bignum squaring (BN_sqr) has an unknown attack vector and impact in some ECC operations.\nCVSS Base Score: 2.6\nCVSS Temporal Score: See http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100835 [http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100835] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:N/I:P/A:N)\n\nPlease consult the security bulletin Vulnerability with RSA Export Keys may affect IBM WebSphere Application Server (CVE-2015-0138) [http://www-01.ibm.com/support/docview.wss?uid=swg21698613] [http://www-01.ibm.com/support/docview.wss?uid=swg21695362] [Vulnerability%20with%20RSA%20Export%20Keys%20may%20affect%20IBM%20WebSphere%20Application%20Server%20(CVE-2015-0138)] for vulnerability details and information about IBM WebSphere Application Server fixes.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q019", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Tivoli Network Manager IP Edition Interim Fixes for GSKit:\nNote:The SSL connection between Tivoli Network Manager IP Edition and Tivoli Netcool/OMNIbus is affected.\nSingle server SSL users should upgrade to an appropriate OMNIbus fixpack to obtain the GSKit fix.\nRemote OMNIbus SSL connection users should install the Interim Fix below on Tivoli Network Manager IP Edition.\n\nDownload IV71123_IV76121 gskit Interfim Fix or higher level of fix pack from Fix Central\n\nAffectedProduct VRMF APAR Remediation/First Fix Tivoli Network Manager IP Edition 3.8.0.7 IV71123 [http://www-01.ibm.com/support/docview.wss?uid=swg24039199]\n\nhttps://www.ibm.com/support/entry/myportal/product/tivoli/tivoli_network_manager_ip_edition?productContext=1740397766 [https://www.ibm.com/support/entry/myportal/product/tivoli/tivoli_network_manager_ip_edition?productContext=1740397766] Tivoli Network Manager IP Edition 3.9.0.4 IV71123 [http://www-01.ibm.com/support/docview.wss?uid=swg24036687] [http://www-01.ibm.com/support/docview.wss?uid=swg24039199]\nhttps://www.ibm.com/support/entry/myportal/product/tivoli/tivoli_network_manager_ip_edition?productContext=1740397766 [https://www.ibm.com/support/entry/myportal/product/tivoli/tivoli_network_manager_ip_edition?productContext=1740397766] Tivoli Network Manager IP Edition 4.1.1.1 IV71123 [http://www-01.ibm.com/support/docview.wss?uid=swg24039346] [http://www-01.ibm.com/support/docview.wss?uid=swg24039199]\nhttps://www.ibm.com/support/entry/myportal/product/tivoli/tivoli_network_manager_ip_edition?productContext=1740397766 [https://www.ibm.com/support/entry/myportal/product/tivoli/tivoli_network_manager_ip_edition?productContext=1740397766] Tivoli Network Manager IP Edition 4.1 IV71123 [http://www-01.ibm.com/support/docview.wss?uid=swg24036690] [http://www-01.ibm.com/support/docview.wss?uid=swg24039199]\nhttps://www.ibm.com/support/entry/myportal/product/tivoli/tivoli_network_manager_ip_edition?productContext=1740397766 [https://www.ibm.com/support/entry/myportal/product/tivoli/tivoli_network_manager_ip_edition?productContext=1740397766]\nIBM WebSphere Application Server fixes:\n\nVulnerability with RSA Export Keys may affect IBM WebSphere Application Server (CVE-2015-0138) [http://www-01.ibm.com/support/docview.wss?uid=swg21698613] Affected Product and Version(s) Product and Version shipped as a component Tivoli Network Manager IP Edition 3.8 Bundled the TIP version 1.1.1.x, IBM WebSphere version 6.1.0.x and the JRE from IBM SDK Java 2 Technology Edition Version 5. Tivoli Network Manager IP Edition 3.9 Bundled the TIP version 2.1.0.x, IBM WebSphere version 7.0.0.x and the JRE from IBM SDK Java 2 Technology Edition Version 6. Tivoli Network Manager IP Edition 4.1 Bundled the TIP version 2.2.0.x, IBM WebSphere version 7.0.0.x and the JRE from IBM SDK Java 2 Technology Edition Version 6. Tivoli Network Manager IP Edition 4.1.1 Bundled the TIP version 2.2.0.x, IBM WebSphere version 7.0.0.x and the JRE from IBM SDK Java 2 Technology Edition Version 6.\nNote: If TIP has been upgraded, please follow the TIP security bulletin to upgrade the appropriate IBM WebSphere version. 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.", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q019", "section_id": 3, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q019", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] *The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.\n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q019", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "The \u201cFREAK: Factoring Attack on RSA-EXPORT keys\" TLS/SSL client and server vulnerability affects IBM\u00ae Runtime Environment Java\u2122 Technology Edition 6SR16 (and earlier) used by WebSphere Message Broker and the IBM\u00ae Runtime Environment Java\u2122 Technology Edition 7SR8 (and earlier) or 7R1 (and earlier) used by IBM Integration Bus.", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q019", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2015-0138 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0138]\nDESCRIPTION: A vulnerability in various IBM SSL/TLS implementations could allow a remote attacker to downgrade the security of certain SSL/TLS connections. An IBM SSL/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers.\n\nThis vulnerability is also known as the FREAK attack.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691 [http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q019", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Integration Bus V9, V10\nIBM Integration Bus Toolkit V9,\nWebSphere Message Broker V7 and V8\nWebSphere Message Broker Toolkit V7 and V8", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q019", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Product VRMF APAR Remediation/Fix IBM Integration Bus V10 IT07823\nIT07802 The APARs are available in fixpack 10.0.0.1\nhttp://www.ibm.com/support/docview.wss?uid=swg24040056 [http://www.ibm.com/support/docview.wss?uid=swg24040056] IBM Integration Bus V9 IT07823 An interim fix is available from IBM Fix Central.\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT07823 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT07823]\n\nThe APAR is targeted to be available in fix pack 9.0.0.4. IBM Integration Toolkit V9 IT07802 An interim fix is available at [http://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v90/MB900301/]\nhttp://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v90/MB900301/ [http://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v90/MB900301/] WebSphere Message Broker\nV8\nIT07736 An interim fix is available from IBM Fix Central.\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT07736 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT07736]\n\nThe APAR is targeted to be available in fix pack 8.0.0.6. WebSphere Message Broker Toolkit V8 IT07802 An interim fix is available at [http://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v80/MB800501/]\nhttp://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v80/MB800501/ [http://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v80/MB800501/] WebSphere Message Broker\nV7\nIT07736 An interim fix is available from IBM Fix Central.\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT07736 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT07736]\n\nThe APAR is targeted to be available in fix pack 7.0.0.8. WebSphere Message Broker Toolkit V7 IT07802 An interim fix is available at\nhttp://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v70/MB700702/ [http://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v70/MB700702/]\nYou should verify applying this fix does not cause any compatibility issues.\n\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at :\nhttp://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308] WORKAROUNDS AND MITIGATIONS\nNone known", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q019", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q019", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q019", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT\nThe vulnerability was reported to IBM by Karthikeyan Bhargavan of the PROSECCO team at INRIA\n\nCHANGE HISTORY\n 01-Apr-2015: Original Copy Published\n01-Jun-2015: Added V10 & Toolkit fix links\nThe 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\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Security AIX, HP-UX, Linux, Solaris, Windows 10.0, 9.0\nPRODUCT ALIAS/SYNONYM\n WMB IIB", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q184", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The following error message can be observed in the SystemOut.log file:\n\nCWSXM0100E: Multiple replies have been produced for a single request flow in module \n\nMore than one invocation can occur from a single request.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q184", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "This error occurs when a mediation primitive is wired more than once to the next mediation primitive. It might seem to be a single wire. However, upon closer inspection, more than one wire exists.\n\nBy mistake, primitives might be wired more than once when there is only one wire. See the following screen shot:\n[/support/docview.wss?uid=swg21584783&aid=1]\n\nIf you move the primitives in question, however, you notice that there are more wires underneath:\n\n[/support/docview.wss?uid=swg21584783&aid=2]", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q184", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To solve this problem, complete the following steps:\n\n1. Delete any redundant wires.\n\n2. Save the project.\n\n3. Redeploy the application to the server.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q184", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#IC67220: OUTSTANDING PROCESSING OCCURS IN AN AGGREGATIO [http://www.ibm.com/support/docview.wss?uid=swg1IC67220]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Advanced Mediation AIX, Linux, Solaris, Windows, z/OS 8.0, 7.5.1, 7.5.0.1, 7.5 Business Integration WebSphere Process Server Mediation AIX, HP-UX, Linux, Solaris, Windows, z/OS 7.0.0.4, 7.0.0.3, 7.0.0.2, 7.0.0.1, 7.0, 6.2.0.3, 6.2.0.2, 6.2.0.1, 6.2\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q184", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When you attempt to store more than 64Kb of data on a Mediation\n Flow Component's correlation context store, a\n UTFDataFormatException is thrown and the data is not saved.\n\n The exception message seen in the SystemOut.log is of the form:\n\n Caused by: java.io.UTFDataFormatException at\n java.io.DataOutputStream.writeUTF(DataOutputStream.java(\n CompiledCode))\n at com.ibm.ws.sibx.mediation.flowaction.impl.sca.AsyncInvocatio\n n.write(AsyncInvocation.java:331) at\n com.ibm.ws.sibx.context.impl.ContextStoreDestinationImpl.create\n StoreMessage(ContextStoreDestinationImpl.java:423)\n ...", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q184", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Users of WebSphere Enterprise Service Bus *\nand WebSphere Process Server v6.0 where *\na Mediation Flow Component is being used *\nto store more than 64Kb data on the *\ncorrelation context store. *\n\nPROBLEM DESCRIPTION: Users are unable to store more than *\n64Kb of data on the correlation *\ncontext store for a Mediation Flow *\nComponent. *\n*\nThis is due to a program defect, no *\nworkaround is known. *\n\nRECOMMENDATION: If you encounter this problem, you are *\nadvised to install the fix pack which *\ncontains the code fix associated with this *\nAPAR. *\n\n The correlation context store can be used to store user data in\n a Mediation Flow Component, which permits data to be saved on\n a request message flow, and recalled when the corresponding\n response message is received. This permits the use of\n information in the response flow which was only available when\n the request flow was processed, without having to encapsulate\n the data within the message body itself to be propogated\n downstream and back again in the response flow.\n\n However, if you attempt to store more than 64Kb data within\n this data store, the runtime server throws an exception, of\n the form:\n\n java.io.UTFDataFormatException\n at java.io.DataOutputStream.writeUTF(DataOutputStream.java\n (Compiled Code))\n at com.ibm.ws.sibx.mediation.flowaction.impl.sca.\n AsyncInvocation.write(AsyncInvocation.java:331)\n at com.ibm.ws.sibx.context.impl.ContextStoreDestinationImpl\n .createStoreMessage(ContextStoreDestinationImpl.java:423)\n at com.ibm.ws.sibx.context.impl.ContextStoreDestinationImpl\n .setPersistentContext(ContextStoreDestinationImpl.java:370)\n at com.ibm.ws.sibx.context.impl.ContextStoreDestinationImpl\n .put(ContextStoreDestinationImpl.java:240)\n at com.ibm.wsspi.sibx.mediation.flow.ejb.MediationFlowBean\n .transactionNotSupportedWriteContext\n (MediationFlowBean.java:401)\n\n This is caused by a program defect, and there are no known\n workarounds to store more than 64Kb data on the context\n store without the code fix associated with this APAR.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q184", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The code fix associated with this APAR is currently targetted\n to be included in v6.0.2 Fix Pack 3 (6.0.2.3).\n\nThere are currently no known side effects associated with this\n code fix.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q184", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC53221\nREPORTED COMPONENT NAME\n WEB ESB FOR WIN\nREPORTED COMPONENT ID\n 5724I8200\nREPORTED RELEASE\n 200\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2007-07-13\nCLOSED DATE\n 2007-09-06\nLAST MODIFIED DATE\n 2007-09-06\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q184", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEB ESB FOR WIN\nFIXED COMPONENT ID\n 5724I8200", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q184", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R100 PSY\n UP\nR200 PSY\n UP\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q184", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When multiple applications which contain mediation flow\n components are deployed to a runtime server, an intermittent\n exception may be thrown by one of the applications:\n\n [6/16/08 11:20:47:656 CEST] 0000006f ExceptionUtil E\n CNTR0020E: EJB\n threw an unexpected (non-declared) exception during invocation\n of method \"transactionRequiredActivitySessionSupports\" on bean\n \"BeanId(MQAdapterMEDApp#MQAdapterMEDEJB.jar#Module, null)\".\n Exception data:\n com.ibm.wsspi.sibx.mediation.flow.action.FlowActionException:\n com.ibm.wsspi.sibx.context.StoreException: java.io.IOException:\n Error reading XML at\n com.ibm.ws.sibx.mediation.flowaction.impl.sca.FlowActionFactoryI\n mpl.locate(FlowActionFactoryImpl.java:664)\n at\n com.ibm.ws.sibx.scax.runtime.handler.MFCImplementationHandler.pr\n ocessMes sage(MFCImplementationHandler.java:234)\n at\n com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.proce\n ssMessag e(MessageDispatcherImpl.java:1286)\n at\n com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process(\n ManagedM essageImpl.java:815)\n\n The message processing fails when this exception is thrown. For\n this specific problem to occur, one of the mediation flow\n components must contain a BOMapper primitive. Note that this\n flow is not necessarily the one for which the error is thrown.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q184", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Users of WebSphere Enterprise Service Bus *\nand WebSphere Process Server v6.1.0 and *\nv6.1.2, who have deployed multiple *\napplications to a runtime server, at least *\none of which contains a BOMapper primitive. *\n\nPROBLEM DESCRIPTION: Message processing may fail if a *\nthread processes a mediation flow *\ncomponent's message flow which contains *\na BOMapper primitive, and then goes *\non to process a second unrelated *\nmediation flow component which makes *\nuse of an asynchronous callout, and *\ndoes not have access to the same *\nbusiness object schema definitions as *\nthe flow with the BOMapper primitive. *\n\nRECOMMENDATION: If you encounter this problem, you are *\nadvised to install the code fix which is *\nassociated with this APAR. *\n*\nAlternatively, as a workaround you can add *\nthe missing schema definition (eg. WSDL *\nfile) to the failing flow, which will also *\nresolve the problem. *\n\n When a mediation flow component which contains a BOMapper\n primitive processes a message, the Business Objects (BOs) used\n may be left in thead local storage.\n\n If the same thread then goes on to process a second mediation\n flow component, which happens to make use of an asynchronous\n callout, an attempt is made to serialise these leftover BOs\n in order to store them on the mediation component's context\n store.\n\n If this second flow does not have visibility of the schema\n definition of these BOs, the serialisation fails, an exception\n is thrown and processing of this message flow ends in failure.\n\n The form of the exception message is:\n\n CNTR0020E: EJB threw an unexpected (non-declared) exception\n during invocation of method \"transactionNotSupportedActivitySess\n ionSupports\" on bean \"BeanId(myAppModuleApp#myappMediationModule\n EJB.jar#Module, null)\". Exception data:\n\n com.ibm.wsspi.sibx.mediation.flow.action.FlowActionException:\n com.ibm.wsspi.sibx.context.StoreException: java.io.IOException:\n Error reading XML\n at com.ibm.ws.sibx.mediation.flowaction.impl.sca.FlowActi\n onFactoryImpl.locate(FlowActionFactoryImpl.java:664)\n at com.ibm.ws.sibx.scax.runtime.handler.MFCImplementation\n Handler.processMessage(MFCImplementationHandler.java:234)\n at com.ibm.ws.sca.internal.message.impl.MessageDispatcher\n Impl.processMessage(MessageDispatcherImpl.java:1286)\n at com.ibm.ws.sca.internal.message.impl.ManagedMessageImp\n l.process(ManagedMessageImpl.java:815)\n at com.ibm.wsspi.sca.ejb.module.impl.ModuleSessionBean.pr\n ocessUOWMessage(ModuleSessionBean.java:338)\n at com.ibm.wsspi.sca.ejb.module.impl.ModuleSessionBean.tr\n ansactionNotSupportedActivitySessionSupports(ModuleSessionBean.j\n ava:279)\n at com.ibm.wsspi.sca.ejb.module.EJSLocalStatelessModule_4\n 3132892.transactionNotSupportedActivitySessionSupports(EJSLocalS\n tatelessModule_43132892.java:199)\n\n Note that there are several reasons why serialisation of the\n business objects can fail in a flow, which would result in a\n similar stack track as that seen here. This APAR is only\n concerned with the one which occurs as a result of aged\n thread local storage business objects.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q184", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The product code was modified to correct this issue. There are\n no known side effects associated with this code change.\n\nThe fix was targeted to be included in the following fix packs:\n\nv6.1.0 Fix Pack 3 (6.1.0.3)\n v6.1.2 Fix Pack 2 (6.1.2.0)\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q184", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC58725\nREPORTED COMPONENT NAME\n WEB ESB FOR WIN\nREPORTED COMPONENT ID\n 5724I8200\nREPORTED RELEASE\n 300\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2008-11-01\nCLOSED DATE\n 2008-11-21\nLAST MODIFIED DATE\n 2008-11-21\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q184", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEB ESB FOR WIN\nFIXED COMPONENT ID\n 5724I8200", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q184", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R100 PSN\n UP\nR200 PSN\n UP\nR300 PSY\n UP\nR612 PSY\n UP", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q184", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Starting with WebSphere Process Server Version 7, interface maps are marked as deprecated and should not be used. If you use WebSphere Integration Developer Version 7 and attempt to use interface maps in your application workflow, an informational dialog box opens to inform you that you need to use mediation flows instead. As a WebSphere Integration Developer Version 7 user, you are also offered the option to have interface maps automatically converted into equivalent mediation flows. When you opt for the automatic conversion, WebSphere Integration Developer removes any existing interface maps from the your application assembly diagram and replaces them with mediation flows.\n\nWhen you have an interface map that is part of a relationship workflow and the mapped interface contains a request-response operation, the automatic conversion performed by WebSphere Integration Developer Version 7 results in a failing mediation flow. When the application containing the newly created mediation flow is deployed, any execution of the flow leads to a mediation runtime error with a stack trace like the following messages:\n\nCWSXM0202E: An unexpected exception occurred when processing mediation flow for component Component1 in module test\nCWSXM1025E: An unexpected exception occurred when the flow was called:\nCWSXM0111E: Service runtime exception calling an import from mediation component Component1\nin module test\nCWSXM0205E: An unexpected business logic exception occurred.:\nCWSXM3655E: Exception while executing Business Object map:\nCWLAS0015E: The Submap transform #1 in the response_Map map did not complete because of the following exception:\nCWLAS0015E: The Submap transform #2 in the response_Submap map did not complete because of the following exception:\nCWLAS0015E: The Relationship transform #5 in the response_Submap2 map did not complete because of the following exception: Business object is null.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q184", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The automatic conversion of deprecated interface maps to mediation flows offered by WebSphere Integration Developer Version 7 does not work properly when the interface maps to be converted are part of a relationship.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q184", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "The following conditions must be met for the problem to occur:\nYou are running WebSphere Process Server Version 7.0.0.0, 7.0.0 Fix Pack 1, 7.0.0 Fix Pack 2, 7.0.0 Fix Pack 3 or 7.0.0 Fix Pack 4.\nYou are using WebSphere Integration Developer Version 7 as an authoring tool for composing your business application.\nYour business application contains at least one relationship that uses interface maps.\nAny of the mapped interfaces contains a request-response operation.\nYou have used the automatic conversion offered by WebSphere Integration Developer to convert the deprecated interface maps to equivalent mediation flows.\nAfter the automatic conversion, your business application can be deployed successfully but fails at runtime while throwing a mediation runtime error as outlined in the previous symptom section.", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q184", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To resolve this problem, complete the following steps:\n\n1. Upgrade to Version 7.0.0 Fix Pack 4, if you are running WebSphere Process Server Version 7.0.0.0, 7.0.0 Fix Pack 1, 7.0.0 Fix Pack 2 or 7.0.0 Fix Pack 3,\n 2. Install the WebSphere Enterprise Service Bus APAR fix IC79270 and the WebSphere Process Server APAR fix JR40785, which can be obtained from Fix Central.\n 3. Try the automatic conversion again after completing steps 1 and 2.\n 4. After the conversion, edit the mediation flow that results from the automatic conversion in WebSphere Integration Developer and look for a business object map primitive in the mediation's request and response flows respectively. The display names of those primitives will differ, but must be equal for the mediation to work properly.\n 5. Change the display names of the business object maps in the request and response flows to match each other and save the mediation flow component afterwards.\n\nAfter these steps are successful, the problem will no longer occur.\n\nPRODUCT ALIAS/SYNONYM\n WPS\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q184", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When a WebSphere Enterprise Service Bus or WebSphere Process\n Server runtime has processed a message in a Mediation Flow\n Component and subsequent messages do not immediately occur\n on the same thread, some of the associated memory for the\n previous request is not freed up until the next message\n arrives. This can mean in some situations that a higher than\n expected memory foot print is seen during quiet periods.", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q184", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Users of WebSphere Enterprise Service Bus *\nand WebSphere Process Server v6.2 who see *\nhigher than expected memory usage from a *\nflow containing a mediation module that is *\nnot under load. *\n\nPROBLEM DESCRIPTION: A WebSphere Enterprise Service Bus or *\nWebSpshere Process Server mediation *\nmodule will retain in memory a copy *\nof the message passing through each *\nprimitive in the mediation module. *\nUnder low load this can lead to a *\nhigher than expected memory foot *\nprint for the flow. *\n\nRECOMMENDATION: *\n\nAs a message passes through a mediation module a copy of the\n message is stored in memory as it leaves each primitive. This\n is not released for garbage collection by the JVM until the\n next message has entered the module.\n Under periods of low load this may not happen immediately\n resulting in the messages being stored for a longer period and\n a higher than expected memory foot print being seen.", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q184", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The code was modified such that the stored messages are\n released for garbage collection earlier.\n\nThere are no known side effects associated with this fix.\n There is no known alternative workaround should you encounter\n this problem.\n\nThis code fix was targeted to be included in the following fix\n packs:\n 6.2.0 Fix Pack 4 (v6.2.0.4)\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q184", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC66137\nREPORTED COMPONENT NAME\n WEB ESB FOR WIN\nREPORTED COMPONENT ID\n 5724I8200\nREPORTED RELEASE\n 620\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2010-02-10\nCLOSED DATE\n 2010-03-02\nLAST MODIFIED DATE\n 2010-12-02\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n PM33047 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM33047] PM42955 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM42955]", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q184", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEB ESB FOR WIN\nFIXED COMPONENT ID\n 5724I8200", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q184", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R100 PSN\n UP\nR200 PSN\n UP\nR300 PSN\n UP\nR612 PSN\n UP\nR620 PSY\n UP\nR700 PSN\n UP", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q275", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "z/os SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q275", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Customer coded the Work Flow exit and found it could not be\n loaded by the system when requested. They were getting Unable\n to load Library messages. They had the load module in a AFP\n dataset, but it still was not loaded. They then determined the\n following -\n\nI seem to have found a fix / workaround for the problem - with\n the help of\n a more experienced C / C++ programmer on our side.\n\nI basically added the following two #pragma statements found in\n the ICMGENXT\n sample program (but not in the ICMXENT sample program)\n to my own exit code (which is basically a stripped down version\n of\n ICMXENT):\n #pragma strings(readonly)\n #pragma linkage(WXV2TEnterUE,fetchable)\n\nThen I also changed the\n \"extern long WXV2TEnterUE (struct ICMUSERSTRUCT\npCMStruct) \"\n statement to\n \"extern \"C\" long WXV2TEnterUE (struct ICMUSERSTRUCT\npCMStruct)\"\n because we are using a CPP compiler.\n\nThe following exists also need this code added to them.\n ICMXBAU, ICMXENT, ICMXLEA, and ICMXOVE\n can be made more \"z/OS ready\".", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q275", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Add the following two statements to your user exit code -\n #pragma strings(readonly)\n #pragma linkage(WXV2TEnterUE,fetchable)\n And also the following -\n Then I also changed the\n \"extern long WXV2TEnterUE (struct ICMUSERSTRUCT\npCMStruct) \"\n statement to\n \"extern \"C\" long WXV2TEnterUE (struct ICMUSERSTRUCT\npCMStruct)\"\n because we are using a CPP compiler.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q275", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USER EXIT CODE WHEN COMPILED WILL NOT LOAD. FAILS WITH A UNABLE\n TO LOAD LIBRARY ERROR MESSAGE.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q275", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The proper linkage statements were not in the exit\n program samples. The problem has been corrected.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q275", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PK11887\nREPORTED COMPONENT NAME\n CM390 LIB SER R\nREPORTED COMPONENT ID\n 5697H6000\nREPORTED RELEASE\n 830\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2005-09-15\nCLOSED DATE\n 2006-03-24\nLAST MODIFIED DATE\n 2007-11-15\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q275", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n CM390 LIB SER R\nFIXED COMPONENT ID\n 5697H6000", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q275", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R830 PSY\n UP", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q275", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "How do I make all users have the same priority and their priority decreases as they keep submitting jobs? Or do I need to specify each user. I have tried several combinations but not able to find one in which all users get same priority and priority of each user should decreases upon usage/job submission\n\nTo give all users the same fairshare for a specific queue you'd define the FAIRSHARE parameter as follows:\nFAIRSHARE = USER_SHARES[[default,1]]\n\nRun 'badmin reconfig' after you've made this change and look at the output of 'bqueues -l ' to make sure this change has taken affect. You check this by looking for the following entries in the output:\nSCHEDULING POLICIES: FAIRSHARE\nUSER_SHARES: [default, 1]\n\nCross reference information Segment Product Component Platform Version Edition IBM Spectrum Computing IBM Spectrum LSF", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q275", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do I include long descriptions when sending data in using the Maximo Enterprise Adapter (MEA) or Maximo Integration Framework (MIF)?", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q275", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Maximo 6.x MEA\n\n1. Go To Integration -> Integration Object\n\nOn the Persistent Fields tab, exclude HASLD\nOn the Non-Persistent Fields tab, include DESCRIPTION_LONGDESCRIPTION\n\nMaximo 7.x MIF\n\n1. Go To Integration -> Object Structures\n\nClick Select Action -> Exclude/Include Fields\n\nOn the Persistent Fields tab, exclude HASLD\nOn the Non-Persistent Fields tab, include DESCRIPTION_LONGDESCRIPTION\n\nMaximo 6.x/7.x XML\n\nAdd the long description tag to the inbound XML:\n\nxxxxx\n\nDo not include the HASLD tag. This column will be set automatically.\n\nThe same process will work for sending data in using flat files and interface tables, however, you must use an alias for DESCRIPTION_LONGDESCRIPTION on DB2 and SQL Server since the column name is longer than 18. If your object structure has multiple MBOs with long descriptions, you will have to use an alias to identify each column name uniquely.\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Maximo Enterprise Adapter Not Applicable", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q275", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Either no rows returned or too many rows returned when querying for long description.", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q275", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Scenario 1: Need to query long description for job tasks added to a job plan\n\nJob plan 'IT-ISSUE' has two job tasks:\nTask 10 has a long description\nTask 20 does NOT have a long description\n\n[/support/docview.wss?uid=swg21425997&aid=1] [/support/docview.wss?uid=swg21425997&aid=1]\n\nTask 10 has a long description 'task10 LDTEXT'\n\n[/support/docview.wss?uid=swg21425997&aid=2]\n\nSteps to get the long description out of the job tasks:\n\nSELECT JOBPLANID FROM JOBPLAN WHERE JPNUM='IT-ISSUE'\noutput: JOBPLANID = 51\n\nThen take output from the query above and put it in the query below:\n\nSELECT LDTEXT FROM LONGDESCRIPTION WHERE LDOWNERTABLE='JOBTASK' AND LDOWNERCOL='DESCRIPTION'\nAND LDKEY IN (SELECT JOBTASK.JOBTASKID FROM JOBTASK WHERE jobtask.jobplanid= 51)\n\noutput: LDTEXT = task10 LDTEXT\n\nNOTE: Do not use outer join between jobtask and longdescription to query for LDTEXT\n\nScenario 2: Need to query long description for the data sheet long description added to a work order\n\nData sheet 'NEWDS' has an asset function with long description.\n\n[/support/docview.wss?uid=swg21425997&aid=3]\n\n[/support/docview.wss?uid=swg21425997&aid=4]\n\nGo to the Work Order Tracking application.\nBring up a work order.\nGo to the Data Sheet tab.\nClick New Row, enter the data sheet NEWDS in the Data Sheet field.\n\n[/support/docview.wss?uid=swg21425997&aid=5]\n\nDescription for asset function 10 has a long description.\n\n[/support/docview.wss?uid=swg21425997&aid=6]\n\nSolution:\nSteps to get the long description out of the job tasks:\n\nSELECT PLUSCDSINSTRID FROM PLUSCDSINSTR WHERE DSPLANNUM ='NEWDS' AND REVISIONNUM='0' AND HASLD=1 AND ASSETFUNCTION=10\n\noutput:\nPLUSCDSINSTRID = 21\n\nThen take output from the query above and put it in the query below:\n\nSELECT * FROM LONGDESCRIPTION\nWHERE ldownertable = 'PLUSCDSINSTR' and ldownercol = 'DESCRIPTION'\nAND LDKEY IN (\nselect pluscdsinstr.pluscdsinstrID\nfrom pluscdsinstr\nwhere\nDSPLANNUM ='NEWDS' AND REVISIONNUM='0' AND HASLD=1 AND ASSETFUNCTION=10)\n\noutput:\nLDTEXT = asset function 10 LDTEXT\n\nNOTE: the query should use 'PLUSCDSINSTR' and NOT PLUSCWODSINSTR as the ldownertable.\nIf PLUSCWODSINSTR is used, it may not return any output.", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q275", "section_id": 0, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\n\nHISTORICAL NUMBER\n 74316", "logical_doc_id": 6, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q105", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q105", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2017-12418, CVE-2017-12427, CVE-2017-12428, CVE-2017-12429, CVE-2017-12430, CVE-2017-12431, CVE-2017-12432, CVE-2017-12433, CVE-2017-12434, CVE-2017-12435, CVE-2017-12563, CVE-2017-12564, CVE-2017-12565, CVE-2017-12566, CVE-2017-12587, CVE-2017-12640, CVE-2017-12641, CVE-2017-12642, CVE-2017-12643, CVE-2017-12644, CVE-2017-12654, CVE-2017-12662 CVE-2017-12663 CVE-2017-12664 CVE-2017-12665 CVE-2017-12666 CVE-2017-12667 CVE-2017-12668 CVE-2017-12669 CVE-2017-12670 CVE-2017-12671 CVE-2017-12672 CVE-2017-12673 CVE-2017-12674 CVE-2017-12675 CVE-2017-12676 CVE-2017-12983 CVE-2017-13058 CVE-2017-13059 CVE-2017-13060 CVE-2017-13061 and CVE-2017-13062\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\nPRODUCT ALIAS/SYNONYM\n WMB HVE IIB HVE\n\nFLASH (ALERT)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q105", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat and Samba (CVE-2016-2842, CVE-2016-2118, CVE-2015-5370, CVE-2016-2110, CVE-2016-2111, CVE-2016-2112, CVE-2016-2113, CVE-2016-2114, CVE-2016-2115 )", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q105", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server and Samba that are vulnerable to\n*\n*\n\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2.\n\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2 as applicable. RELATED INFORMATION\n OpenSource OpenSSL Vuln [http://openssl.org/news/secadv/20160301.txt]\nbadlock [http://badlock.org/]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\nPRODUCT ALIAS/SYNONYM\n WebSphere Message Broker WMB IBM Integration Bus IIB\n\nFLASH (ALERT)", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q105", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat - CVE-2016-3075, CVE-2016-5118, CVE-2015-8900, CVE-2015-8901, CVE-2015-8902, CVE-2015-8903, CVE-2016-4562, CVE-2016-4563, CVE-2016-4564", "logical_doc_id": 2, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q105", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2016-3075, CVE-2016-5118, CVE-2015-8900, CVE-2015-8901, CVE-2015-8902, CVE-2015-8903, CVE-2016-4562, CVE-2016-4563 and CVE-2016-4564\n\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2.\n\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2 as applicable.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\nPRODUCT ALIAS/SYNONYM\n WebSphere Message Broker WMB IBM Integration Bus IIB\n\nIIB WMB FLASH (ALERT)", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q105", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux", "logical_doc_id": 3, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q105", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to\nCVE-2017-14746 CVE-2017-15085 CVE-2017-15086 CVE-2017-15087 CVE-2017-15275\n\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2\n\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\n\nFLASH (ALERT)", "logical_doc_id": 3, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q105", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux.", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q105", "section_id": 3, "heading": "CONTENT", "parent": null, "text": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2016-2126, CVE-2016-2125, CVE-2016-2123, CVE-2016-8866, CVE-2016-9556, CVE-2016-9559, and CVE-2016-9773.\n\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2.\n\nRemediation:\n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0\nPRODUCT ALIAS/SYNONYM\n WMB HVE IIB HVE", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q067", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The process creation might hang. In the SystemOut.log file, you see a hung thread exception for a thread holding a database connection. For example:\n\n[17.07.14 15:10:55:669 CEST] 000000bd ThreadMonitor W WSVR0605W: Thread \"WorkManager.bpm-em-workmanager : 0\" (0000041d) has been active for 745100 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.\nat java.net.SocketInputStream.socketRead0(Native Method)\nat java.net.SocketInputStream.read(SocketInputStream.java:140)\nat com.ibm.db2.jcc.t4.z.b(z.java:199)\nat com.ibm.db2.jcc.t4.z.c(z.java:259)\nat com.ibm.db2.jcc.t4.z.c(z.java:372)\nat com.ibm.db2.jcc.t4.z.v(z.java:1147)\nat com.ibm.db2.jcc.t4.cb.a(cb.java:68)\nat com.ibm.db2.jcc.t4.q.a(q.java:57)\nat com.ibm.db2.jcc.t4.sb.a(sb.java:225)\nat com.ibm.db2.jcc.am.kn.a(kn.java:2936)\nat com.ibm.db2.jcc.am.kn.d(kn.java:4870)\nat com.ibm.db2.jcc.am.kn.a(kn.java:4318)\nat com.ibm.db2.jcc.am.kn.c(kn.java:4156)\nat com.ibm.db2.jcc.am.kn.executeBatch(kn.java:2436)\nat com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteBatch(WSJdbcPreparedStatement.java:1037)\nat com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.executeBatch(WSJdbcStatement.java:843)\nat com.lombardisoftware.bpd.runtime.engine.BPDInstanceDAO.insertNewBDVariables(BPDInstanceDAO.java:1292)\nat com.lombardisoftware.bpd.runtime.engine.BPDInstanceDAO.saveSearchableValues(BPDInstanceDAO.java:1005)\nat com.lombardisoftware.bpd.runtime.engine.BPDInstanceDAO.createBPDInstance(BPDInstanceDAO.java:180)\nat com.lombardisoftware.server.ejb.bpd.BPDEngineServicesCore.doStartBPD(BPDEngineServicesCore.java:452)\nat com.lombardisoftware.server.ejb.bpd.BPDEngineServicesCore.doStartBPD(BPDEngineServicesCore.java:281)\nat com.lombardisoftware.server.ejb.bpd.BPDEngineServicesCore.startBPD(BPDEngineServicesCore.java:200)\nat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\nat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)\nat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)\nat java.lang.reflect.Method.invoke(Method.java:611)\nat org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)\nat org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)\nat org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)\nat com.lombardisoftware.utility.spring.TransactionInterceptor$2.call(TransactionInterceptor.java:67)\nat com.lombardisoftware.utility.spring.ProgrammaticTransactionSupport$1.doInTransaction(ProgrammaticTransactionSupport.java:436)\nat org.springframework.transaction.jta.WebSphereUowTransactionManager$UOWActionAdapter.run(WebSphereUowTransactionManager.java:306)\nat com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.runUnderNewUOW(EmbeddableUOWManagerImpl.java:790)\nat com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.runUnderUOW(EmbeddableUOWManagerImpl.java:369)\nat org.springframework.transaction.jta.WebSphereUowTransactionManager.execute(WebSphereUowTransactionManager.java:252)\nat com.lombardisoftware.utility.spring.ProgrammaticTransactionSupport.executeInNewTransaction(ProgrammaticTransactionSupport.java:431)\nat com.lombardisoftware.utility.spring.ProgrammaticTransactionSupport.execute(ProgrammaticTransactionSupport.java:294)\nat com.lombardisoftware.utility.spring.TransactionInterceptor.invoke(TransactionInterceptor.java:65)\nat org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)\nat com.lombardisoftware.utility.spring.CoreEntryInterceptor.invoke(CoreEntryInterceptor.java:44)\nat com.lombardisoftware.utility.spring.PSCoreEntryInterceptor.invoke(PSCoreEntryInterceptor.java:14)\nat org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)\nat org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)\nat com.sun.proxy.$Proxy75.startBPD(Unknown Source)\nat com.lombardisoftware.client.delegate.BPDEngineServicesDelegateDefault.startBPD(BPDEngineServicesDelegateDefault.java:150)\nat com.lombardisoftware.core.script.js.AbstractTWSystemScriptable.startNewProcess(AbstractTWSystemScriptable.java:1458)\nat com.lombardisoftware.core.script.js.AbstractTWSystemScriptable.jsFunction_startProcessByName(AbstractTWSystemScriptable.java:979)", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q067", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The observed behavior is currently a limitation in the product.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q067", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "The following steps reproduce the issue:\n\n1. Define a UCA with an attached service. In the attached service, start a new process instance using the tw.system.startProcessByName() JavaScript method. The process that you start has variables that are defined as \"Available in Search\" within the Business Data Search section of the business process definition (BPD) editor.\n 2. Start the UCA either through an outbound message event, REST API, or an invoke-UCA-component in a service.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q067", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "In his case, use the BPMN best practice, which is to model the process with a start message event. The UCA is then attached to the start message event .\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Express Business Process Definition (BPD) Linux, Windows 8.5.5, 8.5, 8.0.1, 8.0, 7.5.1, 7.5 Business Integration IBM Business Process Manager Advanced Business Process Definition (BPD) AIX, Linux, Solaris, Windows 8.5.5, 8.5, 8.0.1, 8.0, 7.5.1, 7.5\nPRODUCT ALIAS/SYNONYM\n BPM", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q067", "section_id": 4, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24032315]\n7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23 [http://www-01.ibm.com/support/docview.wss?uid=swg24032493]\n8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24033190]\n7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25 [http://www-01.ibm.com/support/docview.wss?uid=swg24033267]\n8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24033754]\n7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27 [http://www-01.ibm.com/support/docview.wss?uid=swg24033882]\n8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24034673]\n7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29 [http://www-01.ibm.com/support/docview.wss?uid=swg24034966]\n8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24035457]\n8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24036729]\n7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31 [http://www-01.ibm.com/support/docview.wss?uid=swg24036768]\n7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg24035324]\n7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33 [http://www-01.ibm.com/support/docview.wss?uid=swg24037573]\n8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24037574]\n7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35 [http://www-01.ibm.com/support/docview.wss?uid=swg24038310]\n8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24039242]\n7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37 [http://www-01.ibm.com/support/docview.wss?uid=swg24039338]\n8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24040425]\n7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39 [http://www-01.ibm.com/support/docview.wss?uid=swg24041013]\n8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24041590]\n7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41 [http://www-01.ibm.com/support/docview.wss?uid=swg24041931]\n8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24042746]\n7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43 [http://www-01.ibm.com/support/docview.wss?uid=swg24043400]\n8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http://www-01.ibm.com/support/docview.wss?uid=swg24044096]\n7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45 [http://www-01.ibm.com/support/docview.wss?uid=swg24044551]\n8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q067", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "An application server JVM can hang if a thread logging an FFDC\n hangs.\n\n The problem can be detected by observing the WSVR0605W hung\n thread notifications in the SystemOut.log.\n\n One thread will be running the FFDCFilter.processException()\n which can be invoked from any WebSphere Application Server\n component. The thread will get stuck doing its work.\n In the following example, the thread which invoked\n FFDCFilter.processException() is stuck waiting on a response to\n the OracleConnectionWrapper.getMetaData() method call:\n\n [05/24/12 12:06:35:286 EST] 00000016 ThreadMonitor W\n WSVR0605W: Thread \"ORB.thread.pool : 32\" (000000d6) has\n been active for 304721 milliseconds and may be hung. There\n is/are 16 thread(s) in total in the server that may be hung.\n at\n oracle.jdbc.OracleConnectionWrapper.getMetaData(OracleConnection\n Wrapper.java:150)\n at\n com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.introspectSe\n lf(WSRdbManagedConnectionImpl.java:1480)\n at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n at\n sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor\n Impl.java:60)\n at\n sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod\n AccessorImpl.java:37)\n at java.lang.reflect.Method.invoke(Method.java:611)\n at\n com.ibm.ws.ffdc.impl.Formatters$IntrospectSelfFormatter$1.run(Fo\n rmatters.java:99)\n at\n com.ibm.ws.ffdc.impl.Formatters$IntrospectSelfFormatter$1.run(Fo\n rmatters.java:96)\n\n ...\n\n at\n com.ibm.ffdc.util.provider.IncidentEntry.log(IncidentEntry.java:\n 96)\n at com.ibm.ffdc.util.provider.Ffdc.log(Ffdc.java:90)\n at\n com.ibm.ws.ffdc.FFDCFilter.processException(FFDCFilter.java:114)\n at\n com.ibm.ejs.j2c.FreePool.createOrWaitForConnection(FreePool.java\n :1671)\n at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2496)\n\n Looking later in the SystemOut.log, there will be more hung\n thread notifications which show that the\n FFDCFilter.processException() method is stuck waiting on an\n Ffdc. call to complete. The stack trace of such a thread\n will look like this:\n\n [05/24/12 12:42:35:914 EST] 00000003 ThreadMonitor W\n WSVR0605W: Thread \"ORB.thread.pool : 29\" (000007f4) has been\n active for 224151 milliseconds and may be hung. There is/are 23\n thread(s) in total in the server that may be hung.\n at com.ibm.ffdc.util.provider.Ffdc.(Ffdc.java:64)\n at\n com.ibm.ffdc.util.provider.FfdcProvider.getFfdc(FfdcProvider.jav\n a:289)\n at com.ibm.ffdc.impl.Ffdc.getFfdc(Ffdc.java:188)\n at\n com.ibm.ws.ffdc.FFDCFilter.processException(FFDCFilter.java:112)\n at\n com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteUpda\n te(WSJdbcPreparedStatement.java:1179)\n at\n com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeUpdate(\n WSJdbcPreparedStatement.java:816)\n\n It is possible that the first FFDC thread which got hung (in\n this example, \"ORB.thread.pool : 32\") will eventually complete.\n If it does complete, the threads will start moving and the hang\n will clear up. However, if it never completes, then it is the\n same as if a true thread deadlock had occurred.\n\n This same type of analysis can be performed using a\n javacore/thread dump, however, javacores are not always\n available.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q067", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of IBM WebSphere Application *\nServer V7.0 and V8.0 *\n\nPROBLEM DESCRIPTION: Syncrhonization between FFDC *\nincidents can cause a server hang *\nwhen an unrecoverable problem *\noccurs in a given incident. *\n\nRECOMMENDATION: *\n\nSyncrhonization between FFDC incidents can cause a server hang\n when an unrecoverable problem occurs in a given incident.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q067", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "FFDC has been modified to ensure that incidents can continue\n to be logged from other components when a given component's\n incident-handling hangs a thread. The impact to this is that\n the FFDC summary log may indicate that the incident file of a\n bad thread was created, while the thread may not have returned\n so the incident file will not exist. Therefore, a missing\n incident entry that might have appeared in a summary file is\n an indication that the component logging to FFDC did not\n return control.\n\nThe fix for this APAR is currently targeted for inclusion in\n fix packs 7.0.0.23 and 8.0.0.3. Please refer to the\n Recommended Updates page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q067", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM45011\nREPORTED COMPONENT NAME\n WEBS APP SERV N\nREPORTED COMPONENT ID\n 5724H8800\nREPORTED RELEASE\n 700\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2011-08-03\nCLOSED DATE\n 2011-12-15\nLAST MODIFIED DATE\n 2012-06-01\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q067", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBS APP SERV N\nFIXED COMPONENT ID\n 5724H8800", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q067", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R700 PSY\n UP\nR800 PSY\n UP", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q067", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "When you do a broad search with a small keyword, you expect to receive many entries in return. When your search is more specific, you use a longer keyword to try to narrow the search. However, when you expect fewer returns from your search, it does not happen. The user list remains empty.\n\nYou can find the following exception in the SystemOut.log file:\n\n[8/7/12 14:02:59:435 CEST] 000000xx exception E com.ibm.ws.wim.\nadapter.ldap.LdapConnection search(String, String, Object[],\nSearchControls) CWWIM4520E The 'javax.naming.NamingException: LDAP\nresponse read timed out, timeout used:20000ms.; Remaining name:\n'DC=xxx,DC=xxx,DC=xxx,DC=com'; Resolved object: 'com.sun.jndi.\nldap.LdapCtx@196fbd6a'' naming exception occurred during processing.\n[8/7/12 14:02:59:435 CEST] 00000068 exception E com.ibm.ws.wim.\nadapter.ldap.LdapConnection search(String, String, Object[],\nSearchControls)\ncom.ibm.websphere.wim.exception.\nWIMSystemException: CWWIM4520E The 'javax.naming.NamingException: LDAP\nresponse read timed out, timeout used:20000ms.; Remaining name:\n'DC=xxx,DC=xxx,DC=xxx,DC=com'; Resolved object: 'com.sun.jndi.\nldap.LdapCtx@196fbd6a'' naming exception occurred during processing.\nat com.ibm.ws.wim.adapter.ldap.LdapConnection.search\n(LdapConnection.java:2951)\nat com.ibm.ws.wim.adapter.ldap.LdapConnection.checkSearchCache\n(LdapConnection.java:2781)\nat com.ibm.ws.wim.adapter.ldap.LdapConnection.search\n(LdapConnection.java:2971)\n...", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q067", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "In some cases, LDAP might take longer to respond on a more specific search, which results in an LDAP timeout.", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q067", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To resolve this issue, increase the LDAP timeout limit by using one of the following options:\nOption 1\n Use the wsadmin command:\n $AdminTask updateIdMgrLDAPServer {-id AD -connectTimeout 0}\n $AdminConfig save\n\nAfter it is saved, view the wimconfig.xml file and make sure you see connectTimeout=\"0\"\n\nYou can find the wimconfig.xml file in the following locations in the deployment manager configuration: * {WAS_HOME}\\profiles\\profile_name\\config\\cells\\cell_name\\wim\\config\\wimconfig.xml\nprofile_root/conf/cells/cell_name/wim/config/wimconfig.xml\n\nA complete restart of the WebSphere Application Server / IBM Business Process Manager environment is required to make this change take effect.\nOption 2\n You will edit the wimconfig.xml file directly. However, before you edit the file, make a backup copy of it. Edit the wimconfig.xml file and search forconnectTimeout. Change this value from connectTimeout=\"20\" to connectTimeout=\"0\" and save the file.\n\nA complete restart of the WebSphere Application Server / IBM Business Process Manager environment is required to make this change take effect.\n\nNote: The connectTimeout increment value is in seconds of time. The example value 0 is to wait indefinitely. Different values can be set accordingly.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Security AIX, Linux, Linux zSeries, Solaris, Windows 8.5, 8.0.1, 8.0, 7.5.1, 7.5 Business Integration IBM Business Process Manager Express Security Linux, Windows 8.5, 8.0.1, 8.0, 7.5.1, 7.5\n\nA FIX IS AVAILABLE\nVersion 8.5 Refresh Pack 7 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24041575]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q067", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "During UserFullSync or GroupFullSync, the following error might\n prevent synchronization between LDAP and BPM tables\n\n org.springframework.dao.DataIntegrityViolationException:\n PreparedStatementCallback; SQL insert into LSW_USR_GRP_MEM_XREF\n (USER_ID, GROUP_ID) values (?, ?) ; DB2 SQL Error:\n SQLCODE=-530,\n SQLSTATE=23503,\n SQLERRMC=DB2INST1.LSW_USR_GRP_MEM_XREF.LSWC_UGXREF_FK2,\n DRIVER=4.11.69;\n\n nested exception is\n com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException:\n DB2 SQL Error: SQLCODE=-530, SQLSTATE=23503,\n SQLERRMC=DB2INST1.LSW_USR_GRP_MEM_XREF.LSWC_UGXREF_FK2,\n DRIVER=4.11.69\n at org.springframework.jdbc.support.\n SQLExceptionSubclassTranslator.translate\n (SQLExceptionSubclassTranslator.java:69)\n at org.springframework.jdbc.support.\n SQLErrorCodeSQLExceptionTranslator.translate\n (SQLErrorCodeSQLExceptionTranslator.java:237)\n at org.springframework.jdbc.core.JdbcTemplate.execute\n (JdbcTemplate.java:607)\n at org.springframework.jdbc.core.JdbcTemplate.execute\n (JdbcTemplate.java:619)\n at com.lombardisoftware.server.ejb.persistence.dao.\n UserGroupMemberDAO.setUserGroupMembership\n (UserGroupMemberDAO.java:179)\n at com.lombardisoftware.server.core.GroupCore.\n setUserGroupMembership(GroupCore.java:367)\n at com.lombardisoftware.server.ejb.security.SecurityCore.\n updateGroupMembership(SecurityCore.java:328)\n at com.lombardisoftware.server.ejb.security.SecurityCore.\n initializeNewLogin(SecurityCore.java:201)\n at sun.reflect.GeneratedMethodAccessor492.\n invoke(Unknown Source)\n at sun.reflect.DelegatingMethodAccessorImpl.invoke\n (DelegatingMethodAccessorImpl.java:37)\n at java.lang.reflect.Method.invoke(Method.java:611)\n at org.springframework.aop.support.AopUtils.\n invokeJoinpointUsingReflection(AopUtils.java:310)\n at org.springframework.aop.framework.\n ReflectiveMethodInvocation.invokeJoinpoint\n (ReflectiveMethodInvocation.java:182)\n at org.springframework.aop.framework.\n ReflectiveMethodInvocation.proceed\n (ReflectiveMethodInvocation.java:149)\n at com.lombardisoftware.utility.spring.\n TransactionInterceptor$2.call(TransactionInterceptor.java:67)\n at com.lombardisoftware.utility.spring.\n ProgrammaticTransactionSupport$1.doInTransaction\n (ProgrammaticTransactionSupport.java:436)\n at org.springframework.transaction.jta.\n WebSphereUowTransactionManager$UOWActionAdapter.run\n (WebSphereUowTransactionManager.java:306)\n at com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.\n runUnderNewUOW(EmbeddableUOWManagerImpl.java:791)\n at com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.\n runUnderUOW(EmbeddableUOWManagerImpl.java:370)\n at org.springframework.transaction.jta.\n WebSphereUowTransactionManager.execute\n (WebSphereUowTransactionManager.java:252)\n at com.lombardisoftware.utility.spring.\n ProgrammaticTransactionSupport.executeInNewTransaction\n (ProgrammaticTransactionSupport.java:431)\n at com.lombardisoftware.utility.spring.\n ProgrammaticTransactionSupport.execute\n (ProgrammaticTransactionSupport.java:294)\n at com.lombardisoftware.utility.spring.\n TransactionInterceptor.invoke(TransactionInterceptor.java:65)\n at org.springframework.aop.framework.\n ReflectiveMethodInvocation.proceed\n (ReflectiveMethodInvocation.java:171)\n at com.lombardisoftware.utility.spring.CoreEntryInterceptor.\n invoke(CoreEntryInterceptor.java:44)\n at com.lombardisoftware.utility.spring.PSCoreEntryInterceptor.\n invoke(PSCoreEntryInterceptor.java:14)\n at org.springframework.aop.framework.\n ReflectiveMethodInvocation.proceed\n (ReflectiveMethodInvocation.java:171)\n at org.springframework.aop.framework.JdkDynamicAopProxy.\n invoke(JdkDynamicAopProxy.java:204)\n at com.sun.proxy.$Proxy131.initializeNewLogin(Unknown Source)\n ...\n\n Caused by:\n com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException:\n DB2\n SQL Error: SQLCODE=-530, SQLSTATE=23503,\n SQLERRMC=DB2INST1.LSW_USR_GRP_MEM_XREF.LSWC_UG\n XREF_FK2, DRIVER=4.11.69\n at com.ibm.db2.jcc.am.gd.a(gd.java:672)\n at com.ibm.db2.jcc.am.gd.a(gd.java:60)\n at com.ibm.db2.jcc.am.gd.a(gd.java:127)\n at com.ibm.db2.jcc.am.jn.b(jn.java:2230)\n at com.ibm.db2.jcc.am.jn.c(jn.java:2213)\n at com.ibm.db2.jcc.t4.cb.k(cb.java:369)\n at com.ibm.db2.jcc.t4.cb.a(cb.java:61)\n at com.ibm.db2.jcc.t4.q.a(q.java:50)\n at com.ibm.db2.jcc.t4.sb.b(sb.java:220)\n at com.ibm.db2.jcc.am.kn.oc(kn.java:2930)\n at com.ibm.db2.jcc.am.kn.b(kn.java:3876)\n at com.ibm.db2.jcc.am.kn.gc(kn.java:743)\n\n Server startup group replication code includes phase to add new\n external groups. The replication code which performs detection\n and removal of duplicate groups from the list of new groups\n does not properly recognize group names with trailing spaces as\n duplicates.", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q067", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Find the duplicate rows by running the following query:\n\nSELECT\n GROUP_ID,\n '\"' ]] GROUP_NAME ]] '\"',\n '\"' ]] DISPLAY_NAME ]] '\"',\n PARENT_GROUP_ID,\n GROUP_TYPE,\n '\"' ]] DESCRIPTION ]] '\"',\n GROUP_STATE\n FROM BPMUSER.LSW_USR_GRP_XREF\n WHERE\n TRIM(LOWER(GROUP_NAME)) <> LOWER(GROUP_NAME);\n\nand delete the row by running the following SQL:\n\nDELETE FROM BPMADMIN.LSW_USR_GRP_XREF WHERE GROUP_ID IN (SELECT\n GROUP_ID FROM BPMADMIN.LSW_USR_GRP_XREF WHERE GROUP_TYPE=0 AND\n GROUP_NAME LIKE '% ');", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q067", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "A fix that properly handles trailing blanks in group names will\n be incorporated into a later release.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q067", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "TEMPORARY FIX\nNot applicable", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q067", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR52842\nREPORTED COMPONENT NAME\n BPM ADVANCED\nREPORTED COMPONENT ID\n 5725C9400\nREPORTED RELEASE\n 850\nSTATUS\n CLOSED FIN\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2015-03-16\nCLOSED DATE\n 2015-05-20\nLAST MODIFIED DATE\n 2015-05-20\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q067", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM STANDARD\nFIXED COMPONENT ID\n 5725C9500", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q067", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R850 PSN\n UP", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q067", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "6.1.0.5 Download: WebSphere Portal and WCM V6.1.0 fix pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24027475]\n6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24030970]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q067", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Under some rare conditions a hang can be seen when Portlet\n actions are executed. These conditions are that the same action\n ID is submitted more than one time by a Portlet and garbage\n collection occours between the 2 actions.\n\n In the logs a NullPointerException can be seen:\n\n [6/9/10 9:13:07:007 CDT] 0000006a Servlet E\n com.ibm.wps.engine.Servlet handleException EJPEJ0070E: An\n exception occurred while processing the request.\n java.lang.NullPointerException\n at com.ibm.wps.engine.phases.WPActionPhase$LockManager$Data\n .access$200(WPActionPhase.java:3462)\n at com.ibm.wps.engine.phases.WPActionPhase$LockManager\n .lockReleased(WPActionPhase.java:3453)\n at com.ibm.wps.engine.phases.WPActionPhase\n .processPortlets(WPActionPhase.java:2762)\n at com.ibm.wps.engine.phases.WPActionPhase\n .execute(WPActionPhase.java:668)\n at com.ibm.wps.state.phases.AbstractActionPhase\n .next(AbstractActionPhase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888)\n ...\n\n Some minutes later the Application Server will report hang\n threads:\n\n [6/9/10 9:22:41:135 CDT] 00000025 ThreadMonitor W WSVR0605W:\n Thread \"WebContainer : 31\" (00000088) has been active for\n 602945\n milliseconds and may be hung. There is/are 1 thread(s) in\n total\n in the server that may be hung.\n at sun.misc.Unsafe.park(Native Method)\n at java.util.concurrent.locks.LockSupport.park(LockSupport\n .java:158)\n at java.util.concurrent.locks.AbstractQueuedSynchronizer\n .parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:747)\n at java.util.concurrent.locks.AbstractQueuedSynchronizer\n .acquireQueued(AbstractQueuedSynchronizer.java:778)\n at java.util.concurrent.locks.AbstractQueuedSynchronizer\n .acquire(AbstractQueuedSynchronizer.java:1114)\n at java.util.concurrent.locks.ReentrantLock$FairSync\n .lock(ReentrantLock.java:201)\n at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock\n .java:262)\n at com.ibm.wps.engine.phases.WPActionPhase\n .processPortlets(WPActionPhase.java:2463)\n at com.ibm.wps.engine.phases.WPActionPhase\n .execute(WPActionPhase.java:668)\n at com.ibm.wps.state.phases.AbstractActionPhase\n .next(AbstractActionPhase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888)\n ...", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q067", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Under some rare conditions a hang can be seen when Portlet\n actions are executed. These conditions are that the same action\n ID is submitted more than one time by a Portlet and garbage\n collection occurs between the 2 actions. In the logs a\n NullPointerException can be seen:\n\n [6/9/10 9:13:07:007 CDT] 0000006a Servlet E\n com.ibm.wps.engine.Servlet handleException EJPEJ0070E: An\n exception occurred while processing the request.\n java.lang.NullPointerException at\n com.ibm.wps.engine.phases.WPActionPhase$LockManager$Data.access$\n 200(WPActionPhase.java:3462)\n at\n com.ibm.wps.engine.phases.WPActionPhase$LockManager.lockReleased\n (WPActionPhase.java:3453)\n at\n com.ibm.wps.engine.phases.WPActionPhase.processPortlets(WPAction\n Phase.java:2762)\n at\n com.ibm.wps.engine.phases.WPActionPhase.execute(WPActionPhase.ja\n va:668)\n at\n com.ibm.wps.state.phases.AbstractActionPhase.next(AbstractAction\n Phase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888) ...\n S\n\n Some minutes later the Application Server will report hang\n threads:\n\n [6/9/10 9:22:41:135 CDT] 00000025 ThreadMonitor W\n WSVR0605W: Thread \"WebContainer : 31\" (00000088) has been active\n for 602945 milliseconds and may be hung. There is/are 1\n thread(s) in total in the server that may be hung.\n at sun.misc.Unsafe.park(Native Method) at\n java.util.concurrent.locks.LockSupport.park(LockSupport.java:158\n )\n at\n java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndChe\n ckInterrupt(AbstractQueuedSynchronizer.java:747)\n at\n java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQue\n ued(AbstractQueuedSynchronizer.java:778)\n at\n java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(Ab\n stractQueuedSynchronizer.java:1114)\n at\n java.util.concurrent.locks.ReentrantLock$FairSync.lock(Reentrant\n Lock.java:201)\n at\n java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java\n :262)\n at\n com.ibm.wps.engine.phases.WPActionPhase.processPortlets(WPAction\n Phase.java:2463)\n at\n com.ibm.wps.engine.phases.WPActionPhase.execute(WPActionPhase.ja\n va:668)\n at\n com.ibm.wps.state.phases.AbstractActionPhase.next(AbstractAction\n Phase.java:130)\n at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:855)\n at com.ibm.wps.engine.Servlet.doGet(Servlet.java:617)\n at com.ibm.wps.engine.Servlet.doPost(Servlet.java:888) ...", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q067", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fixed action ID synchronization.\n\nFailing Module(s):\n Engine: State handling\n\nAffected Users:\n All Users\n\nVersion Information:\n Portal Version(s): 6.1.0.3\n Pre-Requisite(s): ---\n Co-Requisite(s): ---\n\nManuel Steps:\n None\n\nPlatform Specific:\n This fix applies to all platforms.\n\nPM16223 is part of Cumulative Fix 06 for Portal 6.1.0.3/6.1.5.0.\n\nThe fix is available from Fix Central:\n\nhttp://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde\n r?apar=PM14900&productid=WebSphere%20Portal&brandid=5 [http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorder?apar=PM14900&productid=WebSphere%20Portal&brandid=5]\n\nYou may need to type or paste the complete address into your Web\n browser.\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q067", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM16223\nREPORTED COMPONENT NAME\n WEBSPHERE PORTA\nREPORTED COMPONENT ID\n 5724E7600\nREPORTED RELEASE\n 61C\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2010-06-10\nCLOSED DATE\n 2010-07-20\nLAST MODIFIED DATE\n 2010-07-20\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q067", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBSPHERE PORTA\nFIXED COMPONENT ID\n 5724E7600", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q067", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R61C PSY\n UP", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q017", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Your Integration Node (broker) fails to respond to a deployment request that was issued by using either the WMB/IIB Toolkit, the Explorer plugin, or the mqsideploy command. You might see a deployment hang/timeout, or BIP2066E errors in the message log.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q017", "section_id": 1, "heading": "ENVIRONMENT", "parent": null, "text": "These instructions are for WebSphere Message Broker or IBM Integration Bus on AIX, HP-UX, Linux, Solaris or Windows systems.\nReturn to the WMB / IIB MustGather index [http://www.ibm.com/support/docview.wss?uid=swg21209857] for other problems.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q017", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "STEP 1: SELF-GUIDED TROUBLESHOOTING\n\nA BIP2066E message indicates that a response was not received from your execution group within the time period specified in the ConfigurationChangeTimeout parameter.\nThe default setting for deployment timeouts is 5 minutes (300 seconds), so increase this value only if the timeout was manually reduced to a lower value.\n\nMany broker commands, including starting, stopping, and creating objects are considered deployment actions.\nYou may see a BIP2066E error in the message log even if you did not use the mqsideploy command.\n\nDoes one specific mqsi command timeout, or do multiple mqsi commands timeout?\nDo even non-deployment commands, such as mqsilist or mqsiservice, timeout?\nCan you re-create the problem from a different deployment method?\nmqsideploy\nToolkit\nExplorer\n\nAre messages backing up on any of the SYSTEM.BROKER.* queues?\nDo these messages continue to appear when the Broker are stopped?\n\nSTEP 2: COLLECT DATA\n\n1. Error logs * On UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.\n See: Configuring the syslog daemon [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/an04230_.htm]\nOn Window systems, the local error log is the Windows Application Event Log. You can find the Event Viewer from the Windows Control Panel.\n See: Windows: Viewing the local error log [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/an04090_.htm]\n\n2.\n 3. Traces\n a) In your broker environment, SET or EXPORT the environment variables\n'MQSI_SHOW_DEPLOY=1'\n'MQSI_DEPLOY_PROGRESS=1'\n\nb) Restart the broker components to pick up the change to the environment.\n c) Output of command mqsidc\n d) Capture a deploy trace [http://www.ibm.com/support/docview.wss?uid=swg21177049]\n\n4.\n 5. General Broker information * Record the WebSphere Message Broker version, release, and maintenance level.\n This can be captured using the command 'mqsiservice -v'.\nRecord the operating system version, release, and maintenance level.\nRecord the version, release, and maintenance level of any related products and components for the problematic application.\nCollect the broker's environment.\nenv (UNIX)\nset (Windows)\nCollect the Standard Output/Error logs.\n On UNIX and Linux systems, WMB writes information to both 'stdout' and 'stderr' files.\n On Window systems, WMB writes information to a 'console.out' file.\n These files are located under the Message Broker workpath.\n See: Standard System Logs [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/au14165_.htm]", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q017", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "STEP 3: SUBMIT DATA TO IBM\nUse IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM.\nSend your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis.\n\nPlease see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support.\n\nBack to top", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q017", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "Deploy trace instructions [http://www.ibm.com/support/docview.wss?uid=swg21177049]\nsubmitting documentation to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217]\n\nPRODUCT ALIAS/SYNONYM\n WMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q017", "section_id": 0, "heading": "ENVIRONMENT", "parent": null, "text": "These instructions are for WebSphere Message Broker or IBM Integration Bus on AIX, HP-UX, Linux, and Solaris systems.\nReturn to the WebSphere Message Broker MustGather index [http://www-01.ibm.com/support/docview.wss?uid=swg21209857] for other systems.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q017", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "STEP 1: SELF-GUIDED TROUBLESHOOTING\n\n1. Consider Using the Test Client in trace and debug mode [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/af52260_.htm].\n 2.\n 3. A user level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#1] is intended to assist users with understanding how their ESQL is processed.\n It will also show a high level view of the message flow behavior.\n 4.\n 5. Check for known issues:\n Dynamic guide to help troubleshooting Message Broker [https://www.ibm.com/developerworks/community/blogs/c7e1448b-9651-456c-9924-f78bec90d2c2/entry/try_a_dynamic_guide_to_help_with_troubleshooting_message_broker?lang=en] IIB and Web services [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac55700_.htm]\n Implementing WebService security in WMB [http://www.ibm.com/developerworks/websphere/library/techarticles/1008_fan/1008_fan.html]\n Run the WebServices samples [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ax20230_.htm?cp=SSMKHH_9.0.0%2F1-2-4]\n [http://www.ibm.com/software/htp/cics/tserver/support/]WebSphere Message Broker support site [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Message_Broker]\n\nSTEP 2: COLLECT DATA\n\n1. mqsidc\n See: mqsidc usage instructions [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bu46012_.htm]\nThis command line tool is only available for WMB 7.0.0.5+, WMB 8.0.0.1+, and IIB 9.0.\nWhen running the tool, select the option for 'Broker Collector', when prompted.\n\n2.\n 3. Project Interchange files for the problematic flow/set/ESQL/model\nYou can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.\n See: Exporting files from the Workbench [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ax20230_.htm?cp=SSMKHH_9.0.0%2F1-2-4]\n\n4.\n 5. Traces If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321] can be used to gain a better understanding of the problem. * A service level trace [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321#2] is intended to be provided to IBM Support to assist in the diagnosis of your issue.\n[http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177049]SSL trace [http://www.ibm.com/support/docview.wss?uid=swg21300238] for HTTPS problems only\n[http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177049]SOAP debug trace [http://www.ibm.com/support/docview.wss?uid=swg21660124] when using SOAP nodes with http (not https)\n\n6.\n 7. General Broker information\n If the mqsidc tool was not run, then capture this information manually * Record the IBM Integration Bus or WebSphere Message Broker version, release, and maintenance level.\n This can be captured using the command 'mqsiservice -v'..\nRecord the operating system version, release, and maintenance level.\nRecord the version, release, and maintenance level of any related products and components for the problematic application.\nCollect the local error log. On UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.\n See: Configuring the syslog daemon [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/an04230_.htm]\nCollect the Standard Output/Error logs.\n WMB writes information to both STDOUT and STDERR. These files are located under the Message Broker workpath.\n See: Standard System Logs [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/au14165_.htm]\nAdditional information\nOutput of command: mqsilist -r -d2\nIs IIB/WMB acting as service provider or service consumer?", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q017", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "ATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!\nWhen sending data to IBM, be sure to update your PMR or send a note with the following information:\nTell us what errors you saw, where you saw them, and what time they happened Let us know if you made any changes to WebSphere Message Broker or the system before the problem Share any other observations which you think will help us to better understand the problem\n\nSTEP 3: SUBMIT DATA TO IBM\nUse IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM.\nSend your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis.\n\nPlease see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support.\n\nBack to top\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker AIX, HP-UX, Linux, Solaris, Windows 8.0\nPRODUCT ALIAS/SYNONYM\n WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q017", "section_id": 0, "heading": "ENVIRONMENT", "parent": null, "text": "These instructions are for WebSphere Message Broker or IBM Integration Bus on AIX, HP-UX, Linux, and Solaris systems.\nReturn to the WebSphere Message Broker MustGather index [http://www-01.ibm.com/support/docview.wss?uid=swg21209857] for other systems.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q017", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "STEP 1: SELF-GUIDED TROUBLESHOOTING\n\n1. Consider Using the Test Client in trace and debug mode [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/af52260_.htm].\n 2.\n 3. A user level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#1] is intended to assist users with understanding how their ESQL is processed.\n It will also show a high level view of the message flow behavior.\n 4.\n 5. Check for known issues:\n WebSphere Adapter nodes [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/ac37160_.htm] Transport and connectivity samples [https://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ax20230_.htm]\n Resolving problems when developing message flows with WebSphere Adapter nodes [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/au16538_.htm]\n Integrating WMB with SAP [http://www-01.ibm.com/support/docview.wss?uid=swg27018476&aid=1]\n [http://www.ibm.com/software/htp/cics/tserver/support/]WebSphere Message Broker support site [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Message_Broker]\n\nSTEP 2: COLLECT DATA\n\n1. mqsidc\n See: mqsidc usage instructions [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bu46010_.htm]\nThis command line tool is only available for WMB 7.0.0.5+, WMB 8.0.0.1+, and IIB 9.0.\nWhen running the tool, select the option for 'Broker Collector', when prompted.\n\n2.\n 3. Project Interchange files for the problematic flow/set/ESQL/model\nYou can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.\n See: Backing up the Toolkit Workspace [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/an27100_.htm]\n\n4.\n 5. Refer to Adapter troubleshooting MustGathers [http://www-01.ibm.com/support/docview.wss?uid=swg21438193]\n 6. Traces If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321] can be used to gain a better understanding of the problem. * A user level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#1] is intended to assist users with understanding how their ESQL is processed. It will also show a high level view of the message flow behavior.\nA service level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#2] is intended to be provided to IBM Support to assist in the diagnosis of your issue.\nRFC traces:\n Steps to enable and collect the RFC Traces:\n 1. Launch the Adapter Connection Wizard ,and proceed to the 'Service Generation and Deployment Configuration' window. In the SAP RFC trace configuration section:\nSet the RFCTraceOn property to 'true'\nSet the RFC Trace Level property to '8' , which outputs verbose debug messages, full\n execution path, info messages, errors and warnings\nSet the Folder for RFC trace files property to the directory location where the RFC Traces\n are created\nAlternatively, these properties may also be set on SAPConnection configurable service [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bn28742_.htm] using mqsichangeproperties command or MB Explorer, which would require a broker/execution group restart.\n For example: mqsichangeproperties -c SAPConnection -o Template -n RFCTraceOn -v true\n\n2. Recreate the issue.\n\n3. Collect the RFC trace files generated.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q017", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Note: The trace files are created in the directory where the adapter process has been started by default. The trace file has a .trc file extension and the file name will start with the letters rfc followed by a unique identifier. For example, rfc03912_02220.trc.\n\n7.\n 8. General Broker information\n If the mqsidc tool was not run, then capture this information manually * Record the WebSphere Message Broker version, release, and maintenance level.\n This can be captured using the command 'mqsiservice -v'..\nRecord the operating system version, release, and maintenance level.\nRecord the version, release, and maintenance level of any related products and components for the problematic application.\nCollect the local error log. On UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.\n See: Configuring the syslog daemon [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/an04230_.htm]\nCollect the Standard Output/Error logs.\n WMB writes information to both STDOUT and STDERR. These files are located under the Message Broker workpath.\n See: Standard System Logs [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/au14165_.htm]\n\nATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!\nWhen sending data to IBM, be sure to update your PMR or send a note with the following information:\nTell us what errors you saw, where you saw them, and what time they happened Let us know if you made any changes to WebSphere Message Broker or the system before the problem Share any other observations which you think will help us to better understand the problem\n\nSTEP 3: SUBMIT DATA TO IBM\nUse IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM.\nSend your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis.\n\nPlease see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support.\n\nBack to top\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus AIX, HP-UX, Linux, Solaris 10.0, 9.0 All Editions\nPRODUCT ALIAS/SYNONYM\n WMBFE MBFE WMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q017", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "MessageFlow is a valid reportable entity name for the -o parameter, but the mqsireportproperties command does not have the functionality to allow the specifying of a message flow or uuid. Therefore it is not possible to request the properties for just a single message flow.\nFor example: If you try to run the following command:\nmqsireportproperties -e -o MessageFlow -r\n\nYou would see the exception: BIP2330E MessageFlow does not exist\n\nAs a workaround you could put one message flow in the execution group. Then report the properties for all messages flows in the execution group with the following commands:\n\nmqsireportproperties -e -o AllMessageFlows -a\nmqsireportproperties -e -o AllMessageFlows -r\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus 9.0 All Editions\nPRODUCT ALIAS/SYNONYM\n WMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q017", "section_id": 0, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Reviewing BAR files, by using the mqsireadbar command, shows that the contents of BAR files created with the Toolkit and command line are not exactly the same.\nThe resources in the BAR file created in the Toolkit are not compiled by default, so it includes all resources (.msgflows and .esql files) in the library or application. This indicates that you did not select the build option \"Compile and in-line resources\" when creating the BAR file.\n\nThe resources in the BAR file created with the mqsi command are compiled (.cmf) files, so the compiled message flows already have the ESQL code embedded in the .cmf, and some .esql files are not added as individual resources.", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q017", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To correct the issue, add the parameter -deployAsSource when building the BAR file using the mqsi command. By using this parameter, the source .esql and .msgflow files are included explicitly in the BAR file, instead of the .cmf.\n\nThe default options used to build both BAR files are not exactly the same for the Toolkit and mqsicreatebar command. When the BAR file is built using the Toolkit, the option \"Compile and in-line resources\" is not selected by default, but this option is enabled by default in the mqsicreatebar command.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Linux, Windows 9.0 All Editions\nPRODUCT ALIAS/SYNONYM\n WMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q303", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "After entering the user ID and password in the login page, and then pressing the \"continue\" button,\nthe login page does not change, stuck at \"processing\" and then returns to the login page again.\"\n\nAll users get essentially locked out completely from DASH sessions.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q303", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "In order to maximize the time between session timeouts, the customer is setting the timeout parameter in the security.xml file to 2147483647.\n\nThis timeout parameter used in the security.xml file is a WAS setting, but DASH is using a javascript call (settimeout), which causes a condition that prevents a login, if the timeout value is really big.\n\nNote: 2147483647 is the maximum positive value for a 32-bit signed binary integer in computing.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q303", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "This condition that prevents logins can be averted by setting the custom property LTPAFIX in the consoleProperties.xml to \"false\".\n\nPlease follow this steps:\n\n1. On DASH server, navigate to /profile/config/cells/JazzSMNode01Cell/applications/isc.ear/deployments/isc/isclite.war/WEB-INF\n\n2. Take a backup of consoleProperties.xml\n\n3. Open consoleProperties.xml in edit-mode.\n\n4. Search for \"LTPAFIX\" and change the value from \"true\" to \"false\".\n\nExample:\n\nBefore\n\n\n\n\nAfter\n====\n\n\n\n5. Save the file.\n\n6. Restart DASH server.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q303", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "The tag requiresSSL in the security.xml in was set to true.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q303", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Review the security configuration on the IBM WebSphere Application Server for the FileNet Workplace XT application. Check the setting requiresSSL to see whether it has been set to true or false.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q303", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The WebSphere Application Server's security.xml can be reviewed for this specific label requiresSSL. Review the value for the \"requiresSSL\" and ensure it is set to false.\n\n1. Make a backup of the security.xml file: /config/cells/cellname/security.xml\n\n2. Edit the security.xml file by searching for requiresSSL=.\n\n\n\n3. Save the security.xml file\n\n4. Restart the WebSphere Application Server.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q303", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Where can I find a quick start guide to deploy an Object Server failover pair for OMNIbus 7.4?", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q303", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "The following document provides a quick deployment guide to get OMNIbus up and running in 10 steps. The example deployment configures two Object Servers as a failover pair with a bi-directional Object Server gateway configured to run under the Process Agent. The example configuration is completed on Linux, but the same steps can be applied to all operating systems.\n\nQuick Deployment 7.4 Create Netcool OMNIbus Failover Object Server Pair.doc [/support/docview.wss?uid=swg21685468&aid=2]Quick Deployment 7.4 Create Netcool OMNIbus Failover Object Server Pair.doc [/support/docview.wss?uid=swg21685468&aid=1]\n\nStep 1: Set environment variables on each system\nStep 2: Configure the omni.dat file on each system\nStep 3: Create Primary Object Server\nStep 4: Create Backup Object Server\nStep 5: Configure bi-directional Object Server failover gateway\nStep 6: Configure the Process Agents\nStep 7: Start Process Agents\nStep 8: Configure the Object Server to connect to the Process Agent\nStep 9: Test Failover\nStep 10: Test Failback\n\nMore information is available for setting up the Omnibus Multitier architecture at\nhttp://www-01.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/omnibus/wip/install/task/omn_esf_settingupstandardmultitier.html [http://www-01.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/omnibus/wip/install/task/omn_esf_settingupstandardmultitier.html]\n\nIn Omnibus 8.1, the initial configuration has been automated with the configuration wizard nco_icw\nhttp://www-01.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/omnibus/wip/install/reference/omn_ins_ict.html [http://www-01.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/omnibus/wip/install/reference/omn_ins_ict.html]", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q303", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "2147483647 is in minute and it is 4085 years. There is no reason to have this number this large.\nUse reasonable time out value instead of unnecessary very large numbers.\n\nFor example: *\n*\n*\n*", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q303", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "There are three possible causes:", "logical_doc_id": 4, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q303", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The three solutions appear here starting with the solution to the problem that occurs most often to the problem that occurs least often. Work through them in the order listed.\n\nWhen you try to login to the administrative console, a prefrences.xml file is created in WAS_HOME\\wstemp\\user_dir. If creation of preferences.xml fails due to lack of disk space, it leaves prefrences.xml file with zero length. This zero length prefrences.xml file causes the SAXParseException Premature end of file.\n\na. Clean up the disk space problem.\n\nb. Delete the WAS_HOME\\wstemp\\user_dir\\prefrences.xml file\n\nc. Try to login to administrative console. This builds new prefrences.xml with correct data so you can login to the administrative console.\n\n1. To resolve the issue:\n\na. Disable WebSphere Application Server security by stopping WebSphere Application Server (Network Deployment and nodeagent).\n\nb. Make a backup copy of the WAS_HOME/config/cells/node name/security.xml file.\n\nc. Edit the WAS_HOME/config/cells/node name/security.xml. Edit the line starting with \"/bin directory:\n\nFor Windows platforms: backupConfig.bat\n For UNIX platforms: ./backupConfig.sh\n\n3. Uninstalling and reinstalling of the administrative console:\n\na. Start the wsadmin tool from the WAS_HOME/bin directory:\n\nwsadmin.sh/bat -conntype NONE\n\nb. List all the applications:\n\n$AdminApp list\n\nNote: This shows all the applications installed. If you have more than one \"adminconsole\", uninstall all the adminconsole applications.\n\nc. Uninstall the administrative console:\n\n$AdminApp uninstall adminconsole\n\nd. Save the changes:\n\n$AdminConfig save\n\ne. List all the applications:\n\n$AdminApp list\n\nYou should not see the administrative console listed.\n\na. Install the administrative console:\n\n$AdminApp install $WAS_HOME/installableApps/adminconsole.ear \"-node my_Base_Node -cell my_Cell -server server1 -appname adminconsole\"\n\nb. Save the changes:\n\n$AdminConfig save\n\nc. List all the applications:\n\n$AdminApp list\n\nYou now see the administrative console listed and can start it.\n\nIf you still experience problems open a PMR with IBM Support [https://www-304.ibm.com/usrsrvc/account/userservices/jsp/login.jsp?persistPage=true].", "logical_doc_id": 4, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q303", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q241", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The messages shown in the ncp_poller.DOMAIN.trace file will be similar to these:\n\nCould not open /home/netcool/opt/IBM/tivoli/netcool/precision/platform/linux2x86/lib/libNcpDbDb2.so: libdb2.so.1: cannot open shared object file: No such file or directory\n\nThu Nov 17 16:32:30 2011 Warning: A required dynamic library file is missing. found in file CNcpDbFactory.cc at line 783 - When attempting to open shared lib: /home/netcool/opt/IBM/tivoli/netcool/precision/platform/linux2x86/lib/libNcpDbDb2.so\n\nThu Nov 17 16:32:30 2011 Warning: A generic non-fatal error has occurred found in file CNcpDbPoller.cc at line 111 - Error: No databse configured for dbId: NCMONITOR\n\nThu Nov 17 16:32:30 2011 Warning: An unexpected nil pointer reference has been found. found in file CDbSnmpTargetFactory.cc at line 79 - Cannot get domain information from database\n\nThu Nov 17 16:32:30 2011 Warning: A generic non-fatal error has occurred found in file CChangedConfigPoller.cc at line 74 - SNMP target poller unable to connect to the database\n\nThu Nov 17 16:32:30 2011 Warning: A generic non-fatal error has occurred found in file CNcpPollerApplication.cc at line 615 - No changes to the SNMP configuration will be picked up without restarting the poller\n\nThu Nov 17 16:32:30 2011 Warning: An unexpected nil pointer reference has been found. found in file CMib.cc at line 1241 - cannot create database handle\n\nThu Nov 17 16:32:30 2011 Warning: An unexpected nil pointer reference has been found. found in file CMib.cc at line 174 - cannot initialise database connection for 'MIB'\n\nThu Nov 17 16:32:30 2011 Warning: Cannot connect to database found in file CEntityAlert.cc at line 70\n\nThu Nov 17 16:32:30 2011 Warning: A generic non-fatal initialisation error has occurred. found in file IPollDataMux.cc at line 46\n\nThu Nov 17 16:32:30 2011 Warning: An unexpected nil pointer reference has been found. found in file CMonitorApplication.cc at line 141 - cannot retrieve domain manager information\n\nThu Nov 17 16:32:30 2011 Warning: An unexpected nil pointer reference has been found. found in file CMonitorTemplateManager.cc at line 77 - cannot create DB handle for 'NCMONITOR'\n\nThu Nov 17 16:32:30 2011 Warning: An unexpected nil pointer reference has been found. found in file CMonitorPolicyManager.cc at line 136 - cannot create DB handle for 'NCMONITOR'\n\nThu Nov 17 16:32:30 2011 Warning: An unexpected nil pointer reference has been found. found in file CMonitorPolicyManager.cc at line 713 - no monitor DB\n\nThu Nov 17 16:32:30 2011 Warning: An unexpected nil pointer reference has been found. found in file CRealTimeTblCallback.cc at line 422", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q241", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The DB2 libraries are not included in the ld.so.conf file, thus cannot be executed when the sticky bit (or access-right flag) is present on the ncp_poller processes.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q241", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "non-root ITNM install, DB2 databases", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q241", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "1 ) Stop your ITNM processes the normal ITNM user:\n\n[ netcool@testbox : ~/opt/IBM/tivoli/netcool/log/precision ]\n$ itnm_stop ncp\n\n[ netcool@testbox : ~/opt/IBM/tivoli/netcool/log/precision ]\n$ itnm_status\nOMNIbus:\nnco_pad RUNNING PID=3799 NCO_PA\nnco_objserv RUNNING PID=3827 NCOMS\nnco_p_mttrapd RUNNING PID=4082 NCOMS\nNetwork Manager:\nncp_ctrl NOT RUNNING\nTivoli Integrated Portal:\nServer RUNNING PID=6555\n\n2) As the root user, edit your /etc/ld.so.conf:\n[ root@testbox : /etc ]\n# vi /etc/ld.so.conf\ninclude ld.so.conf.d/*.conf\n/home/netcool/opt/IBM/tivoli/netcool/precision/platform/linux2x86/lib\n/home/netcool/opt/IBM/tivoli/netcool/platform/linux2x86/lib\n....\n/home/netcool/sqllib/lib32/\n\n3) As root user, run ldconfig. Use the \"-v\" option to get verbose output:\n[ root@testbox : /etc ]\n# ldconfig -v\n/usr/lib/mysql:\nlibmysqlclient_r.so.14 -> libmysqlclient_r.so.14.0.0\nlibmysqlclient_r.so.10 -> libmysqlclient_r.so.10.0.0\n...........\n\n4) As your ITNM user, restart your ITNM processes:\n[ netcool@testbox : ~/opt/IBM/tivoli/netcool/log/precision ]\n$ itnm_start ncp\nNetwork Manager:\nDomain: DOMAIN\nncp_ctrl RUNNING PID=31961 DOMAIN\nncp_store IDLE PID= DOMAIN\nncp_class IDLE PID= DOMAIN\nncp_auth IDLE PID= DOMAIN\nncp_model IDLE PID= DOMAIN\nncp_disco IDLE PID= DOMAIN\nncp_f_amos IDLE PID= DOMAIN\nncp_d_helpserv IDLE PID= DOMAIN\nncp_config IDLE PID= DOMAIN\nncp_poller IDLE PID= DOMAIN\nnco_p_ncpmonitor IDLE PID= DOMAIN\nncp_ncogate IDLE PID= DOMAIN\nncp_webtool IDLE PID= DOMAIN", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q241", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Given an access ip address for a device, how can I tell what community string is being used by ITNM?", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q241", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "You will need to query the ncmonitor database to determine which community string is being used, and, most likely, use the ncp_crypt program to decrypt that string.\n\nUsing ncp_oql to execute the query is the easiest:\n\n[ root@testbox : /opt/IBM/tivoli/netcool/precision ]\n\n# ncp_oql -service ncim -domain ITNMDOM -username ncim -password netcool -query \"select * from ncmonitor.snmpv1Sec where ACCESSID in (select READACCESSID from ncmonitor.snmpTarget where DOMAIN='ITNMDOM' and NETADDR='192.168.113.68');\"\n\nncp_oql ( IBM Tivoli Network Manager OQL Interface )\n\nCopyright (C) 1997 - 2010 By IBM Corporation. All Rights Reserved. See product license for details.\n\nIBM Tivoli Network Manager Version 3.9 (Build 49) created by ncpbuild at 22:06:25 Wed Feb 15 GMT 2012\n\nConnected to INFORMIX DB schema NCIM\n\nExecuting query:\n\nselect * from ncmonitor.snmpv1Sec where ACCESSID in (select READACCESSID from ncmonitor.snmpTarget where DOMAIN='ITNMDOM' and NETADDR='192.168.113.68');\n\n{\n\nACCESSID=22;\n\nCOMMUNITY='@44:SMcxaoBlMTwbIZ9NnzfaaFyXhQhbVaLSwfHyXL9Lg18=@';\n\nENCRYPTED=1;\n\n}\n\n1 rows(s)\n\nThen, use the ncp_crypt command to decrypt the community string:\n\n[ root@testbox : /opt/IBM/tivoli/netcool/precision ]\n\n# ncp_crypt -decrypt -password @44:SMcxaoBlMTwbIZ9NnzfaaFyXhQhbVaLSwfHyXL9Lg18=@\n\nncp_crypt ( IBM Tivoli Network Manager Password Encryption/Decryption Tool )\n\nCopyright (C) 1997 - 2010 By IBM Corporation. All Rights Reserved. See product license for details.\n\nIBM Tivoli Network Manager Version 3.9 (Build 49) created by ncpbuild at 22:06:25 Wed Feb 15 GMT 2012\n\n@44:SMcxaoBlMTwbIZ9NnzfaaFyXhQhbVaLSwfHyXL9Lg18=@ 'public'", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q241", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "When running '/home/ncosys/.acsi_ncosys/bin/listIU.sh', it is failing with the following error:\n\nACUIR00003E The query failed with return code, 2.", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q241", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Some directories and files, such as the tmp/ and db.lck files had a different owner than the admin that installed the product.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q241", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Check the ownership of the directories and file in:\n\n/home/ncosys/.acsi_ncosys/repos/IURegistryDB]# ls -ltr\nrwxrwxrwx 1 ncosys ncoadmin 897 Jun 9 2011 service.properties* drwxrwxrwx 2 ncosys ncoadmin 4096 Jun 9 2011 seg0/\ndrwxrwxrwx 2 ncosys ncoadmin 256 Jan 20 00:15 log/\ndrwx------ 2 jtobin staff 256 May 4 00:15 tmp/\nrw------- 1 jtobin staff 4 May 4 00:15 dbex.lck\nrw------- 1 jtobin staff 38 May 4 00:15 db.lck", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q241", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "In the above example, have the system administrator change the group and owner of the files back to ncosys and ncoadmin.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q241", "section_id": 4, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "IBM Tivoli Network Manager IP 3.9.0 Fix Pack 3, 3.9.0-TIV-ITNMIP-FP0003 [http://www-01.ibm.com/support/docview.wss?uid=swg24033501]\nIBM Tivoli Network Manager IP 3.9.0 Fix Pack 4, 3.9.0-TIV-ITNMIP-FP0004 [http://www-01.ibm.com/support/docview.wss?uid=swg24034724]\nIBM Tivoli Network Manager IP Edition 3.9.0 Fix Pack 5, 3.9.0-TIV-ITNMIP-FP0005 [http://www-01.ibm.com/support/docview.wss?uid=swg24037809]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q241", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "ncp_dh_ping cored with debug 4 on and whenever TraceRoute agent\n enabled.\n\nThe following message shown in nco_dh_ping.DomainName.trace:\n** glibc detected *** ncp_dh_ping: double free or corruption\n (!prev): 0x080969a0 ***\n CDiscoPingHelper::DHProcessIO\n CDiscoPingHelper::DHProcessIO - packetLen=56 sockID=11\n fromaddr=9.42.16.1\n CDiscoTracePinger::DRPProcessIOReply()\n Received 56 bytes in the return packet\n 45 C0 00 38 A4 7F 00 00 FF 01 E3 B8 09 2A 10 01\n 09 2A 10 78 0B 00 38 34 00 00 00 00 45 00 00 1C\n 00 00 40 00 01 11 31 D5 09 2A 10 78 AC 1E 82 3C\n 88 6A 09 08 78 61 B2 F7 Traceroute time exceeded\n CDiscoTracePinger::DRPProcessIOReply() packet received on wrong\n port so discarding\n ======= Backtrace: =========\n /lib/libc.so.6[0xf7a6c911]\n /lib/libc.so.6(__libc_free+0x84)[0xf7a6df84]\n /usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xf7c0b1e1]\n /usr/lib/libstdc++.so.6(_ZdaPv+0x1d)[0xf7c0b23d]\n /opt/IBM/tivoli/netcool/precision/platform/linux2x86/lib/libVert\n igo.so.1(_ZN18CPingPacketBuilderD1Ev+0x28)[0xf7da1738]\n /opt/IBM/tivoli/netcool/precision/platform/linux2x86/lib/libDisc\n oCommon.so.1(_ZN17CDiscoTracePinger14DTPDoPingTraceEv+0x394)[0xf\n 7d3c1b4]\n /opt/IBM/tivoli/netcool/precision/platform/linux2x86/lib/libDisc\n oCommon.so.1(_ZN17CDiscoTracePinger17DTPDoPingAndTraceEPKcii+0x2\n 9f)[0xf7d3c78f]\n ncp_dh_ping(_ZN16CDiscoPingHelper14DPHDoTracePingE22EDiscoPingRe\n sponseTypePKciiiP10CRivRecord+0xb7)[0x804dbc7]\n ncp_dh_ping(_ZN16CDiscoPingHelper11DHDoRequestEP10CRivRecord+0x3\n 6c)[0x804f0fc]\n /opt/IBM/tivoli/netcool/precision/platform/linux2x86/lib/libDisc\n oHelper.so.1(_ZN12CDiscoHelper16DHProcessRequestEP10CRivRecord+0\n x92)[0xf7d5aab2]\n /opt/IBM/tivoli/netcool/precision/platform/linux2x86/lib/libDisc\n oHelper.so.1(_Z18newRequestThreadFnPvS_+0x30)[0xf7d5d650]\n /opt/IBM/tivoli/netcool/precision/platform/linux2x86/lib/libNCPB\n ase.so.1(_ZN12CRivServPool12MainWorkLoopEv+0xcf)[0xf7eed22f]\n /opt/IBM/tivoli/netcool/precision/platform/linux2x86/lib/libNCPB\n ase.so.1(_ZN12CRivServPool19ThreadStartFunctionEPv+0x29)[0xf7eec\n 829]\n /lib/libpthread.so.0[0xf7c7234b]\n /lib/libc.so.6(__clone+0x5e)[0xf7ac665e]", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q241", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nUser with TraceRoute agent enabled and have ping helper at *\ndebug 4 trace level. *\n\nPROBLEM DESCRIPTION: *\nNcp_dh_ping core with message ?double free or corruption? to *\nlog file when running at debug 4 level. *\n*\n*** glibc detected *** ncp_dh_ping: double free or *\ncorruption (!prev): 0x080969a0 *** *\n\nRECOMMENDATION: *\nThe problem occurs only if the debug 4 trace is enabled in *\nping helper. *\nBefore applying the fix, disabling the debug 4 trace would *\nprevent the problem. *", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q241", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A double free was occurring when the ping helper was run in\n debug 4.\n\nAn object was created for debug output which consumed some\n memory that was then freed later. After creation, grab back the\n memory to prevent the double free.\n\nThe following fixpacks will contain the fix:\n | fix pack | 3.9.0-ITNMIP-FP0001\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q241", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV07692\nREPORTED COMPONENT NAME\n NC/PREC DISCOVY\nREPORTED COMPONENT ID\n 5724O52DS\nREPORTED RELEASE\n 390\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2011-09-13\nCLOSED DATE\n 2011-09-23\nLAST MODIFIED DATE\n 2011-09-23\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q241", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n NC/PREC DISCOVY\nFIXED COMPONENT ID\n 5724O52DS", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q241", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R390 PSN\n UP\nR390 PSY\n UP\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q241", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Problem title\n The mttrapd probe upgraded from version\n 10 to version 15 (aix-nco-p-mttrapd-15_0) and the upgrade\n mttrapd failed to to load module successfully .\n\nWhen starting the probe, customer see the following warning:\n Failed to load module successfully\n\n2013-04-04T15:21:53: Debug: D-UNK-000-000: Attempting API\n interrogation\n 2013-04-04T15:21:53: Debug: D-UNK-000-000:\n /opt/IBM/tivoli/netcool/platform/aix5/lib/libOpl.so\n 2013-04-04T15:21:53: Debug: D-ETC-004-032: Attempting to load\n module\n 'libOpl' from path:\n /opt/IBM/tivoli/netcool/platform/aix5/lib/libOpl.so\n 2013-04-04T15:21:53: Warning: W-UNK-000-000: Failed to load\n module\n successfully\n 2013-04-04T15:21:53: Information: I-UNK-000-000: Connecting ...\n 2013-04-04T15:21:53: Debug: D-UNK-000-000: Shutting down\n Probewatch\n heartbeat thread.\n 2013-04-04T15:21:53: Debug: D-UNK-000-000: Probewatch heartbeat\n thread\n is already shutdown.\n 2013-04-04T15:21:53: Debug: D-UNK-000-000: Stopping separate\n communications threads if they are running.\n 2013-04-04T15:21:53: Debug: D-UNK-000-000: Running with single\n threaded\n communications.\n 2013-04-04T15:21:53: Debug: D-UNK-000-000: Reading\n /opt/IBM/tivoli/netcool/etc/rules/snmptrap.test.rules\n 2013-04-04T15:21:53: Debug: D-UNK-000-000: Plain text rules file\n detected.\n 2013-04-04T15:21:53: Debug: D-UNK-000-000: Setting target server\n to\n 'AGG'.\n 2013-04-04T15:21:53: Debug: D-UNK-000-000: Setting default\n target\n server to 'AGG_P'.\n 2013-04-04T15:21:53: Debug: D-UNK-000-000: Default target backup\n server\n is 'AGG_B'.\n\nThough the module is present ....\n\nls -la /opt/IBM/tivoli/netcool/platform/aix5/lib/libOpl.so\nr-xr-xr-x 1 netcool ncoadmin 354148 Aug 29 2012\n /opt/IBM/tivoli/netcool/platform/aix5/lib/libOpl.so", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q241", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Provided a test fix which resolved the issue.\n 14611.077.649.nco_p_mttrapd.gz", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q241", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nAll users of nco_p_mttrapd. *\n\nPROBLEM DESCRIPTION: *\nWhen starting the probe, customer see the following warning: *\nFailed to load module successfully *\n\nRECOMMENDATION: *\nUsers need to upgrade to nco_p_mttrapd v15.1. *\n\nProbe need to recompiled with fix in libnsprobe partialbuild.", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q241", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV40476\nREPORTED COMPONENT NAME\n NETCOOL/OMNIBUS\nREPORTED COMPONENT ID\n 5724O4800\nREPORTED RELEASE\n 100\nSTATUS\n CLOSED FIN\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-04-25\nCLOSED DATE\n 2013-06-10\nLAST MODIFIED DATE\n 2013-06-10\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q241", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n NC/OBUS MTTRAPD\nFIXED COMPONENT ID\n 5724P03MT", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q241", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R100 PSY\n UP", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q154", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Why does onstat -g cmsm shows message : Failover Arbitrator: Failover is disabled ?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q154", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Missing sysadmin database", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q154", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "After starting connection manager see below message in onstat -g cmsm\n\nFailover Arbitrator: Failover is disabled\n\nUnified Connection Manager: mySampleCM Hostname: minos\n\nCLUSTER pri_root_cluster LOCAL\nSLA Connections Service/Protocol Rule\nsla1_prim_cm1 0 5115/onsoctcp DBSERVERS=primary\nsla2_sec_cm1 0 5116/onsoctcp DBSERVERS=HDR,primary\n\nFailover Arbitrator: Failover is disabled\nORDER=HDR TIMEOUT=0 RETRY=1 PRIORITY=0\n\nLooking at the connection manager log see below message:\n\nCluster pri_root_cluster Arbitrator FOC string = ORDER=ENABLED TIMEOUT=10 RETRY=5\nFOC TIMEOUT = 10\nFOC RETRY = 5\nThe server type of cluster pri_root_cluster server sec_root is HDR.\nConnection Manager successfully connected to sec_root\nFOC converted from 'DISABLED' to 'ORDER=DISABLED TIMEOUT=0 RETRY=1'\nError: Arbitrator requires sysadmin database for failover but cannot find sysadmin in pri_root\nError: FOC: Failover Arbitrator disabled.\nConnection Manager started successfully\n\nIf $INFORMIXDIR/etc/sysadmin/stop file exists, remove it and restart the server.\nMake sure sysadmin database is created. After sysadmin database is created successfully restart the connection manager. You should see below in connection manager log :\n\nListener sla1_prim_cm1 DBSERVERS=primary is active with 4 worker threads\nConnection Manager successfully connected to pri_root\nThe server type of cluster pri_root_cluster server pri_root is Primary.\nCluster pri_root_cluster Arbitrator FOC string = ORDER=ENABLED TIMEOUT=10 RETRY=5\nFOC TIMEOUT = 10\nFOC RETRY = 5\nThe server type of cluster pri_root_cluster server sec_root is HDR.\nConnection Manager successfully connected to sec_root\nConnection Manager started successfully\nCM mySampleCM arbitrator for pri_root_cluster is active\n\nAlso onstat -g cmsm should show :\n\nonstat -g cmsm\n\nIBM Informix Dynamic Server Version 11.70.FC7W2 -- On-Line (Prim) -- Up 00:04:29 -- 173792 Kbytes\nUnified Connection Manager: mySampleCM Hostname: minos\n\nCLUSTER pri_root_cluster LOCAL\nSLA Connections Service/Protocol Rule\nsla1_prim_cm1 0 5115/onsoctcp DBSERVERS=primary\nsla2_sec_cm1 0 5116/onsoctcp DBSERVERS=HDR,primary\n\nFailover Arbitrator: Active Arbitrator, Primary is up\nORDER=HDR TIMEOUT=10 RETRY=5 PRIORITY=0\n\nPRODUCT ALIAS/SYNONYM\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q154", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "We have identify this is a bug from Impact 3.1 to Impact 4.x.\n Basically\n the SNMP datatypes are looking for this:\n\n ClassNotFoundException:\n com.micromuse.response.corbadsa.snmpdsa.SNMPDSAOrgNode\n\n This class has been modify on Impact 4.x to:\n\n com.micromuse.dsa.snmpdsa.SnmpOrgNode\n\n For now the work around of recreating the datatype will work.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q154", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "recreating the SNMP datatypes will work", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q154", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Netcool/Impact users who are perfroming an *\nupgrade from 3.1 to 4.0.2 and includes SNMP *\ndata types *\n\nPROBLEM DESCRIPTION: THE CLASS FROM SNMP DATATYPE HAS BEEN *\nUPDATE IT ON IMPACT 4.X *\n\nRECOMMENDATION: *\n*\n\n Steps to replicate: 1) Export Impact 3.1 server that includes\n SNMP data type 2) Import the exported directed directory to\n 4.0.2 install 3) Login to GUI server and view the data item or\n configuration: 4) Observer the error:\n\n ClassNotFoundException:\n com.micromuse.response.corbadsa.snmpdsa.SNMPDSAOrgNode", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q154", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This issue was resolved in: 4.0.2-TIV-NCI-IF0003\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q154", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IZ26482\nREPORTED COMPONENT NAME\n NETCOOL/IMPACT\nREPORTED COMPONENT ID\n 5724O59IS\nREPORTED RELEASE\n 400\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2008-07-07\nCLOSED DATE\n 2008-09-12\nLAST MODIFIED DATE\n 2008-09-12\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\nNETCOOL", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q154", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n NETCOOL/IMPACT\nFIXED COMPONENT ID\n 5724O59IS", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q154", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R400 PSY\n UP\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q154", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Customer was testing failover on impact 5.1 clustering.\n However, the failover test failed when they pull the cable of\n Primary server.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q154", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n All IBM Netcool/Impact 5.1 who are using failover and cluster\n settings\n\nPROBLEM DESCRIPTION:\n Clustering settings:\n 1) Machine a has primary cluster member NCIP\n 2) Machine b has secondary cluster member NCIS\n 3) Pull the plug off Machine a where primary is runing\n 4) Note that secondary takes about 2 hours to recognize that the\n primary is down\n\nRECOMMENDATION:\n Upgrade to Impact 5.1 Fix Pack 0001 5.1.0.1-TIV-NCI-FP0001", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q154", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fixed in Impact 5.1 Fix Pack 0001\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q154", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IZ49592\nREPORTED COMPONENT NAME\n NETCOOL/IMPACT\nREPORTED COMPONENT ID\n 5724O59IS\nREPORTED RELEASE\n 510\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2009-04-17\nCLOSED DATE\n 2009-05-05\nLAST MODIFIED DATE\n 2009-05-05\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q154", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n NETCOOL/IMPACT\nFIXED COMPONENT ID\n 5724O59IS", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q154", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R510 PSN\n UP", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q154", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The .type file of the Secondary ImpactServer configuration is truncated with the error message:\n*", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q154", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "APAR \"IZ81446: IMPACT 511 CLUSTER UNABLE TO REPLICATE DATATYPES WITH USERPARMETERS VALUES IN EXCESS OF 16,000 CHARACTERS.\" [link below]", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q154", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Additional comments associated with APAR IZ81446 release notes:\n\n\"a new property is added to increase the file size limit:\nAdd the property to $NCHOME/impact/etc/_server.props file\nwhere size limit can be 8192, 16384, 32768, etc.. \"\n\nThe property would have to be added to all ImpactServers in the Cluster and would require a restart to enable - ensuring that the ImpactServer started as Primary had the correct, uncorrupted .type file to be replicated across the Cluster. Also ensure that there are no trailing white-space characters on the property as these invalidate properties in lower versions of Impact.\n\nThe APAR is not an issue in Impact 6 and 7, but one would still have to include this property with an appropriate value to handle a large character length for the USERPARAMETERS parameter.\n\nThe character length includes the whole USERPARAMETERS property name as well as the definition.\n\nFor example one would add the property:\nto the files:\n*\nwhere one wished to allow the replication of a DataType between two ImpactServers called NCI1 and NCI2 in a Cluster where the USERPARMETERS property line were 20,000 characters long.", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q154", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "APAR IZ81446 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ81446]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q154", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "In an asymmetrical cluster (clients failover to 2 other servers,\n some to one\n the rest to the other) there is a large impact when the clients\n do a\n ServerGetClusterReplicaMatches call to find the server to fail\n over to. The\n impact can be so large as to make the server unavailable causing\n existing\n clients connected to failover, bringing the entire cluster\n down.", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q154", "section_id": 4, "heading": "COMMENTS", "parent": null, "text": "This APAR is associated with SPR# SWAS8GGHMC.\n The problem was caused by a user error or user misunderstanding.", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q154", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n LO61624\nREPORTED COMPONENT NAME\n DOMINO SERVER\nREPORTED COMPONENT ID\n 5724E6200\nREPORTED RELEASE\n 850\nSTATUS\n CLOSED USE\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2011-06-15\nCLOSED DATE\n 2013-11-21\nLAST MODIFIED DATE\n 2013-11-21\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q154", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n DOMINO SERVER\nFIXED COMPONENT ID\n 5724E6200", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q239", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The p2 based eclipse package does not start up correctly for non-administrator or it takes abnormal amount of time (10 minutes) to start up. The log file in the user's .eclipse/ibm.software.delivery.platform_7.5.0_???? folder, for example: /home/joe/.eclipse/ibm.software.delivery.platform_7.5.0_1529064711/configuration/1225137678916.log, may contain an entry like:\n\n!MESSAGE Exception launching the Eclipse Platform:\n\n!STACK\n\njava.lang.ClassNotFoundException: org.eclipse.core.runtime.adaptor.EclipseStarter\n\nat java.net.URLClassLoader.findClass(Unknown Source)\n\nat java.lang.ClassLoader.loadClass(Unknown Source)\n\nat java.lang.ClassLoader.loadClass(Unknown Source)\n\nat org.eclipse.equinox.launcher.Main.invokeFramework(Unknown Source)\n\nat org.eclipse.equinox.launcher.Main.basicRun(Unknown Source)\n\nat org.eclipse.equinox.launcher.Main.run(Unknown Source)\n\nat org.eclipse.equinox.launcher.Main.main(Unknown Source)", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q239", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "This issue has been identified as Eclipse defect 255268 [https://bugs.eclipse.org/bugs/show_bug.cgi?id=255268]. Review the Bug report for more details.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q239", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "WORKAROUND:\n\nDelete the user's .eclipse/ibm.software.delivery.platform_7.5.0_???? directory.\n\nFor example:\n\nrm -rf /home/joe/.eclipse/ibm.software.delivery.platform_7.5.0_1529064711\n\nThen relaunch the package.\n\nCross Reference information Segment Product Component Platform Version Edition Software Development Rational Application Developer for WebSphere Software Not Applicable 7.5.2 All Editions\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q239", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Error Message: Test did not run:\n testSignedContent10(org.eclipse.osgi.tests.security.SignedBundle\n Test)\n .\n Stack Trace: java.lang.Exception: Test did not run:\n testSignedContent10(org.eclipse.osgi.tests.security.SignedBundle\n Test)\n at\n org.eclipse.core.tests.session.SessionTestRunner.run(SessionTest\n Runner.java:307)\n at\n org.eclipse.core.tests.session.TestDescriptor.run(TestDescriptor\n .java:87)\n at\n org.eclipse.core.tests.session.SessionTestSuite.runSessionTest(S\n essionTestSuite.java:156)\n at\n org.eclipse.core.tests.session.SessionTestSuite.runTest(SessionT\n estSuite.java:174)\n at\n org.eclipse.core.tests.session.SessionTestSuite.runTestSuite(Ses\n sionTestSuite.java:192)\n at\n org.eclipse.core.tests.session.SessionTestSuite.runTest(SessionT\n estSuite.java:177)\n at\n org.eclipse.core.tests.session.SessionTestSuite.run(SessionTestS\n uite.java:129)\n at\n org.eclipse.core.tests.session.ConfigurationSessionTestSuite.run\n (ConfigurationSessionTestSuite.java:198)\n at\n org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:37\n 6)\n at\n org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:20\n 9)\n at\n org.eclipse.test.CoreTestApplication.runTests(CoreTestApplicatio\n n.java:35)\n at\n org.eclipse.test.CoreTestApplication.run(CoreTestApplication.jav\n a:31)\n at\n org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodW\n ithException(EclipseAppContainer.java:587)\n at\n org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseApp\n Handle.java:198)\n at\n org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.run\n Application(EclipseAppLauncher.java:110)\n at\n org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.sta\n rt(EclipseAppLauncher.java:79)\n at\n org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStart\n er.java:369)\n at\n org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStart\n er.java:179)\n at\n org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)\n at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)\n at org.eclipse.equinox.launcher.Main.run(Main.java:1407)\n at org.eclipse.equinox.launcher.Main.main(Main.java:1383)\n at org.eclipse.core.launcher.Main.main(Main.java:34)\n .", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q239", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "There are two situations will cause this situation:\n 1. Though the WeakReference key is GC'd, it is not on the\n ReferenceQueue yet.\n 2. After asking for more space in the rehash, there is a GC\n happened.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q239", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This defect will be fixed in:\n 6.0.0 SR11\n 6.0.1 SR4\n .\n WeakHashMap has been updated to prevent the problem.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q239", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV25853\nREPORTED COMPONENT NAME\n JAVA CLASS LIBS\nREPORTED COMPONENT ID\n 620700130\nREPORTED RELEASE\n 600\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2012-08-07\nCLOSED DATE\n 2012-08-07\nLAST MODIFIED DATE\n 2012-11-11\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q239", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n JAVA CLASS LIBS\nFIXED COMPONENT ID\n 620700130", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q239", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R600 PSY\n UP", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q239", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The following example shows the exception received when opening WebSphere Business Space in the Eclipse internal browser:\n\n!ENTRY org.eclipse.ui 4 0 2009-11-19 08:53:02.619\n!MESSAGE Unhandled event loop exception\n!STACK 0\njava.lang.StackOverflowError: operating system stack overflow\nat org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)\nat org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2371)\nat org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420)\nat org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384)\nat org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348)\nat org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200)\nat org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495)\nat org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)\nat org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490)\nat org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)\nat org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)\nat org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)\nat org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)\nat org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)\nat org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)\nat org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)\nat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\nat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)\nat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)\nat java.lang.reflect.Method.invoke(Method.java:599)\nat org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)\nat org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)\nat org.eclipse.equinox.launcher.Main.run(Main.java:1236)\nat org.eclipse.equinox.launcher.Main.main(Main.java:1212)", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q239", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "As a result of this problem, the Launch menu in the Servers view will launch the WebSphere Business Space in an external browser.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q239", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The error message in the console is as follows.\n\nException occurred during playback of script [Komut_Dosyas\u0131] [CRFCN0019E: RationalTestScriptException on line 99 of script Komut_Dosyas\u0131 - com.rational.test.ft.MethodNotFoundException: Rational.Test.Ft.Domain.Net.Wpf.WindowProxy.\u0130nputChars.].\n\nSteps to reproduce:\n\n 1. Switch the format to Turkish in the Region and Language control panel.\n\n [/support/docview.wss?uid=swg21652345&aid=1]\n\n 2. Open your .NET application.\n\n 3. Record a script that puts a character in an edit box of your .NET application.\n\n Disclaimer All source code and/or binaries attached to this document are referred to here as \"the Program\". IBM is not providing program services of any kind for the Program. IBM is providing the Program on an \"AS IS\" basis without warranty of any kind. IBM WILL NOT BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM, OR ITS RESELLER, HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.\n\n textBox1text().click(atDPoint(78.0,9.0));\n mainWindowwindow().inputChars(\"q\");\n\n 4. Playback the script.\n\nObserve the MethodNotFoundException and CRFCN0019E in the RFT console.\n\nIn the log you see the following entries.\n\nexception_name = com.rational.test.ft.MethodNotFoundException\nexception_message = Rational.Test.Ft.Domain.Net.Wpf.WindowProxy.InputChars\nexception_stack = ------------------------------\nat com.rational.test.ft.object.interfaces.ClientTestObject.invokeProxy(ClientTestObject.java:411)\nat com.rational.test.ft.object.interfaces.WPF.WpfTopLevelSubitemTestObject.inputChars(WpfTopLevelSubitemTestObject.java:121)\nat KomutDosyasi1.testMain(KomutDosyasi1.java:36)\nat org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)\nat org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)\nat org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)\nat org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)\nat org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)\nat org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)\nat org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)\nat org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)\nat org.eclipse.equinox.launcher.Main.run(Main.java:1438)\nat org.eclipse.equinox.launcher.Main.main(Main.java:1414)\nat org.eclipse.core.launcher.Main.main(Main.java:34)\n\nWhenever you start the application in Turkish format, you get the error. When you start the script in English format, the script runs error free.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q239", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "This issue has been identified as a product defect and logged under APAR #PI07030.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q239", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "The application under test runs on .NET Framework 4.0.\n\nRFT uses the the Cp1254 text file encoding.\n\n[/support/docview.wss?uid=swg21652345&aid=2] [/support/docview.wss?uid=swg21652345&aid=2]\n\n[/support/docview.wss?uid=swg21652345&aid=3] [/support/docview.wss?uid=swg21652345&aid=3]\n\n[/support/docview.wss?uid=swg21652345&aid=4] [/support/docview.wss?uid=swg21652345&aid=4]", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q239", "section_id": 4, "heading": "WORKAROUND", "parent": null, "text": "The following steps result in an error free playback.\n\n1. Switch the format to English.\n\n2. Start the AUT.\n\n3. Switch back to Turkish.\n\n4. Run the RFT script.\n\nNow the script runs error free.", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q239", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To correct this error, try adding the following lines:\ncom.ibm.mq.osgi.allclient,9.0.0.1,plugins/com.ibm.mq.osgi.allclient_9.0.0.1.jar,4,false\ncom.ibm.mq.osgi.allclientprereqs,9.0.0.1,plugins/com.ibm.mq.osgi.allclientprereqs_9.0.0.1.jar,4,false\n\nto the file:\n\\MQExplorer\\eclipse\\configuration\\org.eclipse.equinox.simpleconfigurator\\bundles.info\n\nThen retry starting the Explorer.\n\nPlease note that this error is specific to Fix Pack 9.0.0.1 and its plugins.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM MQ Not Applicable Windows", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q021", "section_id": 0, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Rational Application Developer for WebSphere Software, Version 7.0.0.8 [http://www-01.ibm.com/support/docview.wss?uid=swg24020739]\n6.1.1.8: WebSphere Application Server Toolkit Version 6.1.1 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24023506]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q021", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "While using the Web Services wizard to create a WAS51 JAX-RPC\n web services client project from\n a WSDL file, the web services Generate Client wizard failed with\n IWAB0014E Unexpected exception occurred.\n\n The proxy for WASv5.1 web service was not able to generated.\n WAS51 wsdl2java fails due to a name collision problem in the\n WSDL file.\n Specifically ,a name collision between the complex type name and\n the\n service name. In this example where both names are \"PNInfo\":\n\n and \n\n The two PNInfo.java\n (com.cnh.ebom. and com.cnh.ebom.icp.service.)\n were in conflict.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q021", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "A simple WORKAROUND, assuming you own the WSDL file,\n would be to change the Service name in the example from\n PNinfo to something else, such as PNInfoService.\n That is, change to\n \n and regenerate the web service,\n This workaround assumes you have control over the WSDL for this\n service\n and its is not already used in production as is.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q021", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of WebSphere Application Server *\nToolkit v6.1.1 and Rational Application *\nDeveloper v7.0 *\n\nPROBLEM DESCRIPTION: The webservice Proxy generation fails *\nwith a NullPointerException due to the *\nservice name and complex type name *\nbeing the same in the WSDL. *\n\nRECOMMENDATION: *\n\n If a WSDL contains a service that has the same name as a\n complex type then the JAX-RPC webservice proxy generation will\n fail with a NullPointerException.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q021", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The error was happening because the complex type name and\n service name were being used directly from the WSDL when it\n should come from the JAX-RPC mapping file since the underlying\n WAS webservice emitter will change the names.\n\nThe fix for this APAR is currently targeted for inclusion in\n the WebSphere Application Server Toolkit fixpack 6.1.1.8 and\n Rational Application Developer fixpack 7.0.0.8. Please refer\n to the following Recommended Updates page for WebSphere\n Application Server Toolkit delivery information:\n http://www.ibm.com/support/docview.wss?uid=swg27004980 [http://www.ibm.com/support/docview.wss?uid=swg27004980]\n and the following Recommended Updates page for Rational\n Application Developer delivery information:\n http://www.ibm.com/support/docview.wss?uid=swg27007823 [http://www.ibm.com/support/docview.wss?uid=swg27007823]\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q021", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PK67458\nREPORTED COMPONENT NAME\n WEBAPP SERVER A\nREPORTED COMPONENT ID\n 5724J0820\nREPORTED RELEASE\n 610\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2008-06-10\nCLOSED DATE\n 2008-06-12\nLAST MODIFIED DATE\n 2008-06-26\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q021", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBAPP SERVER A\nFIXED COMPONENT ID\n 5724J0820", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q021", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R610 PSY\n UP", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q021", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The WSDL Cache Policy is not refreshing from a WSDL in the local:/// directory.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q021", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "In a WS Proxy, you can refresh WSDL from an URL using WSDL Cache policy. However, if the WSDL is hosted on the DataPower appliance, such as in local:///, rather than on an external URL, the WSDL Cache Policy does not apply.\n\nFor instance, changes made to local:///test.wsdl are not picked up by WS Proxy although there is a WSDL Cache policy setting the URL Match expression to local:///test.wsdl.\n\nThis issue was reported to Quality Engineering but it was determined that the DataPower device is working as designed. The device will not poll WSDL files on the local store.\n\nThe WSDL Cache policy works with WSDL files hosted on an external URL.\n\nTo refresh a WSDL in the local:/// directory, disable and re-enable the service.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q021", "section_id": 2, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Fix packs for DataPower Service Gateway version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037486]\nFix packs for DataPower B2B Appliance version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037487]\nFix packs for DataPower Integration Appliance version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037488]\nFix packs for DataPower Gateway version 7.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24038524]\nFix packs for DataPower Gateway version 7.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24039783]\nFix packs for DataPower Gateway version 7.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24041543]\nFix packs for DataPower Gateway version 7.5.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24042194]\nFix packs for DataPower Gateway version 7.5.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24042699]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q021", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "WSDL cache refreshes continue after disabling the domain. This\n might cause WSDL fetch and compile errors to flood the logs.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q021", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "To minimize how often the refreshes occur, increase the WSDL\n cache refresh interval.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q021", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Affected is use of WSDL refresh.\n\nRefreshing WSDL's continues when objects are\n down.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q021", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fix is available in 7.0.0.16, 7.1.0.13, 7.2.0.10, 7.5.0.4,\n 7.5.1.3 and\n 7.5.2.1\n\nFor a list of the latest fix packs available, please see:\n http://www-01.ibm.com/support/docview.wss?uid=swg21237631 [http://www-01.ibm.com/support/docview.wss?uid=swg21237631]\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q021", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT17056\nREPORTED COMPONENT NAME\n DATAPOWER\nREPORTED COMPONENT ID\n DP1234567\nREPORTED RELEASE\n 720\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-09-26\nCLOSED DATE\n 2016-11-08\nLAST MODIFIED DATE\n 2016-11-21\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\n0", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q021", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n DATAPOWER\nFIXED COMPONENT ID\n DP1234567", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q021", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R752 PSY\n UP", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q021", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "A WSDL can be retrieved from a Web Service Proxy by allowing the GET method in the HTTP or HTTPS front side handler and going to the URL of the service including \"?wsdl\" for the query string such as:\n\nhttp://service:port/uri?wsdl\n\nBy default, the GET method is disabled within a Web Service Proxy. If the GET method is not enabled, you will not be able to retrieve the WSDL from the URL.\n\nNOTE: When a WSDL contains include or import references to other documents, the WSDL that is output from DataPower will also contain include or import references. If you are unable to access your complete WSDL or if you find that something is missing when using this method, contact IBM Support [http://www.ibm.com/support/docview.wss?uid=swg21236322] for assistance with troubleshooting the problem.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower Integration Appliance XI50 Not Applicable Firmware 3.6.1, 3.6.0 Edition Independent Business Integration WebSphere DataPower XML Security Gateway XS40 Not Applicable Firmware 3.6.1, 3.6.0 Edition Independent", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q021", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "This slowdown is due to the time required to render multiple WSDLs in certain browsers.", "logical_doc_id": 5, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q021", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To minimize the impact of this issue, consider creating additional WS-Proxies to reduce the number of WSDLs per proxy.\n\nNOTE: Firmware 3.8.1+ improved WebGUI performance in the Web Service Proxy configuration when populated with a large number of WSDL files.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower SOA Appliances Not Applicable Firmware Edition Independent", "logical_doc_id": 5, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q112", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q112", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Quintus #225183\n\nWith a model loaded, if I select an\n element in the browser and 'Edit Unit...' to deselect the option\n 'Include in next load', the item still loads every way I have\n tried to\n reload the model. I've tried reloading the model from the Files\n menu and\n selecting the name of the recently opened project, and I've\n tried using\n the Open button and selecting the project with various options\n including\n 'Restore Last Session'. In all cases, the unit I did not want to\n load,\n seems to load and the 'Include in next load' option is always\n returned\n to being checked.\n Of course, if I just manually unload the unit first things work\n ok using\n these various methods to reload the model but if I want to\n momentarily\n keep a unit loaded but set it so that it will not load the next\n time\n (which I thought was the intent of this option), I can't seem to\n get\n that to work. I am using Rhapsody 7.4.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q112", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "\"Include in next load\" check box (on Unit Information\n window) not working for reference units.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q112", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fixed in version 7.5.0.1.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q112", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PK89060\nREPORTED COMPONENT NAME\n TLOGIC RHAPSODY\nREPORTED COMPONENT ID\n 5724V74RP\nREPORTED RELEASE\n 740\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2009-06-16\nCLOSED DATE\n 2009-12-04\nLAST MODIFIED DATE\n 2009-12-04\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q112", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n TLOGIC RHAPSODY\nFIXED COMPONENT ID\n 5724V74RP", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q112", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R740 PSN\n UP\n\nOMNIbus 730; FP0004; OMNIbus 7.3.0; 7.3.0.4 DOWNLOADABLE FILES", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q112", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This fix pack is a cumulative fix release and addresses some APARs and internally found issues since the release of OMNIbus 7.3.0 Fix Pack 3.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q112", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "This is a cumulative fix pack for Tivoli Netcool/OMNIbus version 7.3.0.\n\n7.3.0-TIV-NCOMNIbus-FP0004 Fixes\n\nIZ80783\nWhen probe failover is enabled, and a slave probe is running on\nWindows, the number of handles as seen in the Windows Task\nManager grows continuously. This problem has been fixed.\n\nIZ80678\nAlerts with a Manager of GatewayWatch were previously missing\ndata in the ServerName and Tally columns of the ObjectServer.\nThis problem has been fixed.\n\nIZ75736\nAn encrypted PA.Password shows in clear text in the Administrator\nGUI. Also, if any value is changed in the Administrator GUI,\nencrypted passwords get written out in decrypted form. This\nproblem has been resolved.\n\nIZ84694\nInstallation of a 7.3 probe on Windows may fail.\n\nIZ84890\nThe object server core dumps when starting up due to bad trigger\nsyntax. This problem has been resolved.\n\nIZ78509\nFields containing single quotes can cause tools to fail from the\nWindows Event List. This problem has been resolved.\n\nIZ85473\nOMNIbus fix pack installations were failing due to Java out of\nmemory errors. This problem has been resolved.\n\nIZ86656\nOMNIbus 7.3 is now supported on AIX 7.1.\n\nIZ84650\nThe recorded profiling times may be incorrect on a busy system.\nThe profiling timer was not being suspended when the Object\nServer was busy with other tasks. This problem has been\nresolved.\n\nIZ86876\nWhen running the 'uninstall' program for a gateway or probe, the\nuninstaller would be removed but the gateway or probe would\nremain installed. This has been fixed.\n\nIZ83743\nJapanese character strings are truncated when displayed in the\nbottom portion of the Windows event list. This problem has been\nresolved.\n\nIZ81420\nWhen a group is deleted via the Administrator, the tool access\ndata associated with that group is not removed. This caused\nnco_confpack export to fail. The tool access data associated\nwith the group is now removed. However, if the Administrator is\nnot used to delete the group - if the group is deleted using the\nSQL interface, with 'drop group ' - the tool access\ndata will not be removed, and the nco_confpack export will still\nfail.\n\nIZ84304\nReduced memory required for storing large multi-column lookup\ntables.\nIncreased performance of lookup tables with large numbers of\nentries.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q112", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "IZ86660\nIf a tool that required a prompt was launched, it would be\nexecuted when the prompt window is closed with the 'X' or using\nAlt+F4. The new and correct behavior will be for the tool\nexecution to be aborted.\n\nIZ89203\nProbes on Windows failed to locate rules files given by relative\npaths on the command line. This has now been fixed.\n\nIZ69192\nProbes on Windows could create log file pools instead of writing\nto a single log file. This has been fixed.\n\nIZ88264\nUpdates were made to the default rules file provided for\nintegration with Tivoli Application Dependency Discovery\nManager (TADDM).\nNOTE: Applying the fix pack will overwrite the current rules\nfile at NCHOME/omnibus/extensions/taddm/tivoli_eif_taddm.rules\nwithout prompting the end user.\n\nPREREQUISITES\nThis fix pack installs on any GA Release (including previous GA fixpacks) of Tivoli Netcool/OMNIbus 7.3.0.\n\nINSTALLATION INSTRUCTIONS\nInstallation\n\nUNIX\n---\n\nIMPORTANT: Before installing this fix, ensure that all Tivoli Network\nManagment applications on your computer have been shutdown.\n\nExtract the contents of 7.3.0-TIV-NCOMNIbus--FP0004.tar\nin to a temporary directory, replacing the placeholder with the\nstring identifying your platform.\n\nFrom within the directory enter the following command to install this fix\ninteractively.\n\n./install.bin\n\nWindows\n\nIMPORTANT: Before installing this fix, ensure that all Tivoli Network\nManagment applications on your computer have been shutdown.\n\nExtract the contents of 7.3.0-TIV-NCOMNIbus-win32-FP0004.zip\nin to a temporary directory.\n\nTo install this fix interactively double click install.exe.\n\nDOWNLOAD PACKAGE\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 7.3.0-TIV-NCOMNIbus-AIX-FP0004 12/31/2010 US English 173813760 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=7.3.0-TIV-NCOMNIbus-AIX-FP0004&product=ibm%2FTivoli%2FTivoli%20Netcool%20OMNIbus&source=dbluesearch] [ ] 7.3.0-TIV-NCOMNIbus-HPUX-FP0004 12/31/2010 US English 180572160 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=7.3.0-TIV-NCOMNIbus-HPUX-FP0004&product=ibm%2FTivoli%2FTivoli%20Netcool%20OMNIbus&source=dbluesearch] [ ] 7.3.0-TIV-NCOMNIbus-HPUXIA-FP0004 12/31/2010 US English 193351680 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=7.3.0-TIV-NCOMNIbus-HPUXIA-FP0004&product=ibm%2FTivoli%2FTivoli%20Netcool%20OMNIbus&source=dbluesearch] [ ] 7.3.0-TIV-NCOMNIbus-Linux-FP0004 12/31/2010 US English 172175360 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=7.3.0-TIV-NCOMNIbus-Linux-FP0004&product=ibm%2FTivoli%2FTivoli%20Netcool%20OMNIbus&source=dbluesearch] [ ] 7.3.0-TIV-NCOMNIbus-ZLinux-FP0004 12/31/2010 US English 198799360 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=7.3.0-TIV-NCOMNIbus-ZLinux-FP0004&product=ibm%2FTivoli%2FTivoli%20Netcool%20OMNIbus&source=dbluesearch] [ ] 7.3.0-TIV-NCOMNIbus-Solaris-FP0004 12/31/2010 US English 181193216 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=7.3.0-TIV-NCOMNIbus-Solaris-FP0004&product=ibm%2FTivoli%2FTivoli%20Netcool%20OMNIbus&source=dbluesearch] [ ] 7.3.0-TIV-NCOMNIbus-Windows-FP0004 12/31/2010 US English 211791005 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=7.3.0-TIV-NCOMNIbus-Windows-FP0004&product=ibm%2FTivoli%2FTivoli%20Netcool%20OMNIbus&source=dbluesearch] [ ]\nPRODUCT ALIAS/SYNONYM\n OMNIbus\n\n[/support/docview.wss?uid=swg24027482&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24027482&aid=2]Problems (APARS) fixed\nIZ80783, IZ80678, IZ75736, IZ84694, IZ84890, IZ78509, IZ85473, IZ86656, IZ84650, IZ86876, IZ83743, IZ81420, IZ84304, IZ86660, IZ89203, IZ69192, IZ88264, IZ37272, IZ60407, IZ62951, IZ62720, IZ67228, IZ63491, IZ55799, IZ65930, IZ65261, IZ65536, IZ65290, IZ35655, IZ74616, IZ60269, IZ62580, IZ63926, IZ66216, IZ66645, IZ66738, IZ68706, IZ70481, IZ70653, IZ66383, IZ69057, IZ71966, IZ70104, IZ67525, IZ69099, IZ65925, IZ68862, IZ72292, IZ75578, IZ75853, IZ75955, IZ70187, IZ76225, IZ76040, IZ77352, IZ78305, IZ79684, IZ80143, IZ77515, IZ81037, IZ82721", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q112", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "You are getting this error because your Clementine/Modeler hasn't been configured to work with SPSS Statistics application.\n\nTo configure Clementine/Modeler to work with SPSS and other applications, choose Helper Applications from the Tools menu.\n\nIf Statistics is installed on your computer, you can configure Clementine to send data to SPSS using the SPSS Export node.\n\nStatistics Interactive: Enter the name of the command to execute Statistics in interactive mode (usually, paswstat.exe in the Statistics program directory).\n\nConnection: If Statistics Server is located on the same server as Clementine/Modeler Server, you can enable a connection between the two applications, which increases efficiency by leaving data on the server during analysis. Select Server to enable the Port option below. The default setting is Local.\n\nPort. Specify the server port for SPSS Statistics Server.\n\nStatistics License Location Utility: Click on this button and browse to the Statistics program installation directory on the client computer.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q112", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Modeler forum is Live! [https://developer.ibm.com/answers/topics/modeler/?smartspace=predictive-analytics]\n\nHISTORICAL NUMBER\n 54450", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q112", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Environment:\n IBM WebSphere Application Server 7.0.0.15\n IBM Maximo Asset Management 7.5.0.3\n Tivoli's process automation engine 7.5.0.3\n Server OS: Windows Server 2008 R2 6.1 build 7601 Service Pack 1\n\nConcerns/Problem:\n On creation of labour contract entries in labour reporting, when\n creating an invoice from these labour transactions, the \"Create\n Invoice\" dialog box is displayed listing the invoice number and\n description.\n Is it possible to make the Description field mandatory when\n creating invoice from Labor Report application select action\n menu \"Create Invoice\" dialog box?\n\nWhen creating an invoice from Labor Report application, Maximo\n uses the object (CREATEINVOICE) which is a non-persistent\n object.\n\nI have tested this on Maximo demo,\n 1. I tried to set the non-persistent object, CREATEINVOICE, the\n description field to be required field in Application Designer\n application, it does not work for me\n 2. I tried to change the CREATEINVOICE description field to\n required in Database Configuration application, it does not work\n for me. After set the description be a required field in\n database, I still can create invoice from Labor Report\n application select action menu without to enter any data in the\n invoice description field.\n 3. I have tried to make the invoice table/object description\n field as required in Application Designer application, but this\n still not work for the Labor Report create invoice dialog box.\n 4. It works only I changed the Invoice description to required\n in database configuration application.\n\nIt seems if you want to make the invoice description to be\n mandatory, you need to do this from Database Configuration for\n invoice object.\n\nBut this causes another issue.\n When testing, at the point you click the \"OK\" button when the\n description is blank you get a message stating the field is\n mandatory, then you enter a description and click the \"OK\"\n button again and the following message appears:\n \"BMXAA4129E - Record already exists for Site=LYB,\n Invoice=INV-59092. Ensure that the key value for the given\n record is unique.\"", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q112", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Maximo neither creates the invoice or lets you save the record\n and you must cancel the \"Create Invoice\" dialog box.\n When reopen the \"Create Invoice\" dialog box, and enter the\n description in the field, the invoice is created.\n But the problem is one invoice number is lost. That is, if at\n the first time the user does not enter data in the Description\n field and click \"OK\" button, Maximo shows error message (field\n is mandatory), then user has to close the \"Create Invoice\"\n dialog box and reopen it again, it increments to the next\n invoice number, and one invoice number lost.\n The client does not want to lose an invoice number as this is a\n big problem for auditors.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q112", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nMaximo users who use the Create Invoice functionality in the *\nLabor Reporting application. *\n\nPROBLEM DESCRIPTION: *\nDescription made required in Create Invoice dialog was not *\nvalidated - user could click OK without being prompted with *\nan error saying required field description is blank. *\n\nRECOMMENDATION: *\nPlease upgrade to REL 7.5.0.5 or request hotfixes. *", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q112", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This is fixed in code.\n\nThe fix for this APAR is contained in the following maintenance\n package:\n | release\\fix pack | Interim Fix for Release 7.5.0.5 Product\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q112", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV43838\nREPORTED COMPONENT NAME\n WORK & MTRL APP\nREPORTED COMPONENT ID\n TIVOWRKMM\nREPORTED RELEASE\n 750\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2013-06-05\nCLOSED DATE\n 2013-06-07\nLAST MODIFIED DATE\n 2013-06-07\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\nMAXIMO", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q112", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WORK & MTRL APP\nFIXED COMPONENT ID\n TIVOWRKMM", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q112", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R750 PSY\n UP", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q112", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The command fails and the following error is received: Tool in menu but not found, menu: AlertsMenu, tool: CLEAR_LWY.", "logical_doc_id": 5, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q112", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The menu AlertsMenu has a tool in it called CLEAR_LWY, however the tool no longer exists.", "logical_doc_id": 5, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q112", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Recreate the tool and associate it with the menu and try to run the command again.", "logical_doc_id": 5, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q141", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "In the following image, Word 1 and Word 2 are on separate lines, but after NormalizeCCO is run may show in a single line as Word Word 1 2.\n\n[/support/docview.wss?uid=swg21701910&aid=1]", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q141", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "When text is not cleanly printed in lines, such as when the font varies or the text is vertically offset, Datacap may not always be able to locate text when loading field values. The NormalizeCCO goes through the CCO file, and cleans up all the entries so they appear in regular lines. For most images this improves ultimate recognition results, but for some complex images, NormalizeCCO cannot determine where to separate the lines and merges all words into a single line.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q141", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Add the following action prior to NormalizeCCO.\n*\n\nThe first parameter is the percentage of a line that two words must be offset to be considered as separate lines. If the value is not set, the default is 50. In the example, if two words are vertically offset by more than 35% of the height of the words, then they are considered to be on separate lines. Lower values are more likely to split words into separate lines. Higher values are more likely to merge words into a single line.\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Datacap Not Applicable Windows 9.0.1, 9.0.0", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q141", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "In cases where ALSCAL users have reported this error, the data file was usually comprised of one or more proximity matrices, as opposed to raw data. In these situations, there were rows of system missing (sysmis) values in the .sav file. This occurrence often involved data that had been created by exporting a database or spreadsheet file, such as an Excel file. If you were reading in a file with proximity matrices for 15 variables for each of 10 cases (for an individual differences, or INDSCAL, model), ALSCAL would expect 150 rows of data. If extra lines were read at the bottom of the file, ALSCAL would interpret these rows as part of the data for case 11. If the data matrix for case 11 is incomplete, you get the error message that you mentioned. Check for any such extra lines in the data file and delete them. The extra lines would not necessarily be at the end of the file. Sometimes, people put blank lines between each pair of matrices.\n\nThis error message has also been reported in cases where the data was comprised of raw data, (such as respondent ratings on each variable, with each row in the data file representing a respondent and each variable representing an attribute that was rated), but where the user's syntax or dialog choices indicated that the data was comprised of one or more proximity matrices. If the number of rows of data did not equal a multiple of the number of variables (or exactly the number of variables when an INDSCAL model was not chosen), then the last matrix would be considered incomplete and the error message would be printed. In this situation, however, a more serious misrepresentation of the data (case-level vs. matrix) would underlie the message.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q141", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The error has also been reported in cases where the user has analyzed a subset of the variables in a proximities matrix but did not filter out or delete the rows that correspond to the unused variables. For example, suppose that you had a proximities matrix with 60 variables, item1 to item60, and 60 rows corresponding to those variables. If you ran ALSCAL with only 50 of the variables named in the variable list, but did not filter the cases for the unused variables, ALSCAL would try to analyze a 60X50 matrix and interpret the 10 extra rows as belonging to an incomplete second subject matrix. Thus, you would get the \"too few cases\" message when you really had too many cases. You can run ALSCAL in this situation by first filtering out or deleting the cases that correspond to unused variables. You can filter cases from the 'Data->Select' Cases' menu. If you are using the first 50 variables, for example, you could then choose to select cases \"Based on time or case range\" and choose a range of 1 to 50. The equivalent command syntax would be:\n\nFILTER OFF.\nUSE 1 thru 50.\nEXECUTE.\n\nIf your unused variables are scattered among the used variables, rather than in a block at the end or beginning of the dictionary, then you would need to construct a more complex filter condition under \"If case satisfies condition\",. If there was a VARNAME_ variable in the proximities file (which is not necessary for ALSCAL), with values ranging from \"ITEM1 to ITEM60 (for example), you could filter out the cases to be omitted by a condition such as\nNOT(ANY(VARNAME_,'ITEM24','ITEM35','ITEM43','ITEM52')). The equivalent syntax commands are:\n\nUSE ALL.\nCOMPUTE filter_$=NOT(ANY(VARNAME_,'ITEM24','ITEM35','ITEM43','ITEM52')).\nVARIABLE LABEL filter_$ 'NOT(ANY(VARNAME_,'ITEM24','ITEM35','ITEM43','ITEM52')) (FILTER)'.\nVALUE LABELS filter_$ 0 'Not Selected' 1 'Selected'.\nFORMAT filter_$ (f1.0).\nFILTER BY filter_$.\nEXECUTE.\n\nFor a single analysis with the reduced proximities matrix, you could use this simple command set just before your ALSCAL command:\ntemporary.\nselect if NOT(ANY(VARNAME_,'ITEM24','ITEM35','ITEM43','ITEM43')).\nYour alscal command here.\n\nIf you don't have a VARNAME_ variable, you could create an id variable based on the case number and filter on that variable. (Don't include the id variable in the ALSCAL command.\n\ncompute id = $casenum.\nexecute.\ntemporary.\nselect if NOT(ANY(id,24,35,43,52)).\n\nHISTORICAL NUMBER\n 24536", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q141", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "I am loading line data with carriage controls (CC) into an OnDemand application that I have defined (on the View Information tab) with both a Line Count value of 60 and with CC = Yes. When I view the loaded data from the OnDemand client most of the page breaks are wrong. Some pages have the correct number of lines per page while others have only a few lines on the page. Also, when I set the application to use Large Object (LO) support on the Load Information tab, though I know there should be 100 pages total when I go to page \"100\" (per the client) I don't see the expected last data. But, if I continue scrolling (to page \"130 \") then I see the last lines of data that I expected to be on page 100.\n\nFurthermore I have found that If I blank out the Line Count value in the application, the data will still display incorrectly. It's only after I reload the data with the Line Count value blanked out that the data will display correctly. Why am I getting these results?", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q141", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The OS/390 Indexer does not support LINECNT (the line count parameter).", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q141", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "The OS/390 Indexer requires that there be carriage control characters for line print reports that don't use the ANYSTORE exit. The OS/390 indexer ignores the LINECNT, CC and CCTYPE indexing parameters.\n\nThe Line Count value (on the View Information tab) should match the value for LINECNT (from the Index Information tab) . so that indexing and viewing are in sync.\n\nTherefore, when using the OS/390 Indexer do not specify a value for Line Count . Instead, leave it blank, otherwise it can cause the undesired page breaks that you are seeing.\n\nNote: OnDemand windows client 8.4.1.1 (or earlier) ignored the Line Count value on the View Information tab when the application was set to use LO (Large Object).\n\nNote: Starting with OnDemand server version 8.5, when loading as LO, the value for Line Count is stored with the data in a Large Object Header. Therefore, for any changes to take effect you will need to reload the data. If the reload is done with arsdoc get/arsload, there is the added condition that you need to edit the generic index file generated by arsdoc get and change the LARGE_OBJECT_DOC_LINE_CNT: to -1", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q141", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "I have created an application with User Defined data type of extension PDF, and I'm using the Generic indexer to archive my data. I've created an .IND file in the IFS but when I try to add the report to OnDemand, I receive the error message \"Invalid generic index file format: > <\" in both the system log 88 message and in the joblog as a CPF9898. What am I doing wrong?", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q141", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "It's possible that your .IND file is either the wrong Coded Character Set ID (CCSID) or it contains blank lines.", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q141", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "To check the CCSID, to make sure it matches the CCSID specified for the instance owner, do the following:\n\n1. Use WRKLNK to put an 8 next to the .IND file. Look for \"Coded character set ID\".\n2. If the CCSID shows a value other than the value of the instance user profile (e.g., QUSROND) or 1252 to indicate it came from the PC, change it. You can do this by using option 2 next to the .IND file and then pressing the F15 key to change the CCSID.\n\nTo check to see if your .IND file has blank lines, do the following:\n\n1. Use WRKLNK to put a 5 next to the .IND file. A correct .IND file should show:\nCOMMENT: Test Index file\nCODEPAGE:37\nCOMMENT: Index value #1 - First Name\nGROUP_FIELD_NAME:FirstName\nGROUP_FIELD_VALUE:Bob\nCOMMENT: Index Value #2 - Middle Initial\nGROUP_FIELD_NAME:MiddleInitial\n(and so on.......)\n2. If you see blank lines between any of the index values or anywhere else in this file, you'll need to either remove them using a \"D\" to the left of the line or add the word \"COMMENT:\" at the beginning of the blank line.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q141", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "I am trying to implement File Manager and am having trouble with CONTAINS. I try to use it like the book describes and it doesn't work. The problem seems to be with multiple 'needles'. If I use just one, it works fine. It appears that the example is trying to say that multiple 'needles' separated by a comma is an 'or' function. Is that right? I have found that if the CONTAINS spans multiple lines it fails and if it is all in one line it works. How should the following be coded to work, and where is it documented:\n\nIf CO(FLD(7,8),''USER1'',\n''USER2'',\n''USER3'')\nThen exit ''drop''", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q141", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Missing REXX continuation character.", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q141", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "When spanning multiple lines, the REXX processing requires a comma as a continuation character (in addition to the comma needed as part of File Manager syntax). So, in your example, you would need 2 commas between each of the strings to be compared. For example, with this COntains [http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/fmnu1l02/2.3.5.9?DT=20111012002410]:\n* If CO(FLD(7,8),''USER1'',,\n* ''USER2'',,\n* ''USER3'')\n\n....the first comma is part of what you would use for File Manager, whether it is on one or more than one line. As the coding you are doing is in the REXX language, the second comma in the example is required as a line continuation character per REXX syntax, not File Manager syntax. Therefore, besides the File Manager required comma, the second comma is required REXX syntax to continue onto the next line.\n\nYou can find this documented in the TSO/E REXX Reference [http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IKJ4A3A0/CCONTENTS?SHELF=ikj4bkc0&DN=SA22-7790-10&DT=20110621111559] located on the TSO/E bookshelf at:\n\nhttp://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/Shelves?filter=tso&SUBMIT=Find [http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/Shelves?filter=tso&SUBMIT=Find]\n\nIf you will be using REXX coding as part of your use of File Manager, it would be a good idea to have a REXX Reference handy to help with the REXX syntax. RELATED INFORMATION\n#File Manager Library [http://www.ibm.com/software/awdtools/filemanager/library/]\nz/OS V1R13.0 TSO/E Bookshelf [http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/Shelves/ikj4bkc0]\n\nHISTORICAL NUMBER\n 17733-082-000", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q284", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Multiple, unrelated mailboxes appear as options in the dropdown list for the Mailbox Path field of the Upload Files tab in My File Gateway", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q284", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "There are two parts to the cause. The first part is that at least one of the groups of which the User Account is a member has permissions to specific mailboxes. Those are the extra mailboxes showing in the dropdown list. The other part is that, as the user account was not created automatically by creating a partner in the SFG user interface, no virtual root was automatically assigned to it, so it shows every mailbox that the user account has permissions to either directly or through its group memberships.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q284", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "There are two choices to resolve the problem. Choose the one that best fits your needs.\n\nOption 1: Create a virtual root for the user account. The advantage to this method is it is specific to the user account. The potential disadvantage is that the user account will only have access to its virtual root mailbox and its sub-mailboxes, even if it needs access to some of the other mailboxes. Create the virtual root by doing the following:\n\n1. Edit the user account and write down the value in the Identity field. For this example, assume it is Partner537.\n 2. Go to Deployment > Mailboxes > Virtual Roots in the SBI menu.\n 3. Create a virtual root using /Partner537 as the mailbox.\n\nOption 2: Remove the specific mailbox permissions in all groups that the user account is a member of. The advantage to this is it will likely allow you to take care of multiple user accounts in one process. The potential disadvantage is that if any of the members of that group really do need access to all of the mailboxes that the group specifically has permissions to, they will lose them. Change the groups' permissions by doing the following:\n\n1. Edit the User account and write down all the items showing in the Assigned box of the Groups screen, then click Cancel.\n 2. Go to Accounts > Groups in the SBI menu.\n 3. Type the name of one of the groups written down above in the Group Name field and click Go!\n 4. Click \"edit\"\n 5. Click the Next button until you are at the Assign Permissions screen.\n 6. Remove all mailbox entries from the Assigned box, then click Save.\n 7. Click Finish.\n 8. Repeat steps 3-7 for all the other groups that the user account is a member of.\n\nNOTE: No method exists for leaving the specific permissions in the groups, but also giving the user account access through My File Gateway to two or more mailboxes that have only the root mailbox as a common ancestor.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q284", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Problem Description: Unable to manage LDAPx accounts. When\n loggin in as\n a regular ITIM user that manages an LDAPX account, you are\n unable to\n change the password and do other changes to the account even\n though an\n ACI is in place granting all permissions. In fact the account\n doesn't\n even show up under 'Manage Passwords' at all. To debug this\n issue both\n I and the customer ran DocTool and when we looked at the ACI for\n the\n LDAPX account type the only attribute given read/write\n permissions was\n 'labeleduri'. Even though the GUI shows all permissions being\n granted.\n Customer Recreate: See steps below.\n Desired Behavior: That ACI permit ITIM users to manage their\n LDAPX\n accounts.\n Your Steps to Duplicate:\n 1. Install LDAPX agent 4.5.5 build 4.5.1011\n 2. Install profile on ITIM server. I recreated on 4.5.1 FP16\n IF19\n 3. Go to 'My Organization'->'Control Access'. Then 'Add' a new\n ACI.\n 4. Select 'Account' and then make the Customer Class '\n XLdapAccount'.\n 6. IN the ACI make the scope 'Subtree', under operation grant\n everything\n and under 'Attribute Permissions' grant everything for read and\n write.\n 7. Make sure \"Allow Self' is set to 'Yes' and then save.\n 8. Do recon to get accounts with the agent and then adopt orphan\n account\n to an ITIM user.\n 9. Login as the ITIM user that adopted one of thes LDAPX\n accounts.\n 10. You should not see the account under manage passwords, you\n may see\n it undermanage accounts.\n 11. Run DocTool and then look at the info for the ACI you\n created.It\n will show that only the 'labeleduri' attribue has any\n permissions set.\n ITIM SERVER RELEASE: 4.5.1.5183\n Environment:\n Operating System : Win2k/AIX5.2\n enrole/ITIM version : enRole 4.5.1.5183\n interim release installed: IF19\n Database server : DB2 8.1\n Directory server : IDS 5.1\n WebServer : WAS 5.02\n Java Version : 1.3.1_06\n Other software? : no\n Agent(s) installed? : LDAPX 4.5.1011", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q284", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "This is a documentation change for the ITIM\n Configuration Guide. Please use the following information:\n The \"CustomLabels.properties\" in \"$ITIM_HOME\\Data\" folder needs\n to be modified to correct this problem. The LDAPX Agent has\n two password attributes, erpassword and userpassword. Only one\n exists in the CustomLabels.properties file To correct the\n problem, edit the CustomLabels.properties file in\n \\Data\" folder and find the line:\n userpassword=Password and change that to:\n userpassword=User Password also look for the line\n erpassword=Password and ensure erpassword=Password\n Note: The solution shown above has been provided only for the\n English language. If a different language pack is installed on\n the system, then user needs to edit the\n words to accomodate the language used.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q284", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The ITIM Configuration Guide will be updated\n to provide the configuration information needed.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q284", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IY59603\nREPORTED COMPONENT NAME\n ITIM AGENTS\nREPORTED COMPONENT ID\n 5724C34AG\nREPORTED RELEASE\n 450\nSTATUS\n CLOSED DOC\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2004-07-28\nCLOSED DATE\n 2004-10-14\nLAST MODIFIED DATE\n 2004-10-14\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nPublications Referenced SC32149300 FIX INFORMATION\nFIXED COMPONENT NAME\n IBM TIV IDENT M\nFIXED COMPONENT ID\n 5724C3402", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q284", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Does IBM Mobile Connect offer user account lockout protections or password lockouts? Yes.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q284", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "For complete instructions on how to install and perform an initial configuration on IBM Mobile Connect see technote 7043160 [http://www-01.ibm.com/support/docview.wss?uid=swg27043160]. For specific details on creating and configuring the resources discussed in this article see pages 6 - 9 of that same document.\n\nThe first resource to be aware of is called the Wireless Password Policy. Why Wireless? It's a legacy thing, but really has nothing to do with something which is wireless.\nWireless Password Policy - Within the Gatekeeper under the Default Resources container you will find the Wireless Password Policies. There are 3 which are shipped with IMC, but as with any resource new ones could be created, or existing ones modified. This resource container was primarily used when the requirement was to have IMC local user accounts which required passwords. This resource allowed to specify the rules for passwords used to authenticate using local IMC system accounts. However, it is not common to use local IMC based system accounts, but rather to leverage existing user directories within LDAP or RADIUS servers.\n The Wireless Password Policy still does offer a function which can be useful on a couple of fronts. * User Account Lockouts and where they take place.", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q284", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "[/support/docview.wss?uid=swg21985055&aid=1]\nThe field \"Number of failed connection attempts before lock\" allows the IMC Administrator to specify how many failures to connect occur before IMC locks that account. It is important to understand how IMC counts failed connection attempts. In the above screen shot we have 5 failed connection attempts before lock. Traditionally that would lead one to believe that after 5 consecutive failed connections where the password was incorrect IMC would lock the account. That is not how this works. IBM Mobile Connect will ONLY count a connection attempt as FAILED if a unique password arrives on the request. That means that in order for IMC to lock an account locally the same user account would have to submit 5 requests which all had a different password. The reason that IMC operates this way is to implement another user account lockout feature and that is User Account Lockout at the Authentication Server level. It is desirable in most cases to prevent unnecessary calls from users into call centers to get their accounts unlocked in the company LDAP / RADIUS servers. To assist with this problem IMC will not resend a new request to an LDAP / RADIUS server for authentication on an account which IMC has received a return code indicating a bad password. If a new request has a different password after a failed attempt then it would go to the authentication server for validation. * The use case here would be an IBM Verse or Connections Mobile app which has the log-in credentials stored in the app. The account password needs to be changed and is changed by the user on the company authentication server. However, on the mobile app the password has not been changed. The mobile device attempts to connect to Traveler or Connections, etc. using a password which is no longer valid. IMC has no awareness of this. A request is sent to IMC and forwarded to the Authentication Server. The Authentication Server responds back with a bad password response. IMC sends this response to the device and notes this failure.", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q284", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "ONLY with the Wireless Password Policy in use with an Authentication Profile will IMC accept the incoming requests from the device, but if the requests contain the same known bad password IMC will NOT connect to the Authentication Server again, but does create a Message Log (wg.log) entry indicating that this account has tried X times with the same bad password. The login fails and device is notified of the failure. This helps to prevent an account from being locked out at the Authentication Server.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q284", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Authentication Profiles\n\n[/support/docview.wss?uid=swg21985055&aid=2]\n\nAuthentication Profiles are the mechanism by which IMC validates user requests for access to configured applications. Authentication Profiles are associated with HTTP Access Services or Mobile Access Services. For HTTP Access an Authentication Profile is configured on the Mode Tab. For flexibility among many possible HTTP Access Service resources there exists the ability to \"Automatically unlock accounts after (min).\nIf user accounts do become locked at the IMC level, in order to assist in preventing unwanted calls from users to unlock their accounts at this level the Authentication Profile may specify the number of minutes before IMC will automatically unlock a user account. This feature has no bearing on accounts locked for other reasons than the number of failed connection attempts with a bad password, nor does this feature have any affect on locked accounts at an LDAP or RADIUS server level.\n\nHTTP Access Service\n[/support/docview.wss?uid=swg21985055&aid=3] [/support/docview.wss?uid=swg21985055&aid=3]", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q284", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "A feature added with APAR IV82920 will allow a timer specified in minutes which will reset the Password Retry timeout. The default time is 1440 or 24 hours. So, the default behavior (and following the values in this technote) would be if 5 CONSECUTIVE requests were received from a user account which had different bad passwords then the account would get locked. Otherwise, when using the same bad password IMC gets the failure from LDAP, and does not return to that server if it receives new requests with the same known bad password.\nWhile the Lockout Protection is normally viewed as a positive thing, sometimes more control over the situation is desired. One use case would be where the End User successfully changes their password, but it may take X amount of time to become effective at the LDAP server. If that End User attempts to use the updated password immediately, IMC will get a failed login attempt return code from LDAP, and upon subsequent attempts which also use the same flagged incorrect password IMC will not return to LDAP. The End User is unaware of this, and if there were a configuration option allowing the same bad password counter to expire after a certain amount of time then end users might be educated that sometimes updated passwords may take some time to become effective, and IMC could still offer protection while allowing End User's with known good passwords to ultimately log in to their application via IBM Mobile Connect.\n In that case an administrator could use the Password Retry timeout (min) feature to lower the amount of time which made sense for their environment.", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q284", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What is changing in the Infosphere Information Server support experience?", "logical_doc_id": 5, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q284", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "We are always striving to seek new and better ways to improve our communications and the support we offer. With that in mind, we\u2019re excited to announce we\u2019re launching a new Support Community/Experience for a select number of IBM products, Information Server will be one of these products going live with this new technology in the coming weeks.", "logical_doc_id": 5, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q284", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Our new community will provide you enhance transparency into your ticket resolution workflow along with improved self-service options. You can see a quick video overview of the initial experience here: https://mediacenter.ibm.com/media/t/1_hjcvgybl [https://mediacenter.ibm.com/media/t/1_hjcvgybl]\n\nThe move to this new support experience should be seamless for you. Specifically:\n\u00b7 Your bookmarks and existing access methods will automatically connect to the new Support Community once you\u2019ve selected Information Server as a product.\n\u00b7 The same URLs you currently use will continue to work, or you can use a new URL to reach the new Support experience directly: https://www.ibm.com/mysupport [https://www.ibm.com/mysupport]\n\u00b7 Any existing PMRs will be automatically converted to \u201cCases\u201d in the new tool. Simply choose \u201ccases\u201d from the Information Server support landing page to see status or make updates\n\nWe know you may have other IBM products and those too will be migrating to this new experience over time. Please note that you may receive other communications notifying you of the plans for other IBM products. Your experience with Information Server support will continue to evolve as well. Among other improvements, we\u2019re incorporating IBM Watson technology, and providing a truly \u201cone-stop shop\u201d for Customer Support related information for Information Server.\n\nYou will know Information Server has migrated once it appears in the product selection area on the new Support Community.\nTo access the Community:\n1) Go to www.ibm.com/mysupport [http://www.ibm.com/mysupport%5Ch] , where you can select your product.\n2) For a personalized experience, you can login with your IBM ID.\nIf you do not have an IBM ID, go here to sign up for one https://www.ibm.com/account/us-en/signup/register.html [https://www.ibm.com/account/us-en/signup/register.html%5Ch].\nNote: You can also start in the legacy Service Request Tool (https://www-947.ibm.com/support/servicerequest/ [https://www-947.ibm.com/support/servicerequest/]), which will automatically redirected to the new experience.\n\nIf you are experiencing a problem with the portal (such as a login issue, etc.), we are here to help. You can submit your issue via our Support Community [https://www.ibm.com/mysupport/s/] by clicking \u201cEmail IBM Support\u201d, or emailing spe@us.ibm.com [spe@us.ibm.com] and we will get back to you as quickly as possible.\n\nThe Information Server Team", "logical_doc_id": 5, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q284", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Is it possible to use two different IBM\u00ae Rational\u00ae ClearCase\u00ae privileged user (clearcase_albd) accounts for accessing the VOB server?", "logical_doc_id": 6, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q284", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "You want to use two different albd accounts for accessing your VOB server.\n\nYou want to change the albd account and during the transition phase there will be two accounts present.\n\nReview the ClearCase Administrators Guide on the topic of The Rational ClearCase server process user [http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m1/index.jsp?topic=/com.ibm.rational.clearcase.cc_admin.doc/topics/c_access_usr_grp_privileged_ccspu.htm]for more information about this account.", "logical_doc_id": 6, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q284", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Yes this is possible.\n\nWhen using multiple ALBD user accounts, the key consideration is that the accounts need to be as close to identical as possible as described below.\n\nKey Considerations\nIf the VOBs are on a UNIX\u00ae/Linux\u00ae server, then the Microsoft\u00ae Windows\u00ae albd accounts need to map over to the same VOB-owner account that is using Samba or TAS. If for some reason this is not possible, see Note 3 below.\n\nReview the ClearCase Administrators Guide on the topic of Mapping the Rational ClearCase server process user [http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m1/index.jsp?topic=/com.ibm.rational.clearcase.cc_admin.doc/topics/t_pcnfssmb_smb_samba_mapccspu.htm] for more information.\nThe albd accounts must be members of the same groups. Especially the \"ClearCase Server Process Group,\" also known as the \"ClearCase\" or \"ClearCase Administrators' group.\"\n\nTwo common use cases for multiple albd accounts\n 1. Security policies require ALL accounts to change their passwords every \"n\" days, including service accounts.\n\nIn this case, the albd account is \"rotated\" every \"n-7\" days from a workstation logged in with domain administration rights. This can be done using a simple script.\n\nDISCLAIMER:\n All source code and/or binaries attached to this document are referred to here as \"the Program\". IBM is not providing program services of any kind for the Program. IBM is providing the Program on an \"AS IS\" basis without warranty of any kind. IBM WILL NOT BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM, OR ITS RESELLER, HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.\n\nfor /f \"delims=:\" %%x in ('cleartool lsclient -host {registry server} -type all ^| findstr \"Windows\"') do sc \\\\%%x config albd obj= {new_account} password= {new_acct_password} & sc \\\\%%x stop albd & sc \\\\%%x start albd\n\nNote 1: The spaces after \"obj=\" and \"password=\" are significant and will cause the command to error if they are excluded.\n\nNote 2: This script makes no allowance for machines that are not currently active. A \"production-ready\" script would include the ability to account for this and also keep track of which ClearCase hosts have had their albd account \"rotated\" in order to avoid the problem.\n Refer to the sc Windows on-line help for the \"sc qc\" command for more information on how to verify the account information for a service.", "logical_doc_id": 6, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q284", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Review the ClearCase Command Reference Guide on the topic of lsclients [http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m1/index.jsp?topic=/com.ibm.rational.clearcase.cc_ref.doc/topics/ct_lsclients.htm](cleartool man lsclients) for more information.\n\nThe old albd account would then be manually locked out until such time as the password rotation deadline approaches again.\n\n2. Different albd accounts for central VOB/view servers and end-user workstations. This is primarily done to prevent albd account issues (account lockouts, etc) on the albd account from impacting the VOB servers themselves.\n\nNote 3: In an interop configuration, the ALBD account that is in use on client hosts needs to have this minimum level of access rights:\nRead information from the VOBs source pools. This is sufficient for normal ClearCase operations like checkin and checkout.\nWrite to the VOBs cleartext pools, This is needed to allow cleartext construction, and file opens will fail (intermittently, with little apparent pattern) if one or more of the albd accounts does not have the necessary access rights.\nWrite to the VOBs derived object pools. This is to permit Derived Object promotion to view storage as part of the wink-in process.", "logical_doc_id": 6, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q284", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#Methods for changing the albd password [http://www.ibm.com/support/docview.wss?uid=swg21146207]\nVerify that clearcase_albd is in the ClearCase group [http://www.ibm.com/support/docview.wss?uid=swg21150347]\nUse of a non-VOB-owner account for TAS or Samba access [http://www.ibm.com/support/docview.wss?uid=swg21150254]", "logical_doc_id": 6, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q308", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This list features the most requested documents as well as those identified as valuable in helping answer your questions related to IBM BigFix family of products. The list will be updated periodically to reflect new trends and issues.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q308", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "List of featured documents for IBM BigFix:\n\nFeatured Documents\n\nEssential:\nIBM BigFix Support Center [http://www-01.ibm.com/support/docview.wss?uid=swg21624185]\nIBM BigFix Documentation [http://www-01.ibm.com/support/docview.wss?uid=swg21964132]\n\nCommon problems and solutions: * How do I clear the IBM BigFix Console cache? (1505993) [http://www-01.ibm.com/support/docview.wss?uid=swg21505993]\nWhat do the action status messages mean? (1505986) [http://www-01.ibm.com/support/docview.wss?uid=swg21505986]\nHow do I troubleshoot Fixlet actions? (1505932) [http://www-01.ibm.com/support/docview.wss?uid=swg21505932]\nCan I automatically assign a TEM Client a particular relay at installation time? (1505838) [http://www-01.ibm.com/support/docview.wss?uid=swg21505838]\nHow do I use TEM with a proxy? (1505994) [http://www-01.ibm.com/support/docview.wss?uid=swg21505994]\nWhat do the winsock error numbers in the TEM Client logs mean? (1505977) [http://www-01.ibm.com/support/docview.wss?uid=swg21505977]\nCan the SQL Server database exist on a separate computer from the TEM Server? [http://www-01.ibm.com/support/docview.wss?uid=swg21505841] (1505841)\nHow can I tell if I have gathered the latest Fixlet messages that have been published by Tivoli Endpoint Manager? (1505823) [http://www-01.ibm.com/support/docview.wss?uid=swg21505823]\nComputers grayed out in the console (1505813) [http://www-01.ibm.com/support/docview.wss?uid=swg21505813]\nWhy do my TEM Clients report \"\" for every action I take? (1505835) [http://www-01.ibm.com/support/docview.wss?uid=swg21505835]\nPreventing Send Refresh abuse in a large deployment [http://www-01.ibm.com/support/docview.wss?uid=swg21688336]\nWhy do some TEM Clients have not reported or unknown for a computer name or other properties? [http://www-01.ibm.com/support/docview.wss?uid=swg21505948]\n\nSystem/Network Requirements: * BigFix Server System Requirements [http://www-01.ibm.com/support/docview.wss?uid=swg21505691]\nBigFix Console System Requirements [http://www-01.ibm.com/support/docview.wss?uid=swg21505693]\nBigFix Platform Support Policy [http://www-01.ibm.com/support/docview.wss?uid=swg21570458]\nBigFix Network Traffic Guide [https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli%20Endpoint%20Manager/page/Network%20Traffic%20Guide?lang=en]\n\nIf you were unable not able to find a solution on this page to the problem you are experiencing, you also could: * Further search for a solution via the IBM BigFix Support Portal [https://support.podc.sl.edst.ibm.com/support/home/product/Q055780Z86547U43/IBM_BigFix_family]\nSearch for solutions on the BigFix Forum [https://forum.bigfix.com/]\nVisit the BigFix DeveloperWorks Wiki [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Endpoint+Manager/page/Home]\nAccess BigFix Documentation [http://www-01.ibm.com/support/docview.wss?uid=swg21964132]\nSee additional resources on the IBM BigFix Support Center [http://www-01.ibm.com/support/docview.wss?uid=swg21624185]\n\nIn the event you are unable to find a solution or work around your issue, you can open a PMR with L2 Bigfix Support, see: What information do I include when I open a PMR with IBM BigFix Support? (1505708) [http://www-01.ibm.com/support/docview.wss?uid=swg21505708]\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q308", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Domino 9.0.1\n Notes 9.0.1 64 bit (Mac), Notes 9.0.1 IF8 64 bit (Mac)\n\n1. Open a mail database in which a problematic html mail is\n encoded as quoted-printable.\n\n2. Open the problematic document.\n\nNote: You will find three lines with three bullet points under\n a section title as follows:\n\nex)\n\n(Section Number). Section Title\n (bullet point) Sentence 1\n (bullet point) Sentence 2\n (bullet point) Sentence 3\n\n3. Hit on \"Reply with history only\" button.\n\nYou will find only the sentence 1 is truncated.\n\nex)\n (Section Number). Section Title\n (bullet point) Sentence 2\n (bullet point) Sentence 3", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q308", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "-Reply with Internet-Style History.\nUse IBM notes on windows platform.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q308", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "This regression was introduced by ICU upgrade from 3.4.1 to\n 49.1. In ICU_ccSTRnNextExt, we first translate the string\n from LMBCS to Unicode, there is no problem in this step, after\n that, we call ICU RuleBasedBreakIterator (abbr. rbbi) to get\n the next break of the string, but here has a bug, when the\n hard return (i.e. 0x00) is behind some specific characters, it\n will be skipped by mistake in Japan locale.\n\nMy solution is:\n In the logic of searching break when rbbi goes through each\n unicode character, I added a check, if current one is hard\n return (i.e. 0x00), then I deem it as a break.\n\nThis fix is\n in ICU code, the mechanism of checking break is a little\n complicated, it may cost us much time if we want to understand\n the details of why the hard return does not work behind these\n special characters in Janpan locale. My solution is simple and\n straighforward.\n\nICAA Notes client team has tested my fix on\n both Mac and Window for SPR #TITHAGFAXH and #TITHAFJ8DR. The\n root cause of this SPR is the same as these 2 SPRs.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q308", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This regression was introduced by ICU upgrade from 3.4.1 to\n 49.1. In ICU_ccSTRnNextExt, we first translate the string\n from LMBCS to Unicode, there is no problem in this step, after\n that, we call ICU RuleBasedBreakIterator (abbr. rbbi) to get\n the next break of the string, but here has a bug, when the\n hard return (i.e. 0x00) is behind some specific characters, it\n will be skipped by mistake in Japan locale.\n\nMy solution is:\n In the logic of searching break when rbbi goes through each\n unicode character, I added a check, if current one is hard\n return (i.e. 0x00), then I deem it as a break.\n\nThis fix is\n in ICU code, the mechanism of checking break is a little\n complicated, it may cost us much time if we want to understand\n the details of why the hard return does not work behind these\n special characters in Janpan locale. My solution is simple and\n straighforward.\n\nICAA Notes client team has tested my fix on\n both Mac and Window for SPR #TITHAGFAXH and #TITHAFJ8DR. The\n root cause of this SPR is the same as these 2 SPRs.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q308", "section_id": 4, "heading": "COMMENTS", "parent": null, "text": "This APAR is associated with SPR# HHIEALLGQ3.\n This regression was introduced by ICU upgrade from 3.4.1 to\n 49.1. In ICU_ccSTRnNextExt, we first translate the string\n from LMBCS to Unicode, there is no problem in this step, after\n that, we call ICU RuleBasedBreakIterator (abbr. rbbi) to get\n the next break of the string, but here has a bug, when the\n hard return (i.e. 0x00) is behind some specific characters, it\n will be skipped by mistake in Japan locale.\n\nMy solution is:\n In the logic of searching break when rbbi goes through each\n unicode character, I added a check, if current one is hard\n return (i.e. 0x00), then I deem it as a break.\n\nThis fix is\n in ICU code, the mechanism of checking break is a little\n complicated, it may cost us much time if we want to understand\n the details of why the hard return does not work behind these\n special characters in Janpan locale. My solution is simple and\n straighforward.\n\nICAA Notes client team has tested my fix on\n both Mac and Window for SPR #TITHAGFAXH and #TITHAFJ8DR. The\n root cause of this SPR is the same as these 2 SPRs.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q308", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n LO92133\nREPORTED COMPONENT NAME\n NOTES CLIENT\nREPORTED COMPONENT ID\n 5724E6255\nREPORTED RELEASE\n 901\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2017-04-20\nCLOSED DATE\n 2017-06-02\nLAST MODIFIED DATE\n 2017-06-02\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q308", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n NOTES CLIENT\nFIXED COMPONENT ID\n 5724E6255", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q308", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R901 PSN\n UP\n\nwste_webcast; WSTE; Support Technical Exchange; education; presentation; webcast; STEwebcastDocument; was; troubleshooting; troubleshoot; problem determination WEBCAST", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q308", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This session gives you the chance to ask questions about the Troubleshooting and Problem Determination aspect of the WebSphere Application Server. Topics include:\nAdministration\nSecurity\nServer hangs/crashes\nPerformance\nHTTP sessions\nDatabase connectivity issues\nWeb services", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q308", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Open Mic sessions are conducted in a question and answer format. The table below provides a time index (minutes:seconds) to the recording and describes the questions or topics discussed. You can fast forward to any question using the time index, a table containing the panel of experts is also included.\n\nTo play or download the audio of this Open Mic session, see the Audio Section of this document.\n\nOpen Mic session\n3 June 2009 - 11:00 a.m. - 12:00 p.m. EDT", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q308", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Time Questions asked 00:00 Silence 00:00 General introduction 02:30 Technical introduction 04:52 What tools are available to help troubleshoot WebSphere problems and what types of problems can be analyzed with these tools? 08:06 How do I troubleshoot an application server startup issue? 12:21 What best practices should I follow to avoid problems with database connection pooling, and how should I troubleshoot connection pool problems when they do occur? 18:05 How do we debug a node synchronization issue? 23:09 What tools are available to troubleshoot a Outofmemory (OOM) error in our environment? 25:15 I'm interested in application server hangs - what causes it and how to mitigate it? 29:19 With regard to node synchronization, if I understand correctly, node synchronization only synchronize configuration files under the config folder - what happens if my application code is out of sync and needs to be refreshed? How do I initiate synchronization from the Deployment Manager to the node? 34:51 I notice that if I have a database connection error, normally I see a hung thread. Once I fix the database, will the hung thread go away, or do I have to restart the app server to recover from that? 37:36 My application server crashes because of an application using a large amount of memory space (heap size). Is there any way we can reduce that space? 40:50 Is there a command we can run from command line to find out what is the heap memory usage? 42:10 What is the difference between the aged time-out that can be set in a data source connection pool, and the WebSphere Transaction time-out? 45:57 I have a few commands from my WebSphere Application Server that is taking a long time to execute. How do I enable tracing to see what is going on within my application server and where the bottleneck is? 50:47 What is the overhead for creating multiple core groups? 55:05 We installed WAS Binary basically on file system, and we noticed a pretty big degradation when going from SAN to NAS, even when we are just performing a basic wsadmin command. Is that normal? If not, what steps should I take to start collecting data that can lead to the resolution of the problem?", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q308", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "58:15 Does WebSphere Application Server care about what underlying storage system it is on, be it LAN, SAN, local disks? 60:54 Closing remarks 61:28 End of Call\nPanel of experts: Vikram Thommandru WebSphere Application Server L2 Support Ajit Jariwala WebSphere Application Server L2 Support David P Tiler WebSphere Application Server L2 Support Kumaran Ayyakutti WebSphere Application Server L2 Support Partha S Momidi WebSphere Application Server L2 Support Paul Bullis WebSphere Application Server L2 Support Ajay Bhalodia WebSphere Application Server L2 Support Ramakrishna Boggarapu WebSphere Application Server L2 Support\nPRESENTATION\n[http://www.ibm.com/i/v16/icons/weblecture.gif]WSTE-06032009-OpenMic-WASTroubleshootingProblemDetermination-Momidi.pdf [/support/docview.wss?uid=swg27015668&aid=2] [/support/docview.wss?uid=swg27015668&aid=1]", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q308", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "[http://www.ibm.com/i/v14/icons/sout.gif] Get Adobe Reader [http://www.adobe.com/products/acrobat/readstep2.html] to view PDF\n\nGroup Chat Transcript\n\nThe transcript of the group chat area for this Open Mic session is attached below. Throughout the presentation replay, you may hear the presenters posting additional resources and links to the group chat area. Please refer to the transcript below for these information:\n\nWSTE-06032009-OpenMic-WASTroubleshootingProblemDetermination-Momidi-Transcript-GroupChat.txt [/support/docview.wss?uid=swg27015668&aid=4] [/support/docview.wss?uid=swg27015668&aid=3]\n\nTips: For best viewing, right-click and select Save As to store the transcript on your local computer, and then open the transcript with a text reader.\n\nAUDIO\n[http://www.ibm.com/i/v16/icons/aud.gif]Click on Download Audio [ftp://public.dhe.ibm.com/software/websphere/techexchange/Jun-03-2009-Momidi.mp3] to play the recording of this conference call (MP3 format). Right-click and select Save As to store the file on your local computer for later playback. Remember that you can fast forward to any question using the time index.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q308", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "WebSphere Support Technical Exchange [http://www.ibm.com/software/websphere/webcast]", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q308", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "In general, it is possible for the situation you describe (positive correlation between regressors with coefficients of opposite signs) to occur in regression. This is known as a suppressor effect in regression. The sign and magnitude of the regression coefficient for a predictor is a function of the partial correlation of the predictor with the dependent variable and the standard deviations of those variables. Suppose that dependent variable Y is predicted by W and X. The partial correlation of Y with X,\nr(XY.W) is the correlation of X and Y with the effect of W partialled out. This partial correlation squared is the proportion of the variance of Y that is associated with X but not associated with W.\n\nr(XY.W) = [r(XY) - r(XW)*r(WY)]/ [sqrt(1-r(XW)**2)*sqrt(1-r(WY)**2)] .\n\nNote that the denominator of this formula will always be positive. If all 3 correlations in the numerator are positive, but the product of r(XW) and r(WY) is larger than r(XY), then the numerator of the formula will be negative. If r(XY) is close to 0 and the other correlations are large, then X and Y may have a substantial negative partial correlation, despite having a small positive zero-order (nonpartialled) correlation.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q308", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our AMOS forum is Live! [https://developer.ibm.com/answers/search.html?f=&type=question&redirect=search%2Fsearch&sort=relevance&q=%2B[amos]]\n\nHISTORICAL NUMBER\n 41839", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q308", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Author's note: In this response, although I refer to covariates in the plural form, the principles discussed apply as well to models having only a single covariate.\n\nTo get the classical repeated measures ANCOVA results for repeated measures with constant covariates --like those modeled in Winer (1971)-- you'll have to run two GLM models. Run the first model with the covariates, but only report the between-subjects portion of that analysis. Run the second model without the covariates, but only report the within-subjects (WS) portion of that model.\n\nIf you only run one model that includes the covariates, the covariates appear in the WS portion of the model as interactions with the WS factor. This is not the same as partialling the covariates from the WS factor; it is what it looks like --a set of interaction terms. This is the way other so-called GLM programs (e.g., SAS and SYSTAT) handle covariates in repeated measures models, but that doesn't necessarily mean that it's what you want to do. If you want to run Winer's model, then use the two-model approach described in the previous paragraph.\n\nIf you choose to run Winer's model, you would do well to examine the WS portion of the output from the model that includes the covariate. A significant interaction between a covariate and a WS factor indicates that the slope of the covariate is not the same across levels of the WS factor. This is a violation of the homogeneity of slopes (HOS) assumption in ANCOVA. As such, it invalidates the use of ANCOVA in modeling your data.\n\nFinally, there are two alternative ways to estimate Winer's model in SPSS. First, you can run the model using commands in the older SPSS MANOVA program. Second, you can run the model in SPSS MIXED. For a worked example of how to model Winer's (1971; p. 803) example in MIXED, see Resolution 22273. Both MANOVA and MIXED adopt Winer's convention. A constant covariate is partialled from the between-subjects effects, but it is neither partialled from nor does it interact with the WS effects.\n\n___________________", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q308", "section_id": 1, "heading": "References", "parent": null, "text": "Winer, B. J. (1971). Statistical principles in experimental design (2nd Ed.). New York: McGraw-Hill.\n\nWiner, B. J., Brown, D. R. & Michels, K. M. (1991). Statistical principles in experimental design (3rd Ed.). New York: McGraw-Hill.", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q308", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\n\nHISTORICAL NUMBER\n 22133", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q242", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "DIRECT LINKS TO FIXES\nbpm.8570.cf2017.03.delta.repository [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8570.cf2017.03.delta.repository&source=SAR]\nDownloading IBM Business Process Manager V8.5.7 Cumulative Fix 2017.03 [http://www-01.ibm.com/support/docview.wss?uid=swg24043252]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q242", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When you create a business object variable in the main track and\n later create a new track in which you make changes to the\n business object variable, like adding a new parameter or\n removing some of the existing parameters, you notice that these\n changes are not reflected in the new track when you debug a\n client-side human service that contains the modified business\n object variable.\n\nPRODUCTS AFFECTED:\n IBM Business Process Manager (BPM) Advanced\n IBM BPM Standard\n IBM BPM Express", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q242", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Make the track that you're working on the default track.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q242", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "No additional information is available.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q242", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A fix will be included in IBM BPM V8.5.7 cumulative fix 2017.03\n that ensures the updated business object is used while you debug\n a client-side human service in a new track.\n\nTo determine whether the cumulative fix is available and\n download it if it is, complete the following steps on Fix\n Central:\n\n1. On the Select product tab, select WebSphere as the product\n group, IBM Business Process Manager with your edition from the\n WebSphere options, All as the installed version, and All as the\n platform, and then click Continue.\n 2. In the Text field, enter \"cumulative fix\", and click\n Continue.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q242", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR57253\nREPORTED COMPONENT NAME\n BPM STANDARD\nREPORTED COMPONENT ID\n 5725C9500\nREPORTED RELEASE\n 857\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2017-01-12\nCLOSED DATE\n 2017-01-12\nLAST MODIFIED DATE\n 2017-04-26\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q242", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM STANDARD\nFIXED COMPONENT ID\n 5725C9500", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q242", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R857 PSY\n UP\n\nDIRECT LINKS TO FIXES\n8.5.7.0-WS-WBM-IFJR54678 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Monitor&fixids=8.5.7.0-WS-WBM-IFJR54678&source=SAR]\n8.5.6.0-WS-WBM-IFJR54678 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Monitor&fixids=8.5.6.0-WS-WBM-IFJR54678&source=SAR]\n8.5.5.0-WS-WBM-IFJR54678 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Monitor&fixids=8.5.5.0-WS-WBM-IFJR54678&source=SAR]\n8.0.1.3-WS-BSPACE-IFJR56078 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.0.1.3-WS-BSPACE-IFJR56078&source=SAR]\n7.5.1.2-WS-BSPACE-IFJR54678 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=7.5.1.2-WS-BSPACE-IFJR54678&source=SAR]\n8.5.6.1-WS-BPM-IFJR54678 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.5.6.1-WS-BPM-IFJR54678&source=SAR]\n8.0.1.3-WS-BSPACE-IFJR54678 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.0.1.3-WS-BSPACE-IFJR54678&source=SAR]\n8.5.0.2-WS-BPM-IFJR54678 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.5.0.2-WS-BPM-IFJR54678&source=SAR]\n8.5.5.0-WS-BPM-IFJR54678 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.5.5.0-WS-BPM-IFJR54678&source=SAR]\n8.5.6.2-WS-BPM-IFJR54678 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.5.6.2-WS-BPM-IFJR54678&source=SAR]\nVersion 8.5 Refresh Pack 7 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24041575]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q242", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Multiple security vulnerabilities exist in IBM Business Space:\n\nCVE-2015-7400 - XML external entity expansion vulnerability\n CVE-2015-7407 - Server Side Request Forgery\n CVE-2015-7454 - Incomplete implementation of LOCKEDDOWN mode\n CVE-2014-8912 - Authorization bypass in Mashups\n\nYou cannot disable the user search function for non-privileged\n users.\n\nPRODUCTS AFFECTED\n IBM Business Process Manager (BPM) Advanced\n IBM BPM Standard\n IBM BPM Express", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q242", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "CVEID:\u00a0CVE-2015-7400\n DESCRIPTION:\u00a0IBM Business Process Manager is vulnerable to a\n denial of service, caused by an XML External Entity Injection\n (XXE) error when processing XML data. A remote authenticated\n attacker could exploit this vulnerability to consume all\n available CPU resources and cause a denial of service.\n CVSS Base Score: 4.3\n CVSS Temporal Score:\n See\u00a0https://exchange.xforce.ibmcloud.com/vulnerabilities/107105\n for the current score\n CVSS Environmental Score*: Undefined\n CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L)\n\nCVEID:\u00a0CVE-2015-7407\n DESCRIPTION:\u00a0IBM Mashups is vulnerable to Server Side Request\n Forgery. A remote attacker might use specially crafted HTTP\n requests to IBM Mashups in order to make the Mashups servers\n call other reachable HTTP services in its network.\n CVSS Base Score: 7.5\n CVSS Temporal Score:\n See\u00a0https://exchange.xforce.ibmcloud.com/vulnerabilities/107433\n for the current score\n CVSS Environmental Score*: Undefined\n CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N)\n\nCVEID:\u00a0CVE-2015-7454\n DESCRIPTION:\u00a0IBM Business Process Manager could allow an\n authenticated user to create pages and spaces that they should\n not have access to due to improper access restrictions.\n CVSS Base Score: 4.3\n CVSS Temporal Score:\n See\u00a0https://exchange.xforce.ibmcloud.com/vulnerabilities/108333\n for the current score\n CVSS Environmental Score*: Undefined\n CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N)\n\nOn BPM V7.5.1.2, this APAR also resolves:\n CVEID:\u00a0CVE-2014-8912\n DESCRIPTION:\u00a0IBM WebSphere Portal and other products could allow\n a remote attacker to obtain sensitive information, caused by the\n failure to restrict access to resources located within web\n applications. An attacker could exploit this vulnerability to\n obtain configuration data and other sensitive information.\n CVSS Base Score: 5\n CVSS Temporal Score:\n See\u00a0https://exchange.xforce.ibmcloud.com/vulnerabilities/99253\u00a0f\n or the current score\n CVSS Environmental Score*: Undefined\n CVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q242", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A fix is available for IBM BPM V7.5.1.2, V8.0.1.3, V8.5.0.2,\n V8.5.5.0, V8.5.6.0 cumulative fix 2, and IBM BPM V8.5.7.0\n CF2016.06 that removes these vulnerabilities. This fix also\n introduces a new feature whereby you can disable the user search\n capability.\n\n On Fix Central (http://www.ibm.com/support/fixcentral), search\n for JR54678:\n\n 1. Select IBM Business Process Manager with your edition from\n the product selector, the installed version to the fix pack\n level, and your platform, and then click Continue.\n 2. Select APAR or SPR, enter JR54678, and click Continue.\n\n When you download fix packages, ensure that you also download\n the readme file for each fix. Review each readme file for\n additional installation instructions and information about the\n fix.\n\n To enable this feature, configure the\n com.ibm.mashups.usersearch.blocked property as described in the\n readme file for your version of the product.\n\nTEMPORARY FIX\nNot applicable", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q242", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR54678\nREPORTED COMPONENT NAME\n BPM STANDARD\nREPORTED COMPONENT ID\n 5725C9500\nREPORTED RELEASE\n 850\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2015-11-10\nCLOSED DATE\n 2016-08-25\nLAST MODIFIED DATE\n 2016-08-25\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q242", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM STANDARD\nFIXED COMPONENT ID\n 5725C9500", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q242", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R751 PSY\n UP\nR801 PSY\n UP\nR850 PSY\n UP\nR855 PSY\n UP\nR856 PSY\n UP\nR857 PSY\n UP\n\nDIRECT LINKS TO FIXES\nbpm.8570.cf2016.09.delta.repository.2of2 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8570.cf2016.09.delta.repository.2of2&source=SAR]\nbpm.8570.cf2016.09.delta.repository.1of2 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8570.cf2016.09.delta.repository.1of2&source=SAR]\nDownloading IBM Business Process Manager V8.5.7 Cumulative Fix 2016.09 [http://www-01.ibm.com/support/docview.wss?uid=swg24042580]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q242", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "While you migrate from IBM Business Process Manager (BPM)\n V7.5.1.2 to IBM BPM V8.5.7, you might use a feature in the\n V7.5.1.2 saved search definition to change the column name\n for business data (which is exposed for the search). This\n feature was available only in V7.5.1.2. Since IBM BPM\n V8.x, the column name has based on the alias definition\n for the business variable. Nevertheless, the customized\n column name (as it is saved within a product XML file)\n works in the runtime environment of IBM Process Portal and\n it is shown on the Heritage Process Portal. However, the\n customized column name is not displayed on the Process\n Portal in IBM BPM V8.5.7.\n\nPRODUCTS AFFECTED\n IBM Business Process Manager (BPM) Advanced\n IBM BPM Standard\n IBM BPM Express", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q242", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "No additional information is available.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q242", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A fix will be included in IBM BPM V8.5.7.0 cumulative fix\n 2016.09 that uses the REST API that Heritage Process Portal used\n to get the missing data for Process Portal, shows the aliases\n defined in V7.5.1.2, and keeps the current behavior for saved\n search created on recent IBM BPM versions.\n\nWith this fix applied, the aliases that you created for business\n data column on saved searches are displayed; however, you cannot\n create new saved searches with aliases for business data\n columns. Plus, if you modify a saved search with aliases for\n business data columns, those aliases are overwritten with the\n name of the column.\n\nTo determine whether the cumulative fix is available and\n download it if it is, complete the following steps on Fix\n Central:\n\n1. On the Select product tab, select WebSphere as the product\n group, IBM Business Process Manager with your edition from the\n WebSphere options, All as the installed version, and All as the\n platform, and then click Continue.\n 2. In the Text field, enter \"cumulative fix?, and click\n Continue.\n\nWhen you download fix packages, ensure that you also download\n the readme file for each fix. Review each readme file for\n additional installation instructions and information about the\n fix.\n\nTEMPORARY FIX\nNot applicable.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q242", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR56456\nREPORTED COMPONENT NAME\n BPM STANDARD\nREPORTED COMPONENT ID\n 5725C9500\nREPORTED RELEASE\n 857\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-08-26\nCLOSED DATE\n 2016-09-19\nLAST MODIFIED DATE\n 2016-09-19\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q242", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM STANDARD\nFIXED COMPONENT ID\n 5725C9500", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q242", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R857 PSY\n UP\n\nISA data collection datacollection logs bpmdc isadc NEWS", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q242", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "The new data collector in IBM Business Process Manager V8.5 is designed for ease of use to gather some of the standard information that is needed to debug IBM Business Process Manager issues. This command-line tool can gather log file or configuration information and upload it to a Problem Management Record (PMR). This collector is also included in IBM Business Process Manager V8.0.1 Fix Pack 3.", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q242", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "The script gathers various product information, compresses it into a .zip file, and can optionally send the compressed file to IBM for a PMR. You can also use this tool to compress the data without sending it to IBM. The command is profile_root/bin/bpmdc\nThe profile_root variable is the base profile directory for the profile from which you want to get data.\n\nCommon Examples\n\nTo gather the logs and upload them to ECURep:\nC:/MyProfileDirectory/bin/bpmdc -PMR=12345.678.901 -uploadToIBM=yes\n\nTo gather the logs and config directory:\n\nC:/MyProfileDirectory/bin/bpmdc -PMR=12345.678.901 -uploadToIBM=yes -config=yes\n\nTo gather logs for installation issues:\n\nC:/MyProfileDirectory/bin/bpmdc -PMR=12345.678.901 -uploadToIBM=yes -type=Install\n\nTo gather 3 java cores from MyAppServer at 60 second intervals:\n\nC:/MyProfileDirectory/bin/bpmdc -PMR=12345.678.901 -uploadToIBM=yes -type=Dump -server=MyAppServer -soapport=8881 -user=admin -password=admin -dumptype=Thread -count=3 -interval=60", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q242", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Command Line Parameter Default Value Description PMR None This parameter is the 11-digit PMR number to which the data is associated. Use one of the following forms for this value: 12345.678.901 or \"12345,678,901\"\nNote: Comma characters can be an issue on the Microsoft Windows command-line if you do not surround the value with the double quote characters. uploadToIBM no This parameter specifies whether to upload the data to the IBM ECURep site for a particular PMR. You can set this value to yes or no. outputDirectory install_root/BPM/isadc This parameter specifies the path to the directory where the output collection .zip file will be stored. type General This parameter specifies which type of collection to run. The valid values are General, Install, or Dump(8.5.5). config no With a general collection, when you set this parameter to yes, the config directory is included. You can set this value to yes or no. help No values When you include this parameter with the command, a description of the command options is displayed. Server Connection options added in 8.5.5\nRequired for -type=Dump server No default This option specifies the server from which you wish to collect JVM dumps. soapport No default This option specifies the SOAP port for the server. user No default This option specifies the user with wsadmin access to the server to which you are connecting. password No default This option specifies the password for the user. Dump options added in 8.5.5\nAvailable for -type=Dump dumptype Thread This option specifies the type of Java\u2122 virtual machine (JVM) dump to trigger:\nThread - Javacore or thread dump.\nHeap - A Heap dump is generated.\nSystem - System dump is also generated and has JExtract run on it. count 1 This option specifies the number of JVM dumps to trigger during the collection. interval 0 This option specifies the interval in seconds to wait between JVM dumps.\n\nYou can run the command without any parameters, which results in the general collection being run and the logs directory is compressed into a .zip file.\n\nThe output file name has the following format: PMRnumber . type _ timeStampValue .zip\nIn V8.5.5 the format is changed to: PMRnumber . ProfileName_type _ timeStampValue .zip", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q242", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "The data gathered is based on the profile where the command is run. If it is run from the installation directory, then the default profile is used.\n\nNote: Be sure to run the command from the profile from which you wish to gather data.\n\nGeneral collection\nThe \"General\" collection gathers the following information: * Profile logs directory (profile_root/logs). The collected files include all of the server log files and trace under this profile directory.\nThe results of the versionInfo-maintenancePackages command.\n(Optionally) The profile config directory (profile_root/config). This directory is only collected when the -config=yes option is used.\n\nNote: The limitation with this collection is that it does not gather log files and trace if it goes to a custom directory outside of the Profile logs directory. It is not recommended that you change the log file locations from the default as it makes it more difficult for other people to find them.\n\nInstall collection\nThe \"Install\" collection gathers the following information that is listed in the Collect troubleshooting data for installation or upgrade problems with IBM Business Process Manager products [http://www.ibm.com/support/docview.wss?uid=swg21506937] document:\nAny temporary launchpad log files.\nInstallation Manager Data directory\nThe results of the versionInfo -maintenancePackages command\nInstallation logs directory\nProfile logs directory\nDatabase upgrade script log files\nVarious configuration files that are related to the installation process\n\nJVM Dump collection The \"Dump\" collection type triggers various JVM dumps on a target server within a profile prior to gathering the general collection and generated dumps.\n\nWith the provided server connection options, the command will connect to the server using the soapport to make a wsadmin connection with the user and password. Depending on the dump type, it will trigger various JVM dumps until the count amount is reached. The dumps are triggered a set number of seconds apart based on the interval that is set.", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q242", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "The collection will gather the general collection files like /logs and version information in addition to the dump files like Javacores, heap dumps and system dump .zip files.\nThread - This type will trigger Javacores or thread dumps to be produced for the JVM.\nHeap - This type will trigger heap dumps to be generated.\nSystem - This type will trigger system dumps to be generated. It will also run JExtract on the dump prior to the upload, which can take some time depending on the heap size.\n\nCommon usage The following list provides some common usage scenarios for this command:\nAfter an issue occurs, use the basic bpmdc command to compress the log files for the profile into a .zip file.\nRecreate your issue after setting a trace string using the administrative console [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/ttrb_entrrs.html] or wsadmin [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/txml_troubleshooting.html].\n Then, run the bpmdc command to collect the log files and send them to IBM.\nAfter opening a PMR, use bpmdc-PMR=PMRnumber-uploadToIBM=yes with the most relevant type options to upload data.\nIBM Support provides a specific command or set of commands to run for your environment that gets the needed data.\nIBM Support provides a traces string that needs to be gathered with the commands. With trace enabled, you recreate the issue or wait for a reoccurrence before running the provided commands to gather and upload the data to IBM.", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q242", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "A simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21644209]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard General AIX, Linux, Linux zSeries, Solaris, Windows 8.5 Business Integration IBM Business Process Manager Express General Linux, Linux zSeries, Windows 8.5\nPRODUCT ALIAS/SYNONYM\n BPM", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q242", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "You are having a problem with the IBM Master Data Management (MDM) products. You would like to know what information you must collect (MustGather) so that the IBM Master Data Management Support team can diagnose your problem. If you gather this documentation before contacting support, it will expedite the troubleshooting process and save you time.", "logical_doc_id": 5, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q242", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Collect the following troubleshooting data if you need help from IBM Master Data Management Support to resolve the problem\n\nDiagnosing the problem :\n\nStart the problem analysis:\nReview the SystemOut.log file at WAS_Home\u200b\u200b/profiles/\u200b\u200bprofile\u200b\u200b_\u200b\u200bname\u200b\u200b/\u200b\u200blogs\u200b\u200b/server\u200b\u200b_\u200b\u200bname and look for error messages that have been logged around the time stamp when the issue showed up.\nSearch the appropriate product support site from the following list for known problems using symptoms such as the message number and error codes:\n\nIBM Master Data Management Knowledge Center [https://www.ibm.com/support/knowledgecenter/SSWSR9]\nIBM Master Data Management Fix Central [https://www-945.ibm.com/support/fixcentral/]\nIBM Master Data Management developer Works [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W2c3ebf603f05_4460_8e8b_a26780b35b45]\nIBM Master Data Management dWAnswers [https://developer.ibm.com/answers/topics/mdm-migration/]", "logical_doc_id": 5, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q242", "section_id": 0, "heading": "RELATED INFORMATION", "parent": null, "text": "Data Collection Using the MDM Assistant Tool (MAT) [http://www-01.ibm.com/support/docview.wss?uid=swg21700482]\nMustGather: Installation issues for InfoSphere MDM11 an [http://www-01.ibm.com/support/docview.wss?uid=swg21967803]\nMustGather: Read first Performance data collection for [http://www-01.ibm.com/support/docview.wss?uid=swg21700894]\nSend data on FTP [http://www-05.ibm.com/de/support/ecurep/send.html]\nIBM Services [https://www-304.ibm.com/support/docview.wss?uid=swg21264419]\nIBM Software Compatibility Report [http://www-01.ibm.com/support/docview.wss?uid=swg27035486]", "logical_doc_id": 6, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q179", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere MQ 5.3 and IBM MQ 8 for HPE NonStop have addressed a vulnerability in which OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q179", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2017-3735 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3735]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate. An attacker could exploit this vulnerability to trigger an out-of-bounds read, resulting in an incorrect text display of the certificate.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/131047 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131047] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q179", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "All versions of WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q179", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "For MQ 5.3\n*\n*\n*\n*\n* https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=5.3.1.14&platform=HP+NonStop&function=all\nFor MQ 8\n*\nhere", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q179", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q179", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q179", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nThe 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.", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q179", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "OpenSSL vulnerabilities were disclosed on March 19, 2015 by the OpenSSL Project. OpenSSL is used by IBM WebSphere MQ Advanced Message Security for the IBM i platform, IBM WebSphere MQ HP-NSS and IBM WebSphere MQ Paho MQTT clients. IBM WebSphere MQ Advanced Message Security for the IBM i platform and IBM WebSphere MQ HP-NSS client have addressed the applicable CVEs.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q179", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2015-0209 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0209]\nDESCRIPTION: OpenSSL could allow a remote attacker to execute arbitrary code on the system, caused by a use-after-free error in the d2i_ECPrivateKey or EVP_PKCS82PKEY function. An attacker could exploit this vulnerability to corrupt memory and execute arbitrary code on the system and cause a denial of service.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101674 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101674] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:P/A:P)\n\nCVEID: CVE-2015-0286 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0286]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an error in the ASN1_TYPE_cmp function when attempting to compare ASN.1 boolean types. An attacker could exploit this vulnerability to crash any certificate verification operation and cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101666 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101666] 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-0289 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0289]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by the failure to properly handle missing outer ContentInfo by the PKCS#7 parsing code. An attacker could exploit this vulnerability using a malformed ASN.1-encoded PKCS#7 blob to trigger a NULL pointer dereference.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101669 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101669] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q179", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM WebSphere MQ Advanced Message Security for IBM i platform - V8.0.0.2 and earlier\n\nIBM WebSphere MQ Client for HP Integrity NonStop Server - V8.0.0.2 and earlier\n\nIBM Mobile Messaging and M2M Client Pack - Eclipse Paho MQTT C Client libraries for Linux & Windows platforms only", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q179", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "IBM WebSphere MQ Advanced Message Security for IBM i platform\n\nThe fix is provided in fix pack 8.0.0.3 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.2&platform=IBM+i&function=all]. or later.\n\nIBM WebSphere MQ HP-NSS client\n\nThe fix is provided in fix pack 8.0.0.3 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.2&platform=HP+NonStop&function=all] or later.", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q179", "section_id": 4, "heading": "WORKAROUNDS AND MITIGATIONS", "parent": null, "text": "Eclipse Paho MQTT C Client (Linux & Windows)\n\nThe C client libraries provided by the MA9B SupportPac can also be rebuilt from source and linked against OpenSSL 1.0.1m or later using the following instructions [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mm.tc.doc/tc10155_.htm].", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q179", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q179", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\nOpenSSL Project vulnerability website [http://www.openssl.org/news/vulnerabilities.html] (for detail on what versions are affected)\nOpenSSL Advisory on above listed CVEs [https://www.openssl.org/news/secadv_20150319.txt] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT\nNone.\n\nCHANGE HISTORY\n 22 June 2015 - Original Version Published.\nThe 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.", "logical_doc_id": 1, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q179", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21962359]", "logical_doc_id": 1, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q179", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "OpenSSL\u306e\u8106\u5f31\u6027\u306fOpenSSL Project\u306b\u3088\u3063\u30662015\u5e743\u670819\u65e5\u306b\u958b\u793a\u3055\u308c\u307e\u3057\u305f\u3002 OpenSSL\u306f\u3001IBM WebSphere MQ Advanced Message Security for the IBM i\u30d7\u30e9\u30c3\u30c8\u30d5\u30a9\u30fc\u30e0\u3001 IBM WebSphere MQ HP-NSS\u3068IBM WebSphere MQ Paho MQTT \u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u3067\u4f7f\u7528\u3055\u308c\u307e\u3059\u3002\nIBM WebSphere MQ Advanced Message Security for the IBM i \u3068IBM WebSphere MQ HP-NSS \u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u306f\u3001\u8a72\u5f53\u306eCVE\u306b\u5bfe\u51e6\u3057\u307e\u3057\u305f\u3002", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q179", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "\u8106\u5f31\u6027\u306e\u8a73\u7d30\uff1a\n\nCVEID: CVE-2015-0209 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0209]\nDESCRIPTION: OpenSSL could allow a remote attacker to execute arbitrary code on the system, caused by a use-after-free error in the d2i_ECPrivateKey or EVP_PKCS82PKEY function. An attacker could exploit this vulnerability to corrupt memory and execute arbitrary code on the system and cause a denial of service.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101674 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101674] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:P/A:P)\n\nCVEID: CVE-2015-0286 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0286]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an error in the ASN1_TYPE_cmp function when attempting to compare ASN.1 boolean types. An attacker could exploit this vulnerability to crash any certificate verification operation and cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101666 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101666] 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-0289 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0289]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by the failure to properly handle missing outer ContentInfo by the PKCS#7 parsing code. An attacker could exploit this vulnerability using a malformed ASN.1-encoded PKCS#7 blob to trigger a NULL pointer dereference.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101669 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101669] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q179", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "\u5f71\u97ff\u306e\u3042\u308b\u88fd\u54c1\u30fb\u30d0\u30fc\u30b8\u30e7\u30f3\uff1a\n\n\u6b21\u306e\u88fd\u54c1\u306b\u5f71\u97ff\u304c\u3042\u308a\u307e\u3059\u3002\n\n\u30fbIBM WebSphere MQ Advanced Message Security for IBM i platform - V8.0.0.2 \u672a\u6e80\u306e\u30ea\u30ea\u30fc \u30b9\n\n\u30fbIBM WebSphere MQ Client for HP Integrity NonStop Server - V8.0.0.2 \u672a\u6e80\u306e\u30ea\u30ea\u30fc \u30b9\n\n\u30fbIBM Mobile Messaging and M2M Client Pack - Eclipse Paho MQTT C Client libraries for Linux & Windows platforms only", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q179", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "\u4fee\u6b63\u7b56\uff1a\n\nIBM WebSphere MQ Advanced Message Security for IBM i platform\n\nFix Pack 8.0.0.3 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.2&platform=IBM+i&function=all] \u4ee5\u964d\u3092\u5c0e\u5165\u3057\u3066\u304f\u3060\u3055\u3044\u3002\n\nIBM WebSphere MQ HP-NSS client\n\nFix Pack 8.0.0.3 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.2&platform=HP+NonStop&function=all] \u4ee5\u964d\u3092\u5c0e\u5165\u3057\u3066\u304f\u3060\u3055\u3044\u3002", "logical_doc_id": 2, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q179", "section_id": 4, "heading": "WORKAROUNDS AND MITIGATIONS", "parent": null, "text": "\u56de\u907f\u7b56/\u8efd\u6e1b\u7b56\uff1a\n\nEclipse Paho MQTT C Client (Linux & Windows)\nMA9B\u30b5\u30dd\u30fc\u30c8\u30d1\u30c3\u30af MA9B \u304c\u63d0\u4f9b\u3059\u308bC\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u30e9\u30a4\u30d6\u30e9\u30ea\u306f\u3001\u30bd\u30fc\u30b9\u304b\u3089\u30ea\u30d3\u30eb\u30c9\u3068OpenSSL 1.0.1.m \u4ee5\u964d\u306b\u30ea\u30f3\u30af\u3067\u304d\u307e\u3059\u3002\u624b\u9806\u306f\u3001instructions [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mm.tc.doc/tc10155_.htm]\u3092\u53c2\u7167\u304f\u3060\u3055\u3044\u3002", "logical_doc_id": 2, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q179", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q179", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\n. \u53c2\u7167\u60c5\u5831\uff1a\n\nOpenSSL Project vulnerability website [http://www.openssl.org/news/vulnerabilities.html] (for detail on what versions are affected)\n\nOpenSSL Advisory on above listed CVEs [https://www.openssl.org/news/secadv_20150319.txt]\n\n[IBM\u30b5\u30a4\u30c8]\n\u3053\u306e\u6587\u66f8\u306f\u3001\u7c73\u56fd IBM \u793e\u306e\u8cc7\u6599\u3092\u7ffb\u8a33\u3057\u305f\u53c2\u8003\u6587\u66f8\u3067\u3059\u3002\u7ffb\u8a33\u5143\u306e\u6587\u66f8\u306f\u3001\u4ee5\u4e0b\u306e\u30ea\u30f3\u30af\u3088\u308a\u3054\u53c2\u7167\u304f\u3060\u3055\u3044\u3002\nSecurity Bulletin: Vulnerabilities in OpenSSL affect IBM WebSphere MQ Advanced Message Security for IBM i, IBM WebSphere MQ Client for HP-NSS [http://www.ibm.com/support/docview.wss?uid=swg21902519]\n\n\u516c\u958b\u6e08\u307f\u306e\u30d5\u30a3\u30c3\u30af\u30b9\u30d1\u30c3\u30af\u306b\u3064\u3044\u3066\u306f\u3001\u4ee5\u4e0b\u306e\u30b5\u30a4\u30c8\u3088\u308a\u3054\u5229\u7528\u3044\u305f\u3060\u3051\u307e\u3059\u3002\nRecommended fixes for WebSphere MQ [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\n\u30d5\u30a3\u30c3\u30af\u30b9\u30fb\u30d1\u30c3\u30af\u306e\u516c\u958b\u4e88\u5b9a\u306b\u3064\u3044\u3066\u306f\u3001\u4ee5\u4e0b\u306e\u30b5\u30a4\u30c8\u3088\u308a\u3054\u78ba\u8a8d\u3044\u305f\u3060\u3051\u307e\u3059\u3002\nWebSphere MQ planned maintenance release dates [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n[CVSS\u60c5\u5831]\n\u72ec\u7acb\u884c\u653f\u6cd5\u4eba \u60c5\u5831\u51e6\u7406\u63a8\u9032\u6a5f\u69cb: \u5171\u901a\u8106\u5f31\u6027\u8a55\u4fa1\u30b7\u30b9\u30c6\u30e0CVSS\u6982\u8aac [http://www.ipa.go.jp/security/vuln/CVSS.html]\nJVN iPedia: CVSS\u8a08\u7b97\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u65e5\u672c\u8a9e\u7248 [http://jvndb.jvn.jp/cvss/ja.html]", "logical_doc_id": 2, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q179", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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] . \u95a2\u9023\u60c5\u5831\uff1a\n.\n[\u304a\u554f\u5408\u305b\u5148]\n\u6280\u8853\u7684\u306a\u5185\u5bb9\u306b\u95a2\u3057\u3066\u3001\u30b5\u30fc\u30d3\u30b9\u5951\u7d04\u306e\u3042\u308b\u304a\u5ba2\u69d8\u306fIBM\u30b5\u30fc\u30d3\u30b9\u30fb\u30e9\u30a4\u30f3\u306b\u304a\u554f\u3044\u5408\u308f\u305b\u304f\u3060\u3055\u3044\u3002\nIBM \u30b5\u30fc\u30d3\u30b9\u30fb\u30e9\u30a4\u30f3 [http://www.ibm.com/jp/news/20070420001.html]\nThe 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\u95a2\u9023\u60c5\u5831\n An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21902519]", "logical_doc_id": 2, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q179", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "OpenSSL vulnerabilities were disclosed on September 22 and 26, 2016 by the OpenSSL Project. OpenSSL is used by IBM MQ Advanced Message Security on the IBM i platform only. IBM MQ Advanced Message Security has addressed the applicable CVEs.", "logical_doc_id": 3, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q179", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-2177 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2177]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by the incorrect use of pointer arithmetic for heap-buffer boundary checks. By leveraging unexpected malloc behavior, a remote attacker could exploit this vulnerability to trigger an integer overflow and cause the application to crash.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113890 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113890] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H)\n\nCVEID: CVE-2016-2178 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2178]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error in the DSA implementation that allows the following of a non-constant time codepath for certain operations. An attacker could exploit this vulnerability using a cache-timing attack to recover the private DSA key.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113889 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113889] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)", "logical_doc_id": 3, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q179", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM MQ V8\n\nMaintenance versions 8.0.0.0 through 8.0.0.5 are affected.\n\nIBM MQ V9\n\n9.0.0.0 only", "logical_doc_id": 3, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q179", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "IBM MQ V8\n\nApply fixpack 8.0.0.6 [http://www-01.ibm.com/support/docview.wss?uid=swg21995100]\n\nIBM MQ V9\n\nApply fixpack 9.0.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27048059]", "logical_doc_id": 3, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q179", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 3, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q179", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 3, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q179", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 13 March 2017: Original version published\n24 May 2017: Details for 9.0.0.1 added\nThe 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.", "logical_doc_id": 3, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q179", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg22000474]", "logical_doc_id": 3, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q179", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "OpenSSL vulnerabilities were disclosed on November 2, 2017 by the OpenSSL Project. OpenSSL is used by IBM SDK for Node.js. IBM SDK for Node.js has addressed the applicable CVEs.", "logical_doc_id": 4, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q179", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID:CVE-2017-3735 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3735]\nDescription:OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAdressFamily extension in an X.509 certificate. An attacker could exploit this vulnerability to trigger an out-of-bounds read, resulting in an incorrect text display of the certificate.\nCVSS Base Score: 4.3\nCVSS Temporal Score:https://exchange.xforce.ibmcloud.com/vulnerabilities/131047 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131047] for more information\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N)\n\nCVEID: CVE-2017-3736 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3736]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by a carry propagation flaw in the the x86_64 Montgomery squaring function bn_sqrx8x_internal(). An attacker with online access to an unpatched system could exploit this vulnerability to obtain information about the private key.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/134397 [https://exchange.xforce.ibmcloud.com/vulnerabilities/134397] for more information\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N)", "logical_doc_id": 4, "chunk_id": 32 }, { "doc_id": "techqa_DEV_Q179", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "These vulnerabilities affect IBM SDK for Node.js v4.8.5.0 and earlier releases.\nThese vulnerabilities affect IBM SDK for Node.js v6.11.5.0 and earlier releases.\nThese vulnerabilities affect IBM SDK for Node.js v8.9.0.0 and earlier releases.", "logical_doc_id": 4, "chunk_id": 33 }, { "doc_id": "techqa_DEV_Q179", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "The fixes for these vulnerabilities are included in IBM SDK for Node.js v4.8.6.0 and subsequent releases.\nThe fixes for these vulnerabilities are included in IBM SDK for Node.js v6.12.0.0 and subsequent releases.\nThe fixes for these vulnerabilities are included in IBM SDK for Node.js v8.9.3.0 and subsequent releases.\n\nIBM SDK for Node.js can be downloaded, subject to the terms of the developerWorks license, fromhere [http://www.ibm.com/developerworks/web/nodesdk/].\n\nIBM customers requiring an update for an SDK shipped with an IBM product should contactIBM support [http://www.ibm.com/support/], and/or refer to the appropriate product security bulletin.", "logical_doc_id": 4, "chunk_id": 34 }, { "doc_id": "techqa_DEV_Q179", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 4, "chunk_id": 35 }, { "doc_id": "techqa_DEV_Q179", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 4, "chunk_id": 36 }, { "doc_id": "techqa_DEV_Q179", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nNode.js 4.8.6 [https://nodejs.org/en/blog/release/v4.8.6/] Node.js 6.12.0 [https://nodejs.org/en/blog/release/v6.12.0/]\n\nNode.js 8.9.1 [https://nodejs.org/en/blog/release/v8.9.1/]\n\nCHANGE HISTORY\n December 22 2017: Original version published\nThe 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.", "logical_doc_id": 4, "chunk_id": 37 }, { "doc_id": "techqa_DEV_Q261", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "This issue is caused by specifying a \"Naming Context\" value in the Service Definition that spans multiple subparts of the directory. It is only an issue if the customer has multiple subdirectories configured in the Active Directory setup.\nFor example, if there were 2 subparts to the AD tree, \"CN=Administrators,DC=Acme,DC=com\", and \"DC=Users,DC=Acme,DC=com\". Then specifying a naming context of \"DC=Acme,DC=com\" would cause the issue.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q261", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Use an LDAP browser to connect to the ITIM LDAP server. Navigate to the AD profile definition. For example, if the root of ITIM is \"DC=COM\", go to:\nThen add a value to the multi-valued \"erproperties\" attribute:\nThen restart the ITIM server (or wait 10 minutes for the object profile cache to refresh).\n\nAnother way of correcting this would be to edit the ITIM data file containing the initial LDAP data contents, and then re-run \"ldapConfig\". While this may be simpler, note this will reload the ITIM LDAP data into the directory, and so will erase any customizations that have been done, such as ACI modifications, or form designer changes to standard forms.\n\nTo edit the ITIM LDAP data, edit file $ITIM/config/ldap/itimx.dsml2. Search for \"Service Profile Definition for AD Feed Source\". 30 lines after this should be the line \"\". After this line (which is actually line 1132 in the current version of this file), add the new line:\nShut down the ITIM server. Then open a command window, and \"cd\" to the $ITIM/bin/win directory, then run \"ldapConfig\". For example:\n*\nFollow prompts, with same values as used when ITIM was installed.\n\nThen restart the ITIM server.\n\nPRODUCT ALIAS/SYNONYM\n ITIM ISIM", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q261", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What is the maxsession.reloadcache attribute used for in Maximo 7.5?", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q261", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Q: What is the purpose of this attribute?\nA: It is the means of communicating the cache change among different servers in the used cluster\n\nQ: What areas are affected or related to reloadcache attribute?\n\nA: If a data dictionary entry is modified through the user action connecting to one server, the server updates its own cache, however needs to inform other servers that the cache needs to be reloaded. So, it puts the information on the other server's maxsession record to say \"this is what has been changed, update yourself\".\n\nIn other words, it is used to inform the other application servers in a system with multiple application servers(often in a cluster) that a change has been made to cached data and the application servers must reload that data.\n\nQ: When is Maximo going to use this reloaded cache?\n\nA: Each server has a type thread poking the applicable Maximo record and this way querying it's own record in maxsession..This method then ensures the thread is looking into this entry. By default this occurs once every 60 seconds and updates the server timestamp with the current date and time. If the reloadcache column is not null, then the listed caches are reloaded and the value zeroed out.\n\nNote!: Any Maximo cache will use this not just the data dictionary, e.g condition cache, maximodd, adminmode state, crontask/escalation definitions, properties, maxvars, autokey data and logging settings.\n\nQ: What is affected when you change the attribute type or length, as below example?\n\nalter table maxsession modify (reloadcache varchar2(2048));\nupdate maxattribute set length=2048 where objectname='MAXSESSION' and attributename='RELOADCACHE';\nupdate maxattributecfg set length=2048 where objectname='MAXSESSION' and attributename='RELOADCACHE';\n\nA: The above statement example is fine as all it will do is increasing the length. However if you make it smaller then there may not be room for a long list. Do not change the attribute type!\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Control Desk AIX, HP-UX 7.5 Systems and Asset Management Tivoli Asset Management for IT AIX, HP-UX, Linux, Solaris, Windows 7.5 Systems and Asset Management Tivoli Change and Configuration Management Database AIX, Linux, Windows, Solaris, HP-UX 7.5 Systems and Asset Management Tivoli Service Request Manager AIX, Linux, Solaris 7.5\n\nAIX SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q261", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Description:\n .\n Abstract: VPM-CV5 INTEROP: EACH TIME THE\n GEOMETRY IS OPENED AND SWICTHED TO\n DESIGN MODE ALL THE FILES ARE COPIED TO A\n LOCAL DIRECTORY UNDER CATTemp\n .\n Scenario:\n 1) Open a PSN graph\n 2) Select some CATParts and load them into CV5\n 3) If the work with cache system is checked the\n cgrs are created\n 4) Switch to design mode\n 5) The files loaded are copied to\n $CATTEMP/SelectiveLoadingCache\n 6) Close the window\n 7) All the files under\n $CATTEMP/SelectiveLoadingCache are deleted, the\n cgrs remain\n 8) If the same Parts are again loaded into CV5 the\n cgrs are used from the cache\n .\n Result:\n But when are switched to design mode the files are\n copied again into local directory.\n With CV4 and the cgr files, the timestamp is used\n to check if it is necesary to reload the files into the\n local directory. Why not with CV5 files?\n .\n .", "logical_doc_id": 2, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q261", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "VPM-CV5 INTEROP: EACH TIME THE GEOMETRY IS OPENED AND SWICTHED\n TO DESIGN MODE ALL THE FILES ARE COPIED TO A LOCAL DIRECTORY UN\n D\n Description:\n .\n Abstract: VPM-CV5 INTEROP: EACH TIME THE\n GEOMETRY IS OPENED AND SWICTHED TO\n DESIGN MODE ALL THE FILES ARE COPIED TO A\n LOCAL DIRECTORY UNDER CATTemp\n .\n Scenario:\n 1) Open a PSN graph\n 2) Select some CATParts and load them into CV5\n 3) If the work with cache system is checked the\n cgrs are created\n 4) Switch to design mode\n 5) The files loaded are copied to\n $CATTEMP/SelectiveLoadingCache\n 6) Close the window\n 7) All the files under\n $CATTEMP/SelectiveLoadingCache are deleted, the\n cgrs remain\n 8) If the same Parts are again loaded into CV5 the\n cgrs are used from the cache\n .\n Result:\n But when are switched to design mode the files are\n copied again into local directory.\n With CV4 and the cgr files, the timestamp is used\n to check if it is necesary to reload the files into the\n local directory. Why not with CV5 files?\n .\n .", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q261", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "THIS PROBLEM IS PERMANENT RESTRICTION IN\n CATIA.\n .\n Incident Diagnosis\n VPM-CV5 INTEROP: EACH TIME THE GEOMETRY IS\n OPENED AND SWICTHED TO DESIGN MODE ALL\n THE FILES ARE COPIED TO A LOCAL DIRECTORY\n UNDER CATTemp\n .\n Restriction Explanation\n The SelectiveLoadingCache is an internal cache\n used to support the selective loading of V5 design\n documents such as CATParts, CATDrawing...\n This means that when you open this document, you\n can load its contained data progessively when the\n data is needed by an application.\n This is the purpose of this cache. It is not meant to\n be a persistent cache, keeping the data after\n document closing.\n .\n By-Pass\n None\n .\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q261", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n HD46994\nREPORTED COMPONENT NAME\n CATIA V5 NT>XP\nREPORTED COMPONENT ID\n 569151000\nREPORTED RELEASE\n 515\nSTATUS\n CLOSED PRS\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2005-11-24\nCLOSED DATE\n 2005-12-15\nLAST MODIFIED DATE\n 2005-12-15\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q261", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24041819]\n8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]\n8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24043005]\n8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24042746]\n8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]\n8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http://www-01.ibm.com/support/docview.wss?uid=swg24044096]\n8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]\n8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q261", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "If base entry and name in repository is different and\n clearCache functionality is used with clearEntity mode then\n virtual member manager (VMM) still looks in the cache and gets\n the entity from the cache instead of fetching it from the LDAP\n server.", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q261", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of IBM WebSphere Application *\nServer V8.0 and V8.5 virtual member *\nmanager (VMM) *\n\nPROBLEM DESCRIPTION: Clear cache does not work if *\nclearEntity *\nmode is used. *\n\nRECOMMENDATION: *\n\nLDAP Clear cache functionality of VMM does not work when using\n clearEntity mode. Problems occur only if there is a different\n base entry used than the name in the repository entry.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q261", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This APAR fixes the issue. It clears the cache properly even if\n base entry is different than name in repository.\n\nThe fix for this APAR is currently targeted for inclusion in\n fix packs 8.0.0.13 and 8.5.5.9. Please refer to the\n Recommended Updates page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q261", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI47826\nREPORTED COMPONENT NAME\n WEBS APP SERV N\nREPORTED COMPONENT ID\n 5724H8800\nREPORTED RELEASE\n 800\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2015-08-28\nCLOSED DATE\n 2015-12-09\nLAST MODIFIED DATE\n 2015-12-09\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q261", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBS APP SERV N\nFIXED COMPONENT ID\n 5724H8800", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q261", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R800 PSY\n UP\nR850 PSY\n UP\n\nECMFeaturedDocument; CSEDocument; FeaturedDocument; featured documents; featured; top 10; top ten; popular; most popular; recommended; most requested; highlight; newsletter; Newsletter NEWSLETTER", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q261", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM\u00ae Atlas eDiscovery Process Management helps attorneys, paralegals and discovery directors efficiently manage a rigorous, highly defensible legal holds workflow.\n\nThis document features the most requested documents as well as those identified as valuable in helping answer your questions related to Atlas eDiscovery Process Management. The list will be updated periodically to reflect new trends and issues.", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q261", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "The content below was sent in the Support Newsletter for Atlas eDiscovery Process Manager on 16 Dec, 2015. If you would like to subscribe, see the instructions in the IBM Knowledge Collection: IBM Support Newsletters for Enterprise Content Management (ECM). [http://www-01.ibm.com/support/docview.wss?uid=swg27041952&acss=danl_708_web]\nThis document contains links (URLs) to Atlas eDiscovery Process Manager technical support documents and information that can help you get more value from your software. It is intended to help you to be proactive in your support and administration of Atlas eDiscovery Process Manager. This document includes:\nIn the Spotlight\nPlan\nEducation\n\nIn the Spotlight", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q261", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "1. How do we list Stewards and Discovery Delegates when we add custodians to a Collection Plan ? [http://www-01.ibm.com/support/docview.wss?uid=swg21967053&acss=danl_2644_web]\n This is due to a parameter setting in the component MATTER_EXCEPTIONS\n 2. Why do some users notice flicker in Internet Explorer v10 when using Atlas? [http://www-01.ibm.com/support/docview.wss?uid=swg21968534&acss=danl_2644_web]\n This is caused when you use the GPU Rendering option in Internet Explorer\n 3. Technical Support (TS) Chat available for some ECM Products [http://www.ibm.com/support/docview.wss?uid=swg27045851&acss=danl_2644_web]\n Technical Support (TS) Chat available for IBM FileNet Image Services, IBM Datacap, Case Foundation, and Case Manager\n 4. Get Connected to Enterprise Content Management (ECM) Support through Social Media [http://www.ibm.com/support/docview.wss?uid=swg21686616&acss=danl_2644_web]\n IBM ECM Support is now on LinkedIn, Facebook and Twitter. We invite you to Connect with us on LinkedIn, Like us on Facebook and/or Follow us on Twitter.\n 5. ECM End Of Service (EOS) Products [https://www.ibm.com/developerworks/community/blogs/f70916bb-0083-4dee-8297-84c8820ea35a/entry/ecm_end_of_service_products?lang=en&acss=danl_2644_web]\n IBM at times sets for software products an End Of Support (EOS) Date. Once set there is often time to either upgrade to the next revision level or switch to a new product. We would like our clients to be aware of EOS dates for products they use and make appropriate plans.\n 6. Featured Documents for Atlas eDiscovery Process Management [http://www-01.ibm.com/support/docview.wss?uid=swg27046183&acss=danl_2644_web]\n This document features the most requested documents as well as those identified as valuable in helping answer your questions related to Atlas eDiscovery Process Management. The list will be updated periodically to reflect new trends and issues.\n 7. IBM Support Easy OnBoarding tool [https://support-easy-onboarding.mybluemix.net]\n This is a fun, engaging, educational tool that assists our clients to sign up for 5 basic client self-assist tools/services: obtain an IBM ID, sign up for My Notifications, access the IBM Support Portal, register for Service Request, and register for Passport Advantage. CATHY, our Client Agent to Help You, will walk you through the steps to sign up. Earn tokens for every step you complete and play the game at the end!\n\nBack to top\n\nPlan", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q261", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "1. Relax in Fountains of ECM Knowledge...Let's keep it flowing [https://www.ibm.com/developerworks/community/blogs/f70916bb-0083-4dee-8297-84c8820ea35a/entry/relax_in_fountains_of_ecm_knowledge_let_s_keep_it_flowing?lang=en&acss=danl_2644_web]\n We need feedback from our valued clients so that we can keep you updated on the information you need!\n 2. \">Best Practices for Releasing Custodians from Hold in Atlas 6.0.3.x [ Data Design -> Add-ons Database Connections Global Configuration -> Administration -> Database Connections External Repositories Global Configuration -> Administration -> External Repositories Fixed Content Devices Global Configuration -> Administration -> Fixed Content Devices Marking Sets Global Configuration -> Data Design -> Marking Sets Object Stores Global Configuration -> Object Stores PE Connection Points Global Configuration -> Object Stores-> -> Administration -> Workflow System -> Connection Points PE Region Ids Global Configuration -> Object Stores-> -> Administration -> Workflow System -> Connection Points Replication Groups Global Configuration -> Administration -> Replication Groups Sites Global Configuration -> Administration -> Sites -> Properties -> IBM Search Server Global Configuration -> Administration -> Text Search Servers -> Properties -> Content Cache Global Configuration -> Administration -> Content Cache Areas === Object Stores Level ===\n\nFEM ACCE Change Preprocessor Actions Events, Actions, Processes -> Change Preprocessor Actions Choice Lists Data Design -> Choice Lists Document Class Data Design -> Classes Document Classification Action Events, Actions, Processes -> Document Classification Action Document Lifecycles -> Document Lifecycle Action Events, Actions, Processes -> Document Lifecycle Action Document Lifecycles -> Document Lifecycle Policies Events, Actions, Processes -> Document Lifecycle Policies Events -> Event Action Events, Actions, Processes -> Event Action Events -> Subscriptions Events, Actions, Processes -> Subscriptions Export Manifest N/A Index Areas Administrative -> Index Areas Other Classes Data Design -> Classes -> Other Classes Property Templates Data Design -> Property Templates Publishing Queue Administrative -> Publishing Queue Replication Queue Administrative -> Replication Queue Root Folder Browse -> Root Folder Saved Searches Search Search Results Search Security Policies Administrative -> Security Policies Storage Areas Administrative -> Storage Areas Storage Policies Administrative -> Storage Policies Unfiled Documents Browse -> Unfiled Documents Workflow Definitions Events, Actions, Processes -> Workflow Definitions Index Job Management (Right-click ObjectStore -> All Tasks -> Index Job Management) Administrative -> Index Job Manager", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q209", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The P8 server logs will show the following message:\n\nCBR FNRCE0010E - ERROR CSEDispatcherForSPI:Master serial=91 running with error , with message The value given for a property or list element lies outside the permitted range or value set, or exceeds the maximum length allowed. Failed to decode the password property value, most likely because the property value was not UTF-8 encoded, then encrypted.\\ncom.filenet.api.exception.EngineRuntimeException: FNRCE0010E: E_BAD_VALUE: The value given for a property or list element lies outside the permitted range or value set, or exceeds the maximum length allowed. Failed to decode the password property value, most likely because the property value was not UTF-8 encoded, then encrypted.\\n at com.filenet.engine.util.Encryption.masterDecryptDecode(Encryption.java:151)\\n at com.filenet.engine.util.Encryption.masterDecryptDecodeString(Encryption.java:170)\\n at\n,,,,\\nCaused by: com.filenet.api.exception.EngineRuntimeException: FNRCE0066E: E_UNEXPECTED_EXCEPTION: An unexpected exception occurred. The unexpected exception is chained to this exception. Message was: General exception while encrypting or decrypting data\\n", "logical_doc_id": 2, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q209", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The FileNet Content Engine Content Search Services authentication token in ACCE does not match the token configured for the IBM Content Search Services server.", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q209", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "1. To find the authentication token configTool printToken \u2013configPath path\n\nFor example:\nC:\\Program Files\\IBM\\Content Search Services\\CSS Server\\bin>configTool printToken -configPath \"C:\\ProgramFiles\\IBM\\Content Search Services\\CSS Server\\config\"\n\n2. Access the properties for the server in the ACCE:\n\ni In the domain navigation pane, click the Text Search Servers folder.\nii In the details pane, click the name of the IBM\u00ae Content Search Services server.\niii Click the General tab and in the Authentication token field, enter the correct token value.", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q209", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "TAB NAVIGATION\n1. Learning more [http://www.ibm.com/support/docview.wss?rs=3278&uid=swg27010422]\n2. Troubleshooting [http://www.ibm.com/support/docview.wss?rs=3278&uid=swg21674966] - selected tab,\n3. Collecting data [http://www.ibm.com/support/docview.wss?rs=3278&uid=swg21674818]\n\nTroubleshooting steps to help resolve commo n FileNet Content Engine Administrative Console for Content Engine (ACCE) issues.\n\n1. Clear the browser cache and retry.\n2. Confirm browser version is supported in the Hardware and Software requirement guide ( http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/prereqsForProduct?deliverableId=1313767706422 [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/prereqsForProduct?deliverableId=1313767706422]) and any notes that apply.\n3. Review the commonly encountered issues below:\n\"Administrative Console for Content Platform Engine (ACCE) that runs on JBoss may intermittently encounter exceptions\" - http://www.ibm.com/support/docview.wss?uid=swg21673327 [http://www.ibm.com/support/docview.wss?uid=swg21673327]\n\"Plugin resource not found\" error occurs when using Administration Console for Content Platform Engine (ACCE)\" - http://www-01.ibm.com/support/docview.wss?uid=swg21662794 [http://www-01.ibm.com/support/docview.wss?uid=swg21662794]\n\"Unable to log on to Administration Console for Content Platform Engine after upgrading to Content Platform Engine 5.2.\" - http://www.ibm.com/support/docview.wss?uid=swg21662806 [http://www.ibm.com/support/docview.wss?uid=swg21662806]\n\"Object doesn't support this property or method\" error occurs when trying to log on to Administration Console for Content Engine (ACCE) - http://www-01.ibm.com/support/docview.wss?uid=swg21661518 [http://www-01.ibm.com/support/docview.wss?uid=swg21661518]\n\"Cannot login to ACCE\" - http://www-01.ibm.com/support/docview.wss?uid=swg21656346 [http://www-01.ibm.com/support/docview.wss?uid=swg21656346]\n\"Unable to create a Domain in FileNet Content engine using ACCE\" - http://www-01.ibm.com/support/docview.wss?uid=swg21645831 [http://www-01.ibm.com/support/docview.wss?uid=swg21645831]\n\"Error when connecting to Enterprise Manager or Administrative Console for Content Engine\" - http://www-01.ibm.com/support/docview.wss?uid=swg21663222 [http://www-01.ibm.com/support/docview.wss?uid=swg21663222]\n\"ACCE configuration panel can not start due to Java 2 Security Permission error\" - [http://www-01.ibm.com/support/docview.wss?uid=swg21631682] http://www-01.ibm.com/support/docview.wss?uid=swg21631682 [http://www-01.ibm.com/support/docview.wss?uid=swg21631682]\n\"Administrative Console for Content Engine (ACCE) fails to load with the following error \"SyntaxError: illegal character ?\"\" - http://www.ibm.com/support/docview.wss?uid=swg21961579 [http://www.ibm.com/support/docview.wss?uid=swg21961579]\n\nWhat to do Next?\nIf the preceding troubleshooting steps did not solve your problem, see the MustGather: FileNet Content Engine Administrative Console for Content Engine (ACCE) problems to continue the investigation.\n\n SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 3, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q209", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Administration Console for Content Platform Engine (ACCE) does\n not handle replication mapping of the same CE class to multiple\n Image Service (IS) external repositories correctly.\n\nConfiguration steps:\nCreate same IS class and properties name on the 2 IS servers\n (ISClass1, ISProp1, ISProp2, etc).\nOn CE side via FileNet Enterprise Manager (FEM) or ACCE, add 2\n Fix Content Devices (FCD) to connect to the 2 Image Services\n (IS) servers\nAdd the 2 External repositories to connect to each of the FCD\n above (IS_REP1, IS_REP2)\nAdd a CE class (CEClass1) to map to both of the above 2\n external repositories\n\nSteps to Reproduce:\n\nIssue 1: Class mappings with same CE class show the same\n External name in ACCE- OS - Replication Mapping tab.\n\nFor class mappings added via FEM with same CE class added\n previously, if you view it via ACCE- OS - Replication Mapping\n tab, it shows both with CE class mapping property with the same\n External name.\n FEM reflects the correct External Repository name when you go\n into the configuration of each class mapping 2 class mappings to\n same CE class with different external respository which were\n added via FEM.\n Click on each of the Class mapping each class and BOTH show the\n same External Repository.\n It does not show one for each of the repository.\n\nIssue 2: Duplicate property names appear in the CE mapping\n class.\n\nIf you click on ACCE - OS - Replication mapping tab - select a\n CE class mapping -Replication Property Mapping tab - you will\n see all the property names are duplicated. It displays the\n property mapping for both class mappings for same CE class when\n it should only display the property mapping for the class\n mapping selected. Removing the mapping can remove the wrong\n property mapping for the other class mapping.\n FEM does not show duplicate properties.", "logical_doc_id": 4, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q209", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Use FileNet Enterprise Manager.", "logical_doc_id": 4, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q209", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nCustomers using 5.2.0.3-P8CPE-IF006 or 5.2.1.0-P8CPE and *\nprior ACCE to manage replication mappings with multiple *\nImage Services. *\n\nPROBLEM DESCRIPTION: *\nAdministration Console for Content Platform Engine (ACCE) *\ndoes not handle replication mapping of the same CE class to *\nmultiple Image Service (IS) external repositories correctly. *\nThe class mapping to the second IS repository may not be *\ncreated. The property mappings associated with a class *\nmapping might be listed under the wrong class mapping. *\n\nRECOMMENDATION: *\nUpgrade to 5.2.0.4-P8CPE-FP004 or 5.2.1.2-P8CPE-FP002 or *\nlater. *", "logical_doc_id": 4, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q209", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fixed in 5.2.0.4-P8CPE-FP004 and 5.2.1.2-P8CPE-FP002 and higher.\n When there are multiple IS external repositories with same set\n of external classes, ACCE should allow multiple class mappings\n between the same CPE class and the same IS class in different IS\n repository. The associated property mappings should be listed\n correctly.\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q209", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PJ43019\nREPORTED COMPONENT NAME\n CONTENT ENGINE\nREPORTED COMPONENT ID\n 5724R8101\nREPORTED RELEASE\n 520\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2015-02-24\nCLOSED DATE\n 2015-06-15\nLAST MODIFIED DATE\n 2015-06-15\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q209", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n CONTENT ENGINE\nFIXED COMPONENT ID\n 5724R8101", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q209", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R520 PSY\n UP\nR521 PSY\n UP", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q217", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "In general when accessing SPSS Modeler or SPSS Statistics software via a remote desktop or terminal services session a network license is required. In some configurations where the Windows host limits the number of active sessions to 1 a local license may still operate, but we cannot assist with attempts to achieve such a configuration.\n\nPlease see the documentation for your version of SPSS Modeler or SPSS Statistics for details on how to setup and use a network/concurrent license. You will most likely also need to contact your local IBM Sales office to purchase a network license (they are not interchangeable with site licenses and may be priced differently).\n\nIBM contact information can be found at http://www.ibm.com/planetwide [http://www.ibm.com/planetwide]", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q217", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Licensing forum is Live! [https://developer.ibm.com/answers/topics/spsslicensing.html]\n\nHISTORICAL NUMBER\n 84539\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q217", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "I have Modeler 15FP3 and Statistics 21FP2 with a\n network/concurrent user license. I have licensed Statistics in\n Modeler as instructed. When I use the Statistics node, I get\n 'IBM SPSS Statistics Model Node error: can't find valid license\n in\n C:\\Program Files\\IBM\\SPSS\\Statistics\\21\"", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q217", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Request a license for Statistics 22 if you don't have one, and\n upgrade to Statistics 22.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q217", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nThis affects all users of IBM SPSS Modeler. *\n\nPROBLEM DESCRIPTION: *\nCANNOT USE STATISTICS NODES WITH A CONCURRENT USER LICENSE *\nIN *\nMODELER 15FP3 AND STATISTICS 21 *\n\nRECOMMENDATION: *\nPlease upgrade to IBM SPSS Modeler 17.0. *", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q217", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI23830\nREPORTED COMPONENT NAME\n SPSS MODELER\nREPORTED COMPONENT ID\n 5725A64MD\nREPORTED RELEASE\n F00\nSTATUS\n CLOSED FIN\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-08-13\nCLOSED DATE\n 2015-03-12\nLAST MODIFIED DATE\n 2015-03-12\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q217", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "RF00 PSY\n UP\nRG00 PSY\n UP", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q217", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What are the different types of licenses available for Modeler\\Clementine and SPSS? What is the difference between single user, site and network license? What type of license should I choose? Also, which work with stand alone computers and which for terminal services?", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q217", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "LICENSE TYPES:\nConcurrent User (network) Installation (also called Network Licenses)\nThis is applicable to Modeler\\Clementine Client and SPSS Client installations only.\n\nConcurrent user licenses, (also known as network licenses), allow you to install Modeler\\Clementine or SPSS on any number of machines but control the number of users that can start the application at the same time. This offers you more flexibility than named-user licenses (also known as single-user licenses, see below) in multiple-user environments. Only a concurrent user license can be used with terminal services.\nSingle user/Site license Installation\nThis is applicable to Modeler\\Clementine & SPSS Client, Modeler 14.0 Server & SPSS 18 Server and below or Modeler\\Clementine & SPSS Batch, AMOS and SPSS Text Analysis for Surveys.\n\nNamed-user licenses (also known as single-user licenses) allow you to install Modeler\\Clementine or SPSS on a fixed number of machines to be used by given user(s). You will most likely have a different license code for each user (machine). A single-user code can be applied to two separate machines for use by the same user (i.e. one work machine, one home machine).\n\nA site license is used predominantly by universities. If you have a site license you will have one license/authorization code that can be applied to multiple Modeler\\Clementine Client installations (the number of installations that you can apply a site license authorization code to is determined by the number of users you have purchased. Once you have installed it on this many machines the code will not be accepted by subsequent installs).", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q217", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Licensing forum is Live! [https://developer.ibm.com/answers/topics/spsslicensing.html]\n\nHISTORICAL NUMBER\n 62148", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q217", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "How do I add a new license to the SPSS (Sentinel RMS) License Manager? [http://www.ibm.com/support/docview.wss?uid=swg21989508]\n\nHow do I migrate my SPSS (Sentinel RMS) License Manager client(s) to a new host? [http://www.ibm.com/support/docview.wss?uid=swg21987631]\n\nHow do I move/migrate my License Manager to a new host? [http://www.ibm.com/support/docview.wss?uid=swg21489714]\n\nInstalling and licensing the SPSS Concurrent License Manager in a virtual environment. [http://www.ibm.com/support/docview.wss?uid=swg21677004]\n\nHow do I perform a version upgrade on a solo (non-redundant) License Manager installed on a Windows host? [http://www.ibm.com/support/docview.wss?uid=swg21989211]\n\nHow do I analyze a License Manager usage log file? [http://www.ibm.com/support/docview.wss?uid=swg21986875]\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Business Analytics SPSS Modeler Business Analytics SPSS Statistics Business Analytics SPSS Text Analytics for Surveys", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q217", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Please visit this link:\n\nhttps://youtu.be/t4p1LB5c-y4 [https://youtu.be/t4p1LB5c-y4]\n\nto view a short video which will walk you through the steps to install IBM SPSS Concurrent Licensing Tools.", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q217", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\nNeed more help? Our Licensing forum is Live! [https://developer.ibm.com/answers/topics/spsslicensing.html]\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Statistics Business Analytics SPSS Modeler", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q300", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Using the KIS.LOCK table as an example, the TEPS log shows the following error:\n\nKFWITM217E Request error: [IBM][CLI Driver][DB2/LINUXX8664] SQL0204N \"KIS.LOCK\" is an undefined name. SQLSTATE=42704, GENERIC SQLSTATE: 42S02, ERR: -204 SQLExecDirect rc=-1: SQL_ERROR\n\nFollowed by these lines stating that it cannot allocate new pages in the tablespace when it tries to create the KIS.LOCK table (the table name could be any table name):\n(5183C8E3.0013-1D:ctsqlaccessodbc.cpp,347,\"CTSQLEvalODBC::IssueStatementWorker::run\") TEPS(486): CREATE TABLE KIS.LOCK ( hostname VARCHAR(254) NOT NULL, tool VARCHAR(10) NOT NULL, pid INT NOT NULL DEFAULT 1, timestamp VARCHAR(32) NOT NULL, username VARCHAR(254) NOT NULL, PRIMARY KEY(hostname))\n\n(5183C8E4.0000-1D:ctsqlconnectionodbc.cpp,148,\"CTSQLEvalODBC::Connection::sqlErrorCheckMsg\") [IBM][CLI Driver][DB2/LINUXX8664] SQL0289N Unable to allocate new pages in table space \"USERSPACE1\". SQLSTATE=57011, GENERIC SQLSTATE: 57011, ERR: -289", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q300", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The USERSPACE1 tablespace is defined as automatic storage, but when you view it using the \"db2 list tablespaces show detail\" command after connecting to the database it shows Free pages = 0 as shown below.\n\ndb2 connect to WAREHOUS user itmuser using \n\ndb2 list tablespaces show detail\nTablespace ID = 2\nName = USERSPACE1\nType = Database managed space\nContents = All permanent data. Large table\nspace.\nState = 0x0000\nDetailed explanation:\nNormal\nTotal pages = 15392\nUseable pages = 15360\nUsed pages = 15360\nFree pages = 0\nHigh water mark (pages) = 15360\nPage size (bytes) = 4096\nExtent size (pages) = 32\nPrefetch size (pages) = 32\nNumber of containers = 1\n\nThe database is out of file space to allocate new storage for tables, so more space needs to be allocated for the database.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q300", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "If the tablespace is set up to use automatic storage then it means the file system is full. Check your file system space to see if it is full. You should be able to use the \"df -k\" command on Unix.\n\nIf the database storage is located on a logical volume you could add more file space.\n\nHere is a link specifying how to add a separate path for additional storage:\nhttp://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=%2Fcom.ibm.db2.luw.admin.dbobj.doc%2Fdoc%2Ft0023143.html [http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=%2Fcom.ibm.db2.luw.admin.dbobj.doc%2Fdoc%2Ft0023143.html]\n\nAlso if normal reorgs and runstats have not been done on the tables in the database, it could be an issue where the space is not getting reclaimed by the operating system. Here is a link showing giving an example about how to set up regular reorgs and runstats:\nhttp://www-304.ibm.com/support/docview.wss?uid=swg21444174 [http://www-304.ibm.com/support/docview.wss?uid=swg21444174]\n\nSo basically the answer here is to increase the space available to the database.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q300", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Following reasons apply:\nIf the DMS or automatic storage tablespaces are not created in DB2 Version 9.7 or later, as the \"Reclaimable Storage\" is not available in tablespaces created in earlier versions(V9.1/V9.5) of the DB2 product.\nTrying to alter a SMS tablespace as this feature is not supported on SMS tablespaces.\n\nExample testcase on a TEMPSPACE1 SMS tablespace.\n*\nDB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL1763N Invalid ALTER TABLESPACE statement for table space \"TEMPSPACE1\" due to reason \"11\" SQLSTATE=429BC", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q300", "section_id": 1, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "MON_GET_TABLESPACE table function and RECLAIMABLE_SPACE_ENABLED monitor element can be used to identify whether the tablespace is enabled for reclaimable storage or not. Example:\ndb2 \"SELECT varchar(tbsp_name, 30) as tbsp_name, tbsp_type, RECLAIMABLE_SPACE_ENABLED FROM TABLE(MON_GET_TABLESPACE('',-2))\"\n\nSnippet of the output:\n\nTBSP_NAME TBSP_TYPE RECLAIMABLE_SPACE_ENABLED\n---------------- ----------- -------------------------\nSYSCATSPACE DMS 1\nTEMPSPACE1 SMS 0\nUSERSPACE1 DMS 1\n\nIf the RECLAIMABLE_SPACE_ENABLED monitor element returns a value of 1, then the tablespace is enabled for reclaimable storage. Otherwise, it returns a value of 0.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q300", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To use the reclaimable storage feature, make sure to create the DMS or automatic storage tablespaces in DB2 Version 9.7 or later. Example testcase on SYSCATSPACE DMS tablespace which has reclaimable storage enabled.\n*\n*\nNote:\nTablespaces migrated from DB2 V9.1/V9.5 to V9.7 won't get upgraded directly to use the reclaimable storage feature. RELATED INFORMATION\n Reclaimable storage [http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.dbobj.doc/doc/c0055392.html]", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q300", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How does DB2 perform LOB Space Allocation and Management", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q300", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "DB2 stores most row data in fixed size (4KB, 8KB, 16KB, 32KB) pages. This data is referenced by queries via bufferpool access, i.e. it is read from disk into bufferpool memory to be worked on.\nLOB (large object) data is handled differently. A LOB (CLOB - character large object, BLOB \u2013 binary large object, or DBCLOB - double byte large object) is stored outside regular row based storage. A LOB can be up to 2GB in size (1GB for a logged LOB). The necessity of handling large amounts of data of potentially very disparate sizes efficiently is what drives the LOB storage mechanism.\n\nThere is a descriptor in the regular row data that points to the actual LOB data itself. The size of this descriptor varies from 60 to 312 bytes, depending on the size defined for the LOB in the definition of the table. The actual size of the LOB data is also included in the descriptor. If a row's LOB is defined with an inline size, then, if the entire LOB will fit, it will be inlined into the regular data page. If the LOB data is larger than the inline size, none of the LOB will be inlined. If the actual LOB size is smaller than the descriptor size, it will be implicitly inlined, even if no inlining is defined in the table definition.\n\nAll LOB data that does not get inlined as described above will be stored as follows.\n\nLOB data has two components, LBA and LB. The LBA object contains all space allocation information. The LB object contains the actual LOB data. If the tablespace is defined as using System Managed Storage (SMS), then these two objects can be seen as separate files, with .LBA and .LB file extensions. Data in the LBA object passes through the bufferpool. Data in the LB object is not buffered by DB2. Some memory buffering of LB data can be obtained by utilizing the OS file system cache.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q300", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "The LOB space storage uses what is called a Buddy Space mechanism. There are two types of buddy space - Super Buddy Space (SBS) and Regular Buddy Space (RBS). SBSes control allocation of large segments of data, from 256k to 64m bytes. An RBS controls allocation of segments of size 1k (the minimum LOB allocation unit) to 128KB. There are multiple RBSes per SBS.\n\nIn an empty table, there is just one SBS. We then insert a 50KB LOB. As the LOB is inserted, the SBS gets subdivided (always by a factor of 2) until, eventually, we have an RBS segment of a size that can completely contain the LOB, i.e. the RBS size will be 64K. Since we always subdivide by factors of 2, at this stage we will have the occupied segment, and a free buddy segment of 64k, as well as free buddy segments back up the chain at the 128KB (RBS), 256KB(SBS), 512KB(SBS) size, and so on. DB2 maintains a hint of where space of a particular size is located, and so another insert of, say, 60KB, would go straight to the buddy segment of the first insert. If we do a third insert (55KB this time), we have no pointer to free space of the right size, so we will look for a segment of the next largest size, i.e. 128KB, and we will subdivide that into 2 64KB segments, and use one of them. The other (its buddy) will be free space.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q300", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "The space remaining in a segment beyond the user data is not used, i.e. for our first insert of 50KB, the last 14KB is not used. There is a COMPACT option which can be specified for LOB columns. The effect of specifying this option is to subdivide the LOB data into smaller pieces to derive a closer 'fit' with the buddy segment sizes. For example, for our first insert of 50KB of data, with COMPACT we would divide data into a 32KB, 16KB and 2KB segment, and would thereby not 'waste' any space at all. However, these pieces will not necessarily be contiguous and may even be widely separated, and so retrieval of the data may suffer. Update operations are also affected by COMPACT. Generally with LOBs, an update will result in a delete followed by an insert. This will always be the case when COMPACT is specified. However, in the case of our first 50KB LOB insert, a subsequent operation that appended, say, 12KB of data would result in an in-place update of the existing segment, and result in less 'waste' at the end of the segment. Use of COMPACT is not recommended in most scenarios.\n\nA delete of a LOB will put its buddy space into a delete-pending state. After commit takes place the segment is eligible to move to a free state. If the buddy space of the freed segment is also free, the two will be combined to form a single segment of the next higher size, for example two 64KB buddy spaces would become a 128KB buddy.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q300", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "As already mentioned, DB2 maintains hints of where the next piece of space of a particular size is located. These hints can be maintained by both insert and delete operations. They will also indicate when there is no free space, i.e. a new insert needs to extend the tablespace. This hinting mechanism is however just a single indication. If we assume a situation where some delete jobs have created some free buddy space segments of various sizes in the \u201cmiddle\u201d of the table, the hints will be pointing to this newly freed area. When multiple concurrent inserts try to use this space, only one will get it. The other inserts will have to search for free space. The space search could be very lengthy \u2013 the next free buddy space segment of the right size could be a long way away. Also, when there are concurrent inserters in this state, referencing the allocation pages themselves could suffer from contention issues. Once new free space is found, the hint mechanism will be reestablished, with the likely result that inserts will become quick once again. This kind of situation can lead to erratic insert times \u2013 normally quick, but occasionally long, or even very long.\n\nAdvice is to :\nInline the LOBs if possible.\nIncrease the bufferpool to a FIXED size so space management pages can be\nkept in the bufferpool to avoid physical IO to disk in order to have them in the bufferpool.\nMake sure that Operating System Filesystem Cache is enabled for LOBs Tablespaces.\nREORG using LONGLOBDATA, or use admin_move_table, or copy to another table with LOAD from Cursor and then rename.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q300", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Some further details relating to LOB Objects:\nAn update of a LOB is mostly a delete/insert of a LOB.\nLOB Allocation Pages(LOBA) are read into the bufferpool assigned to the LONG part of the table.\nAPPEND ON does not work for LOBs, it only works for REGULAR data.\nDB2MAXFSCRSEARCH can only be used for REGULAR data to limit\nthe number of space management pages DB2 reads before appending data at the end of the table. It does not work for LOBs. There is no 'exit procedure' in the insert LOB algorithm.\nThere are no stats available on how deorganized/fragmented a LOB table\nis. No reorgchck for LOBs either. db2 inspect does give some indication\non the number of space management pages.\n\nThe insert LOB algorithm tries to accommodate LOBS of any size.\n\nThis means the number of space management pages to be read in order to find free space depends on :\nThe size of the LOB to be inserted. The larger the LOB the more space management pages need to be read in bufferpool memory.\nHow unorganised the table is due to lots of deletes and updates that have been one on the table. The more unorganised the more pages need to be read in order to find free space.\n\nAIX FIXES ARE AVAILABLE\nDB2 Version 9.5 Fix Pack 3b for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24022591]\nDB2 Version 9.5 Fix Pack 4 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24023213]\nDB2 Version 9.5 Fix Pack 3a for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24021838]\nDB2 Version 9.5 Fix Pack 3 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24021563]\nDB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24024215]\nDB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24025421]\nDB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24027747]\nDB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24028731]\nDB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24030302]\nDB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24032087]\nDB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24033308]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q300", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The AUTORESIZE clause are not valid for\n system managed space (SMS) table spaces or for database managed\n space\n (DMS) table spaces that are defined to use raw device\n containers. However db2look was generating AUTORESIZE clause\n for SMS tablespaces, hence this has to be corrected.\n n/a\n n/a", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q300", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Users Affected: All\n Problem Description:\n The AUTORESIZE clause are not valid for\n system managed space (SMS) table spaces or for database managed\n space\n (DMS) table spaces that are defined to use raw device\n containers. However db2look was generating AUTORESIZE clause\n for SMS tablespaces, hence this has to be corrected.\n Problem Summary:\n The AUTORESIZE clause are not valid for\n system managed space (SMS) table spaces or for database managed\n space\n (DMS) table spaces that are defined to use raw device\n containers. However db2look was generating AUTORESIZE clause\n for SMS tablespaces, hence this has to be corrected.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q300", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "\"Problem was first fixed in Version 9.5 Fix Pack 3\"\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q300", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IZ35488\nREPORTED COMPONENT NAME\n DB2 UDB ESE AIX\nREPORTED COMPONENT ID\n 5765F4100\nREPORTED RELEASE\n 950\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2008-10-22\nCLOSED DATE\n 2009-04-20\nLAST MODIFIED DATE\n 2009-04-20\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q300", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n DB2 UDB ESE AIX\nFIXED COMPONENT ID\n 5765F4100", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q300", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R950 PSY\n UP\n\nAIX FIXES ARE AVAILABLE\nDB2 Version 9.5 Fix Pack 4 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24023213]\nDB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24024215]\nDB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24025421]\nDB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24027747]\nDB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24028731]\nDB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24030302]\nDB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24032087]\nDB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24033308]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q300", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "If the root of the automatic storage path does not have enough\n free file system space, and an attempt is made to extend the\n tablespace, DB2 will incorrectly report SQL0968C \"file system\n full\" without checking the amount of free file system space\n in the full path where the new container should be created.\n .\n For example, say that the following automatic storage path\n is defined (output taken from a database snapshot):\n .\n Automatic storage path = /home/db2inst1\n .\n An attempt is made to extend the tablespace. A new container\n is about to be created in the following path consisting of\n the automatic storage path, instance name, node number,\n database name, and tablespace id:\n .\n /home/db2inst1/db2inst1/NODE0000/SAMPLE/T0000004/\n .\n However, DB2 will not check the amount of free disk space\n in this long path where the container is going to be created.\n Instead, only \"/home/db2inst1\" is considered. This is an\n incorrect assumption since \"/home/db2inst1\" can contain\n mounted filesystems, for example \"/home/db2inst1/db2inst1\",\n which can have a sufficient amount of free disk space.\n .\n DB2 should always check the target path where the new\n container is going to be created, not just the root of it.\n If the target path does not exist, DB2 will check the file\n system information of the last subdirectory in the existing\n path. For example, if only\n .\n /home/db2inst1/db2inst1/NODE0000/\n .\n exists, DB2 will check the amount of free space in this\n directory.", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q300", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Ensure the root of the automatic storage path has a sufficient\n amount of free file system space.", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q300", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "see APAR description", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q300", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Problem first fixed in DB2 UDB 9.5 FixPak 4.\n\nTEMPORARY FIX\nsee APAR text", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q300", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IZ15060\nREPORTED COMPONENT NAME\n DB2 UDB ESE AIX\nREPORTED COMPONENT ID\n 5765F4100\nREPORTED RELEASE\n 950\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2008-02-07\nCLOSED DATE\n 2009-06-05\nLAST MODIFIED DATE\n 2009-06-05\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n IZ15048 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ15048]\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\nENGN_SQB", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q300", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n DB2 UDB ESE AIX\nFIXED COMPONENT ID\n 5765F4100", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q300", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R950 PSN\n UP", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q052", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "How will I know if the default certificate has expired?\n\nWhen the certificate has expired, users will receive a \"Secure Connection Failed\" message in their browser instead of the APM Login Page.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q052", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "To maintain valid UI certificates in your upgraded APM V8.1.4 server installations that are still using the default out of the box certificates, the existing keystore and truststore files must be replaced with the files that are attached at the end of this technote. These new keystore and truststore files contain certificates that are set to expire in March, 2028.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q052", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "The following new keystore files that are attached at the end of this technote contain certificates that will expire in 2028:\n\n1. updated.8.1.4.key.jks (password: apmpass)\n2. updated.8.1.4.trust.jks (password: ccmR0cKs!)\n\nHow do I know if I am using the default certificate files in an upgraded environment?\n\n1. Identify an upgraded V8.1.4 default UI shared keystore by verifying the following:\nThe password is apmpass\nThere is only a single certificate listed\nAlias is \"default\"\nExpires 4/21/19\nSignature Algorithm is SHA256withRSA\nOwner: CN=liberty, O=IBM, C=US and Issuer: CN=liberty, O=IBM, C=US\n\n1.1. Navigate to the APMUI keystore directory by issuing the following command::\n\n# cd /opt/ibm/wlp/usr/shared/resources/security\n\n1.2. List the certificates in the key store by issuing the following command:\n\n# /opt/ibm/java/jre/bin/keytool -v -list -keystore ./key.jks\n\nEnter the keystore password: apmpass\n\n1.3. Verify the output:\n\nKeystore type: jks\nKeystore provider: IBMJCE\nYour keystore contains 1 entry\nAlias name: default\nCreation date: Apr 21, 2016\nEntry type: keyEntry\nCertificate chain length: 1\nCertificate[1]:\nOwner: CN=liberty, O=IBM, C=US\nIssuer: CN=liberty, O=IBM, C=US\nSerial number: 191bd82a\nValid from: 4/21/16 1:09 PM until: 4/21/19 1:09 PM\nCertificate fingerprints:\nMD5: 06:FB:FA:F0:68:49:65:38:6D:FB:B3:2D:8A:24:5D:2B\nSHA1: A2:39:41:40:F8:D5:3A:6D:80:62:D5:D5:6A:27:EB:9B:3A:35:B2:DA\nSHA256: 85:B9:FB:97:98:69:B8:DF:2A:B0:38:C6:3B:C7:87:CA:71:21:CA:CE:DE:D0:09:57:FF:AF:B7:EB:E8:77:FD:6D\nSignature algorithm name: SHA256withRSA\nVersion: 3\nExtensions:\n#1: ObjectId: 2.5.29.14 Criticality=false\nSubjectKeyIdentifier [\nKeyIdentifier [\n0000: 1b 97 38 19 52 43 34 f6 2a 0e 7f a4 22 db 07 80 ..8.RC4.........\n0010: 41 6e 47 a5 AnG.\n]\n]\n\n2. Identify an upgraded V8.1.4 default truststore by verifying the following:\nThe password is ccmR0cKs!\nThere is only a single certificate listed\nAlias is \"oidc\"\nExpires 4/21/19\nSignature Algorithm is SHA256withRSA\nOwner: CN=liberty, O=IBM,C=US and Issuer: CN=liberty, O=IBM, C=US\nSerial number matches the certificate in the key.jks file above\n\n2.1. Navigate to the keystore directory by issuing the following command::\n\n# cd /opt/ibm/wlp/usr/shared/resources/security\n\n2.2. List the certificates in the key store by issuing the following command:\n\n# /opt/ibm/java/jre/bin/keytool -v -list -keystore ./trust.jks\n\nEnter keystore password: ccmR0cKs!\n\n2.3. Verify the output:", "logical_doc_id": 2, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q052", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Keystore type: jks\nKeystore provider: IBMJCE\nYour keystore contains 1 entry\nAlias name: oidc\nCreation date: Apr 6, 2018\nEntry type: trustedCertEntry\nOwner: CN=liberty, O=IBM, C=US\nIssuer: CN=liberty, O=IBM, C=US\nSerial number: 191bd82a\nValid from: 4/21/16 1:09 PM until: 4/21/19 1:09 PM\nCertificate fingerprints:\nMD5: 06:FB:FA:F0:68:49:65:38:6D:FB:B3:2D:8A:24:5D:2B\nSHA1: A2:39:41:40:F8:D5:3A:6D:80:62:D5:D5:6A:27:EB:9B:3A:35:B2:DA\nSHA256: 85:B9:FB:97:98:69:B8:DF:2A:B0:38:C6:3B:C7:87:CA:71:21:CA:CE:DE:D0:09:57:FF:AF:B7:EB:E8:77:FD:6D\nSignature algorithm name: SHA256withRSA\nVersion: 3\nExtensions:\n#1: ObjectId: 2.5.29.14 Criticality=false\nSubjectKeyIdentifier [\nKeyIdentifier [\n0000: 1b 97 38 19 52 43 34 f6 2a 0e 7f a4 22 db 07 80 ..8.RC4.........\n0010: 41 6e 47 a5 AnG.\n]\n]\n\nProcedures\n\nInstallation procedure (using /opt/ibm as the install directory)", "logical_doc_id": 2, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q052", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "1. Download the new files that are attached at the end of this technote into a temporary directory ( /tmp) on the APM server.\n\n2. Stop APM by issuing the following command:\n\napm stop_all\n\n3. Back up the existing shared keystore by issuing the following command:\n\ncp /opt/ibm/wlp/usr/shared/resources/security/key.jks\n/opt/ibm/wlp/usr/shared/resources/security/key.jks.BAK\n\n4. Install the new keystore (replace the existing file) by issuing the following command:\n\ncp /tmp/updated.8.1.4.key.jks /opt/ibm/wlp/usr/shared/resources/security/key.jks\n\n5. Back up the existing UI truststore by issuing the following command:\n\ncp /opt/ibm/wlp/usr/shared/resources/security/trust.jks /opt/ibm/wlp/usr/shared/resources/security/trust.jks.BAK\n\n6. Install the new UI truststore (replace the existing file) by issuing the following command:\n\ncp /tmp/updated.8.1.4.trust.jks /opt/ibm/wlp/usr/shared/resources/security/trust.jks\n\n7. Restart APM by issuing the following command:\n\napm start_all\n\nVerification procedure - verifying the installation of the new keystore files\n\n1. After APM is restarted, navigate to the APMUI at https://:9443 [https://apm_server_hostname:9443/]\n\nwhere is the hostname of your V8.1.4 APM server.\n\n2. Verify that the APM Log in page appears and log in.\n\n3. Verify that agent data is shown on the APM dashboard.\nNote: The passwords for the keystores and truststores are the same passwords as the upgraded 8.1.4 environment, therefore, you don't need to update the server.xml and serverVariables.xml files.\n\nKeystore and truststore files:\nupdated.8.1.4.trust.jks [/support/docview.wss?uid=swg22016073&aid=2]updated.8.1.4.trust.jks [/support/docview.wss?uid=swg22016073&aid=1] updated.8.1.4.key.jks [/support/docview.wss?uid=swg22016073&aid=4]updated.8.1.4.key.jks [/support/docview.wss?uid=swg22016073&aid=3]", "logical_doc_id": 3, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q052", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "Once you have obtained a new certificate from your certificate authority and are ready to replace the expiring one currently in use by your DataPower configuration with this new certificate, there is no single prescribed manner in which to perform the replacement operation. The following information presents some options for formulating an approach that best fits your environment.", "logical_doc_id": 4, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q052", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "First, know your certificate material. It's not uncommon for newer certificates to be chained, so it is not a one for one replacement; the existing certificate on the DataPower appliance may need to be replaced by more than one certificate. Therefore, it is important to ensure you have the full certificate chain, as appropriate (i.e, the personal, intermediate and root certificates). Certificate authorities may send two certificates in the chain and expect the third one to be downloaded from their website.\n\nHere's a screenshot of a sample chain. Notice that you can check the 'Certification Path' tab if there are any remaining certificates in the chain. Also note the chain of \"Issued To\" and \"Issued By\" identities.\nExampleCertificateChain.jpg [/support/docview.wss?uid=swg21500046&aid=2]ExampleCertificateChain.jpg [/support/docview.wss?uid=swg21500046&aid=1]\n\nAs for the certificate configuration on DataPower, the appliance will reference the actual key and certificate files stored in the cert: directory by file name. Navigation in the WebGUI to the SSL Proxy Profile -> Crypto Profile -> Crypto Key and Certificate objects will show the current files referenced by the configuration.\n\n[/support/docview.wss?uid=swg21500046&aid=3] [/support/docview.wss?uid=swg21500046&aid=3]\n\nFor example, your DataPower configuration may currently reference the existing files cert:///current-key.pem and cert:///current-cert.pem.\n\n[/support/docview.wss?uid=swg21500046&aid=4] [/support/docview.wss?uid=swg21500046&aid=4]\n\nAs long as the replacement file(s) are NOT named the same as these files (i.e. the new ones are named cert:///new-key.pemand cert:///new-cert.pem for example), it is safe to load the new file(s) into the cert: directory at any time ahead of the replacement operation. Your existing configuration will not use the new files, so long as the Crypto Key and Certificate Objects still refer to the files associated with the expiring certificate (i.e. cert:///current-key.pem and cert:///current-cert.pem).\n\n[/support/docview.wss?uid=swg21500046&aid=5] [/support/docview.wss?uid=swg21500046&aid=5]\n\nHaving both expiring and replacement files in the cert: directory at once allows for the capability to modify the configuration to point to the new files or revert it back to the expiring files relatively easily or to configure a new SSL Proxy Profile object that references the new files. The new SSL Proxy Profile could be used to test independently of the currently running configuration using a new test service such as an XML Firewall.\n\nYou can navigate directly to the key and certificate objects using these paths:\nObjects \u2192 Crypto Configuration \u2192 Crypto Certificate.\nObjects \u2192 Crypto Configuration \u2192 Crypto Key", "logical_doc_id": 4, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q052", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Another view is from Control Panel -> Keys and Certificate Management.\n\n[/support/docview.wss?uid=swg21500046&aid=6] [/support/docview.wss?uid=swg21500046&aid=6]\n\nEither way, note how the configuration ultimately references the files in the cert: directory and plan ahead for how you prefer to reference the new files.\n\nThey may be swapped out within the existing Crypto Configuration objects (i.e. update the objects to reference the new file(s) or to revert to the expiring ones as needed).\n\nAlternatively, a new separate set of Crypto Configuration objects that reference the new files may be created and replacement performed at the Crypto object level by updating the configuration to reference the new replacement Crypto Configuration objects.\n\nImportant Note: If the replacement certificate has the same file name of the expired certificate, you MUST disable/enable the certificate object in order to clear all cached references to the expired certificate.\n\nFor more information on certificates, refer to the product documentation specific to your firmware and appliance type. Navigate to the Administrator's Guide, under \"Managing the Appliance\" - \"Working with keys and certificates\" from the WebSphere DataPower Product Documentation Portal [http://www-01.ibm.com/support/docview.wss?uid=swg21377654].", "logical_doc_id": 4, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q052", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "A Validation Credential object configured with multiple Certificate Authority certificates containing identical subject DNs but different key material may fail to validate incoming certificates that have been signed with one of the issuer certificates.", "logical_doc_id": 5, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q052", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "DataPower searches the certificate list based on subject DN and attempts to validate against the first certificate that it finds with the given DN. If the initial attempt fails, the certificate validation will fail.", "logical_doc_id": 5, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q052", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "A common scenario in which this issue arises is when a CA certificate is due to expire and the CA has issued a new certificate for the same subject.", "logical_doc_id": 5, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q052", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "If certificate validation fails (especially with \"certificate signature failure\"), check to make sure all of the configured certificates have unique subject DNs. If there is more than one certificate with the same subject DN, this may be the issue.", "logical_doc_id": 5, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q052", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Use a single certificate with a given subject DN per Validation Credential object or upgrade to a firmware version above 3.8.1 when it is available.", "logical_doc_id": 5, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q052", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do you replace an expired SSL certificate on the Sametime Gateway?\n\nSSL/TLS certificates are used on the Gateway to associate trust between external instant messaging services. These certificates have an expiration date when they no longer can provide the associated trust.", "logical_doc_id": 6, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q052", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "The Sametime Gateway application uses the WebSphere Application Server Java keystores to maintain the SSL/TLS certificates. You have the following options when replacing the expired certificate:\nCreate a new certificate request\nReceive a renewed certificate request from your CA\n\nMore information on each option is provided below.\n\nCreate a new certificate request\n\nCreate a new certificate request and apply that certificate by following the procedures in the Sametime product documentation:\n\nFor a single server > Requesting a certificate signed by a Certificate Authority [http://publib.boulder.ibm.com/infocenter/sametime/v8r5/index.jsp?topic=/com.ibm.help.sametime.v85.doc/config/config_gw_ssl_request_cert.html]\n\nFor a cluster server> Creating a certificate request [http://publib.boulder.ibm.com/infocenter/sametime/v8r5/index.jsp?topic=/com.ibm.help.sametime.v85.doc/config/config_gw_ssl_request_cert_clus.html]\n\nReceive a renewed certificate request from your CA\n\nYou can receive a renewed certificate from your certificate authority (CA) without recreating the request by using these steps:\n\n1. Locate the keystore in use 1. For a single server the keystore (key.p12 or STGWKS.p12) will be located in the following directory path:\n\n\\WebSphere\\Appserver\\profiles\\[RTCGWServer]\\config\\cells\\[CellName]\\nodes\\[NodeName]\n 2. For a cluster the keystore (key.p12 or STGWKS.p12) will be located in the following directory path:\n\n\\WebSphere\\Appserver\\profiles\\[RTCGWServer]\\config\\cells\\[CellName]\\nodes\\[SIP Proxy Node Name]\n\n2. Load IBM Key Manager, iKeyman, by running the following script:\n\n\\WebSphere\\Appserver\\bin\\ikeyman.bat\n\n3. Once loaded, click open, then change the keystore type to PKCS12, and browse to the keystore you located above. The default keystore password is \"WebAS\"; you will need to enter this password to open the keystore.\n\n4. Once the keystore is opened within ikeyman, you can \"receive\" the renewed certificate that was delivered by your CA. This step can be achieved by selecting the \"Receive\" button and browsing to the renewed certificate on the file system.\n\n5. Next confirm that you successfully received the renewed certificate by selecting \"View Details\" within ikeyman. This task shows you the validity of the certificate so that you can confirm that the expired certificate has been replaced with the renewed certificate.\n\n6. Launch the Integrated Solutions Console for the Sametime Gateway server, and navigate to the SSL Configurations.\n\nSecurity -> SSL certificate and key management -> Manage Endpoint Security configurations 1. For a single server select the inbound node name (for example, STGWNode)\n\nFor a cluster expand the ProxyNode and select the SIPProxyServer", "logical_doc_id": 6, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q052", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Screen capture of SIPProxyServer node:\n [/support/docview.wss?uid=swg21442836&aid=1]\n 2. You will be brought to \"Specific SSL configurations for this endpoint.\" Do not change anything on this page; simply select \"Update certificate aliases.\" This step loads the newly received certificate into memory.\n 3. Repeat this procedure on the outbound node on the Manage Endpoint Security configurations page.\n\n7. Now your Sametime Gateway has been configured to use your renewed certificate. In some cases, it might be required to restart the environment.", "logical_doc_id": 6, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q052", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Error message in the application message log (e.g. msg__test-WAS855.log)\n\nPROGRAM ERROR null null com.tivoli.pd.jutil.PDSslServices refreshCert WebContainer : 1\n[\nHPDBA0609E Unable to automatically refresh keystore file:/var/PolicyDirector/keytab/java.ks.\n]\n\nat com.tivoli.pd.jras.pdjlog.PDJLogger.exception(PDJLogger.java:143)\nat com.tivoli.pd.jras.pdjlog.PDJMessageLogger.exception(PDJMessageLogger.java:79)\nat com.tivoli.pd.jutil.PDSslServices$2.run(PDSslServices.java:1584)\nat java.security.AccessController.doPrivileged(Native Method)\nat com.tivoli.pd.jutil.PDSslServices.refreshCert(PDSslServices.java:1445)\nat com.tivoli.pd.jutil.PDSslServices.checkAndRefreshCert(PDSslServices.java:897)\n.....\nPROGRAM ERROR null null com.tivoli.pd.jutil.PDSslServices refreshCert WebContainer : 1 java.lang.IllegalStateException:\n[\nHPDBA0609E Unable to automatically refresh keystore file:/var/PolicyDirector/keytab/java.ks.\n]\nat com.tivoli.pd.jutil.PDSslServices$2.run(PDSslServices.java:1568)\nat java.security.AccessController.doPrivileged(Native Method)\nat com.tivoli.pd.jutil.PDSslServices.refreshCert(PDSslServices.java:1445)\nat com.tivoli.pd.jutil.PDSslServices.checkAndRefreshCert(PDSslServices.java:897)\nat com.tivoli.pd.jutil.PDSslServices.checkWrappedSSLContext(PDSslServices.java:938)\n.....", "logical_doc_id": 7, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q052", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Automatic refresh of the certificate fails because the userid which is running the WAS java process does not have sufficient access rights to write to the directory where the keystore file exists.", "logical_doc_id": 7, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q052", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "Environment:\n\nISAM 7.0.0.16\nWAS 8\nSolaris\n\nIBM support recreated issue with following environment:\nISAM 7.0.0.10\nWAS 8.5.5\nLinux", "logical_doc_id": 7, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q052", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "The following error indicates that the certificate has NOT been expired. Instead the certificate has reached its midlife and an automatic refresh of the certificate is tried. However an attempt to refresh the certificate has failed.\n\nPROGRAM ERROR null null com.tivoli.pd.jutil.PDSslServices refreshCert\nWebContainer : 2 java.lang.IllegalStateException:\n[\nHPDBA0609E Unable to automatically refresh keystore file:\n/var/PolicyDirector/keytab/java.ks.\n]\n\nDeterming if a certificate has reached its midlife:\n\nCheck the ivmgrd.conf for certificate lifetime:\n# SSL certificate lifetime in days.\nssl-cert-life = 365\n\nCheck the certificate from the keystore to compare if it has reached the midlife:\n\nkeytool -list -v -keystore -storetype JCEKS\n\nExample:\nkeytool -list -v -keystore /var/PolicyDirector/keytab/testautocertrefresh.ks -storetype JCEKS\nEnter keystore password: <-just hit enter here, no need for password for listing certificates\n**************** WARNING WARNING WARNING *****************\nThe integrity of the information stored in the keystore *\nhas NOT been verified! In order to verify its integrity, *\nyou must provide the srckeystore password. *\n**************** WARNING WARNING WARNING *****************\n\nKeystore type: JCEKS\nKeystore provider: IBMJCE\n\nYour keystore contains 1 entry\n\nAlias name: appsvr\nCreation date: Dec 16, 2015\nEntry type: keyEntry\nCertificate chain length: 2\nCertificate[1]:\nOwner: CN=testautocertrefresh/WAS855, OU=Default, O=Policy Director, C=US\nIssuer: CN=pdca, O=Policy Director, C=US\nSerial number: 10001593\nValid from: 12/15/15 12:02 AM until: 12/17/16 12:02 AM\nCertificate fingerprints:\nMD5: 29:F1:37:E7:7C:8F:79:C5:22:6F:FA:48:88:D5:52:8D\nSHA1: FE:CF:BF:F6:B2:8D:6E:E1:10:B5:A3:76:F0:70:CD:B1:E3:25:32:BC\nCertificate[2]:\nOwner: CN=pdca, O=Policy Director, C=US\nIssuer: CN=pdca, O=Policy Director, C=US\nSerial number: 7a3896d80bfd99e1\nValid from: 1/13/15 2:13 PM until: 1/9/35 2:13 PM\nCertificate fingerprints:\nMD5: F4:5C:45:6A:10:0B:74:48:96:52:B5:B5:F6:CB:77:B8\nSHA1: 83:7A:7D:D2:DE:CA:C1:ED:0E:71:A6:C2:0B:7E:F4:36:1E:A4:6E:01\n....\n\nSimulation Recreation steps:\nManually refresh the certificate using SvrSslCfg -action replcert command\nModify the system clock on the Policy Server and on the server where java application is run so that the certificate midlife is reached but less than the certificate expiration time\nRun test with a Java application as a non-root user (e.g. ibmuser)\nRun test application which has code \"new PDContext(args[1], args[2].toCharArray(), configURL);\" to initiate the certificate refresh\nCheck that the user running the Java application does not have access rights to write to the directory where the key store file exists (e.g. /var/PolicyDirector/keytab).\n\nCheck directory access rights:", "logical_doc_id": 7, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q052", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "ls -l /var/PolicyDirector/\ntotal 8\ndrwxr-xr-x 2 ivmgr ivmgr 4096 Dec 21 00:00 keytab <- ibmuser does not have write access to the keytab directory\ndrwxrwxrwx 2 ivmgr ivmgr 4096 Dec 16 00:02 log", "logical_doc_id": 7, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q052", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Correct the access rights of the directory where the keystore file exists for the Java process to write to the keystore file.\n\nPRODUCT ALIAS/SYNONYM\n TAM\nISAM\nITAM", "logical_doc_id": 7, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q030", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Things To Gather For GDE Dump Analysis", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q030", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Things to gather for dump analysis:\n- Agentinfo output\n- Any information about when the dump occurred, whether it occurred during a specific task, etc.\n- Any existing analyses that the customer already has gathered themselves or from a vendor\n- Any console output captured during the crash event\n- We also need some platform-specific information\u2026.\n\nLinux :\nSecure Core Image and Kernel\n/var/crash/xxx/vmcore\n\nSolaris :\nKernel and image in the /var/crash/hostname\n\nvmcore.x\nvmdump.x\n\nAIX :\nsnap file\nHow to generate snap file\nsnap -gc\n\n/opt/vormetric/DataSecurityExpert/agent/secfs/.sec/mod/secfs2\n\nHP-UX :\n\nentire contents of /var/adm/crash/crash.x\noutput from var/adm/crash>ls \u2013l\n\nWindows :\n\nMemory dump file, preferably with windows configured for complete memory dumps", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q030", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How can I write verbose gc output to a log file other than the native_stdout?", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q030", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "By default, Solaris and HP-UX do not write verbose GC to a log file. This must be configured.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q030", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "WAS 8.5.0.2 (and higher), WAS 8.0.0.6 (and higher), WAS 7.0.0.27 (and higher):\n\nSolaris:\nAdd the following parameters to the generic JVM arguments:\nXX:+PrintGCDetails\nXX:+PrintGCDateStamps\nXX:+PrintHeapAtGC\nXloggc:/tmp/gc.log\n\nTo enable log file rotation:\nXX:+UseGCLogFileRotation\nXX:NumberOfGCLogFiles=10\nXX:GCLogFileSize=10M\n\nnotes:\nXloggc:\nex: -Xloggc:/tmp/gc.log\nXX:+UseGCLogFileRotati o n * Enabled GC log rotation, requires -Xloggc\nXX:NumberOfGClogFiles= * Set the number of files to use when rotating logs, must be >= 1. The rotated log files will use the following naming scheme, .0, .1, ..., .n-1.\nXX:GCLogFileSize=K (or M) * The size of the log file at which point the log will be rotated, must be >= 8K.\n\nHP:\nAdd the following parameters to the generic JVM arguments:\nXX:+PrintGCDetails\nXX:+PrintGCDateStamps\nXX:+PrintHeapAtGC\nXverbosegc:file= /tmp/gc_pid$$.vgc\n\nTo enable log file rotation:\nXX:+UseGCLogFileRotation\nXX:NumberOfGCLogFiles=10\nXX:GCLogFileSize=10M\n\nnote : $$ maps to the PID of the java process RELATED INFORMATION\n 6941923 : RFE: Handling large log files produced by lon [http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6941923]\nEnabling verbose garbage collection (verbosegc) in WebS [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21114927]\nWhere to set generic JVM arguments in WebSphere Applica [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21417365]\nVerify Java SDK version shipped with IBM WebSphere Appl [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27005002]\nHP-UX Java 6.0.18 - Handling large GC log files [http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03119431/c03119431.pdf]\nHP-UX Java 7.0.05 - Handling large GC log files [http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03123467/c03123467.pdf]\nOracle - Java HotSpot VM Options [http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html]", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q030", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "The JNI layer trace can be turned on in the configuration file found in the WTX installation directory. The configuration file name differs by version.\n\nVersion File Name 8.1, 8.2, 8.3 dtx.ini\nThe configuration file contains a section named [JNI Layer Trace].\n\n[JNI Layer Trace]\n;switch=off\n;file=\n\nThese instructions will assist you in changing the configuration file so that a trace file is created.\n 1. Find the [JNI Layer Trace] section in the configuration file.\n 2. Uncomment (delete the semicolon [ ; ] from the front of the line) the switch option.\n 3. Change the switch option from \"off\" to \"on\".\n 4. Uncomment the file option.\n 5. Add a complete path and file name to the file option.\n\nNote: The user running the map or system must have the correct permissions to write to the directory and file specified in the file option.\n\nAn example of the modified options is listed below.\n\n[JNI Layer Trace]\nswitch=on\nfile=c:\\temp\\jnitrace.txt\n\nAfter completing these instructions, your configuration file is ready to create a JNI layer trace. Run the map or system that contains the map using a Java based adapter. The trace file will appear in the file you indicated.\n\nAdditional settings for JNI layer trace\n\nThere are three additional options that can be set to make the trace file display more, or verbose, information. These are set in the [JVM Options] section of the configuration file.\n\n[JVM Options]\n;option1=\n;option2=\n;...\n\nThe three options are for verbose class loading, verbose garbage collection, and verbose JNI. Each is described in the table below.\n\nOption Description -verbose:class Specifies whether to use verbose debug output for class loading. -verbose:gc Specifies whether to use verbose debug output for garbage collection. -verbose:jni Specifies whether to use verbose debug output for native method invocation.\nThese instructions will assist you in changing the configuration file so that a verbose JNI trace file is created.\n 1. Find the [JVM Options] section in the configuration file.\n 2. Uncomment (delete the semicolon [ ; ] from the front of the line) for option1.\n 3. Add one of the options listed in the table above.\n 4. Repeat steps 2 and 3 for each option you would like added. Add optionN=, where N is the next number and N <= 128.", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q030", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "An example of the modified options is listed below.\n\n[JVM Options]\noption1=-verbose:jni\noption2=-verbose:gc\noption3=-verbose:class\n\nNote: Tracing creates very large files and should only be used for debugging purposes. When not in use, each option can be turned off by commenting (adding a semi-colon to the front of) the line in the configuration file.", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q030", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "#How to enable Java Native Interface layer trace [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21244512]\n\nCross reference information Segment Product Component Platform Version Edition Data & Information Management WebSphere Transformation Extender Java Adapter AIX, HP-UX, Linux, Solaris, Windows 8.1, 8.0.1, 8.0 International, US Data & Information Management WebSphere Transformation Extender JMS Adapter AIX, HP-UX, Linux, Solaris, Windows 8.1, 8.0.1, 8.0 International, US Data & Information Management WebSphere Transformation Extender JNDI Adapter AIX, HP-UX, Linux, Solaris, Windows 8.1, 8.0.1, 8.0 International, US Data & Information Management WebSphere Transformation Extender MIME Adapter AIX, HP-UX, Linux, Solaris, Windows 8.1, 8.0.1, 8.0 International, US Data & Information Management WebSphere Transformation Extender SDK AIX, HP-UX, Linux, Solaris, Windows 8.1, 8.0.1, 8.0 International, US\nPRODUCT ALIAS/SYNONYM\n Ascential DataStage TX Mercator", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q030", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "This MustGather will assist you in collecting the data necessary to help you diagnose and resolve the issue. If you are unable to determine the root cause using the information collected, you should open a PMR with IBM Support [http://www.ibm.com/contact] for further investigation providing the data collected.", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q030", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "You can use the IBM Support Assistant Lite (ISA Lite) Data Collector tool [https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.team.concert.doc/topics/t_using_the_isal.html] to quickly collect diagnostic files, such as log files, configuration files or to run traces. This tool is bundled with RTC 4.x and above. ISA Lite collects information about your Jazz Team Server environment and stores the information in a .zip archive file. If you have a need to open a service request with IBM Support [http://www.ibm.com/contact] for further assistance, you can send the archive file with the data collection so that they can help diagnose and fix problems.\n\nThe information below should be gathered in addition to the normal information and log gathering done by ISA Lite.\n\nSCM Data Transfer Issues\n\nSCM CLI\n\nSCM Eclipse Client\n\nSCM Web UI\n\nSCM Additional Resources\n\n#SCM%20Data%20Transfer%20Issues\n\nSCM Data Transfer Issues\nWhen there is difficulty with transferring data between the server and the client such a timeouts, out of memory errors or general slowness collect the following data.\n\nPreparation\n\nEnable Verbose Garbage Collection in WebSphere\n*\n*\n*\n*\n*\n*\nFor more information on verbose GC including additional instructions for Solaris or HP-UX, see:\n Enabling verbose garbage collection (verboseGC) in WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21114927]\n For more information on collecting data related to WebSphere see:\n MustGather: Read first for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg21145599]\n\nEnable the JVM to create javacores in WebSphere\n*\n-Xdump:java:events=user\n*\n*\nNote\n*\n-Xdump:java+\nheap\n+\nsystem\n:events=user\n*\nRestart the Application Server for the previous two changes to take effect.\n\nEnable the JVM to create javacores and verbose GC logging in Tomcat *\n*\n* -Xdump:java:events=user\nRestart the Application Server for the changes to take effect.\n\nNote: Both the previous settings should be safe to leave enabled at all times. Garbage collection has a minimal impact on the server and Xdump has no impact unless explicitly called.\n\nData Collection *\n\nNote: Because of the amount of logs generated by the following two settings it is recommended that they be disabled after reproducing the problem.", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q030", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Enable SCM Service Logging *\n*\n*\n*\n*\n*\nnot\n*\nEnable SCM and SQL tracing *\nlog4j.properties\n*\n*\n*\n*\n*\nhttps://\n\n/\nccm\n/admin?internal=true\nSelect Reload Log Settings on the left side under Internal Tools,\n Disable when reproduction is complete\nTo disable you must replace TRACE and DEBUG with OFF and use the Reload Log Settings operation again.\n Removing them or commenting them out will prevent them from being disabled.\n log4j.logger.com.ibm.team.scm=OFF\n log4j.logger.sqlTxLogger=OFF\n\nStart the WAIT script *\n* Example\n*\n* waitDataCollector.sh --sleep 60 --iters 40 \n*\nNote\n* Warning:\n*\nUse the Query Stats counter service to gather query stats. *\n*\n*\n*\n*\n* Reset Query Stats\n* Start Collecting Query Stats\n*\n*\n*\nQuery Stats View\nReproduce the problem, collect and send in the following:\n* This will include the logs containing the SCM and SQL traces.\n*\n4.x Data Collection tool [https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.team.concert.doc/topics/t_using_the_isal.html]\n3.x Data Collection tool [http://www-01.ibm.com/support/docview.wss?uid=swg21455421]\n2.x Data Collection tool [http://www-01.ibm.com/support/docview.wss?uid=swg21433019]\n\nBack to top\n\nSCM CLI (Command Line Interface)\nCan this issue be reproduced in the Eclipse client (not using the CLI) or web US (User Interface)?\n\nSCM Eclipse Client\nCollect the relevant screenshots\nCollect the workspace log file located in \u2018workspace directory/metadata\u2019 named .log\n\nSCM Web UI * Collect the relevant screenshots\n\nSCM Additional Resources\nSCM Command Line Bug Reporting [https://jazz.net/wiki/bin/view/Main/SCMCommandLineBugReporting]\nMUSTGATHER: Troubleshooting hangs of the scm.exe application [http://www.ibm.com/support/docview.wss?uid=swg21572522]\n\nBack to top\n\nLeverage the Jazz Community Jazz and Rational Team Concert have an active community that can provide you with additional resources. Browse and contribute to the User forums, contribute to the Team Blog and review the Team wiki.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q030", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Refer to technote 1319600 [http://ibm.com/support/docview.wss?uid=swg21319600] for details and links.", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q030", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Once the generation of Verbose GC output has been setup [http://www.ibm.com/support/docview.wss?rs=727&uid=swg21222436] and the output gathered, it is possible to carry out analysis of the data.\nThis can be carried out in one of two ways:\nUsing a Visualisation tool\nManual Analysis by reading the XML log file\n\nVisulization Tools There are currently two publically available tools that are capable of analyzing the Verbose GC output:\nDiagnostic Tool for Java Garbage Collector: http://www.alphaworks.ibm.com/tech/gcdiag [http://www.alphaworks.ibm.com/tech/gcdiag]\nIBM Pattern Modeling and Analysis Tool for Java Garbage Collector (PMAT): http://www.alphaworks.ibm.com/tech/pmat [http://www.alphaworks.ibm.com/tech/pmat]\n\nManual Analysis The Verbose GC output that is received is dependent on which of the following three Garbage Collection strategies is in place:\n-Xgcpolicy:optthruput Optimum Throughput [http://www.ibm.com/support/docview.wss?rs=727&uid=swg21222443]\n-Xgcpolicy:optavgpause Concurrent GC [http://www.ibm.com/support/docview.wss?rs=727&uid=swg21222459]\n-Xgcpolicy:gencon Generational and Concurrent [http://www.ibm.com/support/docview.wss?rs=727&uid=swg21222486]\n\nIt is recommended that a visualization tool is used to develop an overview of the Garbage Collector activity and trends, and then carry out manual analysis for Garbage Collection cycles of particular interest. RELATED INFORMATION\n Optimum Through Put [http://www.ibm.com/support/docview.wss?uid=swg21222443]\nConcurrent GC [http://www.ibm.com/support/docview.wss?uid=swg21222459]\nGenerational and Concurrent [http://www.ibm.com/support/docview.wss?uid=swg21222486]\nDiagnostic Tool for Java Garbage Collector [http://www.alphaworks.ibm.com/tech/gcdiag]\nPMAT [http://www.alphaworks.ibm.com/tech/PMAT]\nHeapDump Analysis [http://www.ibm.com/support/docview.wss?uid=swg21222458]", "logical_doc_id": 5, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q018", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "DIRECT LINKS TO FIXES\nbpm.8570.cf2016.09.delta.repository.2of2 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8570.cf2016.09.delta.repository.2of2&source=SAR]\nbpm.8570.cf2016.09.delta.repository.1of2 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8570.cf2016.09.delta.repository.1of2&source=SAR]\n8.5.5.0-WS-BPM-IFJR56208 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.5.5.0-WS-BPM-IFJR56208&source=SAR]\nDownloading IBM Business Process Manager V8.5.7 Cumulative Fix 2016.09 [http://www-01.ibm.com/support/docview.wss?uid=swg24042580]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q018", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "You receive an unexpected database exception when you request\n defined groups by using square brackets in the REST API filter\n expression and the runtime database is an IBM DB2 database.\n\n [6/22/16 13:27:12:638 UTC] 00000109 wle E\n CWLLG2229E: An\n exception occurred in an EJB call. Error: StatementCallback;\n SQL\n [select\n t0.GROUP_ID,t0.GROUP_NAME,t0.DISPLAY_NAME,t0.GROUP_TYPE,t0.DESCR\n IPTION,t\n 0.GROUP_STATE,t0.PARENT_GROUP_ID,t0.PARTICIPANT_ID from\n LSW_USR_GRP_XREF\n t0 where GROUP_NAME LIKE 'GD\\_\\[NE1\\]\n ISI-Lojas\\_S\\_4e3d7766-f757-44f1-bada-948e55d65435.958c0974-c6ef\n4850-98\n d5-370d6661f2b5' ESCAPE '\\']; DB2 SQL Error: SQLCODE=-130,\n SQLSTATE=22025, SQLERRMC=null, DRIVER=4.11.69; nested exception\n is\n com.ibm.db2.jcc.am.SqlDataException: DB2 SQL Error:\n SQLCODE=-130,\n SQLSTATE=22025, SQLERRMC=null, DRIVER=4.11.69\n\n org.springframework.dao.DataIntegrityViolationException:\n StatementCallback; SQL [select\n t0.GROUP_ID,t0.GROUP_NAME,t0.DISPLAY_NAME,t0.GROUP_TYPE,t0.DESCR\n IPTION,t\n 0.GROUP_STATE,t0.PARENT_GROUP_ID,t0.PARTICIPANT_ID from\n LSW_USR_GRP_XREF\n t0 where GROUP_NAME LIKE 'GD\\_\\[NE1\\]\n ISI-Lojas\\_S\\_4e3d7766-f757-44f1-bada-948e55d65435.958c0974-c6ef\n4850-98\n d5-370d6661f2b5' ESCAPE '\\']; DB2 SQL Error: SQLCODE=-130,\n SQLSTATE=22025, SQLERRMC=null, DRIVER=4.11.69; nested exception\n is\n com.ibm.db2.jcc.am.SqlDataException: DB2 SQL Error:\n SQLCODE=-130,\n SQLSTATE=22025, SQLERRMC=null, DRIVER=4.11.69\n at\n org.springframework.jdbc.support.SQLExceptionSubclassTranslator.\n translate(SQLExceptionSubclassTranslator.java:63)\n at\n org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTransla\n tor.translate(SQLErrorCodeSQLExceptionTranslator.java:237)\n at\n org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.\n java:407\n )\n at\n org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.ja\n va:458)\n at\n org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.ja\n va:466)\n at\n org.springframework.jdbc.core.simple.SimpleJdbcTemplate.query(Si\n mpleJdbcTemplate.java:187)\n at\n com.lombardisoftware.server.ejb.persistence.dao.UnversionedPODAO\n .executeQuery(UnversionedPODAO.java:233)\n at\n com.lombardisoftware.server.ejb.persistence.dao.UnversionedPODAO\n .findOrdered(UnversionedPODAO.java:222)\n at\n com.lombardisoftware.server.ejb.persistence.dao.UnversionedPODAO\n .findOrdered(UnversionedPODAO.java:207)\n at\n com.lombardisoftware.server.ejb.persistence.dao.UnversionedPODAO\n .find(UnversionedPODAO.java:203)\n at\n com.lombardisoftware.server.ejb.persistence.dao.UserGroupDAO.fin\n dByFilter(UserGroupDAO.java:109)\n at\n com.lombardisoftware.server.core.GroupCore.getGroups(GroupCore.j\n ava:1293)\n at\n com.lombardisoftware.server.ejb.psapi.UserGroupAPIFacadeCore.get\n UserGroupsByFilter(UserGroupAPIFacadeCore.java:111)", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q018", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "When you specify a filter containing square brackets like\n http://localhost:9080/rest/bpm/wle/v1/groups?filter=A[1*, you\n see an error message like\n\n CWTBG0019E: Unexpected exception during execution. Exception\n information: 'Unexpected database exception'.\n\n The error occurs because escaped square brackets are in the SQL,\n which is sent to the database.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q018", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A fix is available for IBM BPM V8.5.5.0 that does not escape\n square brackets in the filter condition of group requests.\n\nOn Fix Central (http://www.ibm.com/support/fixcentral), search\n for JR56208:\n\n1. Select IBM Business Process Manager with your edition from\n the product selector, the installed version to the fix pack\n level, and your platform, and then click Continue.\n\n2. Select APAR or SPR, enter JR56208, and click Continue.\n\nWhen you download fix packages, ensure that you also download\n the readme file for each fix. Review each readme file for\n additional installation instructions and information about the\n fix.\n\nTo apply the fix, complete the following steps:\n\n1. Shut down the IBM BPM server in a controlled and complete\n manner to ensure that all transactions completed.\n\n2. Extract the .zip file to a directory. For example, extract\n the file to C:\\temp.\n\n3. Add the fix pack repository location in IBM Installation\n Manager:\n a. Start IBM Installation Manager.\n b. In Installation Manager, select File > Preferences >\n Repositories.\n c. Click Add Repository.\n d. Browse to or enter the file path to the repository.config\n file. The repository.config file is located in the\n directory where you extracted the compressed files, for\n example, enter C:\\temp\\repository.config. Click OK.\n\n4. On the main page of the Installation Manager, click Update.\n\n5. Restart the IBM BPM server.\n\nTo remove the fix, complete the following steps:\n\nIMPORTANT NOTE: Remove fixes in the reverse order than the\n order in which they were applied. Do not remove a fix unless all\n fixes applied after it are removed. You may reapply a removed\n fix.\n\nExample: If your system has fix1, fix2, and fix3 applied in\n that order and fix2 must be removed, fix3 must be removed first;\n then fix2 may be removed.\n\n1. Shut down the IBM BPM server in a controlled and complete\n manner to ensure that all transactions completed.\n\n2. Start IBM Installation Manager.\n\n3. On the main page of the Installation Manager, click\n Uninstall.\n\n4. Select the package to uninstall and follow the prompts on\n screen.\n\n5. Restart the IBM BPM server.\n\nTEMPORARY FIX\nNot applicable", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q018", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR56208\nREPORTED COMPONENT NAME\n BPM ADVANCED\nREPORTED COMPONENT ID\n 5725C9400\nREPORTED RELEASE\n 857\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-06-27\nCLOSED DATE\n 2016-07-08\nLAST MODIFIED DATE\n 2016-07-15\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q018", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM STANDARD\nFIXED COMPONENT ID\n 5725C9500", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q018", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R855 PSY\n UP\n\nA FIX IS AVAILABLE\nVersion 7.5.1 Fix Pack 1 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24033036]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q018", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When trying to create snapshot of a process app, users may\n encounter failure and exception below:\n com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException:\n Error for batch element #1:\n DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505,\n SQLERRMC=3;DB2INST1.\n LSW_SNAPSHOT, DRIVER=3.61.65\n\n This full exception message would be:\n [2/7/13 15:48:13:498 GMT] 0000003a wle E Exception while\n creating the snapshot\n com.lombardisoftware.client.delegate.BusinessDelegateException:\n com.lombardisoftware.client.delegate.BusinessDelegateException:\n PreparedStatementCallback; SQL [update LSW_SNAPSHOT set\n CREATED_ON = ?,NAME = ?,ACRONYM = ?,DESCRIPTION = ?,\n SEQ_NUM = ?,ERROR_COUNTER = ?,ORIG_CREATED_ON = ?,ACTIVATED_ON =\n ?,\n ARCHIVED_ON = ?,REPOSITORY_BRANCH_ID = ?,CREATED_BY_USER_ID = ?,\n BRANCH_ID = ?,PROJECT_ID = ?,CHANGE_DATA = ?,IS_ACTIVE = ?,\n IS_BLA_ACTIVE = ?,IS_STARTED = ?,IS_INSTALLED =\n ?,IS_BLA_INSTALLED = ?,\n IS_TIP_DEPLOYED = ?,IS_DEFAULT = ?,IS_ARCHIVED = ? where\n SNAPSHOT_ID =\n ?];\n Error for batch element #1: DB2 SQL Error: SQLCODE=-803,\n SQLSTATE=23505, SQLERRMC=3;DB2INST1.LSW_SNAPSHOT,\n DRIVER=3.61.65;\n nested exception is\n DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505,\n SQLERRMC=3;DB2INST1.\n LSW_SNAPSHOT, DRIVER=3.61.65\n at\n com.lombardisoftware.client.delegate.BusinessDelegateException.a\n sBusinessDelegate\n\n Acronym generation code in BPM 7501 did not take into\n consideration the\n acronym of archived snapshots. This resulted in non-unique\n acronym\n generation and subsequent Constraint Violations exceptions in\n DB. This fix will check for all existing acronyms in archived or\n unarchived state while\n generating unique acronym.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q018", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Users of BPM Express, Standard, and *\nAdvanced. *\n\nPROBLEM DESCRIPTION: Acronyms in archived snapshots are not *\ntaken into consideration when *\ngenerating acronyms, resulting in non- *\nunique acronyms. *\nAcronym generation code in BPM 7501 did *\nnot take into consideration the acronym *\nof archived snapshots. This resulted in *\nnon-unique *\nacronym generation and subsequent *\nConstraint Violations exceptions in DB. *\nThis fix will check for all existing *\nacronyms in archived or unarchived *\nstate while generating unique acronym. *\n\nRECOMMENDATION: *\n\n This will be fixed in a future release pack.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q018", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR44672\nREPORTED COMPONENT NAME\n BPM STANDARD\nREPORTED COMPONENT ID\n 5725C9500\nREPORTED RELEASE\n 750\nSTATUS\n CLOSED FIN\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2012-11-07\nCLOSED DATE\n 2013-02-05\nLAST MODIFIED DATE\n 2013-05-20\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q018", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R750 PSY\n UP\n\nDIRECT LINKS TO FIXES\n8.5.5.0-WS-BPM-IFJR56448 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.5.5.0-WS-BPM-IFJR56448&source=SAR]\nbpm.8570.cf2016.09.delta.repository.2of2 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8570.cf2016.09.delta.repository.2of2&source=SAR]\nbpm.8570.cf2016.09.delta.repository.1of2 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8570.cf2016.09.delta.repository.1of2&source=SAR]\n8.0.1.3-WS-BPM-IFJR56448 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.0.1.3-WS-BPM-IFJR56448&source=SAR]\nDownloading IBM Business Process Manager V8.5.7 Cumulative Fix 2016.09 [http://www-01.ibm.com/support/docview.wss?uid=swg24042580]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q018", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When you try to run the BPMSnapshotCleanup command on an IBM\n Process Center to clean up snapshots, the operation fails with a\n foreign key constraint violation. In the SystemOut.log file of\n the server, you find an exception like this\n\n [04/08/16 12:52:46:775 BRT] 00000068 PALAdminComma I\n BPMSnapshotCleanup failed due to: PreparedStatementCallback; SQL\n [DELETE FROM LSW_USR_GRP_XREF WHERE GROUP_ID = ?]; Error for\n batch element #1: DB2 SQL Error: SQLCODE=-532, SQLSTATE=23504,\n SQLERRMC=WFCUSR.LSW_PARTICIPANT_GROUP.LSWC_PART_GRP_FK,\n DRIVER=4.14.122; nested exception is\n com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException:\n Error for batch element #1: DB2 SQL Error: SQLCODE=-532,\n SQLSTATE=23504,\n SQLERRMC=WFCUSR.LSW_PARTICIPANT_GROUP.LSWC_PART_GRP_FK,\n DRIVER=4.14.122\n java.lang.Exception:\n PreparedStatementCallback; SQL [DELETE FROM LSW_USR_GRP_XREF\n WHERE GROUP_ID = ?]; Error for batch element #1: DB2 SQL Error:\n SQLCODE=-532, SQLSTATE=23504,\n SQLERRMC=WFCUSR.LSW_PARTICIPANT_GROUP.LSWC_PART_GRP_FK,\n DRIVER=4.14.122; nested exception is\n com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException:\n Error for batch element #1: DB2 SQL Error: SQLCODE=-532,\n SQLSTATE=23504,\n SQLERRMC=WFCUSR.LSW_PARTICIPANT_GROUP.LSWC_PART_GRP_FK,\n DRIVER=4.14.122\n at com.lombardisoftware.client.delegate.\n BusinessDelegateException.asBusinessDelegateException\n (BusinessDelegateException.java:41)\n at com.lombardisoftware.client.delegate.\n RepositoryServicesDelegateDefault.snapshotCleanupWithinTX\n (RepositoryServicesDelegateDefault.java:1401)\n at com.lombardisoftware.server.ejb.repositoryservices.\n SnapshotDeleteSupport.snapshotCleanup\n (SnapshotDeleteSupport.java:239)\n at com.lombardisoftware.server.ejb.repositoryservices.\n RepositoryServicesCore.snapshotCleanup\n (RepositoryServicesCore.java:504)\n ...", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q018", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "During snapshot cleanup, the runtime information for participant\n groups or teams is also removed. The relevant data is retrieved\n by using a database query. The BPMSnapshotCleanup command tried\n to delete more data, which caused the foreign key violation.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q018", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A fix is available for IBM BPM V8.0.1.3 that ensures the\n BPMSnapshotCleanup command no longer retrieves and deletes\n information it should not.\n\nOn Fix Central (http://www.ibm.com/support/fixcentral), search\n for JR56448:\n\n1. Select IBM Business Process Manager with your edition from\n the product selector, the installed version to the fix pack\n level, and your platform, and then click Continue.\n\n2. Select APAR or SPR, enter JR56448, and click Continue.\n\nWhen you download fix packages, ensure that you also download\n the readme file for each fix. Review each readme file for\n additional installation instructions and information about the\n fix.\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q018", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR56448\nREPORTED COMPONENT NAME\n BPM ADVANCED\nREPORTED COMPONENT ID\n 5725C9400\nREPORTED RELEASE\n 801\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-08-05\nCLOSED DATE\n 2016-09-27\nLAST MODIFIED DATE\n 2016-09-27\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q018", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM STANDARD\nFIXED COMPONENT ID\n 5725C9500", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q018", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R801 PSY\n UP\n\nA FIX IS AVAILABLE\nVersion 8.5 Refresh Pack 7 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24041575]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q018", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The first time you start the deployment manager after applying\n the IBM Business Process Manager (BPM) V8.5.6.0 cumulative fix\n 1, the server does not start and SQLCODE=-952 database errors\n like the following errors are logged in the\n /logs/BPMUpdateSystemApp*.log file:\n\n org.springframework.dao.TransientDataAccessResourceException:Sta\n tementCallback; SQL [ DELETE FROM BPM_COACH_VIEW_CONFIG_OPTION\n WHERE VERSION_ID NOT IN(SELECT PO_VERSION_ID FROM\n LSW_PO_VERSIONS WHERE PO_TYPE = 66)]; DB2 SQL Error:\n SQLCODE=-952, SQLSTATE=57014,SQLERRMC=null, DRIVER=4.18.60;\n nested exception iscom.ibm.db2.jcc.am.SqlTimeoutException: DB2\n SQL Error: SQLCODE=-952,SQLSTATE=57014, SQLERRMC=null,\n DRIVER=4.18.60\n at\n org.springframework.jdbc.support.SQLExceptionSubclassTranslator.\n translate(SQLExceptionSubclassTranslator.java:58) at\n org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTransla\n tor.translate(SQLErrorCodeSQLExceptionTranslator.java:237)...\n Caused by: com.ibm.db2.jcc.am.SqlTimeoutException: DB2 SQL\n Error:SQLCODE=-952, SQLSTATE=57014, SQLERRMC=null,\n DRIVER=4.18.60\n at com.ibm.db2.jcc.am.kd.a(kd.java:749)at\n com.ibm.db2.jcc.am.kd.a(kd.java:66)\n at com.ibm.db2.jcc.am.kd.a(kd.java:135)at\n com.ibm.db2.jcc.am.bp.c(bp.java:2788)...\n\n PRODUCTS AFFECTED\n IBM BPM Advanced\n IBM BPM Standard\n IBM BPM Express", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q018", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "If you have many entries in the LSW_PO_VERSIONS table of the IBM\n Process Server database, a value that is too small for the Java\n maximum heap size is set when the BPMUpdateSystemApp admin\n command runs to update the IBM BPM toolkits and process\n applications.", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q018", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A fix will be incorporated into an IBM BPM V8.5.6.0 cumulative\n fix that increases the Java maximum heap size for running the\n BPMUpdateSystemApp admin command.\n\nNOTE: This fix might not work all your DEs. A fix that applies\n to all DEs will be available later.\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q018", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR54815\nREPORTED COMPONENT NAME\n BPM ADVANCED\nREPORTED COMPONENT ID\n 5725C9400\nREPORTED RELEASE\n 856\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2015-11-26\nCLOSED DATE\n 2015-12-15\nLAST MODIFIED DATE\n 2015-12-15\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q018", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM ADVANCED\nFIXED COMPONENT ID\n 5725C9400", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q018", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R856 PSY\n UP\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q018", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "PMR 34054,000,781 is a good example that illustrates the problem\n with lacking a self-assisted error in the system out and in the\n error dialog which user can easily understand and be\n informed of the corrective action for an issue that has\n occurred.\n\nIn the case of PMR 34054,000,781, the issue is that the\n Application Security is disabled for some reason by user\n without the knowledge that Application Security must be enabled\n for deployment to work in BPM. The deployment failed with an\n SQL exception as the user is returned as UNAUTHENTICATED and\n hence the insert statement cannot be constructed.\n\ne.g.\n\nCaused by:\n org.springframework.dao.DataIntegrityViolationException:\n PreparedStatementCallback; SQL [insert into LSW_PROJECT\n (PROJECT_ID,CREATED_ON,LAST_MODIFIED,ARCHIVED_ON,NAME,DESCRIPTIO\n N,SHORT_\n NAME,CREATED_BY_USER_ID,LAST_MODIFIED_BY_USER_ID,RELEASE_PROCESS\n _ID,RELE\n ASE_PROCESS_BRANCH_ID,IS_ARCHIVED,IS_TOOLKIT,IS_BRANCHING_ENABLE\n D,IS_HID\n DEN,IS_SYSTEM,IS_IMMUTABLE) values\n (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)];\n Error for batch element #1: DB2 SQL Error: SQLCODE=-407,\n SQLSTATE=23502,\n SQLERRMC=TBSPACEID=2, TABLEID=147, COLNO=1, DRIVER=3.61.65;\n nested\n exception is\n com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException:\n Error for\n batch element #1: DB2 SQL Error: SQLCODE=-407, SQLSTATE=23502,\n SQLERRMC=TBSPACEID=2, TABLEID=147, COLNO=1, DRIVER=3.61.65\n\nThe logged SQL exception is misleading in terms of determing the\n root cause. Although from the trace, one can see the user was\n returned as UNAUTHENTICATED but it does not mention any\n consequence it may cause as a result and what needs to be done\n to correct it.\n\nAfter spending much time, the support team had to go through\n both BPM dev and then WAS support to nail down the root cause\n which is Application Security is disabled. When that\n happens, authentication is skipped and hence UNAUTHENTICATED\n for the user will be returned. But since BPM does not support\n disabling Application Security by design, it resulted in\n deployment failure and the PMR was opened as a Sev 1 system down\n as customer could not deploy an application.\n\nThe PMR could have been avoided if a better error message is\n thrown in the systemout or a pop-up dialog indicating the\n possible cause and the corrective action.\n\nI see this \"problem determination\" issue in the product in\n general because the error is not as helpful as it could be.", "logical_doc_id": 5, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q018", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The Advanced Transition error that the user gets in a pop-up\n dialog when encountering deployment failure is another\n good example. The \"Advanced Transition\" error does not provide\n any meaningful information why the failure happened nor what\n action can be taken. It only indicates to user that the\n deployment failed. The user must go read the logs and sometimes\n the log does not have the underlying error either and trace is\n needed to be turned on to determine the cause which means the\n customer must rely on support to provide the trace string and\n analyze the issue for them. If the error can be more\n indicative, it will help with PMR reduction for sure.", "logical_doc_id": 5, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q018", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "The problem has been fixed in future release.", "logical_doc_id": 5, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q018", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR44546\nREPORTED COMPONENT NAME\n BPM ADVANCED\nREPORTED COMPONENT ID\n 5725C9400\nREPORTED RELEASE\n 751\nSTATUS\n CLOSED FIN\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2012-10-25\nCLOSED DATE\n 2014-12-11\nLAST MODIFIED DATE\n 2014-12-11\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q018", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R855 PSY\n UP", "logical_doc_id": 5, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q042", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Multiple security vulnerabilities exist in the IBM SDK Java Technology Edition that is shipped with IBM WebSphere Application Server and included in the products that are listed in this document.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q042", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "The affected products are shipped with a version of IBM WebSphere Application Server, which is shipped with an IBM SDK Java Technology Edition and is based on the Oracle Java Development Kit (JDK). Oracle has released the January 2014 critical patch updates (CPU), which contain security vulnerability fixes. The IBM SDK for Java Technology Edition has been updated to incorporate the critical patch updates.\nThe following vulnerabilities are applicable to IBM WebSphere Application Server and for the affected product.\n\nCVEID: CVE-2014-0411 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0411]\nDescription: Timing differences based on validity of TLS messages\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/90357 [https://exchange.xforce.ibmcloud.com/vulnerabilities/90357] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N)\n\nVulnerability fixes for other advisories are included in the IBM SDK Java\u2122 Technology Edition but IBM WebSphere Application Server and the products listed below are not vulnerable to them. You will need to evaluate your own code to determine if you are vulnerable. Refer to the Reference section for more information on the advisories not applicable to IBM WebSphere Application Server.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q042", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "WebSphere Lombardi Edition V7.1.0.x, 7.2.0.x", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q042", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Install IBM WebSphere Application Server interim fixes as appropriate for your current IBM WebSphere Application Server version as described in Security Bulletin: Multiple vulnerabilities in current IBM SDK for Java for WebSphere Application Server January 2014 CPU [https://www.ibm.com/support/docview.wss?uid=swg21663938]", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q042", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q042", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\nIBM Security Alerts [http://www.ibm.com/developerworks/java/jdk/alerts]\nIBM WebSphere Application Server Security Bulletin January 2014 [https://www-01.ibm.com/support/docview.wss?uid=swg21663938]\nIBM SDK for Java Security Bulletin January 2014 [http://www-01.ibm.com/support/docview.wss?uid=swg21662968]\nOracle Critical Patch Update Advisory - January 2014 [http://www.oracle.com/technetwork/topics/security/cpujan2014-1972949.html]", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q042", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nThe 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.", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q042", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Supported combinations of IBM HTTP Server, WebSphere Application Server, and the WebSphere WebServer Plug-in\nThere are a variety of issues surrounding support of mixed releases of IBM HTTP Server (IHS), WebSphere Application Server (WAS), and the WebSphere Web Server Plug-in (WAS Plugin). This document only refers to the IBM HTTP Server (powered by Apache) on AIX, HP-UX, Linux, Solaris, Windows, and z/OS (not \"IBM i\").\n\nIn general, the recommended configuration is to use all three components from the same release. However, there are a variety of situations where using other combinations is required.\n\nNote: Customer and product support is only provided when all components in use have a support entitlement.\n\nTerminology\n* Versioning\nWebSphere Application Server uses the following naming scheme: V.R.M.F\nV = version\nR = release\nM = modification\nF = fix pack\nSupported, UnSupported, and other configurations\nFor reference, we categorize support into three categories: supported, unsupported, and other: WebSphere Application Server Support Statement [http://www-01.ibm.com/support/docview.wss?uid=swg27004311]\n\nSupported combinations of the Application Server and WebServer Plug-in A release (such as 9.0, 8.5, 8.0, or 7.0) of the WebServer Plug-in can be used with the corresponding release and any previous releases of the application server, as long as the application server version (in terms of V.R.M.F) is not more\nthan two versions older than the WebServer Plug-in.\n\nAny release of WebSphere Application Server Liberty (\"Liberty Profile\") is supported with any release of the WAS Plug-in from 8.5.5 or later. This include Liberty Profile continuous delivery releases (such as 16.0.0.x or 17.0.0.x) as well as Beta releases.\nFor example, an 8.0 Plugin can front-end servers from 8.0, 7.0, 6.1, and 6.0 whether they're all from a single release or in a mixed cell. Application servers from 8.5 or 8.5.5 would not be a supported configuration, because they are later releases. Similarly, application servers from 5.1/5.0 would not be supported because they are more than two versions (in terms of V.R.M.F) older.\n\nExamples of N-2 Version support: * WAS Plugin 9.0: WAS 7.0, WAS 8.0, WAS 8.5, WAS 8.5.5, WAS 9.0 WAS Plugin 8.5.5: WAS 6.0, WAS 6.1, WAS 7.0, WAS 8.0, WAS 8.5, WAS 8.5.5 WAS Plugin 8.0: WAS 6.0, WAS 6.1, WAS 7.0, WAS 8.0 WAS Plugin 7.0: WAS 5.0, WAS 5.1, WAS 6.0, WAS 6.1, WAS 7.0", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q042", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Exceptions:\nIHS 7.0 + Plugin 7.0 is supported with WAS 8.0, 8.5, and 8.5.5 as a transitional measure for users of third-party IHS modules that did not support IHS 8.0 or later in a timely manner. It is important to note that IHS 7.0 was released in 2008 and lacks support for important security protocols like TLS1.2, ECDHE, and AES-GCM. (IHS 8.0 was released in 2011)\n\nNotes:\nRefer to the following URL for considerations and frequently asked questions related to using the version 8 WAS Plug-in with a version 7 application server:\n\nhttp://publib.boulder.ibm.com/httpserv/ihsdiag/ihs8was7.html [http://publib.boulder.ibm.com/httpserv/ihsdiag/ihs8was7.html]\n\nSupported configurations of Web Servers and the WAS Plugin Given a compatible Plugin has been selected based on WAS release requirements, The release (V.R.M.F) of IBM HTTP Server used must match the Plugin release exactly.\n\nThird-party webservers are only a supported configuration if they are explicitly listed in the supporting software documentation for the WAS release.\n\nExceptions:\nIBM HTTP Server 8.5 used as part of z/OS Ported Tools is additionally supported with the 8.0 Plug-in. While this combination is supported, using the corresponding release is strongly recommended.\nIBM HTTP Server 9.0 included with z/OS V2R2 (and later) is additionally supported with the 8.0 and 8.5 Plugins. While this combination is supported, using the corresponding release is strongly recommended (when available).\n\nUnsupported combinations These are combinations with known technical problems.\nIHS 8.0 or later cannot be used with Plugin 7.0 or earlier (distributed platforms, incompatible GSKit major release)\nIHS 7.0 or earlier cannot be used with Plugin 8.0 or later (distributed platforms, incompatible GSKit major release)\n\nOther configurations\nAny combination not explicitly addressed above is an \"other configuration\". These configurations are not tested or recommended.\nIf WAS is a higher releases than the Plugin, the generated XML might trigger warnings at startup.\n\nOther recommendations\nThere is no required relationship between IHS, Plugin, and WAS fixpack (V.R.M. F) levels, but staying current is strongly recommended. Furthermore, using levels contemporary (but not necessarily identical) with one another is also strongly recommended.", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q042", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "History\n20150812: Clarify V7 transitional support and \"VRMF\" terminology\n20150511: Previous versions of this document were ambiguous with respect to mixed cells vs cells from a previous release.\n20150511: Previous versions of this document permitted future releases of IHS + Plugin only under specific enumerated circumstances.\n20150511: Permit IHS on z/OS to use previous releases of the WAS Plug-in.\n20160316: Emphasize Version as the differentiator, provide examples of N-2 versions.\n20160624: Mention relationship to Liberty.\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Plug-in (remote) Install AIX, Linux, Solaris, Windows 7.0 Application Servers Runtimes for Java Technology Java SDK\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q042", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "This APAR describes the issues that customers encountered with\n IBM WebSphere Application Server Version 8.5. These issues were\n resolved as information center updates in February, 2014", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q042", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: This APAR provides a cumulative list of *\nthe documentation issues for month_year *\nthat affect users of IBM WebSphere *\nApplication Server Version 8.5. *\n\nPROBLEM DESCRIPTION: The Information Centers for WebSphere *\nApplication Server Version 8.5 need *\nto reflect customer enhancement *\nrequests received in problem *\nmanagement records (PMRs). These *\nenhancements can include fixing *\ntechnical inaccuracies or clarifying *\nvague information. *\n\nRECOMMENDATION: *\n\nSee the Problem conclusion section for a description of the\n issues, which are described in customer PMRs, and the\n documentation change or changes that will address these issues.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q042", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Note: We update our information centers monthly. The following\n Version 8.5 modifications will be available in the month_year\n update to the Information Centers. To access the latest\n on-line documentation, go to the product library page at\n http://www.ibm.com/software/webservers/appserv/library and\n select the version and product that is appropriate for your\n WebSphere Application Server environment.\n\nID: PI10514\n Problem : Customer can launch IBM Installation Manager GUI,\n however, no text is displayed in the IBM Installation Manager\n main GUI; empty boxes are displayed without any fonts or text.\n The customer is unable to see available options, unable to\n navigate, or access other panels.\n It is determined that installing the following two X11\n filesets on the AIX system resolves this problem. These\n filesets need to be added to the WebSphere Application Server\n information center as a requirement for AIX systems where\n WebSphere Application Server or IBM Installation manager GUI's\n are used:\nX11.fnt.coreX\nX11.fnt.iso_T1\n This problem can also occur with the WebSphere Application\n Server GUIs; WebSphere customization toolbox,, profile\n management tool, or not installed.\n\nResolution: Topic, Preparing AIX systems for installation,\n is update to include the following:\n To support the graphical user environment on AIX for IBM\n Installation Manager and WebSphere GUIs, install the following:\n\nX11.fnt.coreX\n X11.fnt.iso.T1\n\nID: 755960\n Problem : Some of the parameters for PDJrteCfg utility are\n incorrectly specified in the topic,\n com.tivoli.pd.jcfg.PDJrteCfg utility for Tivoli Access Manager\n single sign-on, The syntax documented is as follows:\n ${JAVA_HOME}/bin/java\nDfile.encoding=ISO8859-1\nXnoargsconversion\nDpd.home=${WAS_HOME}/java/jre/PolicyDirector\ncp ${WAS_HOME}/tivoli/tam/PD.jar\nDwas.installroot=${WAS_HOME}\n com.tivoli.pd.jcfg.PDJrteCfg\naction config\ncfgfiles_path ${WAS_HOME}/java/jre\nhost myhost.us.ibm.com\nalt_config\nwas\njava_home ${JAVA_HOME}\n\nResolution: Topic, com.tivoli.pd.jcfg.PDJrteCfg utility for\n Tivoli Access Manager single sign-on, is updated and the\n PDInteCfg utility syntax is documented as follows:\n\nNote: Before running the PDJrteCfg utility, run\n \"setupCmdLine.sh and set ${TIV_HOME} and ${TAM_HOST} as system\n environment variables.\n\n${WAS_HOME}/java/jre/bin/java\nDjava.ext.dirs=${TIV_HOME}:${WAS_HOME}/java/jre/lib/ext\nDpd.cfg.home=${TIV_HOME}\nDwas.install.root=${WAS_HOME}\nDpd.home=${TIV_HOME}/PolicyDirector\ncp ${TIV_HOME}/PD.jar\n com.tivoli.pd.jcfg.PDJrteCfg\naction config\nwas\njava_home ${WAS_HOME}/java/jre\nhost ${TAM_HOST}\nport 389\ncfgfiles_path ${TIV_HOME}\nalt_config\nconfig_type full\n\nThe same update is made in the V8.0 information center.\n\nID: 756074\n Problem : Topic, Installing IBM WebSphere SDK Java Technology\n Edition Version 7.0 using the command line, fails to remind\n the reader that when using the imcl command to install the\n offering, the option needs to specify\n the appropriate WebSphere Application Server installation\n path. As a result, the reader can specify the wrong\n installation path.", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q042", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Resolution: Topic, Installing IBM WebSphere SDK Java\n Technology Edition Version 7.0 using the command line, is\n updated to add the following note:\n\nNote: For installation_directory, specify the appropriate\n WebSphere Application Server installation path on which to\n install IBM WebSphere SDK Java Technology Edition Version 7.0.\n\nID: 756128\n Problem : Customer is unable to find documentation that states\n that you are unable to\n install Plugins under the IHS_HOME directory. Customers that\n try to do this using\n the Installation Manager GUI, found that they were unable to\n proceed\n due to a message that states:\n\n\"The installation directory for the new \"Plugins\" package\n group must not be a parent or sub-directory of a previously\n used installation directory.\"\n\nThe information center needs to document that you are unable\n to install Plugins under the IHS_HOME directory.\n\nResolution: Topics, Installing the Web Server Plug-ins using\n the command line, Installing and uninstalling the Web Server\n Plug-ins on distributed operating systems, and Installing the\n Web Server Plug-ins using response files, have been updated by\n adding the following note:\n\nNOTE: The target directory for the plug-in must be an empty\n directory and cannot be installed in a subdirectory of the IBM\n HTTP Server target directory.\n\nThis update also applies to the same topics in the V8.0\n information center.\n\nID: 756310\n Problem : Topic, Storing transaction and compensation logs in\n a relational database for high availability, has vague and\n misleading documentation concerning requirements on the\n application server in the peer recovery group (cluster) and\n its use of a single datasource for logs. This vague\n information must be clarified.\n\nResolution: Topic, Storing transaction and compensation logs\n in a relational database for high availability, is updated\n with the following note:\n\nImportant: Each server in the cluster must be able to\n reference the datasource that a given application server\n references for its logs. That is, the datasource must be\n scoped to the cluster (or cell). This scoping allows peer\n recovery.\n\nThis update also applies to the same topic in the V8.0\n informaton center.\n\nID: 756590\n Problem : Topic, Configuring client reroute for applications\n that use DB2 databases, has an incorrect statement that says\n for the following properties:\n\nRetry interval for client reroute\n Maximum retries for client reroute", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q042", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Attention: If you do not specify a value for these properties,\n DB2\n failover processing (client rerouting) does not occur.\n\nFor V8.0 and V8.5, client rerouting continues to occur even if\n you do not specify the properties: Retry interval for client\n reroute AND Maximum retires for client reroute.\n\nResolution: Topic, Configuring client reroute for\n applications that use DB2 databases, is updated. The\n ATTENTION currently documented that says, ----If you do not\n specify a value for these properties, DB2\n failover processing (client rerouting) does not occur.--- is\n removed from the topic.\n\nThis update also applies to the V8.0 version of the\n information center topic.\n\nID: 756014\n Problem : he online documentation for IBM WebSphere Edge\n components is\n misleading and should be updated to prevent customer confusion\n and\n misconfiguration. The latest versions of the Load Balancing\n Guide contains\n incorrect information and is missing vital information that is\n required\n to configure the environment.\n\nThe concepts guide for Version 8.5.5 should\n be updated so as to reflect that NAT, CBR and SS is now\n supported.\n\nWe can also add the additional note on users not needing to\n configure\n cluster address using ifconfig command in user space load\n balancer.\n\nResolution: The Edge plugin has been updated to reflect the\n Load Balancer 8.5.5 changes in the concepts section.\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q042", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI10514\nREPORTED COMPONENT NAME\n WEBSPHERE APP S\nREPORTED COMPONENT ID\n 5724J0800\nREPORTED RELEASE\n 850\nSTATUS\n CLOSED DOC\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-01-29\nCLOSED DATE\n 2014-03-23\nLAST MODIFIED DATE\n 2014-08-20\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q042", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q042", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Customer has uploaded the following IBM WebSphere SDK Java\n Technology Edition 7.1 fix package to the IBM Installation\n Manager Repository on the PureApplication System:\n\n7.1.3.10_0001-WS-IBMWASJAVA-Linux.zip\n\nThe package is not available from the instance console\n (maintenance operation) under \"maintenance fixes\" or\n \"maintenance fixpacks\". Since they cannot select it, they can\n not apply the fix to the virtual machine instances.", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q042", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Use imcl manually to install the fix as described here:\n\n Why am I unable to install IBM WebSphere SDK Java Technology\n Edition 7.1 fix package from PureApplication System maintenance\n operations panel?\n https://developer.ibm.com/answers/questions/263001/why-am-i-unab [https://developer.ibm.com/answers/questions/263001/why-am-i-unab]\n le-to-install-ibm-websphere-sdk-java/\n\n See also:\n Installation Manager Update Packages dialog does not list\n WebSphere Liberty\n https://developer.ibm.com/answers/questions/272058/installation- [https://developer.ibm.com/answers/questions/272058/installation-]\n manager-update-packages-dialog-does-n/\n\n To confirm that APAR IT14680 is the root cause of a problem\n where a fix is not listed properly on the Manage > Maintenance\n page:\n\n Confirm that Installation Manager lists the fix as available:\nSSH onto the virtual machine where the fix needs to be applied\nUpdate your SSH tool settings so that the commands you issue\n and their output are saved in a file\nIssue the following commands\n\n sudo -u virtuser ./imcl listAvailableFixes \nrepositories http://IBMWorkloadDeployer:8585/IMRepository/Compo [http://IBMWorkloadDeployer:8585/IMRepository/Compo]\n\n where is the name of the fix to be applied, for\n example:\n\n sudo -u virtuser ./imcl listAvailableFixes\n com.ibm.websphere.liberty.ND.v85_8.5.5009.20160227_1546\nrepositories http://IBMWorkloadDeployer:8585/IMRepository/Compo [http://IBMWorkloadDeployer:8585/IMRepository/Compo]\n\n If an external Installation Manager Repository is also\n available, also issue\n\n sudo -u virtuser ./imcl listAvailableFixes \nrepositories http:// [http://]\n\n where is the name of the fix to be applied, and\n is the URL for the external IM\n repository.\n\n Enable tracing to collect logs with fixpack calculation\n information included:\nSelect System > Workload Troubleshooting\nAdd a trace for\n \"com.ibm.maestro.mgmt.resources.IfixMgmtResource\"\nSet the trace level to ALL\nRecreate the problem\nWait 2 hours\nSelect System > Workload Troubleshooting again\nDownload All Logs\n (take care *not* to choose Download Latest Logs)\nProvide the trace.zip file to IBM support\n\n To review the logs for information\nUnzip trace.zip and look for servers.zip\nUnzip servers.zip\nUnzip the Kernel Services logs inside servers.zip\nReview the Kernel Services logs for log entries from\n IfixMgmtResource.", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q042", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "The code checking if a fix is applicable to a product installed\n on a virtual machine was expecting to compare versions for\n maintenance in the V.R.M.F formart (version, release,\n maintenance, fix). The Java fix had an unhandled version\n format.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q042", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A code fix is being provided in PureApplication System version\n 2.2.0.0.\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q042", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT14680\nREPORTED COMPONENT NAME\n PAPP SYS 8382 I\nREPORTED COMPONENT ID\n 5725G3200\nREPORTED RELEASE\n 210\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-04-06\nCLOSED DATE\n 2016-04-07\nLAST MODIFIED DATE\n 2017-01-26\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q042", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n PAPP SYS 8382 I\nFIXED COMPONENT ID\n 5725G3200", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q042", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R220 PSY\n UP", "logical_doc_id": 3, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q042", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "WebSphere Application Server is shipped as a component of IBM Business Process Manager, WebSphere Process Server, and WebSphere Lombardi Edition. WebSphere Application Server Liberty is shipped as a component of the optional BPM component Process Federation Server. Information about security vulnerabilities affecting IBM WebSphere Application Server Traditional and IBM WebSphere Application Server Liberty have been published in a security bulletin.", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q042", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Please consult the Security Bulletin: WebSphere Application Server update of IBM\u00ae SDK Java\u2122 Technology Edition [http://www.ibm.com/support/docview.wss?uid=swg22003016] [http://www.ibm.com/support/docview.wss?uid=swg21998379] for vulnerability details and information about fixes.\nAdditionally, IBM BPM, and WPS might be affected by the following vulnerability:\n\nCVEID:CVE-2017-1289 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1289]\nDESCRIPTION: IBM SDK, Java Technology Edition is vulnerable XML External Entity Injection (XXE) error when processing XML data. A remote attacker could exploit this vulnerability to expose highly sensitive information or consume memory resources.\nCVSS Base Score: 8.2\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/125150 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125150]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L)", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q042", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Business Process Manager V7.5.0.0 through V7.5.1.2\nIBM Business Process Manager V8.0.0.0 through V8.0.1.3\nIBM Business Process Manager V8.5.0.0 through V8.5.0.2\nIBM Business Process Manager V8.5.5.0\nIBM Business Process Manager V8.5.6.0 through V8.5.6.0 CF2\nIBM Business Process Manager V8.5.7.0 through V8.5.7.0 Cumulative Fix 2017.03\n\nNote that 8.5.7.0 Cumulative Fix 2017.03 cannot automatically install interim fixes for the base Application Server. It is important to follow the complete installation instructions and manually ensure that recommended security fixes are installed.\n\nFor earlier and unsupported versions of the products, IBM recommends upgrading to a fixed, supported version of the product.", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q042", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q042", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q042", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 18 May 2017: Original Version Published\nThe 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\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Express Security Linux, Windows 8.5.7.CF201703, 8.5.7.CF201612, 8.5.7.CF201609, 8.5.7.CF201606, 8.5.7, 8.5.6.2, 8.5.6.1, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration IBM Business Process Manager Standard Security AIX, Linux, Solaris, Windows 8.5.7.CF201703, 8.5.7.CF201612, 8.5.7.CF201609, 8.5.7.CF201606, 8.5.7, 8.5.6.2, 8.5.6.1, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration WebSphere Lombardi Edition Security AIX, HP-UX, Linux, Linux zSeries, Linux/x86, Solaris, Windows, Windows Vista, Windows XP 7.2.0.5, 7.2.0.4, 7.2.0.3, 7.2.0.2, 7.2.0.1, 7.2 Business Integration WebSphere Process Server AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS 7.0.0.5, 7.0.0.4, 7.0.0.3, 7.0.0.2, 7.0.0.1, 7.0", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q158", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "A FIX IS AVAILABLE\nRational DOORS and DOORS Web Access Fix Pack 1 (9.6.0.1) for 9.6 [http://www-01.ibm.com/support/docview.wss?uid=swg24037946]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q158", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Currently the documentation for format of the dbadmin command in\n \"Configuring the Rational DOORS database server\" has Quotation\n marks for all -dcnBrokerUri and -dcnChannelName parameters.\n\n Link:\n http://pic.dhe.ibm.com/infocenter/doorshlp/v9r5m2/index.jsp?topi\n c=%2Fcom.ibm.rational.dwa.install.doc%2Ftopics%2Ft_setupddbs.htm [http://pic.dhe.ibm.com/infocenter/doorshlp/v9r5m2/index.jsp?topic=%2Fcom.ibm.rational.dwa.install.doc%2Ftopics%2Ft_setupddbs.htm]\n l\n\n Format specified in the above Link: dbadmin -dcnEnable -data\n port@DOORSserver -P server_password -dcnBrokerUri\n tcp://broker:61616 -dcnChannelName dcn -dwaHost\n DWAserver dwaPort port dwaProtocol http or https\n\n However, an error \"CRCRD7222E Unable to connect to broker\" is\n displayed when accessing File > OSLC > Working Sets\n if the dbadmin command has been run with the value for\ndcnBrokerUri parameter enclosed within double quotes.\n Hence, these double quotes need to be removed for the value of\ndcnBrokerUri parameter.\n\n It has also been observed that if the value of -dcnChannelName\n which is dcn by default, is enclosed within double quotes,\n though the ETL job completes and says its successful, no data\n would have been transferred to the Data Warehouse. Hence, the\n double quotes need to be removed for the value of\ndcnChannelName parameter.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q158", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nUsers of DOORS Web Access *\n\nPROBLEM DESCRIPTION: *\nCurrently the documentation for format of the dbadmin *\ncommand in *\n\"Configuring the Rational DOORS database server\" has *\nQuotation *\nmarks for all -dcnBrokerUri and -dcnChannelName parameters. *\n*\nLink: *\nhttp://pic.dhe.ibm.com/infocenter/doorshlp/v9r5m2/index.jsp? *\ntopi *\nc=%2Fcom.ibm.rational.dwa.install.doc%2Ftopics%2Ft_setupddbs *\n.htm *\nl *\n*\nFormat specified in the above Link: dbadmin -dcnEnable -data *\nport@DOORSserver -P server_password -dcnBrokerUri *\ntcp://broker:61616 -dcnChannelName dcn *\n-dwaHost *\nDWAserver dwaPort port dwaProtocol http or https *\n*\nHowever, an error \"CRCRD7222E Unable to connect to broker\" *\nis *\ndisplayed when accessing File > OSLC > Working Sets *\nif the dbadmin command has been run with the value for *\n-dcnBrokerUri parameter enclosed within double quotes. *\nHence, these double quotes need to be removed for the value *\nof *\n-dcnBrokerUri parameter. *\n*\nIt has also been observed that if the value of *\n-dcnChannelName *\nwhich is dcn by default, is enclosed within double quotes, *\nthough the ETL job completes and says its successful, no *\ndata *\nwould have been transferred to the Data Warehouse. Hence, *\nthe *\ndouble quotes need to be removed for the value of *\n-dcnChannelName parameter. *\n\nRECOMMENDATION: *", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q158", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The documentation has been updated to clarify the current\n behaviour\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q158", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI17630\nREPORTED COMPONENT NAME\n TLOGIC DOORS WE\nREPORTED COMPONENT ID\n 5724V97WA\nREPORTED RELEASE\n 952\nSTATUS\n CLOSED DOC\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-05-09\nCLOSED DATE\n 2014-09-11\nLAST MODIFIED DATE\n 2014-09-11\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q158", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This feature allows users to define scripts to run at Tivoli Monitoring OS agents sites at a defined frequency.", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "(C) Copyright International Business Machines Corporation 2015. All rights reserved.\nComponent: IBM(R) Tivoli(R) Monitoring OS Agents, Version 6.3.0 FixPack 5\n\nDate: 30 June 2015\n\nContents:\n\n1.0 Introduction\n1.1 Quick Start\n2.0 New Attribute groups\n3.0 Parameters in OS agent environment files\n4.0 Parameters in property file\n5.0 Examples of property file\n6.0 Examples of private situations\n7.0 Custom Scripts and Custom Scripts Runtime workspaces\n8.0 Known problems and limitations\n9.0 Troubleshooting\n10.0 Quick Start Scenario\n\n1. Introduction\n\nThis feature allows users to define scripts to run at Tivoli Monitoring OS agents sites at a defined frequency.\n\nThe feature is enabled by default. The administrator can enable/disable it by setting a new environment variable\nKXX_FCP_SCRIPT=true/false (default true)in the agent configuration file, where XX can be:\nLZ for Linux OS agent\nUX for Unix OS agent\nNT for Windows OS agent\n\nThis is an overview of the scripting feature; details will be provided in the following sections.\n\nThe OS agent loops, at a configurable interval, looking for script definition property files (*.properties) in a configurable directory path.\nThe property files are parsed and OS Monitoring Agent spawns a new process named \u201cfcp_daemon\u201d if at least one valid script definition is found. This new daemon is responsible for scheduling the script executions and gathering all information regarding running scripts.\n\nAccording to another configurable interval, the OS agent loops getting the execution script results from the fcp_daemon.\nThe OS Agent is able to parse the script standard output, splitting each row in up to 16 attributes.\nAn event is sent for each standard output row of the script and these events can be caught by pure event situations.\n\n1.1 Quick Start\n\nThe feature is enabled with default values as soon as the OS agent is started. The only action to start using the feature is the following:\ncreate a property file under default directory (on Linux/UNIX is $CANDLEHOME/localconfig//scripts_definitions, on Windows is %CANDLE_HOME%\\localconfig\\nt\\scripts_definitions) using as an example the provided template script_property.txt.\n\nOnly two properties are required:\nATTRIBUTE_NAME=Any name used to uniquely identify the script definition inside the property file.\nSCRIPT_PATH_WITH_PARMS=The fully qualified path of the script with arguments.", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Not only shell scripts but also perl and other types of scripts can be used. You just need to specify the full command to execute in the SCRIPT_PATH_WITH_PARMS property.\nFor example, \"perl C:\\IBM\\scripts\\ITM_Custom_Scripts\\date.pl\". In this example you need to make sure that the location of \"perl\" can be resolved by the agent through the PATH variable in its environment. Specify the full path where \"perl\" is installed otherwise.\n\nFurther properties and details can be found in this document and in the template script_property.txt under $CANDLEHOME/localconfig/lz/scripts_definitions.\n\n2. New Attribute groups\n\nTwo new attribute groups have been added for this feature as detailed below. Statistic and execution data of all the scripts are stored in these two tables. The name of the property file (Property_File) and the attribute name defined in the property file (Attribute_Name) are the 2 key fields of these two tables. These two keys must be used in situation conditions to filter rows related to a specific script.\n\nAttribute group: KXX_Custom_Scripts (multiple rows), table: KXXSCRPTS (sampled).\nDescription: Configuration and statistic data gathered using custom scripts. It contains a row for each defined script, information on the fcp_daemon and on property files:", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Attribute Size Description\n=========================== ===== =========================\nSystem_Name 32 This is the managed system name of the agent.\nTimestamp 16 This is the local time when the data was collected.\nProperty_File 256 The name of the property file.\nAttribute_Name 96 The attribute name that is defined in the properties file. The attribute is used for metric identification.\nScript_Name 512 The name of the script.\nScript_Path 512 The fully qualified path name of the script with arguments.\nCustom_Name 96 The custom name that is defined in the properties file. It is used for custom reporting.\nStandard_Output_Type 4 Standard output type of the script.\nStatus_Code 4 The status of the script. It includes general errors, configuration errors, the status or the execution code returned by the\nScript Provider.\nExecution_Start 16 The time when the last execution of this script started.\nExecution_Duration 4 The duration of the last execution of this script, in seconds. When timing out, the value of the configured timeout is returnd.\nAverage_Execution_Duration 4 The average duration, in seconds, of all the execution of the script.\nRefresh_Interval 4 The interval, in seconds, that the agent attempts to start this script.\nNumber_of_Collections 4 The count of execution attempts of this script since agent started.\nIntervals_Skipped 4 The count of occurrences where an execution of this script is skipped because the previous execution is still running.\nProperty_Group 64 The name of the property group.\nReturn_Code 4 Integer value returned by the Script.\nCust_Label_Str1 16 Label for custom string attribute #1\nCust_Label_Str2 16 Label for custom string attribute #2\nCust_Label_Str3 16 Label for custom string attribute #3\nCust_Label_Str4 16 Label for custom string attribute #4\nCust_Label_Str5 16 Label for custom string attribute #5\nCust_Label_Int1 16 Label for custom integer attribute #1\nCust_Label_Int2 16 Label for custom integer attribute #2\nCust_Label_Int3 16 Label for custom integer attribute #3\nCust_Label_Int4 16 Label for custom integer attribute #4\nCust_Label_Int5 16 Label for custom integer attribute #5\nCust_Label_Float1 16 Label for custom floating point attribute #1\nCust_Label_Float2 16 Label for custom floating point attribute #2\nCust_Label_Float3 16 Label for custom floating point attribute #3\nCust_Label_Float4 16 Label for custom floating point attribute #4\nCust_Label_Float5 16 Label for custom floating point attribute #5\nStandard_Error 2048 Script Standard Error in a unique row", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "In addition to script definitions, the table may report rows to return errors found on property files and they are identified by @ANY@ as Attribute_Name. Moreover, a row is always used to report the status of fcp_daemon and it is identified by @ANY@ as Property_File and @ANY@ as Attribute_Name.\n\nAttribute group: KXX_Custom_Scripts_Runtime (multiple rows), table: KXXSCRRTM (pure).\nDescription: Data gathered using custom scripts. It contains the output rows of the scripts currently running:\n\nAttribute Size Description\n======================= ==== =========================\nSystem_Name 32 This is the managed system name of the agent.\nTimestamp 16 This is the local time when the data was collected.\nProperty_File 256 The name of the property file.\nAttribute_Name 96 The attribute name that is defined in the properties file. The attribute is used for metric identification.\nScript_Path 512 The fully qualified path of the script.\nCustom_Name 96 The custom name that is defined in the properties file. It is used for custom reporting.\nReturn_Code 4 Integer value returned by the Script.\nRow_Number 4 Output row number.\nStandard_Output_Type 4 Standard output type of the script.\nStandard_Output_String 2048 Script Standard Output in String Format.\nStandard_Output_Integer 8 Script Output in Integer Format\nStandard_Output_Float 8 Script Output in Floating Point Format (2 decimals).\nCust_Attr_Str1 64 Custom string attribute #1\nCust_Attr_Str2 64 Custom string attribute #2\nCust_Attr_Str3 64 Custom string attribute #3\nCust_Attr_Str4 64 Custom string attribute #4\nCust_Attr_Str5 64 Custom string attribute #5\nCust_Attr_Int1 8 Custom integer attribute #1\nCust_Attr_Int2 8 Custom integer attribute #2\nCust_Attr_Int3 8 Custom integer attribute #3\nCust_Attr_Int4 8 Custom integer attribute #4\nCust_Attr_Int5 8 Custom integer attribute #5\nCust_Attr_Float1 8 Custom floating point (2 decimals) attribute #1\nCust_Attr_Float2 8 Custom floating point (2 decimals) attribute #2\nCust_Attr_Float3 8 Custom floating point (2 decimals) attribute #3\nCust_Attr_Float4 8 Custom floating point (2 decimals) attribute #4\nCust_Attr_Float5 8 Custom floating point (2 decimals) attribute #5\n\nNote: different status conditions can be monitored using the Status_Code field in the statistic table KXX_Custom_Scripts.\nThe following detailed list provides different values for the Status_Code field:\n\nInitial general statuses\nUNKNOWN_ERROR (status code=0) --> Error\nNO_ERROR (status code=1) --> Informational", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "General daemon statuses\nFEATURE_NOT_ENABLED (status code=40) --> Informational\nDAEMON_STARTING (status code=2) --> Informational\nDAEMON_STARTED (status code=3) --> Informational\nDAEMON_STOPPING (status code=4) --> Informational\nDAEMON_STOPPED (status code=5) --> Informational\nDAEMON_STOPPING_AT_AGENT_STOP (status code=6) --> Informational\nDAEMON_STOPPED_AT_AGENT_STOP (status code=7) --> Informational\nDAEMON_ERROR (status code=8) --> Error\nDAEMON_ERROR_NO_RESTART (status code=9)-> Fatal Error\n\nGeneral directory statuses\nERROR_OPENING_PROP_DIRECTORY (status code=10) --> Error\nPROP_DIRECTORY_NOT_FOUND (status code=11) --> Error\nNO_SCRIPT_DEFINED (status code=12)--> Warning\n\nProperty file statuses\nPROP_FILE_NOT_FOUND (status code=13) --> Error\nERROR_OPENING_PROP_FILE (status code=14) --> Error\n\nScript definition statuses\nSCRIPT_ADDED (status code=15) --> Informational\nSCRIPT_CHANGED (status code=16) --> Informational\nSCRIPT_REMOVED (status code=17) --> Informational\nSCRIPT_INACTIVE (status code=18) --> Informational\nNO_SCRIPT_PATH (status code=21)--> Error\nSCRIPT_PATH_INVALID (status code=22)--> Error\n\nExecution statuses from the fcp_daemon\nFACTORY_UNKNOWN_ERROR (status code=23) --> Error\nFACTORY_NO_ERROR (status code=24)--> Informational\nGENERAL_ERROR (status code=25)--> Error\nOBJECT_NOT_FOUND (status code=26)--> Error\nOBJECT_CURRENTLY_UNAVAILABLE (status code=27)--> Error\nNO_INSTANCES_RETURNED (status code=28)--> Error\nNO_RESPONSE_RECEIVED (status code=29)--> Error\nAUTHENTICATION_FAILED (status code=30)--> Error\nACCESS_DENIED (status code=31)--> Error\nTIMEOUT (status code=32)--> Error\nNOT_IMPLEMENTED (status code=33)--> Error\nRESPONSE_TOO_BIG (status code=34) --> Error\nGENERAL_RESPONSE_ERROR (status code=35)--> Error\nSCRIPT_NONZERO_RETURN (status code=36)--> Error\nSCRIPT_NOT_FOUND (status code=37)--> Error\nSCRIPT_LAUNCH_ERROR (status code=38)--> Error\nINVALID_TOKEN_TYPES(status code=39) --> Error\n\n3. Parameters in OS agent environment files\n\nIt is possible to customize the feature setting parameters in the OS agent environment files:\n$CANDLEHOME/config/lz.ini file for the Linux OS agent\n$CANDLEHOME/config/ux.ini for the UNIX OS agent\n%CANDLE_HOME%\\TMAITM6_x64\\KNTENV for Windows 64bit OS agent\n%CANDLE_HOME%\\TMAITM6\\KNTENV for Windows 32bit OS agent\n\nThe scripting feature is enabled by default. To disable it set:\nKXX_FCP_SCRIPT=false", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Other parameters can be defined inside the agent environment files based on specific needs:\nKXX_FCP_SCRIPT_DEFINITIONS (default location on Linux/UNIX is $CANDLEHOME/localconfig//scripts_definitions, on Windows it is %CANDLE_HOME%\\localconfig\\nt\\scripts_definitions)\nThe location where property files are stored.\nKXX_FCP_SCRIPT_INTERVAL (default 60 sec)\nOS agent uses the value of this variable as loop interval in seconds to check execution of running scripts and it sends events if the filter condition is satisfied. The minimum value is 30 seconds, the maximum value is 300 seconds. Invalid values will be reset to the default.\nNote: this parameter is ignored if KXX_FCP_SCRIPT_SYNC_INTERVALS is set to USE_SCRIPT (see definition below).\nKXX_FCP_SCRIPT_SYNC_INTERVALS (USE_AGENT|USE_SCRIPT|NO - default USE_AGENT)\nIf the agent looping interval defined by KXX_FCP_SCRIPT_INTERVAL is bigger than the script execution frequency, it can happen that data produced by some of the script execution loops is lost.\nTo avoid this behaviour the script execution frequency can be synchronized with the agent looping interval setting the KXX_FCP_SCRIPT_SYNC_INTERVALS to:\nUSE_AGENT; the value of each script execution frequency is forced to be the maximum between KXX_FCP_SCRIPT_INTERVAL and EXECUTION_FREQUENCY defined in its property file.\nUSE_SCRIPT; the agent looping interval is dynamically set to the minimum frequency value (EXECUTION_FREQUENCY in property file) between all of the defined scripts . The value set by KXX_FCP_SCRIPT_INTERVAL is ignored. The frequency of the scripts remain the ones defined in the property files. When using USE_SCRIPT, the agent looping interval may change every time a script definition is added, changed or removed. In any case, it cannot be lower than the value set by KXX_FCP_OVERRIDE_MIN_FREQUENCY_LIMIT or bigger than 300 seconds.\nNO; no synchronization is performed and some execution results could be lost.\nKXX_FCP_SCRIPT_DEFINITIONS_CHECK_INTERVAL (default 300 sec)\nAt startup and at every interval defined by this variable, the OS agent checks for any changes in scripts or property files.\nNote that if KXX_FCP_SCRIPT_DEFINITIONS_CHECK_INTERVAL is less than the agent looping interval it will be reset to the agent looping interval. The maximum allowed value is the default, 300 seconds.\nKXX_FCP_USER (default OS agent user)\nThis parameter is valid only on linux and unix platforms. It defines the user used to spawn fcp_deamon process if different from OS agent process user; all the scripts are executed by this user. Note that the user owner of the OS agent must have correct permission to spawn the fcp_daemon process. On windows a different user must be defined as login of the service \"Monitoring Agent for Windows OS - FCProvider\". The user must have \"Full Control\" permission to CANDLE_HOME and scripts repository directories. For more information please refer to official IBM Monitoring documentation:\nhttp://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/oswin/running_as_a_non-admin_user.htm [http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/oswin/running_as_a_non-admin_user.htm]\nKXX_FCP_MAX_CDP_DP_THREAD_POOL_SIZE (default 10)\nIt defines the maximum concurrent number of scripts to be executed. Maximum value is 32.\nKXX_FCP_MAX_DAEMON_RESTARTS (default 4)\nThe OS agent watches the fcp_daemon: if an abnormal exit of process occurs, the OS agent restarts it. This is done for the KXX_FCP_MAX_DAEMON_RESTARTS (times at a day).\nThe value 0 must be used to avoid the restart; if -1 is set, the OS agent retries to restart fcp_daemon forever. The restart counter is reset at OS agent restart.\nKXX_FCP_SEND_SCRIPT_RUNTIME_EVENTS (default: true)\nIf set to false, the OS agent stops sending events for each row of script standard output. In this case script outputs are visible on TEP console workspaces but no situations will be displayed and no historical collection data will be collected.\nKXX_FCP_OVERRIDE_MIN_FREQUENCY_LIMIT (default: 5 seconds)\nIt is used when KXX_FCP_SCRIPT_SYNC_INTERVALS is set to USE_SCRIPT. In this condition, it sets the minimum value of the OS agent looping interval.\nUsing low values for the the OS agent looping interval (less than 5 seconds) is highly invasive and can impact OS agent performances. If a frequent data collection is needed (e.g. every second), it is strongly suggested to customize a script that caches data at the needed frequency and returns the collected data to the OS agent at an higher interval (e.g. every 60 seconds).", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "The following Agent Builder (CDP) variables can also be used to control the behavior of the fcp_daemon:\nCDP_DP_REFRESH_INTERVAL (default 60 sec) Global script scheduled start time. Used if the frequency is not passed in the script property file.\nCDP_DP_SCRIPT_TIMEOUT (default 30 sec) Global script execution maximum time. When the execution time of a script exceeds this limit, its Status_Code is set to TIMEOUT\nCDP_DP_KILL_ORPHAN_SCRIPTS (Y|N - default N) Global behaviour used by fcp_daemon process for timing out scripts. When set to 'Y', the scripts are killed, otherwise they are abandoned. This value is ignored for a specific script if the KILL_AFTER_TIMEOUT key is set in the script property file\nCDP_MAXIMUM_ROW_COUNT_FOR_CPCI_DATA_RESPONSES (default 1000) Global value added for performance reasons to limit the maximum number of output rows returned by the scripts. Additional rows after this limit are ignored. Allowed values are positive integer. Invalid values means no limit.\n\nThe fcp_daemon also supports the other environment variables used to control Agent Builder agents. For a complete list see the official Agent Builder documentation here:\nhttp://publib.boulder.ibm.com/infocenter/tivihelp/v61r1/topic/com.ibm.itm.doc_6.3/agentbuilder63_user.pdf [http://publib.boulder.ibm.com/infocenter/tivihelp/v61r1/topic/com.ibm.itm.doc_6.3/agentbuilder63_user.pdf]\n\n4. Parameters in property files", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "The KXX_FCP_SCRIPT_DEFINITIONS directory contains a list of *.properties files. Each property file contains a list of\nscripts to run with respective properties in the form of key=value. The properties that can be defined (case in-sensitive) are:\nATTRIBUTE_NAME (Required - string max 256 characters).\nIt is a name of your choice that defines a specific script and its attributes. The characters that can be used for the\nATTRIBUTE NAME name can be alphabetical, numeric and only the underscore can be used as a special character. If other special characters (even a blank is considered this way) are used they get converted into underscore (_).\nWhen multiple scripts are listed inside the same property file, more different ATTRIBUTE_NAME must be defined (one for each script). It must be the first value specified for each defined script and delimits the start of the properties set for the specific script until the next ATTRIBUTE_NAME.\nSCRIPT_PATH_WITH_PARMS (Required - string max 512 characters).\nIt defines the full path to the script with parameters, separated by a blank. No special characters can be used in the script path name.\nValues containing blanks must be enclosed in single (') or double quotes (\").\nEnvironment variables can be passed, but only enclosed in ${...} for all the platforms. Environment variables must be available in the OS agent process context.\nEXECUTION_FREQUENCY (Optional - default 60 sec).\nIt indicates the script execution frequency.\nCUSTOM_NAME (Optional - string max 256 characters)\nThe user can fill it with a description of the script.\nIS_ACTIVE (true|false - Optional - default true).\nIt activates the script. If false, the script is not executed.\nDISABLE_USE_AGENT_SYNC (true|false - Optional - default false). If true, the EXECUTION_FREQUENCY of the script is respected also if the global variable KXX_FCP_SCRIPT_SYNC_INTERVALS is set to USE_AGENT.\nKILL_AFTER_TIMEOUT (true|false - Optional - default value defined by the CDP_DP_KILL_ORPHAN_SCRIPTS variable).\nWhen true the script is killed after timeout (a timeout occurs when script execution is greater than the value specified by CDP_DP_SCRIPT_TIMEOUT parameter in OS agent configuration file) otherwise it is ignored. In both cases no data is collected. Note that when KILL_AFTER_TIMEOUT is set, only the script defined in property file is killed and not child processes (if any) spawned by the script. This feature is not supported by Solaris and Windows 32 bit OS agents and any timing out scripts are abandoned.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Output rows returned by a script are parsed. The script returns a standard output (called hereafter as first token). When the script returns more values in the output row they are added as additional tokens for a maximum of 5 strings, 5 integers and 5 floats following a predefined syntax as described below:\nOUTPUT_TYPE (STRING|INTEGER|FLOAT - Optional - default string). It defines the type of the first token returned by each row of the script;\nOUTPUT_TYPE can be:\n1. STRING (default): strings up to 2048 characters. When used, the \"Standard_Output_String\" attribute of KXX_Custom_Scripts_Runtime is filled in by the first token.\n2. INTEGER: allows getting numeric values between -9223372036854775806 and 9223372036854775806. When used, the \"Standard_Output_Integer\" attribute of KXX_Custom_Scripts_Runtime is filled in by the first token.\n3. FLOAT: allows getting numeric values between -92233720368547758.06 and 92233720368547758.06,(with 2 decimal\nprecision). When used, the \"Standard_Output_Float\" attribute of KXX_Custom_Scripts_Runtime is filled in by the first token.\nTOKEN_TYPES (STRING|INTEGER|FLOAT - Optional).\nIt defines the output type of additional tokens after the first one. The user can define a maximum of 5 strings, 5 integers and 5 floats. It is a list of types separated by commas:\n,,\u2026\ntoken_type can be empty or one from (case insensitive):\nSTRING or S\nINTEGER or I\nFLOAT or F\nIf is empty, the corresponding token is skipped.\nExamples of the same valid layouts:\nTOKEN_TYPES=S,I,S,,,F,,F,F\nTOKEN_TYPES=String,integer,S,,,Float,,f,FLOAT\nTOKEN_LABELS (STRING - maximum 16 characters each label - Optional).\nIt defines the labels of the tokens defined in TOKEN_TYPES. This value is a list of token labels separated\nby commas, and must correspond to the tokens defined by TOKEN_TYPES.\ne.g.:\nTOKEN_TYPES=S,I,S,,,F,,F,F\nTOKEN_LABELS=Cpu Name,Cpu number,Description,,,value 1,,value 2,value 3\nIt is ignored if TOKEN_TYPES is not set.\nTOKEN_SEPARATOR (Optional - default semicolon \";\").\nIt sets the string to be used as separator to split the output row in tokens. It is ignored if TOKEN_TYPES is not set. Empty value (blank) is accepted as separator and multiple consecutive blanks in output rows are considered as a single one.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "The following two parameters allow you to filter the rows output of a script; they are applied by the OS agent only to the first token and they must be used together:\nFILTER_VALUE (Optional).\nThe value used for comparison. It is required if FILTER_OPERATOR is defined.\nIf the OUTPUT_TYPE is a string, the filter value must reflect exactly the string value returned by the script that is intended to be filtered, without any additional quotes (no wildcards allowed).\nFILTER_OPERATOR (Optional).\nThe operator used for the comparison. It is required if FILTER_VALUE is defined. Accepted FILTER_OPERATOR values include:\n= (equal to)\n!= (different from)\n> (bigger than) only for numeric type\n>= (not lower than) only for numeric type\n< (lower than) only for numeric type\n<= (not bigger than) only for numeric type\n\n5. Examples of property file\n\n#First script definition: script ex_script1.sh is launched every 150 seconds, it returns float values and only the output rows equal to 0.5 will be considered by the agent.\n\nATTRIBUTE_NAME=sample1\nSCRIPT_PATH_WITH_PARMS=/opt/ibm/itmd4255a/localconfig/lz/scripts_definitions/ex_script1.sh\nEXECUTION_FREQUENCY=150\nOUTPUT_TYPE=FLOAT\nFILTER_VALUE=0.5\nFILTER_OPERATOR==\n\n#Second script definition: script ex_script2 is launched every 60 seconds, it returns integer values and only the rows different from 0 will be considered by the agent.\n\nATTRIBUTE_NAME=ex_script2\nSCRIPT_PATH_WITH_PARMS=${CANDLE_HOME}/tmp/check_out.sh\nEXECUTION_FREQUENCY=60\nOUTPUT_TYPE=INTEGER\nFILTER_VALUE=0\nFILTER_OPERATOR=!=\n\n#Third script definition: script ex_script3.sh is launched every 120 seconds with 3 input parameters (the first input parameter is an integer, the second and third are string). It's killed if it hangs or if the execution time is greater than the timeout value.\n\nATTRIBUTE_NAME=ex_script3\nSCRIPT_PATH_WITH_PARMS=/opt/scripts/ex_script3.sh 1 \"second input parameter\" \"third input parameter\"\nEXECUTION_FREQUENCY=120\nOUTPUT_TYPE=STRING\nKILL_AFTER_TIMEOUT=TRUE\n\n#Fourth script definition: script cpu_mem_percentage.sh is launched every 50 seconds and returns the cpuid as standard output string and 2 float for Idle and Used CPU percentage and 2 integers for Memory and Virtual Memory usage. The pipe is used as separator to parse the output. An example of row that must be returned by the script is:\ncpu2|35,5|65,5|3443|123800\n\nATTRIBUTE_NAME=cpu and mem Usage\nSCRIPT_PATH_WITH_PARMS=${SCRIPT_HOME}/cpu_mem_percentage.sh\nOUTPUT_TYPE=STRING\nTOKEN_TYPES=F,F,I,I\nTOKEN_LABELS= Idle CPU %, Used CPU %, Virt MEM used MB, MEM used MB\nTOKEN_SEPARATOR=|\nEXECUTION_FREQUENCY=50\n\n6. Examples of private situations", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "The private situations definitions can be inserted into the xx_situations.xml under $CANDLEHOME/localconfig/lz for linux or $CANDLEHOME/localconfig/ux for unix or %CANDLE_HOME%\\localconfig\\nt for Windows to monitor scripts execution.\nExamples below are for the Linux OS agent:\n\n\n\nFCP_CheckLOGFileExists_pr\n\n\n\n\n\n\n\nFCP_ScriptRetCode_pr\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n7. Custom Scripts and Custom Scripts Runtime Workspaces\n\nA new OS agent navigation item has been added in the TEP console. It contains two workspaces: \"Custom Scripts\" and \"Custom Scripts Runtime\".\n\n\"Custom Scripts\" workspace contains the following views:\n\"Factory Daemon Status\" table view showing informational/warning/error events related to the fcp_daemon process.\n\"Properties Files error\" table view showing problems related to property files.\n\"Number of execution per script\" bar chart view summarizing the executions of defined scripts\n\"Defined Scripts\" table view showing detailed information of defined scripts.\n\n\"Custom Scripts Runtime\" workspace is called clicking on the anchor of a specific script and provides information on script execution. The views provided by default on the TEP console are to be intended as example workspaces with all available custom attributes. Users can duplicate and customize workspaces to filter out fields that are not needed according to the output returned by their scripts.\n\n8. Known problems and limitations", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "The Scripting Feature is not supported on Windows 2003 64-bit systems.\nKill after timeout does not work on Solaris and Windows 32 bit OS agents.\nThe fcp_daemon may stop executing scripts in Windows 32 bit If some scripts do not complete within the time out period and the user has turned on intensive tracing. If this happens the data reported on the TEP will reflect the last time the script was actually run. It is also possible that the OS agent will stop returning data. Terminating the fcp_daemon process will allow the agent to resume proper operation.\nSCRIPT_NONZERO_RETURN is returned instead of SCRIPT_NOT_FOUND or SCRIPT_LAUNCH_ERROR on Solaris.\nThe scripting feature does not provide full Native Language Support; some issues may be found using Nationalized characters in property files or script outputs.\nOn windows OS agent there is no possibility of executing scripts residing on a mapped network drive.\n\n9. Troubleshooting\n\nStandard KBB_RAS1 variable will apply to the OS agent and to the fcp_daemon processes.\nTo apply a specific trace setting to fcp_daemon only, use the KXX_FCP_KBB_RAS1 variable; when KXX_FCP_KBB_RAS1 is set, the value specified by KBB_RAS1 is ignored by fcp_daemon.\n\nTo trace the operations logged by the OS agent core threads of the feature:\nKBB_RAS1=ERROR (UNIT:factory ALL)\n\nTo trace scripting queries from the ITM server and events sent to the server, add the entries:\n(UNIT:klz34 ALL) (UNIT:klz35 ALL) on Linux OS agent\n(UNIT:kux48 ALL) (UNIT:kux49 ALL) on Unix OS agent\n(UNIT:knt84 ALL) (UNIT:knt85 ALL) on Windows OS agent\n\nTo view tema traces to verify private situation execution, add the entries:\n(UNIT:kraavp all) (UNIT:kraapv all)\n\nTo see the execution of the scripts and how the data from the scripts is being parsed set:\nKXX_FCP_KBB_RAS1=Error (UNIT:command ALL)\n\nTo troubleshoot problems in the communication between the os agent and fcp_daemon add this trace level to both KBB_RAS1 and KXX_FCP_KBB_RAS1:\n(UNIT:cps_socket FLOW) (UNIT:cpci FLOW)\n\nTo see the interaction between the OS agent process and the fcp_daemon in detail add to both KBB_RAS1 and KXX_FCP_KBB_RAS1:\n(UNIT:cps_socket ALL) (UNIT:cpci ALL)\n\n10. Quick Start Scenario\n\nThe following section describes the minimum steps needed to configure a linux OS agent to run 2 custom scripts.\n\nCustom Scripts descriptions", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Let's suppose the user has 2 scripts under a directory /scripts_repo:\ncheckDIRsize.sh that checks the size of a specified directory passed as input parameter. Its output is an integer like the following:\n\n4594740\ncpu_mem_usage.sh that checks the used CPU percentages and used Swap Memory megabytes. Its output is returned in the following form:\n\ncpu1|96,5|23800\n\nwhere the first token is the CPU id, the second token is the used CPU percentage, the third token is the used swap memory in megabyte.\n\nCustomization needed to have the linux OS agent run above scripts\n\nThe feature is enabled with default values as soon as the OS agent is started:\nyou could create one or two property files (.properties)under the default directory $CANDLEHOME/localconfig/lz/scripts_definitions. In this example let's create 2 property files one for each script called checkDIRsize.properties and cpu_mem_usage.properties:\n\n#CheckDIRsize.properties\nATTRIBUTE_NAME=OPT_DIR_SIZE\nSCRIPT_PATH_WITH_PARMS=/scripts_repo/checkDIRsize.sh /opt\nEXECUTION_FREQUENCY=20\nOUTPUT_TYPE=INTEGER\n\n#cpu_mem_usage.properties\nATTRIBUTE_NAME=cpu_mem_usage\nSCRIPT_PATH_WITH_PARMS=/scripts_repo/cpu_mem_percentage.sh\nOUTPUT_TYPE=string\nTOKEN_TYPES=F,I\nTOKEN_LABELS= Used CPU %, Swap MEM used MB\nTOKEN_SEPARATOR=|\nEXECUTION_FREQUENCY=10\nThere is no need to restart the OS agent after adding (or changing) the 2 property files above: the OS agent checks script definition directory with a specified time interval (default value 300 seconds). Open the TEP console and under the \"Custom Scripts\" workspace the scripts details and results are shown.\n\nChange History:\n\n2017-01-09: Added new item under \"8. Known problems and limitations\" that the Scripting Feature is not supported on Windows 2003 64-bit systems.", "logical_doc_id": 2, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q158", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "If a DBRA function references another worksheet cell for a numeric element name, and the cell containing the element name is formatted as anything other than Text, the DBRA function fails.\n\nFor example, this DBRA function references cell D9 for a numeric element name:\n=DBRA(\"ServerName:DimensionName\",D9,\"dimension 2\")\n\nIf cell D9 is formatted as Number, or anything other than Text, the DBRA function will not return an attribute value.\n\nThis issue can become exposed when you paste a numeric value into a worksheet cell that is referenced by a DBRA function for a numeric element name.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "DBRA formula does not return attribute values.", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q158", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To work around this issue, ensure that any cell that is referenced by a DBRA function for an element name is formatted as Text.\n\nYou can also replace any DBRA formulas that include numeric element names with DBRW formulas that reference the }elementsattributes control cube for the dimension from which you want to retrieve attribute values. DBRW formulas do not require numeric element names to be enclosed in quotes, and can handle references to cells that are formatted as either Text or Number.\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q158", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "IBM InfoSphere Data Architect allows to specify default values\n for columns of CHAR datatype (CHAR, VARCHAR, etc.) as a\n character literal or as a character literal enclosed in quotes.\n Despite CHAR columns' default values get automatically enclosed\n in quotes during DDL generation, specifying default value as a\n character literal without quotes may cause subsequent comparison\n against the source database to report this literal to differ\n from correspondent literal in underlying database which is\n always enclosed in quotes.", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q158", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Enclose CHAR columns' default values in quotes.", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q158", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nAll users. *\n\nPROBLEM DESCRIPTION: *\nInfoSphere Data Architect considers a character N in a *\nPhysical Data Model created from forward engineering and a *\ncharacter 'N' in a Physical Data Model created from Reverse *\nEngineering as a difference. This comes up as InfoSphere *\nData Architect tends to add quotes around the character N *\nduring Reverse Engineering. *\n\nRECOMMENDATION: *\nThis problem was fixed in InfoSphere Data Architect v7.5.3.1 *", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q158", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This problem was fixed in InfoSphere Data Architect v7.5.3.1\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q158", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR37810\nREPORTED COMPONENT NAME\n INFO DATA ARCHI\nREPORTED COMPONENT ID\n 5724V1500\nREPORTED RELEASE\n 752\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2010-09-21\nCLOSED DATE\n 2012-06-25\nLAST MODIFIED DATE\n 2012-06-26\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q158", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n INFO DATA ARCHI\nFIXED COMPONENT ID\n 5724V1500", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q158", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R752 PSN\n UP\n\nAIX SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q158", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "SCENARIO:\n 1. Create a new Part or Procuct.\n 2. Create a new parameter of any type.\n 3. Rename the parameter to dot (.)\n .\n OBSERVATION:\n The parameter name which is \".\" is not enclosed within single\n quotes.\n .\n EXPECTED RESULT:\n Parameter name \".\" should be enclosed within single quotes", "logical_doc_id": 5, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q158", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "SCENARIO:\n 1. Create a new Part or Procuct.\n 2. Create a new parameter of any type.\n 3. Rename the parameter to dot (.)\n .\n OBSERVATION:\n The parameter name which is \".\" is not enclosed within single\n quotes.\n .\n EXPECTED RESULT:\n Parameter name \".\" should be enclosed within single quotes", "logical_doc_id": 5, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q158", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "THIS PROBLEM WILL BE FIXED ON CATIA VERSION V5R21 GA level.\n Additional Closure Information:\n INCIDENT DIAGNOSIS:\n A parameter named '.' (dot) was accepted but Knowledge parser\n does not support it. Special character dot is not enclosed\n within single quotes while renaming a user parameter.\n .\n CORRECTION EXPLANATION:\n A parameter named '.' (dot) is now enclosed within single\n quotes.\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q158", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n HD94813\nREPORTED COMPONENT NAME\n CATIA V5 NT>XP\nREPORTED COMPONENT ID\n 569151000\nREPORTED RELEASE\n 519\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2010-03-24\nCLOSED DATE\n 2010-05-26\nLAST MODIFIED DATE\n 2010-05-26\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 32 }, { "doc_id": "techqa_DEV_Q158", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n CATIA V5 NT>XP\nFIXED COMPONENT ID\n 569151000", "logical_doc_id": 5, "chunk_id": 33 }, { "doc_id": "techqa_DEV_Q158", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R521 PSN\n UP", "logical_doc_id": 5, "chunk_id": 34 }, { "doc_id": "techqa_DEV_Q278", "section_id": 0, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "IBM Rational Automation Framework, Version 3.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24030588]\nRational Automation Framework Fix Pack 2 (3.0.1.2) for 3.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24037116]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q278", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "?SIBVirtualGatewayLink\n\n WASKey='virtualLink'\n\n name='CORESRV_BUS:IASRV_BUS'\n\n uuid='A5C940353A069CF363A7693A'\n\n ?\n\n [exec] CRWWA9902I ConfigWriter - _createWASObject: creating:\n\n SIBVirtualGatewayLink under parent: CORESRV_BUS\n\n (cells/esawpscell/buses/IASRV_BUS|sib-bus.\n\n xml#SIBForeignBus_1307601804655)\n\n [exec] WASX7017E: Exception received while running file\n\n '/sys/RAFW/product/actions/configure/was/common/nd/scripts/siBus\n .py';\n exception information: com.ibm.websphere.management.exception.\n\n InvalidAttributeValException: ADMG0012E: The attribute value for\n\n attribute name is not valid.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q278", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\n\nPROBLEM DESCRIPTION: *\n\nRECOMMENDATION: *\n\nUsing the was_common_configure_sibus to read and\n subsequently write MQ links or SIB links was failing as\n was_common_configure_sibus uses AdminConfig to write data\n back to WAS when it should have been using AdminTask to\n perform the write back to WAS.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q278", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Properly capture SIB links and MQ links using\n was_common_configure_sibus in export mode.\n was_common_configure_sibus cannot be used in execute mode to\n write out the data, as AdminConfig is used instead of\n AdminTask, which is what should be used. In order to write\n out the data base to WAS,\n was_common_configure_sibus_mq_links or\n was_common_configure_sibus_sib_links should be used\n instead, as they use AdminTask to write the data.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q278", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM41189\nREPORTED COMPONENT NAME\n RATL AUTO FW FO\nREPORTED COMPONENT ID\n 5724S2713\nREPORTED RELEASE\n 712\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2011-06-09\nCLOSED DATE\n 2011-08-31\nLAST MODIFIED DATE\n 2011-08-31\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q278", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n RATL AUTO FW FO\nFIXED COMPONENT ID\n 5724S2713", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q278", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R712 PSN\n UP", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q278", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "The messaging engine XXXXYYYYZZZ cannot be started as there is no runtime\ninitialized for it yet, retry the operation once it has initialized.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q278", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "By looking at the systemout.log, we have something like:\n.\n\n[6/24/14 15:05:32:488 EDT] 0000001e SibMessage E [XXXXYYYYZZZ] CWSIS1561E: The messaging engine's unique id does not match that found in the file store. ME_UUID=BPE98764B8E93CB4, ME_UUID(FS)=4587F87990047458\n.\nThese are the messaging engine UUID mismatch scenarios:\n.\n.\n1) When the data store or file store of different messaging engine is pointed to the current one.\n.\n2) A backup of the data store or file store taken at an earlier time was restored.\n.\n3) You have deleted the messaging engine and recreated the Messaging Engine with the same name and trying to use the previous file store which was associated with the old messaging engine(UUID).", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q278", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "To resolve the issue you will have to delete the file store for this Messaging Engine: .\n\nXXXXYYYYZZZ\n.\nDelete the existing file stores for this messaging engine and restart the JVM.\nThis action will create the new file store for the new UUID's.\n\nNote1: You must treat the log file, the temporary store file, and the permanent store file as one unit; that is, delete operation must be performed on all three files.\nNote2:By performing the suggested action, all the messages in the filestore will be lost.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q278", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "Deleting files following removal of a messaging engine [http://www-01.ibm.com/support/knowledgecenter/SSAW57_7.0.0/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tjm1060_.html]", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q278", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "You can use ESXi with multiple datastores. How do you migrate the virtual machine template, which is created by the Image Construction and Composition Tool for IBM SmartCloud Orchestrator, from one datastore to another datastore?", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q278", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "You can use one of the following methods to migrate the virtual machine template:\nMove the datastore within the same VMware region\n Do not move, delete, or clone the image. Just change the datastore using VMware. You do not need to register the image again.\nMove datastore 1 (DS1) to datastore 2 (DS2) across VMware region server 1 (RS1) to region server 2 (RS2).\n\n1. Identify the image (IM1) in glance. Look for a property called metadata. The property contains the UUID of the ISO image, which contains the metadata. You can find the ISO file as /var/lib/glance/images/ on region server 1 (RS1).\n\n2. Clone the image (IM1) from datastore (DS1) on region server 1 (RS1) to datastore (DS2) on region server 1 (RS2). For this example, use IM2 as the name for this second image. You can use both vmotion or the reference repository check in and check out.\n\n3. Create a new image in glance region server (RS2), pass it the ISO files that were copied from step 1, and take note of the UUID.\n\n4. Create or update the glance metadata image property for the image (IM2) to the UUID value that was noted in the previous step.\n\n5. Register the cloned image (IM2) in IBM SmartCloud Orchestrator\n\n SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q278", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When a destination is created while an server is active, but the\n messaging engine for that application server is stopped, the\n dynamic reload logic does not add that destination to the\n internal state of the messaging engine.\n When the messaging engine is later started (due to a failover in\n this case), a CWSIP0062E message is outputted, and the\n destination cannot be accessed.\n When the whole application server is restarted, the knowledge\n of all destinations for the messaging engine is reloaded, and\n the destination becomes available again.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q278", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Restart the application server where the CWSIP0062E message\n is logged.", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q278", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Users of the default messaging provider for *\nWebSphere Application Server V6.0 *\n\nPROBLEM DESCRIPTION: If a destination is created while a *\nmessaging engine is stopped, but the *\napplication server that hosts it is *\nrunning, then a CWSIP0062E error is *\nseen in the logs on startup of the *\nmessaging engine, and the destination *\ncannot be accessed. *\n\nRECOMMENDATION: *\n\nIn a failover environment, it is common for a messaging engine\n for a bus not to be running within a particular application\n server, even though the application server itself is active.\n\nIf a new destination is created in the bus, and dynamic\n configuration reload is enabled for that bus, the SIBus service\n of all application servers which can host messaging engines are\n informed of the change.\n\nHowever, in the case where a messaging engine is inactive\n within an application server, this process was working\n incorrectly. Knowledge of bus destinations was not fully\n reloaded for the inactive messaging engine, causing the\n following error during messaging engine startup (for example\n after a failover):\n\nCWSIP0062E: The destination {0} with UUID {1} could not be\n recovered due to a possible WCCM configuration error\n\nAfter the messaging engine started, the destination could not\n be accessed by applications.", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q278", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This APAR fixes the issue.\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q278", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PK53590\nREPORTED COMPONENT NAME\n PLAT MSG COM\nREPORTED COMPONENT ID\n 620400101\nREPORTED RELEASE\n 100\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2007-09-26\nCLOSED DATE\n 2007-10-17\nLAST MODIFIED DATE\n 2007-10-25\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q278", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n PLAT MSG COM\nFIXED COMPONENT ID\n 620400101", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q278", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R100 PSY\n UP", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q278", "section_id": 1, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "The desired device to be added does not show in the GUI but shows in the CLI output when listing devices.", "logical_doc_id": 5, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q278", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Since the device is partially added in TKLM, we need to remove it then add it.\n\nPlease refer to below instructions :\n*** Before we make any changes, please take a TKLM backup:\nhttp://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.tklm.doc_2.0/tsk/tsk_ic_admin_backup.html [http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.tklm.doc_2.0/tsk/tsk_ic_admin_backup.html]\n\nOpen a Windows command prompt and change directory to TIP_HOME\\bin:\n\ncd \\ibm\\tivoli\\tiptklmV2\\bin\n\nLog into wsadmin as the built-in local administrator account :\n\nwsadmin.bat -username tklmadmin -password -lang jython\n\nOn UNIX\n\n./wsadmin.sh -username tklmadmin -password -lang jython\n\nPart 1: If you have pending devices and you need to accept them. List all Pending devices requests & accept them if you find any:\n\na) List all devices pending requests, look for devices that you are\ntrying to add and copy UUID value:\nprint AdminTask.tklmPendingDeviceList()\n\nb) Accept pending devices requests:\nprint AdminTask.tklmPendingDeviceAccept('[-deviceUUID\nDEVICE-7d588437-e725-48bf-a836-00a47df64e78 -usage LTO]]')\n\nFor additional information regarding pending device requests, refer to\nthe below documentation:\nhttp://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=% [http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=%]\n2Fcom.ibm.tklm.doc_2.0%2Ftsk%2Ftsk_ic_admin_deviceautopend.html\n\nPart 2: If there are no pending devices requests listed, you can try to list existing devices and remove them from there:\n\na) List all devices, look for devices that you are trying to add and\ncopy UUID value:\n\nprint AdminTask.tklmDeviceList('[-type LTO]')\n\nExample below for serial number 009912345678\n\nDescription = test1234124\nSerial Number = 009912345678\nDevice uuid = DEVICE-bc063d11-2587-4101-a2c3-e4937c02b057\nDevice group = LTO\nWorld wide name =\nSym alias = LATEST\n\nb) Remove devices specifying the problem device uuid:\n\nprint AdminTask.tklmDeviceDelete('[-uuid DEVICE-bc063d11-2587-4101-a2c3-e4937c02b057]')\n\nc) List all devices again making sure the the problem device is not in the list:\nprint AdminTask.tklmDeviceList('[-type LTO]')\n\nd) When confirmed, try to add devices manually through TKLM portal (GUI)\n\nPRODUCT ALIAS/SYNONYM\n TKLM", "logical_doc_id": 5, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q307", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "OpenSSL vulnerabilities were disclosed on September 22 and 26, 2016 by the OpenSSL Project. OpenSSL is used by IBM Sterling Connect:Direct for HP NonStop. IBM Sterling Connect:Direct for HP NonStop has addressed the applicable CVEs.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q307", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-2177 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2177]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by the incorrect use of pointer arithmetic for heap-buffer boundary checks. By leveraging unexpected malloc behavior, a remote attacker could exploit this vulnerability to trigger an integer overflow and cause the application to crash.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113890 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113890] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H)\n\nCVEID: CVE-2016-6306 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6306]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by missing message length checks when parsing certificates. A remote authenticated attacker could exploit this vulnerability to trigger an out-of-bounds read and cause a denial of service.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117112 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117112] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L)\n\nCVEID: CVE-2016-2183 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2183]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error in the Triple-DES on 64-bit block cipher, used as a part of the SSL/TLS protocol. By capturing large amounts of encrypted traffic between the SSL/TLS server and the client, a remote attacker able to conduct a man-in-the-middle attack could exploit this vulnerability to recover the plaintext data and obtain sensitive information. This vulnerability is known as the SWEET32 Birthday attack.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116337 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116337] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q307", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Sterling Connect:Direct for HP NonStop 3.6.0", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q307", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "The recommended solution is to apply the fix as soon as practical. Please see below for information about the available fixes.\n\nVRMF APAR Remediation/First Fix 3.6.0 IT08228 Apply Fix Pack 3.6.0.2, available on Fix Central [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Other%2Bsoftware&product=ibm/Other+software/Sterling+Connect%3ADirect+for+HP+NonStop&release=3.6.0.1&platform=All&function=all]\nYou should verify that applying this configuration change does not cause any compatibility issues. WORKAROUNDS AND MITIGATIONS\nCVE-2016-2183: In versions of C:D for HP NonStop older than 3.6.0.2, deselect the Triple-DES (3DES) cipher suite if it is specified in the Secure+ configuration. To avoid production outages when switching to another cipher, coordinate the configuration change to an agreed cipher with the security administrator of each remote node with which you use Secure+. The recommended cipher suite is AES128-SHA or AES256-SHA.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q307", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "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.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q307", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q307", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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 07 November 2016: Original version published\nThe 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.", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q307", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "OpenSSL\u30d7\u30ed\u30b8\u30a7\u30af\u30c8\u304b\u3089\u3001OpenSSL\u306e\u8106\u5f31\u6027\u304c2016\u5e749\u670822\u65e5\u300126\u65e5\u306b\u516c\u958b\u3055\u308c\u307e\u3057\u305f\u3002\nIBM WebSphere MQ Advanced Message Security \u306fIBM i \u30d7\u30e9\u30c3\u30c8\u30d5\u30a9\u30fc\u30e0\u4e0a\u3067\u306e\u307f\u3001OpenSSL\u3092\u4f7f\u7528\u3057\u3066\u3044\u307e\u3059\u3002\n\u3053\u306e\u305f\u3081 IBM WebSphere MQ Advanced Message Security \u306f\u3053\u308c\u3089\u306eCVE\u306e\u5f71\u97ff\u3092\u53d7\u3051\u307e\u3059\u3002\n\n\u6700\u65b0\u306e\u60c5\u5831\u306b\u3064\u3044\u3066\u306f\u4e0b\u8a18\u306e\u6587\u66f8\uff08\u82f1\u8a9e\uff09\u3092\u3054\u53c2\u7167\u304f\u3060\u3055\u3044\u3002\nSecurity Bulletin: Vulnerabilities in OpenSSL affect IBM WebSphere MQ Advanced Message Security (CVE-2016-2177, CVE-2016-2178)\nhttp://www.ibm.com/support/docview.wss?uid=swg21999724 [http://www.ibm.com/support/docview.wss?uid=swg21999724]", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q307", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-2177 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2177]\nDESCRIPTION: OpenSSL\u306f\u30b5\u30fc\u30d3\u30b9\u62d2\u5426\u3092\u5f15\u304d\u8d77\u3053\u3059\u8106\u5f31\u6027\u3092\u542b\u3093\u3067\u3044\u307e\u3059\u3002\n\u3053\u308c\u306f\u30d2\u30fc\u30d7\u30fb\u30d0\u30c3\u30d5\u30a1\u30fc\u306e\u30d0\u30a6\u30f3\u30c0\u30ea\u30fc\u30fb\u30c1\u30a7\u30c3\u30af\u3067\u7528\u3044\u3089\u308c\u308b\u3001\u30dd\u30a4\u30f3\u30bf\u6f14\u7b97\u5b50\u306e\u4e0d\u6b63\u306a\u5229\u7528\u306b\u3088\u3063\u3066\u5f15\u304d\u8d77\u3053\u3055\u308c\u307e\u3059\u3002\n\u4e88\u671f\u3057\u306a\u3044malloc\u3092\u4f7f\u7528\u3059\u308b\u3053\u3068\u3067\u3001\u30ea\u30e2\u30fc\u30c8\u306e\u653b\u6483\u8005\u306f\u3053\u306e\u8106\u5f31\u6027\u3092\u60aa\u7528\u3057\u3066integer\u306e\u30aa\u30fc\u30d0\u30fc\u30d5\u30ed\u30fc\u3092\u5f15\u304d\u8d77\u3053\u3057\u3001\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u3092\u30af\u30e9\u30c3\u30b7\u30e5\u3055\u305b\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002\nCVSS Base Score: 5.9\nCVSS Temporal Score: \u73fe\u6642\u70b9\u306e\u30b9\u30b3\u30a2\u306f\u4ee5\u4e0b\u306e\u30b5\u30a4\u30c8\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002https://exchange.xforce.ibmcloud.com/vulnerabilities/113890 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113890]\nCVSS Environmental Score*: \u672a\u5b9a\u7fa9\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H)\n\nCVEID: CVE-2016-2178 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2178]\nDESCRIPTION: OpenSSL\u306fDSA\u5b9f\u88c5\u306b\u542b\u307e\u308c\u308b\u30a8\u30e9\u30fc\u306b\u3088\u3063\u3066\u3001\u30ea\u30e2\u30fc\u30c8\u653b\u6483\u8005\u306b\u91cd\u8981\u306a\u60c5\u5831\u3092\u4e0e\u3048\u3066\u3057\u307e\u3046\u53ef\u80fd\u6027\u304c\u3042\u308a\u307e\u3059\u3002\u3053\u306e\u30a8\u30e9\u30fc\u306f\u7279\u5b9a\u306e\u64cd\u4f5c\u3092\u4e0d\u7279\u5b9a\u306e\u6642\u9593\u306b\u8a31\u3059\u305f\u3081\u3001\u653b\u6483\u8005\u306f\u3053\u306e\u8106\u5f31\u6027\u3092\u60aa\u7528\u3057\u3066\u30ad\u30e3\u30c3\u30b7\u30e5\u30bf\u30a4\u30df\u30f3\u30b0\u653b\u6483\u3092\u4f7f\u7528\u3057\u3001DSA\u79d8\u5bc6\u9375\u3092\u53d6\u5f97\u3059\u308b\u3053\u3068\u304c\u53ef\u80fd\u3067\u3059\nCVSS Base Score: 5.3\nCVSS Temporal Score: \u73fe\u6642\u70b9\u306e\u30b9\u30b3\u30a2\u306f\u4ee5\u4e0b\u306e\u30b5\u30a4\u30c8\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002 https://exchange.xforce.ibmcloud.com/vulnerabilities/113889 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113889]\nCVSS Environmental Score*: \u672a\u5b9a\u7fa9\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q307", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM WebSphere MQ V8\n8.0.0.0 \u304b\u3089 8.0.0.5 \u307e\u3067\u306e\u4fdd\u5b88\u30d0\u30fc\u30b8\u30e7\u30f3\u304c\u5f71\u97ff\u3092\u53d7\u3051\u307e\u3059\u3002", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q307", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Fix Pack 8.0.0.6 [http://www-01.ibm.com/support/docview.wss?uid=swg21995100] \u4ee5\u964d\u3078\u30a2\u30c3\u30d7\u30c7\u30fc\u30c8\u3057\u307e\u3059\u3002", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q307", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q307", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q307", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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\u516c\u958b\u6e08\u307f\u306e\u30d5\u30a3\u30c3\u30af\u30b9\u30d1\u30c3\u30af\u306b\u3064\u3044\u3066\u306f\u3001\u4ee5\u4e0b\u306e\u30b5\u30a4\u30c8\u3088\u308a\u3054\u5229\u7528\u3044\u305f\u3060\u3051\u307e\u3059\u3002\nRecommended Fixes for WebSphere MQ\nhttp://www.ibm.com/support/docview.wss?uid=swg27006037 [http://www.ibm.com/support/docview.wss?uid=swg27006037]\n\n\u30d5\u30a3\u30c3\u30af\u30b9\u30fb\u30d1\u30c3\u30af\u306e\u516c\u958b\u4e88\u5b9a\u306b\u3064\u3044\u3066\u306f\u3001\u4ee5\u4e0b\u306e\u30b5\u30a4\u30c8\u3088\u308a\u3054\u78ba\u8a8d\u3044\u305f\u3060\u3051\u307e\u3059\u3002\nMQ planned maintenance release dates\nhttp://www.ibm.com/support/docview.wss?uid=swg27006309 [http://www.ibm.com/support/docview.wss?uid=swg27006309]\nCHANGE HISTORY\n 2017\u5e74 3\u670813\u65e5\uff1a\u521d\u7248\u516c\u958b\nThe 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\u95a2\u9023\u60c5\u5831\n An US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21999724]", "logical_doc_id": 1, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q307", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "OpenSSL vulnerabilities were disclosed on September 22 and 26, 2016 by the OpenSSL Project. OpenSSL is used by HP SSL on HP OpenVMS. IBM WebSphere MQ on OpenVMS Alpha and Itanium uses HP SSL and has addressed the applicable CVE ( CVE-2016-2183 ) known as \u201cSWEET32 Birthday attack\" .", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q307", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-2183 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2183]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error in the in the Triple-DES on 64-bit block cipher, used as a part of the SSL/TLS protocol. By capturing large amounts of encrypted traffic between the SSL/TLS server and the client, a remote attacker able to conduct a man-in-the-middle attack could exploit this vulnerability to recover the plaintext data and obtain sensitive information. This vulnerability is known as the SWEET32 Birthday attack.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/116337 [https://exchange.xforce.ibmcloud.com/vulnerabilities/116337] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q307", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "The vulnerability affects version 6.0 of IBM WebSphere MQ on OpenVMS Alpha & Itanium.", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q307", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Product VRMF APAR Remediation/First Fix IBM WebSphere MQ on OpenVMS Alpha and Itanium.\n6.0.2.13 IT18095 Download from Fix Central [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%2FWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=All&platform=All&function=aparId&apars=IT18095&source=fc]\nOn HP OpenVMS, IBM MQ V6.0.2.13 is a pre-requisite for applying the fix , refer to APAR IT18095 for additional details on the fix. WORKAROUNDS AND MITIGATIONS\nNone", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q307", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q307", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 2, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q307", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 15 December 2016 : Original version published\nThe 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.", "logical_doc_id": 2, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q307", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere MQ 5.3 and IBM MQ 8 for HPE NonStop have addressed a vulnerability in which OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q307", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2017-3735 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3735]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate. An attacker could exploit this vulnerability to trigger an out-of-bounds read, resulting in an incorrect text display of the certificate.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/131047 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131047] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N)", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q307", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "All versions of WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server", "logical_doc_id": 3, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q307", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "For MQ 5.3\n*\n*\n*\n*\n* https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=5.3.1.14&platform=HP+NonStop&function=all\nFor MQ 8\n*\nhere", "logical_doc_id": 3, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q307", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 3, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q307", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 3, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q307", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nThe 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\nPSIRT SECURITY BULLETIN", "logical_doc_id": 3, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q307", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "A vulnerability was found in the OpenSSL release used by the Windows and z/OS Security Identity Adapters. These adapters have been upgraded to a more current OpenSSL release that corrects CVE-2017-3735 \"Malformed X.509 IPAddressFamily could cause OOB read\" vulnerability.", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q307", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2017-3735 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3735]\n\nDESCRIPTION:\nCVE-2017-3735 : OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAdressFamily extension in an X.509 certificate. An attacker could exploit this vulnerability to trigger an out-of-bounds read, resulting in an incorrect text display of the certificate.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/131047 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131047] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:l/I:N/A:N) CVE-2017-3736 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3736]", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q307", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Security Identity Manager v6.0 Adapters for Windows and z/OS platforms\n\nIBM Security Identity Adapters v7.x for Windows and z/OS platforms", "logical_doc_id": 4, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q307", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Obtain the latest GA levels of 6.0 or 7.x adapters, as found on the Fix Link pages listed below:\n\nProduct Fix Link ISIM v6.0 Adapters Adapters for IBM Security Identity Manager v6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg21599053] Security Identity v7.x Adapters for IGI, ISIM, PIM IBM Security Identity Adapters [http://www-01.ibm.com/support/docview.wss?uid=swg21687732] 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.", "logical_doc_id": 4, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q307", "section_id": 4, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 4, "chunk_id": 32 }, { "doc_id": "techqa_DEV_Q307", "section_id": 5, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 20 March 2018: First publish\nThe 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.", "logical_doc_id": 4, "chunk_id": 33 }, { "doc_id": "techqa_DEV_Q195", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q195", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "A security vulnerability in the WebSphere DataPower XC10\n Appliance allows unauthenticated access to administrative\n operations, and security vulnerabilities in Java transport\n layer security (TLS) might allow attackers access.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q195", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Users of IBM WebSphere DataPower XC10 *\nAppliance v2.0 and higher. *\n\nPROBLEM DESCRIPTION: Attackers can have unauthenticated *\naccess to administrative operations *\nbecause of security vulnerabilities *\nin Java TLS. *\n\nRECOMMENDATION: Install a firmware version that contains *\nthis APAR. *\n\nCVE-2013-0600 - A knowledgeable user may submit administrative\n commands to the WebSphere DataPower XC10 Appliance without\n authentication.\n CVSS Base Score: 9.3\n CVSS Temporal Score: See http://xforce.iss.net/xforce/xfdb/83617 [http://xforce.iss.net/xforce/xfdb/83617]\n for the current score\n CVSS Environmental Score*: Undefined\n CVSS Vector: (AV:N/AC:M/AU:N/C:C/I:C/A:C)\n CVE-2013-0440 - Unspecified vulnerability in Java Runtime\n Environment allows remote attackers to affect availability via\n vectors related to JSSE.\n CVSS Base Score: 5\n CVSS Temporal Score: See\n http://xforce.iss.net/xforce/xfdb/81799 [http://xforce.iss.net/xforce/xfdb/81799]\n CVSS Environmental Score*: Undefined\n CVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)\n CVE-2013-0443 - Unspecified vulnerability in Java Runtime\n Environment allows remote attackers to affect confidentiality\n and integrity via vectors related to JSSE.\n CVSS Base Score: 4\n CVSS Temporal Score: See\n http://xforce.iss.net/xforce/xfdb/81801 [http://xforce.iss.net/xforce/xfdb/81801]\n CVSS Environmental Score*: Undefined\n CVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N)\n CVE-2013-0169 - The TLS protocol does not properly consider\n timing side-channel attacks, which allows remote attackers to\n conduct distinguishing attacks and plain-text recovery attacks\n via statistical analysis of timing data for crafted packets, aka\n the \"Lucky Thirteen\" issue.\n CVSS Base Score: 4.3\n CVSS Temporal Score: See\n http://xforce.iss.net/xforce/xfdb/81902 [http://xforce.iss.net/xforce/xfdb/81902]\n CVSS Environmental Score*: Undefined\n CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q195", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The vulnerabilities were found and corrected in the appropriate\n code in the runtime environment. Download a version of the\n firmware for either V2.0.0.3 or V2.1.0.3 that\n contains this APAR\n (http://www-01.ibm.com/support/docview.wss?uid=swg27019704).\n For more information about this security vulnerability, see\n the following web page:\n http://www-01.ibm.com/support/docview.wss?uid=swg21636324 [http://www-01.ibm.com/support/docview.wss?uid=swg21636324]\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q195", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC91726\nREPORTED COMPONENT NAME\n WSDATAPOWER XC1\nREPORTED COMPONENT ID\n 5765H4200\nREPORTED RELEASE\n 200\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-04-22\nCLOSED DATE\n 2013-06-18\nLAST MODIFIED DATE\n 2013-06-18\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q195", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WSDATAPOWER XC1\nFIXED COMPONENT ID\n 5765H4200", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q195", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R200 PSY\n UP\nR210 PSY\n UP", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q195", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Is this HotFix for TLS 1.0 (http://www-01.ibm.com/support/docview.wss?uid=swg21694441 [http://www-01.ibm.com/support/docview.wss?uid=swg21694441]) able to support also TLS 1.2?", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q195", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Yes, TLSv1.2 is supported by using the same fix.\nJust an additional NOTE: As the default version expected is TLSv1, if you have disabled TLSv1 in the DataPower appliance (use only TLSv1.2), then please make sure to manually modify the value of KBN_SOMA_PROTOCOL to TLSv1.2.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q195", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do I prevent DataPower from using SSLv3 when communicating with WebSphere MQ ?", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q195", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Due to various vulnerabilities reported in SSLv3 protocol, it is highly recommended to disable SSLv3 across all configuration objects in DataPower.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q195", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "1. First make sure to Quiesce all domains and services to stop traffic to the appliance. System quiesce and unquiesce commands can be invoked by navigating to Administration --> Main --> System Control.\n\n2. There are two things you need do to prevent DataPower from communicating with WebSphere MQ using SSLv3.\n\nWhen DataPower mq-qm object is using Key Repository (GSkit):\n\n(a). In DataPower Control Panel, navigate to \"Configure MQ Queue Manager\" page. Under the \"Connections\" tab, configure the parameter \"SSL Cipher Specification\" to use one of the cipher specifications listed below.\n\nFor DataPower versions 6.0.0 and later:\n\nTLS_RSA_WITH_AES_128_CBC_SHA\nTLS_RSA_WITH_AES_256_CBC_SHA\nTLS_RSA_WITH_NULL_SHA256\nTLS_RSA_WITH_AES_128_CBC_SHA256\nTLS_RSA_WITH_AES_256_CBC_SHA256\n\nFor DataPower versions prior to 6.0.0:\n\nTLS_RSA_WITH_AES_128_CBC_SHA\nTLS_RSA_WITH_AES_256_CBC_SHA\nAES_SHA_US\n\n(b). In WebSphere MQ channels select the same TLS protocol as DataPower uses from the channel CipherSpec.\n\nWhen DataPower mq-qm object is using an SSL Proxy Profile:\n\nFor V6 or later: http://pic.dhe.ibm.com/infocenter/wsdatap/v6r0m0/topic/com.ibm.dp.xg.doc/mq_securingwithansslproxyprofileobject.html [http://pic.dhe.ibm.com/infocenter/wsdatap/v6r0m0/topic/com.ibm.dp.xg.doc/mq_securingwithansslproxyprofileobject.html]\n\nFor version prior to V6.0:\nhttp://www-01.ibm.com/support/knowledgecenter/SS9H2Y_5.0.0/com.ibm.dp.xg.doc/integratingwithmq107.htm%23wq71?lang=en [http://www-01.ibm.com/support/knowledgecenter/SS9H2Y_5.0.0/com.ibm.dp.xg.doc/integratingwithmq107.htm%23wq71?lang=en] (for version v5)\n\nhttp://pic.dhe.ibm.com/infocenter/wsdatap/v4r0m2/index.jsp?topic=%2Fcom.ibm.dp.xb.doc%2Fintegratingwithmq108.htm [http://pic.dhe.ibm.com/infocenter/wsdatap/v4r0m2/index.jsp?topic=%2Fcom.ibm.dp.xb.doc%2Fintegratingwithmq108.htm] (for version v4)", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q195", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#Vulnerability in SSLv3 affects DataPower CVE-2014-3566 [http://www-01.ibm.com/support/docview.wss?uid=swg21687189]\nSecurity Bulletin: Vulnerability in SSLv3 affects IBM W [http://www-01.ibm.com/support/docview.wss?uid=swg21687433&myns=swgws&mynp=OCSSFKSJ&mync=E]\nSecuring with an SSL Proxy Profile object (V600) [http://pic.dhe.ibm.com/infocenter/wsdatap/v6r0m0/index.jsp?topic=%2Fcom.ibm.dp.xg.doc%2Fmq_securingwithansslproxyprofileobject.html]\nSecuring communication with remote queue managers(V500) [http://www-01.ibm.com/support/knowledgecenter/SS9H2Y_5.0.0/com.ibm.dp.xg.doc/integratingwithmq107.htm%23wq71?lang=en]\nSecuring communication with remote queue managers(V402) [http://pic.dhe.ibm.com/infocenter/wsdatap/v4r0m2/index.jsp?topic=%2Fcom.ibm.dp.xb.doc%2Fintegratingwithmq108.htm]", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q195", "section_id": 4, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Fix packs for DataPower XML Security Gateway version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034955]\nFix packs for DataPower B2B Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034956]\nFix packs for DataPower Integration Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034957]\nFix packs for DataPower Low Latency Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034958]\nFix packs for DataPower Service Gateway version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034959]\nFix packs for DataPower Service Gateway version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036407]\nFix packs for DataPower B2B Appliance version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036409]\nFix packs for DataPower Integration Appliance version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036410]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q195", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The SSL stack of the DataPower appliance might encounter an\n unexpected firmware restart when TLS 1.2 is used. This problem\n is known as CVE-2013-6449.", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q195", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Use SSL configurations that disable TLS version 1.2.", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q195", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Customers using SSL configurations that support TLS 1.2 might\n encounter an unexpected firmware restart. TLS 1.2 is supported\n by default in the Crypto Profile object starting in firmware\n 6.0.0.0.", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q195", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fix is available in 6.0.0.5 and 6.0.1.1.\n\nFor a list of the latest fix packs available, please see:\n http://www-01.ibm.com/support/docview.wss?uid=swg21237631 [http://www-01.ibm.com/support/docview.wss?uid=swg21237631]\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q195", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC98780\nREPORTED COMPONENT NAME\n DATAPOWER\nREPORTED COMPONENT ID\n DP1234567\nREPORTED RELEASE\n 600\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-01-16\nCLOSED DATE\n 2014-01-22\nLAST MODIFIED DATE\n 2014-03-31\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q195", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n DATAPOWER\nFIXED COMPONENT ID\n DP1234567", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q195", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R600 PSY\n UP\nR601 PSY\n UP\n\nFIX README", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q195", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "TLSv1.2 is now supported between the IBM Security Identity Manager virtual appliance and middleware servers such as the Identity data store and the directory server. The protocol is used to establish communication between IBM Security Identity Manager Server and the middleware servers.", "logical_doc_id": 5, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q195", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "You must set the same TLS protocol version on the middleware servers and as a local management interface protocol (LMI). The LMI protocol must be set from virtual appliance dashboard using Advanced tuning parameters panel. The supported TLS protocol versions are: TLS, TLSv1, TLSv1.1, and TLSv1.2.\n\nNote: The TLS protocol version specified from VA dashboard will be applicable to both middleware servers (Identity Data Store and Directory server). We cannot specify different TLS protocol version for each middleware servers.\nTo set the TLS protocol for IBM Security Identity Manager Server (ISIM) see Managing server settings [https://www.ibm.com/support/knowledgecenter/en/SSRMWJ_7.0.1.7/com.ibm.isim.doc/configuring/tsk/t_va_custom_server_settings.htm].\nTo set the TLS protocol for local management interface (LMI), see Advanced tuning parameters for the virtual appliance [https://www.ibm.com/support/knowledgecenter/en/SSRMWJ_7.0.1.7/com.ibm.isim.doc/admin/ref/r_adv_tuning.htm]\n\nConsider the following scenarios as you configure the TLS protocol. Note: For every scenario, after completing each step, check the IBM Security Identity Manager virtual appliance dashboard for any notifications and take the appropriate action.\n\nScenario #1\nNew installation of the IBM Security Identity Manager virtual appliance and you want to enable the TLS protocol\n\n1. When you configure IBM Security Identity Manager by using the initial configuration wizard [https://www.ibm.com/support/knowledgecenter/en/SSRMWJ_7.0.1.7/com.ibm.isim.doc/installing/tsk/t_using_activation_wizard.htm], use either SSL or Non-SSL mode for directory and database server configuration. Use of the TLS protocol on directory and database server during initial configuration is not supported.\n 2. Once the ISIM VA system is ready, refer to the applicable scenarios for enabling the TLS protocol.\n\nScenario #2\nISIM VA working environment: The SSL connection exists between ISIM and middleware servers before upgrading to 7.0.1.7 or later. 1. Upgrade the existing ISIM VA version to 7.0.1.7 version or later.\n 2. Set the required TLS protocol version for middleware servers.\n 3. Set the same TLS protocol version for ISIM Server.\n 4. Set the same TLS protocol version for LMI.\n\nScenario #3\nISIM VA working environment: The SSL connection does not exist between ISIM and middleware servers before upgrading to 7.0.1.7 or later. 1. Upgrade the existing ISIM VA version to 7.0.1.7 version or later.\n 2. Set the required TLS protocol version for ISIM Server\n 3. Set the same TLS protocol version for LMI.\n 4. Set the same TLS protocol version for middleware servers.\n 5. Reconfigure the database server, directory server and select the SSL check box to enable the secure connection.", "logical_doc_id": 5, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q195", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Scenario #4\nISIM VA working cluster environment (primary node and member nodes exist). 1. Set the required TLS protocol version on primary node using applicable scenario #2 or #3.\n 2. Setting the TLS protocol version for ISIM Server on member nodes is not required. This will be handled as part of cluster nodes synchronization.\n 3. Set the same TLS protocol version for LMI on member nodes individually.\n 4. Synchronize the member nodes in the cluster for TLS protocol configuration changes that performed on the primary node.\n\nScenario #5\nISIM VA working cluster environment (primary node and member nodes exist) and you are adding new member nodes. 1. Set the TLS protocol version (same as of exiting members) for LMI on newly created member nodes. Do this step before connecting to primary node.\n 2. Complete the additional steps to add the newly created member node into the cluster.\n\nScenario #6\nISIM VA working environment and backing up the primary node where TLS protocol is enabled. 1. Set the TLS protocol version (same as of primary node) for LMI of backup node. This should be done before connecting to primary node.\n 2. Execute the additional steps to set up a backup of the primary node.\n\nScenario #7\nISIM VA working environment and upgrading it to 7.0.1.7 version or later. 1. Upgrade the ISIM VA to 7.0.1.7 version or later.\n 2. If TLS protocol must be set after upgrade then refer the applicable scenarios and execute steps, otherwise no other actions required.", "logical_doc_id": 5, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q186", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "You must use the silent installation process to install IBM Rational ClearQuest on platforms that do not use the graphical user interface (GUI).", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q186", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "These platforms are:\nHP PA-Risc\n\nNote: For platforms that do use the GUI, follow the installation instructions provided in the IBM Rational ClearQuest Information Center: http://publib.boulder.ibm.com/infocenter/cqhelp/v7r1m0/index.jsp [http://publib.boulder.ibm.com/infocenter/cqhelp/v7r1m0/index.jsp]. To silently install Rational ClearQuest:\n\n1. If the ESD image is not available through a UNC or NFS path:\n*\n* esd_image_root\n*\n\n2. If the ESD image is available through a UNC or NFS path, copy the file esd_image_root/product_response_platform.xml onto a writeable disk.\n\n3. Open and read the license agreement files located in esd_image_root/license_agreements. xx indicates the language of the file. The files are: *\nLA_xx\n*\nLI_xx\n*\nnon_ibm_license\n*\nnotices\n\n4. Open the response file, product_response_platform.xml.\n\n5. If you agree to the license agreement, change the value for the acceptLicense key to true.\n\n\n6. Change the value for the repository location key to ' esd_image_root/diskTag.inf'.\n\n \n \n\n7. Follow the comments within the response file to configure your product's installation.\n\n8. Open the file esd_image_root/InstallerImage_$platform/install.xml. Find the version key and copy the value. You use this value in the next step. For example:\n\n \n \n\n9. Open the response file. In the command, update the version attribute for the offering key with the value copied from the install.xml file. If the version attribute is not listed for the offering key in the response file, you must add it.\n\n \n \n\n10. If IBM Installation Manager is not installed, you must install it. If an older version of Installation Manager is installed, it must be upgraded. To install Installation Manager that is bundled along with the product or to upgrade the current installed version of Installation Manager, follow the instructions below.\n* \n* esd_image_root/InstallerImage_$platform/install.xml\n* \n \n \n* \n \n \n \n*\n* \n \n \n \n\n11. Run the command:\nesd_image_root/InstallerImage*/install --launcher.ini esd_image_root/InstallerImage*/silent-install.ini -silent -input product_response_platform.xml -log logfile\n*\n* -showVerboseProgress\n*\n*\nPRODUCT DOCUMENTATION", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q186", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "How to automate the process of deploying IBM\u00ae Algo Financial Modeler\u00ae 2.2.0 software within your organisation", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q186", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Introduction\n\nThis document is for the benefit of IT personnel who wish to automate the process of deploying IBM Algo Financial Modeler software within their organisation. This can be done by invoking the IBM Algo Financial Modeler MSI installer file from the command-line using the MSIEXEC program. This document assumes familiarity with this program.\n\nAll of the IBM Algo Financial Modeler components are packaged into a single MSI installer file which has a 32 and a 64-bit version. There are also license installers that enable the purchased options. The appropriate files can be downloaded from Passport Advantage [http://www-01.ibm.com/software/howtobuy/passportadvantage/?lnk=msdDO-shop-usen].\n\nImportant note: Before any installation takes place, it is essential that you read the installation pages for the current release (see Related information section below). These pages contains details of:\nWhat needs to be installed to use the features you require, including any prerequisites\nChanges to the system which may affect the installation\nHow to test that the installation is successful\n\nAutomated installation\n\nStandard installation of the IBM Algo Financial Modeler software packages by running the MSI installer file is interactive and displays a number of dialog boxes to the user so that they can select the software they require and fill in any necessary parameters. The purpose of automated installation is to preset the required software and parameters via the command-line so that user interaction is not required. Consequently, by invoking the MSI installer file with the MSIEXEC program, the installation can be made to proceed silently and in a manner tailored to individual company requirements.\n\nThe MSIEXEC command-line option /I is used to perform an installation and the option /qb is used to remove the dialog boxes from the installation as follows:\n\nMSIEXEC /I \"C:\\IBM_Algo_Financial_Modeler_Base.msi\" /qb\n\nHere the 32-bit installer MSI file has been saved to the C:\\ drive on the local machine. For more information regarding the command-line options for MSIEXEC please refer to the Microsoft website [http://technet.microsoft.com/en-gb/library/bb490936.aspx].\n\nIBM Algo Financial Modeler installation parameters\n\nIn addition to the command-line options, the IBM Algo Financial Modeler MSI installer file has several command-line parameters which can be used to preset the corresponding installation parameters. Some of these parameters have default values and are, therefore, optional; please check the installation instructions for the installer on the installation page for more information.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q186", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Please note that this section applies to both the 32 and 64-bit versions of the Base MSI installer.\n\nINSTALLLEVEL\n\nA value should be specified for the INSTALLLEVEL parameter in order to specify the software to install. If no INSTALLLEVEL parameter is specified a default value of 100 is used, meaning that all software would be installed, apart from the Standard Code.\n\nValue Purpose 40 Installs the IBM Algo Financial Modeler add-in for Microsoft\u00ae Excel 50 Installs the IBM Algo Financial Modeler add-in for Microsoft Access 60 Installs the IBM Algo Financial Modeler ODBC Driver 70 Installs the IBM Algo Financial Modeler Worker software for distributed processing 80 Installs a shortcut to automatically run the Worker Admin and Worker software when a user logs on 90 Installs the IBM Algo Financial Modeler Toolkit 100 Installs the IBM Algo Financial Modeler Development Software 110 Installs the IBM Algo Financial Modeler Standard Code\nSpecifying an INSTALLLEVEL means that all software with an INSTALLLEVEL value of less than or equal to that number will be installed.\n\nFor example, the following command-line instruction to silently install the IBM Algo Financial Modeler software would install the Development Software itself, along with the Toolkit, Worker startup shortcut, Worker software, ODBC Driver and the Add-ins for Microsoft Access and Excel.\n\nMSIEXEC /I \"C:\\IBM_Algo_Financial_Modeler_Base.msi\" AGREETOLICENSE=YES /qb\n\nSoftware with a lower INSTALLLEVEL value can be explicitly excluded using some of the optional parameters detailed below.\n\nOptional parameters", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q186", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Parameter Purpose AGREETOLICENSE Specify AGREETOLICENSE=YES to agree to the license agreement and install the software (must always be explicitly set to YES for the installation to proceed) NO_ADDINS Specify NO_ADDINS=YES to exclude the Microsoft Office Add-ins from the silent installation NO_DEVSOFTWARE Specify NO_DEVSOFTWARE=YES to exclude the Development Software from the silent installation NO_TOOLKIT Specify NO_TOOLKIT=YES to exclude the Toolkit from the silent installation\n(* this will only take effect if NO_DEVSOFTWARE is also set to YES as it is not possible to install the Development software without the Toolkit) NO_ODBC Specify NO_ODBC=YES to exclude the ODBC Driver from the silent installation NO_WORKER Specify NO_WORKER=YES to exclude the Worker from the silent installation ODBCCOMPATIBILITY Specify ODBCCOMPATIBILITY=YES to install components that provide backward compatibility with connection strings for the VIPitech ODBC Driver without needing to have the VIPitech ODBC driver installed\n(* can only be used if INSTALLLEVEL>=60 and NO_ODBC is not set to YES) WS_DOMAIN Each of these parameters must be supplied in order to install the IBM Algo Financial Modeler Worker as a windows service\n(* can only be used if INSTALLLEVEL>=70 and NO_WORKER is not set to YES) WS_USERNAME WS_PASSWORD INSTALLDIR Specify INSTALLDIR=\"C:\\My Installation Path\\\"\nExamples\n\nThe following command-line instruction will silently install just the Development software only to D:\\My AFM Installation:\n\nMSIEXEC /I \"C:\\IBM_Algo_Financial_Modeler_Base.msi\" AGREETOLICENSE=YES INSTALLDIR=\"D:\\My AFM Installation\" NO_ADDINS=YES NO_ODBC=YES NO_WORKER=YES /qb\n\nThe following command-line instruction will silently install the Standard Code as well as the Development software to the default installation directory:\n\nMSIEXEC /I \"C:\\IBM_Algo_Financial_Modeler_Base.msi\" INSTALLLEVEL=110 AGREETOLICENSE=YES NO_ADDINS=YES NO_ODBC=YES NO_WORKER=YES /qb\n\nThe following command-line instruction will silently install the ODBC Driver (with backward compatibility for VIPitech ODBC Driver connection strings) and the Add-ins for Microsoft Excel and Access (but not the Worker software) to the default installation directory:\n\nMSIEXEC /I \"C:\\IBM_Algo_Financial_Modeler_Base.msi\" AGREETOLICENSE=YES INSTALLLEVEL=60 ODBCCOMPATIBILITY=YES /qb\n\nTo include the Worker, simply increase the INSTALLLEVEL to 80. The following example adds the Worker and Windows service to run the Worker as a service to the previous example:\n\nMSIEXEC /I \"C:\\IBM_Algo_Financial_Modeler_Base.msi\" AGREETOLICENSE=YES INSTALLLEVEL=80 ODBCCOMPATIBILITY=YES WS_DOMAIN=\"Domain Name\" WS_USERNAME=MyUsername WS_PASSWORD=MyP#ssw0rd /qb\n\nTo install just the 64-bit ODBC driver (with backward compatibility):\n\nMSIEXEC /I \"C:\\IBM_Algo_Financial_Modeler_Base_64bit.msi\" AGREETOLICENSE=YES INSTALLLEVEL=60 ODBCCOMPATIBILITY=YES NO_ADDINS=YES /qb", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q186", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Please note that quotation marks are required around a parameter value when that value contains spaces and that the \"YES\" values are case sensitive and must all be upper case.\n\nLicense Installers\n\nIn addition to the IBM Algo Financial Modeler base MSI installer that installs the required features for 32-bit and 64-bit applications, the appropriate license installers must also be run on the client machines to enable the chargeable components/options that have been purchased.\n\nThere are no optional command line parameters and all license installers should be invoked as per the examples for the Grid Connector license installer below (the latter specifying the installation path as D:\\My AFM Installation):\n\nMSIEXEC /I \"C:\\IBM_Algo_Financial_Modeler_Connector.msi\" AGREETOLICENSE=YES /qb\n\nMSIEXEC /I \"C:\\IBM_Algo_Financial_Modeler_Connector.msi\" AGREETOLICENSE=YES INSTALLDIR=\"D:\\My AFM Installation\" /qb", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q186", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Algo Financial Modeler 2.2.0 Installation Guide [http://www-01.ibm.com/support/docview.wss?uid=swg27039227]", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q186", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "Rational Test Enabler is not released as a part of the 7.0.2 and 7.0.3 release.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q186", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Install IBM Rational Test Enabler version 7.0.1.\n\nIf you are installing Rational Test Enabler for the first time:\n\n1. Install Rational Robot 7.0.2 or 7.0.3\n 2. Install Rational Test Enabler 7.0.1\n\nIf you have the previous versions of Rational Robot and Rational Test Enabler: 1. Uninstall Rational Robot and Rational Test Enabler.\n 2. Install Rational Robot 7.0.2 or 7.0.3.\n 3. Install Rational Test Enabler 7.0.1.\n\nNOTE\nYou must uninstall all previous versions of Rational Robot before upgrading to the new version.\n\nThe following steps describes how to download the Rational Test Enabler 7.0.1.\n\n1. Log on to the Rational Release Area Download site [https://www.software.ibm.com/webapp/iwm/web/reg/pick.do?lang=en_US&source=RATL-RATIONAL].\n\n2. Search for IBM Rational Robot V7.0.3 Windows English eAssembly. Then select the radio button.\n\n[/support/docview.wss?uid=swg21322417&aid=1] [/support/docview.wss?uid=swg21322417&aid=1]\n\n3. Scroll all the way down to click Continue.\n\n4. Click View license and carefully read the License Agreement. If you agree, select I agree then click\n I confirm.\n\n5. Select IBM Rational Test Enablers V7.0.1 Windows English.\n\n[/support/docview.wss?uid=swg21322417&aid=2] [/support/docview.wss?uid=swg21322417&aid=2]\n\n6. If you still agree with the license agreement, select I agree, then click I confirm.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q186", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The following error occurs during the installation of the Permanent license for Rational Software Architect V8.0 C++ Extension:\n\nThe full error message is as follows:\n\nError installing.\nInstalling License key and agreement for Rational Software Architect V8.0 C++ Product 1.0.0 is not allowed in this package group; it is not compatible with com.ibm.rsa80.cpp.pek.offering 8.0.1.20110519_1306. It may be installed in a different package group.\nSoftware being installed: License key and agreement for Rational Software Architect V8.0 C++ Product 1.0.0 (OFFERING.com.ibm.rsa80.cpp.pek 1.0.0)\nSoftware being installed: OFFERING.com.ibm.rsa80.cpp.pek.offering 8.0.1.20110519_1306\nOnly one of the following can be installed at once:\nSE.0.com.ibm.rsa80.cpp.pek.assembly 1.0.0\nSE.0.com.ibm.rsa80.cpp.pek.assembly 8.0.1.20110519_1306\nCannot satisfy dependency:\nFrom: License key and agreement for Rational Software Architect V8.0 C++ Product 1.0.0 (OFFERING.com.ibm.rsa80.cpp.pek 1.0.0)\nTo: SE.0.com.ibm.rsa80.cpp.pek.assembly [1.0.0,2.0.0)\nCannot satisfy dependency:\nFrom: OFFERING.com.ibm.rsa80.cpp.pek.offering 8.0.1.20110519_1306\nTo: SE.0.com.ibm.rsa80.cpp.pek.assembly [8.0.1,9.0.0)\n\nimage\n[/support/docview.wss?uid=swg21516347&aid=1] [/support/docview.wss?uid=swg21516347&aid=1]", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q186", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The temporary license installed previously to extend the evaluation period collides with the permanent license installation.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q186", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Apply the following steps to resolve the issue:\n\n 1. Create a xml response file (for example named uninstallTempCppLicense.xml ) with the following information.\n\n \n \n \n \n \n\n 2. Run the following command from a command prompt.\n\n /eclipse/tools/imcl.exe -input /uninstallTempCppLicense.xml\n\n 3. Run the installation of the permanent license file from the IBM Installation Manager installation wizard.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q186", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "When the complete path to the silent response file is not specified as part of the command invoking the silent install, it fails with the following error message in the log file:\n\n08-16-2012 09:52:31: Silent install configuration file: silent_response.txt\n08-16-2012 09:52:31:\n08-16-2012 09:52:31: AgentDeployRunning=FALSE.\n08-16-2012 09:52:31:\n08-16-2012 09:52:31: SEVERE: You must agree to the License Agreement.\n08-16-2012 09:52:31: SEVERE: Silent install config error.\n08-16-2012 09:52:31: Silent install config error.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q186", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Specify the complete path to the silent response file while launching the silent install.\n\ne.g.\nsetup /z\"/sfE:\\TEMP\\silent_response.txt\" /s /f2\"C:\\temp\\itm6_agent_setup.log\"", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q166", "section_id": 0, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24043005]\n8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]\n8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q166", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The IBM WebSphere MQ JCA Resource Adapter shipped with IBM\n WebSphere Application Server Version 8.5.5 needs to be updated\n to 7.1.0.7 + fix for WMQ-RA APAR IT15559 [http://www-01.ibm.com/support/docview.wss?uid=swg1IT15559] described in the\n following link:\n http://www-01.ibm.com/support/docview.wss?uid=swg1IT15559 [http://www-01.ibm.com/support/docview.wss?uid=swg1IT15559]", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q166", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of IBM WebSphere Application *\nServer WebSphere MQ JCA Resource Adapter *\n\nPROBLEM DESCRIPTION: The WebSphere MQ JCA Resource Adapter *\nshipped within WebSphere Application *\nServer requires updating. *\n\nRECOMMENDATION: *\n\nThe WebSphere MQ JCA Resource Adapter shipped within WebSphere\n Application Server is used by all applications connecting to\n WebSphere MQ from within the application server.\n WebSphere Application Server now ships a new version of\n WebSphere MQ fix pack 7.1.0.7 that also includes WMQ RA APAR\n IT15559 [http://www-01.ibm.com/support/docview.wss?uid=swg1IT15559].", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q166", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The fix for this APAR updates the WebSphere MQ JCA resource\n adapter shipped with WebSphere Application Server.\n With the fix applied, the following log entry should be seen\n on all servers on all nodes (except those where the 'Update\n resource adapter...' button has been used to manually update\n the resource adapter):\n WMSG1703I: RAR implementation version\n 7.1.0.7-k710-007-151026_IT15559 [http://www-01.ibm.com/support/docview.wss?uid=swg1IT15559]\n\nThe fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.5.11. Please refer to the Recommended Updates\n page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q166", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI70191\nREPORTED COMPONENT NAME\n WEBSPHERE APP S\nREPORTED COMPONENT ID\n 5724J0800\nREPORTED RELEASE\n 850\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-10-06\nCLOSED DATE\n 2016-11-15\nLAST MODIFIED DATE\n 2016-11-15\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q166", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBSPHERE APP S\nFIXED COMPONENT ID\n 5724J0800", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q166", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R850 PSY\n UP\n\nz/os SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q166", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Update the IBM WebSphere MQ JCA Resource Adapter shipped with\n IBM WebSphere Application Server Versions 7.0 and 8.0 to\n WebSphere MQ fix pack 7.0.1.6", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q166", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of IBM WebSphere Application *\nServer *\n\nPROBLEM DESCRIPTION: New maintenance is available for the *\nIBM WebSphere MQ JCA Resource Adapter. *\n\nRECOMMENDATION: *\n\nNew maintenance is available for the IBM WebSphere MQ JCA\n Resource Adapter shipped with the product.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q166", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The fix updates the version of the IBM WebSphere MQ JCA\n Resource Adapter shipped with the product to the latest\n available release, 7.0.1.6.\n\nThe fix for this APAR is currently targeted for inclusion in\n fix pack 7.0.0.21 and 8.0.0.2. Please refer to the Recommended\n Updates page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q166", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM78359\nREPORTED COMPONENT NAME\n WEBSPHERE FOR Z\nREPORTED COMPONENT ID\n 5655I3500\nREPORTED RELEASE\n 700\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2012-12-04\nCLOSED DATE\n 2012-12-04\nLAST MODIFIED DATE\n 2012-12-05\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n PM46219 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM46219]\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q166", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBSPHERE FOR Z\nFIXED COMPONENT ID\n 5655I3500", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q166", "section_id": 0, "heading": "CAUSE", "parent": null, "text": "WebSphere MQ (WMQ) Resource Adapter, shipped with WebSphere Application Server, had a defect which blocked the finalizer thread while closing a ServerSession object. This would then block the garbage collection of all objects with a finalize method, leading to OutOfMemory events. The largest heap user might be com.ibm.jsse2.SSLSocketImpl objects. This problem was fixed under WMQ APAR IV14093 which shipped with certain levels of WebSphere Application Server Fix Packs.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q166", "section_id": 1, "heading": "ENVIRONMENT", "parent": null, "text": "WebSphere Application Server V7.0, V8,0, V8.5", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q166", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Collect a heapdump and javacore from an OOM event. Use Memory Analyzer or IBM HeapAnalyzer for heapdump analysis. You might see \"com.ibm.jsse2.SSLSocketImpl\" as a leak suspect.\n\n(For example)\n16,985 instances of \"com.ibm.jsse2.SSLSocketImpl\" 594,807,720 (59.86%) byte\n\nIf corresponding javacore shows a Finalizer thread is waiting on \"com/ibm/mq/connector/inbound/ServerSessionImpl$IsInUseLock\", the root cause is most likely WMQ APAR IV14093.\n\n(For example)\n\"Finalizer thread\"\nWaiting on: com/ibm/mq/connector/inbound/ServerSessionImpl$IsInUseLock@0x976F7DE0 Owned by: \nJava callstack:\nat java/lang/Object.wait(Native Method)\nat java/lang/Object.wait(Object.java:167(Compiled Code))\nat com/ibm/mq/connector/inbound/ServerSessionImpl.close(ServerSessionImpl.java:285)\n(entered lock:com/ibm/mq/connector/inbound/ServerSessionImpl$IsInUseLock\n@0x976F7DE0, entry count: 1)\nat com/ibm/mq/connector/inbound/ServerSessionImpl.finalize(ServerSessionImpl.java:397)\nat java/lang/J9VMInternals.runFinalize(J9VMInternals.java:455(Compiled Code))", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q166", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Applying WebSphere Application Server Fix Pack 8.5.0.2, 8.0.0.5, 7.0.0.27 or a later Fix Pack.\n\nRecommended fixes for WebSphere Application Server\nhttp://www.ibm.com/support/docview.wss?uid=swg27004980 [http://www.ibm.com/support/docview.wss?uid=swg27004980]\n\nThe APAR is included in WMQ Fix Pack 7.0.1.9 and 7.1.0.2.\n\nIV14093: OUTOFMEMORYEXCEPTION IN WEBSPHERE APPLICATION SERVER DUE TO HUNG FINALIZER THREAD WHILE PROCESSING WMQ CONNECTION EVENT\nhttp://www.ibm.com/support/docview.wss?uid=swg1IV14093 [http://www.ibm.com/support/docview.wss?uid=swg1IV14093]\nWebSphere MQ Fix Pack 7.0.1.9\nWebSphere MQ Fix Pack 7.1.0.2\n\nThose version of WMQ are shipped with WebSphere Application Server Fix Pack in 8.5.0.2, 8.0.0.5 and 7.0.0.27.\n\nWhich version of WebSphere MQ is shipped with WebSphere Application Server ?\nhttp://www.ibm.com/support/docview.wss?uid=swg21248089 [http://www.ibm.com/support/docview.wss?uid=swg21248089]\n\nWebSphere Application Server Version 8.5 ships with the WebSphere MQ 7.1 Resource Adapter.\nWAS 8.5.0.2 - WMQ 7.1.0.2 - This level includes APAR IV14093\nWAS 8.5.0.1 - WMQ 7.1.0.1\nWAS 8.5.0.0 - WMQ 7.1.0.0\n\nWebSphere Application Server Version 8 ships with the WebSphere MQ 7.0 Resource Adapter.\nWAS 8.0.0.5 - WMQ 7.0.1.9 - This level includes APAR IV14093\nWAS 8.0.0.4 - WMQ 7.0.1.7\nWAS 8.0.0.3 - WMQ 7.0.1.7\nWAS 8.0.0.2 - WMQ 7.0.1.6\nWAS 8.0.0.1 - WMQ 7.0.1.5\n\nWebSphere Application Server Version 7 ships with the WebSphere MQ 7.0 Resource Adapter.\nWAS 7.0.0.27 - WMQ 7.0.1.9 - This level includes APAR IV14093\nWAS 7.0.0.25 - WMQ 7.0.1.7\nWAS 7.0.0.23 - WMQ 7.0.1.7\nWAS 7.0.0.21 - WMQ 7.0.1.6\nWAS 7.0.0.19 - WMQ 7.0.1.5\nWAS 7.0.0.17 - WMQ 7.0.1.4\n\n PRODUCT DOCUMENTATION", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q166", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This document contains the statement of support for the WebSphere MQ resource adapter provided with WebSphere MQ V7.1 and later.", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q166", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "WebSphere MQ V7.1 and later includes a J2EE Connector Architecture (JCA) V1.5 resource adapter. The resource adapter implements the JCA V1.5 interfaces and can be used in J2EE 1.4 (or later) compliant application servers to access the resources of a WebSphere MQ queue manager.\n\nUsing the resource adapter with WebSphere Application Server Version 7 and Version 8\nThe WebSphere MQ messaging provider in WebSphere Application Server Version 7 and Version 8 includes a version of the WebSphere MQ resource adapter. The version of the resource adapter supplied with the Application Server should be used in these environment.\n\nUpdates to the WebSphere MQ resource adapter that is installed with the application server are included in WebSphere Application Server Fix Packs.\n\nFor more details please see:\n\nInformation about using the WebSphere MQ messaging provider for WebSphere Application Server Version 7.0 [http://publib.boulder.ibm.com/infocenter/prodconn/v1r0m0/topic/com.ibm.scenarios.wmqwasusing.doc/topics/swg21316899.htm]\n\nInformation about using the WebSphere MQ messaging provider for WebSphere Application Server Version 8.0 [http://publib.boulder.ibm.com/infocenter/prodconn/v1r0m0/topic/com.ibm.scenarios.wmqwasusing.doc/topics/swg21498708.htm]\n[http://publib.boulder.ibm.com/infocenter/prodconn/v1r0m0/topic/com.ibm.scenarios.wmqwasusing.doc/topics/swg21498708.htm]\nInformation about using the WebSphere MQ messaging provider for WebSphere Application Server Version 8.5 [http://publib.boulder.ibm.com/infocenter/prodconn/v1r0m0/topic/com.ibm.scenarios.wmqwasusing.doc/topics/swg21498708_85.htm]\n\nIdentifying which WebSphere MQ client is shipped with WebSphere Application Server [http://publib.boulder.ibm.com/infocenter/prodconn/v1r0m0/topic/com.ibm.scenarios.wmqwasusing.doc/topics/swg21248089.htm]\n\nUsing the resource adapter with WebSphere Application Server Version 6.1\nThe resource adapter must not be used with WebSphere Application Server Version 6.1. To access the resources of a WebSphere MQ queue manager from within WebSphere Application Server, use the WebSphere MQ messaging provider. [http://publib.boulder.ibm.com/infocenter/prodconn/v1r0m0/topic/com.ibm.scenarios.wmqwasusing.doc/topics/swg21307203.htm]\nInformation about using WebSphere MQ as the JMS Provider for WebSphere Application Server Version 6.1 [http://publib.boulder.ibm.com/infocenter/prodconn/v1r0m0/topic/com.ibm.scenarios.wmqwasusing.doc/topics/swg21307203.htm]\n\nUsing the resource adapter with other application servers\nFor all other J2EE 1.4 (or later) compliant application servers, problems following successful completion of the WebSphere MQ resource adapter Installation Verification Test (IVT) can be reported to IBM for the investigation of WebSphere MQ product trace and other WebSphere MQ diagnostic information. If the WebSphere MQ resource adapter IVT cannot be run successfully, problems encountered are likely to be caused by incorrect deployment or incorrect resource definitions which are application server specific and the problems should be investigated using application server documentation and / or the support organization for that application server.\n\nIBM has tested the resource adapter on the application servers listed below\nWebSphere Application Server Community Edition V2.1.1.5\nJBoss Application Server V6.0.0", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q166", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Example scripts and detailed instructions for running the IVT with JBoss V6.0.0 and WAS CE V2.1.1.5 can be found in the WebSphere MQ 7.1 and V7.5 Information Centers.\n\nGeneral issues\n\nSession interleaving is not supported:\nSome application servers provide a capability called session interleaving, where the same JMS session can be used in multiple transactions, although it is only enlisted in one at a time. This is not supported by the WebSphere MQ resource adapter, and can lead to the issues shown below:\nAn attempt to put a message to a WebSphere MQ queue fails with reason code 2072 (MQRC_SYNCPOINT_NOT_AVAILABLE).\nCalls to xa_close() fail with reason code -3 (XAER_PROTO), and an FDC with probe ID AT040010 is generated on the WebSphere MQ queue manager being accessed from the application server.\n\nPlease see your application server documentation for how to disable this capability.\n\nJava\u2122 Transaction API (JTA) Specification of how XA resources are recovered for XA transaction recovery:\nSection 3.4.8 of the JTA specification does not define a specific mechanism by which XA resources are recreated to perform XA transactional recovery. As such, it is up to each individual transaction manager (and therefore application server) how XA resources involved in an XA transaction are recovered. It is possible that, for some application servers, the WebSphere MQ resource adapter does not implement the application server specific mechanism utilized to perform XA transactional recovery.\n\nIBM has tested XA transactional recovery with the WebSphere MQ 7.1 resource adapter on the following application servers:\nWebSphere Application Server V7.0, V8.0 and V8.5.\nWebSphere Application Server Community Edition V2.1.1.5\nJBoss Application Server V6.0.0\n\nORIGINAL PUBLICATION DATE\n 2011/10/11\n\nPRODUCT ALIAS/SYNONYM\n WMQ MQ", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q166", "section_id": 2, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24033606]\n8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24034672]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q166", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Update the IBM WebSphere MQ JCA Resource Adapter shipped with\n IBM WebSphere Application Server Version 8.5 to WebSphere MQ\n fix pack 7.1.0.1", "logical_doc_id": 5, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q166", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of IBM WebSphere Application *\nServer using the provided IBM WebSphere MQ *\nJCA Resource Adapter. *\n\nPROBLEM DESCRIPTION: New maintenance is available for the *\nIBM WebSphere MQ JCA Resource Adapter. *\n\nRECOMMENDATION: *\n\nNew maintenance is available for the IBM WebSphere MQ JCA\n Resource Adapter shipped with the product.", "logical_doc_id": 5, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q166", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The fix updates the version of the IBM WebSphere MQ JCA\n Resource Adapter shipped with the product to the latest\n available release, 7.1.0.1.\n\nThe fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.0.1. Please refer to the Recommended Updates\n page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q166", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM67639\nREPORTED COMPONENT NAME\n WEBSPHERE APP S\nREPORTED COMPONENT ID\n 5724J0800\nREPORTED RELEASE\n 850\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2012-06-26\nCLOSED DATE\n 2012-06-27\nLAST MODIFIED DATE\n 2012-06-27\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q166", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBSPHERE APP S\nFIXED COMPONENT ID\n 5724J0800", "logical_doc_id": 5, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q166", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R850 PSY\n UP", "logical_doc_id": 5, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q161", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Help page missing", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q161", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The file:\n*\nis incorrect in Impact 7.1.0.2 (Fix Pack 2) only.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q161", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "This issue is not pertinent to other subversions of Impact 7.1.0 - upgrade to Impact 7.1.0.3 or later.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q161", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "This TechNote is related to the series of TechNotes revolving around the subject of \"Avoiding unwanted event reprocessing\" - please see the TechNote of that title [link below].\n\nAs part of an Event Flagging*, Go_NoGo Checking**, UpdateEventQueue() function*** configuration the application of EventLocking can assist in preventing the unwanted multiple reprocessing of events. By setting EventLocking against a suitable field (for example: Identifier) to single thread processing of events with the same field value, we can ensure that only one copy of an event gets processed at a time.\n\nThe advantage of doing so is in preventing thread race conditions (where two or more threads are processing the same event simultaneously). This enables the UpdateEventQueue configuration to remove extra copies of the event from the EventReader EventQueue and the Event Flagging configuration to flag the event as being processed. If a copy of the event is the waiting in the EventProcessor EventQueue the Go_NoGo Checking will then find the flag value updated in the ObjectServer to show that the event has already been processed and the Go_NoGo Checking will then exit attempting to process the event again.\n\nThe configuration is achieved in the Event Mapping tab of the EventReader configuration editor pane by ticking the selection:\nand providing a valid field or field combination in the associated Expression space - for example:\n[/support/docview.wss?uid=swg21675051&aid=1]", "logical_doc_id": 2, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q161", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Please note that failing to provide a Expression value will result in processing failure - please see the TechNote \"Events captured, but not processed by EventReader\" [ link below]. Please also note that using EventLocking also restricts the processing to the Primary ImpactServer and can impinge upon the ability to process events efficiently.", "logical_doc_id": 3, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q161", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "- See TechNote \"Event flagging\" [ link below].", "logical_doc_id": 4, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q161", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "* - See TechNote \"Event Flagging with Go_NoGo checking\" [ link below].", "logical_doc_id": 5, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q161", "section_id": 0, "heading": "RELATED INFORMATION", "parent": null, "text": "Avoiding unwanted event reprocessing [http://www-01.ibm.com/support/docview.wss?uid=swg21386538]\nEvent flagging [http://www-01.ibm.com/support/docview.wss?uid=swg21626633]\nEvents captured but not processed by EventReader [http://www-01.ibm.com/support/docview.wss?uid=swg21575086]\nEvent Flagging with Go_NoGo checking [http://www-01.ibm.com/support/docview.wss?uid=swg21675015]\nRemoving duplicate event records from EventQueue with U [http://www-01.ibm.com/support/docview.wss?uid=swg21675016]", "logical_doc_id": 6, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q161", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "While it is possible that this problem could be caused by delays to event forwarding in a multi-tiered Netcool/OMNIbus architecture, the most likely cause of this behaviour is the state_change trigger.\n\nNormally, when an event is updated within Netcool/OMNIbus the StateChange field is updated to the current time by the Netcool/OMNIbus state_change trigger. WebGUI uses this field to determine whether to refresh the status of an event currently being displayed in the AEL, so if the trigger is disabled the status of the event in WebGUI will not be updated, even though the acknowledgement flag has been set in the ObjectServer.", "logical_doc_id": 7, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q161", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The EventReader stops acquiring events that are pertinent for processing because it is using a StateChange value that is too high.", "logical_doc_id": 8, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q161", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "An event has had its StateChange value artificially increased by some unknown component (Probe, Trigger, etc) to reflect a future date. The EventReader captures the event and then uses the highest captured StateChange value in its outgoing SQL to capture pertinent events.", "logical_doc_id": 8, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q161", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Pertinent events are not being processed. Looking in the EventReader log file the number of events being captured in each Read is 0. Testing the SQL being used in an nco_sql session produces a 0 result too. Testing the SQL again in an nco_sql session without the \"and StateChange >= 1234567890\" clause returns all the unprocessed rows.", "logical_doc_id": 8, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q161", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Something has \"future dated\" the StateChange value of an event in the ObjectServer, the EventReader captured the event and, since the EventReader will use the highest StateChange value captured in the previous poll in the SQL of its next poll, this then future dated the value used in the EventReader. The EventReader will persist with this value (and will increment it by 1 every other poll) until such a time as it captures an event with a higher StateChange value.\n\nThe simplest solution is to manually reset the EventReader StateChange value via the GUI. Stop the EventReader, open it for edit, click the \"Clear State\" button, exit the editor and restart the EventReader.\n\nAn alternate solution is to perform this operation via the Command Line Interface:\ntelnet [Hostname] [Port]\n\nwhere [Hostname] is the resolvable hostname of the ImpactServer host and [Port] is the CLI port number (2000, by default). You will need to supply a suitable username (admin, for example) and password. Then at the READY prompt enter the series of commands:\nUpdate Service set Running=false where Name='[EventReaderName]';\n* Update Service set ClearState=true where Name='[EventReaderName]';\n* Update Service set Running=true where Name='[EventReaderName]';\n\nwhere [EventReaderName] is the name of the EventReader that requires this restart process.\n\nIn cases where the likelihood of StateChange being inappropriately incremented in this fashion is quite high, one might wish to automate this process and have a Policy hunt for such occurrences. Please find following an example of a \"hunter\" Policy to capture any reoccurrence of this issue:\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n* ANN=\"AcquireStateChange\";\n Log(2,ID+ANN);\n Script=\"/opt/IBM/netcool/impact/bin/CheckState.sh\";\n Parameter=\"password\";\n JRExecAction(Script, Parameter, false, 30);\n NumExecOutput=Length(ExecOutput);\n Log(3,ID+ANN+\": NumExecOutput: \"+NumExecOutput);\n\nIf(NumExecOutput >= 1)\n { *\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n* Log(ID+ANN+\": CurrentStateChange: \"+HumanStateChange+\" is greater than CurrentTime: \"+HumanCurrentTime);\n Log(ID+ANN+\": !!! Clearing EventReader State !!!\");\n Script=\"/opt/IBM/netcool/impact/bin/ClearState.sh\";\n Parameter=\"password\";\n JRExecAction(Script, Parameter, false, 30);\n*\n*\n* Log(1,ID+ANN+\": CurrentStateChange: \"+HumanStateChange+\" is less than CurrentTime: \"+HumanCurrentTime);\n*\n*\n* Log(ID+ANN+\": !!! There is some freaky stuff happening here !!! - CurrentStateChange: \"+HumanStateChange+\" and CurrentTime: \"+HumanCurrentTime+\" !!! \");\n}\n Else\n { *\n\n}\n*\n*\n* Log(3,ID+ANN+\": No UnprocessedEvents\");\n*\n*\n*", "logical_doc_id": 8, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q161", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "As you can see this is designed to be run by a PolicyActivator and checks for events that have been around in the ObjectServer for a while (a minute) and are pertinent for processing by Impact (ImpactFlag = 1), but have not. If it finds any it then acquires the StateChange value from the .state file via JRExecServer using the example script referred to in the above example Policy as CheckState.sh:\n*\n*\n*\nIf the Policy finds the string it extracts the StateChange value and compares it against the current time and, if StateChange exceeds the current time, it undertakes the stop, clear and restart of the EventReader to bring StateChange back into line.\n\nThis examples a simple script to use the Command Line Interface to stop the EventReader, clear the StateChange value and restart the EventReader and is referred to in the above exampled Policy as ClearState.sh:\n*\n*\n*\n*\n*\n*\n*\nPlease note that the ClearState.sh script should not contain any spaces or special characters otherwise calling EOF will throw errors. Also, in latter versions of Impact, the username and password should be those of the tipadmin. Additionally, rather than have the password sitting clear case in a script one can pass it as a JRExecAction Parameter from the Policy - still clear case but the relevance of the variable can be made less obvious.\n\nBoth of these scripts are called by the JRExecAction() function in the example Policy and this in turn requires the JRExecServer to be running on the ImpactServer host(s *).", "logical_doc_id": 8, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q161", "section_id": 0, "heading": "RELATED INFORMATION", "parent": null, "text": "JRExecAction() function usage [http://www-01.ibm.com/support/docview.wss?uid=swg21515756]\n\nDIRECT LINKS TO FIXES\n7.1.0-TIV-NCI-ZLINUX-FP0012 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-ZLINUX-FP0012&source=SAR]\n7.1.0-TIV-NCI-WINDOWS-FP0012 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-WINDOWS-FP0012&source=SAR]\n7.1.0-TIV-NCI-SOLARIS-FP0012 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-SOLARIS-FP0012&source=SAR]\n7.1.0-TIV-NCI-LINUX-FP0012 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-LINUX-FP0012&source=SAR]\n7.1.0-TIV-NCI-AIX-FP0012 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-AIX-FP0012&source=SAR]\nIBM Tivoli Netcool/Impact V7.1.0 Fix Pack 12 (7.1.0-TIV-NCI-FP0012) [http://www-01.ibm.com/support/docview.wss?uid=swg24044312]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 9, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q161", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Product: IBM Tivoli Netcool Impact 7.1.0\n Release: 7.1.0 FP9\n Severity: 3\n\nProblem Description: IBM Tivoli Netcool Impact 7.1.0\n\nRelated Events & Seasonal Event Analytics reporter Database\n timestamp issue.\n\nInstalled Related Events and Seasonal Event Analytics.\n The environment includes used Impact 7.1.0.9, WebGui 8.1.0.8,\n OMNIbus 8.1.0.11.\n The MSSQL database is configured to use 'dd.MM.yyyy hh:mm:ss'\n\nconfigured history_db_timestampformat=dd.MM.yyyy hh:mm:ss\n using the ./nci_trigger NCI impactadmin/impactpass\n NOI_DefaultValues_Export FILENAME /tmp/NOI_DefaultValues.props\n and\n ./nci_trigger NCI impactadmin/impactpass\n NOI_DefaultValues_Configure\n FILENAME /tmp/NOI_DefaultValues.props\n\nWhich leads to several parsing issues \"Could not convert varchar\n to datetime ... out of range\".\n Errors found in the standard Impact policylogger - log file\n each time they activate one of the RE/SE services.\n\nPolicy RE_CONFIGURE, line #160 reads:\n\nvar analyseStartTime = LocalTime(startTime,\n dateFormatToInsert);\n var analyseEndTime = LocalTime(endTime, dateFormatToInsert);\n\nfurther down in line #172 reads:\n\nfilterForResults = noiHistory.getResultsFilter(\"1=0\",\n ALERT_DATE_COLUMN, analyseStartTime, analyseEndTime);\n\nanalyseStartTime and analyseEndTime are used for the analysis of\n the history database (MSSQL) and the start and end time of\n the analysis is being formatted using the format\n dateFormatToInsert.\n\ndateFormatToInsert is defined in the policy NOI_CONSTANTS\n in line #151 which reads:\n\nvar dateFormatToInsert = 'yyyy-MM-dd HH:mm:ss.SSS';\n\nAnalysis and findings by L3\n\n01 Aug 2017 17:09:29,449:\n [RE_CONFIGURE][pool-2-thread-141]Parser log:\n RE_CONFIGURE: Filter for Results: ((Severity=3) AND (\n FIRSTOCCURRENCE >\n '2013-07-28 00:00:00.000' )) AND ( FIRSTOCCURRENCE < '2013-07-31\n 23:59:59.000')\n\nfor\n\nconfiguration_db_timestampformat yyyy-MM-dd HH:mm:ss.SSS\n history_db_timestampformat yyyy-MM-dd HH:mm:ss.SSS\n\naka defaults.\n\n// Default values\n var dateFormatToInsert = 'yyyy-MM-dd HH:mm:ss.SSS';\n\nConversionn uses LocalTime. Policy Function. Where MM is month,\n d is day\n and yyyy is year.\n\ni.e. set format to dd/M/yyyy and make appropriate changes to\n NOI_CONSTANTS and RE_CONFIGURE policies.\n\nThis eliminates errors in NCI_policylogger_RE_CONFIGURE.log but\n changes\n also needed in NCI_ConfigureResults.\n\nThe above 3 policies need changes for the Configuration to be\n created.\n Other changes needed for running configuration.\n\nSE_PROCESSCONFIG -", "logical_doc_id": 10, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q161", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "01 Aug 2017 12:05:00,564:\n [SE_PROCESSCONFIG][pool-2-thread-96]Parser\n log: Executing processing for job: RESULTID = 8 AND STATUS = 4\n AND\n ERRORSTEP = 0 AND ISFILTERINCLUDE is null AND ROWSPROCESSED =\n 0.0 AND\n TOTALROWSTOBEPROCESSED = 5582.0 AND CREATIONTIME = 1501603469\n AND\n RESULT_START_TIME = '2009-03-17 05:29:22.0' AND RESULT_END_TIME\n =\n '2017-07-17 05:29:22.0' AND IMPACT_DATASOURCE_NAME is null AND\n IMPACT_DATATYPE_NAME is null AND TIMESTAMP_COLUMN_NAME is null\n AND\n ROW_IDENTIFER_COLUMN_NAME is null AND RESULTNAME = 'mssql' AND\n CUSTOMERID = 'geraldine' AND ALGORITHM_COLUMNNAMES is null AND\n DESCRIPTION = AND RESULT_FILTER = 'Severity>1' AND\n FILTER_RUN_VALUE =\n 100 AND FILTER_RUN_TYPE = 'MONTHS' AND REPORTDATETYPE =\n 'RELATIVE' AND\n EVENTIDENTITIES = 'USINGGLOBALSETTINGS' AND PROCESSSTEP = 7 AND\n REPORTTYPE = 'Seasonality' AND AUTO_DEPLOY = 'false' AND\n SCHEDULED =\n 'false' AND SCHEDULED_VALUE = 0 AND SCHEDULED_TYPE = 'MONTHS'\n AND\n PROFILEID = 2 AND IS_RELATED_EVENT = 'true' AND SELECTEDFIELDS\n is null\n AND START_TIME = '2017-08-01 12:04:29.0' AND PREV_START_TIME is\n null AND\n PROGRESS = 0 AND LAST_RUN_DURATION = '00:40:02' AND\n OVERRIDEGLOBALEVENTIDENTITY = 'false' AND PROCESSING_ORDER = 1\n\n01 Aug 2017 12:05:19,245:\n [SE_PROCESSCONFIG][pool-2-thread-96]Caused by:\n com.micromuse.response.common.PolicyProcessingException:\n JavaException:\n com.microsoft.sqlserver.jdbc.SQLServerException: The conversion\n of a\n varchar data type to a datetime data type resulted in an\n out-of-range\n value. (pool-2-thread-97#88) in seasonalityProcess\n\nThis looks like a Derby select - though that format is\n unchanged.\n SE_PROCESSCONFIG calls seasonalityProcess policy. This is where\n the real\n error is\n\n01 Aug 2017 18:24:55,056:\n [seasonalityProcess][pool-2-thread-161]Parser\n log: TIME 04a: Loading data from DB\n 01 Aug 2017 18:24:55,056:\n [seasonalityProcess][pool-2-thread-161]Parser\n log: Inside getData\n 01 Aug 2017 18:24:55,056:\n [seasonalityProcess][pool-2-thread-161]Parser\n log: Query : SELECT\n SUMMARY,SEVERITY,NODE,ALERTGROUP,FIRSTOCCURRENCE,IDENTIFIER,SERV\n ERNAME,S\n ERVERSERIAL,OWNERUID,ACKNOWLEDGED,TALLY FROM\n dbo.REPORTER_STATUS WHERE\n ((Severity=3) AND ( FIRSTOCCURRENCE > '2013-07-28 00:00:00.000'\n )) AND (\n FIRSTOCCURRENCE < '2013-07-29 00:00:00.000') AND (SEVERITY >=0)\n 01 Aug 2017 18:24:55,250:\n [seasonalityProcess][pool-2-thread-161]Parser\n log: WARNING!!! Unable to retrieve event history, retrying...\n\n01 Aug 2017 18:24:55,251:\n [seasonalityProcess][pool-2-thread-161]Parser\n log: Inside getData\n 01 Aug 2017 18:24:55,251:\n [seasonalityProcess][pool-2-thread-161]Parser\n log: Query : SELECT\n SUMMARY,SEVERITY,NODE,ALERTGROUP,FIRSTOCCURRENCE,IDENTIFIER,SERV\n ERNAME,S\n ERVERSERIAL,OWNERUID,ACKNOWLEDGED,TALLY FROM\n dbo.REPORTER_STATUS WHERE\n ((Severity=3) AND ( FIRSTOCCURRENCE > '2013-07-28 00:00:00.000'\n )) AND (\n FIRSTOCCURRENCE < '2013-07-29 00:00:00.000') AND (SEVERITY >=0)\n\n01 Aug 2017 18:24:55,434:\n [seasonalityProcess][pool-2-thread-161]Parser\n log: Error in retrieving data from the history table:\n JavaException:\n com.microsoft.sqlserver.jdbc.SQLServerException: The conversion\n of a\n varchar data type to a datetime data type resulted in an\n out-of-range\n value.\n\nseasonalityProcess.js also need to be changed.", "logical_doc_id": 10, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q161", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nAll Impact Users *\n\nPROBLEM DESCRIPTION: *\nUsing MSSQL as the reporting database, the RE and SE NOI *\nreports have issues when the timestamp is different from *\n*\nstandard US timestamps. In the customer's case, the MSSQL *\ndatabase is configured to use 'dd.MM.yyyy hh:mm:ss'. *\n*\nNote: By default MSSQL using American date time format. *\n*\nErrors in the NOI policy logs are *\ncom.microsoft.sqlserver.jdbc.SQLServerException: The *\nconversion of a varchar data type to a datetime data type *\nresulted in an out-of-range value. *\n\nRECOMMENDATION: *", "logical_doc_id": 10, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q161", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV98662\nREPORTED COMPONENT NAME\n NC/IMPACT RTID\nREPORTED COMPONENT ID\n 5724O5900\nREPORTED RELEASE\n 710\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2017-08-02\nCLOSED DATE\n 2017-10-13\nLAST MODIFIED DATE\n 2017-10-13\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\nUNKNOWN", "logical_doc_id": 10, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q161", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n NC/IMPACT RTID\nFIXED COMPONENT ID\n 5724O5900", "logical_doc_id": 10, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q161", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R710 PSY\n UP", "logical_doc_id": 10, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q035", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "OpenSSL vulnerabilities were disclosed by the OpenSSL project. OpenSSL is used by the Cordova tools in IBM Rational Application Developer for WebSphere Software. IBM Rational Application Developer for WebSphere Software has addressed the applicable CVEs.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q035", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-8610 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8610]\nDESCRIPTION: SSL/TLS protocol is vulnerable to a denial of service, caused by an error when processing ALERT packets during a SSL handshake. By sending specially-crafted packets, a remote attacker could exploit this vulnerability to cause the application to stop responding.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118296 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118296] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)\n\nCVEID: CVE-2017-3730 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3730]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by a NULL pointer dereference. By sending specially crafted parameters for a DHE or ECDHE key exchange, a remote attacker could exploit this vulnerability to cause the application to crash.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/121311 [https://exchange.xforce.ibmcloud.com/vulnerabilities/121311] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)\n\nCVEID: CVE-2017-3731 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3731]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an out-of-bounds read when using a specific cipher. By sending specially crafted truncated packets, a remote attacker could exploit this vulnerability using CHACHA20/POLY1305 to cause the application to crash.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/121312 [https://exchange.xforce.ibmcloud.com/vulnerabilities/121312] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)\n\nCVEID: CVE-2017-3732 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3732]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by a propagation error in the BN_mod_exp() function. An attacker could exploit this vulnerability to obtain information about the private key.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/121313 [https://exchange.xforce.ibmcloud.com/vulnerabilities/121313] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\nCVEID: CVE-2016-7055 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7055]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an error in a Broadwell-specific Montgomery multiplication procedure. By sending specially crafted data, a remote attacker could exploit this vulnerability to trigger errors in public-key operations in configurations where multiple remote clients select an affected EC algorithm and cause a denial of service.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118748 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118748] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q035", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2017-3733 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3733]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an error during a renegotiate handshake when the original handshake did not include the Encrypt-Then-Mac extension. A remote authenticated attacker could exploit this vulnerability to cause the application to crash.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/122091 [https://exchange.xforce.ibmcloud.com/vulnerabilities/122091] 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-6799 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6799]\nDESCRIPTION: Apache Cordova Android could allow local attacker to obtain sensitive information, caused by a flaw in the Log class. An attacker could exploit this vulnerability to obtain sensitive information.\nCVSS Base Score: 4.0\nCVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/125857 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125857]for more information\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q035", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Rational Application Developer for WebSphere Software v9.1, v9.5 and v9.6", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q035", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Update the IBM SDK for Node.js using by the Cordova platform in the product to address this vulnerability:\n\nProduct VRMF APAR Remediation/First Fix Rational Application Developer 9.1 PI83070 Apply the following fixes: * Rational-RAD91x-Cordova-ifix [https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=ibm~Rational&product=ibm/Rational/IBM+Rational+Application+Developer+for+WebSphere+Software&release=All&platform=All&function=fixId&fixids=Rational-RAD91x-Cordova-ifix&includeRequisites=1&includeSupersedes=0&downloadMethod=http]\nHybridMobileFeaturePatch91 [https://rcs-testfix2.ratl.swg.usma.ibm.com/cgi-bin/fix_portal.pl?do_view=RAD-8GW7CcBTQX9M]\n\nRational Application Developer 9.5 PI83070 Apply the following fixes: * Rational-RAD95x-Cordova-ifix [https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=ibm~Rational&product=ibm/Rational/IBM+Rational+Application+Developer+for+WebSphere+Software&release=All&platform=All&function=fixId&fixids=Rational-RAD95x-Cordova-ifix&includeRequisites=1&includeSupersedes=0&downloadMethod=http]\nHybridMobileFeaturePatch95 [https://rcs-testfix2.ratl.swg.usma.ibm.com/cgi-bin/fix_portal.pl?do_view=RAD-51rhRQy6NBL2]\n\nRational Application Developer 9.6 PI83070 * Apply IBM SDK for Node.js Version 6 release updated equivalent to the Joyent Node.js API version 6.10.3 [https://developer.ibm.com/node/sdk/v6/] to the Cordova platform in the product.\n\nInstallation instructions for applying the update to the Cordova platform in the product can be found here:\n\nUpgrading the IBM SDK for Node.js used by Cordova [http://www.ibm.com/support/docview.wss?uid=swg21684946]", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q035", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q035", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 0, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q035", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 18 July 2017: Original document published\nThe 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.", "logical_doc_id": 0, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q035", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "OpenSSL vulnerabilities were disclosed on December 3, 2015 by the OpenSSL Project. OpenSSL is used by Rational Software Architect and Rational Software Architect for WebSphere Software. The applicable CVEs have been addressed.", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q035", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2015-3193 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3193]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error in the x86_64 Montgomery squaring procedure. An attacker with online access to an unpatched system could exploit this vulnerability to obtain private key information.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/108502 [https://exchange.xforce.ibmcloud.com/vulnerabilities/108502] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\nCVEID: CVE-2015-3194 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3194]\n\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by a NULL pointer dereference when verifying certificates via a malformed routine. An attacker could exploit this vulnerability using signature verification routines with an absent PSS parameter to cause any certificate verification operation to crash.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/108503 [https://exchange.xforce.ibmcloud.com/vulnerabilities/108503] 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-2015-3195 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3195]\n\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by a memory leak in a malformed X509_ATTRIBUTE structure. An attacker could exploit this vulnerability to obtain CMS data and other sensitive information.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/108504 [https://exchange.xforce.ibmcloud.com/vulnerabilities/108504] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\nCVEID: CVE-2015-3196 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3196]\n\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by a race condition when PSK identity hints are received by a multi-threaded client and the SSL_CTX structure is updated with the incorrect value. An attacker could exploit this vulnerability to possibly corrupt memory and cause a denial of service.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/108505 [https://exchange.xforce.ibmcloud.com/vulnerabilities/108505] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L)\n\nCVEID: CVE-2015-1794 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1794]\n\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by an error when a client receives a ServerKeyExchange for an anonymous DH ciphersuite with the value of p set to 0. An attacker could exploit this vulnerability to trigger a segfault and cause a denial of service.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/108539 [https://exchange.xforce.ibmcloud.com/vulnerabilities/108539] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/Au:N/C:N/I:N/A:P)", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q035", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Rational Software Architect and Rational Software Architect for WebSphere Software: Ver 9.1 through 9.5", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q035", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Update the IBM SDK for Node.js using by the Cordova platform in the product to address this vulnerability:\n\nProduct VRMF [/support/docview.wss?uid=swg21974243&aid=1] Remediation/First Fix Rational Software Architect and Rational Software Architect for WebSphere Software 9.1, 9.1.x, and 9.5 [/support/docview.wss?uid=swg21974243&aid=2] * * Apply IBM SDK for Node.js Version 1.1 release updated equivalent to the Joyent Node.js API version 0.10.41 [http://www.ibm.com/developerworks/web/nodesdk/] to the Cordova platform in the product.\n\nInstallation instructions for applying the update to the Cordova platform in the product can be found here:\n\nUpgrading the IBM SDK for Node.js used by Cordova [http://www.ibm.com/support/docview.wss?uid=swg21684946]", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q035", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q035", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] CHANGE HISTORY\n 07 January 2016 Original Version Published\nThe 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\nCross reference information Segment Product Component Platform Version Edition Software Development Rational Software Architect Designer 9.5 Software Development Rational Software Architect for WebSphere Software Modeling Linux, Windows 9.1, 9.1.1, 9.1.2, 9.1.2.1 Software Development Rational Software Architect Designer for WebSphere Software 9.5", "logical_doc_id": 1, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q035", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Two ReDoS vulnerabilities in modules included in the Node.js npm tool shipped by IBM Rational Application Developer for WebSphere Software.", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q035", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2016-2515 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2515]\nDESCRIPTION: Node.JS hawk is vulnerable to a denial of service, caused by an error in the regular expression implementation. An attacker could exploit this vulnerability using an overly long header or URI to cause the application to hang.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/110819 [https://exchange.xforce.ibmcloud.com/vulnerabilities/110819] 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-2537 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2537]\nDESCRIPTION: Node.js is vulnerable to a denial of service, caused by an error in the regular expression implementation. An attacker could exploit this vulnerability using a regular expression to block the event loop and cause the application to hang.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/110870 [https://exchange.xforce.ibmcloud.com/vulnerabilities/110870] 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)", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q035", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM Rational Application Developer for WebSphere Software v9.1 and v9.5", "logical_doc_id": 2, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q035", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Rational Application Developer 9.1.x and 9.5.x PI60929 * Apply IBM SDK for Node.js Version 1.1 release updated equivalent to the Joyent Node.js API version 0.10.44 [https://developer.ibm.com/node/sdk/#v11] to the Cordova platform in the product.\n\nInstallation instructions for applying the update to the Cordova platform in the product can be found here:\n\nUpgrading the IBM SDK for Node.js used by Cordova [http://www.ibm.com/support/docview.wss?uid=swg21684946]", "logical_doc_id": 2, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q035", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q035", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] 16 May 2016: Original Version Published *The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.\n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.", "logical_doc_id": 2, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q035", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "Denial of service vulnerability in module semver, used by the npm package management tool", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q035", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID:CVE-2015-8855 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8855]\nDESCRIPTION:The Node.js semver module is vulnerable to a denial of service, caused by an error in the regular expression implementation. An attacker could exploit this vulnerability using a regular expression to cause the application to hang.\nCVSS Base Score: 5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/112562 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112562]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)\n\nThe semver module included in IBM SDK for Node.js is a bundled dependency of the Node Package Manager (npm). This module instance is not normally exposed to end users of IBM SDK for Node.js.", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q035", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "These vulnerabilities affect IBM SDK for Node.js v1.1.0.20 and previous releases.\nThese vulnerabilities affect IBM SDK for Node.js v1.2.0.1 and previous releases.", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q035", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "The fixes for these vulnerabilities are included in IBM SDK for Node.js v1.1.1.0 and subsequent releases.\nThe fixes for these vulnerabilities are included in IBM SDK for Node.js v1.2.0.2 and subsequent releases.\n\nIBM SDK for Node.js can be downloaded, subject to the terms of the developerWorks license, from here [http://www.ibm.com/developerworks/web/nodesdk/].\n\nIBM customers requiring an update for an SDK shipped with an IBM product should contact IBM support [http://www.ibm.com/support/], and/or refer to the appropriate product security bulletin.", "logical_doc_id": 3, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q035", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 3, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q035", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] CHANGE HISTORY\n May 9 2016: Original version published\nThe 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.", "logical_doc_id": 3, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q035", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM API Connect has addressed the following vulnerability.\n\nNode.js is vulnerable to a denial of service, caused by an uncaught exception flaw in the zlib module. By making 8 an invalid value for the windowBits parameter, a remote attacker could exploit this vulnerability to cause the application to crash.", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q035", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID:CVE-2017-14919 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14919]\nDESCRIPTION:Node.js is vulnerable to a denial of service, caused by an uncaught exception flaw in the zlib module. By making 8 an invalid value for the windowBits parameter, a remote attacker could exploit this vulnerability to cause the application to crash.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/134286 [https://exchange.xforce.ibmcloud.com/vulnerabilities/134286]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q035", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Affected API Connect Affected Versions IBM API Connect 5.0.0.0-5.0.6.4 IBM API Connect 5.0.7.0-5.0.7.2 IBM API Connect 5.0.8.0-5.0.8.1 REMEDIATION/FIXES\n\nAffected Product Addressed in VRMF APAR Remediation/First Fix IBM API Connect\n\nV5.0.0.0 - 5.0.6.4 5.0.6.5 LI79994 Addressed in IBM API Connect V5.0.6.5.\n\nFollow this link and find the \"APIConnect-Portal\" package.\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.4&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.2&platform=All&function=all] IBM API Connect\n\nV5.0.7.0 - 5.0.7.2 5.0.8.2 LI79994 Addressed in IBM API Connect V5.0.8.2.\n\nFollow this link and find the \"APIConnect_Management\" and \"APIConnect-Portal\" packages.\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.8.1&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.2&platform=All&function=all] IBM API Connect\n\nV5.0.8.0 - 5.0.8.1 5.0.8.2 LI79994 Addressed in IBM API Connect V5.0.8.2.\n\nFollow this link and find the \"APIConnect_Management\" and \"APIConnect-Portal\" packages.\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.8.1&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.2&platform=All&function=all] GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q035", "section_id": 3, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q035", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nCHANGE HISTORY\n 08 February 2018: original document published\nThe 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.", "logical_doc_id": 4, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q282", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This new gateway will be ready for downloading on November 24, 2016.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q282", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "This version addresses the following enhancement requests:\nRFE 85941: Enhancement to add HTTP proxy support. New property updated to specify the HTTP proxy with optional port.\nRFE 88118: Enhancement to allow the gateway to accommodate a change in REST API behavior between ServiceNow versions Eureka/Fiji compared to Geneva.\n\nYou can download the installation package from the IBM Passport Advantage website:\nwww.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\n\nYou can access the latest version of the guide written for this gateway on the IBM Knowledge Center:\n\nwww.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/gateways/snowgw/wip/concept/snowgw_intro.html [https://www.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/gateways/snowgw/wip/concept/snowgw_intro.html]\n\nNetcool/OMNIbus V8.1\n\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the gateway for all supported Operating Systems. To obtain this new package, use the Find by part number field to search for part number: CNFT1EN\n\nNote: The Netcool/OMNIbus V8.1 version of this gateway supports the following Operating Systems: AIX, Linux, Solaris, Windows and zLinux.\n\nNetcool/OMNIbus V7.4.0\n\nIf you are running Netcool/OMNIbus V7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.\n\nPart number Operating System CNFQ2EN AIX CNFQ3EN HP-UX Integrity CNFQ4EN Linux for zSeries CNFQ5EN Linux CNFQ6EN Solaris CNFQ7EN Windows Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.\n\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website: https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html]\n\nrelease notice; downloads; Netcool/OMNIbus Gateway NGtkTK Support Package; (libngtktk 4_0) NEWS", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q282", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "A new version of the Netcool/OMNIbus Gateway NGtkTK Support Package will be available to download from November 30, 2012.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q282", "section_id": 3, "heading": "CONTENT", "parent": null, "text": "The support package has been repackaged to coincide with the release of Netcool/OMNIbus V7.4. The new package is functionally identical to the old package; it is only the licensing that has changed. Additional information may be found in the announcement letter US reference 212-459 dated November 27, 2012.\n\nYou can download the installation package from the IBM Passport Advantage website:\nwww.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\n\nThe part numbers for both the old package and the new package are given in the table below. The part number that you download depends on which version of Netcool/OMNIbus that you have installed because that determines which eAssembly you can access when you visit the IBM Passport Advantage website. The previous package is currently available on the IBM Tivoli Netcool/OMNIbus Gateway Tier 1 and 2 eAssembly. The new package is available on the IBM Tivoli Netcool/OMNIbus Data Exchange Tier and Gateways under OMNIbus Tier eAssembly.\n\nTo obtain this new package, search for the part number that corresponds to your operating system as shown in the table below. You can also search for the package by name, or by operating system.\n\nNetcool/OMNIbus Gateway Tier 1 and 2 eAssembly Netcool/OMNIbus Data Exchange Tier and Gateways under OMNIbus Tier eAssembly Operating System CI9CHEN CIDU6EN AIX CI9CIEN CIDU7EN HP-UX PA-RISC CI9CJEN CIDU8EN HPUX on Itanium CI9CLEN CIDV0EN Linux CI9CKEN CIDU9EN Linux for zSeries CI9CMEN CIDV1EN Solaris CI9CNEN CIDV2EN Windows Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.\n\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:\n\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q282", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The Netcool/OMNIbus ODBC Gateway Reference Guide available from\n\nhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp [http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp]\n\nstates:\n\n\"The Informix and DB2 versions of the ODBC Gateway do not\n support full data exchange with IBM Tivoli Netcool/Reporter.\"\n\non page 4.\n\nThis should only apply to Informix, as DB2 is supported for\n Reporter but Informix isn't.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q282", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of the ODBC Gateway. *\n\nPROBLEM DESCRIPTION: The Netcool/OMNIbus ODBC Gateway *\nReference Guide incorrectly states that *\nthe DB2 version of the ODBC Gateway *\ndoes not support full data exchange *\nwith IBM Tivoli Netcool/Reporter. It *\nis only the Informix version of the *\ngateway that does not support full data *\nexchange with IBM Tivoli *\nNetcool/Reporter. *\n\nRECOMMENDATION: *\n*\n\nThe reference to the DB2 versions of the ODBC Gateway as\n unsupported for full data exchange with IBM Tivoli\n Netcool/Reporter will be removed.\n\nThe third sentence of the IBM Tivoli/Reporter topic in the\n Overview will be changed to:\n\nThe Informix version of the ODBC Gateway does not support full\n data exchange with IBM Tivoli Netcool/Reporter.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q282", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The product documentation will be updated with the next release\n of the gateway.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q282", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IZ22010\nREPORTED COMPONENT NAME\n OMNI DB2 GATEWA\nREPORTED COMPONENT ID\n 5724O71DB\nREPORTED RELEASE\n 100\nSTATUS\n CLOSED DOC\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2008-05-08\nCLOSED DATE\n 2008-05-21\nLAST MODIFIED DATE\n 2008-05-21\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nPublications Referenced SC23639600 FIX INFORMATION", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q282", "section_id": 6, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "release note; downloads; nco-g-socket-java; Java Gateway for Socket NEWS", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q282", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "A new version of the Netcool/OMNIbus Socket Gateway will be available to download from August 6, 2015.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q282", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "You can access the latest version of the guide written for this gateway on the IBM Knowledge Center:\n\nwww.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/gateways/socketjavagw/wip/concept/socketjavagw_instl_cnfgr_gateway.html [http://www.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/gateways/socketjavagw/wip/concept/socketjavagw_instl_cnfgr_gateway.html]\n\nYou can download the installation package from the IBM Passport Advantage website:\nwww.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\n\nNetcool/OMNIbus V8.1\n\nThe Netcool/OMNIbus V8.1 version of this gateway supports the following Operating Systems:\n\nAIX, Linux, Solaris, Windows and zLinux.\n\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the gateway for all supported Operating Systems. To obtain this package, use the Find by part number field to search for part number: CN6I1EN\n\nNetcool/OMNIbus V7.4.0\n\nIf you are running Netcool/OMNIbus V7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.\n\nPart number Operating System CN6GZEN AIX CN6H1EN HPUX on Itanium CN6H2EN Linux CN6H3EN Linux for zSeries CN6H4EN Solaris CN6H5EN Windows Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.\n\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:\n\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html]", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q282", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "ODBC Gateway : How can you check the ODBCINI file works?", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q282", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The ODBC Gateway log messages can be hard to understand due to the volume of messages written in production environments.\n\nThe latest test fix ODBC libraries include the bind23 binary for testing connections defined in the ODBCINI file.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q282", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Note: It is recommended that you upgrade to the JDBC Gateway as the ODBC drivers are no longer maintained\n\nIf you are using the current GA product, the latest ODBC Gateway and libraries can be requested from IBM Netcool support.\n\nDefine a test ODBCINI file and database connection:\nYou can test an ODBCINI file using the bind command provided with the ODBC library package:\ne.g.\nexport ODBCINI\nODBCINI=/tmp/odbc.ini\n\nvi /tmp/odbc.ini\n[ODBC Data Sources]\nDB2=DataDirect 5.3 DB2 Wire Protocol\n\n[ODBC]\nIANAAppCodePage=4\nInstallDir=/opt/IBM/tivoli/netcool/omnibus/platform/aix5\nTrace=0\nTraceFile=/opt/IBM/tivoli/netcool/omnibus/log/G_ODBC.odbctrace.out\nTraceDll=/opt/IBM/tivoli/netcool/omnibus/platform/aix5/lib/odbctrac.so\n\n[DB2]\nDriver=/opt/IBM/tivoli/netcool/omnibus/platform/aix5/lib/BMdb223.so\nDescription=DataDirect 5.3 DB2 Wire Protocol\n#Database applies to DB2 UDB only\nDatabase=ODBCGW\nIpAddress=orion.sbank.uk.ibm.com\nTcpPort=50000\n#\nAuthenticationMethod=0\n#EOF\n\nSet the environment for using the bind command and run the bind23 command:\nLIBPATH=/opt/IBM/tivoli/netcool/omnibus/platform/aix5/lib\nexport LIBPATH\ncd $LIBPATH\n./bind23 DB2\nUser Name: reporter\nPassword:\nSecurityMechanism: '0'\nCreating packages ...Packages created and bound.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q282", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "ODBC Gateway product status [http://www-01.ibm.com/support/docview.wss?uid=swg21641166]\nSupport's guide to the JDBC Gateway [http://www-01.ibm.com/support/docview.wss?uid=swg21608681]", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q150", "section_id": 0, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24033190]\n8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24033606]\n8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24033754]\n8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24034672]\n8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24034673]\n8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24035457]\n8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24036729]\n8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24037574]\n8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24039242]\n8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24040425]\n8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24041590]\n8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24042746]\n8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http://www-01.ibm.com/support/docview.wss?uid=swg24044096]\n8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q150", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Profile creation in BPM fails with an OutOfMemoryException in\n profileTemplates\\default\\actions\\postinstallManagement.ant", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q150", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of IBM WebSphere Application *\nServer V8.0 and V8.5 on Microsoft Windows *\noperating systems *\n\nPROBLEM DESCRIPTION: Profile creation in Business Process *\nManagement (BPM) fails with an *\nOutOfMemoryError *\n\nRECOMMENDATION: *\n\nProfile creation would fail with errors similar to:\n JVMDUMP039I Processing dump event \"systhrow\", detail\n \"java/lang/OutOfMemoryError\" at 2012/04/25 04:44:47 - please\n wait.\n JVMDUMP032I JVM requested System dump using\n 'C:\\BPM\\v8.0\\bin\\core.20120425.044447.2064.0001.dmp' in\n response to an event\n JVMDUMP010I System dump written to\n C:\\BPM\\v8.0\\bin\\core.20120425.044447.2064.0001.dmp\n JVMDUMP032I JVM requested Heap dump using\n 'C:\\BPM\\v8.0\\bin\\heapdump.20120425.044447.2064.0002.phd' in\n response to an event\n JVMDUMP010I Heap dump written to\n C:\\BPM\\v8.0\\bin\\heapdump.20120425.044447.2064.0002.phd\n JVMDUMP032I JVM requested Java dump using\n 'C:\\BPM\\v8.0\\bin\\javacore.20120425.044447.2064.0004.txt' in\n response to an event\n JVMDUMP010I Java dump written to\n C:\\BPM\\v8.0\\bin\\javacore.20120425.044447.2064.0004.txt\n JVMDUMP032I JVM requested Snap dump using\n 'C:\\BPM\\v8.0\\bin\\Snap.20120425.044447.2064.0006.trc' in\n response to an event\n JVMDUMP010I Snap dump written to\n C:\\BPM\\v8.0\\bin\\Snap.20120425.044447.2064.0006.trc\n JVMDUMP013I Processed dump event \"systhrow\", detail\n \"java/lang/OutOfMemoryError\".\n INSTCONFFAILED: The profile could not be created. For more\n information, consult\n the C:\\BPM\\v8.0\\logs\\manageprofiles\\ProcCtr02_create.log file.\n The error statements might be in different order and some\n statements might be repeated multiple times.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q150", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The OutOfMemoryError was resolved by increasing the maximum\n java heap size by changing -Xmx value to -Xmx512M.\n\nThe fix for this APAR is currently targeted for inclusion in\n fix packs 8.0.0.4 and 8.5.0.1.\n Please refer to the Recommended Updates page for delivery\n information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX\nIn WAS_HOME/bin/manageprofiles.bat increase the maximum java\n heap size by changing -Xmx value to -Xmx512M.\n Note: WAS_HOME refers to the installation directory of\n WebSphere Application Server.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q150", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM63963\nREPORTED COMPONENT NAME\n WEBS APP SERV N\nREPORTED COMPONENT ID\n 5724H8800\nREPORTED RELEASE\n 800\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2012-05-04\nCLOSED DATE\n 2012-07-24\nLAST MODIFIED DATE\n 2012-07-24\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q150", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBS APP SERV N\nFIXED COMPONENT ID\n 5724H8800", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q150", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R800 PSY\n UP\nR850 PSY\n UP", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q150", "section_id": 0, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Note: Before collecting the troubleshooting data, take a look at the knowledge collection [http://www.ibm.com/support/docview.wss?uid=swg27037045], which lists the known performance problems in the IBM Business Process Manager product. If that page does not help, provide the following MustGather data:\n\nGENERAL TUNING VERSUS SPECIFIC ISSUES\n\nIBM technical support is only for specific product issues and questions. If you need assistance with general tuning, environment health checks or application tuning then you may want to look into engaging IBM Services. We also have this Performance tuning Redbooks which provides guidance on the many aspects of BPM performance tuning.\n\"IBM Business Process Manager V8.5 Performance Tuning and Best Practices\" [http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/SG248216.html]\n\nIf you have a specific product issue or question related to product behavior then we can assist with that via technical support. We will need a detailed use case for the issue, the delay times you are seeing or your question and why you consider this a product performance issue.\n\nOVERVIEW OF PERFORMANCE DIAGNOSTIC INFORMATION\nGather the following information and files. See the steps below for more detailed information:\nDetailed problem description including use case, questions, and concerns.\nDetailed environment description and topology\nProfile /logs directory\nProfile /config directory\nverbose gc logging\nJava\u2122cores during the delay timeframe\nFeedback on whether any OS or Database resource is being exhausted.\n(As needed) PI or TWX export of the application involved in the delay.\n(As needed) Tracing specific to the product area of the problem\n(As needed) Logging of the http traffic involved in the issue\n\nDETAILED PERFORMANCE DIAGNOSTIC INFORMATION\nThe following information provide detailed steps to gather each type of information that may be required for performance issues. When capturing a set of data ensure that it is complete and covers the timeframe of the occurrence that you point out.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q150", "section_id": 0, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "1: Detailed problem description.\n*\n* What product use case or application path has performance issues?\n For example login to process portal, starting a task, startup of BPM server What delay times in seconds are you seeing? Why do you consider this a product performance issue? Was there at time the same scenario did not have a performance concern?\n* Does this always occur for a particular action?\n If not, how often does it occur? Is it specific to a particular application or piece of an application? Was there any change before the issue started to occur?\n For example a configuration change, new application deployed, or load increased. Is there anything you have found which helps work around the issue? If the related action is not known, how often does the issue occur?\n Do you notice any similarities like high user load, particular time of day, or other common factors? How does this impact your business?\n\n2: Detailed environment description and topology *\n* versionInfo -maintenancePackages\n*\nDescription the topology of the environment including clusters and nodes used. Provide details about the database and other third party products involved in the behavior. Are there multiple networks involved in the communications?\n If so, do they span large distances (BPM and database server not collocated) ? If browser related, do you see the same behavior in Internet Explorer, Firefox, and Chrome?\n\n3: Profile /logs directory *\n*\n*\n\n4: Profile /config directory *\n*\nCellName\n*\n5: Enable verbose GC *\n*\n\"Enabling VerboseGC\"\n* Process Designer Mustgather\n*\n6: Generate javacores during the issue. *\n*\ngenerating javacores for Windows\n*\n7: Review the system resources *\nSee this reference document for running BPM in a virtual environment.\n*", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q150", "section_id": 0, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "8: PI or TWX export of the application *\n*\nProject Interchange(PI) export\n*\n* TWX export\n*\n9: Tracing specific to the product area of the problem *\nvarious product MustGathers\n*\n*\n10: Logging of the HTTP traffic. *\ncaptured via browser plugins\nThis covers general information useful for most performance issues. Although each issue could require additional information specific to an area or problem. Component specific mustgathers [http://www-01.ibm.com/support/docview.wss?uid=swg21569731] can be reviewed for more details on data to collect for a particular area. Performance issue may also require multiple collections of data as the issue is narrowed down.\nWHAT TO DO NEXT\n 1. Review the logs and traces at the time of the problem to try to determine the source of the problem.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q150", "section_id": 0, "heading": "RELATED INFORMATION", "parent": null, "text": "BPM - Performance Tuning and Best Practices [http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/SG248216.html]\nHow to resolve memory issues in BPM? [http://www.ibm.com/support/docview.wss?uid=swg21499538]\nConfigure Java logging (WebSphere Application Server) [http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/ttrb_configjavalog.html]\nSearch: WebSphere Application Server - Perf MustGather [http://www.ibm.com/support/search.wss?tc=SSCMPB9+SSCMP9J&q=MustGatherDocument]\nSearch: WebSphere Application Server OOM MustGather [http://www.ibm.com/support/search.wss?tc=SSCMPCY&q=MustGatherDocument]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Lombardi Edition General Linux, Windows 7.2, 7.1 Business Integration IBM Business Process Manager Express Performance Linux, Windows 8.5, 8.0.1, 8.0, 7.5.1, 7.5 Business Integration IBM Business Process Manager Standard Performance AIX, Linux, Solaris, Windows 8.5, 8.0.1, 8.0, 7.5.1, 7.5 Business Integration IBM BPM Advanced Pattern on Red Hat Enterprise Linux Server Performance Linux Red Hat - xSeries 8.0.1, 8.0 Business Integration IBM Business Process Manager Advanced Pattern on AIX Performance AIX 8.0.1\nPRODUCT ALIAS/SYNONYM\n BPM\n\n DIRECT LINKS TO FIXES\nbpm.8560.cf1.delta.repository.2 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8560.cf1.delta.repository.2&source=SAR]\nbpm.8560.cf1.delta.repository.1 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8560.cf1.delta.repository.1&source=SAR]\n8.5.6.0-WS-BPM-IFJR52537 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.5.6.0-WS-BPM-IFJR52537&source=SAR]\n8.5.5.0-WS-BPM-IFJR52537 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.5.5.0-WS-BPM-IFJR52537&source=SAR]\nVersion 8.5 Refresh Pack 7 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24041575]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q150", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When you place your inbound web service inside a toolkit and\n one parameter is defined as a complex type list, the inbound\n web service generated WSDL contains an array type definition\n in a non-existent namespace and the runtime-generated SOAP\n message does not accomplish the WSDL definition. As a result,\n the web service client reports an error when loading the wrong\n WSDL or parsing the SOAP response message.\n\n This can lead to the following hung threads\n [4/14/16 8:01:33:763 CEST] 000000a5 ThreadMonitor W WSVR0605W:\n Thread\n \"WebContainer : 0\" (000001b2) has been active for 726141\n milliseconds and may be hung. There is/are 1 thread(s) in\n total in the server that may be hung.\n at\n java.util.HashMap.findNonNullKeyEntry(HashMap.java:605)\n\n \"WebContainer : 37\" J9VMThread:0x0000000049652700,\n j9thread_t:0x000001004F719B40,\n java/lang/Thread:0x000000071FA2E298,\n state:R, prio=5\n (java/lang/Thread getId:0x24E2, isDaemon:true)\n (native thread ID:0x43D001D, native priority:0x5, native\n policy:UNKNOWN, vmstate:CW, vm thread flags:0x00000001)\n CPU usage total: 21.683002000 secs, user: 21.648816000 secs,\n system:\n 0.034186000 secs\n Heap bytes allocated since last GC cycle=0 (0x0)\n Java callstack:\n at java/util/HashMap.findNonNullKeyEntry(HashMap.java:605\n (Compiled Code))\n at java/util/HashMap.getEntry(HashMap.java:589(Compiled Code))\n at java/util/HashMap.get(HashMap.java:575(Compiled Code))\n at com/lombardisoftware/core/xml/XMLTypeDescriptor.\n getFieldDescriptorByElementQName(XMLTypeDescriptor.java:495\n (Compiled Code))\n at com/lombardisoftware/core/xml/AbstractXMLSerializer.\n deserializeComplexType(AbstractXMLSerializer.java:1871(Compiled\n Code))\n at com/lombardisoftware/core/xml/AbstractXMLSerializer.\n deserializeObject(AbstractXMLSerializer.java:1335(Compiled\n Code))\n at com/lombardisoftware/core/xml/AbstractXMLSerializer.\n deserialize(AbstractXMLSerializer.java:1089)\n at com/lombardisoftware/sca/databinding/AxiomToTWObject.\n fromOMElement(AxiomToTWObject.java:111)", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q150", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "No local fix", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q150", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: IBM Business Process Manager (BPM) *\nAdvanced *\nIBM BPM Express *\nIBM BPM Standard *\n\nPROBLEM DESCRIPTION: When you place your inbound web *\nservice inside a toolkit and one *\nparameter is defined as a complex *\ntype list, the inbound web service *\ngenerated WSDL contains an array type *\ndefinition in a non-existent *\nnamespace and the runtime-generated *\nSOAP message does not accomplish the *\nWSDL definition. As a result, the web *\nservice client reports an error when *\nloading the wrong WSDL or parsing the *\nSOAP response message. *\n\nRECOMMENDATION: *\n\nWhen you put the inbound web service inside a toolkit, the\n WSDL might use the namespace of the toolkit instead of the\n process application namespace. As a result, the array list\n items are created with the wrong namespace and wrong WSDL and\n a wrong SOAP message are generated.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q150", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A fix is available for IBM BPM V8.5.5.0 that ensures the\n correct namespace is used no matter where the web service is\n placed.\n\nOn Fix Central (http://www.ibm.com/support/fixcentral), search\n for JR52537:\n\n1.Select IBM Business Process Manager with your edition from\n the product selector, the installed version to the fix pack\n level, and your platform, and then click Continue.\n 2.Select APAR or SPR, enter JR52537, and click Continue.\n\nWhen you download fix packages, ensure that you also download\n the readme file for each fix. Review each readme file for\n additional installation instructions and information about the\n fix.\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q150", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR52537\nREPORTED COMPONENT NAME\n BPM ADVANCED\nREPORTED COMPONENT ID\n 5725C9400\nREPORTED RELEASE\n 855\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2015-02-12\nCLOSED DATE\n 2015-04-07\nLAST MODIFIED DATE\n 2016-12-30\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q150", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM ADVANCED\nFIXED COMPONENT ID\n 5725C9400", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q150", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R800 PSY\n UP\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\nDIRECT LINKS TO FIXES\n8.6.0.201712-WS-BPM-IFJR59388 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager&fixids=8.6.0.201712-WS-BPM-IFJR59388&source=SAR]\n8.6.0.0-WS-BPM-IFJR59388 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager&fixids=8.6.0.0-WS-BPM-IFJR59388&source=SAR]", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q150", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "According to the Microsoft SQLServer database statement,\n sqljdbc42.jar supports Java 8 and later versions. Therefore,\n support for IBM Business Process Manager (BPM) is needed so you\n can use sqljdbc42.jar with Java 8 to connect to the Microsoft\n SQL Server database.", "logical_doc_id": 5, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q150", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "LOCAL FIX:\u00d8\n N/A", "logical_doc_id": 5, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q150", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "No additional information is available.", "logical_doc_id": 5, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q150", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A fix is available that enables IBM BPM to support to use\n sqljdbc42.jar with Java 8 so you can connect to a Microsoft SQL\n Server database. This problem is already fixed in IBM BPM V8.6\n CF2017.09 and later versions.\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q150", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR59388\nREPORTED COMPONENT NAME\n BPM\nREPORTED COMPONENT ID\n 5737A5700\nREPORTED RELEASE\n 860\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2018-04-10\nCLOSED DATE\n 2018-04-20\nLAST MODIFIED DATE\n 2018-04-20\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q150", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM\nFIXED COMPONENT ID\n 5737A5700", "logical_doc_id": 5, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q150", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "DIRECT LINKS TO FIXES\n8.5.6.2-WS-BPMPCPD-IFJR55110 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.5.6.2-WS-BPMPCPD-IFJR55110&source=SAR]\n8.5.5.0-WS-BPMPCPD-IFJR55110 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.5.5.0-WS-BPMPCPD-IFJR55110&source=SAR]\n8.5.0.2-WS-BPMPCPD-IFJR55110 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.5.0.2-WS-BPMPCPD-IFJR55110&source=SAR]\n8.0.1.3-WS-BPMPC-IFJR55110 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=8.0.1.3-WS-BPMPC-IFJR55110&source=SAR]\n7.5.1.2-WS-BPMPC-IFJR55110 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=7.5.1.2-WS-BPMPC-IFJR55110&source=SAR]\nWLE-7.2.0.5-HotFix-JR55110 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FWebSphere+Lombardi+Edition&fixids=WLE-7.2.0.5-HotFix-JR55110&source=SAR]\nVersion 8.5 Refresh Pack 7 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24041575]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 5, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q150", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "There are multiple vulnerabilities in IBM SDK Java Technology\n Edition, which IBM WebSphere Application Server uses in IBM\n Business Process Manager (BPM) and IBM WebSphere Lombardi\n Edition. These issues were disclosed as part of the \"Multiple\n vulnerabilities in current releases of the IBM SDK, Java\n Technology Edition\" in January 2016. For more information, see\n \"Security Bulletin: Security vulnerabilities have been\n identified in IBM WebSphere Application Server shipped with IBM\n Business Process Manager and WebSphere Lombardi Edition\n (CVE-2016-0483, CVE-2016-0475, CVE-2016-0466, CVE-2015-7575,\n CVE-2016-0448)\"\n (http://www.ibm.com/support/docview.wss?uid=swg21977021).\n\nPRODUCTS AFFECTED\n IBM BPM Advanced\n IBM BPM Standard\n IBM BPM Express\n WebSphere Lombardi Editon", "logical_doc_id": 6, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q150", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "No additional information is available.", "logical_doc_id": 6, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q150", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "A fix is available for the latest fix pack of all supported\n releases of IBM BPM and WebSphere Lombardi Edition.\n\nOn Fix Central (http://www.ibm.com/support/fixcentral), search\n for JR55110:\n\n1. Select IBM Business Process Manager with your edition or\n IBM WebSphere Lombardi Edition from the product selector, the\n installed version to the fix pack level, and your platform, and\n then click Continue.\n 2. Select APAR or SPR, enter JR55110, and click Continue.\n\nWhen you download fix packages, ensure that you also download\n the readme file for each fix. Review each readme file for\n additional installation instructions and information about the\n fix.\n\nTEMPORARY FIX", "logical_doc_id": 6, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q150", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR55110\nREPORTED COMPONENT NAME\n BPM ADVANCED\nREPORTED COMPONENT ID\n 5725C9400\nREPORTED RELEASE\n 751\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-01-27\nCLOSED DATE\n 2016-02-23\nLAST MODIFIED DATE\n 2016-02-23\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 6, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q150", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM ADVANCED\nFIXED COMPONENT ID\n 5725C9400", "logical_doc_id": 6, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q150", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R751 PSY\n UP\nR801 PSY\n UP\nR850 PSY\n UP\nR855 PSY\n UP\nR856 PSY\n UP\nR857 PSY\n UP", "logical_doc_id": 6, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q136", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q136", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Enterprise console is affected by the following vulnerability:\n OWASP category: OTG-INPVAL-001 - Testing for Reflected Cross\n Site Scripting\n\nhttps://www.owasp.org/index.php/Testing_for_Reflected_Cross_site [https://www.owasp.org/index.php/Testing_for_Reflected_Cross_site]\n _scripting_(OTG-INPVAL-001)\n\nSome parameters in some forms are vulnerable to XSS exploit.\n\nVulnerable forms and parameters:\n TAB Explore - Check Action Rule - Edit\n TAB Compose - Action Rule - OK\n TAB Analyze - Generate Project Report - Generate Report\n TAB Query - Generate Report on Query Results", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q136", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "There was a vulnerability in the enterprise console.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q136", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The code was fixed.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q136", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n RS03052\nREPORTED COMPONENT NAME\n WS DECISION CTR\nREPORTED COMPONENT ID\n 5725B6900\nREPORTED RELEASE\n 881\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2018-03-06\nCLOSED DATE\n 2018-03-07\nLAST MODIFIED DATE\n 2018-03-07\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\n999", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q136", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WS DECISION CTR\nFIXED COMPONENT ID\n 5725B6900", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q136", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q136", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Resource rates are visible and editable in the staffing view: My\n Resources\n\nThe Reg Cost/hr and Special Cost/hr fields are visible and\n editable in the My Resources tab of the staffing view by Project\n Managers without the appropriate security rights.\n See attached customer screenshot: cost_rates.jpg\n\nFound by customer on 7112ifix7\n Reproduced by TSE on 7112ifix11\n\nSteps to reproduce:\n 1) Create a resource pm01 with Portfolio Manager security role\n 2) Set in Application Administration ? Security that the\n Portfolio Manager role has Resource Record ? Records of Other\n Resources ? Rates ? View and Edit both unchecked\n 3) Login as pm01\n 4) Create a proposal\n 5) Go to the staffing view and search for a resource having\n rates\n 6) Add the resource to My Resources\n 7) Despite the security settings, rates are visible both on My\n Resources. They can also be edited, but the modifications seems\n not to be saved in the resource record.\n 8) Note that opening the resource record, rates are correctly\n not visible as expected\n 9) Also the WBS security setting for Project Group/Project\n Manager ? Staff Acquisition ? Cost/Rates ? Resource /Profile\n Rates ? View and Edit doesn't affect the visibility of the Rates\n in My Resources", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q136", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Problem is with missing security validation in My Resources tab\n in Staffing view", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q136", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Solution is to add Security validation that already exist in the\n other tabs in the top grid of the Rational Portfolio Manager GUI\n Search and assigned area, in order to keep consistency.\n\nImportant comments:\n 1. Rates in top grid in My Resources tab are not supposed to be\n editable. This grid is read only, like the rest of the top grids\n in other tabs in staffing view.\n 2. Security mentioned in the description of the defect is\n Resource security and does not control Rate and Cost fields in\n the staffing view. These fields are controlled by Assignment\n security that can be found under Staff Acquisition -> Cost/Rates\n node in WBS security tab in Application Administration.\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q136", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM23394\nREPORTED COMPONENT NAME\n RATL PORT MGR W\nREPORTED COMPONENT ID\n 5724J4001\nREPORTED RELEASE\n 710\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2010-09-28\nCLOSED DATE\n 2011-01-06\nLAST MODIFIED DATE\n 2011-01-06\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q136", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n RATL PORT MGR W\nFIXED COMPONENT ID\n 5724J4001", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q136", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R711 PSY\n UP", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q136", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "1380403; RATLC01476000; PK79137; CQ; ClearQuest; alm; Copy Project; ALM_CopyProject; Related Projects; ERROR!; The entity's Named Hook \"ALM_CopyProject\" failed; This operation is permitted only when the entity is in an editable state; that is; when an AdActionDef of the appropriate type is being applied; ALMSecurityPolicy; Everyone TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q136", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "This problem occurs with an ALM schema. When using the Copy Project button on the Related Projects tab, you get this error:\n\nERROR! The entity's Named Hook \"ALM_CopyProject\" failed, the error message is 'This operation is permitted only when the entity is in an editable state (that is, when an AdActionDef of the appropriate type is being applied) at C:/Program Files/Rational/ClearQuest/Common/lib/perl5/site_perl/5.8.6/CQPerlExt.pm'", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q136", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "An ALMSecurityPolicy record named \"Everyone\" does not exist.", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q136", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Creating a Security Policy record named \"Everyone\" will resolve this problem.\n\nHere is an excerpt from the Copying an existing project topic [https://publib.boulder.ibm.com/infocenter/cqhelp/v7r1m0/index.jsp?topic=/com.ibm.rational.clearquest.alm.doc/topics/cloning.htm] of the ClearQuest Information Center [http://ibm.com/support/docview.wss?rs=988&uid=swg27010159]:\n\nIf a new category is specified for the new cloned project, all ALMRole record SecurityPolicies are set to the Everyone SecurityPolicy. You may need to update the value for each ALMRole record SecurityPolicy on the cloned records as required by your policy.\n\nIt should state that you need to create an ALMSecurityPolicy record named \"Everyone\" prior to running Copy Project. This is a documentation defect that will be addressed in a future update of the ClearQuest Information Center.", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q136", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How to estimate the database capacity that should be allocated to the JRules modules Rule Team Server (RTS), Rule Execution Server (RES) and the Decision Validation Service (DVS) Decision Warehouse (DW) ?", "logical_doc_id": 5, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q136", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "The attached utility allows to bootstrap a capacity planning effort for the database schemas that are used by the JRules modules ( RTS, RES and DW ). This utility takes as input a set of metrics used to automate the creation of an RTS project, the creation of baselines in RTS, the publication of ruleapps to RES, the creation of scenario suites in RTS and the DVS execution of the scenario suites along with capture of DW traces.\n\nExamples of the metrics that can be used to control the size of the generated project are:\nnumber of data classes and number of attributes per class : allows to control the overall size of the Business Object Model (BOM)\nnumber of data class instances received as input and output of the rule project : allows to control the amount of data received as input and returned as output by the ruleset, which has an impact on DW\nnumber of top level rule packages in the rule project : each top level package is populated with a action rules and decision table, a ruleflow is created that executes each top level package in sequence with one rule task per top level package\nnumber of action rules and decision tables per top level rule package\nnumber of conditions and actions for in the action rules\nnumber of condition and action columns along with size of each partition in decision tables\nnumber of baselines to create : with the creation of each baseline a configurable percentage of the rules are modified to simulate rule maintenance activities over time, a ruleapp is published to RES for each baseline\nnumber of scenario suites and number of scenario per suite", "logical_doc_id": 5, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q136", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Instructions for JRules 7.0.x and 7.1.x:\n 1. Extract the jrules-dbsizing.zip zip file to a development machine where the JRules 7.0.x modules are installed\n 2. Edit the file jrules-dbsizing/build.xml to point the variable jrules.home to the base directory of your JRules product installation, for example C:/Program Files/IBM/WebsphereILOGJRules703\n 3. Edit the file jrules-dbsizing/configuration.properties to configure: 1. URL and login/password to connect to JRules Teamserver\n 2. Name of the RES server configuration to use for RuleApp deployments and DVS scenario suite executions ( a matching name configuration should exist in RTS > Configure > Deployment > Manage Servers , note that depending on JRules version the default may be Sample or %Sample so it is recommended to recreate a new Server configuration in RTS if an error occurs in the utility such as \"RES server configuration not found: Sample\" )\n 3. Adjust the metrics according to the expected complexity of the planned JRules project\n\n4. From a command line in the directory jrules-dbsizing execute: ant\n 5. Once the execution completes, the following side effects are expected: 1. A newly created project is present in RTS with baselines and scenario suites\n 2. For each baseline created, a RuleApp is deployed and available in RES\n 3. For each scenario suite created the Decision Warehouse contains traces for an execution", "logical_doc_id": 5, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q136", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "6. Request from the database administrator to provide metrics on the database usage that results from running the tool ( the tool does not directly provide nor compute such usage information)\njrules-dbsizing.zip [/support/docview.wss?uid=swg21430461&aid=2] [/support/docview.wss?uid=swg21430461&aid=1]\nInstructions for ODM 7.5 and 8.x:\n 1. Extract the odm-dbsizing.zip file to a development machine where the ODM product is installed\n 2. Edit the file odm-dbsizing/build.xml to point the variable odm.home to the base directory of your ODM product installation, for example C:/IBM/ODM85/ODM\n 3. Edit the file odm-dbsizing/configuration.properties to configure: 1. URL and login/password to connect to ODM Decision Center\n 2. Name of the RES server configuration to use for RuleApp deployments and DVS scenario suite executions ( a matching name configuration should exist in Decision Center Enterprise > Configure > Deployment > Manage Servers , note that depending on ODM version the default may be Sample or %Sample so it is recommended to recreate a new Server configuration in Decision Center Enterprise if an error occurs in the utility such as \"RES server configuration not found: Sample\" )\n 3. Adjust the metrics according to the expected complexity of the planned ODM project\n\n4. From a command line in the directory odm-dbsizing execute: ant run\n 5. Once the execution completes, the following side effects are expected: 1. A newly created project is present in Decision Center Enterprise with baselines and scenario suites\n 2. For each baseline created, a RuleApp is deployed and available in RES\n 3. For each scenario suite created the Decision Warehouse contains traces for an execution\n\n6. Request from the database administrator to provide metrics on the database usage that results from running the tool ( the tool does not directly provide nor compute such usage information)\n* odm-dbsizing.zip [/support/docview.wss?uid=swg21430461&aid=4]odm-dbsizing.zip [/support/docview.wss?uid=swg21430461&aid=3]\nNote: because of the side effects listed above this tool should not be used on a production environment.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Platform Independent 8.6, 8.5, 8.0.1, 8.0, 7.5 Enterprise", "logical_doc_id": 5, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q136", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "I have created a new DVS format, using the DVS editor in Rule Designer.\n(For instance, to set a higher precision to be used when running my DVS tests).\nHow can I use this new format when running DVS tests and simulations, in both Rule Designer and Decision Center?", "logical_doc_id": 6, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q136", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "In Rule Designer, you cannot use this custom format for DVS testing and simulations, since you cannot set a specific DVS Project (with the custom format) when executing. This means that you will always rely on the default format. However, your custom format can be published to Decision Center, and can be used there for DVS testing and simulations.", "logical_doc_id": 6, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q136", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Methodology to publish and use your own DVS format to Decision Center:\n\n1) Create your new DVS Project in Rule Designer.\n2) In this DVS Project Editor, select Repackage Ear, and repackage the ear file for the application server that you are using. For instance, if you are on WAS8, the ear files are jrules-teamserver-WAS8.ear and jrules-SSP-WAS8.ear.\nThe 2 ear files should be re-generated.\n3) Re-publish your ear files to your application server. For instance, if you are using WebSphere Application Server 8.0, open the WAS Business Console, and go to Application -> Application Type -> WebSphere Enterprise Application.\nThere you will see the existing deployed ear files, including the ones above.\nSelect them and click on update, and select the new generated ear files to republish the repackaged ear files with your own DVS format.\n4) Connect to Decision Center, and click Project Option in the Project tab.\nThere, you will see that your format is available but not checked.\nCheck it.\n5) Create a new Test Suite.\nIn \"Step\n\n3. Scenario\", among the different choices of format, your custom format will be available.", "logical_doc_id": 6, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q136", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#DVS Format [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0m1/index.jsp?topic=%2Fcom.ibm.wodm.dserver.rules.designer.test%2Ftopics%2Fcon_dvsformats.html]\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Decision Center Usability Platform Independent 8.5, 8.0.1, 8.0.0.1, 8.0, 7.5 Edition Independent", "logical_doc_id": 6, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q162", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere Application Server is shipped as a component of IBM Tivoli Netcool Configuration Manager. Information about a security vulnerability affecting IBM WebSphere Application Server has been published in a security bulletin.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q162", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Please consult the security bulletin Vulnerability in Apache Commons affects IBM WebSphere Application Server (CVE-2015-7450) [http://www-01.ibm.com/support/docview.wss?uid=swg21970575] for vulnerability details and information about fixes.\nCVEID: CVE-2015-7450 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7450]\nDESCRIPTION: Apache Commons Collections could allow a remote attacker to execute arbitrary code on the system, caused by the deserialization of data with Java InvokerTransformer class. By sending specially crafted data, an attacker could exploit this vulnerability to execute arbitrary Java code on the system.\nCVSS Base Score: 9.8\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/107918 [https://exchange.xforce.ibmcloud.com/vulnerabilities/107918] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q162", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Principal Product and Version(s) Affected Supporting Product and Version ITNCM version 6.4.1.3\nITNCM version 6.3.0.6 Embedded IBM WebSphere Application Server eWAS 7.0 REMEDIATION/FIXES\n\n install_dir/B19/aix_a/code/command/catstart -run CNEXT\n The following messages appear as CATIA starts:\n Starting CATIA V5 program. Please wait...\n Cannot open library libCATDrafting2DLProvider.a\n Cannot open library libCATRmaView.a\n Cannot open library libCATPenConfiguration.a\n Cannot open library libCATRdgWorkbench.a\n .\n While attempting a new part, the following message is added:\n Cannot open library libCATMechanicalModelerUI.a\n .\n When I attempt to create a new drawing, the following message\n is added:\n Cannot open library libCATDuiWkbDrw.a\n .\n No error files are created. All error messages appear on the\n screen,\n not in a log file. No Abendtrace is created.\n .\n Check Prerequisites runs OK.Integrity Check Level 1, Level 2\n and Level 3 all run OK.\n .\n Default CATSettings were used.\n This same system also has ENOVIA V6R2010 Server code\n installed, which runs successfully.\n .\n Possible defect area:\n When compared lslpp ?L output of L2 machine with users\n machine, it was found that following file sets were missing\n at users end.\n xlsmp.aix53.rte SMP Runtime Libraries for\n AIX 5.3\n xlsmp.rte SMP Runtime Library\n\n xlsmp.msg.en_US.rte SMP Runtime Messages - U.S. English\n\n .\n User explained that he installed what is mentioned in R19\n Pdir (and 3ds.com site) but not got above file sets installed\n on his machine.\n .\n Expected results:\n 1. According to V5R19 PDir, followings are the Prerequisites\n for CATIA:\n .\n AIX 6.1 Technology Level 02 GA with following components:\n XL C/C++ V10.1.0.0 Run-time Environment (part of AIX 6.1\n TL02)\n XL Fortran V12.1.0.0 Run-Time Environment (part of AIX 6.1\n TL02)\n Java 1.5.0 32 bit Service Refresh 7\n JAVA 1.5.0 IBM AIX build pap32dev-20080315 (SR7)\n Fileset: Java5.sdk 5.0.0.175\n .\n Is above prerequisites list is sufficient to get above xlsmp\n file sets ? If not:\n 2. Which other application user needs to install.\n .", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q096", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Scenario :\n Background:\n Environment:\n AIX 6.1 TL2\n C++ runtime 10.1.0.0\n Fortran runtime 12.1.0.0\n Scenario:\n 1. Unable to create parts or drawings in CATIA V5R19 SP4\n (32-bit) on AIX 6.1 (64-bit kernel). CATIA seems to start OK\nthe GUI appears, the Product Structure workbench is loaded,\n 2. Initial Product1.CATProduct appears. If user then attempts\n to create a new Part or Drawing, a \"Licensing problem\"\n message window appears with the message \"No license available\n for this application\". I am running with an AL3 license.\n If CATIA started from command line:\n > install_dir/B19/aix_a/code/command/catstart -run CNEXT\n The following messages appear as CATIA starts:\n Starting CATIA V5 program. Please wait...\n Cannot open library libCATDrafting2DLProvider.a\n Cannot open library libCATRmaView.a\n Cannot open library libCATPenConfiguration.a\n Cannot open library libCATRdgWorkbench.a\n .\n While attempting a new part, the following message is added:\n Cannot open library libCATMechanicalModelerUI.a\n .\n When I attempt to create a new drawing, the following message\n is added:\n Cannot open library libCATDuiWkbDrw.a\n .\n No error files are created. All error messages appear on the\n screen,\n not in a log file. No Abendtrace is created.\n .\n Check Prerequisites runs OK.Integrity Check Level 1, Level 2\n and Level 3 all run OK.\n .\n Default CATSettings were used.\n This same system also has ENOVIA V6R2010 Server code\n installed, which runs successfully.\n .\n Possible defect area:\n When compared lslpp ???L output of L2 machine with users\n machine, it was found that following file sets were missing\n at users end.\n xlsmp.aix53.rte SMP Runtime Libraries for\n AIX 5.3\n xlsmp.rte SMP Runtime Library\n\n xlsmp.msg.en_US.rte SMP Runtime Messages - U.S. English\n\n .\n User explained that he installed what is mentioned in R19\n Pdir (and 3ds.com site) but not got above file sets installed\n on his machine.\n .\n Expected results:\n 1. According to V5R19 PDir, followings are the Prerequisites\n for CATIA:\n .\n AIX 6.1 Technology Level 02 GA with following components:\n XL C/C++ V10.1.0.0 Run-time Environment (part of AIX 6.1\n TL02)\n XL Fortran V12.1.0.0 Run-Time Environment (part of AIX 6.1\n TL02)\n Java 1.5.0 32 bit Service Refresh 7\n JAVA 1.5.0 IBM AIX build pap32dev-20080315 (SR7)\n Fileset: Java5.sdk 5.0.0.175\n .\n Is above prerequisites list is sufficient to get above xlsmp\n file sets ? If not:\n 2. Which other application user needs to install.\n .", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q096", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "THIS MODIFICATION WILL BE INCLUDED IN V5R20SP02 Program\n Directory\n Additional Closure Information:\n Program Directory has been updated with required reference of\n SMP Runtime Library. You can find reference at following\n location.\n .\n V5R20SP02 Program Directory->\n Prerequisites->\n V5 Client Side (V5 Client Hardware & Software Requirements)->\n Check the ???IBM AIX??? section. You will find sentence ???SMP\n Runtime Library as delivered on AIX CDs??? added to it.\n .\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q096", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n HD92934\nREPORTED COMPONENT NAME\n CATIA V5 AIX\nREPORTED COMPONENT ID\n 569101000\nREPORTED RELEASE\n 519\nSTATUS\n CLOSED DOC\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2010-01-25\nCLOSED DATE\n 2010-06-04\nLAST MODIFIED DATE\n 2010-06-04\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q096", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "WebSphere MQ V6.0 Fix Pack 6.0.2.12 [http://www-01.ibm.com/support/docview.wss?uid=swg24033317]\nWebSphere MQ V6.0 for iSeries Fix Pack 6.0.2.12 [http://www-01.ibm.com/support/docview.wss?uid=swg24033319]\nWebSphere MQ V7.5 Fix Pack 7.5.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24034616]\nWebSphere MQ V7.0 Fix Pack 7.0.1.10 [http://www-01.ibm.com/support/docview.wss?uid=swg24034145]\nWebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.10 [http://www-01.ibm.com/support/docview.wss?uid=swg24034909]\nFix Pack 7.1.0.3 for WebSphere MQ V7.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24035405]\nWebSphere MQ 6.0 for HP OpenVMS Alpha and Itanium - Fix Pack 6.0.2.12 [http://www-01.ibm.com/support/docview.wss?uid=swg24035627]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q096", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "If a queue manager ends other than in the normal way via endmqm\n (e.g. due to a sudden machine reboot), then recovery actions by\n the queue manager on restart may result in a damaged queue.\n\nThe queue is at risk of becoming damaged in that circumstance,\n if it is used with a mixture of persistent and non-persistent\n messages. This problem may be more prevalent for transmit\n queues, which can often hold both persistent and non-persistent\n messages.\n\nIt is also possible that the problem could manifest as the\n reappearance of previously got persistent messages on the\n queue, rather than the queue being reported as damaged.\n\nThere is only a very small possibility of encountering this\n problem, due to a number of factors needing to co-exist for it\n to occur.\n\nThe typical damaged queue resulting from this problem will be\n of size 1712 bytes, or more likely, 10240 bytes. Examination of\n the q file (by IBM Service) would reveal a non-null head of\n message chain, but no message.", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q096", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n You may encounter this issue if you do not always end the queue\n manager gracefully, via endmqm. In addition, to encounter the\n problem you must also be using some queues with a mixture of\n persistent and non-persistent messages.\n\nPlatforms affected:\n All Distributed (iSeries, all Unix and Windows)\n\nPROBLEM SUMMARY:\n This problem requires the following sequence of operations to\n occur (some are user driven, and some are driven by the queue\n manager itself):\n\nPut some persistent messages to a queue.\n\nFlush the persistent messages to disk, other than by a\n checkpoint. That can happen when setting queue attributes.\n\nGet all of the persistent messages.\n\nInitiate a checkpoint.\n\nAfter initiating the checkpoint, but before the queue itself is\n checkpointed, put a non-persistent message.\n\nThat sets up a possibility that the queue checkpoint will fail\n to flush a null head of message chain, and it may also truncate\n the queue to below the q file message area. It is important to\n flush a null head because all the persistent messages have been\n got and we had previously flushed the persistent messages to\n disk.\n\nIf the queue manager is hard-crashed immediately after the\n checkpoint, then on queue manager restart the queue file may\n contain persistent messages that had previously all been got.\n Or, if the queue checkpoint operation before the queue manager\n crash truncated the queue, then the queue will be reported as\n damaged on attempting to access it.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q096", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The queue checkpoint logic was revised to correctly handle the\n problem situation described.\n\nThe fix is targeted for delivery in the following PTFs:\n\nv6.0\n Platform Fix Pack 6.0.2.12\n------- --------------------\n Windows U200331\n AIX U842074\n HP-UX (PA-RISC) U842208\n HP-UX (Itanium) U842213\n Solaris (SPARC) U842209\n Solaris (x86-64) U842216\n iSeries tbc_p600_0_2_12\n Linux (x86) U842210\n Linux (x86-64) U842215\n Linux (zSeries) U842211\n Linux (Power) U842212\n Linux (s390x) U842214\n\nv7.0\n Platform Fix Pack 7.0.1.10\n------- --------------------\n Windows U200352\n AIX U853055\n HP-UX (PA-RISC) U853082\n HP-UX (Itanium) U853087\n Solaris (SPARC) U853083\n Solaris (x86-64) U853089\n iSeries 7.0.1.10\n Linux (x86) U853084\n Linux (x86-64) U853088\n Linux (zSeries) U853085\n Linux (Power) U853086\n\nv7.1\n Platform Fix Pack 7.1.0.3\n------- --------------------\n Windows 7.1.0.3\n AIX 7.1.0.3\n HP-UX (Itanium) 7.1.0.3\n Solaris (SPARC) 7.1.0.3\n Solaris (x86-64) 7.1.0.3\n iSeries 7.1.0.3\n Linux (x86) 7.1.0.3\n Linux (x86-64) 7.1.0.3\n Linux (zSeries) 7.1.0.3\n Linux (Power) 7.1.0.3\n\nPlatform v7.5\n------- --------------------\n Multiplatforms 7.5.0.1\n\nThe latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\nIf the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q096", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV22043\nREPORTED COMPONENT NAME\n WMQ LIN X86 V6\nREPORTED COMPONENT ID\n 5724H7204\nREPORTED RELEASE\n 602\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2012-06-01\nCLOSED DATE\n 2012-09-19\nLAST MODIFIED DATE\n 2012-09-19\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q096", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ LIN X86 V6\nFIXED COMPONENT ID\n 5724H7204", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q096", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R602 PSY\n UP", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q096", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do I debug a java OutOfMemory problem with my Streams Application and the IBM JVM", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q096", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Streams application runs out of heap memory", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q096", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Collecting the javacore and heapdump\n\nWhen a java primitive operator or Streams java native function runs out of heap memory, messages similar to the one below will print in the pec.pe.<#>.stdouterr file for the failing pe.\n\nJVMDUMP032I JVM requested Java dump using '/opt/ibm/streamsadmin/.streams/var/Streams.sab_DLZ-mydomain-myinstance/6f3aa3e4-aa87-4ffb-9dc6-5658472a6688/currentWorkingDir/37/javacore.20161011.040350.15759.0003.txt' in response to an event\n\nJVMDUMP032I JVM requested Heap dump using '/opt/ibm/streamsadmin/.streams/var/Streams.sab_DLZ-mydomain-myInstance/6f3aa3e4-aa87-4ffb-9dc6-5658472a6688/currentWorkingDir/37/heapdump.20161011.040350.15759.0002.phd' in response to an event\n\nThis message shows the current working directory of the pe where the heapdump and javacore reside. Copy these files out to a persistent location before cancelling the job for analysis as they will be deleted with canceljob.\n\nAs an alternative, you can set the following streams application environment variables prior to the launch of the job to make sure these files go to a persistent location that does not get deleted with canceljob. The location should be a network location that is available to all resources. Set these with streamtool setproperty --application-ev for example.\n\nmkdir -p /some/known/network/location/mydomain/myinstance\n\nstreamtool setproperty -d mydomain -i myinstance --application-ev IBM_JAVACOREDIR=/some/known/network/location/mydomain/myinstance\n\nstreamtool setproperty -d mydomain -i myinstance --application-ev IBM_HEAPDUMPDIR=/some/known/network/location/mydomain/myinstance\n\nstreamtool setproperty -d mydomain -i myinstance --application-ev IBM_COREDIR=/some/known/network/location/mydomain/myinstance\n\nHow to Analyze the javacore and heapdump\n\nFirst look at the \"Thread Details\" section of the javacore to see what call caused the OutOfMemory state. This is not necessarily the problem area, but can be a good indicator.\n\nNext use the IBM Heap Analyzer to identify specific leak suspects and adjust the application accordingly\nhttps://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=4544bafe-c7a2-455f-9d43-eb866ea60091 [https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=4544bafe-c7a2-455f-9d43-eb866ea60091]\n\nIf you determine that there is not a leak but more memory is needed by the application, you can adjust the heap with the -Xmx option by specifying vmArgs in the application or setting IBM_JAVA_OPTIONS in with streamtool setproperty --application-ev.", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q096", "section_id": 3, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "6.2.0.2: WebSphere Integration Developer V6.2.0 Fix Pack 2 for Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24024412]\n6.2.0.2: WebSphere Integration Developer V6.2.0 Fix Pack 2 for Linux [http://www-01.ibm.com/support/docview.wss?uid=swg24024471]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q096", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Customer trying to run headless test in WID6.2.0 and v6.2.0.1\n but running in several error messages, especially during\n wid.deployment.\n \"I am having the same difficulties deploying projects from\n workspaces via script, including the workspace in the recently\n published sample:\n\n http://www.ibm.com/developerworks/websphere/library/techarticles\n /0903_bist/0903_bist.html [http://www.ibm.com/developerworks/websphere/library/techarticles/0903_bist/0903_bist.html]\n\n I tried this build a couple of times after rebooting and got an\n interesting error:\n\n deploy:\n [wid.deploy] Deploying BSM_VendingMachine module.\n [wid.deploy] Starting WebSphere Process Server v6.2 at\n localhost.\n [wid.deploy] java.lang.IncompatibleClassChangeError\n [wid.deploy] at\n com.ibm.wbit.runtime.server.Utilities.getWTEMBeanObject(Unknown\n Source)\n [wid.deploy] at\n com.ibm.wbit.runtime.v61.prepublish.WorkflowPrePublishDelegate.v\n alidate(Unknown Source)\n [wid.deploy] at\n com.ibm.wbit.runtime.v61.WBIServerBehaviour.prePublishValidate(U\n nknown Source)\n [wid.deploy] at\n com.ibm.wbit.runtime.v61.WBIServerBehaviour.publishModules(Unkno\n wn Source)\n [wid.deploy] at\n org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publis\n h(ServerBehaviourDelegate.java:871)\n [wid.deploy] at\n org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publis\n h(ServerBehaviourDelegate.java:707)\n [wid.deploy] at\n com.ibm.wbit.runtime.server.SCAServerBehaviour.publish(Unknown\n Source)\n [wid.deploy] at\n org.eclipse.wst.server.core.internal.Server.publishImpl(Server.j\n ava:2492)\n [wid.deploy] at\n org.eclipse.wst.server.core.internal.Server$PublishJob.run(Serve\n r.java:270)\n [wid.deploy] at\n org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q096", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Customer trying to run headless test in WID6.2.0 and v6.2.0.1\n but running in several error messages, especially during\n wid.deployment.\n \"I am having the same difficulties deploying projects from\n workspaces via script, including the workspace in the recently\n published sample:\n\n http://www.ibm.com/developerworks/websphere/library/techarticles\n /0903_bist/0903_bist.html [http://www.ibm.com/developerworks/websphere/library/techarticles/0903_bist/0903_bist.html]\n\n I tried this build a couple of times after rebooting and got an\n interesting error:\n\n deploy:\n [wid.deploy] Deploying BSM_VendingMachine module.\n [wid.deploy] Starting WebSphere Process Server v6.2 at\n localhost.\n [wid.deploy] java.lang.IncompatibleClassChangeError\n [wid.deploy] at\n com.ibm.wbit.runtime.server.Utilities.getWTEMBeanObject(Unknown\n Source)\n [wid.deploy] at\n com.ibm.wbit.runtime.v61.prepublish.WorkflowPrePublishDelegate.v\n alidate(Unknown Source)\n [wid.deploy] at\n com.ibm.wbit.runtime.v61.WBIServerBehaviour.prePublishValidate(U\n nknown Source)\n\n Eclipse ant creates a different classloader to run the ant\n scripts. The problem is that with WID, the JRE contains xerces,\n during builds the plugins use the xerces plugin to load the\n xmls. The problem occurs when the is run on the main thread, the\n classloader does not pick up the xerces plugin rather uses the\n xerces that comes with the JRE, causing a class case exception\n that's wrapped in the CoreException.\n\n The solution is the create our own classloader that uses the\n plugin classloading first before loading the classes from the\n JRE.\n\n The code changes are in com.ibm.wbit.comptest.ant.\n There are 2 new classes RunAntWidPreferences.java and\n WidAntClassloader.java\n The RunAntWid.java class was updated to use those classes.", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q096", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR33483\nREPORTED COMPONENT NAME\n WS INTEGRATION\nREPORTED COMPONENT ID\n 5724I6600\nREPORTED RELEASE\n 620\nSTATUS\n CLOSED FIN\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2009-07-09\nCLOSED DATE\n 2009-07-09\nLAST MODIFIED DATE\n 2009-07-09\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q096", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R620 PSY\n UP", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q096", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How can I make use of the WebSphere MQ Read Ahead functionality from an application that uses the WebSphere MQ classes for JMS to create a subscription on a topic, and then synchronously receives messages that are published on that topic?", "logical_doc_id": 5, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q096", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "WebSphere MQ V7 introduced a new feature called \"Read Ahead [http://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.dev.doc/q026310_.htm]\". This performance optimization allows WebSphere MQ queue managers to stream non-persistent messages to client applications connecting via TCP/IP before the application has requested them. The client stores these messages in a Read Ahead Buffer. When an application requests a message, the client removes the message from the buffer and gives it to the application for processing.\nJMS applications running in one of the following environments:\nThe WebSphere MQ classes for JMS.\nThe WebSphere MQ Resource Adapter.\nThe WebSphere MQ OSGi bundles.\n\nthat connect to a WebSphere MQ queue manager using the CLIENT transport in WebSphere MQ messaging provider normal mode, [http://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.connect.doc/intro_jms_msgprov.htm] and receive messages synchronously, can make use of the new functionality.", "logical_doc_id": 5, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q096", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "This technote will look at how applications that subscribe to a topic need to be written in order to take advantage of the Read Ahead functionality, as well as discussing what JMS Destination and WebSphere MQ properties need to be set to turn on Read Ahead.", "logical_doc_id": 6, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q096", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Applications running within an WebSphere Application Server environment can also make use of this functionality. Details of how to do this will be covered in a future technote.\n\nWriting a JMS application to use Read Ahead to receive messages synchronously\nThe Read Ahead feature will only stream non-persistent messages to client applications that are getting messages outside of a transaction.\n\nIn JMS terms, this means that the application must be using a non-transacted JMS session that has an acknowledgement mode of either AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE in order to be eligible to make use of Read Ahead.\n\nHere is an example which shows an application creating a non-transacted, AUTO_ACKNOWLEDGE JMS Session:\nThe non-transacted JMS Session can then be used to create a MessageConsumer object for the JMS Destination that maps to the WebSphere MQ topic which the non-persistent messages will be published on.\n\nOnce the MessageConsumer has been created, applications that get non-persistent messages by calling one of the following methods:\n*\n*\nwill be eligible to make use of Read Ahead, if the JMS Destination and the WebSphere MQ topic that the Destination maps to allows this functionality.\n\nConfiguring the JMS Destination and WebSphere MQ to allow Read Ahead\nWhen an application uses the WebSphere MQ classes for JMS to subscribe to a WebSphere MQ topic, a managed subscription will be created. This managed subscription will either be durable or non-durable, depending upon how the application created the subscription.\n\nWith managed subscriptions, the WebSphere MQ Publish/Subscribe Engine will create a managed queue for the application. Every time a message is published on the WebSphere MQ topic that the application has subscribed to, the WebSphere MQ Publish/Subscribe Engine will take a copy of that message and put it onto the managed queue. When the JMS application requests a message, the WebSphere MQ Publish/Subscribe Engine will remove a message from the managed queue and returns it to the application for processing.\n\nBy default, the managed queue that the WebSphere MQ Publish/Subscribe Engine will create for applications that take out a subscription will be based on one of the following model queues:\nSYSTEM.DURABLE.MODEL.QUEUE\nSYSTEM.NDURABLE.MODEL.QUEUE\n\nThe model queues used to create the managed subscriptions can be changed by modifying the WebSphere MQ Topic properties MDURMDL and MNDURMDL [http://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.explorer.doc/e_properties_topics.htm].", "logical_doc_id": 7, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q096", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Whether Read Ahead will be enabled when the MessageConsumer gets the non-persistent messages that are published on the topic the MessageConsumer is subscribed to depends upon the following two properties:\nThe JMS Destination Property READAHEADALLOWED (RAALD) [http://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.ref.dev.doc/q112370_.htm]\nThe WebSphere MQ queue property DEFREADA of the model queue used to create the managed queue used by the managed subscription created for the application. [http://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.dev.doc/q032570_.htm]\n\nThe WebSphere MQ queue property DEFREADA specifies whether applications that get messages from this queue can use Read Ahead if they are getting non-persistent messages outside of a transaction.\n\nThe JMS Destination property READAHEADALLOWED controls whether JMS applications using a non-transacted Session that has an acknowledgement mode of either AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE will use Read Ahead when getting non-persistent messages from a queue.\n\nIt is a combination of these two properties that determines if Read Ahead will be used.\n\nThe following table shows the possible values for the READAHEADALLOWED and DEFREADA properties, and what they need to be set to for the Read Ahead functionality to be enabled:\n\n[/support/docview.wss?uid=swg21574053&aid=1] RAALD = NO RAALD = YES RAALD = AS_DEST\nor\nAS_TOPIC_DEF DEFREADA=NO Read Ahead\ndisabled Read Ahead enabled Read Ahead\ndisabled DEFREADA=YES Read Ahead\ndisabled Read Ahead enabled Read Ahead enabled DEFREADA=DISABLED Read Ahead\ndisabled Read Ahead\ndisabled Read Ahead\ndisabled\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM MQ\nPRODUCT ALIAS/SYNONYM\n WMQ WebSphere MQ MQSeries", "logical_doc_id": 7, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q297", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This interim fix provides a solution for APAR RS02616 and RS02614.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q297", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "The following list shows the components in Operational Decision Manager that are directly affected by this interim fix:\nRule Designer\nDecision Center\n\nYou can find more information on the problems in the following APAR descriptions: * [http://www.ibm.com/support/docview.wss?uid=swg1RS02192]RS02616 [http://www.ibm.com/support/docview.wss?uid=swg1RS02616]: DEFAULT TRIM BEHAVIOR CHANGED BETWEEN 8.0 AND 8.8\nRS02614 [http://www.ibm.com/support/docview.wss?uid=swg1RS02614]: RULE DESIGNER XOM DEPLOYMENTS APPEAR TO REQUIRE USE OF DEFAULT XOM .JAR NAME\n\nSEE ALSO\nOperational Decision Manager Interim Fixes [http://www.ibm.com/support/docview.wss?uid=swg21640630]\n\nINSTALLATION INSTRUCTIONS\nFollow the instructions in the readme.\n\nURL LANGUAGE SIZE(Bytes) Readme [http://download4.boulder.ibm.com/sar/CMA/WSA/06q9c/0/Readme.html] English 1886\nDOWNLOAD PACKAGE\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs]\nWhat is DD? [http://www6.software.ibm.com/dldirector/doc/DDfaq_en.html] 8.8.0.1-WS-ODM-IF045 02-Feb-17 Language Independent 11200000 FC [https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=ibm%2FWebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=All&platform=All&function=fixId&fixids=8.8.0.1-WS-ODM-IF045&includeRequisites=1&includeSupersedes=] [ ] DD\n [/support/docview.wss?uid=swg24043312&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24043312&aid=2]Problems (APARS) fixed\nRS02616 , RS02614\n\nA FIX IS AVAILABLE\nOperational Decision Manager V8.0.1.1 Fix Pack [http://www-01.ibm.com/support/docview.wss?uid=swg24034803]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q297", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When running a DVS test suite for a ruleset using a managed XOM,\n after an update to the XOM the changes are not found and the\n ruleset parsing fails.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q297", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Execute a different test suite not using the same XOM to reset\n the XOM classloader loaded in the SSP", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q297", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "the ssp keep the latest loaded classloader in memory. Each\n subsequent execution does not use the managed XOM it should", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q297", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "the code is modified so that a new classloader is created and\n use for each dvs test execution.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q297", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n RS01263\nREPORTED COMPONENT NAME\n WDS FOR RULES\nREPORTED COMPONENT ID\n 5725B6903\nREPORTED RELEASE\n 801\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-03-11\nCLOSED DATE\n 2013-03-28\nLAST MODIFIED DATE\n 2013-03-28\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\n999", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q297", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WDS FOR RULES\nFIXED COMPONENT ID\n 5725B6903", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q297", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R801 PSY\n UP", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q297", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The call fails and returns the following root cause, which points at missing XOM classes, although those classes have been deployed using the managed XOM feature:\n\nCause: java.lang.RuntimeException: java.rmi.RemoteException: CORBA NO_IMPLEMENT 0x4f4d0001 No; nested exception is:\norg.omg.CORBA.NO_IMPLEMENT:\nSERVER (id=4773e3aa, host=myhost.com) TRACE START:\norg.omg.CORBA.NO_IMPLEMENT: The sender's class RMI:test.MyParameterClass:1C07FA96BB0B7F99:1461E0CFE4DEDE78 is not present on the local classpath, and the class is not marked as truncatable, so it cannot be unmarshaled. vmcid: OMG minor code: 1 completed: No\nat com.ibm.rmi.io.IIOPInputStream.inputObjectFVD(IIOPInputStream.java:1536)\nat com.ibm.rmi.io.IIOPInputStream.simpleReadObjectInternal(IIOPInputStream.java:418)\nat com.ibm.rmi.io.IIOPInputStream.simpleReadObjectLoop(IIOPInputStream.java:526)\nat com.ibm.rmi.io.IIOPInputStream.readObjectDelegate(IIOPInputStream.java:386)\nat com.ibm.rmi.io.IIOPInputStream.readObjectOverride(IIOPInputStream.java:649)\nat java.io.ObjectInputStream.readObject(ObjectInputStream.java:359)\nat java.util.HashMap.readObject(HashMap.java:875)\nat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\nat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)\nat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)\nat java.lang.reflect.Method.invoke(Method.java:611)\nat com.ibm.rmi.io.IIOPInputStream.invokeObjectReader(IIOPInputStream.java:1708)\nat com.ibm.rmi.io.IIOPInputStream.inputObjectUsingClassDesc(IIOPInputStream.java:1443)\nat com.ibm.rmi.io.IIOPInputStream.inputObjectClassDesc(IIOPInputStream.java:1418)\nat com.ibm.rmi.io.IIOPInputStream.readSerializable(IIOPInputStream.java:1150)\nat com.ibm.rmi.io.IIOPInputStream.simpleReadObjectInternal(IIOPInputStream.java:441)\nat com.ibm.rmi.io.IIOPInputStream.simpleReadObject(IIOPInputStream.java:477)\nat com.ibm.rmi.io.ValueHandlerImpl.readValue(ValueHandlerImpl.java:210)\nat com.ibm.rmi.iiop.CDRReader.read_value(CDRReader.java:1573)\nat com.ibm.rmi.iiop.CDRReader.read_abstract_interface(CDRReader.java:1554)\nat com.ibm.rmi.iiop.CDRReader.read_abstract_interface(CDRReader.java:1546)\nat ilog.rules.res.session.impl.ejb3._EJSRemote0SFIlrStatefulSessionEJB3_476e3d99_Tie.execute__java_util_Map(_EJSRemote0SFIlrStatefulSessionEJB3_476e3d99_Tie.java)\nat ilog.rules.res.session.impl.ejb3._EJSRemote0SFIlrStatefulSessionEJB3_476e3d99_Tie._invoke(_EJSRemote0SFIlrStatefulSessionEJB3_476e3d99_Tie.java)\nat com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:623)\nat com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:476)\nat com.ibm.rmi.iiop.ORB.process(ORB.java:513)\nat com.ibm.CORBA.iiop.ORB.process(ORB.java:1574)\nat com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2845)\nat com.ibm.rmi.iiop.Connection.doWork(Connection.java:2718)\nat com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)\nat com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)\nat com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)\nSERVER (id=4773e3aa, host=myhost.com) TRACE END.\nvmcid: OMG minor code: 1 completed: No", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q297", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "You can specify which Java XOM resources and libraries to attach to a ruleset by setting the ruleset.managedxom.uris property as explained in the Information Center, section Decision Server V8.0 > Decision Server Rules > Managing business rule execution in Rule Execution Server > Deploying Java XOMs > Managed Java XOM > Managed Java XOM setup and lifecycle [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/con_res_managed_jxom_lifecycle.html].\n\nHowever, rule sessions cannot retrieve the managed-XOM class loader: rule sessions, whether POJO, Java SE, or EJB (Enterprise JavaBean), cannot access the class loader to build input and output objects for execution.\n\nThe managed Java XOM is therefore made available to the engine for ruleset parsing but not to the code that calls the ruleset. In the EJB case, rule sessions need to access the Java XOM classes so that they can serialize/deserialize the parameter objects of the custom XOM types that are exchanged with the remote client.\n\nThis constraint means that the managed Java XOM feature is useful mostly for decision services or for rulesets with simple-type parameters.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q297", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "If the ruleset parameters are of XOM custom types, make the XOM classes accessible to the rule session by packaging them into the deployed application, along with the product rule sessions.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q297", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#WODM V7.5 doc on Managed Java XOM [http://pic.dhe.ibm.com/infocenter/dmanager/v7r5/topic/com.ibm.dserver.res/Content/Business_Rules/_pubskel/Infocenter_Primary/ps_DS_Rule_Execution_Server1502.html]\nCalling and packaging EJB rule sessions for Java EE [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_dev_ejb_packag_j2ee.html]\n\n SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q297", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The method getXOMClassMappingForBOMType can be used in a\n scenario provider to get the class and clasloader information\n from the BOM and this can then be used to instantiate classes.\n When the XOM is managed by the RES this method does\n not return the class from the ruleset classloader and it is\n not possible to instantiate new instances from on it.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q297", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "The class returned by this method is serialized so there is no\n reference to the original classloader when it is available in\n the SSP", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q297", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The code is modified so that the provider class is created in\n the XOM classloader which makes every objects defined in the\n ruleset also available in the data provider.\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q297", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n RS01273\nREPORTED COMPONENT NAME\n WS DECISION CTR\nREPORTED COMPONENT ID\n 5725B6900\nREPORTED RELEASE\n 801\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-03-21\nCLOSED DATE\n 2013-04-15\nLAST MODIFIED DATE\n 2013-04-15\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\n999", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q297", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WS DECISION CTR\nFIXED COMPONENT ID\n 5725B6900", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q297", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R801 PSY\n UP", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q297", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "The WSDL automatically generated by the MTDS is not always what you expect or you may want to modify the binding. Since the WSDL is generated automatically at runtime, you cannot modify directly the WSDL in Rule Studio or Eclipse. Then, how to do it?", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q297", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "JRules leverages Java API for XML Web Services Annotations (JAX-WS) to get the WSDL generated from the java XOM", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q297", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "You will have to add annotations in your java XOM. The annotations will be processed when the WSDL generation API (JAX-WS) parse the java XOM.\n\nBut first, you will have to upgrade the version of the JAXWS libraries, as the version provided in JRules 7.0.x and 7.1.x (JAX-WS v2.1.1) is not compatible with annotations.\n\nYou can download the newer library (v2.1.7) from the JAX-WS reference implementation's web site: http://jax-ws.java.net/ [http://jax-ws.java.net/]\n\nYou will thus need to update the build script accordingly, so that it picks up the JAX-WS jar files from the newer version. This means modifying the definition in the build.xml file (in the MTDS project).\n\nThen, in your java XOM, add for instance the annotation @XmlElement(required=true) for the attributes that musts have a minoccur=\"1\" in the XSD so that they are no longer tagged as Optional in the WSDL generated.\n\nFor xml binding java annotations, refer to the java doc [http://docs.oracle.com/javase/6/docs/api/javax/xml/bind/annotation/package-tree.html]\n\nIf you want to have an attribute that is required and not nullable, you will annotate it :\n\npublic class Foo {\n@XmlElement(nillable=true, required=true)\npublic int bar;\n}\n\nThe XML generated will be :\n\n\n\n\n\n", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q106", "section_id": 0, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "WebSphere MQ 6.0 for HP OpenVMS Alpha and Itanium - Fix Pack 6.0.1.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24022202]\nWebSphere MQ 6.0 for HP OpenVMS Alpha and Itanium - Fix Pack 6.0.2.7 [http://www-01.ibm.com/support/docview.wss?uid=swg24027266]\nWebSphere MQ 6.0 for HP OpenVMS Alpha and Itanium - Fix Pack 6.0.2.10 (FP03) [http://www-01.ibm.com/support/docview.wss?uid=swg24029987]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q106", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "MQ 5.3 for HP OpenVMS\n High CPU consumption is noticed while AMQZMGR0 process is\n monitoring its child processes such as command server, channel\n initiator, and listener processes.\n .\n The customer looked at the call stack, the stack shows it is\n looping as follows:\n .\n AMQZMGR0 -> MQMCS+0011CD60 -> waitpid() -> fchown()\n .\n There is no FDCs, no errors in AMQERR*.LOG, and no MQ trace\n files are generated when doing strmqtrc.\n .\n To recreate the problem, the customer executes strmqm as\n follows:\n .\n mqs_startup (Start MQ)\n crtmqm\n dspmqver\n strmqm\n ana/image Check AMQZMGR0 ID and link date(Check build date)\n show system/proc=test* - List MQ processes\n mon proc/topc - Show CPU 100%\n ana/sys SDA - Show call stack information", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q106", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "On WMQ V6 on OpenVMS the process manager consumes high CPU even\n when queue manager is idle, while monitoring child processes.\n The queue manager works normally. When machine is loaded with\n tasks the CPU usage of the process manager comes down, because\n the system schedules other tasks. But anyway because of the\n high CPU intensive monitoring by the process manager some\n amount of CPU is always wasted.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q106", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "WMQ has been modified so that the process manager does not do\n a CPU intensive monitoring of child processes.\n The fix for this APAR will be available through WMQ6.0 FP1\n IBM WebSphere MQ for HP OPENVMS Alpha V6.0 IC58895 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC58895]\n IBM WebSphere MQ for HP OPENVMS Itanium V6.0 IC58896 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC58896]\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q106", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC58635\nREPORTED COMPONENT NAME\n MQSERIES OVMS I\nREPORTED COMPONENT ID\n 5724A3802\nREPORTED RELEASE\n 600\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2008-10-23\nCLOSED DATE\n 2008-11-27\nLAST MODIFIED DATE\n 2008-11-27\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q106", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n MQSERIES OVMS I\nFIXED COMPONENT ID\n 5724A3802", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q106", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R600 PSY\n UP", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q106", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do you correlate a thread consuming High CPU with a particular thread stack in the native_stdout.log?", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q106", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "This document explains how to correlate data from the MustGather below which utilizes GlancePlus: [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21166017]\nMustGather: Performance, Hang, or High CPU Issues on HP-UX [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21127574]\n\nThe following files will be used to determine the thread that has high CPU: * hpux_glance.out\nnative_stdout.log\n\nSample output from hpux_glance.out\n----16:26:11\ngbl cpu utilization = 93%\nalive processes = 213\nactive processes = 16\npriority queue = 0.1\nrun queue = 0.7\ncontext switch rate = 333\nnetwork packet rate = 1.6\ndisk phys io rate = 29.1\nmemory pageout rate = 0.0\nsystem call rate = 41834\nprocess fork rate = 0.0\nproc completion rate= 0.4\nhighest syscall rate= 9332 for system call write\narm compl tran rate = 0.0\n\nProcess name pid ktid pricpu%scall% dsptch cpu-swtch shell-cmd\n----------- --- ---- --- ---- ------ ------ --------- ---------\njava 11671 5134935 154 20 98 0 /opt/IBM/WebSphere/AppServer60\njava116715551377223828 334 0 /opt/IBM/WebSphere/AppServer60\n\n1. The hpux_glance.sh script outputs 13 times every 25 seconds and tracks CPU usage. Each section is separated by a timestamp. CPU usage is indicated in the cpu% column. By default it displays only java processes/threads.\n\n2. The pid column contains the process ID. If the PID is for an application server, the\n.pid contains the matching PID. You can find this file in the server logs directory. In the above example, the PID is 11671.\n\n3. The ktid column identifies an individual thread. In this example, the thread 5551377 is utilizing 82% of the CPU.\n\nSample thread dump from native_stdout.log\n\"WebContainer : 3\" daemon prio=10 tid=03025200 nid=92 lwp_id=5551377 runnable [0x5e4e4000..0x5e4e34f0]\nat java.io.FileOutputStream.writeBytes(Native Method)\nat java.io.FileOutputStream.write(FileOutputStream.java:260)\nat com.ibm.ejs.ras.WrappingFileOutputStream.write(WrappingFileOutputStream.java:362)\nlocked <67acb728> (a com.ibm.ejs.ras.WrappingFileOutputStream)\n...\n\n4. Search the native_stdout.log for the ktid. The ktid has a one-to-one correspondence with the lwp_id. In the example, the matching thread has lwp_id equal to 5551377.\n\n5. Review the thread dump to reveal the methods most likely causing the high CPU. RELATED INFORMATION\n MustGather: Performance Hang or High CPU on HP-UX [http://www.ibm.com/support/docview.wss?uid=swg21127574]", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q106", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "When CERTLABL is configured on the channel that DataPower is using to connect to queue manager, the connection would fail and DataPower MQ Queue Manager object would be down.\n\nThe following errors will be seen in the DataPower logs:\n[mq][error] mq-qm(mqqm): tid(238161): test connection failed (2539)\n [mq][error] mq-qm(mqqm): tid(238161): Queue Manager Error: 'mq-server.ibm.com:1111' ''. Reason code - 2539\n The reason code is: 2539 0x000009eb MQRC_CHANNEL_CONFIG_ERROR\n\nOn MQ Server, there will be error logs explaining this connection failure: *\n*\n* The SSL or TLS channel 'SSL.SVRCONN.2' is configured to use certificate label\n 'SSL.SVRCONN.2'. However, the remote peer did not send the necessary\n information to allow the local channel to use the correct certificate. The\n remote host is 'datapower (xxx.xxx.xxx.xxx)'.\nThis error occurs when the local channel definition has a certificate label and\n the remote peer does not support selection of certificates.\n The channel did not start.\n* Ensure that the remote peer supports certificate label configuration. Refer to\n the Security section of the WebSphere MQ Information Center for details of\n certificate label requirements. Alternatively, alter the local channel\n definition so that it does not specify a certificate label.", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q106", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "MQ version 8 and the later version provides a new parameter \"CERTLABL\" for administrators to specify a certificate to be used when making a SSL connection to a channel. This allows multiple certificates to be configured, one for each channel. All certificates are managed in the same queue manager on MQ Server. In order to utilize this function, both ends of the channel must be running MQ version 8 or the later version and must support Server Name Indication (SNI).\nAlthough DataPower version 7.2.0 runs MQ version 8 client and also supports SNI for the rest of the services, it does not support SNI for MQ Queue Manager object.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q106", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "MQ Server version 8, DataPower version 7.2.0", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q106", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "In order for DataPower to connect to the queue manager, the CERTLABL must be removed from the channel, which means you must not configure the CERTLABL on the MQ Server. After removing the CERTLABL from the channel, the channel would use the default certificate as configured in queue manager's properties.", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q106", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM MQ V8 Features and Enhancements [http://www.redbooks.ibm.com/redbooks/pdfs/sg248218.pdf]", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q106", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Why does WebSphere DataPower spike with a high CPU rate when a WebSphere MQ connection is unavailable? Is there a solution to this issue?", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q106", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "If the value of Retry Attempts is set to 0 on the DataPower MQ Queue Manager object, this negates the benefits of the Long Retry Interval since it will not be used. DataPower will retry forever using the specified Retry Interval. The default setting of Retry Attempts as 0 and Retry Interval as 1 second is provided to preserve backward compatibility. However, these default values should be changed to take advantage of Long Retry Interval feature available in firmware.", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q106", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "The solution to the issue of having DataPower vulnerable to the MQ Queue Manager being inaccessible is to change the Retry Attempts parameter on the Configure MQ Queue Manager window from 0 to some number. As an example, change the parameters as follows:\nRetry Attempts - change the default of 0 to 6 Retry Interval - change the default of 1 to 10 seconds Long Retry Interval - change the default of 1800 to 600 seconds (10 minutes)\n\nIn the event that the Queue Manager is down or a connection is not established, the above example configuration will allow the MQ QM Object to retry 6 times with 10 second intervals. After 6 attempts, the MQ QM object will retry every 10 minutes.\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower Integration Appliance XI50 Firmware 3.8 Business Integration WebSphere DataPower Low Latency Appliance XM70 Firmware 3.8\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q106", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "CPU usage can spike and cause performance degradation when new\n synchronous replicas request data from primary shards during\n startup.", "logical_doc_id": 5, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q106", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: WebSphere eXtreme Scale users running with *\nthe eXtreme IO (XIO) transport. *\n\nPROBLEM DESCRIPTION: New synchronous replicas that *\naggressively copy data from the *\nprimary shard can cause high CPU *\nusage. *\n\nRECOMMENDATION: *\n\nNew synchronous replicas request data quickly from primary\n shards during startup. The aggressive replication can cause\n high CPU usage during this time. After a synchronous replica\n copies all the existing data from the primary shard, it\n receives data in real time from the primary shard, and the CPU\n returns to normal.\n Customers using asynchronous replicas can see a similar\n problem when primary shards move to new containers. The method\n of transferring an existing primary to a new location uses a\n temporary synchronous replica and can see high CPU usage\n during this time.\n This fix automatically regulates the replication rate based on\n how fast the primary shard responds to the synchronous replica\n in XIO environments.", "logical_doc_id": 5, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q106", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Apply the interim fix.\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q106", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI15315\nREPORTED COMPONENT NAME\n WS EXTREME SCAL\nREPORTED COMPONENT ID\n 5724X6702\nREPORTED RELEASE\n 860\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-04-04\nCLOSED DATE\n 2014-04-15\nLAST MODIFIED DATE\n 2014-04-15\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q106", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WS EXTREME SCAL\nFIXED COMPONENT ID\n 5724X6702", "logical_doc_id": 5, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q106", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R860 PSY\n UP", "logical_doc_id": 5, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q111", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "StaleConnectionException may be seen after upgrade JCC driver.\n\nWebsphere log file:\n\n SystemOut.log:[10/6/10 17:29:01:089 MST] 0000005e ConnectionEve A\nJ2CA0056I: The Connection Manager received a fatal connection error\nfrom the Resource Adapter for resource jdbc/db2xa/ear/PUX1Q/DB_MIND.\nThe exception which was received is com.ibm.websphere.ce.cm.\nStaleConnectionException: [jcc][t4][2028][11149][3.58.136] Actual code\npoint, 0x2413 does not match expected code point, 0x2408. ERRORCODE=-\n4499, SQLSTATE=null:com.ibm.db2.jcc.am.qo: [jcc][t4][2028][11149]\n[3.58.136] Actual code point, 0x2413 does not match expected code\npoint, 0x2408. ERRORCODE=-4499, SQLSTATE=null", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q111", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Fix for this issue incorporated in JCC driver version 3.59.81 that was shipped with DB2 v9.5fp6a or later and DB2 v9.7fp2 or later (defect 134363):\nhttps://www-304.ibm.com/support/docview.wss?uid=swg1IC66739 [https://www-304.ibm.com/support/docview.wss?uid=swg1IC66739]\n\nAs a workaround, \"COMMIT ON RETURN YES\" can be added to the definition of stored procedure on the host.\n\nYou might receive SQL0751N or XAER_NOTA on XA END while using \"COMMIT ON RETURN YES\" if stored procedure call is a part of XA transaction.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q111", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Technote 1433093 [http://www.ibm.com/support/docview.wss?uid=swg21433093]\nAPAR IZ07301 [https://www.ibm.com/support/docview.wss?uid=swg1IZ07301]\nAPAR IC66739 (134363) [https://www.ibm.com/support/docview.wss?uid=swg1IC66739]\n\nz/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q111", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Customer Rep: Fission Lin\n\n Problem: Agents connect to remote TEMS 3 not viewed\n\n Action Taken:\n\n Please open an apar with the following severity and information:\n\n ==\n Compid: 5724C04MS\n\n Abstract: stale ephemeral lb entries lead to connection errors.\n\n Environment:\n All supported Tivoli platforms at tepfp5, d7121a.\n\n Problem Description:\n a remote TEMS attached via ephemeral pipe will\n leave \"stale\" GLB entries (of the form \"0.0.0.n\")\n at the HUB if the remote TEMS re-registers without\n an intervening normal shutdown (where it explicitly\n unregisters the problem entries). Once this occurs, the\n HUB will find the stale entries first, and cause distributed\n requests to that REMOTE to fail with connection errors even\n though the remote and any attached agents appear online.\n\n Detailed Recreation Procedure:\n Connect a remote TEMS to a HUB using the ephemeral keyword\n (KDE_TRANSPORT=...IP.PIPE EPHEMERAL:Y ...) in the configuration\n of the remote TEMS. Once the remote TEMS has connected to the\n HUB and registered with the GLB, force a situation distribution\n to that remote TEMS. Having then a situation distributed to the\n remote TEMS, crash that remote TEMS and restart it. Once\n restarted, the HUB will experience comm failures trying to\n again distribute a situation to that remote TEMS. The comm\n errors will be associated with the old remote TEMS address.\n\n Related Files and Output:\n The RAS1 log for the HUB will show communication failures to the\n remote TEMS with an address with an ephemeral address (of the\n form \"0.0.0.n\") which is not the address registered by that\n remote:\n\n KDSRU001 Remote request communication failure to destination\nHUB ip.pipe:0.0.0.1.1918..\n\n Approver:\n nic\n\n ==\n\n Action Planned: Proceed with defect resolution.", "logical_doc_id": 3, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q111", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All ITMS/ENGINE users. *\n\nPROBLEM DESCRIPTION: STALE EPHEMERAL LB ENTRIES LEAD TO *\nCONNECTION ERRORS *\n\nRECOMMENDATION: Apply the PTF. *\n\nA remote TEMS attached via ephemeral pipe will leave \"stale\"\n GLB entries (of the form \"0.0.0.n\") at the HUB if the remote\n TEMS re-registers without an intervening normal shutdown\n (where it explicitly unregisters the problem entries). This\n typically occurs when a remote TEMS crashes after connecting\n to the HUB. Once this crash happens, the HUB will find old,\n stale remote TEMS entries first, and cause distributed\n requests to that REMOTE to fail with connection errors even\n though the remote and any attached agents appear online.", "logical_doc_id": 3, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q111", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Code in Basic Services was changed to remove all ephemeral\n addresses on behalf of the remote TEMS when NETWORK and\n INTERFACE compare flags are set on the same call. Code in the\n TEMS was changed to (re)register the remote TEMS address with\n each heartbeat, thus maintaining currency.\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q111", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n OA23485\nREPORTED COMPONENT NAME\n CT/ENGINE\nREPORTED COMPONENT ID\n 5608A41CE\nREPORTED RELEASE\n 610\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2007-12-11\nCLOSED DATE\n 2007-12-11\nLAST MODIFIED DATE\n 2009-05-20\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n OA22688 [http://www-01.ibm.com/support/docview.wss?uid=swg1OA22688]\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\nKDE1LNKP KLXN", "logical_doc_id": 3, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q111", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n CT/ENGINE\nFIXED COMPONENT ID\n 5608A41CE", "logical_doc_id": 3, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q111", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R610 PSY UA38475 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UA38475]\n UP07/12/15 P F712\n\nFIX IS AVAILABLE\nSELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL. YOU WILL BE REQUIRED TO SIGN IN. DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES.", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q111", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The client log shows something like the following example:\n\n2011-04-11T11:32:29.291+0300 INFO :\n\n CliSessionContext (CCM_ADDR=myhost192:54049:x.x.128.186, user=ccm_root, server=http:/myserver:8400, database=/ccmdb/mydb): Received command [finduse, myscript.sh,3.1:shsrc:1] {cli}\n\n2011-04-11T11:32:29.293+0300 WARNING:\n\nCliSessionContext (CCM_ADDR=myhost192:54049:x.x..128.186, user=ccm_root, server=http://myserver:8400, database=/ccmdb/mydb): General IO error. java.net.SocketException:\n\nConnection reset IO related error. Connection reset\n\nRecommendation: Please check data communication, protocol data, etc. {cli}\n\nGeneral IO error. java.net.SocketException\n\n2011-04-11T11:32:29.297+0300 INFO :\n\nCliSessionContext (CCM_ADDR=myhost192:54049:x.x.128.186, user=ccm_root, server=http://myserver:8400, database=/ccmdb/mydb): Command completion status 4, time 280 ms {cli}", "logical_doc_id": 4, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q111", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Errors in the Synergy Web Mode backend session API may be caused by the API itself (ie. this may be a code issue) or by the backend session Accent code (ie. this may be an Accent code issue or a database corruption)", "logical_doc_id": 4, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q111", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "IBM Rational Synergy clients operating in Web Mode connect to a pool of backend Synergy sessions which run on the Synergy Web Server. The Web Server manages the web client connections and distributes queries and requests for data amongst the backend sessions in a round robin fashion.", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q111", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "It is important to determine whether it is the API itself or the backend sessions which are the source of the problem. This is not obvious from the error messages in the logs.\n\n1. Issues of incompatibility between the Synergy server and client binaries must be eliminated as possible causes.\n\n2. Also the database should be checked for any corruption.\n\n3. If necessary the backend sessions can be traced for any Accent errors", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q111", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "1. Run the command \"ccm version -a\" on the server and on the client to ensure thay are at the same patch and ifix level. Check the /db/MDL_INFO file to ensure the database matches the binaries on the server and client.\n\n2. Log onto the Synergy server as the Synergy admin user (usually ccm_root) and run the command...\n\nccmdb check \n\n......to ensure that there is no database corruption.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q111", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Resolve any database corruption with reference to the following technotes:\n\nhttp://www.ibm.com/support/docview.wss?uid=swg21325223 [http://www.ibm.com/support/docview.wss?uid=swg21325223] # for Informix databases\nhttp://www.ibm.com/support/docview.wss?uid=swg21325720 [http://www.ibm.com/support/docview.wss?uid=swg21325720] # for Oracle databases\n\nIf steps 1. or 2. above show any issues which require resolution then, once the issues are resolved, retry the Synergy Web Mode operation which resulted in the original \"General IO error. java.net.SocketException\" error to see if the problem is now cleared. If, however, the problem persists continue to get an Accent trace of the Synergy backend sessions.\n\n3. Accent tracing\nThe suspicion should be that there may be an underlying Accent code error which is coming back to the java-based Synergy Web Mode API and causing the IO error. To check this we can try to get an Accent trace.\n\nTracing can be done of Accent backend sessions within web mode based clients. The Accent code will be traced from the incoming call from the API until that call is returned from the Accent code. Every call is traced until the Accent tracing is turned off regardless if the call is executed using different backend sessions. This means that trace output can be interlaced because of calls from the client being executed in parallel by different backend sessions.\n\nTurning on tracing using GUI\nAccent tracing within the GUI is turned on using the \"hidden\" options within the Tools menu in the Synergy GUI. Open the Tools Menu > Options dialog, Press Ctrl+D, click Ok. Open the Tools Menu again, this menu will now have a number of new menu items, use the Start Accent tracing menu item.\n\nTurning on tracing using CLI\nThe \"ccm trace_on \" command will turn on the Accent tracing from the web mode CLI.\nLog files will be found in /log/_ui.log and /log/_eng.log ....where is the name of the user who will reproduce the error.\n\nMake sure these log files are cleared down before turning on the trace and reproducing the error condition. Accent traces can be rather large and customers may need the help of Technical Support to analyse them. Look for calls to svm_api in engine log to see what calls are made to the work area server.\n\nIf difficulties continue with the Web Mode and \"General IO error...\" please contact Technical Support for additional troubleshooting options.", "logical_doc_id": 5, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q111", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Steps to reproduce:\n\n 1. Migrate data warehouse to a different database, for example, from Derby to IBM DB2\n\n 2. Run the JTS Common job using the WebUI:\n\n https://[your-server-name]:[port]/jts/admin#action=com.ibm.team.reportsManagement.etlConfig\n\nThe job fails and the following error message appears in the JTS log file:\n\n WARN internal.registry.AbstractActivationManagerOwner - An error occurred while trying to execute a service method java.lang.IllegalStateException: This service proxy does not have a reference to the most current instance in the service manager. If you hit this problem, your code is most likely holding onto a stale service reference and using it after it has been deactivated.", "logical_doc_id": 6, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q111", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The root cause of this problem is the change in the database settings for data warehouse connection.", "logical_doc_id": 6, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q111", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "SOLUTION\n\nRestart the JTS server to prevent the errors.", "logical_doc_id": 6, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q111", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Lotus\u00ae Connections Profiles does not recognize the most recent changes made to the underlying data store that stores user profile data, and you suspect that the culprit is a stale cache.\n\nHow do you modify the last-modified cache in Lotus Connections Profiles?", "logical_doc_id": 7, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q111", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The Profiles last-modified (last-mod) cache is used to enable clients and proxies to validate the freshness of cached profile page data without requiring the WebSphere Application Server (WAS) to query the database for reasons related to performance.\n\nIn production environments, identity management tools, such as Tivoli Directory Integrator, will periodically update the database utilized by Profiles. As those user identity management tools operate independently of WAS and, therefore, have no access to the profiles last-modified time cache, it is important to flush the cache to ensure data freshness.\n\nThe Administrative MBean used in Lotus Profiles does not expose the properties necessary to alter the last-modified cache refresh cycle, thus modifying these properties manually is required.", "logical_doc_id": 7, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q111", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "This issue has been reported to Quality Engineering as SPR# JKIY72CP5N and has been fixed in Connections 1.0.2.\n\nWorkaround:\n\n1. Using a text editor, modify the profiles-config.xml file located in the Application Server \"config\" directory under:\n ${WAS_HOME}/profiles/${YOUR_PROFILE}/cells/${YOUR_CELL} -->\n /nodes/${YOUR_NODE}/LotusConnections-config/profiles-config.xml\n\n2. Locate the section \"/\"\n\n3. Modify the following settings as required to ensure that your Lotus Connections Profiles system utilizes the most recently data as is feasible.\n XML Element Value Type Description 24 hour (HH:MM) time The initial time from which this task is queued to start Minutes The interval between last-modified cache refreshes Minutes A built in delay to prevent the cache from being run until at least X minutes after the application server has been started.\n 4. Save the changed made to profiles-config.xml\n\n5. Start and stop the Profiles application to cause the new settings to take effect..\n*", "logical_doc_id": 7, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q135", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "Possible abrupt data access loss that can be prevented", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q135", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "This problem was recently recognized, and can cause the interface adapters to suddenly halt, and close the links. No data internal to the box is lost.\n\nRecovery option are in recommended order:\n\n1. Upgrade system firmware\n 2. Reboot system\n 3. Reset Interface Adapters.\n\nTo Prevent Access Loss, please read further.\n\nOn Flashsystem 720/820:\n\nCode levels less than 6.3.2_p2 are affected.\n\nAll Adapter types are affected. FC, IB\n\nRun System Report from Gui Panel, or CLI (system report)\n\nOpen file, check header page information:\n\n=== System Report ===\n=== Fri Mar 06 07:44:40 CST 2015 ===\n\n= System overview =\n\nSystem type: RamSan-820\nVersion: 6.3.1-p10\nUptime: 07:44:46 up 248 days, 17:18, load average: 5.16, 5.26, 5.42\nCapacity (GiB): 19199\nChassis serial: 00R1CC3\nMTMS: 9834-AE2-00R1CC3\nETH0: 10.10.65.96\nSID: ef275\n\nIf Uptime is at 248 day, and box has halted\u2026..Reboot\n\nNote: Due to the abrupt halt, and both interface cards halting simultaneously, recovery code can fail Flashcards that are not really not defective. Display using CLI \u201cstorage\u201d command, or GUI storage panel. If Flashcards are in failed state, Contact Support for resolution.\n\nIf lower than 248:\n\n1. Reboot box on a scheduled basis. Reboot will reset timer, and Uptime will be accurate.\n\n2. Use Cli, and reset Fibre Adapter cli command fc reset fc reset fc-1 or fc-2 wait a few minutes between adapter resets to let the network settle. Using this method is concurrent, but will not update Uptime counter\n\nFor IB adapters: ib reset ib reset ib-1 or ib reset ib-2\n\nFix Now Available:\n\n6.3.2-p2 posted on 04/06/2015 with resolution to 248-day bug\nhttp://www.ibm.com/support/fixcentral/ [http://www.ibm.com/support/fixcentral/]\n\nOn Flashsystem 840, or V840\n\nFirmware levels less than 1.1.3.7 are affected.\n\nAll Adapter types are affected. FC, IB, FCOE, iSCSi\n\nGui access:\n\nLogin screen, or click on System:\n\nTop Left corner:\n\n[/support/docview.wss?uid=ssg1S1005126&aid=1]\n\nClick on Actions:\n\n[/support/docview.wss?uid=ssg1S1005126&aid=2]\n\nClick on Properties:\n\n[/support/docview.wss?uid=ssg1S1005126&aid=3] [/support/docview.wss?uid=ssg1S1005126&aid=3]\n\nWe have found a more accurate way to Calculate Adapter level time remaining until Lockup:\n(This may require support Assistance to complete)\nOn the System Report, search for os_cpu_tick\n\nTotal number of ticks for os_cpu_tick is 2147483648", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q135", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "|===== OS Timers =====| -> sncon_cmd: os.timers\nOS_Time == 542143780, 3 Active timers\n[10000] ticks: 1 expire: 542143780 pdata:0x0 cb: os_cpu_tick\n[10001] ticks: 30 expire: 542143807 pdata:0x0 cb: hw_dma_watchdog\n[10002] ticks: 100 expire: 542143806 pdata:0x0 cb: sp_watchdog\nFormula:\n\n2147483648 - 542143780 / 100/ 60 / 60 /24 = 185 days remaining until Adapter lock-up\n\ntotal ticks - current os_cpu_tick/100 /60 /60 /24 = days remaining until Adapter lockup\n\nThis must be repeated for ALL 4 Adapters 04, 08, 0C, and 10\n\nUptime is displayed\u2026\n\nIf at 248, and box has halted\u2026\u2026..Reboot.\n\nstopsystem \u2013reboot Note: This command is non-concurrent\n\nIf below 248, three options:\n\n1. Upgrade to a new firmware level (if below 1.1.3.6). The action of installing firmware concurrently will reset the adapters one at a time.\n\nFix Now Available:\n\n1.1.3.8-43.46 posted on 04/17/2015 with resolution to 248-day bug\nhttp://www.ibm.com/support/fixcentral/ [http://www.ibm.com/support/fixcentral/]\n\n2. Schedule a reboot during a maintenance window.\n\nNote: Do not use GUI and do NOT use \"satask stopnode to reboot.\n\nUse CLI procedure:\n\n1) Determine NON-config node using lsnodecanister\n2) Reboot non-config node using stopsystem \u2013reboot \u2013node (approximately 5 minutes)\n3) force failover satask startservice -force THEN log back into cluster\n(approximately 1 minute)\n4) Reboot remaining node using stopsystem \u2013reboot \u2013node (approximately 5 minutes)\n3. Reset adapters one at a time using CLi commands:\n\nnote: Using this method is concurrent, but will not update Uptime counter.\n\nsvctask maintenance -action reset -canister 1 -adapter 1\nsvctask maintenance -action reset -canister 1 -adapter 2\n\n(wait a few minutes to allow paths to recover)\n\nsvctask maintenance -action reset -canister 2 -adapter 1\nsvctask maintenance -action reset -canister 2 -adapter 2\n\nCross reference information Segment Product Component Platform Version Edition Flash Storage IBM FlashSystem 720 Platform Independent Version Independent Flash Storage IBM FlashSystem 840 Platform Independent Version Independent Flash Storage IBM FlashSystem V840 Platform Independent Version Independent Flash Storage RamSan-820 Platform Independent Version Independent Flash Storage RamSan-720 Platform Independent Version Independent\n\nAIX FIXES ARE AVAILABLE\nIBM Spectrum Control V5.2.14 (May 2017) [http://www-01.ibm.com/support/docview.wss?uid=swg24043414]\nIBM Spectrum Control V5.2.15 (August 2017) [http://www-01.ibm.com/support/docview.wss?uid=swg24043749]\nIBM Spectrum Control V5.2.15.2 (November 2017) [http://www-01.ibm.com/support/docview.wss?uid=swg24044286]\nIBM Spectrum Control V5.2.16 (March 2018) [http://www-01.ibm.com/support/docview.wss?uid=swg24044454]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q135", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "After upgrading SVC firmware to 7.8.1, the device server becomes\n inaccessible and appears to hang. Cannot access the Spectrum\n Control user interface until the connection between Spectrum\n Control and the SVC is shut down.\n\n The follow messages are observed repeatedly for different port\n numbers in dmSvcTrace.log and traceTPCDeviceServer.log:\n\n SSH Port forwarding failed for local port <#>\n com.ibm.tpc.monitor.SVCEventListener\n\n establishSshTunnelPortForwarding\n SVC-Notification-xxxx-xxxx-xxxx\n\n Connection failed. \n com.ibm.tpc.common.api.napi.NAPIConnectionException: rc = 0,\n msg = No connection established.\n\n You would also see a large number of network connections owned\n by the device server pid. (ps -ef | grep deviceServer)\n > netstat -lanp | grep LISTEN | grep \n\n As a result, errors like the following are also logged:\n Failed to create input file\n /opt/IBM/TPC/device/log/epm/xxxx.txt\n java.io.FileNotFoundException:\n /opt/IBM/TPC/device/log/epm/xxxx.txt (Too many open files)", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q135", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nIBM Spectrum Control 5.2.x users monitoring *\nSVC/Storwize/Flash devices at firmware level 7.8.1 *\n\nPROBLEM DESCRIPTION: *\nIBM Spectrum Control 5.2.x device server becomes *\ninaccessible and appears to hang after adding or upgrading a *\nSVC/Storwize/Flash device to firmware to 7.8.1. The device *\nserver becomes inaccessible and appears to hang. Users *\ncannot access the Spectrum Control user interface until the *\nconnection between Spectrum Control and the SVC is shut *\ndown. *\n*\nSee IBM Support Flash (Alert) for additional details: *\nhttp://www-01.ibm.com/support/docview.wss?uid=swg22002420 *\n\nRECOMMENDATION: *\nApply IBM Spectrum Control fix maintenance when available. *\n*\nUpgrade SVC/Storwize/Flash devices to firmware to 7.8.1.1 or *\nhigher. Or contact IBM Support to request an ifix for 7.8.1 *\n-- reference SVC APAR HU01531 *", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q135", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The solution to this problem includes fixes for both IBM\n Spectrum Control and the storage system. Apply the fix for\n Spectrum Control to stabilize the system and prevent it from\n hanging. Reboot the Spectrum Control server to free up\n connections prior to applying a fix. Also apply a minimum\n firmware level of 7.8.1.1, or the ifix for APAR HU01531 to\n resolve connection issues with the storage system for event\n notification.\n\nThe Spectrum Control fix for APAR IT20204 is targeted for the\n following maintenance package:\n\n| refresh pack | 5.2-TIV-TPC-RP0014 - target May 2017\n\nFixed in IBM Spectrum Control 5.2.14\n\nhttp://www.ibm.com/support/docview.wss?&uid=swg21320822 [http://www.ibm.com/support/docview.wss?&uid=swg21320822]\n\nThe target dates for future refresh packs do not represent a\n formal commitment by IBM. The dates are subject to change\n without notice.\n\nRecommended to upgrade SVC/Storwize/Flash devices to firmware to\n 7.8.1.1 or higher. Or contact IBM Support to request an ifix\n for 7.8.1 -- reference SVC APAR HU01531.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q135", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT20204\nREPORTED COMPONENT NAME\n TPC\nREPORTED COMPONENT ID\n 5608TPC00\nREPORTED RELEASE\n 52C\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n YesHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2017-04-13\nCLOSED DATE\n 2017-05-17\nLAST MODIFIED DATE\n 2017-08-28\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q135", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n TPC\nFIXED COMPONENT ID\n 5608TPC00", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q135", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R52C PSY\n UP\nR52D PSY\n UP", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q135", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Installing firmware using the USB port on the service processor on a system that is not managed by an HMC:\n\nThis method is generally recommended if you are directed to do so by your next level of support, by an isolation procedure, or after exchanging the service processor assembly.\n\nDownloading the server firmware fix and copying it to a USB flash drive\n\nNote: These instructions are written for the generic USB flash drive without any added software.\n\nTo download the fix and copy to a USB flash drive, you should follow these steps:\n\n1. From a computer or server with an Internet connection, go to this Recommended Fixes [http://www-912.ibm.com/s_dir/slkbase.nsf/ibmscdirect/e58d7bbf0eac9a2786256ead005f54d8?OpenDocument&TableRow=3.2#3.] page. 2. Locate the desired firmware from the previous step and save the associated .rpm and .xml files (as an example, EL350_118_038.rpm). 3. Verify that your USB flash drive is formatted to FAT32. If it is not, you should complete the following steps:\n\na. Plug your USB flash drive into the USB slot of your server or computer. A message will display informing you that the operating system recognizes the drive, and it is ready to use.\n\nb. Double-click My Computer, and then right-click the appropriate device drive.\n\nc. Select Format. The Format Removable Disk dialogue box is displayed.\n\nd. Ensure that the File system field displays FAT32 and that the Quick Format check box is cleared. All other fields remain in their default setting.\n\ne. Click Start. Attention: A warning message will display to inform you that the format action will erase all of the data in the flash memory. Click OK to allow the process to continue.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q135", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "f. Click OK when the action is complete. 4. Insert the blank, formatted USB flash drive into the USB port on the server or computer where you copied the .rpm and .xml files. A message will display informing you that the operating system recognizes the drive and it is ready to use. 5. Copy the .rpm and .xml files to the USB flash drive. 6. To remove the USB flash drive safely, double-click the Safely Remove Hardware icon in the lower right corner of the screen. 7. Follow the prompts to remove the USB flash drive. 8. Continue with installing the server firmware through the USB port on the service processor assembly.\nInstalling the server firmware through the USB port on the service processor assembly\n\nTo install the server firmware through the USB port on the service processor assembly, perform the following steps:\n\nImportant Note: Do not interrupt this process after you begin. 1. Ensure that the server is in service processor standby. Service processor standby is indicated when the server is powered off, and the power-on LED on the control panel is blinking slowly. 2. Insert the USB flash drive into one of the following:\n\no The top USB port on the back on a rack-mounted system\no The right-most USB port on a deskside system\nFor additional information, refer to the Location Codes section in the host model of the service guide.\n\nThe firmware level will load automatically. The level of firmware on the USB flash drive will be installed onto both the P and T sides of the service processor assembly.\n\nSeveral checkpoints will be posted on the control panel during the installation of the firmware. They are as follows:\n\no C100B101: The firmware image is being installed on a side of the flash.\no C100B102: The firmware image is being installed on the other side of the flash.\no C100B103: The firmware installation has been completed successfully.\n\nNote: If a C100B104 code is displayed, the firmware installation has failed. You should perform the following steps:", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q135", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "1. Ensure that the USB flash drive contains the firmware fix. If necessary, copy the firmware to the USB flash drive again.\n2. Retry the task with another USB flash drive.\n3. If necessary, consult your service provider.\n4. After checkpoint C100B103 is displayed on the control panel, you can safely remove the USB flash drive.\n5. Continue with verifying that the firmware installed correctly.\n\nVerifying that the firmware installed correctly\n\nTo verify that the firmware installed correctly, you should perform the following steps: 1. Access the ASMI and view the level of server firmware displayed in the upper-right corner below the copyright statement on the Welcome pane. 2. Verify that the level of server firmware that is displayed is the level that you installed. 3. If the level of server firmware that is displayed is not the level that you installed, retry installing the firmware using another USB flash drive. If the problem persists, contact your next level of support.\n\nHISTORICAL NUMBER\n 591426009", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q135", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What fixes and known issues are included in 20140413_Proventia_10G_Network_Active_Bypass_update-8_fw3.9-34?", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q135", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Important: Installation instructions have changed depending on Firmware currently installed. Look at readme included with the patch for detailed instructions.\nNew fixes added in this update (firmware 3.9-34)\nIntroduces fixes for OpenSSL Vulnerabilities:\nIntroduces fixes for OpenSSH Vulnerabilities: *\nIntroduces a new feature for uploading security certificates through the LMI. *\nIntroduces a fix in which user/password parameters are no longer required when configuring the SMTP notifications, but both are still available as optional.\nIntroduces a new feature that allows for installation of this firmware at any patch. *\n*\n*\nInstallation of firmware 3.4-23 or higher will only allow network negotiation when both external device and NAB network ports are set to fixed, or both set to auto.\n\nKnown Issues in update (firmware 3.9-34)\nIn some cases, invalid security certificates can be uploaded to the unit. In case the LMI is no longer accessible, the user must login to the unit as the root user through a console or SSH connection, remove all pem files from the flash directory and reboot the unit.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q135", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Upgrading to 3.9 from 3.4 may cause the root password to change. Upgrading will also break the ability to change the root and admin password from both LMI and admin console. Follow the steps in Technote http://www.ibm.com/support/docview.wss?uid=swg21672103 [http://www.ibm.com/support/docview.wss?uid=swg21672103] to fix the issue.\nNTP/TACACS menus have extra options other than enable/disable. These options do not do anything and will be removed in the next release.\nBond service is currently not working.\n\nNew fixes added in this update (firmware 3.4-23)\nFixes issue where End User License Agreement does not show up after installing update with install script through console.\nFixes issue where switchd process some times uses close to 100% CPU.\nUpgrades to a newer version of Openssh, Lighttpd, and Php.\nNew features added: *\n*\n*\n*\n*\n*\n*\n\nNew fixes added in this update (firmware 2.18-42)\nCorrects an issue that made it necessary to remove and then reapply power to reset the 10G NAB after installing a firmware update.\nUpgrades to a newer version of OpenSSL.\nCorrects an issue that caused duplicate notifications (including SNMP traps and e-mails) to be sent upon state change events.\nCorrects an issue that could lead to system instability when using certain TACACS+ server configurations.\nCorrected an issue where the 'link mode' heartbeat fail-over delay was longer than normal.\n\nFixes previously included in update 5 (firmware 2.15-36)\nCorrects an issue with the heartbeat receive routine, and adds new checks to prevent buffer corruption.\nAddresses a buffer overflow in the 'updated' process.\nCorrects an issue that prevented NTP from starting automatically after a reboot.\n\nFixes previously included in update 4 (firmware 2.13-34)\nCorrects an issue which could cause port statistics values to appear blank even when traffic is flowing.\nAdds support for additional duplex and link speed options on the management interface.\n\nFixes previously included in update 3 (firmware 2.11-28)\nCorrects an issue in which heartbeat emitting procedures on different segments could overlap and cause a 10G NAB to go into bypass unnecessarily.\n\nFixes previously included in update 2 (firmware 1.0.0343c3c)\nA race condition has recently been discovered in the stock Proventia Network Active Bypass 10G (NAB) firmware that will cause this appliance to experience high CPU utilization. This patch implements a workaround to automatically reboot the 10G NAB when this situation is detected.\n\nFixes previously included in update 1 (firmware 1.0.2919)\nCorrects an issue that prevents this appliance from successfully passing multicast traffic.", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q135", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "Download the IBM WebSphere DataPower XC10 Appliance Version 2.1 firmware upgrade. You can also download the client, which is required for WebSphere DataPower XC10 Appliance to work", "logical_doc_id": 5, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q135", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "This firmware release includes improved capability and new features for WebSphere DataPower XC10 Appliance Version 2.1.\n\nCaution: After you upgrade either 9235-92X or 7199-92X appliance types with Version 2.1 firmware, you cannot roll back to any previous firmware version. You must operate at the Version 2.1 or higher firmware level.\n\nWhen you are upgrading to Version 2.1, you cannot run a firmware upgrade on a collective that is currently servicing workload. When you upgrade a collective from a previous major version of DataPower XC10 Appliance, all of the data, not including your configuration, that was loaded into the data grids is lost. In addition, all members of the collective must be upgraded to the same major version (Version 2.1.0.x) before service can be restored. Upgrades between fix packs, for example, versions 2.1.0.0 to 2.1.0.1, can be done with no loss of service and while servicing workload as long as each appliance is upgraded individually and you wait for the upgraded appliance to reboot and re-replicate before proceeding to upgrade the next appliance. When you are running firmware upgrades on the appliances in a collective from a version prior to 2.1, the appliance that you upgrade does not fully restart until all of the appliances in the collective are upgraded to Version 2.1.\n\nYou must complete the firmware upgrade process on one appliance before starting the process on another appliance within the collective. Do not make any configuration changes until all of the appliances are on the same firmware level. See Updating the firmware [http://pic.dhe.ibm.com/infocenter/wdpxc/v2r1/topic/com.ibm.websphere.datapower.xc.doc/aa/aat_updating_firmware.html] in the WebSphere DataPower XC10 Appliance Information Center, for more information.\n\nFor IBM WebSphere DataPower XC10 Appliance to work with WebSphere Application Server or clients in a stand-alone environment, you must install the WebSphere eXtreme Scale Client or package the client Java archive (JAR) files with your application. You can download the client from this document as well.\n\nClient installation: If you have a previous version of the client, an upgrade is not available. Use IBM Installation Manager to install the full version of the client.\n\nINSTALLATION INSTRUCTIONS\nComplete the following instructions to download the firmware and client images.", "logical_doc_id": 5, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q135", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "1. Initialize and configure the appliance.\n The firmware upgrades for the 9235-92x and 7199-92x appliances are available in this document. See Initializing and configuring WebSphere DataPower XC10 Appliance [http://publib.boulder.ibm.com/infocenter/wdpxc/v2r1/topic/com.ibm.websphere.datapower.xc.doc/tinitappl.html] in the product information center for more information about the initialization and firmware upgrade process.\n 2. Install the client for your appliance to work. 1. Download one or more of the following images from this page:\n Description File name WebSphere eXtreme Scale Client in a stand-alone environment image_xs_client.8500.zip WebSphere eXtreme Scale Client for WebSphere Application Server Version 6 image_xs_client_was6.8500.zip WebSphere eXtreme Scale Client for WebSphere Application Server Version 7 image_xs_client_was7.8500.zip WebSphere eXtreme Scale Client for WebSphere Application Server Version 8 image_xs_client_was8.8500.zip\n 2. Install IBM Installation Manager [http://www-01.ibm.com/support/docview.wss?uid=swg24031300].\n 3. Use Installation Manager to install the product from the product repositories that you downloaded in step 1.\n\nSee Installing WebSphere eXtreme Scale Client [http://publib.boulder.ibm.com/infocenter/wdpxc/v2r1/topic/com.ibm.websphere.datapower.xc.doc/tinstclient.html] for more information about installing the client.\n\nDOWNLOAD PACKAGE\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is DD? [http://www6.software.ibm.com/dldirector/doc/DDfaq_en.html] 9235-92x Firmware 3 May 2012 English 379568542 HTTP [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+DataPower+XC10+Appliance&release=All&platform=All&function=fixId&fixids=2.1.0.0-WS-DPXC10-a1218.02220817-9235&includeSupersedes=0] DD 7199-92x Firmware 3 May 2012 English 379534233 HTTP [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+DataPower+XC10+Appliance&release=All&platform=All&function=fixId&fixids=2.1.0.0-WS-DPXC10-a1218.02220817-7199&includeSupersedes=0] DD image_xs_client.8500.zip 27 Apr 2012 English 1472522240 FTP [ftp://public.dhe.ibm.com/software/websphere/extended/support/wxs/wxs8500client/image_xs_client.8500.zip] DD image_xs_client_was6.8500.zip 27 Apr 2012 English 87135232 FTP [ftp://public.dhe.ibm.com/software/websphere/extended/support/wxs/wxs8500client/image_xs_client_was6.8500.zip] DD image_xs_client_was7.8500.zip 27 Apr 2012 English 226498560 FTP [ftp://public.dhe.ibm.com/software/websphere/extended/support/wxs/wxs8500client/image_xs_client_was7.8500.zip] DD image_xs_client_was8.8500.zip 27 Apr 2012 English 250612736 FTP [ftp://public.dhe.ibm.com/software/websphere/extended/support/wxs/wxs8500client/image_xs_client_was8.8500.zip] DD", "logical_doc_id": 5, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q267", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What are the features incorporated with the \"Tools and Utilities\" License key for IBM Rational Rhapsody?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q267", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "You would like to know all the features of the Tools and Utilities license key", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q267", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "The license features that come incorporated with IBM Rational Rhapsody Tools & Utilities Add on keys are as follows:\nReporterPro\nReporter\nRPGetConnected\nRPGetConnectedWind\nRPGetConnectedVxw\nRPGetConnectedSol\nRPGetConnectedN\nRPGetConnectedG\nRPUNCS\nRPTcSEAddon\nRPGraphPanel\nRPRG\nRPRG_DOORS\nRPRG_X2TXT\nRPRG_REQPRO\nRPRG_RP\nRPRG_SIMULINK\nRPRG_TAGGER\nRPRG_CALIBERRM\nRPUSimulink\nRPXMI\nRPTAUXMI\n\nNote: Important functionalities of Rational Rhapsody such as Gateway [ RPRG], Import and Export of XMI files in Rhapsody [RPXMI], Panel Diagrams [RPGraphPanel] and Reporter Plus [ReporterPro] among others are covered", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q267", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "Rational DOORS license features [http://www-01.ibm.com/support/docview.wss?uid=swg21607708]\nRational TAU License features [http://www-01.ibm.com/support/docview.wss?uid=swg21608087]\nRational Build Forge features [http://www-01.ibm.com/support/docview.wss?uid=swg21608803]\nRational Dashboard [http://www-01.ibm.com/support/docview.wss?uid=swg21608812]", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q267", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How to generate a Floating license key for IBM Rational System Architect with DODAF", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q267", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Steps to generate a license key for Rational System Architect with add-ons from the Rational License key center:\n\n1. Open the Rational License key center page at: http://www.ibm.com/software/rational/support/licensing/ [http://www.ibm.com/software/rational/support/licensing/]\n 2. Log in using your login credentials sent in the welcome email\n 3. Click 'Get Keys'\n 4. Select the Product 'IBM Telelogic System Architect'\n 5. Select 'Telelogic System Architect Floating single site'\n 6. Check the availability box of license keys and then hit 'Next'\n 7. Enter the Number of keys to generate and fill the information for the below fields\n Version: Select the appropriate product version\n Existing Hosts: select 'Use existing host'\n Server Configuration: select 'Single license server'\n Host Id type: select accordingly from the list\n Host Id: enter the host id as selected from the above option\n Host name: enter host name of the machine\n Port: enter the port number (19353)\n Description: Enter a short description\n 8. Click 'Generate' and the next page will display the license file\n 9. Click 'Download License Keys' and save the file as 'license.dat' on the machine", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q267", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do you change the trial download into a permanently licensed product after you have installed the evaluation version of an IBM Rational Software Development Platform desktop product, such as Rational Software Architect?", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q267", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Trial version of Rational software products can be converted to the permanent licensed products by applying/enabling the permanent license key over a evaluation key.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q267", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Follow the instructions below to install the activation kit or to enable floating license keys. The product activation kits contain the permanent license key for converting a trial Rational product.\n\nAfter you download a product activation kit, you must import the kit from the download location by using IBM Installation Manager.\n\nNote: IBM Rational Method Composer uses the product activation kit, license keys and the IBM Installation Manager as of version 7.2 and 7.5, but it does not support floating license keys.\n\nTo import an activation kit and enable the new license key\n\n1. Start IBM Installation Manager.\n\n2. On the main page, click Manage Licenses.\n\n3. On the Install Packages page, select a package and click Import product enablement kit.\n\n4. Click Next.\n Details for the selected package are displayed, including the current license kind and the version range to which the license applies.\n\n5. Browse to the path of the download location for the kit, then select the appropriate Java archive (JAR) file and click Open.\n\n6. Click Next. The Summary page displays the target install directory for the activation kit, the product the new license applies to, and version information.\n\n7. Click Finish.\n\nTo enable floating license keys\n\n1. Start IBM Installation Manager.\n\n2. On the main page, click Manage Licenses.\n\n3. On the Install Packages page, select a version of a package, click Configure license servers, and click Next.\n\n4. On the License Servers page, select the Enable Rational Common Licensing check box.\n\n5. Configure one or more license server connections. 1. Click the Add button.\n 2. In the Add Server window, in the Name field, type the host name of the license server.\n 3. (Optional) In the Port field, type a value for environments where a firewall is used. Do not assign a value to this port unless your administrator instructs you to do so.\n 4. Click OK.\n 5. If your system administrator has given you the host names of additional license servers, repeat the steps to add each server.\n For a redundant license server configuration (in which three servers are used), type each host name in this format: hostname1, hostname2, hostname3.\n For each port number, type accordingly: host1port#, host2port#, host3port#.\n\n6. Click Next.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q267", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "7. (Optional) Configure the license usage order for your custom packages. The order of licenses in the list determines the order in which your product attempts to obtain license keys for specific licenses.\n\n8. Click Finish.\n\nNote: The Manage Licenses wizard indicates whether the floating licenses configuration is successful. When you open the enabled product next, a connection is created to the license server to obtain a license key from the pool of available floating license keys.\n\nFor the latest version\n\nTo enable floating license keys\n 1. In IBM Installation Manager, go to Manage Licenses, then Select the product that you would like import\n 2. Select Configure Floating license support and click Next\n 3. Select Enable floating license enforcement and click on + button\n 4. Select Server type > Add Name > Add Port\n 5. Click on Test Connection > OK\n 6. Select Next > Finish\n\n1.\n\nTo import an activation kit and enable the new license key\n\n1. Launch IBM Installation Manager.\n 2. Click the Manage Licenses button.\n 3. Highlight the product for which you are importing the activation kit.\n 4. Click the Import product activation kit radio button.\n 5. Click Next.\n 6. Browse to the .jar file and click Next.\n 7. After reading and accepting the license agreement click Finish.\n 8. You should receive a message stating that the license import was successful. Click Finish\n 9. You will now be back on the main page of the Installation Manager.\n 10. Click the Manage Licenses button.\n 11. Highlight the product for which you just imported the activation kit.\n 12. Click the Configure floating license support radio button.\n 13. Click Next.\n 14. Click the Disable floating license enforcement radio button.\n 15. Click Finish.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q267", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#1250404: Product Activation of Eclipse-based Rational P [http://www.ibm.com/support/docview.wss?uid=swg21250404]\nA Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21568947]\nA simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21570367]\nA Korean translation is available [http://www.ibm.com/support/docview.wss?uid=swg21575178]\n\nfixpack; patch DOWNLOADABLE FILES", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q267", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "IBM Telelogic Rhapsody 7.4.0.1 fix pack release.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q267", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "The Telelogic Rhapsody version 7.4.0.1 fix pack release is available for download on the IBM FixCentral site.\n\nPREREQUISITES\nTelelogic Rhapsody 7.4.0.1 replaces existing versions of Telelogic Rhapsody 7.4. It is possible to install Telelogic Rhapsody 7.4.0.1 concurrently with releases prior to 7.4.\n\nLicensing:\nThe upgrade to Rhapsody 7.4.0.1 is included for all licenses with current maintenance contracts.\nYou can now use the License Key Center [https://www-01.ibm.com/software/rational/support/licensing/] [https://www-01.ibm.com/software/rational/support/licensing/l] to get and manage your keys for Telelogic products. This includes Telelogic software purchases made through IBM as well as for legacy orders through Telelogic AB.\n\nThe IBM license agreement entitles users to \u201cborrow\u201d licenses from a floating license server for use offline when disconnected from the server. If you wish to use this capability then you need to obtain a new license file with borrowing enabled.\n\nUsers with Rhapsody 7.0 or earlier licenses will need to get a new license to use Rhapsody 7.4.0.1 from the License Key Center [https://www-01.ibm.com/software/rational/support/licensing/]\n\nSystem Requirements:\n\nSupported Host Platforms\n*\n*\n*\nHardware Requirements *\n*\n*\n\nINSTALLATION INSTRUCTIONS\nFor specific installation instructions, please refer to the Rhapsody Read Me file, Rhapsody Installation Guide, and Rhapsody Upgrade guide located on the Fix Central site.\n\nURL LANGUAGE SIZE(Bytes) Install Guide for Windows and Linux [http://download2.boulder.ibm.com/sar/CMA/RAA/00g5u/1/install.pdf] English 788590\nDOWNLOAD PACKAGE\nPlease select the FixCentral packages directly below, or follow the steps outlined to obtain all associated documentation and install packages.a\n\n1. Download Rhapsody 7.4.0.1 and view more detailed documentation such as the Read Me file and the Defects Fixed List at: Fix Central http://www-933.ibm.com/support/fixcentral/ [http://www-933.ibm.com/support/fixcentral/]\n2. Select Rational as the product group.\n3. Select product \u201cTelelogic Rational\u201d\n4. Select Installed Version as 7.4.\nNOTE: Do NOT select 7.4.0.1 at this point. You will be directed to the proper release by selecting 7.4\n5. Choose the platform desired\n6. Click continue\n7. On Identify Fixes page select Browse Fixes and All and click continue\n8. Select the Fix pack or click Select all and click Continue\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options\nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] Windows Installer 3/24/2009 English 603720000 FC [http://download2.boulder.ibm.com/sar/CMA/RAA/00g5u/1/Rhap741WinBuild1367309.zip] [ ] Linux Installer 3/24/2009 English 363920000 FC [http://download2.boulder.ibm.com/sar/CMA/RAA/00g68/2/Rhap741LinuxBuild1367309.tar.gz] [ ]\nTECHNICAL SUPPORT\n\nRational Telelogic software support\nLinks to specific product support pages plus general topics such as downloads and product documentation are available from the IBM Rational Telelogic software support main page [http://www.ibm.com/rational/support/telelogic].", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q267", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "RSA; RSM; RSD; rda; rpt; rft; rmt; rdbe; rad; A. \uc601\uad6c; \uc784\uc2dc; \uc2e4\uc2dc\uac04; \ub77c\uc774\uc13c\uc2a4; \ud0a4; \uc784\uc2dc; \ub77c\uc774\uc13c\uc2a4; \ud3c9\uac00; GA; \ubc84\uc804; 1254371; SDP; RMC; \uc81c\ud488 \ud65c\uc131\ud654 \ud0b7 \uac00\uc838\uc624\uae30; \ub77c\uc774\uc13c\uc2a4 \uadf8\ub807\uc9c0\ub9cc \ubd80\ub3d9 \uad6c\uc131 TECHNOTE (FAQ)\n\n\uc9c8\ubb38\n [Korean] Rational Software Architect \uc640 \uac19\uc740 \uc18c\ud504\ud2b8\uc6e8\uc5b4 \uc804\ub2ec \ud50c\ub7ab\ud3fc\uc758 \ub370\uc2a4\ud06c\ud0d1 \uc81c\ud488\uc758 \ud3c9\uac00\ud310\uc744 \uc124\uce58\ud6c4 \uc2dc\ud5d8\ud310\uc744 \uc601\uad6c \ub77c\uc774\uc13c\uc2a4\uac00 \uc801\uc6a9\ub41c \uc81c\ud488\uc73c\ub85c \ubcc0\uacbd\ud558\ub824\uba74 \uc5b4\ub5bb\uac8c \ud569\ub2c8\uae4c?\n\n\uc751\ub2f5\n\ub2e4\uc74c \uc9c0\uc2dc\uc0ac\ud56d\uc744 \ub530\ub77c\uc11c \ud65c\uc131\ud654 \ud0b7\uc744 \uc124\uce58\ud558\uac70\ub098 Floating \ub77c\uc774\uc13c\uc2a4 \ud0a4\ub97c \uc0ac\uc6a9\ud558\uc5ec \uc8fc\uc2ed\uc2dc\uc624. \uc81c\ud488 \ud65c\uc131\ud654 \ud0b7(Activation kit) \uc5d0\ub294 \ud3c9\uac00\ud310 Rational \uc81c\ud488\uc744 \uc804\ud658\ud560\uc218\uc788\ub294 \uc601\uad6c \ub77c\uc774\uc13c\uc2a4 \ud0a4\uac00 \ud3ec\ud568\ub418\uc5b4 \uc788\uc2b5\ub2c8\ub2e4. \uc81c\ud488 \ud65c\uc131\ud654 \ud0b7\uc744 \ub2e4\uc6b4\ub85c\ub4dc\ud55c \ub2e4\uc74c IBM Installation Manager\ub97c \uc0ac\uc6a9\ud558\uc5ec \ub2e4\uc6b4\ub85c\ub4dc \uc704\uce58\uc5d0\uc11c \ud574\ub2f9 \ud0b7\uc744 \uc801\uc6a9\ud558\uc5ec\uc57c \ud569\ub2c8\ub2e4.\n\n\ucc38\uace0: Rational Method Composer \uc81c\ud488\uc740 \ud65c\uc131\ud654 \ud0b7\uc744 , \ub77c\uc774\uc13c\uc2a4 \ud0a4 \uadf8\ub9ac\uace0 Installation Manager \ub97c \ubc84\uc83c 7.2 \uc640 7.5\ubd80\ud130 \uc9c0\uc6d0\ud558\uace0\uc788\uc2b5\ub2c8\ub2e4 \ud558\uc9c0\ub9cc \ud50c\ub85c\ud305 \ub77c\uc774\uc13c\uc2a4\ud0a4\ub294 \uc9c0\uc6d0\ud558\uc9c0 \uc54a\uc2b5\ub2c8\ub2e4.\n\n\ud65c\uc131\ud654 \ud0b7\uc744 \uc801\uc6a9\ud558\uc5ec \uc0c8 \ub77c\uc774\uc13c\uc2a4 \ud0a4 \ub97c \uc0ac\uc6a9\ud558\ub294 \ubc29\ubc95\n\n1. IBM Installation Manager\ub97c \uc2dc\uc791\ud558\uc2ed\uc2dc\uc624.\n\n2. \uae30\ubcf8 \ud398\uc774\uc9c0\uc5d0\uc11c \ub77c\uc774\uc13c\uc2a4 \uad00\ub9ac(Manage Licenses) \ub97c \ud074\ub9ad\ud558\uc2ed\uc2dc\uc624.\n\n3. \ud328\ud0a4\uc9c0 \uc124\uce58 \ud398\uc774\uc9c0\uc5d0\uc11c \ud328\ud0a4\uc9c0\ub97c \uc120\ud0dd\ud558\uace0 \uc81c\ud488 \uc0ac\uc6a9 \ud0b7 \uac00\uc838\uc624\uae30\ub97c \ud074\ub9ad\ud558\uc2ed\uc2dc\uc624.\n\n4. \ub2e4\uc74c(Next) \uc744 \ub204\ub974\uc2ed\uc2dc\uc624.\n\n\uc120\ud0dd\ud55c \ud328\ud0a4\uc9c0\uc758 \uc138\ubd80\uc0ac\ud56d\uc778 \ub77c\uc774\uc13c\uc2a4 \uc720\ud615 \ubc0f \ub77c\uc774\uc13c\uc2a4\uac00 \uc801\uc6a9\ub418\ub294 \ubc84\uc804 \ubc94\uc704\uac00 \ud45c\uae30\ub429\ub2c8\ub2e4.\n\n5. \ud65c\uc131\ud654 \ud0b7\uc758 \ub2e4\uc6b4\ub85c\ub4dc \uc704\uce58 \uacbd\ub85c\ub97c \ucc3e\uc740 \ud6c4 \ud574\ub2f9 Java \uc544\uce74\uc774\ube0c (JAR) \ud30c\uc77c\uc744 \uc120\ud0dd\ud558\uace0 \uc5f4\uae30(Open)\ub97c \ud074\ub9ad\ud558\uc2ed\uc2dc\uc624.\n\n6. \ub2e4\uc74c(Next) \uc744 \ub204\ub974\uc2ed\uc2dc\uc624. \uc694\uc57d \ud398\uc774\uc9c0\uc5d0\uc11c \ud65c\uc131\ud654 \ud0b7\uc758 \ub300\uc0c1 \uc124\uce58 \ub514\ub809\ud1a0\ub9ac, \uc0c8 \ub77c\uc774\uc13c\uc2a4\uac00 \uc801\uc6a9\ub41c \uc81c\ud488 \ubc0f \ubc84\uc804 \uc815\ubcf4\ub97c \ud45c\uc2dc\ud569\ub2c8\ub2e4.\n\n7. \uc644\ub8cc(Finish) \ub97c \ub204\ub974\uc2ed\uc2dc\uc624.\n\nFloating \ub77c\uc774\uc13c\uc2a4 \ud0a4 \ub97c \uc801\uc6a9\ud558\ub294 \ubc29\ubc95\n\n1. IBM Installation Manager\ub97c \uc2dc\uc791\ud558\uc2ed\uc2dc\uc624.\n\n2. \uae30\ubcf8 \ud398\uc774\uc9c0\uc5d0\uc11c \ub77c\uc774\uc13c\uc2a4 \uad00\ub9ac(Manage licenses) \ub97c \ud074\ub9ad\ud558\uc2ed\uc2dc\uc624.\n\n3. \ud328\ud0a4\uc9c0 \uc124\uce58 \ud398\uc774\uc9c0\uc5d0\uc11c, \ud328\ud0a4\uc9c0 \ubc88\ud638\ub97c \uc120\ud0dd\ud55c \ub2e4\uc74c \ub77c\uc774\uc13c\uc2a4 \uc11c\ubc84 \uad6c\uc131(Configure License servers) \uc744 \ud074\ub9ad\ud558\uace0 \ub2e4\uc74c(Next) \uc744 \ud074\ub9ad\ud558\uc2ed\uc2dc\uc624.\n\n4. \ub77c\uc774\uc13c\uc2a4 \uc11c\ubc84 \ud398\uc774\uc9c0\uc5d0\uc11c Rational Common Licensing \uc0ac\uc6a9 \uc120\ud0dd\ub780(Enable Rational Common Licensing) \uc744 \uc120\ud0dd\ud558\uc2ed\uc2dc\uc624.\n\n5. \ud558\ub098 \uc774\uc0c1\uc758 \ub77c\uc774\uc13c\uc2a4 \uc11c\ubc84 \uc5f0\uacb0\uc744 \uad6c\uc131\ud558\uc2ed\uc2dc\uc624.\n\na. \ucd94\uac00 \ub2e8\ucd94(Add) \ub97c \ud074\ub9ad\ud569\ub2c8\ub2e4.\n\nb. \uc11c\ubc84 \ucd94\uac00 \ucc3d\uc5d0\uc11c, \uc774\ub984 \ud544\ub4dc( Name) \uc5d0 \ub77c\uc774\uc13c\uc2a4 \uc11c\ubc84\uc758 \ud638\uc2a4\ud2b8 \uc774\ub984\uc744 \uc785\ub825\ud558\uc2ed\uc2dc\uc624.\n\nc. (\uc120\ud0dd\uc0ac\ud56d) \ud3ec\ud2b8 \ud544\ub4dc(Port) \uc5d0\uc11c, \ubc29\ud654\ubcbd\uc774 \uc0ac\uc6a9\ub418\ub294 \ud658\uacbd\uc758 \uac12\uc744 \uc785\ub825\ud558\uc2ed\uc2dc\uc624. \uad00\ub9ac\uc790\uc758 \uc9c0\uc2dc\uac00 \uc5c6\uc73c\uba74 \uc774 \ud3ec\ud2b8\uc5d0 \uac12\uc744 \uc9c0\uc815\ud558\uc9c0 \ub9c8\uc2ed\uc2dc\uc624.\n\nd. \ud655\uc778 (OK) \uc744 \ub204\ub974\uc2ed\uc2dc\uc624.\n\ne. \uc2dc\uc2a4\ud15c \uad00\ub9ac\uc790\uac00 \ucd94\uac00 \ub77c\uc774\uc13c\uc2a4 \uc11c\ubc84\uc758 \ud638\uc2a4\ud2b8 \uc774\ub984\uc744 \uc81c\uacf5\ud55c \uacbd\uc6b0, \uc774 \ub2e8\uacc4\ub97c \ubc18\ubcf5\ud558\uc5ec \uac01 \uc11c \ubc84\ub97c \ucd94\uac00\ud558\uc2ed\uc2dc\uc624.\n\n\ubc31\uc5c5 \ub77c\uc774\uc13c\uc2a4 \uc11c\ubc84(Redundant License server) \uad6c\uc131 (\uc138 \uac1c\uc758 \uc11c\ubc84\uac00 \uc0ac\uc6a9\ub418\ub294 \uacbd\uc6b0), \uac01 \ud638\uc2a4\ud2b8 \uc774\ub984 \ud615\uc2dd: hostname1, hostname2, hostname3 \uc744 \uc785\ub825\ud558\uc5ec\uc8fc\uc2ed\uc2dc\uc624 \ub610\ud55c \uac01\uac01\uc758 \ud3ec\ud2b8 \ubc88\ud638\ub97c \uc785\ub825\ud558\uc5ec\uc8fc\uc2ed\uc2dc\uc624. : host1port#, host2port#, host3port#.\n\n6. \ub2e4\uc74c(Next) \uc744 \ub204\ub974\uc2ed\uc2dc\uc624.\n\n7. (\uc120\ud0dd\uc0ac\ud56d) \uc0ac\uc6a9\uc790 \uc815\uc758 \ud328\ud0a4\uc9c0\uc758 \ub77c\uc774\uc13c\uc2a4 \uc0ac\uc6a9 \uc21c\uc11c\ub97c \uad6c\uc131\ud558\uc2ed\uc2dc\uc624. \ubaa9\ub85d\uc758 \ub77c\uc774\uc13c\uc2a4 \uc21c\uc11c\uac00 \uc81c\ud488\uc774 \ud2b9\uc815 \ub77c\uc774\uc13c\uc2a4\uc758 \ub77c\uc774\uc13c\uc2a4 \ud0a4\ub97c \uac00\uc838\uc624\ub294 \uc21c\uc11c\ub97c \uacb0\uc815\ud569\ub2c8\ub2e4.\n\n8. \uc644\ub8cc(Finish) \ub97c \ub204\ub974\uc2ed\uc2dc\uc624.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q267", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "\ucc38\uace0: \ub77c\uc774\uc13c\uc2a4 \uad00\ub9ac \ub9c8\ubc95\uc0ac\uac00 Floating \ub77c\uc774\uc13c\uc2a4 \uad6c\uc131\uc758 \uc131\uacf5 \uc5ec\ubd80\ub97c \ud45c\uc2dc\ud569\ub2c8\ub2e4. \ub2e4\uc74c \ubc88\uc5d0 \uc81c\ud488\uc744 \uc5f4\uba74, \ub77c\uc774\uc13c\uc2a4 \uc11c\ubc84\uc5d0 \ub300\ud55c \uc5f0\uacb0\uc774 \uc791\uc131\ub418\uc5b4 \uc0ac\uc6a9 \uac00\ub2a5\ud55c Floating \ub77c\uc774\uc13c\uc2a4 \ud0a4\uc758 \ud480\uc5d0\uc11c \ub77c\uc774\uc13c\uc2a4 \ud0a4\ub97c \uc5bb\uc2b5\ub2c8\ub2e4.\n\n\ucd5c\uc2e0 \ubc84\uc804\uc758\n\nFloating \ub77c\uc774\uc13c\uc2a4 \ud0a4 \uc0ac\uc6a9\n\n1. Installation Manager\uc5d0\uc11c \ub77c\uc774\uc13c\uc2a4 \uad00\ub9ac(Manage Licenses) \ub97c \uc120\ud0dd\ud558\uc2e0\ud6c4 , \ub77c\uc774\uc13c\uc2a4\ub97c \uc801\uc6a9 \ud558\uc2dc\uace0\uc790 \ud558\ub294 \uc81c\ud488\uc744 \uc120\ud0dd\ud558\uc5ec \uc8fc\uc2ed\uc2dc\uc624.\n\n2. Floating \ub77c\uc774\uc13c\uc2a4 \uc9c0\uc6d0 \uad6c\uc131( Configure Floating license support) \uc744 \uc120\ud0dd\ud558\uace0 \ub2e4\uc74c\uc744 \ud074\ub9ad\ud558\uc2ed\uc2dc\uc624.\n\n3. Floating \ub77c\uc774\uc13c\uc2a4 \uc801\uc6a9 (Enable Floating license enforcement) \uc744 \uc0ac\uc6a9 \uac00\ub2a5\ud558\uac8c \ud558\uace0+ \ub2e8\ucd94\ub97c \ud074\ub9ad\ud558\uc2ed\uc2dc\uc624\n\n4. \uc11c\ubc84 \uc720\ud615(Server Type) > \ucd94\uac00 \uc774\ub984(Add name) > \ud3ec\ud2b8 \ucd94\uac00 (Add port) \ub97c \uc120\ud0dd\ud558\uc5ec \uc8fc\uc2ed\uc2dc\uc624.\n\n5. \uc5f0\uacb0 \ud14c\uc2a4\ud2b8> \ud655\uc778\uc744 \ud074\ub9ad\ud558\uc2ed\uc2dc\uc624.\n\n6. \ub2e4\uc74c> \uc644\ub8cc\ub97c \ud074\ub9ad\ud558\uc2ed\uc2dc\uc624.\n\n\ud65c\uc131\ud654 \ud0b7\uc744 \uc801\uc6a9\ud558\uc5ec \uc0c8\ub85c\uc6b4 \ub77c\uc774\uc13c\uc2a4\ub97c \ud65c\uc131\ud654 \ud558\ub294 \ubc29\ubc95\n\n1. IBM Installation Manager\ub97c \uc2e4\ud589\ud558\uc2ed\uc2dc\uc624.\n\n2. \ub77c\uc774\uc13c\uc2a4 \uad00\ub9ac \ubc84\ud2bc\uc744 \ud074\ub9ad\ud558\uc5ec \uc8fc\uc2ed\uc2dc\uc624 ( Manage Licenses)\n\n3. \ud65c\uc131\ud654 \ud0a4\ud2b8\ub97c \uc801\uc6a9\ud558\uc2dc\ub824\ub294 \uc81c\ud488\uc744 \ud558\uc774\ub77c\uc774\ud2b8 \ud558\uc5ec \uc8fc\uc2ed\uc2dc\uc624.\n\n4. \ud65c\uc131\ud654 \ud0a4\ud2b8 \ubd88\ub7ec\uc624\uae30 ( Import Product activation kit) \ubc84\ud2bc\uc744 \ub20c\ub7ec\uc8fc\uc2ed\uc2dc\uc624.\n\n5. \ub2e4\uc74c\uc744 \ud074\ub9ad\ud558\uc2ed\uc2dc\uc624.\n\n6. .jar \ud30c\uc77c\uc758 \uacbd\ub85c\ub97c \uac80\uc0c9\ud55c\ud6c4 \ub2e4\uc74c(Next) \uc744 \ud074\ub9ad\ud558\uc5ec\uc8fc\uc2ed\uc2dc\uc624.\n\n7. \ub77c\uc774\uc13c\uc2a4 \uacc4\uc57d\uc744 \uc77d\uace0 \uc2b9\uc778\ud55c \ud6c4 \uc644\ub8cc(Finish) \ub97c \ud074\ub9ad\ud558\uc2ed\uc2dc\uc624.\n\n8. \ubcf8 \ub77c\uc774\uc13c\uc2a4 \uc801\uc6a9\uc774 \uc131\uacf5\ud588\ub2e4\ub294 \uba54\uc2dc\uc9c0\uac00 \ud45c\uc2dc\ub429\ub2c8\ub2e4. \uc644\ub8cc\ub97c \ub204\ub974\uc2ed\uc2dc\uc624.\n\n9. \uc774\uc81c \ub2e4\uc2dc \uc124\uce58 \uad00\ub9ac\uc790\uc758 \uae30\ubcf8 \ud398\uc774\uc9c0\uac00 \ud45c\uc2dc\ub429\ub2c8\ub2e4. .\n\n10. \ub77c\uc774\uc13c\uc2a4 \uad00\ub9ac \ubc84\ud2bc\uc744 \ud074\ub9ad\ud558\uc5ec \uc8fc\uc2ed\uc2dc\uc624 ( Manage Licenses)\n\n11. \ud65c\uc131\ud654 \ud0a4\ud2b8\ub97c \uc801\uc6a9\uc2dc\ud0a8 \uc81c\ud488\uc744 \uc120\ud0dd\ud558\uc5ec \uc8fc\uc2ed\uc2dc\uc624.\n\n12. \ud50c\ub85c\ud305 \ub77c\uc774\uc13c\uc2a4 \uc9c0\uc6d0 \uad6c\uc131 ( Configure Floating license support) \ubc84\ud2bc\uc744 \ud074\ub9ad\ud558\uc5ec \uc8fc\uc2ed\uc2dc\uc624\n\n13. \ub2e4\uc74c(Next) \uc744 \ub204\ub974\uc2ed\uc2dc\uc624.\n\n14. \ud50c\ub85c\ud305 \ub77c\uc774\uc13c\uc2a4 \ube44\ud65c\uc131\ud654 ( Disable Floating License) \ub97c \ud074\ub9ad\ud558\uc5ec \uc8fc\uc2ed\uc2dc\uc624.\n\n15. \uc644\ub8cc\ub97c \ud074\ub9ad\ud558\uc2ed\uc2dc\uc624.\n\n\uad00\ub828 \uc815\ubcf4\n#1250404: Product Activation of Eclipse-based Rational P [http://www.ibm.com/support/docview.wss?uid=swg21250404]\nAn US English translation is available [http://www.ibm.com/support/docview.wss?uid=swg21254371]\n\n\uad50\ucc28 \ucc38\uc870 \uc815\ubcf4 \uc138\uadf8\uba3c\ud2b8 \uc81c\ud488 \uad6c\uc131\uc694\uc18c \ud50c\ub7ab\ud3fc \ubc84\uc804 \uc5d0\ub514\uc158 Software Development Rational Application Developer for WebSphere Software Licensing Windows 7.0 Software Development Rational Asset Manager Licensing Windows 7.0 Software Development Rational Business Developer Licensing Windows 7.0 Software Development Rational Functional Tester Licensing Windows 7.0 Software Development Rational Manual Tester Licensing Windows 7.0 Software Development Rational Modeling Extension for Microsoft .NET Licensing Windows 7.0 Software Development Rational Performance Tester Licensing Windows 7.0 Software Development Rational Software Modeler Licensing Windows 7.0 Software Development Rational Systems Developer Licensing Windows 7.0 Data & Information Management Rational Data Architect Licensing 7.0 Software Development Rational Method Composer Licensing Windows 7.2", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q012", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Clear instructions to change Host Key.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q012", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Instructions on the info center were a but unclear", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q012", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "A) Use the following command to create a new host key:\n\n[root@nzhost1 nz]# /nz/kit/bin/adm/nzkey generate -hostkey -file /export/home/nz/hostkey.txt\nHost key written to file\n\nThe command creates saves the key in the specified file in plaintext.\nYou can then specify the host or key file as part of an nzkey change operation.\n\nImportant: The key files are in plain text and unencrypted. After you use the files to change the key for the hosts or SPUs, make sure that you delete the generated key files to protect the keys from being read\nby users who log in to the NPS system.\n\nB) Backup keystore\n\nTo create a key store backup file:\n\n[root@nzhost-h1 ~]# /nz/kit/bin/adm/nzkeybackup /nz/var/keybackup.tar.gz\n\nKeystore archive /nz/var/keybackup.tar.gz written\n\nCopy this file somewhere safe in case a restore is needed. You may also delete this once copy is completed.\n\nC) To change the host AEK, the NPS system must be in the Stopped state. The new AEK takes effect on both hosts when the nzkey command finishes running successfully. The command creates a backup copy of the current keystore before it changes the key. After the change is finished, you should create a backup of the new keystore using the nzkeybackup command.\n\n1. Log in to the active host of the NPS system as the nz user.\n\n2. Transition the system to the Stopped state, for example:\n[nz@nzhost1 ~]$ nzsystem stop\n\n3. Run the nzstate command to confirm that the system is in the Stopped state.\n\n4. Log in as the root user:\n\n[nz@nzhost1 ~]$ su - root\n\n5. Use the nzkey change command to change the host key:\n\n[root@nzhost-h1 ~] /nz/kit/bin/adm/nzkey change -hostkey -file\n/export/home/nz/hostkey.txt -backupdir /nz/var/backups/\n\n# Keystore archive /nz/var/backups/keydb_20140711054140.tar.gz written\n\nAEK Summary\n\nResult: Key operation completed successfully.\n\n6. Create a backup of the updated keystore:\n[root@nzhost-h1 ~] /nz/kit/bin/adm/nzkeybackup /nz/var/keybackup.tar.gz Keystore archive /nz/var/keybackup.tar.gz written\n\n7. Log out of the root account and return to the nz account.\n\n8. Run the nzstart command to return the system to the Online state.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q012", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "After they key is successfully applied, move the /nz/var/keybackup.tar.gz to a secure location away from the appliance so that you have a backup available for disaster recovery of the keystore. You should lso delete the host key file (/export/home/nz/hostkey.txt in this example) as a security precaution for someone finding your authentication key outside the protected keystore.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q012", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "nzudxcompile command returns an \"Argument list too long\" error and aborts.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q012", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "ARG_MAX configuration parameter limits the number of argument list in command line. In this case the client used more than 131072 argument with many program *.c files.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q012", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Check ARG_MAX value in the command line:\n\n$ getconf ARG_MAX\n131072", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q012", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "This ARG_MAX kernel parameter adjusted to much larger from kernel release version 2.6.23, that is 2621440 (http://www.in-ulm.de/~mascheck/various/argmax [http://www.in-ulm.de/~mascheck/various/argmax]).\n\nBut we support upto Redhat 5.11 in Twinfin which is less than kernel release 2.6.23. So we have no way to allow ARG_MAX larger than 131072 at this time.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q012", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Grooming takes time and resources hence to work more efficiently you chose to groom tables differently depending if they are CBT or non-CBT. For CBT (clustered base tables) you use the /nz/kit/bin/adm/tools/cbts_needing_groom script. But for non-CBT?", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q012", "section_id": 1, "heading": "ENVIRONMENT", "parent": null, "text": "IBM PureData System for Analytics", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q012", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "CBT tables are listed in the _V_TABLE_ORGANIZE_COLUMN view. You can join the _V_TABLE with _V_TABLE_ORGANIZE_COLUMN to get the list of CBT vs NON-CBT, for example:\n\nselect a.objid, tablename, schema, nvl2(b.objid, 'CBT', 'NON-CBT') CBT_TABLE\nfrom _V_TABLE a LEFT JOIN (select distinct objid from _V_TABLE_ORGANIZE_COLUMN) b\non a.objid = b.objid\n\nYou can use the below SQL to identify Non-CBTs and pass it as an input to the nz_groom command using the \"-in\" option:\n\nselect tablename from _v_table where objid NOT IN (select objid from _v_table_organize_column);\n\nWith nz_groom -scan command:\n\n[nz@xyz2 ~]$ export TEST_DB_NAME=TESTDB;\n[nz@xyz2 ~]$ nz_groom $TEST_DB_NAME -scan -in `nzsql -d $TEST_DB_NAME -A -t -c \"select tablename from _v_table where objid NOT IN (select objid from _v_table_organize_column) and objtype = 'TABLE';\"`\n\nWith the -scan/-records arguments, you can use -rows, -percent and -size to define thresholds. For instance to show Non-CBT tables with >= 1M reclaimable rows, you can use the below:\n\n[nz@xyz2 ~]$ nz_groom $TEST_DB_NAME -scan -rows 1000000 -in `nzsql -d $TEST_DB_NAME -A -t -c \"select tablename from _v_table where objid NOT IN (select objid from _v_table_organize_column) and objtype = 'TABLE';\"`\n\nPlease lookup \"nz_groom --help\" for syntax and other usage options.\n\nFor CBTs, use the cbts_needing_groom script, or just use objid IN in the above SQL to generate the list of CBTs.\n\nPRODUCT ALIAS/SYNONYM\n pda netezza\n\n0403-027 The parameter list is too long; SecureMain; KCI1343E; 0403-027 TROUBLESHOOTING\n\nPROBLEM\nAgent install fails during secureMain step and generates an error - /usr/bin/chmod: 0403-027 The parameter list is too long", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q012", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The itmsecure_.log shows the below error\n\n/Tivoli/itm/bin/secureLock[134]: /usr/bin/chmod: 0403-027 The parameter list is too long.\nKCI1343E secureMain completed with errors. For more information, check the log file /Tivoli/itm/logs/itmsecure_062012135428.log.", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q012", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The real cause for this error is:\n\nThe system has exceeded the AIX ARG_MAX value: 0403-027 The parameter list is too long. This AIX value can be increased with smitty.\n\nThe maximum size, in 4KB blocks, that the ARG/ENV list is allowed when running exec subroutines. This prevents exec subroutines from failing if the argument list is too long. You can specify a value in the range of 6 through 1024. The default value is 6. Specifying a higher value may constrain system memory resources. This change takes affect immediately and is preserved over boot.\"", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q012", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "Any AIX system", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q012", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To resolve the issue increase the ARG_MAX value\nTo check the value use the below command :\n\nlsattr -E -l sys0 -a ncargs\n\nTo change the value use the below command. You can change the value to 32, or increase to few more than the original value.\n\nchdev -l sys0 -a ncargs='32' (default is 6)", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q012", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Through \"Query->Execute with SPU utilization monitor\" menu from Aginity, clients can run SQL statement while checking SPU utilization. At this time Aginity requires host credential to run /nz/kit/bin/adm/nzsqa command on Netezza host.\nClient users should logon one designated host user other than \"nz\" user at this time to protect \"nz\" user credential from many clients.\nHow can we make other user than \"nz\" run /nz/kit/bin/adm/nzsqa?", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q012", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "nzsqa command has a permission 700, so only \"nz\" user can run this command successfully. To run nzsqa successfully from other user than \"nz\" and other group than \"nz\", nzsqa file's permission needs to be changed to 4705 to set effective user id for nzsqa file.", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q012", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "We can create a host user with any group name other than \"nz\" group and then change nzsqa binary's file permission as below:\n\n[nz] $ chmod 4705 /nz/kit/bin/adm/nzsqa\n\nThe steps for this are below:\n\n[root] # useradd -G nobody monuser\n\n[root] # passwd monuser\nChanging password for user dummyuser.\nNew password:\nRetype new password:\npasswd: all authentication tokens updated successfully.\n\n[monuser] $ /nz/kit/bin/adm/nzsqa", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q100", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "For Problem Determination of ITCAM for Agent Data Power, what logs are required ?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q100", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Information required for ITCAM Agent for Data Power problem determination.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q100", "section_id": 2, "heading": "ANSWER", "parent": null, "text": "Please provide following from each environment that is experiencing the problem :\n\n 1. Platform and version number.\n2. MachineType and Appliance Firmware level.\n3. The result of following command from '/bin' directory\nfrom all the machines (Agent, ITM product) related to this issue.\n\"cinfo -i\" from UNIX platform\n\"kincinfo -i\" from Windows platform\n4. Detailed description of problem and STEP BY STEP problem recreation senario.\n(Messages and other information displaced in screen)\n5. If System stops on UNIX system, zip up the core dumps from Agent for DP installed machine\nat /bin directory.\n6. Helpful screenshots if appropriate.\n7. Export of \"SNMP Settings\" on the device.\n\n8. Logs/config files - Please send following information from Agent for DP installed machine,\nAgent Log - Output of /bin/pdcollect\nZip up the Agent Configuration files as below Logs Type Location of logs. Agent Config files * Windows :\n \\TMAITM6\\*.cfg\nUnix/Linux :\n /config/*.cfg\n\n SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q100", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Problem Description :\n\nThe MIB of v4.0.2.0 indicates that\n dpStatusSystemUsageTableTable is obsoleted.\n\ndpStatusSystemUsageTableTable OBJECT-TYPE\n SYNTAX SEQUENCE OF DPStatusSystemUsageTableEntry\n MAX-ACCESS not-accessible\n STATUS obsolete\n DESCRIPTION\n \"Component level system usage.\n Note: this is obsoleted and is replaced by\n dpStatusSystemUsage2Table as of release 4.0.1\"\n\n::= { dpStatus 201 }\n\nITCAM Agent for WebSphere DataPower Appliance v6.3 requests\n component level system usage from OID\n 1.3.6.1.4.1.14685.3.1.201.1.1-6.\n This is obsoleted starting from firmware v4.0.1 released June\n 30,2011. From firmware v4.0.1, there is no data returned for\n these OIDs from the DataPower device.\n\nBecause of this..\n the \"Performance Object Status\" workspace showed Error Code \"NO\n INSTANCE RETURNED\" of the SystemUsageTable attribute group.\n\nApprover : ZW", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q100", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "The problem was fixed on version 7.1 per Hong Liang@BN L3", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q100", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Need to close this Apar, cause the problem resolved in V7.1\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q100", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV09557\nREPORTED COMPONENT NAME\n ITCAM SOA PLAT\nREPORTED COMPONENT ID\n 5724V0700\nREPORTED RELEASE\n 620\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n YesSpecatt / New Function\nSUBMITTED DATE\n 2011-10-24\nCLOSED DATE\n 2014-06-09\nLAST MODIFIED DATE\n 2014-06-09\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q100", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n ITCAM SOA PLAT\nFIXED COMPONENT ID\n 5724V0700", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q100", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R710 PSY\n UP", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q100", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "Is there a way to use TCR Reporting for the BN DataPower agent?", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q100", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "Currently as of 1H2015, there is no TCR Template available for the BN DataPower agent (v7.01 FP1). So, if you are looking to download a TCR template for this agent, you will not find any on Passport Advantage. There is an open RFE out on the RFE website which documents this requirement.\n\nThe RFE link is:\nhttp://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=68440 [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=68440]\n\nSo, if you want to use TCR for the DataPower agent, you have to Custom reporting inside of TCR itself.\n\nPRODUCT ALIAS/SYNONYM\n ITCAM ITCAM for DataPower agent", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q100", "section_id": 2, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "7.1.0.3-TIV-ITCAMAD-IF0005: ITCAM for Application Diagnostics V7.1 FP3 IF5 [http://www-01.ibm.com/support/docview.wss?uid=swg24033938]\n7.1.0.3-TIV-ITCAMAD-IF0004: ITCAM for Application Diagnostics V7.1 FP3 IF6 [http://www-01.ibm.com/support/docview.wss?uid=swg24034668]\n7.1.0.3-TIV-ITCAMAD-IF0008: ITCAM for Application Diagnostics V7.1 FP3 IF8 [http://www-01.ibm.com/support/docview.wss?uid=swg24037994]\n7.1.0-TIV-ITCAMAD-FP0004: ITCAM for Application Diagnostics V7.1 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24041705]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q100", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Users Affected:\n User of Agent for WebSphere in ITCAM for WebSphere V6.2 or\n ITCAM for Application Diagnostics 7.1 who set\n CTIRA_SUBSYSTEM_ID in ITM agent configuration file (yn.ini)\n\nProblem Description:\n TEP workspaces are blank on agent level (for example\n Application Server Status workspace). This happens when\n value of CTIRA_SUBSYSTEM_ID property in yn.ini is different\n than agent node id set in agent configuration file\n (/config/_yn.cfg or\n /config/_yn.xml).", "logical_doc_id": 3, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q100", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Local Fix/Workaround:\n Reconfigure agent to have exactly same node id\n as value in CTIRA_SUBSYSTEM_ID. Or manually set it\n in following files:\nfor 6.2 release: KYN_ALT_NODEID property in\n /config/_yn.cfg file\nfor 7.1 release: value in tag in\n /config/_yn.xml file to new value\n vrt0085 ).\n\nRestart the agent and verify TEP workspaces.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q100", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Agent for WebSphere in ITCAM for WebSphere\nV6.2 and ITCAM for Application Diagnostics 7.1 users who\nset CTIRA_SUBSYSTEM_ID in agent configuration file.\n\nPROBLEM DESCRIPTION:\nTEP workspaces are blank on agent level (for example\nApplication Server Status workspace). This happens when value\nof CTIRA_SUBSYSTEM_ID property in yn.ini is different than\nagent node id set in agent configuration file:\nv6.2: /config/_yn.cfg,\nv7.1: /config/_yn.xml.\n\nRECOMMENDATION: Use ITCAM for WebSphere 6.2 FP6, Interim\nFix 1, TEMA (6.2.0.6-TIV-ITCAM_WAS_TEMA-IF001) or newer\nrelease which contains this fix to resolve this issue.", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q100", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Setting CTIRA_SUBSYSTEM_ID causes registration on TEMS under\n Managed System Name like: ::KYNA.\n However, TEMA has it's own setting for agent ID called\n 'Alternative Node ID' which is stored in\n /config/_yn.cfg or\n /config/_yn.xml files. This value is\n used to build internal identification similar to Managed System\n Name.\n When CTIRA_SUBSYSTEM_ID is different than 'Alternative Node ID'\n then TEMA drops request from ITM as those request are for agent\n with CTIRA_SUBSYSTEM_ID name and TEMA identifies it's name as\n value of 'Alternative Node ID'.\n\nThe fix for this APAR introduces the precedence of agent node ID\n configurations. If CTIRA_SUBSYSTEM_ID value is present in\n /config/yn.ini file then it overrides value of\n 'Alternative Node ID'.\n\nThe fix for this APAR is contained in the following maintenance\n packages:\n\n| interim fix | 6.2.0.6-TIV-ITCAM_WAS_TEMA-IF001\n | interim fix | 7.1.0.3-TIV-ITCAMAD-IF0005\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q100", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM73305\nREPORTED COMPONENT NAME\n ITCAM WAS DIST\nREPORTED COMPONENT ID\n 5724L6200\nREPORTED RELEASE\n 610\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2012-09-20\nCLOSED DATE\n 2012-11-30\nLAST MODIFIED DATE\n 2012-11-30\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q100", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n ITCAM WAS DIST\nFIXED COMPONENT ID\n 5724L6200", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q100", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R610 PSY\n UP\nR710 PSY\n UP", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q100", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "For the installation of the following components:\nData Collector (FMID HAAD710);\nITCAM Common Services (FMID HAAD71C);\nMonitoring Agent (FMID HKYN710);\nthe Program Directory names are incorrectly referenced in the ITCAM Agent for WebSphere Applications Installation Guide for z/OS.\n\nThe installation for all of these components is covered in the following Program Directory:\nProgram Directory for IBM Tivoli Composite Application Manager (ITCAM) for Application Diagnostics on z/OS V7.1", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q271", "section_id": 0, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "While displaying a quarter/year format for the variable, SPSS/PASW Statistics is actually working with the actual date value. In this case the date values of 8/11/2001 and 8/12/2001 have the same MOYR value, but their internal values different. As a result, SPSS will create a separate row or column for these values.\n\nHere is an example of how we can create a variable (in this instance, from an existing date variable called MONTH) that has a true MOYR format:\n\nCOMPUTE mnth=date.moyr (xdate.month(month),xdate.year(month)).\nEXECUTE.\nFORMATS mnth (MOYR6).\n\nHere we pull the month value and the year value from the existing MONTH variable, and combine them using the DATE.MOYR function. Next we use the FORMATS command to display a true MOYR format. Then, we can run our CROSSTABS procedure using the new MNTH variable and see one row or column for each unique value", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q271", "section_id": 1, "heading": "RELATED INFORMATION", "parent": null, "text": "Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\n\nHISTORICAL NUMBER\n 20074\n\nDOWNLOADABLE FILES", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q271", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This document contains information about obtaining Parascript FieldScript for IBM Datacap Taskmaster Capture Versions 8.0.1 and 8.1.0, and for IBM Datacap Version 9.0.0.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q271", "section_id": 1, "heading": "DOWNLOAD DESCRIPTION", "parent": null, "text": "Parascript FieldScript for IBM Datacap Versions 8.0.1, 8.1.0, and 9.0.0, and the associated data disk that contains the United States Postal Service (USPS) database are available for download only through Passport Advantage.\n\nThe address information in the USPS database on the data disk is automatically disabled 105 days after the date of issue. IBM refreshes the data disk on the 14th day of every month, or the previous business day. You must ensure that you obtain the refreshed data from Passport Advantage on a regular schedule so that you avoid issues that are associated with disabled address information.\n\nPREREQUISITES\nSee the following website for detailed system requirements.\n\nURL LANGUAGE SIZE(Bytes) Hardware and software requirements [http://www.ibm.com/support/docview.wss?uid=swg27043811] English 15234\nINSTALLATION INSTRUCTIONS\nSee the Parascript(R) FieldScript(R) for IBM Datacap Taskmaster Capture Version 8.0.1 Guide for installation instructions.\n\nClick on the other links for related information.\n\nURL LANGUAGE SIZE(Bytes) Parascript FieldScript for Taskmaster Guide [http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss?CTY=US&FNC=SRX&PBL=GC19-3374-00] English 55555 IBM Datacap Publication Library [http://www.ibm.com/support/docview.wss?uid=swg27043856] English 1000 Parascript FieldScript with Datacap V8.1.0 & V9.0.0 [http://www.ibm.com/support/docview.wss?uid=swg27035840] English 1000\nDOWNLOAD PACKAGE\nTo download Parascript FieldScript, sign in to Passport Advantage [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm] by using your IBM ID. If you are not a returning customer or you do not have an IBM ID, you can register to obtain an IBM ID.\n\nAfter you sign in to Passport Advantage, you can select the software to which you are entitled to download.\n\nClick the HTTP link to go to the Passport Advantage Online website.\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options Passport Advantage Online 16 Dec 2011 English 1024 HTTP [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\nTECHNICAL SUPPORT\n Passport Advantage Online support:\nhttps://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html [https://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html]\n\nIBM Datacap Taskmaster Capture V8.0.1 and V8.1.0 support: http://www.ibm.com/support/entry/portal/Overview/Software/Information_Management/Datacap_Taskmaster_Capture [http://www.ibm.com/support/entry/portal/Overview/Software/Information_Management/Datacap_Taskmaster_Capture]\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Datacap Taskmaster Capture\n\nRELEASE NOTES", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q271", "section_id": 2, "heading": "ABSTRACT", "parent": null, "text": "You must modify the header information in the ICR_P.rrx file to run Parascript V8.0.1 with Datacap Taskmaster Capture V8.1.0 or Datacap V9.0.0.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q271", "section_id": 3, "heading": "CONTENT", "parent": null, "text": "After you install Parascript FieldScript V8.0.1, you must edit the ICR_P.rrx file to run the product with Datacap Taskmaster Capture V8.1.0 or Datacap V9.0.0:\n\n1. Navigate to the \\RRS directory and open the ICR_P.rrx file with a text editor.\n 2. In the header information of the RRX file, replace instances of rrunner.rrx with rrunner.\n 3. Replace instances of recog_shared.rrx with recog_shared.\n 4. Save and close the file.\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Datacap Taskmaster Capture\n\nlste_webcast; STEwebcastDocument WEBCAST", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q271", "section_id": 4, "heading": "ABSTRACT", "parent": null, "text": "Listen to this replay as members of the IBM Connections team share information on Upgrading to IBM Connections 5.0.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q271", "section_id": 5, "heading": "CONTENT", "parent": null, "text": "Topic: Upgrading to IBM Connections 5.0\nDate recorded: Wednesday, January 14, 2015\n\nPresentation OpenMic_UpgradeConn_011415.pdf [/support/docview.wss?uid=swg27044439&aid=2]OpenMic_UpgradeConn_011415.pdf [/support/docview.wss?uid=swg27044439&aid=1]\n\nAudio recording\nUpgrading to IBM Connections 5.0 Open Mic Jan 14 2015.mp3 [/support/docview.wss?uid=swg27044439&aid=4]Upgrading to IBM Connections 5.0 Open Mic Jan 14 2015.mp3 [/support/docview.wss?uid=swg27044439&aid=3]\n\nVideo recording\nA section of the session was created as a video. This 2-min video describes the deployment options available when upgrading to IBM Connections 5.0. The video can be found on the ICS Support Videos YouTube channel:\nhttps://youtu.be/boLdka6n8Dw [https://youtu.be/boLdka6n8Dw]\n\nThis 7-min video provides an overview of the External User Collaboration model, including what users see, the features available to them and the configuration needed to enable this on your platform:\nhttps://youtu.be/isyIThwKBPI [https://youtu.be/isyIThwKBPI]\n\nQ&A summary\nAudio recording (length 54:45 minutes)\n\nApproximate time stamp Topic 00:00 Presentation of slides 48:06 Question: After a server restart, the applications start but the servlets do not until the first request comes in. This behavior is slowing down the performance for the first user. Is there a way to resolve this behavior?\n\nAnswer: No, there does not appear to be a way to pre-load the servlets you are using. There are some settings in the web.xml that are to pre-load the servlets but not applying in this case. Support is researching your question and will share what we find through your PMR. 49:36 To use the doc viewer plugin for Connections, do we need to install all IBM Docs pieces?\n\nNo, you do not need all of IBM Docs. There are six Docs components. If you will only use file viewer, all you need is three of those components: file viewer application server, the conversion application server, and file viewer plug-in. 50:26 For surveys and polls, is it a widget or do I run a task for setup?", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q271", "section_id": 5, "heading": "CONTENT", "parent": null, "text": "Surveys is a widget, working with IBM Forms Experience Builder. To use, you first install and set up Forms Experience Builder. To integrate the two, you update the widgetconfig.xml file on the Connections community server and add jar files on the Forms server to allow the two-way communication. When you create a survey widget in a Community, that action creates a form on the Forms server and assigns that community to the form. Refer to the slides in the presentation above for details. 52:55 I do not see an editor, like the EditLive rich text editor, for the community description. Is this function coming in a future release?\n\nThe text limit for the description is configurable; see the product documentation. As far as rich text editing, we're not aware of plans at this time but that feature has been requested.\nWeb Conference chat\n\nWhat are CCM and Ephox? CCM = Connections Content Manager. It's our integration of Connections and FileNet with the library widget in Communities. Ephox is Ephox Edit Live. It's a new full feature text editor used in blogs, wiki's, etc. Is IBM Docs (Doc viewer) a separate installation? And this viewer has use only during the document preview in activity stream, right? Docs and Docs File Viewer is a separate install. File viewer is used in document preview, the new thumbnail view in Files and Activity Stream. IBM Docs gives you the ability to create documents, spreadsheets and presentation online as well as edit those in a group setting, all online.", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q271", "section_id": 5, "heading": "CONTENT", "parent": null, "text": "During the presentation, you mention files and CCM go in File system and Databases separately. We have both Files and CCM components. How is that stored? In both cases we store the actual file on the network share drive. In the DB, we store the meta-data, filename and location the file exists on the file store. Has any sizable environment ever done an in-place upgrade? One support panelist has seen a couple but most sizable environments are done side-by-side. Can we migrate from V3 to V5? You run the DB upgrade scripts from 3.0 to 4.0, then the upgrade scripts from 4.0 to 5.0. You would not need to install a 4.0 Connections server, just a 5.0 server that you will migrate the 3.0 - 4.0 - 5.0 data to. How about the compatibility of the Ephox RTE within newer versions of Java? Are those warnings and applet-based packaging being used in this Ephox? EditLive is only supported for Java 1.6 & 1.7 Besides the IBM documentation, anyone have a guide to do a side-by-side upgrade? Is there a zero-to-hero guide for version 5? There is an informative blog written by one of our IBM champions: http://turtleblog.info/2014/09/30/my-connections-migration-checklist/ [http://turtleblog.info/2014/09/30/my-connections-migration-checklist/] No zero-to-hero guide exists for 5.0; prior versions are in the IBM Connections wiki. The panelists noted this request and will look into publishing a similar guide for 5.0.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q271", "section_id": 5, "heading": "CONTENT", "parent": null, "text": "We have issues installing Cognos on Linux cluster environment. Have you installed successfully? Yes, I have installed Cognos successfully. It's easier in 5.0 because there is a wizard now. Typically the issues I see are problems getting the metrics running, due to the 32-bit Oracle or DB2 client not being installed. When installing Cognos transformer, we are getting \"Segmentation Fault\" error running build-all.sh. We have 32 and 64 bit libraries. That sounds like a problem with the db client. You can go to /cognos/servlet/dispatch/ext, and navigate to the DB configurations and make sure we are able to connect to the db via the client and JDBC drivers. It may be best to open a service request to troubleshoot further. Is the Quickr Plug-in still required for Round-Trip Editing? The desktop plugins will allow you to do round trip editing; the documentation will be updated for this soon. Is it required to edit the files_config.xml for round trip editing to work with the Desktop Plugin and not use the quickr plugin? The file to edit is library-config.xml. That feature may not be completely ready yet with CR1, but is expected, along with documentation updates, for CR2. Round trip editing works with CR1 as long as you have updated the library plugin. About Open Mic Webcasts IBM Collaboration Solutions Support wants to help you take full advantage of your products. Join us for our Open Mic Webcast series as technical experts share their knowledge and answer your questions. These webcasts are designed to address specific topics and provide an in-depth and focused technical exchange in a convenient online webcast format. For more information about our Open Mic webcasts, visit the IBM Collaboration Solutions Support Open Mics [http://www.ibm.com/software/lotus/support/lotus-open-mics/] page.\n\nORIGINAL PUBLICATION DATE\n 2014/12/8\n\nlste_webcast; STEwebcastDocument WEBCAST", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q271", "section_id": 6, "heading": "ABSTRACT", "parent": null, "text": "IBM hosted an Open Mic Webcast on June 4, 2014. The topic was \"Fixing Unread Marks.\" Amy Knox gave a very informative presentation and she was joined by Tim Southgate and several other members of the Domino Support and Development teams for Q&A.", "logical_doc_id": 1, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q271", "section_id": 7, "heading": "CONTENT", "parent": null, "text": "Presentation FixingUnreadMarks_June4.pdf [/support/docview.wss?uid=swg27042034&aid=2]FixingUnreadMarks_June4.pdf [/support/docview.wss?uid=swg27042034&aid=1]\n\nAudio Replay\nFixing Unread Marks - Open Mic - 04 June 2014 (edited).mp3 [/support/docview.wss?uid=swg27042034&aid=4]Fixing Unread Marks - Open Mic - 04 June 2014 (edited).mp3 [/support/docview.wss?uid=swg27042034&aid=3]\n75 minutes long\nQ&A starts at 46:52\n\nRecommended Resources * Enabling syncing of read or unread changes [http://www-10.lotus.com/ldd/dominowiki.nsf/xpDocViewer.xsp?lookupName=Administering+IBM+Notes+Traveler+9.0.1#action=openDocument&res_title=Enabling_syncing_of_read_or_unread_changes_A901&content=pdcontent]\nApple limitations and restrictions [http://www-10.lotus.com/ldd/dominowiki.nsf/xpDocViewer.xsp?lookupName=Using+IBM+Notes+Traveler+9.0.1#action=openDocument&res_title=Apple_limitations_and_restrictions_U901&content=pdcontent]\nNotes Traveler - Read/ Unread Marks Synchronization [http://www-01.ibm.com/support/docview.wss?uid=swg21666362]\nThe Architecture of Unread Marks in Lotus Notes [http://www-01.ibm.com/support/docview.wss?uid=swg27002920]\nThe enhanced unread functionality in Notes/Domino [http://www-01.ibm.com/support/docview.wss?uid=swg21140018]\nOpen Mic - Troubleshooting & Best Practices for Read/Unread Marks (Feb 2012) [http://www-01.ibm.com/support/docview.wss?uid=swg21588524]\nOpen Mic Replay and Q&A: Understanding and Troubleshooting Unread Marks in Notes/Domino (Jan 2012) [http://www-01.ibm.com/support/docview.wss?uid=swg27023614]\n\nQ&A\n\nQ1. What defines a real large database? I have an MMR user with 2.5 GB mail file does this qualify as \"really large\"?\nThere is no hard number since the specific net/system performance characteristics affect this. I would take it as something to be aware of if there are application databases that are significantly larger than a typical mail file. And something that might need to be analyzed on these databases if there are performance issues.\n\nQ2a. Since changing iNotes auth from Domino to AD, iNotes unread status is out of sync. Why, and is there a fix for that?\nUnread marks are per user. Using a new credential name will create a new unread mark table.\n\nQb. We reference the user's Domino name in a field in their AD account. Have not added the user's AD to our ACL. So it should be the same user, no? * It was my first idea. I recommend to use the IBM tool to review the unread table.\nMaybe look to name mapping the AD folks to the Domino name so that the distinguished name Domino treats the user as is consistent to who they were known as before\n\nQ3. In the iNotes issue, re bad user. What would happen with the user profile in iNotes (guess it would mismatch)?\nYou'd have a different unread table for the mail file owner than the user logging in with delegate access.", "logical_doc_id": 1, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q271", "section_id": 7, "heading": "CONTENT", "parent": null, "text": "Q4. You indicated there is a log in the cache.ndk file. So what happens if a user shuts down Notes, deletes their cache.ndk file and other things because they're trying to get something working again. What happens with the unread marks at that point? When they start up and it builds a new cache. * To my knowledge, the replication of the unreads via the newer activity unread log, which is what gets created when you enable replication of the unreads. That should be able to handle that properly. There's been some discussion of apparently some shortcomings when you either move replicas or when you move the cache on the client. It's not clear to me what all the issues are there. Without specific cases and without it a reproducible scenario, it's hard for me to answer that specifically.\nTechnically when you create a new replica, part of the replication is to replicate across the Activity log. When you have replication enabled on the .nsf. I'm more accustomed working on it from server to server and that generally works. I'm not sure how the client interacts with it that could interfere with that at this point without having a specific problem to understand.", "logical_doc_id": 1, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q271", "section_id": 7, "heading": "CONTENT", "parent": null, "text": "Q5. State of the Activity log is dependent on the client time stamps. How far out of sync in time can the Notes desktop be with the server and still have things work correctly? Person's desktop is 10 minutes ahead or behind the server time. How much time difference is going to cause a problem? * It should be able to get the deltas based on which server it is replicating with and pick up the new activity since then. It should be based on where you're pulling from relative to the replication history for that specific source and destination. It shouldn't interfere with different source and destination time. If there is an issue there I'm not aware of it.\nIf the client was behind, I don't think that would be as bad as if the client was ahead. If the client was 30 minutes ahead, it wouldn't be able to sync - the time stamps would be wrong. Eventually it would catch up. If the client was ahead and time stamped documents 30 minutes ahead, eventually the replication task is going to see that and pick it all up. I think it's only a matter if we're saying 3 months ahead, then it's going to take 3 months for that to catch up.\n\nQ6. We have a customer who is geographically dispersed. We're considering using extended administration servers. In your presentation you mentioned the AdminP ini parameter. Where you have these extended administration servers (in various regions around the world), would you place that parameter on each one of those extended administration servers, in order for replication in that region to work as you described?\nYes, I definitely would. Put it on any server that's going to initiate the new replica.", "logical_doc_id": 1, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q271", "section_id": 7, "heading": "CONTENT", "parent": null, "text": "Q7a. Question about the in-house tools that only IBM has access to. Why is that? I'm inclined frankly to skip over all of the troubleshooting and immediately open a PMR and troubleshoot with those tools. and use other information to supplement IBM's information to get a resolution when the problem is involved. So I'm wondering why we can't have those tools and what your thoughts are on that process? Should we be going to IBM right away for quick expedited resolution? That's a really great question. From my perspective, I don't feel that I'm allowed to send out a tool that is listed as internal. I think the tool dump unread is useful. I don't know the reasons why it's not publicly available at this time and I actually hesitated to put it in this presentation. You bring up a great point. Why not just skip all that and open a PMR and run the Unread Tool and see. The thing is that not all the issues have to do with the Unread table being incorrect. But what can help is maybe I have a renamed user or maybe I had two different user names (Joe User is Joe A User at the same time) . So I could see that information. It's only going to give me a subset of information. Generally with internal tools, first of all they haven't gone through quality assurance so we can't release them from the perspective of there's risk involved and the tools haven't been properly tested, and how are users supposed to use them, and if they are allowed to use them under specific circumstances there could be a set of switches or features in those tools that could lead to higher risk. And the other issues are if they are used incorrectly or overly used, they could cause either performance problems or loss of data or things of that nature. So basically the tool hasn't been productized in a way that users could use them in a friendly fashion and not get themselves in trouble, or we're just not sure. Also, it's not part of the product, it's not a feature so there are some legal reasons behind that too..", "logical_doc_id": 1, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q271", "section_id": 7, "heading": "CONTENT", "parent": null, "text": "But if there are tools that are useful to you that you really think should be part of the product, please push so they can be made part of the product. If there's good reason to promote an internal tool to be something that's used for a lot of problem resolution, it'll save you time and money, as far as the development staff is concerned there can be some good motivations to either incorporate that into another tool/utility or promote the tool itself to be more available. Follow-up comment from IBM client:\n*\n*\n*\nFollow-up comment from IBM developer:\n*\nQ8. How many documents can a database handle? * There's not really a document limit, it's more of a hard data limit. The maximum size of any Notes/Domino database is 64GB. You could have one document with a 63GB attachment or you could have millions of (small) documents. Not related to total number of documents in a database but more so the nature of how they are going to affect things like ID tables which are used to represent things like Unreads and Searches. What could happen is that you could hit a soft limit way before the hard limit of databases due to the way we compress and store ID tables.", "logical_doc_id": 1, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q271", "section_id": 7, "heading": "CONTENT", "parent": null, "text": "About Open Mic Webcasts IBM Collaboration Solutions (Lotus) Support wants to help you take full advantage of your products. Join us for our Open Mic Webcast series as technical experts share their knowledge and answer your questions. These webcasts are designed to address specific topics and provide an in-depth and focused technical exchange in a convenient online webcast format. For more information about our Open Mic webcasts, visit the IBM Collaboration Solutions Support Open Mics [http://www.ibm.com/software/lotus/support/lotus-open-mics/] page.\n\nORIGINAL PUBLICATION DATE\n 2014/5/13", "logical_doc_id": 1, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q238", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Secondary ImpactServer fails to start, configuration not fully copied from Primary ImpactServer to Secondary file system.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q238", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The PolicyList file:\n\n$NCHOME/impact/etc/policylist\n\nwas corrupted with missing entries and missing properties for the existing entries.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q238", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "Example log file trail building up to the issue:\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\n*\nIn this instance the last thing it is attempting to replicate is the PolicyList.", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q238", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "For this example - rebuild the PolicyList [link below].\n\nPerform these actions as the user used to install and run Impact:\n*\n*\n $NCHOME/bin/ewas.sh stop -user wasadmin -password netcool\n*\n*\n* $NCHOME/impact/etc/NCI1_policylist\n*\n*\n$NCHOME/impact/etc/NCI1_policylist.orig\n*\n*\n*\n* $NCHOME/impact/etc/NCI1_policylist\n*\n*\n$NCHOME/impact/install/nci_startsvn $NCHOME/platform/[Arch]/svn/bin $NCHOME/platform/[Arch]/svn/repository\n*\n*\n$NCHOME/impact/install/nci_addsvn NCI1 $NCHOME/platform/[Arch]/svn/bin $NCHOME/platform/[Arch]/svn/repository\n*\n*\n$NCHOME/bin/ewas.sh start\n*\n*\n*\n*", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q238", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "#Rebuilding PolicyList file by hand [https://www.ibm.com/support/docview.wss?uid=swg21507893]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q238", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Impact Cluster is configured with 4 Impact Servers installed\n over 4 Linux servers. When all four Impact Servers are started,\n each server can be accessed by the web admin tool, and each\n server correctly points to IMP_A as the primary server.\n\nHowever, when IMP_A is stopped, the other 3 servers fail to\n select a new primary, and instead still point to IMP_A as the\n primary.\n\nI have repeated this test many times, and once they correctly\n failed over, setting IMP_D as the primary, However when I\n stopped IMP_D, the remaining 2 servers continued to point to\n IMP_D as the primary.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q238", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Impact with 4 clsuter members configured result in last\n secondary server is not able to convert itself to be primary. As\n result, if all other 3 clusters are stopped, the 4th one will\n stay secondary and not processing events", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q238", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This issue is fixed in IBM Netcool/Impact 5.1.0.1 Interim Fix\n 0005 5.1.0.1-TIV-NCI-IF0005\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q238", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IZ80505\nREPORTED COMPONENT NAME\n NETCOOL/IMPACT\nREPORTED COMPONENT ID\n 5724O59IS\nREPORTED RELEASE\n 510\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2010-07-20\nCLOSED DATE\n 2010-08-27\nLAST MODIFIED DATE\n 2010-08-27\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q238", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n NETCOOL/IMPACT\nFIXED COMPONENT ID\n 5724O59IS", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q238", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R510 PSY\n UP\n\nz/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q238", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "In sites that have dual online logging enabled, the IMS log\n reader component will only attempt to access a secondary OLDS if\n an I/O error is reported for a primary OLDS. Depending on what\n kind of DASD these logs are stored on, attempts to read data\n from the active OLDS that IMS is currently writing data to can\n cause contention that impacts IMS operations.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q238", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: Data Replication for IMS *\nIBM InfoSphere Classic Change Data *\nCapture for z/OS for IMS *\n\nPROBLEM DESCRIPTION: In sites that have dual online *\nlogging enabled, the IMS log reader *\ncomponent will only attempt to access *\na secondary OLDS if an I/O error is *\nreported for a primary OLDS. *\nDepending on what kind of DASD these *\nlogs are stored on, attempts to read *\ndata from the active OLDS that IMS is *\ncurrently writing data to can cause *\ncontention that impacts IMS *\noperations. This is particularly true *\nwhen there are multiple address *\nspaces attempting to access the *\nsame log. *\n\nRECOMMENDATION: *\n\nA new OLDSPOLICY configuration parameter has been added that\n allows an administrator to identify whether the IMS log reader\n service should select secondary OLDS versus primary OLDS when\n dual logging is enabled for an IMS online subsystem.", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q238", "section_id": 4, "heading": "COMMENTS", "parent": null, "text": "A new OLDSPOLICY configuration parameter has been added that\n allows an administrator to identify whether the IMS log reader\n service should select secondary OLDS versus primary OLDS when\n dual logging is enabled for an IMS online subsystem.\n This new parameter also allows an administrator to identify\n whether the IMS log reader service should select an archive\n log versus an online log during stream activation processing.\n The following OLDSPOLICY options are available:\n 1) Use primary OLDS and select an online log if available\n during stream activation (default)\n 2) Use a secondary OLDS and select an online log if available\n during stream activation\n 3) Use primary OLDS and select an archive log if available\n during stream activation\n 4) Use a secondary OLDS and select an archive log if available\n during stream activation\n An update has been made to the OLDSPOLICY parameter to\n support this. The IBM Knowledge Center has been updated with\n the details for Version 11.3.\n See the link below:\n http://www-01.ibm.com/support/docview.wss?uid=swg27039728&wv=1 [http://www-01.ibm.com/support/docview.wss?uid=swg27039728&wv=1]", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q238", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI69792\nREPORTED COMPONENT NAME\n CLASSIC FED & E\nREPORTED COMPONENT ID\n 5697I8200\nREPORTED RELEASE\n B30\nSTATUS\n CLOSED UR1\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-09-27\nCLOSED DATE\n 2016-10-06\nLAST MODIFIED DATE\n 2016-11-02\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n UI41466\n\nMODULES/MACROS\nCECCBCFG CECCCNTL CECCDCFG CECCFGUT CECCLRFU CECCLRIC CECCLRID\n CECCLRIE CECCLRIH CECCLRII CECCLRIM CECCLRIQ CECCLRIR CECCLRIS\n CECCLRIT CECCLRSM CECCMTO CECMCFG1\n\nPublications Referenced SC19417400 FIX INFORMATION\nFIXED COMPONENT NAME\n CLASSIC FED & E\nFIXED COMPONENT ID\n 5697I8200", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q238", "section_id": 6, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "RB30 PSY UI41466 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI41466]\n UP16/10/08 P F610\n\nFIX IS AVAILABLE\nSELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL. YOU WILL BE REQUIRED TO SIGN IN. DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES.\n\nDIRECT LINKS TO FIXES\n7.1.0-TIV-NCI-SOLARIS-FP0013 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-SOLARIS-FP0013&source=SAR]\n7.1.0-TIV-NCI-WINDOWS-FP0013 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-WINDOWS-FP0013&source=SAR]\n7.1.0-TIV-NCI-ZLINUX-FP0013 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-ZLINUX-FP0013&source=SAR]\n7.1.0-TIV-NCI-LINUX-FP0013 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-LINUX-FP0013&source=SAR]\n7.1.0-TIV-NCI-AIX-FP0013 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Netcool+Impact&fixids=7.1.0-TIV-NCI-AIX-FP0013&source=SAR]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q238", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Product: IBM Tivoli Netcool/Impact\n Release: 7.1.0\n Severity: 3\n\nProblem Description: IBM Tivoli Netcool/Impact 7.1.0\n\nNeed to update the Impact documentation to include what is\n replicated in an Impact cluster.\n\nA user assumed that the running state of a service in\n Impact is replicated in a cluster environment. i.e.\n\n1) Manually stop a service on the primary.\n 2) Shutdown the primary.\n 3) Secondary takes over as the acting primary.\n\nNote: The service is set to automatically start on startup\n\n4) After the secondary starts up the running state of the\n service is started (running).\n\nThe user assumed if the service is stopped on the\n primary then when the secondary takes over as the acting\n primary the running state of the service on the secondary\n should also be stopped.", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q238", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Clarification regarding service status replication in a clusterh\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q238", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IJ02522\nREPORTED COMPONENT NAME\n NETCOOL/IMPACT\nREPORTED COMPONENT ID\n 5724O59IS\nREPORTED RELEASE\n 710\nSTATUS\n CLOSED DOC\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2017-12-08\nCLOSED DATE\n 2018-01-20\nLAST MODIFIED DATE\n 2018-01-20\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nPublications Referenced SC27492310 FIX INFORMATION", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q238", "section_id": 6, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q238", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Unlike events read by event readers, events processed by a\n policy launched by a policy activator are not processed by the\n event processor. The implication of that is that in a\n normally-functioning cluster, events processed via an activated\n policy will only ever be processed on the current primary\n server.\n\nThe Impact documentation should state this in order to avoid\n confusion.", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q238", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nAll Impact Users *\n\nPROBLEM DESCRIPTION: *\nQuestion re policy activator: Q: Why doesn't the policy *\nactivator run on the secondary cluster *\nmember? Can I do anything about it? *\n\nRECOMMENDATION: *\nIt's expected behaviour that policy activators run only on *\nthe primary. *\n*\nThe only service normally active on a secondary server in *\nthe cluster is the event processor. The event processor *\ndoes not handle *\nevents from policies activated by a policy activator, only *\nevents read from event reader queues. Therefore an event *\nprocessed via a policy activator will only ever be processed *\non the Impact server where the policy activator service is *\nrunning. *\n*\nThere is no way of configuring this to behave differently in *\nImpact itself currently. However, it is possible to *\nactivate a policy to run on the secondary by using a cron *\njob to run nci_trigger at intervals. But the risk with this *\napproach is that it will have no failover *\ncapability. Another idea is to put the policies inside an *\nevent reader of their own and set that event reader to have *\na very *\nlong polling interval - the same frequency as your policy *\nactivator. *", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q238", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Documentation will be updated with next Service Release\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q238", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV80943\nREPORTED COMPONENT NAME\n NETCOOL/IMPACT\nREPORTED COMPONENT ID\n 5724O59IS\nREPORTED RELEASE\n 610\nSTATUS\n CLOSED DOC\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-01-28\nCLOSED DATE\n 2016-03-09\nLAST MODIFIED DATE\n 2016-03-09\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nPublications Referenced SC23883404 FIX INFORMATION", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q218", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "AMQ9641 error pattern in system.log or WebSphereMQSuite.log\n[2015-11-05 13:24:43.873] ERROR MQException during MQCONN: CC=2 RC=2397\n[2015-11-05 13:24:43.873] ERROR [1446722683873] MQJE001: Completion Code '2', Reason '2397'.\n[2015-11-05 13:24:43.873] ERRORDTL [1446722683873]com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2397'.\nat com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:247)\nat com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:588)\nat com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:630)\nat com.ibm.mq.StoredManagedConnection.(StoredManagedConnection.java:107)\nat com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:205)\nat com.ibm.mq.MQQueueManagerFactory.obtainBaseMQQueueManager(MQQueueManagerFactory.java:911)\nat com.ibm.mq.MQQueueManagerFactory.procure(MQQueueManagerFactory.java:799)\nat com.ibm.mq.MQQueueManagerFactory.constructQueueManager(MQQueueManagerFactory.java:750)\nat com.ibm.mq.MQQueueManagerFactory.createQueueManager(MQQueueManagerFactory.java:157)\nat com.ibm.mq.MQQueueManager.(MQQueueManager.java:681)\nat com.sterlingcommerce.woodstock.services.wsmqSuite.WSMQSession.openConnection(WSMQSession.java:296)\nat com.sterlingcommerce.woodstock.services.wsmqSuite.WSMQSession.openSession(WSMQSession.java:274)\nat com.sterlingcommerce.woodstock.services.wsmqSuite.WSMQImpl.openSession(WSMQImpl.java:121)\nat com.sterlingcommerce.woodstock.services.wsmqSuite.WSMQImpl.processData(WSMQImpl.java:63)\nat com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.invokeService(ActivityEngineHelper.java:1821)\nat com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.nextMainLogic(ActivityEngineHelper.java:635)\nat com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.next(ActivityEngineHelper.java:362)\nat com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.doWork(WorkFlowQueueListener.java:440)\nat com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.run(WorkFlowQueueListener.java:236)\nat com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.onMessage(WorkFlowQueueListener.java:197)\nat com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.onMessage(WorkFlowQueueListener.java:184)\nat com.sterlingcommerce.woodstock.workflow.queue.wfTransporter.run(wfTransporter.java:444)\nat com.sterlingcommerce.woodstock.workflow.queue.BasicExecutor$Worker.run(BasicExecutor.java:508)\nat java.lang.Thread.run(Thread.java:662)\nCaused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2397;AMQ9204: Connection to host '192.168.0.1(1414)' rejected. [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2397;AMQ9641: Remote CipherSpec error for channel 'MQCHL' to host ''. [3=MQCHL]],3=192.168.0.1(1414),5=RemoteConnection.analyseErrorSegment]\nat com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:2062)\nat com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1226)\nat com.ibm.mq.ese.jmqi.InterceptedJmqiImpl.jmqiConnect(InterceptedJmqiImpl.java:311)\nat com.ibm.mq.ese.jmqi.ESEJMQI.jmqiConnect(ESEJMQI.java:337)\nat com.ibm.mq.MQSESSION.MQCONNX_j(MQSESSION.java:924)\nat com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:236)\n... 23 more\nCaused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2397;AMQ9641: Remote CipherSpec error for channel 'MQCHL' to host ''. [3=MQCHL]\nat com.ibm.mq.jmqi.remote.impl.RemoteConnection.analyseErrorSegment(RemoteConnection.java:3846)\nat com.ibm.mq.jmqi.remote.impl.RemoteConnection.receiveTSH(RemoteConnection.java:2746)\nat com.ibm.mq.jmqi.remote.impl.RemoteConnection.initSess(RemoteConnection.java:1034)\nat com.ibm.mq.jmqi.remote.impl.RemoteConnection.connect(RemoteConnection.java:727)\nat com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSessionFromNewConnection(RemoteConnectionSpecification.java:400)\nat com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSession(RemoteConnectionSpecification.java:299)\nat com.ibm.mq.jmqi.remote.impl.RemoteConnectionPool.getSession(RemoteConnectionPool.java:164)\nat com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1599)\n... 28 more\n\nAMQ9631 Error pattern in AMQERR*.LOG.\n10/28/2015 09:59:53 AM - Process(4665.10199066) User(mqm) Program(amqrmppa)\nHost(lcoalhost)\nAMQ9631: The CipherSpec negotiated during the SSL handshake does not match the\nrequired CipherSpec for channel 'MQCHL'.\n\nEXPLANATION:\nThere is a mismatch between the CipherSpecs on the local and remote ends of\nchannel 'MQCHL'. The channel will not run until this mismatch is\nresolved. The CipherSpec required in the local channel definition is\n'TLS_RSA_WITH_3DES_EDE_CBC_SHA'. The name of the CipherSpec negotiated during\nthe SSL handshake is 'TLS_RSA_WITH_3DES_EDE_CBC_SHA'. A code is displayed if\nthe name of the negotiated CipherSpec cannot be determined.\nACTION:\nChange the channel definitions for 'MQCHL' so the two ends have matching\nCipherSpecs and restart the channel. If the certificate in use by one end of\nthe channel is a Global Server Certificate, then the negotiated CipherSpec may\nnot match that specified on either end of the channel. This is because the SSL\nprotocol allows a Global Server Certificate to automatically negotiate a higher\nlevel of encryption. In these cases specify a CipherSpec which meets the\nrequirements of the Global Server Certificate.\n---- amqccisa.c : 889 --------------------------------------------------------", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q218", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "IBM WebSphere MQ version 7.0.1.6 and 7.5.0.4 (and analogous) do not support TLS with non IBM JDK\n(see APAR IV66840 http://www-01.ibm.com/support/docview.wss?uid=swg1IV66840 [http://www-01.ibm.com/support/docview.wss?uid=swg1IV66840]).", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q218", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "ISBI 5.2.x (pre 5.2.5)\nSun JDK 1.6\nMQ client jar libs v7.0 (pre 7.0.1.13), v7.1 (pre 7.1.0.7), v7.5 (pre 7.5.0.5) or v8.0 (pre 8.0.0.2)\nWMQ Adapter or WMQ Suite Open Session Service\nSSL connection with CipherSpec SSL_RSA_WITH_3DES_EDE_CBC_SHA or SSL_RSA_WITH_DES_CBC_SHA that is mapped to a TLS cipher for MQ\n (see http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.dev.doc/q032470_.htm [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.dev.doc/q032470_.htm])\nFIPSMode=true (default)", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q218", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "When using WMQ Adapter check /logs/system.log* for error pattern described in Symptom section above.\nWhen using WMQ Suite Open Session Service check /logs/WebSphereMQSuite.log* for error pattern described in Symptom section above.\nCheck on IBM WebSphere MQ Server the Queue Manager's error logs ( /qmgrs//errors/AMQERR*.LOG) for error pattern described in Symptom section above.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q218", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "On Windows: please use IBM JDK or follow these steps:\n\n 1. Uninstall existing MQ client libs from ISBI (see http://www.ibm.com/support/docview.wss?uid=swg21690573 [http://www.ibm.com/support/docview.wss?uid=swg21690573])\n 2. Install recent MQ client libs (at least version 7.0.1.13, 7.1.0.7, 7.5.0.5 or 8.0.0.2) in ISBI (see http://www.ibm.com/support/docview.wss?uid=swg21670087 [http://www.ibm.com/support/docview.wss?uid=swg21670087])\n 3. Just adding \"JVM_ARGS_PREFIX=-Dcom.ibm.mq.cfg.useIBMCipherMappings=false\" to \\properties\\tuning.properties would not work because of APAR IT08432 (http://www.ibm.com/support/docview.wss?uid=swg1IT08432 [http://www.ibm.com/support/docview.wss?uid=swg1IT08432]).\n Thus it is required to follow these additional steps: * open \\properties\\installNoappsWindowsService.cmd.in\nfind the line \"echo &JVM_ARGS_PREFIX; >> %PARAM_FILE%\"\nadd a new line containing \"echo -Dcom.ibm.mq.cfg.useIBMCipherMappings=false >> %PARAM_FILE%\" after this line\nsave and close \\properties\\installNoappsWindowsService.cmd.in\n\n 4. Open a command prompt from \\bin and: * call setupfiles.cmd\ncall uninstallWindowsService.cmd\ncall installWindowsService.cmd\n\n 5. Restart ISBI\n\nOn non Windows: please use IBM JDK or follow these steps:\n\n 1. Uninstall existing MQ client libs from ISBI (see http://www.ibm.com/support/docview.wss?uid=swg21690573 [http://www.ibm.com/support/docview.wss?uid=swg21690573])\n 2. Install recent MQ client libs (at least version 7.0.1.13, 7.1.0.7, 7.5.0.5 or 8.0.0.2) in ISBI (see http://www.ibm.com/support/docview.wss?uid=swg21670087 [http://www.ibm.com/support/docview.wss?uid=swg21670087])\n 3. Add \"JVM_ARGS_PREFIX=-Dcom.ibm.mq.cfg.useIBMCipherMappings=false\" to \\properties\\tuning.properties\n 4. Open a command prompt from \\bin and call setupfiles.sh\n 5. Restart ISBI", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q218", "section_id": 5, "heading": "RELATED INFORMATION", "parent": null, "text": "TechDoc: APAR IV66840 [http://www.ibm.com/support/docview.wss?uid=swg1IV66840]\nMQ Docu: SSL CipherSpecs and CipherSuites in JMS [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.dev.doc/q032470_.htm]", "logical_doc_id": 0, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q218", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "TechNote: How to uninstall WebSphere MQ Client jars [http://www.ibm.com/support/docview.wss?uid=swg21690573]", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q218", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "TechNote: How to get and install new MQ Client jars [http://www.ibm.com/support/docview.wss?uid=swg21670087]\nAPAR IT08432: JVM ARGUMENTS PREFIX/SUFFIX OPTION ON WIn [http://www.ibm.com/support/docview.wss?uid=swg1IT08432]", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q218", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Users observe errors when attempting to install or migrate to IBM MQ 8.0.0.4 using the following levels of IBM Pure Application System:\n2.1.2.0\n2.2.0.0 and later\n\nThis affects users with IBM MQ Pure Application System pattern-types 1.0.0.2 and earlier.", "logical_doc_id": 3, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q218", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Because of an interface change in IBM Pure Application System 2.1.2.0, and in 2.2.0.0 and greater, installation and upgrade of IBM MQ at the latest maintenance level contained in the pattern-type fails. The installation appears to succeed, but IBM MQ 8.0.0.2 is installed and the subsequent fixpack update is not applied. This affects IBM MQ Pure Application System pattern-types 1.0.0.2 and earlier, leading to the following restrictions:\nFor IBM Pure Application System releases earlier than 2.1.2.0 and at version 2.1.2.1, you can install all versions of IBM MQ contained in the pattern-type. You can also apply maintenance to running pattern instances.\nFor IBM Pure Application System 2.1.2.0, 2.2.0.0 and later, you can install IBM MQ 8.0.0.2 only. You cannot install later versions e.g., 8.0.0.4. You cannot apply maintenance to running pattern instances.", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q218", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "A new maintenance.py lifecycle script is available to enable installation and migration of the latest maintenance level of IBM MQ contained in the pattern-type.\n\nThis update, and installation steps, can be obtained from IBM Fix Central:\n\nhttp://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=8.0&platform=All&function=fixId&fixids=1.0.0.2-WS-MQ-Pure-LAIT15252&includeSupersedes=0&source=fc [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=8.0&platform=All&function=fixId&fixids=1.0.0.2-WS-MQ-Pure-LAIT15252&includeSupersedes=0&source=fc]\n\nAPAR IT15252 has been raised for the IBM MQ development team to address this issue within future releases of the IBM MQ Pure Application System pattern-type.\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q218", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The WebSphere MQ MFT 'fteListAgents' command for the protocol\n bridge agent returns the following warning message:\n \"BFGCL0014W: No agents exist that match the current selection\n criteria\".", "logical_doc_id": 4, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q218", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "1) Specify the name of the agent followed by an asterisk\n character.\n\nFor example:\n\nfteListAgents MY_BRIDGE_AGENT*\n\n2) Specify the name of the agent followed by the string:\n\n\"MY_BRIDGE_AGENT ( )\"\n\nwhere can be one of the following strings:\nbridge\nWeb Gateway\nConnect:Direct bridge\n\nFor example:\n\nfteListagents \"MY_BRIDGE_AGENT ( bridge )\"\n\n3) Use the fteShowAgentDetails command to get status information\n about a particular agent.", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q218", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n This issue affects users of the WebSphere MQ Managed File\n Transfer command fteListAgents who specify a pattern argument\n that is exactly the name of an agent which is of type protocol\n bridge, Connect:Direct bridge or web.\n\nPlatforms affected:\n MultiPlatform\n\nPROBLEM DESCRIPTION:\n The WebSphere MQ Managed File Transfer (MFT) command:\n\nfteListAgents\n\ncan be used to list all of the agents that are registered with a\n particular coordination queue manager. The command provides\n additional information for some agents to identify their types.\n This is the case for protocol bridge agents, Connect:Direct\n bridge agents and web agents. For example:\n\n$ ./fteListAgents\n 5724-H72 Copyright IBM Corp. 2008, 2013. ALL RIGHTS RESERVED\n Agent Name: Queue Manager Name: Status:\n AGENT1 MFT_QMGR STOPPED\n AGENT2 MFT_QMGR READY\n PBAGENT ( bridge ) MFT_QMGR READY\n\nIn the above example output, the agents with names \"AGENT1\" and\n \"AGENT2\" are standard WebSphere MQ MFT agents,. However the\n agent with name \"PBAGENT\" is a protocol bridge agent, identified\n by the string \" ( bridge )\" appended to the agents name.\n\nThe fteListAgents command accepts an optional pattern parameter\n that is used to filter the list of agents that are displayed in\n the command output. For example, the pattern \"A*\" can be used to\n list all known WebSphere MQ MFT agents whose name begins with\n \"A\":\n\n$ ./fteListAgents \"A*\"\n 5724-H72 Copyright IBM Corp. 2008, 2013. ALL RIGHTS RESERVED\n Agent Name: Queue Manager Name: Status:\n AGENT1 MFT75_QMGR STOPPED\n AGENT2 MFT75_QMGR READY\n\nThe pattern provided when invoking the command should have been\n used to filter against the name of an agent. However, it was\n being used to match against the name displayed on the output of\n the command. For non-standard agents (bridge, Connect:Direct\n bridge and web), this resulted in the pattern being matched\n against more than just the agent name. For these types of agents\n therefore, if the pattern specified on the fteListAgents command\n was exactly the name of a non-standard agent, then the matching\n would fail and the command would return the message:\n\nBFGCL0014W: No agents exist that match the current selection\n criteria.\n\neven in the case where an agent with the name specified existed\n and was registered with the coordination queue manager.\n\nContinuing the example above where a protocol bridge agent with\n the name \"PBAGENT\" exists, specifying the name of the agent as\n the pattern returns no results:\n\n$ ./fteListagents PBAGENT\n 5724-H72 Copyright IBM Corp. 2008, 2013. ALL RIGHTS RESERVED\n BFGCL0014W: No agents exist that match the current selection\n criteria.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q218", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The WebSphere MQ Managed File Transfer (MFT) code for the\n fteListAgents command has been updated such that when a pattern\n to filter the list of agents displayed is provided, it is\n matched against both the agent name and the displayed agent name\n on the commands output. Therefore patterns that exactly match\n the name of a WebSphere MQ MFT agent, regardless of agent type,\n will be listed in the output of the command.\n\nThis APAR still permits the pattern provided to be matched\n against the display name of the agent. As such, in the case\n where a user only wants to list agents of type protocol bridge,\n they can specify, for example, the pattern \"* ( bridge )\". This\n pattern will fail to match against any agent names, but will\n match against the displayed agent names when the agents are of\n protocol bridge type.\n\nThe fix is targeted for delivery in the following PTFs:\n\nVersion Maintenance Level\n v7.5 7.5.0.6\n v8.0 8.0.0.4\n\nThe latest available FTE maintenance can be obtained from\n 'Fix List for WebSphere MQ File Transfer Edition 7.0'\n http://www-01.ibm.com/support/docview.wss?uid=swg27015313 [http://www-01.ibm.com/support/docview.wss?uid=swg27015313]\n\nThe latest available MQ maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\nIf the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q218", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT09363\nREPORTED COMPONENT NAME\n WMQ MFT\nREPORTED COMPONENT ID\n 5724H7242\nREPORTED RELEASE\n 750\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2015-06-09\nCLOSED DATE\n 2015-06-26\nLAST MODIFIED DATE\n 2015-06-26\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q218", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ MFT\nFIXED COMPONENT ID\n 5724H7242", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q218", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R750 PSY\n UP\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q218", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The \"MQ Advanced V8.0 Virtual System Pattern Type for IBM\n PureApplication System Multilingual (CN7AEML)\" includes a\n template \"IBM MQ Multi-instance with 2 pairs\" that includes\n a default value for the \"Storage Maximum limit (K,M,G)\" of\n 100M which is insufficient for 2 queue managers.\n\nWhen creating IBM MQ Virtual System Pattern Type patterns from\n existing templates with this preset default GPFS storage\n limitation value, the pattern with a pair of HA Multi-instance\n IBM MQ components will fail to deploy.\n\nOne or both of the following might be witnessed:\n The active and standby queue manager in the VM fail to start.\n The trace.log shows the IBM MQ error (893).", "logical_doc_id": 5, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q218", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "When using the provided template to create your pattern, change\n the GPFS storage maximum value to 1G or higher depending on your\n requirements.", "logical_doc_id": 5, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q218", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n Users of the IBM MQ Virtual System Pattern Type patterns from\n existing templates with a preset default GPFS storage limitation\n value.\n\nPlatforms affected:\n MultiPlatform\n\nPROBLEM DESCRIPTION:\n The pattern failed to deploy because the GPFS storage maximum\n limitation value in the pattern template provided was set too\n low. The value in the pattern template was 100M but should be\n higher.\n\nEach queue manager requires approximately 100M of space when\n created but this storage requirement will increase with further\n configuration and runtime processing of messages. The same GPFS\n partition might be used in multiple deploys, so the\n configuration needs to allow enough storage for the required\n workload", "logical_doc_id": 5, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q218", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The IBM MQ Virtual System Pattern Type pattern template has been\n updated to set the GPFS storage maximum limitation value to 1G\n\nThe fix is targeted for delivery in the following PTFs:\n\nVersion Maintenance Level\n v8.0 8.0.0.5\n\nThe latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\nIf the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q218", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT12401\nREPORTED COMPONENT NAME\n WMQ BASE MULTIP\nREPORTED COMPONENT ID\n 5724H7251\nREPORTED RELEASE\n 800\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2015-11-23\nCLOSED DATE\n 2016-01-28\nLAST MODIFIED DATE\n 2016-01-28\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q218", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ BASE MULTIP\nFIXED COMPONENT ID\n 5724H7251", "logical_doc_id": 5, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q218", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R800 PSY\n UP", "logical_doc_id": 5, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q218", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "After running the application for a few days it would hang and the Heap memory space was full.\nGarbage Collection runs were not able to free up any memory and GC logs were showing the pattern of a memory leak.", "logical_doc_id": 6, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q218", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "In the heap dump files 84% of the memory space was occupied by the following class:\ncom/ibm/mq/jmqi/remote/impl/RemoteConnectionPool", "logical_doc_id": 6, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q218", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "Production and QA.", "logical_doc_id": 6, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q218", "section_id": 3, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "To diagnose the situation enable verbose GS logging in the JVM. Analyse GC logs over a period of time and they should reveal a slow progressive increase in the heap size with the typical pattern of a memory leak.\nYou can also generate some heapdump files when the heap size is full and search which objects are occupying the memory.", "logical_doc_id": 6, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q218", "section_id": 4, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Go in the Sterling B2B Integrator in the /install/properties directory and review the dynamicclasspath.cfg file.\n\nVerify that all the required jar files are been installed:\n\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/com.ibm.mq.allclient.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/com.ibm.mq.axis2.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/com.ibm.mq.commonservices.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/com.ibm.mq.defaultconfig.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/com.ibm.mq.headers.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/com.ibm.mq.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/com.ibm.mq.jmqi.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/com.ibm.mq.jms.Nojndi.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/com.ibm.mq.pcf.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/com.ibm.mq.postcard.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/com.ibm.mq.soap.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/com.ibm.mq.tools.ras.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/com.ibm.mq.traceControl.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/com.ibm.mqjms.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/fscontext.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/jms.jar\nVENDOR_JAR=/home/sb2bi_user/install/jar/ibm_mq/9_0/providerutil.jar\n\nWhen we verified the size of the files installed in Sterling B2B Integrator and compared them with the *.jar files on the WS MQ Server and we noticed there was a substantial difference in the size of the files.\nWe found out the libraries installed were from WS MQ version 9.0.0.0 and the WS MQ Server was in version 9.0.0.2.\n\nThe customer went on the WS MQ Server under the /install_dir/java/lib and copied the correct version of all the jar files.\nHe then replaced them in all the folders referenced in the dynamicclasspath.cfg file and restarted the application.\nAfter the restart the memory leak problem was resolved and GC logs were showing stable memory consumption.", "logical_doc_id": 6, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q256", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q256", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "AFFECTED URL:\n http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/in [http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/in]\n stall/rm_production_farm.dita\n .\n TEXT READS:\n The image of the Topology is incorrect as it indicates that\n release and jcr db domains should be unique and the write up for\n that section would need to be modified.\n .\n TEXT SHOULD READ:\n The image should be updated to show only release as unique.\n write up for section should indicate that only release would be\n unique (in a unique Portal farm) while all db domains are shared\n (in a shared Portal farm).", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q256", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Refer to the above.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q256", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "This is planned to be changed in the product documentation.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q256", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This is planned to be changed in the product documentation.\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q256", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI25000\nREPORTED COMPONENT NAME\n WEBSPHERE PORTA\nREPORTED COMPONENT ID\n 5724E7600\nREPORTED RELEASE\n 850\nSTATUS\n CLOSED DOC\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-09-03\nCLOSED DATE\n 2014-12-03\nLAST MODIFIED DATE\n 2014-12-03\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q256", "section_id": 0, "heading": "ENVIRONMENT", "parent": null, "text": "These instructions are for WebSphere Message Broker or IBM Integration Bus on Windows systems.\nReturn to the WebSphere Message Broker MustGather index [http://www-01.ibm.com/support/docview.wss?uid=swg21209857] for other systems.", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q256", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "STEP 1: SELF-GUIDED TROUBLESHOOTING\n\n1. Review the WebSphere Technical Exchange for your version:\n Webcast replay: Migrating to IBM Integration Bus v9.0 [http://www-01.ibm.com/support/docview.wss?uid=swg27038933]\n\n2. Check for known issues:\n Resolving problems that occur when migrating or importing resources [http://www.ibm.com/support/knowledgecenter/en/SSMKHH_10.0.0/com.ibm.etools.mft.doc/au16662_.htm]\n WebSphere Support Blog (WMB Migration) [https://www.ibm.com/developerworks/community/blogs/aimsupport/search?lang=en&t=entry&f=all&q=migration%20wmb]\n [http://www.ibm.com/software/htp/cics/tserver/support/]WebSphere Message Broker support site [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Message_Broker]\n\nSTEP 2: COLLECT DATA\n\n1. mqsidc See: mqsidc usage instructions [http://www.ibm.com/support/knowledgecenter/en/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bu46012_.htm]\nWhen running the tool, select the option for 'Broker Collector', when prompted.\n\n2.\n 3. mqsimigratecomponents command\n If you used 'mqsimigratecomponents', please send in the output of the command from the time of the failing migration. You can used the same command, post migration, to check or verify the current components.\n See: mqsimigratecomponents command [http://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/an26150_.htm]\n 4.\n 5. General Broker information\n If the mqsidc tool was not run, then capture this information manually * Record the WebSphere Message Broker version, release, and maintenance level.\n This can be captured using the command 'mqsiservice -v'..\nRecord the operating system version, release, and maintenance level.\nRecord the version, release, and maintenance level of any related products and components for the problematic application.\nCollect the local error log.\n On Window systems, the local error log is the Windows Application Event Log.\n You can find the Event Viewer from the Windows Control Panel.\n See: Event viewer logs [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21295454]\nCollect the Standard Output/Error logs.\n On Window systems, WMB writes information to a 'console.out' file.\n This file is located under the Message Broker workpath.\n See: Standard System Logs [http://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/au14165_.htm]\n\nATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!\nWhen sending data to IBM, be sure to update your PMR or send a note with the following information:\nTell us what errors you saw, where you saw them, and what time they happened Let us know if you made any changes to WebSphere Message Broker or the system before the problem Share any other observations which you think will help us to better understand the problem\n\nSTEP 3: SUBMIT DATA TO IBM\nUse IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM.\nSend your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis.\n\nPlease see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support.\n\nBack to top", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q256", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "PRODUCT ALIAS/SYNONYM\n WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q256", "section_id": 0, "heading": "ENVIRONMENT", "parent": null, "text": "These instructions are for WebSphere Message Broker or IBM Integration Bus on Windows systems.\nReturn to the WMB / IIB MustGather index [http://www-01.ibm.com/support/docview.wss?uid=swg21209857] for other systems.", "logical_doc_id": 3, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q256", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "STEP 1: SELF-GUIDED TROUBLESHOOTING\n\n1. Consider Using the Test Client in trace and debug mode [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/af52260_.htm].\n 2.\n 3. A user level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#1] is intended to assist users with understanding how their ESQL is processed.\n It will also show a high level view of the message flow behavior.\n 4.\n 5. Check for known issues:\n Troubleshooting JMS nodes [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac24877_.htm]\n developerWorks Forums: WebSphere Message Broker: JMS [https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-000000000281&query=jms]\n WebSphere Message Broker support site [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Message_Broker]\n\nSTEP 2: COLLECT DATA\n\n1. mqsidc See: mqsidc usage instructions [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/bu46012_.htm]\nWhen running the tool, select the option for 'Broker Collector', when prompted.\n\n2.\n 3. JMS details\n Export a current view of your JMS configuration with these items: * mqsireportproperties -c JMSProviders -o -r\nthe contents of the jarsURL directory\nthe JNDI bindings file\n\n4.\n 5. Project Interchange files for the problematic flow/set/ESQL/model\nYou can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.\n See: Exporting your message flow projects from the Toolkit [http://www.ibm.com/support/docview.wss?uid=swg21418121]\n\n6.\n 7. Traces If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321] can be used to gain a better understanding of the problem. * A user level trace [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321#1] is intended to assist users with understanding how their ESQL is processed. It will also show a high level view of the message flow behavior.\nA service level trace [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21177321#2] is intended to be provided to IBM Support to assist in the diagnosis of your issue.\n\n8.\n 9. General Broker information\n If the mqsidc tool was not run, then capture this information manually * Record the WebSphere Message Broker version, release, and maintenance level.\n This can be captured using the command 'mqsiservice -v'.\nRecord the operating system version, release, and maintenance level.\nRecord the version, release, and maintenance level of any related products and components for the problematic application.\nCollect the local error log.\n On Window systems, the local error log is the Windows Application Event Log.\n You can find the Event Viewer from the Windows Control Panel.\n See: Event viewer logs [http://www.ibm.com/support/docview.wss?rs=849&uid=swg21295454]\nCollect the Standard Output/Error logs.\n On Window systems, WMB writes information to a 'console.out' file.\n This file is located under the Message Broker workpath.\n See: Standard System Logs [http://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/au14165_.htm]", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q256", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "ATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!\nWhen sending data to IBM, be sure to update your PMR or send a note with the following information:\nTell us what errors you saw, where you saw them, and what time they happened Let us know if you made any changes to WebSphere Message Broker or the system before the problem Share any other observations which you think will help us to better understand the problem\n\nSTEP 3: SUBMIT DATA TO IBM\nUse IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM.\nSend your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis.\n\nPlease see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support.\n\nBack to top\n\nPRODUCT ALIAS/SYNONYM\n WMB MB WBIMB", "logical_doc_id": 3, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q256", "section_id": 0, "heading": "ENVIRONMENT", "parent": null, "text": "These instructions are for WebSphere Message Broker or IBM Integration Bus on AIX, HP-UX, Linux, and Solaris systems.\nReturn to the WMB / IIB MustGather index [http://www-01.ibm.com/support/docview.wss?uid=swg21209857] for other systems.", "logical_doc_id": 4, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q256", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "STEP 1: SELF-GUIDED TROUBLESHOOTING\n\n1. Understand the problem that is occurring. * Consider using the Test Client in trace and debug mode [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/af52260_.htm].\nA user level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#1] is intended to assist users with understanding how their ESQL is processed.\n It will also show a high level view of the message flow behavior.\nThe product documentation contains several suggestions for Monitoring the Global Cache [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bn23786_.htm].\n\n2.\n 3. Locate the errors. * Global Cache interactions are logged in the Global Cache Activity Log [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bj23784_.htm].\nInformational messages and unhandled exceptions are written to the IIB Syslog [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/an04230_.htm]. This will also contain a number of BIP71** messages relating to startup/connection of cache components, and whether any of them have failed.\nSome messages may be written to the 'stderr' and 'stdout' files [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/au14165_.htm], located under the Broker's (Integration Node's) workpath.\n\n4.\n 5. Check for known issues and solutions. * General information regarding the Global Cache [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bc23789_.htm] is available in the product documentation, as well as instructions on how to configure the cache [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bn23780_.htm] via the provided tooling.\nReview how to access the Global Cache from a JavaCompute node [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bc23770_.htm].\nThe IIB development and support teams regularly update the IIB DeveloperWorks Blog with Global Cache solutions [https://developer.ibm.com/integration/blog/].\nYour problem may have been discussed on the IIB dWAnswers forum [https://developer.ibm.com/answers/?community=iib].\n*\nWebSphere Message Broker support site\n\nSTEP 2: COLLECT DATA\n\n1. mqsidc\n See: mqsidc usage instructions [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/bu46012_.htm]\nWhen running the tool, select the option for 'Broker Collector', when prompted.\n\n2.\n 3.\n 4. Global Cache details\n Export a current view of your Global Cache with these commands.\n See: mqsicacheadmin command [http://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/bn23783_.htm] * mqsicacheadmin -c listHosts\nmqsicacheadmin -c showMapSizes\nmqsicacheadmin -c showPlacement\nmqsireportproperties -b cachemanager -o CacheManager -r\nmqsireportproperties -e -o ComIbmCacheManager -r\n\n5.\n 6.\n 7. Traces\n If the problem occurs during a runtime test or with the Toolkit test facility,\n an Execution Group service level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#2] can be used to gain a better understanding of the problem.", "logical_doc_id": 4, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q256", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Note: For issues with Global Cache, broker service trace contains WXS trace. However, you may sometimes be advised to set a specific WXS trace string. Moreover, for startup issues, a WXS trace string must be specified, as well as enabling service trace. * For startup issues, run this command prior to tracing:\n mqsichangeproperties -e -o ComIbmCacheManager -n overrideTraceSpec -v ObjectGrid*=fine=enabled\nTo capture all information (very verbose), run this command prior to tracing:\n mqsichangeproperties -e -o ComIbmCacheManager -n overrideTraceSpec -v ObjectGrid*=all=enabled\n\n8.\n 9.\n 10. Project Interchange files for the problematic message flow\nYou can export your Message Flow and Java project(s) into an archive file for easy transmission to IBM Support.\n See: Exporting your message flow projects from the Toolkit [http://www-01.ibm.com/support/docview.wss?uid=swg21418121]\n\n11.\n 12.\n\nATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!\nWhen sending data to IBM, be sure to update your PMR or send a note with the following information:\nTell us what errors you saw, where you saw them, and what time they happened Let us know if you made any changes to WebSphere Message Broker or the system before the problem Share any other observations which you think will help us to better understand the problem\n\nSTEP 3: SUBMIT DATA TO IBM\nUse IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM.\nSend your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis.\n\nPlease see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support.\n\nBack to top\n\nPRODUCT ALIAS/SYNONYM\n IIB WMB WXS GC", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q256", "section_id": 0, "heading": "ENVIRONMENT", "parent": null, "text": "These instructions are for WebSphere Message Broker or IBM Integration Bus on AIX, HP-UX, Linux, and Solaris systems.\nReturn to the WebSphere Message Broker MustGather index [http://www-01.ibm.com/support/docview.wss?uid=swg21209857] for other systems.", "logical_doc_id": 5, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q256", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "STEP 1: SELF-GUIDED TROUBLESHOOTING\n\n1. Consider Using the Test Client in trace and debug mode [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/af52260_.htm].\n 2.\n 3. A user level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#1] is intended to assist users with understanding how their ESQL is processed.\n It will also show a high level view of the message flow behavior.\n 4.\n 5. Check for known issues:\n WebSphere Adapter nodes [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/ac37160_.htm] Transport and connectivity samples [https://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ax20230_.htm]\n Resolving problems when developing message flows with WebSphere Adapter nodes [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/au16538_.htm]\n Integrating WMB with SAP [http://www-01.ibm.com/support/docview.wss?uid=swg27018476&aid=1]\n [http://www.ibm.com/software/htp/cics/tserver/support/]WebSphere Message Broker support site [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Message_Broker]\n\nSTEP 2: COLLECT DATA\n\n1. mqsidc\n See: mqsidc usage instructions [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bu46010_.htm]\nThis command line tool is only available for WMB 7.0.0.5+, WMB 8.0.0.1+, and IIB 9.0.\nWhen running the tool, select the option for 'Broker Collector', when prompted.\n\n2.\n 3. Project Interchange files for the problematic flow/set/ESQL/model\nYou can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.\n See: Backing up the Toolkit Workspace [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/an27100_.htm]\n\n4.\n 5. Refer to Adapter troubleshooting MustGathers [http://www-01.ibm.com/support/docview.wss?uid=swg21438193]\n 6. Traces If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321] can be used to gain a better understanding of the problem. * A user level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#1] is intended to assist users with understanding how their ESQL is processed. It will also show a high level view of the message flow behavior.\nA service level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#2] is intended to be provided to IBM Support to assist in the diagnosis of your issue.\nRFC traces:\n Steps to enable and collect the RFC Traces:\n 1. Launch the Adapter Connection Wizard ,and proceed to the 'Service Generation and Deployment Configuration' window. In the SAP RFC trace configuration section:\nSet the RFCTraceOn property to 'true'\nSet the RFC Trace Level property to '8' , which outputs verbose debug messages, full\n execution path, info messages, errors and warnings\nSet the Folder for RFC trace files property to the directory location where the RFC Traces\n are created\nAlternatively, these properties may also be set on SAPConnection configurable service [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bn28742_.htm] using mqsichangeproperties command or MB Explorer, which would require a broker/execution group restart.\n For example: mqsichangeproperties -c SAPConnection -o Template -n RFCTraceOn -v true\n\n2. Recreate the issue.\n\n3. Collect the RFC trace files generated.", "logical_doc_id": 5, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q256", "section_id": 1, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Note: The trace files are created in the directory where the adapter process has been started by default. The trace file has a .trc file extension and the file name will start with the letters rfc followed by a unique identifier. For example, rfc03912_02220.trc.\n\n7.\n 8. General Broker information\n If the mqsidc tool was not run, then capture this information manually * Record the WebSphere Message Broker version, release, and maintenance level.\n This can be captured using the command 'mqsiservice -v'..\nRecord the operating system version, release, and maintenance level.\nRecord the version, release, and maintenance level of any related products and components for the problematic application.\nCollect the local error log. On UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.\n See: Configuring the syslog daemon [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/an04230_.htm]\nCollect the Standard Output/Error logs.\n WMB writes information to both STDOUT and STDERR. These files are located under the Message Broker workpath.\n See: Standard System Logs [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/au14165_.htm]\n\nATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!\nWhen sending data to IBM, be sure to update your PMR or send a note with the following information:\nTell us what errors you saw, where you saw them, and what time they happened Let us know if you made any changes to WebSphere Message Broker or the system before the problem Share any other observations which you think will help us to better understand the problem\n\nSTEP 3: SUBMIT DATA TO IBM\nUse IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM.\nSend your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis.\n\nPlease see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support.\n\nBack to top\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus AIX, HP-UX, Linux, Solaris 10.0, 9.0 All Editions\nPRODUCT ALIAS/SYNONYM\n WMBFE MBFE WMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI", "logical_doc_id": 5, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q103", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "On the WebSphere Integrated Solutions Console, the Search application status reports \"Partial Start\".\n\nChecking the systemout.log, you see messages like the following after attempting to start the Search application on these nodes:\n\nLocalExceptio E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method \"getBean\" on bean \"BeanId(Search#dboard.search.ejb.jar#Search\nServiceLocator, null)\". Exception data: org.springframework.beans.factory.access.BootstrapException: Unable to initialize group definition. Group resource name [classpath*:spring/search/app/SearchBeanRefF\nactory.xml], factory key [spring.search.app]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'spring.search.app' defined in URL [wsjar:file:/E:/\nIBM/WebSphere/AppServer/profiles/connect1/installedApps/ConnectionsCell/Search.ear/search.common.jar!/spring/search/app/SearchBeanRefFactory.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.springframework.context.support.ClassPathXmlApplicationContext]: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'INDEXER:dcsWorkManager' defined in class path resource [spring/search/service/IndexingServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: Context: ConnectionsCell/clusters/InfraCluster, name: wm/search-dcs: First component in name search-dcs not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]\nat org.springframework.beans.factory.access.SingletonBeanFactoryLocator.useBeanFactory(SingletonBeanFactoryLocator.java:389)\n\n...", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q103", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "When IBM Connections is first installed, each node is automatically given a Work Manager for Search. However, you must create the Work Managers manually for any subsequent nodes created. The behavior described here indicates that additional Work Managers have not been created.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q103", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Once the Work Managers are created, the Search application should start on all affected Nodes. Instructions on how to do this are available here, in the IBM Connections documentation:\nhttp://www-01.ibm.com/support/knowledgecenter/SSYGQH_5.0.0/admin/admin/t_admin_search_create_work_managers.dita [http://www-01.ibm.com/support/knowledgecenter/SSYGQH_5.0.0/admin/admin/t_admin_search_create_work_managers.dita]\n\nWHITE PAPER", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q103", "section_id": 0, "heading": "ABSTRACT", "parent": null, "text": "This article answers some of the commonly asked questions related to IBM\u00ae Rational\u00ae Application Developer version 7.5 and provides best practice recommendations on a number of different topics.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q103", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Updated - See Change History.\n\nTable of Contents\nCommon Best Practices#J2EE%20Best%20Practices\nJ2EE Best Practices\nMiscellaneous\nChange History\n\nCommon Best Practices\n\nMigration:\n\nJAR included in lib under EAR project root [javascript:void(0);] [javascript:void(0);] (click to expand) Scenario:\nYou have JAR files that you include in the lib directory under the EAR project root. For Web or EJB projects, you select these JAR files as J2EE Jar/Module dependencies.\n\nWith Rational Application Developer 7.5, packages or classes in these JAR files are not accessible in Web or EJB projects; however, the same thing works fine when the JARs are placed directly under EAR root.\n\nQuestion:\n\nDoes Rational Application Developer automatically pick up the files under the lib directory in an EAR?\n\nAnswer:\n\nRational Application Developer does not automatically pick up the files under the lib directory in an EAR.\n\nWORKAROUND:\n\nYou may work around this issue by adding the library to your classpath using the Project > Properties > Add JAR option (which will add these JARs to your classpath). IBM Rational is considering automatic recognition of JARs under the lib directory in the classpath in a future version.\n\nMigrate EJB 2.x to EJB 3.0 [javascript:void(0);] [javascript:void(0);] (click to expand) Question:\nIs there a way to migrate EJB 2.x beans to EJB 3.0 beans?\n\nAnswer:\n\nCurrently there is no tool provided by Rational Application Developer that enables migrating an EJB 2.x bean to EJB 3.0.\n\nEJB 3.0 provides significant amount of simplification in terms of what is laid down by the specification, as compared to EJB 2.1. You may have a significant amount of EJB 2.x artifacts, but are excited about leveraging the simplicity and power of EJB 3.0.\n\nIf this is the case, the recommended approach is to create new artifacts in EJB 3.0, and leverage the power of Rational Application Developer to ensure that these new artifacts work well with your pre-EJB 3.0 artifacts.\n\nHow to migrate \"some\" projects [javascript:void(0);] [javascript:void(0);] (click to expand) Question:\n\nYou have chosen not to migrate all your projects to Rational Application Developer 7.5. How can you prevent certain projects from being migrated?\nAnswer:\n\nClose any projects that you chose not to migrate. When you open the project, migration will run for the project.", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q103", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Removing the .compatibility file [javascript:void(0);] [javascript:void(0);] (click to expand) Question:\nDo you need the .compatibility file?\n\nAnswer:\n\nNo.\n\nThe .compatibility file is no longer used in version 7.5.\n\nRight-click the project and click Java EE > Remove Obsolete Metadata to properly remove the uneeded files.\n\nValidating migration [javascript:void(0);] [javascript:void(0);] (click to expand) Question:\nYou closed the migration results. How do you determine what happened during the migration?\n\nAnswer:\n\nThe validation of your migration can be rerun. From the menu bar select Window > Show View > Other ... > Migration > Migration Results. When the view opens, click the green arrow.\n\nVersion control and migration [javascript:void(0);] [javascript:void(0);] (click to expand) Question:\nIn previous versions of Rational Application Developer, you did not know which files should be released into your source code management system. Which files should be checked out when migrating in version 7.5?\n\nAnswer:\n\nRational Application Developer 7.5 now ensures that any file that needs to be modified is read/write before proceeding with migration.\n\nNote: Ideally, you should check out the entire project.\n\nOn the Migration Project Resources page, you can see which files in the workspace will be modified by the migration process.\n\nTo copy a the list of the files, right-click the list and click Select All, then right-click the list and click Copy.\n\nRestarting a failed migration [javascript:void(0);] [javascript:void(0);] (click to expand) Question:\nThe migration failed. Is there any way to restart the migration?\n\nAnswer:\n\nYes.\n\nRestart the workspace or close and reopen the project. Migration will start for any project that requires migration.\n\nMigration and start-up performance [javascript:void(0);] [javascript:void(0);] (click to expand) Question:\nIn version 7.5, since migration runs at start-up, are there any performance issues when starting Rational Application Developer?\n\nAnswer:\n\nNo.\n\nThere are no performance issues. Migration runs on a separate thread, is lightweight and does not block Rational Application Developer start-up.\n\nValidation:\n\nIncremental validation [javascript:void(0);] [javascript:void(0);] (click to expand) Scenario:\nThe validators always run after every build of a project. Similar to the \"incremental build\", there should be a feature implemented that performs an \"incremental validation\" where the validation would only validate the changes that have been made since the last validation (or build). For example, if Java code is changed EJB Validator and J2EE Validator do not need to run.\n\nQuestion:", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q103", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Is there a way to incrementally validate parts of a build in version 7.5?\n\nAnswer:\n\nThere is no EE 5 validation (or any incremental validation feature) in Rational Application Developer 7.5.\n\nBack to top\n\nJ2EE Best Practices\n\nDeployment Descriptor Editors:\n\nCreate JAX-WS Deployment Descriptor [javascript:void(0);] [javascript:void(0);] (click to expand) Question: How do you generate JAX-WS deployment descriptor for an application?\n\nAnswer:\n\nYou can create JAX-WS deployment descriptor by opening up the \"Services\" folder of the project in the Enterprise Explorer, and right clicking on the service name, selecting the Generate > Deployment Descriptor options.\n\nExample:\n\n[/support/docview.wss?uid=swg27013753&aid=1] [/support/docview.wss?uid=swg27013753&aid=1]\n\nDefine security roles using EJB 3 DD [javascript:void(0);] [javascript:void(0);] (click to expand) Question:\nHow do you define a security role in an application using the new EJB 3 DD?\n\nAnswer:\n\n1. Open the EJB 3 Deployment Descriptor by double clicking on the DD node in the Enterprise Explorer.\n\n2. Selecting the root node, add an Assembly node in the DD.\n\n3. Select the Assembly node and press the 'Add' button. In the list of actions that comes up, you will be able to select the Security Role action.\n\nDefine security roles using EAR DD [javascript:void(0);] [javascript:void(0);] (click to expand) Question:\nHow do you define a security role in an application using the new EAR DD?\n\nAnswer:\n\nAfter opening the EAR Deployment Descriptor, select the Application node, and click on Add. You will be presented the Security Role option in the list of Actions.\n\nBinding and Extension descriptors [javascript:void(0);] [javascript:void(0);] (click to expand) Question:\nHow do you generate bindings and extensions descriptors for an application?\n\nAnswer:\n\nYou can create WebSphere Bindings and Extensions files by right clicking on the project node in the Enterprise Explorer, and from the Java EE Context Menu, selecting the 'Generate WebSphere Bindings' and 'Generate WebSphere Extensions' options.\n\nEJB Security Identity [javascript:void(0);] [javascript:void(0);] (click to expand) Question:\nYou created an annotated EJB 3 Session Bean. How do you create a Security Identity for this bean?\n\nAnswer:", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q103", "section_id": 1, "heading": "CONTENT", "parent": null, "text": "Annotated beans do not show up in the EJB Deployment descriptor when they are created. For most wizards invoked through the EJB 3 Deployment Descriptor, you do not need to override the bean in the DD. However, in order to create a Security Identity for an annotated bean, you need to override it in the Deployment Descriptor.\n\nWhen to install the WebSphere Application Server v6.1 Feature Packs [javascript:void(0);] [javascript:void(0);] (click to expand)\n\nQuestion: When should you install the WebSphere Application Server v6.1 Feature Packs? Answer: If you want to use JAXB Schema to Java Bean wizard or run JAX-WS Web Services on WebSphere Application Server v6.1. [/support/docview.wss?uid=swg27013753&aid=2] Project structure differences - 7.x vs 7.5 [javascript:void(0);] [javascript:void(0);] (click to expand) Question: Are there any differences in project structure between Rational Application Developer version 7 and version 7.5? Answer: No Project structure differences - 6.x vs 7.5 [javascript:void(0);] [javascript:void(0);] (click to expand) Question: Are there any differences in project structure between Rational Application Developer version 6 and version 7.5? Answer: Yes. The .compatibility file is no longer needed in Rational Application Developer 7.5. Installing the EJB 3 Feature Pack [javascript:void(0);] [javascript:void(0);](click to expand) Question: When should you install the EJB 3 Feature Pack? Answer: With WebSphere Application Server 7, you do not need to install the EJB 3 Feature Pack. [ Back to top\n\nChange History [javascript:void(0);] [javascript:void(0);] (click to expand) Change History 05 November 2008 Initial Release 09 December 2008 Added new tip on creating JAX-WS deployment descriptors to J2EE Best Practices section and added Whne to install WAS v6.1 Feature Pack to the Miscellaneous section.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q103", "section_id": 2, "heading": "RELATED INFORMATION", "parent": null, "text": "Rational Application Developer v7.0.x.x Best Practices [http://www.ibm.com/support/docview.wss?uid=swg27013754]\nRational Application Developer v5.x/6.x Best Practices [http://www.ibm.com/support/docview.wss?uid=swg27013752]", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q103", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "ERROR; [13/01/2015 08:49:19]; BLL;\ncom.ibm.gre.engine.ejb.business.util.RecordHostCallAdapter.onUpdate(Reco\nrdHostCallAdapter.java:200);\n\nHost exception:\njava.rmi.NoSuchObjectException: CORBA OBJECT_NOT_EXIST 0x0 No; nested\nexception is: org.omg.CORBA.OBJECT_NOT_EXIST: java.rmi.NoSuchObjectException:\nStateful bean BeanId(rmecmhost.RMECMRemoteHost#RemoteHostEJB.jar#MyRemoteHost,\nE3EE523F-014A-4000-E000-2120AC110170) was removed or timed out. vmcid:\n0x0 minor code: 0 completed: No", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q103", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "Session access timed out", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q103", "section_id": 2, "heading": "ENVIRONMENT", "parent": null, "text": "IBM Records Manager 8.5\nWindows 2008 R2", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q103", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Set this by selecting\nApplication servers > {servername} > Process definition > Java Virtual Machine > Custom properties\nThere should be defaulted entries, such as UseEJB61FEPScanPolicy.\nSelect \"New\" then add the property name\ncom.ibm.websphere.ejbcontainer.defaultSessionAccessTimeout and the desired value, 30000 and save the property.\nA JVM restart will be required in order to pick up the new property and value.\ncom.ibm.websphere.ejbcontainer.defaultSessionAccessTimeout = 30000", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q103", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "java.net.SocketTimeoutException; standalone; federated; wp-modify-ldap-security; wp-create-ldap TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q103", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The ConfigTrace.log file will display messages similar to the following:\n\n[wplc-create-federated-ldap-server] com.ibm.websphere.wim.exception.WIMConfigurationException: CWWIM5020E Could not connect to the ldap://myldapserver.example.com:389 repository\nusing properties:[derefAliases=always],[authentication=simple],[sslConfiguration=], [connectTimeout=0],[sslEnabled=false],[id=myldap],[certificateMapMode=EXACT_DN],\n[certificateFilter=],[ldapServerType=IDS],[bindPassword=****],[referal=ignore],[bindDN=cn=root],[host=myldapserver.example.com],[connectionPool=true],[port=389],\n[wplc-create-federated-ldap-server] Caused by: javax.naming.CommunicationException:myldapserver.example.com:389 [Rootexception is java.net.SocketTimeoutException: connect timed out]\n[wplc-create-federated-ldap-server] Caused by: java.net.SocketTimeoutException: connect timed out", "logical_doc_id": 4, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q103", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "In a standalone configuration, the Portal server is unable to communicate with the LDAP server.\n\nIn a clustered configuration, the Portal server and/or the Deployment Manager are unable to communicate with the LDAP server.", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q103", "section_id": 2, "heading": "DIAGNOSING THE PROBLEM", "parent": null, "text": "1) Collect and submit logs and configuration data as outlined in the following document: [http://www-304.ibm.com/support/docview.wss?uid=swg21447938]\n\nConfiguring Security for Portal [http://www-304.ibm.com/support/docview.wss?uid=swg21447938]\n\n2) Recommended but optional: Download a third-party tool (such as the ldapsearch [http://www-01.ibm.com/support/docview.wss?uid=swg21113384] tool) that can verify your server(s) are able to communicate with the LDAP server independent of the Portal ConfigEngine configuration task. Run the tool directly from the Portal server (and Deployment Manager if clustered) to verify all servers can communicate with the LDAP server.", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q103", "section_id": 3, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "In this particular use case, a network firewall was configured to block all traffic to the LDAP server except from IP addresses that were explicitly whitelisted / permitted to connect. The primary Portal server had been configured in the network firewall to communicate with the LDAP server, but the Deployment Manager had not been configured. Adding the Deployment Manager IP address to the firewall rules allowed the configuration task to complete successfully.", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q103", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "Portal v7 Infocenter: Configure Federated LDAP [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Adding_an_LDAP_user_registry_on_AIX_wp7]\nPortal v7 Infocenter: Configure Standalone LDAP [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Configuring_a_standalone_LDAP_user_registry_on_AIX_wp7]\nldapsearch [http://www-01.ibm.com/support/docview.wss?uid=swg21113384]\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", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q103", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Debug; WTE 6.1; Spring; BeanCreationException; GenericSignatureFormatError; Bugzilla; 207186; 1289491 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When running Junits tests in conjunction with the Spring framework, starting the IBM\u00ae WebSphere\u00ae Test Environment (WTE) v6.1 in debug mode within IBM\u00ae Rational\u00ae Application Developer (RAD) fails with BeanCreationException and GenericSignatureFormatError exceptions.", "logical_doc_id": 5, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q103", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "Here is an example of the exception that gets raised:\n*\n* Exception caught while initializing context org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'valueListDao' defined in ServletContext resource [/WEB-INF/context/applicationContext.xml]: Initialization of bean failed;nested exception is java.lang.reflect.GenericSignatureFormatError Caused by:java.lang.reflect.GenericSignatureFormatError", "logical_doc_id": 6, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q103", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The cause of the problem is a defect in IBM Java\u2122 Virtual Machine (JVM) versions prior to v5.0.0 SR6, as detailed in the Bugzilla links in the Related information section.", "logical_doc_id": 6, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q103", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "To resolve this error, update the WTE 6.1 with fixpack 13 or above (see the links in the Related information) and the related Java\u2122 SDK 1.5.0 SR6 using the associated v6.1 Maintenance Download Wizard from the related link.", "logical_doc_id": 6, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q103", "section_id": 3, "heading": "RELATED INFORMATION", "parent": null, "text": "#Bugzilla 207186 [https://bugs.eclipse.org/bugs/show_bug.cgi?id=207186]\nWebSphere fixpacks [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nCross Reference information Segment Product Component Platform Version Edition Software Development Rational Software Architect Debugging Applications Windows 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4 All Editions", "logical_doc_id": 6, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q248", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "SUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q248", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Description : Assembly Relation Position Matrix reverts to\n Identity after versioning a Component Assembly.\n We have found\n a number of Component Assemblies, where the details of the\n Component Assembly Relation Position Matrix reverts back to\n Identity after the Part is Versioned.\n We have not been able\n to identify a repeatable scenario. We understand the\n difficulty in not having a reproducable scenario.\n I am\n including a sample SQL script and its output for Part number\n 403Z1348-7. You will see that in version ---, the Assembly\n Relationships have positioning. In --A, the Assembly\n Relationships revert back to Identity. Version --B is In Work\n and being used by the Engineer to correct the Instances\n created with Version --A.\n Without a reproducable scenario,\n this is difficult to debug. However, this same part number\n should exist in the recent data rerfresh and Workplace. You\n should be able to see the postion shift in that data\n refresh.\n I am opening this CR to begin communication on the\n issue. We are analyzing additional data and interviewing\n Designers as to what actions they may have been doing when\n this occured.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q248", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Description : Assembly Relation Position Matrix reverts to\n Identity after versioning a Component Assembly.\n We have found\n a number of Component Assemblies, where the details of the\n Component Assembly Relation Position Matrix reverts back to\n Identity after the Part is Versioned.\n We have not been able\n to identify a repeatable scenario. We understand the\n difficulty in not having a reproducable scenario.\n I am\n including a sample SQL script and its output for Part number\n 403Z1348-7. You will see that in version ---, the Assembly\n Relationships have positioning. In --A, the Assembly\n Relationships revert back to Identity. Version --B is In Work\n and being used by the Engineer to correct the Instances\n created with Version --A.\n Without a reproducable scenario,\n this is difficult to debug. However, this same part number\n should exist in the recent data rerfresh and Workplace. You\n should be able to see the postion shift in that data\n refresh.\n I am opening this CR to begin communication on the\n issue. We are analyzing additional data and interviewing\n Designers as to what actions they may have been doing when\n this occured.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q248", "section_id": 4, "heading": "COMMENTS", "parent": null, "text": "There is a utility in existence already that can repair the\n missing data. \"Unreproducible\" in this case simply means that\n the repair already exists and there is no need for a new code\n delivery.\n THE PROBLEM WAS SUBMITTED ON :\n VERSION\n V5R18.\n THIS PROBLEM IS NOT REPRODUCIBLE ON :\n VERSION V5R19\n SP6.\n Additional Closure Information:\n There is a utility in\n existence already that can repair the missing data.\n \"Unreproducible\" in this case simply means that the repair\n already exists and there is no need for a new code\n delivery.\n THE PROBLEM WAS SUBMITTED ON :\n VERSION\n V5R18.\n THIS PROBLEM IS NOT REPRODUCIBLE ON :\n VERSION V5R19\n SP6.\n To run the repair utility, use the following\n documentation:\n Inside catstart,\n CorrectARMatrixPos -user\n USERNAME -pwd PASSWORD -vid PARTNUMBER -version VERSIONSTRING\nreport REPORTFILE\nsimul | -delete\nuser USERNAME\n : user name\npwd PASSWORD\n : user password\nvid PARTNUMBER\n : User have to specify parent part number\n having child part with wrong matrix position\nversion\n VERSIONSTRING : User have to specify\n version string for parent part having child part with wrong\n matrix position\nreport REPORTFILE : Tool will\n create reports containing document name which is link to parts\n are not ok and will be deleted.\ndelete\n : Run the tool and\n delete the invalid property. If not specified, simulation\n mode will be used.\nsimul\n :\n Run the tool without committing changes to database. This\n option is assumed\n unless\ndelete is given.\n Return code signification:\n 0\n : Quitting the application successfully\n 1\n : Failed to get the session\n 2 : Bad input\n parameter\n 3 : Failed to create or write to report\n file.\n In the lab we corrupted a database to simulate the\n corruption at customer site, and then ran this utility in R19.\n It corrected the data.", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q248", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n HD88448\nREPORTED COMPONENT NAME\n ENOVIA V5 VPM N\nREPORTED COMPONENT ID\n 569151400\nREPORTED RELEASE\n 518\nSTATUS\n CLOSED UR1\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2009-09-03\nCLOSED DATE\n 2009-09-28\nLAST MODIFIED DATE\n 2009-10-27\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q248", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n ENOVIA V5 VPM N\nFIXED COMPONENT ID\n 569151400", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q248", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R519 PSN SP51906\n UP09/10/27 I 1000\n\nA FIX IS AVAILABLE\nDownload Information: Version 8.1.0 IBM Spectrum Protect for Virtual Environments [http://www-01.ibm.com/support/docview.wss?uid=swg24042955]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q248", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Validate nodes from the Data Protection for VMware GUI reports a\n successful message, but also reports an error icon.\n The success message reported is:\n ANS0302I (RC0) Successfully done.\n However, a red X icon next the node name suggests an error.\n This behavior can occur when there are no VM guests in the\n environment.\n Customer/L2 Diagnostics:\n Review the messages.log file located in C:\\IBM\\tivoli\\tsm\\\n tdpvmware\\webserver\\usr\\servers\\veProfile\\ VMwarePlugin\\logs\n for the following:\n [4/13/16 8:51:41:227 PDT] 000000d0 SystemOut\n O DONE [10]: vmcli.cmd -f inquire_detail -t TSM -q dmverify -d\n -o , 7.049 seconds\n [4/13/16 8:51:41:773 PDT] 0000002e SystemOut\n O [queryDMVerify] Synchronous return code: 2\n Running the inquire_detail command manually will result in the\n following:\n #ERROR ANS0302I (RC0) Successfully done.\n #ERROR\n #PARAM STATUS=success\n Initial Impact: Low\n Tivoli Storage Manager Versions Affected:\n All IBM Spectrum Protect Data Protection for VMware levels on\n Windows and Linux.\n Additional Keywords:\n TSM TDP VE plugin", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q248", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "Create a dummy VM guest to bypass the error.", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q248", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nTivoli Storage Manager for Virtual Environments Data *\nProtection for VMware versions 7.1, 6.4 and 6.3 running on *\nall Microsoft Windows x64 and Linux x86_64 platforms *\n\nPROBLEM DESCRIPTION: *\nSee ERROR DESCRIPTION *\n\nRECOMMENDATION: *\n- *", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q248", "section_id": 4, "heading": "COMMENTS", "parent": null, "text": "If there is a next release of IBM Spectrum Protect after 7.1,\n this APAR will be fixed in that next release.", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q248", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT15182\nREPORTED COMPONENT NAME\n TSM FOR VE DP V\nREPORTED COMPONENT ID\n 5725TVEVM\nREPORTED RELEASE\n 71W\nSTATUS\n CLOSED FIN\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-05-09\nCLOSED DATE\n 2016-06-13\nLAST MODIFIED DATE\n 2016-06-13\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n\nMODULES/MACROS\ntsmcli", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q248", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R71W PSN\n UP\nR71L PSN\n UP\nR64W PSN\n UP\nR64L PSN\n UP\nR63W PSN\n UP\nR63L PSN\n UP", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q248", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "What is the exact data acquired by the ILMT Agent and from VM Manager?", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q248", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "1. What data is acquired from Agent\n\nGenerally from the agent the below data is acquired:\nhostname\nip_address\nagent id\nprocessor type of the node (if it is possible to retrieve it from the system)\nlogical processor cores count on the partition\nprocessors cores count on the node (if possible)\nserial number of the machine (for bare metal) and/or\nUUID of the virtual machine etc.\n\nIn order to check the exact data that the agent is generating and sending to the server you can check the content of the /scanner/tlm_hw_output.gz (output from the hardware scan) and /scanner/tlm_local_sw_output.gz (output from the software scan) files.\n\n2. What data is acquired from VM Manager.\n\nGenerally in VIRT schema the RAW data retrieved from VM Manager (ESX server / vCenter) are kept. We are retrieving this data using the VMWare Web Services SDK (a Java API version of it). Next the data from the VIRT schema is being processed and stored in different tables in ADM schema (like ADM.NODE or ADM.MEASURE).\n\nData about the virtual machines (VIRT.GUEST) like:\nUUID of the VM (EXT_ID)\nparent ID (id of the host or cluster)\nnumber of the logical processor cores assigned to the virtual machines (CPU_NUMBER)\n\nData about host/servers (VIRT.HOST):\nUUID of the server (EXT_ID) - VirtualMachine.config.uuid (from VMWare API)\nparent ID (cluster or VM Manager)\nhardware vendor\nhardware model\nprocessor vendor\nprocessor name / description\nnumber of physical processors on the host\nnumber of cores\nconnection state (CONNECTED - 0, DISCONNECTED - 1, NOT_RESPONDING - 2) - only the connected once are used to the following processing - HostSystem.runtime.connectionState (from VMWare API)\n\nData about the clusters (Virt.CLUSTER):\ncluster name\nparent ID (id of the VM Manager)\n\nNot all data which was retrieved from VM Manager is used for calculation or building the virtual topology - some of the data are being retrieved only to check the accuracy of the data. Additionally the data in the VIRT schema is not stored permanently - it is being rewritten during each VM Manager connection task (by default each 30 minutes). Only the data in ADM schema are 'permanent' and used for PVU calculations.\n\nz/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q248", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Multiple issues running the CKRCARLA COMPAREOPT function", "logical_doc_id": 4, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q248", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of zSecure Manager for RACF z/VM *\nexploiting compare processing. *\n\nPROBLEM DESCRIPTION: zSecure Manager for RACF z/VM has *\nvarious issues regarding compare *\nprocessing. *\n\nRECOMMENDATION: Apply the PTF provided. *\n\nzSecure Manager for RACF z/VM has various issues regarding\n compare processing:\na problem where the input data set type (RACF database,\n UNLOAD, CKFREEZE) is confused with the input data set\n security product (can be observed on CKR0615 message);\nprogramming error that can result in MSGCKR1967 while SUMMARY\n CARLa statement is being processed;\n Beside that zSecure Manager for RACF z/VM compare processing has\n been improved to have a better notion of an allocated BASE input\n set, and better definitions for the default comparison\n properties (COMAREOPT CARLa statement) as used in the zSecure\n user interface.", "logical_doc_id": 4, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q248", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "zSecure Manager for RACF z/VM has been adjusted in order to have\n an improved and corrected comparison processing.\nPLEASE NOTE the following documentation changes for\n Security zSecure Version 1.13 Messages Guide (SC14-7667-00).\nChapter 5. CKR messages\n\nFollowing messages have been added:\n\nCKR2427 Automatic compare ignored for newlist type= at\n line .\n Severity: 0\n Explanation: An automatic compare was specified using\n FUNCTION=BASE on an ALLOC statement, but this\n newlist type does not support an automatic compare.\n The newlist will be processed as if no\n FUNCTION=BASE was specified on an ALLOC statement.\n COMPARE_RESULT and COMPARE_CHANGES fields are\n allowed, but will return a blank value. No\n filtering will take place because of COMPAREOPT\n SHOW processing.\n User response: To explicitly request that this newlist perform\n a compare operation, you must define your own\n compare operation. See \"Compare processing\" in\n the User Reference Manual.\n\nCKR2428 Default compare requires compare fields in newlist\n type= at line .\n Severity: 12\n Explanation: A compare was specified for this newlist type using\n COMPAREOPT=DEFAULT on the NEWLIST statement.\n However, the internal knowledge base is missing\n fields to compare. To use this newlist to compare,\n create a COMPAREOPT statement that defines which\n fields to compare. You might also need to specify\n the BY and BASE fields.\n User response: See \"Compare processing\" in the User Reference\n Manual for information on creating comparison\n operations.\n\nCKR2506 Internal error: automatic compare requires compare\n fields in newlist type= at line .\n Severity: 24\n Explanation: The internal knowledge base for this newlist type\n contains an inconsistency. It supports automatic\n comparison, but it has no defined fields to\n compare.\n User response: See the Electronic Support Web site for possible\n maintenance associated with this message. If you\n cannot find applicable maintenance, contact IBM\n Software Support. You can still use this newlist\n for comparing by creating a COMPAREOPT statement\n with a correct compare specification. See\n \"Compare processing\" in the User Reference Manual\n for information on creating comparison\n operations.", "logical_doc_id": 4, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q248", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "CKR2507 Internal error: Default compare base field not\n supported. (Only COMPLEX and SYSTEM.) Newlist\n type=.\n Severity: 24\n Explanation: The internal knowledge base for this newlist type\n contains an inconsistency. The indicated field is\n defined as a base field, but only the COMPLEX and\n SYSTEM fields are allowed as base fields.\n User response: See the Electronic Support Web site for possible\n maintenance associated with this message. If you\n cannot find applicable maintenance, contact IBM\n Software Support. You can still use this newlist\n for comparing by creating a COMPAREOPT statement\n with a correct compare specification. See\n \"Compare processing\" in the User Reference Manual\n for information on creating comparison\n operations.\n\nFollowing messages have been removed:\n\nCKR1464, CKR1473, and CKR1508.\n 1B1Y\n CKAFDEF\n CKASMRD\n CKRADSN\n CKRALLOC\n CKRCOMP\n CKRFDEF\n CKRFLDT\n CKRINP@\n CKRINPA\n CKRINPE\n CKRMAIN\n CKROUFLD\n CKRSMMO\n CKRSYDB\n C2RDFLD\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q248", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n VM18480\nREPORTED COMPONENT NAME\n TIV ZSECMGR-RAC\nREPORTED COMPONENT ID\n 5655T1300\nREPORTED RELEASE\n 1B1\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2012-08-09\nCLOSED DATE\n 2012-10-16\nLAST MODIFIED DATE\n 2012-10-31\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n UV61175\n\nMODULES/MACROS\nCKAFDEF CKASMRD CKRADSN CKRALLOC CKRCOMP\n CKRFDEF CKRFLDT CKRINP@ CKRINPA CKRINPE CKRMAIN CKROUFLD\n CKRSMMO CKRSYDB C2RDFLD", "logical_doc_id": 4, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q248", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n TIV ZSECMGR-RAC\nFIXED COMPONENT ID\n 5655T1300", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q248", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R1B1 PSY UV61175 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UV61175]\n UP12/10/18 P 1210\n\nFIX IS AVAILABLE\nSELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL. YOU WILL BE REQUIRED TO SIGN IN. DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES.", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q248", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Version 8.5 Refresh Pack 5 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24037683]\nDownload Version 8.0.1 Fix Pack 3 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24037734]\nVersion 8.5.0 Fix Pack 2 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24040683]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q248", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When the flow control leads back to the same coach, the runtime\n passes the list of changed variables to the coach processing.\n However, the variable snapshot taken to compare the changes\n against is taken after the post-assignments have been\n processed. This results in the message not appearing in the\n list of changed variables.\n\nServer log after 'sample coach' is first loaded:\n [9/25/13 12:39:24:577 EDT] 00000290 wle_servlet I\n CWLLG0006I:\n Initializing a new session.\n [9/25/13 12:39:24:588 EDT] 00000290 wle_security I\n CWLLG1088I:\n Initializing session is done for user tw_admin\n [9/25/13 12:39:24:598 EDT] 00000290 wle_javascrip I sample\n coach\n pre-execution start, errorMessage=
This Excel file\n has missing headers. Please check the file and try again
\n\nServer log after button 'Clear Message' is pressed:\n [9/25/13 12:39:25:734 EDT] 00000290 wle_security I\n CWLLG1088I:\n Initializing session is done for user tw_admin\n [9/25/13 12:39:29:808 EDT] 000000c8 wle_javascrip I sample\n coach post-execution start, errorMessage=
This Excel file\n has missing headers. Please check the file and try again
\n [9/25/13 12:39:29:808 EDT] 000000c8 wle_javascrip I sample\n coach post-execution end, errorMessage=from post\n [9/25/13 12:39:29:811 EDT] 000000c8 wle_javascrip I sample\n coach pre-execution start, errorMessage=from post\n\nHence, the value of errorMessage is updated to \"from post\" on\n the server. Yet, the delta returned with the boundary event of\n 'Clear Message' does not reflect that update, which is the\n reason the user's coach views are not notified of the change:\n\nThis is the data sent with the POST to server:\n {\"boundaryEventInfo\":{\"boundaryEventId\":\"boundaryEvent_2\",\"bound\n aryEvent\n EndStateId\":\"6135cc91-c33d-4c0a-9e53-ced2c36996f7\",\"fireValidati\n on\":\"0\"}\n ,\"stateInfo\":{\"zComponentId\":\"3028.a2d31d42-cd85-4f83-ad47-65a87\n 636ae23\"\n ,\"zComponentName\":\"CoachNG\",\"zTaskId\":\"p1\",\"zWorkflowState\":\"3\",\n \"applicationId\":\"2\",\"applicationInstanceId\":\"guid:6df52810907a6b\n 87:-7b76\n 6002:141328e00fe:-7ffe\",\"zDbg\":\"0\"},\"data\":{\"local\":{\"coachHeade\n r\":\"TestProcess1\",\"errorMessage\":\"
This Excel\n file has missing headers. Please check the file and try\n again
\"}}}\n\nThis is the data sent back to the browser with the response\n (Note: no\n errorMessage in it):\n {\"delta\":{\"tw.local.coachHeaderUpdate\":\"Coach header\n updated\",\"tw.local.coachHeader\":\"Coach header\n updated\"},\"event\":\"taskDataChanged\"}\n ", "logical_doc_id": 5, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q248", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "==>Variables that are changed in the post-assignment script are\n ignored when the flow control returns to the same coach.\n\nEDITIONS AFFECTED:\n ==>IBM Business Process Manager Advanced, Standard, and Express\n\nPROBLEM DETAILED DESCRIPTION:\n ==>During the boundary event handling, a snapshot of the\n variables that includes in the post-assignment script is taken\n too late. As a result, when the flow controls returns to the\n same coach the delta logic misses the changes in the\n post-assignment script.", "logical_doc_id": 5, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q248", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "==>A fix is available for IBM BPM V8.0.1.1, V8.0.1.2 and\n V8.5.0.1 that fix ensures that the post-assignment script runs\n properly when the flow control leads back to the same coach.\n\nOn Fix Central (http://www.ibm.com/support/fixcentral), search\n for JR48553:\n\n1. Select the product group, product, installed version, and\n platform and click Continue.\n 2. Select APAR or SPR, enter JR48553, and click Continue.\n\nWhen downloading fix packages, ensure that you also download the\n readme file for each fix. Review each readme file for additional\n installation instructions and information about the fix.\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q248", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR48553\nREPORTED COMPONENT NAME\n BPM STANDARD\nREPORTED COMPONENT ID\n 5725C9500\nREPORTED RELEASE\n 801\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-11-19\nCLOSED DATE\n 2013-12-19\nLAST MODIFIED DATE\n 2014-09-05\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q248", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM STANDARD\nFIXED COMPONENT ID\n 5725C9500", "logical_doc_id": 5, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q248", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R801 PSY\n UP", "logical_doc_id": 5, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q074", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere Application Server is shipped as a component of IBM SOA Policy Gateway Pattern for AIX Server 2.5 and IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server. Information about a security vulnerability affecting IBM WebSphere Application Server has been published in a security bulletin.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q074", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Please consult the security bulletin:\nSecurity Bulletin: HTTP response splitting attack in WebSphere Application Server (CVE-2015-2017) [http://www.ibm.com/support/docview.wss?uid=swg21966837]\n\nfor vulnerability details and information about fixes.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q074", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM SOA Policy Gateway Pattern for AIX Server 2.5\nIBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5\nIBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.0\n\nAll affected by IBM WebSphere Application Server V8.0", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q074", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q074", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] CHANGE HISTORY\n 03 November 2015: Original document published\nThe 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.", "logical_doc_id": 0, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q074", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere Application Server, IBM HTTP Server, IBM DB2, IBM SPSS Modeler, IBM Cognos Business Intelligence Server, IBM SPSS Collaboration and Deployment Services and IBM WebSphere MQ are shipped as components of IBM Predictive Maintenance and Quality. Information about a security vulnerability affecting IBM WebSphere Application Server, IBM HTTP Server, IBM DB2, IBM SPSS Modeler, IBM Cognos Business Intelligence Server, IBM SPSS Collaboration and Deployment Services and IBM WebSphere MQ has been published their respective security bulletins.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q074", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Please consult the Security Bulletin: Vulnerability in RC4 stream cipher affects WebSphere Application Server (CVE-2015-2808) [http://www-01.ibm.com/support/docview.wss?uid=swg21701503] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Vulnerability in RC4 stream cipher affects IBM HTTP Server (CVE-2015-2808) [http://www-01.ibm.com/support/docview.wss?uid=swg21701072] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Vulnerability in RC4 stream cipher affects IBM DB2 (CVE-2015-2808) [https://www-304.ibm.com/support/docview.wss?uid=swg21717865] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Vulnerability in RC4 stream cipher affects IBM SPSS Modeler (CVE-2015-2808) [http://www-01.ibm.com/support/docview.wss?uid=swg21882559] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Vulnerability in RC4 stream cipher affects IBM Cognos Business Intelligence Server (CVE-2015-2808) [http://www-01.ibm.com/support/docview.wss?uid=swg21715530] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Vulnerability in RC4 stream cipher in IBM SDK Java Technology Edition, Versions 1.6 and 1.7 affects IBM SPSS Collaboration and Deployment Services (CVE-2015-2808) [http://www-01.ibm.com/support/docview.wss?uid=swg21883440&myns=swgimgmt&mynp=OCSS69YH&mync=E&cm_sp=swgimgmt-_-OCSS69YH-_-E] for vulnerability details and information about fixes.\n\nPlease consult the Security Bulletin: Vulnerability in RC4 stream cipher affects IBM WebSphere MQ (CVE-2015-2808) [http://www-01.ibm.com/support/docview.wss?uid=swg21883551&myns=swgws&mynp=OCSSFKSJ&mync=E&cm_sp=swgws-_-OCSSFKSJ-_-E] for vulnerability details and information about fixes.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q074", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Principal Product and Version(s) Affected Supporting Product and Version IBM Predictive Maintenance and Quality 1.0\n\nIBM Predictive Maintenance and Quality 2.0\n\nIBM Predictive Maintenance and Quality 2.5 IBM WebSphere Application Server v8.0\nIBM HTTP Server v8.0\nIBM DB2 Enterprise Server Edition 9.7.0.7\nIBM SPSS Modeler Server 15.0\nIBM Cognos Business Intelligence Server 10.2\nIBM SPSS Collaboration and Deployment Services 5.0\nIBM WebSphere MQ 7.5\n\nIBM WebSphere Application Server v8.5.5\nIBM HTTP Server v8.0\nIBM DB2 Enterprise Server Edition 10.1.0.3\nIBM SPSS Modeler Server 16.0\nIBM Cognos Business Intelligence Server 10.2.1\nIBM SPSS Collaboration and Deployment Services 6.0\nIBM WebSphere MQ 7.5.0.2\n\nIBM WebSphere Application Server v8.5.5.3\nIBM HTTP Server v8.5.5.3\nIBM DB2 Enterprise Server Edition 10.5.0.4\nIBM SPSS Modeler Server 16.0.0.1\nIBM Cognos Business Intelligence Server 10.2.2\nIBM SPSS Collaboration and Deployment Services 6.0.0.1\nIBM WebSphere MQ 7.5.0.4 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.", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q074", "section_id": 3, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] CHANGE HISTORY\n May 5, 2015: Original Version Published\nThe 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\nCVE-2016-0729; CVE-2016-4463; CVE-2016-5995; CVE-2016-0215; CVE-2015-4872; CVE-2015-4893; CVE-2015-4803; CVE-2016-0201; CVE-2015-7420; CVE-2015-7421; CVE-2015-0138; CVE-2015-0159; CVE-2014-6221; CVE-2014-8730; CVE-2015-2808; CVE-2015-1788; CVE-2015-4000. CVE-2015-0204; CVE-2015-1947; CVE-2016-0201; CVE-2015-7420; CVE-2015-7421 SECURITY BULLETIN", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q074", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM DB2 Enterprise Server Edition is shipped as a component of IBM Cloud Orchestrator, IBM Cloud Orchestrator Enterprise, IBM SmartCloud Orchestrator, and IBM SmartCloud Orchestrator Enterprise.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q074", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "Consult the following security bulletins for IBM DB2 Enterprise Server Edition for vulnerability details and information about fixes.\nSecurity Bulletin: IBM\u00ae DB2\u00ae LUW is vulnerable to Sweet32 Birthday Attack (CVE-2016-2183) [http://www-01.ibm.com/support/docview.wss?uid=swg21994375]\nFlash DB2 Version 10.1, End of Support September 30, 2017 [http://www.ibm.com/support/docview.wss?uid=swg22001885&myns=swgimgmt&mynp=OCSSEPGG&mync=E&cm_sp=swgimgmt-_-OCSSEPGG-_-E]\nSecurity Vulnerabilities, HIPER and Special Attention APARs fixed in DB2 for Linux, UNIX, and Windows Version 10.5 [http://www-01.ibm.com/support/docview.wss?uid=swg21647054]\n[http://www-01.ibm.com/support/docview.wss?uid=swg21610582]Security Vulnerabilities, HIPER and Special Attention APARs fixed in DB2 for Linux, UNIX, and Windows Version 10.1 [http://www-01.ibm.com/support/docview.wss?uid=swg21610582]\nSecurity Bulletin: Vulnerabilty in XMLC affects IBM\u00ae DB2\u00ae LUW (CVE-2016-0729, CVE-2016-4463) [http://www-01.ibm.com/support/docview.wss?uid=swg21984685]\nSecurity Bulletin: Local escalation of privilege vulnerability in IBM\u00ae DB2\u00ae (CVE-2016-5995) [http://www-01.ibm.com/support/docview.wss?uid=swg21990061]\nSecurity Bulletin: IBM\u00ae DB2\u00ae LUW contains a denial of service vulnerability using a SELECT statement with subquery containing the AVG OLAP function on Oracle compatible database (CVE-2016-0215) [http://www-01.ibm.com/support/docview.wss?uid=swg21979986]\nSecurity Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM DB2 Accessories Suite for Linux, UNIX and Windows (CVE-2015-4872, CVE-2015-4893, CVE-2015-4803) [http://www-01.ibm.com/support/docview.wss?uid=swg21988938]\nSecurity Bulletin: Vulnerabilities in the GSKit component of IBM\u00ae DB2\u00ae LUW (CVE-2016-0201, CVE-2015-7420 & CVE-2015-7421) [http://www-01.ibm.com/support/docview.wss?uid=swg21977787]\nSecurity Bulletin: Vulnerabilities in GPFS affect IBM\u00ae DB2\u00ae LUW on AIX and Linux (CVE-2015-4974, CVE-2015-4981 & CVE-2015-7403) [http://www-01.ibm.com/support/docview.wss?uid=swg21972152]\nSecurity Bulletin: IBM\u00ae DB2\u00ae LUW contains a denial of service vulnerability in which a malformated DRDA message may cause the DB2 server to terminate abnormally (CVE-2016-0211) [http://www-01.ibm.com/support/docview.wss?uid=swg21979984]\nSecurity Bulletin: IBM\u00ae DB2\u00ae LUW contains a denial of service vulnerability using a SELECT statement with subquery containing the AVG OLAP function on Oracle compatible database (CVE-2016-0215) [http://www-01.ibm.com/support/docview.wss?uid=swg21979984]\nSecurity Bulletin: Vulnerability in IBM Java SDK affects IBM\u00ae DB2\u00ae LUW (CVE-2015-7575) [http://www-01.ibm.com/support/docview.wss?uid=swg21976363]\nSecurity Bulletin: Local escalation of privilege vulnerability in IBM DB2 LUW (CVE-2015-1947) [https://www-304.ibm.com/support/docview.wss?uid=swg21970376]\nSecurity Bulletin: Vulnerability in OpenSSL affect IBM DB2 (CVE-2015-0204) [www-01.ibm.com/support/docview.wss?uid=swg21968869] [http://www-01.ibm.com/support/docview.wss?uid=swg21967893]\n\n[http://www-01.ibm.com/support/docview.wss?uid=swg21967893] * Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM DB2 (CVE-2015-4000) [http://www-01.ibm.com/support/docview.wss?uid=swg21967893]\nSecurity Bulletin: Vulnerability in OpenSSL affects IBM DB2 (CVE-2015-1788) [http://www.ibm.com/support/docview.wss?uid=swg21964766&myns=swgimgmt&mynp=OCSSEPGG&mync=E&cm_sp=swgimgmt-_-OCSSEPGG-_-E]\nSecurity Bulletin: Vulnerabilities in GSKit affect IBM DB2 (CVE-2015-0138, CVE-2015-0159 and CVE-2014-6221) [http://www.ibm.com/support/docview.wss?uid=swg21699543]\nSecurity Bulletin: TLS padding vulnerability affects IBM DB2 LUW (CVE-2014-8730) [http://www.ibm.com/support/docview.wss?uid=swg21692618]\nSecurity Bulletin: Vulnerability in RC4 stream cipher affects IBM DB2 LUW (CVE-2015-2808) [http://www.ibm.com/support/docview.wss?uid=swg21717865]\nSecurity Bulletin: A vulnerability in the GSKit component of IBM Tivoli Monitoring (CVE-2015-1788) [http://www-01.ibm.com/support/docview.wss?uid=swg21997156]", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q074", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "Principal Product and Version Affected Supporting Product and Version IBM Cloud Orchestrator 2.5, 2.5.0.1, 2.5.0.1 Interim Fix 1, 2.4.0.2, 2.4.0.3 IBM Cloud Orchestrator Enterprise 2.5, 2.5.0.1, 2.5.0.1 Interim Fix 1, 2.4.0.2, 2.4.0.3\n\nIBM DB2 Enterprise Server Edition 10.5.0.5 IBM Cloud Orchestrator 2.4, 2.4.0.1, 2.4.0.2 IBM Cloud Orchestrator Enterprise 2.4, 2.4.0.2\n\nIBM DB2 Enterprise Server Edition 10.5.0.2 IBM SmartCloud Orchestrator 2.3 IBM SmartCloud Orchestrator Enterprise 2.3\n\nIBM DB2 Enterprise Server Edition 10.1 IBM SmartCloud Orchestrator 2.3.0.1 IBM SmartCloud Orchestrator Enterprise 2.3.0.1\n\nIBM DB2 Enterprise Server Edition 10.5 GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q074", "section_id": 3, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide]\nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q074", "section_id": 4, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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\n13 January 2017: Included IBM Tivoli Monitoring security bulletin\n15 September 2016 : Last update new bulletins\n27 June 2016: Last update new bulletins\n30 April 2015: Original copy published\nThe 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.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q074", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "A vulnerability in WebSphere Application Server could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions.", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q074", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2015-1920 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1920]\nDESCRIPTION: WebSphere Application Server could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions.\nCVSS Base Score: 9.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/102404 [https://exchange.xforce.ibmcloud.com/vulnerabilities/102404] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:C/I:C/A:C)", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q074", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "IBM SOA Policy Gateway Pattern for AIX Server version 2.5", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q074", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Customers should install WebSphere Application Server Interim Fix PI38302 [http://www-01.ibm.com/support/docview.wss?uid=swg24039898]", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q074", "section_id": 5, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q074", "section_id": 6, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q074", "section_id": 7, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]\nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]\n\nACKNOWLEDGEMENT\nNone\n\nCHANGE HISTORY\n 8 June 2015: Original document published.\nThe 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\nCVE-2015-1920 SECURITY BULLETIN", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q074", "section_id": 0, "heading": "SUMMARY", "parent": null, "text": "IBM WebSphere Application Server and WebSphere Application Server Hypervisor Edition could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions.", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q074", "section_id": 1, "heading": "VULNERABILITY DETAILS", "parent": null, "text": "CVEID: CVE-2015-1920 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1920]\nDESCRIPTION: WebSphere Application Server could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions.\nCVSS Base Score: 9.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/102404 [https://exchange.xforce.ibmcloud.com/vulnerabilities/102404] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:C/I:C/A:C)", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q074", "section_id": 2, "heading": "AFFECTED PRODUCTS AND VERSIONS", "parent": null, "text": "SmartCloud Cost Management 2.1 and 2.1.0.1\nTivoli Usage and Accounting Manager 7.3 including all related fix packs", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q074", "section_id": 3, "heading": "REMEDIATION/FIXES", "parent": null, "text": "Review security bulletin Security Vulnerability in IBM WebSphere Application Server (CVE-2015-1920) [http://www-01.ibm.com/support/docview.wss?uid=swg21883573]for details.", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q074", "section_id": 4, "heading": "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS", "parent": null, "text": "Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q074", "section_id": 5, "heading": "REFERENCES", "parent": null, "text": "Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]\nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q074", "section_id": 6, "heading": "RELATED INFORMATION", "parent": null, "text": "IBM 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]\nThe 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\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli Usage and Accounting Manager Enterprise Edition AIX, Linux, Windows 7.3", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q270", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q270", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "This APAR updates the Java Runtime Environment (JRE) supplied\n with WebSphere MQ V7.1, V7.5 and V8.0. See below for platforms\n updated\n and to which version.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q270", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n The JRE which is embedded into WebSphere MQ is used\n to run the following Java components of the product:\n\nWebSphere MQ Managed File Transfer\n WebSphere MQ Explorer\n WebSphere MQ Extended Reach (MQXR) service\n\nPlatforms affected:\n AIX, Linux on Power, Linux on x86, Linux on x86-64, Linux on\n zSeries, Solaris SPARC, Solaris x86-64, Windows, HP-UX Itanium,\n HP-UX PA-RISC\n\nPROBLEM DESCRIPTION:\n This APAR updates the Java Runtime Environment (JRE) supplied\n with WebSphere MQ V7.1, V7.5 and V8.0. See below for platforms\n updated\n and to which version.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q270", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This APAR updates the JRE for the following platforms for\n WebSphere MQ V7.1 & V7.5:\n\nAIX - Java 6.0 (SR16-FP26)\n (6.0.16.26)\n HP-UX IA32 - Java 6.0 (SR16-FP22) (6.0.16.22)\n HP-UX IA64 - Java 6.0 (SR16-FP22) (6.0.16.22)\n Linux (x86-32) - Java 6.0 (SR16-FP26) (6.0.16.26)\n Linux (x86-64) - Java 6.0 (SR16-FP26) (6.0.16.26)\n Linux (PPC64) - Java 6.0 (SR16-FP26) (6.0.16.26)\n zLinux - Java 6.0 (SR16-FP26) (6.0.16.26)\n Solaris (x86-64) - Java 6.0 (SR16-FP25) (6.0.16.25)\n Solaris (SPARC) - Java 6.0 (SR16-FP25) (6.0.16.25)\n Windows - Java 6.0 (SR16-FP26) (6.0.16.26)\n\nAnd updates the JRE updates for the following platforms for\n WebSphere MQ V8.0:\n\nAIX - Java 7.1 (SR3-FP40) (7.1.3.40)\n HP-UX (IA32) - Java 7.0 (SR9-FP32) (7.0.9.32)\n HP-UX (IA64) - Java 7.0 (SR9-FP32) (7.0.9.32)\n Linux (x86-32) - Java 7.1 (SR3-FP40) (7.1.3.40)\n Linux (x86-64) - Java 7.1 (SR3-FP40) (7.1.3.40)\n Linux (PPC64LE) - Java 7.1 (SR3-FP40) (7.1.3.40)\n zLinux - Java 7.1 (SR3-FP40) (7.1.3.40)\n Solaris (x86-64) - Java 7.0 (SR9-FP40) (7.0.9.40)\n Solaris (SPARC) - Java 7.0 (SR9-FP40) (7.0.9.40)\n Windows (32-bit) - Java 7.1 (SR3-FP40) (7.1.3.40)\n Windows (64-bit) - Java 7.1 (SR3-FP40) (7.1.3.40)\n\nThe fix is targeted for delivery in the following PTFs:\n\nVersion Maintenance Level\n v7.1 7.1.0.8\n v7.5 7.5.0.7\n v8.0 8.0.0.5\n\nThe latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\nIf the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q270", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT14908\nREPORTED COMPONENT NAME\n WMQ WINDOWS V7\nREPORTED COMPONENT ID\n 5724H7220\nREPORTED RELEASE\n 710\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-04-22\nCLOSED DATE\n 2016-05-18\nLAST MODIFIED DATE\n 2016-05-18\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q270", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ WINDOWS V7\nFIXED COMPONENT ID\n 5724H7220", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q270", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R710 PSY\n UP\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q270", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The WebSphere MQ V7.0 installation contains a 1.5\n Java Runtime Environments (JREs), supplied within the JRE\n install component.\n\nNew revisions of this JRE are released periodically to address\n program defects, and products which embed the JRE should\n be updated accordingly.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q270", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n The JRE which is embedded into WebSphere MQ is used\n to run the following Java components of the product:\n\nGSKit graphical interface\n WebSphere MQ Explorer\n\nPlatforms affected:\n AIX, HP-UX Itanium, HP-UX PA-RISC, Linux on Power, Linux on\n S390, Linux on x86, Linux on x86-64, Linux on zSeries, Solaris\n SPARC, Solaris x86-64, Windows\n\nPROBLEM DESCRIPTION:\n This APAR updates the Java Runtime Environment (JRE) supplied\n with WebSphere MQ 7.0 to the level:\n\nJava 5.0 Service Refresh 16 Fix Pack 8 (SR16-FP8)", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q270", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This APAR updates the JRE updates for the following platforms:\n\nAIX\n HP-UX (IA64)\n HP-UX (PA-RISC)\n Linux (x86-32)\n Linux (x86-64)\n Linux PPC64\n zLinux\n Solaris (x86-64)\n Solaris (SPARC)\n Windows\n\nThe fix is targeted for delivery in the following PTFs:\n\nVersion Maintenance Level\n v7.0 7.0.1.13\n\nThe latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\nIf the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q270", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT06182\nREPORTED COMPONENT NAME\n WMQ WINDOWS V7\nREPORTED COMPONENT ID\n 5724H7220\nREPORTED RELEASE\n 701\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-12-19\nCLOSED DATE\n 2015-01-13\nLAST MODIFIED DATE\n 2015-01-13\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q270", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ WINDOWS V7\nFIXED COMPONENT ID\n 5724H7220", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q270", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R701 PSY\n UP\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q270", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The WebSphere MQ V7.1 and V7.5 installation contains a 1.6\n Java Runtime Environments (JREs), supplied within the JRE\n install component.\n\nNew revisions of this JRE are released periodically to address\n program defects, and products which embed the JRE should\n be updated accordingly.", "logical_doc_id": 3, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q270", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n The JRE which is embedded into WebSphere MQ is used\n to run the following Java components of the product:\n\nWebSphere MQ Managed File Transfer\n GSKit graphical interface\n WebSphere MQ Explorer\n WebSphere MQ Extended Reach (MQXR) service\n\nPlatforms affected:\n AIX, Linux on Power, Linux on S390, Linux on x86, Linux on\n x86-64, Linux on zSeries, Solaris SPARC, Solaris x86-64,\n Windows, HP-UX Itanium\n\nPROBLEM DESCRIPTION:\n This APAR updates the Java Runtime Environment (JRE) supplied\n with WebSphere MQ 7.1 and 7.5, to the level:\n\nJava 6.0 Service Refresh 16 Fix Pack 2 (SR16-FP2)", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q270", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "This APAR updates the JRE updates for the following platforms:\n\nAIX\n HP-UX (IA64)\n Linux (x86-32)\n Linux (x86-64)\n Linux PPC64\n zLinux\n Solaris (x86-64)\n Solaris (SPARC)\n Windows\n\nThe fix is targeted for delivery in the following PTFs:\n\nVersion Maintenance Level\n v7.1 7.1.0.7\n v7.5 7.5.0.5\n\nThe latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\nIf the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q270", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV67334\nREPORTED COMPONENT NAME\n WMQ LIN X86 V7\nREPORTED COMPONENT ID\n 5724H7224\nREPORTED RELEASE\n 710\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-11-28\nCLOSED DATE\n 2015-01-12\nLAST MODIFIED DATE\n 2015-04-24\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q270", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ LIN X86 V7\nFIXED COMPONENT ID\n 5724H7224", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q270", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R710 PSY\n UP", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q270", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "WebSphere MQ V6.0 Fix Pack 6.0.2.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24015717]\nWebSphere MQ V6.0 for iSeries Fix Pack 6.0.2.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24015718]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q270", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Customers using runmqckm or amqtcert on Windows systems may\n find that they are unable to migrate or import some SSL\n certificates when WMQ 6.0.2.1 is installed.\n\nThe most likely error message is \"the specified database has\n been corrupted\", for a certificate which can be imported\n using a version of WMQ prior to 6.0.2.1.", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q270", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n Customers using WMQ 6.0.2.1 for Windows who need to import or\n migrate certificates using keys over a certain size.\n\nPlatforms affected:\n Windows\n\nPROBLEM SUMMARY:\n WMQ 6.0.2.1 for Windows uses a Java runtime environment to run\n the GSkit SSL certificate administration commands (amqtcert,\n runmqckm/gsk7cmd). The Java runtime has some JCE policy files\n which control what strength of cryptography is permitted for use\n with GSkit administration commands.\n\n6.0.2.1 erroneously shipped an incorrect set of JCE policy\n files. Instead of shipping the unlimited strength files (as with\n previous fixpacks), only the standard files were shipped. This\n prevents certain certificates with large keys from being\n imported or migrated.", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q270", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "WMQ for Windows has been changed such that the correct policy\n files will be shipped in future fixpacks. Meanwhile, 6.0.2.1\n users affected by this issue may use the following work-around:\n\n1. Download the unrestricted Java policy files (or obtain\n them from a WMQ 6 version before 6.0.2.1). The relevant files\n are local_policy.jar and US_export_policy.jar and they are\n installed by default in C:\\Program Files\\IBM\\WebSphere\n MQ\\gskit\\jre\\lib\\security\n\n2. Replace the two 6.0.2.1 gskit\\jre\\lib\\security policy\n files with the unrestricted ones obtained in step", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q270", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "1.\n\n The certificate administration command will then work the same\n as in previous versions.\n\n The fix is targeted for delivery in the following PTFs:\n\n v6.0\n Platform Fix Pack 6.0.2.2\n------- --------------------\n Windows U200270\n\n The latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\n If the maintenance level is not yet available, information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q270", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IC52687\nREPORTED COMPONENT NAME\n WMQ WINDOWS V6\nREPORTED COMPONENT ID\n 5724H7200\nREPORTED RELEASE\n 602\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2007-05-14\nCLOSED DATE\n 2007-05-30\nLAST MODIFIED DATE\n 2007-07-27\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q270", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ WINDOWS V6\nFIXED COMPONENT ID\n 5724H7200", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q270", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R600 PSY\n UP\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q270", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "The user is unable to rename or delete the queue manager's\n certificate from the queue manager's key database.\n\nFrom the runmqakm program the following error text is seen:\n CTGSK2005W A database error occurred.\n\nFrom the runmqckm program the following error text is seen:\n An invalid password was provided, the key database has been\n corrupted or it is of the wrong type. Expected database type:\n CMS", "logical_doc_id": 5, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q270", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED:\n Users with certificates stored in key repositories, when\n attempting to delete or rename a certificate.\n This issue affects users of the GSKit included with all levels\n of MQ 7.5.\n This issue affects users of the GSKit included with MQ 8.0.0.0\n and MQ 8.0.0.4.\n This issue does not affect users of the GSKit included with MQ\n 8.0.0.1 through MQ 8.0.0.3.\n\nPlatforms affected:\n MultiPlatform\n\nPROBLEM DESCRIPTION:\n The bundled GSKit software contained a defect which caused this\n problem.", "logical_doc_id": 5, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q270", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The bundled GSKit defect has been fixed.\n\nThe fix is targeted for delivery in the following PTFs:\n\nVersion Maintenance Level\n v7.5 7.5.0.6\n v8.0 8.0.0.5\n\nThe latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n\nIf the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q270", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IT12105\nREPORTED COMPONENT NAME\n WMQ BASE MULTIP\nREPORTED COMPONENT ID\n 5724H7241\nREPORTED RELEASE\n 750\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2015-11-04\nCLOSED DATE\n 2015-12-23\nLAST MODIFIED DATE\n 2015-12-23\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q270", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WMQ BASE MULTIP\nFIXED COMPONENT ID\n 5724H7241", "logical_doc_id": 5, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q270", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R750 PSY\n UP", "logical_doc_id": 5, "chunk_id": 32 }, { "doc_id": "techqa_DEV_Q104", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "A FIX IS AVAILABLE\nIBM Rational Design Manager 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24041312]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q104", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "If more than one DOORS module is associated, only one is shown\n in Rhapsody.\n\nTo have some fun, I associated two DOORS modules from one\n database and\n two DOORS modules from a second database on a different server.\n I\n opened up Rhapsody and I had one module from each of the two\n databases!\n\nI also noticed, when I opened Rhapsody it only asked me to log\n in to\n one of the DOORS databases. I had to request to be logged into\n the\n second database. I tried this several times, and it was\n consistent.", "logical_doc_id": 1, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q104", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nRhapsody DM *\n\nPROBLEM DESCRIPTION: *\nWHEN I ASSOCIATED MULTIPLE DOORS MODEL IN DM, *\nONLY ONE IS DISPLAYED IN RHAPSODY. *\n\nRECOMMENDATION: *", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q104", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fixed in 6.0 iFix1 and 5.0.2 iFix8\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q104", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI40825\nREPORTED COMPONENT NAME\n RATL RHAP DESIG\nREPORTED COMPONENT ID\n 5725D8000\nREPORTED RELEASE\n 502\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2015-05-11\nCLOSED DATE\n 2015-09-01\nLAST MODIFIED DATE\n 2015-09-01\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q104", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n RATL RHAP DESIG\nFIXED COMPONENT ID\n 5725D8000", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q104", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R502 PSY\n UP\n\nA FIX IS AVAILABLE\nIBM Rational Rhapsody 8.2.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24043638]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q104", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "With Rhapsody 8.2 installed and Eclipse (Mars) with the 8.2\n Platform Integration plugin, Rhapsody will crash if you:\n\n1: Open Rhapsody and load a model.\n 2: Open Eclipse and ensure a Rhapsody model is loaded (note that\n the plugin does not appear to be working correctly; the Rhp\n specific controls are not loading).\n 3: Modify the model in the Rhapsody client and save.\n\nThe crash does NOT occur if you open Eclipse first, and then\n open Rhapsody.", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q104", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nRhapsody *\n\nPROBLEM DESCRIPTION: *\nCRASH WHEN SAVING IN RHAPSODY AND ECLIPSE IS OPEN *\n\nRECOMMENDATION: *", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q104", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fixed\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q104", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI81041\nREPORTED COMPONENT NAME\n TLOGIC RHAPSODY\nREPORTED COMPONENT ID\n 5724V74RP\nREPORTED RELEASE\n 820\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2017-05-04\nCLOSED DATE\n 2017-06-11\nLAST MODIFIED DATE\n 2017-06-11\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q104", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n TLOGIC RHAPSODY\nFIXED COMPONENT ID\n 5724V74RP", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q104", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R820 PSN\n UP", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q104", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "Rational Rhapsody Fix Pack 2 (8.0.2) for 8.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034499]\nRational Rhapsody 8.0.6 [http://www-01.ibm.com/support/docview.wss?uid=swg24037021]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q104", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Headline:\n Memory leak observed in Rhapsody 8.0\n\nAbstract:\n Attempts to use Rhapsody continuously for some hours results in\n Performance Issue\n\nError_description:\n Rhapsody slows down considerably after using for a few hours on\n Windows XP. The reason is analysed to the fact that it keeps\n occupying more and more memory after subsequent\n actions....Finally it reaches a stage when even simple actions\n such as performing an 'Add to Model' or moving the cursor takes\n 2 minutes.\n\nSteps to Reproduce:\n Try1:\n I opened C++ model ?HomeAlarmWithPorts?. Memory used by Rhapsody\n = 17452 Kb.\n I open then OMD named: ?home alarm overview?. Memory used by\n Rhapsody = 27172 Kb.\n I close this OMD. Memory used by Rhapsody = 27160 Kb.\n I open again the same OMD (home alarm overview). Memory used by\n Rhapsody = 27204 Kb.\n I close again this OMD. Memory used by Rhapsody = 27164 Kb.\n I open again OMD named : home alarm overview. Memory used by\n Rhapsody = 27392 Kb.\n I close again this OMD. Memory used by Rhapsody = 27380 Kb.\n\nTry2:\n Tried to reproduce with a simple sample model and the results\n are more bad. Memory used shows as high as 47,000Kb while\n Rhapsody is launched..Opening a model shoots to 99,300 Kb.\n Closing the model brings it down to only 99,100Kb. Next time we\n open a model, it increases from 99,100 to 1,03,000 and so on...\n\nThe cycle keeps increasing.\n\nThis is potentially a big problem if huge models are opened.\n\nWorkaround:\n High risk for Rhapsody to crash.\n Decreases work efficiency.", "logical_doc_id": 3, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q104", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\n\nPROBLEM DESCRIPTION: *\n\nRECOMMENDATION: *\n\nMemory leak observed in Rhapsody 8.0", "logical_doc_id": 3, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q104", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fixed in 8.0.2\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q104", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM82411\nREPORTED COMPONENT NAME\n TLOGIC RHAPSODY\nREPORTED COMPONENT ID\n 5724V74RP\nREPORTED RELEASE\n 753\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-02-08\nCLOSED DATE\n 2013-03-21\nLAST MODIFIED DATE\n 2013-03-21\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q104", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n TLOGIC RHAPSODY\nFIXED COMPONENT ID\n 5724V74RP", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q104", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R753 PSN\n UP\n\nA FIX IS AVAILABLE\nIBM Rational Rhapsody 8.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24042928]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q104", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "PMR COMPID: RA0035SLS REL: 813\n Prod Name: Rational Rhapsody\n Pri/Sev: P2/S2\n\nNotifications:\n working with customer on new PO contract nim7127-7014211 allow c\n\nLink PMR in ICSW (assumes ICSW is open):\n http://127.0.0.1:8350/?ui=true&action=macro¯o=launch('04250,\n 082,000')\n Link to Client History Environment:\n https://webapps.rcsnl.ams.nl.ibm.com/deployment/view?source=clie\n nthistory&icn=0760071&countrycode=000&user=aratzloff@us.ibm.com [https://webapps.rcsnl.ams.nl.ibm.com/deployment/view?source=clienthistory&icn=0760071&countrycode=000&user=aratzloff@us.ibm.com]\n\nEscalation Questions:\n\nBusiness Impact\n\nThe crash slows down work. This model has been rolled out to\n customers, and it's important it's fixed soon.", "logical_doc_id": 4, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q104", "section_id": 1, "heading": "Environment", "parent": null, "text": "Windows 7\n Rhapsody 8.1.3 64-bit\n\nProblem Statement aka Comment line, work item summary...\n\nThe customer is using Rhapsody 8.1.3 64-bit. They have a large,\n integrated model (with a lot of referenced model content). When\n they try and do a search of the model, Rhapsody crashes. It does\n not happen every time, but it is highly repeatable with the\n model.\n\nAttached is a screenshot, the RER, and the version info.\n\nCustomer cannot send the model.\n\nHow do we get the crashing to stop happening in 64-bit?\n--\n\n8. Zvika Verzberger Feb 14, 2016 3:36 AM\n Cannot reproduce the bug.\n But, I can see issues with performance when the search on huge\n model resulting a very long list of elements.\n Please open a defect for that.\n\n7. Alexander A. Ratzloff Feb 11, 2016 12:06 AM\n From Raz:\n\n\"We can not get that model.\n\nI asked for some statistics:\n They say it is about 6 M model-elements, with about 30% of it\n Tags.\n\nDiscussing with Zvika, Zvika observed some less-then-optimal\n behavior\n in that scenario, will make some code changes and we'll let GM\n test to see if we are on the issue causing the crash.\"\n\n6. Zvika Verzberger Feb 8, 2016 3:59 AM\n I guess that this is specific for the specific model.\n Please attach the model and add the exact scenario (what was\n searched, what was selected etc.).\n\n5. Raz Yerushalmi Feb 8, 2016 3:42 AM\n @aratzloff@us.ibm.com @andreas.themis@uk.ibm.com please avoid\n assigning me as L3 owner, it is not very productive...\n regarding the issue at hand:\n Indeed, we saw the crash on-site at GM, running 8.1.4 against\n some of their larger models.\n When I tried on my own machine, I did not get it to crash.\n\nThe scenario they ran is simple:\n Run search on large model, and once results are shown, click the\n name column and then some other column to get it sorted twice.\n\nI'll discuss with further with Zvika.\n\n4. Andreas Themis Feb 4, 2016 10:11 AM\n Raz onsite working with customer to find root cause\n Crash verified\n\n3. Andreas Themis Jan 25, 2016 9:58 AM\n Alex: customer is testing on 814\n\nwill update", "logical_doc_id": 4, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q104", "section_id": 1, "heading": "Environment", "parent": null, "text": "2. Zvika Verzberger Dec 28, 2015 6:01 AM\n I cannot reproduce that.\n If the customer has a consistent scenario, please attach the\n original model and give the exact scenario.\n\n1. Alexander A. Ratzloff Dec 17, 2015 11:32 PM\n Added: attachment 91531 (Error_2015_12_9_12_15_50.zip),\n attachment 91532 (RhapsodyVersionInfo.txt), attachment 91533\n (Rhapsody Error Report - When Finding Signals.png)", "logical_doc_id": 4, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q104", "section_id": 3, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nRhapsody users *\n\nPROBLEM DESCRIPTION: *\nRHAPSODY 8.1.3 64-BIT CRASHING WHILE WORKING WITH SEARCH *\n\nRECOMMENDATION: *", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q104", "section_id": 4, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fixed in Rhapsody 8.2\n\nTEMPORARY FIX", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q104", "section_id": 6, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI57493\nREPORTED COMPONENT NAME\n TLOGIC RHAPSODY\nREPORTED COMPONENT ID\n 5724V74RP\nREPORTED RELEASE\n 813\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-02-18\nCLOSED DATE\n 2016-12-05\nLAST MODIFIED DATE\n 2016-12-05\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q104", "section_id": 7, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n TLOGIC RHAPSODY\nFIXED COMPONENT ID\n 5724V74RP", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q104", "section_id": 8, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R813 PSN\n UP\n\nA FIX IS AVAILABLE\nIBM Rational Rhapsody 8.3.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24044061]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q104", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "After updating a model from an earlier version of Rhapsody to\n Rhapsody 8.2, There are some instances where the code is\n incorrect.\n When a constructor initializer contains a boolean expression\n with a greater-than (>) symbol, this is causing Rhapsody to\n generate what appears to be garbled code.\n For example, if the ctor initializer in the model contains the\n following:\n\nitsClass(argument_0, argument_0 > 0, argument_0, argument_0),\n attribute_0(argument_0)\n\nthe resulting code is:\n\nclass_with_gt_initializer::class_with_gt_initializer(int\n argument_0) :\n itsClass(argument_0, argument_0 > 0,\n argument_0),\n attribute_0(argument_0),\n argument_0),\n attribute_0(argument_0) {\n\nI have tried setting CPP_CG::Class::MultiLineInitializerList to\n false to see if the feature to format the initializer list on\n multiple lines is causing the issue, but that does not resolve\n it.", "logical_doc_id": 5, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q104", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: *\nRhapsody *\n\nPROBLEM DESCRIPTION: *\nISSUE WITH NON-TRIVIAL CONSTRUCTOR INITIALIZER *\n\nRECOMMENDATION: *", "logical_doc_id": 5, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q104", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "constructor initializer with the chanracters '>','<' sometimes\n not Roundtriped, generated correctly\n problem fixed.\n\none limitation stay, if initializer contain generalization to\n template class the strig in the template <> section must not\n contain the charcters '>','<' (exept as template brackets)\n posible work around this limitations:\nbrackets around the template expresions, exapmples:\n superclass<(template_expersion > 1)>(init_expression)\n superclass<<(expe1 >1)>,<(expe2 <1)>>(init expression)\nuse property CPP_CG::Operation::OrderedConstructorInitializer\n for correct none reorder code generation\nuse property\n CPP_CG::Operation::DisableAutoGeneratedInitializer\n for simpler code generation and Roundtrip of constructor\n initialaizer, in this case the initialazer is a simple string\n that copied as is from the initializer field to the code in code\n generation and to the model in roundtrip\n\nTEMPORARY FIX", "logical_doc_id": 5, "chunk_id": 30 }, { "doc_id": "techqa_DEV_Q104", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI81878\nREPORTED COMPONENT NAME\n TLOGIC RHAPSODY\nREPORTED COMPONENT ID\n 5724V74RP\nREPORTED RELEASE\n 820\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2017-05-19\nCLOSED DATE\n 2017-12-04\nLAST MODIFIED DATE\n 2017-12-04\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 5, "chunk_id": 31 }, { "doc_id": "techqa_DEV_Q104", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n TLOGIC RHAPSODY\nFIXED COMPONENT ID\n 5724V74RP", "logical_doc_id": 5, "chunk_id": 32 }, { "doc_id": "techqa_DEV_Q104", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R820 PSY\n UP", "logical_doc_id": 5, "chunk_id": 33 }, { "doc_id": "techqa_DEV_Q194", "section_id": 0, "heading": "SYMPTOM", "parent": null, "text": "The SystemOut.log file shows warning messages similar to:\n\n0000001a ThreadMonitor W WSVR0605W: Thread \"ORB.thread.pool : 123\" (00000245) has been active for 773732 milliseconds and may be hung. There is/are 153 thread(s) in total in the server that may be hung.", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q194", "section_id": 1, "heading": "CAUSE", "parent": null, "text": "The limit to the number of threads allowed to process TWS operations is reached causing a performance bottleneck. This scenario will only occur in large TWS networks with a high activity level.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q194", "section_id": 2, "heading": "RESOLVING THE PROBLEM", "parent": null, "text": "Perform the following steps:\n\n1. Modify:\n$TWA_HOME/eWAS/profiles/twaprofile/config/cells/DefaultNode/nodes/DefaultNode/servers/twaserver/resources-pme.xml\n\n1a. Locate the Default Work Manager section:\n\n.\n\n1b. Modify isGrowable to \"true\"\n\n2. Restart the embedded WebSphere Application Server (eWAS):\n\n(In conman, run stopappserver;wait and startappserver.)\n\nThis will allow eWAS to spawn more threads to process TWS operations.\n\nPRODUCT ALIAS/SYNONYM\n Maestro\nTWS\nTWA", "logical_doc_id": 0, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q194", "section_id": 3, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24038133]\n7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35 [http://www-01.ibm.com/support/docview.wss?uid=swg24038310]\n8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24038539]\n8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24039242]\n7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37 [http://www-01.ibm.com/support/docview.wss?uid=swg24039338]\n8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24039425]\n8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040035]\n8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24040425]\n8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24040533]\n7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39 [http://www-01.ibm.com/support/docview.wss?uid=swg24041013]\n8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041178]\n8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24041590]\n8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24041819]\n7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41 [http://www-01.ibm.com/support/docview.wss?uid=swg24041931]\n8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]\n8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24043005]\n8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24042746]\n7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43 [http://www-01.ibm.com/support/docview.wss?uid=swg24043400]\n8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]\n8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http://www-01.ibm.com/support/docview.wss?uid=swg24044096]\n8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]\n7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45 [http://www-01.ibm.com/support/docview.wss?uid=swg24044551]\n8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 0, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q194", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "A deadlock may occur when stopping an application\n that contains a resource adapter module, which causes two\n threads to hang and the application to fail to stop.\n .\n The SystemOut.log will show the following hung thread detection\n messages:\n .\n WSVR0605W: Thread \"HAManager.thread.pool : 1\" (00000017) has\n been active for 628025 milliseconds and may be hung. There\n is/are 1 thread(s) in total in the server that may be hung.\n at\n com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(C\n onnectionFactoryBuilderImpl.java:436)\n at\n javax.naming.spi.NamingManager.getObjectInstanceByFactoryInRefer\n ence(NamingManager.java:501)\n at\n javax.naming.spi.NamingManager.getObjectInstance(NamingManager.j\n ava:365)\n at\n com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupE\n xt(Helpers.java:927)\n ...\n\n WSVR0605W: Thread \"Default : 4\" (0000003e) has been active for\n 627799 milliseconds and may be hung. There is/are 2 thread(s)\n in total in the server that may be hung.\n at\n com.ibm.ejs.j2c.RALifeCycleManagerImpl.shutdown(RALifeCycleManag\n erImpl.java:1483)\n at\n com.ibm.ejs.j2c.RALifeCycleManagerImpl.stop(RALifeCycleManagerIm\n pl.java:782)\n at\n com.ibm.ws.runtime.component.ApplicationMgrImpl.stop(Application\n MgrImpl.java:1151)\n ...\n\n A Javacore will show that a deadlock has occurred:\n .\n**WARNING*** Deadlock detected in [HAManager.thread.pool : 1]\n [Default : 2]\n\n HAManager.thread.pool : 1\n State\n Deadlock/Blocked\n Monitor\n Owns Monitor Lock on\n com/ibm/ejs/j2c/RAWrapperImpl@0x000000074E493120/0x000000074E493\n 12C\n Waiting for Monitor Lock on\n java/lang/Object@0x00000007443ADCF8/0x00000007443ADD04\n Java Stack\n at\n com/ibm/ejs/j2c/ConnectionFactoryBuilderServerImpl.createCFD_Com\n mon(ConnectionFactoryBuilderServerImpl.java:330)\n at\n com/ibm/ejs/j2c/ConnectionFactoryBuilderServerImpl.processObject\n Instance(ConnectionFactoryBuilderServerImpl.java:1027)\n at\n com/ibm/ejs/j2c/ConnectionFactoryBuilderImpl.getObjectInstance(C\n onnectionFactoryBuilderImpl.java:664)\n at\n javax/naming/spi/NamingManager.getObjectInstanceByFactoryInRefer\n ence(NamingManager.java:501)\n ...\n\n Default : 2\n State\n Deadlock/Blocked\n Monitor\n Owns Monitor Lock on\n java/lang/Object@0x00000007443ADCF8/0x00000007443ADD04\n Waiting for Monitor Lock on\n com/ibm/ejs/j2c/RAWrapperImpl@0x000000074E493120/0x000000074E493\n 12C\n Java Stack\n at\n com/ibm/ejs/j2c/RALifeCycleManagerImpl.shutdown(RALifeCycleManag\n erImpl.java:1483)\n at\n com/ibm/ejs/j2c/RALifeCycleManagerImpl.stop(RALifeCycleManagerIm\n pl.java:782)\n at\n com/ibm/ws/runtime/component/ApplicationMgrImpl.stop(Application\n MgrImpl.java:1151)\n ...\n\n This is a timing/synchronization issue that can occur when\n running WebSphere Application Server with a fix pack level\n that includes apar PM93319 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM93319].", "logical_doc_id": 1, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q194", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of IBM WebSphere Application *\nServer with applications that include a *\nresource adapter. *\n\nPROBLEM DESCRIPTION: Threads hang due to a deadlock when *\nstopping an application that includes *\na resource adapter. *\n\nRECOMMENDATION: *\n\nA deadlock can occur between the application stop thread and\n the j2c resource adapter work thread doing a lookup due to\n synchronization and issues which can prevent stopping the\n application.", "logical_doc_id": 1, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q194", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The WebSphere Application Server J2C code has been corrected\n to properly synchronize the locking objects.\n The fix for this APAR is currently targeted for inclusion in\n fix packs 7.0.0.35, 8.0.0.10 and 8.5.5.3. Please refer to the\n Recommended Updates page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX", "logical_doc_id": 1, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q194", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI13428\nREPORTED COMPONENT NAME\n WEBS APP SERV N\nREPORTED COMPONENT ID\n 5724H8800\nREPORTED RELEASE\n 700\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2014-03-10\nCLOSED DATE\n 2014-07-15\nLAST MODIFIED DATE\n 2014-07-15\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 1, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q194", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBS APP SERV N\nFIXED COMPONENT ID\n 5724H8800", "logical_doc_id": 1, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q194", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R700 PSY\n UP\nR800 PSY\n UP\nR850 PSY\n UP\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 1, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q194", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Whan we open the application in designer it takes a long time\n to open, around 10 minutes. In the logs it says about thread\n is hung.\n See the detailed error below:\n WSVR0605W: Thread \"WebContainer : 20\" (00000caa) has been\n active for 680003 milliseconds and may be hung. There is/are\n 12 thread(s) in total in the server that may be hung.\n at\n com.ibm.bpm.pal.action.BaseActionsImpl.executeAction(BaseActions\n Impl.java:387)\n at\n com.ibm.bpm.pal.action.SnapshotActionsImpl.archive(SnapshotActio\n nsImpl.java:132)\n at\n com.lombardisoftware.server.ejb.repositoryservices.ArchiveSuppor\n t.toggle(ArchiveSupport.java:213)\n at\n com.lombardisoftware.server.ejb.repositoryservices.ArchiveSuppor\n t.toggleChildren(ArchiveSupport.java:179)\n at\n com.lombardisoftware.server.ejb.repositoryservices.ArchiveSuppor\n t.archive(ArchiveSupport.java:89)\n at\n com.lombardisoftware.server.ejb.repositoryservices.RepositorySer\n vicesCore.archive(RepositoryServicesCore.java:496)\n at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n at\n sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor\n Impl.java:60)\n at\n sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod\n AccessorImpl.java:37)\n at java.lang.reflect.Method.invoke(Method.java:611)\n at\n org.springframework.aop.support.AopUtils.invokeJoinpointUsingRef\n lection(AopUtils.java:310)\n .-------------------------------------------------------------\n Looking at the instrumentation logs, the following calls are\n taking a long amount of time:\n\n PersistenceServicesCore.findByFilter - multiple occurrences\n PersistenceServicesCore.findByPrimaryKey - multiple occurrences\n PersistenceServicesCore.findAll - multiple occurrences\n PersistenceServicesCore.findQuietlyByPrimaryKey\n ClientServicesCore.libraryDelete\n RuntimeServicesCore.getActiveFavoriteOfServiceExposeType -\n multiple\n occurrences\n UserStatusServicesCore.setClientActivityStatusAndPALUpdates -\n multiple\n occurrences\n SecurityCore.getUserLocalePreferences\n SecurityCore.updateGroupMembership\n EnvironmentServicesCore.isRepository\n RepositoryServicesCore.copyItemsToExistingProject\n RepositoryServicesCore.copyItemsToTip\n RepositoryServicesCore.getLastNSnapshots - multiple occurrences\n RepositoryServicesCore.getLastModifiedBranches - multiple\n occurrences\n com.lombardisoftware.component.javaconnector.worker.JavaConnecto\n rWorker\nmultiple occurrences\n com.lombardisoftware.component.coach.worker.CoachWorker\n com.lombardisoftware.component.twscript.worker.ScriptWorker", "logical_doc_id": 2, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q194", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: User who wants to open Process *\nApplications in Process Designer. *\n\nPROBLEM DESCRIPTION: Hung threads will be experienced in *\nthe Repository layer when two threads *\nperform an archive operation on the *\nsame snapshot. The issue occurs *\nbecause one thread acquires a DB lock *\nand waits on a Java synchronized lock *\nacquired by the second thread. This *\nscenario causes a deadlock. *\n\nRECOMMENDATION: *\n\n There are quite a few hung threads can be seen in the java\n core dump files, one surrounding the synchronized block of\n ServerImpl.getContainerCapability() and the other surrounding\n BaseActionsImpl.getRepositoryState().\n The suspect in both cases being, Thread 1 is acquiring a db\n lock and waiting on the java lock (owing to the synchronized)\n acquired by Thread 2 which is waiting on a db lock. The\n patterns can be identified with the following\n Thread 1 waiting on java lock:\n Thread \"WebContainer : 6\" (0000004a) has been active for\n 632672 milliseconds and may be hung. There is/are 1 thread(s)\n in total in the server that may be hung.\n at\n com.ibm.bpm.pal.capability.ServerImpl.getContainerCapability(Ser\n verImpl.java:201)\n at\n com.ibm.bpm.pal.statemachine.StateMachine.getState(StateMachine.\n java:299)\n at\n com.ibm.bpm.pal.statemachine.StateMachine.getPossibleActions(Sta\n teMachine.java:807)\n at\n com.ibm.bpm.pal.action.BaseActionsImpl.getPossibleActions(BaseAc\n tionsImpl.java:96)\n at\n com.ibm.bpm.pal.action.TipActionsImpl.getPossibleActions(TipActi\n onsImpl.java:45)\n at\n com.lombardisoftware.repository.server.ObjectManagementServiceIm\n pl.getPossibleTIPActions(Ob\n Thread 2 Waiting on db lock:\n Thread \"WebContainer : 0\" (0000003b) has been active for\n 632657 milliseconds and may be hung. There is/are 2 thread(s)\n in total in the server that may be hung.\n at java.net.SocketInputStream.socketRead0(Native Method)\n at java.net.SocketInputStream.read\n (SocketInputStream.java:140)\n at\n com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1525)\n at\n com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:\n 3317)\n at\n com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.j\n ava:4437\n Similar pattern is seen with few other hung threads.", "logical_doc_id": 2, "chunk_id": 11 }, { "doc_id": "techqa_DEV_Q194", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The ifix implemented the mechanism to prevent the above\n mentioned deadlock from happening.\n\nFor install/uninstall instruction about ifix JR44560, please\n download the README file along with the ifix file from Fix\n Central.\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 12 }, { "doc_id": "techqa_DEV_Q194", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n JR44560\nREPORTED COMPONENT NAME\n BPM STANDARD\nREPORTED COMPONENT ID\n 5725C9500\nREPORTED RELEASE\n 800\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2012-10-26\nCLOSED DATE\n 2013-01-15\nLAST MODIFIED DATE\n 2014-03-21\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 13 }, { "doc_id": "techqa_DEV_Q194", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n BPM STANDARD\nFIXED COMPONENT ID\n 5725C9500", "logical_doc_id": 2, "chunk_id": 14 }, { "doc_id": "techqa_DEV_Q194", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R800 PSY\n UP\n\nA FIX IS AVAILABLE\nFixes integrated in WebSphere Portal 8.0.0.1 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24034497]", "logical_doc_id": 2, "chunk_id": 15 }, { "doc_id": "techqa_DEV_Q194", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Hung BackgroundCache thread reported by WAS during pre-rendering\n of a large site.\n\n Example messages in the system log:\n ThreadMonitor W \uffa0 \uffa0 WSVR0605W: Thread\n \"WorkManager.wpsDefaultWorkManager : 2\" (0000006f) has been\n active for 719719 milliseconds and may be hung. \uffa0 There is/are 4\n thread(s) in total in the server that may be hung.\n at java.lang.Thread.sleep(Native Method)\n at java.lang.Thread.sleep(Thread.java:896)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:303)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:347)\n at com.aptrix.cacher.Cacher.storePreRenderedContent(Cacher)\n at com.aptrix.cacher.Cacher.cache(Cacher.java:213)\n ...", "logical_doc_id": 3, "chunk_id": 16 }, { "doc_id": "techqa_DEV_Q194", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Hung BackgroundCache thread reported by WAS during pre-rendering\n of a large site.\n\n Example messages in the system log:\n ThreadMonitor W \u00a0WSVR0605W: Thread\n \"WorkManager.wpsDefaultWorkManager : 2\" (0000006f) has been\n active for 719719 milliseconds and may be hung. \u00a0There is/are 4\n thread(s) in total in the server that may be hung.\n at java.lang.Thread.sleep(Native Method)\n at java.lang.Thread.sleep(Thread.java:896)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:303)\n at com.aptrix.cacher.Cacher.cacheDescendents(Cacher.java:347)\n at com.aptrix.cacher.Cacher.storePreRenderedContent(Cacher)\n at com.aptrix.cacher.Cacher.cache(Cacher.java:213)\n ...", "logical_doc_id": 3, "chunk_id": 17 }, { "doc_id": "techqa_DEV_Q194", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Code was modified to prevent the hung threads from occurring\n during the pre-rendering of large sites.\n\nTEMPORARY FIX", "logical_doc_id": 3, "chunk_id": 18 }, { "doc_id": "techqa_DEV_Q194", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PM95353\nREPORTED COMPONENT NAME\n LOTUS WEB CONT\nREPORTED COMPONENT ID\n 5724I2900\nREPORTED RELEASE\n 800\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt\nSUBMITTED DATE\n 2013-08-19\nCLOSED DATE\n 2013-09-08\nLAST MODIFIED DATE\n 2013-09-08\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 3, "chunk_id": 19 }, { "doc_id": "techqa_DEV_Q194", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n LOTUS WEB CONT\nFIXED COMPONENT ID\n 5724I2900", "logical_doc_id": 3, "chunk_id": 20 }, { "doc_id": "techqa_DEV_Q194", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R800 PSY\n UP", "logical_doc_id": 3, "chunk_id": 21 }, { "doc_id": "techqa_DEV_Q194", "section_id": 8, "heading": "FIXES ARE AVAILABLE", "parent": null, "text": "9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24043338]\n9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043693]\n8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]\n9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24044067]\n9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24044242]\n8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]\n9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24044620]\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 3, "chunk_id": 22 }, { "doc_id": "techqa_DEV_Q194", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "When com.ibm.websphere.threadmonitor.dump.java is set to true\n and if com.ibm.websphere.threadmonitor.dump.java.track is NOT\n set then by default a java thread dump is created continuously\n at the default hung thread detection time interval (default 3\n mins). So basically it will continuously produce java thread\n dumps every minute while the thread remains hung.\n\n In customer situation the hung thread never recovers and as a\n result a java thread dump is produced every 3 minutes and\n fills up gigabytes of storage.", "logical_doc_id": 4, "chunk_id": 23 }, { "doc_id": "techqa_DEV_Q194", "section_id": 1, "heading": "LOCAL FIX", "parent": null, "text": "You can set\n com.ibm.websphere.threadmonitor.dump.java to 1", "logical_doc_id": 4, "chunk_id": 24 }, { "doc_id": "techqa_DEV_Q194", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "USERS AFFECTED: All users of IBM WebSphere Application *\nServer *\n\nPROBLEM DESCRIPTION: The hung thread detection system *\nrepeatedly dumps javacores for the *\nsame hung thread *\n\nRECOMMENDATION: *\n\n The WebSphere Application Server thread monitor allows users\n to track hung threads by periodically dumping a javacore as\n long as the thread is detected as hung, using the\n com.ibm.websphere.threadmonitor.dump.java.track property.\n If this property is unset, the default value is set to be\n identical to the value of\n com.ibm.websphere.threadmonitor.dump.java. If the property is\n set to \"true\", the thread monitor sets those properties to the\n maximum integer value, so a thread hung for a long period of\n time would cause javacores to be thrown basically\n indefinitely.\n Users who had used this property on previous editions of\n WebSphere Application Server would have been likely to use the\n \"true\" value, as the property utilized boolean values in its\n original incarnation, but since the \"track\" property did not\n exist, they would have only had one javacore thrown per thread.", "logical_doc_id": 4, "chunk_id": 25 }, { "doc_id": "techqa_DEV_Q194", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "The default value of the \"track\" property was modified so that\n if left unset, only one javacore would be thrown for a single\n hung thread.\n\n The fix for this APAR is currently targeted for inclusion in\n fix packs 8.5.5.12 and 9.0.0.3. Please refer to the\n Recommended Updates page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n\nTEMPORARY FIX\nAs a workaround, users can set the system property\n com.ibm.websphere.threadmonitor.dump.java.track to \"1\".", "logical_doc_id": 4, "chunk_id": 26 }, { "doc_id": "techqa_DEV_Q194", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n PI65836\nREPORTED COMPONENT NAME\n WEBS APP SERV N\nREPORTED COMPONENT ID\n 5724H8800\nREPORTED RELEASE\n 850\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-07-13\nCLOSED DATE\n 2016-11-22\nLAST MODIFIED DATE\n 2016-11-22\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 4, "chunk_id": 27 }, { "doc_id": "techqa_DEV_Q194", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n WEBS APP SERV N\nFIXED COMPONENT ID\n 5724H8800", "logical_doc_id": 4, "chunk_id": 28 }, { "doc_id": "techqa_DEV_Q194", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R850 PSY\n UP\nR900 PSY\n UP", "logical_doc_id": 4, "chunk_id": 29 }, { "doc_id": "techqa_DEV_Q124", "section_id": 0, "heading": "QUESTION", "parent": null, "text": "How do you generate a report to show the \"up time\" (how long the agent is up and running since it was started) of the Managed Systems in IBM Tivoli Monitoring (ITM) environment?", "logical_doc_id": 0, "chunk_id": 0 }, { "doc_id": "techqa_DEV_Q124", "section_id": 1, "heading": "ANSWER", "parent": null, "text": "There is no direct command, however, there is a work around but one needs some scripting skills (any language and any OS).\n\nThe GBLTMSTAMP value on the below query, gives the Start time of the managed system\n\nYou could write a script to execute a query and take the GBLTMSTAMP value and subtract the current timestamp to get the up time for the managed system\n\nSELECT GBLTMSTMP, NODE, ORIGINNODE, O4ONLINE, PRODUCT, THRUNODE, VERSION\nFROM O4SRV.INODESTS;\n\nWhere NODE is the managed system name.", "logical_doc_id": 0, "chunk_id": 1 }, { "doc_id": "techqa_DEV_Q124", "section_id": 0, "heading": "DOCUMENT", "parent": null, "text": "Note : How to execute a query is not within the scope of this technote\n\nSUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.", "logical_doc_id": 1, "chunk_id": 2 }, { "doc_id": "techqa_DEV_Q124", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Request for enhancement to the Custom Scripting feature as\n follows:\n\none of my client was highly interested in this new feature but\n then very when he recognized, that this feature does only\n trigger pure. In fact most scripts do status monitoring with\n both, good and bad status for an item and therefore certainly\n need sampled events instead to see clearing events as well.\n\nDoes this work as design, and if so, do we plan to change the\n behavior?\n\nOtherwise the agent will never achieve what it is supposed to:\n substitute hundreds of existing agentbuilder agents over time.", "logical_doc_id": 2, "chunk_id": 3 }, { "doc_id": "techqa_DEV_Q124", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "Problem Description: Events from situations on custom scripts do\n not close automatically.\n\nProblem/Problem Summary: The data gathered executing the custom\n scripts in 6.30 FP5 are reported using the\n KXX_Custom_Scripts_Runtime attribute groups (where XX stands\n for LZ or NT or UX). These groups implement 'pure event'\n tables. Because of this, situations cannot receive\n 'clearing' events and need to be manually closed.", "logical_doc_id": 2, "chunk_id": 4 }, { "doc_id": "techqa_DEV_Q124", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "Fix/Problem Conclusion: New KXX_Custom_Scripts_Rtm_Smp sampled\n tables added. They report the same custom scripts' output data\n as those reported by the existing pure event tables.\n\nSpecifications are as follow:\n\nAttribute group: KXX_Custom_Scripts_Rtm_Smp (multiple rows)\n\nTable: KXXSCRTSM (Sampled)\n\nDescription: Data gathered using custom scripts. It contains\n the output rows of the scripts currently running.\n\nAttribute Size Description\n ======================= ==== ==================================\n System_Name 32 This is the managed system name of\n the agent.\n Timestamp 16 This is the local time when the\n data was collected\n Property_File 256 The name of the property file\n Attribute_Name 96 The attribute name that is defined\n in the properties file. The\n attribute is used for metric\n identification.\n Script_Path 512 The fully qualified path of the\n script.\n Custom_Name 96 The custom name that is defined\n in the properties file. It is used\n for custom reporting.\n Return_Code 4 Integer value returned by the\n script\n Row_Number 4 Output row number.\n Standard_Output_Type 4 Standard output type of the script\n Standard_Output_String 2048 Script Standard Output in String\n format.\n Standard_Output_Integer 8 Script Output in Integer format\n Standard_Output_Float 8 Script Output in Floating Point\n format (2 decimals).\n Cust_Attr_Str1 64 Custom string attribute #1\n Cust_Attr_Str2 64 Custom string attribute #2\n Cust_Attr_Str3 64 Custom string attribute #3\n Cust_Attr_Str4 64 Custom string attribute #4\n Cust_Attr_Str5 64 Custom string attribute #5\n Cust_Attr_Int1 8 Custom integer attribute #1\n Cust_Attr_Int2 8 Custom integer attribute #2\n Cust_Attr_Int3 8 Custom integer attribute #3\n Cust_Attr_Int4 8 Custom integer attribute #4\n Cust_Attr_Int5 8 Custom integer attribute #5\n Cust_Attr_Float1 8 Custom floating point (2 decimals)\n attribute #1\n Cust_Attr_Float2 8 Custom floating point (2 decimals)\n attribute #2\n Cust_Attr_Float3 8 Custom floating point (2 decimals)\n attribute #3\n Cust_Attr_Float4 8 Custom floating point (2 decimals)\n attribute #4\n Cust_Attr_Float5 8 Custom floating point (2 decimals)\n attribute #5\n\nThe OS agent sends events only if there are situations or\n historical collections using the pure event table; to\n completely avoid the sending of events, the Administrator can\n set to 'false' the environment variable:\nKXX_FCP_SEND_SCRIPT_RUNTIME_EVENTS (default: true)\n If set to false, the OS agent stops sending events for each\n row of script standard output. In this case script outputs are\n visible on TEP console workspaces but no situations will be\n displayed and no historical collection data will be collected.", "logical_doc_id": 2, "chunk_id": 5 }, { "doc_id": "techqa_DEV_Q124", "section_id": 3, "heading": "PROBLEM CONCLUSION", "parent": null, "text": "No TEP workspace changes are introduced by this APAR, but a\n new built-in query named \"Script execution results sampled\",\n based on the new sampled tables, is provided.\n\nThe fix for this APAR will be contained in the following\n maintenance packages:\n\n| FixPack | 6.3.0-TIV-ITM-FP0007\n | InterimFix | 6.3.0.5-TIV-ITM_LINUX-IF0002\n | InterimFix | 6.3.0.5-TIV-ITM_UNIX-IF0002\n | InterimFix | 6.3.0.5-TIV-ITM_WIN-IF0001\n\nTEMPORARY FIX", "logical_doc_id": 2, "chunk_id": 6 }, { "doc_id": "techqa_DEV_Q124", "section_id": 5, "heading": "APAR INFORMATION", "parent": null, "text": "APAR NUMBER\n IV85663\nREPORTED COMPONENT NAME\n ITM AGENT LINUX\nREPORTED COMPONENT ID\n 5724C04LN\nREPORTED RELEASE\n 630\nSTATUS\n CLOSED PER\nPE\n NoPE\nHIPER\n NoHIPER\nSPECIAL ATTENTION\n NoSpecatt / Xsystem\nSUBMITTED DATE\n 2016-06-15\nCLOSED DATE\n 2016-06-15\nLAST MODIFIED DATE\n 2016-06-15\nAPAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n IV77559 [http://www-01.ibm.com/support/docview.wss?uid=swg1IV77559]\nAPAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:", "logical_doc_id": 2, "chunk_id": 7 }, { "doc_id": "techqa_DEV_Q124", "section_id": 6, "heading": "FIX INFORMATION", "parent": null, "text": "FIXED COMPONENT NAME\n ITM AGENT LINUX\nFIXED COMPONENT ID\n 5724C04LN", "logical_doc_id": 2, "chunk_id": 8 }, { "doc_id": "techqa_DEV_Q124", "section_id": 7, "heading": "APPLICABLE COMPONENT LEVELS", "parent": null, "text": "R630 PSY\nR610 PSN\nR620 PSN\nR621 PSN\nR622 PSN\nR623 PSN\n\nSUBSCRIBE\nYou can track all active APARs for this component.", "logical_doc_id": 2, "chunk_id": 9 }, { "doc_id": "techqa_DEV_Q124", "section_id": 0, "heading": "ERROR DESCRIPTION", "parent": null, "text": "Both APAR:IY42077 [http://www-01.ibm.com/support/docview.wss?uid=swg1IY42077] and this one relate to WebSEAL's support\n for protecting Web servers\n against cross-site scripting attacks.\n\nThe problem is \"bad requests are not recorded in request.log\"\n\nWhen the filtering does work, there's no entry written to the\n log to indicate that anything was filtered.\n\nMichael T. at the Gold Coast confirmed\n that these requests should definitely be logged,\n especially in this case, as otherwise there's no way\n to determine\n who's trying to attack you.", "logical_doc_id": 3, "chunk_id": 10 }, { "doc_id": "techqa_DEV_Q124", "section_id": 2, "heading": "PROBLEM SUMMARY", "parent": null, "text": "When there is a \"?\" in the URI, WebSEAL does not\n filter the request, ie, still find