1
00:00:00,380 --> 00:00:00,980
High fence.

2
00:00:01,000 --> 00:00:03,470
So very complicated decisions such factors.

3
00:00:03,500 --> 00:00:06,770
And here will be discussing body odor that you are right.

4
00:00:07,080 --> 00:00:14,190
The Open Data protocol abbreviated as auditor and it was the creation of risk based data services which

5
00:00:14,310 --> 00:00:19,860
allow the sources and the sources are identified using informed source identifiers.

6
00:00:19,860 --> 00:00:27,610
You add eyes and are defined in our data model to be published and edited by the lines using simple

7
00:00:27,750 --> 00:00:31,340
I should be messages at the crux.

8
00:00:31,340 --> 00:00:38,810
We need to operate on resources exposed wire or data services and you are interested in text on how

9
00:00:38,810 --> 00:00:42,240
these manipulations over resources can happen.

10
00:00:42,770 --> 00:00:49,580
So it's a combination of resources or protocol is a combination of resources and which is enabled to

11
00:00:49,580 --> 00:00:57,760
rest with the services and data research published in the model which basically lets us know overall

12
00:00:57,790 --> 00:01:02,240
operations are based on it can be applied on those particular resources.

13
00:01:02,760 --> 00:01:06,230
So in all but we need to operate upon.

14
00:01:06,230 --> 00:01:11,800
Are the resources and what operations we can do over the resources what on many collisions can happen

15
00:01:11,800 --> 00:01:14,590
over the resources.

16
00:01:14,610 --> 00:01:15,100
You are right.

17
00:01:15,100 --> 00:01:17,580
Is this index of doing that.

18
00:01:18,180 --> 00:01:21,100
So that is or discard less uniform resource identifier.

19
00:01:21,120 --> 00:01:27,630
And that is the audit that you are right into the syntax of operating on the resources that these other

20
00:01:28,690 --> 00:01:30,530
so you are incompetent.

21
00:01:30,790 --> 00:01:34,240
You are used by an auditor service has a pretty significant parts.

22
00:01:34,390 --> 00:01:36,000
One is a service group you are right.

23
00:01:36,370 --> 00:01:41,350
So this really is a thing from which everything begins services to do right we have.

24
00:01:41,530 --> 00:01:46,880
Then we have the resource part and then we are declared a string of options.

25
00:01:46,930 --> 00:01:47,190
All right.

26
00:01:47,770 --> 00:01:52,930
So we have got these the initial part from Verdi which is the fruit of the service.

27
00:01:52,930 --> 00:01:54,110
The service will do alright.

28
00:01:54,370 --> 00:01:56,060
And then comes the resource part.

29
00:01:56,080 --> 00:02:02,410
Look how we can navigate within depart within the resources and then there are certain additional query

30
00:02:02,410 --> 00:02:04,780
string options that are available to us.

31
00:02:04,780 --> 00:02:10,030
So we'll be looking into each of these henceforth before we go any further.

32
00:02:10,060 --> 00:02:14,240
So first of all we need to understand the significance of this of this fruit fly.

33
00:02:14,440 --> 00:02:16,600
As far as success factors is concerned.

34
00:02:17,110 --> 00:02:21,700
So let's take that detour for a brief moment.

35
00:02:21,700 --> 00:02:27,220
So here is there is a picture depicting the success factors application you order data entry level and

36
00:02:27,250 --> 00:02:28,600
audit that you are right.

37
00:02:29,200 --> 00:02:36,490
So here also we will be able to distinguish or make distinction between what is difference what is a

38
00:02:36,490 --> 00:02:39,080
difference between all the cheap parts here.

39
00:02:39,200 --> 00:02:45,040
What is the success factors that piggish anywhere in right where this data center whether it is or the

40
00:02:45,040 --> 00:02:45,760
diuretic.

41
00:02:46,030 --> 00:02:51,550
So when we hear these terms we should be able to distinctly identify what each of these does mean.

42
00:02:51,630 --> 00:02:58,660
So when we talk about the application the substance that is application you are or normally in day to

43
00:02:58,660 --> 00:03:02,290
day language you just call this company you are a company idea you are.

