Difference between revisions of "Export Services Configuration"
| Line 16: | Line 16: | ||
:GvAdapters.xml: see [[Adapters]] section, for more information | :GvAdapters.xml: see [[Adapters]] section, for more information | ||
:GVCore.xml: see [[GVCore]] section, for more information | :GVCore.xml: see [[GVCore]] section, for more information | ||
| − | :GVESV.jks: | + | :GVESV.jks: This file is the keystore that Vulcon or GVConsole can be used to encipher private data |
:GVSupport.xml: | :GVSupport.xml: | ||
:GVVariables.xml: | :GVVariables.xml: | ||
:gvesb-catalog.xml: | :gvesb-catalog.xml: | ||
Revision as of 11:29, 4 March 2013
The Export configuration functionality generates a zip file containing the GreenVulcano® ESB configuration. This file can be used in VulCon to align the VulCon configuration to the server configuration
The zip file structure is:
- Config
- BpelProcess: this folder contains all file for Bpel service
- Rules: this folder contains all files for Drools configuration
- dtds: this folder contains all dtd that gvCore use.
- gvdte: this folder contains all xsl files.
- keystores: this folder contains the keystore that can be used in GreenVulcano® ESB services
- reports: this folder contains Birt template
- services: this folder contail all file to configure GreenVulcano® ESB services
- wsdl: this folder contains all WSDL file exposed by GreenVulcano® ESB
- xsd: this folder contains the XSD files that can be used to validate XML contents
- GvAdapters.xml: see Adapters section, for more information
- GVCore.xml: see GVCore section, for more information
- GVESV.jks: This file is the keystore that Vulcon or GVConsole can be used to encipher private data
- GVSupport.xml:
- GVVariables.xml:
- gvesb-catalog.xml:
