Service deployment fails in VSE with external production database - Service Virtualization

Products

• Service Virtualization

Issue/Introduction

Virtual services fail to deploy to the Virtual Service Environment (VSE) after Model Archive (MAR) files are manually deleted from the vseDeploy folder. This typically occurs when using an external production database where metadata synchronization is lost between the file system and the database records.

 

Environment

All support DevTest releases and databases.

Cause

Manually deleting MAR files from the vseDeploy folder bypasses the standard undeploy logic. This leaves residual metadata in the external database and the local VSE cache, causing the system to report deployment conflicts or corrupted archives.

Resolution

To clear residual values and restore synchronization, follow these steps:

1. Stop the VSE service.
2. Navigate to DevTest_Home/vseDeploy/VSE_[Port] and move all files/folders (including .mar.tracking and .services) to a backup location.
3. Delete the contents of the following temporary folders to remove stale sessions:
   • DevTest_Home/lisatmp_####/vsBuilderSessions
   • DevTest_Home/lisatmp_####/vsRecording
   • DevTest_Home/lisatmp_####/lads
4. Verify the site.properties file for the Registry. Ensure the following property is set correctly for an external database: lisadb.internal.enabled=false
5. Start the DevTest Registry.
6. Start the VSE service. The VSE recreates its local catalog without stale references.

Note: Always use the DevTest Portal or Workstation to "Undeploy" services to ensure database and file system entries are synchronized.