After reading Stephen's posting I remembered another gotcha if you use an Escalation to do any LDAP work. In a past life we had an Escalation that would run in the early morning to synch AD info via a Vendor form. Since the Escalations are single threaded no other escalations would fire until this job finished many many hours later. For a few days we could not figure out why critical escalations were not firing until we found this "special" process.
Jason
On 9/14/06, Heider, Stephen <[EMAIL PROTECTED]> wrote:
Chris,
I currently pull data from multiple sources, including LDAP and three HR
systems. I run a process periodically throughout the day (to pick up
any changes, new hires, terms) that combines data from these sources
into one SQL table on the Remedy server. The table is connected to a
Remedy View form. This combines the data and makes it available to
Remedy workflow as needed. Another process updates the SHR:People form
(HD 5.5) and User form.
By keeping a consolidated copy of the employee/user data locally it is
very quick to retrieve or report on. The frequency of your updates will
depend partly on the level of strain it places on your Remedy server
and/or WAN.
If everyone's internet/WAN speed significantly slows down or if your
Remedy server's CPU is pegged when you run your process then you will
likely want to run it overnight or during times where it does not
heavily impact your network. However, if the effect on Remedy and the
WAN is very small then run it as often as your company needs.
Here is another option if running your consolidation process is too
resource intensive and you need to run it frequently: Run most of the
process on another server and use replication (SQL Server). I use that
here for our asset management system (TS Census/Zen Asset Management)
located 1000 miles away from the Remedy server. I run a process every 5
minutes [on the other server] that detects updated computer scan data
and consolidates it into a few tables. SQL Replication automatically
keeps these tables in synch on the Remedy server. Very little data gets
passed across the WAN and there is no processing at all on the Remedy
side (for updating something like SHR:People then there would be at
least some processing needed on the Remedy server).
These and the other suggestions posted should hopefully get you going.
Stephen
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Pierson, Shawn
Sent: Thursday, September 14, 2006 2:37 PM
To: arslist@ARSLIST.ORG
Subject: Re: people lookup in realtime from LDAP ?
I thought about doing this in the past for a custom application. I
wanted to be able to pull people information from Active Directory, then
create another table to store users that will not be in Active
Directory. Unfortunately, since you can not make a Join Form against a
Vendor Form, there really is no other good way to use LDAP than storing
the data on the database.
Additionally, ARDBC is capable of caching, so you can set up Remedy to
not be a huge drain on the AD server's resources or the network for
common requests.
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of L. J. Head
Sent: Thursday, September 14, 2006 11:13 AM
To: arslist@ARSLIST.ORG
Subject: Re: people lookup in realtime from LDAP ?
Yes that is possible but you have several things to worry about when you
do that.
1. What sort of connection exists between your remedy and AD server for
querying. 2. How many queries are you performing daily across that
connection and if you want to cause that type of network traffic 3. As
someone else already mentioned, is there any workflow associated with
the People records that would be affected by not using the people form
4. Are there any 'customers' of your solution that are not members of
your AD infrastructure? If so you will need some type of toggle to be
able to pull from the local resource instead of the network 5. Are your
LDAP servers capable of the type of load that you will be imposing on
them by doing almost constant queries from them
All that having been said...I have a custom system setup using only the
AD server for its customer data and it works fine.
L. J. Head
Software Engineer
Remedy Approved Consultant
The information in this e-mail, and any files transmitted with it, is
intended for the exclusive use of the recipient(s) to which it is
addressed and may contain confidential, proprietary or privileged
information. If you are not an intended recipient, you have received
this transmission in error and any use, review, dissemination,
distribution, printing or copying of this information is strictly
prohibited. If you have received this e-mail in error, please notify
the sender immediately of the erroneous transmission by reply e-mail,
immediately delete this e-mail and all electronic copies of it from your
system and destroy any hard copies of it that you may have made. Thank
you.
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
__20060125_______________________This posting was submitted with HTML in it___
