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).
The following error show up when trying to setup VP Server with MySQL as server database.
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.
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.
VP Server is an integrated server providing the facilities including Teamwork operation support, Hosting of floating license and Centralized update server. Upgrade VP Server to new build, or even new version is extremely easy and can be done in few clicks. This article will teach you how to update your VP Server using the build-in update feature.
With Visual Paradigm’s floating license you can define the access code to control the access of the license. The access code basically is a password and it server for 2 main purpose. First, it helps to prevents unauthorized access to your license key and only when user have the right access code can use it, which increased the level of security. Second is to divide your floating licenses into groups. Think about if group A and B both acquire licenses from the same VP Server, group A may use up all the keys, leaving no available license for group B, when there is no control. Access code solves this problem by enforcing the need of supplying a valid password when trying to acquiring license from server by client.
The floating license allows you to share your Visual Paradigm license key between your team. While using floating license the software need to keep online and connect to license server for validation. In some situation, such as working in customer’s site or during travel, you may not able to get access to your license server. In this case you can export the floating license key form your server and use the software offline. In this article we will show you how to export the floating license key form your license server, and how to return it back after using.
VP Server is a server application which included the Teamwork Server, Floating License Server and Update Server. As 64 bit system already become the majority player, starting from version 13.0 VP Server no longer offer 32 bit installation package. But even the 32 bit installation package was no longer offered, you can still setup VP Server on a 32 bit environment. This article will teach you how to setup a VP Server on a 32 bit system. Read more
VP Server is a server application which included the Teamwork Server, Floating License Server and Update Server. Instead of setup these server applications one by one; they can be setup via the single VP Server package. VP Server using database for storing the settings and configurations, such as teamwork user account, history for check-in & check-out of project files, floating license status, etc. You can setup VP Server with an embedded database, or using some popular DBMS such as Microsoft SQL Server, MySQL, Oracle and PostgreSQL. This article will teach you how to setup a Microsoft SQL Server database for the VP Server. We will use the Microsoft SQL Server 2014 Express Edition to demonstrate how it works. Read more
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