Page History

• mortar
• sap2java

Occasionally problems are found within the code associated with one of these JARs and it must be replaced. This is often done by simply deleting the jar from your applications WebContent/WEB-INF/lib folder and copying the corrected jar from the dist folder of either mortar or sap2java and placing it into your project's WebContent/WEB-INF/lib folder.

...

 mortar

Mortar contains common code needed by our SAP web 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.
Image Removed
Then navigate to SAPBaseAction via Open Declaration and attach the source: Image Removed
 
In the Source Attachment Configuration window click on the Workspace... button. Select the src directory within the mortar project you checked out above.  
 (see attach source).

A number of useful session attributes are set via mortar. Your actions can access these session attributes with the following code:

...

1. CERT (base64EncodedCert)
2. USERNAME (Users Full Name taken from their certificate)
3. KERBID (Users Kerberos Principle taken from their certificate)
4. SAP_SYSTEM_ID (e.g., SF2, SF5, etc)
5. WAS_SYSTEM_ID (e.g., J02?)
6. WAS_HOST (e.g., insidemit-apps-dev)
7. 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 using the tag library searchhelp.tld without any additional code. See the Search Help section on the Development Framework page.

Mortar also handles all the SAP connections and, in particular, any RFC error messages.

 sap2java

See sap2java under tools for a definition of what it is. See FAQ for how to use it to generate proxies.