44
00:03:02,740 --> 00:03:04,350
So what does that mean.

45
00:03:04,360 --> 00:03:11,680
It means you are in on to which the user experience or the user interface is exposed.

46
00:03:11,680 --> 00:03:14,920
That is the end user the application users.

47
00:03:14,920 --> 00:03:19,720
So these aren't the end users here which are depicted with the people here.

48
00:03:20,050 --> 00:03:26,260
So these are the only users who interact with the application via user interface.

49
00:03:26,290 --> 00:03:31,750
So this is a user interface of the company of these exercises application and they interact.

50
00:03:31,750 --> 00:03:39,320
The end users interact with the application which exposes all the features and in their various charts

51
00:03:39,340 --> 00:03:45,520
and all that so that that application they interact with over the application you are stuck to that

52
00:03:45,520 --> 00:03:50,980
position you are in for longer than you do via different sets of factors application you are all we

53
00:03:50,980 --> 00:03:53,560
need to provide the company you ready and the.

54
00:03:54,090 --> 00:04:00,940
And if necessary if anybody then basically it is by default we to these applications by the user which

55
00:04:00,940 --> 00:04:05,020
has been defined and dissected better fecundity IDP entry deployed.

56
00:04:06,430 --> 00:04:13,180
So this about two sets of factors application you are is application you are in our company which exposes

57
00:04:13,180 --> 00:04:15,830
the user interface.

58
00:04:15,910 --> 00:04:19,990
Now when we talk about the data center what is a data center.

59
00:04:19,990 --> 00:04:26,970
So as we know that economically the applications follows the to dial to touch application right.

60
00:04:26,980 --> 00:04:28,250
So one diarrhea.

61
00:04:28,300 --> 00:04:33,730
The application layer as I can tell you is integrating with the data obviously and so here is somewhat

62
00:04:33,730 --> 00:04:39,000
similar analogy if we build up to this is the application the application layer that is different entity

63
00:04:39,010 --> 00:04:45,320
application layer and the backend is the data center so we can analyze it as a database so right.

64
00:04:45,670 --> 00:04:50,520
So it is the backend which is dead and that backend is called data center.

65
00:04:50,860 --> 00:04:51,520
All right.

66
00:04:51,640 --> 00:04:57,700
So application each of the application has a corresponding data center and the backend and cordless

67
00:04:57,800 --> 00:04:59,470
access factors data center.

68
00:04:59,680 --> 00:05:03,220
And then there is also a you are responding to the data center.

69
00:05:03,250 --> 00:05:09,340
We just call data center you are and as highlighted here it gets this demo it starts off suspect dot

70
00:05:09,610 --> 00:05:11,140
com somewhat here.

71
00:05:11,560 --> 00:05:15,350
And just one EMC demo it does suspect suspects start from here.

72
00:05:15,370 --> 00:05:18,000
But the application you are in.

73
00:05:18,390 --> 00:05:24,310
So we're in the third application you will find that part it doesn't favor you at all back in part and

74
00:05:24,310 --> 00:05:26,470
then the data all the time you are right.

75
00:05:26,500 --> 00:05:27,870
So what is in order to you right.

76
00:05:27,890 --> 00:05:30,200
It is let me state.

77
00:05:30,730 --> 00:05:37,660
So all data you are right is the data center here in this point it is the data center you are at this

78
00:05:37,660 --> 00:05:39,760
point okay.

79
00:05:40,070 --> 00:05:41,970
And then this is really data center you.

80
00:05:42,410 --> 00:05:49,820
And then we have suffix it with certain values that is slash data slash B to slash.

81
00:05:49,890 --> 00:05:53,420
So this becomes the culmination of these two things.

82
00:05:53,420 --> 00:05:56,490
The submission of these two things becomes deep or data.

83
00:05:56,510 --> 00:05:57,200
You are right.

84
00:05:57,560 --> 00:06:04,670
And this is the auditor you are right which is this service route you are a of the auditor for Success

85
00:06:04,670 --> 00:06:14,090
Factors cushion arises here multiple full multiple full pushes at ABC year the pieces in BMC this demo

86
00:06:14,170 --> 00:06:15,950
a toxic perspective.

