This file provides important information about enhancements and fixes in webMethods Integration Server 6.5. For information about enhancements and fixes in previous webMethods Integration Server releases, see the readme for those releases.
1.0 Enhancements
2.0 Included Fixes and Service Packs
5.0 Added and Removed Services and APIs
6.0 Enhancements and Fixes in Previous Release
webMethods Integration Server 6.5 includes the following enhancements.
1-I4WSL
New “Suspended” state for polling notifications and listeners. With this
release you can now suspend polling notifications and listeners without the
potential loss of data. For example, you can now suspend JDBC Adapter polling
notifications and still maintain event data within a notification’s buffer
table until you re-enable the notification.
1-O0LSX
Support for polling notifications in a cluster. You can now deploy JDBC
Adapter polling notifications in an Integration Server cluster without the
worry of receiving duplicate notification documents or documents out of order.
1-USG1Q
Hiding non-public WmART services in Developer.
Services that are delivered with the WmART package that are not intended for
public use are now hidden from view in the Developer. For the list of publicly
supported WmART services, see the webMethods Developer Built-In Services Guide.
1-UTO3E
Listeners now require active notifications before being enabled. Adapter
listeners can no longer be enabled if they do not have any active notifications
associated with them.
1-VQ0LQ
Track and display adapter fix levels. You can now see a list of updates applied
to your 6.x adapters on each adapter’s About page in
the Integration Server Administrator.
1-WZFFF
Dynamic connections at run time. Adapter services now provide a new
parameter called $connectionName that enables you to dynamically override the
connection associated with an adapter service at run time. In previous
releases, you could permanently change the connection associated with a
service, but you could not programmatically update a connection associated with
a service within a flow.
1-WZIFB
Extended set of WmART public services. The WmART package now contains
additional public services that enable you to programmatically locate and list
adapter components such as connections, listeners, services and notifications.
You can use these new services for creating more robust adapter integrations.
1-ALTPR
A Refresh Page link is now available on Integration Server Administrator
Trigger Management pages. This link provides a quick and convenient way to view
the latest Trigger-specific values for the queue settings and status of the
triggers. It also displays the current Global trigger settings and allocations.
1-AWAJH, 1-AI5GF, 1-PMJQB, 1-PMJZF, 1-83NT9
Integration Server 6.5 allows you to control trigger processing at the
individual trigger level. You can now turn the retrieval of documents and the
processing of those documents on or off on a trigger-by-trigger basis. This
capability will greatly facilitate maintenance on your back-end systems.
In addition, Integration Server 6.5 offers a centralized trigger management user interface that lets you view, edit, and configure every trigger for a given Integration Server. Because you have greater visibility into the number of documents and threads that are available to specific trigger queues, you can more easily adjust the run-time performance of your triggers. All of your trigger modifications are persisted across restarts and package reloads, improving your ability to administer and maintain your Integration Server.
1-UKCOE, 1-QLM8M
In Integration Server 6.5, several key modifications to the LDAP Manager
provide greater reliability, flexibility, and improved scalability when
authenticating and authorizing thousands of users and groups contained in an
enterprise-class LDAP system. Users are now authenticated directly against the
LDAP system, and group information is retrieved on demand, reducing memory
overhead and providing compatibility with a variety of authentication
mechanisms. In addition, you can now configure more than one LDAP system at run
time. This allows you to authenticate and authorize against users who are
configured in separate LDAP systems, and to fail over to backup LDAP systems
for increased availability.
1-9HIXE
webMethods Integration Server now provides direct support for Microsoft Active
Directory as a means for authenticating groups/users. Integration Server no
longer requires a workaround to support Microsoft Active Directory.
1-7GUE9, 1-7SPBS, 1-PU2P3
Integration Server 6.5 introduces a diagnostic port and an accompanying
supportability tool you can use to better diagnose your run-time environment.
Together, the port and the tool allow you to reliably obtain key diagnostic
information about Integration Server, such as configuration, operational, and
logging data, without disrupting the normal operations of your system.
1-SH2TT
You can start Integration Server 6.5 in "safe
mode" to better diagnose and correct fatal initialization errors. When you
start Integration Server in “safe mode,” connections to the Integration Server
database and webMethods Broker are disabled and all packages other than WmRoot
are inactive. You can then use Integration Server Administrator to isolate and
correct invalid configuration settings that are preventing you from starting a
fully operational run-time environment.
1-5Y0KB
Integration Server 6.5 introduces Secure FTP, the ability to send and receive
credentials and data securely via FTP over SSL. You can enable an FTPS
listener to receive requests from standard Secure FTP clients, and you can
leverage built-in services to send data to standard Secure FTP servers.
1-T8NLZ
The pub.client.ftp:ls and pub.client.ftp:cdls services
now support a new input parameter named orderby. If this parameter is
specified, the service returns a list of files in timestamp order. This is
equivalent to sending the NLST -t command to the remote FTP server.
1-T9APT
Integration Server FTP Server functionality now provides an FTP home directory
for each user. The Integration Server creates each user’s FTP home directory
the first timer the user successfully logs on to the FTP Server. To configure
the directory that contains the users’ home directories, set the configuration
parameter watt.server.userFtpRootDir.
See the webMethods Integration Server Administrator’s Guide, Appendix B, for more information about this feature and a description of the new parameter watt.server.userFtpRootDir.
1-SKEF2
The pub.client.ftp:get service now supports a new
input parameter called largefilethreshold. If this parameter is specified, then
for files that are larger than the specified threshold, the service returns a
handle to a java.io.InputStream instead of returning the file as a byte[].
1-T8B2H
The FTP listener now supports putting XML files that
do not have a .xml extension. See the XML
Services Developer’s Guide for documentation on how to configure the
content handler for files that do not have an extension.
1-T9ARU
A new input parameter called putunique has been added to the pub.client:ftp, pub.client.ftp:put, and pub.client.ftp:mput services.
When this parameter is set to true, the services will send the STOU command to
the remote FTP server to put the file with a unique name.
1-OE1QW, 1-OE1S7
Passwords stored by Integration Server to access external resources (including
remote Integration Servers) are now encrypted on disk.
The master password used to encrypt and decrypt the outbound passwords is
configurable through the Integration Server Administrator.
1-A5Q1V
The passwords for Proxy Servers, Email Listeners, Clustering,
Remote Server Aliases, LDAP, WmDB package, and JDBC pools are now stored in a
secure store and have been removed from the config files.
1-AK941
The Flat File Adapter now supports reading and writing documents based on byte
positions instead of character positions. This allows customers to read and
write fixed-position flat files in multibyte encodings such as ISO-2022-JP.
Note: The Flat File adapter only returns character-based data. It is not capable of returning the raw bytes of the original file.
1-AKBFP
When defining a flat file schema, you can define an
alternate name for a record, composite, or field definition. You do this to
provide a more meaningful name that can be helpful when mapping the record,
composite, or field definition.
1-AKBGJ
When defining a flat file schema, you can define a
text description for a record, composite, or field definition. Users can view
this description as a tool tip in the Flow Editor when mapping the record,
composite, or field definition.
1-OYWSQ (IS_6-0-1_Fix131)
The pub.flatFile:convertToValues and wm.b2b.edi:convertToValues service can
produce composites that contain empty, trailing subfield delimiters. This fix
alters the behavior of the following flags to suppress consecutive subfield
delimiters at the end of a composite:
- For the pub.flatFile:convertToValues service, this fix affects the trimTrailingDelimiters flag
- For the wm.b2b.edi:convertToValues service, this fix affects the noEmptyTrailingFields flag
1-UMEK7 (IS_6-1_Fix65)
Enhancements to WmFlatFile for alternate code sets.
The WmFlatFile package now supports alternate code sets. This allows the WmFlatFile package to create a flat file schema with the correct code lists for EDI transactions that contain both consecutive loops with the same name and alternate code sets.
The WmFlatFile package now provides a configuration parameter that you can use to disable support for alternate code sets. If you want to disable support for alternate codes sets, add the following to the <IntegrationServer>/packages/WmFlatFile/config/ff.cnf file:
useAlternateCodeSets=false
1-USS3R (IS_6-1_Fix66,
IS_6-0-1_SP2_Fix139)
The pub.flatFile:convertToValues service returns the recordWithNoID record as
an array, even if there is only one record.
To resolve this issue, WmFlatFile provides the new configuration parameter 'recWithNoIDLike46' that can be used to set the behavior of the pub.flatFile:convertToValues service to match the behavior of the 4.6 version. If there is only one recordWithNoID record, the service returns the recordWithNoID as a single record and not as an array.
To have records without an id behave the same as 4.6, add the following line to the <IntegrationServer>
/packages/WmFlatFile/config/ff.cnf file:
recWithNoIDLike46=true
1-UXZU4 (IS_6-1_Fix72)
Enhancement to WmFlatFile to enforce field sorting by the pub.flatFile:convertToString
service.
In WmFlatFile version 6.0, the pub.flatFile:convertToString service always sorted fields in records. In a later release, the value of 'sortInput' input parameter indicated whether or not the pub.flatFile:convertToString sorted fields to match the flat file schema. The default for 'sortInput' parameter was false, which indicates that the default behavior is that the service does not sort fields. (This requires that the fields in the record match the order of the flat file schema.) Consequently, the default field sorting behavior for the pub.flatFile:convertToString service is different in current versions of WmFlatFile than in the 6.0 version.
To provide the default field sorting behavior available in the 6.0 FCS version, WmFlatFile now provides a configuration parameter 'alwaysSortFields'. When this parameter is set to true, the pub.flatFile:convertToString service will always sort fields, regardless of the value of the input parameter 'sortInput'. The default value of the 'alwaysSortFields' parameter is false. If you want to enforce field sorting, add the following to the <IntegrationServer>/packages/WmFlatFile/config/ff.cnf file:
alwaysSortFields=true
Note: The value of the 'sortInput' parameter also determines whether records are sorted. The value of the 'alwaysSortFields' configuration parameter will not overwrite the record sorting behavior set by the 'sortInput' parameter.
1-QVAMY (IS_6-0-1_SP2_Fix156,
IS_4-6_SP2_Fix184)
Integration Server does not detect malformed entities during XML parsing.
This error occurs because the XML parser does not detect malformed entities and parses them into an empty string. For example, "> ;" becomes "".
According to the XML 1.0 spec, an entity or character spec is of the form &string; with no white space. For example, > is a legal reference and > ; is illegal.
With this fix, by default the Integration Server throws an exception if it detects a malformed entity. Specifically the pub.web:documentToRecord service (4.6) and the pub.xml:xmlNodeToDocument service (6.x) will throw the following error:
com.wm.app.b2b.server.ServiceException:
[ISC.0042.9332] Malformed entity reference: <illegal text>
For customers who prefer to allow the malformed entries, the following configuration property has been added.
watt.server.xml.enforceEntityRef=false
Set this property to "false" to prevent the Integration Server from throwing an exception when the XML parser detects a malformed entity.
1-B0YJK
If Integration Server cannot connect to the configured remote repository on startup, it will now log an error message to the journal log
and then shut down.
1-IVR2D
TSpace management and configuration is now performed by Integration Server
instead of by layered packages such as WmTN, WmEDI, and WmFlatFile. See the webMethods Integration Server
Administrator’s Guide, Appendix B, for a description of the new parameters
watt.server.tspace.location and watt.server.tspace.max.
1-N9RUR
The pub.client:smtp service has a new input parameter
called auth, which allows the user to input user and password information.
1-O7B6N
The Integration Server is now enhanced to save the status of XA transactions.
In accordance with the JCA specification, Integration Server’s XA compliant
transaction manager saves its decision to commit a transaction as well as
manage the recovery of the transaction if the transaction is not
committed.
1-PXWZ1
Integration Server now includes the DataDirect Connect JDBC Sybase Driver.xml
file so the user can select the built-in Sybase Driver when configuring the
JDBC pool for audit logging.
1-QWQ4D, 1-QLIXL
Integration Server 6.5 services have a new property that specifies how many
times the service should be retried if the service throws a transient
error as indicated by an ISRuntimeException. For information about configuring
service retry, see the webMethods Developer User's Guide, chapter 6.
1-SZDDH
The pub.flow:getRetryCount service returns a new
parameter called maxRetryCount, which returns the maximum retry attempts
specified for the top-level service or trigger.
1-T4JYF
The number of System Threads shown on the Statistics page of the webMethods
Integration Server Administrator now matches the number of threads shown by a
thread dump. This is a more accurate representation of the actual thread count.
1-QLM9I, 1-QEGRU
The internal Apache Tomcat engine has been upgraded from version 4.x to version
5.0.28. This version of Tomcat supports many more character encodings for JSP
pages than the previous versions.
1-QLRJD, 1-RUWNN, 1-OFBC8
The Entrust Java Toolkit that ships with Integration Server and provides SSL
support has been upgraded from version 6.1 to version 7.0. This version of the
toolkit includes enhancements such as:
- Single signed jar
file
- SSL handshake
error fix
- Support for 256/384/512 bit SHA hashes
- AES support for SSL
- Validation of PKCS#7 and XML Sig
without logging into Entrust user object
- Timestamp support
- Fix for the "bad client public DH
value" error
- Removal of upper limit on the number
of certificates that can be in the trusted CA folder
1-TOIM3
A new “Refresh Trusted CA Certificates Cache” link has been added to the
Security > Certificates screen. This allows you to add new certificates to
the CA certificates directory and apply them without needing to restart
Integration Server.
1-U4LNF
(IS_6-1_Fix58)
Added capability to register Content Handlers for multipart messages at the
service level.
Currently in the Integration Server, only one Content Handler may be registered per content type. This is usually not a problem. However, multipart messages need to be processed in different ways since multipart messages are used as transport structures for different protocols (i.e. EDI, email). In each of these cases, the multipart message needs to be processed in a different way. This is where it is useful to have the ability to register multiple Content Handlers for multipart messages. The Content Handler that is used for a particular message depends on the service being invoked. To accomplish this, a new API has been added.
The following method has been added to the com.wm.app.b2b.server.HandlerFactory_Multipart class.
putContentHandler(String
serviceName, Class contentHandler)
where
serviceName is the name of the service that this Content Handler will apply for
and:
contentHandler is the ContentHandler to register for this service.
contentHandler MUST
implementcom.wm.app.b2b.server.ContentHandler.
After this call, whenever serviceName is invoked and the content type of the incoming data is multipart/mixed or multipart/related, then contentHandler will be used.
Other types of multipart messages (i.e. multipart/form-data) can also be used in this way by calling
ServerAPI.registerContentHandler*"multipart/related",
new HandlerFactory_Multipart());
1-UWLZY
(IS_6-0-1_SP3_Fix8, IS_4-6_SP3_Fix2)
SOAP Envelope reference changed to point to 2001 recommendation.
A SOAP Envelope created using the pub.soap.utils:CreateSoapData service has namespace declarations that point to the 1999 version of the schema specification. This fix updates the reference to the 2001 recommendation.
The old SOAP envelopes had the following namespace declarations:
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
The new SOAP envelopes will have the following namespacedeclarations:
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
1-V6ROS
The default JVM that is used to run Integration Server on Windows platforms has
been upgraded from IBM JRE 1.3.1 to IBM JRE 1.4.2.
1-WDBN7
The default JVM minimum and maximum heap size in server.bat/sh was increased to
256 MB and 512 MB, respectively.
webMethods Integration Server 6.5 includes the following fixes and service packs that were shipped since the last release.
webMethods Integration Server 6.5 includes the contents of webMethods Integration Server 6.1 Service Pack 1. For more information about this service pack, see the webMethods Integration Server 6.1 Service Pack 1 Enhancements and Fixes document on the webMethods Bookshelf.
1-UVKHZ (IS_6-1_SP1_Fix1, IS_6-1_Fix69, IS_6-0-1_SP3_Fix6,
IS_6-0-1_SP2_Fix171)
File poller cannot move a file from monitoring directory to working directory
even though file poller has permissions.
Integration Server generates the following message when the file poller attempts to move the file:
[FPL.0001.0012C] Could not move source file /fileLocation/fileName to working directory /newLocation
This issue is now fixed.
1-V1K2L (IS_6-1_SP1_Fix1, IS_6-1_Fix75)
Record delimiter characters are lost when pub.flatfile:convertToValues service
executes.
When the pub.flatfile:convertToValues service writes undefined data to tspace, the record delimiter characters are lost.
Now, the pub.flatfile:convertToValues service preserves record delimiter characters.
1-TLOWQ (IS_6-1_SP1_Fix2, IS_6-1_Fix62)
References in decoded SOAP messages appear as NULL.
The SOAP message decoder is not properly handling SOAP messages that contain several references to the same multi-reference. In the resulting decoded document, every instance of the reference, except for the last instance, has a value of NULL. The last instance contains the correct value.
With this fix, SOAP messages that contain several references to a single multi-reference are decoded correctly.
1-V37ET (IS_6-1_SP1_Fix2, IS_6-1_Fix76)
Integration Server generates invalid XML when creating an XML Schema from an IS
schema.
If an IS schema contains a string data type in which the enumeration or pattern constraining facet values use escapable characters, the Integration Server generates invalid XML when attempting to create an XML Schema definition for the IS schema. This situation can also occur when the Integration Server generates a WSDL file for a service that uses the IS schema in its input or output signature.
With this fix, the Integration Server properly handles escapable characters when generating an XML Schema definition for an IS schema.
1-T7H6Q (IS_6-1_SP1_Fix3, IS_6-1_Fix62, IS_6-0-1_SP3_Fix3,
IS_6-0-1_SP2_Fix145)
Audit logging creates large file-based log files.
If Audit Logging has been configured to write to a database, and the database is unavailable, the audit logging subsystem will log every time an attempt to log an audit event fails. This can have the effect of creating very large file based log files on the Integration Server.
With this fix, this audit logging subsystem only logs the first failed attempt to log an audit event.
1-UA5RT (IS_6-1_SP1_Fix4, IS_6-1_Fix62, IS_6-0-1_SP3_Fix8)
Flow step time-out values are not being honored.
When multiple flow services execute concurrently, the Integration Server reports that flow steps time out even if the flow steps execute within the specified time-out period.
With this fix, flow step time out values will be honored and will work as documented.
1-TR9F6 (IS_6-1_SP1_Fix6, IS_6-1_Fix62)
Fields are missing from webMethods Repository Configuration screen.
The webMethods Repository Configuration screen (which can be accessed by running repoui.sh or repoui.bat) does not display all fields located in the Database portion of the screen. This situation occurs if the value of the Database URL field is greater than 104 characters.
This fix resolves this issue by increasing the maximum length of the Database URL field to 300 characters.
1-U6T5U (IS_6-1_SP1_Fix7, IS_6-1_Fix62)
WmUDDI package contains documents with invalid document references.
This fix corrects the invalid document references.
1-URG16 (IS_6-1_SP1_Fix8, IS_6-1_Fix68)
Guaranteed documents might be lost when the Integration Server and Broker are
disconnected.
When the connection to the Broker is lost, the Integration Server places all published guaranteed documents in the outbound document store. When the connection to the Broker is re-established, the Integration Server publishes the documents from the outbound document store to the Broker. Under certain conditions, the transport layer of the Integration Server does not properly handler error conditions and then might enter into an inconsistent state. This situation makes it possible for guaranteed documents in the outbound document store to be lost.
The transport layer now handles error conditions correctly, ensuring that guaranteed documents in the outbound document store are published to the Broker.
1-Q17DQ (IS_6-1_Fix17)
JSP tags provided by webMethods do not work as expected in the Eclipse IDE.
This fix updates the JSP tags so that the tags are parsed correctly within the Eclipse IDE.
1-TZI8J (IS_6-1_Fix62, IS_6-0-1_SP2_Fix153)
For FORM authentication, the WmTomcat package does not set the servlet session
with the correct user information.
In the cases where FORM authentication is used instead of HTTP authentication, WmTomcat does not set the correct user information in the servlet session.
With this fix, the WmTomcat package correctly handles FORM authentication by setting the correct user information in the servlet session.
1-S37K3 (IS_6-0-1_SP3_Fix1)
Add Oracle 9i RAC support for Integration Server 6.0.1 logging, PRT 6.0.1
logging, and Monitor 6.0.1 logging.
With this fix, Integration Server, PRT, and Monitor include the Data Direct Connect JDBC 3.3 Driver. This driver is required for Oracle 9i RAC support.
1-S31XR (IS_6-0-1_SP3_Fix3, IS_6-0-1_SP2_Fix170)
An exception is thrown when the Email listener tries to process an email that
has an attachment.
Fix IS_6-0-1_Fix145 added a Multipart Content Handler to handle multipart MIME messages; however, this fix inadvertently prevented the Email listener from processing emails that have attachments.
With this fix, the Email Listener works correctly with the new multipart Content Handler.
1-RWDU4 (IS_6-0-1_SP3_Fix3)
Integration Server appears to lock up when configuration property
watt.server.ldap.usersInGroups is set to ""true"".
When the configuration property watt.server.ldap.usersInGroups is set to ""true"", Integration Server generates an LDAP filter that is not supported by certain LDAP directories. This causes the user manager to sometimes report that users cannot be found, even though they are valid users.
With this fix, Integration Server generates the filter in compliance with the LDAP specification.
When using custom authentication modules, if the module is able to successfully authenticate a user name and password, but the user does not exist or the authentication manager cannot find the user, Integration Server might not respond to the client connection or it might close the connection. As a result, the client application to appears to hang until the connection times out.
With this fix, when the authentication manager cannot find a user, Integration Server displays an authentication challenge prompt.
1-QG7G9 (IS_6-0-1_SP3_Fix3)
When using Microsoft Active Directory, the Integration Server reports the
following error, "Failed to initialize LDAP module".
Previously, escape sequences in distinguished names would be re-escaped, causing lookups to fail. Now backslashes that are already part of escape sequences are recognized and are not re-escaped.
1-TE8SP (IS_6-0-1_SP3_Fix3)
Execution of the pub.soap.processor:registerProcessor built-in service results
in a service exception stating that there are illegal characters in the
directive name.
This error occurs when you include the dot (.) symbol in the directive name, for example, servlet.rpcrouter, when specifying the directive input parameter.
With this fix, the service allows the dot (.) character in the directive name.
1-TO6L6 (IS_6-0-1_SP3_Fix4)
The scheduler can become deadlocked under certain conditions.
It is possible for the scheduler to become deadlocked if the number of scheduler threads is low compared to the number of scheduled tasks. This happens due to a situation of one thread attempting to get a thread from the scheduler thread pool while another thread attempts to return a thread to the thread pool. The first thread holds a lock on an object that the second thread needs to acquire a thread. If there are currently no threads available, this will result in a deadlock condition.
This issue has been solved by introducing a timeout for the thread that attempts to obtain a thread from the thread pool.
1-TLOWQ (IS_6-0-1_SP3_Fix7)
References in decoded SOAP messages appear as NULL.
The SOAP message decoder is not properly handling SOAP messages that contain several references to the same multi-reference. In the resulting decoded document, every instance of the reference, except for the last instance, has a value of NULL. The last instance contains the correct value.
With this fix, SOAP messages that contain several references to a single multi-reference are decoded correctly.
1-TX91Q (IS_6-0-1_SP3_Fix7)
Integration Server issues an SSL "Handshake failure" if not receiving
"Client Hello" in 20 seconds.
The Integration waits for 20 seconds during an SSL handshake for a response from the client before timing out the attempt. It is possible that some clients may take longer than 20 to respond.
This fix adds the ability to configure this timeout value by setting the new property watt.net.ssl.server.clientHandshakeTimeout to the desired timeout in milliseconds. The default is 20000 milliseconds (20 seconds).
1-UO6KO (IS_6-0-1_SP3_Fix8)
A Repository Server that is running as an NT service can not be stopped
completely.
When stopping a Repository Server service, the Repository Server itself will stop, but the NT service will linger for 30 minutes.
With this fix, a Repository Server that is running as an NT service can be stopped completely.
When applying the fix, the classpath in IntegrationServer\reposerver\bin\repostore.bat will have to be modified to include the fix, as follows:
set REPOCLASSPATH="%JAVA_DIR%\LIB\RT.JAR;%IS_DIR%\updates\IS_6-0-1_SP3_Fix8.jar;%IS_DIR%\lib\client.jar;%IS_DIR%\lib\server.jar;%IS_DIR%\lib\mail.jar"
1-PZNAD (IS_6-0-1_SP3_Fix9, IS_6-0-1_SP1_Fix143)
In some situations the Integration Server appears to become unresponsive when
JDBC statements are not closed.
A thread dump indicates finalizer thread is waiting to acquire a lock in the finalizer for a class in the com.wm.dd.jdbc.base package. In some cases an OutOfMemoryError was thrown. This situation results from a combination of JDBC statements not being closed and the DataDirect finalizers for those statements requiring synchronization on a connection that is in use in another thread.
This fix resolves this issue by closing the result and statement before releasing the connection. This prevents the statement finalizer from synchronizing with the connection.
1-U26UZ (IS_6-0-1_SP3_Fix10)
Integration Server logs Access Denied error after successful login.
After invoking a service and supplying the correct login username and password, the Integration Server logs an "Access Denied" error in the error log, even though the login was successful.
With this fix, the Integration Server no longer logs an Access Denied error after a successful login.
1-UW7E3 (IS_6-0-1_SP3_Fix11)
When running a service in Developer, service results formatted in an output
template contain the entire pipeline instead of just the designated results.
When a service request with a Content-Type set to "text/xml" invokes a service that uses an output template to present service results, the resulting file contains the entire pipeline in addition to the data specified by the output template.
This issue is now resolved.
1-VAOJ0 (IS_6-0-1_SP3_Fix11)
Prefixes in XML Schema definitions generated from document types contain
invalid XML characters.
If a document type contains fields that uses illegal XML characters in the field name prefix, an XML Schema definition or WSDL document generated from the document type will contain illegal XML. That is, the xmlns declaration that the Integration Server creates for the prefix will contain illegal XML.
Now, before generating an xmlns declaration for the prefix, the Integration Server verifies that the prefix contains valid XML characters. If the prefix contains illegal XML, the Integration Server generates the following message:
[ISC.0124.9015] Document to XSD error: Field Prefix prefixName from field fieldName cannot be represented in XML Schema. The field prefix name does not conform to the XML NCName definition.
1-VF4QI (IS_6-0-1_SP3_Fix11)
Integration Server does not generate an error message when all the threads in
the scheduler thread pool are in use.
Now, the Integration Server writes the following error message to the server log at log level 2 to indicate that all the threads in the scheduler thread pool are in use:
[ISS.0069.0018] No threads available to run task taskName
As before, the scheduled task will wait for the next available thread.
This change requires IS 6.0.1 SP3 Fix 7.
1-JBFIB (IS_6-0-1_SP2_Fix118)
When JDBC connections encounter errors, the connection is not "destroyed",
creating resource problems on the system supporting the database.
This fix corrects the problem by destroying all discarded connections.
1-OLD8G (IS_6-0-1_SP2_Fix121)
Clearing state information for joins can delay Integration Server start up.
Because the Integration Server deletes state information for completed and expired joins during start up only, a large amount of join state information can cause the Integration Server to start up more slowly.
Now, the Integration Server periodically removes state information for completed and expired joins. The server parameter watt.server.dispatcher.join.reaperDelay determines how frequently (in milliseconds) the Integration Server removes join state information. The default is 1800000 milliseconds (30 minutes)
1-NOYFZ (IS_6-0-1_SP2_Fix122)
Integration Server accepts ""{crypt}"" but not
""{CRYPT}"" as a valid prefix during password
authentication.
When authenticating passwords that are stored in an LDAP server using the ""crypt"" algorithm, the Integration Server accepts ""{crypt}"" but not ""{CRYPT}"" as a valid prefix for the passwords. With this fix, the Integration Server will not consider case when validating the prefix.
1-OP84E (IS_6-0-1_SP2_Fix123)
Editing scheduled tasks in the Integration Server Administrator can cause task
input values to be lost.
When editing a scheduled task using the Integration Server Administrator, input values for the scheduled task were sometimes lost. With this fix, the Integration Server preserves input values when the scheduled task is edited using the Integration Server Administrator.
1-OP5HA (IS_6-0-1_SP2_Fix124)
During startup, Integration Server deletes files in
the Completion&Error directory for the file polling port.
This fix adds a new option to the file polling port configuration page to specify whether files in this directory should be deleted at startup.
1-N14LX (IS_6-0-1_SP2_Fix124)
Disabling a file polling listener does not stop all listener threads.
When the file polling listener is re-enabled, the actual number of invocation threads is twice the number specified for the port. This is of special concern when the number of invocation threads is set to one to ensure serial processing of files by the file polling listener.
This fix properly shuts down all file polling listener invocation threads, so that when the listener is re-enabled, only the specified number of invocation threads are active.
1-OOZFL (IS_6-0-1_Fix125)
The ftp services pub.client.ftp:get and pub.client.ftp:mget will sometimes
throw NullPointerExceptions.
If the services pub.client.ftp:get or pub.client.ftp:mget fail (for example, if the remote files do not have proper permissions), the next time these services are run in the same session, a null pointer exception will be thrown.
With this fix, the second operation will no longer throw the null pointer exception.
1-HAG99 (IS_6-0-1_Fix125)
Failed file transfers using put, mput, and append services of pub.client.ftp
may cause local file permissions to change to read-only.
If an error occurs on the remote server during a file transfer, the permissions for the local file may change to read-only. Now this works correctly.
1-OWPBT (IS_6-0-1_SP2_Fix128)
With fix IS_6-0-1_SP2_Fix107 installed, the pub.flatFile:convertToValues
service does not include record delimiters
in the undefined data results.
This fix alters the pub.flatFile:convertToValues service so it includes the record delimiters."
1-PBKNX (IS_6-0-1_SP2_Fix130)
Error occurs when publishing a document with a field that has a datetime constraint.
This fix resolves a situation in which Integration Server throws an exception when it attempts to publish a document that contains a field with a datetime constraint and the field is set to null.
1-P6VSR (IS_6-0-1_SP2_Fix133)
For complex tasks, the public service scheduler:getTaskInfo does not return the
correct nextRun value.
With this fix, the nextRun value is updated as expected.
1-OSSG2 (IS_6-0-1_SP2_Fix133)
In Trading Networks, JDBC threads sometimes get deadlocked.
In Trading Networks, multiple calls to releaseConnection() to release the same connection cause a deadlock in the JDBC connection pool.
With this fix, subsequent calls to releaseConnection() are ignored.
1-PWO2B (IS_6-0-1_SP2_Fix133)
Guaranteed Delivery will sometimes become disabled.
Previously an exception from any Guaranteed Delivery job request would disable further Guaranteed Delivery processing. This change keeps Guaranteed Delivery processing enabled, but instead fails the job in question.
1-Q7H5B (IS_6-0-1_SP2_Fix142, IS_6-0-1_SP1_Fix141)
Two issues occur on the internal server in a Reverse Invoke configuration.
Issue 1: Integration Server Administrator sometimes displays an incomplete Security>Ports>Reverse Invoke>Internal Server page.
This problem is caused by the wm.server.security.revInvoke:listRegisteredConnections service throwing null pointer exceptions when all registration connections and the alias for the proxy server have been deleted from the internal server.
With this fix, the service no longer throws null pointer exceptions in this situation and the complete page is displayed.
Issue 2: Integration Server ignores requests to delete a registered connection.
With this fix, Integration Server deletes the registered connection when requested.
1-Q6P4W (IS_6-0-1_SP2_Fix145)
If there is an error in a transformer, the service pub.flow:getLastError may
incorrectly return a null when it should return a lastError object.
This happens if there is a multiple transformation in a MAP step and a one of the transformations before the last transformation raises an error. Subsequent transformations which complete successfully clear this error which causes the pub.flow:getLastError service to incorrectly return null.
1-QCKET (IS_6-0-1_SP2_Fix145)
The contents of an email without attachments cannot be passed to a service.
This behavior occurs because the email listener expects the body of the email to contain the URL-encoded parameters for a service.
With this fix, an administrator can now use the setup page for the email listener to configure the listener to accept the contents of an email "as is" and pass them to a service or content handler.
1-Q62T2 (IS_6-0-1_SP2_Fix145)
Connections to a remote server sometimes close when using the pub.client:http service.
This problem occurs when a header is set to null when using this service. The null header prevents valid headers from being sent to a remote server. Instead, just the body of the HTTP message is sent. This usually causes the remote server to close the connection.
With this fix, null header values are skipped and the other valid headers are sent to the remote service as expected.
1-NV9L6 (IS_6-0-1_SP2_Fix145, IS_6-0-1_SP2_Fix133)
webMethods Repository Server does not reconnect to a database.
This problem is due to a String encoding bug in JVMs prior to 1.4.
This fix works around this JVM problem and the Repository Server reconnects to the database as expected.
1-P7RCZ (IS_6-0-1_SP2_Fix145, IS_4-6_Fix177)
Problems occur while running multiple webMethods-supplied packages on the same
Integration Server.
This problem occurs because some packages were shipped with their own content handler for multipart MIME messages. This caused problems when running more than one of these packages on the same Integration Server.
With this fix, Integration Server provides a generic content handler and factory where each adapter can register its own coder for multipart MIME messages.
1-QJKXQ (IS_6-0-1_SP2_Fix146)
If the ACL settings are changed on an adapter service, the changes are lost if
Integration Server is restarted.
The default ACL setting for an adapter service is "Default <inherited>". When any ACL setting is changed on the adapter service and the containing package is reloaded or Integration Server is restarted, every ACL setting will revert to "Default <inherited>".
With this fix, Integration Server maintains ACL settings when Integration Server is restarted and when packages are reloaded.
1-S240Q (IS_6-0-1_SP2_Fix149)
wm.b2b.edi.util:formatTime4_4 is not working properly.
This fix addresses a situation in which the parser did not report error messages based on original badData.
1-QY2YO (IS_6-0-1_SP2_Fix150)
The pub.flow:getLastError service does not report service errors that
are caused by access errors.
If a user without execute privileges attempts to invoke a service, then the pub.flow:getLastError service does not report any errors. Also, the output of the pub.flow:getLastError service will be empty.
This fix corrects the pub.flow:getLastError service so that it reports all execute access errors.
1-R1F6R (IS_6-0-1_SP2_Fix150)
The pub.io:mark, pub.io:read, pub.io:reset services do not correctly read a
stream.
The BoundedInputStream generated for an HTTP request did not correctly support the mark and reset APIs, which caused the stream to be truncated when read after a call to reset.
This fix allows the Integration Server to correctly read the stream after the stream is marked and reset.
1-R853H (IS_6-0-1_SP2_Fix150)
Integration Server cannot clear certain parameters that belong to the
pub.client:smtp service once they are set.
If certain parameters in the pub.client:smtp service are set on one invocation and not set on a second invocation, the parameter values set by the first invocation are used. These parameters include mailhost, mailhostPort, and auth. The only way to clear these values is to restart Integration Server.
With this fix, the values of the mailhost, mailhostPort, and auth parameters are no longer cached by the pub.client:smtp service.
1-RM4NZ (IS_6-0-1_SP2_Fix150)
When generating a WSDL document for a service that contains complex types in
the output signature and an empty input signature, the target namespace is
omitted from the generated WSDL document.
This fix corrects the problem.
1-Q6NX2 (IS_6-0-1_SP2_Fix152)
Trigger processing mode is out of sync with the Shared Document Order mode of
the corresponding Broker client.
Under exceptional conditions, the document processing mode for a trigger (serial or concurrent) can get out of sync with the Shared Document Order mode for the corresponding Broker client (Publisher or None).
This fix detects this problem by providing a check that compares the modes whenever a trigger is saved. If the modes are out of sync, Integration Server issues a journal log message.
To synchronize the document processing mode and the Shared Document Order mode, change the document processing mode of the trigger and save the trigger while the Broker is connected. Then, change the document processing mode of the trigger back to the original value and save the change. For example, if the trigger uses a document processing mode of "serial," change the document processing mode to "concurrent" and save the change. Then, change the document processing mode back to "serial" and save the change. Note that if you change the document processing mode when the Broker is disconnected, the modes will remain out of sync.
1-QLS91 (IS_6-0-1_SP2_Fix156)
Some binary fields in SOAP messages and attachments to SOAP messages are
improperly decoded. Specifically, some bytes are decoded to 63 (the '?' character).
With this fix, binary fields in SOAP messages are properly decoded.
1-RRC9N (IS_6-0-1_SP2_Fix156)
Integration Server mistakenly creates a session and returns a session cookie
for a stateless service.
This fix resolves an issue the Integration Server created a session and returned a session cookie for a failed, stateless service.
1-RX6AZ (IS_6-0-1_SP2_Fix157)
The release character is not properly escaped when calling the service
pub.flatFile:convertToString.
If a field contains a release character that character should be replaced by two release characters. This does not occur unless the field contains another character that must be escaped, i.e. a delimiter character.
This fix modifies the service pub.flatFile:convertToString so that fields containing a release character and without any delimiter characters are escaped properly.
1-Q03S9 (IS_6-0-1_SP2_Fix159)
Various SOAP error messages received when Web services execute.
Due to thread safety issues, the execution of Web services that use namespaces and run on multi-processor machines sometimes results in SOAP error messages.
This fix corrects the problem.
1-QOHRT (IS_6-0-1_SP2_Fix159)
Errors sometimes occur when a Web service is invoked while Integrated Windows
Authentication (NT Challenge Response) is enabled.
The NTLM Challenge-Response protocol requires that multiple messages be exchanged, but the Integration Server prevents this because it treats multiple 'Content-Length' entries as duplicates and rejects them.
This fix corrects the problem.
1-RNX85 (IS_6-0-1_SP2_Fix159)
NullPointerException occurs when running a WmDB transaction as a scheduled
service.
Transactions in the WmDB package are prone to failure when started by scheduled services. A scheduled service is removed after 10 minutes and the connection associated with it is destroyed.
This fix addresses the problem by creating scheduled services that can execute for as long as 24 days.
1-RYRM2 (IS_6-0-1_SP2_Fix159)
Web service connectors return the SOAP fault "this is a document/literal
endpoint" and can experience interoperability problems.
This problem occurs because, by default, all SOAP envelopes generated by Integration Server have the following attribute and value:
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
This fix removes the attribute from SOAP envelopes for SOAP doc/literal encoding.
1-S0PEG (IS_6-0-1_SP2_Fix159)
NullPointerExceptions sometimes occur during execution of the
pub.clien.ftp:login service.
When an error occurs during an FTP operation, sometimes Integration Server does not properly delete the FTP session. In subsequent attempts to perform an FTP operation to the same FTP server with the same user and from within the same object, Integration Server will attempt to use that session. If the session is in an unusable state, the FTP operation fails and an error is issued.
This fix improves FTP session management by providing an idle timeout setting for the FTP session. When a session times out, Integration Server removes it from memory. The default idle timeout is 10 minutes. You can change this value by using the property watt.net.ft.
1-S4PC2 (IS_6-0-1_SP2_Fix159)
Java services do not compile if Integration Server uses classes in a dependent
package.
When using Developer, Java services do not compile if the service uses classes in another package. This occurs because the dependent package is not added to the classpath that the compiler uses to search for classes. This fix solves this issue by updating the Java service compiler to include dependent packages in the classpath when compiling packages.
1-S84RC (IS_6-0-1_SP2_Fix159)
Improperly generated SOAP responses sometimes cause interoperability problems.
The encoding type information that the Integration Server provides by default in RPC-encoded messages can lead to encoding type mismatches.
This fix provides a configuration property that allows you to suppress the encoding type information:
watt.server.SOAP.encodeXSIType=false
1-RLPJD (IS_6-0-1_SP2_Fix162)
Integration Server sends the wrong cookie when two Integration Servers have the
same host name.
When an Integration Server sends SOAP RPC or HTTP requests to two different Integration Servers located on the same host, the requesting Integration Server sends both servers the cookie for the first Integration Server. This causes an access denied error for the second server because it receives the wrong cookie.
This fix ensures that the requesting Integration Server sends the correct cookies by matching cookies to port numbers and URLs.
1-S2K9G (IS_6-0-1_SP2_Fix162)
Join Manager takes a long time to initialize when Integration Server starts.
During startup of Integration Server, the Join Manager examines the join entries in the repository and then removes expired join entries. Previously, the Join Manager did not examine and remove join entries with a status of 0 (zero). The time needed to initialize the Join Manager increased as the number of entries with a status of 0 (zero) increased.
This fix ensures that the Join Manager examines and removes expired join entries with a status or 0 (zero).
Note: After installing this fix, you need to restart the Integration Server twice to recognize an improvement in the Join Manager's initialization time. This is because the removal of expired join entries from the repository is a two-stage process.
1-S30GX (IS_6-0-1_SP2_Fix162)
Multiple invocations of a stateless service require that credentials be input
for each invocation.
Credentials are not being cached and reused for stateless services. Specifically, when a service is invoked, a client may cache both authorization and session information. If the service is stateless, the Integration Server discards its session information when the service completes. However, the Integration Server does not ask the client to discard its session cookie. Consequently, if the client submits the now stale cookie with a subsequent request, the Integration Server rejects the request because the Integration Server considers it an attempt to use an invalid session.
With this fix, the Integration Server asks the client to discard its session cookie at the same time the Integration Server discards its own session. This allows cached credentials to be used in subsequent calls, even to stateless services.
1-SW10E (IS_6-0-1_SP2_Fix163)
In 6.0.1, the wm.b2b.edi:convertToString service in the WmEDI package and the
pub.flatFile:convertToString service in the WmFlatFile package require the
input document to match the structure of the document type exactly as it is
created by a flat file schema.
Fields defined with Nth position extractors must be present in the document as strings with their name equal to the field name. ID Node Extractors must be present as documents with the same name as the field that contains a string with the name 'code'.
In 4.6, the convertToString service accepts either format, regardless of the type of field defined. Therefore, a field can be either a string or document that contains a string with the name 'code'.
This fix provides a flag that will modify the behavior of the wm.b2b.edi:convertToString and pub.flatFile:convertToString services such that it accepts either field structure. This is the same behavior as in version 4.6.
1-TPAW1 (IS_6-0-1_SP2_Fix166)
A problem occurs when any ART-based listener notifications are shut down while
the associated listener is active.
In this scenario, during the listener notification shutdown sequence, the notification uses the same connection that is in use by the active listener, causing transactional corruption that can result in data loss.
1-TRSZ2 (IS_6-0-1_SP2_Fix166)
ART commits listener messages that are not processed.
If no notification processes the data returned by an ART listener, the default behavior is to commit the transaction. In a shutdown scenario, notifications may be shut down while the listener is reading data. If no notification is available to process the data, the read-portion of the transaction is still committed. This results in data loss.
This fix corrects the problem by changing the default behavior to roll back the transaction if listener data is not handled by a notification.
1-TB7N1 (IS_6-0-1_SP2_Fix169)
Added configuration option to FTP Listener to specify address to send in PORT
command to FTP client.
When running in passive mode, the FTP Listener sends a PORT command to the FTP client which specifies the address and port the client should connect to so as to create the data connection. If the FTP Listener is behind a NAT server, then this will not work since the address of the host that the Integration Server is running on is not visible to the FTP client.
This fix adds the property watt.net.ftpPassiveLocalAddr which may be used to specify the address that should be sent by the PORT command instead of the internal address. This may be specified as either a host name or an IP address. In addition, the passive mode address can also be set on a per FTP Listener basis from the FTP Listener setup page. The watt.net.ftpPassiveLocalAddr property will used if the address is set by both methods.
1-QDPJZ (IS_6-0-1_SP1_Fix147)
HTTP requests to a Tomcat page do not allow lowercase HTTP headers, such as
+ACI-host+ACI- instead of +ACI-Host+ACI-.
With this fix, header parsing is now case insensitive.
1-QVLFG (IS_6-0-1_SP1_Fix147)
Flat file port that uses one thread processes files out of sequence.
If a flat file port uses a single thread, the port processes files in sequential order based on the file’s time stamp.
1-QT1JN (IS_6-0-1_SP1_Fix148)
With Java versions prior to 1.4, if security provider libraries existing
in JAVA_HOME/jre/lib/ext
(such as jce1_2_2.jar and sunjce_provider.jar), the result is an class cast
exception of iaik.asn1.structures.Name during startup.
The code has been changed so that if the property “watt.server.reorderSecurityProviders” is set to true, the security providers are reordered, and the Java random number generator is used instead of that from the IAIK package.
1-NXHHQ (IS_6-0-1_Fix134)
Invoking a remote service leaves a socket in CLOSE_WAIT.
When calling a Web service through a Web service connector, the socket that was used to connect to the remote server is left in a CLOSE_WAIT state, which means that it was not closed.
With this fix the socket is now closed.
1-RD5W4 (IS_6-0-1_Fix154, IS_4-6_SP2_Fix191)
Integration Server and Developer throw errors when loading an XML Schema file
(XSD) using constraining facet restrictions.
Errors with codes [B2BCORE.0082.9712], [B2BCORE.0082.9485] are displayed, when using schemas with facet restrictions.
With this fix, Integration Server and Developer allow facet usage in XML Schemas.
1-U8CK1 (IS_6-0-1_Fix172)
Integration Server does not respond to shutdown requests from the Integration
Server Administrator.
After applying IS_6-0-1_Fix88, IS_6-0-1_Fix101, or IS_6-0-1_SP3, an Integration Server that was started as an NT service does not respond to shutdown requests from the Integration Server Administrator.
With this fix, an Integration Server started as an NT service properly responds to shutdown requests from the Integration Server Administrator.
1-STM5Y (IS_4-6_SP3_Fix1)
Integration Server does not honor value of watt.server.stats.pollTime
parameter.
With this fix, the Integration Server honors the value of the watt.server.stats.pollTime. This server parameter specifies the number of seconds between updates of the statistics log. The default is 60 seconds. The Integration Server must be restarted for changes to this parameter to take effect.
1-T6IV4 (IS_4-6_SP3_Fix1)
ArrayStoreException thrown during SOAP requests.
The Integration Server throws an ArrayStoreException when a SOAP request specifies an array data type, but does not specify a data type for the array’s children.
With this fix, the Integration Server sets the children's data types to be that same as the parent’s and the exception is no longer thrown.
1-T8FGN (IS_4-6_SP3_Fix1)
Enhancements to LDAP functionality.
This fix addresses the following issues related to LDAP: Issue 1: Integration Server cannot handle an LDAP user that contains a slash in its distinguished name.
With this fix, these users are handled properly.
Issue 2: When using Microsoft Active Directory, the Integration Server reports the following error, "Failed to initialize LDAP module".
Previously, escape sequences in distinguished names would be re-escaped, causing lookups to fail. Now backslashes that are already part of escape sequences are recognized and are not re-escaped.
1-UP0T8 (IS_4-6_SP3_Fix2, IS_4-6_SP2_Fix197)
A job does not run at its scheduled time, and then runs twice at its next
scheduled time.
This problem occurs because of a problem in the job scheduler’s logic.
This fix corrects the problem.
1-N555L (IS_4-6_SP2_Fix169)
Under certain circumstances, Integration Server can produce errors such
as:
SSLv3 padding length error: 123, Error: state not hs_change_cipherspec, and Bad Record MAC.
Errors such as this usually occurred under conditions where a client would try to resume an SSL session that had already expired on the server. This problem has been fixed.
The Integration Server can, under certain conditions, produce errors such as SSLv3 padding length error: 123, Error: state not hs_change_cipherspec, and Bad Record MAC. These errors were difficult to reproduce but usually occurred under conditions that allowed the situation to arise where a client would try to resume an SSL session that had already expired on the server.
1-O99VZ (IS_4-6_SP2_Fix170)
In a Reverse Invoke environment, the Internal Server is unable to
retrieve "HTTP request URL" information using the
pub.flow:getTransportInfo service.
This fix corrects the problem.
1-N6U1Z (IS_4-6_SP2_Fix172)
The pub.client:ftp service returns the incorrect result code.
The pub.client:ftp public service returns the incorrect result code from the remote FTP server when you invoke the pub.client:ftp service with the "transfertype" input variable set to "passive".
With this fix, the pub.client:ftp service returns the correct code.
1-OLJAZ (IS_4-6_SP2_Fix175)
SOAP directives sent through the Reverse Invoke Proxy Server no longer work.
Fix IS_4-6_SP2_Fix136 unintentionally blocks SOAP directives on the reverse invoke proxy server.
With this fix, SOAP directives are no longer blocked.
1-HUUZF (IS_4-6_SP2_Fix175)
There is no way to prevent access to DSP pages and other HTTP directives on the
Reverse Invoke Proxy Server. As a result, unauthorized requests are passed to
the internal server for security checks.
This fix provides the following configuration property to control which proxy ports are allowed to use HTTP invocation:
watt.server.revInvoke.allowDirective
Specify a list of proxy ports (separated by commas) that should only be allowed to use HTTP invocations. All other proxy ports will continue to allow any type of service, including DSP pages.
The Integration Server configuration file resides in <IntegrationServer_directory>/config/server.cnf file.
1-NOCX9 (IS_4-6_SP2_Fix179)
In a Reverse Invoke environment, the Internal Server is unable to retrieve
"HTTP request URL" and "HTTP request query" information
using the pub.flow:getTransportInfo service.
This fix corrects the problem.
1-O9DJI (IS_4-6_SP2_Fix179)
During startup, if the Integration Server detects errors with its configuration
directory, it does not log information about the problem.
During server startup, the server logs no messages about the files in the server’s configuration directory. If any of the files in this directory become corrupted or contain zero (0) bytes, the Integration Server exits without any information.
With this fix applied, the server logs a message about the problem before exiting.
1-KICC0 (IS_4-6_SP2_Fix179)
An ArrayIndexOutOfBoundsException is thrown when invoking the pub.web:recordToDocument
service.
This exception occurs when Integration Server receives multiple documents that are to be processed similarly and arrive at the same time. A race condition occurs when multiple threads hit a common method that initialized a structure.
To resolve this issue, the method has been moved to a static block.
1-RD5WS (IS_4-6_SP2_Fix184)
A cluster session does not contain correct group membership information for the session
user.
In a cluster, a session shared between cluster servers does not contain the correct group membership information for the session user. When this occurs, the session user will be wrongly denied access to resources to which the session user should have access.
Now, the session user will contain the correct group membership information.
1-S1WA9 (IS_4-6_SP2_Fix184)
Various SOAP error messages received when Web services run.
Due to thread safety issues, Web services running on multi-processor machines sometimes experience namespace problems that result in SOAP error messages. This issue may also occur during package replication or loading if the package contains services that use universal names.
This fix corrects the problem.
1-RLNKK (IS_4-6_SP2_Fix188)
Integration Server issues an SSL "Handshake failure" if it does not
receive a "Client Hello" in 20 seconds.
During an SSL handshake, the Integration Server waits 20 seconds for a response from the client before timing out the attempt. Some clients may take longer than 20 seconds to respond.
This fix provides a new server parameter, named watt.net.ssl.server.clientHandshakeTimeout, which specifies the timeout value in milliseconds. The default is 20000 milliseconds (20 seconds).
1-LTRA7 (IS_4-6_SP2_Fix189)
When reloading packages with Integration Server Administrator, if the
same package is reloaded rapidly multiple times, the package can become
corrupted. The corruption may include loss of data and services.
This fix corrects the problem by blocking any reload request for a package if the package is already being reloaded.
1-S0MJW (IS_4-6_SP2_Fix190)
The service pub.list:sizeOfList returns the value in a locale specific format (e.g.
1,234 instead of raw data 1234).
With this fix, the pub.list:sizeOfList service returns unformatted raw data.
1-STM5Y (IS_4-6_SP2_Fix190)
Integration Server does not honor value of watt.server.stats.pollTime
parameter.
With this fix, the Integration Server honors the value of the watt.server.stats.pollTime. This server parameter specifies the number of seconds between updates of the statistics log. The default is 60 seconds. The Integration Server must be restarted for changes to this parameter to take effect.
1-OH2OZ (IS_4-6_Fix173)
The wm.server.ns.syncToNamespace service throws a NullPointerException during
Integration Server startup.
With this fix, the service no longer throws a NullPointerException and the Integration Server starts successfully.
1-OQFBW (IS_4-6_Fix176)
Editing scheduled tasks in Integration Server Administrator can cause task
input values to be lost.
When an administrator edits a schedule task, input values for the scheduled task are sometimes lost.
With this fix, Integration Server preserves input values when the scheduled task is edited using Integration Server Administrator.
1-PMEOX (IS_4-6_Fix178)
HTTP client request for a specific session fails if that session has already
timed out.
If an HTTP request does not specify a session ID in its Cookie header, when a non-stateless service is invoked, a session is created. If subsequent requests specify this session in the HTTP request, the session is reused.
However, if HTTP requests are made to this session after the session expires, the target Integration Server returns a message to the client Integration Server with an HTTP status code of 401 and indicates that the requested session has expired. In response, the client Integration Server should resubmit the request with the required authentication. However, the client Integration Server fails to do so.
With this fix, the client Integration Server resubmits the HTTP request with the required authentication.
1-OH655 (IS_4-6_Fix178)
The Integration Server cannot authenticate to a Microsoft Proxy 2.0 server when
making HTTPS requests.
This problem occurs because the Integration Server does not support authentication to a Microsoft Proxy 2.0 server when requesting Web resources using HTTPS.
This fix adds this support.
1-PRUUT (IS_4-6_Fix181)
Integration Server throws Null Pointer Exceptions multiple times during server
startup.
While trying to load .access files during server startup, the Integration Server sometimes throws Null Pointer Exceptions.
This fix corrects the problem.
1-Q8RQM (IS_4-6_Fix185)
MIME service does not parse S/MIME data correctly.
The pub.mime:createMimeData service cannot parse S/MIME data and throws an exception if it receives a MIME stream that contains one or more S/MIME body parts and the MIME stream is not a multi-part S/MIME message.
With this fix, the service correctly parses the S/MIME data.
1-QEVGQ (IS_4-6_Fix186)
Problems occur with scheduled tasks running in a cluster.
Scheduled tasks that are marked as Run from End will become active again if they are canceled while they are running. In addition, these tasks can overlap execution on different Integration Servers in the cluster.
This fix corrects these problems.
In addition to the webMethods Manager fixes included in Integration Server 6.1 Service Pack 1, webMethods Integration Server 6.5 includes the following webMethods Manager fixes that were made available since the last release.
1-TMZR1 (Manager_6-1-5_Fix3)
When managed Integration Servers were restarted several times quickly, Manager
Server reported a Failed ObjectStatus for several MBeans created for those
Integration Servers, even when the Servers were again fully operational. This
caused Manager Server and Manager Console to become out of sync. As a result,
Manager Console reported an incorrect status for the Integration Servers and
rules associated with those Servers remained violated.
Now, the MBeans automatically resynchronize, enabling Manager Console to display the correct status for the Integration Servers.
1-UMY4L (Manager_6-1-5_Fix5,
Manager_6-1_Fix13, Manager_6-0-1_Fix23)
By default, Manager Server manages all Integration Server services. Instead,
Manager Server should not manage any Integration Server services and allow
users to select the services they want to manage. In addition, users should be
able to change the default behavior.
This fix changes the default behavior for managing Integration Server services. With this fix, Manager Server does not manage any services. Users can select the services they want to manage on the Integration Server Service Filter page in the Manager Server. For more information about service filtering, see the webMethods Manager Server Administrator's Guide.
This fix also introduces a new service located in the WmOmiIs package, omi.wm.is.filter:setServiceEnableProperty. This service allows users to change the default service filtering behavior. To have Manager Server manage all Integration Server services by default, set the serviceEnabled input parameter for this service to True. (The default is False.) One way to set this service input parameter is to test the service using Integration Server Administrator. For more information about testing services using Integration Server Administrator, see the webMethods Integration Server Administrator's Guide.
Note: This setting changes only the default service filtering behavior for newly deployed packages from this point forward. You need to restart Manager Server for this change to take effect.
For detailed information about these fixes and service packs for webMethods Integration Server, see the Knowledge Base on the webMethods Advantage Web site.
The issues listed below have been resolved in webMethods Integration Server 6.5 but were not previously released in any fixes or service packs.
1-52GZD
LDAP and
The columns in Japanese versions of the LDAP and
With this update, these pages are fully localized to Japanese and the columns appear in Japanese.
1-7UB1T
The pub.client.ftp:quit service sends a lowercase
'quit' to the FTP server.
Depending on the FTP server, sending a lowercase ‘quit’ command may cause a 500 - Syntax Error.
In accordance with the official specification of the File Transfer Protocol (rfc-959), the pub.client.ftp:quit service now sends an uppercase ‘QUIT’ command to the FTP server.
1-AG249
Changing the date format for log files does not affect
the Error Log or Audit Log.
Changing the date format for log files alters the Server Log settings but has no effect on the Error Log or Audit Log.
With this update, the Integration Server correctly alters the date format in the Error Log, Audit Log, and Server Log.
1-JLT8I
The built in services pub.client:ftp and
pub.client.ftp:login ignore the value set in the encoding input parameter.
With this update, if the encoding input parameter is set, the services will use the value as the encoding method for the FTP sessions they create.
1-JZMW2, 1-OF41J
Execution of links between nested document lists does not work predictably if
those links use variable substitution with array indexing.
With this update, variable substitution works correctly when used with array indexing for links between nested fields.
1-K7NIX
HTTPS listener does not support IP address restrictions.
All built-in listeners except for the HTTPS listener honor the global IP address restrictions.
With this update, the HTTPS listener honors the global IP address restrictions.
1-KNDCG
The pub.mime:getEnvelopeStream MIME service
incorrectly sets the name of the header MIME-Version.
The service pub.mime:getEnvelopeStream sets the name of the required MIME header with the wrong case. That is, the name should be "MIME-Version" but the service sets it to "Mime-Version”. The MIME rfc states that this header must be "MIME-Version".
With this update, pub.mime:getEnvelopeStream sets the name of the required MIME header to the correct string, "MIME-Version".
1-MWKQZ
Flow services with a read-only node.ndf file are not considered System Locked.
If a flow service’s flow.xml file is read-only, the flow is considered System Locked. However, if the node.ndf is read-only, it is not considered System Locked.
With this update, the Integration Server takes both files into account when assessing the System Locked flag.
1-MWKUI
A Java Service is not considered System Locked when the associated .java file
is read-only.
The Integration Server does not consider a Java file to be System Locked even though its associated .java file is read-only. As a result, the Integration Server allows you to make changes to the Java file, but when you try to save the changes, you get an error.
With this update, the Integration Server considers a Java file with a read-only .java file to be System Locked and does not allow you to edit it.
1-MZCM0
User receives no error message when installing an Integration Server package
whose dependencies are not met.
When a user installs a package, for example package A, which depends on package B, and package B does not exist on the Integration Server, the user does not receive an error message. Instead, the user sees "Package installed and activated". The Integration Server does not enable the package and writes a message to the server log stating that the package could not be enabled.
With this update, if a package is not enabled because package dependencies are not met, the Integration Server alerts the user.
1-MZOO1
Integration Server intermittently issues “Transaction is active” errors.
If a flow service completes without closing a user-managed transaction, the transaction can remain open and corrupt the server thread pool. When this happens, the Integration Server intermittently issues “Transaction is active" errors.
With this update, the Integration Server avoids the problem by rolling back any open, user-managed transactions before returning the thread to the server thread pool.
1-N09WW
Published guaranteed documents are lost when the connection to Broker is
unavailable.
When Integration Server connects to a cluster of Broker servers (using the watt.server.broker.producer.multiclient property) and the connected Broker server fails over, Integration Server does not release connections to the failed node correctly. Although it appears that Integration Server establishes a connection to a new Broker server, the old connections remain and do not switch over to the new Broker server. Consequently, when Integration Server publishes documents to the Broker via the old connection, documents are lost and not stored in the outbound document store.
With this update, Integration Server now releases the old connections successfully.
1-N819V
Fields on the Security > Access Control Lists screen are too narrow to
display the names of some of the groups in an ACL.
Fields on the Security > Access Control Lists screen are too narrow to display the names of some of the groups in an ACL, no matter how wide the browser window is.
With this update, the ACL fields now resize with the browser window, using as much space as is available.
1-NW12H
A replying service fails after executing the pub.publish:reply
service.
In a local publish-and-wait scenario, the replying service fails after executing the pub.publish:reply service if no trigger subscribes to the reply document.
With this update, the replying service continues executing regardless of whether a trigger subscribes to the reply document.
1-NWVJ1
The Edit Notification Order screen displays instead of the View Notification
Order screen when the user clicks the View Notification Order link from the
View Listener screen.
With this update, the View Notification Order screen displays when the user clicks the View Notification Order link.
1-O03G3
Integration Server does not start if an invalid date format such as
"ABCDEF" is specified for the log timestamp format.
With this update, Integration Server now ignores the invalid value and starts with the default system value.
1-O284A
Root and Current context IDs do not match across Start, End, and Expire within
the same Session Log.
Root and Current context IDs do not match across Start, End, and Expire within the same Session Log. As a result, the sessions cannot be correlated to any specific Start, End, or Expire activity and there is no way to track the life cycle of a session.
With this update, the Session IDs match across Start, End, and Expire within the same session.
1-O2J2Y
Namespace association is not updated when you change a synchronous listener
notification.
If you change a synchronous listener notification to reference a flow service other than the one used when the notification was created, the Integration Server does not update the namespace association. The namespace association is shown in "find references" and "find dependents."
With this update, the Integration Server makes the correct associations.
1-O50CR
The “errors” output parameter for the pub.schema:createXSD
service is not marked as conditional.
The “errors” output parameter for the pub.schema:createXSD service is not marked as conditional. It is possible to create XSDs without warnings or errors; therefore, the "errors" output parameter should be marked as conditional.
With this update, both the "warnings" and "errors" output parameters are now marked conditional.
1-O7UUP
The "account" output parameter of the pub.client.ftp:sessioninfo service is required, but it should be optional.
With this update, the "account" output parameter is optional.
1-O7UX6
The pub.client.ftp:sessioninfo service does not return
a dataport value.
With this update, the pub.client.ftp.sessionInfo service returns the dataport value. If the dataport value is specified at login, the sessionInfo Service returns the same dataport value, otherwise the service returns 0.
1-O8IVP
Remove the ability to perform multiple callbacks for polling notification.
This update removes the ability for polling notification callbacks in overlap mode to be called multiple times.
1-OA9GD
The Last Request column in the Server > Statistics > Sessions panel is
incorrectly labeled "Milisec."
The Last Request column in labeled “Milisec” but should be “Sec” instead.
With this update, the column is labeled “Sec.”
1-OC0SR
Part of the status message displayed on the Security > Ports > Change
Global IP Access Restrictions page is not localized.
When you select “Add a Host to the Allow/Deny List” from the Security > Ports > Change Global IP Access Restrictions page, the strings "Allow" and "Deny" in the status message are not translated into the local language.
With this update, these words are localized.
1-OXIGP
WebSphere MQ Adapter listeners running on non-transactional connections
sometimes receive the following error: "[ART.117.4036] Adapter Runtime
(Adapter Service): Unable to rollback transaction. Transaction state:
Transaction is active."
This error occurs because connection pools used by the listeners are also used by other nodes. Listener nodes use internal connection pool configurations that make that connection pool incompatible with other node types (such as Adapter Service and Polling Notification).
This update adds checks to prevent nodes from being created or updated in a way that will cause transaction errors. Additional checks at runtime prevent adapter services from being invoked or Polling Notifications from starting with a connection that is associated with a registered listener. Similarly, listeners cannot be started using a connection that is associated with a registered adapter service or Polling Notification.
1-OZCQ9
The extended status containing schedule and/or cluster
settings is lost.
The extended status containing the schedule and/or cluster settings is lost in a copied or renamed polling notification.
With this update, the extended status is retained.
1-PAPX9
Error log contains “method not found” errors.
Integration Server writes misleading "method not found" errors to the error log when Developer is used to browse built-in Java services from packages such as WmEDI, WmEDIforTN, and WmFlatFile.
With this update, Integration Server no longer writes misleading "method not found" errors to the error log file.
1-PHY27
Errors such as "Could not import java.util.*" or
"java.lang.Object not found" are issued by the server.sh file.
The server.sh file checks that the dt.jar file is executable, but does not check that the file exists. This causes errors in some configurations on AIX.
The code has been changed to include both checks.
1-PLU2D
Use of the watt.server.broker.producer.multiclient property can cause documents
to build up on Broker.
If there is an error, the subscriber is supposed to deliver an Adapter::error back to the client that published the event. However, the XXXX_DefaultClient_MultiPub service is not retrieving documents from the Broker. As a result, documents build up in the queues of these MultiPub clients.
With this update, by default, the Envelope property "errorsTo" is now set to the default client. This causes the error documents to be sent through to the default client, which will either engage the correct trigger or drop the document if no one has subscribed to it.
1-PODRR
The trigger process does not resubmit a service when Deliver Until
property is set to “Successful”.
The trigger retry process rejects the document after one execution attempt of the trigger service when the Deliver Until property for the trigger is set to “Successful”. Trigger retry works correctly when the Deliver Until property is set to ”Max retries exceeded" and a retry count and interval are supplied. When the Deliver Until property is set to “Successful” the trigger should continue to attempt to retry the document until it is successfully processed.
With this update, documents are correctly resubmitted to the trigger when the Deliver Until value is set to “Successful”. The Integration Server will continue to resubmit documents until the service succeeds.
1-PSANJ
Explicit mappings taking longer than necessary.
The flow engine was cloning the pipeline unnecessarily when processing an explicit link between String foo and String foo, causing the process to be slower than necessary.
With this update, mapping has been enhanced to ensure that pipeline cloning is only done when necessary. As a result, implicit and explicit mappings now show similar performance.
1-PSCDS
In a clustered environment, polling sometimes begins on one server in a cluster
before back-end resources on another server in the cluster have finished
initializing.
When polling notification activities are coordinated across a cluster, one instance is often required to initialize back-end resources before any instance can begin polling. If an instance of the same polling notification is started on another server while the first is still initializing the back end, the second instance can start polling before initialization is complete.
This update corrects the problem by forcing other instances to wait for initialization to be completed before polling can begin.
1-PSO0J
In a clustered environment, polling sometimes begins against an uninitialized
back-end resource.
When polling notification activities are coordinated across a cluster, one instance is often required to initialize back-end resources before any instance can begin polling. If initialization fails, it is not detected by other instances of the polling notification and they can begin polling against an uninitialized back-end resource.
This update corrects the problem by causing other instances to attempt initialization if the first failed.
1-PYK4H
In a clustered environment, the wrong instance becomes the primary polling
notification, limiting the administrator’s control over the environment.
When polling notifications are configured to coordinate activities in "standby mode", one instance of the polling notification is designated as "primary", and it executes all polls. Other instances of that polling notification on other servers in the cluster act as hot-standbys, only executing polls if the primary instance stops. The user can control establishment of the primary instance by starting one instance before the others. However, if polling does not begin immediately, another instance could become primary, limiting the administrator’s control over the environment.
This update corrects the problem by establishing the primary instance as soon as the first instance starts.
1-PYK8A
Clustered polling notifications are required to have identical configurations
(both the notification configuration and relevant system configuration
settings) but this restriction is not enforced.
This update enforces that policy by preventing any instance from starting if the relevant configuration settings are not the same as those of any currently operating instance.
1-PYS1L
In a clustered environment, if the configured limit for polling notification coordination
is changed such that the current setting in a polling notification is no longer
valid, the DSP does not initialize correctly.
This update corrects the problem, causing the DSP to initialize as if the coordination mode were set to "disabled."
1-Q0KXR
If a clustered polling notification is shut down while
it is executing a poll, other instances of the polling notification in the
cluster may incorrectly begin executing before the first instance completes.
This update corrects the problem by using separate flags to track polling status and node state.
1-QCDMV
Integration Server enforces old package dependencies.
When installing a new version of a package, Integration Server enforces the dependencies specified by the previous version of the package instead of the new version of the package.
With this update, Integration Server correctly uses the dependencies specified in the new version of the package.
1-QEBV9
Exceptions during the listener shutdown process cause the listener to remain in
a failed state.
Under normal operations, when ART receives an exception that can be retried, ART shuts down the listener, waits for the backoff timeout to expire, then restarts the listener. If the listenerShutdown() call also produces another exception that can be retried, the retry is defeated and the listener remains in a failed state.
This update corrects the problem by preventing exceptions thrown by listenerShutdown from affecting listener operations.
1-QEKTH
Integration Server does not parse S/MIME data if it is a body part of a
multipart message that is not a MIME message.
With this update, Integration Server correctly parses S/MIME data when it is a body part of a multipart message that is not a MIME message.
1-QH03R
Scheduled service execution fails on start up if the scheduler tries to invoke
a service before its package is loaded.
With this update, the user task scheduler now waits until all packages are loaded and their startup services are finished executing.
1-QS7D4
Adapters lose their ACL settings after the Integration Server restarts.
Any ACL settings made on an adapter (using Developer or the Server Administrator) are lost when the Integration Server is restarted. The settings all revert back to the defaults. This causes a security problem.
With this update, adapter ACL settings are now persisted correctly.
1-RDC7C
Listener execution time statistics (visible in the Manager console) incorrectly
include time spent waiting for the data to appear on the back end.
With this update, the execution statistics have been corrected to measure the time spent processing the data once it appears.
1-RHRFM
If a listener notification is shutdown while it is
processing listener data, the shutdown thread and the listener thread use a
single connection. This can cause the listener to fail, particularly if the
connection is transacted.
This update corrects the problem by using a different connection on each thread.
1-RJHH1
Previous implementations of the wm.art.dev.listener:createListenerNode
and wm.art.dev.listener:updateListenerNode services required the caller to
provide values for all metadata properties.
Now the caller only needs to identify the properties it wants to set.
1-RSTC1
Output validation errors mask Java exceptions.
If output validation is enabled when a Java service throws an exception, the Integration Server immediately validates the pipeline output and then reports an output validation error rather than reporting the exception that caused it. The user gets an " Output validation failed" error. This masks the real issue, which is a Java exception.
The Integration Server now reports the original Java exception instead of the validation error.
1-RZM8Z
Adapter polling notifications remain in a pending disabled state indefinitely.
Under certain circumstances, polling notifications can remain in a pending disabled state indefinitely. This requires that a "force disable" operation be performed before the node can be enabled.
This fix corrects the problem and notifications will now proceed to a disabled state when all active polls are completed.
1-S2KC9
Connection Pools are not reset correctly if an exception is thrown from one of
the connections in the pool.
With this update, the entire pool is now reset correctly.
1-SE7HZ
Listener shuts down after a connection attempt fails.
Sometime a listener will shut down, rather than retry a failed connection attempt.
With this update, the Integration Server retries the connection instead of shutting down the listener.
1-SE9KY
The adapter listener retry count is not reset.
The retry counter is not being reset for adapter listeners.
With this update, the retry count is reset if the listener successfully starts up.
1-SE9OF
Adapter services do not retry if an attempt to retrieve a connection fails.
If an adapter service encounters a retry-able exception when attempting to retrieve a connection from the pool, the Integration Server propagates the condition as a non-retry-able exception and does not re-execute the adapter service.
This fix corrects the problem so that the exceptions are properly propagated.
1-SF2S3
Exceptions from the pub.art.transaction:rollbackTranasaction
service are not logged and propagated.
With this update, exceptions that occur when the pub.art.transaction:rollbackTranasaction service executes are logged and propagated.
1-SFF6S
Calls to pub.art.rollbackTransaction fail if a non-fatal connection exception occurs
in a lone transacted connection.
With this update, the rollback succeeds in this situation.
1-SK7KV
Extra pipeline data causes unexpected behavior when certain pub.art* services
execute.
The following services can be adversely affected by pipeline data that is not part of the service signature: pub.art.connection:enableConnection, pub.art.connection:disableConnection, pub.art.listener:setListenerNodeConnection, pub.art.notification:setListenerNotificationNodeListener, pub.art.notification:setPolligNotificationNodeConnection, and pub.art.service:setAdapterServiceNodeConnection.
This update corrects the problem by isolating only the signature fields on the inbound pipeline and using a separate pipeline for forwarded service invocations.
1-T8VNP
An associated connection pool is not reset when an adapter throws an
AdapterConnectionException.
With this update, if an adapter throws an AdapterConnectionException in response to a polling notification, the connection pool is reset (that is, all pooled connections are destroyed and are not regenerated until the next connection request).
1-TEHHT
FTP port does not log client commands and server responses.
With this update, FTP commands and replies through the FTP port are now logged to the journal log (server.log) at level 9 for facility 71.
1-TKK6N
Integration Server incorrectly sets the ObjectStatus value for
omi.wm.is.IsHttpPort, omi.is.IntegrationServer and omi.wm.is.IsPackage to a
Japanese value.
When running webMethods Manager Server in a Japanese locale with a managed Integration Server that has the Japanese Language Pack installed, Integration Server incorrectly sets the ObjectStatus value for omi.wm.is.IsHttpPort, omi.is.IntegrationServer, and omi.wm.is.IsPackage to a Japanese value. This causes incorrect behavior on the Integration Server.
With this update, the ObjectStatus value is always set in English regardless of locale.
1-UTG6P
Integration Server does not properly encode or decode dates.
When java.util.Date objects are marshaled between clients and Integration Server (or serialized and deserialized by pub.flow:savePipeline and pub.flow:restorePipeline) the millisecond value is lost. Also, if the client and server are running in different time zones that use the same time zone abbreviation, the time zone might be corrupted.
This update enhances the serialization format to append milliseconds to the encoded string. Additionally, Integration Server now converts dates to GMT to eliminate time zone conflicts.
1-VF5OZ
The Execute ACL assigned to a top-level folder is reset to Default after
Integration Server restarts.
When a user creates a new folder using the New wizard, the Execute ACL assigned to a top-level folder is reset to Default after Integration Server restarts.
With this update, Integration Server maintains the Execute ACL value across restart.
1-VV6EW
NullPointerExceptions occur during Integration Server startup when a client
attempts to connect to a port before Integration Server is completely
initialized. The stack trace is similar to the following:
java.lang.NullPointerException
at
com.wm.util.Strings.cat(Strings.java:125)
at
com.wm.net.HttpHeader.write(HttpHeader.java:390)
at
com.wm.app.b2b.server.HTTPResponse.send(HTTPResponse.java:231)
This update eliminates this exception.
1-X1RKQ
You cannot perform a "Safe Delete" of a
package that has .jar files in its code/jars directory.
With this update, you can perform a "Safe Delete" of a package that has a jar file in its code/jars directory. However, if the package has a .jar or .zip file in the code/jars/static directory, the "Safe Delete" will fail because jars in code/jars/static are loaded by the application class loader and cannot be released while the application is running.
None.
This release contains the following changes to built-in services and the APIs.
The following services and APIs have been added in this release.
New Services
|
Service Name |
Description |
|
pub.art:listRegisteredAdapters |
Returns the display name and adapter type name of all registered adapters. |
|
pub.art.connection:listAdapterConnections |
Lists connection nodes associated with a specified adapter. |
|
pub.art.listener:listAdapterListeners |
Lists listeners associated with a specified adapter. |
|
pub.art.listener:queryListenerState |
Returns the current state for a listener. |
|
pub.art.listener:resumeListener |
Resumes a specified listener. |
|
pub.art.listener:suspendListener |
Suspends a specified listener. |
|
pub.art.notification:listAdapterListenerNotifications |
Lists the listener notifications associated with a specified adapter. |
|
pub.art.notification:listAdapterPollingNotifications |
Lists the polling notifications associated with a specified adapter. |
|
pub.art.notification:resumePollingNotification |
Resumes a specified polling notification node. |
|
pub.art.notification:suspendPollingNotification |
Suspends a specified polling notification. |
|
pub.art.service:listAdapterServices |
Lists adapter services associated with a specified adapter. |
|
pub.flow:setResponseCode |
Specifies the HTTP response code to be returned by the webMethods Integration Server to a calling process. |
|
pub.io.close |
Closes a java.io.InputStream object. |
|
pub.io:createByteArray |
Creates a byte array of the specified length. This service was moved from the WmFlatFile package. |
|
pub.io.mark |
Marks the current position in the InputStream. This service was moved from the WmFlatFile package. |
|
pub.io.markSupported |
Enables you to test whether your InputStream supports the mark and reset operations. |
|
pub.io.read |
Reads a number of bytes from the InputStream and stores them into a buffer. This service was moved from the WmFlatFile package. |
|
pub.io.reset |
Repositions the InputStream to the position at the time the pub.io:mark service was last invoked on the stream. This service was moved from the WmFlatFile package. |
|
pub.io.skip |
Skips over and discards the specified number of bytes from this InputStream. This service was moved from the WmFlatFile package. |
|
pub.security:setKeyAndChainFromBytes |
Associates a key and certificate chain with the subsequent set of invoked services. |
|
pub.trigger:resumeProcessing |
Resumes document processing for the specified trigger. |
|
pub.trigger:resumeRetrieval |
Resumes retrieval of documents from the Broker for a specific trigger. |
|
pub.trigger:suspendProcessing |
Suspends document processing for the specified trigger. |
|
pub.trigger.suspendRetrieval |
Suspends retrieval of documents from the Broker for a specific trigger. |
New APIs
- com.wm.app.b2b.server.ServerAPI.checkAcl()
A new method, checkAcl(), was added to the com.wm.app.b2b.server.ServerAPI class. This method returns true if the specified user belongs to a group that is a member of the specified ACL. The syntax is:
public static boolean checkAcl(java.lang.String aclName, java.lang.String userName)
- com.wm.app.b2b.server.Service.getHttpHeaderField()
A new method, getHttpHeaderField(), was added to the com.wm.app.b2b.server.Service class. This allows you to access fields in the service’s HTTP response or request headers. The syntax is:
public static java.lang String getHttpHeaderField(java.lang.String fieldName, com.wm.net.HttpHeader header)
- com.wm.app.b2b.server.dispatcher.trigger.TriggerFacade
This new class provides a collection of methods that can be used to suspend and resume document retrieval or document processing for an individual trigger. The class also contains methods that can be used to view and modify trigger properties.
The following services and APIs have been removed in this release.
None.
The following services have been deprecated:
- pub.cluster:disableServiceRedir
- pub.cluster:disableSessionRedir
- pub.security.reverseInvoke:*
To view information about the previous release of webMethods Integration Server, see the previous enhancements and fixes document on the webMethods Bookshelf.
IS-E&F-65-20050520