This is a high-level, descriptive overview of the VIPM Enterprise VI Reuse System.
System Components
The Enterprise VI Package Repository consists of three main components/concepts:
• VI Package Repository - a collection of VI Packages and other files stored in a folder
• VIPM Clients - VIPM installations that will access the VI Package Repository (e.g. over the network), in order to download VI Packages
• Repository Manager Window - a window in VI Package Manager Enterprise Edition that allows you to create/manage your VI Package Repository
Setting up the System
Setting up an Enterprise VI Package Repository System requires the following steps:
1. Create a VI Package Repository using the Repository Manager Window in VIPM Enterprise Edition (and, add some packages to the VI Package Repository).
2. Decide which protocol your VIPM Clients will use to access the VI Package Repository - for example: File Sharing or HTTP (Apache or IIS Web Server). See the Enabling VIPM Client Access to your Repository over the Network for more information.
3. Decide where on the network you will keep your VI Package Repository (for example a Network File Server or HTTP 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. Authorize VIPM Clients using the Repository Client Authorization Dialog of VIPM Enterprise Edition.
6. Connect VIPM Clients 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 Enterprise VI Package Repository System involves the following activities:
• Adding (and removing) authorized VIPM Clients to (and from) the VI Package Repository using the Client Authorization dialog in the Repository Manager.
• Adding (a.k.a. "releasing") 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.
If you have any feedback or questions (including ideas for other topics you'd like to learn more about), please consider posting them to the VIPM Discussion Forums. We're looking forward to your feedback. All Contents, Copyright © 2006-2009, JKI. All Rights Reserved. |