VPository is a cloud-based collaboration platform provided by Visual Paradigm. VPository allow software teams to store and share Visual Paradigm projects with team members. Companies could using VPository for team collaboration. In some situation user may need to connect with different VPository during their work, i.e. a consultant may need to connect to the VPository form their different customers. Since each Visual Paradigm workspace can only connect to one VPository, to achieve this user will need to work with multiple workspace, with each workspace connect to one VPository.
To do this: Read more
VP Server is a critical component for a team since it serve as both Teamwork Server (on-premises setup of VPository) for team collaboration development, as well as the License Server for floating license environment. Thanks for that VP Server was using a standard Apache Tomcat webserver as its base, you can easily protect the communications with VP Server by configure it to run with your own SSL certificate.
It is often that you have quite a number of models being reused across projects. Duplicating those models across projects would lead to a management nightmare in which you will need to update all those models on all projects when you need to make changes on it. By creating reference projects in Visual Paradigm Standard Edition, you can define those model elements as a global project, which can be reused by other projects. The reference project not only works locally on your machine, but also works in team collaboration environment where it can be shared across teammates. In this article we will teach you how to migrate your local working projects as well as your referenced projects into VPository environment. Read more
VPository is a cloud-based collaboration platform launched by Visual Paradigm on June, 2013. The enterprise-strength collaborative platform provides software development teams with 1 GB FREE storage to store their software design. Team members can access VPository to checkout the projects they need and start working on them. Click on the links below to learn more about VPository.
- What is VPository and how can VPository boost software development team’s productivity?
- How do I subscribe to VPository? – text version
- How do I subscribe to VPository? – video version
If you have any questions or suggestions, feel free to contact the Visual Paradigm support team.
|This article is out-dated and the support of Subversion had been discontinued since version 13.0.|
If your team uses Subversion server (SVN) to manage your work, and if your server has to use a proxy server to access the internet, you need to edit your servers configuration file to indicate the proxy to use. This article will show you how.
Commit sends your local changes to server, while update grabs from server the latest changes made by your teammates. Frequent committing and updating help ensure that people in your team are all working on the latest and common project data. If you have a large number of projects in your workspace, the mass commit and mass update function are particularly helpful. They can save you time by committing or updating all projects in workspace in one go, rather than to do it project by project. In this article, you will learn how to commit and update multiple projects at one time. Note that the techniques to cover apply to any of the supported concurrent versioning systems: Visual Paradigm Teamwork Server, SVN, CVS, Perforce, ClearCase.
When your team is composed of people with different roles and authorities, you may want to have control over their actions in the modeling tool, to prevent them from making undesired changes. For example, while it is reasonable for a software architect to build class models, it is not reasonable for him to restructure any model developed, through the refactor feature. With VP Server, administrator is allowed configure the access rights of features for members or member groups. For example, by turning off the “manage referenced project” permissions for a member, he/she won’t be able to add and remove referenced project. In this article, you will see how to configure client permission when creating and editing a member.
When Visual Paradigm release a new new version, it comes with many new and enhanced features. In order for a project file created in an old version to work smoothly in new version, it has to undergo a conversion process, which involve the checking and patching of project data. The conversion process is a one-off procedure done when you first open the project in new version. It may take a while to complete. So you can imagine if you are working as a team and your team have many, many projects, conversion can be a fairly daunting task.
For this reason, Visual Paradigm introduced the mass project migration feature. It helps you convert a group of projects from old version to new version at the same time, and eventually have them committed to the server automatically. With this, you can assign one team member to execute the mass project migration. And when the migration is complete, ask the rest of the team re-checkout the projects from server. Since the projects have been converted, team members can directly open the project without having to wait for any project conversion, which saves a great deal of time.
Notice that the technique described in this article applies to any users who use Visual Paradigm’s client products (VP-UML/Agilian/Lorigizn) with any kind of supported concurrent versioning system (VP Server, SVN, CVS, Perforce, ClearCase).