Save the add-on files in a folder of your choosing and make sure the path to the binary folder is correct in the pkgmsi32.bat (or pkgmsi64.bat) script by editing the WIX_BUILD_LOCATION variable.
Add the custom agent-ca.pem and log4ensics.conf files in the folder.
The files to be deployed can be customized by editing nxlog-conf.wxs.
Finally, execute either the pkgmsi32.bat or the pkgmsi64.bat script, depending on the targeted architecture. While both the resulting MSIs include platform independent files, we strongly advise to build and install the appropriate custom configuration MSI that matches the NXLog installation.
The script will proceed to build the MSI. Depending on the architecture selected, the result will be either nxlog-conf_x86.msi or nxlog-conf_x64.msi.
Comments (3)
could not understand from
Save the add-on files in a folder of your choosing and make sure the path to the binary folder is correct in the pkgmsi32.bat (or pkgmsi64.bat) script by editing the WIX_BUILD_LOCATION variable.
Add the custom agent-ca.pem and log4ensics.conf files in the folder.
The files to be deployed can be customized by editing nxlog-conf.wxs.
Finally, execute either the pkgmsi32.bat or the pkgmsi64.bat script, depending on the targeted architecture. While both the resulting MSIs include platform independent files, we strongly advise to build and install the appropriate custom configuration MSI that matches the NXLog installation.
The script will proceed to build the MSI. Depending on the architecture selected, the result will be either nxlog-conf_x86.msi or nxlog-conf_x64.msi.
Could you please formulate, what confused you exactly?
Regards, Arch
The quick and dirty is