When you start to use application edition manager, you
might come across some questions about the application edition manager
functionality.
Can the application edition manager ensure interruption-free
application upgrade for workloads that are driven by Internet InterORB
Protocol (IIOP) or Java Message
Service (JMS) protocols?
No. The application edition manager
can ensure interruption-free application upgrades only for workloads
managed by the on demand router (ODR). The ODR supports HTTP and HTTPS
only.
Can the application edition manager ensure interruption-free
application upgrades for workloads that include calls between Java Platform,
Enterprise Edition (Java EE) Version 5 applications?
Yes, the application edition manager can ensure an interruption-free
update if each interapplication request uses HTTP or HTTPS protocol
through an on demand router.
Can the application edition manager ensure interruption-free
application upgrades for workloads that are hosted on static clusters?
Yes, if an on demand router is managing the work sent
to that static cluster.
Can the application edition manager support the deployment
of one edition of an application to one cluster and the deployment
of another edition to a different cluster?
Yes. The application
edition manager supports different editions simultaneously deployed
on different targets. You must establish routing policies for routing
traffic to different editions.
Does the application edition manager support the activation
of different editions on different members of the same cluster?
No.
Does the application edition manager restart the application
or the entire server to activate a new edition?
No, the
application edition manager does not restart the application or server.
You must perform the following steps:
- Stop the active edition.
- Deactivate the active edition.
- Activate the new edition.
- Start the new edition.
Can the application edition manager handle the rollout
of editions with incompatible changes?
Yes, the application
edition manager can handle this situation if the on demand router
is configured to perform edition-aware routing. For more information
about edition-aware routing, read about edition compatibility.
Can the application edition manager handle the rollout
of editions that include database schema changes?
Yes,
you can perform rollout of editions that include database schema changes
if the database changes are compatible with earlier versions.