VP Server is a server application which included the Teamwork Server, Floating License Server and Update Server. To protect you from losing your valuable works, it is recommended to backup the server from time-to-time. This article will show you how to get it done by using the built-in backup script.
One of the feature for the on-premises VP Server is use as the update source for the VP Client to perform software update. This help to make sure all users within the company using the same build of Visual Paradigm’s application. During setup of update mechanism VP Server will check any available update of VP application over Internet. This article teach user how to configure the proxy server for their VP Server so that they can check for software update from Visual Paradigm’s website. To configure proxy server for VP Server:
Starting from version 16.0 Visual Paradigm’s on-premises Teamwork Server and VP Online support user authentication with Kerberos. This article explains how to configure your Teamwork Server/VP Online for Kerberos authentication.
The migration procedure provides a way for user to move data from one server to another one. This is helpful under the following situation:
To perform server migration:
In latest version 16.0 Visual Paradigm introduced a new Form Builder feature (supported in Professional Edition or above) which allow user to create executable forms using visual editor. The designed form can go live for data collection. For on-premises Teamwork Server or local workspace (local personal server) the data collected by the forms will be stored in the local Content Repository within the server. Subject to user’s environment the default port used by Content Repository may conflict with other services on user’s computer. In case conflict was found user can change the port used by Content Repository. To change the port number of Content Repository:
Some users may experience problem that VP Server fail to run after upgrade to version 13.0, or server remain in its current version after upgrade. This problem is caused by the VP Server is still running with the old JRE1.6. For deliver better features some libraries used by VP Server was being upgraded. Unfortunately they are not compatible with the old JRE 1.6. For users experienced problem on upgrade server can take the following steps to upgrade your server to version 13.0: Read more
VP Server using database plus file system to store its configuration data and model information (for Teamwork Server user). VP Server can be configure to run with embedded database, or using external database such as MySQL, Maria DB, SQL Server, Oracle and PostgreSQL. In case VP Server is configured to run with external database and the connection info need to be changed, i.e. change to a new password due to password policy, user can follow the steps below to alter database connection info for their VP Server. Read more
VP Server is a central repository for provide various service to user performing team collaboration development. VP Server using a database plus file system to store its data. The following article explains how user can rename the VP Server database if their VP Server is configured to run with external database (SQL Server, Maria DB, SQL Server and PostgreSQL).
Floating license enables users to share the Visual Paradigm concurrently based on the limit of concurrent access specified on the floating license. In order to access the floating license, you need to install the VP Server and enable its Floating License Server Module in your Local Area Network in advance. This article will demonstrate how to download, install and configure VP Server and enable the Floating License Server module.
