Installing the Viewpoint Development Portal 14.00

Extensibility
Extensibility covers the mechanisms by which you, as the user or developer, can extend the functionality of the Teradata Database, for example with the use of User Defined Functions, or UDFs.
Teradata Employee

Installing the Viewpoint Development Portal 14.00

This tutorial steps through the process to install the Teradata Viewpoint Development Portal, a cut-down version of Viewpoint, on your local desktop machine. These instructions are specifically for Windows, though the PDK has been validated to work on Mac OS X, Linux, and Solaris.

Step 1: Install Prerequisite Software

Java 1.5 SDK

Download and install "Java 2 Platform, Standard Edition 5.0". You'll want the JDK 5.0 without the NetBeans IDE or the Java EE. After installing the Java SDK, add a JAVA_HOME environment variable that points to the installation location of the JDK. Don't forget to add the Java JDK bin directory to the Windows PATH environment variable, as described in the Java installation instructions.

Ant 1.7.x

Download and install Ant. After installation, add Ant's bin directory to your Windows PATH environment variable.

PostgreSQL 8.1.x to 8.3.x

Download PostgreSQL and run the installer.

  1. On the "Service configuration" screen, either choose a secure password or accept the offer to allow the system to replace your weak password with a secure auto-generated one. If you use a weak password, the install will fail later with the inability to create the user.
    • Use the default superuser name of postgres and enter a password. Be sure to remember the password for this superuser!
    • If you want to connect to the database from another system, check the box "Accept connections on all addresses, not just localhost".
    • If there are separate Encoding fields for Server and Client they should both be SQL_ASCII.
    • If you change the PostgreSQL port number, you will need to remember the new port as well.
  2. Uncheck "Launch Stack Builder at exit" on the last install screen.

Step 2: Setting Up the PostgreSQL Database

  1. Under the folder PostgreSQL is installed in, edit data\postgresql.conf:
    • Under QUERY TUNING, set constraint_exclusion = on and remove the "#" from the beginning of the line.
  2. Open a command prompt and navigate to the directory PostgreSQL is installed in, then enter these commands:
    cd bin
    createlang --username=postgres --password=<SERVICE_ACCOUNT_PASSWORD> plpgSQL template1

    Enter the PostgreSQL superuser password when prompted. If you receive a warning that the language plpgSQL already exists, you can ignore it and proceed.
  3. Run "pgAdmin III" from the Start menu under PostgreSQL.
  4. Double-click "PostgreSQL Database Server 8.x (localhost)" to connect, and enter the superuser password.
  5. Right-click on Login Roles, and select New Login Role...

  6. Create a role named viewpoint that can create database objects.



    Be sure to remember this password! This is the password that will be used for setting up the Teradata Viewpoint Portal in the following steps.
  7. Repeat Steps 5 and 6 to create another role name cam.  Be sure to remember the password also.
  8. Create a database named lportal with owner viewpoint 

  9. Repeat Step 8 to create databases named dcsdb, td_portal, and td_portlets (all with owner viewpoint).
  10. Repeat Step 8 to create a database named cam, with owner cam.
  11. Create a schema under dcsdb called tasm with owner viewpoint.  You can do this by expanding the tree for dcsdb created in Step 9.  Right click on Schemas and select New Schema.  Enter tasm as the Name and select viewpoint as the Owner.  Click OK to save.
  12. Repeat Step 11 and create another schema under dcsdb called tasmwd.
  13. Repeat Step 11 and create another schema under dcsdb called config.
  14. Repeat Step 11 and create another schema uder cam called config with owner cam.

Step 3: Unzip the Teradata Viewpoint PDK

  1. Download the Teradata Viewpoint PDK.
  2. Unzip the file, creating a folder called tdpdk-xx.xx.xx.xx, where the xx's indicate the version number. The rest of this tutorial assumes that this folder is located at C:\tdpdk-xx.xx.xx.xx, but it can be located elsewhere if desired.

Step 4: Configuring the Teradata Viewpoint Portal 

While configuring the Teradata Viewpoint Portal, you might need to modify JDBC URLs for the PostgreSQL database. If the PostgreSQL database is running on your local machine with the default port(5432), you do not need to make any changes to these URLs.

If the database is running on a separate system, you need to replace "localhost" with the name of the database system. If you are using a custom PostgreSQL port number, replace "5432" with the custom port number.

Important: Do not make any other changes to these URLs.

Edit C:\tdpdk-xx.xx.xx.xx\viewpoint-portal\conf\server.xml

