UMRA Service Projects in LISD

basicgratisMechanics

Nov 5, 2013 (3 years and 9 months ago)

99 views

UMRA
Service
Projects

in LISD

STUDENT AUTOMATION


Student Automation


SIS > DB

Scheduled: Yes

Start Time: 12:01 AM

Frequency: Daily

Prerequisites: None

Sub
-
Processes Called:

Student Automation


SIS > DB 2

Purpose:

Loads all student data from Zangle and stores derived values into a staging database on the
spsid server

to
wait for

further processing by other automation scripts
.


Student Automation


DB

> AD

Scheduled: Yes

Start Time: 12:30 AM

Frequency: Daily

Prerequ
isites: Student Automation


SIS > DB

Sub
-
Processes Called:

Student Automation


DB > AD 2

Purpose:

Cycles through records previously put in the staging database and compares for changes with
the Active Directory User Objects. Unique key for compare is the

ident field in Zangle (studemo table)
and the Title field on the Active Directory Object. The value contained in these fields is the student’s ID
number.


If the student account already exists, the process will check to see if any changes have been made t
o the
account and update Active Directory accordingly. If the student account does not exist, it will be created
at that time. The student’s home folder and rights will also be created.


Student Automation


AD > DB

Scheduled: Yes

Start Time: 01:30 AM

Freq
uency: Daily

Prerequisites:

Student Automation


SIS > DB, Student Automation DB > AD

Sub
-
Processes Called:




Student Automation AD > DB 2



Student Automation AD > DB 3 (Compares student record in Active Directory against current
record from staging table.
This script disables AD accounts.)



Student Automation AD > DB 4

Purpose:

Compares user object data in Active Directory with user data in the SIS staging table. Updates
and disables Active Directory user objects based on data in staging table from SIS (Zang
le).


Student Automation


Check Secondary Campus

Scheduled: Yes

Start Time: 03:00 AM

Frequency: Daily

Prerequisites:

Sub
-
Processes Called:

Student Automation


Check Secondary Campus 2

Purpose:

Checks for students dual enrolled at DJCC.
Process then a
dds
the “multiple” campus (DJCC)

Student Group to indicated students.


new
Student Automation


SIS > DB

Scheduled: Yes

Start Time: N/A

Frequency: Every 15 minutes

Prerequisites:

None

Sub
-
Processes Called:

newStudent Automation


SIS > DB 2

Purpose:

Loads
new
student data from Zangle updated since the last run and stores derived values into
a staging database on the spsid server.


new
Student Automation


DB > AD

Scheduled: Yes

Start Time: N/A

Frequency: Every 15 minutes

Prerequisites:

newStudent Automation


SIS > DB

Sub
-
Processes Called:

newStudent Automation


DB > AD 2

Purpose:

Cycles through records previously put in the staging database and
adds student’s

Active
Directory User Objects. Unique key for compare is the ident field in
Zangle (studemo table) and the Title
field on the Active Directory Object. The value contained in these fields is the student’s ID number.


There are a set of automation files that duplicate Student Automation used for Summer School. The files
are prefixed

with SS
-
.

STAFF AUTOMATION


St
aff

Automation


IFAS > DB

Scheduled: Yes

Start Time: 12:15 AM

Frequency: Hourly

Prerequisites: None

Sub
-
Processes Called:




Staff Automation


IFAS > DB 2

o

Staff Automation


IFAS > Enter Into Zangle

o

Staff Automation


IFAS >

Enter Into AD



Staff Automation
-

Compare

Purpose:

Retrieves records updated since the last run from spsifasdb and stores them in a temporary
table for processing.
The process calls several sub
-
processes to determine action. If user does not exist
in Activ
e Directory and the user’s start date is less than 30 days away, an AD account, home folder and
email will be created.

The generated email address will be updated in Zangle and IFAS.


If the user does not exist in Zangle, a record will be created in
facdemo along with an initial track record
(facstat) based on the job code received from IFAS.

A record will also be created in the facuid table so
the selected user can login to Zangle immediately. If the user already exists in Zangle, an email will be
se
nt to the Zangle Administrator to review the account for an update.



At completion,
the
process will update
the field lastrunstamp in lisd_u
mra on spsifasdb.


St
aff

Automation


Disable Accounts

Scheduled: Yes

Start Time: 11:30 PM

Frequency: Daily

Prerequ
isites: None

Sub
-
Processes Called:

Staff Automation


Disable Accounts 2

Purpose:

Builds a record set of employees on their last day of work by checking the lastdaywrk field in
hr_empmstr table on IFAS. These records are stored in a temporary table and then processed
individually by sub
-
process. Sub
-
process finds the account in Active
Directory and disables the account.
An email is generated for each disabled user and emailed to the helpdesk.


/* Edit 2/18/2011 */

This process has been modified to also reflect if the owner of the disabled account has district
equipment checked out. Equi
pment details are included in the email notification and Ms. Rogers has
been included in the distribution list.


St
aff

Automation


Add New Staff

Scheduled: Yes

Start Time: 06:00 AM

Frequency: Daily

Prerequisites: None

Sub
-
Processes Called:



Staff Automatio
n


IFAS > DB 2

o

Staff Automation


IFAS > Enter Into Zangle

o

Staff Automation


