PilotFish Best Practices

• Understanding How PilotFish Software Works

• Plan Your Interfaces Before
  Implementing

• Understand Types of Transactions You Will Be Processing

• Pay Attention to Naming Convention

• Use Consistent Route Structure

• Use & Understand Transaction Data (Trans Data)

• Use Transaction Attribute (Trans Attrs)

• Externalize Environment Properties Early On

• Use Data Validation

• Use Transformation Modules

• Use Error Routes

• Use Route Descriptions

• Re-use XSLT Transformations When Possible

• You Can Rename Routes/Listeners/Interfaces – But Be Very
  Careful

• Use System Info Fields

• Use Data Mapper’s Testing Tab

• Use Architectural References

• Version And Backup Your Changes

• Handle Transport Results In Another Route

• Use Log Tailing To Monitor Logs While Testing

• Understand Synchronous Responses

• Understand Logging Levels And Use Them While Testing Or
  Troubleshooting

• Understand How External Jars Are Loaded

• Understand Differences Between FTP, FTPS, And SFTP &
  Nuances Of Each

• Use Debug Tracing (Only Temporarily)

• Use Drag & Drop In the Data Mapper

• Data Mapper Tips

• Use XSLT and Practice It

• Use Interface Packages

• Use the eiPlatform Emulator Within eiConsole

• Use the Debug mode

• Use the Data Mapper’s Format Builders

• Use Routing Rules

• Use Forking but not Joining

• Use Process Orchestration for Forking With Joining – But
  Use Caution

• Use “Null Listener” For Triggers Based On Interval

• Use Auth for Http Listener (Web Service)

• Use OGNL, Learn It & Practice It

• Use Thread Pools

• Use Message Queues

• Use SQLXML Logging

• Restrict Meta To Increase Performance With Database SQL
  Transport

• Consider Local-name() Notation For XPath

• Use Security Mechanisms

• Use Java VisualVM For Performance Tuning

• Use Global Transaction Monitors For Larger Interfaces

• Use OGNL To Access SQLXML Results Inline In XSLT

• Use Well-known Standards When Possible

• Use the Disable Route Feature

• Use the eiDashboard

• Use Java VM Settings for eiPlatform to Increase Heap Size

• Use Reverse Proxy to Expose PilotFish Web Services to the
  Public Internet

• Use Built-in Regression Testing Tools When Upgrading the
  eiPlatform

• Use Test Suite Software to Keep Known Working and Not
  Working Messages for Quick Smoke Testing & Load Testing

• Understand How The Logs Work

• Don’t Have to Restart eiPlatform When Only Making XSLT
  Transformation Changes

• Configuring PilotFish Interfaces – Do’s & Don’ts

• Cleaning Up Working Directory Temporary Files

• Have an Upgrade Plan!