87
00:06:16,330 --> 00:06:20,660
So this is the application you are and we give you front end logging application on to come to you right

88
00:06:21,190 --> 00:06:28,270
now given this complete well can we find out what is the data centers corresponding to this particular

89
00:06:28,300 --> 00:06:34,210
application you are it because as you can see from the name it is PMC is demo it does expect this outcome

90
00:06:34,240 --> 00:06:40,330
and the corresponding data center that is EPA says demo it such as factors that come to the naming names

91
00:06:40,330 --> 00:06:40,920
are different.

92
00:06:41,470 --> 00:06:47,350
And basically if we call this part as host that is a system of it as host.

93
00:06:47,350 --> 00:06:56,080
So this is the data center host and this is the is demo it is the application you add in host are applications

94
00:06:56,080 --> 00:06:57,830
Server Post right.

95
00:06:58,060 --> 00:07:04,330
So how we can find out corresponding to a particular application you are if you know the logging details

96
00:07:04,330 --> 00:07:09,700
or they log in application you are forced access to the application how can we get to know these back

97
00:07:09,700 --> 00:07:13,560
and what is the backend data center you are spending do that.

98
00:07:14,200 --> 00:07:20,230
So this topic we have extensively discussed in the previous sessions album in the S.F. API when we were

99
00:07:20,230 --> 00:07:21,500
discussing this FERPA.

100
00:07:21,550 --> 00:07:24,000
So that session can also be different.

101
00:07:24,100 --> 00:07:31,600
But here in chart also we will come down and try to derive ideas as to how we can associate or how can

102
00:07:31,660 --> 00:07:38,950
we demystify or how can be together make our own tests or if you are a just doing the application you

103
00:07:38,950 --> 00:07:42,030
are seeing that in a jiffy.

104
00:07:42,190 --> 00:07:48,910
Only thing is it is always recommended that this kind of information that is the application do oral

105
00:07:48,970 --> 00:07:50,570
What if you get a interview at all.

106
00:07:50,740 --> 00:07:56,950
It is all this vertical entity we gather from this exercise this support but in case you are together

107
00:07:57,040 --> 00:08:04,090
on your own then it could be provided as a hint that to together the appropriate data set that you are

108
00:08:04,330 --> 00:08:05,890
responding to the application you are.

109
00:08:06,280 --> 00:08:13,020
Otherwise SFP Success Factors support can vary we make that information relevant to you.

110
00:08:13,300 --> 00:08:13,640
All right.

111
00:08:13,930 --> 00:08:21,000
So we further so hearing we are taking some examples of this such as factors or data you are right.

112
00:08:21,550 --> 00:08:26,190
So for an example if we are successful at this instance you are letting the application you are allowed

113
00:08:26,260 --> 00:08:29,700
we can call every company idea compete you are.

114
00:08:29,800 --> 00:08:36,220
So if it is spent is it demo it or such as vectors dot com slash log in the corresponding data center

115
00:08:36,220 --> 00:08:42,790
you are released as GDP as APAC as demo or just let us come and take the spending audit you are right.

116
00:08:42,790 --> 00:08:49,600
Is this particular information suffix it or special effects that we can you can also see the fold over

117
00:08:49,600 --> 00:08:56,500
here so it is always a good idea to put in into it also as a how we can derive this information to see

118
00:08:56,530 --> 00:08:59,140
in a jiffy in the upcoming moments.

119
00:08:59,650 --> 00:09:04,380
So now if we compare these so this wont be all information about the audit you you right.

120
00:09:04,840 --> 00:09:10,300
So now if you compare it with the SFE pay so they say you are that we were concerned about the SFE API

121
00:09:10,300 --> 00:09:10,660
board.

122
00:09:10,960 --> 00:09:15,780
So we had the application success factors in assessing whether that was the same if we had the data

123
00:09:15,780 --> 00:09:20,530
center you whether so the data center remains the same whether it is audit separate gets most of the

124
00:09:20,530 --> 00:09:27,280
time most of the time for like just do regular practices in the data center you would remain the same

125
00:09:27,280 --> 00:09:33,800
whether it is as a PPA or whether it is audit API because the back end up an application is the same.

