{"id": "VAL_Q000", "document": "IBM Download Jazz for Service Management Version 1.1.3.0 - United States  DOWNLOADABLE FILES\n\nABSTRACT\n You can download Jazz for Service Management from the Passport Advantage web site by using the electronic image part numbers that are provided in this document. \n\nDOWNLOAD DESCRIPTION\n\n\nJazz™ for Service Management brings together the Open Services for Lifecycle Collaboration (OSLC) community's open specifications for linking data and other shared integration services; including dashboard and reporting services. Jazz for Service Management underpins client defined management scenarios such as cloud; performance monitoring; and IT service management.\n\nJazz for Service Management has a number of integration services: Dashboard Services provided by IBM® Dashboard Application Services Hub and Reporting Services.\n\nFor more information about Jazz for Service Management; see the Jazz for Service Management documentation [http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/psc_ic-homepage.html].\n\nVersion 1.1.3.0 is a full refresh of Jazz for Service Management Version 1.1 Base with Modification 3. \n\n\n\nDOWNLOADING JAZZ FOR SERVICE MANAGEMENT ELECTRONIC IMAGES\nYou can download images by using the IBM Download Director applet or HTTP. If possible choose Download Director; because it automatically verifies the completeness of each image that it processes.\n\nTip: If you use Download Director to download the software; then you can also use it to extract the contents of all the compressed files that you downloaded in the session.\n\n\n 1.  Before you start the installation; check the Jazz for Service Management Technotes [http://www.ibm.com/support/search.wss?q=jazzsm1130relnotes] for late breaking issues or updated installation instructions.\n 2.  Determine the set of platform-specific images to download for the installation scenario or integration services to install; as summarized in the following table. Scenario Images Full installation; all integration services and middleware  * Jazz™ for Service Management 1.1.3.0\n      * IBM® Tivoli® Common Reporting 3.1.3.0\n      * IBM® WebSphere® Application Server 8.5.5.9\n      * IBM® DB2® Enterprise Server Edition 10.5\n     \n     Custom installation; Dashboard Application Services Hub  * Jazz™ for Service Management 1.1.3.0\n      * IBM® WebSphere® Application Server 8.5.5.9; optional if already installed\n      * IBM® WebSphere® Application Server V8.5 Supplements; for high availability environment only\n      * IBM® DB2® Enterprise Server Edition 10.5; for high availability environment only\n     \n     Custom installation; Reporting Services  * Jazz™ for Service Management 1.1.3.0\n      * IBM® Tivoli® Common Reporting 3.1.3.0\n      * IBM® WebSphere® Application Server 8.5.5.9; optional if already installed\n      * IBM® DB2® Enterprise Server Edition 10.5; optional if already installed\n     \n     \n 3.  Create one or more of the following temporary directories in the same file system:  * JazzSM_Image_Home directory; which refers to the directory that will contain the extracted contents of the Jazz for Service Management platform-specific image.\n      * Image_Imgs_Home directory; which refers to the directory that will contain the extracted contents of platform-specific images for middleware. Tip: You only create this directory if you intend to install IBM DB2®; IBM WebSphere® Application Server.\n        \n        \n     \n     \n 4.   Navigate to the IBM Passport Advantage web site [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]. \n     Note: You require an IBM Customer ID to sign in and continue.\n 5.  Select the Find by part number search option under Download finder options.\n 6.  Search for each downloadable image by part number; as outlined in the relevant Operating_System tab in this download document.\n 7.  Select and download only the images for your platform that you need.\n 8.  Extract the downloaded images into directories that you created in step 3. \n     \n     Important: If you have downloaded the middleware and you want to perform a full installation; ensure that your Install_Imgs_Home directory is set up as follows:\n     |-ESE (Windows) [extracted DB2 installation image on Windows] \n     |-ese (UNIX) [extracted DB2 installation image on AIX; Linux; or Linux for System z] \n     |-WASRepository [extracted WebSphere Application Server installation image]\n     |-TCRCognos [extracted Tivoli Common Reporting Cognos® installation image] This directory structure is not required for a custom installation; for example; installing a subset of integration services by using the launchpad custom workflow or IBM Installation Manager GUI.\n     \n     \n 9.  To perform a full installation; download the Quick Start image with a part number of CNC1MML. It contains quick start guides for these installation scenarios.  * CNC1MML_JazzSM_lang_code.pdf - Quick start guide for the full installation scenario; to install all Jazz for Service Management integration services; IBM DB2®; and IBM WebSphere® Application Server on a single server for evaluation and development purposes. \n     \n     \n 10. If you want to perform a custom installation; for example; install only a subset of Jazz for Service Management integration services or use existing supported installations of WebSphere Application Server or DB2; see Custom installation scenario [http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_c_install_advanced_opt.html] in the Jazz for Service Management documentation.\n\n\n\nTAB NAVIGATION\n * AIX®\n * Linux\n * Linux on System z®\n * Windows\n\n\n\nSee Jazz for Service Management Detailed System Requirements [http://www.ibm.com/support/docview.wss?uid=swg27038732] for the AIX operating systems on which Jazz for Service Management is supported.\n\nDownloadable images with part numbers\n\nYou can download electronic images for Jazz for Service Management and its database and application server middleware. Refer to the following sections for details about the images that are required and optional.\n\n * Required software\n * Optional software\n\nRequired software Part number\n\nDescription\n\nCNC1NML Jazz for Service Management 1.1.3.0 for AIX®; 64-bit; Multilingual\n\nContains the Jazz for Service Management launchpad; IBM Installation Manager Version 1.8.4.1; IBM Prerequisite Scanner Version 1.2.0.18; IBM Tivoli Directory Integrator Identity Edition Version 7.1.1.5; and the Installation Manager software packages for following integration service: IBM Dashboard Application Services Hub Version 3.1.3.0\n\nCNC1SML IBM Tivoli Common Reporting 3.1.3.0 for AIX®; 64-bit; Multilingual\n\nContains the base installation image.\n\nOptional software Download the following supplemental software under the following conditions:\n\n * If you want to install Jazz for Service Management and its database and application server middleware on a single server for evaluation and development purposes; also referred to as a full installation.\n * If you do not have an existing supported version of WebSphere Application Server.\n * If you do not have an existing supported version of DB2 Enterprise Server Edition and you want to install Reporting Services and Dashboard Application Services Hub in a high-availability environment.\n * If you want to set up Dashboard Application Services Hub in a high-availability environment.\n\nOptional WebSphere Application Server software Part number\n\nDescription\n\nCNC1YML IBM® WebSphere® Application Server 8.5.5.9 for Jazz for Service Management for AIX®; 64-bit; Multilingual\n\n \n\nContains WebSphere Application Server Version 8.5.5.9 and IBM WebSphere SDK for Java Technology Edition 7.0.8.0\n\nCI6X0ML\nCI6X1ML\nCI6X2ML\nIBM® WebSphere® Application Server V8.5 Supplements (1 of 3) for Multiplatform; Multilingual\nIBM® WebSphere® Application Server V8.5 Supplements (2 of 3) for Multiplatform; Multilingual\nIBM® WebSphere® Application Server V8.5 Supplements (3 of 3) for Multiplatform; Multilingual\n\n\nContains supplemental WebSphere Application Server software; including IBM HTTP Server and IBM HTTP Server plug-in for IBM WebSphere Application Server.\n\nImportant: Download only if you want to set up Dashboard Application Services Hub in a high-availability environment. You must download all 3 images and extract them to the same location.\n\nOptional DB2 software Part number\n\nDescription\n\nCIW3TML IBM® DB2® Enterprise Server Edition V10.5 for AIX® Multilingual CIPH4ML IBM® DB2® 10.5 Enterprise Server Edition - Restricted Use Quick Start and Activation Multiplatform Multilingual CIWM8ML IBM® DB2® 10.5 National Language Pack for AIX® Multilingual Back to top\n\nSee Jazz for Service Management Detailed System Requirements [http://www.ibm.com/support/docview.wss?uid=swg27038732] for the Linux operating systems on which Jazz for Service Management is supported.\n\nDownloadable images with part numbers\n\nYou can download electronic images for Jazz for Service Management and its database and application server middleware. Refer to the following sections for details about the images that are required and optional.\n\n * Required software\n * Optional software\n\nRequired software Part number\n\nDescription\n\nCNC1PML Jazz for Service Management 1.1.3.0 for Linux®; 64-bit; Multilingual\n\nContains the Jazz for Service Management launchpad; IBM Installation Manager Version 18.2; IBM Prerequisite Scanner Version 1.2.0.18; IBM Tivoli Directory Integrator Identity Edition Version 7.1.1.5; and the Installation Manager software packages for following integration service: IBM Dashboard Application Services Hub Version 3.1.3.0.\n\nCNC1TML IBM® Tivoli® Common Reporting 3.1.3.0 for Linux®; 64-bit; Multilingual\n\nContains the base installation image.\n\nOptional software Download the following supplemental software under the following conditions:\n\n * If you want to install Jazz for Service Management and its database and application server middleware on a single server for evaluation and development purposes; also referred to as a full installation.\n * If you do not have an existing supported version of WebSphere Application Server.\n * If you do not have an existing supported version of DB2 Enterprise Server Edition and you want to install Tivoli Common Reporting or Dashboard Application Services Hub in a high-availability environment.\n * If you want to set up Dashboard Application Services Hub in a high-availability environment.\n\nOptional WebSphere Application Server software Part number\n\nDescription\n\nCNC1ZML IBM® WebSphere® Application Server 8.5.5.9 for Jazz for Service Management for Linux®; 64-bit; Multilingual\n\n \n\nContains WebSphere Application Server Version 8.5.5.9 and IBM WebSphere SDK for Java Technology Edition 7.0.8.0\n\nCI6X0ML\nCI6X1ML\nCI6X2ML\nIBM® WebSphere® Application Server V8.5 Supplements (1 of 3) for Multiplatform; Multilingual\nIBM® WebSphere® Application Server V8.5 Supplements (2 of 3) for Multiplatform; Multilingual\nIBM® WebSphere® Application Server V8.5 Supplements (3 of 3) for Multiplatform; Multilingual\n\n\nContains supplemental WebSphere Application Server software; including IBM HTTP Server and IBM HTTP Server plug-in for IBM WebSphere Application Server.\n\nImportant: Download only if you want to set up Dashboard Application Services Hub in a high-availability environment. You must download all 3 images and extract them to the same location.\n\nOptional DB2 software Part number\n\nDescription\n\nCIXV0ML IBM® DB2® Enterprise Server Edition V10.5 for Linux® on AMD64 and Intel® EM64T systems (x64) Multilingual CIPH4ML IBM® DB2® 10.5 Enterprise Server Edition - Restricted Use Quick Start and Activation Multiplatform Multilingual CIWM5ML IBM® DB2® 10.5 National Language Pack for Linux® on AMD64 and Intel® EM64T systems (x64) Multilingual Back to top\n\nSee Jazz for Service Management Detailed System Requirements [http://www.ibm.com/support/docview.wss?uid=swg27038732] for the Linux on System z operating systems on which Jazz for Service Management is supported.\n\nDownloadable images with part numbers\n\nYou can download electronic images for Jazz for Service Management and its database and application server middleware. Refer to the following sections for details about the images that are required and optional.\n\n * Required software\n * Optional software\n\nRequired software Part number\n\nDescription\n\nCNC1QML Jazz for Service Management 1.1.3.0 for Linux® on System z®; 64-bit; Multilingual\n\nContains the Jazz for Service Management launchpad; IBM Installation Manager Version 1.8.4.1; IBM Prerequisite Scanner Version 1.2.0.18; IBM Tivoli Directory Integrator Identity Edition Version 7.1.1.5; and the Installation Manager software packages for following integration service: IBM Dashboard Application Services Hub Version 3.1.3.0.\n\nCNC1UML IBM® Tivoli® Common Reporting 3.1.3.0 for Linux® on System z®; Multilingual\n\nContains the base installation image.\n\nOptional software Download the following supplemental software under the following conditions:\n\n * If you want to install Jazz for Service Management and its database and application server middleware on a single server for evaluation and development purposes; also referred to as a full installation.\n * If you do not have an existing supported version of WebSphere Application Server.\n * If you do not have an existing supported version of DB2 Enterprise Server Edition and you want to install Tivoli Common Reporting or Dashboard Application Services Hub in a high-availability environment.\n * If you want to set up Dashboard Application Services Hub in a high-availability environment.\n\nOptional WebSphere Application Server software Part number\n\nDescription\n\nCNC20ML IBM® WebSphere® Application Server 8.5.5.9 for Jazz for Service Management for Linux® on System z®; 64-bit; Multilingual\n\n \n\nContains WebSphere Application Server Version 8.5.5.9 and IBM WebSphere SDK for Java Technology Edition 7.0.8.0\n\nCI6X0ML\nCI6X1ML\nCI6X2ML\nIBM® WebSphere® Application Server V8.5 Supplements (1 of 3) for Multiplatform; Multilingual\nIBM® WebSphere® Application Server V8.5 Supplements (2 of 3) for Multiplatform; Multilingual\nIBM® WebSphere® Application Server V8.5 Supplements (3 of 3) for Multiplatform; Multilingual\n\n\nContains supplemental WebSphere Application Server software; including IBM HTTP Server and IBM HTTP Server plug-in for IBM WebSphere Application Server.\n\nImportant: Download only if you want to set up Dashboard Application Services Hub in a high-availability environment. You must download all 3 images and extract them to the same location.\n\nOptional DB2 software Part number\n\nDescription\n\nCIW3SML IBM® DB2® Enterprise Server Edition V10.5 for Linux® on System z® Multilingual CIWM7ML IBM® DB2® 10.5; National Language Pack V10.5 for Linux® on System z® Multilingual Back to top\n\nSee Jazz for Service Management Detailed System Requirements [http://www.ibm.com/support/docview.wss?uid=swg27038732] for the Windows operating systems on which Jazz for Service Management is supported.\n\nDownloadable images with part numbers\n\nYou can download electronic images for Jazz for Service Management and its database and application server middleware. Refer to the following sections for details about the images that are required and optional.\n\n * Required software\n * Optional software\n\nRequired software Part number\n\nDescription\n\nCNC1RML Jazz for Service Management 1.1.3.0 for Windows; 64-bit; Multilingual\n\nContains the Jazz for Service Management launchpad; IBM Installation Manager Version 1.8.4.1; IBM Prerequisite Scanner Version 1.2.0.18; IBM Tivoli Directory Integrator Identity Edition Version 7.1.1.5; and the Installation Manager software packages for following integration services: IBM Dashboard Application Services Hub Version 3.1.3.0.\n\nCNC1VML IBM® Tivoli® Common Reporting 3.1.3.0 for Windows; Multilingual\n\nContains the base installation image.\n\nOptional software Download the following supplemental software under the following conditions:\n\n * If you want to install Jazz for Service Management and its database and application server middleware on a single server for evaluation and development purposes; also referred to as a full installation.\n * If you do not have an existing supported version of WebSphere Application Server.\n * If you do not have an existing supported version of DB2 Enterprise Server Edition and you want to install Tivoli Common Reporting or Dashboard Application Services Hub in a high-availability environment.\n * If you want to set up Dashboard Application Services Hub in a high-availability environment.\n * If you want to model business data views of your data by using Framework Manager.\n\nOptional WebSphere Application Server software Part number\n\nDescription\n\nCNC21ML IBM® WebSphere® Application Server 8.5.5.9 for Jazz for Service Management for Windows; 64-bit; Multilingual\n\n \n\nContains WebSphere Application Server Version 8.5.5.9 and IBM WebSphere SDK for Java Technology Edition 7.0.8.0\n\nCI6X0ML\nCI6X1ML\nCI6X2ML\nIBM® WebSphere® Application Server V8.5 Supplements (1 of 3) for Multiplatform; Multilingual\nIBM® WebSphere® Application Server V8.5 Supplements (2 of 3) for Multiplatform; Multilingual\nIBM® WebSphere® Application Server V8.5 Supplements (3 of 3) for Multiplatform; Multilingual\n\n\nContains supplemental WebSphere Application Server software; including IBM HTTP Server and IBM HTTP Server plug-in for IBM WebSphere Application Server.\n\nImportant: Download only if you want to set up Dashboard Application Services Hub in a high-availability environment. You must download all 3 images and extract them to the same location.\n\nOptional DB2 software Part number\n\nDescription\n\nCIW3YML IBM® DB2® Enterprise Server Edition V10.5 for Windows on AMD64 and EM64T systems (x64) Multilingual CIPH4ML IBM® DB2® 10.5 Enterprise Server Edition Restricted Use Quick Start Guide and Activation Optional Tivoli Common Reporting 3.1.2.0 software Part number\n\nDescription\n\nCNC1WML IBM® Tivoli® Common Reporting 3.1.3.0 IBM® Cognos® Framework Manager for Windows; Multilingual\n\nCNC1XML IBM® Tivoli® Common Reporting 3.1.3.0 IBM® Cognos® Cube Designer for Windows; Multilingual\n\nBack to top\n\nConnect; learn; and share with the Jazz for Service Management Community Jazz for Service Management has an active community that can provide you with additional resources. Browse and contribute to the forums and the blog. Review the wiki on topics such as best practices. You can also learn more about upcoming releases; provide feedback; or suggest enhancements.\nSee the Jazz for Service Management community [https://www.ibm.com/developerworks/servicemanagement/jazzsm/index.html] on Service Management Connect.", "question": "Web GUI 8.1 FP7 requires DASH 3.1.2.1 or later \n\nYou wanted to install Web GUI 8.1 FP7, but your DASH version does not meet the required version.\n\nIM 1.8 displayed the following:\n\n     ERROR: The installed IBM Dashboard Application Services Hub version is 3.1.0.3, but requires version 3.1.2.1 or later.\n\n", "answer": "Version 1.1.3.0 is a full refresh of Jazz for Service Management Version 1.1 Base with Modification 3."}
{"id": "VAL_Q002", "document": "IBM Unable to open a profile in FileNet Content Engine Configuration Manager User Interface (CMUI) on Redhat Linux 7.x - United States  TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Unable to open a profile in FileNet Content Engine Configuration Manager User Interface (CMUI) on Redhat Linux 7.x. \n\nSYMPTOM\nCMUI will javacore with the following in the javacore.txt \n\n1XHEXCPCODE J9Generic_Signal_Number: 00000004\n1XHEXCPCODE Signal_Number: 0000000B\n1XHEXCPCODE Error_Value: 00000000\n1XHEXCPCODE Signal_Code: 00000080\n1XHEXCPCODE Handler1: F7169E6A\n1XHEXCPCODE Handler2: F711400A\n1XHEXCPCODE InaccessibleAddress: 00000000\nNULL\n1XHEXCPMODULE Module: /lib/libcairo.so.2\n1XHEXCPMODULE Module_base_address: D5436000 \n\n\nCAUSE\n\"adwaita-gtk2-theme\" (32 and 64 bit) and \"adwaita-gtk3-theme\" 64 bit libraries were missing. \n\n\n\nRESOLVING THE PROBLEM\nInstall the missing libraries \"adwaita-gtk2-theme\" (32 and 64 bit) and \"adwaita-gtk3-theme\" 64 bit. Please contact RedHat to obtain the missing libraries.", "question": "Unable to open profile from P8 Content Engine Configuration manager (CMUI) on Redhat Linux 7.2, getting GPF and javacore dump. \n\nLaunch configmgr then try to open an existing profile. Once I click ok on the dialog box to\n\"Verify your application server setting before proceeding...\" Configuration manager would crash and GPF. I can see the javacore.txt and dmp file created.\nThe javacore.txt contains the following:\n\n0SECTION TITLE subcomponent dump routine NULL =============================== 1TICHARSET UTF-8 1TISIGINFO Dump Event \"gpf\" (00002000) received 1TIDATETIME Date: 2016/05/05 at 04:53:30 1TIFILENAME Javacore filename: /opt/IBM/FileNet/ContentEngine/tools/configure/javacore.20160505.045330.25035.0002.txt 1TIREQFLAGS Request Flags: 0x81 (exclusive+preempt) 1TIPREPSTATE Prep State: 0x100 (trace_disabled) 1TIPREPINFO Exclusive VM access not taken: data may not be consistent across javacore sections NULL ------------------------------------------------------------------------ 0SECTION GPINFO subcomponent dump routine NULL ================================ 2XHOSLEVEL OS Level : Linux 3.10.0-327.13.1.el7.x86_64 2XHCPUS Processors - 3XHCPUARCH Architecture : x86 3XHNUMCPUS How Many : 1 3XHNUMASUP NUMA is either not supported or has been disabled by user NULL\n1XHEXCPCODE J9Generic_Signal_Number: 00000004 1XHEXCPCODE Signal_Number: 0000000B 1XHEXCPCODE Error_Value: 00000000 1XHEXCPCODE Signal_Code: 00000080 1XHEXCPCODE Handler1: F72A2E6A 1XHEXCPCODE Handler2: F724D00A 1XHEXCPCODE InaccessibleAddress: 00000000 NULL\n1XHEXCPMODULE Module: /lib/libcairo.so.2 1XHEXCPMODULE Module_base_address: D55FC000\n\nThis is a Redhat Linux 7.2 environment with Content Platform Engine CPE 5.2.1.4.", "answer": "Install the missing libraries \"adwaita-gtk2-theme\" (32 and 64 bit) and \"adwaita-gtk3-theme\" 64 bit. Please contact RedHat to obtain the missing libraries."}
{"id": "VAL_Q007", "document": "IBM Netcool/OMNIbus Integrations Release Notice - Socket Gateway (nco-g-socket-java-2_0) - United States release note; downloads; nco-g-socket-java; Java Gateway for Socket NEWS\n\nABSTRACT\n A new version of the Netcool/OMNIbus Socket Gateway will be available to download from August 6, 2015. \n\nCONTENT\n \n\nYou can access the latest version of the guide written for this gateway on the IBM Knowledge Center:\n\nwww.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/gateways/socketjavagw/wip/concept/socketjavagw_instl_cnfgr_gateway.html [http://www.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/gateways/socketjavagw/wip/concept/socketjavagw_instl_cnfgr_gateway.html]\n\nYou can download the installation package from the IBM Passport Advantage website: \nwww.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\n\nNetcool/OMNIbus V8.1\n\nThe Netcool/OMNIbus V8.1 version of this gateway supports the following Operating Systems:\n\nAIX, Linux, Solaris, Windows and zLinux.\n\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the gateway for all supported Operating Systems. To obtain this package, use the Find by part number field to search for part number: CN6I1EN\n\nNetcool/OMNIbus V7.4.0\n\nIf you are running Netcool/OMNIbus V7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.\n\nPart number Operating System CN6GZEN AIX CN6H1EN HPUX on Itanium CN6H2EN Linux CN6H3EN Linux for zSeries CN6H4EN Solaris CN6H5EN Windows Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.\n\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:\n\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html]", "question": "Which Socket Gateway should I be using with Netcool Omnibus (NOI) ? Which Socket Gateway should I be using with Netcool Omnibus (NOI) ?\n\nThere are 2 versions of the gateway; nco-g-socket-java-2_0 and nco-g-socket-10_0 Users may be confused what version they should download or use ", "answer": "A new version of the Netcool/OMNIbus Socket Gateway will be available to download from August 6, 2015."}
{"id": "VAL_Q008", "document": "IBM How to export and import keys from an HSM-enabled IBM WebSphere DataPower SOA Appliance - United States  TECHNOTE (FAQ)\n\nQUESTION\n How do I export and import private keys between the same or different Hardware Security Module (HSM) enabled IBM WebSphere DataPower SOA Appliance? \n\nANSWER\nHSM-enabled DataPower appliances support the export of private keys using the crypto-export command. For key export to work, various conditions must be met: \n\n * HSMs must be initialized and in the same key sharing domain on exporting and importing machines \n * The private key in question must be marked exportable at keygen time (see keygen's exportable option) \n * HSMs on exporting and importing machines must share internal key-wrapping keys (see hsm-clone-kwk command). A key-wrapping key is a key that encrypts another key.\n\n\nEach HSM has a special key inside of it, the key-wrapping key, that is used to encrypt exported private keys (and to decrypt imported private keys). If the goal is to restore exported keys to the same appliance, then you don't need to worry about hsm-clone-kwk, red keys, or the hsm-domain parameter. That is because the key-wrapping key at import time will already match the key-wrapping key at export time (since the HSM device is the same). If the goal is to move exported keys from one appliance to another one, then all of the steps in this section must be followed :- \n\nFirst, the two HSMs in question must be both be initialized and in the same key sharing domain. This means that they must both be initialized in the same mode (both in Security Level 2 or both in Security Level 3). In Security Level 2 mode, they must have used the same hsm-domain parameter during hsm-reinit (this parameter has a default value that is the same on all appliances). In Security Level 3 mode, they must have used the same red PED key during hsm-reinit (and the second initialization must not have overwritten the key value from the first initialization). \n\nSecond, the key to be exported must be exportable. The exportability of keys is immutable. It is determined at keygen time, and it is controlled by that command's exportable parameter. If a key was created outside of the appliance (not using keygen), then it is always considered exportable. \n\nFinally, before the crypto-export crypto-import sequence, the key-wrapping keys must be synchronized using the hsm-clone-kwk command. This command must be run four times: once on the source HSM appliance (with the key-wrapping key you are copying), once on the destination HSM appliance, once again on the source HSM appliance, and once again on the destination HSM appliance. Each time the command is run, it will need the output file from the previous step (as the input to the current step) which must be moved manually (usually with the copy command). \n\nOnce all of this has been done, then private keys may move from system to system with crypto-export and crypto-import. \n\nNote that the non-HSM appliance can export keys immediately at keygen time, but never at a later time. \n\nFor additional information refer to the online Info Center [http://publib.boulder.ibm.com/infocenter/wsdatap/v3r8m2/index.jsp?topic=%2Fxi50%2Fwelcome.htm] and search for \"PIN entry device\".\n\nNote: You will need to sign into the documentation portal with your IBM Registration ID and password.", "question": "How can I export a private key from DataPower Gateway Appliance? \n\nHow can I export a private key from DataPower Gateway appliance?\n\n", "answer": "HSM-enabled DataPower appliances support the export of private keys using the crypto-export command."}
{"id": "VAL_Q010", "document": "IBM 'EJPDB0160E: The sanity checks of the database layer failed' error occurs during startup after successful database transfer - United States EJPDB0160E: The sanity checks of the database layer failed. EJPDB0160E TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After receiving a 'Build Successful' message during a database transfer for IBM® WebSphere® Portal, you attempt to start WebSphere_Portal and receives this error message, \"EJPDB0160E: The sanity checks of the database layer failed\". \n\nSYMPTOM\nThe entire error message and stack trace will appear like this in the SystemOut.log: \n\n=======================================================================================\n\n[8/19/08 15:51:50:788 EDT] 0000001e DataStoreServ W com.ibm.wps.services.datastore.DataStoreServiceImpl checkCorrectSetup EJPDB0085W: The character encoding of the database is not UTF-8.\n[8/19/08 15:51:50:822 EDT] 0000001e Servlet E com.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of service failed.\ncom.ibm.wps.util.DataBackendException: EJPDB0160E: The sanity checks of the database layer failed.\nat com.ibm.wps.services.datastore.DataStoreServiceImpl.checkCorrectSetup(DataStoreServiceImpl.java:669)\nat com.ibm.wps.services.datastore.DataStoreServiceImpl.init(DataStoreServiceImpl.java:288)\nat com.ibm.wps.services.Service.init(Service.java:107)\nat com.ibm.wps.services.Service.init(Service.java:83)\nat com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:391)\nat com.ibm.wps.services.ServiceManager.initInternal(ServiceManager.java:285)\nat com.ibm.wps.services.ServiceManager.init(ServiceManager.java:179)\nat com.ibm.wps.services.ServiceManager.init(ServiceManager.java:114)\nat com.ibm.wps.engine.Servlet.init(Servlet.java:239)\nat com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:199)\nat com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:319)\nat com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1230)\nat com.ibm.ws.wswebcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:152)\nat com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:99)\nat com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:849)\nat com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:771)\nat com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:491)\nat com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:328)\nat com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:290)\nat com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:90)\nat com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157)\nat com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:665)\nat com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:618)\nat com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:335)\nat com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:551)\nat com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1303)\nat com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1138)\nat com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:569)\nat com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:817)\nat com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:949)\nat com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2122)\nat com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:342)\nat com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)\n\n======================================================================================\n\n\nCAUSE\nThe database was not created using UTF-8 character encoding. \n\n\nDIAGNOSING THE PROBLEM\nOn an Oracle® environment you can run these SQL statements to determine the character sets: \n\n\n\nSELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER IN ('NLS_CHARACTERSET', 'NLS_NCHAR_CHARACTERSET'); \nSELECT PROPERTY_VALUE FROM DATABASE_PROPERTIES WHERE PROPERTY_NAME IN \n('NLS_CHARACTERSET', 'NLS_NCHAR_CHARACTERSET'); \n\nIn this case the customer had these results for both SQL statements:\n\n============================= \nPROPERTY_VALUE \n------------- \nWE8ISO8859P1 \nAL16UTF16 \n=============================\n\nIf the database character sets had been setup correctly then both lines would have read \"AL16UTF16\". In this case NLS_CHARACTERSET returns \"WE8ISO8859P1\" which is not a supported format. If the database had been setup correctly both lines would have produced \"AL16UTF16\". \n\n\n\nRESOLVING THE PROBLEM\nAt this point there is no way to salvage the database in its current state. The entire Portal database must be dropped and recreated using the specifications provided in the InfoCenter at this link: \n\n\nhttp://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.e [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/index.jsp?topic=/com.ibm.wp.ent.doc/config/aix_oracle_create_db.html]\nnt.doc/config/aix_oracle_create_db.html [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/index.jsp?topic=/com.ibm.wp.ent.doc/config/aix_oracle_create_db.html] \n\nThis is the specific information in the Information Center pertaining to character encoding:\n\n=============================\n\nAll databases must be created using UNICODE Database and National character sets such as UTF8, AL32UTF8, or AL16UTF16. \n\n=============================", "question": "We transferred the database to an external database on our Portal 8.5 environment and now seeing errors, EJPDB0085W and EJPFD0016E in the logs \n\nAfter transferring the Portal database we seeing the following....\n\n     [3/1/16 6:22:19:481 CST] 00000071 DataStoreServ W com.ibm.wps.services.\n     datastore.DataStoreServiceImpl checkCorrectSetup EJPDB0085W: The\n     character encoding of the database is not UTF-8.\n     [3/1/16 6:22:19:528 CST] 00000071 Servlet       E com.ibm.wps.engine.\n     Servlet init EJPFD0016E: Initialization of service failed.\n                                      com.ibm.wps.util.DataBackendException:\n     EJPDB0160E: The sanity checks of the database layer failed.\n                     at com.ibm.wps.services.datastore.DataStoreServiceImpl.\n     checkCorrectSetup(DataStoreServiceImpl.java:712)\n                     at com.ibm.wps.services.datastore.DataStoreServiceImpl.\n     init(DataStoreServiceImpl.java:288)\n\n...\n\n     [3/1/16 6:22:19:824 CST] 00000071 DatabaseInsig W com.ibm.wps.datastore.\n     dbinsight.DatabaseInsight checkCharacterEncodingForOracle EJPDB0166W:\n     The character encoding of database domain [[Domain: jcr]] is not\n     correct. The value [WE8MSWIN1252] is set for key [NLS_CHARACTERSET] in\n     parameter section [NLS_DATABASE_PARAMETERS] where expected values only\n     can contain one of [[UTF8, AL16UTF16, AL32UTF8, UTFE]].\n\\", "answer": "At this point there is no way to salvage the database in its current state. The entire Portal database must be dropped and recreated using the specifications provided in the InfoCenter at this link: \n\n\nhttp://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.e [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/index.jsp?topic=/com.ibm.wp.ent.doc/config/aix_oracle_create_db.html]"}
{"id": "VAL_Q011", "document": "IBM How to process an IBM SDK core dump with Jextract (AIX, Linux, Windows) - United States crash; coredump; dumps; dump; dmp; dmps; jextracted; jextract; userdump; dtfj TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n How do you process a raw core dump using Jextract? \n\nJextract is a tool provided with the IBM SDK to process and compress a core dump for later processing with tools such as DTFJ, which can be downloaded with IBM Support Assistant. \n\nRESOLVING THE PROBLEM\nYou can process a core dump with Jextract, as long as the dump itself was produced by the IBM WebSphere Application Server JVM and is processed on the same system as the dump. \n\nA processed dump can be used in both the Eclipse Memory Analyzer Tool [http://www.ibm.com/developerworks/java/jdk/tools/mat.html] and the DTFJ Dump Analyzer [http://www.ibm.com/developerworks/java/jdk/tools/dumpanalyzer/]. Both are included as downloadable tools from within IBM Support Assistant Workbench [http://www.ibm.com/software/support/isa/]. \n\n\n\n\nLocating the Core Dump \n\nFor WebSphere Application Server installations, the default location for the core dumps is in the profile's root directory: <WAS_HOME>/profiles/<PROFILE_NAME>/ \n\nThe file extension will usually be *.dmp, but on some versions of AIX and Linux, the file may simply be named core. The process id and the date stamp are normally appended to the name of the file. \n\n\n\n\nProcessing the Dump \n\nExecute the jextract command on the same system and installation of WebSphere Application Server that the core dump was produced on. If you don't use the full path on AIX or Linux, make sure to use ./jextract (including the dot-slash) so the correct executable is picked up. \n\nReplace [COREDUMP_PATH] with the full path plus filename of the core dump produced. \n\n \n\nIf you do not know if compressed references is enabled, scroll to the FAQ section for a brief explanation. \n\n \n\nDetermining the Java Directory \n\nBecause different profiles on WebSphere Application Server 8.5.5.X and later can use different SDKs, the java directory inside the installation folder can differ. To determine the path, check the process list for the application server process and see which folder the java executable is being launched from. \n\n \n\nNOTE: If you are on WebSphere Liberty and are using an IBM SDK, the entire path to that SDK will differ. \n\n \n\n\n\n\n32-bit JVM and\n64-bit JVM with Compressed References disabled\nAIX/Linux: \n<WAS_HOME>/<JAVA_DIR>/jre/bin/jextract [COREDUMP_PATH]\n\nWindows: \n<WAS_HOME>\\<JAVA_DIR>\\jre\\bin\\jextract.exe [COREDUMP_PATH]\n\n\n\n\n64-bit JVM with Compressed References enabled\nDoes not apply to WebSphere Application Server 6.1\nAIX/Linux: \n<WAS_HOME>/<JAVA_DIR>/jre/bin/jextract -J-Xcompressedrefs [COREDUMP_PATH]\n\nWindows: \n<WAS_HOME>\\<JAVA_DIR>\\jre\\bin\\jextract.exe -J-Xcompressedrefs [COREDUMP_PATH] \n\n \n\n\n\n\nMax Heap Size \n\nTo adjust the max heap size, you can add -J-Xmx to adjust the size. For example, -J-Xmx1024m allows for a max heap size of 1024 MB when jextract is run. \n\n \n\n \n\n\n\n\nFiles Generated \n\nThe output will determine where the compressed data is stored (usually a .zip extension, .sdff is seen on older environments). Check the location of the core dump as that will be the most common location. \n\nCore files are usually compressible since a lot of data is zero; 10x compression can be expected in the resulting zip file \n\n \n\nIf you find XML files in the output directory, this may mean jextract failed, as these files are supposed to be placed automatically within the SDFF or ZIP file. \n\n \n\n\n\n\nError Messages \n\nEyeCatcher Error\nUnable to find J9VMRAS eyecatcher\nError. Internal failure detected during jextract \n\nThis error message indicates that jextract failed to identify the dump. This could be due to a number of things, including \n\n* The dump was not produced by WebSphere Application Server\n* The dump was produced from a native library or component such as a JNI component or database driver.\n* (AIX only) The dump generated is in an incompatible dump format due to an AIX OS issue (see APAR IZ88097 [http://www.ibm.com/support/docview.wss?uid=swg1IZ88097] for more details). \n\n \n\nOut of Memory Error \n\nSometimes the core dump is much larger than the default heap size can manage, and the recommendation is to increase the heap size using the -J-Xmx option. \n\n \n\n\n\n\nFAQ \n\nHow do I determine if compressed references is enabled? \n\nCompressed references were first introduced in 64-bit builds of IBM SDK 6.0. If WebSphere Application Server is at version 7.0.0.3 or higher, it will be enabled by default; see APAR PK75174 [http://www.ibm.com/support/docview.wss?uid=swg1PK75174]. \n\nChecking the JVM arguments in the admin console can verify if compressed references was enabled manually. However, it's best to check the ps output or the javacore for the argument -Xcompressedrefs \n\nIf you find the argument -Xnocompressedrefs has been added, this means it's disabled (see page 7 of this document [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf] for more info)) \n\n \n\nWhat happens to jextract if I cannot determine if compressed references was enabled? \n\nIf you run jextract and did not realize compressed references was enabled, the output will ask you to rerun jextract and add the following argument: -J-Xcompressedrefs \n\n\n\nRELATED INFORMATION\n MustGather: Crash on AIX [http://www.ibm.com/support/docview.wss?uid=swg21055387]\nMustGather: Crash on Linux [http://www.ibm.com/support/docview.wss?uid=swg21104706]\nMustGather: Crash on Windows [http://www.ibm.com/support/docview.wss?uid=swg21053924]\nGenerating Userdumps on Windows [http://www.ibm.com/support/docview.wss?uid=swg21138203]\nCrash on AIX produces no core or a truncated core [http://www.ibm.com/support/docview.wss?uid=swg21052642]\nCrash on Linux produces no core or a truncated core [http://www.ibm.com/support/docview.wss?uid=swg21115658]", "question": "How to proceed when jextract utility is throwing an OutOfMemory error ? \n\nI was getting a crash and was told to provide a \"jextracted core dump\". I ran the jextract command as instructed:\n\n/java/jre/bin/jextract [CORE_PATH]\n\nbut I am getting now an OutOfMemory error when jextract itself is running so I cannot proceed with the original crash investigation.", "answer": "Sometimes the core dump is much larger than the default heap size can manage, and the recommendation is to increase the heap size using the -J-Xmx option."}
{"id": "VAL_Q012", "document": "IBM UDX compilation error - United States  TECHNOTE (TROUBLESHOOTING)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n English \n\nPROBLEM(ABSTRACT)\n Following error can be met during UDX compilation.\nCan't exec \"/nz/kit/bin/adm/nzudxcompile\": Argument list too long \n\nSYMPTOM\nnzudxcompile command returns an \"Argument list too long\" error and aborts.\n\n\nCAUSE\nARG_MAX configuration parameter limits the number of argument list in command line. In this case the client used more than 131072 argument with many program *.c files.\n\nDIAGNOSING THE PROBLEM\nCheck ARG_MAX value in the command line: \n\n$ getconf ARG_MAX\n131072\n\n\nRESOLVING THE PROBLEM\nThis ARG_MAX kernel parameter adjusted to much larger from kernel release version 2.6.23, that is 2621440 (http://www.in-ulm.de/~mascheck/various/argmax [http://www.in-ulm.de/~mascheck/various/argmax]). \n\nBut we support upto Redhat 5.11 in Twinfin which is less than kernel release 2.6.23. So we have no way to allow ARG_MAX larger than 131072 at this time.", "question": "I receive the following during UDX compilation Can't exec \"/nz/kit/bin/adm/nzudxcompile\": Argument list too long ", "answer": "This ARG_MAX kernel parameter adjusted to much larger from kernel release version 2.6.23, that is 2621440 (http://www.in-ulm.de/~mascheck/various/argmax [http://www.in-ulm.de/~mascheck/various/argmax]). \n\nBut we support upto Redhat 5.11 in Twinfin which is less than kernel release 2.6.23. So we have no way to allow ARG_MAX larger than 131072 at this time."}
{"id": "VAL_Q013", "document": "IBM When and how to apply a modification or fix pack - United States fix pack update bug correction APAR TECHNOTE (FAQ)\n\nQUESTION\n When and how should I apply a modification or fix pack to my JRules or Operational Decision Management (WODM/ODM) installation?\n\n\nCAUSE\nThe Operational Decision Manager version numbers use the standard IBM formatV.R.M.Fwhich stands for Version.Release.Modification.Fixpack. See the V.R.M.F Maintenance Stream Delivery Vehicle terminology explanation [http://www.ibm.com/support/docview.wss?uid=swg27008656] for more details. \n\n\nModification and fix pack numbers are the third and fourth digits in the IBM product version number, for example: 8.5.M.F. \n\n\nModification and fix packs include only bug fixes, so they do not affect the product functionality or your data.\n\n\nSee the following technotes to find out which update your installation need:\n\n\n * Finding the version of ODM product and fixes [http://www.ibm.com/support/docview.wss?uid=swg21627850] to determine the exact product versions that are installed on your machine.\n   \n * Find the version of ODM components [http://www.ibm.com/support/docview.wss?uid=swg21400738] to determine the exact module or library versions that are deployed on your servers.\n   \n * Operational Decision Manager Download document [http://www.ibm.com/support/docview.wss?uid=swg24031636] to learn about the latest modification or fix pack that is available for your product version. \n   \n * IBM Operational Decision Manager detailed system requirements [http://www.ibm.com/support/docview.wss?uid=swg27023067] to verify that your configuration is supported with your current product version.\n   \n * IBM Support Lifecycle [http://www.ibm.com/software/websphere/support/lifecycle/] to verify that your current version does not reach end of support in the near future.\n\n\n\nReferring to the last two documents above, you may find out that you need to migrate to the latest product version to ensure continued support of your applications. In that case, refer to technote Migrating to the latest version of Operational Decision Management [http://www.ibm.com/support/docview.wss?uid=swg21589725]. \n\nThat being said, make sure to consider migrating to the latest version or release ( V.R.M.F) of the product as soon as possible to benefit from the latest added features and improvements. \nANSWER\nAs with any software product, even if you do not have any issues with running your current configuration, you should apply the latest modification or fix pack to take advantage of these benefits: \n\n * Anticipate and avoid the risk of encountering defects already fixed. \n * Apply the latest product improvements that are available (performance, for example). \n * Maintain a serviceable system and be able to install an interim fix when required.\n\n\n\nWHEN TO UPDATE\nThe latest modification or fix pack should be installed as soon as it is available. \n\nYou can subscribe to the IBM Support My Notifications [https://www.ibm.com/support/mynotifications] to be notified of any fix pack releases, and you can also bookmark the Operational Decision Manager Download document [http://www.ibm.com/support/docview.wss?uid=swg24031636] page, which lists the latest modifications or fix packs. \n\nSee the technote Fix pack release notification for Operational Decision Manager [http://www.ibm.com/support/docview.wss?uid=swg21665593] to find out when a modification or fix pack will be available.\n\n\n\n\n\n\nBEFORE UPDATING\n\n\nThe databases used in the sample server are deleted and recreated during the update. If you are using those databases and want to save the existing content, perform the following steps before updating: \n *  Stop the sample server. In the folder <ODM_HOME>/shared/data/derby, create an archive file containing the resdb and rtsdb folders. Save the archive file, such as zip file, in the data folder. After installation, unzip the archive file in the folder <ODM_HOME>/shared/data/derby to restore your databases before restarting the sample server. \n\n\n\nA new profile is also created for the sample server, at the first server start following the installation of a modification or fix pack. \n\nIf you want to continue using the same ports, you must delete the existing profile prior. In the <ODM_HOME>/shared/bin folder, from the command line, run the command ../tools/ant/bin/ant forcedestroyprofile. \n\n\nNote: The sample server is not designed to be used in a production system. For a production system, you must create a dedicated profile and database that you update using the following steps. \n\n\n\n\nUPDATING\n\n\nEach modification or fix pack page provides instructions on how to download and run the installer, in addition to providing a list of corrections that are included in the update. \n\nThe fix pack installation updates the following files and folders:  * JAR libraries in the installation directories, including <ODMInstallDir>\\<Module>\\lib. \n * EAR and WAR applications in the <ODMInstallDir>\\<Module>\\applicationservers\\<App Server> folders.\n\n\nOnce this is done, you perform these tasks:  * Repackage your client applications with the up-to-date libraries. \n * Reapply product customizations to the up-to-date Java EE modules (EARs and WARs).\n\n\n\nNote that all customizations you developed before the update, for example modifications of the descriptors, must be reapplied to the new, up-to-date EARs and WARs. It is a good idea to document and automate those customizations using scripts to make the process easier and error-proof. \n\nFinally, you must update the client applications and ODM modules on your server or servers with the same settings as you deployed previously. If you redeploy the application, follow again the documentation instructions to deploy all ODM modules to your servers [http://pic.dhe.ibm.com/infocenter/dmanager/v8r5m1/topic/com.ibm.odm.distrib.config/topics/odm_distrib_config.html]. \n\nKeep in mind that applying a modification or a fix pack does not require any data migration, so your projects and database remain the same. \n\nUPDATING RULE EXECUTION SERVER\n\n\nUpdate the following applications in the application server:  *  jrules-res-xu-<server>.rar jrules-res-management-<server>.ear jrules-ssp-<server>.ear jrules-res-htds-<server>ear \n\n\nMake sure you do not change the class loading policies for applications and modules ( parent last for all ODM modules). \n\nNote: Updating the eXecution Unit RAR file requires a restart of the server. \n\n\nUPDATE DECISION CENTER\n\n\nUpdate the following application in your application server: \n * jrules-teamserver-<server>.ear\n\n\nMake sure you do not change the class loading policies for applications and modules ( parent last for all ODM modules). \n\nUPDATE THE EVENTS RUNTIME\n\n 1. Stop the event runtime application, wberuntimeear. \n 2. Uninstall the following applications, if they exist:  * wbefileconnector \n     * wbehttpconnector \n     * wbejdbcconnector \n     * wbejmsconnector \n     * wbesoapconnector\n    \n    \n 3. Update the application wberuntimeear. \n 4. Start the application wberuntimeear.\n\n\nMake sure you do not change the class loading policies for applications and modules ( parent last for all ODM modules). \n\n\n\n\nADDITIONAL CONSIDERATIONS\n * Again, in addition to applying the latest modification or fix pack, consider migrating to the latest version or release (V.R.M.F) of the product as soon as possible to benefit from recently added features and improvements. See our technote Migrating to the latest version of Operational Decision Management [http://www.ibm.com/support/docview.wss?uid=swg21589725] for more information. \n * For JRules 7.1, you can refer to the JRules 7.1 list of fix packs [http://www.ibm.com/support/docview.wss?uid=swg27019787] and also Upgrading JRules to the latest V7.1 fix pack [http://www.ibm.com/support/docview.wss?uid=swg21474292] to learn how to apply the fix packs. But note that JRules 7.1 reaches end of support in September 2015 (see the IBM Support Lifecycle [http://www.ibm.com/software/websphere/support/lifecycle/] page). To ensure continued product support, plan an upgrade to the latest product version before that date.\n\nRELATED INFORMATION\n Fix pack release notification for ODM [http://www.ibm.com/support/docview.wss?uid=swg21665593 ]\n\n\n \n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere ILOG JRules Maintenance Platform Independent 7.1, 7.0", "question": "Additional steps to apply fix pack to Decision Center \n\nWe are upgrading ODM 8.8.1 Decision Center to the latest 8.8.1.3.\n\nAre there any additional steps to apply the fixpack to Decision Center after we install the fixpack with Installation Manager?", "answer": "As with any software product, even if you do not have any issues with running your current configuration, you should apply the latest modification or fix pack to take advantage of these benefits: \n\n * Anticipate and avoid the risk of encountering defects already fixed. \n * Apply the latest product improvements that are available (performance, for example). \n * Maintain a serviceable system and be able to install an interim fix when required."}
{"id": "VAL_Q014", "document": "IBM Java SDK Upgrade Policy for the IBM WebSphere Application Server - United States upgrade policy TECHNOTE (FAQ)\n\nQUESTION\n What is the Java™ SDK upgrade policy for the IBM® WebSphere® Application Server? \n\nCAUSE\nUpdating to the latest compatible Java SDK could help you resolve problems more quickly.\n\nANSWER\nThe IBM WebSphere Application Server Java SDK can be upgraded to the latest service release for the same Java SDK version. \n\nList of WebSphere Application Server fix packs and the corresponding Java SDK versions [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27005002]\n\nPolicy Summary by WebSphere Application Server release:\n\nWebSphere Application Server V8.0, V8.5, V8.5.5\nStarting with V8.0 and applicable to all subsequent releases and fixpacks, there is one install package that contains updates for both WebSphere Application Server and Java SDK. Applying fixpacks of WebSphere Application Server also upgrades the SDK that is packaged and bundled within the fixpack. Additionally, separate Java SDK fixpacks are also available that contain just the SDK updates which can be applied to upgrade the SDK.\n\nWebSphere Application Server V7.0\nAny V7.0 fix pack can upgrade to the latest Java SDK 1.6.0 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V6.1\nAny V6.1 fix pack can upgrade to the latest Java SDK 1.5.0 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V6.0\nAny V6.0 fix pack can upgrade to the latest Java SDK 1.4.2 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V5.1\nAny V5.1 fix pack can upgrade to the latest Java SDK 1.4.1 and any V5.1.1 can be upgraded to the latest Java SDK 1.4.2 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V5.0\nAny V5.0 fix pack can upgrade to the latest Java SDK 1.3.1 service release packaged for WebSphere Application Server.\n\n\n\nDetails of Java SDK Upgrade Policy\n\nWebSphere Application Server leverages the Java SDK as a base component. This results in unique support issues, including:\n\n\n * Matching Java SDK service releases to Application Server releases and fix packs\n   \n   \n * Delivering updates and fixes associated with the Java SDK on any given Application Server release.\n\n\nIn an effort to resolve customer Java SDK situations as quickly as possible, WebSphere Application Server Support has done a quickest-path-to-resolution analysis, determining the most direct way to collect problem information. \n\nIn some cases, problem resolution might include finding shortcuts to resolve symptoms. One shortcut is an immediate upgrade to a newer compatible Java SDK service release, before gathering detailed problem determination data. \n\nThere are multiple advantages to performing an immediate Java SDK upgrade as a quicker path to resolution over a full Problem Determination (PD) process: \n 1. There is a continuous stream of fixes going into the Java SDK. Many problems encountered by customers are resolved by these fixes.\n    \n    \n 2. When a new problem is encountered, applying the latest Java SDK is a quick way to determine if related fixes change the symptoms or correct the problem.\n    \n    \n 3. Many documented Java SDK fixes have common symptoms. Frequently, limited PD data does not isolate the problem to a single root cause.\n    \n\n\nThese factors highlight the advantage of applying a newer Java SDK before working through a full PD cycle. \n\nJava SDK and WebSphere Application Server software are updated frequently. To avoid compatibility issues for customers, WebSphere Application Server Support maintains this Java SDK Upgrade Policy. \n\nWebSphere Application Server Support details: \nhttp://www.ibm.com/software/webservers/appserv/support.html [http://www.ibm.com/software/webservers/appserv/support.html] \n\nIdentifying compatibility limitations between WebSphere Application Server releases and Java SDK service releases that have not been tested together reduces risk. \n\nImportant: Using a Java SDK not specifically packaged with WebSphere Application Server and supplied by IBM, or in violation of the Java SDK Upgrade Policy, is not supported by IBM WebSphere Application Server Support for Java SDK problems. RELATED INFORMATION\n Verify Java SDK version shipped with WebSphere fix pack [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27005002]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK", "question": "Installing fixpacks with Installation Manager - when did it change from using updateInstaller,  starting in which version of WebSphere I was using updateInstaller to install fixpacks, and there was a separate fixpack for WebSphere and separate for the JDK, independent of each other. Now I understand that with Installation Manager there is a single package containing both the WebSphere App server fixpack as well as the JDK. When did this occur, starting with which version of WebSphere ? ", "answer": ""}
{"id": "VAL_Q016", "document": "IBM Distribute Decision Validation Service tests on different Rule Execution Server instances - United States SSPResolver; SSP TECHNOTE (FAQ)\n\nQUESTION\n Can I configure Rules Team Server to distribute the Decision Validation Service tests to multiple application servers? \n\nCAUSE\nWith a Rule Execution Server environment defined on a domain with multiple servers it is possible to define which Rule Execution Server instances will be used to execute the Rule Team Server Decision Services\n\nANSWER\nFirst remember to pack all your XOMs (eXecutable Object Model) into the ssp.war following the documentation [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.doc/Content/Business_Rules/Documentation/_pubskel/JRules/ps_JRules_Global720.html]. \n\nThen make sure the SSP (ssp.war) is deployed on each server along with a XU connection factory and the appropriate datasource definition. \n\n \n\nThen create your own SSP resolver, add it to the teamserver.war and set the teamserver.defaultSSPResolver.class property to this class following this specification [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/index.jsp?topic=/com.ibm.websphere.ilog.jrules.doc/html/api/html/ilog/rules/teamserver/model/testing/IlrSSPResolver.html]. \n\n \n\nBy implementing your own method IlrSSPResolver.getSSPURL(String serverName,URL url), you will be able to point to something else than the default provider. \n\nThe default provider uses the url of the Rule Execution Server passed in parameter and replaces the application name with testing. \n\nA simple implementation can use the server name to return a specific server URL. \n\nfor example you can have 2 servers defined in RTS: \n\n * testingServer1 http://host1:9080/res \n * testingServer2 http://host1:9080/res\n\n\nAnd your SSP provider can evaluate the SSP URL as follow : \nif ( serverName.equals(\"testingServer1\") )\n{\nreturn ( new URL( \"http://server1:9080/testing\" ) );\n}\nelse if ( serverName.equals(\"testingServer2\") )\n{\nreturn ( new URL( \"http://server2:9080/testing\" );\n}\nelse \nreturn( new URL( \"http://host1:9080/testing\" )); \n\n \n\nThen when running a DVS test the execution will be dispatched according to the server you choose. \n\n \n\nFor a more elaborate implementation you can have a dependency with the project being tested so that you can distribute the DVS execution based on a project: \n\n\nManagerBean bean = ManagerBean.getInstance() ; \nIlrSession session = bean.getSession(); \nIlrRuleProject project = session.getWorkingBaseline().getProject();\nString pname = project.getName(); \n\n.\n\nRELATED INFORMATION\n#Repackaging the XOM for remote testing [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.doc/Content/Business_Rules/Documentation/_pubskel/JRules/ps_JRules_Global720.html]\nIlrSSPResolver [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/index.jsp?topic=/com.ibm.websphere.ilog.jrules.doc/html/api/html/ilog/rules/teamserver/model/testing/IlrSSPResolver.html]", "question": "How to configure DC to look on a different App server for the SSP? \n\nI have a single Application server with the RES console installed, and then a separate application server with the XU, the ssp ear, etc. on that one. Each app server is configured separately with respective ports. for example, mgmt server (with the RES console only) has port 8000, and the runtime server (with all of the runtime components) has port 9000.\n\nThe problem I am running into is the following:\n\nWhen I am trying to run a DVS test suite from Decision Center against RES, (my server endpoint in Decision Center is configured as http://hostname:port/res)\n\nI am getting a \"the host and port are responsive but the \"/testing/sspService\" cannot be found. This is expected if it is looking on the same server as the RES console since the application (ssp) is not deployed there.\n\nHowever, I cannot seem to configure the RES console to not assume that the ssp is running on the same port.", "answer": "First remember to pack all your XOMs (eXecutable Object Model) into the ssp.war following the documentation [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.doc/Content/Business_Rules/Documentation/_pubskel/JRules/ps_JRules_Global720.html]. \n\nThen make sure the SSP (ssp.war) is deployed on each server along with a XU connection factory and the appropriate datasource definition. \n\n \n\nThen create your own SSP resolver, add it to the teamserver.war and set the teamserver.defaultSSPResolver.class property to this class following this specification [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/index.jsp?topic=/com.ibm.websphere.ilog.jrules.doc/html/api/html/ilog/rules/teamserver/model/testing/IlrSSPResolver.html]. \n\n \n\nBy implementing your own method IlrSSPResolver.getSSPURL(String serverName,URL url), you will be able to point to something else than the default provider. \n\nThe default provider uses the url of the Rule Execution Server passed in parameter and replaces the application name with testing. \n\nA simple implementation can use the server name to return a specific server URL."}
{"id": "VAL_Q019", "document": "IBM Security Bulletin : Multiple vulnerabilities in IBM Java Runtime affect IBM Integration Bus and WebSphere Message Broker (CVE-2015-0138) - United States  SECURITY BULLETIN\n\nSUMMARY\n The “FREAK: Factoring Attack on RSA-EXPORT keys\" TLS/SSL client and server vulnerability affects IBM® Runtime Environment Java™ Technology Edition 6SR16 (and earlier) used by WebSphere Message Broker and the IBM® Runtime Environment Java™ Technology Edition 7SR8 (and earlier) or 7R1 (and earlier) used by IBM Integration Bus. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-0138 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0138]\nDESCRIPTION: A vulnerability in various IBM SSL/TLS implementations could allow a remote attacker to downgrade the security of certain SSL/TLS connections. An IBM SSL/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers. \n\nThis vulnerability is also known as the FREAK attack. \n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691 [http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Integration Bus V9, V10 \nIBM Integration Bus Toolkit V9,\nWebSphere Message Broker V7 and V8 \nWebSphere Message Broker Toolkit V7 and V8\n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus V10 IT07823 \nIT07802 The APARs are available in fixpack 10.0.0.1\nhttp://www.ibm.com/support/docview.wss?uid=swg24040056 [http://www.ibm.com/support/docview.wss?uid=swg24040056] IBM Integration Bus V9 IT07823 An interim fix is available from IBM Fix Central.\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT07823 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT07823]\n\nThe APAR is targeted to be available in fix pack 9.0.0.4. IBM Integration Toolkit V9 IT07802 An interim fix is available at [http://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v90/MB900301/]\nhttp://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v90/MB900301/ [http://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v90/MB900301/] WebSphere Message Broker\nV8\nIT07736 An interim fix is available from IBM Fix Central.\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT07736 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT07736]\n\nThe APAR is targeted to be available in fix pack 8.0.0.6. WebSphere Message Broker Toolkit V8 IT07802 An interim fix is available at [http://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v80/MB800501/]\nhttp://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v80/MB800501/ [http://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v80/MB800501/] WebSphere Message Broker\nV7\nIT07736 An interim fix is available from IBM Fix Central.\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT07736 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT07736]\n\nThe APAR is targeted to be available in fix pack 7.0.0.8. WebSphere Message Broker Toolkit V7 IT07802 An interim fix is available at\nhttp://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v70/MB700702/ [http://public.dhe.ibm.com/software/websphere/studiotools/wmbt/v70/MB700702/] \nYou should verify applying this fix does not cause any compatibility issues. \n\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : \nhttp://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308] WORKAROUNDS AND MITIGATIONS\nNone known \n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT\nThe vulnerability was reported to IBM by Karthikeyan Bhargavan of the PROSECCO team at INRIA \n\nCHANGE HISTORY\n 01-Apr-2015: Original Copy Published\n01-Jun-2015: Added V10 & Toolkit fix links\n\n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Security AIX, HP-UX, Linux, Solaris, Windows 10.0, 9.0 \nPRODUCT ALIAS/SYNONYM\n WMB IIB", "question": "Help with Security Bulletin : Multiple vulnerabilities in IBM Java Runtime affect IIB and WMB (CVE-2015-0138) I need to understand details regarding Security Bulletin : Multiple vulnerabilities in IBM Java Runtime affect IBM Integration Bus and WebSphere Message Broker (CVE-2015-0138). This is also commonly referenced as “FREAK: Factoring Attack on RSA-EXPORT keys\" TLS/SSL client and server vulnerability. Where can I find this information? ", "answer": "The “FREAK: Factoring Attack on RSA-EXPORT keys\" TLS/SSL client and server vulnerability affects IBM® Runtime Environment Java™ Technology Edition 6SR16 (and earlier) used by WebSphere Message Broker and the IBM® Runtime Environment Java™ Technology Edition 7SR8 (and earlier) or 7R1 (and earlier) used by IBM Integration Bus."}