|
Integrating with Autotask
Autotask provides a complete IT business management solution that combines Service Desk, CRM, Projects, Time & Expense, Billing and more.
From the TT system drop-down, select AUTO TASK as the TT system with which the eG manager should integrate. Then, to enable the eG manager to connect to the Autotask installation in your environment, specify the following:
Then, specify the following:
Account discover period: Enter how frequently the eG manager needs to auto-discover the user accounts configured in Autotask. By default, this is set to 3600000 millisecs. If an auto-discovered user account is mapped to one/more zones configured in eG, then Autotask will automatically assign the trouble related to the servers in those zones, to the corresponding user account. To map an auto-discovered user account with one/more zones, do the following:
Open the eg_services.ini file in the <EG_INSTALL_DIR>\manager\config directory, using an editor. Typically, when user accounts are auto-discovered for the first time from Autotask, the eG manager automatically creates a section named [AUTOTASK_ACCOUNT_MAPPING] in the eg_services.ini file. All auto-discovered user accounts are inserted as entries in this section, in the following format:
[AUTOTASK_ACCOUNT_MAPPING]
<AccountName1>$@$<AccountNumber1>=
<AccountName2>$@$<AccountNumber2>=
. . .
. . .
. . .
<AccountNameN>$@$<AccountNumberN>=
To map a user account to one/more zones, just configure a comma-separated list of zones against the corresponding <AccountName1>$@$<AccountNumber1> entry in the [AUTOTASK_ACCOUNT_MAPPING] section, as shown below
[AUTOTASK_ACCOUNT_MAPPING]
<AccountName1>$@$<AccountNumber1>=east_coast_zone,zone_singapore,zone_london
Finally, save the eg_services.ini file.
Queue ID: Specify the ID of the queue to which eG alarms are to be assigned. By default, 8 is the queue to which all eG alarms are assigned.
Default account: Indicate to which user account eG alarms are to be assigned by default. If a server on which eG has raised an alarm does not belong to any zone or any zone that is mapped to a user account, then such an alarm will be automatically assigned to the default user account. Likewise, if auto-discovered user accounts are not mapped to any zones configured in eG, then all eG alarms will be automatically assigned to the default user account.
Ticket type: Indicate the type of ticket that is to be raised in Autotask for every eG alarm that the eG manager sends to it. By default, this parameter is set to 3, which indicates that for eG alarms tickets of type, Problem, are generated by default in Autotask. You can change the value of this parameter to 1 to indicate Service request or 2 to indicate Incident. Work type: The work type to be assigned to the trouble tickets generated for the eG alarms. By default, this is 29683401. Critical due period: The time (in millisecs) by which tickets of a Critical priority will be resolved. Major due period: The time (in millisecs) by which tickets of a Major priority will be resolved. Minor due period: The time (in millisecs) by which tickets of a Minor priority will be resolved.
Next, specify the format in which the title of the trouble ticket is to be displayed in the Autotask console. The default format is as follows:
Priority :$prior Component : $cname Component Type : $ctype Layer : $layer Problem Description : $pdesc
The text preceding the ‘:’ (colon) in the format above indicates what information follows. The ‘dollared’ ($) text that follows the ‘:’ (colon) is a variable, the value of which varies at run time, depending upon the eG alarms. For example, in the default format above, Priority is a label that indicates that the information that follows the ‘:’ is the priority of the alarm. The variable $priorthat succeeds the ‘:’ represents the alarm priority, and changes according to the priority of the actual alarm that is sent by the eG manager to Autotask. While you can change the labels, you are advised against changing any of the variable names.
The other variables that are part of the default format are discussed in the table below:
| $cname |
Will display the name of the problem component |
| $ctype |
Will display the component type to which the problem component belongs |
| $layer |
Will display the layer affected by the problem |
| $pdesc |
Will display a brief problem description |
So, if a Critical alarm raised by the eG manager for a high CPU usage problem detected in the Operating System layer of the Windows server, 192.168.10.15, is routed to Autotask, the web services API of Autotask will convert the alarm into a trouble ticket titled (by default) as follows:
Priority:Critical Component:192.168.10.15 Component Type:Windows Layer:Operating System Problem Description:High CPU usage
The implementation of eG integration with ServiceDesk exists in a Java class file named AutoTaskIntegrator.java. Additionally, the API files and library files that support this class file are jarred in AutoTask.jar file. In eG, this jar file is referred to as the TT integration archive file. By default, the implementation class file and the jar file are bundled with the eG manager and are available in the <EG_INSTALL_DIR>\manager\lib directory on the eG manager host. However, if later, changes are made to these files, you will have to re-upload them to the eG manager. In such a case, set the Do you want to upload the supporting archives? flag to Yes, and click the Upload button alongside. This will invoke the UPLOAD FILES window.
In the UPLOAD FILES window, specify the full path to the Wrapper class file - i.e., the AutoTaskIntegrator.java file - and the TT Integration Archive File - i.e., the AutoTask.jar file - to be uploaded. Use the Browse button for the path specification. Finally, click the Upload button.
Finally, click the Update button to save the changes.
|