126
00:09:34,000 --> 00:09:38,980
And then the asset PPA you are all defaults in the fact that there would be a different suffix discreetly

127
00:09:39,010 --> 00:09:49,790
appended to the ability to do data center you add in as compared to the data you are all and then we

128
00:09:49,790 --> 00:09:56,750
had the S of API still you and we are looking the additional question mark still and then also we could

129
00:09:56,750 --> 00:10:00,320
have 40 different projects so point to the left.

130
00:10:00,350 --> 00:10:05,550
So this was a difference on how the asset PPA orders and do the day rates are different.

131
00:10:05,690 --> 00:10:09,130
So here in the audit world we are only concerned about the two parts.

132
00:10:09,140 --> 00:10:16,470
What is the this application you are in the various different tenders that you are a part B and D data

133
00:10:16,480 --> 00:10:22,270
center during the backend is the backend logic part and then the data you are right which is the service

134
00:10:22,300 --> 00:10:26,860
route you are right of our audit that concept you're going to make.

135
00:10:26,870 --> 00:10:34,000
So for us the most important part of the audit that you are a right to do the most important part of

136
00:10:35,280 --> 00:10:36,330
now let's proceed further.

137
00:10:36,330 --> 00:10:45,960
The next slide hearing we saw in the S.F. EPA if you made the calls to the application you are so somehow

138
00:10:45,990 --> 00:10:51,390
if you would have made a call to the application provider like you would have made use of EMC as it

139
00:10:51,890 --> 00:11:00,380
is BMC is demo a total at the start com instead of APAC is demo 8 which was the data center.

140
00:11:00,460 --> 00:11:08,730
And instead of that reviews the applications lost in the SFE be the EU might have gone to desert sands

141
00:11:08,730 --> 00:11:15,390
but it does not advocate it would edit out it can edit it out because of timing or time and all that

142
00:11:15,430 --> 00:11:24,430
pernicious but it's not allowed because of any very specific error stating that you know this is naughty.

143
00:11:24,570 --> 00:11:24,930
Right.

144
00:11:24,930 --> 00:11:25,400
You are right.

145
00:11:25,410 --> 00:11:28,920
We pointed to our future as a PPA cause too.

146
00:11:29,280 --> 00:11:35,810
So in this if it was it was not us very technical error that solar it was more of the time all that

147
00:11:35,920 --> 00:11:36,760
and all that.

148
00:11:36,960 --> 00:11:45,050
But if you tried to make a call to audit a file and use the tax factors application post in the U.S.

149
00:11:45,060 --> 00:11:50,140
right then we are going to get deep edit here state of it and it is what we did.

150
00:11:50,220 --> 00:11:56,730
So we can see done but again the information we just showing up in the air is these EPA endpoint.

151
00:11:57,180 --> 00:12:02,950
So what if the EPA investigates authentication or external or online aviation and what poverty.

152
00:12:02,970 --> 00:12:05,440
So it starts a week it doesn't give 30 permission.

153
00:12:05,470 --> 00:12:14,230
So in the old Rita Cosby strictly needs to follow these or did you worry ah and henceforth leave data

154
00:12:14,240 --> 00:12:15,970
center and not by the application.

155
00:12:15,970 --> 00:12:22,970
So what would so coming to the next point calling the audit done over the applications and what first

156
00:12:22,970 --> 00:12:24,760
name is not supported.

157
00:12:24,780 --> 00:12:32,370
I didn't function that statement but here so rather do this FERPA or it may be we always need to make

158
00:12:32,370 --> 00:12:39,870
a call to the auditor sorry to these data centers to check into the back and not to and never never

159
00:12:39,870 --> 00:12:49,290
buy the front end which if you have to issue an application server or the way some now coming through

160
00:12:49,290 --> 00:12:55,620
these points section of activities center you are also hearing we're discussing about that knowing the

161
00:12:56,340 --> 00:13:03,280
company you are an artist Success Factors application you are and how we can deduce the data center

162
00:13:03,660 --> 00:13:06,110
you are and has four key data.

163
00:13:06,180 --> 00:13:06,810
You are right.

164
00:13:07,560 --> 00:13:09,930
So this is where we can follow.

