After generating a new folder with the instrumented code of your Front-End application, the content of this folder needs to be deployed instead of your original code on the server for the client browser to work against.
If you’re using labIDs , please refer to the following documentation Front end application as part of an Integration Build for the additional commands required to manage labId parameters in your deployment steps.
Deploying the folder containing the instrumented code
For example if your original folder was named ‘dist' and the new folder with the instrumented code is 'sl_dist’, you can follow the steps below:
Rename the original folder from ‘
dist’ to ‘dist_original’Windows OS: rename dist dist_original Linux/Unix OS: mv dist dist_original
Use the instrumented folder instead using one of the following options by renaming the ‘
sl_dist’ to ‘dist’Windows OS: rename sl_dist dist Linux/Unix OS: mv sl_dist dist
On Unix/Linux system you also have the ability to define a ‘dist’ soft link to the ‘sl_dist’ folder.
ln -s sl_dist dist
Validate the Instrumentation and build number in the JS source from the Browser
In your Browser, open the source code of your JS page: is there the Sealights' instrumentation code and the right build number at the beginning of the page ? If Yes, all is set.
