Converting applications from User tool to Mid Tier
Advantages of converting User tool to BMC Remedy Mid Tier
The following video provides information about advantages of converting BMC Remedy applications from user tool to mid tier.
To convert BMC Remedy applications from User tool to Mid Tier
- Replace all the macros with Run Process active link commands.
In BMC Remedy application, macros are used for operations such as running reports, click buttons, menus and so on. You should convert all such macros to active link run process commands. See Process commands.
Replace all unsupported keywords with active links. See Keywords.
Examples: $FIELDHELP$, $HARDWARE$, $TCPPORT$, $OS$, $GUIDETEXT$
|Keep minimum traffic between client and server|
High amount of traffic between a client and a server, especially in WAN environment, can lead to decrease performance in a browser. Here are some common checks that will help you reduce traffic between client and server:
|If possible, defer operations|
Note: There are some optimizations that occur automatically in the mid tier, like postponing all UI updates and refreshing table fields at the end of processing.
|Develop or move business logic to run from the server||Business logic is a workflow that drives or validates a business process, which should be run by filters. Client or server interactions performed at the server, reduce the number of active links on the form, which improves the performance on the client.|
You must perform the following workflows at the server side:
|Avoid fiddling with web forms|
Avoiding unnecessary fiddling on the web form makes the web form more responsive. You should avoid unnecessary screen fiddling, if it provides minimal value to the end user.
|Remove obsolete fields|
Do not remove the following fields:
|Tune form and field definitions|
Examples for keeping minimum traffic between client and sever
All examples use BMC Remedy ITSM as a service management system.
Use service call to consolidate round-trip communication with the server BMC Remedy ITSM gets data (system rules, application rules, people data, and support group data) from multiple source forms when a ticket is opened.
To get data, a window loaded active link needs to issue four round-trip calls to the server.
Data can be consolidated to one service call, which is managed and returned from the server side. When you use the service call, the window loaded active link makes one round trip service call to the server, and on the server side filters related to that service gets data from the different areas.
You must run the filter as an end user and not as an administrator.
Use web developer tools to examine all backchannel calls
Use hidden table columns to prepopulate other fields
The table fields in a form retrieve data from the server, based on the table qualification. If you need additional information based on the retrieved records, for other workflow, you should include that information in the table fields as hidden columns.
Use global variables
Store the data that is used for multiple forms in a global variable. This eliminates the need to retrieve the data multiple times in standard form variables on each form that requires the data.
Before using global variables
After using global variables
Reduce redundant workflow
Evaluate the workflows that are executed multiple times and reduce the redundant workflows. You can use active link logging and analyzer to find the redundant workflows.
Examples for deferring operation
Turn off the automatic table refreshes
Turning off automatic table refreshes prevents round-trip communication to server when you scroll through incident tickets.
Smart active links
Make active links smart enough to refresh only when a tab is selected.
Example of avoid screen fiddling