%META:TOPICPARENT{name="TroubleshootingUDALoggingTracing"}% = Generating Server-side Multi-Tier Request Broker Trace Logs (All Platforms) = The following instructions enable you to create a time-stamped, Request Broker Trace: == Command Line Method (requires brief Broker shutdown) == # As a user with full read/write/execute permissions on the server-side Multi-Tier installation, get to a command-line prompt on the Multi-Tier Broker host. # Navigate to the /bin sub-directory of the Multi-Tier installation (e.g., /opt/openlink/bin/). # Execute the following commands: {{{ . ../openlink.sh ./oplshut -fy ./oplrqb -dv }}} Note: the Broker's output will take over this login session. Closing this session will terminate the Broker, but you may minimize the window, and use another Terminal/DOS session to execute additional command-line operations. # Recreate the error condition, by whatever means necessary. # Return to the above login session, and issue cmd-C to terminate the Broker. # Relaunch the Broker with your usual launch command, e.g., -- {{{ ./oplrqb }}} # The oplrqb.log in the /bin sub-directory of your Multi-Tier will contain a very detailed log of recent activity. == Web-based Admin Assistant (no Broker shutdown required) == # Open your Admin Assistant in a Web browser. # Drill down to Server Components Administration -> Request Broker Administration -> Edit Request Broker's Parameters (Wizard). # Enter your Admin Assistant username & password. (Both values default to "**{{{admin}}}**".) # Advance one screen and set Log Detail to DEBUG. # Scroll through the screens to end. # Click Save. # Click Reinitialize OpenLink Request Broker. # Recreate the error condition. # Retrieve the log and forward it to Product Support. == Related == * [[UnderstandRequestBrokerLogLevels|Understanding Request Broker Log Levels]] * [[GeneratingClientsideODBCTracesAllDrivers|Generating Client-side ODBC Traces and Driver Debug Logs]]