By setup VP Server as system service it will automatically starts when the machine boots. This avoid the VP Server need to manually start by user before using it. In this article we will show you how to setup the VP Server as Windows system service.
VP Server providing the update server module which helps to host the product update. The update module will constantly check for update from Visual Paradigm’s download site. By configure user’s Visual Paradigm client performing update via the update server, the colleagues are guarantee to be running the product on the same build. But for some company they want their colleague run on a fixed build rather than the latest one, you can then follow the procedure below to configure the update server only provide update on specific build number of Visual Paradigm. Read more
Visual Paradigm Project Viewer (VP Viewer) is a free application which allow user to browse the content of your projects without the need of purchase any license key. For large organization you can setup viewer users in your repository so that they can browser your projects without afraid that they will get modified. In this article we will show you how to create viewer users in your on-premises Teamwork Server and how the viewer users can access to your repository.
Starting from v16.0 the on-premises VP Server comes with a new module called Content Repository, which is responsible to support the new VP Form features. By default the Content Repository is configured for HTTP connection only. To make the Content Repository works with HTTPS connection you will need to adjust the configuration in the following way:
Starting from version 16.1 the VP Server require a new node module in order perform certain services. By default VP Server will automatically download and install this module for user. But in case user’ VP Server cannot access Internet then the auto setup procedure will not work and in this case user can follow the steps below to manual install this module to their VP Server.
Visual Paradigm Tabular allow user collect, organize and extra data into spreadsheet. It allow user insert large collection of data and then perform analysis, and further transform into visual presentation such as charts, reports, tables, etc. At the moment the Tabular feature is only available for online. Even user with on-premises Teamwork Server they also need to access to Visual Paradigm’s Tabular Server over Internet in order to use this feature. We understand this may causing confusion to uses whose environment not allow to access Internet. To avoid confusion by default this feature is disabled in on-premises Teamwork Server.
Visual Paradigm Online and the on-premises Teamwork Server support integrate with Active Directory using Visual Paradigm’s DS Connector to perform user authentication. During setup you can select the users from your Active Directory to join your VP Online/Teamwork Server. Some users may experience a problem that they can only list out the first 1000 users from Active Directory, where users out of this range cannot be select. This is caused by Active Directory by default only allow query on 1000 objects, which means you can only list out 1000 users in DS Connector. In this article we will show you how to adjust the query limit in your Active Directory to solve this problem.
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:
The migration procedure provides a way for user to move data from one server to another one. This is helpful under the following situation:
- Move the server from one machine to another machine (include changing OS)
- Change of server database (i.e. form embedded database to external database)
- Upgrade server which span across multiple versions (i.e. from v12 directly to v16)
- Update server runtime
To perform server migration: