Resolve runtime problems

To resolve runtime errors on the application server, see the file svc.out in the appsvr log directory. You can examine the exception.log and default.log files to resolve runtime problems.

The Java™ file naming convention makes it easy to identify which script failed. The error message also identifies the line number in the generated Java file. To resolve the problem, view the generated Java file and scroll to the line where the runtime error occurred. The generated Java code includes script code as comments every few lines. For example, consider the following portion of code from a sample generated Java file. 
// function checkIfPartyPartyTypeExist(party, partyType) 

    public static Object ScriptFunction__
checkIfPartyPartyTypeExist(HashMap hmContext, 
Object party, Object partyType) throws Exception

    { 

        // var bRet = false; 

        Object bRet = (java.lang.Boolean) Boolean.FALSE;  

        // var rootEntry = party.getRootEntryNode(); 

        Object rootEntry = GenGetRootEntryNodeOperation.
execute(hmContext , (IEntry) party); 

        // var entryNodes = rootEntry.getEntryNodes
(getCatalogSpecName() + "/Party Types/Party Type Code"); 

        Object entryNodes = GenGetEntryNodesOperation.execute
(hmContext , (EntryNode) rootEntry, (String) 
BinaryOperation.execute(BinaryOperation.PLUS, 
ScriptFunction__getCatalogSpecName(hmContext), 
"/Party Types/Party Type Code")); 

        // var entryNodesSize = entryNodes.size(); 

        Object entryNodesSize = (java.lang.Integer) 
GenSizeOperation.execute(hmContext , (HashMap) 
entryNodes);
The comments that are highlighted in bold above are code from the corresponding script. This makes it easy to identify where failures occurred in the script.