Showing posts with label Datapower. Show all posts
Showing posts with label Datapower. Show all posts

Thursday, February 16, 2017

IBM Datapower Developerworks Articles


IBM Datapower DeveloperWorks Articles
4.    Integrating the WebSphere DataPower SOA Appliance XI50 with the WebSphere Application Server V7 default JMS messaging provider
6.    Using OAuth on IBM WebSphere DataPower Appliances
7.     SOA governance using WebSphere DataPower and WebSphere Service Registry and Repository
8.    Leverage DataPower SOA Appliances to extend InfoSphere Master Data Management Server security capabilities
9.    Using WebSphere DataPower and WebSphere MQ File Transfer Edition to manage file transfers
10.  Configuring a WebSphere DataPower Kerberos-secured backend server
11.   Overriding the WebSphere DataPower WSDL optimization conversion
13.  Using the WebSphere DataPower Option for Application Optimization to demonstrate self-balancing across multiple DataPower appliances and intelligent load distribution to backend servers
14.  Integrating WebSphere DataPower SOA Appliances with WebSphere MQ
15.  Performance advantages of using WebSphere DataPower XC10 Appliance as a side cache for a Java application
16.  Integrating DataPower with WebSphere Message Broker using the Broker Explorer
17.  Integrating WebSphere DataPower XML Security Gateway XS40 with WebSphere Message Broker
20. Integrating Web applications with the DataPower Web application firewall service
21.  Managing WebSphere DataPower SOA Appliance configurations for high availability, consistency, and control, Part 1
22. Managing WebSphere DataPower Device configurations for high availability, consistency, and control, Part 2: Application promotion strategies
24. Using DataPower SOA Appliances to query WebSphere Service Registry and Repository

Wednesday, October 26, 2016

How to create an SSL proxy policy



Adding an SSL proxy policy
How to add an SSL proxy policy to a user agent when requests require a secured connection.
About this task
Add an SSL proxy policy to secure the connection. The SSL proxy profile supports secure access to the HTTP proxy server. The SSL proxy profile must be either a client or two-way profile. If the target URL matches the expression, the connection uses the SSL proxy profile to secure the connection.
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 SSL Proxy Profile 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. From the SSL Proxy Profile list, select the profile to support secure access to the HTTP proxy.
    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.

How to create a basic Authentication policy



A user agent request requires basic HTTP authentication (user name and password). If the target URL matches this expression, an HTTP Authorization header is added.
About this task
This header contains the supplied credentials. The URL set defined by this matching expression can be identical to the set defined by the HTTP proxy policy, or it can be a subset.
To establish a connection to a remote resource over FTP or SFTP with password authentication, configure a user agent with a basic authentication policy.
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 Basic-Auth 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 credentials for authentication: User name and password
    4. Click Apply.

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.

Generate Keys and Certificates in Datapower Step by Step



You can generate a private cryptographic key and optionally a self-signed certificate from the Crypto Tools page. The Certificate Signing Request (CSR) needed by a certificate authority (CA) is created by default.
If the file is stored in the cert: directory, it cannot be edited. If a file is stored in the local: directory or in the temporary: directory, it can be edited.
To generate a key:
  1. Click Administration  Miscellaneous  Crypto Tools.
  2. Define the LDAP entry.
    1. Set LDAP (reverse) Order of RDNs to indicate whether to create the LDAP entry in reverse RDN order.onCreates the entry in reverse RDN order.off(Default) Creates the entry in forward RDN order.
    2. Optional: In the Country Name (C) field, enter a country name.
    3. Optional: In the State or Province (ST) field, enter a state name or a province name.
    4. Optional: In the Locality (L) field, enter a locality name.
    5. Optional: In the Organization (O) field, enter the name of an organization.
    6. Optional: In the Organizational Unit (OU) field, enter the name of an organizational unit.
    7. Optional: In the Organizational Unit 2 (OU)Organizational Unit 3 (OU), and Organizational Unit 4 (OU) fields, enter the names of additional organizational units.
    8. In the Common Name (CN) field, enter a common name.
  3. From the RSA Key Length list, select the key length. This defaults to 1024.
  4. In the File Name field, enter the name of the key file to generate. The value takes the directory:///name form. Leave blank to allow the action to create the name.
  5. In the Validity Period field, enter the number of days that the key is valid.
  6. In the Password field, enter a password to access the key file. The password must be at least six characters in length.
  7. In the Password Alias field, enter a password alias to access the key file.
  8. |On HSM-equipped appliances, set Private Key Exportable via hsmkwk to indicate |whether the key can be exported with the HSM key-wrapping-key. |The default value is off.|
    |
    Note:||On Type 7199 appliances, |you must select on or the operation |will fail. The ability to do a subsequent export of the key cannot |be disabled.|
    |
    |
    on|Indicates that the key can be exported.|
    |
    off|(Default) Indicates that the key cannot be exported.|
    |
  9. Set Export Private Key to indicate whether the action writes the key file to the temporary: directory.onWrites the key file to the temporary: directory.off(Default) Does not write the key file to the temporary: directory.
  10. Set Generate Self-Signed Certificate to indicate whether the action creates a self-signed certificate that matches the key.on(Default) Creates a self-signed certificate.offDoes not create a self-signed certificate.
  11. Set Export Self-Signed Certificate to indicate whether the action writes the self-signed certificate to the temporary: directory.on(Default) Writes the self-signed certificate to the temporary: directory.offDoes not write the self-signed certificate to the temporary: directory.
  12. Set Generate Key and Certificate Objects to indicate whether the action automatically creates the objects from the generated files.on(Default) Creates the objects from the generated files.offDoes not create the objects from the generated files.
  13. In the Object Name field, enter the name to use for the Key object and for the Certificate object. Leave blank to allow the action to generate the names from the input information (based on the Common Name (CN) or File Name property).
  14. On HSM-equipped appliances, set Generate Key on HSM to indicate whether to create the key on the HSM.|on|Creates the key on the HSM.|On Type 9235 appliances, |the file name (URL) for the key has the hsm://hsm1/name format.|On Type 7199 appliances, the file name (URL) for the |key has the hsm://hsm2/name format.offCreates the key on the appliance. The file name (URL) for the key has the cert:///name format.
  15. In the Using Existing Key Object field, enter the name of an existing key. If supplied and valid, the action generates a new certificate and a new Certificate Signing Request (CSR) that is based on the key in the identified Key object. In this case, the appliance does not generate a new key.
  16. Click Generate Key to generate a private key and, if requested, a self-signed certificate. A CSR is created automatically.
  17. Follow the prompts.
The CSR can be submitted to a certificate authority (CA) to receive a certificate that is based on this private key. This action creates the following files and objects:
  • Creates the private key file in the cert: directory; for example, cert:///sample-privkey.pem
  • Creates the CSR in the temporary: directory; for example, temporary:///sample.csr
  • If Generate Self-Signed Certificate is enabled, creates a self-signed certificate in the cert: directory; for example,cert:///sample-sscert.pem
  • If Export Self-Signed Certificate is enabled, creates a copy of the self-signed certificate in the temporary: directory; for example, temporary:///sample-sscert.pem
  • If Generate Key and Certificate Objects is enabled, creates a Key object and a Certificate object
If the action creates a self-signed certificate, you can use this certificate-key pair for the following purposes:
  • Establish Identification Credentials
  • Encrypt or decrypt XML documents

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...