Jolt/Tuxedo Pool Member Question

This is the only thread I can find about load balancing JOLT for Oracle Peoplesoft.  So I'm going to post what I had to do to get JOLT through the f5, in hopes it will save a little frustration for someone else. 

The JOLT protocol uses multiple ports, kinda like passive FTP.  The initial connection is on an instance configured port, usually 9200/TCP.  Then the server specifies a temporary port for the rest of the conversation, and the client makes a new TCP connecton to that port, often something like 9201, 9202, 9203... 

To get it through the f5 LTM, I had to put it on it's own destination IP, and use the "any" port. 

ltm pool sc2fi-dev_jolt {
    description "sc2fiX-dev jolt"
    members {
        10.1.122.144:any {
            address 10.1.122.144
            priority-group 10
        }
        10.1.122.145:any {
            address 10.1.122.145
            priority-group 1
        }
    }
    min-active-members 1
    min-up-members 1
}

ltm virtual udfin-dev_jolt {
    description "udfin jolt"
    destination 10.2.56.11:any
    ip-protocol tcp
    mask 255.255.255.255
    pool sc2fi-dev_jolt
    profiles {
        tcp-lan-optimized { }
    }
    rules {
        log
    }
    source 0.0.0.0/0
    source-address-translation {
        pool dr-sc-app
        type snat
    }
    translate-address enabled
    translate-port disabled
    vlans {
        subnet56
    }
    vlans-enabled
    vs-index 46
}

net packet-filter udfin-dev-jolt {
    action accept
    order 320
    rule "dst host 10.2.56.11 and proto TCP and dst portrange 9000-9500 and (  src net 10.2.4.128/27 or src net 10.1.11.0/24 )"
    vlan subnet56
}