VI Package Repositories

This is a high-level overview of how to create and use a VI Package Repository with VIPM, so that you can share packages with your team and test systems throughout your organization.

Key Concepts

The VI Package Repository system consists of three main components/concepts:

• VI Package Repository - a collection of VI Packages and other files stored in a shared folder that is on your local computer, a shared network drive, or even a web server.
• VIPM Pro Clients - VIPM Pro installations that will subscribe to the VI Package Repository (e.g. over the network), in order to download VI Packages from the repository.
• Repository Manager Window - a window in VI Pro that allows you to create/manage your VI Package Repository.

Setting up the System

Setting up a VI Package Repository System requires the following steps:

1. Create a VI Package Repository using the Repository Manager Window in VIPM Pro (and, publish some packages to the VI Package Repository).
2. Decide which protocol your VIPM Clients will use to access the VI Package Repository - for example: Windows File Sharing or HTTP.
3. Decide where on the network you will keep your VI Package Repository (for example a Network File Server or Web Server)
4. Consult with your organization's IT department to ensure that steps #1 and #2 (above) comply with your organization's information and network security policies.
5. VIPM Clients subscribe to the repository from within the VIPM Client's options dialog (Options>>Networking>>Repository URL) as shown in the VIPM Clients section.

Using the System        

Using your VI Package Repository System involves the following activities:

• Publishing new VI Packages to the repository, using the Repository Manager Window - these new VI Packages will then be available to VIPM Clients when they check the Network for Available Packages.
• Deprecating old packages that are no longer recommended for use, so that they will not be visible (by default) to VIPM Client users.
• Backing up your VI Package Repository, just in case.

Important considerations for web server access

VIPM’s Repository Manager Window requires that the repository be accessible via a drive letter access or UNC networked paths. When it comes to giving access to the VIPM clients, you should consider using a web server in order to isolate clients from direct repository access. It’s also very convenient for clients to access the repository when they are outside the internal network.

One possible way to accomplish this is the following:

1. Setup and manage your repository on your local computer hard drive.
2. Configure a web server.
3. Publish packages using the VIPM Repository Manager.
4. Copy the contents of the repository to the web server using FTP/SFTP/DAV. You need to do this every time you edit the repository.

Repository RSS feed

All repositories come preconfigured with an RSS feed. This is a file located at the root of the repository (index.rss). You can subscribe to this feed and get updates when new packages get published.