Author |
Message
|
vijayakranthi |
Posted: Sun Jan 26, 2020 1:29 pm Post subject: Regarding XSL Transform NODE in a message flow |
|
|
Newbie
Joined: 13 Nov 2019 Posts: 9
|
Hi ALL,
Need your inputs about the below scenorio.
Our requirement: To place the xslt on external file system and set the endpoint of the xslt (external file system endpoint) in the local environment properties in the xslt node in a message flow.
Once message flow is deployed, xsl should be cached until we restart the flow or restart the execution group. Is there anyway to do this ?can we use global cache or any other way.
Thanks. |
|
Back to top |
|
 |
timber |
Posted: Mon Jan 27, 2020 8:18 am Post subject: |
|
|
 Grand Master
Joined: 25 Aug 2015 Posts: 1292
|
|
Back to top |
|
 |
arunkumo |
Posted: Mon Jan 27, 2020 1:48 pm Post subject: Re: Regarding XSL Transform NODE in a message flow |
|
|
 Novice
Joined: 21 Sep 2014 Posts: 20
|
vijayakranthi wrote: |
Hi ALL,
Need your inputs about the below scenorio.
Our requirement: To place the xslt on external file system and set the endpoint of the xslt (external file system endpoint) in the local environment properties in the xslt node in a message flow.
Once message flow is deployed, xsl should be cached until we restart the flow or restart the execution group. Is there anyway to do this ?can we use global cache or any other way.
Thanks. |
within the node you can able to set the stylesheet directory right.
why you want to set in output localenvironment again. Choose anyone of the option. |
|
Back to top |
|
 |
vijayakranthi |
Posted: Tue Jan 28, 2020 4:42 pm Post subject: |
|
|
Newbie
Joined: 13 Nov 2019 Posts: 9
|
Hi Timber,
Thank you for your reply. Yes,I have looked this topic,but my requirement is different than it is explained over there.Once the external sheet is set in the properties of xslt node and deployed it should be cached until the message flow is restarted or execution group is started(Even if the xslt is changed in external directory it should not take the latest changes until the message flow is restarted) |
|
Back to top |
|
 |
vijayakranthi |
Posted: Tue Jan 28, 2020 4:44 pm Post subject: Re: Regarding XSL Transform NODE in a message flow |
|
|
Newbie
Joined: 13 Nov 2019 Posts: 9
|
arunkumo wrote: |
vijayakranthi wrote: |
Hi ALL,
Need your inputs about the below scenorio.
Our requirement: To place the xslt on external file system and set the endpoint of the xslt (external file system endpoint) in the local environment properties in the xslt node in a message flow.
Once message flow is deployed, xsl should be cached until we restart the flow or restart the execution group. Is there anyway to do this ?can we use global cache or any other way.
Thanks. |
within the node you can able to set the stylesheet directory right.
why you want to set in output localenvironment again. Choose anyone of the option. |
Hi,
I am not using localenvironment ,I am just using the style sheet name under of XSLT node.Thanks. |
|
Back to top |
|
 |
timber |
Posted: Wed Jan 29, 2020 3:00 am Post subject: |
|
|
 Grand Master
Joined: 25 Aug 2015 Posts: 1292
|
|
Back to top |
|
 |
abhi_thri |
Posted: Wed Jan 29, 2020 3:24 am Post subject: |
|
|
 Knight
Joined: 17 Jul 2017 Posts: 516 Location: UK
|
hi...the details at the infocenter link timber listed seems to imply that the XSLT node should recache the file updates automatically before processing the next message
Quote: |
If you change a cached style sheet (by redeploying or replacing the file in the file system), the XSLTransform node that is holding the cache replaces the cached version with the modified (latest) version before a new message is processed. |
Are you saying that you do not want this default behaviour and instead would like the Node to load the file changes only on explict flow restart? If so what exactly is the rationale for it?
If you think of it, wouldn't it be better to stick to the default behavior so that the changes are picked up immediately as otherwise it might confuse the Support folks (they might assume that the flow is using the latest file on the disk). If you really want to go down this route it may be worth asking IBM to see whether there is any custom environment variable/other settings which would force the flow to recache only on flow restart. |
|
Back to top |
|
 |
|