This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
I have a conditional expression that is supposd to check a PO Line for $0.00 and make the POLINE.LINECOST and POLINE.UNITCOST readonly after the PO has been approved, even if the PO is set back to WAPPR. The condition is:
:linecost = 0.00 and exists (select 1 from postatus where ponum=:ponum and status='APPR')
When I test this out in our DEV environment, on a single JVM instance, it works perfectly. But when I apply it in our PROD environment, which is a virtually clustered Websphere instance with two JVM's, the restriction doesn't work.
Anyone have any issues with single JVM vs clustered?
Hi,
We have thirteen application servers, three in each UI server and four in the report server. We have several conditions on different applications.
If you make an application design change then it does not take effect in the other servers until you restart them or export and import the application design.
I always go to one application server using the port
http://servername:9083/maximo/webclient/login/login.jsp
Then make the changes in the application and export and save the application design.
Then I go to the next server
http://servername:9081/maximo/webclient/login/login.jsp
and import the application design.
I have to import it to all 12 to get them all in synch.
But at least I do not have to restart the application servers.
Dave Bone
--- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@...> wrote:
>
> I have a conditional expression that is supposd to check a PO Line for $0.00 and make the POLINE.LINECOST and POLINE.UNITCOST readonly after the PO has been approved, even if the PO is set back to WAPPR. The condition is:
>
> :linecost = 0.00 and exists (select 1 from postatus where ponum=:ponum and status='APPR')
>
> When I test this out in our DEV environment, on a single JVM instance, it works perfectly. But when I apply it in our PROD environment, which is a virtually clustered Websphere instance with two JVM's, the restriction doesn't work.
>
> Anyone have any issues with single JVM vs clustered?
>