Feature Pack 7 or laterWebSphere Commerce Developer

Database connection validation results sample

The following sample log output details the information that is retrieved, tested, and validated by the database connection validation utility. This sample output is for a WebSphere Commerce Developer environment that runs on the Windows operating system with a Derby database.

The following code is a snippet of a sample wcsDbValidation.log file that is generated when the database connection validation utility is run separate from any other utility or process.

   Buildfile: W:\WCDE_I~1\components\common\xml\databaseValidation.xml
   
   databaseValidation_toolkit:
   
   databaseValidation_server:
   
   GenerateANTProperties:
   [WcsDbValidation]   
   [WcsDbValidation]   
   [WcsDbValidation] ***************************************************************
   [WcsDbValidation] Start time = 2013-06-04 16:06:17.305
   [WcsDbValidation] >>>>>>>>>> System <<<<<<<<<<
1[WcsDbValidation] OS information
   [WcsDbValidation]   OS name = Windows 7
   [WcsDbValidation]   OS version = 6.1 build 7601 Service Pack 1
   [WcsDbValidation]   OS architecture = x86
   [WcsDbValidation]   
2[WcsDbValidation] Java information
   [WcsDbValidation]   Java vendor = IBM Corporation
   [WcsDbValidation]   Java version = 1.6.0
   [WcsDbValidation]   Java specification version = 1.6
   [WcsDbValidation]   Java home = W:\SDP\runtimes\base_v7\java\jre
   [WcsDbValidation]   Java class version = 50.0
   [WcsDbValidation]   Classpath = W:\WCDE_I~1\lib\derby.jar;W:\WCDE_I~1\wasprofile\properties;
                       W:\SDP\runtimes\base_v7\properties;W:\SDP\runtimes\base_v7\lib\startup.jar;W:
                       \SDP\runtimes\base_v7\lib\bootstrap.jar;W:\SDP\runtimes\base_v7/lib/lmproxy.jar;W:
                       \SDP\runtimes\base_v7/lib/urlprotocols.jar;W:\SDP\runtimes\base_v7\java\lib\tools.jar
   [WcsDbValidation]   
3[WcsDbValidation] User information
   [WcsDbValidation]   User name = Administrator
   [WcsDbValidation]   User home = C:\Users\IBM_ADMIN
   [WcsDbValidation]   User directory = W:\WCDE_INT70\bin
   [WcsDbValidation]   User language = en
   [WcsDbValidation]   User timezone = America/New_York
   [WcsDbValidation]   
4[WcsDbValidation] Memory information
   [WcsDbValidation]   Maximum heap allocation =       1.60 gigabytes
   [WcsDbValidation]   Current heap allocation =      10.56 megabytes
   [WcsDbValidation]   
5[WcsDbValidation] WebSphere Commerce information
   [WcsDbValidation]   wcUserInstallDir = W:\WCDE_I~1
   [WcsDbValidation]     wcUserInstallDir is readable = true
   [WcsDbValidation]   instanceName = demo
   [WcsDbValidation]   instanceName directory = W:\WCDE_I~1\instances\demo
   [WcsDbValidation]     instanceName directory is readable = false
   [WcsDbValidation]   loggerconfigfile = W:\WCDE_I~1/xml/loader/WCALoggerConfig.xml
   [WcsDbValidation]     loggerconfigfile is readable = true
   [WcsDbValidation]   errordirectory = W:\WCDE_I~1/logs
   [WcsDbValidation]     errordirectory is readable = true
   [WcsDbValidation] >>>>>>>>>> System <<<<<<<<<<
   [WcsDbValidation]   
   [WcsDbValidation] Database validation start time = 2013-06-04 16:06:17.334
   [WcsDbValidation]   
   [WcsDbValidation] >>>>>>>>>> Database <<<<<<<<<<
6[WcsDbValidation] Input Parameters
   [WcsDbValidation]   dbType = cloudscape
   [WcsDbValidation]   dbHostname missing.
   [WcsDbValidation]   dbName = W:\WCDE_I~1\db\mall
   [WcsDbValidation]   portnumber missing.
   [WcsDbValidation]   dbUserName = APP
   [WcsDbValidation]   dbUserPassword = **************
   [WcsDbValidation]   dbaName = APP
   [WcsDbValidation]   dbaPassword = **************
   [WcsDbValidation]   schemaName = APP
   [WcsDbValidation]   jdbcDriver = org.apache.derby.jdbc.EmbeddedDriver
   [WcsDbValidation]   jdbcURL = jdbc:derby:W:\WCDE_I~1\db\mall
   [WcsDbValidation]   
