The two MIT custom created/maintained JARs are:
- mortar
- sap2java
mortar
Mortar contains common code needed by our SAP apps. All of your actions should be subclasses of SAPBaseAction whose code you can access via Open Declaration -> Attach Source...
First check out the version of mortar used by your application via SVN mortar -> tags -> version of interest.
Then navigate to SAPBaseAction via Open Declaration and attach the source:
In the Source Attachment Configuration window click on the Workspace... button. Select the src directory within the mortar project you checked out above.
A number of useful session attributes are set via mortar. Your actions can access these session attributes with the following code:
String usefulAttribute = (String)request.getSession().getAttribute(GlobalKeys.xxx);
where xxx is one of the following constants:
- CERT (base64EncodedCert)
- USERNAME (Users Full Name taken from their certificate)
- KERBID (Users Kerberos Principle taken from their certificate)
- SAP_SYSTEM_ID (e.g., SF2, SF5, etc)
- WAS_SYSTEM_ID (e.g., J02?)
- WAS_HOST (e.g., insidemit-apps-dev)
- USER_HOME (Where restart should go to)
Mortar 4.10 and above also handles search help which means search help can be implemented on any web page via the tag library searchhelp.tld without any additional code. See the Search Help on the Development Framework page.