When you create an output template within a package, it is stored in the package’s “templates” folder with a filename “[Package][Interface][Service].html”. When the output template is invoked, the webMethods B2B/IS Server uses the default path – which a developer can override.
Use pipeline variable substitution and you will be able to make run-time decisions regarding the proper output template for a transaction.
To perform pipeline variable substitution for the output template, do the following:
-
Create your output templates and save them to the package’s “templates” directory.
-
Select the service to which you want to apply the template(s).
-
Select the “Settings” tab and specify “$template” for the name of the Service Output Template. Be sure to select Type “HTML | XML | WML | HDML”
-
In your Flow, assign the variable “$template” the name of the intended output template to designate your output template. You don’t have to include the full path to the template.
– OR –
You could always just use the pub.report: built-in services (pub.report:runFileTemplate, pub.report:runStringTemplate, pub.report:runTemplate). These services are described in the Built-In Service Guide PDF which can be found in the “docs/” directory of your B2B Server/Integration Server install directory.
#webMethods#Flow-and-Java-services#Integration-Server-and-ESB