OE 11.6.3 x64 on Windows 10 and Ubuntu server 16.04.
When I create a PASOE instance on both platforms with:
tcman.sh (or .bat) create -p ... -P ... -s ... -N as-oerest-dev1 ./as
as/bin/tcman.sh (or .bat) deploy -a testapp <DLC>/servers/pasoe/extras/oeabl.war
Then all the configuration settings in conf/openedge.properties look like this on Linux:
However, if I look the same settings on windows, they look like:
This is kind of annoying because when I want to change these settings via oeprop I have to address the same property for the same ABL Webapp in two different ways. I would consider this a bug. What would you guys think?
Aha! I don't use the instance name in the tcman deploy.
The help states:
$ bin\tcman.bat help deployusage: tcman deploy [options] -u <uid:pwd> [-a <app-name>] <war-file-path>
The help doesn't even mentions that possibility...
So when I deploy an ABL webapp I use the following:
bin\tcman deploy -a testapp %DLC%\servers\pasoe\extras\oeabl.war
without the instance name. Ok, that doesn't explain btw why there's a difference between Linux and Windows because I used the same tcman deploy twice.
This is kind of annoying because when I want to change these settings via oeprop I have to address the same property for the same ABL Wepapp in two different ways. I would consider this a bug. What would you guys think?
You received this notification because you subscribed to the forum. To stop receiving updates from only this thread,
post as spam/abuse.
Architect of the SmartComponent Library and WinKit
What is definitely is a bug is that on Windows in OEM when I click the ABL application "as-oerest-dev1" there's is only 1 ABL WebApp listed: ROOT (not testapp). On Linux there are two ABL WebApps listed: ROOT & testapp. I'm going to contact TechSupport on this.
Please contact techsupport. I will try to reproduce the problem at my end.
I actually did, the case number is: 00383135
In fact it's two cases in one: one for the difference in the config files and one for the ABL Webapp not showing up in OEM. These might be related however.
I tried to create the instance similar to what you have done and it kind of worked fine to me.
pasman create -p 2411 -P 2511 -s 2611 -N oe-rest-app myApp1
tcman deploy -a temp-124 %DLC%\servers\pasoe\extras\oeabl.war oe-rest-app
OfCouse, I was testing it on Windows7 and you have tested it on Windows10 for 11.6.3.But, I have tested the same on 117ESAP on Win10 and it seem to work fine too.
for the record: if I add the instance name after the oeabl.war path I can confirm that works.
And to be precise: if I omit the instance name and the instance is installed in c:\temp\pasoetest1\hoppa the webapp's settings are in the openedge.properties like this:
that's definitely a bug...
I definitely consider it as a bug, I am just trying to reproduce the problem. I will try to reproduce it as per your steps and log a bug.