IC87764: ERRORS SEEN WHEN USING SERVICE DEPLOY AND SUBFLOWS
Fixes are available
Closed as program error.
When using Service Deploy to create a deployable .ear file from a project that uses a subflow that will be contained in a shared library the Service Deploy command will not be able to validate the subflow and will throw an error preventing the .ear from being built. The -ignoreErrors flag will bypass this but will ignore any other errors in the build too.
Using IgnoreErrors options in the command line
A project can be designed to use a subflow in a mediation module but have the definition of the subflow contained in a shared library at runtime instead of the project's .ear file. Service Deploy, when creating the .ear file, would not check the shared libraries on the server which would mean it was unable to find the definition of the subflow which would result in an error. While this could be bypassed by using the -ignoreErrors flag this would also mean any other errors were ignored.
The code was modified to allow the Service Deploy command to find the subflow definition in a shared library on the server. This code fix was targeted to be included in the following fix packs: 7.5.1 Fix Pack 2 (v220.127.116.11) 8.0.1 Fix Pack 1 (v18.104.22.168)
Reported component name
WEB ESB FOR WIN
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
WEB ESB FOR WIN
Fixed component ID
Applicable component levels
Translate this page: