chunk_id string | chunk string |
|---|---|
8907ba67c01af38ff89799fda86085c2_17 | 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
26 June 2015: original document published
29 June 2015: fix serveservlets custom property name and add workaround
30 June 2015: fix serveservlets custom property
16 July 2015: added additional links to ifixes
13 August 2015: added additonal link to ifixes
2 September 2015: updated fix pack dates and level
13 November 2015: updated interim fix PI39768 with PI49437
*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. |
8907ba67c01af38ff89799fda86085c2_18 | 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.
Cross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Hypervisor Edition Application Servers WebSphere Virtual Enterprise |
ac495b774ee063654cd170d8edcc628e_0 | IBM DOORS module fails to open in exclusive edit mode results in error "unable to open module ...no such file or directory" - United States missing session file; file not found; can not open module; open module exclusive edit fails; PM50525 TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Attempts to open a module exclusive edit in IBM Rational DOORS result in the error "DOORS report
Unable to open module '/A Project/Requirements' No such file or directory".
SYMPTOM
A module with a large number of sections is used mostly in shareable edit mode.
You can open the module Read-only , or Shareable-Edit; but not in exclusive edit.
Steps to reproduce:
1. Login to DOORS
2. Click the Project, or folder, icon that contains the module
3. Click the module icon in the DOORS Explorer window
4. Click File > Open> Exclusive Edit (Ctrl + E)
Expected result: The module should open in Exclusive edit mode. |
ac495b774ee063654cd170d8edcc628e_1 | Actual result: The module will not open in exclusive edit module; however it will open in read only mode, or shareable edit mode. If you attempt to check the database integrity for issue the module is not flagged for any problems.
The full error message is as follows:
DOORS report
Unable to open module '/A Project/Requirements' No such file or directory"
C:\Program Files (x86)\IBM\Rational\DOORS\9.5\data\v6data\20\m00000021.mod\current.ver\s1000005.dtc
image
[/support/docview.wss?uid=swg21511831&aid=1] [/support/docview.wss?uid=swg21511831&aid=1]
CAUSE
This issue has been identified as a product defect under APAR PM50525 [http://ibm.com/support/docview.wss?uid=swg1PM31236].
RESOLVING THE PROBLEM
This error indicates that a user session file is corrupted on the database server.
This defect is resolved in IBM Rational DOORS Version 9.4.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27036720#9401]
WORKAROUND: |
ac495b774ee063654cd170d8edcc628e_2 | the following options can be used to correct this problem:
* Retrieve the missing file from system backup and insert it into the module current.ver directory
The advantage of inserting the missing session file is you do not need to restart the database server.
Warning these two option should only be performed by Rational Support. Modifications to the files in your DOORS database could result is data corruption and jeapordize your DOORS database. Send the session.ixc file to support for repair
From the module directory listed in the error message provide support the file session.ixc
Choosing to have support repair the session index file requires you to have all users log out
and shut down the DOORS database server until the repaired file is returned and inserted
to replace the existing data file for the module. |
ac495b774ee063654cd170d8edcc628e_3 | Create a replacement session file
From the module directory listed in the error message provide support the file session.ixc
Adjacent session files will be required in order to to create the replacement.
Your support engineer will identify these files from the session index file.
No work can be performed in the effected module until the replacement session file is restored
for the effected module.
Note: Generally the repair is only required for one user session file. However in circumstances where DOORS reports a missing session file for a module- the event that caused this may have effected session files for other users connected to the module. For this situation you may need to perform a successive repair to the index file. |
da86865b693fe704917b93412893e306_0 | IBM Late breaking updates to DataPower 7.5 documentation - United States NEWS
ABSTRACT
The version 7.5 documentation for IBM DataPower Gateway is not the latest available information. This document covers late breaking updates that are not in IBM Knowledge Center.
Last updated, October 2017.
CONTENT
The late breaking updates in this document apply to DataPower Gateway version 7.5 documentation.
To access specific updates, click the appropriate link: * Upgrade
*
* Installation
*
* GatewayScript
*
* File management
*
* Monitors
To view the change history of this document, see Change history
The corrections in the following sections apply to DataPower Gateway version 7.5 in IBM Knowledge Center. |
da86865b693fe704917b93412893e306_1 | Upgrade *
* Disabled diffie-hellman-group-exchange-sha1 and diffie-hellman-group1-sha1 algorithms by default. Disabled MD5-based MAC algorithms. Limited DH-GEX to 4096 bits for Cisco devices.
*
*
* enable-legacy-kex yes
*
* The enable-legacy-kex command for the SSH server profile in available in 7.5.2.0. The enable-legacy-kex command for the SSH client profile is available in 7.5.2.7.
*
*
* Default cipher suites * chacha20-poly1305@openssh.com (CHACHA20-POLY1305_AT_OPENSSH.COM)
*
* aes128-ctr (AES128-CTR)
*
* aes192-ctr (AES192-CTR)
*
* aes256-ctr (AES256-CTR)
*
* aes128-gcm@openssh.com (AES128-GCM_AT_OPENSSH.COM)
*
* aes256-gcm@openssh.com (AES256-GCM_AT_OPENSSH.COM)
*
* arcfour256 (ARCFOUR256)
*
* arcfour128 (ARCFOUR128)
*
* aes128-cbc (AES128-CBC)
*
* 3des-cbc (3DES-CBC)
*
* blowfish-cbc (BLOWFISH-CBC)
*
* cast128-cbc (CAST128-CBC)
* |
da86865b693fe704917b93412893e306_2 | * aes192-cbc (AES192-CBC)
*
* aes256-cbc (AES256-CBC)
*
* arcfour (ARCFOUR)
*
* rijndael-cbc@lysator.liu.se (RIJNDAEL-CBC_AT_LYSATOR.LIU.SE)
Default KEX algorithms * curve25519-sha256@libssh.org
*
* ecdh-sha2-nistp256
*
* ecdh-sha2-nistp384
*
* ecdh-sha2-nistp521
*
* diffie-hellman-group-exchange-sha256
*
* diffie-hellman-group14-sha1
Default MAC algorithms * umac-64-etm@openssh.com
*
* umac-128-etm@openssh.com
*
* hmac-sha2-256-etm@openssh.com
*
* hmac-sha2-512-etm@openssh.com
*
* hmac-sha1-etm@openssh.com
*
* umac-64@openssh.com
*
* umac-128@openssh.com
*
* hmac-sha2-256
*
* hmac-sha2-512
*
* hmac-sha1
*
* |
da86865b693fe704917b93412893e306_3 | * The SSH client always initiates the banner exchange. During the SSH2 banner exchange, use CR+LF termination for the banner. The SSH client ignores any message from the SSH server until the banner exchange. |
da86865b693fe704917b93412893e306_4 | Back to top
Installation *
* show other-sensors
*
* show sensors-other
*
Back to top
GatewayScript *
* clear gatewayscript-cache path
*
Back to top
File management *
* isamwebroot local policyframework
Back to top
Monitors *
* type
*
* block
*
* shape
*
* type command
*
Back to top
Change history
Last modified: 30 October 2017. * 30 October 2017: Added information about nonexisting block keyword for Message Filter Action type command.
* 19 October 2017: Added information about which directories you can create and remove subdirectories.
* 19 July 2016: Added data about the wrong command troubleshooting command in the installation documentation.
* 17 June 2016: Added data about the undocumented Global command.
* 22 March 2016: Created for 7.5.
Back to top |
58b5e0b5624992934edd72415f74b35f_0 | IBM Data Server Manager (DSM) showing SQLCODE=-206 "<name> is not valid in the context where it is used." - United States SQLCODE 206 -206 SQL0206 SQL0206N DSM incompatible db2level fixpack fix pack db2iupdt TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Data Server Manager log files are full of SQLCODE=-206 "<name> is not valid in the context where it
is used." error
SYMPTOM
The symptoms can vary depending on each installation.
Most common scenario, DSM shows Data Pending status for the monitored database.
CAUSE
When you apply a new DB2 fixpack, the db2iupdt command is used to update an instance to a higher level within a release.
But that command does not necessarily update the database system catalog to support the new fix pack that you have installed.
Meaning, just because the db2level shows a higher level, your database can still be using routines from an older DB2 level. |
58b5e0b5624992934edd72415f74b35f_1 | DIAGNOSING THE PROBLEM
One way to verify what routine levels your database is using, you can run the following DB2 command on the monitored database:
db2 "select versionnumber from sysibm.sysversions order by 1 desc"
If the results is showing a lower level than the ones DSM supports, that means your environment
is not supported, and you are getting the SQLCODE=-206 error.
To verify what are the DB2 levels supported by DSM, please refer to the links below:
- System requirements for IBM Data Server Manager, version 1.1.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27045176]
- System requirements for IBM Data Server Manager, version 2.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27048115]
RESOLVING THE PROBLEM
Run the db2updvnn command according to the db2level of your monitored database: |
58b5e0b5624992934edd72415f74b35f_2 | - For DB2 V9.7 run db2updv97 [https://www.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command
- For DB2 V10.1 run db2updv10 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command
- For DB2 V10.5 run db2updv105 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command
- For DB2 V11.1 run db2updv111 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command |
5cbc62646afe3ffccfb0aa38006b7c63_0 | IBM Security Bulletin: Persistent cross-site scripting vulnerability in Process Admin Console affecting IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) CVE-2015-0156 - United States SECURITY BULLETIN
SUMMARY
IBM Business Process Manager is vulnerable to stored cross-site scripting, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability using a specially-crafted URL to execute script in a victim's Web browser within the security context of the hosting Web site, once the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials.
VULNERABILITY DETAILS
CVEID:CVE-2015-0156 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0156] |
5cbc62646afe3ffccfb0aa38006b7c63_1 | DESCRIPTION:IBM Business Process Manager is vulnerable to stored cross-site scripting, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability using a specially-crafted URL to execute script in a victim's Web browser within the security context of the hosting Web site, once the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials.
CVSS Base Score: 3.5
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/100792 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100792]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:S/C:N/I:P/A:N)
AFFECTED PRODUCTS AND VERSIONS
* IBM Business Process Manager Standard V7.5.x, 8.0.x, 8.5.x
* IBM Business Process Manager Express V7.5.x, 8.0.x, 8.5.x
* IBM Business Process Manager Advanced V7.5.x, 8.0.x, 8.5.x
* WebSphere Lombardi Edition 7.2.x |
5cbc62646afe3ffccfb0aa38006b7c63_2 | If you are using an earlier unsupported version, IBM strongly recommends to upgrade. REMEDIATION/FIXES
Install the interim fix for APAR JR52420 as appropriate for your current IBM Business Process Manager or IT06812 for your current WebSphere Lombardi Edition environment. |
5cbc62646afe3ffccfb0aa38006b7c63_3 | * IBM Business Process Manager Express [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Express&release=All&platform=All&function=aparId&apars=JR52420]
* IBM Business Process Manager Standard [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Standard&release=All&platform=All&function=aparId&apars=JR52420]
* IBM Business Process Manager Advanced [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Advanced&release=All&platform=All&function=aparId&apars=JR52420]
* WebSphere Lombardi Edition [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Lombardi+Edition&release=All&platform=All&function=aparId&apars=IT06812]
WORKAROUNDS AND MITIGATIONS
None |
5cbc62646afe3ffccfb0aa38006b7c63_4 | 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.
REFERENCES
Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]
On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] |
5cbc62646afe3ffccfb0aa38006b7c63_5 | 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
2015-05-13 - initial version published
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. |
5cbc62646afe3ffccfb0aa38006b7c63_6 | 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. |
5cbc62646afe3ffccfb0aa38006b7c63_7 | Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Security AIX, Linux, Linux zSeries, Solaris, Windows 8.5.6, 8.5.5, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration IBM Business Process Manager Express Security Linux, Linux zSeries, Windows 8.5.6, 8.5.5, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration WebSphere Lombardi Edition AIX, HP-UX, Linux, Linux zSeries, Linux/x86, Platform Independent, Solaris, Windows, Windows Vista, Windows XP 7.2.0.5, 7.2.0.4, 7.2.0.3, 7.2.0.2, 7.2.0.1, 7.2 |
7cb69c9b3d579916ed74f3378fc10f88_0 | IBM "An invalid XML character" error is thrown when handling data originating from a WebSphere Adapter - United States Unicode invalid character 0x0 xml serialize serialization XSLT XLS error TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
WeBSphere Adapter is unable to process data from a source containing unicode data due to a serialization error in the broker indicating that "An invalid XML character (Unicode: 0x0) was found in the element content".
SYMPTOM
When processing data using a broker that originates from a WebSphere JCA Adapter, you encounter an exception of the following form:
Source = java.lang.RuntimeException caught trying to serialize BO BusinessObject: F4211BeginDoc@382a382a (F4211FSBeginDoc=F4211FSBeginDoc@67e667e6) probeid = 214 Stack Dump = java.lang.RuntimeException: An invalid XML character (Unicode: 0x0) was found in the element content: |
7cb69c9b3d579916ed74f3378fc10f88_1 | This error occurs while you are performing data transformations within your broker, either for an XSLT or to enable monitoring or tracing of the data stream, and results in a flow failure.
CAUSE
The problem occurs when the source data contains unicode data which is not allowed in XML. In the above example, this is the unicode character 0x0, but there are a number of other unicode characters that can cause the same result. The problem does not occur in the WebSphere Adapter itself because the WebSphere Adapters are entirely capable of handling full unicode data. Rather, the problem happens in some brokers which fail to properly serialize the incoming data into a valid XML object. |
7cb69c9b3d579916ed74f3378fc10f88_2 | RESOLVING THE PROBLEM
The only complete solution at this time is to not process unicode characters that are not valid in XML. This can be done by not importing data fields that might contain such characters or by purging such characters from the incoming data source. It is not sufficient to do filtering in the BO maps since the broker can still run into problems prior to this Java™ mapping.
If handling of fields containing these unicode characters is essential to your use case, it will be necessary to open a PMR with your broker's support team (rather than the WebSphere Adapter team) to determine if there are any alternatives available.
HISTORICAL NUMBER
75349
344
000 |
88c15c5dc9629f4ba7af7d751bc18001_0 | IBM ERROR: Default DB path is not set, when adding database set on RHEL 5 - United States 1320206; ClearQuest; Command Line Tools; CQ; cqreg; add_dbset; initialize; CQ_DATABASES; CQDB_rgys; registry; db set; db_set; Default DB path is not set; Use cqreg initialize first; linux; RHEL; RHEL5 TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
This technote explains why the error, "Default DB path is not set", occurs when adding a connection with IBM® Rational® ClearQuest® on RedHat Enterprise Linux® (RHEL) 5.
SYMPTOM
When running the command cqreg add_dbset, this error occurs:
"Default DB path is not set"
"Default version is 7.0.0"
/opt/rational/clearquest/CQDB_rgys/cqdb_registry/7.0.0 does not exist. Use cqreg initialize first.
CAUSE
Normally, at the end of a ClearQuest installation on UNIX® based platforms, the cqreg initialize command runs automatically. The command creates the registry structure for database sets. During the installation, the command did not run successfully. |
88c15c5dc9629f4ba7af7d751bc18001_1 | DIAGNOSING THE PROBLEM
Verify that the CQDB_rgys directory exists, as defined in the installation options. The following is the default registry location:
/opt/rational/clearquest/CQDB_rgys/cqdb_registry/
If not present, then the cqreg initialize command was not successful.
RESOLVING THE PROBLEM
Run cqreg initialize. The add_dbset command will run successfully afterwards. However, should the same error persist, make sure the command is run as the root user.
Also make sure that the CQ_DATABASES environment variable is set to the desired registry path. If it is not, set the variable accordingly, then run the previously mentioned commands again. |
66bde82de61d1441f3e7dea6d7b23433_0 | IBM PureData Systems for Analytics - nzsql error, Records trailing spring space set to 512 is too small - United States netezza PDA TECHNOTE (FAQ)
QUESTION
What does the message "ERROR: Records trailing spring space set to 512 is too small..." mean?
ANSWER
The following error may appear in the pg.log file:
ERROR: Records trailing spring space set to 512 is too small : Bump it up using the environment variable NZ_SPRINGFIELD_SIZE
This error can occur when a query includes multiple aggregates against varchar or nvarchar columns. As the query is being processed the system allocates memory for each row of the result set. This includes each of the GROUP BY columns and each of the aggregates. For queries doing aggregates on variable length columns, the total length of the record will vary during the process. For example, if the current min value is "Boston" and the new min value is "Albuquerque" space for the new min value needs to increase. |
66bde82de61d1441f3e7dea6d7b23433_1 | The NZ_SPRINGFIELD_SIZE is an extra pseudo-column that is tacked onto each row. It does not contain any data. It is a filler that starts out at NZ_SPRINGFIELD_SIZE and then dynamically shrinks and expands as needed to keep each of the aggregate rows at a fixed length. There is a single springfield in each grouping record that has to shrink and grow to offset the combined changes in width of the running values for all min/max aggregates.
To avoid this error message, increase the value for this parameter as follows:
1. nzstop
2. export NZ_SPRINGFIELD_SIZE=1024
3. nzstart
You can confirm that the environment variable took effect by running the command "nzsystem showregistry". The output should contain the following: "system.maxSpringFieldSize = 1024". |
66bde82de61d1441f3e7dea6d7b23433_2 | Unfortunately, the setting for NZ_SPRINGFIELD_SIZE will revert to its default value the next time the database is stopped and started without the NZ_SPRINGFIELD_SIZE environment variable being set. To ensure that the setting persists after every database restart, do the following:
1. Add the following line to the /nz/data/config/system.cfg file. (Create the file if it does not exist.)
system.maxSpringFieldSize = 1024
2. nzstop
3. nzstart
If 1024 does not work, try higher values. Setting the limit may take a little trial and error. Increasing this value should not have a noticeable impact on other system performance. |
66bde82de61d1441f3e7dea6d7b23433_3 | Note: "By default 512 bytes is allocated to each row taking part in aggregations. By increasing this value by 512 we allocate over 30MB more memory for every 1 000 000 rows participating in aggregations. This is for one query, there might be other queries in the system which do aggregations as well. The more memory that is allocated for NZ_SPRINGFIELD_SIZE (for each row) the less memory left for other processes. Having said this, it is not uncommon to see NZ_SPRINGFIELD_SIZE set to 8192 without consequence but care must be taken and one must still be aware of how increasing NZ_SPRINGFIELD_SIZE will impact resources, thus increase it wisely. "
HISTORICAL NUMBER
NZ755310 |
5f63136815db75602c3b4cc809f3c2fe_0 | IBM Syndicating to VP with exclusive realms does not work. - United States syndication; realm; vp; admin user; getPortalAdministrator TECHNOTE (TROUBLESHOOTING)
PROBLEM
Syndication from base Portal to Virtual Portal with different realms does not work:-
1) Create 2 different realms with different base entries and map one realm ( with base entry e.g DC=org1,DC=test) to base Portal.
2) Create a Virtual portal and map it to another realm ( with base entry e.g DC=org2,DC=test).
3) Attempt to carry out syndication from Base Portal to Virtual Portal.
4) The syndication fails with below exception: |
5f63136815db75602c3b4cc809f3c2fe_1 | [datetime] 0000007f PackageGenera I createIceProjectItemRemoves():: p_items length = 0
[datetime] 0000008b ResponseBL I Performing response for sender: 1abc2a07-e70a-4804-8e09-b7b897eef534 |
5f63136815db75602c3b4cc809f3c2fe_2 | [datetime] 000000a1 SubscriberTas E Unexpected exception thrown while updating subscription: [IceId: <1abc2a07-e70a-4804-8e09-b7b897eef534> Current State: <ICE-INITIAL>], exception: com.presence.connect.wmmcomms.exception.MemberNotFoundException: Message: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST, Cause: com.ibm.wps.um.exceptions.impl.MemberNotFoundExceptionImpl: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST com.presence.connect.wmmcomms.exception.MemberNotFoundException: Message: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST, Cause: com.ibm.wps.um.exceptions.impl.MemberNotFoundExceptionImpl: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST
[...] |
5f63136815db75602c3b4cc809f3c2fe_3 | at com.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator(UserManagementServiceImpl.java:1678)
[...] |
5f63136815db75602c3b4cc809f3c2fe_4 | CAUSE
The Admin user exists on Base Portal but not the Realm which is configured to Virtual Portal.
The Administrator User who is listed as the Domain Admin retrieved with:
com.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator() does not have access to the Virtual Portal.
RESOLVING THE PROBLEM
The Admin user has to be made visible on both base and virtual Portals if you wish to syndicate between the two.
When syndicating to Virtual Portals, the Administrator User who is listed as the Domain Admin retrieved with:
com.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator() should have access to the Virtual Portal.
RELATED INFORMATION
Realm Support [http://www-10.lotus.com/ldd/portalwiki.nsf/xpDocViewer.xsp?lookupName=IBM%20WebSphere%20Portal%208%20Product%20Documentation&documentId=3B264D090122D90D85257B26000692C6&action=openDocument&rev=true&mode=original&content=pdcontent] |
5cbf0ea9917c464ab9018053d713636b_0 | IBM Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects IBM MQ Appliance (CVE-2015-7575) - United States SECURITY BULLETIN
SUMMARY
The MD5 “SLOTH” vulnerability on TLS 1.2 affects IBM MQ Appliance
VULNERABILITY DETAILS
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) |
5cbf0ea9917c464ab9018053d713636b_1 | AFFECTED PRODUCTS AND VERSIONS
IBM MQ Appliance M2000
REMEDIATION/FIXES
Apply the ifix for APAR IT13296 [http://www.ibm.com/support/fixcentral/swg/selectFix?product=ibm/WebSphere/IBM%20MQ%20Appliance%20M2000&fixids=8.0.0.4-IBM-MQ-Appliance-M2000-IT13223&function=fixId&parent=ibm/WebSphere].
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] ACKNOWLEDGEMENT
Reported to IBM by Karthikeyan Bhargavan at INRIA in Paris, France
CHANGE HISTORY
26 January 2016 Original Version Published |
5cbf0ea9917c464ab9018053d713636b_2 | *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.
PRODUCT ALIAS/SYNONYM
IBMMQ |
c7e75efe1e548a8f2ab4742f0bf83754_0 | IBM Tivoli Monitoring: HMC Base Agent 6.2.2.3-TIV-ITM_HMC_BASE-IF0004 - United States DOWNLOADABLE FILES
ABSTRACT
This fix resolves the APARs listed in the APAR Number(s) section below, and adds enhancement feature 215857 to add hardware events.
DOWNLOAD DESCRIPTION
Copyright International Business Machines Corporation 2015.
All rights reserved.
Component: IBM(R) Tivoli(R) Monitoring: HMC Base Agent,
Version 6.2.2.3
Component ID: 5724C04HB
Interim Fix 0004, 6.2.2.3-TIV-ITM_HMC_BASE-IF0004
Date: October 20, 2015
Contents:
1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Copyright and trademark information
10.0 Notices
1.0 General description
===============
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below. |
c7e75efe1e548a8f2ab4742f0bf83754_1 | 2.0 Problems fixed
============
The following problems are addressed by this fix.
2.1 APARs
---------------
APAR: IV67769
Abstract: APPLICATION SUPPORT MISMATCH WARNING MESSAGE
Additional information: After installing interim fix
6.2.2.3-TIV-ITM_HMC_BASE-IF0003, the Tivoli Enterprise
Portal might display a warning indicator that states
Application Support Mismatch and shows HMC Base Servers
with Client Version 06220302 and Server Version 06220303.
2.3 Enhancements
------------------
Feature: 215857
Abstract: New Hardware Events Attribute Group
Additional information: Add a new attribute group to collect
hardware events from the Hardware Management
Console (HMC).
Attribute group name: Hardware Events
Table name : KPHHDWEVNTS
Warehouse table name: KPH_HARDWARE_EVENTS or KPHHDWEVNTS
Attribute descriptions: |
c7e75efe1e548a8f2ab4742f0bf83754_2 | Problem_No - The problem number of the event.
Reference_Code - The reference code for the event.
First_Report_Time - The first time when the event was reported.
PMH_No - The IBM hardware support PMR number that
was created if the call home was successful.
Firmware_Fix - The Firmware Fix for the event.
Service_Event_Text - The description of the service event.
Approval_State - The event approval state, either approved or
unapproved.
Duplicated_Count - The number of times the event has occurred.
Severity - The event severity.
System_MTMS - The machine type/model of the server
reporting the event.
Enclosure_MTMS - The machine type/model of the enclosure
system reporting the event.
Created_Time - The time the event was created.
Event_Time - The time the event was reported.
Call_Home_Intended - Defines if call home was intended for this
event, either true or false.
Analyzing_MTMS - The machine type/model of the analyzing system.
Reference_Code_Extent - The extent of reference code. |
c7e75efe1e548a8f2ab4742f0bf83754_3 | System_Ref_code - The system reference code. |
c7e75efe1e548a8f2ab4742f0bf83754_4 | 2.4 Superseded fixes
---------------------
6.2.2.3-TIV-ITM_HMC_BASE-IF0003
6.2.2.3-TIV-ITM_HMC_BASE-IF0002
6.2.2.3-TIV-ITM_HMC_BASE-IF0001
2.5 APARs and defects included from superseded fixes
---------------------------------------------------------------
6.2.2.3-TIV-ITM_HMC_BASE-IF0003
---------------------------------
APAR: IV60709
Abstract: NO CPU DATA WHEN HMC TIME ZONE IS SET TO BST
Additional information: If the Hardware Management Console (HMC)
time zone is set to BST, data might not be collected.
The data provider might use the incorrect time zone
because BST can represent more than one time zone, for
example, British Summer Time and Bangladesh Standard
Time. When the data provider sends the commands to the
HMC to collect the CPU data, the start and stop times of
the commands might not be correct and might not receive
any data. Also, data might be collected, but for the
wrong time frame. |
c7e75efe1e548a8f2ab4742f0bf83754_5 | 6.2.2.3-TIV-ITM_HMC_BASE-IF0002
---------------------------------
Feature: 208626
Abstract: LPAR Memory Attributes
Additional information: The following new attributes are added in
the Server LPARs attribute group:
Current_Memory - The current amount of memory, in megabytes,
configured for the LPAR.
Warehouse name: CM0
Running_Memory - The amount of memory, in megabytes, varied on-line
by the LPAR.
Warehouse name: RM
In order to display these new attributes in the Tivoli Enterprise
Portal, use the Query Editor and select Server LPARs_V9 under
KPH SERVER LPARS.
6.2.2.3-TIV-ITM_HMC_BASE-IF0001
--------------------------------- |
c7e75efe1e548a8f2ab4742f0bf83754_6 | APAR: IV47101
Abstract: NO CPU DATA DUE TO TIME OUTS ON HMC SSH CALLS
Additional information: In large environments, where there are more
than 150 LPARs on a server, the CPU Units used and CPU
Used Pct might display "Not Collected." The
kph_data_provider_<instance>_0.log displays the
following message:
--
SEVERE: SSHCommandExecutor.call: Timed out while waiting
for `lslparutil -m "<server>" -r "lpar" -s s -F
'lpar_id|time|time_cycles |
entitled_cycles|capped_cycles|uncapped_cycles| idle_cycles'
-- |
c7e75efe1e548a8f2ab4742f0bf83754_7 | APAR: IV50134
Abstract: NO CPU DATA WHEN HMC TIME SET TO GMT FORMAT
Additional information: If the HMC time zone is set to a GMT format,
for example, GMT-08:00, CPU data might not be collected
because the data provider does not recognize the GMT
format and will default to using the local time zone.
When the data provider sends the commands to the HMC to
collect the CPU data, the start and stop times of the
commands might not be correct and might not receive any
data. It is also possible that data will be collected,
but for the wrong time frame.
APAR: IV50135
Abstract: NO DATA IN MEMORY AND PAGING SPACE VIEW
Additional information: The System workspace might not display any
data in the Memory and Paging Space views. This can
happen when the HMC commands:
---
monhmc -r swap -n 0
monhmc -r mem -n 0
---
return data in M bytes instead of k bytes:
---
Swap: 1992M total, 0M used, 1992M free, 2853M cached
Mem: 24336M total, 4534M used, 19801M free, 480M buffers
--- |
c7e75efe1e548a8f2ab4742f0bf83754_8 | APAR: IV50686
Abstract: NO CPU DATA IN NON-ENGLISH LOCALE
Additional information: When the agent runs in a non-English locale,
attributes "CPU Units Used" and "CPU Used Pct" might
display as "Not Collected" due to a Java problem. The
kph_data_provider_0.log will have a message similar to
this:
---
WARNING:
ManagementConsoleInventoryItemBuilder$BasicDataCommand.
processResult: An error occurred while parsing the N2 date
field "Fri Sep 27 11:35:31 JST 2013". Continuing.
---
2.2 Defects
---------------
Defect: 207939
Abstract: Java CPCI - deadlock due to bad lock usage in some versions
of Java runtime
Additional information: Classloading and resource loading might get
locks in the wrong order, due to Java APAR IZ96933,
causing the data provider to stop collecting data. This
fix prevents the problem no matter what version of Java is
running. |
c7e75efe1e548a8f2ab4742f0bf83754_9 | Defect: 208541
Abstract: Add log messages to show data sent to kphagent
Additional information: At log level of FINEST, show the contents of
the rows of data sent from the data provider to the
kphagent process.
3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the
IBM Tivoli Monitoring: HMC Base Agent User's Guide, version 6.2.2.3.
Please refer to the IBM Software Product Compatability Reports (SPCR)
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]
3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:
IBM Tivoli Monitoring: HMC Base Agent, Version 6.2.2 Interim
Feature 3, which is available from PassPort Advantage under the
following eAssembly: |
c7e75efe1e548a8f2ab4742f0bf83754_10 | IBM Tivoli Monitoring for System p V6.2.2 Interim Feature 3, English
(CIH93EN) (Both agent and support files are included in this one
package)
IBM Tivoli Monitoring for System p V6.2.2 Interim Feature 3, Language
Support, Multiplatform, Multilingual (CIH94ML)
For details, see the Troubleshooting Wiki:
https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Monitoring/page/System%20P%20Agents [https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Monitoring/page/System%20P%20Agents]
As this fix is cumulative, it can be installed on any fix level for
this version, release, and mod level above the prerequisite.
4.0 Image directory contents
===================
This fix image contains the following files:
- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004.README - This README file
- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004.tar - Fix archive .tar format
- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004.zip - Fix archive .zip format. |
c7e75efe1e548a8f2ab4742f0bf83754_11 | Note: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a UNIX(R) environment; use the .zip file if
you are working in a Windows(R) environment.
The fix archive file contains the following files:
- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004/kphaix526.dsc
- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004/kph_aix526_tema_if0004.tar
- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004/ph_dd.properties
- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004/ph_dd_062203004.xml
- 6.2.2.2-TIV-ITM_HMC_BASE-IF0004/kpk_tems_teps_tepd_if0004.tar
- 6.2.2.2-TIV-ITM_HMC_BASE-IF0004/kpk_tems_teps_tepd_if0004.zip
5.0 Installation instructions
==================
This fix can only be installed over an existing installation. Use
the following steps to install this fix.
5.1 Before installing the fix
------------------------------
- The prerequisites listed under section 3.1 entitled 'Prerequisites
for this fix' must be installed before this fix can be installed. |
c7e75efe1e548a8f2ab4742f0bf83754_12 | - For the purpose of this README, the symbol <CANDLEHOME> is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
on Windows systems.
Before installing this fix on UNIX systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.
For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME
- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.
5.2 Local agent update
--------------------------
1. Transfer the appropriate archive file
(6.2.2.3-TIV-ITM_HMC_BASE-IF0004.tar or .zip) to a temporary
directory on the system that contains the agent code to be
updated. For the purpose of this README, the symbol <TEMP>
represents the fully qualified path to this directory. Note: On
Windows systems, this path includes the drive letter. |
c7e75efe1e548a8f2ab4742f0bf83754_13 | 2. Expand the archive file using the "tar" command on UNIX systems or
an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.
3. Use the "itmpatch" command to install the fix for the operating
system for that agent. For more information on the "itmpatch"
command, see section 6.2.
On UNIX systems, if the fix was expanded to
<TEMP>/6.2.2.3-TIV-ITM_HMC_BASE-IF0004, the install command is:
> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.2.3-TIV-ITM_HMC_BASE-IF0004/kph_aix526_tema_if0004.tar
5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file
(6.2.2.3-TIV-ITM_HMC_BASE-IF0004.tar or .zip) to a temporary
directory on the IBM Tivoli Enterprise Monitoring Server system.
For the purpose of this README, the symbol <TEMP> represents the
fully qualified path to this directory. Note: On Windows systems,
this path includes the drive letter. |
c7e75efe1e548a8f2ab4742f0bf83754_14 | 2. Expand the archive file using the "tar" command on UNIX systems or
an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.
3. To add the agent fix bundles into the remote deploy depot, use the
"tacmd addBundles" command found in $CANDLEHOME/bin on UNIX systems
or in %CANDLE_HOME%\bin on Windows systems. For more information
on the "tacmd addBundles" command, see the IBM Tivoli Monitoring
Administrator's Guide.
On UNIX systems,
if the fix was expanded to <TEMP>/6.2.2.3-TIV-ITM_HMC_BASE-IF0004:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.2.3-TIV-ITM_HMC_BASE-IF0004
On Windows systems,
if the fix was expanded to <TEMP>\6.2.2.3-TIV-ITM_HMC_BASE-IF0004:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.2.3-TIV-ITM_HMC_BASE-IF0004 |
c7e75efe1e548a8f2ab4742f0bf83754_15 | where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the fix
directory does not contain any prerequisites that the fix
might require. Please see Section 3.1 for the prerequisites
for this fix.
-i is the directory that contains the deployment bundles to be
added to the depot.
4. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the
"tacmd login" and "tacmd updateAgent" commands, see the IBM Tivoli
Monitoring Administrator's Guide.
On UNIX systems:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems
The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command. |
c7e75efe1e548a8f2ab4742f0bf83754_16 | > $CANDLEHOME/bin/tacmd updateAgent -t ph
-n <Managed system name>
-v 062203004
On Windows systems:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>
> %CANDLE_HOME%\bin\tacmd listSystems
The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.
> %CANDLE_HOME%\bin\tacmd updateAgent -t PH
-n <Managed system name>
-v 062203004
Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (PH), not three characters (KPH).
- The node (-n) for the "tacmd updateAgent" command is the managed
system name of the operating system (OS) agent to be updated.
The target node for the "tacmd updateAgent" command is always
an OS agent.
5.4 Agent support update
------------------------------ |
c7e75efe1e548a8f2ab4742f0bf83754_17 | This fix 6.2.2.2-TIV-ITM_HMC_BASE-IF0004 includes changes to the agent
support files which need to be installed. Use the following steps to
update the Tivoli Enterprise Monitoring Server, Tivoli Enterprise
Portal Server, or Tivoli Enterprise Portal Desktop.
1. Transfer the appropriate archive file
(6.2.2.2-TIV-ITM_HMC_BASE-IF0004.tar or .zip) to the Tivoli
Enterprise Monitoring Servers, Tivoli Enterprise Portal Servers,
or Tivoli Enterprise Portal Desktops.
2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms. |
c7e75efe1e548a8f2ab4742f0bf83754_18 | 3. Expand the archive file (kph_tems_teps_tepd_if0004.tar or .zip)
that contains the updates for Tivoli Enterprise Monitoring Server,
Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal
Desktop using the "tar" command on UNIX systems or an extract
utility on Windows systems. This step creates a directory
structure that includes a subdirectory called CD-ROM, with the
necessary updates.
4. Use the Application Support Installer(ASI) GUI or the silent
installation method to install the application support files.
Note: For IBM Tivoli Monitoring Version 6.3 or above, one
of the following additional steps must be performed.
1. Acquire a platform-specific pre-packaged JRE version
of the Application Support Installer (ASI). See IBM
Tivoli Monitoring Application Support Installer,
6.2-tiv-itm_asi-if0003 at
http://www.ibm.com/support/docview.wss?uid=swg24034924 [http://www.ibm.com/support/docview.wss?uid=swg24034924]
for download and installation instructions.
-- OR -- |
c7e75efe1e548a8f2ab4742f0bf83754_19 | 2. Specify the '-j javahome' parameter with the path to
a Java(r) 1.5 or java 1.6 installation when running
the itmasi.sh or itmasi.bat script described below.
GUI installation option
------------------------
The GUI can be started by using one of the following commands
from within the CD-ROM directory where setup.jar is located.
On UNIX systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]
On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]
When prompted by the Application Support Installer for the
installable media directory, select the CD-ROM directory, not the
component directory. The installer can install updates for
multiple components at the same time.
Silent installation option
--------------------------
To use the silent installation option, use one of the following
commands from within the CD-ROM directory where setup.jar is
located. |
c7e75efe1e548a8f2ab4742f0bf83754_20 | Note: Using the silent installation option for Linux and zLinux
operating systems requires the following files contained in
interim fix 6.2-TIV-ITM_ASI-IF0001:
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
Follow the installation instructions contained in the
"6.2-TIV-ITM_ASI-IF0001.README".
On UNIX systems:
> ./itmasi.sh -h <CANDLEHOME>[-silent]
[-r <response file>]
[-j <JAVAHOME>]
On Windows systems:
> itmasi -h <CANDLEHOME> [-silent]
[-r <response file>]
[-j <JAVAHOME>]
where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli
Monitoring installation directory.
-r <response file> - Optional. Customized response file name.
The default response file "response.txt" in
the CD-ROM directory can be copied and modified
for your environment. Do not update "response.txt".
-j <JAVAHOME> - Optional. The fully-qualified path to the "bin"
directory where Java(R) is installed. The
location of Java on your system might vary. |
c7e75efe1e548a8f2ab4742f0bf83754_21 | 5. The next panel presented by the Application Support Installer asks
for the selection of which Tivoli Monitoring components you want
to add application support to. For this fix, check or clear the
check boxes as follows:
checked - Tivoli Enterprise Monitoring Server (TEMS)
checked - Tivoli Enterprise Portal Server (TEPS)
checked - Tivoli Enterprise Desktop Client (TEPD)
Continue through the remaining GUI panels selecting the HMC Base
06.22.03.04 support to complete the installation.
6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal
Browser was running when the update was installed, it must be
restarted.
6.0 Additional installation information
========================
For additional troubleshooting installation information, see the
itmpatch.log in the patchlogs directory in <CANDLEHOME>. |
c7e75efe1e548a8f2ab4742f0bf83754_22 | 6.1 Installation instructions for agent baroc file
-----------------------------------------------------
This fix 6.2.2.2-TIV-ITM_HMC_BASE-IF0004 includes changes to the
agent baroc files that must be installed. Refer to IBM Tivoli
Monitoring Installation and Setup Guide under "Installing monitoring
agent baroc files on the event server" in "Installing the IBM Tivoli
Enterprise Console Event Synchronization" section for more
information.
6.2 Additional information on using "itmpatch" command
--------------------------------------------------------------
The "itmpatch" command has the following syntax:
Usage: itmpatch -h <installation home> [OPTIONS]
itmpatch -h <installation home>
-t { <patch_file_directory> | <patch_file> }
itmpatch -h <installation home>
-i { <patch_file_directory> | <patch_file> } |
c7e75efe1e548a8f2ab4742f0bf83754_23 | where:
-h Specifies the IBM Tivoli Monitoring installation directory
-i Specifies the path to the directory or patch file to be installed
-t Generates a report of the actions to be taken by the patch
For example, on UNIX systems:
- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>
- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>
where:
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring
installation directory. On Windows systems, this path must include
the drive letter.
<TEMP> represents the fully qualified directory specification where
the fix is located. On Windows systems, this must include the drive
letter.
6.3 Verifying the update
---------------------------- |
c7e75efe1e548a8f2ab4742f0bf83754_24 | 1. To verify the agent was updated correctly, use the "tacmd" command
to view the agent's current version after the agent is restarted.
You are required to log in to a Tivoli Enterprise Monitoring
Server prior to viewing the agent version.
For example:
On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring
installation directory, the default location is '/opt/IBM/ITM'.
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems -t PH
On Windows systems, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory, the default location
is 'C:\IBM\ITM'.
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>
> %CANDLE_HOME%\bin\tacmd listSystems -t PH
Note: The component (-t) for the "tacmd listSystems" command is
specified as two characters (PH), not three characters (KPH).
When the agent update is successful, the agent version is:
06.22.03.04. |
c7e75efe1e548a8f2ab4742f0bf83754_25 | 2. To verify the agent support files were updated correctly, use the
"kincinfo" command on Windows systems or the "cinfo" command on
Linux or UNIX systems. The sample output below shows the versions
of the Tivoli Enterprise Portal Server, Tivoli Enterprise
Monitoring Server, or Tivoli Enterprise Portal Desktop systems
after this fix has been successfully applied.
Note: The displayed date of the build might not be accurate. This
is a known problem.
On UNIX or Linux systems:
-------------------------
To validate that all components have been installed, run the
following command:
./cinfo -i
*********** Thu Oct 7 13:57:24 CST 2015 ******************
User: root Groups: system bin sys security cron audit lp
Host name : <hostname> Installer Lvl:06.30.02.00
CandleHome: /opt/IBM/ITM
***********************************************************
...Product inventory
.
.
.
ph Monitoring Agent for HMC Base
tms Version: 06.22.03.04
tps Version: 06.22.03.04
tpw Version: 06.22.03.00
.
.
. |
c7e75efe1e548a8f2ab4742f0bf83754_26 | On Windows systems:
---------------------
To validate that all components have been installed, run the
following command:
For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i
{Add your sample output here}
*********** Thu Oct 7 16:03:55 Eastern Standard Time 2015 **********
User : Administrator Group : NA
Host Name : <hostname> Installer: Ver: 062204000
CandleHome: C:\IBM\ITM
Installitm: C:\IBM\ITM\InstallITM
*********************************************************************
.
.
.
PH Monitoring Agent for HMC Base Support
WINNT Version: 06.22.03.04 Build: 201510070000
PH Monitoring Agent for HMC Base Support
WINNT Version: 06.22.03.04 Build: 201510070000
PH Monitoring Agent for HMC Base Support
WINNT Version: 06.22.03.04 Build: 201510070000
.
.
.
7.0 Known problems and workarounds
=========================
None.
8.0 Additional product information
======================
None. |
c7e75efe1e548a8f2ab4742f0bf83754_27 | 9.0 Copyright and trademark information
==================================
A current list of IBM trademarks is available on the Web at "Copyright
and trademark information" at www.ibm.com/legal/copytrade.shtml.
10.0 Notices
=======
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.
This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice. |
c7e75efe1e548a8f2ab4742f0bf83754_28 | Microsoft, Windows, and Windows Server are trademarks of Microsoft
Corporation in the United States, other countries, or both.
Java and all Java-based trademarks are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States
and other countries.
Other company, product, or service names may be trademarks or service
marks of others. |
c7e75efe1e548a8f2ab4742f0bf83754_29 | Third-Party License Terms and Conditions, Notices and Information
-----------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version. |
c7e75efe1e548a8f2ab4742f0bf83754_30 | Notwithstanding the terms and conditions of any other agreement you
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:
- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.
PREREQUISITES
IBM Tivoli Monitoring: HMC Base Agent, Version 6.2.2 Interim Feature 3 |
c7e75efe1e548a8f2ab4742f0bf83754_31 | INSTALLATION INSTRUCTIONS
Please refer to the README contained in the Description section above for general installation instructions.
DOWNLOAD PACKAGE
Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 6.2.2.3-TIV-ITM_HMC_BASE-IF0004 18 May 2016 English 35850104 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=6.2.2.3-TIV-ITM_HMC_BASE-IF0004&product=ibm%2FTivoli%2FIBM+Tivoli+Monitoring&source=dbluesearch&platform=All] [ ]
PRODUCT ALIAS/SYNONYM
HMC Agent
Monitoring Agent for System P
System P Agent
[/support/docview.wss?uid=swg24042283&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24042283&aid=2]Problems (APARS) fixed
IV47101, IV50134, IV50135, IV50686, IV60709, IV67769 |
76ee641dc774d6627523c7b7a13bda6a_0 | IBM Announcement: End of Support for WebSphere MQ and WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 and WebSphere MQ Telemetry V7.0.1 - United States NEWS
ABSTRACT
IBM has withdrawn support for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ for z/OS V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition for z/OS V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1.
CONTENT
TAB NAVIGATION
* WebSphere MQ and File Transfer Edition V7.0.1 and V7.0.0 • MQ Telemetry V7.0.1 selected tab |
76ee641dc774d6627523c7b7a13bda6a_1 | TAB NAVIGATION
* What were the end of support dates for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1?
* Do these announcements affect WebSphere MQ File Transfer Edition V7.0.4, V7.0.3 and V7.0.2, WebSphere MQ Advanced Message Security V7.0.1, or WebSphere MQ Hypervisor Edition V7.0.1?
* What replacement products are available?
* How do I check which version I am currently running?
* Is any information available to help me upgrade to a later version?
* How do I purchase a support extension for my current version?
* When a WebSphere MQ server product goes out of support, does the client and file transfer agent also go out of support?
* Are these products still supported when they are bundled with another IBM product?
* Is the WebSphere MQ V7.0 Resource Adapter supported in WebSphere Application Server?
* Is documentation still available for these products? |
76ee641dc774d6627523c7b7a13bda6a_2 | * How do I obtain installation images for these products if I still need them?
* Is there an IBM MQ V9.0 or MQ V8.0 trial version available for download? |
76ee641dc774d6627523c7b7a13bda6a_3 | [/support/docview.wss?uid=swg21674407&aid=1]
WHAT ARE THE END OF SUPPORT DATES FOR WEBSPHERE MQ V7.0.1 AND V7.0.0, WEBSPHERE MQ FILE TRANSFER EDITION V7.0.1 AND V7.0.0, AND WEBSPHERE MQ TELEMETRY V7.0.1? |
76ee641dc774d6627523c7b7a13bda6a_4 | * |
76ee641dc774d6627523c7b7a13bda6a_5 | * Product Version Release Date End of Support Platforms WebSphere MQ V7.0.1 28 Aug 2009 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-245] 30 Apr 2015 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] AIX, HP-UX (Itanium), HP-UX (PA-RISC), i5/OS, Linux (POWER), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC), Solaris (x86-64), Windows (x86) WebSphere MQ for z/OS V7.0.1 25 Sep 2009 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-248] 30 Sep 2015 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-150] z/OS WebSphere MQ V7.0.0 16 Jun 2008 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-068] 30 Apr 2015 |
76ee641dc774d6627523c7b7a13bda6a_6 | [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] AIX, HP-UX (Itanium), HP-UX (PA-RISC), i5/OS, Linux (POWER), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC), Solaris (x86-64), Windows (x86) WebSphere MQ for z/OS V7.0.0 27 Jun 2008 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-067] 30 Sep 2011 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS910-014] z/OS WebSphere MQ File Transfer Edition V7.0.1 05 Jun 2009 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-118] 30 Sep 2014 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-158] AIX, HP-UX (Itanium), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC), |
76ee641dc774d6627523c7b7a13bda6a_7 | Windows (x86) WebSphere MQ File Transfer Edition for z/OS V7.0.1 12 Jun 2009 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-119] 30 Sep 2014 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-149] z/OS WebSphere MQ File Transfer Edition V7.0.0 05 Dec 2008 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-331] 30 Sep 2014 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-158] AIX, HP-UX (Itanium), Linux (x86), Solaris (SPARC), Windows (x86) WebSphere MQ File Transfer Edition for z/OS V7.0.0 12 Dec 2008 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-339] 30 Sep 2014 |
76ee641dc774d6627523c7b7a13bda6a_8 | [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-149] z/OS WebSphere MQ Telemetry V7.0.1 27 Aug 2010 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS210-201] 30 Sep 2015 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] Linux (x86-64), Windows (x86) |
76ee641dc774d6627523c7b7a13bda6a_9 | *
* Review lifecycle dates for all IBM MQ and WebSphere MQ products [http://www.ibm.com/software/support/lifecycleapp/PLCSearch.wss?q=%28+%22IBM+MQ%22+OR+%22WebSphere+MQ%22+%29+AND+NOT+%28+Tivoli+OR+Adapter+OR+Broker+OR+Integrator+OR+Workflow+OR+%22Low+Latency+Messaging%22+%29]
End of support information for WebSphere MQ V7.5 and WebSphere MQ Hypervisor Edition V7.5 [http://www.ibm.com/support/docview.wss?&uid=swg21996472]
End of support information for WebSphere MQ V7.1, WebSphere MQ File Transfer Edition V7.0.4, V7.0.3 and V7.0.2, WebSphere MQ Advanced Message Security V7.0.1, and WebSphere MQ Hypervisor Edition V7.0.1 [http://www.ibm.com/support/docview.wss?&uid=swg21980668]
* Back to top |
76ee641dc774d6627523c7b7a13bda6a_10 | DO THESE ANNOUNCEMENTS AFFECT WEBSPHERE MQ FILE TRANSFER EDITION V7.0.4, V7.0.3 AND V7.0.2, WEBSPHERE MQ ADVANCED MESSAGE SECURITY V7.0.1, OR WEBSPHERE MQ HYPERVISOR EDITION V7.0.1?
* IBM has subsequently announced the end of support for these products [http://www.ibm.com/support/docview.wss?uid=swg21980668] on all platforms including z/OS:
*
* Lifecycle dates for WebSphere MQ V7.0 products [http://www.ibm.com/software/support/lifecycleapp/PLCSearch.wss?q=%28%22WebSphere+MQ+%22+AND+%227.0%22%29+OR+%28%22WebSphere+MQ+File+Transfer+Edition+%22+AND+%28%227.0.4%22+OR+%227.0.3%22+OR+%227.0.2%22%29%29+OR+%28%22WebSphere+MQ+Advanced+Message+Security+%22+AND+%227.0.1%22%29]
*
* Back to top
WHAT REPLACEMENT PRODUCTS ARE AVAILABLE? |
76ee641dc774d6627523c7b7a13bda6a_11 | * Replacements for WebSphere MQ V7.0.1 and V7.0.0 include IBM MQ or IBM MQ Advanced V9.0 and V8.0. WebSphere MQ or WebSphere MQ Advanced V7.5 are also available (except on IBM i), but their end of support date is 30 Apri 2018 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117].
* Replacements for WebSphere MQ for z/OS V7.0.1 and V7.0.0 include IBM MQ, IBM MQ Advanced, or IBM MQ Value Unit Edition for z/OS V9.0 and V8.0.0. |
76ee641dc774d6627523c7b7a13bda6a_12 | * Replacements for WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 include IBM MQ Advanced V9.0 and V8.0. WebSphere MQ Advanced V7.5 is also available (except on IBM i), but its end of support date is 30 April 2018 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117]. The Advanced license allows use of the Managed File Transfer and Advanced Message Security components which are now built into MQ and replace the former File Transfer Edition and Advanced Message Security products.
* Replacements for WebSphere MQ File Transfer Edition for z/OS V7.0.1 and V7.0.0 include IBM MQ Advanced for z/OS V9.0 and V8.0.0. The Advanced license allows use of the Managed File Transfer and Advanced Message Security components which are now built into MQ for z/OS and replace the former File Transfer Edition for z/OS and Advanced Message Security for z/OS products. |
76ee641dc774d6627523c7b7a13bda6a_13 | * The replacement for WebSphere MQ Telemetry V7.0.1 is IBM MQ or IBM MQ Advanced V9.0 or V8.0, all of which include Telemetry as a component of the MQ product. WebSphere MQ or WebSphere MQ Advanced V7.5 are also available (except on IBM i), but their end of support date is 30 April 2018 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117].
*
*
* Back to top |
76ee641dc774d6627523c7b7a13bda6a_14 | HOW DO I CHECK WHICH VERSION I AM CURRENTLY RUNNING? |
76ee641dc774d6627523c7b7a13bda6a_15 | * Follow these general instructions [http://www.ibm.com/support/docview.wss?uid=swg21621707] or the IBM MQ Knowledge Center instructions [http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.ref.adm.doc/q083280_.htm] to display your IBM MQ or WebSphere MQ version on all platforms except for z/OS with the command: dspmqver
* On z/OS, look for message CSQY000I [http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.ref.doc/csq_y.htm] in the MSTR joblog to determine your version.
* Follow the IBM MQ Knowledge Center instructions [http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.wmqfte.doc/display_ver_cmd.htm] to display your Managed File Transfer or WebSphere MQ File Transfer Edition version with the command: fteDisplayVersion |
76ee641dc774d6627523c7b7a13bda6a_16 | * WebSphere MQ Telemetry V7.0.1 only runs on WebSphere MQ V7.0.1 (fix pack 7.0.1.3 and later) on Linux (x86-64) and Windows (x86). Although there is no command to display the WebSphere MQ Telemetry version, if your WebSphere MQ version is V7.0.1 and you have a WebSphere MQ Telemetry service and channels [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.tt.doc/tt_intro.htm] configured, then you are running WebSphere MQ Telemetry V7.0.1.
*
* Back to top |
76ee641dc774d6627523c7b7a13bda6a_17 | [/support/docview.wss?uid=swg21674407&aid=2]
IS ANY INFORMATION AVAILABLE TO HELP ME UPGRADE TO A LATER VERSION? |
76ee641dc774d6627523c7b7a13bda6a_18 | * The IBM MQ and WebSphere MQ Migration Guide [https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/websphere_mq_ibm_mq_migration_guide] is available to view online or download:
* IBM MQ and WebSphere MQ Migration Guide [https://www.ibm.com/developerworks/community/blogs/aimsupport/resource/MQ_migration/WMQ_Migration.pdf]
*
* The IBM Knowledge Center also includes information to assist you in migrating to a supported version of IBM MQ or WebSphere MQ:
* Migrating and upgrading to IBM MQ V9.0 [http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.mig.doc/q006180_.htm] Migrating and upgrading to IBM MQ V8.0 [http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.mig.doc/q006180_.htm] Migrating and upgrading to WebSphere MQ V7.5 [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.mig.doc/q006180_.htm]
* |
76ee641dc774d6627523c7b7a13bda6a_19 | * The following WebSphere Support Technical Exchange presentations may be helpful if you are considering running multiple MQ installations on your system:
* Webcast replay: WebSphere MQ Multi-Version - First Steps [http://www.ibm.com/support/docview.wss?uid=swg27024276] Webcast replay: WebSphere MQ Multi-Version - Environment Considerations and Management [http://www.ibm.com/support/docview.wss?uid=swg27024340]
*
* Back to top |
76ee641dc774d6627523c7b7a13bda6a_20 | HOW DO I PURCHASE A SUPPORT EXTENSION FOR MY CURRENT VERSION?
* Support extensions are available for an additional fee. To purchase extended support for WebSphere MQ or any of the other products, please contact your local IBM sales representative.
* US Customers should contact Customer Support Operations at 1-877-426-6006, option #2. If you provide your IBM customer number, they can quickly find your sales representative.
* Customers in other geographies should refer to the IBM directory of worldwide support contacts to find sales contact numbers in your region:
*
* IBM Directory of Worldwide Contacts [http://www.ibm.com/planetwide/]
*
* Back to top
WHEN AN WEBSPHERE MQ SERVER PRODUCT GOES OUT OF SUPPORT, DOES THE CLIENT AND FILE TRANSFER AGENT ALSO GO OUT OF SUPPORT?
* Yes. WebSphere MQ V7.0 clients and WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 agents go out of support at the same time as the server.
*
* Back to top |
76ee641dc774d6627523c7b7a13bda6a_21 | [/support/docview.wss?uid=swg21674407&aid=3]
ARE THESE PRODUCTS STILL SUPPORTED WHEN THEY ARE BUNDLED WITH ANOTHER IBM PRODUCT?
* Yes, support is available for all bundled components until the IBM product that includes them is withdrawn from support. However, they are only supported when used by the bundling IBM product. Unrelated usage is not supported.
*
* Find the end of support date for your IBM software product [http://www.ibm.com/software/support/lifecycle/index_a_z.html]
*
* Back to top
IS THE WEBSPHERE MQ V7.0 RESOURCE ADAPTER SUPPORTED IN WEBSPHERE APPLICATION SERVER? |
76ee641dc774d6627523c7b7a13bda6a_22 | * Yes, the WebSphere MQ V7.0 Resource Adapter [http://www.ibm.com/support/docview.wss?uid=swg21248089#7dotx_0] shipped with WebSphere Application Server V8.0 and V7.0 is supported through 30 April 2018 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-143], when both of those versions of WebSphere Application Server end support, or longer if you purchase a WebSphere Application Server support extension.
* Similarly, the WebSphere MQ V7.1 Resource Adapter [http://www.ibm.com/support/docview.wss?uid=swg21248089#7dotx_0_0] shipped with WebSphere Application Server V8.5.x is supported as long as that version of WebSphere Application Server remains in support, or longer if you purchase a WebSphere Application Server support extension. |
76ee641dc774d6627523c7b7a13bda6a_23 | * However, if you manually install your own copy of the WebSphere MQ V7.x Resource Adapter in WebSphere Application Server or any third-party Java EE server, it will go out of support with the corresponding WebSphere MQ server version.
* The IBM MQ V8.0 and V9.0 Resource Adapters cannot be installed in WebSphere Application Server V8.5.x, V8.0 and V7.0 because those versions support JMS 1.1 while the IBM MQ Resource Adapters implement JMS 2.0. WebSphere Application Server V9.0 ships with the IBM MQ V9.0 Resource Adapter [http://www.ibm.com/support/docview.wss?uid=swg21248089#7dotx_0_0_0] and includes full support for JMS 2.0. The version of MQ Resource Adapter you use must be supported by your Java EE server but does not need to match the version of the queue managers to which you wish to connect.
* Back to top |
76ee641dc774d6627523c7b7a13bda6a_24 | IS DOCUMENTATION STILL AVAILABLE FOR THESE PRODUCTS?
* Yes. Online documentation is available in the IBM Knowledge Center, while downloadable Information Center installations and PDF versions of the manuals are available from the MQ Library page.
*
* WebSphere MQ V7.0.1 Knowledge Center [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.helphome.v70.doc/WelcomePagev7r0.htm] WebSphere MQ V7.0.1 library of downloadable documentation [http://www.ibm.com/software/integration/wmq/library/library701.html] WebSphere MQ V7.0.0 library of downloadable documentation [http://www.ibm.com/software/integration/wmq/library/library700.html] WebSphere MQ File Transfer Edition V7.0.4 Knowledge Center [http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/welcome/WelcomePagev7r0.html] WebSphere MQ Telemetry V7.0.1 [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.tt.doc/tt_intro.htm]
*
* Back to top |
76ee641dc774d6627523c7b7a13bda6a_25 | HOW DO I OBTAIN INSTALLATION IMAGES FOR THESE PRODUCTS IF I STILL NEED THEM?
* Installation images for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1 are no longer available from Passport Advantage [https://www.ibm.com/software/passportadvantage/pao_customer.html]. Contact IBM if you have an urgent business need for these installation images.
*
* Back to top
[/support/docview.wss?uid=swg21674407&aid=4]
IS THERE AN IBM MQ V9.0 OR MQ V8.0 TRIAL VERSION AVAILABLE FOR DOWNLOAD?
* You can obtain a full-featured trial version of IBM MQ to evaluate for 90 days:
*
* Try IBM MQ now [https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?pkgid=&S_SRCID=ESD-WSMQ-EVAL&source=ESD-WSMQ-EVAL&S_TACT=109J84RW&S_CMP=web_ibm_ws_appint_ct_wmq-ov&S_PKG=CR9H9ML&s=&id=2009-08-28+03%3A34%3A46.648052R&fam=&cat=&l=English+International&m=download&ibm-continue=Continue]
*
* Back to top |
76ee641dc774d6627523c7b7a13bda6a_26 | Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere MQ File Transfer Edition Not Applicable AIX, HP-UX, Linux, Solaris, Windows, z/OS 7.0.1, 7.0 All Editions Business Integration WebSphere MQ Telemetry Not Applicable Linux, Windows Business Integration IBM MQ
PRODUCT ALIAS/SYNONYM
WebSphere MQ WMQ |
9221f43b72cef6b22bb773641c60a245_0 | IBM Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM Image Construction and CompositionTool. (CVE-2015-4000) - United States SECURITY BULLETIN
SUMMARY
The Logjam Attack on TLS connections using the Diffie-Hellman (DH) key exchange protocol affects IBM Image Construction and Composition Tool. |
9221f43b72cef6b22bb773641c60a245_1 | VULNERABILITY DETAILS
CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]
DESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as "Logjam".
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N) |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.