After you've configured the connections and other resources, you can activate and run the recipe.

1. Activate the recipe. See Activate a Recipe or Accelerator.
2. Run the recipe from an external application.
   1. In the Integrations section of the project workspace, click Actions on the integration flow, then select Run.
   2. On the Configure and run page, click Endpoint metadata.
   3. In the panel that opens, copy the Endpoint URL value. This is the integration flow's endpoint URL.
   4. To sign a message from an external application, send a POST request to this endpoint URL along with the message to be signed. Provide the message in the POST request's Body. See the subsequent step for example request payload.
      The recipe generates a signature for the message you pass in the request body.
   5. To verify a message and signature from an external application, send a POST request to this endpoint URL along with the message and signature to be verified. Provide the message and signature in the POST request's Body. See the subsequent step for example request payload.
      The recipe verifies the signature against the message you pass in the request body.
3. Test the recipe.
   1. In the Integrations section of the project workspace, click Actions on the Sign Message integration flow, then select Run.
   2. On the Configure and run page, in the Request section, click the Body tab and enter the message as request payload.

      Example request payload to sign message:

      {
        "message ": " {\"EmpId\":\"011\",\"Name\":\"xyz\",\"Email\":\"xyz@oracle.com\"}"
      }
      

   3. In the Response section of the Configure and run page, you’ll find the response returned. The response will be the signature of the message.
   4. In the Integrations section of the project workspace, click Actions on the Verify Message integration flow, then select Run.
   5. On the Configure and run page, in the Request section, click the Body tab and enter the message and its signature as request payload.

      Example request payload to verify message:

      {
      "signature": "WX4vporM4aX0djjRHvCKN3Oxkjx0gjixUSXVkpgCU2IijhI6ElUda9hOP5RynDF7nJrDd8DVKpFrdti9jT68APD4UTyqS+Dt7M/qsGzyjqdOsAEMeLLhYrZVMD+F3m49w1YGTAase7o7PtSVW7uhoJ2Mt9i/A4fYVtYoR0T3IXK4DBr6==",
      "message ": " {\"EmpId\":\"011\",\"Name\":\"xyz\",\"Email\":\"xyz@oracle.com\"}"
      }
      

   6. In the Response section of the Configure and run page, you’ll find the response returned. The response would be either true or false depending on the validity of the signature against the message.

      For example:

      {
        "isSignatureValid" : "true"
      }
      

4. Monitor the running of the integration flow in Oracle Integration. See Monitor Integrations.