Using the administrative console, you can change the configuration of HTTP
export bindings without changing the original source and then redeploying the
application.
About this task
Change HTTP export bindings when you need to change whether a method on a binding is
pingable or to change the encodings a method or binding supports. Required security role for this task: When security and role-base
authorization are enabled, you must log in as an administrator or configurator to perform this
task.
Procedure
- Select the module
that contains the binding by navigating to and clicking the
module name.
- Select
the binding by performing the following steps:
- In the Module components section,
expand Exports.
- Expand the export, and then
expand Binding.
- Click the binding to view
information about its properties.
- Select the scope for the
changes you want to make.
- To change the configuration on the binding scope, click the Binding
Scope tab.
- To change the configuration at the method scope, click the Method
Scope tab.
When both configurations exist, the method scope configuration
takes precedence over the binding scope configuration.
-
Make changes to one or more of the following properties:
- Select method (Method scope only)
Choose the method that you want
to review or configure. Click the arrow in the Select method field to see the
list of methods that can be configured.
- HTTP Methods
Lists the methods and the current configuration for
the methods. You can set whether the method is pingable and the return code for the method.
- Method
The name of the method. The methods are GET, POST, PUT, DELETE,
TRACE, OPTIONS, and HEAD.
- Pingable
Whether or not an HTTP client can ping the method. When
selected, you must specify the return code the binding returns to the client. The default for this
is unchecked.
-
Return code
An integer returned when an HTTP client pings the
method.
- Transfer Encoding
Specifies how information is transferred between
the endpoints. Choices are chunked or identity.
The chunked encoding modifies the body of a message in order to transfer it as a series of
chunks, each with its own size. This allows dynamically produced content to be transferred along
with the information necessary for the recipient to verify that it has received the full message.
Important: If you set this parameter to chunked, Content Encoding
is set to identity and you will be unable to change Content
Encoding.
- Content Encoding
Specifies how the content that traverses the
binding is encoded. Choose either gzip, x-gzip,
deflate, or identity.
- Save your changes to the master configuration.
Results
If you made any updates, the binding is
changed for the selected module. The changes take effect after you
restart the SCA module. Restriction: If the module is redeployed, the configuration
changes you made are replaced by the original settings.
To ensure that the changes you made remain with the module across deployments, use IBM® Integration Designer to make the changes in the source code for the module.
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15