<!-- DCS datasource -->
<Resource name="jdbc/dcs"
auth="Container"
driverClass="org.postgresql.Driver"

jdbcUrl="jdbc:postgresql://localhost:5432/dcsdb"
user="viewpoint"
password="TDv1i2e3w4"

maxPoolSize="100"
minPoolSize="1"
acquireIncrement="1"
maxIdleTime="120"
factory="org.apache.naming.factory.BeanFactory"
type="com.mchange.v2.c3p0.ComboPooledDataSource"/>

<!-- TD Portlets datasource -->
<Resource name="jdbc/td_portlets"
auth="Container"
driverClass="org.postgresql.Driver"

jdbcUrl="jdbc:postgresql://localhost:5432/td_portlets"
user="viewpoint"
password="TDv1i2e3w4"

maxPoolSize="100"
minPoolSize="1"
acquireIncrement="1"
maxIdleTime="120"
factory="org.apache.naming.factory.BeanFactory"
type="com.mchange.v2.c3p0.ComboPooledDataSource"/>

<!-- TD Portal datasource -->
<Resource name="jdbc/td_portal"
auth="Container"
driverClass="org.postgresql.Driver"

jdbcUrl="jdbc:postgresql://localhost:5432/td_portal"
user="viewpoint"
password="TDv1i2e3w4"

maxPoolSize="100"
minPoolSize="1"
acquireIncrement="1"
maxIdleTime="120"
factory="org.apache.naming.factory.BeanFactory"
type="com.mchange.v2.c3p0.ComboPooledDataSource" />

<!-- cam datasource -->
<Resource name="jdbc/cam"
auth="Container"
driverClass="org.postgresql.Driver"
jdbcUrl="jdbc:postgresql://%{activeDatabaseHost}:5432/cam"
user="cam"
password="TDc1a2m3"
maxPoolSize="100"
minPoolSize="1"
acquireIncrement="1"
maxIdleTime="120"
factory="org.apache.naming.factory.BeanFactory"
type="com.teradata.viewpoint.cluster.datasource.c3p0.C3p0PromotionAwareDataSource"/>
  1. You need to provide the portal with the database address and port number, and the PostgreSQL username and password you set up earlier.
    <!-- Datasource used by the Liferay portal itself -->
    <Resource name="jdbc/LiferayPool"
    auth="Container"
    driverClass="org.postgresql.Driver"

    jdbcUrl="jdbc:postgresql://localhost:5432/lportal"
    user="viewpoint"
    password="TDv1i2e3w4"

    maxPoolSize="100"
    minPoolSize="1"
    acquireIncrement="1"
    maxIdleTime="120"
    factory="org.apache.naming.factory.BeanFactory"
    type="com.mchange.v2.c3p0.ComboPooledDataSource"/>

  2. Next, configure the datasource for the Data Collection Service. If you want to connect to an existing DCS database, enter the DCS database login details here. Otherwise, make the same changes as above.
  3. You also need to modify the TD Portlets datasource. As before, provide the PostgreSQL system name and port, along with the username and password.
  4. Repeat Step 3 for the TD Portal datasource.
  5. You also need to modify the cam datasource. Make sure the PostgreSQL system name and port, along with the username and password is correct.

Edit the file C:\tdpdk-xx.xx.xx.xx\viewpoint-portal\setup\config\viewpoint.properties

