Hypertext transport protocol (HTTP)

The HTTP transport node defines the way synchronous messages are sent using the HTTP post method. The HTTP transport node has sender-related properties.

Configuration properties

The following are the properties of this node:

Table 1. HTTP configuration properties
Property Description
URL Enter the URL to which the message is to be posted.
HTTP Post Variable Enter the variable name to which the HTTP post data is to be assigned.
Connection Timeout (ms) Enter the time (in ms) within which the HTTP connection should be created.
Read Timeout (ms) Enter the time (in ms) for which the HTTP connection will wait for a response.
Is Secure If this field is selected, the message is encrypted when being posted to the URL specified.
Key Store Type If Is Secure is checked, set this value to JKS (Java™ Key Store).
Key Store If Is Secure is selected, enter the key store for storing client side digital certificates. If you are using variables instead of the full path names ensure that the variable is defined in the <INSTALL_DIR>/properties/customer_overrides.properties file.
Key Store Passwd If Is Secure is selected, enter the password to access the key store.
Trust Store If Is Secure is selected, enter the trust store for storing server side digital certificates. If you are using variables instead of the full path names ensure that the variable is defined in the <INSTALL_DIR>/properties/customer_overrides.properties file.
Trust Store Passwd If Is Secure is selected, enter the password to access the trust store.
Note: Making a secure HTTP call requires modifying the <JAVA_HOME>/jre/lib/security/java.security file. Comment the following line from the file:
security.provider.2=com.sun.rsajca.Provider

Commenting the property enables the runtime loading of the security.provider variable set later in the code. If you do not want to change the common Java Security file, refer to BEA documentation about using the weblogic.policy file and modify it accordingly. Use the weblogic.policy file with the necessary changes as suggested on the BEA web site.

You can enable the Java Security Manager to use the Oracle weblogic.policy security policy file by adding these parameters to the Oracle WebLogic startup script:

java -Djava.security.manager -Djava.security.policy=<WLS_HOME>/lib/weblogic.policy:wConnection Properties

The following are the HTTP node's connection properties:

Table 2. HTTP connection properties
Connection Node Connection Rules
Can be the first node after the start node Only for services invoked synchronously
Can be placed before
  • Any transport node except for FTP or File I/O
  • Any other component node
Can be placed after
  • Start node
  • Any synchronous transport node
  • Any other component node
  • Any asynchronous transport node (except for FTP or File I/O); use a Pass-through node to connect them
Passes data unchanged Transport nodes do not modify data