Media Transit Requests - HP Data Protector A.06.11 User Manual

3 - Request audit
nl
4 - Send audit
• Parameter 2: XML parameters file
Filename of the XML parameters file, delimited by quotation marks. Media Oper-
ations creates this file before calling the script.
Parameter 3: Results filename
•
Filename passed into the script by Media Operations, delimited by quotation
marks. Media Operations expects any results of the script to be written to this
file.
Parameter 4: Proxy type
•
Whether a Proxy Server is needed to connect to the offsite vendor and, if so,
what type:
0 - No proxy
nl
1 - HTTP proxy
nl
2 - Socks proxy
Parameter 5: Proxy server name
•
Network name of the Proxy Server.
Parameter 6: Proxy port
•
Port number used to connect to the Proxy Server.
• Parameter 7: Proxy username
• Parameter 8: Proxy password

Media transit requests

Transit requests are electronic notifications of media movements to/from an offsite
vendor. There are two types:
• Outgoing —notify offsite vendors about media shipped to them (including media
details).
• Return —notify offsite vendors that you want them to return media to you and
which sets of media to return.
The XML parameters file conforms to the TransitRequest.dtd file. If the transit
request is a return request (for example, transit type is cor or scratch), XML includes
a destination with address and contact details.
Either create two scripts (one for outgoing and one for return requests) or create one
script that adapts its behavior based on the transit type in the XML parameters file.
On exit, your script must return one of these result codes:
146 External interfaces