You need to uncomment (remove the # at the beginning of) several lines in viewpoint.properties. viewpoint.db.host and viewpoint.db.port only need to be uncommented if the database is not on your local system or if you're using a custom port for the database. viewpoint.db.username and viewpoint.db.password should be uncommented and modified to contain your PostgreSQL username and password.

viewpoint.db.host=localhost
viewpoint.db.port=5432

#lportal.db.name=lportal
#tdportal.db.name=td_portal
#tdportlets.db.name=td_portlets
#dcs.db.name=dcsdb

viewpoint.db.username=viewpoint
viewpoint.db.password=TDv1i2e3w4

Step 5: Running the Viewpoint setup script

  • Create an environment variable CATALINA_HOME that points to the path for the Teradata Viewpoint Portal (C:\tdpdk-xx.xx.xx.xx\viewpoint-portal).
  • Open a command prompt and execute the following commands:
C:
cd \tdpdk-xx.xx.xx.xx\viewpoint-portal\setup\bin
setup.bat
  • If you do not have an existing DCS database to connect to, you will need to run the following script:
C:
cd \tdpdk-xx.xx.xx.xx\viewpoint-portal\setup\bin
setup-dcs.bat

Step 6: Start Viewpoint

C:
cd \tdpdk-xx.xx.xx.xx\viewpoint-portal\bin
startup.bat

Step 7: Login to Viewpoint

Troubleshooting

    1. To start Viewpoint, open a command prompt and execute the following commands:
    2. Allow the Viewpoint to start up fully (log output completes) before continuing on to the next step.
    1. Start a web browser and connect to the portal using a URL as follows:
      • If you're accessing the portal from the system it's installed on with the default settings, the portal URL is http://localhost:8080.
      • If the Teradata Viewpoint Portal server is not running on your local machine, or if you've modified the port number, the URL is always in the form http://machinename:portnumber (replace machinename with the machine name and portnumber with the port number).
    2. Log in to the portal using username "admin" with the default password "teradata"(without the quotation marks).
    3. It is recommended that you change this password after logging in by clicking on Profile in the top right of the screen.
    • If your Viewpoint Portal does not start up, please go back through each of the steps to ensure you haven't missed anything.
    • Make sure you have the correct versions of Java, Ant, and Postgres installed.
    • Check the viewpoint.log or the output from the command window to see if there are any errors.  Search the Teradata Developer Exchange Viewpoint forums for any resolutions to the problems.
    • If you have any additional questions or comments, please post them on the Teradata Developer Exchange Viewpoint forums.
Tags (2)
1 REPLY

Re: Installing the Viewpoint Development Portal 14.00

I have tried to install Viewpoint Development portal 14.0 on a laptop running Windows 7 Ultimate (Service pack 1) - 32 bits system.
I have completed steps 1-4 successfully but step 5 gave some problems - see below.
I would appreciate some help in understanding the problem and I would also like to get a solution to it.

C:\tdpdk-14.00.00.00\viewpoint-portal\setup\bin>setup.bat
C:\tdpdk-14.00.00.00\viewpoint-portal
2012-09-20 23:43:03,980 DEBUG - Configured logging with file: config\setup-log.config.xml
2012-09-20 23:43:03,980 DEBUG - Configured logging with file: config\setup-log.config.xml
2012-09-20 23:43:05,488 INFO - STARTING DATABASE SCHEMA MIGRATION!
2012-09-20 23:43:05,488 INFO - STARTING DATABASE SCHEMA MIGRATION!
2012-09-20 23:43:05,493 DEBUG - Initializing schema migration context classpath:com/teradata/viewpoint/database/changesets/tdportal/tdportalSchemaMigration-context.xml
2012-09-20 23:43:05,493 DEBUG - Initializing schema migration context classpath:com/teradata/viewpoint/database/changesets/tdportal/tdportalSchemaMigration-context.xml
2012-09-20 23:43:05,703 DEBUG - Initializing Migrator object for change log classpath:com/teradata/viewpoint/database/changesets/tdportal/tdportal.changeLog-master.xml
2012-09-20 23:43:05,703 DEBUG - Initializing Migrator object for change log classpath:com/teradata/viewpoint/database/changesets/tdportal/tdportal.changeLog-master.xml
2012-09-20 23:43:06,131 DEBUG - The context resolver threw an exception!
org.postgresql.util.PSQLException: ERROR: relation "tdportal_info" does not exist
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1548)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1316)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:351)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:344)
at com.teradata.migrator.SpringMigrator.resolveContexts(SpringMigrator.java:224)
at com.teradata.migrator.SpringMigrator.afterPropertiesSet(SpringMigrator.java:393)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1417)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:580)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
at org.springframework.context.support.FileSystemXmlApplicationContext.(FileSystemXmlApplicationContext.java:140)
at com.teradata.migrator.utility.SchemaMigrator.createApplicationContext(SchemaMigrator.java:391)
at com.teradata.migrator.utility.SchemaMigrator.migrate(SchemaMigrator.java:212)
at com.teradata.migrator.utility.SchemaMigrator.main(SchemaMigrator.java:146)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.teradata.commons.bootstrap.Bootstrap.main(Bootstrap.java:166)
2012-09-20 23:43:06,131 DEBUG - The context resolver threw an exception!
org.postgresql.util.PSQLException: ERROR: relation "tdportal_info" does not exist
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1548)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1316)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:351)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:344)
at com.teradata.migrator.SpringMigrator.resolveContexts(SpringMigrator.java:224)
at com.teradata.migrator.SpringMigrator.afterPropertiesSet(SpringMigrator.java:393)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1417)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:580)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
at org.springframework.context.support.FileSystemXmlApplicationContext.(FileSystemXmlApplicationContext.java:140)
at com.teradata.migrator.utility.SchemaMigrator.createApplicationContext(SchemaMigrator.java:391)
at com.teradata.migrator.utility.SchemaMigrator.migrate(SchemaMigrator.java:212)
at com.teradata.migrator.utility.SchemaMigrator.main(SchemaMigrator.java:146)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.teradata.commons.bootstrap.Bootstrap.main(Bootstrap.java:166)
2012-09-20 23:43:06,279 DEBUG - The table does not exist for context resolver query. Running a clean installation of schema.
2012-09-20 23:43:06,279 DEBUG - The table does not exist for context resolver query. Running a clean installation of schema.
2012-09-20 23:43:06,311 DEBUG - Marking SpringMigrator classpath:com/teradata/viewpoint/database/changesets/tdportal/tdportal.changeLog-master.xml for rollback at Thu Sep 20 23:43:06 CEST 2012
2012-09-20 23:43:06,311 DEBUG - Marking SpringMigrator classpath:com/teradata/viewpoint/database/changesets/tdportal/tdportal.changeLog-master.xml for rollback at Thu Sep 20 23:43:06 CEST 2012
2012-09-20 23:43:07,454 DEBUG - Found schema migration bean(s) for context classpath:com/teradata/viewpoint/database/changesets/tdportal/tdportalSchemaMigration-context.xml
2012-09-20 23:43:07,454 DEBUG - Found schema migration bean(s) for context classpath:com/teradata/viewpoint/database/changesets/tdportal/tdportalSchemaMigration-context.xml
2012-09-20 23:43:07,459 DEBUG - Initializing schema migration context classpath:com/teradata/viewpoint/database/changesets/lportal/lportalSchemaMigration-context.xml
2012-09-20 23:43:07,459 DEBUG - Initializing schema migration context classpath:com/teradata/viewpoint/database/changesets/lportal/lportalSchemaMigration-context.xml
2012-09-20 23:43:07,986 DEBUG - Initializing Migrator object for change log classpath:com/teradata/viewpoint/database/changesets/lportal/lportal.changeLog-master.xml
2012-09-20 23:43:07,986 DEBUG - Initializing Migrator object for change log classpath:com/teradata/viewpoint/database/changesets/lportal/lportal.changeLog-master.xml
2012-09-20 23:43:08,232 DEBUG - The context resolver threw an exception!
org.postgresql.util.PSQLException: ERROR: relation "tdportal_info" does not exist
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1548)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1316)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:351)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:344)
at com.teradata.migrator.SpringMigrator.resolveContexts(SpringMigrator.java:224)
at com.teradata.migrator.SpringMigrator.afterPropertiesSet(SpringMigrator.java:393)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1417)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:580)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
at org.springframework.context.support.FileSystemXmlApplicationContext.(FileSystemXmlApplicationContext.java:140)
at com.teradata.migrator.utility.SchemaMigrator.createApplicationContext(SchemaMigrator.java:391)
at com.teradata.migrator.utility.SchemaMigrator.migrate(SchemaMigrator.java:212)
at com.teradata.migrator.utility.SchemaMigrator.main(SchemaMigrator.java:146)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.teradata.commons.bootstrap.Bootstrap.main(Bootstrap.java:166)
2012-09-20 23:43:08,232 DEBUG - The context resolver threw an exception!
org.postgresql.util.PSQLException: ERROR: relation "tdportal_info" does not exist
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1548)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1316)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:351)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:344)
at com.teradata.migrator.SpringMigrator.resolveContexts(SpringMigrator.java:224)
at com.teradata.migrator.SpringMigrator.afterPropertiesSet(SpringMigrator.java:393)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1417)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:580)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
at org.springframework.context.support.FileSystemXmlApplicationContext.(FileSystemXmlApplicationContext.java:140)
at com.teradata.migrator.utility.SchemaMigrator.createApplicationContext(SchemaMigrator.java:391)
at com.teradata.migrator.utility.SchemaMigrator.migrate(SchemaMigrator.java:212)
at com.teradata.migrator.utility.SchemaMigrator.main(SchemaMigrator.java:146)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.teradata.commons.bootstrap.Bootstrap.main(Bootstrap.java:166)
2012-09-20 23:43:08,373 DEBUG - The table does not exist for context resolver query. Running a clean installation of schema.
2012-09-20 23:43:08,373 DEBUG - The table does not exist for context resolver query. Running a clean installation of schema.
2012-09-20 23:43:08,380 DEBUG - Marking SpringMigrator classpath:com/teradata/viewpoint/database/changesets/lportal/lportal.changeLog-master.xml for rollback at Thu Sep 20 23:43:08 CEST 2012
2012-09-20 23:43:08,380 DEBUG - Marking SpringMigrator classpath:com/teradata/viewpoint/database/changesets/lportal/lportal.changeLog-master.xml for rollback at Thu Sep 20 23:43:08 CEST 2012
2012-09-20 23:43:08,852 DEBUG - Found schema migration bean(s) for context classpath:com/teradata/viewpoint/database/changesets/lportal/lportalSchemaMigration-context.xml
2012-09-20 23:43:08,852 DEBUG - Found schema migration bean(s) for context classpath:com/teradata/viewpoint/database/changesets/lportal/lportalSchemaMigration-context.xml
2012-09-20 23:43:08,857 DEBUG - Attempted roll back of any uncommitted transactions for SpringMigrator classpath:com/teradata/viewpoint/database/changesets/tdportal/tdportal.changeLog-master.xml
2012-09-20 23:43:08,857 DEBUG - Attempted roll back of any uncommitted transactions for SpringMigrator classpath:com/teradata/viewpoint/database/changesets/tdportal/tdportal.changeLog-master.xml
2012-09-20 23:43:08,865 DEBUG - Closed the connection for SpringMigrator classpath:com/teradata/viewpoint/database/changesets/tdportal/tdportal.changeLog-master.xml
2012-09-20 23:43:08,865 DEBUG - Closed the connection for SpringMigrator classpath:com/teradata/viewpoint/database/changesets/tdportal/tdportal.changeLog-master.xml
2012-09-20 23:43:08,876 DEBUG - Closed SpringMigrator for change log classpath:com/teradata/viewpoint/database/changesets/tdportal/tdportal.changeLog-master.xml
2012-09-20 23:43:08,876 DEBUG - Closed SpringMigrator for change log classpath:com/teradata/viewpoint/database/changesets/tdportal/tdportal.changeLog-master.xml
2012-09-20 23:43:08,884 DEBUG - Attempted roll back of any uncommitted transactions for SpringMigrator classpath:com/teradata/viewpoint/database/changesets/lportal/lportal.changeLog-master.xml
2012-09-20 23:43:08,884 DEBUG - Attempted roll back of any uncommitted transactions for SpringMigrator classpath:com/teradata/viewpoint/database/changesets/lportal/lportal.changeLog-master.xml
2012-09-20 23:43:08,888 DEBUG - Closed the connection for SpringMigrator classpath:com/teradata/viewpoint/database/changesets/lportal/lportal.changeLog-master.xml
2012-09-20 23:43:08,888 DEBUG - Closed the connection for SpringMigrator classpath:com/teradata/viewpoint/database/changesets/lportal/lportal.changeLog-master.xml
2012-09-20 23:43:08,903 DEBUG - Closed SpringMigrator for change log classpath:com/teradata/viewpoint/database/changesets/lportal/lportal.changeLog-master.xml
2012-09-20 23:43:08,903 DEBUG - Closed SpringMigrator for change log classpath:com/teradata/viewpoint/database/changesets/lportal/lportal.changeLog-master.xml
2012-09-20 23:43:08,914 DEBUG - Closed schema migration application context org.springframework.context.support.FileSystemXmlApplicationContext@16c163f
2012-09-20 23:43:08,914 DEBUG - Closed schema migration application context org.springframework.context.support.FileSystemXmlApplicationContext@16c163f
2012-09-20 23:43:08,918 DEBUG - Closed schema migration application context org.springframework.context.support.FileSystemXmlApplicationContext@1b03c1a
2012-09-20 23:43:08,918 DEBUG - Closed schema migration application context org.springframework.context.support.FileSystemXmlApplicationContext@1b03c1a
2012-09-20 23:43:08,923 DEBUG - Closed shared application context org.springframework.context.support.FileSystemXmlApplicationContext@17653ae
2012-09-20 23:43:08,923 DEBUG - Closed shared application context org.springframework.context.support.FileSystemXmlApplicationContext@17653ae
2012-09-20 23:43:08,932 INFO - DATABASE SCHEMA MIGRATION SUCCESSFUL!
2012-09-20 23:43:08,932 INFO - DATABASE SCHEMA MIGRATION SUCCESSFUL!