Baanboard.com

Baanboard.com (http://www.baanboard.com/baanboard/index.php)
-   Performance & Tuning (http://www.baanboard.com/baanboard/forumdisplay.php?f=61)
-   -   Baan Performance Tracing Questions (http://www.baanboard.com/baanboard/showthread.php?t=24566)

thomas_b 14th July 2005 17:33

Baan Performance Tracing Questions
 
Greetings,

Does anyone out there know of a way to track specific UI events, such as opening a session, drilling down on a menu, tabbing through fields, etc. We have varying network connection bandwidths in our facilities, and we are trying to determine a correlation between the network bandwidth and Baan performance. More specifically, we are trying to provide a recommendation to our lower bandwidth sites in terms of the network bandwidth or hardware required for adequate Baan performance. We have tuned our db, server hardware, and OS, as performance from our higher bandwidth sites is very good. Any ideas or recommendations would be appreciated.

Baan IVc4, SP 17, AIX 5.3, Oracle 9i

Thank you in advance.

NPRao 14th July 2005 20:13

Thomas, refer to the thread -

Debug Bshell

NPRao 24th July 2005 22:19

I am not sure if you have the option of Page Mode in your BaaN Version.

Here is more info -
Quote:

5-1 Tools Technical Manual
This chapter describes the User Interface (UI) page mode in BaanERP. The UI page mode improves the response times on networks where information
processing can be delayed, for example, in a wide area network (WAN). In normal mode, the 4GL Engine validates the entered data per field. In the UI
page mode, the 4GL Engine validates data per page, and not per field. The synchronous interaction between the UI driver and the bshell is therefore
significantly reduced. The UI page mode is designed for experienced BaanERP users, because the interaction between BaanERP and the user is not as extensive as in the normal mode.
In the normal mode, an error message is displayed immediately when data entered in the active field is not correct. In the UI page mode, an error-logging
window appears, which shows all errors that occurred during the validation of all the data entered on the page. In the UI page mode, the UI driver groups together a number of UI objects that
form a logical unit. A UI object is for example, a field, a button, or a check box. The logical unit is known as a page. A page can be an Overview window or a tab
in a details session with more than one tab. If the UI page mode is selected, each UI object automatically belongs to a page.
If the UI object is positioned on a tab, the object is considered part of the page associated with the related tab. In any other case, the UI object is part of the page
associated with the Overview window.
5 User Interface (UI) page mode Tools Technical Manual 5-2
The following functions are implemented in the UI page mode to improve
network performance:
The UI handles the movement from an active element to another element without any communication with the bshell. An active element is a portion of
the screen that is currently operational or subject to command operations. Usually the cursor or a highlighted section shows the active element on the
display screen. Active elements are, for example, fields, command buttons, check boxes, or list boxes. The UI client handles the behavior of the default button for the command buttons on a page.
Events that result from status changes of UI objects are delayed until a complete page is filled, or another synchronization event occurs. The delayed
events are sent into a minimum number of network frames.
Tab processing
When the UI page mode is selected, the UI driver processes Tab key movements in the details window. The Tab key sequence is identical to the creation order of
the UI objects on a page. Other navigation keys, such as Page Up, Page Down, Home and End are reported to the bshell with the appropriate keystroke.
Default Button handling When the UI page mode is selected, the UI driver handles the default command button. This is the command button that is highlighted when the dialog box is
initially displayed. It can also be the command button with the bold border, indicating that it is automatically selected if you press Enter.
Event processing If the UI page mode is selected, events are treated differently by the UI driver than when normal mode is selected. There are four different event categories:
Suppressed events.
Delayed events.
Synchronization events.
Bypass events.

User Interface (UI) page mode
Tools Technical Manual

5-3
Suppressed events
If the UI page mode is selected, a UI object does not send suppressed events to the bshell. Instead, suppressed events are handled locally by the UI driver on the
client. An example of a suppressed event is to move from an active element to another active element.
Delayed events
Status changes of UI objects can be delayed. As soon as a synchronization event occurs, for example, by clicking the Validate button, the changed UI objects are
requested to synchronize their status with the 4GL engine. The delayed events are sent in the same order as the Tab key sequence of the UI objects on the page.
This is not necessarily the order in which the user enters data. If possible, the delayed events are sent into one network frame to reduce response times.
Synchronization events
The synchronization events make sure that the statuses of the changed UI objects are sent to the bshell for validation.
Synchronization events are:
Selecting a menu item.
Clicking a button.
Moving to another tab.
Moving from a synchronizing field to another field.
Starting a browse session.
Pressing a key that is not handled by the UI client.
Resizing a window.
Using the scroll bar.
Bypass events
The following bypass events are sent immediately to the bshell without first being synchronized with the delayed events:
Using the online Help.
Closing a Windows application that was started through the application Start feature of the UI client.
Using OLE objects.

User Interface (UI) page mode
Tools Technical Manual

5-4
How to select the UI page mode
The UI page mode is selected per user to make sure that inexperienced BaanERP users cannot use it. You must define the UI page mode in the user profile of the
user. The user profile is defined in the User Management module in BaanERP Tools. Follow these steps to select the UI page mode for a user:
1 To select a user data template, or to create a new user data template, start the User Data Template (ttams1110m000) session in the Authorization
Management System (AMS) module. Be sure to choose the Use Page Mode check box under Options on the System Data tab.
2 Start the User Data (ttaad2500m000) session in the User Management module. Double-click the user for which you want to select the UI page mode
to start the details session.
3 Under Templates, enter the new User Data template, which is page-mode enabled. Click Save to return to the overview session.
4 On the Specific menu choose Convert Changes to Run Time DD to rebuild the user profile in the run time database.
5 Restart BaanERP to activate the changed user profile.
Check that the following are true to verify that the UI page mode has been successfully selected:
All the fields and options in the overview windows and detail windows are available.
All commands on the menus of the menu bar in an overview window are available.
On the Window menu the Validate command is available in an overview
window.
The Validate button is displayed on a details window.

User Interface (UI) page mode
Tools Technical Manual
5-5
How to mark UI objects as synchronizing fields

You can mark UI objects on an overview window or details window as synchronizing fields. This means that when you move from one active field or
button to another field or button, all delayed events are sent to the bshell for validation. You can mark the following fields and buttons as synchronizing fields:
Edit fields.
Check boxes.
Option buttons.
List boxes.
Combo boxes.
You must use the Form Editor in BaanERP Tools to mark a form field as a synchronizing field. Complete the following steps to start the Form Editor:
1 On the BaanERP Tools menu, click Application Development, and then click Forms to start the Forms (ttadv3500m000) session.
2 Select a form. On the Specific menu choose Check Out to release the form for modification.
3 On the Specific menu, choose Edit/View Form to start the Form Editor.
Depending on the form type, the appropriate Form Editor starts. The following form editors are available in BaanERP:
The Static Form Editor, which shows the form in an ASCII format. The Dynamic Form Editor, which is a graphical editor in a Windows format.
You can carry out one of the following procedures to mark a field as a synchronizing field:
Static Forms
1 In the ASCII editor, click the field to start the Form Fields (ttadv3501s000)
session.
2 On the General tab, select the Synchronized check box.
3 Click Close to return to the Form Editor.
4 On the Specific menu, choose Check In to finish the procedure.

User Interface (UI) page mode
Tools Technical Manual
5-6
Dynamic Forms

1 In the graphical Dynamic Form Editor, click the field to start the Field Properties session.
2 On the Miscellaneous tab, select the Synchronized check box.
3 Click OK to return to the graphical Dynamic Form Editor.
4 On the Specific menu, choose Check In to finish the procedure.

norwim 25th July 2005 02:03

Hi there,

just a provoking thought ....
as you are using c4 and running on unix .... did you consider to have the remote (lower bandwidth) users use ba6.1 instead of GUI? Depending on what they actually are doing, many users are even happier with ba6.1, as the absence of of mouse often speeds up their work.
just a thought

Norbert

dave_23 25th July 2005 02:57

Webtop
 
I think Webtop is baan's answer to that problem, you could put local
webtop servers in the remote locations and cache the forms there.
I think that would significantly decrease the amount of bandwith going over your WAN.

Dave

Viplov 25th July 2005 12:22

Hi

Citrix can be another choice for low bandwidth locations.


All times are GMT +2. The time now is 14:55.


vB.Sponsors
©2001-2017 - Baanboard.com - Baanforums.com