Integration Server 10.15 | Added, Removed, Deprecated, or Changed Built-In Services | Release 10.15
 
Release 10.15
Added Services
*pub.assets:getHostedAPIs Retrieves the list of APIs in a package on Integration Server.
*pub.flow:setActivityLog Logs user-defined messages to the WMSERVICEACTIVITYLOG table or the WMSERVICEACTIVITYLOG_ yyyymmdd_hhmmss.log file.
*pub.flow:setAuditLogFields Sets the service auditing properties for one or more custom services.
*pub.flow:setCustomLoggedFields Selects the fields of one or more custom services for logging.
*pub.json:jsonToDocument The service converts the JSON data in the input to a document (an IData object). The service allows you to select the data type to which you want to convert an integer, decimal, or boolean value in the JSON data.
*pub.packages:updateHomePage Updates the home page of a custom package. This service does not apply to the system packages.
*pub.security.ports:hostNamesSpec The specification for a service that returns IP addresses or hostnames in the CSV format.
Removed Services
*pub.metadata.assets:publishPackages The WmAssetPublisher package has been removed. There is no replacement service.
Changed Services
*pub.alert.notifier:create The smtpSender/secure/useJSSE input parameter has been removed. All outbound connections use JSSE. If you migrated to Integration Server 10.15 and a migrated service invokes pub.alert.notifier:create, the smtpSender/secure/useJSSE parameter still appears in the pipeline. However, Integration Server ignores the value of the smtpSender/secure/useJSSE parameter, proceeding as if useJSSE were set to yes.
*pub.alert.notifier:update The smtpSender/secure/useJSSE input parameter has been removed. If you migrated to Integration Server 10.15 and a migrated service invokes pub.alert.notifier:update, the smtpSender/secure/useJSSE parameter still appears in the pipeline. However, Integration Server ignores the value of the smtpSender/secure/useJSSE parameter, proceeding as if useJSSE were set to yes.
*pub.alert.notifier:list The smtpSender/secure/useJSSE output parameter has been removed.
*pub.client:http The useJSSE input parameter has been removed. If you migrated to Integration Server 10.15 and a migrated service invokes pub.client:http, the useJSSE parameter still appears in the pipeline. However, Integration Server ignores the value of the useJSSE parameter, proceeding as if useJSSE were set to yes.
*pub.client:smtp The useJSSE input parameter has been removed. If you migrated to Integration Server 10.15 and a migrated service invokes pub.client:smtp, the useJSSE parameter still appears in the pipeline. However, Integration Server ignores the value of the useJSSE parameter ,proceeding as if useJSSE were set to yes.
*pub.client:soapClient The useJSSE input parameter has been removed. If you migrated to Integration Server 10.15 and a migrated service invokes pub.client:soapClient, the useJSSE parameter still appears in the pipeline. However, Integration Server ignores the value of the useJSSE parameter, proceeding as if useJSSE were set to yes.
*pub.client:ftp The secure/useJSSE input parameter has been removed. If you migrated to Integration Server 10.15 and a migrated service invokes pub.client:ftp, the secure/useJSSE parameter still appears in the pipeline. However, Integration Server ignores the value of the secure/useJSSE input parameter, proceeding as if secure/useJSSE were set to yes.
*pub.client.ftp:login The secure/useJSSE input parameter has been removed. If you migrated to Integration Server 10.15 and a migrated service invokes pub.client.ftp:login, the secure/useJSSE parameter still appears in the pipeline. However, Integration Server ignores the value of the secure/useJSSE input parameter, proceeding as if secure/useJSSE were set to yes.
*pub.file:getFile The service now includes the optional largeFile input parameter that indicates whether the file specified in the input is a large file or not.
*pub.json:documentToJSONString The service now includes the optional encodeStringAsBoolean and encodeStringAsNumber input parameters.
*encodeStringAsBoolean If true, converts a boolean value in the string format to boolean by removing the quotes. If false, the boolean value remains in the string format.
*encodeStringAsNumber If true, converts a number in the string format to number by removing the quotes. If false, the number remains in the string format.
*pub.security:encrypt The service now includes the optional publicKeyString input parameter to provide one or more public keys as strings to encrypt data for one or more recipients.
The service also includes the string output parameter to return the encrypted data as a string in the ASCII-armored format when the input to the service is a string.
The data type of the publicKeyBytes input parameter is changed from Byte Array to Object List to provide multiple public key files as byte arrays to the service.
The data type of the publicKeyAlias input parameter is changed from String to String List to provide public key aliases for multiple public keys in a keyring file.
*pub.security:decrypt The service now includes the optional secretKeyString input parameter to provide a secret key as a string to decrypt the data.
The service also includes the string output parameter to return the decrypted data as a string when the input to the service is a string.
*pub.security:decryptAndVerify The service now includes the optional input parameters, secretKeyString to pass a secret key as a string to decrypt the data, and publicKeyString to provide one or more public keys as strings to verify the signature of the decrypted data for one or more recipients.
The service also includes the string output parameter to return the decrypted and verified data as a string when the input to the service is a string.
The data type of the publicKeyBytes input parameter is changed from Byte Array to Object List to provide multiple public key files as byte arrays to the service.
The data type of the publicKeyAlias input parameter is changed from String to String List to provide public key aliases for multiple public keys in a keyring file.
*pub.security:sign The service now includes the optional secretKeyString parameter to pass a secret key as a string to sign data.
The service also includes the string output parameter to return the signed data as a string in the ASCII-armored format when the input to the service is a string.
*pub.security:signAndEncrypt The service now includes the optional secretKeyString input parameter to pass a secret key as a string to sign the data and the publicKeyString input parameter to provide one or more public keys as strings to encrypt the signed data for one or more recipients.
The service also includes the string output parameter to return the signed and encrypted data as a string in the ASCII-armored format when the input to the service is a string.
The data type of the publicKeyBytes input parameter is changed from Byte Array to Object List to provide multiple public key files as byte arrays to the service.
The data type of the publicKeyAlias input parameter is changed from String to String List to provide public key aliases for multiple public keys in a keyring file.
*pub.security:verify The service now includes the optional publicKeyString parameter to provide one or more public keys as strings to verify the signed data for one or more recipients.
The service also includes the string output parameter to return the verified data as a string when the input to the service is a signed string.
The data type of the publicKeyBytes input parameter is changed from Byte Array to Object List to provide multiple public key files as byte arrays to the service.
The data type of the publicKeyAlias input parameter is changed from String to String List to provide public key aliases for multiple public keys in a keyring file.
*pub.xml:queryXMLNode The service now longer supports String Table as resultType.