chunk_id string | chunk string |
|---|---|
976afa078575ae691a8c7aaf1d14d3f1_5 | The WebSphere MQ Documentation contains a section on planning user authorization which also includes a description on access control for clients. A link to this section in the WebSphere MQ V7.1 Documentation is as follows:
WebSphere MQ > Security > Planning for your security requirements >> Planning authorization [http://pic.dhe.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.doc/zs14070_.htm]
Technotes
A Technote is available that explains J2C Authentication Aliases and how they can be used to configure the user identifier flowed to a queue manager when creating a connection:
Enterprise applications, the WebSphere Application Server WebSphere MQ messaging provider connection factories and Authentication Aliases explained [http://www.ibm.com/support/docview.wss?uid=swg21580097]
Cross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server |
9010cd5b53a77732b0801184b1c48513_0 | IBM Specifying the profile path in the BPMConfig properties file for IBM Business Process Manager (BPM) - United States BPMConfig; profile; path; directory TECHNOTE (FAQ)
QUESTION
How do you specify the profile path in the configuration properties file for IBM Business Process Manager so you can use it with the BPMConfig command?
ANSWER
Note: The information that is contained in this document has been moved to dW Answers at this location [https://developer.ibm.com/answers/questions/171346/how-do-you-specify-the-profile-path-with-bpmconfig.html]. The new format will allow you to ask questions of the community to better understand the information. This technote will be archived in 60 days. Please bookmark the new location.
You can use the following property names:
* For a Deployment Manager profile: bpm.dmgr.profilePath
* For a Custom profile: bpm.de.node.#.profilePath |
9010cd5b53a77732b0801184b1c48513_1 | For example:
bpm.dmgr.profilePath=/usr/IBM/bpm85/profiles/DmgrProfile
bpm.de.node.1.profilePath=c:\\Program Files\\WebSphere\\profiles\\MyCustomProfile1
For Microsoft Windows, you can use double backslashes or forward slashes. For example:
bpm.de.node.1.profilePath=c:/Program Files/WebSphere/profiles/MyCustomProfile1
Note: If you are creating the profile makes sure a profilePath value does not exist. The parent directory of the profile path should exist and the user should have write privileges to create a new directory.
For example, if you want to create a profile under the /usr/BPM850profiles/myProfile directory. Create the/usr/BPM850profiles directory, but do not create the /usr/BPM850profiles/myProfile directory.
RELATED INFORMATION
BPMConfig command: sample configuration properties file [http://www.ibm.com/support/knowledgecenter/SSFTDH_8.5.0/com.ibm.wbpm.imuc.doc/topics/samplecfgprops.html] |
9010cd5b53a77732b0801184b1c48513_2 | Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Advanced Installation / Configuration AIX, Linux, Linux zSeries, Solaris, Windows 8.5
PRODUCT ALIAS/SYNONYM
BPM |
1c6b97fd01a01a3dba38a99fc21aa912_0 | IBM JMSListener AutoReconnect properties misconception - United States netcool; impact; netcool/impact; nci; jms; dsa; connectivity; reconnect; auto; autoreconnect; property; properties; listener; jmslistener; misconception; disinformation; misunderstanding; misinterpretation; error; fault; inaccuracy TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
There appears to be a common misconception regarding the application of the JMS DSA Listener properties for AutoReconnect
SYMPTOM
AutoReconnect fails
CAUSE
Properties for the JMSListener in the file:
$NCHOME/impact/etc/[ImpactServerName]_[JMSListenerName].props
have been set as:
impact.[JMSListenerName].jms.autoreconnect=true
impact.[JMSListenerName].jms.autoreconnect.pollinterval=[TimeValue]
RESOLVING THE PROBLEM
Properties for the JMSListener in the file:
$NCHOME/impact/etc/[ImpactServerName]_[JMSListenerName].props |
1c6b97fd01a01a3dba38a99fc21aa912_1 | Where [ImpactServerName] is the name of the ImpactServer (for example: NCI) and [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and the properties should be set as:
impact.[JMSListenerName].autoreconnect=true
impact.[JMSListenerName].autoreconnect.pollinterval=[TimeValue]
Where [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and [TimeValue] is the desired polling interval value in milliseconds (for example: 30000 (equivalent to 30 seconds)). So, the properties are without the additional .jms bit. |
758fb88676d239ce5946cf8e01d8b3a4_0 | IBM No data in some workspaces for MySQL agent - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Monitoring agent for MySQL when configured to monitor MySQL server versions 5.7.6 and above does not collect data for some of the attribute groups.
SYMPTOM
Data does not get collected for the following views that show system and status variable related information:
View name Workspace name Navigator group name Statistics Statistics Availability Operations per second MySQL status data Availability Session status Agent Configuration Configuration Global status Global variables Server String properties Numeric properties Following exception is seen in the JDBC trace logs:
- JdbcConnection.executeFromList-new - java.sql.SQLException: The 'INFORMATION_SCHEMA.GLOBAL_STATUS' feature is disabled; see the documentation for 'show_compatibility_56' |
758fb88676d239ce5946cf8e01d8b3a4_1 | The above error is seen for MySQL versions 5.7.9 and higher. For MySQL versions prior to 5.7.9, selecting from the INFORMATION_SCHEMA tables produces an empty result set with a deprecation warning.
Note: MySQL agent is packaged with ITCAM for Applications (IBM Tivoli Monitoring) and Application Performance Monitoring 8.1.x solutions.
CAUSE
Few tables in the INFORMATION_SCHEMA that are used by the agent to collect monitoring data are deprecated in the MySQL server versions 5.7.6 and above. Due to this deprecation these tables cannot be queried normally and cause an error when the agent tries to query these tables to get data.
More details about the MySQL INFORMATION_SCHEMA migration to performance_schema here:
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-variable-table-migration.html [https://dev.mysql.com/doc/refman/5.7/en/performance-schema-variable-table-migration.html]
ENVIRONMENT
MySQL agent installed on MySQL Server versions 5.7.6 and above. |
758fb88676d239ce5946cf8e01d8b3a4_2 | RESOLVING THE PROBLEM
Users wanting to run the agent on MySQL server versions 5.7.6 and above should use the 'show_compatibility_56' [https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html] system variable which affects whether MySQL 5.6 compatibility is enabled with respect to how system and status variable information is provided by the INFORMATION_SCHEMA.
This variable can be set from the MySQL command prompt as:
set global show_compatibility_56=ON;
The default value of the variable 'show_compatibility_56' for MySQL server versions <=5.7.7 is ‘ON’ and for versions >=5.7.8 is ‘OFF’.
User can check the value of this variable by running the following command from the MySQL command prompt:
show global variables like "show_compatibility_56";
This variable can also be set in the MySQL server configuration file also called as Option file. |
758fb88676d239ce5946cf8e01d8b3a4_3 | User needs to add the following line to the ‘my.cnf’ file (located at ‘<MySQL_Installation_Dir>/my.cnf’ for Windows and ‘/etc/my.cnf’ for UNIX/Linux):
show_compatibility_56=ON
The paths mentioned above are the default paths for the Option file. For more details on where your installation of MySQL server looks for the 'my.cnf' file, refer the URL:
https://dev.mysql.com/doc/refman/5.7/en/option-files.html [https://dev.mysql.com/doc/refman/5.7/en/option-files.html]
Note: Change in 'my.cnf' file will require a MySQL server re-start for the changes to take effect.
More details on the system variable 'show_compatibility_56' here:
https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_show_compatibility_56 [https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_show_compatibility_56]
PRODUCT ALIAS/SYNONYM
Monitoring agent for MySQL Sever |
d4800c4faa7d7166ff202c90e16cf13b_0 | IBM Security Bulletin: IBM MQ and IBM MQ Appliance MQOPEN call might succeed when it should have failed. (CVE-2017-1341 ) - United States SECURITY BULLETIN
SUMMARY
MQOPEN call might succeed when it should have failed, when using generic profile authority matching for remotely defined MQ object.
VULNERABILITY DETAILS
CVEID: CVE-2017-1341 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1341]
DESCRIPTION: IBM WebSphere MQ could allow, under special circumstances, an unauthorized user to access an object which they should have been denied access.
CVSS Base Score: 3.7
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/126456 [https://exchange.xforce.ibmcloud.com/vulnerabilities/126456] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N)
AFFECTED PRODUCTS AND VERSIONS
IBM MQ V8
Maintenance levels 8.0.0.0 - 8.0.0.7
IBM MQ Appliance V8 |
d4800c4faa7d7166ff202c90e16cf13b_1 | Maintenance levels between 8.0.0.0 and 8.0.0.7
IBM MQ V9
Maintenance levels 9.0.0.0 - 9.0.0.1
IBM MQ V9 CD
IBM MQ 9.0.1 - 9.0.3
IBM MQ Appliance V9 CD
IBM MQ Appliance 9.0.1 - 9.0.3
REMEDIATION/FIXES
IBM MQ V8.0 & IBM MQ Appliance V8.0
Apply fix pack 8.0.0.8 [http://www-01.ibm.com/support/docview.wss?uid=swg22010861&myns=swgws&mynp=OCSSFKSJ&mync=R&cm_sp=swgws-_-OCSSFKSJ-_-R]
Apply fix pack 8.0.0.8 for IBM MQ Appliance [http://www-01.ibm.com/support/docview.wss?uid=swg22010861&myns=swgws&mynp=OCSSFKSJ&mync=R&cm_sp=swgws-_-OCSSFKSJ-_-R]
IBM MQ V9
Apply Fix Pack 9.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24044038]
IBM MQ V9 CD
Upgrade to 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348]
IBM MQ Appliance V9 CD
Upgrade to 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348]
WORKAROUNDS AND MITIGATIONS
None. |
d4800c4faa7d7166ff202c90e16cf13b_2 | 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
30 Nov 2017: Initial version
*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. |
d4800c4faa7d7166ff202c90e16cf13b_3 | 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. |
ba553e51e87096ab77564cee2ca0ea97_0 | IBM Tivoli Netcool/OMINbus Integrations Release Notice - Probe for Nokia Network Functions Manager for Packet (nco-p-nokia-nfmp-1_0) - United States release notice; downloads; nco-p-nokia-nfmp; Probe for Nokia Network Functions Manager for Packet NEWS
ABSTRACT
This new probe will be ready for downloading on July 20, 2017.
CONTENT
This probe is written to support Nokia Network Functions Manager for Packet release 17.3.
You can download the package you require from the IBM Passport Advantage website:
www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/nokia_nfmp/wip/concept/nknfmp_intro.html [http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/nokia_nfmp/wip/concept/nknfmp_intro.html]
Netcool/OMNIbus V8.1
If you are running Netcool/OMNIbus V8.1, a single package contains versions of the probe for all supported Operating Systems. To obtain this new package, use the Find by part number field to search for part number: CNL6HEN |
ba553e51e87096ab77564cee2ca0ea97_1 | The Netcool/OMNIbus V8.1 version of this probe supports the following Operating Systems:
AIX, Linux, Solaris and Windows.
Netcool/OMNIbus V7.4.0
If you are running Netcool/OMNIbus V7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below. |
ba553e51e87096ab77564cee2ca0ea97_2 | Part number Operating System CNL6DEN AIX CNL6EEN Linux CNL6FEN Solaris CNL6GEN Windows Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.
If, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:
https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html] |
f694f12faff48a6c41a642509b278b61_0 | IBM Supported Upgrade and Downgrade paths for DataPower Virtual Edition - United States TECHNOTE (FAQ)
QUESTION
Which WebSphere DataPower virtual edition fix pack can I upgrade to and downgrade from?
CAUSE
Not all scrypt4 fix packs are compatible with the 5.0.0.0 OVA files that were released in November 2012 and March 2013. If you upgrade or downgrade with an incompatible fix pack, unexpected errors might occur.
ANSWER
Use the following links to determine which fix packs are compatible with your virtual deployment.
* 5.0.0.0 from 30 November 2012 (build 220750)
* 5.0.0.0 from 29 March 2013 (build 227007)
* 5.0.0.5
* 5.0.0.6
* 5.0.0.8 or later
* 6.0.0.0 or later
5.0.0.0 from 30 November 2012 (build 220750)
When your virtual deployment is the OVA file from 30 November 2012, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013.
Back to top |
f694f12faff48a6c41a642509b278b61_1 | 5.0.0.0 from 29 March 2013 (build 227007)
When your virtual deployment is the OVA file from 29 March 2013, you can install only the 5.0.0.0 fix pack and 5.0.0.8 or later fix packs from Fix Central. On Fix Central, the 5.0.0.5 and 5.0.0.6 fix packs are for the 5.0.0.0 OVA release from 30 November 2013.
Back to top
5.0.0.5
When your virtual deployment is 5.0.0.5, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013.
Back to top
5.0.0.6
When your virtual deployment is 5.0.0.6, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013.
Back to top |
f694f12faff48a6c41a642509b278b61_2 | 5.0.0.8 or later
When your virtual deployment is 5.0.0.8 or later, do not install any fix pack from Fix Cental that is earlier than the 5.0.0.8 fix pack. The 5.0.0.8 fix pack has critical fixes. For more information, see Critical Updates [http://www-01.ibm.com/support/docview.wss?uid=swg21390112#part2].
Note: You must install the 5.0.0.8 or later fix pack to upgrade to 6.0.0.0 or later. The 5.0.0.8 fix pack contains a required fix to allow the larger sized firmware image to fit.
Back to top
6.0.0.0 or later
When your virtual deployment is the 6.0.0.0 OVA file or a firmware upgrade through a 6.0.0.0 or later fix pack, do not install any fix pack from Fix Cental that is earlier than the 5.0.0.8 fix pack. The 5.0.0.8 fix pack has critical fixes. For more information, see Critical Updates [http://www-01.ibm.com/support/docview.wss?uid=swg21390112#part2].
Back to top |
f694f12faff48a6c41a642509b278b61_3 | Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower Service Gateway XG45 Virtual Edition VMware ESXi, VMware ESX 5.0.0, 6.0.0 Edition Independent |
272ef1ad869cac95fa47180c92fa6036_0 | IBM Datacap 9.0.1 FP1 - Readme doc - United States PRODUCT README
ABSTRACT
IBM Datacap 9.0.1 FP1 - Readme doc
CONTENT
About IBM Datacap 9.0.1 Feature Pack 1
Review this document for installation instructions and other important information before you install IBM® Datacap 9.0.1 Feature Pack 1, which cumulatively contains all feature pack updates since IBM Datacap Version 9.0.1 was released.
Upgrading to IBM Datacap 9.0.1 Feature Pack 1
From v9.0.1: use the Patch Installer from Fix Central
Installation Steps
Prerequisite:
· 1) Microsoft .NET Framework 4.6.1
· Run: NDP461-KB3102436-x86-x64-AllOS-ENU.exe
· 2) Microsoft Visual C++ Redistributable Packages for Visual Studio 2013
· Run: vcredist_x86.exe
Install:
· 3) IBM Datacap 9.0.1.1
· Run: Update.exe
From v9.0.0.0, 9.0.0.1, 9.0.0.2 & 9.0.0.3: use the Full Installer from Passport Advantage
Installation Steps
Prerequisite:
· 1) Microsoft .NET Framework 4.6.1 |
272ef1ad869cac95fa47180c92fa6036_1 | · Run: NDP461-KB3102436-x86-x64-AllOS-ENU.exe
· 2) Microsoft Visual C++ Redistributable Packages for Visual Studio 2013
· Run: vcredist_x86.exe
Install:
· 3) IBM Datacap 9.0.1.1
· Run: Setup.exe
Important
Updates are required only on Servers and thick client computers. No update is required for "thin client" computers. You must upgrade all thick clients and servers to the same IBM Datacap version and feature pack. Different versions of IBM Datacap are not compatible; therefore, you cannot connect an IBM Datacap client with a server that has a different IBM Datacap server version or feature pack installed. Operating Datacap Client or Datacap Web with an incompatible version of Datacap Server, or allowing different versions to access one database, can result in loss of data.
Once installed, this feature pack cannot be uninstalled. However, you can use "Uninstall or change a program" in Control Panel to uninstall the entire Datacap product. |
272ef1ad869cac95fa47180c92fa6036_2 | The language you selected when installing Datacap 9.0.1 determined the language displayed in the InstallShield panels at that time, and also controls the language in which the InstallShield panels for this feature pack are displayed.
Alerts!
1) When running an update, the global ruleset DLLs are updated but the copies in each application are not updated.
As a result, new features and fixes are not applied to applications and customers might experience defects that have been fixed.
The global ruleset DLLs are in the Datacap\RRS folder. The application copies are in the application DCO rules folder.
Customers must manually update the ruleset DLLs in each application where they are installed.
2) When running an update, the master task configuration files are updated (Datacap\ProgramSet) but the setting in applications are not updated (in application DCO folder). |
272ef1ad869cac95fa47180c92fa6036_3 | As a result, new features and fixes are not applied to applications and customers might experience problems that have been fixed.
The master task configuration is located in Datacap\ProgramSet. The application settings are in the application DCO folder.
Customers must manually update the task setting in each application where they are installed.
System requirements
Select the following link to see the hardware and software requirements for IBM Datacap.
http://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html [http://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html]
Search for ‘Datacap’, then select "Datacap "
Check the box ‘Show feature packs’ and select 9.0.1 for Feature Pack 1*.
New features added to IBM Datacap 9.0.1 Feature Pack 1 |
272ef1ad869cac95fa47180c92fa6036_4 | For a list of new features that were added to Datacap 9.0.1 in Feature Pack 1, see:
Highlights of IBM Datacap 9.0.1 Feature Pack 1 [http://www.ibm.com/support/knowledgecenter/SSZRWV_9.0.1/com.ibm.datacaptoc.doc/dc_highlights_9011.htm].
http://www.ibm.com/support/knowledgecenter/SSZRWV_9.0.1/com.ibm.datacaptoc.doc/dc_highlights_9011.htm [http://www.ibm.com/support/knowledgecenter/SSZRWV_9.0.1/com.ibm.datacaptoc.doc/dc_highlights_9011.htm]
New Qualifications
IBM Datacap 9.0.1 Feature Pack 1 is qualified for use with:
· Microsoft Windows 10 (except for TMWeb Scanning with Twain drivers;
See “Known Limitations” below for details)
· Oracle 12c (12.1.0.2.0)
· IBM Content Navigator 2.0.3 FP7
Issues fixed in IBM Datacap 9.0.1 Feature Pack 1 |
272ef1ad869cac95fa47180c92fa6036_5 | APAR Number Summary IO23893 Clicking on QA link in tmweb - Administrator fails with error "column named name already belongs to this datatable" if using admin database on SQL server IO24025 Can not import file which name contains '0x905C' such as "保険申告Updated.tif" IO24067 When customer use https + non-activeX to upload, some images will be corrupted frequently IO24082 Lineitem does not show up in Datacap Desktop Verify panel IO24102 Enhance IMail actions to use standard naming convention for ID's of pages created. IO24104 Using LLLDAP certain users are not able to login even when they are in the same group. LDAP is across multiple domains. IO24138 Couldn't create DC_P8 FileNet object error; action FNP8_SetURL () on 9.0 FP 3 and 9.0.1 IO24140 aindex.aspx does not update DATAFILE variable when a page is moved in batch view IO24141 DCDesktop Exception when performing a lookup query against an Oracle database IO24144 Batch aborts during ExcelWorkbookToImage with specific XLSX file IO24168 |
272ef1ad869cac95fa47180c92fa6036_6 | Page data is not generated when the page type is changed through batch structure in verify client of Datacap Navigator IO24169 when task has "-" and then change the batch status from hold to pending in edit job dialog, it will fail. IO24181 Unable to edit and enter values in multiple line edit box in tmweb Verifine panel IO24185 OCR_SR.RotateImageOCR_S () no longer compresses the TIFF image since applying 9.0 FP#2 was deployed IO24186 Thumbnail view of images is not activated in DcDesktop app until an image in batch tree view is clicked on IO24196 Setting a value to a custom column by main profile rule does not work. IO24199 Verify shortcut fails to show the batch list when the job name contains '( )' IO24205 System.OutOfMemory error returned by Datacap.Libraries.Convert.Outlook->OutlookMessageToImageAndAttachment () IO24213 Start bach panel non-overrideable validation not handled gracefully the second time around; Dc Desktop crashes IO24215 FNP8_CreateFolder () does not support / |
272ef1ad869cac95fa47180c92fa6036_7 | handle error in Italian IO24226 Page data failed to be shown in field details panel after running validation with some empty C nodes IO24227 CCO was not reloaded after running the rule so the re-OCR rule cannot take effect until relaunching the batch. IO24232 Main_Page no longer synch's up with custom data panel after switching from main_page to trailing page to main_page IO24249 Imprint.RedactParameters () converting color images to bitonal IO24249 Imprint.RedactByRegEx () only runs at Field level not at Page level but action help is slightly misleading IO24259 DcDesktop - certain columns in Job Monitor ONLY sort by Queue ID column IO24260 DSTUDIO: selecting ruleset "import files - all : Scan", returns message "The Document Hierarchy refers to some nonexistent Rules.". IO24282 MatchBarcodeBP throws an error in the rrs.log when processing non-barcode type pages. IO24289 tmweb fails to create setup file for a task if the app name begins with "AP" IO24381 SetNamePattern () with |
272ef1ad869cac95fa47180c92fa6036_8 | Convert.Unzip () is unable to resolve the naming pattern of the extracted image IO24384 Format and formatDescription are not supported in EDS IO24386 when the auto launch next batch is enabled, the page of the next verify page is not loaded. IO24387 Rescan status cannot be persisted after submitting if it is the only page in the batch IO24388 Split should not enabled on the page which is the only one in its parent document. IO24418 Images id are not numbered sequentially after fault with scanner occurs IO24427 Clicking on "Build Doc" button on custom panel generates exception error in DcDesktop App IO24439 Convert.ExcelWorkbookToImage () distorts the extracted tiff preventing GetBarcodeBP () from reading the barcode from the tiff image IO24447 rescanned page lost "ScanSrcPath" variable IO24461 Cannot paste value to a field if disable readonly on batch tree IO24470 After a job which jumped several tasks is edited via 'Edit Job' button, it could not be shown in Job Monitor IO24473 Batch |
272ef1ad869cac95fa47180c92fa6036_9 | is still in hold status even submitting it if session ever timeout. IO24475 Some Datacap css styles override ICN original ones, so impact ICN and other plugins. IO24477 image viewer error message does not conforming within image viewer. IO24486 Daeja ViewOne functionality of virtual as compared to Professional with DataCap |
272ef1ad869cac95fa47180c92fa6036_10 | Known limitations in IBM Datacap 9.0.1 Feature Pack 1 |
272ef1ad869cac95fa47180c92fa6036_11 | Read this information to learn about known limitations in IBM Datacap 9.0.1 Feature Pack 1.
Component Summary TMWeb Scan Windows 10 supported with IBM Datacap 9.0.1 FP1 with the following known limitations:
1. TMweb's "IE Test" page may result in a dialog box titled “Accusoft Twain Pro7 common 9.0.013” with the message "picdll Load Library failed.”
2. When trying to perform a Web scan with a Physical Scanner connected (via twain drivers) , ie using Web Vscan configured with scancl.aspx, the message "picdll Load Library failed" may be displayed.
If any of these messages appear, TMWeb scanning will not be possible. Medical Claims When in MClaims Prof Red/Black FixupScan, clicking "Next LC" button will advance to the next page and display the data for it (Type and Status), but will keep the previous page selected as well, and changes to Status (from "Invalid Claim Type" to "New Claim") will not be saved. |
272ef1ad869cac95fa47180c92fa6036_12 | Suggested workaround:
After clicking "Next LC" button, which will show previous page and current page selected in the Batch View display, then click the current page node in the Batch View display to properly select only the current page. After this one can continue to change the page Status and click "Next LC" button and repeat workaround for the next page. [/support/docview.wss?uid=swg27047895&aid=1] [/support/docview.wss?uid=swg27047895&aid=1] |
fb108e821cae435c7dd5fcd877064aaa_0 | IBM Configuring file content extraction tools for IBM Connections Search - United States stellent file content conversion extraction TECHNOTE (TROUBLESHOOTING)
PROBLEM
IBM Connections uses the Stellent (Oracle Outside In Technology) Export utility to extract text from documents of various types. The extracted text is added to the Search index allowing users to find documents based on the content.
When the Stellent utility is not configured correctly, file content will not be extracted or indexed. Therefore, search results within IBM Connections will not contain any matches on file content. For any content extraction issues, follow the steps in this tech note.
RESOLVING THE PROBLEM
1 Stellent installation
Ensure that the following IBM Connections post-installation task has been carried out:
http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Copying_Search_conversion_tools_to_local_nodes_ic40 [http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Copying_Search_conversion_tools_to_local_nodes_ic40] |
fb108e821cae435c7dd5fcd877064aaa_1 | 2 Running the exporter in isolation from IBM Connections
To verify that the exporter is working correctly, you can run it on the command line in isolation from IBM Connections. To run the exporter executable on the command line, execute the following as the user that the Search WebSphere Application Server is running under:
1. Change directory to the Stellent binary location. For example:
$ cd /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport
2. Run the exporter command.
The exporter command has the following syntax:
exporter inputpath=<path_to_input_file>
outputpath=<path_to_extracted_text_output>
outputid=FI_SEARCHTEXT
For example,
$ ./exporter inputpath=/root/translation.pdf \ outputpath=/root/testStellent.txt outputid=FI_SEARCHTEXT
If the text extraction worked successfully, you will see the following output:
Export complete
However, if you see a message like the one below, continue to step 3: |
fb108e821cae435c7dd5fcd877064aaa_2 | ./exporter: error while loading shared libraries: libsc_ex.so: cannot open shared object file: No such file or directory
3 Operating System Environment Variables
Ensure that the operating system environment variables LD_LIBRARY_PATH and PATH are set correctly in Section 1. Both variables should contain the Stellent installation directory. To get the current values of the environment variables, run the following commands as the user that the Search WebSphere Application Server is running under:
$ echo $LD_LIBRARY_PATH
$ echo $PATH
To verify that the Stellent exporter executable can be found through the PATH environment variable, run the following command:
$ which exporter
The output of this command should contain the full path to the exporter executable. For example:
/opt/IBM/Connections/data/local/search/stellent/dcs/oiexport/exporter
4 WebSphere Environment |
fb108e821cae435c7dd5fcd877064aaa_3 | Using the WebSphere Application Server administration console, ensure that the WebSphere environment variable FILE_CONTENT_CONVERSION points to the exporter executable.
For example: /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport/exporter
5 File Permissions
Ensure that the user that the Search WebSphere Application Server is running under has sufficient privileges. They should have read/write/execute permissions on the exporter executable and read/write permissions on the other files in the Stellent installation directory.
6 Library compatibility
Verify that the libraries deployed with Stellent are compatible with your platform.
For example, on a 64 bit Linux system:
$ uname -a
Linux host1 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux
$ cd /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport
$ file libsc_ex.so
libsc_ex.so: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV), not stripped |
fb108e821cae435c7dd5fcd877064aaa_4 | (Note that your Stellent installation may contain 32 bit libraries though you are running on 64 bit platform. This is not an issue, provided that the 32 bit compatible libraries are on the LD_LIBRARY_PATH or can be found on the shared library search path).
7 Shared library dependencies
The Stellent exporter executable has a number of dependencies on both the shared libraries packaged with Stellent and on shared libraries installed on your system. To verify that all the required shared libraries can be found, use the 'ldd' command on the exporter executable as follows:
$ ldd -v exporter
Check the output of this command for any shared libraries marked as '=> not found'.
Stellent shared library not found
If a Stellent shared library can't be found, then check that the setting of your LD_LIBRARY_PATH operating system environment variable contains the Stellent installation directory.
System shared library not found |
fb108e821cae435c7dd5fcd877064aaa_5 | If a system shared library can't be found, then you are missing a prerequisite library.
NOTE: It is still possible to pick up libraries from locations other than those included in the LD_LIBRARY_PATH operating system environment variable, as long as they can be found elsewhere on the system's default search path.
In addition to libc.so.6, Stellent is dependent upon the following libraries:
libstdc++.so.5
libgcc_s.so.1
For Red Hat Enterprise Linux 6.0 and later, it is possible that you are missing the package compat-libstdc++-33 . This package contains libstdc++.so.5.
*
* |
f497518728a575e3ac8fed55b32d61d0_0 | IBM Action required for IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 for security vulnerabilities in Red Hat Linux - United States IIB WMB FLASH (ALERT)
ABSTRACT
IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux
CONTENT
IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to
CVE-2017-12691 CVE-2017-12692 CVE-2017-12693 CVE-2017-12875 CVE-2017-12876 CVE-2017-12877 CVE-2017-13131 CVE-2017-13132 CVE-2017-13133 CVE-2017-13134 CVE-2017-13139 CVE-2017-13140 CVE-2017-13141 CVE-2017-13142 CVE-2017-13143 CVE-2017-13144 CVE-2017-13145 CVE-2017-13146 CVE-2017-13658 CVE-2017-13758 CVE-2017-13768 CVE-2017-13769 CVE-2017-14060 CVE-2017-14137 CVE-2017-14138 and CVE-2017-14139 |
f497518728a575e3ac8fed55b32d61d0_1 | IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2
Remediation:
IBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.
Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0 |
48f9758f5a6906157818db3b21624708_0 | IBM Software maintenance strategy for CICS TS and its embedded components - United States Libery Java ; 5655S9700 R660 660 R600 600 HCI6600 R670 670 R700 700 HCI6700 5655-S97 5655S97 ; 5655Y0400 R680 680 R800 800 HCI6800 R690 690 R900 900 HCI6900 R700 700 R000 000 HCI7000 R710 710 R100 100 HCI7100 5655Y0401 5655-Y04 5655Y04 KIXINFO PRODUCT DOCUMENTATION
ABSTRACT
CICS TS support is delivering the information in this document to help customers plan for updates to CICS Transaction Server for z/OS (CICS TS) and related software components such as WebSphere Liberty and CICS Explorer. Installing APAR fixes (PTFs) using Recommended Service Upgrades (RSUs) as early as possible can help avoid problems that could result in a service call, and as long as you test appropriately, help reduce risks to your business.
CONTENT |
48f9758f5a6906157818db3b21624708_1 | [/support/docview.wss?uid=swg27048530&aid=1]Embedded components in CICS TS [http://www-01.ibm.com/support/docview.wss?uid=swg27012749#delivering]
[/support/docview.wss?uid=swg27048530&aid=2]Update recommendations
[/support/docview.wss?uid=swg27048530&aid=3]Related information
Components in CICS TS
CICS TS provides the following embedded runtime components: |
48f9758f5a6906157818db3b21624708_2 | * Equinox
Equinox is an implementation of the OSGi core framework specification and is provided for both OSGi JVM servers and for Liberty JVM servers. Service for these components is provided when and if required.
* Apache Axis2™
Axis2 is an open source web services engine from the Apache Software Foundation and is used within CICS to provide the web service Java™ engine for the Axis2 JVM server environment. Service for this component is provided when and if required.
* WebSphere Application Server Liberty Profile
Liberty fix packs are provided on a regular basis through the CICS TS APAR delivery process and provide an update mechanism to keep the embedded CICS Liberty runtime synchronized with the fix packs provided by WebSphere Application Server. Keeping current helps you resolve problems faster for 2 reasons: * Liberty APAR fixes (known as ifixes) can only be delivered on the latest Liberty fix pack that has been supplied by the CICS APAR process. |
48f9758f5a6906157818db3b21624708_3 | * CICS APAR fixes can require other fixes such as WebSphere Liberty fix packs. |
48f9758f5a6906157818db3b21624708_4 | CICS Explorer and z/OS Explorer
The CICS Software Development Kit (SDK) for Java includes components from CICS for developing CICS Java applications. The CICS SDK for Servlet and JSP support includes Java Enterprise Edition (Java EE) and Liberty API libraries, and automatically installs required components such as WebSphere Developer Toolkit (WDT)." Service for these components is provided through the CICS Explorer fix pack process when and if required.
[/support/docview.wss?uid=swg27048530&aid=4] Back to Top
Update recommendations |
48f9758f5a6906157818db3b21624708_5 | Recommended Service Upgrade (RSU)
IBM recommends that you install all RSU [http://www-03.ibm.com/systems/z/os/zos/support/servicetest/] PTFs as preventive software maintenance for CICS TS. An RSU is a predefined collection of PTFs identified with a SOURCEID of RSUyymm, where yy indicates the last 2 digits of the year and mm indicates the month. [http://www-03.ibm.com/servers/eserver/zseries/zos/servicetst/]You can order an RSU [http://www-1.ibm.com/servers/eserver/zseries/zos/servicetst/]from ShopzSeries [https://www14.software.ibm.com/webapp/ShopzSeries/ShopzSeries.jsp].
Equinox and Apache Axis2
There is unlikely to be much maintenance for Equinox and Axis2. Service for these components is provided when and if required, meaning it will be on a case by case basis and in most cases this will be to resolve service requests. |
48f9758f5a6906157818db3b21624708_6 | WebSphere Application Server Liberty Profile
Refer to Updating Liberty profile for CICS TS and z/OS Connect EE to latest version [http://www.ibm.com/support/docview.wss?uid=swg21993579] for a list of APARs you will need to update CICS TS and z/OS Connect Enterprise Edition (EE) to the latest version of WebSphere Application Server Liberty profile.
CICS Explorer
IBM recommends that you upgrade to the latest release of CICS Explorer to obtain the most recent functionality and service. Old releases of CICS Explorer are not generally updated with new function, but new CICS Explorer releases are compatible with all earlier versions of CICS TS. Therefore, CICS Explorer V5.4 is compatible with CICS TS V4.1 through V5.4. For further details see Latest version of CICS Explorer and CICS Tools plug-ins for CICS Explorer [http://www.ibm.com/support/docview.wss?uid=swg21404312].
[/support/docview.wss?uid=swg27048530&aid=5] Back to Top |
48f9758f5a6906157818db3b21624708_7 | Related information:
* Update Strategy for WebSphere Application Server [http://www.ibm.com/support/docview.wss?uid=swg27036014]
* Fix list for IBM WebSphere Application Server Liberty [http://www.ibm.com/support/docview.wss?uid=swg27043863]
* CICS TS embedded components [http://www.ibm.com/support/knowledgecenter/SSGMCP_5.3.0/com.ibm.cics.ts.standards.doc/topics/supportedComponents.html]
* Fixes by version for CICS products [http://www.ibm.com/support/docview.wss?uid=swg27008833]
[/support/docview.wss?uid=swg27048530&aid=6] Back to Top
PRODUCT ALIAS/SYNONYM
CICS/TS CICS TS CICS Transaction Server |
4ece24351ba7c19e785bf39e2cb233fa_0 | IBM Correct understanding of CSV version of PVU reports - United States TECHNOTE (FAQ)
QUESTION
What files are in the audit snapshot generated by IBM License Metric Tool or IBM BigFix Inventory version 9.x, and what is the correct interpretation of the values in the CSV report files?
CAUSE
The licensing reports in CSV format can be misinterpreted by some customers.
ANSWER
Audit snapshot is a record of PVU and RVU MAPC utilization in your enterprise over a period of time. It contains the following files: |
4ece24351ba7c19e785bf39e2cb233fa_1 | * audit_trail.csv – all user actions that influence the final results of the licensing reports, for example, software classification actions, uploads and imports of the PVU table, software catalog, and charge units as well as changes to the VM managers.
* data_conditions.txt – conditions that were used during the generation of the audit snapshot, including the reporting period and filters applied on the reports as well as general information about the time when the snapshot was generated, version of the PVU table and software catalog, status of the import, aggregation, and recalculation.
* part_numbers.csv - part numbers that are listed in the software catalog for all software products that are included in any of the CSV report files.
* pvu_full_capacity.csv - PVU full capacity license metric results
* pvu_sub_capacity.csv - PVU subcapacity license metric results
* rvu_full_capacity.csv - RVU full capacity license metric results |
4ece24351ba7c19e785bf39e2cb233fa_2 | * rvu_sub_capacity.csv - RVU subcapacity license metric results
* bundling_definitions.csv - list of IBM software regardless of its license type and utilization together with details of the computers on which the software is installed
* readme.txt - a link to this document (technote)
* checksums.txt, signature.rsa, and pub_key.pem - files used by IBM auditors to verify the authenticity and correctness of the audit snapshot. |
4ece24351ba7c19e785bf39e2cb233fa_3 | Why some product instances are not listed in the CSV reports?
CSV reports with information about PVU and RVU MAPC utilization (pvu_full_capacity.csv, pvu_sub_capacity.csv, rvu_full_capacity.csv, and rvu_sub_capacity.csv) list only software instances that were discovered during the license peak value time. If an instance was installed in your environment during the reporting period of the current audit snapshot but was not discovered during the license peak value time, the instance is not listed in the CSV reports.
Example:
Three instances of DB2 are installed. The reporting period is set to one month and DB2 license utilization is as follows:
· Instance 1 uses the maximum of 100 PVUs,
· Instance 2 uses the maximum of 300 PVUs,
· Instance 3 uses the maximum of 500 PVUs. |
4ece24351ba7c19e785bf39e2cb233fa_4 | The license peak value occurs when the sum of PVU values for all instances is the highest and equals 800 PVUs (300 PVUs for instance 2 + 500 PVUs for instance 3). The peak occurs during the period that is marked with a red square (it is the license peak value time). The peak usage for instance 1 is outside of the red square. It means that this instance was installed in the environment during the current reporting period but was not discovered during the license peak value time. This instance is not listed in the CSV report.
[/support/docview.wss?uid=swg21688543&aid=1] [/support/docview.wss?uid=swg21688543&aid=1]
Why some values from the CSV report do not relate back to what is displayed on the user interface? |
4ece24351ba7c19e785bf39e2cb233fa_5 | When all values from column M (Physical Server PVU Subcapacity) for a particular product are added, the obtained value is greater that the value that is displayed in the user interface. It happens due to the way that data is presented in CSV reports and on the user interface.
The All IBM Metrics and IBM PVU subcapacity reports are multilevel, and consist of the following levels:
1. First level: a list of all products
[/support/docview.wss?uid=swg21688543&aid=2] [/support/docview.wss?uid=swg21688543&aid=2]
2. Second level: when you click a product name, you go to information about the physical server on which the product is installed.
[/support/docview.wss?uid=swg21688543&aid=3] [/support/docview.wss?uid=swg21688543&aid=3]
3. Third level: when you click the server name, you go to a list of virtual machines that run on this server and have the product installed.
[/support/docview.wss?uid=swg21688543&aid=4] [/support/docview.wss?uid=swg21688543&aid=4] |
4ece24351ba7c19e785bf39e2cb233fa_6 | The audit snapshot is not multilevel. However, it has to present the same information that the report that is available in the user interface. Below is an excerpt from the audit snapshot that corresponds to the report that was presented on the screen shots above (some columns are hidden in the snapshot to simplify it).
[/support/docview.wss?uid=swg21688543&aid=5] [/support/docview.wss?uid=swg21688543&aid=5]
When values in column M are added, PVU consumption equals 480 PVUs. However, these values should not be added because they all refer to a single server (TLM_VM_423…) on which the four VMs run, not an individual VM that is listed in column P (Computer). |
4ece24351ba7c19e785bf39e2cb233fa_7 | The value in column M is repeated due to the way data needs to be presented in a CSV file. If you want to relate back the value from column M in the audit snapshot to the user interface report, it is the value that you can see in the column PVU Subcapacity Limit on the second level of the report. The value in column L relates back to the column CPU Core Subcapacity on the second level of the report.
[/support/docview.wss?uid=swg21688543&aid=6] [/support/docview.wss?uid=swg21688543&aid=6] |
4ece24351ba7c19e785bf39e2cb233fa_8 | PVU and RVU MAPC subcapacity license terms specify license consumption only on the physical server level. PVU and RVU MAPC values cannot be calculated and presented on the virtual machine or LPAR level, and such data is not provided by License Metric Tool or BigFix Inventory. For more information about virtualization capacity license counting rules that are used for PVU and RVU MAPC calculation, see:
http://www-01.ibm.com/software/passportadvantage/Counting_Software_licenses_using_specific_virtualization_technologies.html [http://www-01.ibm.com/software/passportadvantage/Counting_Software_licenses_using_specific_virtualization_technologies.html]
RELATED INFORMATION
Understanding CSV files with metric utilization [https://www.ibm.com/support/knowledgecenter/en/SS8JFY_9.2.0/com.ibm.lmt.doc/Inventory/softinv/c_understanding_csv.html]
Cross reference information Segment Product Component Platform Version Edition Security IBM BigFix Inventory |
1068647f851e10b0e7362b1566d90fcf_0 | IBM Java SDK Upgrade Policy for the IBM WebSphere Application Server - United States upgrade policy TECHNOTE (FAQ)
QUESTION
What is the Java™ SDK upgrade policy for the IBM® WebSphere® Application Server?
CAUSE
Updating to the latest compatible Java SDK could help you resolve problems more quickly.
ANSWER
The IBM WebSphere Application Server Java SDK can be upgraded to the latest service release for the same Java SDK version.
List of WebSphere Application Server fix packs and the corresponding Java SDK versions [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27005002]
Policy Summary by WebSphere Application Server release: |
1068647f851e10b0e7362b1566d90fcf_1 | WebSphere Application Server V8.0, V8.5, V8.5.5
Starting with V8.0 and applicable to all subsequent releases and fixpacks, there is one install package that contains updates for both WebSphere Application Server and Java SDK. Applying fixpacks of WebSphere Application Server also upgrades the SDK that is packaged and bundled within the fixpack. Additionally, separate Java SDK fixpacks are also available that contain just the SDK updates which can be applied to upgrade the SDK.
WebSphere Application Server V7.0
Any V7.0 fix pack can upgrade to the latest Java SDK 1.6.0 service release packaged for WebSphere Application Server.
WebSphere Application Server V6.1
Any V6.1 fix pack can upgrade to the latest Java SDK 1.5.0 service release packaged for WebSphere Application Server.
WebSphere Application Server V6.0
Any V6.0 fix pack can upgrade to the latest Java SDK 1.4.2 service release packaged for WebSphere Application Server. |
1068647f851e10b0e7362b1566d90fcf_2 | WebSphere Application Server V5.1
Any V5.1 fix pack can upgrade to the latest Java SDK 1.4.1 and any V5.1.1 can be upgraded to the latest Java SDK 1.4.2 service release packaged for WebSphere Application Server.
WebSphere Application Server V5.0
Any V5.0 fix pack can upgrade to the latest Java SDK 1.3.1 service release packaged for WebSphere Application Server.
Details of Java SDK Upgrade Policy
WebSphere Application Server leverages the Java SDK as a base component. This results in unique support issues, including:
* Matching Java SDK service releases to Application Server releases and fix packs
* Delivering updates and fixes associated with the Java SDK on any given Application Server release.
In an effort to resolve customer Java SDK situations as quickly as possible, WebSphere Application Server Support has done a quickest-path-to-resolution analysis, determining the most direct way to collect problem information. |
1068647f851e10b0e7362b1566d90fcf_3 | In some cases, problem resolution might include finding shortcuts to resolve symptoms. One shortcut is an immediate upgrade to a newer compatible Java SDK service release, before gathering detailed problem determination data.
There are multiple advantages to performing an immediate Java SDK upgrade as a quicker path to resolution over a full Problem Determination (PD) process:
1. There is a continuous stream of fixes going into the Java SDK. Many problems encountered by customers are resolved by these fixes.
2. When a new problem is encountered, applying the latest Java SDK is a quick way to determine if related fixes change the symptoms or correct the problem.
3. Many documented Java SDK fixes have common symptoms. Frequently, limited PD data does not isolate the problem to a single root cause.
These factors highlight the advantage of applying a newer Java SDK before working through a full PD cycle. |
1068647f851e10b0e7362b1566d90fcf_4 | Java SDK and WebSphere Application Server software are updated frequently. To avoid compatibility issues for customers, WebSphere Application Server Support maintains this Java SDK Upgrade Policy.
WebSphere Application Server Support details:
http://www.ibm.com/software/webservers/appserv/support.html [http://www.ibm.com/software/webservers/appserv/support.html]
Identifying compatibility limitations between WebSphere Application Server releases and Java SDK service releases that have not been tested together reduces risk.
Important: Using a Java SDK not specifically packaged with WebSphere Application Server and supplied by IBM, or in violation of the Java SDK Upgrade Policy, is not supported by IBM WebSphere Application Server Support for Java SDK problems. RELATED INFORMATION
Verify Java SDK version shipped with WebSphere fix pack [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27005002] |
1068647f851e10b0e7362b1566d90fcf_5 | Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK |
19b31aedf7b058d0233075bfaaf3def8_0 | IBM Message RT7507E: Unable to initialize Repository: Default occurs in SystemOut.log after successful database transfer from Derby to DB2 - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM
Message RT7507E: Unable to initialize Repository: Default occurs in SystemOut.log after successful database transfer from Derby to DB2
SYMPTOM
You may see this stacktrace in SystemOut.log after successfully completing the database transfer from Derby to DB2 |
19b31aedf7b058d0233075bfaaf3def8_1 | [6/25/12 16:10:19:213 CEST] 0000002e InitServlet E INI8504E:One or more initialization step failed. Please check the server log for details.
com.ibm.icm.jcr.RepositoryExistsException: RT7507E: Unable to initialize Repository: Default.
at com.ibm.icm.jcr.RepositoryFactory.init(RepositoryFactory.java:218)
at com.ibm.icm.jcr.RepositoryFactory.getRepository(RepositoryFactory.java:479)
at com.ibm.icm.jcr.servlet.InitServlet.init(InitServlet.java:56)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:336)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:168)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.loadOnStartupCheck(ServletWrapper.java:1341)
at com.ibm.ws.webcontainer.webapp.WebApp.doLoadOnStartupActions(WebApp.java:588)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:559)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:421) |
19b31aedf7b058d0233075bfaaf3def8_2 | at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:88)
at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:169)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:749)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:634)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:422)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:714)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1160)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1369)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:638)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:967)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:766) |
19b31aedf7b058d0233075bfaaf3def8_3 | at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2153)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:445)
at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:388)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$500(CompositionUnitMgrImpl.java:116)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:994)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:349)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1659) |
19b31aedf7b058d0233075bfaaf3def8_4 | CAUSE
Root cause was having another copy of icm.properties in .\wp_profile\PortalServer\jcr\lib\com\ibm\icm, in this case by making a backup copy in the same directory with name icm-copy.properties
RESOLVING THE PROBLEM
Remove the copy so that the only file in .\wp_profile\PortalServer\jcr\lib\com\ibm\icm is icm.properties
RELATED INFORMATION
Fiddler [http://www.fiddlertool.com]
Plug-in MustGather [http://www-01.ibm.com/support/docview.wss?uid=swg21174894]
WebSphere Portal tracing [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/WebSphere_Portal_runtime_logs_wp7]
IHS Rewrite rules (mod_rewrite Apache module) [http://publib.boulder.ibm.com/infocenter/wasinfo/fep/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Frihs_apachemods.html] |
7bc2ea267e36fc6e16b9abda3b44145c_0 | IBM Security Bulletin: Multiple Vulnerabilities identified in IBM® Java SDK affect WebSphere Service Registry and Repository and WebSphere Service Registry and Repository Studio - United States SECURITY BULLETIN
SUMMARY
Multiple vulnerabilities in IBM® SDK Java™ Technology Edition, Version 6 used by WebSphere Service Registry and Repository and WebSphere Service Registry and Repository Studio. These issues were disclosed as part of the IBM Java SDK updates in January 2018.
These issues are also addressed by WebSphere Application Server Network Deployment shipped with WebSphere Service Registry and Repository. |
7bc2ea267e36fc6e16b9abda3b44145c_1 | VULNERABILITY DETAILS
CVEID:CVE-2018-2633 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2633]
DESCRIPTION:An unspecified vulnerability related to the Java SE JNDI component could allow an unauthenticated attacker to take control of the system.
CVSS Base Score: 8.3
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/137885 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137885]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H)
CVEID:CVE-2018-2603 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2603]
DESCRIPTION:An unspecified vulnerability related to the Java SE Libraries component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.
CVSS Base Score: 5.3 |
7bc2ea267e36fc6e16b9abda3b44145c_2 | CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/137855 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137855]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) |
7bc2ea267e36fc6e16b9abda3b44145c_3 | CVEID:CVE-2018-2579 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2579]
DESCRIPTION:An unspecified vulnerability related to the Java SE Libraries component could allow an unauthenticated attacker to obtain sensitive information resulting in a low confidentiality impact using unknown attack vectors.
CVSS Base Score: 3.7
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/137833 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137833]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) |
7bc2ea267e36fc6e16b9abda3b44145c_4 | CVEID:CVE-2018-2602 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2602]
DESCRIPTION:An unspecified vulnerability related to the Java SE I18n component could allow an unauthenticated attacker to cause low confidentiality impact, low integrity impact, and low availability impact.
CVSS Base Score: 4.5
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/137854 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137854]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L)
AFFECTED PRODUCTS AND VERSIONS
WebSphere Service Registry and Repository V8.5 and V8.0 and WebSphere Service Registry and Repository Studio V8.5 are affected. |
7bc2ea267e36fc6e16b9abda3b44145c_5 | REMEDIATION/FIXES
For all releases of WebSphere Service Registry and Repository Studio, upgrade to WebSphere Service Registry and Repository Studio V8.5.6.1_IJ04332 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FWebSphere+Service+Registry+and+Repository&fixids=8.5.6.1-WS-WSRR-Studio-MultiOS-IFIJ04332]
For WebSphere Service Registry and Repository the issues are addressed by WebSphere Application Server.
Principal Product and Version(s) Affected Supporting Product and Version WebSphere Service Registry and Repository V8.5 WebSphere Application Server V8.5.5 WebSphere Service Registry and Repository V8.0 WebSphere Application Server V8.0
Refer to the following security bulletin for vulnerability details and information about fixes addressed by WebSphere Application Server shipped with WebSphere Service Registry and Repository: |
7bc2ea267e36fc6e16b9abda3b44145c_6 | Security Bulletin: Multiple Vulnerabilities in IBM® Java SDK affects WebSphere Application Server January 2018 CPU [http://www.ibm.com/support/docview.wss?uid=swg22013818] 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
14 March 2018: Original version published |
7bc2ea267e36fc6e16b9abda3b44145c_7 | *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. |
539bd36c21beb94310df9f4f7969211a_0 | IBM Error # 2070. The license server is down. Specific symptom number: 3 - United States TECHNOTE (FAQ)
QUESTION
We have network installations of IBM SPSS Statistics/Modeler. When the application is launched, the following errors are reported:
"The current license does not permit this job to continue."
followed by...
"Error # 2070
The license server is down. Please check to see that the license server is running or ask your local SPSS coordinator to check the license server.
This command is not executed.
Specific symptom number: 3."
The Safenet Sentinel License Manager has been licensed and confirmed to be running.
What is the problem?
CAUSE
The above error can be caused by invalid values entered during the licensing phase of installing SPSS Statistics/Modeler or the client machine cannot reach the Sentinel License Manager host using the machine Hostname.
ANSWER
Please do the following to verify: |
539bd36c21beb94310df9f4f7969211a_1 | 1. Navigate to the IBM SPSS Statistics/Modeler directory and open "spssprod.inf", using any text editor.
- By default, SPSS Statistics would store this file in: C:\Program Files\IBM\SPSS\Statistics\xx\
- By default, SPSS Modeler would store this file in: C:\Program Files\IBM\SPSS\Modeler\xx.x\bin\
2. Verify the "DaemonHost" value matches the Hostname or IP Address of the machine where the Safenet Sentinel License Manager is installed.
- E.g. DaemonHost=MyLicenseServer or DaemonHost=127.0.0.1
If the DaemonHost value specifies redundant license servers, please do the following if you are using SPSS Statistics 22 (or earlier) or SPSS Modeler 16.0 (or earlier):
a). Remove all license servers from the "DaemonHost" line and save the file. |
539bd36c21beb94310df9f4f7969211a_2 | b). Create a system environment variable, called LSHOST, on each SPSS client with your redundant license servers as its value. Separate each redundant license server with a colon, e.g.
==========================
Variable: LSHOST
Value: server1:server2:server3
==========================
If the "DaemonHost" value is accurate and you are using a Hostname value, you have a name resolution problem. Error # 2070, Symptom number 3 typically means the SPSS client cannot connect to the name resolution database or the name resolution database does not contain a record for the machine where the SPSS Sentinel License Manager resides. To verify, please do the following:
1. Run lswhere.exe (which is located in the SPSS directory, see above) from the problematic SPSS Client machine and take note of the displayed output. The following is an example of the output:
==========================
Sentinel LM 8.x.x Search Tool For License Servers
Copyright (C) 20xx Rainbow Technologies, Inc. |
539bd36c21beb94310df9f4f7969211a_3 | Server Address : xxx.xxx.xxx.xxx
Server Name : Machine_A
==========================
If the Safenet Sentinel License Manager machine is not listed or you encounter the error, "Error[17]: Probably no servers are running on this subnet.", please add the following system environment variable to the IBM SPSS Statistics/Modeler client and run lswhere.exe again:
==========================
Variable: LSHOST
Value: Name or IP address of the License Manager machine
==========================
For information about defining environment variables, see the Network License Administrator's Guide. If using the LSHOST environment variable does not render the Safenet Sentinel License Manager machine, try using LSFORCEHOST instead.
2. When you see the Safenet Sentinel License Manager machine name and corresponding IP address listed in the lswhere output, ping the displayed Server Name from a command line, e.g.
==========================
ping Machine_A
========================== |
539bd36c21beb94310df9f4f7969211a_4 | An example of the resulting output is as follows:
==========================
Unknown host Machine_A
==========================
If the ping command is unable to resolve the Server Name, you have a name resolution problem and must address it (with help from your IT Administrator/Help Desk team) before IBM SPSS Statistics/Modeler can acquire a license from the Sentinel License Manager.
RELATED INFORMATION
Need more help? Our Modeler forum is Live! [https://developer.ibm.com/answers/topics/modeler/?smartspace=predictive-analytics]
Need more help? Our Licensing forum is Live! [https://developer.ibm.com/answers/topics/spsslicensing.html]
A simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21641554] |
539bd36c21beb94310df9f4f7969211a_5 | Cross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Statistics Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Platform Independent Not Applicable Business Analytics SPSS Amos Windows Not Applicable Business Analytics SPSS SamplePower Platform Independent Not Applicable
HISTORICAL NUMBER
51910 |
3e699506b863fbdc317226b692c4c933_0 | IBM Product upgrade installed a second instance of the DE, causing upgrade failure. - United States DEL2INST; Tivoli; Deployment; Engine; FQDN; Duplicate; acsi TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
The Deployment Engine should only have one instance installed on a server with IBM products installed. In this case, a second DE was installed, which caused the failure of the Product upgrade.
Error: Wrong Deployment Engine.
SYMPTOM
Product install failed. You will get a message similar to this:
You are updating an instance of <Product name> that was installed using
the Tivoli Deployment Engine (DE) located at "/home/nc_admin/.acsi_<Fully Qualified hostname>".
However you are now using the DE located at "/home/nc_admin/.acsi_<hostname>".
When the DE is installed as non-root ( in this case nc_admin ), it will install the DE in the user home directory, in this case /home/nc_admin, and use the FQDN in the name: /home/nc_admin/.acsi_<Fully Qualified hostname> |
3e699506b863fbdc317226b692c4c933_1 | CAUSE
Because the two Product installs used different versions of JVM, the underlying Java is using "hostname" for one version of JVM, and "Fully Qualified hostname" for the other. The DE normally uses the FQDN appended to the "acsi_" string to create the DE directory:
For example, if the Product is being installed as user "nc_admin" and the entry in /etc/hosts is this:
x.xx.xxx.xx server_name.corporation.net server_name
The hostname is "server_name"
Fully Qualified hostname (FQDN) is "server_name.corporation.net"
ENVIRONMENT
Upgrading existing product that uses the Deployment Engine on a UNIX server
DIAGNOSING THE PROBLEM
Output similar to this when the Product install fails:
the Tivoli Deployment Engine (DE) located at "/home/nc_admin/.acsi_<Fully qualified hostname>".
However you are now using the DE located at "<User_home>/nc_admin/.acsi_<hostname>"
RESOLVING THE PROBLEM
There are two options to fix this problem. |
3e699506b863fbdc317226b692c4c933_2 | 1) Make sure the current upgrade is using the same version of JVM as the original install.
2) Removing the newly created DE, which shouldn't have been created, then creating a link to the existing DE is the best work around in this case. The Product upgrade will see the link and add the information to the valid DE install.
*IMPORTANT NOTE: The Product install failure message will tell you what instance of the DE is valid, please refer to the error message in the "Symptom" section above.
At this point there will be the following in the DE_HOME directory:
.acsi_<FQDN> ( Valid DE installation )
.acsi_<userid> ( link to .acsi_<FQDN> )
.acsi_<hostname> ( Invalid DE directory created by the failed Product upgrade )
This can be confirmed by referring to the Product install error.
Removing the invalid DE and creating softlink:
- Backup the original DE installation directory: <DE_HOME>/.acsi_<FQDN> |
3e699506b863fbdc317226b692c4c933_3 | - Move the new invalid DE directory to a backup directory: <DE_HOME>/.acsi_<hostname>
- Create a soft link to the "good" DE install
cd <DE_HOME>
ln -s <DE_HOME>/.acsi_<FQDN> .acsi_<hostname>
- Confirm the link was created successfully, it should look like this:
> ls -lart
lrwxrwxrwx 1 nc_admin ncoadmin <date> .acsi_<hostname> -> <DE_HOME>/.acsi_<FQDN>
3) Retry the product install. You will need to confirm there is no required cleanup before retrying the Product upgrade. |
30f5bdd78566e53f7695ba7e84fce64b_0 | IBM Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Image Construction and Composition Tool (CVE-2015-0410 and CVE-2014-6593) - United States SECURITY BULLETIN
SUMMARY
There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition Version 6 and 7 that are used by IBM Image Construction and Composition Tool. These issues were disclosed as part of the IBM Java SDK updates in January 2015.
VULNERABILITY DETAILS
CVEID: CVE-2015-0410 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0410]
DESCRIPTION: An unspecified vulnerability related to the Security component could allow a remote attacker to cause a denial of service.
CVSS Base Score: 5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100151 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100151] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P) |
30f5bdd78566e53f7695ba7e84fce64b_1 | CVEID: CVE-2014-6593 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6593]
DESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.
CVSS Base Score: 4
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100153 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100153] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N)
AFFECTED PRODUCTS AND VERSIONS
IBM Image Construction and Composition Tool v2.2.1.3
IBM Image Construction and Composition Tool v2.3.1.0
IBM Image Construction and Composition Tool v2.3.2.0
REMEDIATION/FIXES
The solution is to apply the following IBM Image Construction and Composition Tool version fixes.
Upgrade the IBM Image Construction and Composition Tool to the following fix levels: |
30f5bdd78566e53f7695ba7e84fce64b_2 | * For IBM Image Construction and Composition Tool v2.2.1.3 * IBM Image Construction and Composition Tool v2.2.1.3 Build 28
http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=1.1.0.5&platform=All&function=fixId&fixids=ICCT_efix_Repository_2.2.1.3-28&includeSupersedes=0 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=1.1.0.5&platform=All&function=fixId&fixids=ICCT_efix_Repository_2.2.1.3-28&includeSupersedes=0]
For IBM Image Construction and Composition Tool v2.3.1.0 * IBM Image Construction and Composition Tool v2.3.1.0 Build 38 |
30f5bdd78566e53f7695ba7e84fce64b_3 | http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=2.0.0.1&platform=All&function=fixId&fixids=ICCT_efix_Repository_2.3.1.0-38&includeSupersedes=0 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=2.0.0.1&platform=All&function=fixId&fixids=ICCT_efix_Repository_2.3.1.0-38&includeSupersedes=0]
For IBM Image Construction and Composition Tool v2.3.2.0 * IBM Image Construction and Composition Tool v2.3.2.0 Build 12 |
30f5bdd78566e53f7695ba7e84fce64b_4 | http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=2.1.0.0&platform=All&function=fixId&fixids=ICCT_efix_Repository_2.3.2.0-12&includeSupersedes=0 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=2.1.0.0&platform=All&function=fixId&fixids=ICCT_efix_Repository_2.3.2.0-12&includeSupersedes=0] |
30f5bdd78566e53f7695ba7e84fce64b_5 | 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 v2 Guide [http://www.first.org/cvss/v2/guide]
On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]
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
None
CHANGE HISTORY
21 July 2015: Original Version Published
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. |
30f5bdd78566e53f7695ba7e84fce64b_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. |
00b2b30790d2c9b98aef43c46d6e56a5_0 | IBM Security Bulletin: Vulnerability in SSLv3 affects IBM HTTP Server (CVE-2014-3566) - United States SECURITY BULLETIN
SUMMARY
SSLv3 contains a vulnerability that has been referred to as the Padding Oracle On Downgraded Legacy Encryption (POODLE) attack. SSLv3 is enabled by default in the Apache based IBM HTTP Server.
VULNERABILITY DETAILS
CVE ID: CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566]
DESCRIPTION: IBM HTTP Server could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plain text of encrypted connections. |
00b2b30790d2c9b98aef43c46d6e56a5_1 | CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/97013 [https://exchange.xforce.ibmcloud.com/vulnerabilities/97013] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)
AFFECTED PRODUCTS AND VERSIONS
This vulnerability affects all versions and releases of IBM HTTP Server (IHS) component in all editions of WebSphere Application Server and bundling products.
REMEDIATION/FIXES
There is no separate interim fix for the PI27904 APAR that is associated with this issue, but the interim fix for APAR PI31516 (TLS Padding Vulnerability CVE-2014-8730 [http://www-01.ibm.com/support/docview.wss?uid=swg21692502]) includes the update for APAR PI27904. APAR PI27904 update disables SSLv3 by default for IHS 7.0 and newer, and adds the 'SSLProtocolEnable' directive into IHS 7.0.
The update for PI27904 will be included in fix packs 7.0.0.37, 8.0.0.10 and 8.5.5.4. |
00b2b30790d2c9b98aef43c46d6e56a5_2 | WORKAROUNDS AND MITIGATIONS
For all releases and versions of Apache based IBM HTTP Server, IBM recommends disabling SSLv3:
Add the following directive to the httpd.conf file to disable SSLv3 and SSLv2 for each context that contains "SSLEnable":
# Disable SSLv3 for CVE-2014-3566
# SSLv2 is disabled in V8R0 and later by default, and in typical V7
# and earlier configurations disabled implicitly when SSLv3 ciphers
# are configured with SSLCipherSpec.
SSLProtocolDisable SSLv3 SSLv2
Stop and restart IHS for the changes to take affect.
Note:
* If you start IHS with the -f command line argument, or you use the "Include" directive to include alternate configuration files, you may need to search those filenames for SSLEnable.
* If you configure SSL with SSLEnable in the global (non-virtualhost) scope, you will need to move SSLEnable into a virtualhost scope to add SSLProtocolDisable |
00b2b30790d2c9b98aef43c46d6e56a5_3 | IBM recommends that you review your entire environment to identify other areas that enable SSLv3 protocol and take appropriate mitigation (such as disabling SSLv3) and remediation actions. 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. |
00b2b30790d2c9b98aef43c46d6e56a5_4 | REFERENCES
Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]
On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]
HTTPS advisor fails when SSLv3 is disabled on backend servers [http://www-01.ibm.com/support/docview.wss?uid=swg21691795] TLS Padding vulnerability CVE-2014-8730 [http://www-01.ibm.com/support/docview.wss?uid=swg21692502]
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
15 October 2014: original document published
03 November 2014: added extra notes
02 December 2014: added link to reference section
28 January 2015: added links to CVE-2014-8730 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.