AX Proggies Neat n Tidy?

[smokeout]

Just curious on best practice for releases of AX. Bottle up stations under diff versions? I have seen people maintain multiple releases. I have read once you upgrade a Jace to current version there is no field downgrade option. Just curious what is being done.

[digo]

Just curious on best practice for releases of AX. Bottle up stations under diff versions? I have seen people maintain multiple releases. I have read once you upgrade a Jace to current version there a field downgrade option. Just curious what is being done.

Since 3.4 was officially released today for our OEM channel (webs), this is a great topic.

With a demo license, we can run any release - but there's a need to keep everything separate. We have customers on 3.1, 3.2, 3.3, and pretty soon 3.4. A customer's license is permanent (never expires), but is limited to the major rev currently installed.

Keeping each installation in its own folder, and remembering to run the correct platform daemon is key to keeping things straight. Also, programming changes to a live station on remote hosts should be done with the correct rev of workbench.

local platform views are also affected by the daemon currently running. The Software manager view is one of those affected by this. Otherwise you can be fooled into thinking you modules are out-of-date when they shouldn't be or vice-verse.

[Chris_Worthington]

and remembering to run the correct platform daemon is key to keeping things straight.

Often, an over looked step :eek:

[digo]

A good way to avoid this is to create batch files to launch the appropriate plat daemon prior to starting workbench.

something like:

WEBStation-AX-3.4.43.bat

CD C:\Honeywell\WEBStation-AX-3.4.43\bin\
START plat.exe installdaemon
START wb_w.exe && EXIT

[d ward]

With R2 I know that we had to use batch files but with AX can’t we just use the “Install platform demand” that is in the version program file?

[digo]

With R2 I know that we had to use batch files but with AX can’t we just use the “Install platform demand” that is in the version program file?

Yes, you can use it. The batch file is a solution to replace those two shortcuts, that way you'll never forget to run the daemon first when switching among installations.

Also, the "plat.exe installdaemon" command simply registers niagarad.exe as a service in windows. Right-click My Computer-> Manage, and look at the properties of the Niagara service. Path to executable will tell you which version is being used.

[foyler]

digo,

Thanks for the batch file info.

Works for FX Workbench with:
CD C:\JCI\FXSupervisorPro-2.0\bin\
START plat.exe installdaemon
START wb_w.exe -profile:jciFxDriver:JciApplianceProfile && EXIT

and FX Workbench Pro with:
CD C:\JCI\FXSupervisorPro-2.0\bin\
START plat.exe installdaemon
START wb.exe -profile:jciFxDriver:JciFullApplianceProfile && EXIT

I was having trouble with the platform in Workbench 1.2. This should take care of it.