IFAS > Enter Into AD



Staff Automation
-

Compare

Purpose:

Runs normal Staff Automation processes but with a different set of records from IFAS. This
service project returns users from the umraempmstr_all view that have a hr_emppay record with a
calc_beg date that equals the current date. All other sub
-
processes
are the same as called in Staff
Automation


IFAS > DB.


St
aff

Automation


IFAS > DB


Specific EP

Scheduled: No

Start Time: On Command Only

Frequency:
On Command Only

Prerequisites: None

Sub
-
Processes Called:



Staff Automation


IFAS > DB 2

o

Staff Automati
on


IFAS > Enter Into Zangle

o

Staff Automation


IFAS > Enter Into AD



Staff Automation
-

Compare

Purpose:

Run a particular user or small group of users through the entire automation process. The list of
user ids (EP#) to process must be added into the SQL
query inside the top level project (Staff
Automation


IFAS > DB


Specific EP.


Steps to run this project:

1.

Login to the spsid box in the LISD domain and open UMRA Console.

2.

Click File
-
> Open Project from the top menu bar and select ‘Staff Automation


IF
AS > DB


Specific EP from the UMRA Service Projects column on the left.

3.

On the Script tab in the top frame, double
-
click the 4
th

line down that states “Get All IFAS Recs”.

4.

On the resulting box, click the Configure button.

5.

Click on the Query tab.

6.

Modify the IN clause of the query by adding in the EP#’s that require processing.

7.

Query should now read “SELECT * FROM UMRAempmstr_all WHERE ID IN
(‘EP0000000’,’EP1111111’)

8.

Click OK twice.

9.

Click the Save button.

10.

Click the Scheduler icon (7
th

from left of

screen)

11.

Highlight the line “Execute project ‘Staff Automation


IFAS > DB


Specific EP’

12.

Click the Play button or click Actions
-
> Run Now from the top menu bar.



SUB AUTOMATION

Sub Auto


AD > DB

Scheduled: Yes

Start Time: 5am

Frequency:
Every 900 Secon
ds between 5am and 2:15pm

Prerequisites: None

Sub
-
Processes Sub Auto


AD > DB2

Purpose: Compile list of accepted substitute assignments from smartFind, the district’s absence and
substitute system. The query only pulls daily assignments.


(SELECT Concat("
000000",accesscd) as accesscd, accesscd as epnum, locationcode,a.accepteddttm,
a.jobstartdttm, c.lastname

FROM jobdetail a

INNER JOIN job b ON a.jobid = b.jobid

INNER JOIN person c ON a.assignedsubid = c.personid

INNER JOIN location d ON a.locationid =
d.locationid

WHERE a.jobstatus <> 6

AND a.jobstartdttm between date_add(current_date, interval '0:0' hour_second)

and date_add(current_date, interval '23:59:0' hour_second);)


Sub Auto


AD > DB2

Scheduled: No

Start Time: On Command Only

via Sub Auto


AD > DB

Frequency: On Command Only

via Sub Auto


AD > DB

Prerequisites:
Sub Auto


AD > DB

Sub
-
Processes Called
: None

Purpose: Processes recordset retrieved in Sub Auto


AD > DB. For each substitute record, this process

1.

Checks to verify
sub has signed district AUP

a.

(SELECT personID, certCD, modified FROM sfx.personcert WHERE certCd=11 AND
personId=(SELECT personID FROM person where accessCd='%epnum%'))

2.

If AUP signed, copies sub’s home directory to campus share server

3.

Assigns campus teache
r permissions to account

4.

Moves user’s AD account from Administration


Subs OU to campus Teacher OU

5.

Sends an email to campus contact (facilitator)


Sub Auto


Reset Accounts

Scheduled: Yes

Start Time:
7pm

Frequency: Daily

Prerequisites: None

Sub
-
Processes
Called
: Sub Auto


Reset Accounts 2

Purpose:

Find all substitute user accounts in AD to move back to the Administration


Subs OU at the
end of the work day.

LDAP binding:
LDAP://%dc%/OU=Schools,dc=lisd,dc=local

LDAP Filter:
(&
(objectCategory=user)(orgCode=900))


Sub Auto


Reset Accounts 2

Scheduled: No

Start Time: On Command Only

Frequency: On Command Only

Prerequisites: Sub Auto


Reset Accounts

Sub
-
Processes Called
: None

Purpose:

This process strips group memberships from th
e user account, moves home folder back to
admin server and moves the user account back to Admin
i
stration


Subs OU.


COMPUTER MANAGEMENT

computerManagement

Scheduled: Yes

Start Time: Now

Frequency: Every 60 Seconds

Prerequisites: None

Sub
-
Processes Called:

computerManagement2

Purpose: Generate list of newly registered district computers from Domain Computers into the proper
OU in Active Directory.

LDAP Binding:
LDAP://%dc%/OU=Domain Computers,DC=lisd,DC=local

LDAP Filter:
(&
(objectCategory=computer)(name=*
-
*))


computerManagement
2

Scheduled: No

Start Time: On Command Only

Frequency: On Command Only

Prerequisites: computerManagement

Sub
-
Processes Called: None

Purpose: Move newly registered district computers from Domain Comput
ers into the proper OU in
Active Directory.