Difference between revisions of "Enabling DB SavePoint"

From GreenVulcano Wiki
Jump to: navigation, search
(Created page with "{{GVESB}} is provided with the "SavePoint" Console prepared for accessing to a Oracle database. The connection takes place using the parameters defined in the ''GVAdapters.xml''...")
 
 
Line 1: Line 1:
{{GVESB}}  is provided with the "SavePoint" Console prepared for accessing to a Oracle database. The connection takes place using the parameters defined in the ''GVAdapters.xml'' file, presents in the ''GVDataHandlerConfiguration'' section. Enabling the Workflow Engine to be used by the SavePoint, is configured in the ''GVCore.xml'' file from Persistence section.
+
{{GVESB}}  is provided with the "SavePoint" Console prepared for accessing to an Oracle database. The connection takes place using the parameters defined in the ''GVAdapters.xml'' file, present in the ''GVDataHandlerConfiguration'' section. For enabling the Workflow Engine to be used by the SavePoint, it is configured the ''GVCore.xml'' file present in the Persistence section.
  
  

Latest revision as of 10:21, 22 January 2012

GreenVulcano® ESB is provided with the "SavePoint" Console prepared for accessing to an Oracle database. The connection takes place using the parameters defined in the GVAdapters.xml file, present in the GVDataHandlerConfiguration section. For enabling the Workflow Engine to be used by the SavePoint, it is configured the GVCore.xml file present in the Persistence section.


The ddl scripts for the data structure definition into the database and the configuration fragments to be added and/or rewriting in GVCore.xml and GVAdapters.xml files are found in the directories:

  • $GV_HOME/doc/extra/savepoint/mysql
  • $GV_HOME/doc/extra/savepoint/oracle


The configuration fragments can be adjust to the specific connection parameters for the database (url, user, password).