chunk_id string | chunk string |
|---|---|
98ace17eb5467ddaf58f4ad24bf93e93_6 | RELATED INFORMATION
CA Technologies: Session killed by agent heartbeat [http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1314663.aspx]
Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard AIX, Linux, Solaris, Windows 8.5.7.CF201706, 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 Business Integration IBM Business Process Manager Express Linux, Windows 8.5.7.CF201706, 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
PRODUCT ALIAS/SYNONYM
BPM |
9ab3b735f36bd47509993f7831a4a8c3_0 | IBM Fix pack 8001 installlation fails - ADMA5026E: no valid target is specified in ObjectName - United States portal fix pack fixpack 8001 8.0.0.1 install installation fail fails failure ADMA5026E WCMD0003E TECHNOTE (TROUBLESHOOTING)
PROBLEM
During the 8001 fix pack installation, ConfigEngine executes a wsadmin script which tries to read the server definition for any vertical cluster members added to the node. If the Dmgr was not running during the upgrade, it may fail.
SYMPTOM
In ConfigTrace, the process is not connecting to the Dmgr:
========================================
Fri Mar 22 21:19:10 GMT 2013
Target started: action-set-managed-node-flag
action-set-managed-node-flag:
[echo] Is this a Managed Node ? true
Target finished: action-set-managed-node-flag
Fri Mar 22 21:19:11 GMT 2013
Target started: action-set-conntype-property
action-set-conntype-property:
[echo] wsadminConnType set to: NONE
Target finished: action-set-conntype-property
======================================== |
9ab3b735f36bd47509993f7831a4a8c3_1 | The wsadminConnType should be set to SOAP in a cluster. Further in the ConfigTrace, we see this error:
========================================
[wsadmin] WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
[wsadmin] AppName wps_scheduler
[wsadmin] Ear File /opt/IBM/WebSphere/PortalServer/installer/wp.ear/installableApps/wps_scheduler.ear
[wsadmin] Install Options -update -appname "wps_scheduler" -deployejb.classpath {/opt/IBM/WebSphere/PortalServer/base/wp.base/shared/app/wp.base.jar}
[wsadmin] Getting tasks for: wps_scheduler |
9ab3b735f36bd47509993f7831a4a8c3_2 | [wsadmin] ADMA5026E: No valid target is specified in ObjectName WebSphere:cell=MyCell,node=MyNode,server=webserver1 for module wp.scheduler.ejb.jar+META-INF/ejb-jar.xml.
[wsadmin] com.ibm.websphere.management.exception.AdminException: ADMA5026E: No valid target is specified in ObjectName WebSphere:cell=MyCell,node=MyNode,server=webserver1 for module wp.scheduler.ejb.jar+META-INF/ejb-jar.xml.
[wsadmin] at com.ibm.ws.management.application.task.ConfigRepoHelper.getServerNames(ConfigRepoHelper.java:2270)
[wsadmin] at com.ibm.ws.management.application.task.ConfigRepoHelper.getAddRemoveServerNames(ConfigRepoHelper.java:2175)
[wsadmin] at com.ibm.ws.management.application.task.ConfigRepoHelper.getServerNames(ConfigRepoHelper.java:2048)
[wsadmin] at com.ibm.ws.management.application.AppAssociation.getServerNames(AppAssociation.java:1451)
======================================== |
9ab3b735f36bd47509993f7831a4a8c3_3 | In Installation Manager native logs, you may see the following error if an incorrect Dmgr profile name is passed in:
========================================
check-if-ok-to-start-dmgr:
iim-start-dmgr:
[exec] WCMD0003E: The specified profile "Dmgr01" cannot be found.
If a default profile exists and you wish to use it, the -profileName
parameter is not required.
[exec] Result: 1
[exec] Current profile - wp_profile
========================================
CAUSE
The Dmgr is not started during the upgrade, so the installation process cannot connect to it.
RESOLVING THE PROBLEM
1. If using a remote Dmgr, be sure it is started prior to attempting the upgrade.
2. If using a local Dmgr and Installation Manager requires you to stop it prior to attempting the upgrade, follow these steps:
a. Verify the Dmgr profile name by navigating to the Dmgr's AppServer/bin folder and execute this command:
./manageprofiles.sh|bat -listProfiles |
9ab3b735f36bd47509993f7831a4a8c3_4 | b. Pass in the correct Dmgr profile name according to the installation option you are using:
http://www-10.lotus.com/ldd/portalwiki.nsf/xpDocViewer.xsp?lookupName=Readme+8.0.0.1#action=openDocument&res_title=Upgrade_instructions_for_WebSphere_Portal_and_Web_Content_Manager_V8.0.0.1_clustered_servers_8001&content=pdcontent [http://www-10.lotus.com/ldd/portalwiki.nsf/xpDocViewer.xsp?lookupName=Readme+8.0.0.1#action=openDocument&res_title=Upgrade_instructions_for_WebSphere_Portal_and_Web_Content_Manager_V8.0.0.1_clustered_servers_8001&content=pdcontent]
*
* |
ee075a1897058a39a02cc590e1374291_0 | IBM MQ 7.x, MQ 8.0 and MQ 9.0 compatibility with previous versions - including usage of CCDT files, JMS .bindings, SSL/TLS - United States compatibility; compatible TECHNOTE (FAQ)
QUESTION
Are WebSphere MQ (WMQ) V7.0, V7.1, V7.5 and V8.0 compatible with previous versions?
Can an MQ 8.0 client use a CCDT created with a previous version?
Can an MQ 7.0 client use a CCDT created with a newer version?
Can a JMS .bindings file created in 7.1 be used with 8.0?
Can a JMS .bindings file created in 8.0 be using with 7.1?
Can an older MQ client using an old SSL protocol still work with MQ 9.0?
ANSWER
Compatibility statement:
WebSphere MQ V7.0, V7.1, V7.5, V8.0 and V9.0 queue managers and clients inter operate with queue managers and clients from any previous level of the WebSphere MQ or MQSeries products.
This means that ... |
ee075a1897058a39a02cc590e1374291_1 | * A 7.0, 7.1, 7.5, 8.0 and 9.0 client can connect to all queue managers, non-version 7, as well as version 7.0, 7.1, 7.5, 8.0 and 9.0
* A 7.0, 7.1, 7.5, 8.0 and 9.0 queue manager can interact with all clients, non-version 7, as well as version 7.0, 7.1, 7.5, 8.0 and 9.0
Note: If your V7.x, V8.0 or V9.0 client connects to an MQ 6.0 or earlier queue manager, or use a server-connection channel with the attribute SHARECNV = 0 (which treats the connection as being MQ 6.0), then you cannot use V7 features, and structures in your client application.
MQ Client V6 and V7/V8/V9 compatibility
The new features which are available for a version 7.x, 8.0 or 9.0 client connected to a version 6.0 queue manager are:
- Weighted selection on CLNTCONN channels.
- Reconnecting via a previously used channel.
- Maximum message length increased on MQSERVER environment variable. |
ee075a1897058a39a02cc590e1374291_2 | The new feature which is available for a version 6.0 client connected to a version 7.x, 8.0 or 9.0 queue manager is:
- Instance limits on SVRCONN channels.
Caveat
The compatibility statement refers to:
Version.Release
... such as:
A 7.0 client is compatible with a 7.5 queue manager.
This statement does not extend to a more granular specification:
Version.Release.Maintenance.FixPack (V.R.M.F)
If there are known problems at a given V.R.M.F (such as 7.0.0.0), then an upgrade to a more recent fix pack for the same Version.Release will be necessary (such as 7.0.1.11). Notice that the upgrade is within the same Version.Release (7.0) and a migration to a newer Version.Release is not forced.
+ Compatibility of MQ clients and CCDT files
Newer versions of the MQ clients (such as 8.0) know how to handle CCDT files that were created/edited by older queue managers (such as 6.0) |
ee075a1897058a39a02cc590e1374291_3 | Older MQ clients (such as 6.0) do NOT know how to handle CCDT files that were created/edited by newer queue managers (such as 8.0). That is, older clients do not know what are the new attributes (if any) introduced in newer MQ versions.
Based on the above, if you have a mix of versions of MQ clients that use a common CCDT file, then this CCDT file should be edited from a queue manager at the LOWEST (OLDEST) version. For example, if you are using MQ 6.0, 7.0, 7.1, 7.5, 8.0 and 9.0 clients that use a CCDT file, then the CCDT file must be maintained by the MQ queue manager at version 6.0
- However, the newer MQ clients (8.0) when using the CCDT created with 5.3 will NOT be able to fully exploit newer features, even when connecting to an 8.0 queue manager because the CCDT will not show the new attributes for those new features.
MQ CCDT created version Compatible MQ client versions |
ee075a1897058a39a02cc590e1374291_4 | 6.0 6.0 7.0 7.1 7.5 8.0 9.0
7.0 7.0 7.1 7.5 8.0 9.0
7.1 7.1 7.5 8.0 9.0
7.5 7.1 7.5 8.0 9.0
8.0 8.0 9.0
9.0 8.0 9.0
Notes:
- There was no change in the MQCD length between 7.1 and 7.5. Therefore the CCDT created on 7.5 can be used on 7.1.
- There was no change in the MQCD length between 8.0 and 9.0. Therefore the CCDT created on 9.0 can be used on 8.0.
- Unless documented otherwise, CCDTs created on higher level maintenance releases (for example 8.0.0.3) are compatible with lower level (for this example: 8.0.0.0) MQ clients running the same MQ version and release. |
ee075a1897058a39a02cc590e1374291_5 | Update on July 2016:
There are 2 APARs that allow OLDER MQ clients to use NEWER CCDT files!
These APARs relax the restriction by allowing newer CCDTs to be used on older clients but with the caveat that the older client cannot make use of any of the newer channel attributes. These attributes will assume their default values when the CCDT is negotiated with the queue manager.
.
For Java/JMS client applications:
IT10863: WEBSPHERE MQ CLASSES FOR JAVA/JMS APPLICATIONS CAN NOT USE CCDT FILES GENERATED ON A NEWER LEVEL QUEUE MANAGER [http://www.ibm.com/support/docview.wss?uid=swg1IT10863]
Version Maintenance Level
v7.0 7.0.1.14
v7.1 7.1.0.8
v7.5 7.5.0.6
v8.0 8.0.0.3 |
ee075a1897058a39a02cc590e1374291_6 | For C based (and non-Java/JMS) client applications:
IT11547: WEBSPHERE MQ CLIENT APPLICATIONS CANNOT USE CCDT FILES GENERATED ON A NEWER LEVEL QUEUE MANAGER [http://www.ibm.com/support/docview.wss?uid=swg1IT11547].
This applies to C based and non-Java/JMS applications.
Version Maintenance Level
v7.1 7.1.0.8
v7.5 7.5.0.7
v8.0 8.0.0.3
+ Compatibility of MQ clients and JMS .bindings files
- A JMS .bindings file that was created at an older version (such as 7.1) than the MQ JMS client (such as 8.0) will be used without version related errors by the client.
- A JMS .bindings file that was created at a newer version (such as 8.0) than the MQ JMS client (such as 7.1), will be used without version related errors by the client. If there are any new attributes in the JMS administered objects that the older client cannot read, they are ignored.
+ Compatibility of SSL/TLS cipher specifications |
ee075a1897058a39a02cc590e1374291_7 | There have been changes in recent fix packs related to the compatibility of SSL/TLS cipher specifications. For example, if you have a MQ Client at 7.1.0.1 connecting to a MQ 8.0.0.1 queue manager using an older SSL cipher specification, after applying Fix Pack MQ 8.0.0.2 to the queue manager, the connectivity may be broken because the queue manager indicates that the older SSL cipher spec is now deprecated.
For more details on the compatibility of SSL/TLS cipher specifications, see the following blog entry: |
ee075a1897058a39a02cc590e1374291_8 | SSL and TLS Cipher Specification Deprecations for the MQ Product [https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/ssl_and_tls_cipher_specification_deprecations_for_the_mq_product?lang=en]
Miguel A. Rodriguez
May 2016
Due to the recent security vulnerabilities (for example, POODLE Attack), the latest MQ product Fix Packs come with stricter, default security requirements that affect the use of the compromised Secure Socket Layer (SSL) and Weak Transport Level Security (TLS) Cipher Specifications. Since these Cipher Specification deprecations are disabled in MQ Fix Packs by default, review the article for the changes separated by MQ versions and Fix Pack levels. RELATED INFORMATION
WebSphere MQ V7.1 Announcement Letter - PDF [http://www.ibm.com/common/ssi/rep_ca/8/897/ENUS208-068/ENUS208068.PDF]
WebSphere MQ V7.1 Announcement Letter - Web [http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS211-395] |
ee075a1897058a39a02cc590e1374291_9 | WMQ Doc: Coexistence compatibility interoperability [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.mig.doc/q006320_.htm?lang=en] |
ee075a1897058a39a02cc590e1374291_10 | Cross reference information Segment Product Component Platform Version Edition Business Integration IBM MQ
PRODUCT ALIAS/SYNONYM
WMQ MQ |
465bbfef72b4b25891117ee505c3f68d_0 | IBM Web Browser Versions Supported by PathWAI Editor for Messages - United States Web Browser Internet Explorer Editor for Messages 5724K3700 5724K3700TR TECHNOTE (FAQ)
QUESTION
Which web browser versions are supported by Editor for Messages?
ANSWER
Editor for Messages supports Microsoft Internet Explorer only. Mozilla Firefox and Google Chrome are not supported.
Supported IE versions:
IE 6, IE 7, IE 8, IE 9 (compatibility view), IE 10(Compatibility view), IE 11(Compatibility view)
Note:
There are known issues which cause functions not to work correctly with IE 9 or above. For example, the check boxes for queue filters at the right side do not work correctly, and the open queue messages dialog shows in minimum small size. As a workaround, IE compatibility view is recommended. The following explains how to enable it. |
465bbfef72b4b25891117ee505c3f68d_1 | 1. Enter the URL to connect with Editor for Messages Web Server. In my case, 9.123.109.109 is the server IP.
[/support/docview.wss?uid=swg21678261&aid=1] [/support/docview.wss?uid=swg21678261&aid=1]
Screenshot 1
2. Right click on the menu Tools –> Compatibility View. From now on, all views from this site will be displayed in IE compatibility view. You may also add the IP to the compatibility view setting (see screenshot 2) by selecting Tools -> Compatibility View Settings, then it will open following dialog. Now, input the server IP address to add and click ‘close’ to save.
[/support/docview.wss?uid=swg21678261&aid=2]
Screenshot 2
After this, you do not need to select the compatibility view every time when IE is launched. IE will open the site automatically in compatibility view. |
d0a82073d6fdd536592fc569aff801c1_0 | IBM WebSphere Portal inactive session time out and redirect - United States redirect; session; time out; session time out; redirect.logout.url; redirect logout TECHNOTE (TROUBLESHOOTING)
PROBLEM
A redirect to a specific page in IBM WebSphere Portal does not always occur when an inactive session times out or the inactive session time out does not appear to occur at all.
DIAGNOSING THE PROBLEM
You set the following properties in the WP_ConfigService and notice different behavior when the session times out (depending on your version of WebSphere Portal):
*
* redirect.logout = true
*
* redirect.logout.url = <Fully Qualified URL>
The session inactivity time out is 30 minutes but this value does not affect this issue.
RESOLVING THE PROBLEM
In V6.1.0.1, when the session expires, you are redirected to the page specified in the redirect.logout.url property. |
d0a82073d6fdd536592fc569aff801c1_1 | In Portal 6.1.0.1 with APAR PK78213 installed or in V6.1.0.2 and later, you are not redirected to the login page. Instead, the ErrorSessionTimeOut.jsp displays:
[/support/docview.wss?uid=swg21419230&aid=1] [/support/docview.wss?uid=swg21419230&aid=1]
By design, the ErrorSessionTimeOut.jsp always displays when the session times out if a logout URL is configured.
On systems running V6.1.0.1, install APAR PK78213 [http://www-01.ibm.com/support/docview.wss?uid=swg1PK78213] to maintain consistency across all 6.1 platforms.
To redirect to the login page (or any other page) when the session expires, use one of the following methods:
*
*
*
* "Configuring authentication filters"
*
* New security APIs in WebSphere Portal
*
*
*
*
*
*
NOTES
1. This document discusses redirect behavior on session timeout. An "explicit" logout (by selecting or clicking the logout link) is always expected to cause a redirect to the URL specified in redirect.logout.url. |
d0a82073d6fdd536592fc569aff801c1_2 | 2. The inactive session timeout may not work at all in a single node cluster or a cluster with "failover" nodes in which only 1 node is up at a time (for example, when using Portal Express). Either add a second node or set the value for Distributed Sessions from "Memory-to-memory
replication" to None in the WebSphere Application Server Integrated Solutions Console, path: Servers > Server Types > Websphere application servers > WebSphere_Portal > session management > Distributed environment settings. RELATED INFORMATION
APAR PK78213 [http://www.ibm.com/support/docview.wss?uid=swg1PK78213]
Configuring authentication filters [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/topic/com.ibm.wp.ent.doc_v6101/admin/adauthflt.html]
New security APIs in WebSphere Portal [http://www.ibm.com/developerworks/websphere/library/techarticles/0905_buchwald/0905_buchwald.html] |
d0a82073d6fdd536592fc569aff801c1_3 | Peer-to-peer topology [http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/cprs_m2m_p2p_default.html] |
f46f0235d8afce45abc32993606c785c_0 | IBM Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IBM WebSphere MQ (CVE-2016-0475, CVE-2015-7575, CVE-2016-0448) - United States SECURITY BULLETIN
SUMMARY
There are multiple vulnerabilities in IBM® Runtime Environment Java™ Technology Edition that is used by IBM WebSphere MQ. These issues were disclosed as part of the IBM Java SDK updates in January 2016 and include the vulnerability commonly referred to as “SLOTH”. |
f46f0235d8afce45abc32993606c785c_1 | VULNERABILITY DETAILS
CVEID: CVE-2016-0448 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0448]
DESCRIPTION: An unspecified vulnerability in Oracle Java SE and Java SE Embedded related to the JMX component could allow a remote attacker to obtain sensitive information resulting in a partial confidentiality impact using unknown attack vectors.
CVSS Base Score: 4
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109949 [https://exchange.xforce.ibmcloud.com/vulnerabilities/109949] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:S/C:P/I:N/A:N) |
f46f0235d8afce45abc32993606c785c_2 | CVEID: CVE-2015-7575 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575]
DESCRIPTION: The TLS protocol could allow weaker than expected security caused by a collision attack when using the MD5 hash function for signing a ServerKeyExchange message during a TLS handshake. An attacker could exploit this vulnerability using man-in-the-middle techniques to impersonate a TLS server and obtain credentials.
CVSS Base Score: 7.1
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109415 [https://exchange.xforce.ibmcloud.com/vulnerabilities/109415] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N) |
f46f0235d8afce45abc32993606c785c_3 | CVEID: CVE-2016-0475 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0475]
DESCRIPTION: An unspecified vulnerability in Oracle Java SE Java SE Embedded and Jrockit related to the Libraries component has partial confidentiality impact, partial integrity impact, and no availability impact.
CVSS Base Score: 5.8
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109946 [https://exchange.xforce.ibmcloud.com/vulnerabilities/109946] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:P/A:N)
AFFECTED PRODUCTS AND VERSIONS
IBM JRE 7, Java Technology Edition, Version 7 provided by IBM WebSphere MQ 8.0.0.4 and earlier on all platforms (except IBM i and z/OS)
IBM JRE 6, Java Technology Edition, Version 6 provided by IBM WebSphere MQ 7.5.0.5, IBM WebSphere MQ 7.1.0.7 and earlier on all platforms (except IBM i and z/OS)
REMEDIATION/FIXES
IBM WebSphere MQ 8.0
HP-UX |
f46f0235d8afce45abc32993606c785c_4 | Apply fix pack 8.0.0.5 when available, in the interim apply ifix IV81649 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+MQ&release=8.0&platform=HPUX+64-bit,+IA64&function=aparId&apars=IV81649]
AIX, Linux, Solaris & Windows
Apply fix pack 8.0.0.5 when available, in the interim apply ifix IT13492 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+MQ&release=8.0&platform=All&function=aparId&apars=IT13492]
IBM WebSphere MQ 7.5
HP-UX
Apply fix pack 7.5.0.7 when available, in the interim apply ifix IV81649 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+MQ&release=7.5&platform=HPUX+64-bit,+IA64&function=aparId&apars=IV81649]
AIX, Linux, Solaris & Windows
Apply fix pack 7.5.0.6 [http://www-01.ibm.com/support/docview.wss?uid=swg21975660]
IBM WebSphere MQ 7.1
HP-UX |
f46f0235d8afce45abc32993606c785c_5 | Apply fix pack 7.1.0.8 when available, in the interim apply ifix IV81649 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+MQ&release=7.5&platform=HPUX+64-bit,+IA64&function=aparId&apars=IV81649]
AIX, Linux, Solaris & Windows
Apply fix pack 7.1.0.8 when available, in the interim apply ifix IT13492 [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=7.1&platform=All&function=all&source=fc]
WORKAROUNDS AND MITIGATIONS
For CVE-2015-7575:
Users of Java 7 and later can address the issue by updating the ../jre/lib/security/java.security file as follows (both steps are required):
· Add MD5 to the jdk.certpath.disabledAlgorithms property - for example jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024, MD5
· Add MD5withRSA to the jdk.tls.disabledAlgorithms property - for example jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize < 768, MD5withRSA |
f46f0235d8afce45abc32993606c785c_6 | Java 6 requires code changes in the JSSE component in addition to the java.security file modifications, so upgrading the JRE is the only solution.
GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.
IMPORTANT NOTE
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. |
f46f0235d8afce45abc32993606c785c_7 | REFERENCES
Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]
On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]
Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]
On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] IBM Java SDK Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg21974193] ACKNOWLEDGEMENT
CVE-2015-7575 was reported to IBM by Karthikeyan Bhargavan at INRIA in Paris, France
CHANGE HISTORY
22 April 2016: Original version published
29 April 2016: Altered CVE-2015-7575 scoring
2 June 2016: Further correction to CVE-2015-7575 scoring |
f46f0235d8afce45abc32993606c785c_8 | *The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
RELATED INFORMATION
A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21982284] |
274d3dc3091ec6a8718a71133ab48a34_0 | IBM Newly accessed tables result in increasing of dbheap - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Newly accessed tables result in increasing of dbheap
SYMPTOM
From output of command "db2pd -db <db name> -mempools" you can find LogSz/PhySz of the memory pool named "dbh" keeps on increasing.
CAUSE
This is expected result. Every newly accessed table loads the tcb and has associated allocations for data, index, lob, compression dictionaries if applicable. This memory allocation is persistent/cached until the database deactivates or the table is dropped.
DIAGNOSING THE PROBLEM
Collect "db2pd -db showdb -memblocks 2 sort -alldbp", you will find most of the the newly memory allocations are from File 1601762203 LOC 1025 and LOC 1015:
Day 1: |
274d3dc3091ec6a8718a71133ab48a34_1 | All memory consumers in Database memory set:
PoolID PoolName TotalSize(Bytes) %Bytes TotalCount %Count LOC File
2 dbh 2502313088 51.03 59601 7.42 1025 1601762203
2 dbh 1906996352 38.89 59601 7.42 1015 1601762203
2 dbh 325096960 6.63 169321 21.08 2225 1235116617
2 dbh 37055232 0.76 159296 19.84 3159 1235116617
Day 2:
All memory consumers in Database memory set:
PoolID PoolName TotalSize(Bytes) %Bytes TotalCount %Count LOC File
2 dbh 2642441600 50.76 63266 7.16 1025 1601762203
2 dbh 2027344256 38.95 63266 7.16 1015 1601762203
2 dbh 356836992 6.86 185844 21.03 2225 1235116617
2 dbh 40057088 0.77 174834 19.78 3159 1235116617
Note, for different versions, LOC might be different, above LOC only applies to V9.7FP11.
Collect "db2pd -d showdb -tcbstats -alldbp", you will see the number of tcb entries also keeps on increasing.
RESOLVING THE PROBLEM
This is the expected result, once all tables in the database are accessed for at least one time, the memory increasing will stop. |
deb31099d900d1b1e5daf904ae9f45e3_0 | IBM Security Bulletin: WebSphere Message Broker and IBM Integration Bus are affected by information disclosure vulnerability (CVE-2017-1126) - United States WMB IIB SECURITY BULLETIN
SUMMARY
IBM Integration Bus and WebSphere Message Broker have addressed the vulnerability that would allow an unauthorized user to obtain sensitive information about software versions, and which could lead to further attacks.
VULNERABILITY DETAILS
CVEID: CVE-2017-1126 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1126]
DESCRIPTION: IBM Integration Bus and WebSphere Message Broker could allow an unauthorized user to obtain sensitive information about software versions, which could lead to further attacks.
CVSS Base Score: 5.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/121341 [https://exchange.xforce.ibmcloud.com/vulnerabilities/121341] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) |
deb31099d900d1b1e5daf904ae9f45e3_1 | AFFECTED PRODUCTS AND VERSIONS
IBM Integration Bus V9.0.0.0 - V9.0.0.8 and V10.0.0.0 - V10.0.0.9
WebSphere Message Broker V8.0.0.0 - V8.0.0.8
REMEDIATION/FIXES
Product VRMF APAR Remediation/Fix IBM Integration Bus V10.0.0.0-V10.0.0.9 IT18731/
IT21161 The APARs are available in fix pack 10.0.0.10
http://www-01.ibm.com/support/docview.wss?uid=swg24043943 [http://www-01.ibm.com/support/docview.wss?uid=swg24043943] IBM Integration Bus V9.0.0.0-V9.0.0.8 IT18731/
IT21161 The APARs are available in fix pack 9.0.0.9
http://www-01.ibm.com/support/docview.wss?uid=swg24043947 [http://www-01.ibm.com/support/docview.wss?uid=swg24043947] WebSphere Message Broker V8.0.0.0 -V8.0.0.8 IT18731/
IT21161 APAR IT18731 is available in fix pack 8.0.0.9 http://www-01.ibm.com/support/docview.wss?uid=swg24043806 [http://www-01.ibm.com/support/docview.wss?uid=swg24043806] |
deb31099d900d1b1e5daf904ae9f45e3_2 | For a fix for APAR IT21161, please contact IBM support.
Websphere Message Broker V8 is no longer in full support; IBM recommends upgrading to a fixed, supported version/release/platform of the product. If you are an extended support customer and require a fix, this is available only for the latest fixpack (8.0.0.9). To obtain the fix contact IBM support.
WORKAROUNDS AND MITIGATIONS
None
GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.
REFERENCES
Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]
On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]
RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]
CHANGE HISTORY
29 September 2017: Original version published |
deb31099d900d1b1e5daf904ae9f45e3_3 | *The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
RELATED INFORMATION
# |
deb31099d900d1b1e5daf904ae9f45e3_4 | Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker AIX, HP-UX, Linux, Solaris, Windows 8.0
PRODUCT ALIAS/SYNONYM
WMB IIB |
40705de2d092319797e71c42765cccaa_0 | IBM PI54477: ADD ABILITY TO DISABLE LOGGING OF SECJ0371W EXPIRED LTPA TOKEN MESSAGES - United States FIXES ARE AVAILABLE
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24043005]
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24042746]
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http://www-01.ibm.com/support/docview.wss?uid=swg24044096]
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734] |
40705de2d092319797e71c42765cccaa_1 | SUBSCRIBE
You can track all active APARs for this component.
APAR STATUS
* CLOSED AS PROGRAM ERROR.
ERROR DESCRIPTION
* SECJ0371W messages fill the logs and the customer does not find
them useful. They would like to turn off the logging of these
messages.
WL3SEC
LOCAL FIX |
40705de2d092319797e71c42765cccaa_2 | PROBLEM SUMMARY
* ****************************************************************
* USERS AFFECTED: All users of IBM WebSphere Application *
* Server V8.0 and higher. *
****************************************************************
* PROBLEM DESCRIPTION: Users would like to be able to disable *
* SECJ0371W messages *
****************************************************************
* RECOMMENDATION: *
****************************************************************
SECJ0371W messages log every event of an LTPA token
expiration. LTPA token expirations are expected under normal
circumstances. Although at times these messages can alert
customers to unexpected conditions. For instance a client
continues to send an expired token repeatedly.
The customer is requesting the ability to disable the logging |
40705de2d092319797e71c42765cccaa_3 | of the SECJ0371W message. |
40705de2d092319797e71c42765cccaa_4 | PROBLEM CONCLUSION
* A security custom property will be used to disable the logging
of the SECJ0371W message. Setting this property to true will
disable future logging of the message.
com.ibm.websphere.security.ltpa.disableSECJ0371W=true
The fix for this APAR is currently targeted for inclusion in
fix packs 8.0.0.13 and 8.5.5.10. Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]
TEMPORARY FIX
COMMENTS |
40705de2d092319797e71c42765cccaa_5 | APAR INFORMATION
* APAR NUMBER
PI54477
* REPORTED COMPONENT NAME
WEBS APP SERV N
* REPORTED COMPONENT ID
5724H8800
* REPORTED RELEASE
850
* STATUS
CLOSED PER
* PE
NoPE
* HIPER
NoHIPER
* SPECIAL ATTENTION
NoSpecatt / Xsystem
* SUBMITTED DATE
2015-12-18
* CLOSED DATE
2016-02-24
* LAST MODIFIED DATE
2016-07-12
* APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:
* APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:
FIX INFORMATION
* FIXED COMPONENT NAME
WEBS APP SERV N
* FIXED COMPONENT ID
5724H8800
APPLICABLE COMPONENT LEVELS
* R800 PSY
UP
* R850 PSY
UP |
2a6d98821847bb7b7b4c8581b0532bdd_0 | IBM Configuration of the ITCAM agent on AIX leads to Java heap errors. - United States JAVA_OPTS CAMADALL CAMADINST java heap java.lang.OutOfMemoryError CFG5045E TECHNOTE (TROUBLESHOOTING)
THIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):
US English
PROBLEM(ABSTRACT)
Configuration of the ITCAM agent on AIX leads to Java heap errors.
SYMPTOM
During configuration of the YN agent, you will see these errors: |
2a6d98821847bb7b7b4c8581b0532bdd_1 | java.lang.OutOfMemoryError: Java heap space
at org.python.core.PyException.tracebackHere(PyException.java:158)
at org.python.core.PyException.tracebackHere(PyException.java:145)
at org.python.core.PyTableCode.call(PyTableCode.java:169)
at org.python.core.PyBaseCode.call(PyBaseCode.java:301)
at org.python.core.PyBaseCode.call(PyBaseCode.java:141)
at org.python.core.PyFunction.__call__(PyFunction.java:327)
at org.python.core.PyFunction.__call__(PyFunction.java:322)
at org.python.core.PyInstance.ifindfunction(PyInstance.java:168)
at org.python.core.PyInstance.__findattr_ex__(PyInstance.java:148)
at org.python.core.PyObject.__findattr__(PyObject.java:863)
at org.python.core.PyInstance.invoke_ex(PyInstance.java:328)
java.lang.OutOfMemoryError: java.lang.OutOfMemoryError: Java heap space
CFG5045E The configuration process is being terminated due to errors listed above.
CAUSE
Low heap settings in the JAVA_OPTS parameter.
ENVIRONMENT
AIX - Distributed |
2a6d98821847bb7b7b4c8581b0532bdd_2 | RESOLVING THE PROBLEM
The Java heap settings are set in the config.sh script in the JAVA_OPTS line. For AIX, the default settings are way too low.
Please do these changes to get it to work:
Make a backup of the config.sh file, then edit it.
Search for the following line JAVA_OPTS in the config.sh file:[/support/docview.wss?uid=swg21959444&aid=1] [/support/docview.wss?uid=swg21959444&aid=1]
Change the JAVA_OPTS="-Xms256m -Xmx256m" to a higher value like this:
JAVA_OPTS="-Xms512m -Xms512m"
Save file, restart the config again and see if it works now without any Out of Java heap messages.
PRODUCT ALIAS/SYNONYM
ITCAMfAD ITCAM4AD ITCAM for App Diagnostics |
61e87632179eef66f9218ec7f0fd07a8_0 | IBM Downloading IBM SPSS Statistics 24 - United States DOWNLOADABLE FILES
ABSTRACT
Downloading IBM SPSS Statistics 24
DOWNLOAD DESCRIPTION
IBM® SPSS® Statistics is the world’s leading statistical software used to solve business and research problems by means of ad-hoc analysis, hypothesis testing, and predictive analytics. Organizations use IBM SPSS Statistics to understand data, analyze trends, forecast and plan to validate assumptions and drive accurate conclusions.
If you are looking for a free trial version of SPSS Statistics, go here: Free Trial Version [http://www.ibm.com/analytics/us/en/technology/predictive-analytics/#ibm-spss-stats-modeler-trials]
Detailed information on getting started, managing your account, downloading and installing, and licensing is available here: GetSPSS [http://www.ibm.com/software/analytics/spss/support/get_spss.html] |
61e87632179eef66f9218ec7f0fd07a8_1 | Complete documentation for IBM SPSS Statistics 24.0 is available here: IBM SPSS Statistics 24 Knowledge Center [http://www.ibm.com/support/knowledgecenter/SSLVMB_24.0.0]
PDF versions of the installation instructions and manuals are also available here: IBM SPSS Statistics 24 Documentation [http://www.ibm.com/support/docview.wss?uid=swg27047033]
To download a product, go to the IBM Passport Advantage® Web Site [http://www.ibm.com/software/howtobuy/passportadvantage/paocustomer/sdma/SDMA?PO=DOWNLOAD_FIND_BY_PART_NUMBER] and then: |
61e87632179eef66f9218ec7f0fd07a8_2 | 1. Do one of the following:
If you are a returning customer, sign in.
If you are a new customer, register.
2. If the Software download & media access window appears, click I agree.
3. In the Find downloads & media window, click Download finder.
4. Under Download finder, select the download you want, and click Continue.
5. Under Select criteria, select a language and one or more platforms.
6. Under Download options, select the options you want, and click Continue.
7. Under Review “Current version” downloads, expand Current version and under Description, select the download you want, expand it and select the items you want.
8. If applicable, under Select optional downloads, expand and select the items you want.
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.
10. In the Initial Setup dialog, change the Default download location, if you want. |
61e87632179eef66f9218ec7f0fd07a8_3 | 11. If you are prompted, click OK to create the directory where you want the downloaded items to be stored.
12. Click OK to begin the download. |
61e87632179eef66f9218ec7f0fd07a8_4 | Use the plus sign icon to expand the files in the download of your choice in order to avoid downloading unnecessary files.
When the download has finished, Download complete appears in the Download Director dialog. 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.
Downloading and assembling the product
1. Download all of the parts that you need, both required and optional.
2. Unpack each of the parts into a single temporary directory on your system.
3. Follow the installation instructions provided in the download to install the product. |
61e87632179eef66f9218ec7f0fd07a8_5 | For assistance with all questions on generating and accessing authorization codes, including how to enable additional add-on modules that you purchase, go to:
http://public.dhe.ibm.com/software/analytics/spss/licensing/Auth_Codes_092910_2.html [http://public.dhe.ibm.com/software/analytics/spss/licensing/Auth_Codes_092910_2.html]
Any customer with an active support contract can seek activation assistance by logging a support request online or by phone via links available at www.ibm.com/planetwide.
Download Options
You can download entire eAssemblies or individual eImages. The eAssemblies contain all required and optional eImages for each download package. This section lists the eAssemblies. The complete list of eAssemblies and associated eImages is provided below.
IBM SPSS Statistics 24.0 Desktop
Multilingual
Windows: CRZ0ZML
Mac OS: CRZ10ML
Linux: CRZ11ML |
61e87632179eef66f9218ec7f0fd07a8_6 | For Windows, there are 32-bit and 64-bit versions of the product eImage. You only need the one that is appropriate for your computer.
IBM SPSS Statistics Developer
Multilingual
Windows: CRZ1AML
Mac OS: CRZ1BML
Linux: CRZ1CML
For Windows, there are 32-bit and 64-bit versions of the product eImage. You only need the one that is appropriate for your computer.
IBM SPSS Desktop and Developer Documentation
Multilingual
All platforms: CRZ0WML
The installation instructions and manuals for IBM SPSS Statistics Desktop and Developer. This includes installation instructions for all supported platforms for single user installation, site license installation and administration, network license (concurrent license) installation and administration, and data access pack installation (for database access).
Installation instructions for all platforms and all languages are contained in a single eImage. Manuals in PDF form are available in separate eImages for each language. |
61e87632179eef66f9218ec7f0fd07a8_7 | IBM SPSS Statistics Data Drivers
Multilingual
All platforms: CRZ0XML
Drivers to support various data sources in IBM SPSS Statistics Desktop, Developer, and Server.
Note: This eAssembly also contains “IBM SPSS Statistics Data File Drivers”. The Statistics data file drivers allow you to read SPSS Statistics (.sav) data files in applications that support Open Database Connectivity (ODBC) or Java Database Connectivity (JDBC). This is optional. Only download it if you need it.
IBM SPSS Statistics Concurrent User Licensing Server
Multilingual
All platforms: CRZ0YEN
License managers and hardware keys for IBM SPSS Statistics Desktop and Developer.
You will need this if you purchased software that requires a hardware key, or you are an SPSS administrator at a site that purchased concurrent licenses. If you are not aware of either of those conditions, then you don’t need it. |
61e87632179eef66f9218ec7f0fd07a8_8 | If you are an SPSS administrator at a site that purchased concurrent licenses, download the Sentinel License Manager corresponding to the operating system of the computer where you plan to install it.
IBM SPSS Statistics Server
English
Windows: CRZ15ML
Linux for System z: CRZ16ML
Linux: CRZ18ML
Linux for System p LE: CRZ17ML
AIX: CRZ19ML
IBM SPSS Statistics Server is available only in English.
You need to download the correct eImage for your server computer’s operating system.
IBM SPSS Visualization Designer 1.0.3
English
Windows: CRCQ9EN
IBM SPSS SamplePower 3.0.1
English
Windows: CRNK7EN
A desktop application that helps you to find the best sample size for your research.
Complete list of all eAssemblies and eImages
The following table list all the parts available for IBM SPSS Statistics 24.0. |
61e87632179eef66f9218ec7f0fd07a8_9 | Parts and Platform Part Number Category IBM SPSS Statistics Desktop 24.0 Documentation Multilingual eAssembly CRZ0WML IBM SPSS Statistics Client/Developer Installation Documentation 24.0 Multilingual CN99SML Documentation IBM SPSS Statistics Client/Developer Documentation 24.0 English CN99HEN Documentation IBM SPSS Statistics Client/Developer Documentation 24.0 French CN99IFR Documentation IBM SPSS Statistics Client/Developer Documentation 24.0 German CN99JDE Documentation IBM SPSS Statistics Client/Developer Documentation 24.0 Italian CN99KIT Documentation IBM SPSS Statistics Client/Developer Documentation 24.0 Japanese CN99LJA Documentation IBM SPSS Statistics Client/Developer Documentation 24.0 Russian CN99MRU Documentation IBM SPSS Statistics Client/Developer Documentation 24.0 Chinese-simplified CN99FSC Documentation IBM SPSS Statistics Client/Developer Documentation 24.0 Spanish CN99NES Documentation IBM SPSS Statistics Client/Developer Documentation 24.0 Chinese-traditional |
61e87632179eef66f9218ec7f0fd07a8_10 | CN99GTC Documentation IBM SPSS Statistics Client/Developer Documentation 24.0 Korean CN99PKO Documentation IBM SPSS Statistics Client/Developer Documentation 24.0 Polish CN99QPL Documentation IBM SPSS Statistics Client/Developer Documentation 24.0 Portuguese Brazilian CN99RBP Documentation |
61e87632179eef66f9218ec7f0fd07a8_11 | IBM SPSS Statistics Data Drivers 24.0 Multilingual Multiplatform eAssembly CRZ0XML IBM SPSS Statistics Data File Drivers 24.0 Multiplatform Multilingual CN9ADML Optional IBM SPSS Data Access Pack 7.1.1 Multiplatform English CN8IUEN Optional IBM SPSS Statistics - Integration Plug-In for Microsoft .NET 32-bit 24.0 for Microsoft Windows CN98XML Optional IBM SPSS Statistics - Integration Plug-In for Microsoft .NET 64-bit 24.0 for Microsoft Windows CN98YML Optional |
61e87632179eef66f9218ec7f0fd07a8_12 | IBM SPSS Statistics Concurrent User Licensing Server 24.0 English Multiplatform eAssembly CRZ0YEN IBM SPSS Concurrent Licensing Tools 9.6 - License Manager 64-bit AIX English CN997EN Required IBM SPSS Concurrent Licensing Tools 9.6 - License Manager Linux x86-64 English CN998EN Required IBM SPSS Concurrent Licensing Tools 9.6 - License Manager Microsoft Windows English CN99AEN Required IBM SPSS Concurrent Licensing Tools 9.6 - License Manager Mac English CN99BEN Required IBM SPSS Concurrent Licensing Tools 9.6 - Hardware Key Microsoft Windows English CN99CEN Optional IBM SPSS Concurrent Licensing Tools 9.6 - Hardware Key Linux x86-64 English CN99DEN Optional IBM SPSS Concurrent Licensing Tools 9.6 - Hardware Key Mac English CN99EEN Optional |
61e87632179eef66f9218ec7f0fd07a8_13 | IBM SPSS Statistics Desktop 24.0 for Base and all Modules Microsoft Windows Multilingual eAssembly CRZ0ZML IBM SPSS Statistics Client 32-bit 24.0 Microsoft Windows Multilingual CN98SML Required IBM SPSS Statistics Client 64-bit 24.0 Microsoft Windows Multilingual CN98TML Required IBM SPSS Statistics Client 24.0 Microsoft Windows Multilingual (ISO Version) CNA15ML Optional IBM SPSS Statistics Diagnostic Utility 24.0 Microsoft Windows Multilingual CN98ZML Recommended
IBM SPSS Statistics Desktop 24.0 for Base and all Modules Mac OS Multilingual eAssembly CRZ10ML IBM SPSS Statistics Client 24.0 Mac OS Multilingual CN98UML Required IBM SPSS Statistics Client 24.0 Mac OS Silent Multilingual CN98VML Required IBM SPSS Statistics Client 24.0 Mac OS Multilingual (ISO Version) CNA16ML Optional |
61e87632179eef66f9218ec7f0fd07a8_14 | IBM SPSS Statistics Desktop 24.0 for Base and all Modules Linux x86-64 Multilingual eAssembly CRZ11ML IBM SPSS Statistics Client 24.0 Linux x86-64 Multilingual CN98WML Required IBM SPSS Statistics Client 24.0 Linux x86-64 Multilingual (ISO version) CNA17ML Optional
IBM SPSS Statistics Desktop 24.0 for Base and all Modules Academic Microsoft Windows Multilingual eAssembly CRZ12ML IBM SPSS Statistics Client 32-bit 24.0 Microsoft Windows Multilingual CN98SML Required IBM SPSS Statistics Client 64-bit 24.0 Microsoft Windows Multilingual CN98TML Required IBM SPSS Statistics Diagnostic Utility 24.0 Microsoft Windows Multilingual CN98ZML Recommended
IBM SPSS Statistics Desktop 24.0 for Base and all Modules Academic Mac OS Multilingual eAssembly CRZ13ML IBM SPSS Statistics Client 24.0 Mac OS Multilingual CN98UML Required IBM SPSS Statistics Client 24.0 Mac OS Silent Multilingual CN98VML Required |
61e87632179eef66f9218ec7f0fd07a8_15 | IBM SPSS Statistics Desktop 24.0 for Base and all Modules Academic Linux x86-64 Multilingual eAssembly CRZ14ML IBM SPSS Statistics Client 24.0 Linux x86-64 Multilingual CN98WML Required
IBM SPSS Statistics Server 24.0 Microsoft Windows Multilingual eAssembly CRZ15ML IBM SPSS Statistics Server 24.0 Microsoft Windows Multilingual CN99TML Required IBM SPSS Statistics Server Documentation 24.0 English CN99YEN Documentation
IBM SPSS Statistics Server 24.0 Linux on System z Multilingual eAssembly CRZ16ML IBM SPSS Statistics Server 24.0 Linux on System z Multilingual CN99UML Required IBM SPSS Statistics Server Documentation 24.0 English CN99YEN Documentation
IBM SPSS Statistics Server 24.0 Linux x86-64 Multilingual eAssembly CRZ18ML IBM SPSS Statistics Server 24.0 Linux x86-64 Multilingual CN99WML Required IBM SPSS Statistics Server Documentation 24.0 English CN99YEN Documentation |
61e87632179eef66f9218ec7f0fd07a8_16 | IBM SPSS Statistics Server 24.0 AIX Multilingual eAssembly CRZ19ML IBM SPSS Statistics Server 24.0 AIX Multilingual CN99XML Required IBM SPSS Statistics Server Documentation 24.0 English CN99YEN Documentation
IBM SPSS Statistics Server 24.0 Linux on System p LE Multilingual eAssembly CRZ17ML IBM SPSS Statistics Server 24.0 Linux on System p LE Multilingual CN99VML Required IBM SPSS Statistics Server Documentation 24.0 English CN99YEN Documentation
IBM SPSS Statistics Developer 24.0 Microsoft Windows Multilingual eAssembly CRZ1AML IBM SPSS Statistics Developer 32-bit 24.0 Microsoft Windows Multilingual CN99ZML Required IBM SPSS Statistics Developer 64-bit 24.0 Microsoft Windows Multilingual CN9A0ML Required IBM SPSS Statistics Diagnostic Utility 24.0 Microsoft Windows Multilingual CN98ZML Recommended |
61e87632179eef66f9218ec7f0fd07a8_17 | IBM SPSS Statistics Developer 24.0 Mac OS Multilingual eAssembly CRZ1BML IBM SPSS Statistics Developer 24.0 Mac OS Multilingual CN9A1ML Required IBM SPSS Statistics Developer 24.0 Mac OS Silent Multilingual CN9A2ML Required
IBM SPSS Statistics Developer 24.0 Linux x86-64 Multilingual eAssembly CRZ1CML IBM SPSS Statistics Developer 24.0 Linux x86-64 Multilingual CN9A3ML Required
IBM SPSS Statistics Desktop Integrated Student Edition 24.0 Multiplatform English eAssembly CRZ1MEN IBM SPSS Statistics Desktop Integrated Student Edition 24.0 Microsoft Windows English CN994EN Required IBM SPSS Statistics Desktop Integrated Student Edition 24.0 Mac OS English CN995EN Required IBM SPSS Statistics Desktop Integrated Student Edition 24.0 Multiplatform English (ISO Version) CN996EN Required |
61e87632179eef66f9218ec7f0fd07a8_18 | IBM SPSS Visualization Designer 1.0.3 Microsoft Windows English eAssembly CRCQ9EN IBM SPSS Visualization Designer 1.0.3 License Instructions English CI20GEN Required IBM SPSS Visualization Designer 1.0.3 Microsoft Windows Installer English CZN4JEN Required IBM SPSS Visualization Designer Documentation 1.0.3 Microsoft Windows English CZN4KEN Documentation
IBM SPSS SamplePower 3.0.1 Microsoft Windows English eAssembly CRNK7EN IBM SPSS SamplePower 3.0.1 Microsoft Windows English CIP6XEN Required IBM SPSS SamplePower Documentation 3.0 Microsoft Windows English CZN4IEN Documentation
IBM SPSS Statistics 24.0 Collaboration and Deployment Services 8.0 Multiplatforms Multilingual eAssembly CRZ0VML IBM SPSS Statistics 24.0 Collaboration and Deployment Services Adapter 8.0 Multiplatforms Multilingual CN9ACML Optional IBM SPSS Collaboration and Deployment Services Deployment Manager 8.0 Microsoft Windows Multilingual CN9D6ML Optional |
bb4e949f68fdee76dfcdf86bc91e6628_0 | IBM Optimizing barcode recognition with IBM Datacap - United States bar code barcode recognition optimization patch code patchcode TECHNOTE (FAQ)
QUESTION
What can be done to give the best results with barcode recognition?
CAUSE
During printing, the ink can bleed or spread out over the white area, and then, during scanning, additional spreading of black may occur. As a result, the white spaces end up disappearing and the bars blend into each other. This can be seen by looking at the scanned image at high magnification. The barcode must meet the specifications after accounting for this.
ANSWER
To optimize barcode recognition: |
bb4e949f68fdee76dfcdf86bc91e6628_1 | * The width of the thinnest bar (called the X-dimension) must be at least one pixel, and two pixels are recommended for best results. At 200 DPI this means each bar must be at least .01 inch. Generally this translates to about 4 to 5 characters per inch.
* The X-dimension or width of the narrowest black bar and white space between bars must be at least 20 mils (1/50 inch, 1/2 mm). When scanned perfectly at 200 DPI this would result in 4 pixels, and at 300 DPI 6 pixels.
* For Code 39 symbols: a 20 mil X-dimension results in a density of approximately 3.6 characters per inch. Optimally the height should be at least 1/4 inch or 15% of the width, whichever is greater, though this is not an absolute requirement. The minimum quiet zone (white space before and after the bar code) specified by the standard is 1/5 inch. |
bb4e949f68fdee76dfcdf86bc91e6628_2 | * Scanning can sometimes introduce white or black stripes on the image running in the scanning direction, typically vertical stripes if the paper is scanned in Portrait orientation. Bar codes printed in normal horizontal orientation cannot be read reliably when this occurs. It is advisable to print barcodes perpendicular to the direction of scanning. If the barcode must be printed horizontally on a page, scanning in landscape orientation will make the barcode more robust in the presence of common scanner issues.
* By default, Datacap only accepts barcode images with 71% confidence or higher. To modify it to accept low confidence barcodes also, add the following action to run prior to barcode detection: * SetMinimumConfidenceBP(1) - This is equivalent to 11% confidence. Each increment increases the required confidence 10% and higher values can be used if false barcodes are detected. A value of 4 is usually sufficient for this purpose. |
bb4e949f68fdee76dfcdf86bc91e6628_3 | * Barcode recognition has an internal barcode enhancement capability. To maintain high performance, this feature is turned off by default. If low quality barcodes are being received, it may be desired to turn on barcode enhancement, despite the performance hit. To do this, add the following action to run prior to barcode detection: * rrSet(1,@P.bp_enhance)
* Performing Datacap's regular image enhancement (ImageFix) prior to running any barcode recognition action is not recommended. ImageFix is designed to optimize text recognition and can actually degrade the barcode. There are some rare exceptions, and if it is necessary to use image enhancement prior to barcode recognition, pay close attention to the configuration settings, especially vertical line removal and despeckle. To ensure image processing is not interfering with barcode recognition, test with the ImageFix() action removed. |
bb4e949f68fdee76dfcdf86bc91e6628_4 | Cross reference information Segment Product Component Platform Version Edition Enterprise Content Management Datacap Taskmaster Capture Not Applicable 8.1.0 |
de9917d60e89f93605900bb908f628d8_0 | IBM How to enable the snippet results cache in the Netezza Platform Software releases - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
The snippet results cache feature is disabled by default in some NPS releases. Review this topic to learn how to enable the feature if your queries could benefit from it.
CAUSE
Starting with the June 2015 fix packs for NPS 7.1.0.6 and 7.2.0.5, and the NPS 7.2.1 release, the snippet results cache is disabled by default because it was optimized for specific workloads. Starting in the March fix packs 7.1.0.9, 7.2.0.8, and 7.2.1.2, the feature is enabled by default because it is optimized for most workloads.
ENVIRONMENT
Netezza Platform Software releases 7.1.0.6 through 7.1.0.8-P1, 7.2.0.5 through 7.2.0.7-P1 and 7.2.1 through 7.2.1.1-P1
DIAGNOSING THE PROBLEM
Queries that take advantage of the snippet results cache have longer runtimes after upgrades from any 7.x release to a release listed in the Environment section. |
de9917d60e89f93605900bb908f628d8_1 | RESOLVING THE PROBLEM
The snippet results cache is a query optimization feature added in NPS release 7.1 that can help to improve the performance of small queries. The feature was enabled by default for the NPS 7.1 releases up to 7.1.0.6 and for 7.2 releases up to 7.2.0.5.
The snippet results cache saves the intermediate results of snippets and can reuse them rather than incur the processing time to recompute them when needed. The cache can help to improve the performance of small queries.
However, in environments where queries run against tables that constantly change with TRUNCATE, load, updates, and/or rollback operations, caching may not be a good match if cached snippet results are frequently invalidated before they can be reused.
If you upgrade from any 7.x release to a release listed in the Environment section and detect a change in query performance for queries that take advantage of the snippet results cache, you can re-enable the feature. |
de9917d60e89f93605900bb908f628d8_2 | To enable the feature on a session level and test the snippet results cache behavior, you must pause the NPS system, set the variable, and resume the system, as follows:
nzsystem pause -force
nzsystem set -arg system.srcMode=1 -force
nzsystem resume
This setting remains in effect until the database is restarted. You can add the definition to the system.cfg file to keep the setting in effect after the Netezza software restarts:
1. Log in to the Netezza system as the nz user account.
2. With any text editor, open the /nz/data/config/system.cfg file.
3. Look for a system.srcMode definition in the file to make sure that one is not already present and/or commented out. If you find an entry, make sure that system.srcMode=1 is set and not commented out with a # character. If you cannot find an entry, add system.srcMode=1 to the file.
4. Save and close the system.cfg file.
5. Stop and restart the NPS software using the nzstop and then the nzstart commands. |
f291172c3f6909e0f3dd1e5b577e4b84_0 | IBM Rewriting HTTP (port 80) requests to HTTPS (port 443) - United States rewrite; ssl; plugin; dynamic; static; rules; IHS; WAS TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
The rewrite module (mod_rewrite.c) provided with the IBM® HTTP Server can be used as an effective way to automatically rewrite all HTTP requests to HTTPS.
RESOLVING THE PROBLEM
The rewrite module (mod_rewrite.c) can be used to automatically rewrite all HTTP (port 80) requests to HTTPS (port 443). This provides an effective way to ensure that all traffic to and from the IBM HTTP Server is encrypted over the Secure Sockets Layer (SSL) without having to use individual redirects or hard-coded HTTPS links.
Note: The web server should already be configured to handle HTTPS requests successfully
before attempting to implement the following suggestions. For assistance with setting up SSL in the IBM HTTP Server, visit SSL guide [http://www-01.ibm.com/support/docview.wss?uid=swg21179559] |
f291172c3f6909e0f3dd1e5b577e4b84_1 | First, make sure the LoadModule line for mod_rewrite is uncommented in the httpd.conf
LoadModule rewrite_module modules/mod_rewrite.so
Next, add the following to the global scope or any port 80 VirtualHost stanzas defined within the httpd.conf configuration file.
RewriteEngine on
RewriteCond %{SERVER_PORT} =80
RewriteRule ^(.*) https://%{SERVER_NAME}%{REQUEST_URI} [R,L]
Finally, restart the IBM HTTP Server after making the preceding changes
Important: If using HTTP authentication, make sure it is only configured for your SSL virtual host. If it also applies to your port 80 requests, the authentication challenge can pre-empt the rewrite, resulting in user IDs and passwords being sent over an unencrypted session. |
f291172c3f6909e0f3dd1e5b577e4b84_2 | It is also recommended that you configure your port 80 virtual host with a different document root and so on, from your SSL virtual host. This is to be sure that even if your rewrite fails, sensitive information cannot be served from that virtual host over unencrypted sessions.
RELATED INFORMATION
Module mod_rewrite..URL Rewriting Engine [http://httpd.apache.org/docs/mod/mod_rewrite.html] |
50d3398dde2885b50a67059269efdafb_0 | IBM Does the RRT agent support TLS 1.1/1.2 and 256-bit ciphers? - United States 256-bit ciphers; Strong Encryption; TLS 1.1; TLS 1.2; SSL; Generic Failure; Cannot support; RPT; RRT; T6; 71RRT-RPTPLAN; 71RRT-RPTINS; 71RRT-RPTCONF; 71RRT-RPTPLAY; 71RRT-RPTWV; 71RRT-RPTTS TECHNOTE (FAQ)
QUESTION
What do you need to do to configure the Robotic Response Time (RRT) agent to support TLS 1.1/1.2 and 256-bit ciphers?
CAUSE
Support for TLS 1.1/1.2 and 256-bit ciphers is determined by the underlying JRE (Java Runtime Environment). Consequently, in order to support TLS 1.1/1.2 and 256-bit ciphers, patch the RPT workbench JRE, and patch the RRT agent JRE. Both JREs must support the same level of TLS.
ANSWER
SSL (Secure Sockets Layer) and TLS (Transport Layer Security) are transport layer protocols. Ciphers implement security by providing the encryption mechanism. |
50d3398dde2885b50a67059269efdafb_1 | TLS is the new protocol. SSL protocol got up to version 3.0. In effect, TLS 1.0 is SSL 3.1. Currently, TLS versions include TLS 1.1 and 1.2. Each new version adds new features and modifies internal details.
Whether the RRT agent supports TLS1.1/1.2 depends on whether the underlying JRE supports TLS 1.1/1.2. The JRE that supports the RRT agent and the JRE that supports RPT workbench must both support the same version of TLS and the same ciphers.
For example, RRT 7.3 FP01 supports RPT 8.3.0.3, but RPT 8.3.0.3 does not support TLS1.1/1.2. Consequently, RRT 7.3 FP01 also does not support TLS 1.1/1.2.
In comparison, RRT 7.4 with IF21 or IF24 (7.4.0.0-TIV-CAMRT-IF0021 or 7.4.0.0-TIV-CAMRT-IF0024) can support RPT 8.3 and RPT 8.6 since RPT 8.6 supports TLS1.1 /1.2, and the IBM Java 7 included with RRT 7.4 also supports TLS 1.1/1.2. |
50d3398dde2885b50a67059269efdafb_2 | However, when a script uses TLS 1.2/1,2, some ciphers may not be supported. To verify whether certain cipher suites are supported, visit the IBM Java Knowledge Center:
IBM Java Cipher Suite Information
http://www-01.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.security.component.70.doc/security-component/jsse2Docs/ciphersuites.html?lang=en [http://www-01.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.security.component.70.doc/security-component/jsse2Docs/ciphersuites.html?lang=en]
Do You Need to Patch Java?
First, determine whether your script uses 256-bit ciphers. In RPT workbench, open the script in Test Editor mode. In the left panel, drill down through the Server Access Configurations. Select SSL.
[/support/docview.wss?uid=swg21960133&aid=1] |
50d3398dde2885b50a67059269efdafb_3 | In the right panel, examine the available ciphers that display. If the list contains 256-bit ciphers, you need to support Strong Encryption in RPT and the RRT agent. The name identifies the encryption level. For example, SSL_DHE_RSA_WITH_AES_256_CBC_SHA is a 256-bit cipher. The presence of 256 in the cipher name means that the cipher supports 256-bit encryption.
[/support/docview.wss?uid=swg21960133&aid=2] [/support/docview.wss?uid=swg21960133&aid=2]
Cipher Naming Conventions
In RPT workbench, the cipher name always begins with "SSL" to simplify naming conventions. If the script uses TLS as the protocol in the test, then the cipher is a TLS cipher.
[/support/docview.wss?uid=swg21960133&aid=3] [/support/docview.wss?uid=swg21960133&aid=3]
Playback Symptoms
Check whether your script playbacks indicate that the RRT JRE needs to be patched to support Strong Encryption. Strong Encryption adds 256-bit ciphers. |
50d3398dde2885b50a67059269efdafb_4 | 1) The Playback Status workspace shows that playbacks are complete, but the Verification Failures workspace shows:
Event Type: Generic Failure
Violated Value: java.lang.RuntimeException occurred in IBM Registration. Message: java.io.FileNotFoundException: /tmp/RPTTEMP.A1E4CC464D3DD067D
Additional Details: none
2) The trace-robotic log includes messages like the following: |
50d3398dde2885b50a67059269efdafb_5 | [2015-05-05T22:10:58.487-04:00] - MIN - <playback-hostname> - PlaybackThreadPoolWorker-1169 - com.ibm.tivoli.transperf.playback.rpt.RPTPlaybackService.processStatusEvent() - Sending RT VP event: i=|0|, statusEvent=|SimTestStatusEvent Values: monitorName=|<script-name>|,URL=|<monitored-url>|,eventType=|com.ibm.rational.test.lt.HTTPPageVerdict|,eventId=|516.b32|,parentEventId=|516.b27|,ownerId=|A1E4ED99F22F68E2FD5CB86461633031|,text=|Error occurred during connection to server '<server-url>'. Explanation message: 'Cannot support SSL_DHE_RSA_WITH_AES_256_CBC_SHA with currently installed providers'. Since this request is the primary request for the current page all secondary requests will be skipped and the next page will be attempted.|,name=|Primary Request verdict|,actualValue=||,expectedValue=|null|,eventVerdict=|3|,eventReason=|2|,eventDesc=|null||
Patching JREs to Support TLS 1.1/1,2 |
50d3398dde2885b50a67059269efdafb_6 | By default, RPT workbench is configured with restricted or limited strength ciphers. To use less restricted encryption algorithms, you need to download and apply the unlimited jurisdiction policy files (local_policy.jar and US_export_policy.jar).
See Enabling Strong encryption greater than 128 bit key lengths in Rational Performance Tester
http://www.ibm.com/support/docview.wss?uid=swg21245273 [http://www-01.ibm.com/support/docview.wss?uid=swg21245273]
Use the following instructions to patch the JRE that the RRT agent uses.
Note: Backup the jar files that these steps replace -- before you replace these files.
1) Go to the IBM developerWorks Java Technology Security page for JRE 6 security information.
See https://www.ibm.com/developerworks/java/jdk/security/ [https://www.ibm.com/developerworks/java/jdk/security/]
2) Click on the "Java SE 6" link.
3) Click on the "IBM SDK Policy files".
4) On the Sign in page, enter your developerWorks IBM ID and password. |
50d3398dde2885b50a67059269efdafb_7 | 5) After successfully logging in, select Files for Java 5.0 SR16, Java 6 SR13, Java 6 SR5 (J9 VM2.6), Java 7 SR4, and all later releases. Click on Continue.
6) Scroll down to the License portion of the resulting page and click on the View license link to see the licensing terms for the download.
7) If the licensing terms are acceptable, check I agree and click on the I confirm link. If the terms are not acceptable, you are not able to enable strong encryption, and you should click I cancel.
8) Click on the Download now link to download the unrestricted.zip file.
9) Extract the local_policy.jar and US_export_policy.jar files from the unrestricted.zip archive.
10) Log onto the RRT agent host, and stop the RRT agent.
11) Backup the local_policy.jar and US_export_policy.jar files in the <ITM_HOME>/tmaitm6/java60/jre/lib/security and <ITM_HOME>/tmaitm6/java70/jre/lib/security directories on the RRT agent host. |
50d3398dde2885b50a67059269efdafb_8 | 12) Place those two files in the <ITM_HOME>/tmaitm6/java60/jre/lib/security and <ITM_HOME>/tmaitm6/java70/jre/lib/security directories on the RRT agent host. Replace the existing files with the same names. Verify that the file permissions are the same as the files you replaced.
13) Restart the RRT agent.
14) Try to playback the RPT script again. Does the script playback successfully, without error?
RELATED INFORMATION
Security information for JRE 6 [https://www.ibm.com/developerworks/java/jdk/security/]
Enabling Stong encryption greater than 128 bit key leng [http://www.ibm.com/support/docview.wss?uid=swg21245273 ]
HISTORICAL NUMBER
34602.082.000
PRODUCT ALIAS/SYNONYM
ITCAMfT
T7.4 |
40c50987c777b4e68aa532cf1764cca5_0 | IBM Configuring DataPower MQ client to use SSL in mutual authentication mode - United States datapower; mq; websphere mq; ssl; mutual authentication mode; mq manager; 7993; 7993; 7993; machine type 7993 TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
The WebSphere DataPower MQ Client can be configured to use SSL in mutual authentication mode with a Remote WebSphere MQ Manager. This step-by-step technote guides DataPower Appliance users on how to configure DataPower MQ Manager Object to use SSL in mutual authentication mode. This technote assumes that MQ queue manager is configured with key database and its associted password file for using SSL connection with other MQ clients. If it is not configured yet, it has to be done first using the URL: http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.explorer.doc/e_ssl.htm [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.explorer.doc/e_ssl.htm] |
40c50987c777b4e68aa532cf1764cca5_1 | RESOLVING THE PROBLEM
In order to use this technote, you should have a working knowledge of how to setup and administer MQ Server in Windows, AIX, Solaris, HP-UX, or Linux environment. You should also have an understanding of how to configure DataPower MQ Manager Object that connects to remote WebSphere MQ Queue Manager (qmgr). This technote focuses on configuring DataPower MQ Client to use SSL in mutual authentication mode with Firmware Releases 3.8.2 and later fixpacks. Follow these steps to configure DataPower MQ Manager Object (mq-qm object) to access WebSphere MQ Queue Manager (Remote MQ Server) in SSL mutual authentication mode.
WebSphere MQ configuration prerequisites
The following three steps are necessary to make sure that the SSL configurations for the Remote MQ Server is correctly working. Refer to IBM WebSphere MQ product manuals to configure MQ environment to work in SSL mutual authentication mode. |
40c50987c777b4e68aa532cf1764cca5_2 | 1. Configure WebSphere MQ Queue Manager (Remote MQ Server) to use SSL authentication (SSLCAUTH as "required") using URL: http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.explorer.doc/e_ssl.htm [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.explorer.doc/e_ssl.htm].
2. Configure WebSphere MQ Client to use SSL authentication.
3. Verify that WebSphere MQ Client can PUT/GET message(s) using application programs such as amqsputc and amqsgetc with MQ Queue Manager in SSL mutual authentication mode. |
40c50987c777b4e68aa532cf1764cca5_3 | Generate self signed key/certificate
1. Generate the self signed key/certificate pair using the "crypto tool" from the DataPower device.
2. Download the two files to your local machine. For the sake of illustration purpose, the names of the key and certificate files are defined as "dpmqclient-privkey.pem" and "dpmqclient-sscert.pem" respectively.
3. Assuming that openssl tool (www.openssl.org [http://www.openssl.org]) is installed in the local machine. With openssl tool, you can use the following command to create a "pkcs12" type key from the above key/certificate pair which are of PEM type. This step is necessary as MQ key database will not import key/certificate files created as PEM.
openssl pkcs12 -export -out dpmqclient-key.p12-in dpmqclient-sscert.pem-inkey dpmqclient-privkey.pem-name ibmwebspheremqadmin |
40c50987c777b4e68aa532cf1764cca5_4 | Note the value associated with "-name" parameter. IBM WebSphereMQ client required a friendly label as "ibmwebspheremq<userid>" of the MQ client user. In this example, the user name is being used as "admin". This user must be used in the DataPower MQ Queue Manager object and it must also be an authorized user for both the DataPower MQ instance as well as for the remote WebSphere MQ Server. Please refer to Pages G58-62 in the 3.6.0-WebGui Guide for various fields as described in MQ Queue Manager configuration screen. Also note the following two fields with appropriate values which are required for the MQ Queue Manager object to connect the remote WebSphere MQ Server in SSL mode. |
40c50987c777b4e68aa532cf1764cca5_5 | * SSL Key Repository: The key database file name
SSL Cipher Specification: TRIPLE_DES_SHA_US
To import a personal certificate using "iKeycmd" GUI, use the following commands in your host machine where the WebSphere MQ Server/Client is running.
* UNIX
*
*
* gsk7cmd -cert -import -file filename -pw password -type pkcs12 -target filename -target_pw password -target_type cms
*
*
* Windows
*
*
* runmqckm -cert -import -file filename -pw password -type pkcs12 -target filename -target_pw password -target_type cms
*
*
*
*
* -file
* filenam
*
*
* -pw
* password
*
*
* -type
* pkcs12
*
*
* -target
* filename
*
*
* -target_pw
* password
*
*
* -target_type
* cms
*
Generate the new password file |
40c50987c777b4e68aa532cf1764cca5_6 | Follow these steps to generate the new password file.
1. Start the iKeyman GUI using either the gsk7ikm command (on UNIX) or the strmqikm command (on Windows).
2. From the Key Database File menu, click Open. The Open window displays.
3. Click Key database type and select CMS (Certificate Management System).
4. Click Browse to navigate to the directory that contains the key database files.
5. Select the key database file in which you want to save the certificate, for example key.kdb.
6. Click Open. The Password Prompt window displays.
7. Type the password you set when you created the key database and click OK.
8. The name of your key database file displays in the File Name field. The Personal Certificates menu will display both "ibmwebspheremq<qmgr>" and "ibmwebspheremq<user>" labels. |
40c50987c777b4e68aa532cf1764cca5_7 | 9. In the WebSphere MQ Certificate key database, there is one certificate assigned to the queue manager or client. The certificate's Friendly Name attribute contains the string ibmwebspheremq followed in lower case by the queue manager name or the client logon ID. This Friendly Name value becomes the label of the certificate in the GSKit key database. Refer to Alter the Friendly Name (Label) of pkcs12 certificates for importing into GSKit [http://www-01.ibm.com/support/docview.wss?uid=swg21225160] if you want to alter the Friendly Name (Label) of pkcs12 certificates that are part of WebSphere MQ Certificate key database. Refer to "Migrating SSL Security Certificates in WebSphere MQ for Windows" [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzas.doc/sy12430_.htm?resultof=%22%6d%71%22%20%22%66%69%78%22%20%22%6d%69%67%72%61%74%65%64%22%20%22%6d%69%67%72%61%74%22%20%22%63%65%72%74%69%66%69%63%61%74%65%73%22%20%22%63%65%72%74%69%66%22%20] if you want to fix the |
40c50987c777b4e68aa532cf1764cca5_8 | migrated certificates from the WebSphere MQ V5.3 version to later version. [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.csqzao.doc/mi10240_.htm] |
40c50987c777b4e68aa532cf1764cca5_9 | 10. From the key database File menu, click Stash Password. This will create the new password file as "key.sth". Select OK and close the key database File. |
40c50987c777b4e68aa532cf1764cca5_10 | 11. Upload the "key.kdb" and "key.sth" files to "cert:" directory of the DataPower box. Configure the MQ client object in the DataPower box to use this key database as shown in the screen shot above to connect in SSL mutual authentication mode with the MQ Manager. The following screen shot shows the "key.kdb" and "key.sth" files are located in the "cert:" directory of the application domain.[/support/docview.wss?uid=swg21260155&aid=1] [/support/docview.wss?uid=swg21260155&aid=1] This screen shot below shows that mq-qm object is using the "key.kdb" file located in the "cert:" directory with the associated cipher specification as "TRIPLE_DES_SHA_US". Note that SSL Proxy Profile field is "(none)" as this configuration is using key repository method for SSL connection.[/support/docview.wss?uid=swg21260155&aid=2] [/support/docview.wss?uid=swg21260155&aid=2] |
40c50987c777b4e68aa532cf1764cca5_11 | 12. Refresh the SSL security attribute of the MQ Manager to use this key database and password files from the host machine running MQ Server.
Runmqsc <MQ Manager>
Refresh security type(ssl)
End
13. Test your application to PUT/GET MQ message(s) using DataPower MQ client with the new configuration. |
40c50987c777b4e68aa532cf1764cca5_12 | Note: DataPower 3.8 and later firmware provides a separate method for the mq-qm object to use SSL in mutual authentication mode. This method uses DataPower SSL Proxy Profile that includes Crypto profile with Identification Credential. For more details, refer to DataPower InfoCenter on how to create SSL Proxy Profile:
https://www.ibm.com/support/knowledgecenter/SS9H2Y_7.1.0/com.ibm.dp.doc/mq_securingwithansslproxyprofileobject.html [https://www.ibm.com/support/knowledgecenter/SS9H2Y_7.1.0/com.ibm.dp.doc/mq_securingwithansslproxyprofileobject.html] (Fixpack V7.1.0.x)
https://www.ibm.com/support/knowledgecenter/SS9H2Y_7.2.0/com.ibm.dp.doc/mq_securingwithansslproxyprofileobject.html [https://www.ibm.com/support/knowledgecenter/SS9H2Y_7.2.0/com.ibm.dp.doc/mq_securingwithansslproxyprofileobject.html] (Fixpack V7.2.0.x) |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.