Creating the debug log from the local beas Web server
- If your issue is reproducible on the local beas web server
-
- Go to tools - web server - web app 2.1 . Make sure that the port selected at the top is available. If not, click on the check-box Start Server so to stop it. Then change the port number (the field becomes editable once the server is stopped) to an available one. Check again the box Start Server. Click then the link "Web Application Version 2.1" to open the url and access the local beas web server.
- Don't close web server window
- Execute all the steps on the web app that is causing the error. Before running the last step that generates the error go to SAP and start the beas debugger by hitting the keys combination ctrl + shift +i or by clicking on the main menu item View and then on System information
- On the opened debugger window, set level 3. Do not close the window.
- Go back to your browser and run the last step on the web app. You will notice in SAP the beas debugger running.
- Upload the debug and paste the generated link on the support ticket you have opened with Boyum (the link will be automatically in the clipboard)
- Go to tools - web server - web app 2.1 . Make sure that the port selected at the top is available. If not, click on the check-box Start Server so to stop it. Then change the port number (the field becomes editable once the server is stopped) to an available one. Check again the box Start Server. Click then the link "Web Application Version 2.1" to open the url and access the local beas web server.
Creating the debug log from the beas server service screen
- If your issue cannot be reproduced with the first method described in this article, the open the beas manage server screen
-
- Setup the protocol directory. Make sure to set a path with full read/write access rights (C:\beas_protocol for example)
- Check the box to enable the debug to file. Restart the beas service
- Open the beas server by clicking on the golden arrow next to the "Web Application V2.1" label. This will open the beas server url.
- Execute the Web App transaction that is generating an error.
- Get the debug log file (beasDebug.log) generated by the beas server in the protocol directory set at step 1 one of this guide. Attach the file to the support ticket you have opened with Boyum
- Setup the protocol directory. Make sure to set a path with full read/write access rights (C:\beas_protocol for example)
Comments
0 comments
Please sign in to leave a comment.