Showing posts with label policy. Show all posts
Showing posts with label policy. Show all posts

Wednesday, October 26, 2016

How to create a SOAP Action Policy



Adding a SOAP action policy
A user agent can require that the contents of the HTTP SOAPAction request header field be supplied.
About this task
The HTTP header contains the SOAP action (a URI that identifies the intent of the SOAP HTTP request). If the header contains the SoapAction: http://example.org/add header, the URI of http://example.org/add is the value.
Procedure
  1. In the search field, enter User Agent.
  2. From the search results, click User Agent.
  3. Click the name of a user agent configuration.
  4. Click the Soap-Action Policy tab.
  5. Add a policy.
    1. Click Add.
    2. In the URL Matching Expression field, enter a shell-style expression to be the matching pattern for the URL set.
    3. In the Soap Action field, enter the URI of the SOAP action.
    4. Click Apply.
  6. Optional: Repeat the previous step to add another policy.
  7. Click Apply to save the changes to the running configuration.
  8. Optional: Click Save Configuration to save the changes to the persisted configuration

adding a header injection policy



Adding a header injection policy
Add a header injection policy to a user agent to inject an HTTP header (name-value pair) into a request to the remote server.
About this task
Several DataPower® services can also inject HTTP headers. The user agent operates on the request after the service.
Procedure
  1. In the search field, enter User Agent.
  2. From the search results, click User Agent.
  3. Click the name of a user agent configuration.
  4. Click the Inject Header Policy tab.
  5. Add a policy.
    1. Click Add.
    2. In the URL Matching Expression field, enter a shell-style expression to be the matching pattern for the URL set.
    3. Define the header to inject: Header name and value.
    4. Click Apply.
  6. Optional: Repeat the previous step to add another policy.
  7. Click Apply to save the changes to the running configuration.
  8. Optional: Click Save Configuration to save the changes to the persisted configuration.

Adding an SFTP client policy



How to add an SFTP client policy to a user agent.
About this task
The user agent controls the client settings for outgoing SFTP connections for requests that match the URL expression. These settings can be further overridden by query parameters in the URL that initiates the file transfer.
Without SFTP client policies, the client authentication settings are controlled by the basic authentication and public key authentication policies.
Availability: These setting are available for only appliances with the B2B feature.
Procedure
  1. In the search field, enter User Agent.
  2. From the search results, click User Agent.
  3. Click the name of a user agent configuration.
  4. Click the SFTP Client Policies tab.
  5. Add a policy.
    1. Click Add.
    2. In the URL Matching Expression field, enter a shell-style expression to be the matching pattern for the URL set.
    3. From the SSH client profile list, select an SSH client profile.
    4. Optional: Set the Use unique file names property to off to disable the generation of a unique file name for puts to a remote directory.
    5. Click Apply.
  6. Optional: Repeat the previous step to add another policy.
  7. Click Apply to save the changes to the running configuration.
  8. Click Save Configuration to save the changes to the persisted configuration.

Adding an SMTP client policy



Adding an SMTP client policy
How to add an SMTP client policy to a user agent.
About this task
Availability: Appliances with the B2B feature.
The user agent controls the client settings for outgoing SMTP connections for requests that match the URL expression. These client settings can be overridden by query parameters in the URL that initiates the mail transfer.
Procedure
  1. In the search field, enter User Agent.
  2. From the search results, click User Agent.
  3. Click the name of a user agent configuration.
  4. Click the SMTP Client Policies tab.
  5. Add a policy.
    1. Click Add.
    2. In the URL Matching Expression field, enter a shell-style expression to be the matching pattern for the URL set.
    3. In the Recipient email field, enter the default email address to which to send email messages.
    4. In the Sender email field, enter the default email address that identifies the sender.
    5. In the Subject field, enter the default subject for email messages.
    6. From the Options list, click the check boxes for the SMTP options to enable.
    7. To use the Simple Authentication and Security Layer (SASL) client authentication: From the Client Authentication list, select the authentication method.
    8. Click Apply.
  6. Optional: Repeat the previous step to add another policy.
  7. Click Apply to save the changes to the running configuration.
  8. Optional: Click Save Configuration to save the changes to the persisted configuration.

Distributed Computing: A Guide to Comparing Data Between Hive Tables Using Spark

In big data, efficient data comparison is essential for ensuring data integrity and validating data migrations. Apache Spark, with its in-me...