i coded a desktop app which uses a lot of otrs connectors (http://doc.otrs.org/3.3/en/html/generic ... connectors TicketSearch mainly) and it works as expected, the main problem is that after a few hours, our CPU is almost 99% because of the ApplicationPool which hosts OTRS.(If i delete the webservice i created, otrs will work smooth)
So im wondering how the login process works in OTRS Connectors
im guessing that every time i send for example
Code: Select all
<TicketSearch>
<UserLogin>xx</UserLogin>
<Password>xx</Password>
..
..
</TicketSearch>
will improve our OTRS performance if i use
Code: Select all
<SessionCreate>
<!--Optional:-->
<UserLogin>?</UserLogin>
<!--Optional:-->
<CustomerUserLogin>?</CustomerUserLogin>
<!--Optional:-->
<Password>?</Password>
</SessionCreate>
Code: Select all
<TicketSearch>
<SessionID>yyyyyyyyyyyyyyy</SessionID>
...
...
</TicketSearch>
i have my bets for using the Session thing..
Also, how long that SessionID will be valid for?
Im running OTRS 3.3.3 on
Windows Server 2012
Active State perl 5.16.3.1603
Sql Server 2012
Internet Information Services.
Thank you