McAfee EPOCDE-AA-BA Product Guide - Page 87

Creating a folder location on an FTP, HTTP server or UNC share

Page 87 highlights

Setting up repositories Creating and configuring FTP, HTTP, and UNC repositories 8 Tasks • Creating a folder location on an FTP, HTTP server or UNC share on page 87 Use this task to create the folder that hosts repository contents on the distributed repository system. • Adding the distributed repository to ePolicy Orchestrator on page 87 Use this task to add the new distributed repository to the repository list and configure it to use the folder you created. • Avoiding replication of selected packages on page 89 If distributed repositories are set up to replicate only selected packages, your newly checked-in package is replicated by default. Depending on your requirements for testing and validating, you might want to avoid replicating some packages to your distributed repositories. • Disabling replication of selected packages on page 89 • Enabling folder sharing for UNC and HTTP repositories on page 90 Use this task to share a folder on an HTTP or UNC distributed repository. • Editing distributed repositories on page 90 Use this task to edit a distributed repository. • Deleting distributed repositories on page 90 Use this task to delete HTTP, FTP, or UNC distributed repositories. Doing this removes them from the repository list, and removes the distributed repository contents. Creating a folder location on an FTP, HTTP server or UNC share Use this task to create the folder that hosts repository contents on the distributed repository system. • For UNC share repositories, create the folder on the system and enable sharing. • For FTP or HTTP repositories, use your existing FTP or HTTP server software, such as Microsoft Internet Information Services (IIS), to create a new folder and site location. See your web server documentation for details. Adding the distributed repository to ePolicy Orchestrator Use this task to add the new distributed repository to the repository list and configure it to use the folder you created. Do not configure distributed repositories to reference the same directory as your master repository. Doing so causes the files on the master repository to become locked by users of the distributed repository, which can cause pulls and package check-ins to fail and leave the master repository in an unusable state. Task For option definitions, click ? in the interface. 1 Click Menu | Software | Distributed Repositories, then click Actions | New Repository. The Distributed Repository Builder wizard opens. 2 On the Description page, type a unique name and select HTTP, UNC, or FTP, then click Next. The name of the repository does not need to be the name of the system hosting the repository. McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide 87

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328

Tasks
Creating a folder location on an FTP, HTTP server or UNC share
on page 87
Use this task to create the folder that hosts repository contents on the distributed
repository system.
Adding the distributed repository to ePolicy Orchestrator
on page 87
Use this task to add the new distributed repository to the repository list and configure it to
use the folder you created.
Avoiding replication of selected packages
on page 89
If distributed repositories are set up to replicate only selected packages, your newly
checked-in package is replicated by default. Depending on your requirements for testing
and validating, you might want to avoid replicating some packages to your distributed
repositories.
Disabling replication of selected packages
on page 89
Enabling folder sharing for UNC and HTTP repositories
on page 90
Use this task to share a folder on an HTTP or UNC distributed repository.
Editing distributed repositories
on page 90
Use this task to edit a distributed repository.
Deleting distributed repositories
on page 90
Use this task to delete HTTP, FTP, or UNC distributed repositories. Doing this removes them
from the repository list, and removes the distributed repository contents.
Creating a folder location on an FTP, HTTP server or UNC share
Use this task to create the folder that hosts repository contents on the distributed repository system.
For UNC share repositories, create the folder on the system and enable sharing.
For FTP or HTTP repositories, use your existing FTP or HTTP server software, such as Microsoft
Internet Information Services (IIS), to create a new folder and site location. See your web server
documentation for details.
Adding the distributed repository to ePolicy Orchestrator
Use this task to add the new distributed repository to the repository list and configure it to use the
folder you created.
Do not configure distributed repositories to reference the same directory
as your master repository. Doing so causes the files on the master
repository to become locked by users of the distributed repository, which
can cause pulls and package check-ins to fail and leave the master
repository in an unusable state.
Task
For option definitions, click
?
in the interface.
1
Click
Menu
|
Software
|
Distributed Repositories
, then click
Actions
|
New Repository
. The Distributed
Repository Builder wizard opens.
2
On the Description page, type a unique name and select
HTTP
,
UNC
, or
FTP
, then click
Next
. The name
of the repository does not need to be the name of the system hosting the repository.
Setting up repositories
Creating and configuring FTP, HTTP, and UNC repositories
8
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide
87