165
00:13:10,020 --> 00:13:11,810
And this is to be followed on this.

166
00:13:11,860 --> 00:13:15,080
We don't have this information and we want to be inclusive of our kids.

167
00:13:15,120 --> 00:13:18,870
But otherwise this exercise to support and provide this information readily.

168
00:13:19,560 --> 00:13:24,570
So the thing is that this being an application based on the cloud model constitutes different data centers

169
00:13:24,570 --> 00:13:29,460
across the world one of which caused the success of the application instance to which you have access

170
00:13:29,460 --> 00:13:35,730
to the application instances the UI part different ending part an example of the do different value

171
00:13:35,740 --> 00:13:36,870
added it as mentioned below.

172
00:13:36,900 --> 00:13:42,510
So an example of the data center you are in which is the backend part is like it is of the pharmaceutical

173
00:13:42,540 --> 00:13:47,870
school and such as hostname of Success Factors outcome of this particular form where whose name differs

174
00:13:47,880 --> 00:13:49,240
through the data center.

175
00:13:49,290 --> 00:13:55,620
Posting this suspect this instance is a back end by the end users who log in and do the at suspected

176
00:13:55,620 --> 00:13:58,650
instance connects to the application you are allowed the application.

177
00:13:59,220 --> 00:14:04,320
So end users connects to the application you order that for this order the different ending part and

178
00:14:04,320 --> 00:14:10,800
for an example it would be a strategic performance at eight or six suspects dot com slash log in whereas

179
00:14:11,010 --> 00:14:17,700
that is the insidious posting it again it is hostname such as a custom from such blogging where capital

180
00:14:17,710 --> 00:14:20,970
ledge host name refers to the application server posting.

181
00:14:21,030 --> 00:14:27,070
So here we can see that for the data center as well as for the application you are more or less both

182
00:14:27,150 --> 00:14:28,770
the naming conventions are similar.

183
00:14:29,400 --> 00:14:34,920
So if you seek out application server you are duties until you are and so both of them have a difference

184
00:14:34,950 --> 00:14:40,460
in a case for the application whether it is the absence of a hostname or the data center you are logistically

185
00:14:40,460 --> 00:14:41,030
sequels.

186
00:14:41,590 --> 00:14:46,740
Otherwise to our success factors dot outcome is is more or less common in both of these.

187
00:14:46,890 --> 00:14:50,760
So how we can institute the server to leak responding data center.

188
00:14:50,850 --> 00:14:52,110
So let's take an example.

189
00:14:52,110 --> 00:14:55,350
So first of all let's take out that okay.

190
00:14:55,370 --> 00:14:56,300
We have a

191
00:14:59,860 --> 00:15:05,300
so let's take this example except that is dubious current search dash performance manager eight dot

192
00:15:05,320 --> 00:15:06,580
success dot com.

193
00:15:07,060 --> 00:15:11,640
So if we take this example performance manage it X

194
00:15:14,450 --> 00:15:21,420
but performance manager it does success factors dot com.

195
00:15:21,440 --> 00:15:24,340
So this is the application you are in.

196
00:15:24,750 --> 00:15:25,250
That's it.

197
00:15:25,250 --> 00:15:29,640
And we want to find out autistic as polling data center you are right whether it is.

198
00:15:29,660 --> 00:15:31,320
Have you ever.

199
00:15:31,460 --> 00:15:37,530
And we want to find out the data center you are an henceforth the that you are right.

200
00:15:37,670 --> 00:15:38,010
Right.

201
00:15:38,020 --> 00:15:40,860
That is what we are going to eventually come down to.

202
00:15:41,450 --> 00:15:49,010
So the information about it is there is one note that ICP has published a public note and that number

203
00:15:49,010 --> 00:15:50,930
is 2 2 1 5 6 8 2.

204
00:15:51,260 --> 00:15:53,400
And if you seek out this particular law.

205
00:15:53,450 --> 00:15:57,450
So I just copy Open just note here in this particular browser.

206
00:15:57,920 --> 00:16:03,500
So now first of all what we need to do is first of all in the application server hostname so which is

207
00:16:03,500 --> 00:16:07,410
the office manager in our instance for this particular example.

