Eclipse Community Forums: Eclipse Process Manager (Stardust) » Why do we have to provide the schema name in the carnot.properties

Home » Eclipse Projects » Eclipse Process Manager (Stardust) » Why do we have to provide the schema name in the carnot.properties (Schema name in the carnot.properties)

Show: Today's Messages :: Show Polls :: Message Navigator

Why do we have to provide the schema name in the carnot.properties [message #741992]

Thu, 20 October 2011 00:23

Vikram Kodak
Messages: 56
Registered: October 2011

Member

There is no need to put any DB connection settings (URL, driver, user, password) in the carnot.properties file. Those settings will not be used by the engine. In a managed environment Stardust will get the connection from the datasource and hence the datasource's connection parameters are those that matter.

The db connection settings in the carnot.properties will only be used by the sysconsole command (usually a different carnot.properties file, not the one used for the engine). As a pojo app the sysconsole creates a direct database connection and does not look up the datasource in a managed environment. Therefore it needs the settings. If you don't want to store the settings in the carnot.properties then they can also be submitted as command line parameters to the sysconsole command.

Only settings that affect the way the engine creates SQL statements need to be configured in the carnot.properties file, e.g. schema name (if needed), lock tables, DB dialect, query setting,... Those settings will typically be stable across environments.

If you leave the setting in the carnot.properties empty then you have to configure the user account to access the Stardust schema by default.

http://www.oracle-base.com/articles/misc/SchemaOwnersAndApplicationUsers.php

http://download.oracle.com/docs/cd/B19306_01/network.102/b14269/concepts.htm#CHDHHIAD

[Updated on: Thu, 20 October 2011 13:33]

Report message to a moderator

[Message index]

Why do we have to provide the schema name in the carnot.properties

By: Vikram Kodak on Thu, 20 October 2011 00:23

Previous Topic:	Model cannot be deployed after dropping and re-creating a partition
Next Topic:	ActiveMQ Spring configuration throws "no declaration can be found for element 'amq:broker'"

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue May 21 08:18:30 EDT 2013