Biztalk Server 2004 XSLT problem
Hi all,
I am trying to update a BT04 project that contains an XSLT file (just updating an element to look for a different value), but when I build the project and deploy it the XSLT changes are not present. I found a post that said the following:
If you build the map after making changes to the XSLT and deploy the solution, the map somehow doesn't update itself (even though it works when using the 'Test Map' functionality in VS). I just create a link from the root note of the source map to the root note of the destination map and delete the link to refresh the map. Deploying the map now resolves this issue.But I am unsure how or what to link. Any information on how to fix this issue would be greatly appreciated! Please let me know if any more information would help.
Thanks!
[1239 byte] By [
jheywood] at [2008-2-22]
please, give more information.
Are you moving BTS2004 project to BTS2006R2?
After deploying your map is not working properly, isn't it?
Let's separate your problem and this post you found out.
Thanks for the quick response. No, I'm not migrating the project. It's an existing project on a BT04 server. The directory containing the solution is located on another computer in the network where all of our development projects are kept. I copied the entire directory to a new directory with a new version number (which has been done in the past by others -- version 4 is current). While on the development server, that's running BT04, I open the new project make changes to the xslt file, build it, verify the dll is new by date, unenlist the old orchestration, disable/unenlist the ports, undeploy the old version on the server, deploy the new one, bind the orchestration, restart/renlist the ports, and test. I'm just modifying the XSLT to modify the message mapping (it is external also, not using functoids), and deploying it in the development environment first of course. However, the test messages I put through still have the same old results, not showing the modifications made.
Is there any other information I can provide you?
Actually, after restarting the server, it seems to have corrected itself. Is the .dll cached somewhere that isn't handled by undeployment? I have tested several times since I discovered this and it seems that every time I create a new build with an XSLT change, it is necessary to restart the server for the changes to take effect. Does anyone know if this is always necessary?
You don't need to restart the whole server, you just need to restart the host instance. This is commond development practice you do with BizTalk, most of the BizTalk assemblies like Maps, schemas, Orchestration are cached by BizTalk host instance. So, whenever you make any change just restart the host instance, if you are using isolated adapters reset IIS as well.
Regards,
Saravana Kumar
http://www.biztalk247.com/v1/
http://www.digitaldeposit.net/blog
[Please mark the response as "Answer" if it solves your problem.]