208
00:16:07,460 --> 00:16:12,250
First of all find out be literally where we are what is the numerical value that we have.

209
00:16:12,410 --> 00:16:16,370
So here in this public level we have the numerical number as 8.

210
00:16:16,430 --> 00:16:16,900
All right.

211
00:16:17,170 --> 00:16:19,690
So remember this value 8.

212
00:16:19,730 --> 00:16:28,780
So now to this node public Node 2 2 1 5 7 5 6 8 2 varying success factors API others for different centers

213
00:16:28,990 --> 00:16:30,010
is defined.

214
00:16:30,010 --> 00:16:34,230
So now look out for these data center.

215
00:16:34,360 --> 00:16:36,330
Having these number 8 in it.

216
00:16:36,340 --> 00:16:39,630
So 2 7 2 2 7 4 5.

217
00:16:39,700 --> 00:16:41,560
And is a right to in DC.

218
00:16:41,650 --> 00:16:44,890
So this is the data center goal.

219
00:16:45,070 --> 00:16:47,600
Because you have three data centers already.

220
00:16:47,610 --> 00:16:47,850
Right.

221
00:16:47,860 --> 00:16:49,940
One is the production system one reboot.

222
00:16:50,470 --> 00:16:56,080
So now out of these three will be the one which is called the data center for this particular application.

223
00:16:56,200 --> 00:16:58,420
So performance manager it.

224
00:16:58,450 --> 00:17:02,940
Now the thing is the second hand lies in the name.

225
00:17:03,010 --> 00:17:05,490
The name is performance manager.

226
00:17:05,490 --> 00:17:12,970
Now if the name would have constituted something like sales demo or preview then what would have been

227
00:17:12,970 --> 00:17:15,140
done is it Pradesh something.

228
00:17:15,310 --> 00:17:22,010
If it would have seen its demo its name in the application server name then it would have responding.

229
00:17:22,020 --> 00:17:26,520
It would have corresponded to system there was system bureau that did a demo.

230
00:17:26,530 --> 00:17:30,850
There is a data center would have been a B.S. is what each project suspect.

231
00:17:31,520 --> 00:17:38,050
It would have a review in its name then it would have corresponding I've been corresponding to the previous

232
00:17:38,050 --> 00:17:44,710
system url and a data center for that particular application post or application server host which has

233
00:17:44,770 --> 00:17:49,480
a review in it and literal and the numeric value in it.

234
00:17:49,480 --> 00:17:56,500
That would have been API it reviewed or SPSS dot com my clearances it does not contain a client is neither

235
00:17:56,500 --> 00:17:57,890
system or needed review.

236
00:17:58,240 --> 00:18:05,400
So the corresponding data center would be the one from the production and it would be as GDP s API HDR

237
00:18:05,440 --> 00:18:07,280
success factors dot com.

238
00:18:07,660 --> 00:18:11,850
So this will be the data center you are in for the corresponding application.

239
00:18:11,890 --> 00:18:16,720
You are in and if you want to now come down to the audit you are right.

240
00:18:16,740 --> 00:18:23,620
So audit that you write is work like it has to be a data center you are a you earn less we need to provide

241
00:18:23,710 --> 00:18:29,800
additional information which is at the end of this particular note wherein we have to see audit that

242
00:18:29,830 --> 00:18:37,790
API you are a suffix so we have to take the suffix value and then add it to the data center together

243
00:18:37,800 --> 00:18:39,070
that's your phone.

244
00:18:39,070 --> 00:18:47,100
So it could become deep order that you are right only thing in addition here is the port number is also

245
00:18:47,100 --> 00:18:47,510
mentioned.

246
00:18:47,520 --> 00:18:55,470
So currently it is the default secure port SSL port which is 440 but tomorrow this port changes then

247
00:18:55,470 --> 00:18:58,200
we need to spread that indeed you are a landfill.

248
00:18:58,290 --> 00:19:00,560
So it is a good practice that we have this.

249
00:19:01,230 --> 00:19:04,250
We have this habit right now itself.

250
00:19:04,260 --> 00:19:08,200
So what we need to do is we need to provide the port number.

251
00:19:08,490 --> 00:19:12,840
Here we have the data center you are earning you are.

