Page History

...

1. The method edu.mit.mortar.controller.action.GlobalEntryAction.execute is called and a session is created and the following session attributes are set:
   1. GlobalKeys.SAP_SYSTEM_ID
   2. GlobalKeys.WAS_SYSTEM_ID
   3. GlobalKeys.WAS_HOST
   4. GlobalKeys.USER_HOME
2. Your action (which has been configured to chain after /EntryAction) is called which immediately calls the method IDDAction.execute which sets the following session attributes:
   1. GlobalKeys.CERT
   2. GlobalKeys.USERNAME
   3. GlobalKeys.KERBID
3. At the end of IDDAction, SAPBaseAction.doProcess is called which opens a connection to SAP.
4. At the end of SAPBaseAction, your action's method doAction is called within a MessageRuntimeException try catch. (If an Exception is encountered
5. If your action's method doAction calls a SAP RFC, SAPServiceSupport.execute is called and if an error is returned from the SAP RFC at this point, processing will stop and the user will either stay on the same page displaying the error message if an action inputhas been defined with the current jsp in the struts-config or they will be sent to the GlobalKeys.FAIL jsp page with a MessageRuntimeException unless your action intercepts the MessageRuntimeException and handles it.)If your action's method doAction calls a SAP RFC, SAPServiceSupport.execute is eventually called and

This provides automatic RFC error message handling (i.e. it takes all rfc messages and stores them into the struts actionmessages automatically).