Using Reference Path for JDBC Driver in Database Connection

Visual Paradigm support connect to various database server to perform database engineering, including forward and reverse engineering between database and entity relationship diagram (ERD). During the process user will need to connect Visual Paradigm with their database via JDBC connection. A JDBC driver file will involve in the database connection setting. For team environment you can configure the database connection using a reference file path to load the JDBC driver from developer’s environment. In this article we will teach you how to make use of reference file path to specify JDBC driver location when establish database connection.

Read more

UX0025 – Fail to open Process Map, Story Map or Customer Journey Map

This error means the VP Desktop Client fail to load the module for opening Process Map, Story Map, or Customer Journey Map, etc..

Read more

How to configure VP Server’s Content Repository accept HTTPS connection

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:

Read more

How to install node runtime on VP Server

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.

Read more

How to clear System Proxy Setting

Visual Paradigm may store two set of proxy information for user, one is specified by user under Application Options, and the other is specified by administrator during silent/bulk installation (as the default proxy). For Application Options proxy user can modify or remove it simply within the Application Options dialog. But for proxy specified by administrator they are stored in system registry where end user will not able to remove it. To remove the proxy specified by administrator:

Read more

Unable to connect to Visual Paradigm’s Server over Internet

There are several services in Visual Paradigm Desktop client require to connect to Visual Paradigm’s server on Internet, including

Some users may experience problem that their VP Desktop client unable to connect to Visual Paradigm’s server even they do have Internet access. If you see the SSL handshape exception in your Visual Paradigm desktop client’s log file then the problem very likely to be caused by there is a proxy (could be a transparent one) in your network blocking the resolve of SSL certificate thus lead to fail to connect to our server. To solve this problem:

Read more

How to Enable Tabular Feature on On-Premises Teamwork 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.

Tabular feature disabled

Tabular feature disabled

Read more

Adjust number of users to be listed in DS Connector when connecting to Active Directory

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.

Read more