Forum Replies Created
-
Posts
-
Hi,
We have a BizTalk 2004 environment which connects to a MQ Series Queue using the Microsoft BizTalk 2004 Adapter for MQ Series. I have upgaded to BizTalk 2006 on a R&D box and am trying to connect to this same MQ Series Queue and am getting this error:
The adapter \”MQSeries\” raised an error message. Details \”The adapter is not installed or configured correctly on the server . The COM exception is: Retrieving the COM class factory for remote component with CLSID {C34AE9CE-8410-4191-8205-900E08603EC2} from machine X failed due to the following error: 80040154.\”.
On that MQ Box, I have left that existing Adapter Component that needs to run inorder for the 2004 adapter to function.
My question is can I use BizTalk 2006 to communicate with this same component(on the MQ box) or is there a new component that needs to be installed on that box and if so where do I get it from.
Thanks in advance.
well, Neal, I was just creating a dummy application and it’s flow is like ;
1) I will place a xml file with a certain format into a folder A (receiving folder).
2) That file will be processed by orchestration design and and the response Xml file will be sent to folder B.
3) Then a acknowlegment Xml will be generated according to the result ( that is simulated by placing a file of success or failure) in folder C
4) The file is received by BTS and send to a folder D.( just directing it to another folder..)
These 4 folder A B C D are required …its kind of requirement…..so, please kindly guide me how to do it this way.
Please ask for clearification if required futher.
Thanks for responding so quickly.
With Regards
RajatI referred Kishore to this forum. I told him that Enterprise Edition probably requires Windows Enterprise server – and he probably needs to use the developer edition – is that true?
Neal Walters
http://Biztalk-Training.comP.S. Kishore – I also referred you to this page – did it help?
http://blogs.msdn.com/luke/articles/211384.aspx
The QuickStart Guide to Installing & Configuring BizTalk Server 2004 for Windows Server 2003
Even though it says for 2003, the steps for Xp are not much different.Correlation normally works on a promoted field inside the file, so the filename itself is irrelevant.
Neal Walters
http://Biztalk-Training.comFor the first part of your question, you can define two schemas, one for the flat file and one for the desired xml file, then create map that maps from the flat file to the xml file.
You can run and test this with just a simple receive port (and a receive location) and a send port that subscribes to the receive location. On the receive location, attach the map.
For the second part of your question regarding your orchestration and the four folders, I got a list lost. Maybe you could elaborate more specifically.
Neal Walters
http://Biztalk-Training.comSet CopyMode=2 in orchestration for the specific outgoing message and set overwrite property in the physical SendPort in Biztalk Explorer.
Thanks for your reply.
I was wondering how to extract ACK filename since no expression shape is allowed before a Receive in Listen Shape. Apparently a cutome pipeline will do.
Even though i’m on the halfway to achieve this, we decide to avoid the complexity to split the transaction into two parts. One interface just sent G file, and another to receive ACK/ERROR.
For those also face the problem, here’s a really good article includes details about using custom pipleine to extract and change the context properties.
[url]http://geekswithblogs.net/synboogaloo/archive/2005/04/27/38500.aspx[/url]You need to initialize a dynamic port by at runtime providing the address to which you want to send the message (that’s the purpose of dynamic ports). You do this from an expression shape before you send the message to the port, like this:
myPort(Microsoft.XLANGs.BaseTypes.Address) = \”http://www.winterdom.com/whatever\”
Where myPort is the name of your dynamic send port. The example above initializes it to send a message via HTTP, but the exact string will depend on the adapter you want to use to send the message.
You should take a look at Todd Uhl’s SQL White Paper. I think it covers this with a sample.
Should be able to find it here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/BTS_2004WP/html/90a5261b-a220-41bf-bf7f-fd759239242c.asp
The best way is to really read and follow the installation guide available on Microosoft.com. Just go a search on the site for Biztalk 2004 Installation Guide and you should find it.
Good luck!
Not sure if you cut and pasted the original error, or typed it again. If it’s a cut and paste of the actual error, then path is invalid. I do believe however that if you don’t specify a server, it assumes the local box to be the server.
Anyway, you seem to have gotten past that error. For your current issue, are you trying to connect to the same server that the other BizTalk databases are on? If so, the remote connections should have already been figured out. Perhaps it is a security issue. Are you logged in with your account, and what BizTalk groups is that account part of?
Todd Uhl
One way you could do this would be to create a new custom context property on a property schema, and then correlate on that.
What you would do then is have the orchestration write the name of the file (e.g. \”FILE001\”) as the value to this custom property when sending the message while initializing a correlation set built on that property.
Then, I’d have a receive pipeline in the receive port bound to my receive shape that follows the correlation set. The pipeline would have a custom pipeline component that promoted my custom context property to the received message context by extracting the name of the file from the value in the FILE.ReceivedFileName property.
Does that make sense?
[quote:5776069ba3=\”chitchat \”]Within the listen shape i have a recieve shape and a delay shape followed by a construct message on either sides followed by a send shape.
Recieve = Activate – True
Initialising correlation – requestcorrelationset
Delay = new System. Timespan (0,5,0,0)[/quote:5776069ba3]Is the listen shape the first shape in your orchestration?
It makes no sense to have an activatable receive unless the listen shape *is* the first shape in the orchestration (an activatable receive means that you hope to receive through it messages that activate a new instance of an orchestration). If it is like that, then the delay shape does not make sense, because there’s no orchestration instance to timeout on before you receive the activating message.
A setup like yours only makes sense if there are other shapes before the listen shape, and you have a real activatable receive at the start of the orchestration. If that’s the case, then the listen shape should contain a non-activatable receive that *follows* a correlation set (not initializes it).
Why do you need the delay shape? What are you trying to accomplish with it?
