Randeep, we don’t like the out of the box email templates so we’ve build our
own app. In that Workflow I loop through a table field to replace variables of
a template with the ticket data. Overwriting the filter phases means I don’t
have access to the Request ID when I need to send the
Yes i have :-) All those event systems send events to the arserver.
On Oct 12, 2017 7:19 PM, "Dave Shellman" wrote:
> **
> Randeep,
>
> It seems that you have never worked in an environment where HPOV or other
> monitoring applications flood a server with events within a
Randeep,
It seems that you have never worked in an environment where HPOV or other
monitoring applications flood a server with events within a short period of
time that generate hundreds/thousands of records in a short period of time.
Dave
On Thu, Oct 12, 2017 at 10:11 PM Randeep Atwal
Rick, everything that generates NextID's must come through an ARSystem
server so I don't know what you mean when you say 'If you have multiple
outside entities creating large number of records at once'
All requests go through the AR Server.
I would theorize that you may have other factors in
Abhijeet, my results were repeated and conclusive. Here is the only
logical explanation for my findings that makes sense:
There is a time cost to the DB call for Entry IDs. The cost increases
incrementally the more that are requested at once. The thought is that 100
individual requests will
Rick, I do not think that is accurate.
Logically, if the block size is 100 then the server will access the DB once to
retrieve the next block id every 100 records. If it is 1, then the server goes
to the DB for every record.
Later cannot be faster.
Further, to answer the original question,
Actually I had a case where we needed Next ID > 1 due to DB performance. It
wasn’t on the primary form, it was on a child form (something like the Worklog
in ITSM where every action to a ticket is recorded). The database was being
blocked on the update of the Arschema record for that form.
Tim, I think he is looking not for the next one that the DB has, but the
one that's already been allocated to the AR server and would be the next
Entry ID for the next record actually created. In the current scenario,
anywhere between 1 and 99 Entry IDs would have already been fetched from
the DB
Thomas
You can get this data from the "AR System Metadata: arschema" form.
The fields of importance on this form:
Name = the Form Name
nextId = The next available ID for that form
Tim
-Original Message-
From: Action Request System discussion list(ARSList)
Thanks Rick! I actually don’t care whether they reserve the block or not as
long as they allow us to access the info what the next Id is. It could be a
special workflow action or at least an API call. I really don’t get why is that
so difficult to provide?
> On 12. Oct 2017, at 22:42, Rick
Here's the skinny on that. I got this from the engineer who built that
feature, btw.
The problem was that system performance was being constricted around the
action of getting the NextId for a record when multiple sources (say,
Netcool and HPOV) were throwing tons of requests at the (Incident)
i.e. there is no hack to find out the nextID before it actually gets submitted?
Apart from that, I really don’t understand why BMC makes such a fuss around the
nextID. Why can’t they just provide a special command GET-NEXTID?
Thomas
> On Oct 12, 2017, at 10:26 PM, LJ LongWing
There are no interfaces that I'm aware of to ask a specific server what the
next id it will hand out for a specific form is
On Thu, Oct 12, 2017 at 2:14 PM, Thomas Miskiewicz
wrote:
> Hello List,
>
> with NextID Block size being set to 100 —> is it possible the find out
>
Hello List,
with NextID Block size being set to 100 —> is it possible the find out using
the API which will be the next Request-ID that the server will assign to a
request? Or what other options do I have to find out?
--Thomas
But was that did that really on version 9.x?
Yes.
"Bächler Samuel (ewz)" >
skrev: (12 oktober 2017 08:17:29 CEST)
**
Hi Thomas
I once had the problem to change the format of server time. The solution then
was to set the ARDATE environment
But was that did that really on version 9.x?
"Bächler Samuel (ewz)" skrev: (12 oktober 2017
08:17:29 CEST)
>Hi Thomas
>
>I once had the problem to change the format of server time. The
>solution then was to set the ARDATE environment variable. We run ARS on
>Windows. I
Hi Thomas
I once had the problem to change the format of server time. The solution then
was to set the ARDATE environment variable. We run ARS on Windows. I think I
had to reboot the whole system.
Regards,
Sam
[cid:image001.png@01D34332.8B39C080]
17 matches
Mail list logo