There is probably a more elegant approach but I took what is provided from broadcom and created a zip file which house all the files necessary to run appworx - in addition connection.properties pre-populated with the connection values and cert/key files also required.
Instructions are to extract the the contents of the zip to their desktop, and to kick off appworx I have the following batch file:
@echo off
::Variables::
SET APPWORXDIR="%USERPROFILE%\.Appworx"
SET CERTDIR=%~sdp0Client\cert\
::Creates .appworxdir under user profile if it doesnt exist
::Copies required keystore files to communicate with appworx
IF not exist %APPWORXDIR% mkdir %APPWORXDIR% 2>&1
COPY /Y %CERTDIR%\keystore%APPWORXDIR% 2>&1
COPY /Y %CERTDIR%\keystore_config %APPWORXDIR% 2>&1
::Execution of appworx
cd %~sdp0Client
java -jar RunClient.jar
hope that helps
Original Message:
Sent: 04-02-2020 10:35 AM
From: Xavier Western
Subject: Applications Manager 9.3+ Client
How is everyone packaging/distributing the new Applications Manager Clients? For our last upgrade 9.3.0, we created an executable that placed the necessary files where they needed to be. With the next upgrade, it looks like the majority of files will need to be deleted for the new client to work, one issue with this is that the .jar files will not necessarily be the same location for all users.
Are people having end-users updated their own clients or are you somehow packaging it for them?