Forum Replies Created
-
AuthorPosts
-
Thanks greg For your reply….As you said My orchestrations are in different assembly…and there is no dependency between two orchestrations…As per your suggestion..there shouldn’t be any issue in my case….I will update as soon as I will done with my deployment.
Thanks
If you stop a host instance all currently active orchestrations are persisted to the MessageBox. Dehydrated and suspended orchestrations are already persisted. On restart all persisted orchestrations are evaluated to see if they should be made active again.
The only problem you may have is if your orchestrations are in the same assembly or have some dependencies that require you to remove both Orch1 and Orch2 assemblies. In order to remove an assembly you must terminate all orchestrations that are currently using that assembly.
Found the solution,
One should enable Journaling on the Table in DB2.
October 15, 2009 at 3:23 AM in reply to: Reference.xsd does not contain Request en Response message type after adding webservice #23462Thanks for your answer, I’ll try that. So the other webservices work because they all have a complex datatype that contains all the request data.
What is the origin of 850 ? Are yor receiving 850 as a EDI file or XML File. If it is a EDI file You have to configure Partys for 850 Transaaction then you need to add 850 Xml Schema to your project to receive that 850 edi File.Once you get 850..You can Map 850 Schema to the Xml Schema by which you are going to insert into Dtabase.
October 14, 2009 at 2:01 PM in reply to: Reference.xsd does not contain Request en Response message type after adding webservice #23460For basic data types like int and string, there is no schema generated.
If you browse the port type created when you imported the wsdl you will see a multipart message defined:Like GetGroupByName_Request, with a part called Group_Name. The message is of type System.String. You cannot use it in a map to create this message but have to assign it a value in a message assignment shape
GetGroupByName_Request.Group_Name = “myname”;
October 14, 2009 at 8:48 AM in reply to: BizTalk Dynamics AX Adapter – Failed to connect to an IPC Port #23458Some investigations from me:
Note:You must run the BizTalk [Dynamics AX 4.0] adapter on a 32-bit operating system. The BizTalk [Dynamics AX] adapter is not supported on Windows Server 2008.”
It seem like it’s not supported on Windows Server 2008 at all (neither 64bit nore 32bit).
Paul
October 14, 2009 at 7:40 AM in reply to: Reference.xsd does not contain Request en Response message type after adding webservice #23457In the wsdl the webservice method is this:
<s:element name=”GetGroupByName”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”Group_Name” type=”s:string” />
</s:sequence>
</s:complexType><wsdl:message name=”GetGroupByNameSoapIn”>
<wsdl:part name=”parameters” element=”tns:GetGroupByName” />
</wsdl:message>wsdl:message name=”GetGroupByNameSecurity”>
<wsdl:part name=”Security” element=”tns:Security” />
</wsdl:message>
<wsdl:message name=”GetGroupByNameTrust”>
<wsdl:part name=”Trust” element=”tns:Trust” />
</wsdl:message><wsdl:operation name=”GetGroupByName”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>This method processes a Group Name and returns a list giving the the full details of the group if it exists in the database.</documentation>
<wsdl:input message=”tns:GetGroupByNameSoapIn” />
<wsdl:output message=”tns:GetGroupByNameSoapOut” />
</wsdl:operation><wsdl:operation name=”GetGroupByName”>
<soap:operation soapAction=”http://questionmark.com/QMWISe/GetGroupByName” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
<soap:header message=”tns:GetGroupByNameSecurity” part=”Security” use=”literal” />
<soap:header message=”tns:GetGroupByNameTrust” part=”Trust” use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
<soap:header message=”tns:GetGroupByNameSecurity” part=”Security” use=”literal” />
<soap:header message=”tns:GetGroupByNameTrust” part=”Trust” use=”literal” />
</wsdl:output>
</wsdl:operation>I added this to the reference.xsd file:
<xs:element name=”GetGroupByName” nillable=”true” type=”tns:GetGroupByName” />
<xs:complexType name=”GetGroupByName” >
<xs:sequence>
<xs:element minOccurs=”0″ maxOccurs=”1″ name=”Group_Name” type=”xs:string” />
</xs:sequence>
</xs:complexType>I also tried this:
<xs:element name=”GetGroupByName”>
<xs:complexType>
<xs:sequence>
<xs:element minOccurs=”0″ maxOccurs=”1″ name=”Group_Name” type=”xs:string” />
</xs:sequence>
</xs:complexType>Thanks,
Bart
October 14, 2009 at 6:12 AM in reply to: Reference.xsd does not contain Request en Response message type after adding webservice #23456What is the signature of the web service method you are calling?
What are the data types you have added?October 14, 2009 at 4:29 AM in reply to: ESB Itinerary transform response ‘was not a valid map type’ #23453I finally made some progress. I reinstalled the ESB Core application and created the Global.ESB sample application using the Dynamic Resolution and Resolver Service samples.
I solved the problem mentioned in my previous post by loading the maps into the Global.ESB application, since the DynamicResolutionSolicitResp send port is in there and it needs to know about my maps and schema’s. No more exception, but no response either.
While doing a file compare of the sample Itineraries and my own I discovered that mine had a different Guid for the DynamicResolutionSolicitResp send port and a (read only?!) property called “isRequestResponse” set to “true” (where mine stated “false”).
Solution was to set isRequestResponse to true on the Off-Ramp extender that I used as a send port filter.
October 11, 2009 at 10:22 PM in reply to: Deployed schema not being found by XmlReceive pipeline #23447Re-gac and restart the host instance
– Kannan Nova
Hi swamy,
You have to be more specific on what type of business problem you are addressing: are you trying to cobble similar messages together? In this case you can use a design patterns like the Sequential Convoy to achieve that. Or are you just doing message splitting? In that case, you are dealing with a different set of logic and implementation.
Daniel.
October 9, 2009 at 1:27 PM in reply to: Deployed schema not being found by XmlReceive pipeline #23444Hi,
After you deploy your schema and assemblies from Visual Studio, make sure to restart BizTalk Server service to clear things in the memory cache. Hopefully, that should fix your problem.
Daniel.
October 9, 2009 at 11:01 AM in reply to: BizTalk Dynamics AX Adapter – Failed to connect to an IPC Port #23443have somebody solved the problem?
I have the same issue with BTS 2009 + Dynamics4 on WindowsServer2008 x64
October 9, 2009 at 7:38 AM in reply to: Deployed schema not being found by XmlReceive pipeline #23441gac the assembly again.
-
AuthorPosts