WDA application differs across application servers

[Former Member]

Hi,

when transporting from dev to Q, with Q running on 4 different app servers, we see different behaviour of our WDA application. This manifests itself as (for instance) columns of tables not being in the same positions, and also different column widths within the same tables.

It may be down to the different app servers running different versions of the WDA application, but then my question would be: how do we ensure all app servers are "synchronized" whenever we release a new transport? As of now, the users report conflicting test results based on the app behaving differently depending on which app server they happen to be routed to...

OSS doesn't seem to hold any clues to this kind of behaviour. Would a simple flush of the browser cache be sufficient, or is this to do with the app servers themselves (cache, memory, whatever...?)

Regards,

Trond

[abhimanyu_lagishetti7]

I don't believe that the app servers holding different versions of a program, it should be same across the systems.

Pl check with the following:

Column's width changes based on its content if no width is set to the column.

also,

Users can always personalize the column positions, if personalization is set.

Thanks

Abhi