Release 10.0
Added Items
Allowed HTTP method per service For each service, you can identify the HTTP methods that can be used to invoke the service.
Default web service provider endpoint alias For HTTP and HTTPS, you can identify a provider web service endpoint alias as the default for each protocol. If a provider web service descriptor contains a binder that specifies the default endpoint alias or no alias for the Port alias property, Integration Server uses the information in the default alias when constructing the WSDL for the descriptor and during run-time processing.
Follow the master support for JMS connection aliases When Universal Messaging is the JMS provider, you can configure the JMS connection alias to follow the master for consumer and producer connections.
JDBC pool configuration when Integration Server is offline In conjunction with Command Central, Integration Server makes it possible for administrators to change the configuration of JDBC pools when Integration Server is offline.
JMS Trigger Groups A JMS trigger group is a collection of two or more identical JMS triggers. Using the methods in the com.wm.app.b2b.server.jms.consumer. JMSTriggerGroupFacade class, users can quickly create JMS triggers for a trigger group. This can be especially helpful when needing to create several identical triggers that point different Universal Messaging realms, such as when using the new Universal Messaging round robin cluster feature for JMS.
PATCH support Integration Server offers support for HTTP PATCH method, which is used for partial updates. In Service Development, a developer can specify PATCH support when defining REST resources, Integration Server also supports the PATCH methods in the pub.client:http service as well as with CORS (Cross Origin Resource Sharing) requests.
REST Resource URLs Integration Server provides a flexible way to define resource URLs for REST APIs. The new capability allows a developer to define a URL format for the service that does not adhere to the folder structure within the package. Additionally, you can define multiple REST resources for a single service with the HTTP methods of your choice.
Retrieving and Setting HTTP Headers Integration Server provides the ability to get and set HTTP request and response headers easily.
To get the details of an HTTP request for a service, you can add a document reference variable named $httpRequest that references the pub.flow:HTTPRequest document type in the input signature of a service. While invoking a service that includes a $httpRequest document reference variable, Integration Server populates the $httpRequest variable with information from the from the HTTP request.
To get the details of an HTTP request for a service, you can add a document reference variable named $httpRequest that references the pub.flow:HTTPRequest document type in the input signature of a service. While invoking a service that includes a $httpRequest document reference variable, Integration Server populates the $httpRequest variable with information from the from the HTTP request.
Searching for JMS Triggers You can search for of filter the displayed triggers using the Search Triggers link on the Settings > Messaging > JMS Trigger Management page. You can search by trigger name, JMS connection alias or destination to which the trigger subscribes.
Session ID Masking in Logs Session IDs in the session and server logs can now be secured by masking the ID. When you enable the option for securing Session IDs, Integration Server uses the asterisk (*) character to mask the Session ID strings in the logs which prevents user who access the log entries from viewing the actual Session IDs.
Changed Items
Format of the <soap:address location> element in the WSDL of a provider web service descriptor. The <soap:address location> element in the WSDL document generated for a service first provider web service descriptor will be in the following format regardless of specifying either a provider web service endpoint alias or a host and port as the endpoint: http://host_name.port/ws/namespace:descriptorname
Follow the master is configurable per Universal Messaging connection alias For a Universal Messaging connection alias, you can now enable follow the master on a per connection alias basis. Additionally, you can decide whether message producers and/or consumers follow the master realm server using the “Enable Follow the Master for Producers “and “Enable Follow the Master for Consumers” options respectively. Previously, following the master was either enabled or disabled for all connections.
JMS Trigger Management page The Settings > Messaging > JMS Trigger Management page includes the following changes:
Clicking Search Triggers displays a simple search feature.
In the JSM trigger list, columns are re-ordered to put the State column right next to the trigger name.
The State column values can now be “Enabled”, “Disabled”, or “Suspended”. Previously, the possible State values were “Yes”, “No”, “Suspended”.
The Status column is new. Possible values are “Running” or “Not Running” followed up by an explanation, such as “Not Running (trigger disabled)”.
The SOAP-JMS triggers list is displayed only if Integration Server contains a loaded package with a SOAP-JMS trigger.
Maximum Entries in Cache field For a distributed cache, the Maximum Entries in Cache value must be set and must be set to a value greater than 0.
Universal Messaging connection alias Client Authentication The Client Authentication option named SSL is now named Certificate Based, which is more accurate.