...
...
...
...
...
...
...
...
...
...
...
...
| Table of Contents |
|---|
Haystack Compatibility
Below are some builds we have tested with. Go ahead and take a look based on what you have and see what is needed to get it connected. If what you have matches but get an error still, look at Haystack Troubleshooting to see if your issue can be resolved from there.
It is recommended to always verify if the same credentials work when connecting to the station via browser. If not, likely you have incorrect credentials or you have N4 with basic authentication set up on user which doesn't allow you to connect via browser or station. If the latter, then you are fine, otherwise you'll need to figure out why you can't connect through the browser first before even trying in FIN Stack. If you can't hit it in the browser, then chances are you won't hit it with FIN Stack either.
Where to find "HTTPBasicScheme"? This can be found in your Baja module on the Palette. Just add that to your Authentication Scheme Service.
Also, just a side note, we have heard Tridium has a bug when migrating users from AX to N4. Something about the authentication is broken. So it is recommended to create a new super/admin user and use that to connect to FIN Stack.
You can find the nHaystack modules N4 here (soon to add AX): https://stackhub.org/package/nHaystack (in the mean time for AX, you can find them here: https://bitbucket.org/richiemac_77/nhaystack/downloads/)
The below FIN Stack versions are referring to the framework version not build version.
HTTP Configuration with Standard FIN
...
Install
| Code Block |
|---|
AX3.7.106.1 with FIN |
...
v2.1.15 - nHaystack v1.3.0, AuthScheme as Basic/Digest = works |
...
AX3.7.106.1 with FIN |
...
v3.0.13 - nHaystack v1.3.0, AuthScheme as Basic/Digest = works |
...
AX3.8.213 with FIN |
...
v2.1.15 - nHaystack v1.3.0, AuthScheme as Basic = works |
...
AX3.8.213 with FIN |
...
v3.0.13 - nHaystack v1.3.0, AuthScheme as Basic/Digest = works |
...
AX3.8.311 with FIN |
...
v2.1.15 - nHaystack v1.3.0, AuthScheme as Basic = works |
...
AX3.8.311 with FIN |
...
v3.0.13 - nHaystack v1.3.0, AuthScheme as Basic/Digest = works |
...
N4.2.36.38 with FIN |
...
v2.1.15 - nHaystack v2.0.1, AuthScheme as DigestScheme = works |
...
N4.2.36.38 with FIN |
...
v3.0.13 - nHaystack v2.0.1, AuthScheme as HTTPBasicScheme = works |
...
N4.3.58.18 with FIN |
...
v2.1.15 - nHaystack v2.0.1, AuthScheme as DigestScheme = doesn't work with original haystack pod (need custom haystack pod, look below) |
...
N4.3.58.18 with FIN |
...
v3.0.13 - nHaystack v2.0.1, AuthScheme as HTTPBasicScheme = works |
...
N4.4.73.24 with FIN |
...
v2.1.15 - nHaystack v2.0.1, AuthScheme as DigestScheme = doesn't work with original haystack pod (need custom haystack pod, look below) |
...
N4.4.73.24 with FIN |
...
v3.0.13 - nHaystack v2.0.1, AuthScheme as HTTPBasicScheme = works |
...
N4.7.109 with FIN |
...
v2.1.15 - nHaystack v2.1.2, AuthScheme as DigestScheme = doesn't work with original haystack pod (need custom haystack pod, look below) |
...
N4.7.109 with FIN |
...
v3.0.18 - nHaystack v2.1.2, AuthScheme as DigestScheme = works |
HTTPS Configuration with Standard FIN
...
Install
| Code Block |
|---|
AX3.7.106.1 with FIN |
...
v2.1.15 - nHaystack v1.3.0, AuthScheme as Basic/Digest = works |
...
AX3.7.106.1 with FIN |
...
v3.0.13 - nHaystack v1.3.0, AuthScheme as Basic/Digest = works |
...
AX3.8.213 with FIN |
...
v2.1.15 - nHaystack v1.3.0, AuthScheme as Basic = works |
...
AX3.8.213 with FIN |
...
v3.0.13 - nHaystack v1.3.0, AuthScheme as Basic/Digest = works |
...
AX3.8.311 with FIN |
...
v2.1.15 - nHaystack v1.3.0, AuthScheme as Basic = works |
...
AX3.8.311 with FIN |
...
v3.0.13 - nHaystack v1.3.0, AuthScheme as Basic/Digest = works |
...
N4.2.36.38 with FIN |
...
v2.1.15 - nHaystack v2.0.1, AuthScheme as DigestScheme = works |
...
N4.2.36.38 with FIN |
...
v3.0.13 - nHaystack v2.0.1, AuthScheme as HTTPBasicScheme = works |
...
N4.3.58.18 with FIN |
...
v2.1.15 - nHaystack v2.0.1, AuthScheme as DigestScheme = doesn't work with original haystack pod (need custom haystack pod, look below) |
...
N4.3.58.18 with FIN |
...
v3.0.13 - nHaystack v2.0.1, AuthScheme as HTTPBasicScheme = works |
...
N4.4.73.24 with FIN |
...
v2.1.15 - nHaystack v2.0.1, AuthScheme as DigestScheme = doesn't work with original haystack pod (need custom haystack pod, look below) |
...
N4.4.73.24 with FIN |
...
v3.0.13 - nHaystack v2.0.1, AuthScheme as HTTPBasicScheme = works |
...
N4.7.109 with FIN |
...
v2.1.15 - nHaystack v2.1.2, AuthScheme as DigestScheme = doesn't work with original haystack pod (need custom haystack pod, look below) |
...
N4.7.109 with FIN |
...
v3.0.18 - nHaystack v2.1.2, AuthScheme as DigestScheme = works |
For HTTP, make sure "Https Only" is disabled if HTTPS is enabled.
For AX3.5, you will need a concurrent jar - https://project-haystack.org/forum/topic/306
Custom Haystack Pod - N4.3+ with FIN
...
v2.1.15
If you are trying to connect to a N4.3.58.18 station or newer via FIN Stack v2.1.15 use the below custom pod. This will allow you to connect to AX and N4 stations simultaneously. You'll need to do the below steps:
Install latest nhaystack jar files for N4 here: https://stackhub.org/package/nHaystack
How to install nhaystack jar modules here.
Add NHaystackService to services container (go to palette and find nhaystack)
Then right click on NHaystackService to Initialize it
Make sure web service http or https ports are open depending on which you use
Create a new user account and set Authentication Scheme
as DigestSchemeas
DigestSchemeThats it on the Niagara side, then on the FIN
StackFramework side, stop the service
Install this custom haystack pod in the fan folder in the FIN
Stackdirectory (Should look something like this:
C
StackC:\Program Files (x86)\FIN
StackFramework0\FINFramework <your version>\lib\fan):
https://drive.google.com/file/d/1B1W9RPvJltGRjWNKh4HO9yVl8Yx8-BwA/view?usp=sharingStart the service and you should be good.
Tridium Patches
Below are some issues customers have come across that required Tridium patches. If you have any of the issues below, contact your Tridium vendor to get the correct patch to resolve the issue.
If you have N4.3.58.18.3 and JACE crashes, you'll want to try the patch Tridium released to resolve a memory leak issue. The patches mentioned can found below or towards the end of this forum: https://project-haystack.org/forum/topic/537. Released around Jan 22, 2018.
jetty-rt 4.3.58.22.7web-rt 4.3.58.22.7
Having authentication issues between
AX3.8.213andAX3.8.311? If you can't connect when upgrading to one of these AX versions, you'll want to get the below patch from your Tridium vendor. Released around May 14, 2018.web-rt 3.8.312.1