In IFS Applications 9 the stand alone Batch Server
program has been replaced with the new
Batch Processor concept, which is deployed as a part of ifsapp.ear
Enterprise Application. Therefore the old Batch Server should be stopped
and removed prior to upgrade from IFS Applications 8 earlier.
The default Batch Server instance that is started from the old IFS_HOME will be automatically removed when removing the entire IFS_HOME structure. But this is possible to have other instances of Batch Server, outside of the IFS_HOME structure, on the same or other machines. All those Batch Server instances have to be stopped and removed before upgrading the system.
State handling of Application Messages is slightly
different in the new implementation therefore this is important to see that all
messages are processed prior to upgrade. There should not be any Application
Messages in the system in state other then Finished
,
Failed
, Canceled
, Waiting
or Suspended
.
Messages in obsolete states will be automatically canceled during the upgrade
process.
In IFS Applications 10 the stand alone Connect Server
program has been replaced with the new
Connect Reader framework concept, which is also deployed as a part of ifsapp.ear
Enterprise Application. Therefore the old Connect Server should be stopped
and removed prior to upgrade from IFS Applications 9 earlier.
The default Connect Server instance that is started from the old IFS_HOME will be automatically removed when removing the entire IFS_HOME structure. But this is possible to have other instances of Connect Server, outside of the IFS_HOME structure, on the same or other machines. All those Connect Server instances have to be stopped and removed before upgrading the system.