Gateway Name and dev/prod enviroment

Ignition
1

Hi everyone,

I've been searching through the forum but haven’t found a clear answer to this issue.

We have two Ignition gateway instances: one for QA purposes and another for Production. Both are on the client network. However, we’ve run into a problem during deployment: since the history tag bindings include the gateway name in their path, none of our tag bindings work after importing the project from QA to Production.

What’s the best way to handle this? Is there a recommended approach to avoid this issue or make the deployment process smoother?

Thanks in advance for your help!

2

Sorry do you mind expanding with an example of the paths that you are providing? I get the general issue that you are describing, but I have never encountered such an issue (never had a Gateway name in any of our bindings paths).

3

In this image, you can see the tag path used for the tag history binding.

Currently, the gateway names vary depending on the environment:

  • For Development, the gateway name is "ignition-griga-iotwadev1".
  • For QA, the gateway name is "ignition-griga-iotwaqa1".
  • For Production, the gateway name is "ignition-griga-iotwaprd1".

mRemoteNG_JwcuYgYqiD
mRemoteNG_JwcuYgYqiD675×605 67.4 KB

1 Like
4

Have you tried removing the gateway name? Typically, I have only seen and used the form of [TagProvider]TagPath, though I do rarely work directly with Historical Tag Paths. Have you considered using a global tag and expressions to automatically format the provider name for you?

For example:

[GatewayTagValue:TagProvider] TagPath

5

I think expressions are not allowed on "Direct" tags and can only be used in the "Expression" binding type. By this, I mean the two radio buttons in the "Select Tags" section of the Tag History Binding configuration.

I was hoping to avoid using custom expressions and the "Expression" binding type and find a different way to solve this issue.

6

Consider trying to reduce your tag path down to [Provider] TagPath and see if that does anything for you?

7

History is always stored with meta data that includes the name of the source gateway.

Redesign your application to use dynamic tag paths everywhere, so that your UI automatically adapts to the gateway you run it in.

Or, better, set up completely isolated dev and QA environments so the gateway name doesn't have to be changed.

1 Like
8

Tried, but does not work.

9

When you mention dynamic tag paths, are you referring to using the expression in the tag history binding? I was hoping to avoid that approach.
I'll consider using the same name for all three gateways instead.

10

Yes. Any time you don't use that you are boxing yourself into a very non-flexible, hard to maintain design.