IBM E02HRLL-G Administration Guide - Page 43

Non-prepopulated attributes, Uploading the CPA from the ebMS

Page 43 highlights

v Error During runtime when processing an ebMS document from a Partner, WebSphere Partner Gateway validates that the ebMS interaction conforms to the ebMS configuration (for example if encryption is required) and if there is a non conformance the document is failed. The specific failure events can be viewed in the Document or ebMS viewers. Uploading the CPA from the ebMS page About this task Perform the following to upload a CPA: 1. Click Hub Admin > Hub Configuration > ebMS. 2. Click Upload CPA. 3. Click Browse and select the appropriate CPA package. 4. Ensure that ebMS Version 2.0 is selected. 5. Click Upload. During the CPA upload process, you will be asked to select the internal partner from the partners present in the CPA. Non-prepopulated attributes Attribute values are set at connection level during the upload of the CPA. Some attributes however, do not have pre-populated values. The following is the list of such attributes and example values: v Encryption Mime Parameter Values can be: i. smime-type="enveloped-data" ii. type="text/xml" version="1.0" v Encryption Constituent Values can be: i. text/xml:application/binary:application/edi ii. */xml Note: Values are separated by the colon ( : ) delimiter v Packaging Mime Parameter Values can be: i. type="text/xml" version="1.0" ii. type="multipart/related" v Packaging Constituent Values can be: i. text/xml:application/pkcs7-mime ii. text/xml:application/binary:application/edi Note: text/xml must be the first element. v Exclude from Signature Values can be as follows: i. application/binary:text/xml:application/pkcs7-mime ii. application/pkcs7-mime Chapter 4. Hub administration tasks 37

  • 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

v
Error
During runtime when processing an ebMS document from a Partner, WebSphere
Partner Gateway validates that the ebMS interaction conforms to the ebMS
configuration (for example if encryption is required) and if there is a non -
conformance the document is failed. The specific failure events can be viewed in
the Document or ebMS viewers.
Uploading the CPA from the ebMS page
About this task
Perform the following to upload a CPA:
1.
Click
Hub Admin
>
Hub Configuration
>
ebMS
.
2.
Click
Upload CPA
.
3.
Click
Browse
and select the appropriate CPA package.
4.
Ensure that ebMS Version 2.0 is selected.
5.
Click
Upload
.
During the CPA upload process, you will be asked to select the internal partner
from the partners present in the CPA.
Non-prepopulated attributes
Attribute values are set at connection level during the upload of the CPA. Some
attributes however, do not have pre-populated values. The following is the list of
such attributes and example values:
v
Encryption Mime Parameter
Values can be:
i. smime-type=”enveloped-data”
ii. type=”text/xml” version=”1.0”
v
Encryption Constituent
Values can be:
i. text/xml:application/binary:application/edi
ii. */xml
Note:
Values are separated by the colon (
:
) delimiter
v
Packaging Mime Parameter
Values can be:
i. type=”text/xml” version=”1.0”
ii. type=”multipart/related”
v
Packaging Constituent
Values can be:
i. text/xml:application/pkcs7-mime
ii. text/xml:application/binary:application/edi
Note:
text/xml must be the first element.
v
Exclude from Signature
Values can be as follows:
i. application/binary:text/xml:application/pkcs7-mime
ii. application/pkcs7-mime
Chapter 4. Hub administration tasks
37