You'll be prompted to save the file for later use. Please select where you wish to store the file and click 'Save'. There is also an option to cancel if you no longer want to save the file.
Should you wish to use the automatic installation script in a future automatic install of the MESH Client, the command syntax is:
java -jar mesh-6.3.6_20220906-installer-signed.jar auto-install.xml
The installation of the MESH client is now complete. A few further configuration steps must be undertaken before the MESH client is available for use.
The MESH client will have been installed in your chosen folder. Find this folder (if you did not adjust the install destination previously, it will be in 'MESH-APP-HOME'). You should have a series of folders, including 'log', 'proxy' and 'KEYSTORE'. The following configuration steps require access to the files beneath these folders on the list.
Open the meshclient.cfg file in a text editor (such as Notepad or Wordpad). There are three lines to edit in this document. Please edit the bold sections, shown below:
<ClientAuthentication>InsertYourMailboxPasswordHere (it will currently say “ClntAuth1”)</ClientAuthentication>
Your mailbox ID and client authentication will have been confirmed when you applied for your mailbox during the pre-requisite checks. 'Client Authentication' is also known as your mailbox password. You will have made your Keystore password when applying for your endpoint certificate during pre-requisite checks.
The Keystore path refers to the location of your MESH Keystore file (C:\MESH-APP-HOME\KEYSTORE\MESH.keystore for example). You will have made your Keystore password when applying for your endpoint certificate during pre-requisite checks.
If using the MESH client on a non-Windows based server, the above process can be used and the MESH.keystore copied to the server and configured in the same way.
If you'll be accessing the MESH client via the Internet, rather than using the default N3/HSCN network, the following parameters will need to be changed in the mesh.cfg file:
<PrimaryURL> - this needs to be set to: https://mesh-sync.spineservices.nhs.uk
<Keystore> - will need to be set to the name of your KeyStore
For API installation only, the configuration of your certificate will vary depending upon your current systems.
Further configuration changes are available from the default settings, if you wish. Our Advanced and other settings page details many changes that can be implemented, including:
meshclient.cfg file: the maximum and minimum number of messages that can be sent per poll.
Proxy: setting up your MESH client if you sit behind or use a proxy server.
log4j2.xml file: how detailed the logging levels of your MESH client will be. This refers to a log that MESH client produces of all actions, such as start-up, sending data, receiving data, and any message errors. The logs are helpful to refer to if your files fail to send correctly.
Once all the configuration changes have been saved the client can be started by double clicking the runMeshClient.bat. If the client is running you will see the log file generated in the folder defined in the meshclient.cfg file. The default folder location for the log file is \MESH-APP-HOME\log for a new MESH installation.