...
| Code Block |
|---|
<dbConfig name="wso2registry"> <url>jdbc:h2:database/WSO2CARBON_DB</url> <userName>wso2carbon<<username>wso2carbon</userName>username> <password>wso2carbon</password> <driverName>org.h2.Driver</driverName> <maxActive>50</maxActive> <maxWait>60000</maxWait> <minIdle>5</minIdle> </dbConfig> |
...
After the ESB starts for the first time using these files, the configurations are stored in the registry, and the bootstrap files are no longer used. All subsequent server starts use the configurations in the registry, and any modifications users make to the configurations through the user interface are saved in the registry. However, it is a best practice to save the configurations to synapse.xml from time to time so that you can bootstrap the server if a registry error occurs that prevents the server from starting up. For example, if a WSDL file used for creating a proxy service moves to a new location, the ESB will not start. In this case, you can edit synapse.xml to configure the proxy service with the WSDL's new location, and then start the server using the --DuseSynapseXML command line argument to bootstrap it with the configurations in this file.
...
Some of the configurations that can be stored in the registry are:
- Endpoints
- Sequences
- XSLT files
- Rule Scripts
- Scripting language scripts used by the Script Mediator
Storing XSLT files in a registry is needed if the user requires to cluster the WSO2 Enterprise Service Bus. Usually an ESB cluster is created by pointing several ESBs to use the configurations stored in a single registry. Also it is easier to manage the resources like XSLT if they are stored in the registry.
...