Cannot load page while trying to open BPEL console

It is a very common issue that happens basically when we apply a patch set or MLR on our SOA Suite.

First of all whenever we updated or upgrade our SOA Suite we must ensure that we have taken proper bakcup and have performed all the pre and post installation tasks.

Still if you are facing issue then you may need to follow these steps

Compare $ORACLE_HOME/bpel/system/services/lib/orabpel.ear with $ORACLE_HOME/j2ee/oc4j_soa/applications/orabpel.ear

Delete all the entry in $ORACLE_HOME/j2ee/$CONTAINER/application-deployments folder

Check if size of $ORACLE_HOME/bpel/system/j2ee/orabpel.ear equals $PATCH_HOME/files/bpel/system/j2ee/orabpel.ear. If not then take a backup of $ORACLE_HOME/bpel/system/j2ee/orabpel.ear and copy $PATCH_HOME/files/bpel/system/j2ee/orabpel.ear to that location.



Again Check if size of $ORACLE_HOME/bpel/system/services/lib/orabpel.ear equals $ORACLE_HOME/j2ee/$CONTAINER/applications/orabpel.ear. if not then take a back up of $ORACLE_HOME/j2ee/$CONTAINER/applications/orabpel.ear and copy the one from $ORACLE_HOME/bpel/system/services/lib/orabpel.ear

Once done these changes restart your container and check if the issue still persists.
If you are facing the same issue with the human workflow page then you can do the same for the hw_services.ear.


Some times when you log in to your BPEL or esb console using http://host:port/BPELConsole it is automatically redirected to http://host:port/BPELConsole/login_error.jsp page and you are not able to log in to console.This error can be solved by just removing the login_error.jsp from the address bar and then you can log in to the BPEL console.Reason is that the OC4J instance uses the parameter ‘-Doc4j.formauth.redirect=true’, and OC4J does not redirect correctly.This was a bug and has been resolved in the latest release.