Overview

This guide covers the installation, upgrade, and troubleshooting procedures for Self Packager 1.4 on both Linux and Windows systems. 

The Self Packager can be deployed as a service or run by command, and requires proper firewall configuration and JetPatch connector deployment for optimal functionality.

Installation

Linux Installation

Linux machines must have the libX11 package installed to run the server.

Installation File: Download here

Run Server as a Service

1. Extract the content of intigua_pack_server-Release-<VERSION>.tar.gz to the End-Point machine
2. Add run permission to each file (chmod +x <FILE>)
3. ./installSelfpack.sh
4. service selfpack start
5. After that just use go to http://localhost (from the same machine) or http://[ip-of-the-machine] (from outside the machine)

Windows Installation

Installation File:  Download here

• Install intigua_pack_server-Release-<VERSION>.msi as an administrator
• There is no installation progress GUI, so once you run the MSI file, the service will start and always run the background
• After that go to http://localhost (from the same machine) or http://[ip-of-the-machine] (from outside the machine)

On x64 Windows machines: When installing SelfPackager using the MSI, the library folder of the packages will be under Program Files (x86).

Upgrades

Linux Upgrade

Current Installation: Run Server by Command Installation

1. Verify that the Self Packager is not running.
2. Install the new Self Packager.

Current Installation: Run Server as a Service

1. Stop the Self Packager service (selfpack).

Windows Upgrade

1. Install the new Self Packager MSI.
2. Copy the library folder from the user folder (eg, C:\Users\Administrator\library) into the Self Packager installation folder under Program Files / Program Files (x86).
3. Uninstall the MSI through Programs and Features.

Troubleshooting

Old Selfpack service is preventing the upgrade

Sometimes during an upgrade, the old selfpack service is running, and it interferes with the new installation. To solve this, before running the ./installSelfpack.sh, try to disable the selfpack service.

Try this:

systemctl stop selfpack

systemctl start selfpack

Please run these in the command line before attempting to upgrade to a new version.

Insserv

The warning messages of insserv can appear during a conflict between the install command "update-rc.d selfpack defaults" and other scripts you may have running.

To remediate this, you can run a sudo command like "sudo nano /etc/scriptx.sh" and add LSB tags at the beginning of the file.

### BEGIN INIT INFO

# Provides: scriptx

# Required-Start:

# Required-Stop:

# Default-Start: 2 3 4 5

# Default-Stop: 1 0 6

# Short-Description: ...

# Description: ...

### END INIT INFO

Any Other Issue

If any issues persist during installation or upgrade, please procure the web service logs from the machine running the self-packager.

Windows

\Program Files (x86)\SelfPackager\intigua-packager-log

Linux:

/opt/rest/intigua-packager-log