IBM E02HRLL-G Administration Guide - Page 138

Export and Import of archiver configuration, Archiver runtime tasks, What to do next, About this task

Page 138 highlights

1. Click Hub Admin > Hub Configuration > Archiver > Archiver Configuration. The Archiver Task is displayed in the view mode. 2. Click Edit icon to modify the required parameters. Refer to section Table 37 on page 130 for details on the parameters. 3. Save the archiver configuration. The status will change to Currently being scheduled. 4. An event is published to trigger the scheduler component. The scheduler reads the task configuration and updates the WebSphere Application Server configuration. The database tables are updated with the configuration information, which will be used during execution of archiver task and reporting. 5. The status then changes to Scheduled from Currently being scheduled. What to do next You can also reset a failed archiver task by selecting Resume scheduling. Export and Import of archiver configuration About this task For detailed procedure on exporting and/or importing archiver configuration, refer to the chapter Chapter 6, "Administering partner migration," on page 61 Archiver runtime tasks During runtime, the archiving activity is done as described below: 1. The archiver task is invoked by the system. 2. The configuration is read and the appropriate data is archived to the backup locations. 3. The common file system is cleaned up and data is purged from the database tables. Here is the archiver runtime flow: 1. The Scheduled Archiver task runs as per the configured schedule. 2. The Archiver marks itself as Running in the database. The same status is displayed (at that instance) on the console. 3. The archiver reads the stored configuration from the database. The configuration will be stored in the database during the state transition from 'Currently being scheduled' to 'Scheduled'. 4. If the 'Copy' attribute is selected in the archiver configuration, then: a. The archiver takes the backup of the non-repudiation store from the database. The rows from LG_MSG_ARCHIVE table are exported to files in the directory specified in the database archive destination. It also exports the rows from the LG_CERT_ARCHIVE table. b. The archiver copies the contents of the non-repudiation folder to the backup location. Note: The criteria to backup the data is based on the configuration of the archiver task. 5. The archiver cleans-up the files from the Common File System. All files older than the cutoff date specified are deleted. 132 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide

  • 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

1.
Click
Hub Admin > Hub Configuration > Archiver > Archiver Configuration
.
The Archiver Task is displayed in the view mode.
2.
Click
Edit
icon to modify the required parameters. Refer to section Table 37 on
page 130 for details on the parameters.
3.
Save
the archiver configuration. The status will change to
Currently being
scheduled
.
4.
An event is published to trigger the scheduler component. The scheduler reads
the task configuration and updates the WebSphere Application Server
configuration. The database tables are updated with the configuration
information, which will be used during execution of archiver task and
reporting.
5.
The status then changes to
Scheduled
from Currently being scheduled.
What to do next
You can also reset a failed archiver task by selecting
Resume scheduling
.
Export and Import of archiver configuration
About this task
For detailed procedure on exporting and/or importing archiver configuration, refer
to the chapter Chapter 6, “Administering partner migration,” on page 61
Archiver runtime tasks
During runtime, the archiving activity is done as described below:
1.
The archiver task is invoked by the system.
2.
The configuration is read and the appropriate data is archived to the backup
locations.
3.
The common file system is cleaned up and data is purged from the database
tables.
Here is the archiver runtime flow:
1.
The Scheduled Archiver task runs as per the configured schedule.
2.
The Archiver marks itself as
Running
in the database. The same status is
displayed (at that instance) on the console.
3.
The archiver reads the stored configuration from the database. The
configuration will be stored in the database during the state transition from
’Currently being scheduled’ to ’Scheduled’.
4.
If the ’Copy’ attribute is selected in the archiver configuration, then:
a.
The archiver takes the backup of the non-repudiation store from the
database. The rows from LG_MSG_ARCHIVE table are exported to files in
the directory specified in the database archive destination. It also exports
the rows from the LG_CERT_ARCHIVE table.
b.
The archiver copies the contents of the non-repudiation folder to the backup
location.
Note:
The criteria to backup the data is based on the configuration of the
archiver task.
5.
The archiver cleans-up the files from the Common File System. All files older
than the cutoff date specified are deleted.
132
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide