IBM Upgrading to Jazz for Service Management Version 1.1.3.0 using Installation Manager results in a permission denied error - United States jazzsm1130relnotes TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 When upgrading Jazz for Service Management to Version 1.1.3.0 using Installation Manager, the installation fails with the following error:

Cannot run program "/space/IBM/JazzSM/ui/bin/wrapper.sh" (in directory "/space/IBM/JazzSM/ui/bin"): error=13, Permission denied [/space/IBM/JazzSM/install/tip/tipWrapp
erInstall.xml:215]

CAUSE
During the upgrade process the non-root user does not have the correct permissions to run the shell script. This is due to the following:
1. Jazz for Service Management is installed as a non-root user
2. Installation Manager is installed in user mode through root user

RESOLVING THE PROBLEM
The upgrade must be initiated by using the attached script, which gives the non-root user (who originally installed this Jazz for Service Management instance) the correct permissions for the upgrade process.

The script takes two mandatory arguments and one optional argument.

Usage: ./JazzSMgrpModeUpgrade.sh "IM_Install_Location"
"JazzSM_Install_Location [http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/ref/psc_r_pathnames.html]""[Response_file_with_absolute_Path]"

For example (showing default installation paths): ./JazzSMgrpModeUpgrade.sh "/home/root/IBM/InstallManager/" "/opt/IBM/JazzSM/" "/opt/Download/dash_upgrade_rsp.xml"

For IM GUI mode installation, provide the 2 mandatory arguments; IM_Install_Location and JazzSM_Install_Location.
This argument combination invokes Installation Manager in GUI mode and lead you through the rest of the upgrade process.

For IM Silent installation, provide all 3 arguments; IM_Install_Location , JazzSM_Install_Location, and Response_file_with_absolute_Path.
This argument combination invokes Installation Manager in silent mode to upgrade JazzSM.

JazzSMgrpModeUpgrade.sh [/support/docview.wss?uid=swg21985946&aid=2]JazzSMgrpModeUpgrade.sh [/support/docview.wss?uid=swg21985946&aid=1]

Question: DASH 3.1.2.1 to 3.1.3.0 taking long time DASH 3.1.2.1 to 3.1.3.0 taking long time. How to fix this?

Answer: The upgrade must be initiated by using the attached script, which gives the non-root user (who originally installed this Jazz for Service Management instance) the correct permissions for the upgrade process.


IBM Trouble installing ITM on Windows OS - United States  TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 Getting the below error when you try to install ITM on Window OS

"D:\Program Files\IBM\ITM" includes blanks. Due to your system settings the installation path cannot include blanks, please specify location with no spaces.

SYMPTOM
When you try to install ITM on " C:\Program Files\IBM\ITM" it woks fine but when we try to install it on "D:\Program Files\IBM\ITM" we get the below error:

"D:\Program Files\IBM\ITM" includes blanks. Due to your system settings the installation path cannot include blanks, please specify location with no spaces.

If you take out the spaces and use D:\ProgramFiles\IBM\ITM, the install will continue.

RESOLVING THE PROBLEM

Couple of ways to fix this...

1. Remove the space in the directory path and install the ITM on a directory without spaces.

Example : D:\IBM\ITM

2. Check the NTFS 8.3 name creation and enable the 8.3 naming creation to install the ITM on a directory path with spaces.

check the value on the below registry location

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation

In case NtfsDisable8dot3NameCreation is set to (2), this means the following: NTFS sets the 8.3 naming convention creation on a per volume basis.

You can check the 8.3 name creation using this command for the volumes that are impacted.

For example, if the %TEMP% folder is located on c:\, but you are installing on d:\, then you should run these commands:

fsutil 8dot3name query c:
fsutil 8dot3name query d:

You will get an output like this:
The volume state is: 0 (8dot3 name creation is enabled).
The registry state is: 2 (Per volume setting - the default).

Value and Meaning

0 NTFS creates short file names. This setting enables applications that cannot process long file names and computers that use different code pages to find the files.
1 NTFS does not create short file names. Although this setting increases file performance, applications that cannot process long file names, and computers that use different code pages, might not be able to find the files.
2 NTFS sets the 8.3 naming convention creation on a per volume basis.
3 NTFS disables 8dot3 name creation on all volumes except the system volume.

more detail...

https://technet.microsoft.com/en-us/library/cc959352.aspx [https://technet.microsoft.com/en-us/library/cc959352.aspx]

Question: Install path under "Program Files" My path for the OS agent is e:\Program Files\IBM. Is there any issues or underlying problems if I install under "Program Files"? Just want to make sure no issues with a "space" in the install path.

Answer:
Getting the below error when you try to install ITM on Window OS

"D:\Program Files\IBM\ITM" includes blanks. Due to your system settings the installation path cannot include blanks, please specify location with no spaces.


IBM Optim, Optim Connect, ODM, and Optim zOS licensing - United States license key; password; fix pack; enable; license file; Open Data Manager; ODM; entitle TECHNOTE (FAQ)

QUESTION
 Are license keys still required for Optim Distributed, Optim Connect, ODM, and Optim zOS products?

ANSWER
See the attached document for a full explanation of which license keys might be required, how to request them if they are, and how to self-entitle your Optim product if they are not.

Optim license key technote.doc [/support/docview.wss?uid=swg21973794&aid=2]Optim license key technote.doc [/support/docview.wss?uid=swg21973794&aid=1]

Question:
Optim license

We bought Optim 11.3, Test data management and data masking module....

I wonder how to get a Optim license?

Answer:
See the attached document for a full explanation of which license keys might be required, how to request them if they are, and how to self-entitle your Optim product if they are not.

Optim license key technote.doc [/support/docview.wss?uid=swg21973794&aid=2]Optim license key technote.doc


IBM WebSphere Application Server 7.0 Test Environment Extension 7.0.0.41 - United States ifix; interim fix; i-fix; fix; patch; update; fixes; upgrade DOWNLOADABLE FILES

ABSTRACT
 IBM WebSphere Application Server 7 Fix Pack 41 (7.0.0.41) is available as an installed test environment extension

