EBS Forms JWS Migration Checklist and Troubleshooting

The JWS migration process requires applying several specific patches to your EBS instance, which you must first identify using Oracle Support Document 2188898.1. After preparing the environment, the patches are typically applied using the `adop phase=apply` command, often merged into one application phase. Following the patch application, a crucial step is to run `adadmin` to explicitly regenerate all product JAR files, ensuring you select the FORCE option set to ‘Yes’ when prompted to guarantee complete regeneration. Finally, the entire `adop` cycle must be completed, including the `actualize_all`, `finalize`, and `cutover` phases.

This sounds like a configuration issue, possibly related to how the nodes are registered or how the forms launcher profile is configured in the load-balanced environment. You need to verify the configuration of the ‘ICX: Forms Launcher’ system profile to ensure it is correctly pointing to the appropriate URL or load balancer endpoint. Additionally, you should run a query against `apps.fnd_nodes` to inspect the registration status (`support_forms` column) and the `webhost` defined for each of your application nodes to identify inconsistencies.

To test JWS functionality selectively, you can enable it only for specific application users by configuring profile options at the user level. You must set the profile option ‘Enable Java Web Start’ to ‘Yes’ for the designated test users. This allows your test group to use JWS without immediately impacting the rest of the production user base.

Unfortunately, Oracle no longer supports the Look and Feel options of previous releases after applying certain ATG patches like R12.ATG_PF.C.Delta.5 and higher. If your UIX version upgraded to 12.2.6, Oracle explicitly states that only the ‘Alta Look and Feel’ is supported with JWS; customization with SWAN or SKYROS is not supported. This is a standard consequence of moving to the modern JWS architecture.