|
Home > Archive > BizTalk Server Setup > January 2005 > Uninstall assemblies with map and pipeline linked?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Uninstall assemblies with map and pipeline linked?
|
|
| Ben Jiang 2005-01-20, 2:50 am |
| Hi,
You need to remove any maps or customed pipelines linked to an assembly
before you can remove the assembly within Biztalk Explorer.
Now my question is do we have a way by using WMI to create script (like the
ones under samples SDK) to automatically remove receive port(with customed
pipeline or map) first and then to remove the linked assembly?
The reason to do this is because I update my assembly and need to replace
the old one in our production environment (without BT explorer installed).
Another problem is that after I imports the binding file to my production
environment, how do I update sending port credential information such as
username and password?(as we all know that we have to delete username and
password information in our binding xml before we can import into a new
environment). We all know that BT administration console does NOT have
ability to modify thingy!!!??? (I do NOT want to install VS on my production
environment!)
Your help will be highly appreciated.
Cheers
Ben Jiang
| |
| Goutham[MSFT] 2005-01-28, 5:49 pm |
| Ben Jiang,
Here are some answers,
You can remove port using MSBTS_ReceivePort WMI class or by calling
ExplorerOM APIs (you can do both from VBscript).
However, you might not be able to delete port if it is bound to one of the
orchestrations. In that case you need to unbind it first and then you can
delete it (ExplorerOM is the API you need to use for that)
Send port credentials are not easily updatable other than using adapter
configuration XML (it’s a little tricky, since you need to make sure logon
and password are properly XML encoded an injected in the right place in the
XML)
Keep in mind that you can point VS to any management DB, so if your
production environment is in the same domain, you might be able to connect
to it from VS on your dev box
-------
Sample code for doing this and many other functions using EOM is at:
http://msdn.microsoft.com/library/d...-us/sdk/htm/frl
rfmicrosoftbiztalkexplorerom.asp
regards
-g
This posting is provided "AS IS" with no warranties, and confers no rights.
"Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
|
|
|
|
|