DOWNLOAD DESCRIPTION
This download includes the following update to the WebSphere Application Server v7.0 Test Environment extension included with Rational Software Delivery Platform products:

 * IBM WebSphere Application Server Version 7 Fix Pack 41 also known as version 7.0.0.41. For more information, see the WebSphere Application Server readme [http://www-01.ibm.com/support/docview.wss?uid=swg27004980#ver70].
 * WebSphere Application Server Feature Pack for Web 2.0 1.0.1.1
 * WebSphere Application Server Feature Pack for Mobile 1.1.0.1 (Note: This feature pack is available only when installing with version 8.0 or newer.)
 * WebSphere Application Server Feature Pack for Communications Enabled Applications 1.0.0.13
 * WebSphere Application Server Feature Pack for Service Component Architecture 1.0.1.17
 * WebSphere Application Server Feature Pack for XML 1.0.0.15
 * WebSphere Application Server Feature Pack for OSGi Applications and Java Persistence API (JPA) 2.0 v1.0.0.9 (Note: This feature pack is available only when installing with version 8.0 or newer.)
 * WebSphere Application Server Feature Pack for Modern Batch 1.0.0.5 (Note: This feature pack is available only when installing with version 8.0 or newer.)

For more information on feature packs for WebSphere Application Server, see http://www.ibm.com/support/docview.wss?uid=swg27008534&wv=1#was70 [http://www.ibm.com/support/docview.wss?uid=swg27008534&wv=1#was70]. PREREQUISITES
You must have the WebSphere Application Server 7.0 Test Environment extension installed.

You need up to 5.18 GB of disk space to install the fix pack. To download and extract the compressed installation files, you need an additional 6 GB of disk space.

INSTALLATION INSTRUCTIONS
Important: By default, you do not need to download the compressed files that contain the update; the update is downloaded and installed by IBM Installation Manager directly from the IBM update repository.

For instructions on installing this update using Installation Manager, see the topic Updating Installed Product Packages in the information center for your product and version:

 * Rational Application Developer for WebSphere Software, version 8.5.x [http://www.ibm.com/support/knowledgecenter/SSRTLW_8.5.5/com.ibm.rad.install.doc/topics/t_update.html]
 * Rational Application Developer for WebSphere Software, version 9.0.x [http://www.ibm.com/support/knowledgecenter/SSRTLW_9.0.0/com.ibm.rad.install.doc/topics/t_update.html]
 * Rational Application Developer for WebSphere Software, version 9.1.x [http://www.ibm.com/support/knowledgecenter/SSRTLW_9.1.0/com.ibm.rad.install.doc/topics/t_update.html]

To download and install the update from the compressed files, complete the following steps:
 1. Download the update files from Fix Central by following the link listed in the download table below
 2. Extract the compressed files in an appropriate directory. For example, choose to extract to C:\temp\update
 3. Add the update's repository location in IBM Installation Manager:  1. Start IBM Installation Manager.
     2. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.
     3. On the Repositories page, click Add Repository.
     4. In the Add repository window, browse to or enter the file path to the diskTag.inf file, which is located in the disk1 sub-directory in the directory where you extracted the compressed files and then click OK. For example, enter C:\temp\updates\disk1\diskTag.inf.
     5. Click OK to close the Preference page.

 4. Install the update as described in the the topic "Updating Installed Product Packages" in the information center for your product and version

DOWNLOAD PACKAGE
You can download the fix pack from Fix Central using either Download Director, HTTP or FTP.

 1. Click the link in the table that follows to access Fix Central.
 2. On the Select Fixes page, select Fix pack : 9.1.1.2-Rational-RAD-groupfixpack (IBM Rational Application Developer for WebSphere Software Version 9.5.0.2)
 3. Expand section Show contained fixes.
 4. From the list of contained fixed, select one of the following options:

 * (For 64-bit) 7.0.0.41-Rational-WAS70_64-fixzippack (WebSphere Application Server 70 64bit Extension version 7.0.0.41 update pack)
 * (For 32-bit) 7.0.0.41-Rational-WAS70-fixzippack (WebSphere Application Server 70 Extension version 7.0.0.41 update pack
   1. Click Continue and follow the prompts to download the update.

Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 7.0.0.41-Rational-WAS70-fixzippack 6 May 2016 English 1 FC [https://ibm.biz/Bd48Av] [ ]
TECHNICAL SUPPORT

TAB NAVIGATION
 * General Support Information- selected tab,
 * Support Resources [http://www.ibm.com/support/docview.wss?uid=swg27020747]- selected tab,

IBM Rational Software Support Communities

 * Visit the IBM Support Portal [http://www.ibm.com/support/entry/portal/Overview/Software/Rational/product] to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.

 * Visit developerWorks [http://www.ibm.com/developerworks/rational/] to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community [http://www.ibm.com/developerworks/rfe/].

 * Visit the Jazz Community [http://jazz.net/] if you use a Rational product created using the Jazz platform to interact directly with the Jazz development team and other community members, download product trials and betas and track developement progress.

HELPFUL HINTS FOR OBTAINING TECHNICAL ASSISTANCE:
Before you contact IBM Rational Software Support, gather the background information that you need to describe the problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:

 * What software versions were you running when the problem occurred?
 * Do you have logs, traces, or messages that are related to the problem?
 * Can you reproduce the problem? If so, what steps do you take to reproduce it?
 * Is there a workaround for the problem? If so, be prepared to describe the workaround.

If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support [http://www.ibm.com/software/support/exchangeinfo.html].

Follow IBM Rational Client Support on Twitter [http://twitter.com/rationalsupport] | Facebook [http://facebook.com/rationalsupport] | YouTube [http://www.youtube.com/ibmrationalsupport] | devWorks Blog [https://www.ibm.com/developerworks/mydeveloperworks/blogs/nfrsblog/?lang=en]

 Back to top

Question: Is WAS TE v7.0.0.41 available for RAD? Is WebSphere Application Server 7.0 Test Environment Extension (WTE) v 7.0.0.41 available for Rational Application Developer for WebSphere Software (RAD) ?

Answer:
This download includes the following update to the WebSphere Application Server v7.0 Test Environment extension included with Rational Software Delivery Platform products:

 * IBM WebSphere Application Server Version 7 Fix Pack 41 also known as version 7.0.0.41.


IBM Differences between Rational Rhapsody 8.0 Statecharts and UML 2.4.1 Behavior State Machine - United States Restriction; Restrictions; Limitation; Limitations; drawing; graphical; graph; difference; diferences; gap; deffer; feature; features; concept; concepts; error; errors WHITE PAPER

ABSTRACT
 This is a white paper that explains the differences between IBM Rational Rhapsody 8.0.x Statecharts and UML 2.4.1 Behavior State Machine.

CONTENT

Authors: Shinji Kanai, Moria Abadi

OMG UML and IBM Rational Rhapsody have been evolving in parallel, and some differences were created and expanded over time. Not all graphical notations that are defined in UML specification are supported by Rhapsody. There are certain patterns of transitions you cannot draw due to restrictions imposed deliberately, but not necessarily limited by UML specification. Some of UML features such as deferred event and do-activity are not natively supported today. This document covers such gaps that are found between UML specification and Rhapsody implementation, aiming to help you design statechart more effectively and enable easier interchange of statecharts among UML-based modeling tools.

Disclaimer This documentation is created based on differences that are found between Rhapsody 8.0.x Statechart and OMG UML 2.4.1 Superstructure Specification (UML spec). The content is believed to be accurate at the time of publication. Use this documentation at your own risk as it might contain some incompleteness and imprecision.

Table: Graphical Notations and Naming comparison

UML2.4.1 Concept: Behavior state machine element or capability as it is named in OMG UML 2.4.1 Superstructure Spec. Section in spec: The section describing the element in UML spec. In Rhapsody: The corresponding name and graphical notation of UML concept that is used in Rhapsody. Note: Additional comments to help understand the specific concept better.
[/support/docview.wss?uid=swg27040251&aid=1] UML2.4.1 Concept Section in spec In Rhapsody Note 1. Entry Point
[/support/docview.wss?uid=swg27040251&aid=2] 15.3.1 EnterExitPoint
[/support/docview.wss?uid=swg27040251&aid=3] (*) Visualization using a rectangular symbol is not supported
(*) Not supported for composite states (See NO. 36). 2. Exit Point
[/support/docview.wss?uid=swg27040251&aid=4] 15.3.1 EnterExitPoint
[/support/docview.wss?uid=swg27040251&aid=5] (*) Visualization using a rectangular symbol is not supported
(*) Not supported for composite states, only for submachine states 3. Final State
[/support/docview.wss?uid=swg27040251&aid=6] 15.3.2 Termination State
[/support/docview.wss?uid=swg27040251&aid=7] [/support/docview.wss?uid=swg27040251&aid=1] 4. Initial Pseudostate
[/support/docview.wss?uid=swg27040251&aid=8] 15.3.8 Default Connector
[/support/docview.wss?uid=swg27040251&aid=9] [/support/docview.wss?uid=swg27040251&aid=1] 5. Deep History Pseudostate
[/support/docview.wss?uid=swg27040251&aid=10] 15.3.8 History Connector

[/support/docview.wss?uid=swg27040251&aid=11] [/support/docview.wss?uid=swg27040251&aid=1] 6. Shallow History Pseudostate
[/support/docview.wss?uid=swg27040251&aid=12] 15.3.8 Shallow History Connector
[/support/docview.wss?uid=swg27040251&aid=13] (*) Code Generation is supported in v8.0.6. See technote 1668548 [http://www.ibm.com/support/docview.wss?uid=swg21668548] for more information. 7. Join Pseudostate
[/support/docview.wss?uid=swg27040251&aid=14] 15.3.8 Join Sync Bar
[/support/docview.wss?uid=swg27040251&aid=15] [/support/docview.wss?uid=swg27040251&aid=1] 8. Fork Pseudostate
[/support/docview.wss?uid=swg27040251&aid=16] 15.3.8 Fork Sync Bar
[/support/docview.wss?uid=swg27040251&aid=17] [/support/docview.wss?uid=swg27040251&aid=1] 9. Junction Pseudostate
[/support/docview.wss?uid=swg27040251&aid=18] 15.3.8 Junction Connector
[/support/docview.wss?uid=swg27040251&aid=19] (*) Used only for merge. Only one outgoing transition is permitted 10. Static Conditional Branch
[/support/docview.wss?uid=swg27040251&aid=20] 15.3.8 Condition Connector
[/support/docview.wss?uid=swg27040251&aid=21] (*) Only one incoming transition is allowed.
(*) Realized by way of the condition connector. 11. Terminate Pseudostate
[/support/docview.wss?uid=swg27040251&aid=22] 15.3.8 termination Connector
[/support/docview.wss?uid=swg27040251&aid=23] [/support/docview.wss?uid=swg27040251&aid=1] 12. State List
[/support/docview.wss?uid=swg27040251&aid=24] 15.3.8 [/support/docview.wss?uid=swg27040251&aid=25] (*) This is an additional representation for transition from the junction having a history as target. the regular representation can be used instead. 13. Region
[/support/docview.wss?uid=swg27040251&aid=26] 15.3.10 Region
[/support/docview.wss?uid=swg27040251&aid=27] [/support/docview.wss?uid=swg27040251&aid=1] 14. Simple State
[/support/docview.wss?uid=swg27040251&aid=28] 15.3.11 Simple State
[/support/docview.wss?uid=swg27040251&aid=29] [/support/docview.wss?uid=swg27040251&aid=1] 15. Composite State
[/support/docview.wss?uid=swg27040251&aid=30] 15.3.11 Composite State
[/support/docview.wss?uid=swg27040251&aid=31] [/support/docview.wss?uid=swg27040251&aid=1] 16. Submachine State
[/support/docview.wss?uid=swg27040251&aid=32] 15.3.11 Sub-statechart
[/support/docview.wss?uid=swg27040251&aid=33] [/support/docview.wss?uid=swg27040251&aid=1] 17. Entry Behavior
[/support/docview.wss?uid=swg27040251&aid=34] 15.3.11 Action on Entry
[/support/docview.wss?uid=swg27040251&aid=35] [/support/docview.wss?uid=swg27040251&aid=1] 18. Exit behavior
[/support/docview.wss?uid=swg27040251&aid=36] 15.3.11 Action on Exit
[/support/docview.wss?uid=swg27040251&aid=37] [/support/docview.wss?uid=swg27040251&aid=1] 19. Behavior in state (do-activity)
[/support/docview.wss?uid=swg27040251&aid=38] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=39] (*) Can be implemented using entry and exit actions. See appendix (*2) for additional information. 20. Deferred events
[/support/docview.wss?uid=swg27040251&aid=40] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=41] (*) Can be modeled by customizing the framework. See appendix (*3) for additional information. 21. State Redefinition 15.3.11 State Redefinition (*) Class inheritance causes inheritance of statecharts. the inherited statechart can redefine its inherited states. 22. State Machine extension 15.3.12 State machine extension (*) through class inheritance 23. Time event
[/support/docview.wss?uid=swg27040251&aid=42] 15.3.13 Time event
[/support/docview.wss?uid=swg27040251&aid=43] (*) First option tm(<expression>), where<expression> is the number of time units. Second option Accept time event. 24. Transition 15.3.14 Transition (*) A transition cannot be associated with more than one trigger. Separate transitions for each trigger need to be used.
(*) See appendix (*4) for the list of known transaction patterns that are forbidden by Rhapsody. 25. Internal transition
[/support/docview.wss?uid=swg27040251&aid=44] 15.3.14 Reaction in state
[/support/docview.wss?uid=swg27040251&aid=45] [/support/docview.wss?uid=swg27040251&aid=1] 26. Completion transition 15.3.14 Null transition [/support/docview.wss?uid=swg27040251&aid=1] 27. Completion event 15.3.14 Null event [/support/docview.wss?uid=swg27040251&aid=1] 28. Transition redefinition 15.3.14 Transition redefinition (*) Class inheritance causes inheritance of statecharts. the inherited statechart can redefine its transitions, except the source state and the trigger. 29. Signal receipt
[/support/docview.wss?uid=swg27040251&aid=46] 15.3.14 Accept Event Action
[/support/docview.wss?uid=swg27040251&aid=47] [/support/docview.wss?uid=swg27040251&aid=1] 30. Signal sending
[/support/docview.wss?uid=swg27040251&aid=48] 15.3.14 Send Action
[/support/docview.wss?uid=swg27040251&aid=49] [/support/docview.wss?uid=swg27040251&aid=1] 31. Action sequence notation
[/support/docview.wss?uid=swg27040251&aid=50] 15.3.14 [/support/docview.wss?uid=swg27040251&aid=51] [/support/docview.wss?uid=swg27040251&aid=1] 32. Local transition
[/support/docview.wss?uid=swg27040251&aid=52] 15.3.15 [/support/docview.wss?uid=swg27040251&aid=53] [/support/docview.wss?uid=swg27040251&aid=1] 33. Choice Pseudostate/Dynamic Conditional Branch
[/support/docview.wss?uid=swg27040251&aid=54] 15.3.8 [/support/docview.wss?uid=swg27040251&aid=55] (*) Can be simulated for example by using an additional state with guarded outgoing null transitions. See attachment (*1) in appendix. 34. Final Notation
[/support/docview.wss?uid=swg27040251&aid=56] 15.3.8 [/support/docview.wss?uid=swg27040251&aid=57] (*) {final} means that the state cannot be redefined (such as, extended). 35. Entry/Exit Point as part of submachine state graph
[/support/docview.wss?uid=swg27040251&aid=58] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=59] [/support/docview.wss?uid=swg27040251&aid=1] 36. Entry/Exit Point on composite state
[/support/docview.wss?uid=swg27040251&aid=60] 15.3.8 [/support/docview.wss?uid=swg27040251&aid=61] [/support/docview.wss?uid=swg27040251&aid=1] 37. "Bracket" Entry/Exit Point notation
[/support/docview.wss?uid=swg27040251&aid=62] 15.3.1 [/support/docview.wss?uid=swg27040251&aid=63] [/support/docview.wss?uid=swg27040251&aid=1] 38. Referenced/Reused submachine state
[/support/docview.wss?uid=swg27040251&aid=64] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=65] (*) Creation of submachine is supported, but cannot be reused/referenced elsewhere. 39. Multiple triggers for a transition
[/support/docview.wss?uid=swg27040251&aid=66] 15.3.14 [/support/docview.wss?uid=swg27040251&aid=67] [/support/docview.wss?uid=swg27040251&aid=1] 40. Extended Notation
[/support/docview.wss?uid=swg27040251&aid=68] 15.3.11 [/support/docview.wss?uid=swg27040251&aid=69] (*) Similar effect is achievable but need to extend a whole class containing a state machine using generalization.

Appendix:

Disclaimer All source code or binaries attached to this document are referred to here as "the Program". IBM is not providing program services of any kind for the Program. IBM is providing the Program on an "AS IS" basis without warranty of any kind. IBM WILL NOT BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM, OR ITS RESELLER, HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

#tbc

#tbc
(*1) Dynamic Conditional Branch

DynamicBranch74orHigher.zip [/support/docview.wss?uid=swg27040251&aid=71]DynamicBranch74orHigher.zip [/support/docview.wss?uid=swg27040251&aid=70]

#tbc
(*2)
there is a risk that is involved to support an execution of an action that is being performed while the owning object is in a certain state. For example, there is a state "WaitForInput" with Do Action reading an input from the console in the background. Now an event comes to trigger a transition - a need arose to interrupt the operation of reading the input - but there is no generic way to do such things for all operations unless the action is being performed in a different thread and kill this thread. this solution seems risky for embedded systems and considered inefficient.

#tbc
(*3)
Rhapsody does not support deferred events, but there is an easy way to catch an event, which is not consumed, and process it according to your need. OMReactive class contains handleNotConsumed() virtual function, which can be overridden in your reactive class. This function is always called when event is not consumed.

(*4)Transactional Restrictions - List of known transaction patterns that are forbidden by Rhapsody

Multiple outgoing transitions from Exit Point [/support/docview.wss?uid=swg27040251&aid=72] Transition to Condition Connector from Entry/Exit Point having multiple incoming transitions [/support/docview.wss?uid=swg27040251&aid=73] [/support/docview.wss?uid=swg27040251&aid=73]
[/support/docview.wss?uid=swg27040251&aid=74] [/support/docview.wss?uid=swg27040251&aid=74] Direct transition from Junction to Condition Connector [/support/docview.wss?uid=swg27040251&aid=75] Indirect transition from Junction to Condition Connector by way of Entry/Exit Point [/support/docview.wss?uid=swg27040251&aid=76] Direct transition from Join Bar to Junction [/support/docview.wss?uid=swg27040251&aid=77] Direct transition from Junction to Fork Bar [/support/docview.wss?uid=swg27040251&aid=78] Multiple incoming transition to Condition Connector [/support/docview.wss?uid=swg27040251&aid=79] Set a trigger on a transition that is originated from Exit Point [/support/docview.wss?uid=swg27040251&aid=80]
RELATED INFORMATION
 UML 2.4.1 Superstructure [http://www.omg.org/spec/UML/2.4.1/Superstructure/PDF/]
Enhancement for Do Activity [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=8817]
Enhancement for Dynamic Condition Connector [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=7832]
Enhancement for Shallow History Connector [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=5916]
Enhancement Deferred Event [http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=12691]

Question:
During action in Rhapsody Statechart

Hi Folks,

I am developing a statechart in Rhapsody and I have a question.

I could not see in Rhapsody where I can insert an action that must occur during the whole time the state is active.

I can only see : Actions on Entry     and    Actions on Exit.

Where is During Action?

Answer: Some of UML features such as deferred event and do-activity are not natively supported today.


IBM Transformation Extender Oracle adapter does not support SYS_REFCURSOR return type in an Oracle stored procedure / function - United States Oracle Adapter Unsupported datatype SYS_REFCURSOR TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 When using the IBM WebSphere Transformation Extender (WTX) / IBM Transformation Extender (ITX) Oracle adapter to call a stored procedure / function with a REF_SYSCURSOR return type, a failure of "Unsupported datatype returned is being treated as text" occurs.

SYMPTOM
The Oracle database adapter log (.dbl) reports the following error:

Unsupported datatype returned is being treated as text.

CAUSE
SYS_REFCURSOR is not a valid datatype as a return from an Oracle stored procedure call using the WTX / ITX Oracle adapter.

ENVIRONMENT
IBM WebSphere TX / IBM TX Oracle adapter on any valid execution platform

DIAGNOSING THE PROBLEM
LASTERRORMSG() reports 'Failed to execute the SQL statement' and the database adapter log reports 'Unsupported datatype returned is being treated as text.'

RESOLVING THE PROBLEM
Redesign the Stored Procedure to NOT return a SYS_REFCURSOR datatype.

Question:
Stored Procedure in WTX

Hi All,

Can anyone please share the example/steps/document link on how to call Stored Procedure in Input Card of a Map? The Stored Procedure will return multiple rows and columns and we need to map those rows in Output as well. Please enlighten if someone has worked on this?

Answer: SYS_REFCURSOR is not a valid datatype as a return from an Oracle stored procedure call using the WTX / ITX Oracle adapter.


IBM SCM check analyses are showing as <not activated> the SCA user interface - United States  TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 The reason why your check analyses are no longer showing activated and returning data in the SCA user interface.

SYMPTOM
Check analyses in the SCA interface are showing as <not activated> in the SCA user interface where at one point they were activated and returning data. Now they are not activated and not returning data.

CAUSE
The operator who activated the analysis has been deleted. The audit trail cleaner tool was run and it removed the operator and de-activated the analysis.

RESOLVING THE PROBLEM
To resolve the issue, have an active operator reactivate the check analyses and then run a new import in SCA. As a best practice, it is recommended that you have an operator account dedicated to activating the SCM check analyses in your deployment. This account should never be deleted.

Cross reference information Segment Product Component Platform Version Edition Security IBM BigFix Compliance

Question:
SCM check analyses showing as not reported in the SCA user interface
SCM check analyses showing as <not reported> the SCA user interface.

Check analyses in the SCA interface are showing as in the SCA user interface where at one point they were activated and returning data. Now they are not activated and not returning data.

How do I solve this issue?

Answer: To resolve the issue, have an active operator reactivate the check analyses and then run a new import in SCA. As a best practice, it is recommended that you have an operator account dedicated to activating the SCM check analyses in your deployment. This account should never be deleted.


IBM How to serve static files from both IBM HTTP Server and an application in WebSphere Application Server - United States  TECHNOTE (FAQ)

QUESTION
 How can I configure IBM HTTP Server (IHS), and the IBM web server Plug-in, and my web application running in WebSphere Application Server (WAS), to serve some of my static files (JPG, GIF, CSS, JS, etc) from the IHS web server, but serve other static files from my web app running in WAS?

CAUSE
The "fileServingEnabled" property in the ibm-web-ext.xmi file in the web application, is like an ON / OFF switch.
A setting of fileServingEnabled="true" means that ALL static files will be served from the web application in WAS only. In this case, the plug-in config will use a wildcard with the application context-root like "/myapp/*". That way every URL starting with /myapp/* will be routed to the application in WAS.

On the other hand, fileServingEnabled="false" means NO static files will be served from the application in WAS. In this case, a wildcard will NOT be used in the plugin-cfg.xml file. Instead, there will be several URI entries matching the URL-Patterns from <servlet-mappings> in the web.xml, like "/myapp/servlet1" and "/myapp/index.jsp". Requests for dynamic content matching the URI entries in the Plug-in config, will be routed to the application in WAS. But everything else (static content) will be handled by the IHS web server itself.

ANSWER
If you want to serve any static files (JPG, GIF, CSS, JS, etc) from your web application in WAS, you must use fileServingEnabled="true" in the ibm-web-ext.xmi file. That will cause the plug-in to use a wildcard entry for the context-root of your web application. For example, if the context-root is "myapp", then there will be a URI entry for "/myapp/*" in the plug-in config, and everything starting with "myapp" will be routed to the application in WAS.

Now, if you also want to be able to serve some of the static files from the IHS web server itself, you will need to do a trick using RewriteRule in the IHS config. Here is how the trick works:

1) Create a subdirectory called "static" under the IHS DocumentRoot directory. And put the static files that you want IHS to serve into that directory. For example in the IHS document root directory (HTTPServer/htdocs/) create a subdirectory called "static". Something like this:
/usr/IBM/HTTPServer/htdocs/static/

2) In your web application, you will reference those files using relative references like "static/picture.jpg", or "static/mystyles.css".

Those relative references will be interpreted as URLs like this:
/myapp/static/picture.jpg
/myapp/static/mystyles.css

Keep in mind that there really is NOT any "static" subdirectory in the application. But that is ok.

3) Now, in the IHS config, you must use RewriteCond and RewriteRule to watch for these references, and redirect to get them from IHS. For example, look at these directives...

<ifModule mod_rewrite.c>
RewriteEngine on
RewriteRule ^/myapp/static/(.*) /static/$1 [PT]
</ifModule>

It means, if the URI begins with /myapp/static/* then IHS will rewrite it to just /static/* and "pass-through". Since /static/* does NOT match anything in the Plug-in config, the request will be handled by IHS, and the file will be served from the static directory under IHS DocumentRoot.

To the user looking at the URL in the browser they will see this:
/hostname/myapp/static/picture.jpg

But, the file will really be served by IHS from here:
/hostname/static/picture.jpg

Here is another example:

If you just want to match and serve *.gif files from IHS, use:

RewriteCond %{REQUEST_URI} \.(gif)$ [NC]
RewriteRule ^/myapp/(.*) /static/$1 [PT]

If you just want to match and serve *.gif, *.css and *.js files from IHS, use:

RewriteCond %{REQUEST_URI} \.(gif|css|js)$ [NC]
RewriteRule ^/myapp/(.*) /static/$1 [PT]

Which assumes the files themselves are placed in [IHS_DOC_ROOT]/static/.

4) For the static files in the application, you will need to put them in some other directory that is NOT called "static", for example "images/sunset.jpg" would be a directory and file in the myapp application. This URL request, would be handled by the Plug-in and sent to the application in WAS:
hostname/myapp/images/sunset.jpg

So, by using the trick described above, some static files will be served from IHS, like:
/hostname/myapp/static/picture.jpg

But other static files will be served from the web application running in WAS, like:
/hostname/myapp/images/sunset.jpg

Question: How to serve static images from our HTTP Server instead of WebSphere 8.5 application? How to serve static images from our HTTP Server instead of WebSphere 8.5 application?

Answer: If you want to serve any static files (JPG, GIF, CSS, JS, etc) from your web application in WAS, you must use fileServingEnabled="true" in the ibm-web-ext.xmi file. That will cause the plug-in to use a wildcard entry for the context-root of your web application.


IBM Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5 (CVE-2015-4000) - United States  SECURITY BULLETIN

SUMMARY
 The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5.

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)

AFFECTED PRODUCTS AND VERSIONS
IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server version 2.5

REMEDIATION/FIXES
None

WORKAROUNDS AND MITIGATIONS
Customers should follow the mitigation advice contained in the WebSphere Application Server security bulletin, located at http://www.ibm.com/support/docview.wss?uid=swg21957980 [http://www-01.ibm.com/support/docview.wss?uid=swg21957980] .

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
Reported to IBM by The WeakDH team at https://weakdh.org [https://weakdh.org]

CHANGE HISTORY
 08 June 2015: Original document 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.

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.

Question: Help with Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5 (CVE-2015-4000) I need to understand details regarding Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5 (CVE-2015-4000). This vulnerability is commonly referred to as "Logjam". Where can I find this information?

Answer:
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)


IBM How to get debug information when the IBM Content Navigator Installer on the Unix Platform is failling? - United States  TECHNOTE (FAQ)

QUESTION
 How to get debug information when the IBM Content Navigator Installer on the Unix Platform is failling?

ANSWER
To capture the debug output from the UNIX command line, enter one of the following (based on what shell you are using) at the command line prior to executing the installer:
export LAX_DEBUG=true or setenv LAX_DEBUG true or LAX_DEBUG=true or set LAX_DEBUG or whatever would be appropriate for the Unix shell.

Then run the installer. The output that is produced should help debug the installer.
If you would like to redirect output to a file:
1. Set LAX_DEBUG=file as per the instruction above.
2. Run your installer.
3. Once the install is complete a file labeled jx.log will be generated in the same directory as your installer. This file will contain the entire debug output generated by the install.

Question: How to get debug information when the IBM Content Navigator Installer is failing on the Unix Platform? How to get debug information when the IBM Content Navigator Installer is failing on the Unix Platform?

Answer:
To capture the debug output from the UNIX command line, enter one of the following (based on what shell you are using) at the command line prior to executing the installer:
export LAX_DEBUG=true or setenv LAX_DEBUG true or LAX_DEBUG=true or set LAX_DEBUG or whatever would be appropriate for the Unix shell.

Then run the installer. The output that is produced should help debug the installer.
If you would like to redirect output to a file:
1. Set LAX_DEBUG=file as per the instruction above.
2. Run your installer.
3. Once the install is complete a file labeled jx.log will be generated in the same directory as your installer. This file will contain the entire debug output generated by the install.


IBM Will current versions of IBM SPSS Statistics or AMOS for Windows run on a Macintosh operating system? - United States  TECHNOTE (FAQ)

QUESTION
 I have a Macintosh computer with Intel processor. I am wondering if I can install an IBM SPSS Statistics for Windows or IBM SPSS AMOS for Windows releases on this Mac with emulation or dual-booting software such as Boot Camp, Parallels, Virtual PC, Rosetta?

ANSWER
No, installing IBM SPSS Statistics and AMOS for Windows releases on a Macintosh operating system or hardware using any dual booting or emulation software is not supported and cannot run properly.

IBM SPSS Statistics is available for Macintosh operating system as a single release. IBM SPSS AMOS is available only for Microsoft Windows operating system.

RELATED INFORMATION
 Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]

Question:
Licence authorised in SPSS 22, however, same error code of missing license appears I had SPSS 22 that worked fine until the license ended. It was renewed and when I tried to re-enter the license number it was authorised, however, there was still an error code of missing license and so I can work with my SPSS.

This is the error code:

    Error # 7001 There is no license for IBM SPSS Statistics. This could be due to a missing license file or no more network licenses available. For detailed information about this problem, run the 'showlic' utility found in the product installation directory. Execution of this command stops. Specific symptom number: 18

I would appreciate your help!

Answer: No, installing IBM SPSS Statistics and AMOS for Windows releases on a Macintosh operating system or hardware using any dual booting or emulation software is not supported and cannot run properly.


IBM Why does IBM Datacap 8.1 appear to hang, requiring a restart of all components? - United States hang; non responsive; timeout; Admin retry; Engine retry TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 Why does IBM Datacap appear to hang, requiring a restart of all components?

SYMPTOM
The Datacap system appears to become non-responsive, requiring a restart of all components to get it working again.

CAUSE
The cause is due to a malformed SQL query string. From the client perspective, it was reported to occur during logon via TMWeb, and Thick Client. Another case was from a user that was doing a Thick Client query.

TMServer has an feature where it will retry any command that results in error, based on the settings in the registry. The settings reflect the number of retries to do and the time interval to wait. The default settings have a duration of 16 minutes, which gives the appearance that the TMServer has hung.

DIAGNOSING THE PROBLEM
Collect and examine the TMServer log. Look for multiple instances (6-12) of an ADO error, indicating a bad query was executed. This information can be used to identify the user that is causing the problem

RESOLVING THE PROBLEM
While bad queries should be avoided, the following will allow TMServer to respond faster, should a bad query happen:

1. Stop all Datacap applications, then stop the TMServer.

2. Change the following registry entries on the TMServer box:

 *
 *
 *  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Datacap\TMS\InterThread (REG_SZ) Admin retries HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Datacap\TMS\InterThread (REG_SZ) ADO retries HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Datacap\TMS\InterThread (REG_SZ) Engine retries
 *
 *
 *
 *  HKEY_LOCAL_MACHINE\SOFTWARE\Datacap\TMS\InterThread (REG_SZ) Admin retries HKEY_LOCAL_MACHINE\SOFTWARE\Datacap\TMS\InterThread (REG_SZ) ADO retries HKEY_LOCAL_MACHINE\SOFTWARE\Datacap\TMS\InterThread (REG_SZ) Engine retries
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 *

3. Restart the TMServer, then start the Datacap applications in reverse order.

Please Note: Since these are considered tuning parameters, you will need to test to see what settings work best for your system.

Note: for Datacap 9.x, the registry entry name is singular, as in 'Admin retry' or 'Engine retry'.

Question: Why does IBM Datacap 8.1 appear to hang Why does IBM Datacap 8.1 appear to hang, requiring a restart of all components http://ow.ly/yhjCg  #ibmecm

Answer:
The cause is due to a malformed SQL query string. From the client perspective, it was reported to occur during logon via TMWeb, and Thick Client. Another case was from a user that was doing a Thick Client query.

TMServer has an feature where it will retry any command that results in error, based on the settings in the registry. The settings reflect the number of retries to do and the time interval to wait. The default settings have a duration of 16 minutes, which gives the appearance that the TMServer has hung.


IBM WebSphere DataPower is not affected by the Bash vulnerabilities (CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277, and CVE-2014-6278)
Flash (Alert) - United States CVE-2014-6271 CVE-2014-7169 DataPower Bash FLASH (ALERT)

ABSTRACT
 DataPower is not vulnerable to the Bash vulnerabilities that have been referred to as “Bash Bug” or “Shellshock” and the two memory corruption vulnerabilities.

CONTENT
DataPower does not use Bash anywhere. Hence it is not impacted by any of the Bash vulnerabilities.

In particular, DataPower in all editions and all platforms is NOT vulnerable to the Bash vulnerabilities: CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277, and CVE-2014-6278.

IBM recommends that you review your entire environment to identify vulnerable releases of Bash and take appropriate mitigation and remediation actions.

Question: Is DataPower affected by the bash environment variable vulnerability CVE-2014-6271 or CVE-2014-7169 Is DataPower affected by the recent vulnerability reported through CVE-2014-6271 or CVE-2014-7169?

Answer: In particular, DataPower in all editions and all platforms is NOT vulnerable to the Bash vulnerabilities: CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277, and CVE-2014-6278.


IBM How to Export the Scan Results (Detailed Security Issues) into XML format in AppScan Enterprise - United States  TECHNOTE (FAQ)

QUESTION
 Is there a way to Export the Scan Results (Detailed Security Issues) into XML format in IBM Security AppScan Enterprise?

ANSWER
The answer to the question is 'no'.
In AppScan Enterprise Console, there are functions, Export to XML and Export detailed Security issues to PDF, but there is no function Export detailed Security issues to XML.

We strongly suggest to submit an enhancement request (RFE) for the AppScan Enterprise products as described in How to submit enhancement requests for IBM Security products [http://www.ibm.com/support/docview.wss?uid=swg21682719]. The requests there are submitted directly to the AppScan management team.

Question:
export XML results in ASE

Hello everyone, you all know that ASD gives the possibility to export results in XML with File --> Export --> Scan Results as XML (Legacy...) Is there any chance to have the same XML using ASE 9035 ???

Answer:
The answer to the question is 'no'.
In AppScan Enterprise Console, there are functions, Export to XML and Export detailed Security issues to PDF, but there is no function Export detailed Security issues to XML.


IBM Identifying people in scope across Matters in Atlas - United States Atlas People in Scope Views TECHNOTE (FAQ)

QUESTION
 How do I identify people in scope across Matters in Atlas?

CAUSE
Query to identify people in scope across matters in Atlas

ANSWER
REP_PEOPLE_INSCOPE_VW view has information about people in scope. You can create a query by joining the view with REP_MATTER_VW, REP_REQUEST_VW, REP_NOTICES_VW and REP_PERSON_VW views.

Please refer to reporting views documentation at the following link for more details about Matter related views

https://www.ibm.com/support/knowledgecenter/SS5JP8_6.0.3/com.ibm.aps.use.doc/apsrv0044.html [https://www.ibm.com/support/knowledgecenter/SS5JP8_6.0.3/com.ibm.aps.use.doc/apsrv0044.html]l

Question: How do I identify people in scope across Matters in Atlas? How do I identify people in scope across Matters in Atlas?

Answer: REP_PEOPLE_INSCOPE_VW view has information about people in scope. You can create a query by joining the view with REP_MATTER_VW, REP_REQUEST_VW, REP_NOTICES_VW and REP_PERSON_VW views.


IBM Changes in the default user identifier between WebSphere MQ V7.0.1 classes for JMS and WebSphere MQ V7.1 classes for JMS - United States  TECHNOTE (FAQ)

QUESTION
 You have configured a WebSphere Application Server WebSphere MQ messaging provider connection factory without an Authentication Alias and do not programmatically supply user identifier information when creating a connection to a queue manager. You notice a change in the default behaviour between WebSphere Application Server versions regarding the user identifier flowed on the MQCONN to the target WebSphere MQ Queue Manager:

- When using WebSphere Application Server v7.0 and v8.0, no user identifier value (blank) is passed to the queue manager.

- When using WebSphere Application Server V8.5, a non-blank user identifier value is passed to the queue manager.

In the latter case, you receive the following exception when creating a connection to a queue manager:

JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED')

Is this change in behaviour expected?

ANSWER
WebSphere MQ access control is based on user identifiers. There is a deliberate change in the default behaviour between the WebSphere MQ V7.0.1 classes for JMS and the WebSphere MQ V7.1 (and later) classes for JMS regarding the default user identifier flowed to the queue manager.
From the WebSphere MQ V7.1 classes for JMS onwards, a non-blank user identifier is always flowed to the queue manager when creating a connection to WebSphere MQ. This is true even if no user identifier has been specified, or a blank or null user identifier has been specified; for example by calling:

MQConnectionFactory.createConnection();

or:

MQConnectionFactory.createConnection(“”, “”);

or:

MQConnectionFactory.createConnection(null, null);

In the case where a null or blank user identifier has been specified, the WebSphere MQ V7.1 and later classes for JMS will query the value of the Java System Property user.name. The value of this property is flowed to the queue manager for authorization.

As a result, if the user identifier specified by the Java System Property user.name is not authorized to access the queue manager, the queue manager will return an exception to the WebSphere MQ classes for JMS with Reason Code MQRC_NOT_AUTHORIZED and the connection to the queue manager will not be established.

This change in behaviour could affect topologies that previously relied on the default behaviour in the WebSphere MQ V7.0.1 classes for JMS that flowed a blank user identifier when establishing a CLIENT mode transport connection. The expectation that a blank or null user identifier will be flowed by default, and that the user identifier that started the WebSphere MQ server-connection channel would be used by the queue manager when performing the authorization checks, is no longer valid from the WebSphere MQ V7.1 classes for JMS.

In the case outlined above, system administrators that are currently relying on the default behaviour of the WebSphere MQ V7.0.1 classes for JMS should review their configurations regarding the use of user identifiers and authorization. This might also help to improve security within their WebSphere MQ topology.

In summary, the change in behaviour will affect users of:

- The WebSphere MQ V7.1 and later classes for JMS.

- The WebSphere MQ V7.1 and later JCA Resource Adapter that includes the classes for JMS.

- Versions of WebSphere Application Server that include the WebSphere MQ V7.1 and later JCA Resource Adapter. Currently this is WebSphere Application Server V8.5.0.0 and later.

The com.ibm.mq.jms.ForceUserID Java System Property

A Java System Property called “com.ibm.mq.jms.ForceUserID” was introduced as part of APAR IZ49302 [http://www.ibm.com/support/docview.wss?uid=swg1IZ49302] and included from WebSphere MQ V6.0.2.8 and WebSphere MQ V7.0.1.

The changes made as part of this APAR could be used to change the default behaviour in the WebSphere MQ V7.0.1 classes for JMS regarding the user identifier value flowed to the queue manager when creating a connection.

This property is no longer valid from WebSphere MQ V7.1. Setting this property will have no affect on the WebSphere MQ V7.1 classes for JMS and later.

Other Useful Resources

WebSphere MQ Documentation

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

Question:
MQRC_NOT_AUTHORIZED after migrating from Websphere V7.0 to V8.5.5 After migration from WAS 7 TO WAS 8.5.5.3 ,WAS is unable to communicate with MQ and we see the following errors in the SystemOut.log:

com.ibm.msg.client.jms.DetailedJMSSecurityException: JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager 'XXXQM' with connection mode 'Client' and host name 'ipaddress(port)'.
Please check if the supplied username and password are correct on the QueueManager to which you are connecting. at com.ibm.msg.client.wmq.common.internal.Reason .reasonToException(Reason.j ava:516)
.....
Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED'). at com.ibm.msg.client.wmq.common.internal.Reason.createException (Reason.java:204)

                                                                                What is causing this?

Answer: WebSphere MQ access control is based on user identifiers. There is a deliberate change in the default behaviour between the WebSphere MQ V7.0.1 classes for JMS and the WebSphere MQ V7.1 (and later) classes for JMS regarding the default user identifier flowed to the queue manager.


IBM Configure IBM Content Collector to use SSL to communicate with IBM FileNet P8. - United States  TECHNOTE (FAQ)

QUESTION
 How do I configure IBM Content Collector (ICC) to use SSL to communicate with IBM FileNet P8 for all components?

CAUSE
ICC communicates with P8 in several different components. Depending on the API used for the various components, P8 certificates need to be installed in multiple places.

ANSWER
Do the following steps to install P8 certificates. Depending on your business requirements, you may not use all of the components so some steps may not be necessary.

 * First obtain a P8 server certificate by accessing the P8 Content Engine ping page using this URL: https://<ce_server>:<ssl_port>/FileNet/Engine

   From the browser, view the certificate and copy it to a file. Use it for later steps.
   Do not use the MTOM page as it may not produce the same certificate that ICC requires.

 * Perform this step if you are going to run ICC Initial Configuration to create new document classes in P8 object store.  * To import the certificate, issue the following command, whereICCInstallDiris the directory of your Content Collector installation andP8CertificatFileis the certificate for the FileNet P8 server: "ICCInstallDir\java\jre\bin\keytool.exe" -import -file P8CertificateFile
      -keystore "ICCInstallDir\java\jre\lib\security\cacerts" -alias afup8

    * At the password prompt, enter the password for the JRE keystore. (The default password is changeit.)
    * Enterywhen asked whether to trust the certificate.
    * Run ICC Initial Configuration and you should then be able to validate the connection with P8 using SSL.

 * Perform this step if you are going to run task route archiving to P8:  * Add the P8 certificate into the Windows Trusted Root Certificate Authorities via the Microsoft Management Console.
    * For more details instructions, refer to this document:
      http://www-01.ibm.com/support/docview.wss?uid=swg21610358 [http://www-01.ibm.com/support/docview.wss?uid=swg21610358]

 * Perform this step if you are going to retrieve, restore, or search for documents from P8:  * Start ikeyman from ICC-install-directory\AFUWeb\ewasfor the ICC embedded web application server.
    * In the ikeyman utility, select Key Database File>Open, and select PKCS12as key database type.
    * In theLocationfield, specify theWAShome\profiles\profile name\config\cells\cell name\nodes\node name\trust.p12file.
      ReplaceWAShome,profile name,cell name, andnode namewith the proper values of your web application server installation.
    * Click OK.
    * When prompted for a password, enter the password. ClickOK. The default password is WebAS.
    * Under theSigner certificateslist, clickAddto add the P8 certificate.
    * Exit ikeyman utility and restart IBM Content Collector Web Application service.
    * For more details instructions, refer to this document: http://www.ibm.com/support/knowledgecenter/SSAE9L_4.0.1/com.ibm.content.collector.doc_kc/installing/t_afu_establish_trust_relationship.dita?lang=en [http://www.ibm.com/support/knowledgecenter/SSAE9L_4.0.1/com.ibm.content.collector.doc_kc/installing/t_afu_establish_trust_relationship.dita?lang=en]

Question: How to connect ICC to P8 using SSL? In the ICC Configuration Manager, http has been changed to https in the P8 URL. But validating the connection to P8 fails.

Answer: ICC communicates with P8 in several different components. Depending on the API used for the various components, P8 certificates need to be installed in multiple places.


IBM Content Collector Configuration Store is corrupted - United States  TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 IBM Content Collector Configuration Store Service cannot be started successfully due to database corruption.

SYMPTOM
Cannot start the IBM Content Collector Configuration Store Service

CAUSE
Transaction log gets corrupted when IBM Content Collector server runs out of disk space.

RESOLVING THE PROBLEM

 1. Shutdown the IBM Content Collector Configuration Store Service if it is running.
 2. Make a backup copy of all files under the following directory:
    C:\ProgramData\IBM\ContentCollector\ConfigurationStore

    C:\ProgramData may be hidden by default. Show hidden folders by changing the configuration in Folder and Search options > View tab > Hidden files and folders > Show hidden files, folders, and drives.
 3. Free up disk space on the drive
 4. Delete the following files:
    C:\ProgramData\IBM\ContentCollector\ConfigurationStore\logs\*
    C:\ProgramData\IBM\ContentCollector\ConfigurationStore\solmsg.out
    C:\ProgramData\IBM\ContentCollector\ConfigurationStore\solerror.out

    Important:
    Delete only the files under C:\ProgramData\IBM\ContentCollector\ConfigurationStore\logs\.
    Do not delete the folder itself.

 5. If restoring the configuration store to a previously backed up copy is required, run afuConfigStoreTool -backup to restore the backup copy. See production documentation for more information on running this tool. Otherwise, proceed to the next step.
 6. Restart IBM Content Collector services.

RELATED INFORMATION
 IBM Content Collector Information Center [http://pic.dhe.ibm.com/infocenter/email/v4r0m0/index.jsp]

Question: Cannot start the IBM Content Collector Configuration Store Service How to resolve when the IBM Content Collector Configuration Store Service cannot be started?

Answer:
Shutdown the IBM Content Collector Configuration Store Service if it is running.
 2. Make a backup copy of all files under the following directory:
    C:\ProgramData\IBM\ContentCollector\ConfigurationStore

    C:\ProgramData may be hidden by default. Show hidden folders by changing the configuration in Folder and Search options > View tab > Hidden files and folders > Show hidden files, folders, and drives.
 3. Free up disk space on the drive
 4. Delete the following files:
    C:\ProgramData\IBM\ContentCollector\ConfigurationStore\logs\*
    C:\ProgramData\IBM\ContentCollector\ConfigurationStore\solmsg.out
    C:\ProgramData\IBM\ContentCollector\ConfigurationStore\solerror.out

    Important:
    Delete only the files under C:\ProgramData\IBM\ContentCollector\ConfigurationStore\logs\.
    Do not delete the folder itself.

 5. If restoring the configuration store to a previously backed up copy is required, run afuConfigStoreTool -backup to restore the backup copy. See production documentation for more information on running this tool. Otherwise, proceed to the next step.
 6. Restart IBM Content Collector services.


IBM Cloud Orchestrator (ICO) continues to be a strategic solution for IBM - United States  FLASH (ALERT)

ABSTRACT
 Cloud Orchestrator (ICO) continues to be a strategic solution for IBM

CONTENT
IBM Cloud Orchestrator continues to be a strategic solution for IBM in Hybrid Cloud management and will continue to be actively developed. Future IBM Cloud Orchestrator releases will enable management of external OpenStack environments which are compliant with the RefStack certification, providing more choices and flexibility to clients to select their preferred OpenStack vendor. The current release of IBM Cloud Orchestrator will continue to bundle IBM Cloud Manager with OpenStack (ICMO), while future IBM Cloud Orchestrator releases will no longer bundle ICMO, as it has been announced that ICMO is at the end of market (see reference document below).
IBM Cloud Orchestrator (ICO) and IBM Cloud Manager with OpenStack (ICMO) will continue to be supported until Sept 2020.

Reference: ICMO End of Market announcement:
http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS916-062/index.html&lang=en&request_locale=en [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS916-062/index.html&lang=en&request_locale=en]

Question:
ICO's Roadmap of supporting next OpenStack versions

Hello,

ICO 2.5.0.2 is compatible with OpenStack kilo, is there a plan making it work with OpenStack Liberty/Mitika ?

Would you share any information or link about the roadmap, please?

Thanks in advance.

Answer: The current release of IBM Cloud Orchestrator will continue to bundle IBM Cloud Manager with OpenStack (ICMO), while future IBM Cloud Orchestrator releases will no longer bundle ICMO, as it has been announced that ICMO is at the end of market (see reference document below).


IBM Information Server Informix Wire Protocol driver error "Transaction not available" from ODBC Connector Stage - United States  TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 When using the ODBC Connector Stage to access data in an Informix database, receive the following error:

Message: ODBC_Connector_0: ODBC function "SQLPrepare" reported: SQLSTATE = HY000: Native Error Code = -95: Msg = [IBM(DataDirect OEM)][ODBC Informix Wire Protocol driver][Informix]Unexpected Network Error.
ODBC function "SQLPrepare" reported: SQLSTATE = HY000: Native Error Code = -256: Msg = [IBM(DataDirect OEM)][ODBC Informix Wire Protocol driver][Informix]Transaction not available. (CC_OdbcDBStatement::dbsPrepare, file CC_OdbcDBStatement.cpp, line 347)

RESOLVING THE PROBLEM
To resolve the above error, set the Transaction handling>Isolation Level from none to Auto-Commit.

Question: Column Analysis on Informix database using odbc connector fails with error SQLSTATE = HY000: Native Error Code = -256 Column Analysis on Informix database using odbc connector fails with error SQLSTATE = HY000: Native Error Code = -256

Answer: To resolve the above error, set the Transaction handling>Isolation Level from none to Auto-Commit.


IBM Using dblook and ij to work with the embedded Apache Derby in WebSphere Portal - United States  TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 IBM WebSphere Portal 6.1 uses an embedded version of Apache Derby out of the box. However, there is no longer a graphical tool such as CloudView (as with Cloudscape 5.x). In order to obtain the data and structure of the WebSphere Portal database, dblook and ij utilities can be used to accomplish such goals.

RESOLVING THE PROBLEM

Before proceeding with the following, it is strongly recommended that you back up your Derby database. Make a copy of <wp_profile>/PortalServer/derby/wpsdb to a backup directory. Since the version of Derby used in WebSphere Portal is embedded, you must stop the Portal server before you can access the database although you can always work on the backup copy.

NOTE: For simplicity, we will omit the extension of the utilities. You should add ".sh" or ".bat' depending on the platform.

There are three primary utility tools that are installed with WebSphere 6.1, "dblook", "ij", and "sysinfo", under the <was_root>/AppServer/derby/bin/embedded directory. The sysinfo utility generates information about the operating system, the Java version and classpath, and the Derby driver files and version information.

dblook utility
The dblook utility is used to view the database structure (in DDL - Data Definition Language) for a specific database.

The usage is dblook -d <databaseURL> [options], where databaseURL is in the "jdbc:derby:<database>" format. The <database> should be given as a full path, such as C:\IBM\WebSphere\wp_profile\derby\wpsdb.

Commonly used options include:

 *
 *
 *
 *
 *
 *
 *
 *
 *
 *
 * Examples:
 *
 *
 * dblook -d jdbc:derby:C:\IBM\WebSphere\wp_profile\PortalServer\wpsdb -o C:\temp\wpsdb_ddl.sql
 *
 *
 *
 *
 * dblook -d jdbc:derby:C:\IBM\WebSphere\wp_profile\PortalServer\wpsdb -z release -o C:\temp\wpsdb_ddl.sql
 *
 *
 *
 *
 * dblook -d jdbc:derby:C:\IBM\WebSphere\wp_profile\PortalServer\wpsdb -z release -t user_desc -verbose -o C:\temp\user_desc.sql
 *
 *

ij utility
The ij utility is a command line SQL processor. It can be used to run DDL for creating database, tables, indexes, and so on. In a WebSphere Portal environment, it would typically be used for exporting data or making simple changes (when advised by IBM Support).

To start ij, simply open a command prompt or terminal window, change the directory and enter the command. You should then see the ij shell with prompt "ij>".

The following are some common commands that you may use when reviewing data in the Portal database.  *
 * ij> connect 'jdbc:derby:C:\IBM\WebSphere\wp_profile\derby\wpsdb';
 *
 *
 *
 *
 * ij> show connections;
 *
 *
 *  CONNECTION0* - jdbc:derby:C:\ibm\websphere\wp_profile\portalserver\derby\wpsdb
   * = current connection
   ij> driver "org.apache.derby.jdbc.EmbeddedDriver';
 *
 *
 *
 * ij> set schema=release;
 *
 *
 *
 *
 * ij> select * from user_desc where oid=1000;
 *
 *
 *
 *
 * ij> run 'myquery.sql';
 *
 *
 *
 *
 *
 *
 * ij> CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE('RELEASE','USER_DESC','USER_DESC.SQL',';','|',NULL);
 *
 *
 *
 *
 * ij>
 * CALL SYSCS_UTIL.SYSCS_EXPORT_QUERY('SELECT * FROM RELEASE.USER_DESC','user_desc_query.sqlL',null,'|',NULL);
 *
 *

RELATED INFORMATION
 Derby utility from Apache [http://docs.oracle.com/javadb/10.3.3.0/getstart/cgsusingtoolsutils.html]
Derby SQL references from Apache [http://db.apache.org/derby/docs/10.1/ref/crefsqlj23296.html]

Cross reference information Segment Product Component Platform Version Edition Organizational Productivity- Portals & Collaboration WebSphere Portal End of Support Products AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS 7.0, 6.1

Question:
How can I query the Derby database in Portal via SQL statements? I have a Portal system I just installed. I have not yet run database-transfer to copy the data from the Derby database to a DB2, Oracle, or SQL Server database. I don't wish to transfer to an external database and I have a need to run a SQL query against a table or two in the Derby database to troubleshoot an issue.
How can I perform this action?

Answer: In order to obtain the data and structure of the WebSphere Portal database, dblook and ij utilities can be used to accomplish such goals.


IBM Exceptions starting WAS 8.5 as non root user on Solaris - United States  TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 You notice the exceptions below at start up.

SYMPTOM
Exception: command /usr/sbin/zonecfg failed with 1
and
FFDC Exception:java.lang.Exception SourceId:com.ibm.ws.xd.vv.nodedetect.NetworkInterfaceUtil.getMacAddresses ProbeId:2
java.lang.Exception: dlopen() returned error; rc=128

CAUSE
When WebSphere Application Server is run as a non-root user it will not be able to run native commands. This limited access causes the exceptions.

RESOLVING THE PROBLEM
To resolve the problem, run WebSphere Application Server under a root user. If the environment is not virtualized, that is if Solaris zones are not being used then the errors can be ignored as these will only occur at start up and will not affect a non-virtualized environment

Question:
zonecfg error while starting nodeagent and dmgr

I saw zonecfg error while starting nodeagent and dmgr in solaris server

My env is Oracle Solaris 11.2 SPARC, and WAS is 8558, jave 1.7. [1/22/16 21:31:18:379 AEDT] 00000001 SystemOut O java.lang.Exception: command /usr/sbin/zonecfg failed with 1 at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor.executeCommand(SolarisHypervisor.java:357) at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor.access$100 (SolarisHypervisor.java:30) at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor$Zone.processZoneCfg(SolarisHypervisor.java:570) at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor$Zone.(SolarisHypervisor.java:461) at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor ..... Is that normal behavior and what's the exactly meaning of the error?

Answer: When WebSphere Application Server is run as a non-root user it will not be able to run native commands. This limited access causes the exceptions.


IBM How to set an appropriate number of Portal Datasource connections in WebSphere Portal - United States  TECHNOTE (FAQ)

QUESTION
For a given maximum number of Portal WebContainer threads set, what should I set my maximum Portal datasource connections to?

ANSWER
When tuning WebSphere Portal at version 6.0 and beyond, one of the concerns that arises is how should one tune the maximum number of Portal datasources. Portal can and does make heavy internal use of datasources, so miscalculating this (maximum) value can have a significant impact on system behavior. Out of the box, the default maximum setting is 50. This may or may not be sufficient for any given system.

Each Portal request may make any number of database (DB) requests ranging for none to several.. Further, customized portlets and PPR (Parallel Portlet Rendering) may cause several concurrent DB requests. By default, the maximum number of WebContainer threads is also set to 50. Therefore the ratio between the maximum number of Portal datasource connections to the maximum number of Portal WebContainer threads is 1:1. Support has found that this ratio is often too low for the best performance. In the past, there have been recommendations of this ratio as high as of 2:1 or even 2.5:1.

However, these values caused concern in large deployments where the TOTAL number of maximum datasource connections might start to place a strain on backend resources. Recent analysis suggests that these ratio values may be safely reduced to 1.25: 1 for all Portal datasource, with the exception of the jcrDB when WCM is used extensively. In this case, we recommend a ratio of 1.5:1

-----------------------------------------------------------------------------------------------------------------

For example, if your system's

Maximum number of WebContainer threads is 100

then you should set your

Maximum number of Portal datasource connections to 125

for each Portal datasource.

-----------------------------------------------------------------------------------------------------------------

If during Runtime, you should find that your running out of Portal Datasource connections, you may go ahead and increase the ratio up to 2:1. Please be aware of how this might impact your backend resources and be sure to scale your database accordingly.

------------------------------------------------------------------------------------------------------------------

To find the number of WebContainer threads that are running in any particular Portal server, use the WebSphere Application Server Admin Console and go to the following location:

Servers ---> Application Servers --> WebSphere_Portal (your server) --> Thread Pools --> WebContainer

To find the Data Source setting for your Portal datasources, use the WebSphere Application Server Admin Console to go to the following location:

Resources ---> Data Sources ---> wpdbDB (for example) --> Connection pools

--------------------------------------------------------------------------------------------------------------------

Question: What is the correct number of datasource connections for Portal? What is the best way to figure out how to configure the maximum number of datasource connections for my Portal server? What factors are involved that I need watch out for?

Answer:
When tuning WebSphere Portal at version 6.0 and beyond, one of the concerns that arises is how should one tune the maximum number of Portal datasources. Portal can and does make heavy internal use of datasources, so miscalculating this (maximum) value can have a significant impact on system behavior. Out of the box, the default maximum setting is 50. This may or may not be sufficient for any given system.

Each Portal request may make any number of database (DB) requests ranging for none to several.. Further, customized portlets and PPR (Parallel Portlet Rendering) may cause several concurrent DB requests. By default, the maximum number of WebContainer threads is also set to 50. Therefore the ratio between the maximum number of Portal datasource connections to the maximum number of Portal WebContainer threads is 1:1. Support has found that this ratio is often too low for the best performance. In the past, there have been recommendations of this ratio as high as of 2:1 or even 2.5:1.

However, these values caused concern in large deployments where the TOTAL number of maximum datasource connections might start to place a strain on backend resources. Recent analysis suggests that these ratio values may be safely reduced to 1.25: 1 for all Portal datasource, with the exception of the jcrDB when WCM is used extensively. In this case, we recommend a ratio of 1.5:1


IBM Error TASK001X while upgrading Portal 8.0.0.1 to 8.0.0.1 CF14 during import-nodes sub-task - United States upgrade; TASK001X; import-nodes; 404 TECHNOTE (TROUBLESHOOTING)

PROBLEM
While attempting to upgrade Portal to CF14 the upgrade fails during the import-nodes sub-task.

SYMPTOM
The ConfigTrace.log shows the following...

import-nodes:

--- Exception Thrown ---
C:\Portal8\PortalServer\jcr\wp.content.repository.install\config\include
s\jcr.install_cfg.xml:826: com.ibm.icm.jcr.task.TaskException:
TASK001X: Remote task execution failed with response code 404 due to
exception : Not Found . Please check the server log for more
information.

at
com.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:
840)

at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)

at org.apache.tools.ant.Task.perform(Task.java:364)

at org.apache.tools.ant.Target.execute(Target.java:341)

at org.apache.tools.ant.Target.performTasks(Target.java:369)

at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)

at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleChe
ckExecutor.java:37)

...

Caused by: com.ibm.icm.jcr.task.TaskException: TASK001X: Remote task
execution failed with response code 404 due to exception : Not Found .
Please check the server log for more information.

at
com.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:
825)

... 75 more

CAUSE
The customer had previously disabled the autostart on several applications to improve the Portal startup time

ENVIRONMENT
Portal 8.0.0.1
Windows

DIAGNOSING THE PROBLEM
from ConfigTrace.log...

Wed Nov 19 16:49:42 CST 2014
Target started: import-nodes

import-nodes:
--- Exception Thrown ---
C:\Portal8\PortalServer\jcr\wp.content.repository.install\config\include
s\jcr.install_cfg.xml:826: com.ibm.icm.jcr.task.TaskException:
TASK001X: Remote task execution failed with response code 404 due to
exception : Not Found . Please check the server log for more
information.
at
com.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:
840)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)

...

Caused by: com.ibm.icm.jcr.task.TaskException: TASK001X: Remote task
execution failed with response code 404 due to exception : Not Found .
Please check the server log for more information.
at
com.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:
825)
... 75 more

From here I reviewed the SystemOut.log at the same timestamp and see
the following...

[11/19/14 16:49:43:804 CST] 00000042 filter E
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper doFilter
SRVE8109W: Uncaught exception thrown by filter Extensible Filter:
java.io.FileNotFoundException: SRVE0190E: File not found:
/jcr/remotetask
at
com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor._processEDR(
DefaultExtensionProcessor.java:893)
at
com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.processEDR(D
efaultExtensionProcessor.java:874)

Both of these messages seems to indicate a problem with the WCM
startup. This code is contained in the following
application....JavaContentRepository.ear.

Looking at your last Portal startup I saw this below which occurs
during the wcm application startup....

[11/19/14 15:57:54:566 CST] 00000009 ApplicationMg A WSVR0200I:
Starting application: wcm

....

[11/19/14 16:00:36:812 CST] 00000005 TimeoutManage I WTRN0006W:
Transaction
00000149CA10760B000000012830B348BBD991CDC4031D0DFCED27CDD500F13F7FC95B79
00000149CA10760B000000012830B348BBD991CDC4031D0DFCED27CDD500F13F7FC95B79
00000001 has timed out after 120 seconds.
[11/19/14 16:00:36:831 CST] 00000005 TimeoutManage I WTRN0124I: When
the timeout occurred the thread with which the transaction is, or was
most recently, associated was Thread[server.startup : 0,5,main]. The
stack trace of this thread when the timeout occurred was:
java.lang.Thread.blockedOn(Thread.java:1076)
sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce
ssorImpl.java:37)
java.lang.reflect.Method.invoke(Method.java:611)

Knowing this I further reviewed the SystemOut.log to see where the JCR
web module gets loaded during startup....it should begin like this...

SRVE0169I: Loading Web Module: JCRContentRepository.

Your startup does not have this. This prompted me to review the
deployment.xml from the JavaContentRepository application directory at
this location...

Portal8/wp_profile/config/cells/C001389391Cell/applications/JavaContentR
epository.ear/deployments/JavaContentRepository/deployment.xml

The contents show the following...

<targetMappings xmi:id="DeploymentTargetMapping_1335003370698"
enable="false" target="ServerTarget_1335003370698"/>

The enable=false means that you have this application set to not
autostart. Because of this it is not starting during Portal startup
and therefore is not available when the config task attempts to
communicate with it during the upgrade...and therefore causes the
problem.

RESOLVING THE PROBLEM
Please make the following change in the WAS Admin Console...
Applications > WebSphere enterprise applications >
JavaContentRepository > Target specific application status > Check the
box for the WebSphere_Portal server > Click Enable Auto Start > Save
changes > restart Portal

After making this change please attempt the CF upgrade again.

Question: Error TASK001X while upgrading Portal 8.0.0.1 to 8.0.0.1 CF14 during import-nodes sub-task  Error TASK001X while upgrading Portal 8.0.0.1 to 8.0.0.1 CF14 during import-nodes sub-task

Answer:
Please make the following change in the WAS Admin Console...
Applications > WebSphere enterprise applications >
JavaContentRepository > Target specific application status > Check the
box for the WebSphere_Portal server > Click Enable Auto Start > Save
changes > restart Portal

After making this change please attempt the CF upgrade again.


IBM SPSS Student Version and Graduate Pack Resources - United States SPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)

QUESTION
 Where do I get support for IBM SPSS Student Version or Graduate Pack software?

ANSWER
Step 1:
For installation & licensing issues on Student version and Graduate pack, contact your vendor.

 * Hearne [http://www.hearne.software/Software/SPSS-Grad-Packs-for-Students-by-IBM/FAQ]
 * On the Hub [http://onthehub.com/]
 * StudentDiscounts.com [http://studentdiscounts.com/contact-us.aspx]
 * JourneyEd [https://www.journeyed.com/contact]
 * thinkEDU [https://thinkedu.desk.com/]
 * Studica [http://www.studica.com/technical-support]

Cross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version

Question:
How do I transfer my SPSS 24 license key to a new computer? I need to transfer my SPSS 24 license key to a new computer. I was able to download IBM® SPSS® Statistics Standard GradPack 24 for Windows (12-Mo Rental) onto the new computer, but every time I put in the activation code, I am met with this error message:

Authorization failed.: You are not allowed to generate any more new licenses.
End Of Transaction.
No additional authorizations are permitted on this code.
What should I do?

This dW Answers question is about an IBM document with the Title:
SPSS Student Version and Graduate Pack Resources

Answer: For installation & licensing issues on Student version and Graduate pack, contact your vendor.


IBM Tivoli Integrated Portal hangs because of Argus java.lang.OutOfMemory. - United States cacheTime; config.xml; Argus; TIP cache; TIPL2CONF; TIPL2PERF TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 Argus stores it's role authorizations in memory cache, and is not cleaned out unless the TIP is restarted. The "cacheTime" variable controls this, which is set to -1 by default. If the number of TIP roles is high, it can cause Java OOM errors.

SYMPTOM
TIP hangs. SystemOut.log file shows Java.lang.OutOfMemoryError:

[10/2/13 9:27:54:838 CDT] 0000002a webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E:
[Servlet Error]-[/secure/isclite/tiles/nop.jsp]: java.lang.OutOfMemoryError: Java heap space at java.lang.Object.clone(Native Method)

CAUSE
By default, the ARGUS cache will not get cleaned up unless the TIP server is restarted. This normally will give the system good runtime performance. However, in cases where a large number of user/role mappings are defined, the system may run into Java memory issues causing Java OutOfMemory outages.

The cacheTime we are talking about here is Argus cache. The is used for the way the role authorizations are stored in memory by Argus and nothing related to LDAP or SSO. The Argus cache time by default we ship with in TIP is -1 which means the cache will not get cleaned up till we re-start the server.

Error from the <TIP_HOME>/profiles/TIPProfile/logs/server1/SystemOut.log

[10/2/13 9:27:54:838 CDT] 0000002a webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E:
[Servlet Error]-[/secure/isclite/tiles/nop.jsp]: java.lang.OutOfMemoryError: Java heap space at java.lang.Object.clone(Native Method)

ENVIRONMENT
all environments

DIAGNOSING THE PROBLEM
Java heapdump files will be created in the <TIP_HOME>/profiles/TIPProfile directory.

heapdump.20131022.144244.20034001.phd

The Systemout.log will have have errors similar to this:

[10/2/13 9:27:54:838 CDT] 0000002a webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E:
[Servlet Error]-[/secure/isclite/tiles/nop.jsp]: java.lang.OutOfMemoryError: Java heap space at java.lang.Object.clone(Native Method)

Using the memory heap dump analysis shows that Argus is the problem, specifically the instance shown inside the red line in the output of the Java memory analyzer below:

[/support/docview.wss?uid=swg21657452&aid=1] [/support/docview.wss?uid=swg21657452&aid=1]

You can also check the cacheTime variable in the <TIP_HOME>/profiles/TIPProfile/config/cells/TIPCell/commonauthz/config.xml file to confirm if it's set to "-1", which means the Argus cache will not get cleaned up unless the TIP server is restarted.

RESOLVING THE PROBLEM
The cacheTime value in config.xml is in milliseconds. TIP is shipped with the initial value of -1, which means the Argus cache will not be cleared out unless TIP restart. To resolve this issue you need to configure 'cacheTime' to non -1 value. Initially we suggest setting the value to 1200000, which is 20 minutes. After the change you will have to restart the TIP server, normally server1.

NOTE: The cacheTime variable was added in TIP version 2.2.0.0.

Question: How can I configure TIP to clear the ARGUS cache without having to do a system restart? Argus stores it's role authorizations in memory cache, and is not cleaned out unless the TIP is restarted. The "cacheTime" variable in the configFile.xml configuration file controls this, which is set to -1 by default. If the number of TIP roles is high, it can cause Java OOM errors.

Answer: To resolve this issue you need to configure 'cacheTime' to non -1 value. Initially we suggest setting the value to 1200000, which is 20 minutes. After the change you will have to restart the TIP server, normally server1.


IBM Security Bulletin: IBM MQ and IBM MQ Appliance Shared memory leak caused by MQ applications using dynamic queues. (CVE-2017-1283) - United States  SECURITY BULLETIN

SUMMARY
 Shared memory leak caused by MQ applications using dynamic queues.

VULNERABILITY DETAILS
CVEID: CVE-2017-1283 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1283]
DESCRIPTION: IBM WebSphere MQ could allow an authenticated user to cause a shared memory leak by MQ applications using dynamic queues, which can lead to lack of resources for other MQ applications.
CVSS Base Score: 3.1
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/125144 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125144] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L)

AFFECTED PRODUCTS AND VERSIONS
IBM MQ V8
IBM MQ 8.0.0.0 - 8.0.0.6 maintenance levels
IBM MQ Appliance V8
IBM MQ Appliance 8.0.0.0 - 8.0.0.6 maintenance levels
IBM MQ V9
IBM MQ 9.0.0.0 - 9.0.0.1 maintenance levels
IBM MQ V9 CD
IBM MQ 9.0.1 - 9.0.3 releases
IBM MQ Appliance V9 CD
IBM MQ Appliance 9.0.1 - 9.0.3

REMEDIATION/FIXES
IBM MQ V8

Apply Fix Pack 8.0.0.7 [https://www-01.ibm.com/support/docview.wss?uid=swg22005832]
IBM MQ Appliance V8
Apply Fix Pack 8.0.0.7 for MQ Appliance [https://www-01.ibm.com/support/docview.wss?uid=swg22005832]
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 IBM MQ 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348]
IBM MQ Appliance V9 CD
Upgrade to IBM MQ Appliance 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348]

WORKAROUNDS AND MITIGATIONS
None.

GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
 Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.

REFERENCES
Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]
On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]

RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]

CHANGE HISTORY
 14 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.

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.

Question: Security Bulletin: IBM MQ and IBM MQ Appliance Shared memory leak caused by MQ applications using dynamic queues (CVE-2017-1283) I need to understand details regarding Security Bulletin: IBM MQ and IBM MQ Appliance Shared memory leak caused by MQ applications using dynamic queues (CVE-2017-1283). Where can I find this information?

Answer:
CVEID: CVE-2017-1283 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1283]
DESCRIPTION: IBM WebSphere MQ could allow an authenticated user to cause a shared memory leak by MQ applications using dynamic queues, which can lead to lack of resources for other MQ applications.
CVSS Base Score: 3.1
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/125144 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125144] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L)


IBM Multiple logins using the same user ID - United States ConcurrentModificationException; log in; login; multiple; userid; multiple login TECHNOTE (FAQ)

QUESTION
 "ConcurrentModificationException" and other errors may occur if the same user id is logged in to IBM WebSphere Portal multiple times.

ANSWER
WebSphere Portal has no built-in mechanism or configuration setting to limit the number of times a user id may log in. Unexpected behavior may occur if the same id is logged in more than once and this is not supported.

"ConcurrentModificationException" and other errors may be logged.

Most of the related issues were resolved in WebSphere Portal 5.1. However, you may still encounter exceptions or side-effects if you access the Portal in multiple browser windows using the same user id, whether or not the authentication requests take place on separate physical hosts.

It may be possible to prevent multiple logins by writing custom "tracking code." Contact IBM Services for assistance to undertake such a project. WebSphere Portal Development does not have any sample code.

If you wish to write your own code, some of the issues to be aware of are (this is not an inclusive list):

-- Multiple logins may take place on different nodes in a cluster. This means some cluster-wide mechanism would have to be in place to keep track of the logged-in users. Look at the WebSphere Application Server DistributedMap interface.

-- There should be a fail-safe way to track user logout (explicit logout and session timeout). Using a session listener might be a possibility.

-- If a user closes the browser without logging out, that user must wait for a session timeout before logging in again. Otherwise, there should be a "force simultaneous login" option in the login user interface.

For load testing, use unique user ids or virtual users.

RELATED INFORMATION
 Portal 6.1/7.0: Authentication Filters [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/index.jsp?topic=/com.ibm.wp.ent.doc_v615/admin/adauthflt.html]
Portal 6.1: Custom Login Portlet [https://www.ibm.com/support/docview.wss?uid=swg21358508]
Restricting Multiple Sessions [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Restricting_Multiple_Sessions_in_WebSphere_Portal]

Cross reference information Segment Product Component Platform Version Edition Organizational Productivity- Portals & Collaboration WebSphere Portal End of Support Products General AIX, HP-UX, Linux, Solaris, Windows 7.0, 6.1.5, 6.1, 6.0, 5.1

Question: Can Portal prevent the usage of simultaneous logins with the same userID? Is it possible for WebSphere Portal to limit the usage of a userID to one authenticated session as a time? In other words, prevent authenticating to Portal as "user1" from one browser and then simultaneously authenticating to Portal again as "user1" from another browser?

Answer:
WebSphere Portal has no built-in mechanism or configuration setting to limit the number of times a user id may log in. Unexpected behavior may occur if the same id is logged in more than once and this is not supported.

"ConcurrentModificationException" and other errors may be logged.

Most of the related issues were resolved in WebSphere Portal 5.1. However, you may still encounter exceptions or side-effects if you access the Portal in multiple browser windows using the same user id, whether or not the authentication requests take place on separate physical hosts.

It may be possible to prevent multiple logins by writing custom "tracking code." Contact IBM Services for assistance to undertake such a project. WebSphere Portal Development does not have any sample code.

If you wish to write your own code, some of the issues to be aware of are (this is not an inclusive list):

-- Multiple logins may take place on different nodes in a cluster. This means some cluster-wide mechanism would have to be in place to keep track of the logged-in users. Look at the WebSphere Application Server DistributedMap interface.

-- There should be a fail-safe way to track user logout (explicit logout and session timeout). Using a session listener might be a possibility.

-- If a user closes the browser without logging out, that user must wait for a session timeout before logging in again. Otherwise, there should be a "force simultaneous login" option in the login user interface.

For load testing, use unique user ids or virtual users.