0:04 this is a demo of BPR Arch plus okay so
0:07 we have two interactive uh clients one
0:09 on the left here and one on the right
0:12 and you'll notice at the bottom here
0:14 right here this one on the left is
0:17 connect to BP archives right it's a
0:20 different system so well sort of but for
0:21 now I'll just assume it's different and
0:25 then you see on here BP prod okay so
0:28 typically in a customer environment here
0:29 you would have your day-to-day
0:31 operations where you manage sorry your
0:33 production uh environment and on the
0:36 left here you will you know this is the
0:40 archives uh system so if you have a
0:42 archiver set up what would happen is the
0:44 archiver would work in the background
0:48 right it will move data from production
0:52 to archives typically we want to keep
0:55 production as Slim as possible with data
0:57 or you're going to notice bad things
1:00 happen like uh your processes your blue
1:02 prism processes those sessions they'll
1:05 take a lot longer to complete and in a
1:07 very bad case you'll see Deadlocks and
1:10 timeouts and that's not good right so
1:13 you want to keep your data very slim
1:16 specifically the workc item data there
1:21 is a lot of iOS going on with work items
1:24 is customer data being loaded customer
1:26 data data being updated and then delete
1:28 it so there's a lot of operations there
1:31 you don't want to keep too much data or
1:34 loading data will take a very long time
1:36 right the more data it has to the
1:38 interactive client has to Channel
1:41 Through the uh longer it will take
1:43 that's why you want to offload completed
1:46 uh work you items over here to the
1:49 archive system when you set this up you
1:52 say I want to Archive anything older
1:54 than 7 days that has completed I want
1:58 you I want you blue prism archiver to
2:01 move that data over here to the archive
2:03 system so over time the archive system
2:05 will have a lot of data and over here
2:07 your production data you know it'll
2:09 always be current data only and that's a
2:11 good thing you know you'll notice when
2:14 you do your database maintenance such as
2:16 uh rebuilding of indexes you'll notice
2:18 that it's a lot quicker when you have
2:21 less data so just overall generally
2:24 extremely good idea and healthy to have
2:26 an archive system that just constantly
2:28 move this data out so now I'm going to
2:30 show you how it works under underneath
2:32 the hood so this is the presentation
2:34 layer the uh interactive client data is
2:37 either going to be here or here but not
2:39 both it's going to be in production or
2:43 archives but not both so underneath the
2:46 hood I'm going to show you the archives
2:49 database so when you install archiver
2:51 it'll walk you through how to set up a
2:53 database you'll notice over here this is
2:55 the let's assume this is the production
2:58 database so if I go to the tables tab
2:59 this should start looking familiar to
3:03 you you it has all the um the tables
3:05 that you typically would see when you
3:07 log into a blueprism database well if I
3:10 flip back over to the archives database
3:14 right here and I go to tables well
3:16 there's not a whole lot of tables what
3:19 happened there's only seven tables here
3:21 it starts to look familiar these are
3:23 your uh logging and session tables and
3:25 these are your work Q item tables if I
3:28 expand this folder here called synonyms
3:30 I'm I'm going to just expand that
3:41 here you will notice I we called this
3:45 synonym uh BPA active directory domains
3:48 what a synonym is is a uh a link it's a
3:51 linking object underneath the hood you
3:53 can you can name it whatever you want
3:55 and you can point it to whatever you
3:58 want I say that Loosely right there's
3:59 obviously some things you can't
4:02 generally speaking you can and what
4:04 we're going to name this one is BPA
4:06 active directly domains he's actually
4:10 going to the database the production
4:12 database prod even though we're in
4:14 archives we're still in archives
4:18 database but he's pointing to this
4:21 object right here vpa active directory
4:24 domains this is a table this object is a
4:29 table and um in the production database
4:31 so he's link linking this is a link we
4:33 gave that link the same
4:37 name by doing it this way I'm going to
4:39 hit okay here but let me show you where
4:42 it's actually pointing so this is
4:44 production that synonym is actually
4:47 pointing to this guy so you can do that
4:49 you can remotely refer to other objects
4:51 of other databases so that's what the
4:55 synonym do does internally here's the
4:58 beauty of archivers okay
5:00 internally the archive
5:03 just sees it as an internal table we
5:07 kind of tricked it really is a table in
5:10 production and if you look at this uh
5:12 these uh if I go to design here if you
5:21 here they are both pointing to the same
5:24 table which is the production uh
5:27 database table even though uh when I log
5:30 into the BP archives here I logged into
5:33 archives and I log into BP prod even
5:35 though I set it up as two different
5:37 connections to two different databases
5:40 they're referencing the same table by
5:43 doing so we're able to utilize
5:45 everything that production goes on in
5:49 production so if you add in a new
5:51 process in production you'll see it in
5:53 archives for example because it's the
5:56 same table right that's the beauty of
5:58 the way archives is set up it's very
6:01 easy it leverages off of existing
6:04 production tables such as your users
6:06 table so if I change my password over
6:09 here when I go over here I log in with
6:10 the same
6:12 credentials right because it's hitting
6:16 the same tables so you could have two
6:20 ic's open in parallel a controller in a
6:22 a operations room if they don't find
6:25 their data in here if they go to their
6:28 control room and they go to their Q
6:29 management and they can't find the data
6:33 here well they could go over
6:35 here and they can go to Q management
6:37 they and when they do a search for their
6:40 item right over here they do a search
6:41 then it'll show up in here if it's not
6:44 in here it's in here that's the beauty
6:47 of BPR archives the only thing that's
6:50 different is the actual data that we're
6:53 moving nothing else so you don't have to
6:55 worry about sinking process on one side
6:57 and the other nothing like that it's uh
7:00 we trick the interactive client to
7:03 utilize production tables when it think
7:06 is its own by doing so we're able to
7:09 have a clean split of the the data
7:11 either it's in production here or
7:13 archives everything else is the same
7:15 when you're a controller you can just
7:17 have two of these open if you want if
7:19 you can't find here just open a
7:22 connection and find it here now that we
7:24 know that where the data comes from and
7:27 where it goes what's actually doing the
7:30 work so here in my archives databas B
7:32 you here are the tables if I expand this
7:36 programability like so you'll notice
7:38 these three stored procedures right here
7:41 that is the process that actually moving
7:44 the data from prod to archives it runs
7:46 in the background and typically you
7:48 would set up a database job to run at
7:51 certain intervals to move that data and
7:52 that's how the data gets populated into archives
Chrome Extension