all of my sidecar files have at least 2 custom metadata tags..
X-TransactionId and X-CorrelationId
Only X-TransactionId appears in any of the metadata tabs of the VSI constructed from the pairs.
What version of DevTest? Which sidecar files are you using? The global ones (meta-req.properties and meta-rsp.properties) or per-payload sidecars?
DevTest 8.1, using per transaction sidecars
I deleted everything and started again..
now the metadata is correct.. don't know what the difference was..
but I have lost a lot of transactions.. there were 107 unique patterns.. in/out.
while magic string should help with unknowns, the existing patterns matter..
and the metadata is the key to verify which input matches..
- 1 person found this helpful
I'm not sure what you mean by "107 unique patterns", but is it possible that the "lost transactions" are just VSE collapsing duplicates? Also, make sure that you honor the correct file naming pattern.
For reference, the valid filename patterns are as follows:
<prefix>-req.<ext>
<prefix>-rsp[#].<ext>
<prefix>-req-meta.properties
<prefix>-rsp[#]-meta.properties
meta-req.properties
meta-rsp.properties
So, some examples:
txn1-req.txt
txn1-rsp.txt
txn2-req.txt
txn2-rsp.txt
txn2-rsp-meta.properties
Or
meta-req.properties
meta-rsp.properties
txn1-req.xml
txn1-req-meta.properties
txn1-rsp0.xml
txn1-rsp1.xml
txn1-rsp1-meta.properties
txn1-rsp2.xml
etc…yes, that is the pattern I am using, all transaction specific sidecar files
Hi All,
I want to use meta.properties file in my Virtual service to set metadata while creating VSI. I am using LISA 7.0.2 and 7.5. I have one request with two responses for that but when I am using meta.properties file along with RR Pairs, it is added as new response in VSI and metadata is not updated. I am using same naming conventions mentioned above. Format of meta.properties file I am using is as below.
Property=Value
dest=IPaddress
Port=8001
Do I need to follow any specific process or any configuration/settings? Can anyone please share sample meta.properties file and steps I need to apply?
If you have one request and two responses and one sidecar file, that should be 4 files. Can you share the 4 filenames?
Hi Daniel,
I am using one request and two responses. Following are the file names I have used.
msg1-req.xml
msg1-rsp1.xml
msg1-rsp2.xml
msg1-rsp1-meta.properties
msg1-rsp2-meta.properties
Meta properties file I have used as are attached here. I have included MQ meta parameters which are changing/dynamic. Do I have to include all the parameters in meta.properties file?
Don't know what is missed here. If you have used meta.properties files can you please share message and meta files you have used if possible.
Thanks in advance
Anyone can help with how to use sidecars RR pairs please?
sure.. the sidecar files hold the metadata for the transaction.
(all these are for the same transaction, here called MSG1, the last two files are sidecar files)
MSG1-req.txt - holds the operation (get/put/post) and URL
for example
get /v1/rates/rules/{URLPARM0}/rating-services/ HTTP/1.1
and the body content, if any (starting on line 2)
(get doesn't have a body)
MSG1-rsp.txt - holds the response body content
{ "label": "xyz", "serviceId": "somelabel", .... }
MSG1-req-meta.properties holds the request headers
for example
X-TransactionId=ssrul1003p
Accept-Language=en-US
Content-Type=application/json
MSG1-rsp-meta.properties holds the output headers
for example
X-CorrelationId=ssrul1003p78b7d2924d4aa2105aa26369b9e5
X-TransactionId=ssrul1003p
HTTP-Response-Code-Text=OK
HTTP-Response-Code=200
Content-Type=application/json
I don't see anything obviously wrong with your files / naming. Please note that this behavior around sidecar files was fully implemented first in 7.5.1. So, if you are using 7.5.1 or newer and it isn't working for you, the best option is probably to contact support.
Daniel
DevTest 8.1, using per transaction sidecars
I deleted everything and started again..
now the metadata is correct.. don't know what the difference was..
but I have lost a lot of transactions.. there were 107 unique patterns.. in/out.
while magic string should help with unknowns, the existing patterns matter..
and the metadata is the key to verify which input matches..