Fixes are available
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
The cr_db.mssql file generated for SQL Server - there is no way for a user to specify the location of the database file during the configuration. The only way is to generate the SQL file and manually edit it to point it to a different location. It always points it to "Program Files"
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V7.0 users * * who configure Common Event Infrastructure * * ( CEI ) with Microsoft SQL Server database. * **************************************************************** * PROBLEM DESCRIPTION: The automatic configuration process * * of Common Event Infrastructure with * * Microsoft SQL Server database * * generates the scripts for database * * creation that contains paths * * for the database files based on a * * predefined location that cannot be * * changed using the automatic * * configuration process. * **************************************************************** * RECOMMENDATION: * **************************************************************** The automatic process of configuring the Common Event Infrastructure (CEI) with Microsoft SQL Server database does not support consumers specifying a custom path where the Common Event Infrastructure database files are to be located. By default the base location for storing the files on the Microsoft SQL Server is ¢â‚¬ “c:\program files\ibm\event ¢â‚¬ situations when consumers do want to specify a custom location where database files should be stored. The scope for providing the fix is to implement a feature to resolve a usability issue and to extend the customization of the configuration AdminTask.
Problem conclusion
The automatic configuration process with a Microsoft SQL Server database has been changed by adding to the configEventServiceSQLServerDB configuration Admin Task a new optional parameter -dbPath that will be used to specify the custom location for the Common Event Infrastructure database files. The supported path formats (on Windows systems) are shown as in the following examples: c:\temp, c:\temp\, c:/temp, c:/temp/ , c:\test with spaces , c:\test with spaces\ , c:/test with spaces, c:/test with spaces/ (to note that locations containing spaces should be specified within double quotes). If the -dbPath is specified the user is required to specify its value as well; otherwise an error will be raised. If the parameter is not specified the AdminTask will work as before implementing the feature: database files are created using the fixed base location ¢â‚¬ “c:\program files\ibm\event The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.13. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
The consumers do have a work around available that allows them to create the database files in a custom location. This can be achieved by choosing to delay the database and database objects creation by specifying the ¢â‚¬âœcreateDB false for th AdminTask and to tailor the content of the cr_db.mssql file. After that the consumer can proceed to execute the database creation and configuration by executing the cr_event_mssql.bat and provide the requested parameters.
Comments
APAR Information
APAR number
PM16650
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-06-16
Closed date
2010-07-15
Last modified date
2010-07-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
24 October 2021