VLF-ONE iSeries Deployment Oddities
Posted: Fri Mar 10, 2017 8:58 am
I've deployed the beginnings of our VLF-ONE framework to our dev server that is an IBM i Series.
I am noticing a few oddities as compared to the local version that I don't really understand.
First off, I've included the VLFONE_Engine.js file and locally it works great, on the iSeries however it can't be found. I don't know if the install goofed up or what, but when I look in '/LANSA_dcxpgmlib/x_lansa/x_sys/web/vl' its not there. I can copy that file up there to get it to work, but that seems like a hack to something that broke.
Secondly, locally the Filter/Instance List and Command Handler Window position is remembered whereas when running on the iSeries it is not. For example, locally I enabled "Automatic Tiling" and "Arrange Vertically" and every time I execute that object, either in a new window, tab or the same tab, the windows are in the same place. On the iSeries, when I open a new tab or browser, the Filter/Instance list always shows up maximized and the command windows is always on the bottom.
Lastly, while I am planning on implementing my own LOGON handler, I am using UF_OLOGON at the moment with Framework Authority disabled. Locally, I can put anything in the username and password and get in, however on the iSeries I MUST use a valid iSeries username and profile. Is this by design? I had expected the same behavior on both systems, so was surprised by it automatically requiring me to use a valid username and password.
Has anyone else experienced these things or is it just me.
I am noticing a few oddities as compared to the local version that I don't really understand.
First off, I've included the VLFONE_Engine.js file and locally it works great, on the iSeries however it can't be found. I don't know if the install goofed up or what, but when I look in '/LANSA_dcxpgmlib/x_lansa/x_sys/web/vl' its not there. I can copy that file up there to get it to work, but that seems like a hack to something that broke.
Secondly, locally the Filter/Instance List and Command Handler Window position is remembered whereas when running on the iSeries it is not. For example, locally I enabled "Automatic Tiling" and "Arrange Vertically" and every time I execute that object, either in a new window, tab or the same tab, the windows are in the same place. On the iSeries, when I open a new tab or browser, the Filter/Instance list always shows up maximized and the command windows is always on the bottom.
Lastly, while I am planning on implementing my own LOGON handler, I am using UF_OLOGON at the moment with Framework Authority disabled. Locally, I can put anything in the username and password and get in, however on the iSeries I MUST use a valid iSeries username and profile. Is this by design? I had expected the same behavior on both systems, so was surprised by it automatically requiring me to use a valid username and password.
Has anyone else experienced these things or is it just me.