252
00:19:12,960 --> 00:19:21,360
And then the call in port and then all data and then the suffix that we saw National might be to so

253
00:19:21,360 --> 00:19:22,040
that is fair.

254
00:19:22,080 --> 00:19:25,040
And that is how the order to you are a can be formulated.

255
00:19:25,260 --> 00:19:33,870
And then example would be if we have the application you are let's say as this one which is the entity

256
00:19:33,970 --> 00:19:42,000
we say this term of for our success factors dot com and then virtue would be the data center you are

257
00:19:42,000 --> 00:19:43,160
in for this.

258
00:19:43,180 --> 00:19:51,950
Similarly we will go back to this note 2 2 1 5 6 8 2 and we have dinner medical value for over here.

259
00:19:51,970 --> 00:19:57,720
Since we have a very full value photo area so we will find out one corresponding to four which is DC

260
00:19:57,720 --> 00:19:58,330
four here.

261
00:19:58,860 --> 00:20:04,740
So now forward easy for it would be their production system or will review either of the T either of

262
00:20:04,740 --> 00:20:10,690
the two will be the data center for this application you are now since application you are a transport

263
00:20:10,720 --> 00:20:17,350
system or in its name going to be the one for responding to a system or system you are in here so disparate

264
00:20:17,380 --> 00:20:26,820
from deep data center you are all for us and what will be the core data you are a forest it will be

265
00:20:26,830 --> 00:20:35,100
data center you all and then we have to specify a colon the Ford and Ford we saw right now it is 4 4

266
00:20:35,630 --> 00:20:44,930
4 4 3 right and then we have to put in these four data EPA you are a suffix just ordered it s like we

267
00:20:45,140 --> 00:20:53,350
do so that is how we have been formed and that auditor you are right then the or into your identity

268
00:20:54,290 --> 00:20:59,930
and all the calls audit calls we are going to make is we are going to make it to the audit that you

269
00:20:59,930 --> 00:21:00,370
are right.

270
00:21:00,390 --> 00:21:04,110
It says All right.

271
00:21:04,500 --> 00:21:10,170
And as we have seen in the previous sessions that will be at the service of the auditor you are right

272
00:21:10,230 --> 00:21:12,270
which is now which is the service route.

273
00:21:12,300 --> 00:21:16,500
So I said this would be a record one document which is a service document.

274
00:21:16,500 --> 00:21:23,560
So if you tried to read it did this are basically you tried to put this as committee over here.

275
00:21:23,550 --> 00:21:29,640
This was meant to provide in detail to put the positions that you need to provide hearing and then if

276
00:21:29,640 --> 00:21:36,710
you tried to execute it without happening anything then we should be getting deep service to prevent

277
00:21:36,750 --> 00:21:43,440
which users of the solutions are the entity sets at the highest level.

278
00:21:43,470 --> 00:21:48,600
So these are on different systems which are available out of this particular auditor.

279
00:21:48,660 --> 00:21:55,440
You are right and if you want to have that in the format of Jason and Jason format so we can yes on

280
00:21:55,450 --> 00:22:03,690
this specified format difference to Jason over here and get this out in the Jason format on the entity

281
00:22:03,870 --> 00:22:07,140
search feature excellence via this particular auditor.

282
00:22:07,290 --> 00:22:07,950
Right.

283
00:22:09,150 --> 00:22:09,410
All right.

284
00:22:09,480 --> 00:22:17,220
So here we are in the third friend said okay we can gather the audit you are right and it is the service

285
00:22:17,220 --> 00:22:22,910
route you are right for a lot of audit accounts in the upcoming sessions we'll be discussing more into

286
00:22:22,910 --> 00:22:29,050
the audit that you are a competence and how we can understand each of those components are understand

287
00:22:29,050 --> 00:22:35,240
those two that we can build up and the we can mandate clarity this whole spot and the additional resources

288
00:22:35,750 --> 00:22:40,870
available over the auditor you are different.

289
00:22:40,870 --> 00:22:41,920
Thanks for listening.

290
00:22:41,920 --> 00:22:44,130
Stay tuned and we should have begun.

291
00:22:44,530 --> 00:22:44,800
Thank you.