PackPoint is a feature, which is available for professional and enterprise edition users, allowing them to reuse a central repository of common resources (templates, merge modules, exclusions, predefined properties, etc.). Once established, PackPoint is an essential companion for the maintenance of high level teamwork and standardization measures in packaging factories.
In order to use the PackPoint organization structure, the storage location for the PackPoint has to be defined during the setup of RayPack. If a PackPoint is defined, the initial population with resources is executed when RayPack is launched for the first time. All core resources, which are appropriate for permanent maintenance beyond product upgrades and local instance endurance, are automatically put to the PackPoint location. The material preserved within the PackPoint location is the base for any synchronization with the local resources on the packaging machine.
|
Note: PackPoint is not available for Standalone Repackager installations of RayPack. Please use either the custom or typical setup type to enable PackPoint initialization during the application installation. |
If the currently running application instance uses a PackPoint, the path to the storage location can be reviewed from the Troubleshooting view of the About area. However, it is not possible to change the PackPoint location for an existing RayPack instance by using the controls of the application interface.
|
Warning! Even though it is not recommended to do so, users may modify the PackPoint configuration by manually adjusting the content of the Please take into account, that manual modifications may have severe impact on the automated synchronization features of the PackPoint repository. If modifications are needed, make sure to have a copy of the original configuration file at hand if the changes turn out to cause negative side effects or to be erroneous in general. |
Here is an overview of resources that are handed over to PackPoint control if a central repository has been setup for a RayPack packaging environment:
|
Resource location without |
Resource location in PackPoint |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note: [InstDir] is the RayPack installation directory, which is typically something like [PPDir] is the PackPoint location directory, typically something like Both directory locations are freely configurable during the RayPack installation, therefore the actual locations on your packaging machine may vary. |
Types of PackPoint resources
Essentially, two types of PackPoint resources can be distinguished:
- Resources for which a local copy is created
Examples of this type of resources are profiles, exclusions and templates. In order to ensure that a user has permissions to change them, the global PackPoint profiles and templates are copied to the local machine and will be used instead. If there is no access to PackPoint, defaults will be taken from[INSTALLDIR]Resources\Default. These resources are critical and required for RayPack to work. - Resources accessed directly from PackPoint
Most of the customizable resources (Custom Actions, predefined folders, system search, conditions, Merge Modules etc.) are accessed directly from PackPoint. If PackPoint becomes unavailable, certain features may not work (for example, the Merge Modules browser may show no predefined modules etc.). These resources are not critical and RayPack will run even if they are not accessible.
PackPoint update mechanism
Whenever RayPack is launched, the version value of the local resources and the PackPoint version are compared. If they differ (which may occur when the PackPoint has been updated during maintenance or product update phases), one of the following procedures is executed:
- Strict mode (PackPoint overrides local settings)
Any change that has been executed on the PackPoint location will be taken over into the local settings. Any local changes will be lost. This is the default behavior.
During this process:- Existing local RayPack configuration (“
%appdata%\RayPack\*.*”) is being updated from the PackPoint configuration templates ([PPDir]\Default). - Local filters and profiles are overridden
- Package Templates are replaced completely (from PackPoint to local).
- Existing local RayPack configuration (“
- Loose mode (Local settings are preserved)
The local resources and PackPoint resources are merged to generate a synchronized overall state.
During this process:
- Existing local RayPack configuration (“
%appdata%\RayPack\*.*”) is being updated from the PackPoint configuration templates ([PPDir]\Default). - Filters and profiles are merged (only not existing entries are added, exiting entries are remaining the same).
- Local package templates are preserved
- Existing local RayPack configuration (“
This synchronization allows to take over local adjustments into the overall PackPoint, whilst at the same time being able to receive updated PackPoint resources into the settings for the local application instance. In order to reset the changes performed to local settings, users should remove them from the local machine, and relaunch RayPack. The synchronization mechanism will automatically create a new local copy of the resources preserved within the PackPoint.
|
Be aware: If the defined PackPoint location is unavailable due to broken files, missing user rights, or missing connectivity, RayPack is still operational. It will use the local settings. If both, local settings and PackPoint resources are unavailable, RayPack will operate in a failsave mode, using default resources for vital settings informations. Nonetheless, it is highly recommended to repair the PackPoint and the local settings, in order to avoid data loss and working result quality that is of less quality than possible with the settings defined for your individual packaging environment. |
Please use the settings area to define the PackPoint mode of the currently active RayPack product instance. If you encounter any issues with the setup or maintenance of PackPoint, please contact our support team - we will gladly assist.
PackPoint versioning
The following files are used to determine whether the resources must be updated:
%AppData%\RayPack\PackPointVersion.txt
Contains a single value being the local version number of PackPoint resources[PPDir]\Default\PackPointVersion.txt
Contains a single value being the global version number of PackPoint resources. [PPDir] denotes the location to which PackPoint has been installed.
Any time PackPoint is updated, the versions are updated respectively. To force an update of local resources from PackPoint, simply increase the value in global PackPointVersion.txt file.
Manual PackPoint updates and migration
In order to force update of PackPoint, use command line tool rpcmd.exe. The following section contains parameter description and syntax:
Command Line
Command
upgradePackPoint
Performs various upgrade tasks for PackPoint resources. Use this command to:
- Manually upgrade PackPoint created by previous version of RayPack
- Update the shared PackPoint with local resources and modifications
- Repair shared PackPoint files
Parameters
Optional
-upgradeType <FromInstallation | FromLocal | FromPackPoint>
Specifies the update mode.
- FromInstallation: The shared PackPoint resources will be updated from the application installation (by default
C:\Program Files (x86)\RayPack\Resources\). This is the default setting. - FromLocal: The shared PackPoint resources will be updated from the local profiles, exclusion lists, templates (by default
%appdata%\RayPack\) - FromPackPoint: The local profiles, exclusion lists, templates etc. will be updated from the shared PackPoint location
-mode <TargetWins | SourceWins>
Specifies the collision resolving mode.
- TargetWins: In case of conflict between two values, the target value wins (nothing will be overwritten).
- SourceWins: In case of conflict between two values, the source one wins (it will overwrite the target values)
|
Be aware: This switch applies only when merging profiles and/or exclusion list. For other files, target resources are preserved, only missing ones are copied. |
Example
RpCmd.exe upgradePackPoint -upgradeType FromInstallation
Upgrade rules
The resources are updated according to the following rules
- Missing files are copied from source to the target location
- Certain XML resources are merged from source to the target location. In case of conflicts:
- If FromPackPoint mode was used, then the application settings define which one from the source or the target is winning. To read how to change the PackPoint merging strategy, go to the PackPoint chapter.
- For other types of PackPoint update, the target always wins.
How to install and configure PackPoint
Installation of RayPack WITHOUT a configured PackPoint
- Run the MSI and follow the installation steps until “PackPoint Configuration” is reached.
- Enter/Choose the central path for PackPoint. (If the repository is on a share, the path has to be entered manually and cannot be chosen).
Since RayPack always needs to be started as administrator and network drives are setup using the standard user, the complete UNC path (for example: \\vmware-host\Shared Folders\RayPack) should be entered.
- Finish the installation.
- Run RayPack
The PackPoint resources will be updated on the first start of RayPack and not during the installation.
Preparations for PackPoint (the following steps should be executed in RayPack)
- Create or edit MSI and/or MST templates.
- Create or edit profiles.
- Create or edit filter.
- Run the CMD as administrator and enter the following:
“<Path to RayPack folder>\RpCmd.exe upgradePackPoint –mode SourceWins –upgradeType FromLocal”
Installation of RayPack with a configured PackPoint
- Execute the installation as described before OR execute a silent installation like described below.
Create a silent installer using a Response Transform (MST):
- Create a correctly configured MST (containing the path to PackPoint and everything else that is needed)
Before tailoring is executed, “Ignore Systemstate” needs to be checked.
- The following needs to be entered in the CMD:
msiexec.exe /I “<Path to RayPack .msi>” TRANSFORMS=”<Path to RayPack .mst>” /qn /l*vx “<path to log file>”
Create a silent installer for RayPack without Response Transform:
This installation only the RayPack.msi is used, modified by different parameter.
Parametergroups:
- Path parameter:
INSTALLDIR: Specifies the path to the target folder for the RayPack installation.
PACKPOINTDIR: Specifies where PackPoint is located.
- License parameter:
COMPANYNAME: Specifies the name of the company.
EMAIL: Specifies the email address.
ORDERNUMBER: Specifies the order number.
- PackPoint parameter:
PACKPOINTMODE 0: Specifies that the default path to PackPoint is set.
PACKPOINTMODE 1: Specifies that it is only possible to use resources from the RayPack installation folder (PACKPOINTDIR will be ignored).
PACKPOINTMODE 2: Specifies that a user defined path to PackPoint is set.
Example with licensing:
msiexec.exe /I “<Path to RayPack .msi>” INSTALLDIR=”<Path to target folder where RayPack should be installed>” PACKPOINTMODE=2 COMPANYNAME=”<Name of the company>” EMAIL=”<email address>” ORDERNUMBER=”<ordernumber>” /qn /l*vx “<path to log file>”
Example without licensing:
msiexec.exe /I “<Path to RayPack .msi>” INSTALLDIR=”<Path to target folder where RayPack should be installed>” PACKPOINTMODE=2 /qn /l*vx “<path to log file>”
Possible RpCMD parameter for upgradePackPoint
- Mode: Specifies how conflicts with files are being resolved.
-mode SourceWins: With this parameter, files in the target directory are overwritten.
Example: „<Path to RayPack folder>\RpCmd.exe upgradePackPoint -mode SourceWins -upgradeType FromLocal“
-mode TargetWins: With this parameter, files in the target directory are NOT overwritten.
Example: „<Path to RayPack folder>\RpCmd.exe upgradePackPoint –mode TargetWins -upgradeType FromLocal“
- UpgradeType: Specifies from where the PackPoint folder is upgraded.
-upgradeType FromLocal: If this parameter is used, the PackPoint folder is upgraded using the local folder (located in AppData).
Example: „<Path to RayPack folder>\RpCmd.exe upgradePackPoint -mode SourceWins -upgradeType FromLocal“
-upgradeType FromInstallation: If this parameter is used, the PackPoint folder is upgraded from the installation folder from RayPack.
Example: „<Path to RayPack folder>\RpCmd.exe upgradePackPoint -mode SourceWins -upgradeType FromInstallation“
-upgradeType FromPackPoint: If this parameter is used, the PackPoint in AppData will be upgraded from the PackPoint folder.
Example: „<Path to RayPack folder>\RpCmd.exe upgradePackPoint -mode SourceWins -upgradeType FromPackPoint“
Manual configuration of PackPoint path and Setup type
Open the PackPoint.config file in the RayPack installation folder. This is where <Path> and <SetupType> (which contains the information how PackPoint works) can be found.
During the installation the path and SetupType that are chosen are written into this file. After this, these settings can always be changed.
|
|
Automatic PackPoint Upgrade
Many resources are, by default, used directly from the PackPoint folder (for example: MergeModules, Prerequisites, etc.). All resources located in the „Default” folder, must exist locally, therefore a PackPointVersion.txt file exists in the “Default” folder. If the version number of this file is higher than the version number in the local (AppDate) PackPointVersion.txt file, an automatic upgrade from PackPoint ot the local (AppData) Packpoint will be executed.
The following command in the RpCMD does the same:
„<Path to RayPack folder >\RpCmd.exe upgradePackPoint -mode TargetWins -upgradeType FromPackPoint” |
The mode depends on the profile settings.
Comments