# MediationZone 9.3 - Logging และ Error Handling Guidelines ## ภาษาที่ใช้ MediationZone 9.3 ใช้ **APL (Array Programming Language)** ไม่ใช่ Java ### ลักษณะสำคัญของ APL - เป็นภาษาเชิงวัตถุ (Object-oriented) - ออกแบบมาเฉพาะสำหรับการประมวลผลข้อมูลทางโทรคมนาคม - ทำงานบนพื้นฐานของ "Cartridges" และ "Workflows" - ใช้ร่วมกับ DML (DigitalRoute Mediation Language) ### Syntax พื้นฐาน ```apl // Variable declaration string channelName = ""; int portNo = 22492; boolean isConnected = false; // Collections list ports = listCreate(int, 22492, 22493, 22494); // Conditionals if(condition) { // code } else { // code } // Loops for(int i=0; i ports = listCreate(int, 22492, 22493, 22494); boolean success = false; for(int i=0; i ports = listCreate(int, 22492, 22493, 22494); for(int i=0; i-apl-log4j.properties` ```properties # EC-specific logging log4j.rootLogger=INFO, FILE log4j.appender.FILE.File=${pico.tmpdir}/-apl.log ``` #### Suppress Specific Errors ```properties # Suppress TCP Forward agent errors (show as INFO instead) log4j.logger.com.digitalroute.tcpipforw=INFO log4j.logger.com.digitalroute.tcpipforw.netty4.TCPForwardClient=INFO ``` **Apply changes:** Restart EC or wait for next workflow run --- ### 7. Datatype Rules #### ✅ What Can Be Routed ```apl // Primitive types bytearray socketRequest = ...; udrRoute(socketRequest, "toTCP"); // ✅ // Custom UDRs Matcher match = udrCreate(Matcher); udrRoute(match, "toAggregation"); // ✅ Logger log = udrCreate(Logger); udrRoute(log, "saveReqLog"); // ✅ ``` #### ❌ What Cannot Be Routed ```apl // Web Service Cycle objects WSCycle_inquiryLoanPayment request = ...; udrRoute(request, "toTCP"); // ❌ Datatype mismatch! WSCycle_inquiryLoanPayment response = ...; udrRoute(response); // ❌ Datatype mismatch! // These are handled by Web Service framework automatically ``` --- ### 8. Decision Tree: Which Log Level? ``` Exception caught └─> Can system continue normally? ├─> YES → Is this expected/operational? │ ├─> YES → log.info() │ └─> NO → log.warn() └─> NO → Is this critical? ├─> YES → log.error() or log.fatal() └─> NO → log.warn() ``` **Examples:** - Port failed but fallback exists → `log.info()` - All ports failed but client gets response → `log.warn()` - Database connection lost → `log.error()` - Out of memory → `log.fatal()` --- ### 9. Common Mistakes to Avoid #### ❌ Mistake 1: Using Non-existent Functions ```apl // ❌ WRONG drLog("INFO", "message"); info("message"); warning("message"); // ✅ CORRECT log.info("message"); log.warn("message"); ``` #### ❌ Mistake 2: Routing Error Responses ```apl // ❌ WRONG catch(ExceptionDetails ex) { ErrorResponse err = createError(); udrRoute(err); // Datatype mismatch! } // ✅ CORRECT catch(ExceptionDetails ex) { log.info("Handled: " + ex.message); return; // Framework handles response } ``` #### ❌ Mistake 3: Not Catching Exceptions ```apl // ❌ WRONG - Exception propagates to ERROR log udrRoute(socketRequest, "toTCP"); // ✅ CORRECT - Catch and handle try { udrRoute(socketRequest, "toTCP"); } catch(ExceptionDetails ex) { log.info("Connection failed: " + ex.message); } ``` #### ❌ Mistake 4: Wrong Log Level ```apl // ❌ WRONG - Port failure with fallback logged as ERROR catch(ExceptionDetails ex) { log.error("Port failed"); // ทำให้ดูเหมือนมีปัญหาร้ายแรง } // ✅ CORRECT - Log as INFO since we have fallback catch(ExceptionDetails ex) { log.info("Port failed, trying next"); // Operational event } ``` --- ### 10. Testing Log Levels #### ตรวจสอบ Log Output **System Log:** ```bash # View APL logs tail -f $MZ_HOME/var/log//apl.log # View Platform logs tail -f $MZ_HOME/var/log/platform.log # Search for specific level grep "INFO" apl.log grep "ERROR" apl.log ``` **Output Format:** ``` 2024-11-26:10:30:45 UTC [INFO] [Default.workflow_1] Connection handled 2024-11-26:10:30:46 UTC [WARN] [Default.workflow_1] Retry attempt 2 ``` --- ### 11. Best Practices Summary #### ✅ DO - Use `log.info()`, `log.warn()`, `log.error()` from log4j - Catch exceptions at the appropriate level - Log operational issues as INFO - Handle errors gracefully with return - Use retry logic for transient failures - Test log levels in non-production first #### ❌ DON'T - Don't use non-existent functions (drLog, info, warning) - Don't route Web Service Cycle objects - Don't let exceptions propagate uncaught - Don't log expected conditions as ERROR - Don't use `consume()` function (doesn't exist) - Don't forget to log context (acqRefNo, channel, etc.) --- ### 12. Quick Reference ```apl // Logging log.info("message"); // INFO level log.warn("message"); // WARNING level log.error("message"); // ERROR level // Exception handling try { udrRoute(data, "route"); } catch(ExceptionDetails ex) { log.info("Handled: " + ex.message); return; } // Retry pattern for(int i=0; i

SECURE_ACCESS

MediationZone 9.3 - Logging และ Error Handling Guidelines

CONFIRM_DELETE