Virtual data model deployment creates a virtual database of all the heterogeneous sources that have been modeled. Once a virtual data model is designed, it is ready to be deployed.
Verifying the Virtual Data Model
For a smooth deployment, it is necessary to ensure that there are no verification errors in the virtual data model. If the verification is successful, you can proceed towards deployment.
Specifying the Cluster Deployment Directory
A pre-requisite for deployment is to specify the Cluster Deployment Directory. In the Server Explorer window, right-click on the DEFAULT node in the server connections, and choose the option Cluster Settings.
Mention a shared network path for the Staging Directory and Deployment Directory, which is accessible to both the Client and Server. Press Ctrl + S to save the settings.
Deploying a Virtual Data Model
You can deploy a virtual data model from the project as well as Virtual Monitor.
Creating a Deployment from the Project
A virtual data model can be deployed either from the toolbar command or context menu option in the Project Explorer.
Once you select this option, a pop-up will open where you will be required to provide Virtual Database Name, Source Config Path, and Cache Database Info. All these options are pre-filled by default, but you can edit this information.
On clicking OK, you will see the deployment log in the Job Progress window. This log will give you insights about the virtual database deployment and caching.
By clicking on “P”, you can monitor the progress of the cache enabled entity. This will open another job progress tab from where you can check the caching status of an entity.
After the virtual data model has been deployed, you can check its availability on the server. Go to the Virtualization tab and select the option Virtual Model Deployments.4
In the virtual monitor wizard, you can see complete information related to the deployment. The name of the virtual model, status of the job, deployment log, cache status and details, the server on which the model was deployed, name of the machine that created and updated the model, and last updated date.
Creating a Deployment from Archive File
The archive file is used to create a virtual model deployment. When you deploy a VDM from the toolbar or context menu option in a project, the archive file is built automatically at the time of deployment and saved in the project directory. However, you can also build an archive file manually, save it to an arbitrary shared location, and use it to deploy a VDM from the virtual monitor.
To create an archive file for the entire project, right-click on the project name in the Project Explorer and choose the option Build Archive (*.Car) for the Project. This option will create an archive file of all the virtual data models that are included in the project.
To create an archive file for a single virtual data model, right-click on the virtual data model in the Project Explorer and choose the option Build Archive (*.Car) for the Item.
Provide the file path and click Save. As soon as the archive is built, you will receive a notification that Archive has Been Built Successfully. Now, you may open the virtual monitor from the Virtualization tab.
Give the virtual database a name, specify the archive file path, and select the model that you want to deploy from the Virtual Data Model drop down. The Cache Database Info is autodetected from the last connection. Therefore, if you want to create the cache database in another location, the connection information will have to be changed. On clicking the Save button, the virtual data model deployment will begin.
Refresh the virtual entity list, and a new record of the recently created virtual database will be visible on the deployment monitor.
Exploring the Virtual Data Model Deployments Monitor
The virtual data model deployments monitor gives a bird’s eye view of the virtual database deployment. The Status field has three types of values.
Running: If a deployment is active, the status will show Running.
In Progress: If a deployment is being created, the status will show In Progress.
Error: If a deployment ends in error, the status will show Error.
The Cache Status field provides information on whether the cache enabled entities are ready or not.
All entities ready: When all entities that have cache enabled are ready.
Cache not enabled: When cache has not been enabled for any entity.
Some entities in error: When some entities have an error in caching.
Cache not ready: When the cache is not yet ready, and the cache job is still in progress.
Furthermore, you can check detailed information about cache schedules, the last 10 cache jobs, user and system status, and last updated information for the cache enabled entities by clicking on Entity Cache Details.
0 Comments