Bulk installation is a handy approach to install and activate Visual Paradigm on multiple machines. It is specially designed for Visual Paradigm Academic Partner License users who need to setup Visual Paradigm on a considerable number of computers. This article will describe the procedures required for perform the bulk installation on Mac environment. Read more
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.
The Just-in-Time process in Visual Paradigm allows you to create customized enterprise architecture development/agile development process for your team. With the work items provided by Visual Paradigm you can freely add or remove the steps in each phrase of your process. The work items used by the process is accessible via the Teamwork Server, VPository or Personalized Local Server (new in v14.1 SP1). In this article we will show you how to make the work item ready in case your Personalized Local Server was unable to automatically download the work items for you.
Visual Paradigm Project Viewer (VP Viewer) is a free application which allow users to browse the content inside the Visual Paradigm project file. In team collaboration environment, user can use VP Viewer to checkout project form VPository or on-premises Teamwork Server for review. Upon new revision of the project is available, VP Viewer user will be notified and he can update his project to latest revision for reviewing the changes. To update the project to latest revision for VP Viewer: Read more
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.
When you are using Visual Paradigm Teamwork Server (Teamwork Server) or VPository and find a problem, feel free to contact Visual Paradigm to seek for assistance. Remember, the more information you give us, the easier and faster for us to identify the problem, fix the problem and provide a proper solution. In most cases, the steps to produce problem, the log file and a screenshot illustrating the problem are sufficient for us to identify problem. It would be even more effective if you can send us the local project, server revisions as well as the server database (for Teamwork Server) so that we can reproduce and fix the problem accordingly. Read more