[community-content]

Have you tried using the RawString type as the message type in your orchestration? ( The same one used in the examples for HTML emails using the SMTP adapter in the biztalk documentation).

[community-content]

Ram,

Happy to provide an example, however it would be good to get a better idea of what you are trying to acheive so we don't go down the wrong path.

Nick. 

[community-content]

Can u give any url that solves me this problem?Without  web service can we  port data.

We need to test the orchestration know bwfore we deploy?

 

 

[community-content]

Can u give any url that solves me this problem?Without  web service can we  port data.

We need to test the orchestration know bwfore we deploy?

 

 

[community-content]

Hi Nick,

 Thanks for the prompt reply. Can you provide sample to do it custom pipe. As i need to combine two feilds and promote them,or do i need to promote two fields. will that makes anything complicated as i need them in BAM.

 Thanks

ram

[community-content]

Hi Ram,

Only unique elements can be promoted and two elements *cannot* be promoted to create one unique field 'out of the box' – have a look at for more information http://msdn2.microsoft.com/en-us/library/aa561059.aspx. I think you could probably fudge something with distinguished fields
but I doubt it'll be supported by Microsoft, but properties promoted in
a custom pipeline component from a combination would be possible

If you need to read read the value of a repeating element in an orchestration, you'll need to dive out to XPath in an Expression shape. 

Hope this helps,

Nick. 

[community-content]

mtassin,

I encountered exactly the same problem (albeit on a Windows 2003 Ent Ed R2
SP2 installation). After a bit of digging around, I came across [1] which
seemed to imply a repair of the .Net 2.0 framework would resolve the problems.
It did, but I then received the same error for the
Microsoft.BizTalk.Adapter.MQS.dll assembly. After some further digging around I
came across [2] which seemed like a bit of hard-work. 

On an off-chance, I connected my machine to the net (I'm running the
environment in a VMWare machine and it was only connected locally) and the
installation worked without error – I am now working through the configuration.

I don't know if connecting to the 'net did anything, but something worked to
resolve the error. I would suggest you look through those two links and see
whether either of them work for you.

Good luck!

[1] http://www.webservertalk.com/message1430831.html

[2] http://www.nivot.org/2006/01/03/BizTalkSetupError.aspx

[community-content]

Guhan,

I am by no means an expert on the BizTalk Peoplesoft LOB adapter, however if
you read the 'Microsoft BizTalk Adapters for Peoplesoft' document available at http://www.google.co.uk/url?sa=t&ct=res&cd=3&url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2F1%2F6%2F9%2F16968441-c6c8-4bd0-9410-5f4014bc61f0%2Fpeoplesoft.doc&ei=iHsYR46JFaD8wwHD5LySCA&usg=AFQjCNHdHlMQ_R2GFax-HkJXEsO_RmRk9Q&sig2=J0JmXwmTM0hMBtqKevQ_2w

this should give you a good starting point.

To answer your question, you will use the Peoplesoft LOB Adapter to retrieve
data from Peoplesoft and that data will be in an Xml format. You will then map
the Peoplesoft Xml into a format that represents an Insertgram for SQL Server
and insert the data using the BizTalk SQL Adapter that comes 'in the box'.

Delving into the technical aspect of this solution, it would appear that you
cannot poll Peoplesoft (using the LOB adapter) on a receive location (see the
final paragraph on page 9 of the aforementioned document). So, you will need to
use an orchestration to send a request message (over a send port –
solicit/response) to Peoplesoft to gather the necessary data for delivery to
SQL Server. Once you have received a response from Peoplesoft, you can map the
data into the SQL Xml format and send that to SQL Server using a Send Port
configured to use the BizTalk SQL Adapter. Note, you'll need to trigger the
orchestration using a 'throw-away' message.

To generate the necessary Xml schemas (XSD's), use the 'Add Generated Items'
tool in Visual Studio and use the 'Add Adapter Metadata' option selecting the
relevant adapter to use.

Section 3.3.1 of the above document (Design
Pattern: Receive Handler—from PeopleSoft to BizTalk Server) will also help
with your specific problem.

Hope this helps, Nick.

[community-content]

Jens,

The user you used to *run* the install process needs to be admin/dba, *not* the user biztalk services will run under. If you did it that way, though, then simply remove it from the administrators group and remove the user the sysadmin and related privileges in sql.

[community-content]

Here are 2 excellent books that I used to learn BizTalk; this site is very helpful too.

BizTalk 2006 Recipes: A Problem-Solution Approach    ISBN: 1-59059-711-7

Pro BizTalk 2006     ISBN:1-59059-699-4

[community-content]

When you build and deploy the application you have to use the BizTalk Administration Console to "Configure" the application. Configuration includes altering Send/Receive ports. So you can't test the application without specifying send and receive ports; they must be configured before the application starts.

I haven't worked with the PeopleSoft adapter…if PeopleSoft communicates through a Web Service, then yes you do. Otherwise, no you need to specify an adapter for PeopleSoft, which may be a SQL adapter.

[community-content]

How can i test the project without specifying send and receive ports? 

in receive port do we need to include a web service?

Any url or example or webcast u have?

 

 

[community-content]

HI Greg,

 Thanks for the reply. i solved the issue i used custom xslt to make it work. Actaully i am asking how to map two xml files without using any functoids.

 Thanks

 

[community-content]

Hi flasbeir,

We're getting exactly the same two error messages 4-5 times in a day. The system was working good in the test environment. Last week we went on production where the quantity of the messages are very big. We opened a case on Microsoft about this issue. We send event logs for the Mqseries side, biztalk server and network trace files to the microsoft. They're currently working on this issue.

You posted this thread on 03-13-2007. It was 7 months ago. What was the situation of your problem ?

Thank you.

 

 

[community-content]

Possible Solution: I have a round-about way of solving this conundrum…

Have a FILE adapter configured to pickup the EDI file at location B, write a message EDI File Context message to the message box, then write the EDI file to Folder B. EDI File Adapter picks up EDI files from folder B and has a parallel receive port that subscribes to EDI File Context messages. Only when the Orchestration has received the EDI Message and the corresponding EDI File Context message will the orchestration continue.

This is very round-about and I find it very stupid that the Received File Name is not included in the original BizTalk 2006 Release. If anyone can think of a reason that this wouldn't work, let me know…let me know if you think it will work to 😉

[Author]

Posts