This guide explains how to create and deploy a new Connector Service in JetPatch 5.0 using the built-in upload image and auto-service provisioning feature, introduced in version 5.0.
Overview
JetPatch 5.0 and above simplifies connector deployment by allowing administrators to upload connector images (.vai and .bsx files) directly through the UI. Once uploaded, JetPatch automatically provisions a new Connector Service, making it available for deployment to selected endpoints.
1. Prepare Your Connector Files
Before starting, ensure you have:
.vai, .bsx, .exe files for supported OS (e.g., Windows, Linux, etc.,).
2. Upload the Connector Image in the UI
Log in to the JetPatch Web UI with admin privileges:
https://<Your_JetPatch_Server_IP>Navigate to:
a) On Fresh Installation:
To upload connector images for the first time:
Agents → Managed Agents → Upload Image
b) After Uploading the Images:
You can view them under:
Agents → Managed Agents → (JetPatch) → ImagesClick on “Upload Image”
-
Uploading Connector Installer Images
When uploading connector images in JetPatch, follow the steps below carefully to ensure a successful upload and automatic service creation:
In the Upload Image Dialog:
Click “Browse Files” or drag-and-drop the following files into the dialog:
.vaifiles.bsxfiles.exefiles
Wait for Installer Analysis
After selecting the files, JetPatch will automatically begin analyzing the uploaded installers.
During this process, the “Upload” button will be disabled.
Click Upload Once Enabled
Once JetPatch finishes analyzing and validating the installer files, the “Upload” button will become enabled.
Click Upload to begin the actual upload process.
Monitor Upload Progress
Wait until the upload completes.
On success, JetPatch will automatically create a corresponding Connector Service entry based on the uploaded image version and OS type.
3. Auto-Creation of Connector Service
After a successful upload of the connector image files:
JetPatch automatically creates a new Connector Service entry.
Verifying the Created Service:
Navigate to:
Agents → Managed Agents → JetPatch → ServicesLocate the newly created Connector Service in the list.
-
Verify Service URLs:
Check the Primary URL and Secondary URL values associated with the service.
Ensure the URLs are correct and point to a valid and reachable JetPatch server endpoint.
If the URLs are incorrect, the connector may fail to install or communicate with the JetPatch server properly. So, Edit and update them as https://Your_JetPatch_Server_IP_:8443
4. Deploying the Connector to Endpoints (EP) Using the Created Service
Once the connector image has been uploaded and the corresponding Connector Service has been automatically created, you can deploy it to one or more endpoints directly from the JetPatch console.
Steps to Deploy the Connector:
1. Navigate to Endpoint Management:
Go to:
Platform Configuration → Servers
2. Select Target Machines
Before deploying the Connector Service, you must assign the appropriate credentials to each target machine.
Assign Accounts:
Each target server requires a valid account (with necessary privileges) to allow installation.
Navigate to the Servers view and assign an account to each machine as needed.
- Please check assign account for more details.
Select Servers for Deployment:
Use the checkboxes to select one or more servers where you want to deploy the Connector Service.
Ensure that each selected server has an account assigned before proceeding.
3. Open Connector Management Window:
Click on Server Actions → Manage Intigua on Server
A new configuration window will open
4. Enable and Assign Connector Service:
-
In the new window:
Enable the "Manage Intigua on Server" option
From the Connector Service dropdown, select the newly created service (from Step 3)
Click Apply to initiate deployment
JetPatch will trigger the connector installation process on the selected servers.
5. Post-Deployment Validation:
After deployment:
Go to Platform Configuration → Servers
-
In the Status column of the respective machine, you will see a symbol:
The icon will appear in GREEN, and when you hover over it, it should display “Connected”, indicating that the server is reachable.
Comments
0 comments
Please sign in to leave a comment.