RPK200000: How to use the Remote PackRecorder

Application context

PackRecorder > Repackaging on clean machines

Issue

Using RayPack requires product activation. Whilst the implemented web-based activation procedure works fine for permanent packaging machines, it is not the handiest possible solution for the maintenance of several clean machines for repackaging. Usually these are various sets of virtual machines, which are reset for every new repackaging process. Installing the full RayPack framework on every clean machine would also lead to a high number of required licenses. This is not the intended licensing model Raynet has in mind for RayPack.

Solution

Instead of installing the full RayPack framework on each and every machine used for repackaging, users may extract the Remote PackRecorder from the core installation and use it for all repackaging machines without hardware lock and activation requirement. The Remote PackRecorder allows to capture snapshots and edit RCP files generated from the capture delta analysis. For extended packaging measures in PackDesigner, and also for using the PackTailor, users have to transfer the RCP file from the capture machine to the core packaging machine, where the full RayPack framework is installed. Only the full installation on the core packaging machine is bound to the licensing and activation method that depends on the machine’s hardware id.

To prepare the Remote PackRecorder from the core framework installation:

1. Once the full RayPack framework is installed on one device, this one is considered to be the core packaging system.
2. From this core installation, it is possible to extract a RayPack image by just copying the installation folder to a different location (e.g. Network-Share, USB thumb drive, etc.)
   Please make sure to close any instance of RayPack before initiating the copy procedure.
3. All *.rsl (with 4.0) or *.license files (earlier than 4.0) must be deleted from the root folder of the newly created RayPack image.
4. Copy the RayPackFreePackRecorder.rsl (with 4.0) or the RayPackFreePackRecorder.license (earlier than 4.0) from <INSTALLATION_PATH>\RayPack\RemotePackRecorder\ to the root folder of the newly created RayPack image.
5. Ensure that the RayPackFreePackRecorder.rsl (with 4.0) or the RayPackFreePackRecorder.license (earlier than 4.0) is the only *.rsl (with 4.0) or *.license (earlier than 4.0) file within the root folder.
6. This RayPack image may be run from any machine. Simply call the RayPack executable and start capturing processes.
7. Captured RCP files may be edited with the editor that is included in the Remote PackRecorder. It is also possible to build RPP files for later editing from the Remote PackRecorder.
8. RCP or RPP project files have to be either transferred to or made available for access from the core packaging system.
   
   The core machine contains required engines and advanced editor interfaces to adjust the intermediate packaging projects and build target packages (e. g. MSI or virtual formats) from them.

Related topics

Support Ticket ID: 2411