Connect LQE with your dev environment - quality-manager/onboarding GitHub Wiki

How to connect your dev environment to LQE

Follow the instructions in Register a QM Development Environment with a Remote JTS.
- You don't need to set up GC if you don't need it, you just need to be registered under JTS.
- Be sure that the remote server you are connecting has JRS and LQE installed
- Assure your remote server can connect to your dev environment, add your dev env to hosts file if needed
Go to remote server and open LQE: https://remoteserver:port/lqe
Add your local dev env as TRS source
- In LQE go to Administration -> Add data source -> https://yourdevenvhost:9443/jazz/trs2
- Repeat the operation to process-resources Add data source -> https://yourdevenvhost:9443/jazz/process-trs2
Go to "Permissions" and add "everyone" group in QM Resources and Qm process resources
- Additionally I add the user I am using (qmuser) in the user tab, not really necessary but allows to bypass a couple of restrictions when invoking the trs2feed locally
Go to Report builder https://remoteserver:port/rs, select Lifecycle Query Engine as data source and you should be able to see your local project area

Troubleshooting

My local project area is not listed in Report Builder
- Check the permissions tab in LQE mentioned in previous step, if you are not sure what is the appropriate QM tab, add the "everyone" group to the root "LifecycleQueryEngine cycle"._
Still my project area is not listed
- Check steps in Register a QM Development Environment with a Remote JTS, assure you followed every step, the second more common cause is that you didn't add your user to the project area_

Notes and tips

Now that your dev env has been connected to LQE have in mind that LQE has a delay when fetching the data from your dev env so if you want to be 100% sure LQE has the latest data you can use "Force update" in QM data source.
You need to keep the host file in the remote server updated if you are not using a remote server in the same LAN, more so if you are using a remote JTS server on IBM infrastructure, remember the VPN's IP address changes every time you connect, if the remote server can't see your dev environment then it is going to display the node as down and you will be only able to report on stalled data.
If you are doing changes to resources or shapes have in mind how TRS works, if a modification event was not sent then it is not going to fetch the latest data and you won't see your changes, if you don't want to modify the resource then a reindex is recommended.
... more to come.****