7[WcsDbValidation] Connection Testing
   [WcsDbValidation]   Test with supplied jdbcDriver
   [WcsDbValidation]   jdbcDriver = org.apache.derby.jdbc.EmbeddedDriver found.
   [WcsDbValidation]     Location = file:/W:/WCDE_INT70/lib/derby.jar!/org/apache/derby/jdbc/EmbeddedDriver.class
   [WcsDbValidation]   
   [WcsDbValidation]   Test connection with supplied jdbcURL using dbUserName and dbUserPassword.
   [WcsDbValidation]   Connection successful with the following parameters :
   [WcsDbValidation]     jdbcURL = jdbc:derby:W:\WCDE_I~1\db\mall
   [WcsDbValidation]     dbType = cloudscape; dbUserName = APP; dbUserPassword = **************
   [WcsDbValidation]       Connection class name = org.apache.derby.impl.jdbc.EmbedConnection40
   [WcsDbValidation]       Database product name = Apache Derby
   [WcsDbValidation]       Database product version = 10.3.3.1 - (1056613)
   [WcsDbValidation]       Database major version = 10
   [WcsDbValidation]       Database minor version = 3
   [WcsDbValidation]       Database driver name = Apache Derby Embedded JDBC Driver
   [WcsDbValidation]       Database driver version = 10.3.3.1 - (1056613)
   [WcsDbValidation]       Database driver major version = 10
   [WcsDbValidation]       Database driver minor version = 3
   [WcsDbValidation]     WebSphere Commerce features:
   [WcsDbValidation]       Feature name = BASE. VRMF = 7.0.0.8
   [WcsDbValidation]       Feature name = foundation. VRMF = 7.0.7.0
   [WcsDbValidation]       Feature name = store-enhancements. VRMF = 7.0.7.0
   [WcsDbValidation]       Feature name = content-version. VRMF = 7.0.7.0
   [WcsDbValidation]       Feature name = location-services. VRMF = 7.0.7.0
   [WcsDbValidation]       Feature name = management-center. VRMF = 7.0.7.0
   [WcsDbValidation]   
8[WcsDbValidation]   Test other possible drivers and connections
   [WcsDbValidation]   jdbcDriver = org.apache.derby.jdbc.ClientDriver not found.
   [WcsDbValidation]     Class not found : org.apache.derby.jdbc.ClientDriver
   [WcsDbValidation]   
   [WcsDbValidation] >>>>>>>>>> Database <<<<<<<<<<
   [WcsDbValidation] End time = 2013-06-04 16:06:18.027
   [WcsDbValidation] ***************************************************************
   [WcsDbValidation]   
   [WcsDbValidation]   
   
   BUILD SUCCESSFUL
   Total time: 2 seconds
Where
System related information
1 - OS information
Information about the operating system. This information includes the name, version, and architecture of the operating system.
2 - Java information
Information about the Java Runtime Environment. The Java version must be 1.6.0.
3 - User information
Information about the WebSphere Commerce user that is running the database connection validation utility.
4 - Memory information
The allocated memory. Ensure that sufficient memory is allocated for the utility to complete successfully.
5 - WebSphere Commerce information
Information about the WebSphere Commerce instance, including the instance name, installation directory, and logging configuration file.
Database connection information
6 - Input Parameters
The input parameters for the WebSphere Commerce database that are used to complete database-related processes for WebSphere Commerce utilities.
7 - Connection Testing
Information about the JDBC driver and class are output in this section. If a successful database connection is established, the parameters that were used to establish the connection are included in this section.
When the log level is set to 2 or higher, the following log information is also recorded:
[WcsDbValidation] WebSphere Commerce features:
[WcsDbValidation] Feature name = BASE. VRMF = 7.0.0.8
[WcsDbValidation] Feature name = foundation. VRMF = 7.0.7.0
[WcsDbValidation] Feature name = store-enhancements. VRMF = 7.0.7.0
[WcsDbValidation] Feature name = content-version. VRMF = 7.0.7.0
[WcsDbValidation] Feature name = location-services. VRMF = 7.0.7.0
[WcsDbValidation] Feature name = management-center. VRMF = 7.0.7.0 
The extra log information indicates the WebSphere Commerce schema level and the features that are enabled for the WebSphere Commerce instance. For instance, if the value for BASE. VRMF parameter is 7.0.0.8, the WebSphere Commerce schema is on Fix Pack 8 level.
8 - Test other possible drivers and connections
Information about alternate JDBC drivers that are tested and validated by the database connection validation utility. In this sample, no alternate JDBC driver and class are found.