Here a user can directly upload the protofiles by enabling the checkbox for protobuf, and can provide a name for the protofile.

If for Response, Content-Type is set to application/x-protobuf or x-application/protobuf then, only response will be converted into protobuf format. Example -Possible Content-Type header to convert body into protobuf are -Content-Type: application/x-protobufORContent-Type: x-application/protobuf

• Sample Request:Sample request of the service. This is used for testing and for defining Request Parameters. User can select a file where sample request is stored by clicking the Choose
• Response Template:Response of this service for this template. User can parameterize it later using different types of parameters. User can select a file where sample response is stored by clicking the Choose button
  1. There are two sections: Request and Response. Provide the following details and click Save.
     1. Enable Protobuf : Select this check box to enable Protobuf.
     2. Upload Proto File :Select the Proto file by using the Choose button or paste the file content in the body section.
        1. Request Proto file : To get the content in encoded format as passed in the request.
        2. Response Proto file : To get the response in encoded format from the server.
     3. Proto File Name : Provide the name of the proto file.
     4. Message Type: This contains the schema of proto file. This displays the parsed message types from the uploaded proto file. If the content of the proto file is modified, the 'Message Type' drop-down is automatically be refreshed.
     5. Note: All the fields in 'Request' and 'Response' sections are mandatory if enabled.
  2. When you hit a service from Service Virtualization, the data is sent in the encoded format.