Ce contenu n'est pas disponible dans la langue sélectionnée.
3.2. Virtual Database Deployment
A virtual database (VDB) must be deployed before it can be accessed by client applications.
A VDB can be deployed by the following means:
- File Deployment
- File deployment is recommended for quick deployment during development, when the server is running locally on the developer's workstation.
- Management Console
- Deployment via the web-based Management Console is recommended for a simple way of deploying a VDB to a remote server.
- Management Command Line Interface
- Deployment via the EAP Management Command Line Interface (CLI) is another simple option for deployment.
- AdminShell
- Deployment via the AdminShell is recommended for more advanced deployments such as when you want to automate the deployment of artifacts in your environment.
- Admin API
- Deployment via the Admin API is recommended for more advanced deployments such as when you want to deploy a VDB from within other applications.
Note
A VDB can also be deployed within the Teiid Designer. See the Red Hat JBoss Data Virtualization User Guide.
Important
Removal of a VDB cleans up all of its resources automatically; however, existing sessions will not be terminated automatically.
Warning
When deploying a VDB, overwriting a VDB with one of the same name will terminate all connections to the old VDB unless VDB versioning is used.
Red Hat recommends the use of VDB versioning on production systems.
Warning
You can locally name VDB artifacts as you wish, but the runtime names of your deployed VDB artifacts must have an extension of *.vdb for a zip file or *-vdb.xml for an xml file. Failure to name your file correctly will result in a deployment failure as the Teiid subsystem will not know how to handle it.
